NetNumen N31 UNMS (V5.01.01) User Manual Resource Config

NetNumen U31 (IP Network)
Unified Network Management System

User Manual (Resource Configuration Management)
Version 12.10.30
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 © 2010 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 CORPO-
RATION 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 dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. 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
Revision No. Revision Date Revision Reason

R1.0 2010–08–18 First edition
Serial Number: SJ-20100913154504-003

Contents
About This Manual............................................. I

Resource Configuration Frame ..........................1
Resource Configuration Frame Overview ............................ 1
Basic Operation of Main Interface ..................................... 2
Network Resource .............................................9
NE Information............................................................... 9
Configuring NE Basic Information.................................. 9
Configuring NE Expansion Information..........................12
Management Information ...........................................13
Interface Management ...................................................14
Configuring Interface Basic Information ........................14
Configuring an Ethernet Physical Interface ....................15
Configuring Uni Interface Management .........................15
Configuring Cip Interface Management .........................16
Configuring Interface Laser Information........................18
Configuring ATM Interface Information .........................19
Configuring E1/CE1 Interface ......................................20
Configuring IMA Group ...............................................22
Configuring Interface User Information .........................24
Protect Group Configuration Management .....................25
NE Time Management ....................................................27
NE Time Management ................................................27
NTP Server Management ............................................28
NTP Synchronization Mode Management .......................29
Configuring PTP Port Information .................................29
Configuring PTP Global Information ..............................31
Configuring GPS Port .................................................33
Configuring SSM Clock Synchronization ........................35
Configuring SSM Clock Source .....................................36
Configuring External Clock Port ...................................38
Configuring Edge Link Management..............................39
Confidential and Proprietary Information of ZTE CORPORATION I

NetNumen U31 (IP Network) User Manual (Resource Configuration Management)
Link Resource Configuration ............................................39

Layer 2 Management ....................................... 43
Link Aggregation Management ........................................43
LLDP Management .........................................................45
NE Information..........................................................46
Port Information ........................................................46
Configuring Port Mirroring...............................................47
VLAN Management ........................................................48
Configuring a VLAN Port .............................................48
Configuring a VLAN....................................................49
Configuring VLAN Translation ......................................52
Configuring a Selective VLAN ......................................53
Managing a VLAN Domain ...........................................54
Managing Port-Based VLAN Service ..............................55
MAC Address Resource Management ................................58
MAC Address Table Configuration .................................58
Port MAC Address Configuration...................................60
Layer 3 Management ....................................... 63
Route Management........................................................63
Route Topology Analysis .............................................63
Static Route..............................................................64
Routing Protocol ............................................................68
RIP Protocol Management ...........................................68
OSPF Protocol View....................................................68
IS-IS Protocol View....................................................69
BGP Protocol Management ..........................................71
ARP Management .........................................................72
Configuring ARP Global Information .............................73
Configuring ARP Table ................................................74
Service Management ....................................... 75
Traffic Engineering Basic Configuration Management...........75
TE Global Configuration Management ...........................75
TE Interface Management ...........................................77
IGP Configuration Management ...................................78
MPLS LSP Management ..................................................80
Explicit Path Management ...........................................80
Tunnel Management...................................................81
MPLS LSP Path Management .......................................83
Tunnel Protection Management ....................................84
II Confidential and Proprietary Information of ZTE CORPORATION

Security Management...................................... 87
Time Range Management ...............................................87
Time Range Template Management ..............................87
Switch Time Range Management .................................90
ACL Management ..........................................................93
User And Account ..........................................................97
Operation and Maintenance............................. 99
Virtual Circuit Test .........................................................99
Loop Test ................................................................... 100
Configuring time parameters ..................................... 100
Configuring Loop Port............................................... 101
CFM Configuration ....................................................... 101
Enabling Global CFM ................................................ 102
Domain Resource Configuration ................................. 102
Configuring an MD .......................................... 102
Configuring an MA........................................... 103
Configuring an MEP ......................................... 104
Configuring an RMEP ....................................... 107
Configuring an MIP.......................................... 108
LBM Management .................................................... 109
LTM Management .................................................... 110
Ethernet OAM ............................................................. 110
Device Global Configuration ...................................... 110
Device Port Configuration ......................................... 111
Remote Loopback .................................................... 111
Link Monitoring ....................................................... 112
MPLS OAM TRACE........................................................ 112
Configuring MAC TRACE............................................ 113
Configuring MPLS TRACE .......................................... 114
Performance Monitor .................................................... 115
Task Matrix ............................................................. 115
Task Parameters ...................................................... 119
Result Matrix........................................................... 120
Result List .............................................................. 120
Result Graphic......................................................... 120
Result Deletion Policy ............................................... 121
BFD ........................................................................... 121
BFD Global Configuration .......................................... 122
BFD Session ........................................................... 122
BFD Performance..................................................... 124
Confidential and Proprietary Information of ZTE CORPORATION III

Zero-Touch Deployment ............................................... 124

Configuration Template Managemet ............................... 129
Configuration Template Overview............................... 129
Sort Operations ....................................................... 129
Creating a New Template .......................................... 130
Template Management ............................................. 131
Configuration Instance Management .......................... 132
Deploying a Configuration Instance ............................ 133
Zero-Touch Deployment Template .............................. 133
File Management ......................................................... 134
File Management Overview ....................................... 134
Version File Management .......................................... 135
Operations in NE Area...................................... 135
Backing up Version File .................................... 135
Restoring Version File ...................................... 136
Rebooting NE ................................................. 137
Configuring Global Option of Version File
Management ....................................... 138
Getting the Related Information of NE................ 140
Managing Files on an NE .................................. 141
Uploading Version File...................................... 142
Downloading Version File to Client ..................... 142
Deleting a File ................................................ 143
Querying NE According to Version Number ......... 143
Managing Version File Status ............................ 143
Downloading Detailed NE Version
Information......................................... 144
Viewing Detailed NE Version File Informa-
tion .................................................... 144
Modifying a Task ............................................. 144
Task Operation ............................................... 144
Configuration File Management.................................. 145
Backing up Configuration File............................ 145
Exporting Lasted Configuration File.................... 145
Rolling Back Configuration File .......................... 145
Designating a Benchmark File ........................... 146
Comparing Configuration File ............................ 147
Editing Configuration File ................................. 148
Patch File Management............................................. 148
Restoring Patch File ......................................... 148
IV Confidential and Proprietary Information of ZTE CORPORATION

Managing NE .................................................. 149
Performance And Alarm ................................ 151
Querying Performance.................................................. 151
Performance Report List ............................................... 152
Performance Real Query ........................................... 152
Report File Management ........................................... 154
Alarm Management...................................................... 154
Figures .......................................................... 155
Tables ........................................................... 159
Glossary ........................................................ 161
Confidential and Proprietary Information of ZTE CORPORATION V

This page is intentionally blank.
VI Confidential and Proprietary Information of ZTE CORPORATION

About This Manual
Purpose At first, thank you for choosing NetNumen U31 Unified Manage-
ment System of ZTE Corporation!
NetNumen U31 Unified Management System is the intermediate
system between lower level NE and upper layer operation. It
mainly realizes the centralized topology management, centralized
alarm management, centralized performance management and
centralized report management of lower level NE.
This manual provides procedures and guidelines that support the
operation of NetNumen U31 (IP Network) Unified Management
System.
Intended This manual is intended for the following engineers:
Audience
� On-site maintenance engineers
� Network monitoring engineers
� System maintenance engineers
Prerequisite Skill To use this manual effectively, users should have a general un-
and Knowledge derstanding of IP communications technology. Familiarity with the
following is helpful:
� ZXR10 devices
� UMS working principle
What Is in This This manual contains the following chapters:
Manual
Chapter Summary
Chapter 1 Resource Configuration Describes resource configuration

Frame frame and structure.
Chapter 2 Network Resource Describes network resource

management including NE,
interface and so on.
Chapter 3 Layer 2 Management Describes layer 2 management

including aggregation link
management, LLDP management.
Chapter 4 Layer 3 Management Describes layer 3 management

including route management.
Chapter 5 Service Management Describes layer 3 management

including network TE attribute,
tunnel management and so on.
Chapter 6 Security Management Describes security management

including time range
management.
Confidential and Proprietary Information of ZTE CORPORATION I

Chapter Summary
Chapter 7 Operation and Describes operation and

Maintenance maintenance including virtual
line detection and configuration
template.
Chapter 8 Performance and Alarm Describes performance

management including real
time search and performance
report management.
Conventions ZTE documents employ the following typographical conventions.
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
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.
Note: Provides additional information about a certain

topic.
Checkpoint: Indicates that a particular step needs to

be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things

easier or more productive for the reader.
Mouse operation conventions are listed as follows:
Typeface Meaning
Click Refers to clicking the primary mouse button (usually the

left mouse button) once.
Double- Refers to quickly clicking the primary mouse button

