Professional Documents
Culture Documents
Version: V1.2.1
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
R1.1 2010-12-30 Update information about GCSA, GCSAS and EIGMP cards
I
2.12.1 Customizing the Polling Tasks ............................................................... 2-54
2.12.2 Starting the Fault Management.............................................................. 2-57
2.12.3 Customizing the Display Columns ......................................................... 2-59
2.12.4 Customizing the Current Alarm Query Profile ......................................... 2-61
2.12.5 Customizing the History Alarm Query Profile .......................................... 2-63
2.12.6 Customizing the Alarm Rules ................................................................ 2-66
2.12.7 Redefining the Alarm Severities............................................................. 2-71
2.12.8 Setting the Alarm Sounds ..................................................................... 2-72
II
3.11.1 Configuring the LACP Protection ........................................................... 3-57
3.11.2 Configuring the UAPS Protection ........................................................... 3-60
3.12 Configuring the ONU Authentication Mode ....................................................... 3-62
3.13 Configuring the PON Port Protection................................................................ 3-64
3.14 Configuring the VLAN ..................................................................................... 3-67
3.15 Configuring the Multicast Service..................................................................... 3-71
3.16 Configuring Smart QinQ.................................................................................. 3-84
3.17 DHCP Configuration ....................................................................................... 3-87
3.17.1 Overview of DHCP ............................................................................... 3-87
3.17.2 Configuring the DHCP Snooping ........................................................... 3-88
3.17.3 Configuring the DHCP Relay ................................................................. 3-92
3.17.4 Configuring the DHCP Server................................................................ 3-98
III
5.2.2 F822 NE Creation (GPON) ..................................................................... 5-32
5.2.3 Global Parameter Configuration for the F822 (GPON) .............................. 5-32
5.2.4 Service Configuration of the F822 (GPON)............................................... 5-32
IV
About This Manual
Purpose
The ZXA10 C220 xPON Optical Access Convergence Equipment (ZXA10 C220 for short)
is a full-service optical access platform. It supports the video, data, voice, TDM, and CATV
services. The ZXA10 C220 can be connected with ONUs of medium or larger capacity
through various networking technologies.
The ZXA10 C220 device consists of the main control and switching card, xPON subscriber
cards, CES uplink card, and Ethernet uplink card. It provides large-capacity controllable
multicast and high QoS control.
This manual provides detailed information about configurations (NetNumen) on the ZXA10
C220 xPON Optical Access Convergence Equipment.
Intended Audience
This document is intended for:
l Installation and debugging engineer
l System maintenance engineer
l Data configuration engineer
Chapter Summary
Chapter 1, NetNument N31 Overview Introduces the architecture and version of the
NetNumen N31 system.
Chapter 2, NetNumen N31 Installation and Describes the installation and configuration of the
Configuration NetNumen N31 system.
Chapter 4, EPON FTTB ONU Configuration Describes the EPON FTTB ONU data configuration.
Chapter 5, GPON FTTB ONU Configuration Describes the GPON FTTB ONU data configuration.
Chapter 6, EPON FTTH ONU Configuration Describes the EPON FTTH ONU data configuration.
I
Chapter Summary
Chapter 7, GPON FTTH ONU Configuration Describes the GPON FTTH ONU data configuration.
Related Documentation
The following documentation is related to this manual:
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Documentation
Guide
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Feature Guide
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Product
Description
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Hardware
Description
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Cabinet
Installation Guide
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Configuration
Manual (CLI)
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Configuration
Manual (NetNumen) Volume II
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Maintenance
Manual
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Alarm and
Notification Message Reference
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Command
Reference (Volume I)
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Command
Reference (Volume II)
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Command
Reference (Volume III)
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Command
Reference (Volume IV)
l ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Command
Reference (Volume V)
Conventions
ZTE documents employ the following typographical conventions.
Typeface Meaning
Bold Menus, menu options, function names, input fields, radio button names, check
boxes, drop-down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens and company name.
II
Typeface Meaning
Typeface Meaning
Click Refers to clicking the primary mouse button (usually the left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button (usually the left mouse button)
twice.
Right-click Refers to clicking the secondary mouse button (usually the right mouse button)
once.
III
IV
Declaration of RoHS
Compliance
To minimize the environmental impact and take more responsibility to the earth we live,
this document shall serve as formal declaration that the ZXA10 C220 manufactured by
ZTE CORPORATION is in compliance with the Directive 2002/95/EC of the European
Parliament - RoHS (Restriction of Hazardous Substances) with respect to the following
substances:
l Lead (Pb)
l Mercury (Hg)
l Cadmium (Cd)
l Hexavalent Chromium (Cr (VI))
l PolyBrominated Biphenyls (PBB’s)
l PolyBrominated Diphenyl Ethers (PBDE’s)
The ZXA10 C220 manufactured by ZTE CORPORATION meets the requirements of EU 2002/95/EC;
however, some assemblies are customized to client specifications. Addition of specialized,
customer-specified materials or processes which do not meet the requirements of EU 2002/95/EC
may negate RoHS compliance of the assembly. To guarantee compliance of the assembly, the
need for compliant product must be communicated to ZTE CORPORATION in written form. This
declaration is issued based on our current level of knowledge. Since conditions of use are outside
our control, ZTE CORPORATION makes no warranties, express or implied, and assumes no liability
in connection with the use of this information.
I
II
Chapter 1
NetNument N31 Overview
Introduction
The NetNumen N31 unified management system is a unified network management
system, which provides centralized and unified network management on all ZTE PON
products. It also provides customers with a unified and friendly management interface.
System Architecture
The NetNumen N31 unified management system consists of the database server,
NetNumen N31 server, and NetNumen N31 client. Figure 1-1 shows the architecture of
the NetNumen N31 system.
System Version
The NetNumen N31 unified management system is applicable to all PON products, as
described in Table 1-1.
1-1
F820
F821
F822
F803
F809
9806H
1-2
Prerequisites
Before this operation, make sure that:
l Server: The patches of the OS and the database are updated.
2-1
Caution!
When the new computers with the pre-installed OS are used for networking, the computer names may
be the same. If the host has the same name as another computer in the network, the NMS cannot be
started.
Context
The NetNumen N31 NMS can be installed and run on the following operating systems:
l Windows 2000 Server, Windows 2003 Server, Windows XP Professional
l UNIX Solaris 8, UNIX Solaris 9, UNIX Solaris 10
This topic takes the Windows operating system as an example.
Steps
1. Decompress the installation package.
The NetNumen N31 software installation package is delivered in .zip format.
Decompress it in the first-level directory as follows:
l Windows: D:\n31version\
l Solaris: /export/home/n31version/
Table 2-1 lists the files in the installation directory after the package is decompressed.
In the directory where the decompressed installation file is located, run the install
.bat program to install the NetNumen N31 NMS.
2-2
Caution!
In Solaris, run the install.sh script file. If you have no right to run the script file, modify the
user right first.
After the install.bat program is run, the NetNumen Install window is displayed,
as shown in Figure 2-1.
Type the installation path in the installation window, as shown in Figure 2-2.
2-3
Note:
The installation path cannot exceed 240 characters. The installation program automatically cre-
ates the netnumen directory. The following installation paths are recommended:
l In Windows: D:\
l In Solaris: /export/home/
2-4
l 2: Install both the NetNumen N31 Client and NetNumen N31 Server.
After selecting the installation type, press Enter to start installation.
6. Wait for the installation process.
Due to the large number of files, the decompression needs certain time. After the files
are decompressed, the program automatically starts NetNumen Config Center.
– End of Steps –
Result
The NetNumen N31 NMS is installed successfully.
Context
The NetNumen N31 Client is generally installed in Windows. When the Client is installed
and configured, its installation directory can be compressed to create a Green Client. The
Green Client has finished the configuration, such as NE deployment.
To create and install the NetNumen N31 Green Client, perform the following steps:
Steps
1. Create the Green Client.
a. Install the NetNumen N31 Client.
Refer to the section 2.1 Installing the NetNumen N31 NMS.
2-5
Caution!
Before compressing the Client directory, do not start the Client application. A temporary file is
generated when the Client is started for the first time. If the temporary file is open, the Green
Client cannot be started.
If you have started the Client before compressing the Client directory, you need to clear the
temporary file first. For detailed operations, refer to the topic Delete Temp File Tool in the
ZXA10 C220 (V1.2.1) xPON Optical Access Convergence Equipment Configuration Manual
(NetNumen) Volume II.
Note:
Because the original NetNumen directory occupies large space, you need to clear the recycle
bin to release the disk space after deleting the original installation directory.
Note:
2-6
Result
The NetNumen N31 Green Client is created and installed.
Prerequisites
Before this operation, make sure that:
l The NMS database and configuration information are backed up.
l The upgrade patch files are prepared.
Context
To install the NetNumen N31 patches, perform the following steps:
Steps
1. Exit the NetNumen N31 Client and Server processes.
2. Copy the patch files.
If the patch package already contains the platform upgrade package, the system
prompts the following information during the upgrade process:
Upgrade Container must be upgraded.
Please run upgradeSelf.bat or upgradeSelf.sh
in the parent directory,
and then run upgrade container again.
Note:
2-7
After the Client is upgraded, the system automatically generates the directory .\ne
tnumen\upgradeN31\server\upgrade-package-for-client-download\.
Make sure that the directory contains the Client upgrade patch file.
5. Upgrade the database.
Go to .\netnumen\ums-svr\docs\dbscript\install-db\ and run update-
db.bat to upgrade the database.
Note:
Note:
When the NetNumen N31 Client connects to the NetNumen N31 Server that is installed with
patches, the Client automatically installs the patches from the Server.
– End of Steps –
Result
The NetNumen N31 patches are installed successfully.
Note:
To make the modifications effective, you need to restart the NetNumen N31 Server after modifying the
parameters on NetNumen N31 Config Center.
When NetNumen N31 NMS installation is complete, the system starts the NetNumen
configuration center automatically. Besides, you can access the NetNumen configuration
center in the following ways:
l Choose Start > Programs > NetNumen N31 > Tools > NetNumen N31 Config
Center to open the NetNumen Config Center window.
l Run .\netnumen\bin\configcenter.bat to open the NetNumen Config
Center window.
2-8
Note:
In Solaris, you can run configcenter.sh in the relevant path to open the NetNumen Config
Center window.
Prerequisites
Before this operation, make sure that you have accessed NetNumen Config Center.
Context
To configure the basic information, perform the following steps:
Steps
1. Open the Basic Information window.
In the NetNumen Config Center window, select Basic Information from the left pane,
as shown in Figure 2-4.
2-9
2-10
Note:
The memory configured here is the maximum memory space that the JDK can allocate. NetNumen
N31 can configure the 32-bit or 64-bit JDK according to the NE scale. The following configuration
is recommended:
l When the server memory does not exceed 4 GB, use the 32-bit OS and 32-bit JDK.
l When the server memory exceeds 4 GB, use the 64-bit OS and 64-bit JDK.
Result
The basic information is configured successfully.
Prerequisites
Before this operation, make sure that you have accessed NetNumen Config Center.
Context
To configure the NE module, perform the following steps:
Steps
1. Open the NE Module window.
In the NetNumen Config Center window, select NE Module from the left pane, as
shown in Figure 2-5.
2-11
NE Type Service
– End of Steps –
2-12
Result
The NE module is configured successfully.
Prerequisites
Before this operation, make sure that you have accessed NetNumen Config Center.
Context
Because the data files of the database occupy large space, it is better to specify a directory
for the data files when installing the SQL Server database. The database application files
and the data files should be saved in different partitions.
If the directory is not specified, the data files and application files are installed in the same
directory.
To configure the database, perform the following steps:
Steps
1. Open the Database Configuration window.
In the NetNumen Config Center window, select Database Configuration from the
left pane, as shown in Figure 2-6.
2-13
2-14
When the SQL Server database is optimized, the database log mode is changed to
the simple mode. When the SQL Server database is installed for the first time, it needs
to be optimized; otherwise, the database log files may occupy too much space.
Note:
If both of the NetNumen N31 NMS and database are installed for the first time, the database can
be automatically optimized only after the database is initialized. For how to initialize the database,
refer to the topic 2.5 Initializing the Database.
Result
The database is configured successfully.
Follow-Up Action
If the database connection fails, make sure that:
l The database server is installed with the latest upgrade patches. (SQL Server 2000
needs to be installed with Service Pack 4 and SQL Server 2005 needs to be installed
with Service Pack 3.)
l The IP address, port number, administrator name, and password of the database
server are correctly configured.
l The database server is started. Refer to the steps listed in Table 2-5.
MS SQL Server Choose Start > Programs > Microsoft SQL Server 2005 > Configuration
Tools > SQL Server Configuration Manager to insure that the SQL Server
is running.
Oracle Log in to the NMS server where the database is, and then carry out the
following command:
#ps – ef | grep ora
Insure that the Oracle processes are started.
2-15
Telnet to the NM Server where the database is installed, and carry out the following
commands:
$ lsnrctl start //Start the monitor.
$ sqlplus /nolog //Enter the sqlplus.
//nolog means the user does
not log in to the server.
SQL> connect /as sysdba //Connect the database as
the system administrator (sysdba).
//Type the username as system,
and the password as netnumen.
SQL> startup //Start the database server.
SQL> exit //Exit sqlplus.
Prerequisites
Before this operation, make sure that you have accessed NetNumen Config Center.
Context
To configure the FTP service, perform the following steps:
Steps
1. Open the FTP Service window.
In the NetNumen Config Center window, select FTP Service from the left pane, as
shown in Figure 2-7.
2-16
Use Outside FTP It is not selected by default. l In Windows: Both the internal FTP
Server service (provided by the NMS server
process) and external FTP service can
be used.
l In Solaris: Only the external FTP
service can be used, because Solaris
provides the FTP service.
FTP users l update: The user name FTP users that need to be configured when
used for client automatic the external FTP service is used.
upgrade
l webnms: The user
name used for uploading
or downloading the
9806H, F822, and F821
configuration data
l uni: The user name
used for uploading or
downloading the F820
configuration data
2-17
Note:
l When you are downloading the version files, the NMS lists all the files under the FTP user
directory according to the settings on the configuration center, and then sends commands to
the NE. If the path set on NetNumen Config Center is inconsistent with that corresponds to
the FTP user, the version file cannot be uploaded or downloaded.
l When multiple IP addresses are configured on the NMS server, change the IP address of
the FTP user and select the IP address that connects to the NE device, to ensure correct
FTP operations.
Result
The FTP service is configured successfully.
Prerequisites
Before this operation, make sure that you have accessed NetNumen Config Center.
Context
To configure the policy, perform the following steps:
Steps
1. Open the Policy Configuration window.
In the NetNumen Config Center window, select Policy Configuration from the left
pane, as shown in Figure 2-8.
2-18
2-19
2-20
Note:
The functions of the Uep, Caffm, and UepPm databases are as follows:
l Uep: Saves the data of NEs, topology , resources, operation logs, and rights.
l Caffm: Saves the data of the current alarms, history alarms, event notifications, and alarm
rules.
l UepPm: Saves the performance statistics tasks and performance data.
– End of Steps –
Result
The policy is configured successfully.
Prerequisites
Before this operation, make sure that you have accessed NetNumen Config Center.
2-21
Context
Note:
Steps
1. Open the Short Cut window.
In the NetNumen Config Center window, select Short Cut from the left pane, as
shown in Figure 2-9.
– End of Steps –
Result
The shortcuts are configured successfully.
2-22
Prerequisites
Before this operation, make sure that:
Context
If the NetNumen N31 NMS and database are installed for the first time, you need to initialize
the database.
To initialize the database, perform the following steps:
Steps
1. Run the database initialization program.
l In Windows, choose Start > Programs > NetNumen N31 > Tools > NetNumen
N31 Init Database. The NetNumen N31 Init Database window appears, as
shown in Figure 2-10. Type Y and press Enter to start initialization.
2-23
Caution!
Before running ./install-db.sh, switch to the Oracle user. The command is as follows:
#su-oracle
2. Complete initialization.
The initialization process needs a few minutes. When the interface prompts the
following message, it indicates that database initialization is complete.
BUILD SUCCESSFUL
– End of Steps –
Result
The database is initialized successfully.
Prerequisites
Before this operation, make sure that:
l The NetNumen N31 unified management system is installed.
l The database server is started.
Context
To start the NetNumen N31 Server and Client, perform the following steps:
Steps
1. Start NetNumen N31 Server.
The NetNumen N31 Server can run in both the Windows operating system and the
Solaris operating system.
l To start NetNumen N31 Server in the Windows operating system, you can perform
any of the following operations:
à Choose Start > Programs > NetNumen N31 > NetNumen N31 Server.
à Double-click the NetNumen N31 Server shortcut icon on the desktop.
à Run the .\netnumen\bin\startNmsClient.bat file.
Figure 2-11 shows that the NetNumen Server starting window in the Windows
operating system.
2-24
l To start NetNumen N31 Server in the Solaris operating system, perform the
following steps:
Log in to the Solaris server as the “root” user. Use the following commands to
start the NetNumen N31 Server:
$ cd /export/home/netnumen/bin //Open the directory of the
NetNumen Server startup program.
$ ./remoteStartServer.sh //Run the script to start the
NetNumen Server process remotely.
Use the following command to check the running status of the NetNumen N31
Server process.
$ tail -f startNmsServer.log
2-25
Generally, the NM server finishes the startup in five minutes, including the following
processes:
l NetNumen process
l COBRA notify process
l FTP process
When the three processes are started successfully, the NM Server startup is finished,
as shown in Figure 2-12.
Figure 2-13 shows the login window of the NetNumen N31 Client.
2-26
– End of Steps –
Result
Both the NetNumen N31 Server and Client are started successfully.
2-27
Prerequisites
Before this operation, make sure that the NetNumen N31 unified management system is
installed.
Context
The MetricX system is a traffic monitoring and polling system, which is in the distributed
structure. Figure 2-15 shows the topology of the MetricX system.
The MetricX system consists of the server and client. Table 2-8 describes the functions of
the MetricX system.
MetricX Server Control server The control server is the control center of the MetricX
system. All polling servers send the importing and
query requests to the control server. The control server
distributes the collection points and the query requests
to the polling server.
2-28
MetricX Client The MetricX You can open the History Traffic Collection and Traffic
client is History Query windows by right-clicking the NE, in the
integrated in the Rack window, or in the ONU configuration windows
NetNumen N31 such as the ONU Configuration and Port Management
Client. window.
Note:
In addition, the MetricX system provides the northbound interface of the third-party FTP report table to
save the performance report data. This function is enabled when the third party wants to save the data
in the FTP server.
Configuration Data
Practically, you need to install and configure the MetricX server. It is unnecessary to
configure the MetricX client.
This topic introduces the procedure of deploying the MetricX server by using an instance.
Table 2-9 describes the configuration data.
NetNumen N31 Server 192.168.1.100 The computer on which the NetNumen N31
Server is installed
Control server 192.168.1.100 To save the server resources, the control server,
data transaction server, and the NetNumen N31
Data transaction server 192.168.1.100
Server are installed on the same computer.
To deploy the history traffic monitoring system, perform the following steps:
Steps
1. Configure the parameters of MetricX servers.
a. Start MetricX configuration center.
2-29
Note:
In the Solaris operating system, you need to run the metricxCfgCenter.sh file.
2-30
Note:
l The NE scope can not be duplicated or overlapped.
l If there is only one polling server, you just need to configure the NE scope of this
polling server.
2-31
Note:
You can skip this step if the polling server and the NetNumen N31 Server are installed on the
same computer.
2-32
In this example, two polling servers are deployed. You need to modify the
subserverno value as 2, and then save the configuration file.
Note:
l The IP address of the polling server 1 is already configured in the MetricX configuration
center. You can skip this step if only one polling server is deployed.
l If more than one polling servers are deployed, you can modify the subserverno value
to add the polling server. The polling server numbers cannot be repeated and the IP
scope is already configured in Traffic History Collection Config Center window.
The MetricX databases include the control server database and the polling server
database. You need to initialize both databases before you start the MetricX system.
a. Initialize the control server database.
Note:
When you select 1 to create a new database, you need to check the disk space to make sure
there is enough space for the database.
2-33
Note:
In the Solaris operating system, run startMetricxSvr.sh to start the MetricX server.
Note:
In the Solaris operating system, run startMetricxSvr.sh to start the MetricX server.
2-34
On the Control Server tab, configure the IP address of the control server, as
shown in Figure 2-22.
Note:
You need to run the MetricX configuration center and save the configurations if the NetNumen
N31 Client is upgraded.
– End of Steps –
Result
The history traffic monitoring system is configured successfully.
2-35
Prerequisites
Before this operation, make sure that the NetNumen N31 unified management system is
installed.
Context
The NetNumen N31 unified management system is connected to the upper-layer network
management system through the northbound interface, such as the TL1, Syslog, SNMP,
XML, CORBA, FTP, and APP interface. The TL1 interface is recommended because it
supports a more flexible solution to connect to the existing OSS system.
Figure 2-23 shows the relationship among the upper-layer OSS system, the NetNumen
N31 unified management system, and the northbound interface.
Figure 2-23 Relationship of OSS, NetNumen N31 and the Northbound Interface
Note:
By default, the TL1 interface is enabled after the NetNumen N31 unified management system is in-
stalled. You need to configure the parameters related to TL1 interface and test the TL1 interface.
To configure and test the TL1 northbound interface, perform the following steps:
Steps
1. Configure the northbound interface.
2-36
Parameter Description
FILTER_SEVERITY l Critical: 1
l Major: 2
l Minor: 3
l Warning: 4
l Inform: 5
Example:
CHG-PORT-STAT::DID=10.10.99.99,PID=1-1-2-1:8::STATUS=disable;
2-37
Table 2-11 describes some keywords and parameters in the TL1 commands.
Keyword/Parameter Description
– End of Steps –
Result
The TL1 northbound interface is configured successfully.
Prerequisites
Before this operation, make sure that:
l The settings on NetNumen Config Center are complete.
2-38
Context
The NetNumen N31 NMS automatically carries out the configured policy tasks periodically.
The following policies are recommended:
l Backup and Delete Alarm Policy
l Backup and Delete Log Policy
l Synchronize Configuration Data Policy
l Export NE Performance Data Policy
l Data Configuration Backup Policy
l NMS Database Backup Policy
l Running Configuration Save To Flash Policy
l DSL Port Log Retrieve Policy
Steps
1. Display the Policy Management tab.
In the NetNumenN31 Unified Management System window, choose View > Policy
Management. The Policy Management tab is displayed, as shown in Figure 2-25.
From the navigation tree on the left, select Policy Group or Policy Status to view
the created policies. You can perform different operations on a policy, as described in
Table 2-12.
2-39
Refresh l From the main menu, choose Refresh the policy list.
Operation > Refresh.
l Click .
Create Policy l From the main menu, choose Create a policy. Refer to Instance
Operation > Create Policy. of Creating a Policy.
l Click .
Find Policy l From the main menu, choose Find policies according to the
Operation > Find Policy. policy name. You can select the
l Click . Case Sensitive check box.
Delete Policy l Select a policy, and then When the system displays the
choose Operation > Delete Confirm dialog box, click Yes to
Policy from the main menu. delete the policy and click No to
l Select a policy, and then click cancel the operation.
.
l Right-click a policy and
choose Delete Policy.
Suspend Policy l Select a policy, and then When the system displays the
choose Operation > Confirm dialog box, click Yes to
Suspend Policy from suspend the policy and click No
the main menu. to cancel the operation.
l Select a policy, and then click
.
l Right-click a policy and
choose Suspend Policy.
2-40
Execute Instantly l Select a policy, and then When the system displays the
choose Operation > Execute Confirm dialog box, click Yes
Instantly from the main to carry out the selected policy
menu. instantly and click No to cancel
l Select a policy, and then click the operation.
.
l Right-click a policy and
choose Execute Instantly.
– End of Steps –
Result
The policies are configured successfully.
Example
The following example shows how to create a policy.
1. Click to open the Create Policy–Step 1 of 3 dialog box, as shown in Figure 2-26.
2-41
Parameter Configuration
Policy Name It is recommended that the policy name contains the information on
the action template.
Condition Templet Timing Templet l Carry out the policy at the specified time
and carry it out only once.
l Carry out the policy at the specified time
every day, every week, every month, or
every year.
2. Click Next to open the Create Policy–Step 2 of 3 dialog box, as shown in Figure 2-27.
Set the policy execution time.
Note:
It is recommended that the system administrator deploys the policies to ensure that the execution
times of the policies do not conflict.
2-42
3. Click Next to open the Create Policy–Step 3 of 3 dialog box, as shown in Figure 2-28.
Select the NE that carries out the policy.
4. Click Finish.
Configuration Recommendation
By default, the NMS carries out this policy once every day.
Configuration Recommendation
By default, the NMS carries out this policy once every day.
2-43
Context
The NetNumen N31 NMS of the version later than T010 supports this policy. The policy
synchronizes the following configuration data:
l Global data of the OLT NE and ONU NE, such as the NE version number, last
power-ON time, voice global data, and uplink port data of the OLT NE
l Card data of the OLT NE and ONU NE, such as the card version number
l PON port data and uplink port data
l ONU data, such as the ONU management IP address
Configuration Recommendation
Carry out this policy once every two or three days.
Context
Besides the data obtained by the Synchronize Configuration Data Policy, this policy obtains
the port-level statistics data, including the following data:
l Port rate data
l Port attainment performance data
l Port availability data
The data is used for resource query and statistics at the port level, providing important
indices for network quality and fault diagnosis.
Configuration Recommendation
Carry out this policy once at the end of every month or carry it out manually according to
the report period on the NMS.
2-44
Context
When the NE hardware is faulty (such as a component is burnt) or the main control card is
upgraded, the configuration data may be lost. Therefore, the NE configuration files need
to be backed up on the NMS. When the NE data is lost, the backed up data can be used
to restore the NE data.
Note:
Before carrying out this policy, you need to set the FTP user name, password, and main directory
on NetNumen Config Center. For detailed operations, refer to the topic 2.4.4 Configuring the FTP
Service.
The configuration files of the OLT device and F820 device are backed up to the corresponding directory
of the uni user. The configuration files of the 9806H, F822, and F821 devices are backed up to the
corresponding directory of the webnms user.
Configuration Recommendation
Table 2-14 lists the configuration recommendation of this policy.
OLT NE ONU NE
Context
The databases are backed up entirely, including the Uep (basic), Caffm (alarm), and
UepPm (performance) databases.
2-45
Note:
l Before carrying out this policy, you need to set the database backup path on NetNumen Config
Center, that is, the DatabaseBackupPath parameter.
l If it is the Oracle database in Solaris, the database files are backed up on the path of the Oracle
database server. In addition, make sure that the Oracle user has the write permission on that
path.
Configuration Recommendation
Carry out this policy once every week. By default, the system saves three copies of the
database files.
In addition, copy the database files to another storage medium besides the physical host
of the NMS server.
Context
According to the time and period set on the policy, the NMS sends the SaveFlash
command to the NE, and the NE then performs the SaveFlash operation.
After modifying the NE configuration data, perform the SaveFlash operation to avoid data
loss on the NE restart.
Configuration Recommendation
Carry out this policy once every day.
Context
Before this operation, you need to open the NetNumen Config Center window and modify
the FTP user name, password, and the main directory on the FTP Service tab.
Configuration Recommendation
Carry out this policy once every day.
2-46
Context
The administrator of the NetNumen N31 system is recommended to configure the policies.
The administrator needs to follow the following rules to configure the policies:
l The time to carry out the policy cannot be the same.
l Carry out the policy which needs too much resource at idle time.
Backup and Delete Alarm Carry out this policy once every two days at 23:59.
Policy
Backup and Delete Log Policy Carry out this policy once every two days at 23:59.
Synchronize Configuration Carry out this policy once every two days at 01:00.
Data Policy
Export NE Performance Data Carry out this policy once every week at 08:00 on Saturday.
Policy
Running Configuration Save Carry out this policy once every day at 18:00.
To Flash Policy
Data Configuration Backup Carry out this policy once a week at 14:00 on Sunday.
Policy
NMS Database Backup Policy Carry out this policy once a week at 23:59 on Sunday.
2-47
2-48
l For management convenience, it is recommended that the ONU groups do not exceed
three levels.
l The OLT NE name is in “city+office site+device name[-number]” format. If there is
only one OLT, the number is not required. When the user logs in to the NE through
Telnet, this name is displayed at the front of the command line prompt.
l The ONUs can be grouped according to the ONU physical positions. Create the ONU
groups according to the EPON card and PON port information on the OLT.
Prerequisites
Before this operation, make sure that you have logged in to the NetNumen N31 NMS.
Context
To create a role, perform the following steps:
Steps
1. Open the Security Management tab.
In the NetNumenN31 Unified Management System window, choose View >
Security Management to open the Security Management tab. From the navigation
tree on the left, select Role Management. The predefined roles are displayed on the
right pane, as shown in Figure 2-31.
2-49
2. Create a role.
Click to open the Create Role dialog box, as shown in Figure 2-32.
2-50
On the Basic Information tab, set Role Name and Role Description.
b. Set the rights information.
On the Access Rights tab, set the parameters as follows:
l Using predefined settings
From the Operations Assignment drop-down list, select a role. The roles
include the power user (advanced administrator), maintenance person,
operator, and supervisor.
l Using self-defined settings
Select the rights from the left pane to assign the rights to the specified user.
On the right pane, assign the groups and NEs managed by the user, as shown
in Figure 2-33.
Note:
à Right assignment: The modules in the operation tree and the rights in each module
can be assigned independently. For example, alarm operations include acknowl-
edging/unacknowledging alarms, clearing alarms, commenting alarms, forwarding
alarms, and synchronizing alarms.
à Domain assignment: The NEs can be managed according to the domains, including
the provinces, cities, districts, groups, and NEs.
2-51
On the Login Address tab, click add to open the Set IP Range dialog box, as
shown in Figure 2-34. Set the IP address range.
Result
The role is created successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNumen N31 NMS.
l The NMS has a created role besides the default five roles.
Context
Duplicate the role in the following conditions:
2-52
l The new role has the same rights as the created role but has different managed
domains.
l The new role has the same managed domains as the created role but has different
rights.
To duplicate a role, perform the following steps:
Steps
1. Open the window.
In the NetNumenN31 Unified Management System window, choose View >
Security Management to open the Security Management tab. From the navigation
tree on the left, select Role Management, as shown in Figure 2-35.
Right-click the new role and choose Duplicate. The Create Role dialog box appears.
The role information can be modified. For detailed operations, refer to the topic 2.11.1
Creating a Role.
4. Complete the operation.
Click OK.
– End of Steps –
2-53
Result
The role is duplicated.
Prerequisites
Before this operation, make sure that you have logged in to the NetNumen N31 NMS.
Context
On the NetNumen N31 NMS, the built-in link polling module can be used to customize and
modify the NE polling tasks.
The built-in link polling module is integrated in the NMS server processes. It can be used
when the NEs managed by the NMS are less than 5000.
To customize polling tasks, perform the following steps:
Steps
1. Open the Auto Poll Task Setting dialog box.
In the Topology Management window, choose Topology > Poll Configuration. The
Auto Poll Task Setting dialog box appears, as shown in Figure 2-36.
2-54
Operation Description
2-55
Parameter Description
When the NE link is down, the NMS needs to wait for N × T to ( N + 1 ) × T before
receiving the reported alarms. Here, N = alarm threshold and T = interval.
Note:
The polling task of SnmpNode is the default task. C200, C220, 9806H, F820, and F822 are
all of the SnmpNode type.
2-56
Result
The polling task configuration is complete.
Prerequisites
Before this operation, make sure that you have logged in to the NetNumen N31 NMS.
Context
To start fault management, perform the following steps:
Steps
1. Open the window.
In the NetNumenN31 Unified Management System window, choose View > Fault
Management. The Fault Management tab is displayed, as shown in Figure 2-38.
2-57
Note:
You can also perform the following operations to view alarms on the NetNumen N31 NMS:
l On the Topology Management tab, right-click the NE and choose Current Alarm to view
the current alarms on the NE.
l In the Chassis View window, right-click a card or port and choose Alert to view the current
alarms on the card or port.
l In the ONU Configuration window, right-click an ONU and choose Current Alarm to view
the current alarms on the ONU.
Operation Description
Click . When the NMS receives mass alarms, you can lock the
selected alarm.
Select or clear the Auto Refresh When the Auto Refresh check box is cleared, the alarm
check box. list cannot be refreshed automatically or display the
latest alarm.
Right-click an alarm and choose The alarm details include the following ONU information:
Details. l ONU system type
l ONU IP address
l ONU name
l ONU service class
– End of Steps –
Result
The Fault Management window is displayed.
Follow-Up Action
In the NetNumen N31 NMS, you can customize the alarm information as follows:
2-58
Prerequisites
Before this operation, make sure that the Fault Management window is displayed.
Context
To customize the display columns, perform the following steps:
Steps
1. Open the Customize Display Columns dialog box.
In the Fault Management window, click to open the Customize Display Columns
dialog box, as shown in Figure 2-39.
2-59
b. Select NE Type.
c. If alarm acknowledgement is not required, clear (Un)acknowledge Operator,
(Un)acknowledge System, (Un)acknowledgement Information, and
(Un)acknowledging Time.
d. After the display columns are customized, you can drag the columns to adjust the
column orders.
2-60
Click OK.
– End of Steps –
Result
The display columns are customized.
Prerequisites
Before this operation, make sure that the Fault Management window is displayed.
Context
The current alarm query profile helps the maintenance personnel query the current alarms
that match the self-defined conditions quickly.
This topic provides an example of customizing the current alarm query profile. The NE is
C220, the alarm is raised in city A, and the alarm severity is major.
To customize the current alarm query profile, perform the following steps:
Steps
1. Open the window.
In the Fault Management window, click the Management View bar. From the left
navigation tree, double-click View Current Alarms, as shown in Figure 2-40.
2-61
2-62
Set Name, Description, and the query conditions, as listed in Table 2-19.
System Type ZXPON C220 V1.2 This parameter includes the NE type,
link alarm, and correlation alarm. It
also supports fuzzy search. You can
type key words at the bottom of the
right pane for query.
Note:
To quickly query the current alarms, you can also click to open the Query Current Alarm dialog
box, set the query conditions, and then click OK to query alarms.
– End of Steps –
Result
The current alarm query profile is customized.
Prerequisites
Before this operation, make sure that the Fault Management window is displayed.
2-63
Context
The history alarm query profile helps the maintenance personnel query the history alarms
that match the self-defined conditions quickly.
This topic provides two instances of customizing the history alarm query profile.
To customize the history alarm query profile, perform the following steps:
Steps
1. Open the window.
In the Fault Management window, click the Management View bar. From the left
navigation tree, double-click View History Alarms, as shown in Figure 2-42.
2-64
Happen Time Latest: 12 hours The starting time when the alarms
are raised
2-65
Click OK.
5. Carry out the profile.
Select the history alarm query profile, and then click to query alarms.
Note:
You can also click (the Quick Search button) to query history alarms.
– End of Steps –
Result
The history alarm query profile is customized.
Prerequisites
Before this operation, make sure that the Fault Management window is displayed.
Context
On the NetNumen N31 NMS, the alarm rules can be customized.
The NMS operator may have special requirements on alarm notification and handling, such
as:
l Do not report some alarms.
l Report some alarms to the specified users.
l Delay the notification of some alarms.
l Acknowledge or clear some alarms automatically.
Therefore, the alarm rules can be customized to meet such requirements.
Table 2-22 lists the commonly used alarm filtering rules.
2-66
Alarm User Filtering Control the alarm When the NMS receives This rule is effective for
Rule visibility: the alarms that match all the active alarms in
l To set some alarms the conditions, it does the system.
invisible to the not display the alarms This rule does not affect
current user. on the client where the alarm handling by other
l To reduce the alarm current user logs in. users and systems.
data that the current
user needs to be
concerned about.
Alarm Global Control the alarm When the NMS receives This rule is effective for
Filtering Rule visibility: the alarms that match all the active alarms in
l To set some alarms the conditions, it saves the system.
invisible to all the the alarms rather than
users. display them on the
l To reduce the client.
alarm data that the
users need to be
concerned about.
l To save the alarm
data in the system
for statistics and
handling.
Alarm Discarding Control alarm When the NMS receives This rule is effective for
Rule discarding: the alarms that match only the alarms reported
l To filter the reported the conditions, it after the rule is created.
alarms. discards the alarms
l To shield the alarms directly.
that do not need to
be handled in the
NMS.
Steps
1. Open the window.
In the Fault Management window, click the Management View bar. From the left
navigation tree, double-click Management Rule Setting, as shown in Figure 2-44.
2-67
Table 2-23 Configuration Data for the Alarm Global Filtering Rule
Location City A
Severity Minor
a. Create a rule.
2-68
2-69
Location City A
a. Create a rule.
Click to open the New dialog box.
b. Configure the parameters.
2-70
Select Alarm Counting Rule, and then click OK. The Alarm Counting Rule
dialog box is displayed, as shown in Figure 2-47.
Caution!
Result
The alarm rules are configured successfully.
2-71
Prerequisites
Before this operation, make sure that the Fault Management window is displayed.
Context
To redefine the alarm severities, perform the following steps:
Steps
1. Open the window.
In the Fault Management window, choose Setting > Severity Regrading Setting.
The Severity Regrading Setting tab is displayed, as shown in Figure 2-48.
From the New Severity drop-down list, select the new severities for the alarms whose
severities need to be modified.
3. Complete the configuration.
Result
The alarm severities are redefined successfully.
2-72
Prerequisites
Before this operation, make sure the Fault Management window is displayed.
Context
The alarm sounds can be set according to different alarm severities.
To set the alarm sounds, perform the following steps:
Steps
1. Open the Preferences dialog box.
In the Fault Management window, choose Setting > Preferences. The Preferences
dialog box appears, as shown in Figure 2-49.
2-73
Operation Description
Click Select. Select a sound file from the local directory as the alarm sound
according to the alarm severity.
Select the All Silence check Set all the alarm sounds to silent.
box.
– End of Steps –
Result
The alarm sounds are set successfully.
2-74
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
To create an OLT NE, perform the following steps:
Steps
1. Open the Management - Create dialog box.
3-1
2. Configure NE parameters.
In the Management - Create dialog box, select the NE type from the left pane, and
configure the parameters on the Basic tab in the right pane.
Table 3-1 describes the parameters for NE creation.
Parameter Description
Read community The community must be consistent with that configured on the NE.
Default: public
Write community The community must be consistent with that configured on the NE.
Default: public
– End of Steps –
Result
The NE is created successfully.
3-2
Prerequisites
Before this operation, make sure that:
Context
To manage the cards, perform the following steps:
Steps
1. Open the Card Management window.
Right-click the NE and choose System Management > Card Config to open the Card
Management window, as shown in Figure 3-2.
If cards are configured through the CLI mode, click Synchronize to synchronize the
card configuration to the NM server.
3. Add a card.
3-3
a. If cards are not configured through the CLI mode, click the idle slot, and then click
Add to open the Add Card dialog box, as shown in Figure 3-3.
b. Select the card and click OK to return to the Card Management window.
4. Click Close.
– End of Steps –
Result
The cards are successfully managed.
Prerequisites
Before this operation, make sure that:
Context
To manage the NE version, perform the following steps:
3-4
Steps
1. Open the Version Management window.
Right-click the NE and choose System Management > Version Management to open
the Version Management window, as shown in Figure 3-4.
All the versions are displayed on the Version Area tab. Table 3-2 describes the items
on the Version Area tab.
Item Description
2. Click the Version Area tab. You can perform different operations on the version. Table
3-3 described the operations.
Operation Step
3-5
Operation Step
Upload the version to the Click Upload to NMS. Perform this operation in the pop-up
NMS. window.
Result
The NE version is managed successfully.
Example
The following example shows how to upload the version to the NMS.
1. In the Version Management window, click Upload to NMS to display the Upload
Version window, as shown in Figure 3-5.
3-6
Note:
The Upload Version window shows the FTP server IP address, FTP server user name, FTP
server password, FTP server root directory, and backup directory. These parameters need to be
configured properly in NetNumen N31 Config Center.
2. Select the versions that you want to upload. Click Start to upload the versions to the
NMS.
3. When the upload completes, a Message box appears, as shown in Figure 3-6.
3-7
4. Click OK. The Upload Status column shows whether the versions are uploaded
successfully.
5. Click Close to complete the operation.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
A CLI user (telnet user) is the user who manages the NE through CLI.
To configure a CLI user, perform the following steps:
3-8
Steps
1. Open the CLI User Config window.
Right-click the NE and choose System Management > CLI Users Config to open the
CLI User Config window, as shown in Figure 3-7.
2. Configure the CLI user. You can add, delete, or modify a CLI user.
a. Click Add to open the Add Cli User Config dialog box.
b. Configure the User Name and Password. Select the user right from the User
Access Level drop-down list, and the password encryption mode from the PWD
Encrypt Mode drop-down list, as shown in Figure 3-8.
3-9
Common User The user who can only view the configurations
Note:
If you select the Apply to NEs check box, the CLI users are configured in batch.
Result
The CLI user is configured successfully.
Prerequisites
Before this operation, make sure that:
Context
To configure the system name, perform the following steps:
Steps
1. Right-click the NE and choose System Management > NE Basic Info to open the
System Config window.
2. Configure the parameters, as shown in Figure 3-9, and then click Set.
3-10
3. Click Close.
– End of Steps –
Result
The system name is configured successfully.
Figure 3-10 shows the system name displayed in the CLI.
Note:
You can distinguish different NEs in CLI mode by modifying the system name of the NEs.
3-11
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
Usually, the NM server works as the trap server, which receives the alarms from the ZXA10
C220.
To configure the trap server, perform the following steps:
Steps
1. Open the Trap Server Configuration window.
Right-click the NE and choose System Management > Trap Server Config to open
the Trap Server Configuration window, as shown in Figure 3-11.
3-12
Parameter Description
SNMP community The community must be consistent with that configured on the
NE.
Note:
If you select Apply to NEs, the trap server is applied to all NEs.
3. Click Close.
– End of Steps –
Result
The trap server is configured successfully.
3-13
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
The ZXA10 C220 works as an NTP client, which synchronizes time with the NTP server
automatically to ensure the accurate time on the NE. Usually, the NM server works as the
NTP server.
To configure the NTP service, perform the following steps:
Steps
1. Open the NTP Service Management window.
Right-click the NE and choose System Management > NTP Service Management
to open the NTP Service Management window, as shown in Figure 3-13.
Table 3-6 describes the parameters for the NTP service configuration.
3-14
Parameters Description
Poll interval The interval that the NE synchronizes time with the NTP server
Default: 300 seconds
Current service state Whether the NE synchronizes time with the NTP server
Note:
If you select Apply to NEs, the NTP service is applied to all NEs.
Result
The NTP service is configured successfully.
Service Specifications
The NM supports two types of ACL.
l Management ACL: the standard ACL, which matches only source IP addresses of
packets according to specified rules
3-15
l PCL (Policy Control List): a hybrid ACL, which matches the first 80 bytes of the layer-2
frames according to any combination of rules
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
To configure the management ACL, perform the following steps:
Steps
1. Open the Management ACL Configuration window.
Right–lick the NE and choose Ethernet Management > Management ACL > ACL
Configuration to open the Management ACL Configuration window, as shown in
Figure 3-14.
2. Create an ACL.
a. Click Create to open the Create Management ACL Configuration dialog box, as
shown in Figure 3-15.
3-16
b. Enter the ACL index, and then click OK to return to Management ACL
Configuration window.
Note:
b. Click Create to open the Create Management ACL Rule Configuration dialog
box.
3-17
b. Select a protocol and click Modify to open the Modify Management ACL Bind
dialog box, as shown in Figure 3-19.
3-18
c. Choose ACL Bind Index and enter the index, and then click OK to return to the
Management ACL Bind Config window.
d. Click Close.
– End of Steps –
Result
The ACL is successfully configured and applied.
Prerequisites
Before this operation, make sure that:
Context
To configure the management ACL, perform the following steps:
Steps
1. Open the PCL Configuration window.
Right-click the NE and choose Ethernet Management > QoS PCL > QoS PCL
Configuration to open the PCL Configuration window, as shown in Figure 3-20.
3-19
Note:
a. In the PCL Configuration window, click Rule to open the PCL Rule
Configuration window, as shown in Figure 3-22.
3-20
b. Click Create to open the Create PCL Rule Configuration dialog box.
c. Configure the rule parameters, as shown in Figure 3-23.
Parameter Description
Access control To permit or deny the access from the source IP address
IP protocol l IGMP
l OSPF
l PIM
l TCP
l UDP
l VRRP
3-21
Parameter Description
3-22
c. Click Create to open the Create PCL Bind Config dialog box.
d. Configure the parameters, as shown in Figure 3-25, and then click OK to return to
the PCL Bind Config window.
e. Click Close.
– End of Steps –
Result
The PCL is successfully configured and applied.
3-23
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
You can select the ONU type profile to specify the ONU type before you create an ONU
NE.
To configure the ONU type profile, perform the following steps:
Steps
1. Open the ONU Type Profile window.
Right-click the NE and choose EPON Management > Profile Management > ONU
Type Profile to open the ONU Type Profile window, as shown in Figure 3-26.
3-24
Operation Step
Delete an ONU type profile. Select an ONU type profile and click Delete.
3-25
Table 3-9 describes the parameters for ONU type profile configuration.
Parameter Description
Note:
l You must configure the interface profile properly if you want to configure the service on the
relevant slot and port through the extended OAM.
l You need to create a new interface profile for the same ONU type if the slot and type of
the card is different.
a. In the ONU Type Profile window, click Interface Co... to open the Interface
Config of Profile dialog box, as shown in Figure 3-28.
3-26
In the Interface Config of Profile window, you can perform different operations.
Table 3-10 describes these operations related to ONU type interface profile.
Operation Step
Delete an ONU type interface profile. Select an ONU type interface profile and click
Delete.
This example shows the steps of adding an ONU type interface profile.
b. Click Create to open the Add Interface of Profile dialog box.
c. Configure the parameters, as shown in Figure 3-29.
Table 3-11 describes the parameters for ONU type interface profile configuration.
3-27
Table 3-11 Parameters for ONU Type Interface Profile Configuration (EPON)
Parameter Description
l If the Auto Config Status is disabled, this type of ONU cannot update
configuration data automatically from the OLT.
l If the Auto Config Status is enabled, this type of ONU can update configuration
data automatically from the OLT.
Note:
If the ONU NE is created through the profile, the Auto Config Status of the created NE is con-
sistent with that of the profile.
Result
The EPON ONU type profile is configured successfully.
Follow-Up Action
In the NetNumen N31 unified management system, you can perform the following steps to
modify ONU auto-configure status (to enable auto-configure status from OLT) for the ONU
global startup mode or VoIP service.
l In the ONU Basic Attribute Management window, click More... and select Global
Startup Mode to open the ONU Global Startup Mode Configuration dialog box.
Select the startup mode from the Startup Mode drop-down list, as shown in Figure
3-30.
3-28
l In the ONU Basic Attribute Management window, click More... and select VoIP
Startup Mode to open the VoIP Startup Mode dialog box. Select the startup mode
from the Startup Mode drop-down list, as shown in Figure 3-31.
Start-up From OLT Start-up From OLT All the configuration data is updated from the
OLT.
Start-up From OLT Start-up From Local All the configuration data, except VoIP service
data, is updated from the OLT.
Start-up From Local Start-up From OLT No configuration data is updated from the
OLT.
Start-up From Local Start-up From Local No configuration data is updated from the
OLT.
3-29
Prerequisites
Before this operation, make sure that:
Context
You can allocate bandwidth to the ONUs by applying the ONU bandwidth profile to the
ONUs.
To configure the ONU bandwidth profile, perform the following steps:
Steps
1. Open the ONU Bandwidth Profile window.
Right-click the ZXA10 C220 NE and choose EPON Management > Profile
Management > ONU Bandwidth Profile to open the ONU Bandwidth Profile
window, as shown in Figure 3-32.
a. Click Create to open the Add ONU Bandwidth Profile dialog box.
3-30
Table 3-13 describes the parameters for ONU bandwidth profile configuration.
Parameter Description
Result
The EPON ONU bandwidth profile is configured successfully.
3-31
Prerequisites
Before this operation, make sure that:
Context
To configure the EPON VoIP IP profile, perform the following steps:
Steps
1. Open the VOIP IP Profile window.
Right-click the NE and choose EPON Management > Profile Management > VOIP
IP Profile to open the VOIP IP Profile window, as shown in Figure 3-34.
In the VOIP IP Profile window, you can perform different operations. Table 3-14
describes the operations related to VoIP IP profile.
3-32
Operation Step
Parameter Description
3-33
3. Click Close.
– End of Steps –
Result
The VoIP IP profile is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
To configure the VoIP VLAN profile, perform the following steps:
Steps
1. Open the VOIP VLAN Profile window.
Right-click the NE and choose EPON Management > Profile Management > VOIP
VLAN Profile to open the VOIP IP Profile window, as shown in Figure 3-36.
3-34
In the VOIP VLAN Profile window, you can perform different operations. Table 3-16
describes the operations related to a VoIP VLAN profile.
Operation Step
Delete a VoIP VLAN profile. Select a VoIP VLAN profile and click Delete.
Modify a VoIP VLAN profile. Select a VoIP VLAN profile and click Modify.
The following example shows the steps of adding a VoIP VLAN profile.
a. Click Add to open the Create VOIP VLAN Profile dialog box.
Table 3-17 describes the parameters for creating a VoIP VLAN profile.
Parameter Description
3-35
Note:
Different types of ONU support different tag modes. At present, F820 and F420 only support
TAG mode.
Result
The VoIP VLAN profile is configured successfully.
Prerequisites
Before this operation, make sure that:
Context
VoIP protocol profiles include VoIP profile (H.248), VoIP protocol profile (MGCP), and VoIP
protocol profile (SIP). This topic takes VoIP profile (H.248) as an example.
To configure the VoIP protocol profile (H.248), perform the following steps:
Steps
1. Open the VOIP Protocol Profile (H.248) window.
Right-click the NE and choose EPON Management > Profile Management > VOIP
Protocol Profile (H.248) to open the VOIP Protocol Profile (H.248) window, as
shown in Figure 3-38.
3-36
Operation Step
Delete a VoIP protocol profile (H.248). Select a VoIP protocol profile (H.248) and click
Delete.
Modify a VoIP protocol profile (H.248). Select a VoIP protocol profile (H.248) and click
Modify.
The following example shows the steps of adding a VoIP protocol profile (H.248).
a. Click Add to open the Add VoIP Protocol Profile (H.248) dialog box.
b. Configure the parameters, as shown in Figure 3-39.
3-37
Table 3-19 describes some parameters for adding a VoIP protocol profile (H.248).
Parameter Description
Reg Server Port It should be consistent with the register server port
number configured on the media gateway controller.
Result
The VoIP protocol profile (H.248) is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
3-38
Context
To configure the VoIP fax profile, perform the following steps:
Steps
1. Open the VOIP Fax Profile window.
Right-click the NE and choose EPON Management > Profile Management > VOIP
Fax Profile to open the VOIP Fax Profile window, as shown in Figure 3-40.
Operation Step
Delete a VoIP fax profile. Select a VoIP fax profile and click Delete.
Modify a VoIP fax profile. Select a VoIP fax profile and click Modify.
a. Click Add to open the Create VoIP Fax Profile dialog box.
b. Configure the parameters, as shown in Figure 3-41.
3-39
Table 3-21 describes the parameters for creating a VoIP fax profile.
Parameter Description
Result
The VoIP fax profile is configured successfully.
3-40
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
To create an ONU NE, the ONU type is to be specified. The ONU type can be defined by
an ONU type profile.
To configure the ONU type profile, perform the following steps:
Steps
1. Open the ONU Type Profile window.
Right-click the NE and choose GPON Management > Profile Management > ONU
Type Profile to open the ONU Type Profile window, as shown in Figure 3-42.
In the ONU Type Profile window, you can perform different operations.
Table 3-22 describes these operations related to ONU type profile.
Operation Step
3-41
Operation Step
Delete an ONU type profile. Select an ONU type profile and click Delete.
Table 3-23 describes the parameters for the ONU type profile configuration.
Parameter Description
Note:
l You must configure the interface profile properly if you want to configure the service on the
relevant slot and port through the OMCI channel.
l You need to create a new interface profile for the same ONU type if the slot and type of
the card is different.
a. In the ONU Type Profile window, click Interface Co... to open the Interface
Config of Profile dialog box, as shown in Figure 3-44.
3-42
In the Interface Config of Profile window, you can perform different operations.
Table 3-24 describes these operations related to ONU type interface profile.
Operation Step
Delete an ONU type interface profile. Select an ONU type interface profile. Click
Delete.
This example shows the steps of adding an ONU type interface profile.
b. Click Add to open the Create ONU Type Interface Profile dialog box.
c. Configure the parameters, as shown in Figure 3-45.
Table 3-25 describes the parameters for ONU type interface profile configuration.
3-43
Table 3-25 Parameters for ONU Type Interface Profile Configuration (GPON)
Parameter Description
5. Click Close.
– End of Steps –
Result
The ONU type profile is configured successfully.
3-44
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
To create a traffic container (T-CONT), you need to specify the corresponding GPON
bandwidth profile.
To configure the T-CONT bandwidth profile, perform the following steps:
Steps
1. Open the Bandwidth Profile window.
Right-click the ZXA10 C220 NE and choose GPON Management > Profile
Management > Bandwidth Profile to open the Bandwidth Profile window, as
shown in Figure 3-47.
3-45
Parameters Description
Note:
You can select the Apply to Nes check box to apply the profile to all NEs.
3. Click Close.
– End of Steps –
3-46
Result
The T-CONT bandwidth profile is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
Traffic descriptor profiles are used to control downstream traffic on the GEM ports.
To configure the GPON traffic descriptor profile, perform the following steps:
Steps
1. Open the Traffic Descriptor Profile window.
Right-click the ZXA10 C220 NE and choose GPON Management > Profile
Management > Traffic Descriptor Profile to open the Traffic Descriptor Profile
window, as shown in Figure 3-49.
3-47
a. Click Add to open the Add Traffic Descriptor Profile dialog box.
b. Configure the parameters, as shown in Figure 3-50.
Note:
You can select the Apply to Nes check box to apply the profile to all NEs.
Result
The GPON traffic descriptor profile is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
The ZXA10 C220 supports two types of GPON VoIP protocol profiles:
3-48
The configuration procedure for the two profiles are same. This topic takes the VoIP SIP
profile as an example.
To configure the VoIP SIP profile, perform the following steps:
Steps
1. Open the VoIP SIP Profile window.
Right-click the ZXA10 C220 NE and choose GPON Management > Profile
Management > VoIP SIP Profile to open the VoIP SIP Profile window, as shown in
Figure 3-51.
Note:
To open the VoIP MGC Profile window, you can right-click the ZXA10 C220 NE and choose GPON
Management > Profile Management > VoIP MGC Profile.
Operation Step
Delete a VoIP SIP profile. Select a VoIP SIP profile and click Delete.
Modify a VoIP SIP profile. Select a VoIP SIP profile and click Modify.
3-49
The following example shows the steps of adding a VoIP SIP profile.
a. Click Add to open the Add SIP Profile dialog box.
b. Configure the parameters, as shown in Figure 3-52.
Parameter Description
Outbound proxy address IP address of the SIP outbound proxy server, usually the same
as the SIP proxy server
Registrar server IP address of the SIP registrar server, usually the same as the
SIP proxy server
3. Click Close.
– End of Steps –
Result
The GPON VoIP profile is configured successfully.
3-50
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
The port status includes the administration and trap status of the uplink port.
To configure the port status, perform the following steps:
Steps
1. Open the Port Management window.
a. Right-click the NE and choose Ethernet Management > Port Management to
open the Port Management window.
b. Click to select the card, as shown in Figure 3-53.
3-51
b. Select Up from the Admin Port Status drop-down list to enable the port
administration. Select Down to disable the port administration.
c. Click OK to return to the Port Status Config window.
4. Click Close.
– End of Steps –
3-52
Result
The port status is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured on the ZXA10 C220.
l The NMS communicates with the ZXA10 C220 properly.
Context
To configure Ethernet port, perform the following steps:
Steps
1. Open the Port Ethernet Properties window.
a. Right-click the NE and choose Ethernet Management > Port Ethernet
Properties to open the Port Ethernet Properties window.
b. Click to select the card, as shown in Figure 3-55.
3-53
a. Select a port and click Modify to open the Modify Config dialog box, as shown
in Figure 3-56.
b. Configure parameters and then click OK to return to the Port Ethernet Properties
window.
Note:
3. Click Close.
– End of Steps –
Result
The Ethernet port is configured successfully.
Prerequisites
Before this operation, make sure that:
3-54
Context
To configure the port VLAN , perform the following steps:
Steps
1. Open the Port VLAN Configuration window.
a. Right-click the NE and choose Ethernet Management > VLAN Management >
Port VLAN Configuration to open the Port VLAN Configuration window.
b. Click to choose the card, as shown in Figure 3-57.
3-55
Parameter Description
b. Configure parameters and then click OK to return to the Port VLAN Configuration
window.
3. Click Close.
– End of Steps –
Result
The port VLAN is configured successfully.
3-56
Prerequisites
Before this operation, make sure that:
Context
To configure the LACP protection, perform the following steps:
Steps
1. Configure the smartgroup.
a. Right-click the NE and choose Ethernet Management > LACP Management >
Smartgroup Config to open the Smartgroup Config window, as shown in Figure
3-59.
3-57
c. Fill in the index, as show in Figure 3-60, and then click OK to return to the
Smartgroup Config window.
d. Click Close.
2. Configure smartgroup properties.
a. Right-click the NE and choose Ethernet Management > LACP Management
> LACP Aggregating to open the LACP Aggregating Configure window, as
shown in Figure 3-61.
b. Select the smartgroup and click Modify to open the LACP Aggregating
Configure dialog box.
3-58
c. Configure the parameters, as shown in Figure 3-62, and then click OK to return to
the LACP Aggregating Config window.
d. Click Close.
3. Configure smartgroup member port.
a. Right-click the NE and choose Ethernet Management > LACP Management >
LACP Aggregated Configure to open the LACP Aggregated Configure window,
as shown in Figure 3-63.
3-59
d. Click Close.
Note:
l When Port Mode is ON, Static Trunk runs on the port. Configure Port Mode as On
at both ends.
l When Port Mode is Active or Passive, LACP runs on the port. Active means the
active negotiation and Passive means the passive negotiation. When one end is
configured as Active, the other end needs to be configured as Passive. Or, configure
both ends as Active.
l The VLAN link type of the member port must be consistent with the VLAN link type of
smartgroup. If not, this port cannot be added to the Trunk group.
– End of Steps –
Result
The LACP protection is configured successfully.
Prerequisites
Before this operation, make sure that:
3-60
Context
To configure the UAPS protection, perform the following steps:
Steps
1. Open the UAPS Protection Configuration window.
Right-click the NE and choose System Management > UAPS Protection
Configuration to open the UAPS Protection Configuration window, as shown in
Figure 3-65.
3-61
Table 3-30 describes the parameters for the UAPS protection attributes.
Parameter Description
Result
The UAPS protection is configured successfully.
Prerequisites
Before this operation, make sure that:
3-62
Context
The ZXA10 C220 supports five ONU authentication modes:
l MAC address authentication: using the ONU PON MAC address for authentication
By default, this mode is used.
l Logical ID authentication: using the ONU logical ID for authentication
l SN authentication: using the ONU SN for authentication
l Hybrid authentication: using any of the MAC address, logical ID, or SN for
authentication
l SN+MAC authentication: using the ONU SN for authentication when the ONU enters
the network for the first time, and using the PON MAC address for authentication when
the ONU gets online for the second time
To configure the ONU authentication mode, perform the following steps:
Steps
1. Open the OLT Auth Configuration window.
Right-click the NE and choose EPON Management > OLT Authentication
Configuration to open the OLT Auth Configuration window, as shown in Figure
3-67.
Click to select the PON card and return to the OLT Auth Configuration window.
3. Select the authentication mode from the ONU Auth Mode drop-down list, as shown
in Figure 3-68.
3-63
4. Click OK to confirm.
5. Click Close.
– End of Steps –
Result
The ONU authentication mode is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The NMS communicates with the ZXA10 C220 properly.
Context
The ZXA10 C220 supports PON port protection. When the physical link between an ONU
and the ZXA10 C220 is disconnected, the ZXA10 C220 switches the services to the backup
PON port automatically.
Steps
1. Open the PON Protection Configuration window.
There are two ways to open the PON Protection Configuration window:
3-64
Parameter Description
3-65
Parameter Description
3-66
Parameter Description
Clear all Clear all external switch commands, including force, manual or
lock out.
Result
The PON port protection is configured successfully.
Prerequisites
Before this operation, make sure that:
3-67
Context
To configure the VLAN, perform the following steps:
Steps
1. Create a voice VLAN, VLAN 600.
a. Right-click the NE and choose Ethernet Management > VLAN Management >
Static VLAN Configuration to open the Static VLAN Configuration window, as
shown in Figure 3-73.
b. Click Add to open the Static VLAN Configure Properties dialog box.
c. Type 600 in the Start VLAN ID and Last VLAN ID text boxes, as shown in Figure
3-74.
3-68
Parameter Description
VLAN Name The system assigns VLAN name automatically if the user does
not type any information.
1:1 VLAN Enable Status In the 1:1 VLAN mode, there is only one service port and one
uplink in a VLAN, thus packets are forwarded according to
SVLAN ID or CVLAN ID + SVLAN ID, but not MAC address +
VLAN ID.
It is recommended to use the default value, which is Disabled.
Note:
When the END VLAN ID is more than the Start VLAN ID, VLAN can be created in batch.
d. Click OK to confirm.
2. Configure the port VLAN.
a. Right-click the NE and choose Ethernet Management > VLAN Management >
Port VLAN Configuration to open the Port VLAN Configuration window.
b. Click to select the uplink card and return to the Port VLAN Configuration
window, as shown in Figure 3-75.
3-69
Parameter Description
3-70
Result
VLAN is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The NMS communicates with the ZXA10 C220 properly.
Context
For some FTTB ONUs (such as the F820) and FTTH ONUs (such as the F420), the
NetNumen N31 unified management system uses the extended OAM protocol for
management. You need to complete the multicast configurations at the OLT before
provisioning the multicast service at the ONU.
Data Scheme
Table 3-35 describes the data scheme for multicast configuration at thr OLT.
Item Data
3-71
Steps
1. Enable IGMP.
a. Right-click the NE and choose Ethernet Management > Multicast IPTV
Management > IGMP Global to open the IGMP Global Configuration window.
b. On the IGMP Params tab, enable IGMP Status and use the default values for
other parameters, as shown in Figure 3-77.
3-72
d. Click OK to confirm.
3. Add the uplink port to the multicast VLAN.
a. Right-click the NE and choose Ethernet Management > VLAN Management >
Port VLAN Configuration to open the Port VLAN Configuration window.
b. Click to select the uplink card and return to the Port VLAN Configuration
window.
c. Click VLAN Binding to open the VLAN Binding Configuration dialog box.
d. Type 800 in the VLAN ID text box, as shown in Figure 3-79.
3-73
c. Click VLAN Binding to open the VLAN Binding Configuration dialog box.
d. Type 800 in the VLAN ID text box, as shown in Figure 3-81.
3-74
Note:
Before adding the user port to the multicast VLAN, you need to create the multicast GEM
Port.
b. Click New. On the Basic tab, configure the MVLAN basic parameters, as
shown in Figure 3-82.
3-75
Table 3-36 describes the MVLAN basic parameters for the configuration.
Parameter Description
c. Click Add.
d. Configure MVLAN channel groups.
3-76
Parameter Description
d. Click OK.
3-77
Note:
Only the uplink port which is added to VLAN 800 can be bound as the source port.
3-78
Note:
c. Click Create.
7. Configure IPTV channels.
3-79
Parameter Description
Preview Profile Use the new preview profile TEST.PRF in this example.
d. Click OK.
Repeat the same steps to create Program 2 and Program 3.
3-80
b. On the Basic tab, choose New and fill in the package name, as shown in Figure
3-88.
3-81
3-82
c. Select the port and click Modify to open the Port Admin Status dialog box.
d. Select Start from the drop-down list and click OK to return to the Port Access
Control window.
e. On the Package pane, click Right and select Enable to enable the port right, as
shown in Figure 3-91.
f. Click OK.
– End of Steps –
3-83
Result
Multicast is configured successfully.
Prerequisites
Before this operation, make sure that:
l The network devices and lines are normal.
l The VLAN of the upper-layer device interface corresponds to the VLAN configured on
the uplink interface.
l The xPON service card status is normal.
l The xPON basic service is configured.
Context
The xPON OLT is connected by multiple EPON ONUs, which can replace the layer-2
switches, in the downlink direction. The xPON OLT connects the DSLAM through the
ONU to achieve the function of MAN convergence switches. The packets are added
with different external VLAN tags according to different data streams to achieve service
identification.
The ZXA10 C220 supports the following smart QinQ modes:
l Based on a single CVLAN
l Based on a CVLAN segment
l Based on CoS
l Based on the Ethernet type
l Based on single CVLAN + CoS
l Based on single CVLAN + Ethernet type
When the items on the same port conflict, the item configured earliest takes effect.
Steps
1. Configure the SVLAN uplink port.
Refer to the section 3.14 Configuring the VLAN to add the uplink port to the VLAN in
tagged mode.
2. Enable the smart QinQ function.
3-84
a. Right-click the ZXA10 C220 NE and choose Ethernet Management > VLAN
Management > QinQ Enabling. The QinQ Enable Status Config window
appears.
b. Select MainBoard Enable from the Global QinQ Enable Status drop-down list
and click Set to enable the global QinQ function.
c. In the QinQ Enable Status Config window, select the card and PON port. Click
Enable to enable the QinQ function of a PON port, as shown in Figure 3-92.
Note:
The QinQ function of a port can only be enabled after the global QinQ function is enabled.
After the QinQ function of a PON port is enabled, the QinQ function of all the ONUs on this
port is disabled.
a. Right-click the ZXA10 C220 NE and choose Ethernet Management > VLAN
Management > Smart QinQ Config. The Global Smart QinQ Config window
appears.
b. Click Add to display the Add Global QinQ dialog box, as shown in Figure 3-93.
3-85
Parameter Description
3-86
Parameter Description
Ethernet Type If the Match Role Type is Ethernet Type, you need
to select the Ethernet Type here. The options are as
follows:
l ARP
l IPoE
l PPPoE Discovery
l PPPoE Session
d. Click OK.
e. In the Global Smart QinQ Config window, click Close.
– End of Steps –
Result
Smart QinQ is configured successfully.
Service Specifications
The ZXA10 C220 provides the following DHCP applications:
l DHCP Snooping
l DHCP Relay
l DHCP Server
The ZXA10 C220 can serve as a DHCP server or DHCP relay to forward DHCP packets.
Both of the applications, however, cannot be used simultaneously on the same VLAN
interface.
3-87
In addition, the ZXA10 C220 uses DHCP Snooping to prevent unauthorized DHCP server
from accessing the network. A trusted port needs to be configured for the DHCP server.
Prerequisites
Before this operation, make sure that:
l The network devices and lines are normal.
l The xPON service card status is normal.
l The xPON basic service is configured.
Context
When DHCP Snooping is enabled on a ZXA10 C220, only the DHCP server connected to
the trust port is available.
To configure the DHCP Snooping function, perform the following steps:
Steps
1. Open the DHCP Snooping Config window.
Right-click the NE and choose Ethernet Management > DHCP Management > DHCP
Snooping Configuration to open the DHCP Snooping Config window.
2. Configure the DHCP trust port.
On the Uplink Port tab, select the port and click Switch , as shown in Figure 3-94.
3-88
b. Enable the DHCP snooping function, as shown in Figure 3-95, and then click OK
to return to the DHCP Snooping Config window.
On the VLAN Parameter tab, choose the VLAN and click Switch, as shown in Figure
3-96.
3-89
b. Configure the parameters, as shown in Figure 3-97, and then click OK to return to
the DHCP Snooping Config window.
c. Click Close.
6. Enable the DHCP Option82 function.
a. Right-click the NE and choose Ethernet Management > Port Locating Config
to open the Port Locating Configuration window, as shown in Figure 3-98.
3-90
b. On the DHCP Configure tab, click Advance to open the Port Locating DHCP
Advanced Configure dialog box.
c. Enable DHCP Option82, as show in Figure 3-99, and then click OK to return to
the Port Locating Config window.
d. Click Close.
7. Configure the service port.
a. Right-click the NE and choose Ethernet Management > VLAN Management >
Service Port Configuration to open the ServicePort Configuration window.
b. Click to select the service card, and select the OLT port and ONU ID, and
then click Create to open the Create Service Port Configuration dialog box.
c. Configure the parameters, as shown in Figure 3-100, and then click OK to return
to the Service Port Configuration window.
3-91
Note:
Both the Inner CVLAN and the Outer CVLAN are the DHCP VLAN.
d. Click Close.
– End of Steps –
Result
The DHCP Snooping function is configured successfully.
Prerequisites
Before this operation, make sure that:
3-92
Context
To configure the DHCP Relay function, perform the following steps:
Steps
1. Configure the level-3 interface.
a. Right-click the NE and choose Ethernet Management > L3 Interface
Configuration to open the L3 Interface Config window, as shown in Figure
3-101.
c. Configure the parameters, as shown in Figure 3-102, and then click OK.
3-93
d. Select the VLAN, and click IP Addr... to open the L3 Interface IP Address Config
window.
e. Click Create to open the L3 Interface IP Address Config dialog box.
f. Configure the layer-3 interface IP address, as shown in Figure 3-103, and then
click OK to return to the L3 Interface Config window.
3-94
b. Click Advance to open the DHCP L3 Public Global Config dialog box.
c. Enable the DHCP L3 functions, as shown in Figure 3-105, and click OK to return
to the DHCP L3 Public Config window.
a. In the DHCP L3 Public Config window, select the VLAN and click Modify to open
the DHCP L3 Public VLAN... dialog box.
b. Select the VLAN interface mode (Relay in the example) from the VLAN Interface
Mode drop-down list, as shown in Figure 3-106, and click OK.
3-95
Note:
The DHCP Proxy mode, which can detect the user disconnection quickly, is the extension of
the Relay mode.
a. Right-click the NE and choose Ethernet Management > DHCP Management >
DHCP Relay Configuration to open the DHCP Relay Config window.
b. On the VLAN ID tab, select the VLAN and click Modify to open the DHCP Relay
VLAN Interface Config dialog box.
c. Configure the parameter, as shown in Figure 3-107, and then click OK to return to
the DHCP Relay Config window.
Table 3-40 describes the parameters for DHCP Relay VLAN Interface
Configuration.
3-96
Parameter Description
Parameter Description
3-97
Note:
This configuration takes effect only when the Option60 is disabled in the DHCP Relay agent.
a. On the VLAN Interface Server tab of the DHCP Relay Config window, click
Create to open the DHCP Relay VLAN Interface Server dialog box.
b. Configure the parameters, as shown in Figure 3-109, and then click OK to return
to the DHCP Relay Config window.
7. Click Close.
– End of Steps –
Result
The DHCP Relay function is configured successfully.
Prerequisites
Before this operation, make sure that:
l The network devices and lines are normal.
l The xPON service card status is normal.
l The xPON basic service is configured.
Context
To configure the DHCP Server function, perform the following steps:
3-98
Steps
1. Configure level-3 interface.
Refer to the topic 3.17.3 Configuring the DHCP Relay for detailed configuration.
2. Configure the DHCP level-3 public parameters.
Refer to the topic 3.17.3 Configuring the DHCP Relay for detailed configuration.
3. Configure the DHCP level-3 public VLAN interface mode.
Refer to the topic 3.17.3 Configuring the DHCP Relay for detailed configuration.
4. Configure the DHCP server global parameters.
a. Right-click the NE and choose Ethernet Management > DHCP Management >
DHCP Server Configuration to open the DHCP Server Config window.
b. Click Advance to open the DHCP Server Global Config dialog box.
c. Configure the parameters, as shown in Figure 3-110, and then click OK.
b. Configure the parameters, as shown in Figure 3-111, and then click OK to return
to the DHCP Server Config window.
3-99
c. On the VLAN ID tab, select the VLAN and click Modify to open the DHCP Server
VLAN Interface Config dialog box.
d. Select the IP pool, as shown in Figure 3-112, and then click OK.
a. On the VLAN Interface Gateway tab of the DHCP Server Config window, click
Create to open the DHCP Server VLAN Interface Gateway Config dialog box.
b. Configure the parameters, as shown in Figure 3-113, and then click OK to return
to the DHCP Server Config window.
3-100
7. Click Close.
– End of Steps –
Result
The DHCP Server function is configured successfully.
3-101
3-102
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNument N31 unified management system.
l The in-band NM and route are configured.
l The NetNument N31 unified management system communicates with the ZXDSL
9806H properly.
Context
To authenticate an ONU, perform the following steps:
Steps
1. Add an ONU and authenticate it.
a. Open the ONU Configuration window.
4-1
The NetNumen N31 unified management system provides multiple ways to open
the ONU Configuation window. This topic only introduces two ways, as described
in Table 4-1.
Purpose Operation
Open the ONU Configuration On the OLT rack view, right-click the specified PON port
window. and choose ONU Configuration.
The ONU Configuration window manages the ONUs under the specified PON
port in a unified way, as shown in Figure 4-1.
Click Unauth Onu... to open the Unauth ONU Management window, as shown
in Figure 4-2.
4-2
The NetNumen N31 unified management system provides multiple ways to open
the Unauth ONU Config window. Table 4-2 describes the operations.
4-3
Parameters Description
ID ONU ID
Range: 1 – 64
4-4
Note:
The NetNumen N31 unified management system provides three default monitoring levels.
You can modify the level and monitoring period as required.
4-5
c. Click Close.
– End of Steps –
Result
The ONU is authenticated successfully.
Short Description
Perform this procedure to create a 9806H NE through NMS unified management.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
The procedure for creating a 9806H NE is similar to that of creating an OLT NE. Refer to
the topic 3.1 Creating an OLT NE for detailed steps.
To create a 9806H NE, perform the following steps:
Steps
1. Open the Management - Create dialog box.
2. Configure NE parameters.
In the Management - Create dialog box, select ZXDSL9806H from the NE Type pane
in the left, and configure the parameters on the Basic tab in the right pane.
– End of Steps –
4-6
Result
A 9806H NE is created successfully.
Short Description
Perform this procedure to create a ZXDSL 9806H NE through topology synchronization.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is depolyed.
Context
To create an NE, perform the following steps:
Steps
1. Open the ONU Configuration window.
a. Right-click the ZXA10 C220 NE and choose ONU Configuration to open the ONU
Configuration window.
b. In the ONU Configuration window, set the correct card and port. Click Topo
Upda... to open the ONU Topo Node Updating window, as shown in Figure 4-6.
4-7
Result
A 9806H NE is created successfully.
Short Description
Perform this procedure to create a 9806H NE through topology deployment.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is depolyed.
Context
The NetNumen N31 supports the ONU topology deployment function for OLT NEs, which
creates NE groups automatically.
To create a 9806H NE, perform the following steps:
Steps
1. Right-click the ZXA10 C220 NE and choose Deploy Onu Topo to open the ONU Topo
Deploy dialog box, as shown in Figure 4-8.
4-8
2. Click Yes.
– End of Steps –
Result
Figure 4-9 shows the topology deployment of ONUs.
Follow-Up Action
To configure the ONU topology deployment function in the NetNumen N31 unified
management system, perform the following steps:
4-9
2. Modify the parameters in the red frames. Table 4-4 describes the parameters.
Parameters Description
modifyCurrNeNameFlag l 1: If the ONU exits before the deployment, its name is not
modified after the deployment (default).
l 2: If the ONU exits before the deployment, it is renamed
according to the namerule after the deployment.
4-10
Short Description
Perform this procedure to configure the time management on a 9806H.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is depolyed.
Context
To configure the time management, perform the following steps:
Steps
1. Open the Time Management window.
Right-click the 9806H NE and choose System Management > Time Management to
open the NE Time Management window.
2. Configure parameters, as shown in Figure 4-11.
3. Click Apply.
– End of Steps –
4-11
Result
The time management is configured successfully.
Follow-Up Action
You can perform the following steps to configure NE time in batch:
1. Click Batch Configuration to display the Ne Time Batch Configuration, as shown
in Figure 4-12.
4-12
Short Description
Perform this procedure to configure the trap server on a 9806H.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is depolyed.
Context
To configure the trap server, perform the following steps:
Steps
1. Open the Trap Server Configuration window.
Right-click the NE and choose System Management > Trap Server to open the Trap
Server window, as shown in Figure 4-14.
4-13
Note:
If you select Apply to NEs, the trap server is applied to all NEs.
Generally, the Trap Server IP is set to the same IP address of the NM physical host
server.
5. Click OK to return to the Trap Server window.
6. Click Close.
– End of Steps –
Result
The trap server is configured successfully.
4-14
Short Description
Perform this procedure to configure a CLI user on a 9806H.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is depolyed.
Context
To configure a CLI user, perform the following steps:
Steps
1. Open the Rack window.
Double-click the 9806H NE to open the Rack window, as shown in Figure 4-16.
4-15
Note:
In the CLI User Config window, you can perform different operations. Table 4-5
describes the operations related to a CLI user.
Operation Step
Create a CLI user. Click Create. Configure the user name, password, and
access level in the open window.
4. Click Close.
– End of Steps –
Result
The CLI user is configured successfully.
4-16
Short Description
Perform this procedure to configure the SNMP community on a 9806H.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is depolyed.
Context
To configure the SNMP community, perform the following steps:
Steps
1. Open the Rack window.
Double-click the 9806H NE to open the Rack window, as shown in Figure 4-18.
4-17
Note:
You can click Batch Create to create the SNMP community on multiple NEs or click Batch Delete
to delete the SNMP community on multiple NEs.
Note:
It is recommended to select Set as NMS Read Community. If not, the NMS cannot manage
the NE.
4. Click Close.
– End of Steps –
4-18
Result
The SNMP community is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
To create the ADSL line profile, perform the following steps:
Steps
1. Right-click the 9806H NE and choose Offline Profiles > ADSL Offline Line Profile
to open the ADSL Offline Line Profile window, as shown in Figure 4-21.
Note:
You can perform batch operations to NEs by clicking the corresponding buttons in the Batch Op-
erations to NEs box.
4-19
3. Click Create.
– End of Steps –
Result
The ADSL offline line profile is configured successfully.
Short Description
Perform this procedure to configure the 9806H broadband service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Configuration Data
Table 4-6 describes the configuration data of the 9806H broadband service.
Item Data
Context
To configure the 9806H broadband service, perform the following steps:
Steps
1. Configure port VLANs.
4-20
b. Right-click the broadband service card and choose Port VLAN Configuration to
open the Port VLAN Configuration window, as shown in Figure 4-22.
c. Click Modify to display the Port VLAN Configuration dialog box, as shown in
Figure 4-23. Configure the parameters.
Table 4-7 describers the parameters in the Port VLAN Configuration dialog box.
Parameter Description
4-21
Parameter Description
Specify Uplink Ports Bound to VLAN Select the specified Uplink Port to bind the uplink
(Tagged) port to VLANs in batch.
a. In the Rack window, right-click the main control card and choose VLAN
Configuration to open the Static VLAN Configuration window, as shown in
Figure 4-24.
b. Click View Binding to open the Port Binding Information dialog box, as shown
in Figure 4-25.
4-22
Table 4-8 describers the parameters in the DSL Ports Batch Configuration dialog
box.
4-23
Parameter Description
Result
The broadband service is configured successfully.
Short Description
Perform this procedure to configure the multicast service on a 9806H.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Configuration Data
Table 4-9 describes configuration data of the 9806H multicast service.
Item Data
4-24
Item Data
Multicast groups The video server provides three programs, which use the
default preview template:
l Program 1: 224.1.1.1
l Program 1: 224.1.1.2
l Program 1: 224.1.1.3
Context
To configure the 9806H multicast service, perform the following steps:
Steps
1. Configure IPTV global parameters.
a. Double-click the 9806H NE to open the Rack window.
b. Right-click the main control card and choose IPTV Management > IGMP Global
Configuration to open the IGMP Configuration window.
c. Select Enable from the IGMP Status drop-down list and Snooping from the
Working Mode drop-down list, as shown in Figure 4-27.
4-25
d. Click Set.
2. Configure the static VLAN and bind ports.
a. In the 9806H Rack window, right-click the broadband service card and choose
Port VLAN Configuration to open the Port VLAN Configuration window.
b. Click Modify to display the Port VLAN Configuration dialog box. Configure the
parameters, as shown in Figure 4-28.
4-26
c. Click OK.
4. Configure the multicast VLAN.
a. In the 9806H Rack window, right-click the broadband service card and
choose IPTV Management > Multicast VLAN Registration to open the MVR
Configuration window.
b. ON the Basic tab, configure the parameters, as shown in Figure 4-30.
c. Click Add.
5. Configure multicast groups.
a. In the MVR Configuration window, select the Channel IP tab.
b. Click Add to open the MVR Configuration–Add Group dialog box.
c. Configure the parameters, as shown in Figure 4-31.
4-27
d. Click OK.
6. Configure the receiving port.
a. In the MVR Configuration window, select the Receiving Port tab, as shown in
Figure 4-32.
a. On the Source Port tab of the MVR Configuration window, select the specified
uplink port and click Bind, as shown in Figure 4-33.
4-28
Right-click the 9806H NE and choose Save Configuration Data. A confirm dialog
box appears. Click OK to save the configuration data to the flash.
– End of Steps –
Result
The 9806H multicast service is configured successfully.
Short Description
Perform this procedure to configure the VoIP service on a 9806H.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Configuration Data
Table 4-10 lists the 9806H VoIP service configuration data.
4-29
Item Data
l Protocol: H.248
l Registration mode: IPv4
VoIP resouce l SS IP address: 10.66.22.1
l TID: USER0–USER31
l RTP: 00000–00015
Context
To configure the 9806H VoIP service, perform the following steps:
Steps
1. Configure the VoIP service VLAN IP address.
a. Double-click the 9806H NE to open the Rack window.
b. Right-click the main control card and choose System Management > Static
Subnet to open the Subnet Configuration window.
c. Click Create to open the Add Subnet dialog box.
d. Configure parameters, as shown in Figure 4-34, and then click OK.
4-30
Note:
4-31
Note:
When you configure the VoIP service VLAN IP address, the IP address is automatically set to the
MG IP address.
a. In the 9806H NE Rack window, right-click the VoIP card and choose VoIP
Management > MG Configuration to open the MG window.
b. Select the default MG and click Modify to open the Modify MGC dialog box, as
shown in Figure 4-37.
4-32
d. Click OK.
6. Configure VoIP resource.
a. In the 9806H NE Rack window, right-click the VoIP card and choose VoIP
Management > VoIP Resource Configuration to open the VOIP Resource
window, as shown in Figure 4-39.
4-33
b. Click TID Delete to open the Confirm dialog box, and then click OK.
c. Click TID Create to open the Set TID Prefix dialog box.
a. In the 9806H NE Rack window, right-click the VoIP card and choose Port Manager
to open the Port Manager window, as shown in Figure 4-41.
4-34
d. Click Set Termination ID Prefix to open the Set Termination ID Prefix dialog
box. Set the Termination ID prefix, as shown in Figure 4-43.
4-35
e. Click OK to confirm.
8. Query the VoIP registration status.
a. Double-click the 9806H NE to open the Rack window.
b. Right-click the VoIP card and choose VoIP Resource Statistic > H248
Performance Statistic to query the VoIP registration status.
9. Save the data.
Right-click the 9806H NE and choose Save Configuration Data. A confirm dialog
box appears. Click OK to save the configuration data to the flash.
– End of Steps –
Result
The VoIP service on a 9806H is configured successfully.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNument N31 unified management system.
4-36
Context
The procedure for authenticating an F820 ONU (EPON) is similar to that of authenticating a
9806H ONU. Refer to the topic 4.1.1 Authenticating a 9806H ONU for detailed information.
Short Description
Perform this procedure to create an F820 NE through NMS unified management.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is depolyed.
Context
The procedure for creating an ONU NE is similar to that for creating an OLT NE. Refer to
the topic 3.1 Creating an OLT NE for detailed steps.
To create an ONU NE, perform the following steps:
Steps
1. Open the Management - Create dialog box.
On the Topology Management tab in the NetNumenN31 Unified Management
System window, right-click the group and choose Create NE to open the Management
- Create dialog box.
2. Configure NE parameters.
In the Management - Create dialog box, select F820 from the NE Type pane in the
left, and configure the parameters on the Basic tab in the right pane.
3. Click Create, and then click Close.
– End of Steps –
4-37
Result
The NE is created successfully.
Short Description
Perform this procedure to create an F820 NE through topology synchronization.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
The procedure for creating an F820 NE is similar to that for creating a 9806H NE. Refer
to the topic 4.1.2.2 Creating an NE Through Topology Synchronization for detailed
information.
Short Description
Perform this procedure to create an F820 NE through topology deployment.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
The procedure for creating an F820 NE is similar to that for creating a 9806H NE. Refer
to the topic 4.1.2.3 Creating a NE Through ONU Topology Deployment for detailed
information.
4-38
Short Description
Perform this procedure to configure the time management on an F820.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
To configure the time management, perform the following steps:
Steps
1. Open the NE Time window.
Right-click the F820 NE and choose System Management > NE Time to open the
NE Time window, as shown in Figure 4-44.
Note:
If you select Use UMS Server Time, the NE synchronizes the time with the NMS.
If you select Apply to NEs, the time of the NEs is configured in batch.
4-39
3. Click Set.
– End of Steps –
Result
Time management is configured successfully.
Short Description
Perform this procedure to configure the trap server on an F820.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
To configure the trap server, perform the following steps:
Steps
1. Open the Trap Server Configuration window.
Right-click the NE and choose System Management > Trap Server to open the Trap
Server Configuration window, as shown in Figure 4-45.
4-40
Note:
If you select Apply to NEs, the trap server is applied to all NEs.
Result
The trap server is configured successfully.
Short Description
Perform this procedure to configure a CLI user on an F820.
4-41
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
To configure a CLI user, perform the following steps:
Steps
1. Open the Rack window.
Double-click the F820 NE to open the Rack window, as shown in Figure 4-47.
Right-click the MS8E card and choose System Management > CLI User Config to
open the CLI User Config window, as shown in Figure 4-48.
4-42
Note:
In the CLI User Config window, you can perform different operations. Table 4-11
describes the operations related to a CLI user.
Operation Step
Create a CLI user. Click Create. Configure the user name, password, and
access level in the open window.
4. Click Close.
– End of Steps –
Result
The CLI user is configured successfully.
Short Description
Perform this procedure to configure the SNMP community on an F820.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
To configure the SNMP community, perform the following steps:
Steps
1. Open the SNMP Community Configuration window.
4-43
2. Type the SNMP community name in the Community Name text box.
Note:
If you select Apply to Nes, the community name is applied to all NEs.
3. Click OK.
– End of Steps –
Result
The SNMP community is configured successfully.
Short Description
Perform this procedure to configure the F820 broadband service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
l The ONU supports extended OAM protocol management.
4-44
Configuration Data
Table 4-12 describes the configuration data of the F820 broadband service.
Item Data
Context
To configure the F820 broadband service, perform the following steps:
Steps
1. Open the ONU Configuration window.
a. Right-click the ZXA10 C220 NE and choose ONU Configuration to open the ONU
Configuration window.
b. Select the card and port, as shown in Figure 4-50.
4-45
For example, select port 1 and add port 1 to VLAN 2001. Select Tag for Mode, as
shown in Figure 4-51.
Result
The F820 broadband service is configured successfully.
Short Description
Perform this procedure to configure the F820 multicast service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
4-46
Configuration Data
Table 4-13 describes the configuration data of the F820 multicast service.
Item Data
Multicast VLAN 51
Unicast VLAN 85
Context
To configure the F820 multicast service, perform the following steps:
Steps
1. Open the ONU Configuration window.
a. Right-click the ZXA10 C220 NE and choose ONU Configuration to open the ONU
Configuration window.
b. Select the card and port, as shown in Figure 4-52.
4-47
b. In the VLAN and Multicast Configuration dialog box, click the VLAN
Configuration tab.
c. Select the port used for the unicast service, and then modify the port VLAN
configuration.
For example, select port 2, add port 2 to VLAN 85, and select Tag for Mode, as
shown in Figure 4-53.
4-48
Parameter Description
d. Select 51 from the Available Multicast VLAN column. Click to add VLAN
51 to the Multicast VLAN column, as shown in Figure 4-55.
4-49
Result
The F820 multicast service is configured successfully.
Short Description
Perform this procedure to configure the F820 VoIP service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
l The ONU supports extended OAM protocol management.
4-50
Configuration Data
Table 4-15 describes the configuration data of the F820 VoIP service.
Item Data
Voice VLAN 46
Context
To configure the F820 VoIP service, perform the following steps:
Steps
1. Open the ONU Configuration window.
a. Right-click the ZXA10 C220 NE and choose ONU Configuration to open the ONU
Configuration window.
b. Select the card and port, as shown in Figure 4-56.
4-51
4-52
Table 4-16 describes the parameters in the VOIP Connect Config dialog box.
4-53
Parameter Description
a. In the ONU Configuration window, right-click the F820 and choose VOIP
Configuration > Domain Config. The VOIP Domain Config dialog box appears.
b. Configure the parameters as required, as shown in Figure 4-60.
Table 4-17 describes the parameters in the VOIP Domain Config dialog box.
Parameter Description
4-54
a. In the ONU Configuration window, right-click the F820 NE and choose VOIP
Configuration > TID Config (User). The VOIP User TID Config dialog box
appears.
b. Click Add. Configure the user TID parameters in the pop-up dialog box, as shown
in Figure 4-61.
c. Click OK to confirm.
7. Configure VoIP resource termination ID (RTP-TID).
a. In the ONU Configuration window, right-click the F820 NE and choose VOIP
Configuration > TID Config (RTP). The TID Configuration (RTP) dialog box
appears.
b. Configure VoIP resource termination ID, as shown in Figure 4-62.
4-55
Result
The F820 VoIP service is configured successfully.
Prerequisites
Before this operation, make sure that:
4-56
Context
The procedure for authenticating an F822 ONU is similar to that of authenticating a 9806H
ONU. Refer to the topic 4.1.1 Authenticating a 9806H ONU for detailed information.
Short Description
Perform this procedure to create an F822 NE on the NMS unified management system.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
The procedure for creating an ONU NE is similar to that for creating an OLT NE. Refer to
the topic 3.1 Creating an OLT NE for detailed steps.
To create an ONU NE, perform the following steps:
Steps
1. Open the Management - Create dialog box.
On the Topology Management tab in the NetNumenN31 Unified Management
System window, right-click the group and choose Create NE to open the Management
- Create dialog box.
2. Configure NE parameters.
In the Management - Create dialog box, select F820 from the NE Type pane in the
left, and configure the parameters on the Basic tab in the right pane.
3. Click Create, and then click Close.
– End of Steps –
Result
An F822 NE is created successfully.
4-57
Short Description
Perform this procedure to create an F822 NE through topology synchronization.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
The procedure for creating an F822 NE is similar to that for creating a 9806H NE. Refer
to the topic 4.1.2.2 Creating an NE Through Topology Synchronization for detailed
information.
Short Description
Perform this procedure to create an F822 NE through topology deployment.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
The procedure for creating an F822 NE is similar to that for creating a 9806H NE. Refer
to the topic 4.1.2.3 Creating a NE Through ONU Topology Deployment for detailed
information.
4-58
Short Description
Perform this procedure to configure the time management on an F822.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
To configure the time management, perform the following steps:
Steps
1. Open the Time Management window.
Right-click the F822 NE and choose System Management > Time Management to
open the Time Management window.
2. Configure parameters, as shown in Figure 4-63.
3. Click Apply.
4-59
Note:
If you click Batch Configuration, the NE time can be configured in batch. For detailed information,
you can refer to the topic 4.1.3.1 Configuring the Time Management.
– End of Steps –
Result
The time management is configured successfully.
Short Description
Perform this procedure to configure the trap server on an F822.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
To configure the trap server, perform the following steps:
Steps
1. Open the Trap Server Configuration window.
Right-click the NE and choose System Management > Trap Server to open the Trap
Server window, as shown in Figure 4-64.
4-60
Note:
If you select Apply to NEs, the trap server is applied to all NEs.
– End of Steps –
Result
The trap server is configured successfully.
Short Description
Perform this procedure to configure a CLI user on an F822.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
4-61
Context
To configure a CLI user, perform the following steps:
Steps
1. Open the Rack window.
Double-click the F822 NE to open the Rack window, as shown in Figure 4-66.
Note:
In the CLI User Config window, you can perform different operations. Table 4-18
describes the operations related to a CLI user.
4-62
Operation Step
Create a CLI user. Click Create. Configure the user name, password, and
access level in the open window.
4. Click Close.
– End of Steps –
Result
The CLI user is configured successfully.
Short Description
Perform this procedure to configure the SNMP community on an F822.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Context
To configure the SNMP community, perform the following steps:
Steps
1. Open the SNMP Community Configuration window.
Right-click the GNI card and choose System Management > SNMP Community
Configuration to open the SNMP Community Configuration window, as shown in
Figure 4-68.
4-63
Note:
You can click Batch Create to create SNMP community on multiple NEs or click Batch Delete to
delete SNMP community on multiple NEs.
Note:
It is recommended to select Set as NMS Read Community. If not, the NMS cannot manage the
NE.
3. Click Close.
– End of Steps –
Result
The SNMP community is configured successfully.
4-64
Short Description
Perform this procedure to configure the F822 broadband service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NMS.
l The in-band NM and route are configured.
l The OLT device network is deployed.
Configuration Data
Table 4-19 describes the configuration data of the F822 broadband service.
Item Data
Context
To configure the F822 broadband service, perform the following steps:
Steps
1. Configure port VLANs.
4-65
Table 4-20 describers the parameters in the Port VLAN Configuration dialog box.
Parameter Description
Specify Uplink Ports Bound to VLAN Select the specified Uplink Port to bind the uplink
(Tagged) port to VLANs in batch.
4-66
4-67
b. Click Close.
4. Save configuration.
Right-click the NE and choose Save Configuration Data to open the Confirm dialog
box, and then click OK.
– End of Steps –
Result
The F822 broadband service is configured successfully.
Short Description
Perform this procedure to configure the multicast service on an F822.
Prerequisites
Before this operation, make sure that:
4-68
Configuration Data
Table 4-21 describes the configuration data of the F822 multicast service.
Item Data
Context
To configure the F822 multicast service, perform the following steps:
Steps
1. Configure the IGMP global parameters.
a. Double-click the F822 NE to open the Rack window.
b. Right-click the uplink card and choose IPTV Management > IGMP Global
Configuration to open the IGMP Global Configuration window.
c. Configure the parameters, as shown in Figure 4-74.
4-69
d. Click Set.
2. Configure port VLAN.
a. In the Rack window, right-click the broadband service card and choose Port VLAN
Configuration to open the Port VLAN Configuration window.
b. Click Modify to open the Port VLAN Configuration dialog box.
c. Configure the parameters, as shown in Figure 4-75, and then click Set.
3. Configure MVLAN.
a. In the Rack window, right-click the broadband service card and choose IPTV
Management > Multicast VLAN Registration to open the Multicast VLAN
Registration window.
4-70
b. ON the Basic tab, configure the parameters, as shown in Figure 4-76, and then
click Add.
4-71
On the Receiving Port tab, select the MVLAN and the port, and then click Bind, as
shown in Figure 4-78.
7. Save configuration.
4-72
Right-click the NE and choose Save Configuration Data to open the Confirm dialog
box, and then click OK.
– End of Steps –
Result
The F822 multicast service is configured successfully.
Short Description
Perform this procedure to configure the F822 VoIP service.
Prerequisites
Before this operation, make sure that:
Context
The F822 supports three VoIP protocols:
l H.248
l MGCP
l SIP
The F822 does not support the three protocols simultaneously. There are different versions
of F822 that corresponds to each protocol.
Configuration Data
Table 4-22 describes the configuration data of the F822 VoIP service.
Item Data
Priority 7
MG l IP address: 10.51.20.14
l Mask: 255.255.255.0
l Gateway: 10.51.20.1
4-73
Item Data
MGC l ID: 1
l IP address: 10.2.60.25
l Type: ZTE
Context
To configure the F822 VoIP service, perform the following steps:
Steps
1. Double-click the F822 NE to open the Rack window.
2. Configure voice service VLAN uplink port.
a. In the F822 NE Rack window, right-click the main control card and choose Port
VLAN Configuration to open the Port VLAN Configuration window.
b. Select the port and click Modify to open the Port VLAN Configuration dialog box.
c. Configure the VLAN, as shown in Figure 4-80, and then click Set.
4-74
Note:
4-75
Note:
When you configure the VoIP service VLAN IP address, the IP address is automatically set to the
MG IP address.
a. In the F822 NE Rack window, right-click the VoIP card and choose VoIP
Management > MG Configuration to open the MG window.
b. Click Modify to open the Modify MG dialog box, as shown in Figure 4-83.
Note:
l MGC ID: 1
l MGC IP: 192.168.1.10
l User TID: USER000 – USER023
l IPS TID: RTP/00000 – RTP/00031
a. In the F822 NE Rack window, right-click the narrowband card and choose VoIP
Management > MGC Configuration to open the MGC window.
b. Click Modify to open the Modify MGC dialog box.
c. Modify the MGC IP address, as shown in Figure 4-84, and then click OK.
4-76
d. Click Set Termination ID Prefix to open the Set Termination ID Prefix dialog
box.
e. Configure the parameters, as shown in Figure 4-86, and then click OK.
4-77
Right-click the F822 NE and choose Save Configuration Data to open the Confirm
dialog box, and then click OK.
– End of Steps –
Result
The F822 VoIP service is configured successfully.
4-78
Prerequisites
Before this operation, make sure that:
Context
The default F820 ONU type on the ZXA10 C220 is EPON ONU. To configure the GPON
ONU type, refer to the topic 3.9.1 Configuring the GPON ONU Type Profile.
Steps
1. Open the ONU Basic Information window.
5-1
Right-click the ZXA10 C220 NE and choose GPON Management > ONU Basic
Information to open the ONU Basic Information window.
2. Query the unauthenticated ONU.
In the ONU Basic Information window, select the GPON card and the PON port, the
unauthenticated ONU is displayed in the Registered but not in Service ONU pane,
as shown in Figure 5-1.
5-2
Parameter Description
ONU ONU ID
5-3
Parameter Description
a. Select the ONU, and then click Mng Channel to open the Management Channel
dialog box.
b. Configure the parameters, as shown in Figure 5-3, and then click OK to return to
the ONU Basic Information window.
5. Click Close.
– End of Steps –
5-4
Result
The ONU is authenticated successfully.
Short Description
Perform this procedure to configure the F820 broadband service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNumen N31 NMS.
l The in-band NM and route are configured.
l The ZXA10 C220 communicates with the NMS properly.
l The GPON ONU is authenticated.
l The OLT configuration is completed.
Configuration Data
Table 5-2 describes configuration data of the F820 broadband service.
Item Data
VLAN ID 2001
Priority 1
5-5
Item Data
ONU ID 3
Context
To configure the F820 broadband service, perform the following steps:
Steps
1. Configure the T-CONT.
a. Right-click the ZXA10 C220 NE and choose GPON Management > ONU T-CONT
Bandwidth Configuration to open the ONU T-CONT Bandwidth Configuration
window, and then click to select the GPON card, as shown in Figure 5-4.
b. Click Add to open the Add ONU T-CONT Bandwidth Configuration dialog box.
c. Configure T-CONT parameters, and click after Bandwidth to select the
bandwidth profile, as shown in Figure 5-5, and then click OK.
5-6
a. On the GemPort tab, click Add to open the Create GemPort dialog box.
b. Configure GEM Port parameters, as shown in Figure 5-7, and then click OK to
return to the Traffic Connection window.
5-7
Note:
l Flow 1 and flow 255 are the default flows.
l By default, all UNI ports are bound to switch unit 1.
a. On the Connect tab, click Add to open the Create Connect dialog box.
b. Configure the connection parameters, as shown in Figure 5-9, and then click OK.
5-8
b. Select the flow and click Modify to open the Modify ONU Uplink VLAN TAG Filer
Mode dialog box.
c. Configure VLAN Tag filter mode, as shown in Figure 5-11, and then click OK.
5-9
Result
The F820 broadband service is configured successfully.
5-10
Short Description
Perform this procedure to configure the F820 multicast service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNumen N31 NMS.
l The in-band NM and route are configured.
l The ZXA10 C220 communicates with the NMS properly.
l The GPON ONU is authenticated.
l The OLT configuration is completed.
Configuration Data
Table 5-3 describes the configuration data of the F820 multicast service.
Item Data
Prioriy 5
ONU ID 3
Context
To configure the F820 multicast service, perform the following steps:
5-11
Steps
1. Configure the T-CONT.
a. Right-click the ZXA10 C220 NE and choose GPON Management > ONU T-CONT
Bandwidth Configuration to open the ONU T-CONT Bandwidth Configuration
window, and then click to select the GPON card, as shown in Figure 5-13.
b. Click Add to open the Add ONU T-CONT Bandwidth Configuration dialog box.
c. Configure T-CONT parameters, and click after Bandwidth to select the
bandwidth profile, as shown in Figure 5-14, and then click OK.
5-12
Right-click the ZXA10 C220 NE and choose GPON Management > Traffic
Connection to open the Traffic Connection window, select the GPON card, the
PON port, and the ONU, as shown in Figure 5-15.
5-13
Note:
a. Right-click the ZXA10 C220 NE and choose GPON Management > Flow TCI Map
Mode Configuration to open the Flow TCI Map Mode Configuration window,
select the GPON card, the PON port, and the ONU, as shown in Figure 5-19.
5-14
b. Select the flow and click Modify to open the Modify ONU Uplink VLAN TAG Filer
Mode dialog box.
c. Configure VLAN tag filter mode, as shown in Figure 5-20, and then click OK to
return to the Flow TCI Map Mode Configuration window.
d. Click Filter Item Management to open the Flow TCI Map Item Configuration
dialog box.
e. Click Create to open the Create Flow TCI Map Item dialog box.
f. Configure the priority and the VLAN ID, as shown in Figure 5-21, and then click
OK.
5-15
Note:
Flow 255 is the default multicast flow, which connects to GEM Port 4095.
b. Configure VLAN tag filter mode, as shown in Figure 5-22, and then click OK to
return to the Flow TCI Map Mode Configuration window.
c. Click Filter Item Management to open the Flow TCI Map Item Configuration
dialog box.
d. Click Create to open the Create Flow TCI Map Item dialog box.
e. Configure the priority and the VLAN ID, as shown in Figure 5-23, and then click
OK.
5-16
a. Right-click the F820 NE and choose Ethernet Management > Multicast IPTV
Management > IGMP Global to open the IGMP Global Configuration window.
b. Configure IGMP global parameters, as shown in Figure 5-25, and then click Set.
5-17
Note:
It is recommended to use the default IGMP global parameters. The default IGMP protocol on
the F820 is IGMP Snooping.
b. Click to select the main control card, select the port and click Modify to open
the RES_MVLAN Translate Dlg dialog box.
c. Configure the multicast VLAN (CVLAN), as shown in Figure 5-26, and then click
OK.
5-18
Result
The F820 multicast service is configured successfully.
Short Description
Perform this procedure to configure the F820 VoIP service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNumen N31 NMS.
l The in-band NM is configured.
l The ZXA10 C220 communicates with the NMS properly.
l The GPON ONU is authenticated.
l The OLT configuration is completed.
l The data on the SS is configured.
Context
The F820 supports three VoIP protocols:
l H.248
l MGCP
l SIP
The F820 does not support the three protocols simultaneously. There are different versions
of F820 that supports each protocol.
This topic takes the SIP protocol as an example.
Configuration Data
Table 5-4 describes configuration data of the F820 VoIP service.
Item Data
VLAN ID 301
Priority 7
5-19
Item Data
ONU ID 3
Steps
1. Configure the T-CONT.
a. Right-click the ZXA10 C220 NE and choose GPON Management > ONU T-CONT
Bandwidth Configuration to open the ONU T-CONT Bandwidth Configuration
window, and then click to select the GPON card, as shown in Figure 5-27.
5-20
b. Click Add to open the Add ONU T-CONT Bandwidth Configuration dialog box.
c. Configure T-CONT parameters, and click after Bandwidth to select the
bandwidth profile, as shown in Figure 5-28, and then click OK.
Right-click the ZXA10 C220 NE and choose GPON Management > Traffic
Connection to open the Traffic Connection window, select the GPON card, the
PON port, and the ONU, as shown in Figure 5-29.
5-21
a. On the Flow tab, click Add to open the Create Flow dialog box.
b. Configure the flow parameters, as shown in Figure 5-31, and then click OK to
return to the Traffic Connection window.
5-22
Note:
l Flow 1 and flow 255 are the default flows.
l By default, all UNI ports are bound to switch unit 1.
a. Right-click the ZXA10 C220 NE and choose GPON Management > Flow TCI Map
Mode Configuration to open the Flow TCI Map Mode Configuration window,
select the GPON card, the PON port, and the ONU, as shown in Figure 5-33.
5-23
b. Select the flow and click Modify to open the Modify ONU Uplink VLAN TAG Filer
Mode dialog box.
c. Configure VLAN tag filter mode, as shown in Figure 5-34, and then click OK to
return to the Flow TCI Map Mode Configuration window.
d. Click Filter Item Management to open the Flow TCI Map Item Configuration
dialog box.
e. Click Create to open the Create Flow TCI Map Item dialog box.
f. Configure the priority and the VLAN ID, as shown in Figure 5-35, and then click
OK.
5-24
5-25
Note:
c. Configure the parameters, as shown in Figure 5-37, and then click OK.
b. Select the GPON card, the PON port, and the ONU, and then click Modify to open
the Modify IP Host dialog box.
c. Configure IP Host parameters, as shown in Figure 5-38, and then click OK.
5-26
b. Select the GPON card, the PON port, and the ONU, and then click Add to open
the Add SIP Agent dialog box.
c. Configure the SIP agent parameters, as shown in Figure 5-39, and then click OK.
5-27
a. Right-click the ZXA10 C220 NE and choose GPON Management > VOIP
Management > SIP User Management to open the SIP User Management
window.
b. Select the GPON card, the PON port, and the ONU, and then click Add to open
the Add SIP User dialog box.
c. Configure SIP user parameters, as shown in Figure 5-40, and then click OK.
Result
The F820 VoIP service is configured successfully.
Prerequisites
Before this operation, make sure that:
5-28
Context
The default F822 ONU type on the ZXA10 C220 is EPON ONU. To configure the GPON
ONU type, refer to the topic 3.9.1 Configuring the GPON ONU Type Profile.
To authenticate an F822 GPON ONU, perform the following steps:
Steps
1. Open the ONU Basic Information window.
Right-click the ZXA10 C220 NE and choose GPON Management > ONU Basic
Information to open the ONU Basic Information window.
2. Query the unauthenticated ONU.
In the ONU Basic Information window, select the GPON card and the PON port, the
unauthenticated ONU is displayed in the Registered but not in Service ONU pane,
as shown in Figure 5-41.
5-29
Parameter Description
ONU ONU ID
5-30
Parameter Description
a. Select the ONU, and then click Mng Channel to open the Management Channel
dialog box.
b. Configure the parameters, as shown in Figure 5-43, and then click OK to return to
the ONU Basic Information window.
5. Click Close.
– End of Steps –
5-31
Result
The ONU is authenticated successfully.
Short Description
Perform this procedure to configure the F822 broadband service.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNumen N31 NMS.
l The in-band NM and route are configured.
l The ZXA10 C220 communicates with the NMS properly.
l The GPON ONU is authenticated.
l The OLT configuration is completed.
Configuration Data
Table 5-6 describes configuration data of the F822 broadband service.
Item Data
Priority 1
5-32
Item Data
ONU ID 2
Context
To configure the F822 broadband service, perform the following steps:
Steps
1. Configure the T-CONT.
a. Right-click the ZXA10 C220 NE and choose GPON Management > ONU T-CONT
Bandwidth Configuration to open the ONU T-CONT Bandwidth Configuration
window, and then click to select the GPON card, as shown in Figure 5-44.
b. Click Create to open the Add ONU T-CONT Bandwidth Configuration dialog
box.
c. Configure T-CONT parameters, and click after Bandwidth to select the
bandwidth profile, as shown in Figure 5-45, and then click OK.
5-33
a. On the GemPort tab, click Add to open the Create GemPort dialog box.
b. Configure GEM Port parameters, as shown in Figure 5-47, and then click OK to
return to the Traffic Connection window.
5-34
Note:
l Flow 1 and flow 255 are the default flows.
l By default, all UNI ports are bound to switch unit 1.
a. On the Connect tab, click Add to open the Create Connect dialog box.
b. Configure the connection parameters, as shown in Figure 5-49, and then click OK.
5-35
b. Select the flow and click Modify to open the Modify ONU Uplink VLAN TAG Filer
Mode dialog box.
c. Configure VLAN Tag filter mode, as shown in Figure 5-51, and then click OK.
5-36
Result
The F820 broadband service is configured successfully.
Short Description
Perform this procedure to configure the multicast service on an F822.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNumen N31 NMS.
l The in-band NM and route are configured.
l The ZXA10 C220 communicates with the NMS properly.
l The GPON ONU is authenticated.
l The OLT configuration is completed.
Configuration Data
Table 5-7 describes configuration data of the F822 multicast service.
Item Data
5-37
Item Data
Priority 5
ONU ID 3
Steps
1. Configure the T-CONT.
a. Right-click the ZXA10 C220 NE and choose GPON Management > ONU T-CONT
Bandwidth Configuration to open the ONU T-CONT Bandwidth Configuration
window, and then click to select the GPON card, as shown in Figure 5-52.
5-38
b. Click Add to open the Add ONU T-CONT Bandwidth Configuration dialog box.
c. Configure T-CONT parameters, and click after Bandwidth to select the
bandwidth profile, as shown in Figure 5-53, and then click OK.
5-39
b. Configure GEM Port parameters, as shown in Figure 5-55, and then click OK.
Note:
b. Configure the connection parameters, as shown in Figure 5-57, and then click OK.
5-40
b. Select the flow and click Modify to open the Modify ONU Uplink VLAN TAG Filer
Mode dialog box.
c. Configure VLAN Tag filter mode, as shown in Figure 5-59, and then click OK to
return to the Traffic Connection window.
5-41
d. Click Filter Item Management to open the Flow TCI Map Item Configuration
dialog box.
e. Click Create to open the Create Flow TCI Map Item dialog box.
f. Configure the priority and the VLAN ID, as shown in Figure 5-60, and then click
OK.
Note:
Flow 255 is the default multicast flow, which connects to GEM Port 4095.
b. Configure VLAN Tag filter mode, as shown in Figure 5-61, and then click OK to
return to the Traffic Connection window.
5-42
c. Click Filter Item Management to open the Flow TCI Map Item Configuration
dialog box.
d. Click Create to open the Create Flow TCI Map Item dialog box.
e. Configure the priority and the VLAN ID, as shown in Figure 5-62, and then click
OK.
– End of Steps –
Result
The F822 multicast service is configured successfully.
5-43
Short Description
Perform this procedure to provision the VoIP service on an F822.
Prerequisites
Before this operation, make sure that:
l You have logged in to the NetNumen N31 NMS.
l The in-band NM is configured.
l The ZXA10 C220 communicates with the NMS properly.
l The GPON ONU is authenticated.
l The OLT configuration is completed.
l The data on the SS is configured.
Context
The F822 supports three VoIP protocols:
l H.248
l MGCP
l SIP
Configuration Data
Table 5-8 describes configuration data of the F822 VoIP service.
Item Data
VLAN ID 301
Priority 7
ONU ID 3
5-44
Item Data
MG l IP address: 10.51.20.14
l Mask: 255.255.255.0
l Gateway: 10.51.20.1
MGC l ID: 1
l IP address: 10.2.60.25
l Type: ZTE
Steps
1. Configure T-CONT.
a. Right-click the ZXA10 C220 NE and choose GPON Management > ONU T-CONT
Bandwidth Configuration to open the ONU T-CONT Bandwidth Configuration
window, and then click to select the GPON card, as shown in Figure 5-63.
b. Click Add to open the Add ONU T-CONT Bandwidth Configuration dialog box.
5-45
a. On the GemPort tab, click Add to open the Create GemPort dialog box.
b. Configure GEM Port parameters, as shown in Figure 5-66, and then click OK to
return to the Traffic Connection window.
5-46
Note:
l Flow 1 and flow 255 are the default flows.
l By default, all UNI ports are bound to switch unit 1.
a. On the Connect tab, click Add to open the Create Connect dialog box.
b. Configure the connection parameters, as shown in Figure 5-68, and then click OK.
5-47
b. Select the flow and click Modify to open the Modify ONU Uplink VLAN TAG Filer
Mode dialog box.
c. Configure VLAN Tag filter mode, as shown in Figure 5-70, and then click OK to
return to the Flow TCI Map Mode Configuration window.
5-48
d. Click Filter Item Management to open the Flow TCI Map Item Configuration
dialog box.
e. Click Create to open the Create Flow TCI Map Item dialog box.
f. Configure the priority and the VLAN ID, as shown in Figure 5-71, and then click
OK.
– End of Steps –
Result
The F822 VoIP service is configured successfully.
5-49
5-50
6-1
6-2
7-1
7-2
I
ZXA10 C220 Configuration Manual (NetNumen) Volume I
II
Figures
III
ZXA10 C220 Configuration Manual (NetNumen) Volume I
IV
Figures
V
ZXA10 C220 Configuration Manual (NetNumen) Volume I
VI
Figures
VII
ZXA10 C220 Configuration Manual (NetNumen) Volume I
VIII
Figures
IX
ZXA10 C220 Configuration Manual (NetNumen) Volume I
Figure 5-62 Create Flow TCI Map Item (Multicast) .................................................. 5-43
Figure 5-63 ONU T-CONT Bandwidth Configuration ............................................... 5-45
Figure 5-64 Add ONU T-CONT Bandwidth Configuration ........................................ 5-46
Figure 5-65 Traffic Connection ................................................................................ 5-46
Figure 5-66 Create GEM Port ................................................................................. 5-47
Figure 5-67 Create Flow ......................................................................................... 5-47
Figure 5-68 Create Connection ............................................................................... 5-48
Figure 5-69 Flow TCI Map Mode Configuration....................................................... 5-48
Figure 5-70 Modify ONU Uplink VLAN TAG Filer Mode........................................... 5-49
Figure 5-71 Create Flow TCI Map Item ................................................................... 5-49
X
Tables
Table 1-1 NEs NetNumen N31 System Supports ...................................................... 1-2
Table 2-1 Files in the Installation Directory ................................................................ 2-2
Table 2-2 Basic Information Parameters.................................................................. 2-10
Table 2-3 General NEs............................................................................................ 2-12
Table 2-4 Database Configuration Parameters........................................................ 2-14
Table 2-5 Checking Database Server Status ........................................................... 2-15
Table 2-6 FTP Service Configuration Parameters ................................................... 2-17
Table 2-7 Policy Configuration Parameters ............................................................. 2-19
Table 2-8 MetricX System Functions ....................................................................... 2-28
Table 2-9 MetricX Configuration Data...................................................................... 2-29
Table 2-10 TL1 Configuration File Parameters Description...................................... 2-37
Table 2-11 TL1 Command Keywords and Parameters Description .......................... 2-38
Table 2-12 Operations on Policies........................................................................... 2-40
Table 2-13 Policy Basic Information ........................................................................ 2-42
Table 2-14 Configuration Recommendation for Data Configuration Backup
Policy ..................................................................................................... 2-45
Table 2-15 Policy Planning Suggestion ................................................................... 2-47
Table 2-16 Operations on Polling Tasks .................................................................. 2-55
Table 2-17 Polling Task Parameters ........................................................................ 2-56
Table 2-18 Operations of Fault Management .......................................................... 2-58
Table 2-19 Current Alarm Query Conditions ............................................................ 2-63
Table 2-20 History Alarm Query Conditions - Example 1 ......................................... 2-65
Table 2-21 History Alarm Query Conditions - Example 2 ......................................... 2-65
Table 2-22 Alarm Filtering Rules ............................................................................. 2-67
Table 2-23 Configuration Data for the Alarm Global Filtering Rule........................... 2-68
Table 2-24 Configuration Data for the Alarm Counting Rule .................................... 2-70
Table 2-25 Alarm Sound Setting.............................................................................. 2-74
Table 3-1 Parameters for NE Creation ...................................................................... 3-2
Table 3-2 Version Area Description ........................................................................... 3-5
Table 3-3 Version Management Operations .............................................................. 3-5
Table 3-4 User Access Level Description ................................................................ 3-10
Table 3-5 Parameters for Trap Server Configuration ............................................... 3-13
XI
ZXA10 C220 Configuration Manual (NetNumen) Volume I
XII
Tables
Table 3-40 Parameters for DHCP Relay VLAN Interface Configuration ................... 3-97
Table 3-41 Parameters of DHCP Relay Option60.................................................... 3-97
Table 4-1 Ways to Open the ONU Configuration Window........................................ 4-2
Table 4-2 Ways to Open the Unauth ONU Config Window ...................................... 4-3
Table 4-3 Configuration of Basic and Extend Parameters.......................................... 4-4
Table 4-4 Parameters for ONU Topology Deployment Configuration ....................... 4-10
Table 4-5 Operations Related to a CLI User ............................................................ 4-16
Table 4-6 9806H Broadband Service Configuration Data ........................................ 4-20
Table 4-7 Parameters Description for Port VLAN Configuration............................... 4-21
Table 4-8 Parameters Description for DSL Ports Batch Configuration .................... 4-24
Table 4-9 9806H Multicast Service Configuration Data............................................ 4-24
Table 4-10 9806H VoIP Service Configuration Data ................................................ 4-30
Table 4-11 Operations Related to a CLI User .......................................................... 4-43
Table 4-12 F820 Broadband Service Configuration Data......................................... 4-45
Table 4-13 F820 Multicast Service Configuration Data ............................................ 4-47
Table 4-14 Multicast Configuration Parameters Description..................................... 4-49
Table 4-15 F820 VoIP Service Configuration Data................................................... 4-51
Table 4-16 VoIP Connect Configuration Parameters Description ............................. 4-54
Table 4-17 VoIP Domain Configuration Parameters Description .............................. 4-54
Table 4-18 Operations Related to a CLI User .......................................................... 4-63
Table 4-19 F820 Broadband Service Configuration Data......................................... 4-65
Table 4-20 Parameters Description for Port VLAN Configuration............................. 4-66
Table 4-21 Configuration Data of F822 Multicast Service ........................................ 4-69
Table 4-22 F820 VoIP Service Configuration Data................................................... 4-73
Table 5-1 ONU Basic Information Parameters Description ........................................ 5-3
Table 5-2 Configuration Data of F820 Broadband Service......................................... 5-5
Table 5-3 Configuration Data of F820 Multicast Service .......................................... 5-11
Table 5-4 Configuration Data of F820 VoIP Service................................................. 5-19
Table 5-5 ONU Basic Information Parameters Description ...................................... 5-30
Table 5-6 Configuration Data of F822 Broadband Service....................................... 5-32
Table 5-7 Configuration Data of F822 Multicast Service .......................................... 5-37
Table 5-8 Configuration Data of F822 VoIP Service................................................. 5-44
XIII
Tables
B
F
Backup and Delete Alarm Policy ......... 2-43
Backup and Delete Log Policy............ 2-43 F820 NE Creation (EPON) ................. 4-37
F820 NE Creation (GPON) ................... 5-5
C F820 Service Configuration
(EPON)............................................. 4-44
Configuring a CLI User ......................... 3-8
F820 Service Configuration
Configuring Policies............................ 2-38
(GPON) .............................................. 5-5
Configuring the Ethernet Port ............. 3-53
F822 NE Creation (EPON) ................. 4-57
Configuring the PCL ........................... 3-19
F822 NE Creation (GPON) ................. 5-32
Configuring the Port Status ................ 3-51
FTP Service ....................................... 2-16
Configuring the Port VLAN ................. 3-54
Configuring the System Name............ 3-10
Creating a Role .................................. 2-49 G
Creating an OLT NE ............................. 3-1 Global Parameter Configuration for
Customizing the Alarm Rules ............. 2-66 the F820 (EPON).............................. 4-38
Customizing the Current Alarm Query Global Parameter Configuration for
Profile............................................... 2-61 the F820 (GPON) ............................... 5-5
Customizing the Display Global Parameter Configuration for
Columns ........................................... 2-59 the F822 (EPON).............................. 4-58
Customizing the History Alarm Query Global Parameter Configuration for
Profile............................................... 2-63 the F822 (GPON) ............................. 5-32
Customizing the Polling Tasks ............ 2-54 Global Parameter Configuration for
the ZXDSL 9806H ............................ 4-10
D GPON ONU Type Profile .................... 3-41
Data Configuration Backup GPON VoIP Protocol Profile ............... 3-48
Policy ............................................... 2-45
XV
ZXA10 C220 Configuration Manual (NetNumen) Volume I
H S
History Traffic Monitoring Service Configuration of the F822
System ............................................. 2-28 (EPON)............................................. 4-65
Service Configuration of the F822
I (GPON) ............................................ 5-32
Service Configuration of the ZXDSL
Initializing the Database ..................... 2-23
9806H .............................................. 4-20
Installing the NetNumen N31
Setting the Alarm Sounds................... 2-73
NMS ................................................... 2-1
Shortcut ............................................. 2-22
Installing the NetNumen N31
Starting the Fault Management .......... 2-57
Patches .............................................. 2-7
Synchronize Configuration Data
Policy ............................................... 2-44
L
LACP Protection................................. 3-57 T
T-CONT Bandwidth Profile ................. 3-45
M TL1 Northbound Interface................... 2-36
Management ACL .............................. 3-16 Traffic Descriptor Profile ..................... 3-47
Managing the Cards ............................. 3-3
Managing the NE Version..................... 3-4 U
UAPS Protection ................................ 3-60
N
NE Module ..........................................2-11
NetNumen N31 Configuration
Center ................................................ 2-8
NetNumen N31 Green Client................ 2-5
NM Basic Information ........................... 2-9
NMS Database Backup Policy............ 2-45
O
ONU Authentication Mode.................. 3-62
P
Policy ................................................. 2-18
PON Network Topology
Management .................................... 2-47
PON Port Protection........................... 3-64
R
Redefining the Alarm Severities ......... 2-72
Running Configuration Save To Flash
Policy ............................................... 2-46
XVI
Glossary
ACL
- Access Control List
ADSL
- Asymmetric Digital Subscriber Line
ARP
- Address Resolution Protocol
CLI
- Command Line Interface
CVLAN
- Customer Virtual Local Area Network
CoS
- Class of Service
DBA
- Dynamic Bandwidth Allocation
DHCP
- Dynamic Host Configuration Protocol
DSCP
- Differentiated Services Code Point
DSLAM
- Digital Subscriber Line Access Multiplexer
EPON
- Ethernet Passive Optical Network
FTP
- File Transfer Protocol
FTTB
- Fiber to the Building
FTTH
- Fiber to the Home
GEM
- GPON Encapsulation Method
GPON
- Gigabit Passive Optical Network
GUI
- Graphical User Interface
XVII
ZXA10 C220 Configuration Manual (NetNumen) Volume I
ID
- Identification/Identity/Identifier
IGMP
- Internet Group Management Protocol
IP
- Internet Protocol
IPTV
- Internet Protocol Television
JDK
- Java Development Kit
LACP
- Link Aggregation Control Protocol
MAC
- Medium Access Control
MAN
- Metropolitan Area Network
MG
- Media Gateway
MGC
- Media Gateway Controller
MGCP
- Media Gateway Control Protocol
MVLAN
- Multicast Virtual Local Area Network
NAT
- Network Address Translation
NE
- Network Element
NM
- Network Management
NMS
- Network Management System
OAM
- Operation, Administration and Maintenance
OLT
- Optical Line Terminal
OMCI
- ONT Management Control Interface
XVIII
Glossary
ONU
- Optical Network Unit
OS
- Operating System
OSPF
- Open Shortest Path First
OSS
- Operation Support Subsystem
PIM
- PA Interface Module
PON
- Passive Optical Network
PVID
- Port VLAN ID
SIP
- Session Initiation Protocol
SN
- Serial Number
SNMP
- Simple Network Management Protocol
SS
- Soft Switch
TCP
- Transfer Control Protocol
TOS
- Termination Of Service
TPID
- Tag Protocol Identifier
UAPS
- Uplink Auto Protection Switching
UDP
- User Datagram Protocol
UEP
- Unified Element management system Platform
VID
- VLAN Identifier
VLAN
- Virtual Local Area Network
XIX
ZXA10 C220 Configuration Manual (NetNumen) Volume I
VRRP
- Virtual Router Redundancy Protocol
VoIP
- Voice over Internet Protocol
XX