click (usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button (usually

the right mouse button) once.
II Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1
Resource Configuration
Frame
Table of Contents
Resource Configuration Frame Overview ................................ 1
Basic Operation of Main Interface ......................................... 2
Resource Configuration
Frame Overview
Resource configuration module becomes more and more important
in the network management. It not only can be used for network
plan but also has the instruction function on the following network
maintenance. Also it can implement the centralized management
of NE and real time statistics.
Resource configuration frame can implement the following func-
tions:
� Network resource management
NE information management is one of the most important
functions in network management system. It mainly includes
querying NE basic information, expansion information and
management information and adding topology management.
� Layer 2 management
It is applied to management function of data link layer in stan-
dard network protocol including link management, medium
visit and so on.
� Layer 3 management
It is applied to management function of network layer in stan-
dard network protocol including addressing and route selec-
tion.
� Service management
Traditional routing protocol calculates the shortest path for-
warding traffic. Even if some path is blocked, traffic would
not be switched to other paths. When network traffic is small,
this problem is not serious. But the application of network be-
comes more and more widely, traditional shortest path priority
has many problems. In service management, carrier can pre-
Confidential and Proprietary Information of ZTE CORPORATION 1

cisely control the path where traffic is transmitted by traffic

engineering and avoid blocked node to utilize bandwidth re-
source mostly.
� Security management
Security management includes time range management and
user authority management.
� Operation and maintenance
Operation and maintenance include virtual cable detection,
loop detection and end-to-end function.
� File management
File management provides bulk NE version file upgrading and
configuration file backup.
� Performance management
Performance management module only provides real time
query and performance report query in resource configuration
frame. Please refer to NetNumen Unified Network Manage-
ment System Data Product User Manual (Performance and
Alarm) for detailed information.
Basic Operation of Main

Interface
Users can customize according to their demands by knowing re-
source configuration frame.
In network management main interface, select Configuration >
IP Ne Resource Configuration, the Resource Configuration
Management main interface, as shown in Figure 1.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Resource Configuration Frame
FIGURE 1 RESOURCE MANAGEMENT CONFIGURATION TOPOLOGY TREE
Type Selection Click the drop-down menu of device type, all added NE device
Tree types is displayed. In type selection tree, multiple device types
can be selected. When selection is completed, click any location
out of drop-down menu, the drop-down menu is concealed. At this
time, NE and resource configuration tree will be filtered according
to selected device type.
The rule of filter is as follows:
1. NE selection tree: It displays all NEs which have selected de-
vice type, other types of NEs will be concealed.
2. Resource configuration tree: It displays the resource node that
supports selected device type, that is, only the nodes on re-
source configuration tree support all selected device types, can
the source node be displayed. Otherwise it is not displayed.
NE Selection Tree In NE selection tree, select NE so that the related resource can be
queried in resource view area. Users can operate on packet node
and create new packets, modify packets and delete packets.
Resource Resource configuration tree is also named as “resource function
Configuration Tree tree”. Because all resource-related functions are loaded on this
tree, that is, click different resource configuration tree nodes, the
corresponding resource view area will be opened on the right view.
If select NE Information, the NE basic information page will be
opened on the right.
To make users more conveniently operate, some tool buttons such
as expand, collapse, search, filter, customization view can be dis-
played above resource configuration tree, as shown in Figure 2.

FIGURE 2 RESOURCE CONFIGURATION TREE TOOLBAR BUTTON
The functions of resource tree tool buttons are as follows:
� Expand : Expand whole resource configuration tree.
� Collapse : Collapse whole resource configuration tree.

� Filter: Users input the node name, resource configuration tree
will filter according to input condition. Only the nodes meeting
conditions can be displayed.
� Search : It is different from filter. Search is to identify the

node meeting conditions by red font. It does not hide other
nodes.
� View selection: This function is used by the combination with
view customized function. Only the view is customized, can
selection be implemented.
� View customization: click customization button , pop up

view customization dialog box. Users can customize the node
requiring to be displayed (it is related to the selection type
in device type tree. Although some mode appears in current
view, the devices that does not support selection will not be
displayed).
View customization has three functions:
i. Customize view: create one view, and configure the re-
source node on this view.
Select the node in the left resource configuration tree and
configure New View Name, click Create, the view name
will appear in the right list. Click OK to save. When creation
is successful, the view that is currently customized will be
displayed in the view selection frame.
ii. Service function check: check the service that resource
configuration management supports (the displayed service
in resource configuration tree is related to selected device
type. Therefore, generally all service cannot be displayed
completely).
The left tree in view customization window is services that
all resource frame supports. Users can expand to check
detailed service type.
iii. Check device type that resource node supports: When
users require to operate some services, the device type
that this service supports can be checked in resource
configuration tree.
Click the support device drop-down box after service node,
check the device that service node supports, as shown in
Figure 3.

FIGURE 3 USER VIEW CUSTOMIZATION
Resource View Resource view area is the operation area that users create, modify
Area and configure related services. It corresponds to selected resource
node one-by-one.
The following introduces the common concepts in resource view
area:
� “export” button
The main function is to export the data in the list. In drop-
down menu, the displayed data or all data can be exported.
Generally, use Excel format to export list data.
� “import” button
The main function is to import the data. Generally, use Excel
format to import data. The format of importing table must
meet the specification. The detailed chapter will introduce the
format of importing table.
� “refresh” button
load resource from database again and the resource is dis-
played in service table (generally, the search condition can be
configured) .
� “create” button
Create the resource instance related to this service, such as
create NE.
� “delete” button

Delete the resource instance that has existed in network man-

agement or table.
� “save” button
Save some resource instances after modification to database.
� “upload” button
Upload means backing up data on device to network manage-
ment server. After uploading, the data status becomes “syn-
chronized”. The operation of uploading includes three policies:
i. add: add the data that does not exist on network manage-
ment server but on devices. If this policy is not selected,
even if some data exists on the device, after uploading,
these data will not exist on the server.
ii. remove: delete the data that does not exist on devices
but on network management server. If this policy is not
selected, when some data that does not exist on the device
but on server are uploaded, these data will not be deleted
on the server.
iii. modify: when the data of network management server is
different from that of devices, modify the data of server. If
this policy is not selected, when the data of network man-
agement server is different from that of devices, the data
of server will not be modified.
� “deploy” button
Generally, the data of network management server has two
sources. One is established in network management client
end, another is backed up from network management device.
Deployment means recovering the data of network manage-
ment or configuring the data on the device. The operation of
deployment only can be implemented on the “saved” data. Af-
ter deployment, the state of resource on network management
server is “synchronized”.
i. add: configure the data of network management server on
the device. If this policy is not selected, even if some data
exists on the server, when deployment is implemented,
these data will not be configured on the device.
ii. remove: remove the data that does not exist on network
management server but on the device. If this policy is
not selected, even if some data that does not exist on the
device but on server is deployed, these data will not be
deleted on the device.
iii. modify: when the data of network management server is
different from that of devices, modify the data of server. If
this policy is not selected, even if the data of network man-
agement server is different from that of devices, when they
are deployed, the data on the device will not be modified.
At the same time, the deployment includes three types of re-
source audit policies:
i. Audit before deployment: compare the difference between
the data on the sever and that on the device before the data
on network management server is deployed on the device.

ii. Audit after deployment: compare the difference between

the data on the device and that before deployment after
the data on network management server is configured on
the device.
iii. Alarm generation: when audit before deployment or audit
after deployment or both are selected, if the audit result
has the difference, alarm will generate on the server.
� “audit” button
The procedure of comparing the data on the device and the cor-
responding data on the network management sever is named
as audit. After audit, if the data on both sides is same, the
data state on network management server is “synchronized”.
If the data on both sides is not same, there are two kinds of
operation policies, one is to deploy after audit, that is, deploy
the different data to the network management server. Another
is to upload after audit, that is, back up the different data to
network management server.
There are two actions after audit:
i. upload: after audit, when the data on the device is different
from that on the network management server, implement
upload operation.
ii. deploy: after audit, when the data on the device is different
from that on the network management server, implement
deployment operation.
� “remove” button
The data on the device and the corresponding data on net-
work management library are deleted. If users open the client
end, the state of corresponding data will be changed to “un-
synchronized” before “refresh” is not implemented. “save” can
be implemented to save the data on the page to network man-
agement library. If “refresh” is implemented, the data which
is removed will disappear.


Chapter 2
Network Resource
Table of Contents
NE Information .................................................................. 9
Interface Management .......................................................14
NE Time Management ........................................................27
Link Resource Configuration ................................................39
NE Information
NE information management is one of the most important func-
tions in network management system. It includes the following
functions:
� Basic information
It mainly includes addition, modification, deletion, deployment
and uploading function of NE. The detailed NE version, de-
tailed description and establishing time can be queried by list
method.
� Expansion information
NE includes some expansion information including supplier, de-
livery time, batch No., serial number.
� Management information
The mode of implementing management NE information in-
cludes SNMP-related parameter configuration and CLI com-
mand line interface configuration.
Configuring NE Basic Information

NE basic information management has the following operations:
� NE establishment
� NE import and export
� NE information query
� NE modification and deletion
� Audit and deployment

Premise � Network management system is normally enabled and re-

source configuration management has been opened.
� Network management server has connected with NE device.
Create NE 1. Click Network Resource > NE Information > NE Basic In-
formation on the resource configuration management topol-
ogy tree. Basic information is displayed, as shown inFigure 4.
FIGURE 4 NE INFOMATION
2. Point to a button on the tool bar, the description of the button

will be displayed. The functions of the buttons are described
below.
3. Export the data in the table to an Excel file.
i. Click on the tool bar. A dialog box appears.
ii. Set the storage path and file name and then click Save.
The NE information is saved in an Excel file.
NE Import And Generally, adding NE in batch is imported by Excel format, but this
Export requires the NE information has history backup.
1. Import the data in an Excel file to the list of NE basic informa-
tion.
ii. Select the Excel file to be imported and then click Import.
2. Click on the tool bar to obtain the latest NE basic information.
3. Print the basic information. Users can print the data displayed
in the table or print all data.

Chapter 2 Network Resource
i. Click or on the tool bar. A dialog box appears.

ii. Set the print range and copies on the General tab.
iii. Set the paper size, print direction and margin on the Page
Setup tab.
iv. Set the print style on the Advance tab.
v. Click Preview All to preview the print result and click Print
to print the basic information.
Search NE 1. Tick the Number check box of an NE and then click buttonon
Infomation the tool bar. A dialog box appears. Tick Advanced Options,
the detailed basic information will be displayed.
2. Select filter conditions in the filter list boxes and input the filter
contents. The filter conditions include group, display name,
Internet Protocol (IP) address, subnet mask, Medium Access
Control (MAC) address, NE type and version.
3. Search information according to demands.
i. Click Advanced button on the tool bar.
ii. Select search conditions in the pull-down list boxes and
then click on the tool bar. The search result will be dis-
played.
iii. Click on the tool bar to delete the search result.
iv. Click on the tool bar. A dialog box appears. Input Name
and then click Save or Save and Search. When users
search information next time, they can select the search
condition in the pull-down list.
v. Click on the tool bar. The Customize Search Condition
dialog box appears. The conditions in blue background may
be displayed in the first row of the interface and others
are hidden. Users can set the conditions according to their
habits. Click OK to complete the setting.
vi. Click Hide to hide some search conditions.
Modify And Delete 1. Click on the tool bar. Users can create an NE.
NE
2. Modify an NE
i. Tack the Number check box of an NE and then click on
the tool bar. Users can modify the NE.
ii. The information in black can be modified in the list directly.
Users can double-click Display Name, IP Address, Ver-
sion and System Name to set the information again.
iii. Users also can modify the parameters in batch. For the
detailed information, please refer to NE Information.
3. Tick the Number check boxes of several NEs and then click
on the tool bar. A dialog box for confirmation appears. Click
OK to delete the NEs.
4. The background of modified information is in pink. The Status
is “Not Saved”. Click on the tool bar to save the data. The
background of the information becomes normal. The Status
becomes “Saved”.
Audit And Deploy 1. Upload information. Users can synchronize one or several
NE pieces of basic information on NEs with that in the UMS.

i. Tick the Number check boxes of several NEs and then click
on the tool bar. A dialog box appears.
ii. Select the NEs in the Instance List. By default, only Mod-
ify Operation is ticked in Operation Policy area. Click
Execute. The result is displayed.
iii. The link aggregation port information on the NE and that in
the UMS has been synchronized. The Status on NE Basic
Information tab page is “Synchronized”.
If a piece of basic information does not exist on the NE,
the information does not change after upload. If some
attributes of the basic formation in the UMS and the NE
are different, The information in the UMS will be synchro-
nized. If the information is completely the same, there is
no change.
2. Audit the basic information on an NE and that in the UMS.
ii. Users can operate on the information on the Audit dia-
log box. Select “Upload” or “Deploy” in the Select Action
pull-down list box and then click Execute. The result is
displayed in the Audit Result area. The differences are in
red. Click Close.
3. Deploy the information in the UMS to NEs.
ii. Select an instance in the Instance List area, select Add
Option or Modify Option in Operation Policy area and
then click Execute. The result is displayed in the Deploy
List.
4. Create a poll task
ii. Select NEs and then click Modify. A dialog box appears.
Users can set the interval (in the range of 15~2147483647)
and the task state. Click OK.
Configuring NE Expansion
Information
This topic describes how to view and configure the expansion in-
formation of NEs managed by UMS.
Prerequisite � Network management system is normally enabled and re-
1. Click Network Resource > NE Information > NE Expan-
sion Information on the resource configuration management
topology tree. Expansion information is displayed.

2. users can double-click the information in black (such as Ven-

dor, Vendor Info, and so on) and modify the information in
the list directly.
Management Information
SNMP parameters and CLI parameters can be configured in man-
agement information.
Prerequisite � Network management system is normally enabled and re-
Configuring SNMP Users can configure parameters of Simple Network Management
Protocol (SNMP) on NEs to make network management easier.
1. Click Network Resource > NE Information > NE Manage-
ment Information > SNMP on the resource configuration
management topology tree. SNMP information is displayed.
will be displayed. For the detailed information about the button
functions, please refer to Configuring NE Basic Information.
3. Dismount and delete SNMP information on an NE. Before dis-
mounting, the information on the NE should be synchronized
with that in the database.
i. Tick the Number check box of one or several NEs and then
click on the tool bar. A window appears.
ii. Select a node in the Instance List, the detailed commands
of the NE is displayed in the Deploy List. Click Execute.
The state will be displayed in Whether Successful col-
umn.
4. Tick the Number check box of one or several NEs and then
button. An interface for manual testing appears. Wait a
moment and the testing result will be displayed.
Configuring CLI Users can configure parameters of Command Line Interface (CLI)
to make network management easier.
1. Click Network Resource > NE Information > NE Manage-
ment Information > CLI on the resource configuration man-
agement topology tree. SNMP information is displayed.
will be displayed. For the detailed information about the button
functions, please refer to Configuring NE Basic Information.
3. Tick the Number check box of one or several NEs and then
button. An interface for manual testing appears. Wait a
moment and the testing result will be displayed.

Interface Management
NE interface management provides rich functions of physical in-
terfaces and logical interfaces, including displaying, querying, sta-
tistics, navigation of function configuration, and so on.
Configuring Interface Basic

Information
Interface information can be obtained from devices or by manual.
Generally, uploading in batch is applied to get interface informa-
tion.
� NE has been created in NE information.
Creating Manually 1. Click Network Resource > Inface Information > Inf Ba-
Interface sic Information on the resource configuration management
Information topology tree. Interface basic information is displayed. Only
the network management system in enabled state can man-
agement the port.
2. Create an interface
The parameters on the dialog box is described in Table 1.
TABLE 1 CREATING PORT INFORMATION
Parameter Description
NE It is to select an NE on which the interface will be created from the pull-down

list box.
Mode It is the interface mode. After the NE is selected, the Mode is set as Ethernet
physical interface automatically.
Type It is the interface type. The interface type depends on the selected mode.
Slot No. Slot number of device
Port No. It is the interface number, such as 1-5, 7, 9, 10-15.
Sub Slot No. Sub slot number, the range is 1 ~ 65535
Channel No. The created channel number, such as 1 ~ 5, 7 and 9, 10 ~ 15.
ii. Input the interface information and then click OK.

Uploading Upload interface information to the UMS.

Interface
Information in 1. Click on the tool bar. A dialog box appears.
Batch
2. Select one or several NEs and then click OK. A dialog box ap-
pears.
3. The NEs to be uploaded are listed in the Instance List. Select
needed operations in Operation Policy and then click Exe-
cute.
Configuring an Ethernet Physical

Interface
1. Click Network Resource > Inface Information > Inf Eth-
ernet Physical Information on the resource configuration
management topology tree. Ethernet physical interface infor-
mation is displayed.
2. The information in black can be modified on the tab page di-
rectly. For example, double-click Work Mode to modify the
work mode.
3. Click on the tool bar. A dialog box appears, prompting
that statistics is enabled. The number of sub-interfaces is dis-
played. Currently, high-end and middle-end switch and router
support this function.
Configuring Uni Interface

Management
Abstract UNI (User-Network Interface) is user network interface in ATM net-
work. It is the interface between user device and network and di-
rectly faces users. UNI interface defines the interface standard of
physical transmission line, ATM layer standard, UNI signal, OAM
function and management function. According to UNI interface lo-
cation difference, it includes UNI of public network and UNI (PUNI)
of private network. PUNI interface has more formats and more
flexible.
Uni interface management mainly supports ZXCTN 6000 series and
ZXCME 9501R.

Steps 1. Select Network Resource > Interface Information > Uni

Interface Management on the resource configuration man-
agement topology tree. Uni interface status, Device Display
Name, Uni ID, Bind interface and Interface Description can be
viewed in the interface.
2. From left to right, the buttons shown on tool bar are export
data shown on table, create and modify, save and delete, up-
load and upload from NE, deploy and audit and so on. Point
to a button on the tool bar, the description of the button will
be displayed. The following content describes the newly-added
functions.
3. Create Uni Interface.
i. Click to enter Create Uni Interface interface, as

shown in Figure 5.
FIGURE 5 CREATE UNI INTERFACE
ii. Select device and input interface description, click OK to

finish the creation.
4. Upload Uni interface information from NE.
i. Click button to enter Device Selection interface.

ii. After NE is selected, click OK to enter Upload Configu-
ration From Devices interface. Click Execute button to
view Uni-related information in the list.
END OF STEPS
Configuring Cip Interface

Management
Abstract CIP interface management supports all IP transmission platform
products including ZXCTN 6000 series, ZXCTN 9000 series and
ZXCME 9500 series.
premise � Network management system is normally enabled and re-


Steps 1. Select Network Resource > Interface Information > Cip
Interface Management on the resource configuration man-
agement topology tree. Cip interface status, NE name, In-
terface ID, Bind interface ID and name can be viewed in the
interface.
data shown on table, create and modify, save and delete, up-
load and upload from NE, deploy and audit and so on. Point
to a button on the tool bar, the description of the button will
be displayed. The following content describes the newly-added
functions.
3. Click to enter Cip interface create interface, as shown in

Figure 6. After the corresponding information is selected, click
OK to complete the creation.
FIGURE 6 CIP INTERFACE MANAGEMENT CREATION
4. Upload Cip interface information from NE.
i. Click button to enter Device Selection interface.

ii. After NE is selected, click OK to enter Upload Configu-

ration From Devices interface. Click Execute button to
view Cip-related information in the list.
END OF STEPS
Configuring Interface Laser

Information
Network management supports to manage the properties of opti-
cal physical interface. Currently, only ZXCTN 6000 packet trans-
mission product supports this function.
1. To view the information of optical interface, click Network Re-
source > Inf Information > Inf Laser Information on the
resource configuration management topology tree, as shown
in Figure 7. The information includes NE name, NE type and
Name, Type and Laser Status, Laser Offtime and Als Pe-
riod (s), Als Pulse Width (s) and Als Test Pulse Width
(s), Data synchronization Time.
FIGURE 7 INTERFACE LASER INFORMATION INTERFACE
data shown on table, refresh and create, save and upload, up-
load from NE and deploy, audit and so on. Point to a button
on the tool bar, the description of the button will be displayed.
The following content describes the newly-added functions.

3. Click to display the latest interface user information at Inf

User Information interface.
4. The black items can be modified. For example, double-click
Laser Status and modify it directly.
5. The background of modified items is in light red color. Click
to save the data. After that, the background of modified
items turns to normal color like other items.
6. To view the detailed user information of current interface,
right-click the item, and select Detail from the pop-up menu,
the Detail interface appears. Click Previous or Next to view
the detailed user information of the previous or next interface.
Click OK to exit the interface.
Configuring ATM Interface

Information
Abstract ATM (Asynchronous Transfer Mode) is a kind of packet switching
and multiplexing technology based on cell. It is a connection-ori-
ented transmission mode designed for multi-service design. it is
applied to local area network and wide area network and has high
speed data transmission rate and supports many types of commu-
nications such as voice, data, fax, real time video, audio with CD
quality and picture.
At present, ATM interface information management mainly sup-
ports IP transmission platform product.
Steps 1. In resource configuration management topology tree, select
Network Resource > Interface Information > ATM In-
terface Information Management, check ATM interface in-
formation of devices including NE type, ATM virtual interface
name, ATM virtual interface description and binding type.
2. Click the button on the toolbar, popup the ATM Interface

Management interface, as shown in Figure 8.

FIGURE 8 CREATING ATM INTERFACE
3. Select NE, ATM virtual interface instance ID is 1 by default,

in range of 1~1024. Configure remark, binding interface type
and binding interface, and then click OK.
4. In interface management list, select one ATM interface, click
the button on the toolbar, pop up atm interface manage-
ment. Grey means it cannot be modified. After modification
is completed, click OK to complete the configuration.
END OF STEPS
Configuring E1/CE1 Interface

Abstract E1 and CE1 are E1 line standard. The difference between E1 and
CE1 is whether time slot can be divided. 0 and 16 time slot of CE1
cannot be used. 0 transmits synchronization number, 16 transmits
control command. In fact, only 30 time slots can be used.
E1/CE1 port management only supports IP transmission platform
product.
Steps 1. In resource configuration management topology tree, select
Network Resource > Interface Information > E1/CE1
Port management, check device E1/CE1 port information in-
cluding NE type, interface name, interface description and port
rate.

2. Click , the Create guide choose interface appears, as

shown in Figure 9.
FIGURE 9 CREATE GUIDE CHOOSE
3. Select Create E1 interface, and then click next, the Batch

Create E1 Ports interface appears, as shown in Figure 10.
FIGURE 10 BATCH CREATE E1 PORTS INTERFACE
4. Select Insert NE without online, TSB port type which abet

e1 port and Rebate No on the Batch Create E1 Ports inter-
face, and then click Confirm. E1 interfaces can be created in
batch on all ports of the slot.
5. Select an E1 interface from E1 interface management list, and
the click , the E1 Port Properties Change interface ap-
pears, as shown in Figure 11. The greyout items can not be
modified. Click Confirm to finish modification.

FIGURE 11 E1 PORT PROPERTIES CHANGE
The properties of E1 physical interface are listed in Table 2.
TABLE 2 PROPERTIES DESCRIPTION OF E1 PHYSICAL INTERFACE
Property Description
E1_Send Clock There are four options, no

clock, auto and system,
loopback.
E1_LoopBackType There are three options, no set

loopback, internal and line.
E1_Receive Clock There are three options, no

clock, customer and system.
E1_Frame Type There are five options,

UNFRAME, PCM30 and
PCM30CRC, PCM31 and
PCM31CRC.
Configuring IMA Group

Abstract Network designer and manager can use IMA (Inverse Multiplexing
for ATM) to realize ATM access by multiple T1 and E1 connection

according to real requirement instead of using expensive T3 or E3

lines.
IMA group management only supports IP transmission platform
product.
Steps
1. Click , the Create guide choose interface appears, and
then select Create IMA Interface, click Next, the IMA In-
terface Manage interface appears, as shown in Figure 12.
FIGURE 12 IMA INTERFACE MANAGE
2. Select NE, Spanners abet E1 and Rebate No. Select to ports

to be bound in IMA Group Property. Only the E1 ports be-
longing to the same board can be bound. Click Check is true,
a prompt appears to indicate whether the configuration is cor-
rect. Click Confirm to create IMA interface in batch, as shown
in Table 3.

TABLE 3 PROPERTIES DESCRIPTION OF IMA INTERFACE
Group ID OMA group ID, 1 ~ 4096
IMA_FrameLen 32, 64 and 128, 256
IMA_Groupmode config, work and both
IMA_Active Min Links 1 ~ 16
IMA_ReferenceLink E1 interface created on the slot
IMA Alpha 1 ~ 2
IMA Differencedelay 25 ~ 100
IMA_Beta 1 ~ 5
IMA_Gamma 1 ~ 5
Remark Remark, optional parameter
3. Select an IMA interface from IMA interface management list,

click . The IMA Interface Manage interface appears. The
greyout items can not be modified. Click Confirm to finish.
Configuring Interface User

Information
Use information can be configured on low-end switch only, includ-
ing modification and saving.
1. Click Network Resource > Inface Information > Inf User
Information on the resource configuration management
topology tree. User interface information is displayed.
will be displayed. The functions of new buttons are described
below. For the detailed information of other buttons, please
refer to corresponding contents mentioned before.
3. Click on the tool bar to get the latest user interface infor-
mation.
4. The information in black can be modified on the tab page di-
rectly. For example, double-click User Account, User Name,
User Address and Phone Number to modify the information.
5. The background of the cell in which the information is modified
is in pink. Click on the tool bar, the data is saved. The
background color becomes normal.
6. Right-click any lien in the list and select Details from the short-
cut menu. The detailed information of the current interface is

displayed. Click Previous or Next to view the detailed infor-

mation of the previous or next user interface. Click OK to exit
from the dialog box.
Protect Group Configuration

Management
Context This function supports 9000 series of V4.8.31 or later versions.
Prerequisites � Network management system is normally enabled and re-
Steps 1. Select Network Resource > Interface Information > Pro-
tection Group Configuration Management > Port Protec-
tion Configuration on the resource configuration manage-
ment topology tree to enter Port Protect Config interface.
2. Click button to enter Create Port Protect Config inter-

face, as shown in Figure 13. Select the basic information such
as NE. Note that master port should be different from slave
port, otherwise configuration information cannot be created.
If master port is down, slave port will take effect. When con-
figuration is created, Lookout Protect Tunnel is not ticked.
After configuration is completed, click OK to finish the creation.
Note:
� When configuration is created, master port and slave port
cannot be same, but VLAN numbers can be same.
� One port can appear in the different protect groups.

FIGURE 13 CREATE PORT PROTECT CONFIG
3. Uploading from NE also can automatically search the port pro-

tect configuration which has existed.
i. Click button, in Device Selection interface, select NE

or NE group which needs to search.
ii. After selection, click OK button to enter Upload Configu-
ration From Devices interface. Select Execute to search
and upload protect port configuration information.
4. After the creation is completed, port protect information can be
viewed in the list. Also Ne type, IP address, port protect group
number, master port information, slave port information, port
protect mode and switch policy can be viewed.
5. Select port protect configuration information in the list, click
button or double-click cell edit list information in the list to
modify port protect configuration status information.

6. In the list, select port protect configuration information, click

button to refresh port protect configuration information.
7. Click , select switch policy in the drop-down menu in-

cluding forced master/slave switchover, manual master/slave
switchover, clear, lock and so on. The priority from high to
low is clear>lp>fs>ms. If the current protect group status
is “lock”, clear first and then forced master/slave switchover,
manual master/slave switchover can be implemented. After
switchover policy is implemented, the recorded policy list will
modify refreshment automatically.
END OF STEPS
NE Time Management
At present, NE time management function only supports IP trans-
mission platform product.
clock time management function includes:
NTP time management
� NE time management
� NTP server management
� NTP synchronization mode
1588 configuration
� PTP global configuration management
� PTP port configuration management
clock source management
� absolute time port configuration
� SSM clock synchronization configuration
� SSM clock source configuration
� External clock source port management
� Synchronization network border management
NE Time Management
Users can search and set the time zone and time information of
NEs manually through NE time configuration. Users also can com-
pare the time zone and time on NEs with that in UMS server.
1. Click Network Resource > Clock Management > NTP Time
Management > Network Element Time Management on
the resource configuration management topology tree to set
the NE time and time zone.
2. Click the pull-down arrow on the tool bar to select NEs.

3. Click on the tool bar to obtain the NE time and time zone.
4. Select a piece of NE time management information and then
click on the tool bar. A dialog box appears. There are three
methods to modify time and time zone, including Use netnu-
men time and timezone, Use netnumen time and custom
timezone and Customize time and timezone. After modi-
fication, click OK.
NTP Server Management

NE time configuration can use NTP protocol to synchronize NE time.
Users can make NEs and the NTP server synchronize time peri-
odically and automatically through configuring an available NTP
server for UMS.
Management > NTP Server Management on the resource
configuration management topology tree. NTP server informa-
tion is displayed. Users can create, modify, delete or search
for an NTP server.
2. Click on the tool bar. A dialog box appears, as shown in
Figure 14. Input the server name and the address, and then
click Ok. An NTP server is added.
FIGURE 14 ADD SERVER
3. Select a server and then click . A dialog box appears. The

server name can be modified.
4. Select a server to be deleted and then click on the tool bar.
A dialog box for confirmation appears. Click OK.
5. Click on the tool bar. A dialog box appears. Click OK. The
system begins to check the usability of the NTP server. The
result will be displayed after the check. If the NTP server status
is not checked, the result is “Unkown”. If the NTP server status
is checked, the result is “Available” or “Unavailable” according
to the situation of network.

NTP Synchronization Mode

Management
NTP synchronization mode means to designate whether an NE uses
NTP mode to synchronizes NTP time and set the parameters for
NTP synchronization mode.
Management > NTP Synchronization Mode Management
on the resource configuration management topology tree. An
interface appears.
2. Click on the tool bar. A dialog box appears.
3. Select an NE to be synchronized from the NE pull-down list,
input the PollTime (in the range of 4~14). The polling time is
2N, for example, 4 means 24, that is 16 seconds.
4. Click Add in Server Information area. A dialog box appears,
as shown in Figure 15.
FIGURE 15 ADD SERVER
5. Select the server address and locking state. The server address
is the address in NTP server management.
6. Click Add to finishing adding an NE and a server.
Configuring PTP Port Information

Standard Precision Time Protocol (PTP) is a master/slave synchro-
nization system. The core thought is that adopt master/slave
clock mode to code time information, and use network symmetry
and delay measure technique to realize synchronization of mas-
ter/slave time.

1. To enter PTP Port Configure Management interface, click

Network Resource > Clock Management > PTP Time
Management > PTP Port Configure Management on the
resource configuration management topology tree.
2. Click , the ptp port create interface appears, as shown in

Figure 16.
FIGURE 16 PTP PORT CREATE INTERFACE
The proprieties are described on Table 4.
TABLE 4 PTP PORT PROPERTIES
RES_PtpState PTP state, there are three

states, master, slave and
passive
RES_SynInterval The average time interval for

sending Sync messages. It
represents as 2n, n is an integer

ranging from -7 to 1. The
default value is 0.
RES_DelayReInterval The time interval for sending

DelayReq messages. It
ranging from -5 to 5. The
default value is 0.
RES_PDelayReqInterval The time interval for sending

PDelayReq messages. It
ranging from 0 to 5. The default
value is 0.
RES_DelayMech Cross-domain port, there are

two modes, P2P and E2E.
RES_NetProtocol IPv4 and IEEE802
RES_UnSymmetry Ranging from 0~1000000000
RES_UnSignt Positive and negative
3. Right—click a NE on the PTP Port Configure Management

interface, and select Load Interface Data, as shown in Figure
17.
FIGURE 17 LOAD INTERFACE DATA
4. The black items can be modified on the interface. For example,

double-click RES_PtpEnableState and modify it directly on
the interface.
Configuring PTP Global Information



1. To enter PTP Global Configure Management interface, click
Network Resource > Clock Management > PTP Time
Management > PTP Global Configure Management on
the resource configuration management topology tree.
2. Click , the ptp global create interface appears, as shown

in Figure 18.
FIGURE 18 PTP GLOBAL CREATE INTERFACE
3. Select a NE from the left part of ptp global create interface.

Configure the NE according to Table 5. Click OK to finish.
TABLE 5 PTP GLOBAL PROPERTIES
clockMode There are four modes, ordinary,

boundary and e2e, p2p.
alg SSM algorithm, BMC algorithm

and manual forced specification
priority1 User-defined forced priority,

ranging from 1 to 255.

priority2 User-defined manual priority,

ranging from 1 to 255.
onlyOne Yes or no. For clock node,

ordinary clock type does not
require this configuration. The
default setting is no.
twoSteep Yes or no. For clock node,

ordinary clock type and
boundary clock type does not
require this configuration. The
default setting is no.
domainNum This property is already

specified when creating clock
domain. It does not need
special configuration. Here, it
means that this property needs
to be provided to board.
interval It represents as 2n, n is an

integer ranging from -1 to 4.
timeout It represents as 2n, n is an

integer ranging from 2 to 10.
delay P2P or E2E. The default setting

is E2E.
4. The black items can be modified on the interface.
Configuring GPS Port

Abstract SSM (Synchronization Status Message) is only supported by IP
transmission platform products.
1. To enter GPS Interface Configure Management interface,
click Network Resource > Clock Management > SSM Time
Management > GPS Interface Configure Management on
the resource configuration management topology tree.
2. Click on the GPS Interface Configure Management in-

terface, the interface appears.
3. Right—click a NE on the interface, and select Load Interface
Data, as shown in Figure 19.

Configure the NE according to Table 6, and click OK to finish.
TABLE 6 PORT PROPERTIES
InfStatus Absolute time port state
ProtoType UBX or NMEA
InfDirection ingress or egress
1ppsOut For egress, output state of 1pps

is available.
InfSpeed unit is bps, The value is 4800,

9600 or 19200, 38400
InfCableDelay(ns) unit is ns, ranging from 0 to

9999999

Configuring SSM Clock

Synchronization
1. To enter SSM Clock Synchronize Config interface, click Net-
work Resource > Clock Management > SSM Time Man-
agement > SSM Clock Synchronize Config on the resource
configuration management topology tree.
2. Click , the SSM Global Config interface appears, as shown

in Figure 20.
FIGURE 20 SSM GLOBAL CONFIG
Select a NE, configure it according to Table 7, and then click

Confirm.

TABLE 7 SSM GLOBAL PROPERTIES
SSMEnable Whether enable SSM
StationEnable Whether is node clock NE. For

Node clock NE, select external
clock, internal clock or keep
mode clock in clock source list.
IDProtectedEnable Enable or disable ID protection
qualityUnknownEnable Whether enable quality level

unknown.
SSMMode unknown, ssm or ssm1, ssm2
StationID Ranging from 1 to 7
Quality Level There are five levels, unknown,

G.811 Clock Signal and G.812
Relay Site Clock, G.812
Local Clock Signal, G.813
Synchronized Device Clock.
WtrTime Set time to wait clock source

recovery, ranging from 0 to 12.
3. The black items can be modified on the interface. Double-click

it or select a SSM clock synchronization information from list,
and then click to modify.
Configuring SSM Clock Source

SSM clock source configuration includes clock source configura-
tion, protection switching of clock source and clock source lock,
WTR state clear and SSM byte sending.
1. To enter SSM Clock Source Config interface, click Network
Resource > Clock Management > SSM Time Management
> SSM Clock Source Config on the resource configuration
management topology tree.
2. Click , the SSM Global Config interface appears, as shown

in Figure 21.

FIGURE 21 SSM GLOBAL CONFIG INTERFACE
3. Select Select Devices and clockType. To add the matched
interface to list, click the first . To remove the selected
interface, click the second . To remove all interfaces, click
the third . The properties are described in Table 8.
TABLE 8 GPS PORT PROPERTIES
priorityValue 1 ~ 255
recvSSMMode auto-ssm and manual-ssm
Quality Level There are five levels, unknown,

G.811 Clock Signal and G.812
Relay Site Clock, G.812
Local Clock Signal, G.813
Synchronized Device Clock.
confLock There are three options,

dontConf, enable and unenable.
ClearWtrTime There are three options,

dontConf, ClearWtrTime and
ClearAllWtrTime.

Config Switch There are three options,

dontConf, Config Switch and
clear Switch.
4. The black items can be modified on the interface. Double-click

it or select a SSM clock synchronization information from list,
and then click to modify.
Configuring External Clock Port

Abstract External clock port management adopts master/slave mode, the
master table is external clock port list, and the slave table is clock
source list to be exported, and another table is the exported clock
source information of external clock port (non-edited).
1. To enter Extimer Port Management interface, click Network
Resource > Clock Management > SSM Time Management
> Extimer Port Management on the resource configuration
management topology tree.
2. The exported clock source information is displayed at Current
Out Clock, it is non-edited. Click Out Clock tab.
3. Click , the SSM Global Config interface appears. At most

10 clock source to be exported can be created.
4. Right—click a NE on the Extimer Port Create interface, and
select Load Interface Data, as shown in Figure 22. Select
Out Priority, and then click OK to finish.

Configuring Edge Link Management

On x10GE board, No.1 10GE port supports to synchronize network
edges. On GEx8O, GEx8E and GEx4, ATM-STM-1 boards, No.1 and
2 ports support to synchronize network edges.
1. To enter EdgeLink Management interface, click Network
Resource > Clock Management > EdgeLink Management
> on the resource configuration management topology tree.
Link Resource Configuration

Links are important resources that should be managed by UMS.
UMS can locate alarms, collect statistics of performance informa-
tion and implement Ping detection. Users can configure services
on the links through UMS. Link resource configuration provides an
interface for users to manage link resources.


1. Click Network Resource > Link Management > Link Man-
agement on the resource configuration management topology
tree. Link information is displayed.

Figure 23. Select the link type, input the information about A
NE and Z NE and then click OK.
FIGURE 23 CREATE LINK
3. Select a link in the list and then click on the tool bar. A
dialog box appears. The link status and link name can be mod-
ified. After modification, click Modify.
4. Select a link in the list and then click on the tool bar. A
dialog box for confirmation appears. Click OK to delete the
link.

Figure 24. Users can open the periodic task switch and set
the task interval (10 minutes by default). The system will syn-
chronize the link information of all devices that supports LLDP
periodically.

FIGURE 24 LINK DISCOVERY CONFIG
6. Click on the tool bar. A dialog box appears. Select the

NEs of which the links will be uploaded and then click OK. A
window appears,Click Execute.


Chapter 3
Layer 2 Management
Table of Contents
Link Aggregation Management ............................................43
LLDP Management .............................................................45
Configuring Port Mirroring...................................................47
VLAN Management ............................................................48
MAC Address Resource Management ....................................58
Link Aggregation
Management
Abstract Link aggregation is also called Trunk. It is to bind several physical
ports into a logical port to realize load sharing of outgoing traffic
and incoming traffic on the member ports. Users can configure
load sharing policies on switch ports to designate the member port
through which the messages are sent.
When a switch detects that the link of a member ports is inter-
rupted, the switch stops sending messages to this port until the
link of the port recovers. Link aggregation is an important technol-
ogy to increase link bandwidth and realize link transmission flexi-
bility and redundancy.
In link aggregation management interface, aggregation port infor-
mation is listed in the list above. The list below is member port
interface. Generally, link aggregation information is automatically
got by NE uploading.
The following introduces manual creation procedure.
1. Click Layer 2 Management > Link Aggregation Manage-
ment > Link Aggregation Information on the resource con-
figuration management topology tree. Aggregation port infor-
2. Create a link aggregation port
i. Click button on the tool bar to enter Create Link Ag-

gregation Port interface. A dialog box appears.
ii. Select an NE in the pull-down list of NE Display Name.
The port information of the selected NE is displayed in the
list in Information To Be Elected area. Select a port, as
shown in Figure 25.

FIGURE 25 CREATE LINK AGGREGATION PORT 2
The descriptions of common parameters on the dialog box

are shown in Table 9.
TABLE 9 AGGREGATION PORT PARAMETERS
NE Display Name It is the name displayed in the list. Select an NE in the pull-down
list of NE Display Name, the name displayed is the NE name. By
default, it is an IP address. The item with “*” mark is required to
fill in.
NE Type It is the type of the NE selected in NE Display Name pull-down list.
System Priority The range is 1~65535, and the default value is 32768.
*Channel No. It is the number of an aggregation port, in the range of 1~32. The
item with “*” mark is required to fill in.
Group Agg Mode It is the mode to bind physical ports. There are two modes, protocol
and static.
Load Balance Mode It is the load sharing mode of outgoing traffic and incoming traffic
on member ports. There are the following modes, source MAC and
destination MAC, destination IP, destination MAC, source IP and
destination IP, source IP, source MAC, destination IP and destination
port, source IP and source port.

Chapter 3 Layer 2 Management
iii. Click Confirm. A link aggregation port is created.

3. Upload aggregation port information. This is to synchronize
one or several pieces of aggregation port information from NE
to UMS.
i. Select one or several pieces of link aggregation information,
and then click on the tool bar. A window appears.

ii. Select a link aggregation port to upload in the Instance
List and tick the check box of Modify Operation to modify
the resource that is not consistent in NE and UMS. Click
Execute.
iii. The link aggregation port information that is the same in
NE and UMS has been synchronized to UMS. If there is no
such piece of link aggregation port information in the NE,
the link aggregation port information does not change after
uploading. If some attributes of this information in UMS are
not the same with that in the NE, the information in UMS
will be synchronized as that in the NE. If the information in
UMS is completely the same with that in tjr NE, there will
be no change in the interface.
4. Upload from an NE. This is to upload all link aggregation infor-
mation to UMS.
i. Click on the tool bar. A window appears.
ii. Select one or several NEs to upload and then click OK. A
window appears.
iii. Select the NE to be uploaded in the Instance List and
tick the operations in Operation Policy area to modify the
inconsistent configuration in database and NE. Click Exe-
cute.
5. Select one or several pieces of link aggregation port informa-
tion and then click on the tool bar. A dialog box for confir-
mation appears. Click OK to delete the information in UMS.
LLDP Management
LLDP is a new protocol defined in 802.1ab. It makes neighbor de-
vices send messages between each other to update the physical
topology information and establish a device management informa-
tion base. The working flow of LLDP is described below.
1. A local device sends link and management information to the
neighbor devices.
2. The local device receives link and management information
from the neighbor devices.
3. The network management information of neighbor devices is
stored in the local Management Information Base (MIB). The
network management software can query Layer 2 connection
information in the MIB.

LLDP does not work as a configuration protocol of remote systems.

It is not a signaling control protocol between interfaces, either.
LLDP can discover the differences about Layer 2 protocol config-
urations between neighbor devices. However, it does not provide
a mechanism to solve the problems. Instead, it just reports the
problems to the upper layer management devices.
In brief, LLDP is a neighbor discovery protocol. It defines a stan-
dard for Ethernet devices (such as switches, routers, wireless Local
Area Network (LAN) access points, and so on) to make them ad-
vertise their existence to other devices in the network and save
the discovery information of the neighbor devices. For example,
information such as device configuration and identifier can be ad-
vertised through LLDP.
At present, LLDP is supported by ZXR10 8900 series Multi Pro-
tocol Label Switching (MPLS) routing switches, G series 10 gi-
gabit MPLS routing switches, IP transport platform products and
high-end routers.
NE Information
1. Click Layer 2 Management > LLDP Management > NE Info
on the resource configuration management topology tree. NE
information is displayed.
2. The information in black can be modified in the list directly.
Users can double-click LLDP Enable, Message Interval, and
so on to modify the information.
3. The background of the modified information is pink and the
Status is “Not Saved”. Click on the tool bar to save the
data. The background becomes normal and the Status be-
comes “Saved”.
Port Information
1. Click Layer 2 Management > LLDP Management > Port
Info on the resource configuration management topology tree.
Port information is displayed.
2. The information in black can be modified in the list directly.
Users can double-click Port Administration Status to modify
the information.
comes “Saved”.

Configuring Port Mirroring

On switching Ethernet, the communication between two work sta-
tions can not be listened by the third-party. However, in some
cases, people need to monitor all the data packets passing in and
out network and make the management server with monitor soft-
ware capture data. It is so difficult to monitor all data packets
on switching network. Therefore, to make network be monitored,
people usually configure router and switch that forward the data
packets of one or more ports to another port.
Port mirroring function copies a part of or all traffic of source port to
another special mirroring port (destination port). In the case of no
heavy influence on source port throughput, monitor and analyze
network traffic by using mirroring port.
In short, port mirroring mirrors the monitored traffic to the moni-
tored port. The port at which the monitored traffic exists is called
source port, and the monitored port is called destination port. Des-
tination port connects to network analyzer directly.
At present, ZXCTN 6000 series packet transmission product,
ZXR10 2900 series intelligent Ethernet switch and ZXR10 2800S
Gigabit Ethernet switch support port mirroring function.
1. To view the configuration of port mirroring, click Layer 2 Man-
agement > Port Mirror Management > Port Mirror Con-
figuration on the resource configuration management topol-
ogy tree.
2. Right-click any information and select create from the pop-up
menu, or select , the Select Interface interface appears,

FIGURE 26 SELECT INTERFACE
3. Select a NE from the Select Interface interface, and then click

OK, the selected NE is added to the port mirroring configuration
list. The state of newly-added NE is unsaved.
5. The state of modified port mirroring is unsaved. Click to

save.
VLAN Management
Configuring a VLAN Port
Switches and IP transport platform products support VLAN port
configuration.
1. Click Layer 2 Management > Vlan Management > Vlan
Port Config on the resource configuration management topol-
ogy tree. VLAN port information is displayed.

2. For adding a VLAN port, the basic data of the VLAN port is the
same to the basic interface information. Therefore, configure
interface information of NE, and then add VLAN port of the NE.
Click on the tool bar. A dialog box appears, as shown in
Figure 27. Select an NE and then click OK. A VLAN port is
added.
FIGURE 27 NEW VLAN PORT CONFIG
3. The information in black in the list can be modified directly.

Users can double-lick the information and then modify the in-
formation.
4. The background of the modified information is in pink and the
Status is “Not Saved”. Click on the tool bar. The background
becomes normal and the Status becomes “Saved”.
Configuring a VLAN
Switches and IP transport platform products support VLAN config-
uration.
Config on the resource configuration management topology
tree. VLAN Information is displayed.
2. Create a VLAN.

ii. Select an NE and click Next. New Vlan Config tab is

displayed, as shown in Figure 28.
FIGURE 28 NEW VLAN CONFIG STEP 2
iii. Click after Vlan ID text box. A dialog box appears, as

shown in Figure 29. Users can create VLAns in batch.
FIGURE 29 SELECT
iv. Click OK, and then click OK in Figure 28. The new VLANs
are displayed.


Users can double-lick the information and then modify the in-
formation.
4. Modify VLANs in batch.
ii. Select NEs and click Next. Batch Set Parameters tab is
FIGURE 30 MODIFY VLANS IN BATCH STEP
iii. Modify the parameters and then click OK.

5. The background of the modified information is in pink and the

Status is “Not Saved”. Click on the tool bar. The background
becomes normal and the Status becomes “Saved”.
Configuring VLAN Translation

VLAN translation is also called VLAN mapping. It allows the VLAN
IDs used by different Ethernet switches for edge access to be du-
plicated. VLAN translation can be used to modify the duplicated
VLAN ID in different switches to different VLAN IDs and send them
out through uplink interfaces. Therefore, users can be isolated in
Layer 2 Core switches. This simplifies the configuration of edge
access switches.
At present, VLAN translation function is supported by ZXR10 8900
series MPLS routing switches and IP transmission platform prod-
uct.
Translation Config on the resource configuration manage-
ment topology tree. VLAN translation information is displayed.
Figure 31. Select an NE, input Session ID and select the
Ingress Port and other parameter values. Click OK.
FIGURE 31 VLAN TRANSLATION
3. Select a piece of VLAN translation information and then click

on the tool bar. A dialog box appears. Users can modify the
Ingress Port, Egress Port, Ingress Vlan List and Egress
VLAN. After modification, click OK.

Configuring a Selective VLAN

Selective VLAN (SVLAN) is a VLAN extension technology based on
QinQ. It increases the number of VLANs to 4094*4094 by stacking
two 802.1Q headers in Ethernet frames. Meanwhile, several inner
VLANs can be used in a core VLAN. Messages can be switches ac-
cording to outer labels or inner labels and outer labels at the same
time. SVLAN has good flexibility. It can isolate VLANs effectively
and reuses VLAN resources. SVLAN provides necessary basis for
the network architecture of the core network with MPLS switching.
At present, SVLAN is supported by ZXR10 8900 series MPLS rout-
ing switches, ZXCTN 9000 series packet transport products and
ZXCTN 6000 MAN Ethernet products.
1. Click Layer 2 Management > Vlan Management > Selec-
tive Vlan Config on the resource configuration management
topology tree. Selective Vlan information is displayed.
2. Create a Selective VLAN.
i. Click on the tool bar. A dialog box appears, as shown in
Figure 32.
FIGURE 32 NEW SELECTIVE VLAN CONFIG 1

ii. Click Browse to select an NE. Input the Session ID (in

the range of 1~1000). The next action and device support
information are displayed at the top of the dialog box. Click
Next. A dialog box appears.
iii. Select Customer port and Uplink port, input the Invlan
range and Outvlan. Click Next to enter New Selective
Vlan Config interface.
iv. Set Setting priorities, setting working mode and Undi-
rect. Click OK to finish.
3. Select a selective VLAN to be modified and then click on the

tool bar. A dialog box appears. Users can modify Acl number,
Rule number and Outvlan. After modification, click OK.
Managing a VLAN Domain

VLAN domain management is supported by all switches and IP
Service Management > Vlan Domain Management on the
resource configuration management topology tree. VLAN do-
main information is displayed.
Figure 33. Input Vlan Domain ID and Vlan Domain Name.
Floating windows will appear to prompt the requirement for
characters input. Select NEs on the NE tree to add to the do-
main. The NEs on the tree are devices supporting VLAN domain
after filter. Click OK. A VLAN domain is created.

FIGURE 33 CREATE VLAN DOMAIN
3. Select a VLAN domain and then click on the tool bar. A dialog
box appears. Users can modify the Vlan Domain Name and
Vlan Domain Description. After modification, click OK.
4. Select a VLAN domain to save and then click on the tool bar.
The Status of the domain becomes “Saved”.
5. Select a VLAN domain to delete and then click on the tool
bar. A dialog box for confirmation appears. Click Yes. The
VLAN domain is deleted from database and the list. If there
are VLAN services running in the VLAN domain in the database,
the VALN domain cannot be deleted.
6. Select a VLAN domain and then click on the tool bar. A win-
dow appears. The detailed VLAN domain information is dis-
played. All attributes cannot be edited.
Managing Port-Based VLAN Service

Port-based VLAN service management is supported by all switches
and IP transmission platform products.
Service Management > Port-based Vlan Management on
the resource configuration management topology tree. Port-

based VLAN service information is displayed. The positions of

NEs on Vlan Service Topolo View is the same as that in the
physical view. Users can double-click an NE in the topology to
view the information of the NE and right-click an NE to view
the VLAN information of the NE.
2. Create a VLAN.
Figure 34.
FIGURE 34 CREATE VLAN STEP 1
ii. Input the VLAN basic information. Vlan ID is required to

fill in. In the right pane, there are NEs in the VLAN domain.
Select two ore more NEs and then click Next. Select Vlan
Path tab is displayed.
iii. Select the NE path and then click Next. Select Vlan Port
tab is displayed.
iv. Select ports on NEs to add to the VLAN. Click Next. VLAN
Summary tab is displayed. Click Finish.
3. Manage VLAN service discovery tasks.
i. Click on the tool bar. A window appears, as shown in
Figure 35.

FIGURE 35 VLAN SERVICE DISCOVERY MANAGEMENT 1
ii. Select a VLAN domain and set the Execute Mode. Click
Timing Execute. A dialog box appears, prompting that a
VLAN discovery service is added successfully.
iii. Click VLAN Service Discovery Log Management tab.
On the left pane, it is the service discovery task record tree
and theses records are displayed by time. Click a node on
the tree, the detailed records are displayed in the table in
the right pane.
iv. Double-click a line in the table, the detailed information of
the VLAN service discovery task is displayed. Click Print
to print the data of the nodes on the tree, and click Save
As to save the data of the nodes on the tree as a file. Click
Delete to delete the task record.
4. Double-click a VLAN service or select a VLAN service and then
click on the tool bar. Users can view the detailed information
of the VLAN service. The attributes cannot be edited.

MAC Address Resource

Management
Medium Access Control (MAC) is hardware identifier of network de-
vice. Switch forwards packets according to MAC address. MAC ad-
dress is unique, which guarantees the correct forwarding of pack-
ets.
Every switch maintains a MAC address table. In this table, MAC
address corresponds to switch port one by one. When switch re-
ceives data frame, it decides to forward the frame to corresponding
port or filter the frame according to the MAC address table. MAC
address table is the basis and precondition of fast forwarding. On
L2 switch, MAC filter function, static address binding function and
MAC table aging can be configured. On L3 switch, MAC table aging,
MAC address fix and MAC address binding, MAC address learning
and port MAC address learning protection, MAC address filter and
so on can be configured.
At present, MAC address resource management is supported by
ZXR10 8900 series MPLS routing switches, ZXR10 6900 series
10Gigabit routing switches and G series 10Gigabit MPLS routing
switches, IP transmission platform products.
MAC Address Table Configuration

This topic describes the configuration and operation of a MAC ad-
dress table.
1. Click Layer 2 Management > MAC Address Resource Man-
agement > MAC Address Table Config on the resource con-
figuration management topology tree. MAC address table in-
formation is displayed.

Figure 36.

FIGURE 36 ADD MAC ADDRESS
The properties are described in Table 10. Click OK to finish.
TABLE 10 PROPERTY DESCRIPTION
NE Name NE name, select it from

pull-down list
Type MAC address type is static,

dynamic and filter. Filter
Direction is only available
when filter is selected here.
MAC Address MAC address which corresponds

to the NE
VlanId 1 ~ 4096
Port Name Port which corresponds to the

NE, select it from pull-down list
Filter Direction The filter can be performed

according to source, destination
and bidirectional.
3. Select a MAC address in the list and then click on the tool
bar. A dialog box for confirmation appears. Click OK.
4. Curing and Non-Curing
Curing a MAC address is to make a dynamic MAC address not
participate in aging. Non-curing is a reverse process.
i. Select a dynamic MAC address and then click on the tool
bar. A dialog box appears.
ii. Click OK. The aging status becomes No.

iii. The operation for non-curing is similar with that of curing.
Port MAC Address Configuration

This topic describes the configuration and operation of a port MAC
address.
1. Click Layer 2 Management > MAC Address Resource Man-
agement > Port MAC Address Config on the resource con-
figuration management topology tree. Port MAC address infor-

Figure 37.
FIGURE 37 CREATE MAC PORT INFO
The properties are described in Table 11. Click OK to finish.
TABLE 11 PROPERTY DESCRIPTION
NE Name NE name, select it from

pull-down list
Port Name The port which corresponds to

the NE, select it from pull-down
list
Learning Enable Enable or disable
Limit Number 0 ~ 262144
Protect Enable Enable or disable
Protect Time(s) 0 ~ 3600

3. The black items can be double-clicked and modified directly on

the interface.


Chapter 4
Layer 3 Management
Table of Contents
Route Management............................................................63
Routing Protocol ................................................................68
ARP Management .............................................................72
Route Management
Route Topology Analysis
This topic describes how to view the detailed route topology infor-
mation and how to operate a route topology, including uploading,
viewing and displaying the topology.
1. Click Layer 3 Management > Route Management > Route
Topo Analysis on the resource configuration management
topology tree. Route topology analysis information is dis-
played.
2. Click on the tool bar. A window appears, as shown in Figure
38.

FIGURE 38 ROUTE INFO UPLOAD
3. If users click Execute Task Now, it is not necessary to set the

parameter values. A dialog box indicating operation success
will appear. Users also can create a new task. It is necessary
to input the task name and task description, set the execution
mode, and so on.
Static Route
A static route is a piece of route information that is configured
by a network administrator manually. When the network topology
structure or the status of a link changes, the network administra-
tor needs to modify the static route in the routing table manually.
By default, static routing information is private and it is not trans-
mitted to other routers. The network administrator can also set
the static route to be shared. Usually, static routes are used on
simple networks. In such situations, it is easy for network admin-
istrators to know the topologies and configure routing information
correctly.
At present, static route function is supported by IP transmission
platform products.
1. Click Layer 3 Management > Route Management > Static
Route on the resource configuration management topology
tree. Static route information is displayed.
39. Select an NE and input the destination network address,
mask, next hop, and so on. Click add info to add the new static
route to the list at the bottom. Users can click to delete a
selected static route. Click apply to make the configuration
valid.

FIGURE 39 ADD STATIC ROUTE
Parameters on the window are described in Table 12.
TABLE 12 STATIC ROUTE PARAMETERS
NE Name It is a router configured with static routes.
Destination Network It is the network the router to reach.
Subnet Mask It is used to divide an IP address into two parts, a network address
and a host address.
Next Hop It is the egress or an IP address through which the router reaches
the destination network.

Interface It is the local network interface. Here, it is the mng interface, vrf
interface and global routing table interface.
Metric It is the distance or priority.
Tag It is optional.
Whether to Deploy It is used to identify whether the message has been deployed to the
device.
3. Configure static route based load sharing function on links.

i. Click on the tool bar. A window appears, as shown in
Figure 40.
FIGURE 40 LOAD BALANCE SET 1
ii. Select an NE and set the network address, mask and the
maximum number path (That is, the maximum number of
links can be added). Set this value according to the device.

Click next step. Load Balancepolicy set tab is displayed,

FIGURE 41 LOAD BALANCE SET 2
iii. Input the next hop address and set the tag value (in the
range of 150~255). Click add info to add the static route
to the list at the bottom. Users can click to delete a
selected static route. Click apply to save the load balance
configuration to database.

Routing Protocol
RIP Protocol Management
RIP is a kind of interior gateway protocols, which realizes dynamic
route selection as the first one of routing protocol. It is realized on
the basis of local network-based distance vector routing algorithm.
RIPv1 is defined by RFC1058, and RIPv2 is defined by RFC1723.
ZTE devices support RIPv1 and RIPv2 fully. RIPv2 is used by de-
fault. Comparing with RIPv1, RIPv2 has the following advantages,
� Supports Classless Inter-Domain Routing (CIDR) and Variable
Length Subnet Mask (VLSM).
� Protocol packet can bring authentication information.
� Protocol packet can adopt multicast mode.
At present, RIP protocol management is supported by all data de-
vice except low-end switches.
1. To show the information of the interface related to RIP, click
Layer 3 Management > Router Protocol > RIP Manage-
ment > RIP Interface Config Information on the resource
2. Click , the Device Selection interface appears. Select NE

from the Device Selection interface, the Upload Configura-
tion From Devices interface appears. Click Execute to up-
load RIP protocol information of NE to network management,
its state is have synchronization.
3. Select many RIP protocol information items on the RIP Neigh-
bor Information interface, and click , a dialog box appears

to confirm whether to delete the information. Click OK to fin-
ish.
OSPF Protocol View

Open Shortest Path First (OSPF) is one of the most popular and
widely-used routing protocols. It is a kind of link state protocol.
It overcomes the disadvantages of RIP and other distance vector
protocols. It is also a open standard, which means devices coming
from different manufactories can realize protocol interconnection.
OSPFv1 is defined by RFC1131. At present, OSPFv2 is used and it
is defined by RFC2328. ZTE data routing devices support OSPFv2
fully.
OSPF has the following features,
� Fast convergence. It guarantees the synchronization of
databases by fast diffusing link state, and calculate routing
table at the same time.

� There is no route loop. Use Shortest Path First SPF) ti make

sure that no loop occurs.
� Route aggregation. It is used to reduce the size of routing
table.
� It is classless. It supports VLSM and CIDR.
� It reduces the network bandwidth to be required. Since us-
ing trigger updating mechanism, update message is only sent
when the network changes.
� It supports interface packet authentication. It is used to guar-
antee the security of route calculation.
� It sends update message by using multicast mode. In this way,
the influence on network devices of other unrelated network
can be decreased.
At present, OSPF protocol management is supported by all data
devices except low-end switches.
1. To show OSPF information, click Layer 3 Management
> OSPF Management > > OSPF View on the resource
2. There are two areas on the OSPF View interface, the upper
area shows OSPF configuration instance information, and the
lower area shows other information related to OSPF instance.
Select an information item from the upper area, and the OSPF-
related information can be viewed at the lower part, such as
ospfArea, ospfStubArea and ospfLsdb, ospfExLsdb and
ospf Interface, ospfMetric and so on.

load OSPF protocol information of NE to network management,
5. Select many OSPF protocol information items on the OSPF
View interface, and click , a dialog box appears to con-

firm whether to delete the information. Click OK to finish.
IS-IS Protocol View

Intermediate system to intermediate system protocol (IS-IS) is a
advanced by international standardization organization, which is a
routing protocol used for Connectionless Network Protocol (CLNS).
It is the network layer protocol of OSI. By expanding IS-IS pro-
tocol, the support to IP routing is improved, and integrated IS-IS
protocol is formed.
IS-IS is widely used on network acting as a kind of IGPs. Its work-
ing mechanism is similar to that of OSPF. It divides network into

some areas, the routers only manage the routing information of

their area. In this way, router cost is saved. It especially applies
to middle and large-scale network.
Due to IS-IS runs on the basis of CLNS not IP, IS-IS uses Protocol
Data Unit (PDU) defined by ISO for the communication between
routers. IS-IS uses the following PDUs,
� Call PDU
� Link state PDU (LSP)
� Sequence Number PDU (SNP)
Here, Call PDU is similar to the Hello packet used by OSPF protocol.
It is responsible for forming adjacent relationship between routers,
finding new neighbor and detecting whether has neighbor exit.
IS-IS router uses LSA to exchange route information, create and
maintain link state database. A LSP is an important information
item related to router, including area and connected network.
Meanwhile, SNP is used to guarantee that LSP can be transmitted
reliably.
SNP contains the summary information of every LSP on network.
When router receives a SNP, it compares the SNP with its link state
database. If the router loses a LSP existing in SNP, it will reply a
SNP by multicast mode to require the required LSP.
By means of the cooperated usage of LSP and SNP, IS-IS can per-
form reliable route interaction on large-scale network.
IS-IS also uses Dijkstra SPF to calculate routes. IS-IS obtains the
optimized route by using SPF according to link state database, and
then adds the route to IP routing table.
At present, IS-IS protocol management is supported by all data
1. To show IS-IS information, click Layer 3 Management >
IS-IS Management > > ISIS View on the resource config-
uration management topology tree.
2. There are two areas on the ISIS View interface, the upper
area shows ISIS configuration instance information, and the
lower area shows other information related to ISIS instance.
Select an information item from the upper area, and the ISIS-
related information can be viewed at the lower part, such as
isisLSPLevel, isisLSPID and isisLSPSeq, isisLSPZeroLife
and isisLSPChecks and so on.

load ISIS protocol information of NE to network management,
5. Select many IS-IS protocol information items on the ISIS
View interface, and click , a dialog box appears to confirm

whether to delete the information. Click OK to finish.

BGP Protocol Management

Border Gateway Protocol (BGP) is an inter-domain routing protocol
used among ASs, to exchange network reachability information
among ASs running the BGP.
The information is a list of ASs where a route passes through,
which is sufficient to set up a diagram indicating the connection
status of the ASs. Thus, routing policy based on ASs is available,
and also the route loopback problem is solved.
BGP of version 4 (BGP4) is the latest BGP version, which is defined
in RFC1771. BGP4 supports the implementation of CIDR, super-
net and subnet and the functions such as route aggregation and
route filtering. At present, BGP4 has found wide application on the
Internet.
An administrative area with independent routing policies are called
an Autonomous System (AS). An important feature of an AS is that
it has a unified internal route for another AS and has a consistent
topology for reachable destinations. The indicator for an AS is a
16-bit value, ranging from 1 to 65535, where, 1 through 32767
are assignable, 32768 through 64511 are reserved, and 64512
through 65534 are used for private ASs (similar to private network
addresses among IP addresses).
A session set up between BGP routers in different ASs is called an
External Border Gateway Protocol (EBGP) session, while a session
established between BGP routers in the same AS is called an In-
ternal Border Gateway Protocol (IBGP) session.
BGP runs on a reliable transmission protocol. Transmission Control
Protocol (TCP) is used as its bottom-layer protocol, and the TCP
port is port 179. Two routers running BGP first set up a TCP con-
nection, and then pass packet authentication and exchange all the
routing table information. After that, when the route changes, the
routers will send a routing update message to all BGP neighbors,
and then the BGP neighbors will flood the routing information until
the entire network receives the routing information.
When a router sends BGP update messages about the destination
network to its peer router, the messages contain information about
BGP metric (called path attribute). The path attributes have the
following four independent types:
� Well-known mandatory attributes: The attributes need to ap-
pear in the route description.
� AS-path
� Next-hop
� Origin
� Well-known discretionary attributes: The attributes do not
have to appear in route description.
� Local preference
� Atomic aggregate
� Optional transitive attributes: The attributes do not need sup-
port in all BGP implementations. However, if an attribute is
supported, the attribute can be transferred to its BGP neigh-

bor, while attributes not supported by the current router shall

continue being transmitted to other BGP routers.
� Aggregator
� Community
� Optional nontransitive attribute: The attribute indicates that
routers that do not support the attribute need to be deleted.
� Multi-Exit Discriminator (MED)
At present, BGP protocol management is supported by all data
1. To show BGP global configuration information, click Layer 3
Management > BGP Management > BGP Global Infor-
mation on the resource configuration management topology
tree.

load ISIS protocol information of NE to network management,
3. Select many IS-IS protocol information items on the ISIS
View interface, and click , a dialog box appears to confirm

whether to delete the information. Click OK to finish.
4. User can search result according to their requirements.
i. Click Advanced on the interface to show all query condi-
tions.
ii. Select query condition form the pull-down list, and then
click to show the query result.
iii. Click to clear query result.
iv. Click , the Save Query Condition dialog box appears,

enter Name and click Save or Save and Query. The query
condition can be selected from the pull-down list at the next
time.
v. Click , the Customize Query Condition interface ap-

pears, the blue conditions are displayed, and other condi-
tions are hidden. Users can set it for their requirements.
Click OK to finish.
vi. Click Hide to hide a part of query conditions.
5. For the information of BGP relationship navigator, please refer
to Relationship Navigator.
ARP Management
When a network device sends data to another network device, IP
address and physical address (MAC address) of destination device

have to be known. To make that the communication can be per-

formed successfully, ARP maps IP address to physical address.
At present, ARP management is supported by ZXR10 8900 se-
ries 10 Gigabit MPLS routing switch, ZXR10 6900 series 10 Gi-
gabit routing switch and ZXR10 T128/T64E carrier-class high-end
router, ZXR10 T600/T1200 carrier-class high-end router.
Configuring ARP Global Information

1. Click Layer 3 Management > ARP Management > ARP
Global Management on the resource configuration manage-
ment topology tree.
2. Click , the Create ARP configure information interface

appears, as shown in Figure 42. Select a NE, set Enable
MAC default limit-number and Enable whole default
limit-number, and then click OK.
FIGURE 42 CREATE ARP CONFIGURE INFORMATION
3. Select an ARP information item from the list on the ARP Global
Configuration interface. Click , a dialog box appears to
indicate whether IP address and MAC address is bound. Click
, a dialog box appears to indicate that release the binding
between IP address and MAC address.
4. Select an ARP information item from the list on the Interface
limit number configuration interface, as shown in Figure 43.
Set Enable interface default limit-number and Interface
limit number, the range is 1 ~ 65535. Default value is 8912.

FIGURE 43 INTERFACE LIMIT NUMBER CONFIGURATION
Configuring ARP Table

1. Click Layer 3 Management > ARP Management > ARP
Address Config on the resource configuration management
topology tree.
2. Click , the Create ARP configure information interface

appears, as shown in Figure 44. Select NE name,PortName
and ArpType. There are two kinds of ARP types, static and
permanent. Set IP and MacAddress. Click OK to finish.
FIGURE 44 CREATE ARP

Chapter 5
Service Management
Table of Contents
Traffic Engineering Basic Configuration Management ..............75
MPLS LSP Management ......................................................80
Traffic Engineering Basic

Configuration Management
Routers forward traffic according to the shortest paths calculated
out by traditional routing protocols. Even if congestion occurs on
a path, routers do not hand over the traffic to other paths. In
the case that network traffic is not large, the problem is not se-
rious. However, with the applications of Internet becoming wider
and wider, the routing problem caused by traditional shortest path
exposes absolutely.
With traffic engineering, service providers can control the paths of
traffic accurately. This can avoids congested nodes, thus solving
the problem that some paths are overloaded while some paths are
idle and making current bandwidth resources used fully.
At present, Traffic Engineering (TE) is supported by IP transmission
platform product only.
TE Global Configuration Management

This topic describes the global TE configuration and operations,
including creating, modifying, deleting, deploying, auditing, and
so on.
1. Click Service Management > Traffic Engineering Basic
Config Management > Global Config Management on the
resource configuration management topology tree. Global
Config Management tab page is displayed.
Figure 45. Select a node on the topology tree on the left and
then input the parameter values on the right. Click OK.

FIGURE 45 GLOBAL CONFIG ABOUT TE
The parameters of global configuration are described in Table

13.
TABLE 13 GLOBAL TE CONFIGURATION PARAMETERS
Enable TE It is to enable or disable global TE.
Enable RSVP Hello It is to enable or disable Hello detection.
RSVP Hello Interval It is in the range of 5000~65535000, in unit of millisecond, with

default value 30000.
RSVP Hello Loss It is in the range of 2~10, with default value 4.
Min Label It is used to configure the minimum label. The range is 16~59390.
The default value of 16.
Max Label It is used to configure the maximum label. The range is 16~59390.
The default value of 59390.
Enable RSVP GR It is to enable or disable TE Graceful Restart (GR) function.
GR Interval It is to configure the Hello interval of GR function. The range is

10~30000. The default value is 10000.
GR Loss Count It is to configure the Hello loss count of GR function. When the actual
count is larger than the value set, neighbors judges that it is lost. The
range is 4~10. The default value is 4.
GR Recovery Time It is to configure the recovery time of GR function. The range is

0~300000, in unit of millisecond. The default value is 120000.
GR Restart Time It is to configure the restart time of GR function. The range is

0~300000, in unit of millisecond. The default value is 120000.

Chapter 5 Service Management
3. Click on the tool bar. A window appears. Select an NE and

operation policy and then click Execute. The system will up-
load the information according to the operation policy auto-
matically.
If the operation policy is Add Operation, the system will up-
load the information existing in the device but not existing in
the database to the database. If the operation is Modify Oper-
ation, the system will modifying the information in database
according to the information in the device. If the operation
policy is Remove Operation, the system will delete the infor-
mation existing in the database but not existing in the device.
TE Interface Management
This topic describes how to view TE information on a service inter-
face.
Config Management > Interface TE Management on the
resource configuration management topology tree. Interface
TE Management tab is displayed.
Figure 46. Select an NE on the topology tree on the left and
then input parameter values in the right pane. Click OK.
FIGURE 46 INTERFACE TE CONFIG MANAGEMENT

IGP Configuration Management

This topic describes Interior Gateway Protocol (IGP) configuration
and operation.
Config Management > IGP TE Config Management on
the resource configuration management topology tree. IGP
2. Create IGP configuration.
Figure 47.
FIGURE 47 OSPF CONFIG
ii. Select a node on the topology tree on the left, input the
process ID and select a router ID on the right. Click create.
A dialog appears, as shown in Figure 48.
FIGURE 48 CREATE OSPF AREA

iii. Input the area ID and enable TE, and then click OK. The
OSPF area created is displayed in the list in Figure 47. Users
can click modify to modify the status of Enable TE and
click delete to delete an item selected.
iv. Click IS-IS config tab in Figure 47. IS-IS config tab is
FIGURE 49 IGP CONFIG MANAGEMENT 2
v. Select a node on the topology tree on the left. The interface

information of the NE is displayed in the list on the right.
The ISISRouteState column in the list can be edited, and
it can be enable or disable. When it is enable, the inter-
face supports IS-IS enabling; otherwise, it does not sup-
port. Tick the check box before Configure IS-IS. The pa-
rameters of IS-IS configuration are described in Table 14.
TABLE 14 IS-IS CONFIGURATION PARAMETERS
ISISRouterID Users can click to select the IS-IS router ID.
System ID It is to configure the IS-IS system ID.
Metric Style It is divided into two types: extended and non-extended.
Type It is used to configure the level of the router. There are level-1,
level-2-only and level-1-2.
IS-IS Area 1 The range is 10~99.
IS-IS Area 2 It is optional, in the range of 10~99.
IS-IS Area 3 It is optional, in the range of 10~99.

vi. Tick the check boxes in the list and then click OK. The
parameter setting is finished.
MPLS LSP Management

At present, MPLS Label Switched Path (LSP) function is supported
by IP transmission platform products.
Explicit Path Management

This topic describes the configuration and operation of an explicit
path.
1. Click Service Management > MPLS LSP Path Management
> Explicit Path Management on the resource configuration
management topology tree. Explicit Path Management tab
page is displayed. The detailed information of an explicit path
is displayed in the list, and the topology is displayed in the
topology view.
Figure 50.

FIGURE 50 EXPLICIT PATH CONFIG MANAGEMENT 1
3. Select a source IP address in the Start* pull-down list, select

a destination IP address in the End* pull-down list and select
Range. Click Search. All links found are displayed in the
list at the bottom. Select a link, the topology is displayed in
the topology view. Click Next. Explicit path config tab is
displayed.
4. Configure the explicit ID (in the range of 1~65535) or explicit
name. For the configuration of next hop address and type in
the list, please refer to the information in tip area. The next
hop address cannot be null. Click OK. The TE explicit path
information is saved.
Tunnel Management
Tunnel management is to manage the information of tunnels be-
tween source devices and destination devices. Users can create
or modify a tunnel according to creation guide.
> Tunnel Management on the resource configuration man-
agement topology tree. Tunnel Management tab page is dis-
played.


Figure 51.
FIGURE 51 TE OPERATE GUIDE
The parameters shown on Figure 51 are described in Table 1.
TABLE 15 TUNNEL OPERATION PARAMETERS
One-way Or Two-way There are two modes, one-way

and two-day. One-way
corresponds to A->Z tunnel
interface. Two-way corresponds
to A->Z and Z->A tunnel
interface.
NE A(*) Select NE on A side
NE Z(*) Select NE on Z side. The path is

displayed at the right topology.
Detailed path information is
displayed at the list.
Tunnel ID A->Z tunnel ID, 1 ~ 1024
Reverse ID Z->A tunnel ID, 1 ~ 1024
Create PRI 0 ~ 7
Hold PRI 0 ~ 7

Reference Interface (Index) IP address and mask of tunnel

interface have to be recorded
if tunnel does not refer to the
interface of device. When
interface is referred, the
interface is the one of device
with IP address.
3. Select a link from the right topology to create tunnel. Click Add
explicit path on Te Operate Guide, the Explicit path config
management interface appears. For more information, refer
to Explicit Path Management. Click Save Temp Guide to save
tunnel operation template. A prompt will appear to indicate
whether use this template when create tunnel next time. Click
Sve to database to save the newly-added tunnel to network
management database. Click Save and deploy to save the
newly-added tunnel and deploy it to device. Click Close to
close the Te Operate Guide interface
MPLS LSP Path Management

Dynamic LSPs on the network are displayed through a table and
in topology rendering mode in UMS. Users cannot create a piece
of dynamic path information manually. All information is obtained
from devices and then updated to the database.
> Dynamic Path Revert on the resource configuration man-
agement topology tree. Dynamic path reverting information is
displayed.
2. Click on the tool bar, the Device Selection interface ap-
pears. Select a NE to be uploaded and then click OK. The Up-
load Configuration From Devices interface appears. Select
a dynamic LSP to be uploaded in the Instance List, and then
select the corresponding action from Operation Policy to add,
remove or modify the inconsistent resources in the database
and NE. Click Execute to upload the dynamic LSP.
3. Click on the tool bar. The LSP Label Info View interface
appears.
4. Select a NE to be viewed, and then click Next to enter the
Label Info interface, as shown in Figure 52.

FIGURE 52 LABEL INFO
5. Select the Start Node, End Node and optional parameters

from the Dynamic Path Revert interface. Click to search
MPLS LSP path. Click any one on the search result, the detailed
information of the path is displayed at the below list, and the
passed NEs and links are marked on the topology.
Tunnel Protection Management

Fast Reroute (FRR) is an important function of MPLS TE and it is an
enhancement for the function of Resource ReSerVation Protocol-
Traffic Engineering (RSVP-TE) sub-system.
In a complicated network, there are links and nodes becoming
invalid. In the traditional method, IGP processes the links and
nodes to converge the network again and generate routes fast.
For a large-scale network, it costs a long time to converge the
network. Usually it is in unit of second. A lot of packets are lost.
In such situation, MPLS TE FRR can be used to decrease the loss of
packets to the maximum extent. FRR can change over the packets
from an invalid link to the standby link within several dozen mil-
liseconds. This decreases the loss of packets greatly and meets
the requirements of resources.
> Tunnel Protection Management on the resource configu-
ration management topology tree. Tunnel protection informa-
tion is displayed. The existing LSPs are listed in the first list,
and the topology is displayed in the topology view. The Pro-

tect Tunnel Configure and Protect Tunnel Detail Info are

listed in the second list.
2. Click on the tool bar, the Select interface appears.
3. Select Node A(*) and Protected Interface, the existing LSPs
are displayed at the list, select a LSP. Click Confirm to create
the protected tunnel.


Chapter 6
Security Management
Table of Contents
Time Range Management ...................................................87
ACL Management ..............................................................93
User And Account ..............................................................97
Time Range Management

Time Range Template Management
A time range template is a template created in advance in UMS.
The template is used to save time range information. According
to time range types, there are different parameters in the tem-
plates. Time range template management includes querying, cre-
ating, deleting and modifying.
At present, time range template management is supported by
IP transmission platform product, ZXR10 8900 series 10 Gigabit
MPLS routing switch and ZXR10 5900/5200 series full gigabit in-
telligent routing switch, ZXR10 3900A/3200A series L3 intelligent
Ethernet switch.
1. Click Security Management > Time-range Manager >
Time-range Template Manager on the resource config-
uration management topology tree. Time range template
2. Create a time range template.
Figure 53.

FIGURE 53 CREATE TEMPLATE
ii. Input the template name and then click in Added Time-
range Information area. A dialog box appears, as shown
in Figure 54.

Chapter 6 Security Management
FIGURE 54 ADD DETAILED TIME RANGE INFORMATION 1
iii. There are two types of time ranges, absolute time range
and periodic time range. If Absolute Time-range is se-
lected, the detailed information to set is shown in Figure
54. Set the start time and end time. The end time must be
later than the start time. The seconds must be a multiple
of 15. Click OK. The new time range will be displayed in
the list in Figure 53.
iv. If Periodic Time-range is selected in Figure 54, the de-
tailed information to set is shown in Figure 55.

FIGURE 55 ADD DETAILED TIME RANGE INFORMATION 2
v. Select Day Set or Day Range. The end time must be later
than the start time. The seconds must be a multiple of 15.
Click OK. The new time range is added. A time range may
include an absolute time range and several periodic time
ranges. Click OK. A time range is added.
vi. Click OK. A time range template is created.
3. Select a time range template and then click on the tool bar.
A dialog box appears. Users can modify the information of
the template. The time range type can not be modified. The
information in black can be modified in the list directly by dou-
ble-clicking the cell.
4. Select a time range and then click on the tool bar. A dialog
box for confirmation appears. Click OK to delete the template.
comes “Saved”.
Switch Time Range Management

This topic describes switch time range management, include
querying, creating, deleting, and so on.

At present, time range management is supported by IP transmis-

sion platform products, ZXR10 8900 series MPLS routing switches,
ZXR10 5900/5200 series gigabit intelligent routing switches and
ZXR10 3900A/3200A series Layer 3 intelligent Ethernet switches.
1. Click Security Management > Time-range Management
> Switch Time-range Config on the resource configuration
management topology tree. Switch time range information is
displayed.
2. Create a tine range.
ii. Click an NE from the pull-down list box. Tick the check box
before Select Template and then click Import Template.
A dialog box appears, as shown in Figure 56.
FIGURE 56 IMPORT TEMPLATE
iii. All time range templates suiting the NE are displayed. Se-
lect a template according to demand and then click OK
to return to Create Time-range dialog box, as shown in
Figure 57.

FIGURE 57 CREATE TIME RANGE 2
iv. A template is imported successfully. Input the time range

ID (comprising numbers and characters). Users can modify
the template. Click on the tool bar in Figure 57 to add a
new time range. If the check box before Select Template
is not ticked, users can create a template and time range
directly. For the steps to create a template and time range,
please refer to Time Range Template Management. Click
OK.
3. Click on the tool bar. This saves the time range configuration
as a template.

ACL Management
At present, Access Control List (ACL) management is supported by
IP transmission platform product, ZXR10 8900 series MPLS rout-
ing switches, ZXR10 5900/5200 series gigabit intelligent routing
switches and ZXR10 3900A/3200A series Layer 3 intelligent Eth-
ernet switches.
1. Click Security Management > ACL_Manage > Switch ACL
Config on the resource configuration management topology
tree. ACL configuration is displayed. The ACL rules are dis-
played in the second list.
2. Create an ACL and rule.
Figure 58.

FIGURE 58 CREATE NE ACL
ii. Select the device type in the DeviceGroup Name pull-list

box. There are IP transmission platform product, 89/82 se-
ries switches (v4.08.23) and 59/39A series switches. Se-
lect an NE in the NE pull-down list. There are four types
of ACLs, standard ACL, extended ACL, Layer 2 ACL and hy-
brid ACL. The rules are different for different types of ACLs.
Here standard ACL is selected. Select the ACL number (in
the range of 1~99). The value of Rule Match Sequence
is “Auto” or “Config”. Click on the tool bar in the Added
Rule Info area. A dialog box appears, as shown in Figure
59.

FIGURE 59 CREATE ACL RULE
TABLE 16 ACL TYPE AND CONFIGURATION RULE
ACL Type Matching Rule
Standard ACL Only matching the source IP address
Extended ACL Matching the following items: source IP address, destination IP address,
IP protocol types, Transfer Control Protocol (TCP) source port number, TCP
destination port number, User Datagram Protocol (UDP) source port number,
UDP destination port number, Internet Control Message Protocol (ICMP) type,
ICMP Code, Differentiated Services Code Point (DSCP), Type Of Service (ToS)
and Precedence
Layer 2 ACL Matching the following items: source MAC address, destination MAC address,
source VLAN ID, Layer 2 Ethernet protocol type and 802.1p priority
Hybrid ACL Matching the following items: source MAC address, destination MAC address,
source VLAN ID, source IP address, destination IP address, TCP source port
number, TCP destination port number, UDP source port number and UDP
destination port number

iii. Input the rule ID (in the range of 1~1000) and source IP
address. Select the active style. Users can click to select
a time range. Click Ok to finish adding an ACL rule.
iv. Click OK in Figure 58. The new ACL is displayed in the list.
3. Click on the tool bar. A dialog box with auditing result ap-
pears. Information in red is the differences between the data-
base and the NE.
4. Bind an ACL to a physical interface.
i. Select an ACL and then click in the list. A dialog
box appears, as shown in Figure 60.
FIGURE 60 ACL INTERFACE BOUND
ii. The ACL has been bound to an interface. Select In Direc-

tion or Out Direction. An ACL can be bound to several
interfaces. Click OK to close the dialog box. The Status of
the ACL is “Not Saved”.
5. Configure ACL rule.
i. Select a ACL to configure from the Switch ACL Config
interface, the related ACL rule is shown.
ii. Click , a dialog box about creating ACL rule appears.

Here, take extended ACL rule as an example. Figure 61

shows how to create extended ACL rule. Enter Rule ID,

select IP Protocol and Source IP Address and so on,
click Ok.
FIGURE 61 CREATE EXTENDED ACL RULE
iii. Click to modify the selected ACL rule, select to

delete the selected ACL rule, and click and to move
the selected ACL rule.
User And Account

This topic describes hot to add, modify and delete user names and
authorities on devices. At present, user authority configuration
is supported by ZXR10 8900 series switches (V4.08.30) and IP
1. Click Security Management > User and account on the
resource configuration management topology tree. Current
users and authorities are displayed.
2. Click Select Device. A dialog box for device selection appears.
Select a device. If there are user names and user levels in
the device, the information will be displayed. Otherwise, no

3. Click Create to add a user. A window appears, as shown in

Figure 62.
FIGURE 62 ADD USER
4. Input the user name and password. Select the user level. The
range of user level is 1~15. The default value is 1. Bind differ-
ent levels to different users. The lower user level is, the less
commands are available for the user. The higher user level is,
the more commands are available for the user. Usually, the
user level of administrators are 15, that is, administrators can
use all commands. Users of other levels only can use a few
maintenance commands. Click OK to finish adding a user.
5. Select a user in the list and then click Modify to modify the
user authority configuration.
6. Select a user in the list and then click Delete to delete the
user.

Chapter 7
Operation and
Maintenance
Table of Contents
Virtual Circuit Test .............................................................99
Loop Test ....................................................................... 100
CFM Configuration ........................................................... 101
Ethernet OAM ................................................................. 110
MPLS OAM TRACE............................................................ 112
Performance Monitor ........................................................ 115
BFD ............................................................................... 121
Zero-Touch Deployment ................................................... 124
Configuration Template Managemet ................................... 129
File Management ............................................................. 134
Virtual Circuit Test

Virtual Circuit Test (VCT) uses Time Domain Reflectometry (TDR)
to diagnose circuit. In this way, the error state of circuit can be
diagnosed, such as Open, Short and Impedance Mismatch, Good
termination, and the position of error can be calculated according
to the certain formula.
At present, VCT is supported by IP transmission platform products,
ZXR10 8900 series 10 Gigabit MPLS routing switch and ZXR10
8900 series 10 Gigabit routing switch, all low-end switches. VCT
applies for Ethernet electrical interfaces.
1. To show the current VCT information, click Operation & Main-
tenance > VCT > VCT on the resource configuration manage-
ment topology tree.
2. Click on the VCT interface, the Device Selection interface

appears.
3. Select the NE to be uploaded, and click OK, the Upload Con-
figuration From Device interface appears.
4. Select the NE to be uploaded from Instance List, and then
select the corresponding action from Operation Policy to add,
remove or modify the inconsistent resources in the database
and NE. Click Execute to upload.
5. Select one or more interfaces and then click , server per-

forms VCT to the selected interface, and the status is “Test-

ing”. The test result will be displayed and the status will be
“Test Successfully” after wait a moment.
Loop Test
Port loop detection is used to detect whether switch port has loop.
Port has loop, which causes MAC address learning error, broadcast
storm and switch or network paralysis. Use loop detection on a
port, disable the port which has loop, which can easily release the
influence caused by port loop.
Working mechanism of port loop detection is that a switch sends a
detection packet from a port, and if the packet is received by the
port without any change or only with a tag header that means the
port has loop.
The detection packet sent by switch contains the following three
parameters,
� Source MAC address: switch MAC address, and the MAC ad-
dress of every switch is unique.
� Port number: Port number corresponds to the ID of port on
switch one by one.
� VLAN ID: VLAN ID corresponds to the VLAN ID enabled by port
on switch one by one.
� Identifier area: The numeric signature of every switch and ev-
ery port is unique.
If the four parameters containing in the packet sent by and re-
ceived by a port are total same, the port has loop.
At present, port loop detection is supported by IP transmission
platform product, ZXR10 8900 series 10 Gigabit MPLS routing
switch and ZXR10 8900 series 10 Gigabit routing switch, all
low-end switch.
Configuring time parameters

1. Click Operation & Maintenance > LoopDetect > Time Pa-
rameter Configuration on the resource configuration man-
agement topology tree.
2. Click to obtain the latest configuration of time parameters

form database.
3. The black items can be double-clicked directly to modify.

Chapter 7 Operation and Maintenance
Configuring Loop Port

1. Click Operation & Maintenance > LoopDetect > Loop Port
Configuration on the resource configuration management
topology tree.
Loop port parameters are described in Table 17.
TABLE 17 LOOP PORT PARAMETERS
Status Port loop configuration,

synchronized, unsaved or
saved.
Display Name Enable or disable port loop

detection function
Operation Status Port operation status, normal,

protect and block.
VLAN List It shows which VLANs are

permitted to use loop detection.
View Alarm When loop detection is enabled

on a port on a NE, the port
will send detection packet
every once in a while to detect
whether has loop. Alarm is
generated if the port has loop.
The alarm can be queried in
detail.

3. Click to obtain the latest configuration of time parameters

form database.
4. The black items can be double-clicked directly to modify.
CFM Configuration
IEEE 802.1ag standard, that is, the Connectivity Fault Manage-
ment (CFM) function, is a draft of Institute of Electrical and Elec-
tronics Engineers (IEEE) at present. This function mainly aims at
management of “service” level. It provides easy and fast function
for fault discovery, detection and management on networks. It is
effective for users to check and isolate VLANs and generate fault
reports.
At present, ZXR10 8900 series switches of V4.08.22 and V4.08.30
and IP transmission platform product.

Enabling Global CFM

This topic describes how to view global CFM configuration infor-
mation of NEs.
1. Click Operation & Maintenance > CFM > Enable Global
CFM on the resource configuration management topology tree.
Global CFM information is displayed.
2. Click on the tool bar. A dialog box appears. Tick the check
boxes before the devices to upload, and then click OK. The
devices selected are displayed in the list on the Enable Global
CFM tab page.
For example, double-click the Enable Global CFM column to
modify the information.
Domain Resource Configuration
Configuring an MD
Through Maintenance Domain (MD) management, users can cre-
ate, upload, deploy, audit, delete and dismount an MD.
1. Click Operation & Maintenance > CFM > Domain Re-
source Config > MD on the resource configuration manage-
ment topology tree. MD information is displayed.
Figure 63. Input the MD name and level (in the range of 0~7).
Click the pull-down arrow of Device Name to select an NE.
When users do not input the MD index, the system will config-
ure an index for the NE automatically (in the range of 1~16 and
the index increments). If there is a vacant index, the vacancy
is complemented. Device name and MD index are displayed in
the list. Users can click to delete the information in the list
and select an NE to create an MD again. The items with “*”
are required to fill in. Click Apply to apply the configuration to
the database.

FIGURE 63 CREATE MD
3. Click on the tool bar. A dialog box appears. Tick the check
boxes before the devices and then click OK. The devices se-
lected are displayed in the list.
4. Select a piece of MD information and then click on the tool
bar. A dialog box for MD modification appears. Users can add
or delete NEs in the MD, or modify the MD index corresponding
to an NE. Click OK to finish the modification.
Configuring an MA
Through Maintenance Association (MA) management, users can
create, upload, deploy, audit, delete and dismount an MA.
source Config > MA on the resource configuration manage-
ment topology tree. MA information is displayed.
Figure 64.

FIGURE 64 CREATE MA
Select an MD created and input the MA name. Select an NE in

the pull-down list of Device Name. When users do not input
the MA index, the system will configure an index for the NE au-
tomatically (in the range of 1~32 and the index increments).
If there is a vacant index, the vacancy is complemented. Input
the primary VLAN (in the range of 1~4094) of the MA. Config-
ure CCM interval. The interval can be 3ms, 10ms, 100ms, 1s,
10s, 60s or 600s. The protection mode is “VLAN”. The new MA
is displayed in the list. Users can click to delete information
in the list and create an MA again. The items with “*” are re-
quired to fill in. Click Apply to apply the configuration to the
database.
Configuring an MEP
Through Maintenance association End Point (MEP) management,
users can create, upload, deploy, audit, delete or dismount an MEP.
source Config > MEP on the resource configuration manage-
ment topology tree. MEP information is displayed.
Figure 65.

FIGURE 65 CREATE MEP
3. Click the pull-down lists to select an MD, an MA and a device.

The range of MEP ID is 1~8191. Set the MEP priority (in the
range of 0~7, with default value 7) and alarm lowest priority
(in the range of 1~5, with default value 1). Click OK to make
the configuration valid in the UMS. MEP Local Index in the
list is a local MP index (in the range of 1~64 and the index
increments) allocated to the MEP by the system automatically
when users create an MEP. The MP is unique in an MA in a
device.
4. Select a piece of MEP information and then click on the tool
bar. A dialog box appears, as shown in Figure 66.

FIGURE 66 CREATE LBM
The values of MD, MA and source MEP ID are the information in

MEP list. Users do not need to input the values. Select to fill in
a destination MEP ID, a destination MEP MAC or a destination
MIP MAC. Input the counts and time-out values. The ranges of
the values are shown in Figure 66. Click OK to finish Loopback
Message (LBM) creation.
5. Select a piece of MEP information and then click on the tool
bar. A dialog box appears, as shown in Figure 67.

FIGURE 67 CREATE LTM
The values of MD, MA and source MEP ID are the information in

MEP list. Users do not need to input the values. Select to fill in a
destination MEP ID, a destination MEP MAC or a destination MIP
MAC. Input the Time To Live (TTL) and time-out values. The
ranges of the values are shown. Click OK to finish Linktrace
Message (LTM) creation.
Configuring an RMEP
Through Remote Maintenance association End Point (RMEP) man-
agement, users can create, upload, deploy, audit, delete and dis-
mount an RMEP.
source Config > RMEP on the resource configuration
management topology tree. RMEP information is displayed.


Figure 68.
FIGURE 68 CREATE RMEP
Select an MD, an MA and a device name in the pull-down lists.

Input the RMEP ID and RMEP MAC. Click Apply to apply the
configuration to the database. The Local RMEP Index is a
local MP index (in the range of 1~64 and the index increments)
allocated to the RMEP by the system automatically when users
create an RMEP. The MP is unique in an MA in a device.
Configuring an MIP
Through Maintenance domain Intermediate Point (MIP) manage-
ment, users can create, upload, deploy, audit, delete and dismount
an MIP.
source Config > MIP on the resource configuration manage-
ment topology tree. MIP information is displayed.
Figure 69.

FIGURE 69 CREATE MIP
3. Select an MD, an MA and a device name in the pull-down lists.

Input the MIP name. The item with “*” is required to fill in.
Click Apply to apply the configuration to the database. The
Local RMEP Index is a local MP index (in the range of 1 ~ 64
and the index increments) allocated to the MIP by the system
automatically when users create an MIP. The MP is unique in
an MA in a device.
LBM Management
This topic describes how to view all LBM information in the system.
Users can send designated LBM configuration information through
LBM management.
1. Click Operation & Maintenance > CFM > LBM Manage-
ment on the resource configuration management topology
tree. LBM information is displayed.
2. Select one or several pieces of LBM information in the list and
then click on the tool bar. A dialog box appears. The LBM
check result is displayed.
3. Select one or several pieces of LBM information in the list and
then click on the tool bar. A dialog box for confirmation
appears. Click Yes to delete the selected LBM configuration.

LTM Management
This topic describes how to view LTM information in the system.
Users can send designated LTM configuration information through
LTM management.
1. Click Operation & Maintenance > CFM > LTM Manage-
tree. LTM information is displayed.
2. Select one or several pieces of LTM information in the list and
then click on the tool bar. A dialog box appears. The LTM
check result is displayed.
3. Select one or several pieces of LTM information in the list and
then click on the tool bar. A dialog box for confirmation
appears. Click Yes to delete the selected LTM configuration.
Ethernet OAM
Ethernet technologies have developed rapidly in recent years. The
proportion of Ethernet network architectures is increasing. Eth-
ernet devices are used widely on access networks, convergence
networks and backbone networks. Therefore, OAM functions in
Ethernet devices become a focus. The main protocols related to
Ethernet OAM are listed below.
� IEEE 802.3ah (Operations, Administration, and Maintenance-
OAM)
� IEEE 802.1ag (Connectivity Fault Management) (draft)
� ITU-Y 1731 (OAM functions and mechanisms for Ethernet
based networks) (draft)
IEEE 802.3ah mainly aims at the management of “link” level. It
can be used to monitor and handle faults on point-to-point (or
virtual point-to-point) Ethernet links on networks.
At present, Ethernet OAM is supported by ZXR10 8900 series
switches (V4.08.22), IP transmission platform product and ZXR10
2900 series switches (after V2.0.11), ZXR10 ZSR intelligent
integrated multi-service routers (after V2.8.11).
Device Global Configuration

This topic describes how to view OAM global configuration infor-
mation of NEs and modify the configuration.
1. Click Operation & Maintenance > Ethernet OAM > De-
vice Global Config on the resource configuration manage-
ment topology tree. All OAM global configuration information
of NEs is displayed.

2. Select an NE in the Device pull-down list box and select “dis-

able” or “enable” in the pull-down list of OAM Enable. Set the
search conditions and then click on the tool bar. The search
result is displayed in the list.
3. Click on the tool bar. Search conditions are cleared. All OAM
global configuration information is displayed.
4. Users can modify the information in black in the list directly. For
example, double-click OAM Enable and Loopback Timeout
to modify the values.
comes “Saved”.
Device Port Configuration

This topic describes how to view and modify NE port OAM config-
uration information.
1. Click Operation & Maintenance > Ethernet OAM > Device
Port Config on the resource configuration management topol-
ogy tree. All port OAM configuration information is displayed.
2. Select a device in the Device pull-down list box and select a
port in the Port Name pull-down list box on the tool bar. Click
. The search result is displayed in the list.
3. Users can modify the information in black in the list directly.
For example double-click Enable Port, Period, Port Mode or
Port Timeout to modify the values.
comes “Saved”.
Remote Loopback
This topic describes how to view port basic information and re-
mote loopback information. Users can enable or disable remote
loopback and refresh the results.
1. Click Operation & Maintenance > Ethernet OAM > Re-
mote Loopback on the resource configuration management
topology tree. Remote loopback information is displayed.
will be displayed.
3. Click on the tool bar to obtain the port information discov-
ered successfully last time.
4. Before remote loopback is enabled, the remote loopback infor-
mation is shown. The Loopback Status is “off”.

5. Select a piece of remote loopback information and then click

on the tool bar. The system begins to initialize loopback.
6. Wait for 10 seconds. Remote loopback will be enabled suc-
cessfully. The remote loopback status of the master end is “on
(Master)”, and the remote loopback status of the slave end is
“on (Slave)”. Users can view the numbers of loopback mes-
sages sent and received at the master end.
7. Select the master loopback and then click on the tool bar
to disable the current loopback. The loopback is in terminat-
ing status. Wait for 10 seconds. The remote loopback will be
disabled successfully.
8. For the search function, please refer to the contents in Device
Global Configuration.
Link Monitoring
This topic describes how to view port basic information and link
event information. Users can enable or disable link monitoring
and refresh results.
1. Click Operation & Maintenance > Ethernet OAM > Link
Monitor on the resource configuration management topology
tree. OAM link information is displayed.
will be displayed.
3. Click on the tool bar to obtain the port information discov-
ered successfully last time. The information is refreshed auto-
matically every 10 seconds. The numbers of different types of
error frames are displayed.
4. Select a piece of link information in the list and then click
on the tool bar to enable link monitoring on the link. A dialog
box with information indicating success or failure will appear.
5. Select a piece of link information of which the link monitoring
is enabled in the list and then click on the tool bar. The
link monitoring will be disabled. A dialog box with information
indicating success or failure will appear.
6. For the search function, please refer to the contents in Device
Global Configuration.
MPLS OAM TRACE

MPLS OAM is an easy and effective method to detect faults on
MPLS LSP data plane. It can find the faults that cannot be found
by the control plane. With this method, users can find the faults
such as route black hole and route loss in a short time.
At present, MPLS OAM TRACE is supported by ZXR10 8900 series
switches (V4.08.22), IP transmission platform products.

Configuring MAC TRACE

MAC TRACE provides a method to monitor performance and de-
tect errors at MAC layer. MAC TRACE operations include creating,
modifying, deleting, refreshing and starting.
1. Click Operation & Maintenance > MPLS OAM TRACE >
MAC TRACE on the resource configuration management topol-
ogy tree. MAC TRACE information from No.0 hop to No.9 hop
is displayed.
2. Create a MAC TRACE.
Figure 70.
FIGURE 70 CREATE MAC TRACE 1
ii. Input the MAC TRACE name. Click after Source Device
IP text box to select a source device. Select “CE” in the
pull-down list of Source Device Role. Select an interface
in the pull-down list of Source Device Outband Interface
Index. Input the destination device MAC address. Tick the
check boxes of both Internal Vlan ID and External Vlan
ID, or tick the check box of External Vlan ID only, or tick
the check boxes of neither Internal Vlan ID nor External
Vlan ID. Click Ok to finish MAC TRACE creation.
iii. In Figure 70, select “PE” in the pull-down list of Source
Device Role, and select “Outband Interface Trace” in the

pull-down list of Trace Type. Do not change other set-

tings. Click Ok to finish MAC TRACE creation.
iv. In Figure 70, select “PE” in the pull-down list of Source De-
vice Role, select “Vfi Trace” in the pull-down list of Trace
Type, and input the VFI name and pseudo-wire peer IP. Do
not change other settings. Click Ok to finish MAC TRACE
creation.
3. Select a piece of MAC TRACE information in the list and then
click on the tool bar. The system will prompt start success
or failure in the Status column in the list.
Configuring MPLS TRACE

This topic describes how to view the configuration of MPLS TRACE.
The operations of MPLS TRACE include creating, modifying, delet-
ing, refreshing and starting.
1. Click Operation & Maintenance > MPLS OAM TRACE >
MPLS TRACE on the resource configuration management
topology tree. MPLS TRACE information from No.0 hop to
No.9 hop is displayed.
2. Create an MPLS TRACE.
Figure 71.
FIGURE 71 CREATE MPLS TRACE 1
The parameters are described in Table 18.

TABLE 18 MPLS TRACE PARAMETER DESCRIPTIONS
Mpls Trace Name It is the name of MPLS TRACE, within 10 letters and numbers.
Source Device IP It is the IP address of source device. Click to select NEs.
Trace Type It is the TRACE type, including LDP Trace and Rsvp-Tunnel Trace.
LDP Dest Net Segment It is the destination address of LDP LSP.

IP
LDP Dest Net Segment It is the LDP LSP destination mask, in the range of 1~32.
Mask Length
Timeout It is the time-out, in the range of 1~60, in unit of second.
TTL It is the TTL, in the range of 1~255.
ii. Input the parameter values and then click Ok to finish MPLS
TEACE creation.
iii. Select “Rsvp-Tunnel Trace” in the pull-down list of Trace
Type, and select an interface in the pull-down list of Tun-
nel-Interface Index. Do not change other settings. Click
Ok to finish MPLS TEACE creation.
3. Select a piece of MPLS TRACE information in the list and then
click on the tool bar. The system will prompt start success
or failure in the Status column in the list.
Performance Monitor
Performance monitoring provides monitoring function of packet
sending delay, flapping and packet loss rate between a source NE
and a destination NE. The source NE and destination NE can be
either connected directly or indirectly.
Performance monitoring is supported by high-end routers, ZXR10
8900 series 10 Gigabit MPLS routing switch and IP transmission
platform products.
Task Matrix
Configure ping 1. To show all tasks as list, select Task List tab.
task
2. To create a detection task, click on tool bar, as shown in
Figure 72.

FIGURE 72 CREATE PINGTASK
3. Enter TaskGroupName select pingType common ping, vrf

ping and mac outlf ping, mac vfi ping and ldp ping, resptunnel
ping, vpls ping) and the related PingParameter, set Start
Time and EndTime. Click OK to finish.
Configure task 1. Click on the tool bar. A window appears, as shown in Figure
matrix 73.
FIGURE 73 CREATE PING TASK GROUP
2. Input the task group name (letters and numbers only, not more
than 10 characters) and select a ping type. Click the Select
Source. A dialog box appears, as shown in Figure 74.

FIGURE 74 SELECT SOURCE
3. Select the source NE and then click Ok and then click Select
Dest in Figure 73. A window appears, as shown in Figure 75.
FIGURE 75 SELECT DESTINATION
4. Select the destination NE and then click Ok. The source and
destination addresses are displayed.
Note:
Users can create 10 task groups at most, with 10 destination
addresses at most for each task group. That is, up to 100
sub-tasks can be created. Therefore, it is called a task matrix.

5. Click SelectPara, as shown in Figure 76.
FIGURE 76 SELECT PARAMETER
6. A dialog box appears, as shown in Figure 77.
FIGURE 77 SELECT PARAMETER MODEL
� nowCell means applying the parameter model to the se-

lected cell.
� nowSelRow means applying the parameter model to the
row that the selected cell is in.
� allcell means applying the parameter model to all cells in
the task matrix.
Click Ok button after the selection. Click . The interface Cre-
ating Parameter Template appears. For the detailed opera-
tion, please refer to Task Parameter.

Note:
A parameter model must be created before user configure a
task matrix. Otherwise, no parameter model can be selected.
7. Select the start time and the end time and then click Create
in Figure 76. If there are sub-tasks in a task group, sub-task
information will be displayed in TaskMatrix pane. A task ma-
trix is created.
8. Select a task to be deleted and then click .
Task Parameters
1. Click Operation & Maintenance > End To End Test > Task
> Task Parameter on the resource configuration manage-
ment topology tree. Task parameter information is displayed.
78. Input the ParaModelName and SendPacketCounts.
Click Create.
FIGURE 78 CREATE PARAMETER MODEL
3. To refresh model information, click on the tool bar.

Result Matrix
1. Click Operation & Maintenance > End To End Test > Re-
sult > Result Matrix on the resource configuration manage-
ment topology tree. The result matrix information is displayed.
2. Select the TaskGroupName, Index (packet loss ratio,
timedelay and jitter) and Statistics Type (MaximumValue,
MinimumValue and AverageValue, thresholdvalue). Thresh-
old Value is the percentage of the selected parameters. For
example, packet loss ratio is 50%, then input 50 in the text
box of ThresholdValue. Minvalue, Maxvalue and Average
are the minimum, maximum or average value of the generated
result. Granularity has five options, hour, week and day,
month and year. After setting, click to display the result, as
shown in Figure 79.
FIGURE 79 DISPLAY RESULT MATRIX
3. Right-click at task matrix. Select Result List from the pop-up

menu, system will navigate to the result list corresponding to
the task matrix.
Result List
sult > Result List on the resource configuration management
topology tree. The result list is displayed.
2. To generate result list, select Task, StatisticsType and
TimeRange, and then click on the tool bar.
Result Graphic
sult > Result Graphic on the resource configuration manage-
ment topology tree. The result graphic is displayed, as shown
in Figure 80.

FIGURE 80 RESULT GRAPHIC
2. To generate a graphic, select Task, Indicators and Statistics

Type, Granularity and TimeRange, GraphicType and then
click on the tool bar.
Result Deletion Policy

sult > Result Delete Policy on the resource configuration
management topology tree. Result Delete Policy tab is dis-
played.
2. Click Reset. Realtime(Days) is available for editing, the
range is 1 ~7. Modify the policy and then click OK. For ex-
ample, set Realtime(Days) as 2, then system will save the
report data of two days ago.
BFD
BFD is used to improve the speed of fault detection and recovery.
As a draft standard of Internet Engineering Task Force (IETF), BFD
provides an easy method to detect links or the ability to forward
transmission flows of the system.
BFD provides invalidation detection between systems of different
types, including direct-connected physical links, virtual links, tun-

nels, MPLS LSPs and multi-hop routing paths. BFD can be un-
derstood as a simple “Hello” protocol. Many aspects of BFD are
similar with the detection part of routing protocols. A pair of sys-
tems send BFD messages on each path periodically. If a system
cannot receive the message from the other system during a period
long enough, it is certain that a fault occurs on the bidirectional
path between the systems. In some situations, the systems can
negotiate with each other not to send BFD messages periodically
to decrease load.
At present, BFD function is supported by IP transmission platform
products.
BFD Global Configuration

This topic describes how to view BFD global configuration infor-
mation. Users can upload, deploy, save and refresh BFD global
configuration information.
1. Click Operation & Maintenance > BFD > BFD Global Con-
fig on the resource configuration management topology tree.
BFD global configuration information is displayed.
will be displayed.
3. Select an NE in the pull-down list of NE Tree and then click
on the tool bar. Wait a moment. BFP global configuration
information in the selected NE will be displayed in the list.
Note:
If the status of the NE selected is off, system will prompt that
“The NE selected must be on”. If users select several NEs
among which some are on and some are off, the NEs in off
status will be filtered during uploading.
4. Select a piece of BFD global configuration information of which

the status is “Saved” and then click on the tool bar. The
result of correct deployment will be displayed.
5. Users can modify the BFD global configuration information in
the list. After modification, the status of the information is “Not
Saved”. Click on the tool bar. The status of the information
becomes “Saved”.
BFD Session
This topic describes how to view BFD session information. Users
can create, delete, dismount and upload BFD session information.
1. Click Operation & Maintenance > BFD > BFD Session on
the resource configuration management topology tree. BFD
session information is displayed.


Figure 81. Input the parameter values and then click Create.
A dialog with information indicating creation success or failure
will appear.
FIGURE 81 CREATE BFD SESSION
The parameters of BFD session are described in Table 19.
TABLE 19 BFD SESSION PARAMETER DESCRIPTION
NE It is used to select an NE in teh pull-down list. The operations in

Local area and Remote area are the same.
Interface Name It is used to select an interface in the pull-down list.
Interface Address It is used to input the address of corresponding interface.
Protocol Type It is to select an application protocol supported by BFD session. In

the pull-down list, there are STATIC ROUTE, BGP, ISIS, OSPF, PIM,
PW and RSVP LSP.
Min Tx Interval It is to set the minimum interval to transmit a BFD message. It is in

the range of 10~900 and in unit of millisecond.
Min Rx Interval It is to set the minimum interval to receive a BFD message. It is in

the range of 10~900 and in unit of millisecond.
Detect Multiple It is in the range of 3~50.
3. Select an NE in the pull-down list of NE Tree and then click

on the tool bar. Wait a moment. The BFD session information
to upload to the NE will be displayed in the list.

BFD Performance
This topic describes how to monitor the performance information
of BFD sessions.
Click Operation & Maintenance > BFD > BFD Performance
on the resource configuration management topology tree. BFD
performance information is displayed. The system refresh the in-
formation saved in the database every 10 seconds.
Note:
If there is no BFD session, there will be no BFD performance in-
formation.
Zero-Touch Deployment
Context Zero-Touch deployment service means that version file and config-
uration file of middle/low-end switch are saved in the Zero-Touch
deployment server.
Middle/low-end switch can communicate with Zero-Touch deploy-
ment server by private protocol and get version and configuration
from Zero-Touch deployment server.
The purpose is to upgrade running version of middle/low-end
switch in batch and configure the middle/low-end switch in batch
to help user lower the intensity of work and maintenance cost.
Steps 1. Select Operation & Maintenance > Zero-Touch Deploy-
tree to enter Zero-Touch Deployment interface.
2. Click button, export device list by Excel format. The list

includes operation, Admin Status, MAC, NE Type and so on.
3. Click to configure parameters. Enter Zero-Touch Deploy-

ment Parameters interface, as shown inFigure 82. After con-
figuration is completed, click OK to popup the dialog box that
means configuration is successful. Zero-Touch Deployment
server demands: TFTP uses the one accompanied by network
management. FTP not only can use the one accompanied by
network management but also can use third-party FTP server.
(premise : device and Zero-Touch deployment server can be
visited.

FIGURE 82 ZERO-TOUCH DEPLOYMENT PARAMETERS
4. Click button, directly create a piece of configuration infor-

mation in the list. In the list, directly modify MAC address, NE
type, file transmission protocol(including FTP and TFTP), NE
management IP. Only when the legal mac is inputted, it can be
saved.

Note:
Please strictly use the template to configure Zero-Touch De-
ployment NE. MAC must not be null but legal. Otherwise this
line of date cannot be imported for operation.
When NE is created, copied or saved on the panel, mac must
not be null but legal, and same macs do not exist.
If network management is Chinese, use Chinese template. If
network management is English, use English template.
5. Click button to bind configuration file, as shown in Figure

83. Configuration template can be got from network manage-
ment or local. Click From local, select existent configuration
template file in list, configuration script detailed information
will appear at the bottom of page, click OK, prompt that bind-
ing configuration file is successful.

FIGURE 83 BIND CONFIG FILE
6. Click , or select the multiple lines with the same

NE type and then click button to enter Bind version file
interface, as shown in Figure 84. By default, select From ver-
sion warehouse, click one line in list to view the information
in the version. Click From local, select zar file in local file di-
rectory, the version information is viewed below. The method
of configuring script file is similar with that of configuring ver-
sion file. Please refer to version file configuration method.

FIGURE 84 BIND VERSION FILE
7. Click Server Status > Start Server button to start Zero-

Touch Deployment server. Vlan1 address and Zero-Touch De-
ployment server are acquired from dhcp server and start Zero-
Touch Deployment procedure.
8. If Zero-Touch Deployment fails, click button to open Zero-

Touch Deployment log view reason.
END OF STEPS

Configuration Template
Managemet
Configuration Template Overview
Configuration template management includes common template.
There are two default sorts, SNMP configuration and STP config-
uration. Users can define general template according to their re-
quirements. The configuration processes of different templates
are the same. Here, take SNMP configuration as example.
The brief procedure to configure a template: create sort in com-
mon template, create templates in sort catalogs, and then add
configuration instances and deploy the instances.
Sort Operations
1. Right-click Common Template and select New Sort from the
shortcut menu. A dialog box appears, as shown in Figure 85.
Input the sort name and then click Ok. A new template sort
is created. SNMP configuration and STP configuration are cre-
ated already. Users also can define new sort according to their
requirements.
FIGURE 85 NEW SORT
2. Right-click a created sort on the resource configuration man-

agement topology tree. The shortcut menu is shown in Figure
86.

FIGURE 86 SHORTCUT MENU
3. Select Modify Sort from the shortcut menu. A dialog box ap-
pears. Users can modify the sort name. After modification,
click Ok.
4. Select Delete Sort from the shortcut menu. A dialog box ap-
pears. Click Ok to delete the sort.
Creating a New Template

Users can create templates in a sort.
1. Right-click the sort SNMP Config or other sorts, and select
New Template from the shortcut menu. A dialog box appears,

FIGURE 87 ADD NEW TEMPLATE
Another way is that click to create template.

2. Input the template name and script. Click Ok. A template is
created. By default, ROS 4.8 SNMP template, ROS4.6 SNMP
template and L-switch SNMP template. Users can use these
three templates directly or define new template according to
requirements.
Template Management
This topic describes how to configure the created template. Here,
take SNMP configuration as an example.
1. Right-click a template and select Modify Template from the
shortcut menu, or click on the SNMP Config tab page. A
dialog box appears. Users can modify the template name and
script. After modification, click Ok.
2. The information in black in the list can be modified directly on
the SNMP Config interface. Users can double-click Script and
Parameter to modify the information.
3. Right-click a template and select Delete Template from the
shortcut menu, or click on the tool bar on SNMP Config
tab page. A dialog box for confirmation appears. Click OK to
delete the template.

4. Right-click a template and select Copy Template from the

shortcut menu. A template with the same attributes is gener-
ated.
5. Select a template and click on the tool bar on SNMP Config
tab page. A dialog box appears. Input the number of copies
and then click Ok.
6. The background of the modified information is pink . Click
on the tool bar to save the data. The background becomes
normal.
Configuration Instance Management

This topic describes how to manage instance configuration. Here,
take ROS4.8 SNMP configuration template as an example.
1. Click the template named ROS 4.8 SNMP Config Template
on the topology tree on the lest, or double-click the template
in the list on SNMP Config tab page. A tab page is opened.
2. Click on the tool bar. A dialog box appears. Select NEs
and then click Ok. A configuration instance is created. It is
displayed in the list on ROS 4.8 SNMP Config Template tab
page.
3. In the list on the ROS 4.8 SNMP Config Template tab page,
the parameters defined in the configuration template are dis-
played. Users can double-click a parameter to modify the
value. The background of the modified information is pink.
The ranges of parameters are the same with that in Template
Management.
4. The background of the modified information is pink. Click
on the tool bar to save the data. The background becomes
normal.
5. Select a configuration instance and click on the configuration
template tab page. A dialog box appears. Input the number
of copies and then click Ok.
6. Select a configuration instance and click on the template
tab page. A dialog box for confirmation appears. Click Ok to
delete the instance.
7. Click a configuration instance and click on the template tab
page. A dialog box appears, as shown in Figure 88. The mod-
ified configuration is in green.

FIGURE 88 PREVIEW SCRIPT
Deploying a Configuration Instance

1. Select a configuration instance and click on the configuration
template tab page. A dialog box appears.
2. Set the execution mode. There are two modes, once and pe-
riod. By default, the task will be executed immediately. If users
do not want to execute the task immediately, they should mod-
ify the execution mode.
3. Click Ok to execute the task. Wait a moment. The status in
the instance list will become “Have synchronized”.
4. The task will be added to the task area. As two NEs are se-
lected, there are two tasks in the list.
Zero-Touch Deployment Template

Steps 1. Select Operation & Maintenance > Configuration Tem-
plate Management > Zero-Touch Deployment Template
on the resource configuration management topology tree to
enter Zero-Touch Deployment Template interface.

2. Click button to enter Modify Template interface, as shown

in Figure 89.
FIGURE 89 MODIFY TEMPLATE
3. Parameter can be modified and click ok.

END OF STEPS
File Management
File Management Overview
File management consists of version file management and config-
uration file management.
Version file management of IP NEs enables users to manage NE
versions easily. It helps user finish version upgrade and mainte-
nance of NEs in batch quickly and reliably.

Configuration file management of IP NEs means backing up, com-

paring, restoring and exporting configuration files of IP NEs. Users
can trace and maintain the configuration information of NEs in
batch easily.
Version File Management

Click File Management > Version File Management on the re-
source configuration management topology tree.
Version file management page is composed of NE area, file area
and task area.
The operations in the NE area include NE area operation, backing
up a version file, restoring a version file, restarting an NE, set-
ting the global option for version file management, obtaining the
information related to an NE, obtaining maintenance history infor-
mation of version file, managing files on an NE, and so on.
The operations in the file area include uploading a version file,
downloading file to local host, deleting a file, and so on.
The operations in the task area include modifying a task, operation
on a task, viewing task execution history, and so on.
The general principle to manage version files: All operations of NEs
are initiated from the NE area, and operations are executed by the
way of tasks. That is, tasks will be created in the task area when
users operate in the NE area. According to the user configuration,
tasks will be executed on time or periodically. Users also can tick
one task and click the Run immediately button.
Operations in NE Area
The operations in the NE area includes obtaining NE version infor-
mation and deleting an NE.
1. Click in the NE area on Version File Management tab page
to obtain NE information. The operations being operated are
displayed in the Current Operation list. NE version informa-
tion is also displayed.
2. In the NE area on Version File Management tab page, click
to delete the all current operations in the NE area.
3. In the NE area on Version File Management tab page, click
to delete the all current operations on the current page.
Backing up Version File

Backing up version file means backing up device version to file
repository of server.
1. Select NEs with the same type in NE area of Version File Man-
agement, click the backup version file button to pop up
the Backup Version File interface. The File And Device tab

views the NE and version to be backed up. By default, this tab

is not modified. If server has this version file, a prompt will be
present to indicate that backup can not be repeated.
2. Click the Option tab, as shown in Figure 90. Users can set the
items in this tab according to their own requirements. Select
Also backup show version information can back up show
version data at the same time.
FIGURE 90 BACKING UP VERSION FILE-OPTION
3. Click the Execute Manner tab, to configure execute manner of

task. The modes consists of once and period. By default, this
task will be started instantly. Otherwise remember modifying
the execute manner.
4. Click the OK button to start these two tasks. after a while,
popup the dialog box about adding backup version file suc-
cessfully.
5. At this time task will be added to task area.
Restoring Version File

Restoring version file means restoring the version file at local or
in file repository (file repository is stored in NM server installation
directory and is used to save file version) to NE.
agement, click the restore version file button to popup

the Restore Version File interface.

2. Select the file to be restored From local file or From version

file repository, the version file repository location is backup
file storage address. Take From local file as an example.
Click the button to select the version to be restored
from local file. The ROS version and device version also can
be input manually, the Selected Device area lists the NEs to
be restored.
3. Click the Option tab. Users can set the items in this tab ac-
cording to their own requirements. By default, this tab is not
modified.
task. The manners consists of once and period. By default, this
the execute manner.
5. Click the OK button to start these two tasks. after a while,
popup the dialog box about restoring version file successfully.
6. At this time, tasks will be added in task area. Because the two
NEs are selected the two tasks will be newly added in task list.
Rebooting NE
Rebooting NE means rebooting device on NE for user's convenient
management.
agement, click the reboot NE button to popup the Reboot

NE interface. File And Device tab views the NE to be re-
booted. By default, this tab is not modified.
2. Click the Option tab, as shown in Figure 91. Users can set
the items in this tab according to their own requirements. By
default, this tab is not modified.
FIGURE 91 REBOOTING NE-OPTION


task. The manner consists of once and period. By default, this
the execute manner.
4. Click the OK button to start these two tasks. After a while,
the popup will indicate that adding the task of rebooting NE is
successful.
5. At this time task will be added to task area.
Configuring Global Option of Version File

Management
After setting global option of version file management, the task to
be established will take the configuration option as default option.
If a task need special task option, modify when task is established
or modify in task area after task is established.
1. In the Version File Management tag, click the button to

popup the Global option for version file interface, as shown
in Figure 92. Configure global option for version file of high-end
switch and router according to real requirement. It is recom-
mended to use the default value.

FIGURE 92 VERSION FILE GLOBAL OPTION- HIGH-END SWITCH AND ROUTER
2. Click the Low switcher tab, as shown in Figure 93. Configure

global option for version file of low-end switch according to real
requirement.

FIGURE 93 VERSION FILE GLOBAL OPTION- LOW-END SWITCH
Getting the Related Information of NE

The following contents introduce how to get the information of
show running, show start running and show version.
1. Select a NE in NE area of Version File Management, click
to popup the Getting running config success interface

to get the information of show running, as shown in Figure
94.

FIGURE 94 GETTING RUNNING CONFIG SUCCESS
to popup the Getting start config success interface to

get the information of show start running.
to popup the Getting show version success interface

to get the information of show version.
Managing Files on an NE
1. Select an NE in the NE area on the Version File Management
tab page and then click on the tool bar. A window appears.
2. Users can double-click drwx in the list to view the files in the
direction. The detailed information is displayed at the bottom
pane of the window. Users can create a new direction, rename
a file or delete a file on this window.

Uploading Version File

Uploading version file means uploading version file to server in file
area.
1. In the file area of Version File Management, click to

popup the Upload version file to server interface.
2. Click in NE type to select NE type to be uploaded, click

in Select file to select NE version file at local to be
uploaded, input ROS version and device version, as shown in
Figure 95.
FIGURE 95 UPLOADING VERSION FILE TO SERVER
3. Click the Upload button. After a while, popup the prompt

which indicates that uploading is successful. The version up-
loaded successfully is viewed in file area.
Downloading Version File to Client

Downloading version file to client means downloading version file
to client in file area.
1. Select the version file to be downloaded to client in file area of
Version File Management, click to popup the Download
file to client interface.
2. Click the button to select saving address, click the

Download button to popup the message of downloading
successfully.

Deleting a File
Select a file in the file area on the Version File Management tab
page and then click on the tool bar. A dialog box for confirma-
tion appears. Click Yes to delete the file. Click No to cancel the
deletion.
Querying NE According to Version Number

Select a version file from Version File Repository on the Version
File Management tab page, and then click to list the NEs
which relate to the version file. Click to clear the query result.
Managing Version File Status

This topic describes how to define status to every version file on
version file database. There are four status,
1. Select a version file from Version File Repository on the Ver-
sion File Management tab page, and then click to audit
version file status. Table 20 describes the status in detail.
TABLE 20 VERSION FILE STATUS
Status Description
Online It means that the file is being

used by a online NE.
Prepared It means that the file has not

been used by a online NE but
it is a valid version file by
certification. The file can be
used at any time.
Discard This status is defined by user. It

means that the version file will
not be used for a while.
Offline It means that the version file

does not pass certification. The
version file can not be used
as NE version file. Since a
version file is checked when it
be restored, this status appears
seldom.
2. Select a version file from Version File Repository on the Ver-
sion File Management tab page, and then click to change

status. User can change the status prepared into discard and
also can change discard into prepared.

Downloading Detailed NE Version Information

This topic describes how to download detailed NE version informa-
tion. It is a periodic backup mechanism, which records backup file
every time. User can view history NE version information.
1. To download a detailed version file information, select a ver-
sion file from NE Version Details on the Version File Man-
agement tab page, and then click , the Download file to
client interface appears.
2. Click to select saving address, and then click Down-

load, a dialog box appears.
Viewing Detailed NE Version File Information

Detailed NE version file is a return string after show version com-
mand is used. User can view version file information of the se-
lected NE in detail by text.
Select the version file to be viewed from NE Version Details on
the Version File Management tab page, and then click . The
Text Editor interface appears. User can edit the detailed version
file information on the interface.
Modifying a Task
Modifying a task means modifying task option and executing mode.
Task option includes version file name, configuration file name and
reboot option. Executing mode includes "once" and "period".
The tasks with same type NE and same task type can be modified
in bulk.
1. Select the task need to be modified in task area of Version
File Management, click to popup the Modify task option
interface. Click the OK button to finish modification.
2. Select the task to be modified in task area of Version File
Management, click to popup the Modify execute man-
ner interface. Execute mode and execute time can be modi-
fied, click the OK button to finish modification.
Task Operation
For task operation, the tasks of a running file can be started im-
mediately, paused and continued, deleted. For more information,
please refer to Task and Task History Operation.
1. Select a task from the Version File Management tab page,
history of the task is displayed at the right table.
2. Double-click a history item or click , the detailed history

information appears.

Configuration File Management

The interfaces and operations of configuration file management
are similar to those of version file. Some similar functions are not
introduced here. Only the unique operations of configuration file
are introduced in the following contents.
Backing up Configuration File

Backing up configuration file means backing up device configura-
tion file to file repository of server.
The procedure of backing up configuration file is same as that of
backing up version file. Refer to "Backing up Version File" for de-
tailed operation.
Exporting Lasted Configuration File

Exporting lasted configuration file means exporting the lasted con-
figuration file backed up to each NE of file repository during a pe-
riod time.
1. In the file area of Config File Management, click to popup

the Export lasted config file interface.
2. Select the NE to be exported, set the exporting time, click the
button to set the local address to which the file exports.
3. Click the Export button, after a while, the configuration file is
exported successfully to PC.
Rolling Back Configuration File

Same with restoring configuration file, rolling back configuration
file means restoring the configuration file backed up to file repos-
itory to devices.
1. Select NE with the same type in file area of Config File Man-
agement, click the rolling back configuration file button

to popup the Roll Back Config File interface. "File to be re-
stored" can use the configuration file on the interface.
2. Click the Option tab, as shown in Figure 96. Users can set
the items in this tab according to their own requirements. By
default, this tab is not modified.

FIGURE 96 ROLLING BACK CONFIGURATION FILE-OPTION
3. Click the Execute Manner tab, to configure executing mode of

task. The modes consists of once and period. By default, this
the executing mode.
4. Click the OK button to start these two tasks. After a while,
popup the dialog box about rolling back configuration file suc-
cessfully.
5. At this time tasks will be added to task area.
Designating a Benchmark File

A benchmark file is used as a reference when users backup a con-
figuration file.
For example, if there is a benchmark file on an NE, when users
back up the configuration file, the new file will be compared with
the benchmark file. If the two files are consistent, there are same
files. If the two files are not consistent, there are different files.
If there is no benchmark file on an NE, when users back up the
configuration file, the new file will be compared with the existing

configuration files. If one of the configuration files is consistent

with the new file, there are same files.
Select a configuration file in the file area on the Configuration
File Management tab page and then click on the tool bar. A
dialog box will appear, indicating that the file has been designated
as the benchmark file.
An NE can only have one benchmark file. When users select sev-
eral files as the benchmark file, the system will prompt that users
select duplicated NEs. If users designate several files as the bench-
mark file on an NE at different times, the last one will be designated
as the benchmark file.
Comparing Configuration File
1. In the file area of Config File Management, click to

popup the File Compare interface.
2. Click to popup the Choose files interface. Click the

Browse button to select the local files to be compared.
3. Click the OK button to finish. After a while, popup the com-
paring result, as shown in Figure 97. Green indicates added
content, red indicates deleted content, blue indicates modified
content.
FIGURE 97 FILE COMPARE RESULT

Editing Configuration File

This function is used to open a configuration file of server and edit
the configuration.
1. Select the configuration file to be opened in the file area of
Config File Management, click to popup the Text Editor

interface.
2. Directly add, delete, modify, save, search and replace in text
editor.
Patch File Management

Context Patch file management can implement patch file distribution, ac-
quire patch or NE-related information and configure file upload and
download.
Restoring Patch File

Steps 1. Click Performance Management > Performance Report
File Management > Patch File Management on the re-
source tree to enter Patch File Management interface.
2. Click button to enter Restore Patch File interface. Click

Local button to browse local file, select the patch file to be
restored.
3. In Restore Patch File interface, click Options to configure file
information on NE, transmission protocol and manage manner,

FIGURE 98 RESTORE PATCH FILE OPTION
4. In Restore Patch File interface, click Execute Manner to

configure once executing manner and period executing man-
ner. After configuration is completed, click OK button.
END OF STEPS
Managing NE
Steps
1. In Patch File Management interface, click button to enter
Manage Files on NE interface, as shown in Figure 99.

FIGURE 99 MANAGE FILES ON NE
2. In Manage Files on NE interface, the existent file directory is

viewed and the basic configuration including refreshing, newly
establishing directory, renaming and deletion can be imple-
mented by the buttons below the interface. Click Refresh but-
ton to view refresh log below the interface, which lists directory
name and free space.
3. In Patch File Management interface, the existent file can
be uploaded, downloaded and deleted. Click button to im-
port implement configuration file. Click button to download

patch file to local. Click button to delete the selected patch
file.
END OF STEPS

Chapter 8
Performance And Alarm
Table of Contents
Querying Performance...................................................... 151
Performance Report List ................................................... 152
Alarm Management.......................................................... 154
Querying Performance
For performance query, performance data can be queried, sum-
marized and comparison according to different time granularities.
1. Click Network Management > NE Information > NE Ba-
sic Information on the resource tree to enter the NE Basic
Information interface. Select Performance Query tag.
2. Set query condition. The first step of performance query is to
set query condition.
i. Click on the tool bar, the Setting query conditions

interface appears.
ii. Select resource instance, and then click Next to enter the
Performance indicators tag page.
iii. Group has ZXR10SystemUnitTable, NeUsgStat. Select
Group and then select Variable. Click OK to finish.
3. Query data.
i. Select query condition from the pull-down list of . There

are realtime, original and hour, day and week, month. An-
other way is that click directly to query the designated

time.
ii. System will display query result after query time range is
set. System will obtain data on time from server if user se-
lect Real-time Query > Start real-time query. At most
50 data items can be queried. Click Real-time Query >
Stop real-time query to stop periodic query.
4. Select the row to be shown by graphic, the graphic will
displayed immediately. The graphic will change with data
changes.
5. User can save query conditions and query time to favorite for
further usage.

i. Click , and then select Add to Favorites from the short-

cut menu, a dialog box appears. Enter name, and then click
OK.
ii. Click , and then click Apply to query the content to be

collected. Click Remove to delete the content to be col-
lected.
6. Server can save some query results of users. User can fast
switch the query result by using and .
Performance Report List

Performance Real Query
Context In performance list management, performance real query and re-
port list file management can be implemented. At present, the
function is only valid in IP transmission platform products.
In performance real query interface, exporting all views data, cre-
ating view, adding view to favorite folder, exporting dashboard to
template file, importing dashboard to template file, tiled layout
can be implemented.
File Management > Performance Real Query on the re-
source tree to enter Performance Real Query interface.
2. In toolbar, click to create view.

i. Select common TopN view, enter New View interface, as
shown in Figure 100. Select the content which needs sta-
tistics on the left of view, select count type and TopN search
mode. In count type, max, min, avg and sum can be se-
lected. In TopN, select the ranking number to be searched.

Chapter 8 Performance And Alarm
FIGURE 100 COMMON TOPN VIEW
ii. The method of creating low-end switch interface informa-

tion view and that of high-end switch interface information
view are similar. Take the low-end switch interface infor-
mation view as an example. Click Low-End Interface-
Info View to enter New View. The configuration method
of view is same to that of common TopN view.
iii. To create p2p detection view, enter New View interface.
3. After the view is created, enter Performance Real Query in-
terface. Select NE in group and query time, click Query button
to query related information.
4. Click button to add the view to favorite folder. Click

button to export dashboard as file in templ format. The file
of importing dashboard should be in templ format. Click
button to select horizontal layout according to group or vertical
layout according to group.
END OF STEPS

Report File Management

Context In Performance Report File Management interface, report file can
be downloaded, deleted and queried.
File Management on the resource tree to enter Report File
Management interface.
2. Select the template line number to be downloaded, click to

download report list file, click to delete the selected report
file. In Template Name, input the query condition to query
report list file.
END OF STEPS
Alarm Management
Alarm management can make users conveniently check device
alarms and real time alarms and provide root reason analysis. The
alarm function that resource configuration management provides
is only for search analysis. The detailed alarm management mod-
ule content refers to NetNumen Unified Network Management Sys-
tem Data Product User Manual (Performance and Alarm).

Figures
Figure 1 Resource Management Configuration Topology Tree .... 3

Figure 2 Resource Configuration Tree Toolbar Button ............... 4
Figure 3 User View Customization ......................................... 5
Figure 4 NE Infomation ......................................................10
Figure 5 Create Uni Interface ..............................................16
Figure 6 Cip Interface Management Creation .........................17
Figure 7 Interface Laser Information Interface.......................18
Figure 8 Creating ATM Interface ..........................................20
Figure 9 Create guide choose ..............................................21
Figure 10 Batch Create E1 Ports Interface .............................21
Figure 11 E1 Port Properties Change ....................................22
Figure 12 IMA Interface Manage ..........................................23
Figure 13 Create Port Protect Config ....................................26
Figure 14 Add Server .........................................................28
Figure 15 Add Server .........................................................29
Figure 16 ptp port create Interface ......................................30
Figure 17 Load Interface Data .............................................31
Figure 18 ptp global create Interface....................................32
Figure 19 Load Interface Data .............................................34
Figure 20 SSM Global Config ...............................................35
Figure 21 SSM Global Config Interface..................................37
Figure 22 Load Interface Data ............................................39
Figure 23 Create Link.........................................................40
Figure 24 Link Discovery Config...........................................41
Figure 25 Create Link Aggregation Port 2 ..............................44
Figure 26 Select Interface...................................................48
Figure 27 New VLAN Port Config ..........................................49
Figure 28 New VLAN Config Step 2.......................................50
Figure 29 Select ................................................................50
Figure 30 Modify VLANs in Batch Step .................................51
Figure 31 VLAN Translation .................................................52
Figure 32 New Selective VLAN Config 1 ................................53
Figure 33 Create VLAN Domain............................................55
Figure 34 Create VLAN Step 1 .............................................56

Figure 35 VLAN Service Discovery Management 1 ..................57

Figure 36 Add MAC Address ................................................59
Figure 37 Create Mac Port Info ............................................60
Figure 38 Route Info Upload................................................64
Figure 39 Add Static Route .................................................65
Figure 40 Load Balance Set 1 ..............................................66
Figure 41 Load Balance Set 2 ..............................................67
Figure 42 Create ARP configure information ..........................73
Figure 43 Interface limit number configuration ......................74
Figure 44 Create Arp..........................................................74
Figure 45 Global Config about TE .........................................76
Figure 46 Interface TE Config Management ...........................77
Figure 47 OSPF config ........................................................78
Figure 48 Create OSPF Area ................................................78
Figure 49 IGP Config Management 2 ....................................79
Figure 50 Explicit Path Config Management 1 ........................81
Figure 51 Te Operate Guide.................................................82
Figure 52 Label Info...........................................................84
Figure 53 Create Template ..................................................88
Figure 54 Add Detailed Time Range Information 1..................89
Figure 55 Add Detailed Time Range Information 2..................90
Figure 56 Import Template..................................................91
Figure 57 Create Time Range 2 ...........................................92
Figure 58 Create NE ACL ....................................................94
Figure 59 Create ACL Rule ..................................................95
Figure 60 ACL Interface Bound ............................................96
Figure 61 Create Extended ACL Rule ....................................97
Figure 62 Add User ............................................................98
Figure 63 Create MD ........................................................ 103
Figure 64 Create MA ........................................................ 104
Figure 65 Create MEP....................................................... 105
Figure 66 Create LBM....................................................... 106
Figure 67 Create LTM ....................................................... 107
Figure 68 Create RMEP ..................................................... 108
Figure 69 Create MIP ....................................................... 109
Figure 70 Create MAC Trace 1 ........................................... 113
Figure 71 Create MPLS TRACE 1 ........................................ 114
Figure 72 Create PingTask ................................................ 116
Figure 73 Create Ping Task Group ...................................... 116
Figure 74 Select Source.................................................... 117

Figures
Figure 75 Select Destination ............................................. 117

Figure 76 Select Parameter ............................................... 118
Figure 77 Select Parameter Model ...................................... 118
Figure 78 Create Parameter Model ..................................... 119
Figure 79 Display Result Matrix ......................................... 120
Figure 80 Result Graphic .................................................. 121
Figure 81 Create BFD Session ........................................... 123
Figure 82 Zero-Touch Deployment Parameters..................... 125
Figure 83 Bind Config File ................................................. 127
Figure 84 Bind Version File................................................ 128
Figure 85 New Sort.......................................................... 129
Figure 86 Shortcut Menu .................................................. 130
Figure 87 Add New Template............................................. 131
Figure 88 Preview Script................................................... 133
Figure 89 Modify Template ................................................ 134
Figure 90 Backing up Version File-Option ............................ 136
Figure 91 Rebooting NE-Option.......................................... 137
Figure 92 Version File Global Option- High-end Switch and
Router ........................................................... 139
Figure 93 Version File Global Option- Low-end Switch ........... 140
Figure 94 Getting running config success ............................ 141
Figure 95 Uploading Version File to Server .......................... 142
Figure 96 Rolling back Configuration File-Option .................. 146
Figure 97 File Compare Result ........................................... 147
Figure 98 Restore Patch File Option.................................... 149
Figure 99 Manage Files on NE............................................ 150
Figure 100 Common TopN View ......................................... 153


Tables
Table 1 Creating Port Information ........................................14

Table 2 Properties Description of E1 Physical Interface ............22
Table 3 Properties Description of IMA Interface ......................24
Table 4 PTP Port Properties .................................................30
Table 5 PTP Global Properties ..............................................32
Table 6 Port Properties .......................................................34
Table 7 SSM Global Properties .............................................36
Table 8 GPS Port Properties ................................................37
Table 9 Aggregation Port Parameters ....................................44
Table 10 Property Description..............................................59
Table 11 Property Description..............................................60
Table 12 Static Route Parameters.........................................65
Table 13 Global TE Configuration Parameters .........................76
Table 14 IS-IS Configuration Parameters...............................79
Table 15 Tunnel Operation Parameters ..................................82
Table 16 ACL Type and Configuration Rule.............................95
Table 17 Loop Port Parameters .......................................... 101
Table 18 MPLS TRACE Parameter Descriptions ..................... 115
Table 19 BFD Session Parameter Description ....................... 123
Table 20 Version File Status .............................................. 143


Glossary
ACL
- Access Control List
BGP
- Border Gateway Protocol
CFM
- Connectivity Fault Management
CIDR
- Classless Inter-Domain Routing
CLI
- Command Line Interface
CLNS
- ConnectionLess Network Sevice
DSCP
- Differentiated Services Code Point
EBGP
- External Border Gateway Protocol
FRR
- Fast Reroute
GR
- Graceful Restart
IBGP
- Interior Border Gateway Protocol
ICMP
- Internet Control Message Protocol
IEEE
- Institute of Electrical and Electronics Engineers
IETF
- Internet Engineering Task Force
IGP
- Interior Gateway Protocol
IP
- Internet Protocol
LAN
- Local Area Network
LBM
- Loopback Message
LSP
- Label Switched Path
LTM
- Linktrace Message
MA
- Maintenance Association

MAC
- Medium Access Control
MD
- Maintenance Domain
MED
- MULTI_EXIT_DISC
MEP
- Maintenance association End Point
MIB
- Management Information Base
MIP
- Maintenance domain Intermediate Point
MPLS
- Multi Protocol Label Switching
NTP
- Network Time Protocol
OSPF
- Open Shortest Path First
PDU
- Protocol Data Unit
PTP
- Precision Time Protocol
RMEP
- Remote Maintenance association End Point
RSVP-TE
- Resource ReSerVation Protocol - Traffic Engineering
SNMP
- Simple Network Management Protocol
SPF
- Shortest Path First
SVLAN
- Selective VLAN
TCP
- Transfer Control Protocol
TDR
- Time Domain Reflectometry
TE
- Traffic Engineering
TTL
- Time To Live
ToS
- Type Of Service
UDP
- User Datagram Protocol
VLSM
- Variable Length Subnet Mask

NetNumen N31 UNMS (V5.01.01) User Manual Resource Config

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetNumen N31 UNMS (V5.01.01) User Manual Resource Config

Uploaded by

Copyright:

Available Formats

NetNumen U31 (IP Network)

Unified Network Management System

Copyright © 2010 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision No. Revision Date Revision Reason

Serial Number: SJ-20100913154504-003

About This Manual............................................. I

Confidential and Proprietary Information of ZTE CORPORATION I

Link Resource Configuration ............................................39

II Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION III

Zero-Touch Deployment ............................................... 124

IV Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION V

This page is intentionally blank.

VI Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Resource Configuration Describes resource configuration

Chapter 2 Network Resource Describes network resource

Chapter 3 Layer 2 Management Describes layer 2 management

Chapter 4 Layer 3 Management Describes layer 3 management

Chapter 5 Service Management Describes layer 3 management

Chapter 6 Security Management Describes security management

Confidential and Proprietary Information of ZTE CORPORATION I

Chapter 7 Operation and Describes operation and

Chapter 8 Performance and Alarm Describes performance

Conventions ZTE documents employ the following typographical conventions.

Italics References to other Manuals and documents.

“Quotes” Links on screens.

Bold Menus, menu options, function names, input fields,

CAPS Keys on the keyboard and buttons on screens and

Note: Provides additional information about a certain

Checkpoint: Indicates that a particular step needs to

Tip: Indicates a suggestion or hint to make things

Mouse operation conventions are listed as follows:

Click Refers to clicking the primary mouse button (usually the

Double- Refers to quickly clicking the primary mouse button

Right-click Refers to clicking the secondary mouse button (usually

II Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 1

cisely control the path where traffic is transmitted by traffic

Basic Operation of Main

2 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 1 RESOURCE MANAGEMENT CONFIGURATION TOPOLOGY TREE

Confidential and Proprietary Information of ZTE CORPORATION 3

FIGURE 2 RESOURCE CONFIGURATION TREE TOOLBAR BUTTON

The functions of resource tree tool buttons are as follows:

� Expand : Expand whole resource configuration tree.

� Collapse : Collapse whole resource configuration tree.

� Search : It is different from filter. Search is to identify the

� View customization: click customization button , pop up

4 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 3 USER VIEW CUSTOMIZATION

Confidential and Proprietary Information of ZTE CORPORATION 5

Delete the resource instance that has existed in network man-

6 Confidential and Proprietary Information of ZTE CORPORATION

ii. Audit after deployment: compare the difference between

Confidential and Proprietary Information of ZTE CORPORATION 7

This page is intentionally blank.

8 Confidential and Proprietary Information of ZTE CORPORATION

Configuring NE Basic Information

Confidential and Proprietary Information of ZTE CORPORATION 9

Premise � Network management system is normally enabled and re-

2. Point to a button on the tool bar, the description of the button

10 Confidential and Proprietary Information of ZTE CORPORATION