Professional Documents
Culture Documents
Operation Guide For Common PDF
Operation Guide For Common PDF
Operation Guide For Common PDF
System
V100R009C00
Issue 03
Date 2014-05-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Related Version
The following table lists the product version related to this document.
Intended Audience
This document describes the operations for common features on the U2000.
This document guides the user to understand basic operations of the U2000.
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
Symbol Description
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes in earlier issues.
Contents
3 Security Management...............................................................................................................285
3.1 User Security..............................................................................................................................................................287
3.2 Managing User Rights................................................................................................................................................293
3.2.1 Getting to Know Operation Rights Management....................................................................................................293
3.2.1.1 Right Components................................................................................................................................................293
3.2.1.2 U2000 Authorization Principles...........................................................................................................................294
3.2.1.3 Users and User Groups.........................................................................................................................................301
3.2.1.4 Objects and Object Sets........................................................................................................................................303
3.2.1.5 Operation and Operation Set................................................................................................................................304
3.2.2 Scenarios for Operation Right Management...........................................................................................................308
3.2.3 Authorization Plan...................................................................................................................................................310
3.2.4 Assigning Rights to Users.......................................................................................................................................322
3.2.4.1 Authorization Process...........................................................................................................................................322
3.2.4.2 Creating User-Defined Object Sets......................................................................................................................323
3.2.4.3 Creating User-defined Operation Sets..................................................................................................................325
3.2.4.4 Creating and Authorizing U2000 User Groups....................................................................................................328
3.2.4.5 Creating Users and Adding the Users to User Groups.........................................................................................331
3.3.2.1 Setting a Secure Connection Between the U2000 Client and Server...................................................................394
3.3.2.2 Setting the FTP Transfer Policies Between the Client and Server.......................................................................395
3.3.3 Managing Passwords and Locking Clients..............................................................................................................396
3.3.3.1 Changing the Password of the Current User........................................................................................................396
3.3.3.2 Resetting the Password of an NMS user..............................................................................................................396
3.3.3.3 Modifying NMS user Information in Batches......................................................................................................397
3.3.3.4 Locking the Client Immediately...........................................................................................................................399
3.3.3.5 Unlocking the Client.............................................................................................................................................400
3.3.3.6 Setting Auto-Locking for an U2000.....................................................................................................................400
3.3.4 Monitoring U2000 Users.........................................................................................................................................401
3.3.4.1 Monitoring NMS User Sessions...........................................................................................................................401
3.3.4.2 Monitoring NMS User Operations.......................................................................................................................402
3.3.4.3 Forcing U2000 Users to Log Out.........................................................................................................................403
3.3.4.4 Unlocking Users...................................................................................................................................................403
3.3.4.5 Sending Messages to Online Users......................................................................................................................404
3.3.5 Managing the Remote Maintenance User................................................................................................................405
3.4 Managing NE Security...............................................................................................................................................406
3.4.1 NE Security Management........................................................................................................................................406
3.4.2 Setting the NE ACL.................................................................................................................................................408
3.4.2.1 Overview of ACL.................................................................................................................................................408
3.4.2.2 Setting Basic ACL Rules......................................................................................................................................409
3.4.2.3 Setting the Advanced ACL Rules.........................................................................................................................410
3.4.3 Setting the Security Access of an NE......................................................................................................................410
3.4.3.1 Setting Ethernet Access for NEs..........................................................................................................................411
3.4.3.2 Setting Serial Port Access for NEs.......................................................................................................................411
3.4.3.3 Setting the OAM Access to NEs..........................................................................................................................412
3.4.3.4 Setting the COM Access to NEs...........................................................................................................................412
3.4.3.5 Setting the LCT Access to NEs............................................................................................................................413
3.4.4 Managing NE Login................................................................................................................................................414
3.4.4.1 Locking Out NE Login.........................................................................................................................................414
3.4.4.2 Locking Out NE Settings......................................................................................................................................415
3.4.4.3 Querying the Information About an Online NE User...........................................................................................416
3.4.4.4 Switching a Logged-In NE User..........................................................................................................................417
3.4.4.5 Forcing an NE User to Log Out of the U2000.....................................................................................................418
3.4.4.6 Setting NE Login Prompt Message......................................................................................................................418
3.4.5 Managing NE Users.................................................................................................................................................419
3.4.5.1 Querying the Additional Information of NE User................................................................................................419
3.4.5.2 Creating an NE User.............................................................................................................................................420
3.4.5.3 Modifying NE Users.............................................................................................................................................422
3.4.5.4 Changing an NE User Password...........................................................................................................................423
3.4.5.5 Querying NE Security Parameters........................................................................................................................424
4 Log Management.......................................................................................................................438
4.1 Log Management Overview.......................................................................................................................................440
4.1.1 Log Management Policy..........................................................................................................................................440
4.1.2 Log Type..................................................................................................................................................................441
4.1.2.1 U2000 System Logs..............................................................................................................................................441
4.1.2.2 U2000 Security Logs............................................................................................................................................442
4.1.2.3 U2000 Operation Logs.........................................................................................................................................444
4.1.2.4 Syslog Run Logs of IP NEs..................................................................................................................................445
4.1.2.5 Syslog Operation Logs of Access NEs.................................................................................................................446
4.1.2.6 Security Logs of Transport NEs...........................................................................................................................447
4.1.3 Syslog Service.........................................................................................................................................................448
4.2 Managing U2000 System Logs..................................................................................................................................452
4.2.1 Querying U2000 System Logs................................................................................................................................452
4.2.2 Collecting Statistics on U2000 System Logs..........................................................................................................453
4.3 Managing U2000 Security Logs.................................................................................................................................455
4.3.1 Querying U2000 Security Logs...............................................................................................................................455
4.3.2 Collecting Statistics on U2000 Security Logs.........................................................................................................457
4.4 Managing U2000 Operation Logs..............................................................................................................................460
4.4.1 Querying U2000 Operation Logs............................................................................................................................460
4.4.2 Collecting Statistics on U2000 Operation Logs......................................................................................................462
4.5 Setting U2000 Log Templates....................................................................................................................................464
4.6 Managing U2000 Log Data........................................................................................................................................466
4.6.1 Setting U2000 Log Dump........................................................................................................................................466
4.6.2 Setting U2000 Log Overflow Dump.......................................................................................................................467
4.6.3 Manually Dumping U2000 Logs.............................................................................................................................468
4.6.4 Setting U2000 Log Export.......................................................................................................................................469
4.6.5 Setting Device Log Dump.......................................................................................................................................470
4.6.6 Setting U2000 Log Forwarding...............................................................................................................................471
5 Topology Management.............................................................................................................489
5.1 Overview of Topology Management..........................................................................................................................491
5.1.1 Topology Management Function.............................................................................................................................491
5.1.2 Types of Topology Views.......................................................................................................................................493
5.1.3 Objects in a Topology View....................................................................................................................................497
5.1.4 Automatic Topology Discovery..............................................................................................................................502
5.1.5 Alarm Indication in a Topology View.....................................................................................................................503
5.2 Network Topology Construction Process...................................................................................................................504
5.3 Designing a Physical Topology..................................................................................................................................508
5.4 Creating a Subnet........................................................................................................................................................509
5.5 Setting Parameters for the Communication Between the U2000 and NEs................................................................510
5.5.1 Protocols for Communication Between the U2000 and NEs..................................................................................511
5.5.2 Setting SNMP Parameters.......................................................................................................................................516
5.5.2.1 Configuring the Default SNMP Parameters Template.........................................................................................516
5.5.2.2 Setting NE SNMP Parameters..............................................................................................................................517
5.5.3 Setting Telnet/STelnet Parameters..........................................................................................................................520
5.5.3.1 Configuring a Telnet/STelnet Parameter Template..............................................................................................520
5.5.3.2 Setting Telnet/STelnet Parameters with a Template............................................................................................522
5.5.3.3 Manually Setting Telnet/STelnet Parameters.......................................................................................................524
7 Alarm Management...................................................................................................................687
7.1 Basic Concepts...........................................................................................................................................................689
7.1.1 Alarms and Events...................................................................................................................................................689
7.1.2 Alarm Severities......................................................................................................................................................689
7.1.3 Alarm Status............................................................................................................................................................690
7.1.4 Alarm Category.......................................................................................................................................................691
7.1.5 Alarm Notification...................................................................................................................................................692
7.1.6 Current Alarms and Historical Alarms....................................................................................................................696
7.1.7 Alarm Basic Operations...........................................................................................................................................697
7.1.8 Alarm Setting Operations........................................................................................................................................700
7.2 Overview of Fault Operations....................................................................................................................................706
7.3 Setting Remote Alarm or Event Notification.............................................................................................................707
7.3.1 Commissioning the SMS Gateway..........................................................................................................................707
7.3.1.1 Setting Parameters for Alarm Notification by the SMS Gateway........................................................................707
7.3.1.2 Verifying the SMS Gateway.................................................................................................................................709
7.3.2 Commissioning Alarm Notification by Email.........................................................................................................710
7.3.2.1 Setting Parameters for Alarm Notification by Email...........................................................................................710
7.3.2.2 Verifying Remote Alarm Notification by Email..................................................................................................712
7.3.3 Commissioning the Wireless Modem......................................................................................................................713
7.3.3.1 Installing the Wireless Modem.............................................................................................................................713
9 Inventory Management............................................................................................................952
9.1 Telecommunications Room Management..................................................................................................................955
9.1.1 Creating a Telecommunications Room...................................................................................................................955
9.1.2 Installing a Rack or an NMS in a Telecommunications Room...............................................................................956
9.1.3 Querying Telecommunications Rooms...................................................................................................................957
9.1.4 Modifying a Telecommunications Room................................................................................................................957
9.1.5 Deleting a Telecommunications Room...................................................................................................................958
9.1.6 Setting a Flag for a Telecommunications Room.....................................................................................................958
9.1.7 Exporting Information About telecommunications Rooms ....................................................................................959
9.1.8 Collecting Statistics on a Telecommunications Room............................................................................................960
9.2 Rack Management......................................................................................................................................................961
9.2.1 Creating a Rack.......................................................................................................................................................961
9.2.2 Installing a Subrack on a Rack................................................................................................................................962
9.2.3 Querying Racks.......................................................................................................................................................962
9.2.4 Modifying a Rack....................................................................................................................................................963
9.2.5 Deleting a Rack.......................................................................................................................................................964
9.2.6 Setting a Rack Flag..................................................................................................................................................964
9.2.7 Exporting Rack Information....................................................................................................................................965
9.2.8 Collecting Statistics on a Rack................................................................................................................................965
9.3 NE Management.........................................................................................................................................................967
9.3.1 Querying NEs..........................................................................................................................................................967
9.3.2 Setting a Flag for an NE..........................................................................................................................................968
9.3.3 Exporting NE Information.......................................................................................................................................968
9.3.4 Collecting Statistics on an NE.................................................................................................................................969
9.3.5 Collecting Statistics on an Equivalent NE...............................................................................................................970
9.4 Subrack Management.................................................................................................................................................971
9.4.1 Querying Subracks..................................................................................................................................................971
9.4.2 Setting a Flag for a Subrack....................................................................................................................................972
11 Task Management.................................................................................................................1061
11.1 Basic Concepts.......................................................................................................................................................1062
11.1.1 Task Management Window.................................................................................................................................1062
15 Customer Management........................................................................................................1229
15.1 Relationships Between Customers and Users........................................................................................................1231
15.2 Creating a Customer...............................................................................................................................................1231
15.3 Creating a Customer Group....................................................................................................................................1232
15.4 Authorizing a Customer to a U2000 User..............................................................................................................1232
15.5 Browsing Customer Information............................................................................................................................1233
15.6 Viewing Relevant Trails of a Customer.................................................................................................................1233
15.7 Browsing Current Alarms of a Customer...............................................................................................................1234
15.8 Browsing Historical Alarms of a Customer...........................................................................................................1235
15.9 Modifying Customer Information..........................................................................................................................1236
15.10 Deleting a Customer.............................................................................................................................................1236
15.11 Viewing the Customers Affected by an Alarm....................................................................................................1237
15.12 Specifying the Customer of a Service..................................................................................................................1238
15.13 Enabling VCN Status of a Customer....................................................................................................................1239
1 Getting Started
The following topics introduce some preparation operations that will ensure a smooth, trouble-
free launch of the U2000.
U2000 operation interface. These text boxes are used to enter character strings, file names, IP
addresses, MAC addresses, numerals, passwords, dates, time, and so on.
l Do not modify the system time when the U2000 is running. Set the time before installing
the U2000.
– To modify the system time of the server, exit the U2000 server and restart it after the
modification.
– To modify the system time of the client, exit the U2000 client and restart it after the
modification.
l Avoid modifying the name and IP address of the U2000 server computer.
l Log in to the U2000 server as user ossuser on Solaris. Log in to the U2000 server as user
ossuser on SUSE Linux. On Windows, log in to the U2000 server with the same user ID
that you have chosen when installing the U2000. Do not change the Windows user name.
l The data created on the NE is consistent with that on the U2000. After an NE is configured
and runs properly, ensure data consistency between the NE and the U2000 by means of
manual or automatic synchronization.
l Back up the U2000 database periodically to minimize the loss caused by system
malfunction.
l Synchronize the NE configuration data to the NMS and query the latest NE data before
setting the parameters.
l When a potentially service-affecting operation is performed, the U2000 asks the user for
confirmation. For example, the U2000 displays a message indicating that services will be
interrupted when you download the U2000 data to the NE.
l The installation directory of the U2000 must contain only letters, digits and underscores.
Otherwise, the U2000 Online Help cannot be used.
l If you select a non-English language for an NE when maintaining it, garbled characters are
returned after you query information about the NE.
l Ensure that no other data communication or transmission process is running on the OS of
the U2000 server.
l The default passwords for the default U2000 client user, server OS user, and database user
are all Changeme_123. To ensure the security of the U2000, change the default passwords
after the first login and change the non-default passwords regularly. Meanwhile, the
passwords must be complex enough. For example, a password must contain six or more
characters of different types. The allowed character types are digits, letters, and special
characters.
1. Power on a Huawei Tecal RH2288H V2/Huawei Tecal RH5885H V3/IBM X3650 M4/
IBM X3650 M3/IBM X3850 X5 server.
NOTICE
l Huawei Tecal RH2288H V2/Huawei Tecal RH5885H V3 server supports 100 to 240
VAC input voltage.
l IBM X3650 M4/IBM X3650 M3/IBM X3850 X5 server supports 100 to 132 VAC and
200 to 240 VAC input voltage.
l Configure power supply based on the rated system power requirement, see U2000
Hardware Installation Guide (Huawei N610E cabinet). If the power supply is
insufficient, the server automatically stops.
2. Press the power buttons on the peripherals and monitor connected to a server.
3. Wait 2 to 3 minutes. When the green indicator on the front panel of the server blinks every
1s, press the power button on the shelf of the server.
NOTE
If the power button is steady on, the server has been successfully powered on. For details about IBM
server indicators, see the manual for IBM servers or log in to the official IBM website. For details
about Huawei server indicators, see the manual for Huawei servers or log in to the official Huawei
website.
The red boxes in the following figures show the positions of power buttons on Huawei
Tecal RH2288H V2, Huawei Tecal RH5885H V3, IBM X3650 M4, IBM X3650 M3 and
IBM X3850 X5.
Figure 1-1 Position of the power button on Huawei Tecal RH5885H V3 server
Figure 1-2 Position of the power button on Huawei Tecal RH2288H V2 server
Prerequisites
The OS has been started.
Context
Generally, the database starts along with the OS.
Procedure
Step 1 Log in to the OS as a user with administrator rights.
Step 2 Choose Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager > SQL Server Services.
Step 3 Right-click SQL Server (MSSQLSERVER) and choose Start from the shortcut menu.
NOTE
If the SQL Server 2000 database is installed on Windows Server 2003, choose Start > Programs >
Microsoft SQL Server > Service Manager. In the SQL Server Service Manager dialog box, click Start/
Continue.
----End
Result
In the SQL Server (MSSQLSERVER), if Start is dimmed, Microsoft SQL Server 2008 is
running.
NOTE
If the SQL Server 2000 database is installed on Windows Server 2003, in the SQL Server Service
Manager dialog box, if Start/Continue is dimmed, Microsoft SQL Server 2000 is running.
Prerequisites
The OS on the computer on which the U2000 server processes are installed is running properly,
and the database has been started.
Context
l Generally, the U2000 server processes start along with the OS.
l Only one default NMS user, admin, is provided during U2000 software installation. The
admin user is a U2000 administrator with the highest rights on the U2000 system.
Procedure
Step 1 Log in to the OS as a user with administrator rights.
Step 2 View the startup information about the U2000 server processes.
1. Choose Start > Run. The Run window will be displayed.
2. Enter cmd and click OK.
3. In the CLI, run the daem_ps command to check whether the U2000 process is started.
l If information similar to the following is displayed, the U2000 process has started.
imapwatchdog.exe 7672 Services 0 7,172
K
ResourceMonitor.exe 21280 Services 0 23,756
K
imapmrb.exe 29188 Services 0 32,760
K
imapsysd.exe 9968 Services 0 40,988
K
imapeventmgr.exe 2756 Services 0 18,452
K
imap_sysmonitor.exe 5124 Services 0 34,432
K
httpd.exe 4908 Services 0 13,476
K
httpd.exe 28900 Services 0 14,756
K
javaw.exe 24564 Services 0 72,036
K
l If no command output is displayed, the U2000 process is not started. You can run the
D:\oss\server\platform\bin\startnms.bat command in the CLI to start the U2000
process.
NOTE
Step 3 Check the running status of every process on the System Monitor client.
1. Choose Start > All Programs > Network Management System > U2000 System
Monitor or click the shortcut icon on the desktop to start the U2000 System Monitor client.
2. In the Login dialog box, enter a user name and a password.
NOTE
Two data transmission modes are available: Common and Security(SSL) (more secure,
recommended). The default data transmission mode is Security(SSL). For details, see section How
to Set the Communication Mode on the U2000 server for the Single-Server System (Windows).
The initial password of the admin user is Changeme_123 (It is Admin_123 for a U2000 that comes
preinstalled). The password must be changed during the first login to ensure system security. Keep
the password confidential and change it regularly.
----End
Result
l If the U2000 services with the startup type of Automatic have started properly, the
U2000 runs properly.
l If some services have not started, select them, right-click, and choose Start the Service
from the shortcut menu.
l If the U2000 does not run properly, contact Huawei engineers.
Follow-up Procedure
The network management system maintenance suite is used for U2000 commissioning,
maintenance, and redeployment. Generally, the MSuite server starts along with the OS.
In the Windows Task Manager dialog box, check whether msdaemon.exe and
msserver.exe are listed.
l If the two processes are listed, the MSuite server has started.
l If the two processes are not listed, the MSuite server has not started. Navigate to the C:
\OSSENGR\engineering directory of U2000 server and double-click startserver.bat to
start the MSuite server.
NOTICE
l Oracle SPARC T4-2 workstations support only 200 ~ 240 VAC input voltage and do
not support 100 ~ 120 VAC input voltage.
l Netra T4-1/Oracle T4-1/T5220/M4000/M5000 server supports 200 to 240 VAC and
100 to 120 VAC input voltage.
l Configure power supply based on the rated system power requirement, see U2000
Hardware Installation Guide (Huawei N610E cabinet). If the power supply is
insufficient, the server automatically stops and the high availability system fails to
trigger an active/standby switchover.
2. Wait about 2 or 3 minutes. Then switch on the power of the Netra T4-1/Oracle T4-1/Oracle
T4-2/T5220 workstation to start the server.
3. After the server is started, check indicators on the front panel. If the power indicator is
steady green, the server is powered on. If another indicator is on or blinks, the server does
not function properly. Contact the server maintenance engineers to solve the problem. The
following figure shows the positions of the power switch and power indicator.
Figure 1-6 Power switch and power indicator on the Netra T4-1 server
Figure 1-7 Power switch and power indicator on the Oracle T4-1 server
Figure 1-8 Power switch and power indicator on the Oracle T4-2 server
Figure 1-9 Power switch and power indicator on the T5220 server
NOTE
l If the Solaris OS starts automatically on the server, the Solaris OS has been correctly installed.
l If the server displays the OK prompt, enter boot. If the server does not respond, no Solaris OS has been
installed on the server.
M4000/M5000 Server
1. Power on an M4000/M5000 server.
NOTE
Configure power supply based on the rated system power requirement, see U2000 Hardware
Installation Guide (Huawei N610E cabinet). If the power supply is insufficient, the server
automatically stops and the high availability system fails to trigger an active/standby switchover.
This issue occurs frequently for the M4000/M5000 with high power consumption.
2. Insert the key delivered with the server into the key slot in the front panel of the M4000/
M5000 server, and turn the rotary switch to the Locked position labeled with , as shown
in the following figure.
3. Press the power switch of the workstation, which is identified by . Wait 2 to 3 minutes.
If front indicator of the server is on (changes to steady green), the server starts up and
performs self-diagnosis.
NOTE
l Ensure that the green LED power indicator on the operation panel is lit.
l During the power-on process, it is recommended that you use a PC to log in to the controller on
an M4000/M5000 server through a serial interface and enter console -d 0 -f to view the server
start status.
l If the Solaris OS starts automatically on the server, the Solaris OS has been correctly installed.
l If turn the rotary switch to the Service position labeled with , the server cannot access the
OS automatically, the server displays the ok prompt. Enter boot. If the server does not respond,
no Solaris OS has been installed on the server.
Disk Array
NOTICE
l To prevent data loss, do not remove or insert disk modules, controllers, fibers, network cables,
or serial cables when powering on a disk array.
l To prevent disk damage and data loss, do not turn on or cut off the power supply when the
disk is accessing data. If the power supply is cut off, wait at least 1 minute before turning it
on.
NOTE
Power supply must be provided for the two power modules of the OceanStor S2600 and OceanStor
S3900; otherwise, the OceanStor S2600 and OceanStor S3900 fail to be used. Then press the power switch
on the controller A/B. Wait 5 to 10 minutes until the power indicator is steady green, no longer flashing,
indicating the success of the power-on.
Prerequisites
The OS has been started.
Context
Generally, the database starts along with the OS.
Procedure
Step 1 Log in to the OS as the dbuser user.
NOTE
To switch to the dbuser user, run the su - dbuser command. After the U2000 is installed, the password
for the dbuser user is Changeme_123.
Run the following command to check whether the Sybase database is running:
$ ps -ef | grep sybase
NOTE
Run the following commands to start the Sybase database if it is not running:
$ su - dbuser
NOTE
Enter the dbuser user password as prompted. The default password is Changeme_123. For system security,
modify the default password and remember the new password. For details, see How to Change the OS User
Password.
$ . /opt/sybase/SYBASE.sh
$ cd /opt/sybase/ASE*/install
$ ./startserver -f ./RUN_DBSVR &
$ ./startserver -f ./RUN_DBSVR_back &
$ exit
NOTE
l Leave a space between the dot (.) and the command /opt/sybase/SYBASE.sh.
l DBSVR is the name of the database server and DBSVR_back is the name of the database backup
server. These names must be consistent with the actual database names.
l View the database name and database backup server name by running the more /opt/sybase/
interfaces command.
----End
Result
Run the following command to check whether the Sybase process is running:
$ ps -ef | grep sybase
NOTE
Prerequisites
The OS on the computer on which the U2000 server processes are installed is running properly,
and the database has been started.
Context
l Generally, the U2000 server processes start along with the OS.
l Only one default NMS user, admin, is provided during U2000 software installation. The
admin user is a U2000 administrator with the highest rights on the U2000 system.
Procedure
Step 1 Log in to the OS of the server as the ossuser user.
Step 2 Run the following command to check whether the U2000 processes have started:
$ daem_ps
NOTE
If the displayed information contains imap_sysmonitor -cmd start, the U2000 processes have started.
Step 3 Run the following command to start the U2000 processes if they have not started:
$ cd /opt/oss/server/platform/bin
$ ./startnms.sh
Step 4 Perform the following operations to log in to the server GUI as the ossuser user and view the
running status of every process on the System Monitor client:
NOTICE
If the login to the server GUI is unavailable, run the svc_adm -cmd status command as the
ossuser user to view the process status.
Two data transmission modes are available: Common and Security(SSL). The default data
transmission mode is Security(SSL). Security(SSL) is recommended for the high security
requirements. You can run a command on the server to query the data transmission mode.
For details about how to set the communication mode for the U2000 server in a Solaris single-server
system, see How to Set the Communication Mode on the U2000 server for the Single-Server System
(Solaris).
----End
Result
l If the U2000 services with the startup type of Automatic have started properly, the
U2000 runs properly.
l If some services have not started, select them, right-click, and choose Start the Service
from the shortcut menu.
l If the U2000 does not run properly, contact Huawei engineers.
Follow-up Procedure
The network management system maintenance suite is used for U2000 commissioning,
maintenance, and redeployment. Generally, the MSuite server starts along with the OS. If the
MSuite server does not start, run the following commands:
$ su - root
password: password_of_the_root_user
# cd /opt/OSSENGR/engineering
# ./startserver.sh
Run the following command to check whether the network management system maintenance
suite process has started:
$ ps -ef | grep java
root 19913 19907 0 04:04:09 pts/1 0:00 grep java
...
root 18382 18311 0 03:42:33 pts/2 12:20 /opt/OSSJRE/jre_sol/bin/java -server
-Dequinox.conf=engineering/conf/installE
NOTE
Server
1. Power on a IBM X3650 M4/IBM X3650 M3/IBM X3850 X5 server.
NOTICE
l IBM X3650 M4/IBM X3650 M3/IBM X3850 X5 server supports 100 to 132 VAC and
200 to 240 VAC input voltage.
l Configure power supply based on the rated system power requirement, see U2000
Hardware Installation Guide (Huawei N610E cabinet).
For the Single-Server System (SUSE Linux), if the power supply is insufficient, the
server automatically stops.
For the High Availability System (SUSE Linux), if the power supply is insufficient, the
server automatically stops and the high availability system fails to trigger an active/
standby switchover.
2. Press the power button on the chassis of the server to power on the server. In the following
figures, the power button is marked in a red frame.
NOTE
If the power button is steady green, the server has been successfully powered on. For details about
server indicators, see the manual for IBM servers or log in to the official IBM website.
Figure 1-12 Position of the power button of the IBM X3650 M3 server
Figure 1-13 Position of the power button of the IBM X3850 X5 server
Disk Array
NOTICE
l To prevent data loss, do not remove or insert disk modules, controllers, fibers, network cables,
or serial cables when powering on a disk array.
l To prevent disk damage and data loss, do not turn on or cut off the power supply when the
disk is accessing data. If the power supply is cut off, wait at least 1 minute before turning it
on.
NOTE
Power supply must be provided for the two power modules of the OceanStor S3900; otherwise, the
OceanStor S3900 fail to be used. Then press the power switch on the controller A / B. Wait 5 to 10 minutes
until the power indicator is steady green, no longer flashing, indicating the success of the power-on.
Prerequisites
The OS has been started.
Context
Generally, the database starts along with the OS.
Procedure
Step 1 Log in to the OS as the dbuser user.
NOTE
To switch to the dbuser user, run the su - dbuser command. After the U2000 is installed, the password
for the dbuser user is Changeme_123. For system security, modify the default password and remember
the new password. For details, see How to Change the OS User Password.
Step 2 Run the following command to check whether the Sybase database is running.
$ ps -ef | grep sybase
NOTE
Step 3 Run the following commands to start the Sybase database if it is not running.
$ . /opt/sybase/SYBASE.sh
$ cd /opt/sybase/ASE*/install
$ ./startserver -f ./RUN_DBSVR &
$ ./startserver -f ./RUN_DBSVR_back &
NOTE
l Leave a space between the dot (.) and the command /opt/sybase/SYBASE.sh.
l DBSVR is the name of the database server and DBSVR_back is the name of the database backup
server. These names must be consistent with the actual database names.
l View the database name and database backup server name by running the more /opt/sybase/
interfaces command.
----End
Result
Run the following command to check whether the Sybase process is running:
$ ps -ef | grep sybase
NOTE
Prerequisites
The OS on the PC server on which the U2000 server processes are installed is running properly,
and the database has been started.
Context
Generally, the U2000 server processes start along with the OS.
Procedure
Step 1 Log in to the OS of the server as the ossuser user.
Step 2 Ensure that the U2000 is running.
Run the following command to check whether the U2000 is running:
$ daem_ps
NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start. If no
introduction is displayed, the U2000 processes have been stopped.
Step 3 View the running status of each process through the System Monitor on the SUSE Linux OS,
as follows:
1. On the desktop of the OS, double-click the U2000 System Monitor shortcut icon.
NOTE
You can run the following commands to start the system monitor client through the CLI:
$ cd /opt/oss/client
$ ./startup_sysmonitor_global.sh
2. In the dialog box that is displayed, enter the U2000 user name and password to open the
System Monitor window. The initial password of the admin user is Changeme_123 (It is
Admin_123 for a U2000 that comes preinstalled). The password must be changed during
the first login to ensure system security. Keep the password confidential and change it
regularly.
NOTE
Two data transmission modes are available: Common and Security(SSL). The default data
transmission mode is Security(SSL). Security(SSL) is recommended for the high security
requirements. You can run a command on the server to query the data transmission mode.
For details about how to set the communication mode for the U2000 server in a SUSE Linux single-
server system, see How to Set the Communication Mode on the U2000 server for the Single-Server
System (SUSE Linux).
----End
Result
l If the U2000 services with the startup type of Automatic have started properly, the
U2000 runs properly.
l If some services have not started, select them, right-click, and choose Start the Service
from the shortcut menu.
l If the U2000 does not run properly, contact Huawei engineers.
NOTICE
l Oracle SPARC T4-2 workstations support only 200 ~ 240 VAC input voltage and do
not support 100 ~ 120 VAC input voltage.
l Netra T4-1/Oracle T4-1/T5220/M4000/M5000 server supports 200 to 240 VAC and
100 to 120 VAC input voltage.
l Configure power supply based on the rated system power requirement, see U2000
Hardware Installation Guide (Huawei N610E cabinet). If the power supply is
insufficient, the server automatically stops and the high availability system fails to
trigger an active/standby switchover.
2. Wait about 2 or 3 minutes. Then switch on the power of the Netra T4-1/Oracle T4-1/Oracle
T4-2/T5220 workstation to start the server.
3. After the server is started, check indicators on the front panel. If the power indicator is
steady green, the server is powered on. If another indicator is on or blinks, the server does
not function properly. Contact the server maintenance engineers to solve the problem. The
following figure shows the positions of the power switch and power indicator.
Figure 1-14 Power switch and power indicator on the Netra T4-1 server
Figure 1-15 Power switch and power indicator on the Oracle T4-1 server
Figure 1-16 Power switch and power indicator on the Oracle T4-2 server
Figure 1-17 Power switch and power indicator on the T5220 server
NOTE
l If the Solaris OS starts automatically on the server, the Solaris OS has been correctly installed.
l If the server displays the OK prompt, enter boot. If the server does not respond, no Solaris OS has been
installed on the server.
M4000/M5000 Server
1. Power on an M4000/M5000 server.
NOTE
Configure power supply based on the rated system power requirement, see U2000 Hardware
Installation Guide (Huawei N610E cabinet). If the power supply is insufficient, the server
automatically stops and the high availability system fails to trigger an active/standby switchover.
This issue occurs frequently for the M4000/M5000 with high power consumption.
2. Insert the key delivered with the server into the key slot in the front panel of the M4000/
M5000 server, and turn the rotary switch to the Locked position labeled with , as shown
in the following figure.
3. Press the power switch of the workstation, which is identified by . Wait 2 to 3 minutes.
If front indicator of the server is on (changes to steady green), the server starts up and
performs self-diagnosis.
NOTE
l Ensure that the green LED power indicator on the operation panel is lit.
l During the power-on process, it is recommended that you use a PC to log in to the controller on
an M4000/M5000 server through a serial interface and enter console -d 0 -f to view the server
start status.
l If the Solaris OS starts automatically on the server, the Solaris OS has been correctly installed.
l If turn the rotary switch to the Service position labeled with , the server cannot access the
OS automatically, the server displays the ok prompt. Enter boot. If the server does not respond,
no Solaris OS has been installed on the server.
Disk Array
NOTICE
l To prevent data loss, do not remove or insert disk modules, controllers, fibers, network cables,
or serial cables when powering on a disk array.
l To prevent disk damage and data loss, do not turn on or cut off the power supply when the
disk is accessing data. If the power supply is cut off, wait at least 1 minute before turning it
on.
NOTE
Power supply must be provided for the two power modules of the OceanStor S2600 and OceanStor
S3900; otherwise, the OceanStor S2600 and OceanStor S3900 fail to be used. Then press the power switch
on the controller A/B. Wait 5 to 10 minutes until the power indicator is steady green, no longer flashing,
indicating the success of the power-on.
Prerequisites
l The OS has been started.
l The server is properly connected to the network.
l The VCS service must be properly started. The VCS service has started along with the OS
and the disk is functioning properly.
Procedure
Step 1 Perform the following operations to start the Sybase database:
l GUI mode:
1. Log in to the active site as the root user.
2. Run the following command to start the VCS client:
# hagui&
3. Choose File > New Cluster from the main menu. In the dialog box that is displayed,
enter the server IP address and click OK.
NOTE
If you are not logging in to the VCS client for the first time, click a server record in the information
list in the Cluster Monitor window.
4. Enter the default user name admin and the initial password Changeme_123 for the
VCS client. Then click OK. For system security, modify the default password and
remember the new password. For detail, see How to Change the admin User Password
for Logging In to the VCS Client.
5. Ensure that all Veritas resources are in Enabled state. Use the BackupServer resource
as an example. Perform the following operations:
Expand the AppService node and then the SybaseBk node in the navigation tree, right-
click BackupServer, and check whether Enabled has been selected in the shortcut
menu. If Enabled has not been selected, select it.
6. Right-click BackupServer and choose Online > host name from the shortcut menu.
7. In the dialog box that is displayed, click Yes.
Wait until the BackupServer and DatabaseServer resource icons on the Resources
tab page are bright, which indicates that the Sybase database service has started.
l CLI mode:
1. Log in to the active site as the root user.
2. Run the following commands to query Veritas resource names:
# haconf -makerw
# hares -list
3. Run the hares -modify resource name Enabled 1 command to change the status of all
Veritas resources to Enabled. Use the resource names displayed in the previous
command output as an example. Run the following commands to change the status of
all the Veritas resources to Enabled:
For example, execute the following commands in a Solaris high availability system:
# hares -modify BackupServer Enabled 1
# hares -modify DataFilesystem Enabled 1
# hares -modify DatabaseServer Enabled 1
# hares -modify NMSServer Enabled 1
# hares -modify RVGPrimary Enabled 1
# hares -modify datarvg Enabled 1
# hares -modify wac Enabled 1
For example, execute the following commands in a PC Linux high availability system:
# hares -modify APPBOND Enabled 1
# hares -modify BackupServer Enabled 1
# hares -modify DatabaseServer Enabled 1
# hares -modify NMSServer Enabled 1
# hares -modify RVGPrimary Enabled 1
# hares -modify datarvg Enabled 1
# hares -modify mountRes Enabled 1
# hares -modify wac Enabled 1
----End
Result
Run the following command to check whether the Sybase process is running:
$ ps -ef | grep sybase
RUN_DBSVR
dbuser 4675 4664 32 Apr15 ? 2-22:42:47 /opt/sybase/ASE-15_0/bin/
dataserver -sDBSVR -d/opt/sybase/data/lv_master -e/opt/sybase/ASE-15_0/install/
DBSVR.log -c/opt/sybase/ASE-15_0/DBSVR.cfg -M/opt/sybase/ASE-15_0
dbuser 4688 1 0 Apr15 ? 00:00:00 /bin/sh /opt/sybase/ASE-15_0/install/
RUN_DBSVR_back
dbuser 4692 4688 0 Apr15 ? 00:00:00 /opt/sybase/ASE-15_0/bin/
backupserver -SDBSVR_back -e/opt/sybase/ASE-15_0/install/DBSVR_back.log -N25 -C20 -
M/opt/sybase/ASE-15_0/bin/sybmultbuf
...
NOTE
Prerequisites
The OS on the computer on which the U2000 server processes are installed is running properly,
and the database has been started.
Procedure
Step 1 Log in to the OS on the active site as the root user.
NOTE
If the login dialog box is not displayed and a message appears indicating that the current status
is STALE_ADMIN_WAIT, run the # hasys -force host name of node command.
2. Choose Connect to cluster name.
NOTE
If you are logging in to the VCS for the first time, create a new cluster.
1. Choose File > New Cluster.
2. Enter an application network IP address.
3. Click OK.
3. Set User Name and Password.
NOTE
The default VCS user name is admin and the default password is Changeme_123. To ensure
system security, change the default password in time. If the default password has been changed,
enter the new password.
4. Click OK.
5. In the Cluster Explorer window, select the AppService resource group in the
navigation tree, right-click, and choose Online > host name from the shortcut menu to
start the Sybase process and U2000 server processes.
NOTE
Click the Resources tab to view the start status of each resource.
Normally, the value of State for the active site is Online in the Group Status on
Member Systems area on the Status tab page, and the value of Status is Online on
host name in the Resource Status area.
NOTE
----End
Result
1. Log in to the OS of the active site as the ossuser user.
2. Run the following command to check whether the U2000 is running:
$ daem_ps
NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start.
Server
1. Power on a IBM X3650 M4/IBM X3650 M3/IBM X3850 X5 server.
NOTICE
l IBM X3650 M4/IBM X3650 M3/IBM X3850 X5 server supports 100 to 132 VAC and
200 to 240 VAC input voltage.
l Configure power supply based on the rated system power requirement, see U2000
Hardware Installation Guide (Huawei N610E cabinet).
For the Single-Server System (SUSE Linux), if the power supply is insufficient, the
server automatically stops.
For the High Availability System (SUSE Linux), if the power supply is insufficient, the
server automatically stops and the high availability system fails to trigger an active/
standby switchover.
2. Press the power button on the chassis of the server to power on the server. In the following
figures, the power button is marked in a red frame.
NOTE
If the power button is steady green, the server has been successfully powered on. For details about
server indicators, see the manual for IBM servers or log in to the official IBM website.
Figure 1-20 Position of the power button of the IBM X3650 M3 server
Figure 1-21 Position of the power button of the IBM X3850 X5 server
Disk Array
NOTICE
l To prevent data loss, do not remove or insert disk modules, controllers, fibers, network cables,
or serial cables when powering on a disk array.
l To prevent disk damage and data loss, do not turn on or cut off the power supply when the
disk is accessing data. If the power supply is cut off, wait at least 1 minute before turning it
on.
NOTE
Power supply must be provided for the two power modules of the OceanStor S3900; otherwise, the
OceanStor S3900 fail to be used. Then press the power switch on the controller A / B. Wait 5 to 10 minutes
until the power indicator is steady green, no longer flashing, indicating the success of the power-on.
Prerequisites
l The OS has been started.
Procedure
Step 1 Perform the following operations to start the Sybase database:
l GUI mode:
1. Log in to the active site as the root user.
2. Run the following command to start the VCS client:
# hagui&
3. Choose File > New Cluster from the main menu. In the dialog box that is displayed,
enter the server IP address and click OK.
NOTE
If you are not logging in to the VCS client for the first time, click a server record in the information
list in the Cluster Monitor window.
4. Enter the default user name admin and the initial password Changeme_123 for the
VCS client. Then click OK. For system security, modify the default password and
remember the new password. For detail, see How to Change the admin User Password
for Logging In to the VCS Client.
5. Ensure that all Veritas resources are in Enabled state. Use the BackupServer resource
as an example. Perform the following operations:
Expand the AppService node and then the SybaseBk node in the navigation tree, right-
click BackupServer, and check whether Enabled has been selected in the shortcut
menu. If Enabled has not been selected, select it.
6. Right-click BackupServer and choose Online > host name from the shortcut menu.
7. In the dialog box that is displayed, click Yes.
Wait until the BackupServer and DatabaseServer resource icons on the Resources
tab page are bright, which indicates that the Sybase database service has started.
l CLI mode:
1. Log in to the active site as the root user.
2. Run the following commands to query Veritas resource names:
# haconf -makerw
# hares -list
mountRes Primary
wac Primary
3. Run the hares -modify resource name Enabled 1 command to change the status of all
Veritas resources to Enabled. Use the resource names displayed in the previous
command output as an example. Run the following commands to change the status of
all the Veritas resources to Enabled:
For example, execute the following commands in a Solaris high availability system:
# hares -modify BackupServer Enabled 1
# hares -modify DataFilesystem Enabled 1
# hares -modify DatabaseServer Enabled 1
# hares -modify NMSServer Enabled 1
# hares -modify RVGPrimary Enabled 1
# hares -modify datarvg Enabled 1
# hares -modify wac Enabled 1
For example, execute the following commands in a PC Linux high availability system:
# hares -modify APPBOND Enabled 1
# hares -modify BackupServer Enabled 1
# hares -modify DatabaseServer Enabled 1
# hares -modify NMSServer Enabled 1
# hares -modify RVGPrimary Enabled 1
# hares -modify datarvg Enabled 1
# hares -modify mountRes Enabled 1
# hares -modify wac Enabled 1
----End
Result
Run the following command to check whether the Sybase process is running:
$ ps -ef | grep sybase
NOTE
Prerequisites
The OS on the computer on which the U2000 server processes are installed is running properly,
and the database has been started.
Procedure
Step 1 Log in to the OS on the active site as the root user.
NOTE
If the login dialog box is not displayed and a message appears indicating that the current status
is STALE_ADMIN_WAIT, run the # hasys -force host name of node command.
2. Click Connect to cluster name.
NOTE
If you are logging in to the VCS for the first time, create a new cluster.
1. Choose File > New Cluster.
2. Enter an application network IP address.
3. Click OK.
3. Set User Name and Password.
NOTE
The default VCS user name is admin and the default password is Changeme_123. To ensure
system security, change the default password in time. If the default password has been changed,
enter the new password.
4. Click OK.
5. In the Cluster Explorer window, select the AppService resource group in the
navigation tree, right-click, and choose Online > host name from the shortcut menu to
start the Sybase process and U2000 server processes.
NOTE
Click the Resources tab to view the start status of each resource.
Normally, the value of State for the active site is Online in the Group Status on
Member Systems area on the Status tab page, and the value of Status is Online on
host name in the Resource Status area.
NOTE
l hostname specifies the server name. You can run the hostname command to view the server name.
l If a fault has occurred during the start of the AppService process, run the # hagrp -clear AppService
-sys hostname command to rectify the fault. Then run the # hagrp -online AppService -sys hostname
command to start the AppService process.
----End
Result
1. Log in to the OS of the active site as the ossuser user.
2. Run the following command to check whether the U2000 is running:
$ daem_ps
NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start.
Prerequisites
Before logging in to a U2000 client, ensure that the following conditions are met:
Run the ping peer IP address command to check the network communication.
– In a single-server system, the IP address is the system IP address for the server.
– In an availability system, the IP address is the NMS application network IP address for
the active site.
l The ports used between the U2000 client and the U2000 server have been enabled. For
details, see U2000 Communication Port Matrix.
l The IP address of the U2000 client is included in the ACL configured on the U2000 server.
NOTE
By default, an ACL contains all IP addresses. Setting an ACL based on security requirements is
recommended. For details, see 3.3.1.2 Setting the User ACL.
l Valid U2000 user account and password are available.
l U2000 licenses have been correctly loaded to the U2000 server.
l Using the resolution 1024 x 768 or higher is recommended. If the resolution is not used,
the U2000 client GUI may be incomplete. If the GUI contains complex elements, use a
higher resolution at the same ratio, such as 1152 x 864.
Context
l By default, if three incorrect passwords are entered consecutively, the associated user
account will be locked by the U2000. The user admin can unlock common user accounts.
The U2000 will also unlock the user account in 30 minutes.
l The password for the U2000 System Monitor must be the same as that for the U2000 client.
l Check whether the version of the client is the same as the version of server. If they are
different, you must upgrade the client or reinstall a client with the same version as the
server.
Procedure
Step 1 Log in to the OS on which the U2000 client is installed.
l On Windows, log in to the OS as the administrator user.
l On Solaris, log in to the OS GUI as the ossuser user.
Step 2 Double-click the U2000 Client shortcut icon on the desktop. The Login dialog box is displayed.
NOTE
l On Windows, double-click the startup_all_global.bat file in the client installation path, for example
D:\oss\client directory to start the U2000 client.
l On Solaris, run the ./startup_all_global.sh command in the /opt/oss/client directory to start the
U2000 client.
Step 3 In the Login dialog box, select a desired server from the Server drop-down list.
If no server has been configured, perform the following operations to add a server:
1. Click the ... button. In the Server List dialog box, click Add.
2. In the Add Server Information dialog box, set parameters for the U2000 server to be
added and click OK.
Parameter Settings
Name Setting this parameter to the login IP address or the related host name
is recommended.
Secondary server Generally, this parameter is not set. If the U2000 server is running
name (or IP in a high availability system, set this parameter to the IP address of
address) the standby site.
Port Two data transmission modes are available: Common and Security
(SSL) (more secure, recommended). By default, port 31037 is used
in Common mode and port 31039 is used in Security(SSL) (more
secure, recommended) mode.
Mode Two data transmission modes are available: Common and Security
(SSL). The default data transmission mode is Security(SSL).
Security(SSL) is recommended for the high security requirements.
You can run a command on the server to query the data transmission
mode.
l about how to set the communication mode for the U2000 server
and client in a Windows single-server system, see How to Set
the Communication Mode on the U2000 server for the Single-
Server System (Windows).
l about how to set the communication mode for the U2000 server
and client in a Solaris single-server system, see How to Set the
Communication Mode on the U2000 server for the Single-Server
System (Solaris).
l about how to set the communication mode for the U2000 server
and client in a SUSE Linux single-server system, see How to Set
the Communication Mode on the U2000 server for the Single-
Server System (SUSE Linux).
l about how to set the communication mode for the U2000 server
and client in a Solaris high availability system, see How to Set
the Communication Mode of the Server in a High Availability
System (Solaris, SUSE Linux).
l about how to set the communication mode for the U2000 server
and client in a SUSE Linux high availability system, see How to
Set the Communication Mode of the Server in a High
Availability System (Solaris, SUSE Linux).
NOTE
A client can log in to the U2000 server only when they work in the same
mode. If the client and server work in different modes, even if they are
installed on the same host, the client cannot log in to the server.
3. In the Server List dialog box, select a server from the list and click OK.
Step 4 Enter valid user name and password, and click Login.
l The default user name is admin. The initial password of the admin user is
Changeme_123 (It is Admin_123 for a U2000 that comes preinstalled). The password must
be changed during the first login to ensure system security. Keep the password confidential
and change it regularly.
l If you attempt to connect to the server in a non-SSL mode, the client displays a dialog box
indicating security risks.
– If you want to continue the connection, click Yes. If you do not want the client to display
the dialog box again upon subsequent logins, select Do not remind me next time.
NOTE
The IP address of the server being connected is saved to the allComServer.dat file in Client
installation directory\client\client\plugins\loginui\style\conf\loginui. Therefore, the Do not
remind me next time settings apply only to the connected server. If you want the client to display
the dialog box that indicates the security risks upon subsequent logins, delete the
allComServer.dat file.
– If you want to terminate the connection, click No. The Login dialog box is displayed.
You can select the matched communication mode.
l If the client does not trust the server, you need to determine whether the server is trustworthy
using the server certificate.
– If you confirm that the server is trustworthy, click Yes and log in to the client. If you do
not want the system to display the dialog box again, contact the system administrator to
configure a trust certificate.
– If you confirm that the server is untrustworthy, click No to return to the Login dialog box
and contact the system administrator to process the issue.
l When you log in to the U2000 client, a message will be displayed asking you whether to
upgrade the client if the U2000 detects that the local computer version is earlier than the
server version.
– To upgrade the client, click OK.
– To return to the login window, click Cancel.
----End
Result
After the U2000 client is successfully logged in to, it automatically obtains associated data from
the U2000 server.
NOTE
After the U2000 client is successfully logged in to, if a certificate problem is prompted, accept this
certificate permanently. Click OK.
Prerequisites
The U2000 clients must be started properly.
Procedure
Step 1 Choose File > Exit from the main menu.
----End
Prerequisites
Exit all running U2000 clients.
Procedure
Step 1 Log in to the OS as a user with administrator rights.
K
imapmrb.exe 29188 Services 0 32,760
K
imapsysd.exe 9968 Services 0 40,988
K
imapeventmgr.exe 2756 Services 0 18,452
K
imap_sysmonitor.exe 5124 Services 0 34,432
K
httpd.exe 4908 Services 0 13,476
K
httpd.exe 28900 Services 0 14,756
K
javaw.exe 24564 Services 0 72,036
K
NOTE
----End
Result
If no command output is displayed after the daem_ps command is executed, the U2000 process
has stopped.
Prerequisites
The U2000 server processes must have been stopped.
Procedure
Step 1 Log in to the OS as a user with administrator rights.
Step 2 Choose Start > All Programs > Microsoft SQL Server 2008 > Configuration Tools > SQL
Server Configuration Manager > SQL Server Services.
Step 3 Right-click SQL Server (MSSQLSERVER) and choose Stop to stop the database.
NOTE
If the SQL Server 2000 is installed in Windows Server 2003, choose Start > All Programs > Microsoft
SQL Server > Service Manager. The SQL Server Service Manager dialog box is displayed. Then, click
Stop. Then, click Yes.
----End
Result
Two methods are available for checking whether the SQL Server database can connect normally.
NOTE
If the displayed information includes 1>, you can connect to the database normally,
that is, the database is shutted down. Otherwise, the database is started.
l Through the GUI:
1. Click Start > All Programs > Microsoft SQL Server 2008 > SQL Server
Management Studio. The Connect to Server window is displayed.
2. Set parameters according to the following information and then click Connect.
– Server type: Database Engine
– Server name: DBSVR
– Authentication: Windows Authentication
If the displayed SQL Server Management Studio window prompted, you can
connect to the database normally, that is, the database is started. Otherwise, the
database is shutted down.
Prerequisites
l The U2000 server processes must have been stopped.
l The database must have been shut down.
Procedure
Step 1 Log in to the OS as a user with administrator rights.
Step 2 Choose Start > Shut down to shut down the Windows OS.
----End
Prerequisites
Exit all running U2000 clients.
Procedure
Step 1 Log in to the OS of the server as the ossuser user.
Step 2 To check the running status of the U2000 process, run the following command:
NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start. If no
introduction is displayed, the U2000 processes have been stopped.
----End
Result
Run the following command to check the running status of the U2000 process:
$ daem_ps
NOTE
Prerequisites
The U2000 server processes must have been stopped.
Procedure
Step 1 Log in to the OS as the dbuser user.
NOTE
To switch to the dbuser user, run the su - dbuser command. After the U2000 is installed, the password
for the dbuser user is Changeme_123.
Step 2 Run the following command to check whether the Sybase database is running:
$ ps -ef | grep sybase
NOTE
Step 3 Run the following commands to stop the Sybase database if it is running:
$ . /opt/sybase/SYBASE.sh
$ cd /opt/sybase/OCS*/bin
$ ./isql -SDBSVR -Usa
NOTE
NOTE
l Leave a space between the dot (.) and the command /opt/sybase/SYBASE.sh.
l Enter the database sa user password as prompted.
l Information similar to the following is displayed. The error message does not affect the shutdown of
the database.
Server SHUTDOWN by request.
ASE is terminating this process.
CT-LIBRARY error:
ct_results(): network packet layer: internal net library error: Net-
Library operation terminated due to disconnect
----End
Result
Run the following command to check whether the Sybase database is running:
$ ps -ef | grep sybase
NOTE
The database is stopped if the displayed information does not contain /opt/sybase/ASE-15_0/bin/
dataserver -sDBSVR and /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back.
Prerequisites
l The U2000 server processes must have been stopped.
l The database must have been shut down.
Procedure
Step 1 Log in to the Solaris OS as user root.
Step 2 Run the following commands to power off the server:
# sync;sync;sync;sync
# shutdown -y -g0 -i5
----End
1.3.4 Shutting Down the U2000 Server (Single Server System, SUSE
Linux)
Three steps are required to shut down the U2000 server: stop the U2000 server processes, shut
down the database, and power off the server safely.
of the computer where the server is installed or upgrading the version. This topic describes how
to stop the U2000 server processes on the SUSE Linux single-server system.
Prerequisites
All running U2000 clients have been stopped.
Procedure
Step 1 Log in to the OS of the server as the ossuser user.
Step 2 To check the running status of the U2000 process, run the following command:
$ daem_ps
NOTE
The U2000 is running if the displayed information contains imap_sysmonitor -cmd start.
----End
Result
Run the following command to check the running status of the U2000 process:
$ daem_ps
NOTE
Prerequisites
The U2000 server processes must have been stopped.
Procedure
Step 1 Log in to the OS as the dbuser user.
NOTE
To switch to the dbuser user, run the su - dbuser command. After the U2000 is installed, the password
for the dbuser user is Changeme_123. For system security, modify the default password and remember
the new password. For details, see How to Change the OS User Password.
Step 2 Run the following command to check whether the Sybase database is running.
$ ps -ef | grep sybase
NOTE
Step 3 Run the following commands to stop the Sybase database if it is running:
$ . /opt/sybase/SYBASE.sh
$ cd /opt/sybase/OCS*/bin
$ ./isql -SDBSVR -Usa
NOTE
NOTE
l Leave a space between the dot (.) and the command /opt/sybase/SYBASE.sh.
l Enter the database sa user password as prompted.
l Information similar to the following is displayed. The error message does not affect the shutdown of
the database.
Server SHUTDOWN by request.
ASE is terminating this process.
CT-LIBRARY error:
ct_results(): network packet layer: internal net library error: Net-
Library operation terminated due to disconnect
----End
Result
Run the following command to check whether the Sybase database is running:
$ ps -ef | grep sybase
NOTE
The database is stopped if the displayed information does not contain /opt/sybase/ASE-15_0/bin/
dataserver -sDBSVR and /opt/sybase/ASE-15_0/bin/backupserver -SDBSVR_back.
Prerequisites
l The U2000 server processes must have been stopped.
l The database must have been shut down.
Procedure
Step 1 Log in to the OS as the root user.
----End
Prerequisites
Exit all running U2000 clients.
Procedure
Step 1 Log in to the OS of the active site as the root user.
NOTE
If the login dialog box is not displayed and a message appears indicating that the current status
is STALE_ADMIN_WAIT, run the # hasys -force host name of node command.
2. Click Connect to Cluster name.
NOTE
If you are logging in to the VCS for the first time, you need to create a new Cluster.
1. Click File > New Cluster.
2. Enter the IP address of application network.
3. Click OK.
3. Enter the user name and password for VCS login.
NOTE
The default VCS user name is admin and the default password is Changeme_123. To ensure
system security, change the default password in time. If the default password has been changed,
enter the new password.
4. Click OK.
5. Choose AppService from the navigation tree.
6. Click the Resources tab. Right-click NMSServer and choose Offline > Host name
from the shortcut menu. In the Question dialog box, click Yes.
Wait about 1 minute. If the NMSServer icon changes to grey, the U2000 processes
have been stopped.
l CLI mode:
# hares -offline NMSServer -sys hostname
4. Run the following command to check the running status of the U2000 process:
$ daem_ps
NOTE
----End
Prerequisites
The U2000 server processes must have been stopped.
Procedure
Step 1 Perform the following operations to disable the Sybase database service at the primary site in
the HA system:
NOTE
By default, the Sybase database service at the secondary site is not running.
l GUI mode:
1. Log in to the primary site as user root.
2. Run the following command to start the VCS client at the primary site:
# hagui&
3. Choose File > New Cluster from the main menu. In the window that is displayed, enter
the IP address of the server and click OK.
NOTE
If you are not logging in to the VCS client for the first time, click a server record in the information
list in the Cluster Monitor window.
4. Enter the default user name admin and the initial password Changeme_123 for the
VCS client. For system security, modify the default password and remember the new
password. For detail, see How to Change the admin User Password for Logging In to
the VCS Client. Then click OK.
5. On the VCS client of the primary site, right-click the NMSServer node and choose
Offline > hostname from the shortcut menu.
6. In the confirmation dialog box, click Yes.
7. After the NMSServer node is dimmed, right-click the BackupServer node and choose
Offline > hostname from the shortcut menu.
8. In the confirmation dialog box, click Yes.
9. After the BackupServer node is dimmed, right-click the DatabaseServer node and
choose Offline > hostname from the shortcut menu.
NOTE
hostname specifies the server name. You can run the hostname command to view the server name.
Run the following command to check whether the Sybase database service is disabled:
# ps -ef | grep sybase
If the following message is displayed, the Sybase database service has been disabled:
root 9629 14603 0 07:46:52 pts/3 0:00 grep sybase
----End
Prerequisites
The U2000 and database must have been shut down.
Context
Before powering off the server safely, manually stop the VCS service; otherwise, the server may
fail to shut down properly.
Procedure
Step 1 Log in to the OS on the server as the root user.
----End
Prerequisites
l The U2000 server processes must have been stopped.
l The database must have been shut down.
Procedure
Step 1 Log in to the Solaris OS as user root.
Step 2 Run the following commands to power off the server:
# sync;sync;sync;sync
# shutdown -y -g0 -i5
----End
Prerequisites
Exit all running U2000 clients.
Procedure
Step 1 Log in to the OS of the active site as the root user.
Step 2 Stop the U2000 server processes.
l GUI mode:
1. Open a terminal window, run the following command:
# hagui&
NOTE
If the login dialog box is not displayed and a message appears indicating that the current status
is STALE_ADMIN_WAIT, run the # hasys -force host name of node command.
2. Click Connect to Cluster name.
NOTE
If you are logging in to the VCS for the first time, you need to create a new Cluster.
1. Click File > New Cluster.
2. Enter the IP address of application network.
3. Click OK.
3. Enter the user name and password for VCS login.
NOTE
The default VCS user name is admin and the default password is Changeme_123. To ensure
system security, change the default password in time. If the default password has been changed,
enter the new password.
4. Click OK.
5. Choose AppService from the navigation tree.
6. Click the Resources tab. Right-click NMSServer and choose Offline > Host name
from the shortcut menu. In the Question dialog box, click Yes.
Wait about 1 minute. If the NMSServer icon changes to grey, the U2000 processes
have been stopped.
l CLI mode:
# hares -offline NMSServer -sys hostname
NOTE
hostname specifies the server name. You can run the hostname command to view the server name.
4. Run the following command to check the running status of the U2000 process:
$ daem_ps
NOTE
----End
Prerequisites
The U2000 server processes must have been stopped.
Procedure
Step 1 Perform the following operations to disable the Sybase database service at the primary site in
the HA system:
NOTE
By default, the Sybase database service at the secondary site is not running.
l GUI mode:
1. Log in to the primary site as user root.
2. Run the following command to start the VCS client at the primary site:
# hagui&
3. Choose File > New Cluster from the main menu. In the window that is displayed, enter
the IP address of the server and click OK.
NOTE
If you are not logging in to the VCS client for the first time, click a server record in the information
list in the Cluster Monitor window.
4. Enter the default user name admin and the initial password Changeme_123 for the
VCS client. For system security, modify the default password and remember the new
password. For detail, see How to Change the admin User Password for Logging In to
the VCS Client. Then click OK.
5. On the VCS client of the primary site, right-click the NMSServer node and choose
Offline > hostname from the shortcut menu.
6. In the confirmation dialog box, click Yes.
7. After the NMSServer node is dimmed, right-click the BackupServer node and choose
Offline > hostname from the shortcut menu.
8. In the confirmation dialog box, click Yes.
9. After the BackupServer node is dimmed, right-click the DatabaseServer node and
choose Offline > hostname from the shortcut menu.
10. In the confirmation dialog box, click Yes.
l CLI mode:
1. Log in to the primary site as user root.
2. Run the following command to shut down the U2000:
# hares -offline NMSServer -sys hostname
NOTE
hostname specifies the server name. You can run the hostname command to view the server name.
Run the following command to check whether the Sybase database service is disabled:
# ps -ef | grep sybase
If the following message is displayed, the Sybase database service has been disabled:
root 9629 14603 0 07:46:52 pts/3 0:00 grep sybase
----End
Prerequisites
The U2000 and database must have been shut down.
Context
Before powering off the server safely, manually stop the VCS service; otherwise, the server may
fail to shut down properly.
Procedure
Step 1 Log in to the OS on the server as the root user.
----End
Prerequisites
l The U2000 server processes must have been stopped.
l The database must have been shut down.
l The VCS services must have been shut down.
Procedure
Step 1 Log in to the OS as the root user.
----End
Context
If + is appended to a menu option on the main menu of the NMS, you can create the shortcut of
this menu option on the workbench.
Procedure
Step 1 In the main window of the U2000, click the drop-down arrow next to and select Style of
Desktop to access the workbench.
Step 2 Right-click Workbench and choose Create Shortcut from the shortcut menu.
Step 3 In the Create Shortcut dialog box, select the function to be added with a shortcut icon.
Step 4 Click Create. The shortcut icon of the function is displayed on the workbench.
----End
Prerequisites
The U2000 client has been started successfully.
Context
When the NMS is started for the first time, the shortcut function view of the favorites folder is
displayed as a floating window on the Workbench. The default shortcut nodes, such as the alarm,
and Main Topology are displayed in the floating window.
Procedure
Step 2 In the drop-down list that is displayed, select Style of Favorites Folder.
Step 6 Select the node to be added to the favorites folder, and click Create.
----End
Result
The added node is displayed under Default Workbench in the favorites folder.
Prerequisites
The U2000 client has been started successfully.
Context
When the NMS is started for the first time, the shortcut function view of the favorites folder is
displayed as a floating window on the Workbench. The default shortcut nodes, such as the alarm,
and Main Topology are displayed in the floating window.
Procedure
Step 2 In the drop-down list that is displayed, select Style of Desktop or Style of Favorites Folder.
Step 3 If Style of Desktop is selected, the Workbench window is displayed, and the common functions
are displayed as floating icons.
Step 4 If Style of Favorites Folder is selected, the Workbench dialog box is displayed. If you click
+ in the front of Default Workbench or double-click Default Workbench, the common
functions are expanded.
----End
Follow-up Procedure
Right-click a common function and delete or modify it.
If the character set that an NE transfers to the U2000 is different from the character set of the
internal data (NE source file) on the U2000, the data transferred to the U2000 is displayed as
garbled characters. The data that the U2000 applies to the NE is also displayed as garbled
characters, resulting in failure in reading the NE.
Chinese GBK
English ISO-8859-1
Spanish UTF-8
Russian
German
Portuguese
Italian
French
Arabic
l In the case of the MSTP series, WDM series, RTN series, PTN series, router series, and
switch series NEs, if the character sets on an NE are changed, the U2000 refreshes the
character sets in real time so that the character sets on the U2000 are the same as those of
the NE. At the same time, the U2000 notifies the user by means of an event that the NE
character sets are changed.
l In the case of a new NE, if the data on the U2000 is displayed as garbled characters or the
language changes, you can query and modify the character set attribute of a single NE or
NEs in batches in the NE Character Set Management window.
l In the case of an old NE, the character set cannot be modified because an old NE does not
have the character set attribute interface. In the NE Character Set Management window,
if the queried NE is an old NE, the related record is dimmed.
NOTE
l Modifying character sets is not a commonly performed operation. Generally, it is not allowed to modify
character sets. If you change the character set incorrectly, characters may be garbled. If you change the
character set to UTF-8, characters on the NE may be truncated.
l If there is a definite multi-language requirement and the character set needs to be changed to UTF-8,
convert the original character sets according to the guide for related NEs to ensure that the original
data is normally displayed.
Chinese 3
English 1
Spanish 3
Russian 3
German 3
Portuguese 3
Italian 3
French 3
Arabic 2
Field NE
Field NE
Prerequisites
You have logged in to the U2000 client as user admin.
Context
NOTICE
The setting of an error character set may cause garbled characters.
l If multiple languages are required when an NE is created, set the character set to UTF-8
to support multiple language entering.
l If multiple languages are required when an NE is upgraded, set the character set of the NE
to UTF-8 to support multiple language entering.
l If garbled characters are displayed after an NE is upgraded and the character set is set on
the NE, you can restore the setting to the original character set.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Charset Management (traditional
style) from the main menu or select Fix-Network NE Configuration in Application Center
and choose Configuration > NE Batch Configuration > NE Charset Management
(application style) from the main menu.
Step 2 In the NE Character Set Management window, select one or more NEs in the left pane and
click .
Step 6 Select one or more NEs to be modified, right-click in the Character Set column and then choose
the desired character set from the shortcut menu.
NOTE
You can hold down Shift or Ctrl to select multiple NEs, and set or modify character sets in batches.
----End
Initial Window
Figure 1-22 shows the GUI after you log in to the client.
NOTE
If you have added functions to the My Favorites tab, the My Favorites tab is displayed after you log in
to the client.
Figure 1-23 shows the GUI after you click . Table 1-2 describes Figure 1-23.
4 Status Bar Displays the status information of the system, such as the current
user and the IP address of the connected server.
Menu Bar
The U2000 client menu bar consists of the File, My Favorites, Window, and Help menus.
Toolbar
The toolbar provides shortcut icons for system management. Table 1-3 describes the shortcut
icons for system management and their functions.
Exit You can terminate client programs and exit the current U2000
client.
Log out You can log out of the current U2000 client without the
termination of client programs.
Lock Terminal If the client is locked, you are not allowed to perform operations
on the client. You must enter the correct password to unlock the
client.
Full Screen By using this icon, the menu bar, toolbar, output window, and
status bar can be hidden, and therefore the main window can
have more space. You can press Esc to exit the full screen mode.
Output Pane
The output pane displays the echo message of the operation performed when the U2000 is
running, such as the initialization message when you log in to the server.
Status Bar
The status bar displays the information such as the system status, the login users, and the IP
address of the connected server. The information displayed from left to right is as follows:
l Server: Displays the name and IP address used for logging in to the server.
l Login user: Displays the name of the login user.
l Connection duration: Displays the client time in real time.
l System pop-up pane: Displays a message in real time when an operation on the server
affects client operations. For example, after the user opens the Security Management
window, if a user, user group, or operation set is added or deleted on the U2000, the system
pop-up pane displays a message.
NOTE
To enable or disable the function of displaying a message, right-click the icon of the system pop-up
pane and choose Enable or Disable.
l Login mode: Displays the login mode. It can be single-user mode and multi-user mode.
l Connection status: Displays the status of the connection between the client and the server.
When the client is disconnected from the server, the icon on the status bar is changed from
to , and then to . When the status of the alarm indicator changes to ,a
disconnection sound is available.
l Logo: Displays the logo of Huawei Technologies Co., Ltd..
Application Center
Figure 1-24 shows the GUI after you log in to the client. The application center provides
common applications, such as fault management applications. Table 1-4 describes the
operations that can be performed on the Application Center tab.
Operation Details
Application Function
Application Function
IMS&NGN Service Management Manages NGN test beds, query IMS users,
and manages NGN service configuration.
NOTE
Applies to the Core Network NEs.
Application Function
My Favorites
Figure 1-25 shows the GUI after you click My Favorites.
You can add common functions to the My Favorites tab for quick access to the main windows
of the functions. You can also create folders on the My Favorites tab page to classify the
functions. To create a folder, perform the following steps:
1. On the My Favorites tab page, right-click the My Favorites node in the navigation tree
and choose New Folder from the shortcut menu.
2. In the Create Folder dialog box, enter a folder name and click OK.
NOTE
l You can right-click a function under the My Favorites node and choose Copy from the shortcut menu
to copy the function, and then right-click a function and choose Paste from the shortcut menu to paste
the function to the folder.
l You can right-click a folder and choose Delete or Rename from the shortcut menu to delete or rename
the folder respectively.
l Before deleting a folder under the My Favorites node, delete all the functions contained in the folder.
l You can open the main window of a function that has been added to the My Favorites tab page using
the My Favorites menu on the menu bar.
l You can add a maximum of 20 folders on the My Favorites tab page and the total number of favorite
functions can be 200.
Function Search
On this tab, you can enter a keyword to search for functions. The U2000 supports fuzzy matching
by Function or Menu Path. Figure 1-26 shows the GUI displayed after you conduct a function
search.
– : indicates that a function can be added to the My Favorites tab page. Click
next to the function. In the Add to Favorite dialog box, select a folder from the
Location drop-down list and click Add. The function is added to the folder on the My
Favorites tab page.
NOTE
If no folder exists under the My Favorites node, the Add to Favorite dialog box does not appear
Context
l If you have added functions to the My Favorites tab, the tab is displayed after you log in
to a client.
l My Favorites is recommended for quick access to the functions that you want. The legends
related to the My Favorites tab are described as follows:
– : indicates that a function can be added to the My Favorites tab page. Click
next to the function. In the Add to Favorite dialog box, select a folder from the
Location drop-down list and click Add. The function is added to the folder on the My
Favorites tab page.
NOTE
If no folder exists under the My Favorites node, the Add to Favorite dialog box does not appear
Procedure
Step 1 Log in to a client the first time. On the Application Center tab page, right-click an application
to display its functions on the shortcut menu. Click next to a function. In the Add to
Favorite dialog box, select a folder from the Location drop-down list and click Add.
The function is added to the folder on the My Favorites tab page.
Step 2 Click the Function Search tab and enter a keyword to search for functions.
Click next to a function. In the Add to Favorite dialog box, select a folder from the
Location drop-down list and click Add. The function is added to the folder on the My
Favorites tab page.
NOTE
You can double-click a function in the list to open the main window of the function.
Step 3 Optional: Open the main window of an application. Choose an item on the menu bar and click
next to a function listed on the menu. In the Add to Favorite dialog box, select a folder
from the Location drop-down list and click Add. The function is added to the folder on the My
Favorites tab page.
Step 4 Log in to the client again. On the My Favorites tab, click a function to directly open its main
window.
You can choose My Favorites from the main menu and choose a function on the menu to quickly
launch the function.
----End
For how to switch the client to other style, see 1.8.2 Setting the Client Display Style.
Menu Bar
The menu bar provides the entries to all the functions of the U2000 client. It consists of the
following menus: File, Edit, View, Fault, Performance, Configuration, Service, Inventory,
Administration, Window, and Help.
NOTE
The menu items and sub-items displayed on the U2000 vary according to the components deployed on the
U2000 server.
Toolbar
The toolbar provides the shortcut icons for major operation tasks. For details, see 1.6.6
Frequently Used Shortcut Icon.
Workbench list
You can create or modify a workbench using the shortcut icons.
Output Pane
The output pane displays the returned information and other relevant information.
Status Bar
The status bar displays information such as the system status, the login users, and the IP address
of the connected server. The information displayed from left to right is as follows:
l Server and communication mode: Displays the name and IP address used for logging in to
the server and the communication mode between the client and server.
l Login user: Displays the name of the login user.
l Connection duration: Displays the client time in real time.
l System pop-up pane: Display a message in real time when the operation on the client is
affected. It can be disable and enable.
l Login mode: Displays the login mode. It can be single-user mode and multi-user mode.
l Connection status: Displays the status of the connection between the client and the server.
l Logo: Displays the logo of Huawei Technologies Co., Ltd..
Workbench
The shortcut icons on the workbench help you perform operations.
Component Example
Button
Shortcut icon
Radio button
Check box
Tab
Field
Drop-down
menu
Menu
Component Example
Function Tree
Dialog box
Button Function
Button Function
Button Function
NOTE
You can customize the toolbar to display only the frequently-used shortcut icons. To customize the toolbar,
right-click the toolbar and choose a menu item from the shortcut menu.
Control Description
Menu For a menu whose name is followed by an underscore _, you can press
Alt+_ to choose the menu item.
Drop-down menu For a drop-down menu whose name is followed by an underscore _, you
can press Alt+_ to choose the menu item.
Control Description
Drop-down list When the focus is on a drop-down list, you can press the Down arrow
key to expand the drop-down list. You can press the Up, Down arrow
keys to switch between the options in a drop-down list, and press
Enter to select the current option.
Option button If the focus is on an option button, you can press the space bar to select
the option button.
Check box If the focus is on a check box, you can press the space bar to select or
clear the check box.
Navigation tree When the focus is on the navigation tree, you can press the Down arrow
key or Up arrow key to switch between the nodes in the tree. And you
can press the Left arrow key or Right arrow key to expand or collapse a
node that contains subnodes.
Switching When there are multiple controls in a window, dialog box, or tab page,
between controls you can press Tab to switch from one control to another, and press Shift
+Tab to switch to the previous control.
Find Ctrl+F
Cut Ctrl+X
Copy Ctrl+C
Paste Ctrl+V
Save Ctrl+S
NOTE
The common area is under the toolbar on the U2000 client interface.
1.6.8.1 Workbench
This topic describes the workbench. After a client is started, the system automatically accesses
the default workbench. The default shortcut icons are displayed on the workbench.
l In the main window of the U2000, click the drop-down arrow next to and select Style
of Desktop to access the workbench.
l You can click to hide the left list of the workbench, then click to display the left list of
the workbench.
l You can view the description of the function of the workbench in the background picture
of the workbench and press F1 to view the Help.
l You can perform operations on the workbench. For details, see1.8.7 Setting the
Workbench.
Navigation Path
l In the Workbench Window, double-click the Main Topology icon.
l Choose View > Main Topology (traditional style) from the main menu or select Topo
View in Application Center and choose Topology > Main Topology (application style)
from the main menu.
GUI Description
l Open the Main Topology to ensure that main menu items are available.
l The U2000 provides multiple display modes of the client. For example, you can set an
alarm display mode for an object. For details about the meanings and setting methods of
display modes, see 1.8 Customizing the Client GUI Effect.
l The U2000 provides the focus display function. When the pointer stays over a shortcut
button for about 2 seconds, the U2000 will provide a focus display, presenting its meaning.
l The U2000 provides a variety of view windows according to different functions, and the
views can be switched.
– Select Physical Root from the Current View drop-down list. For details, see Physical
Root.
– Select Clock View from the Current View drop-down list. For details, see Clock
View. Alternatively, right-click in a blank area of the current subnet in the physical root
view and choose Switch to Clock View from the shortcut menu to switch to the subnet
in the clock view.
– Select Custom View from the Current View drop-down list. For details, see 5.9.1
Creating Custom Views.
Main Topology
Figure 1-28 shows the Main Topology of the U2000.
13 12 11 10 9 8 7 6
5: Alarm panel, Alarm 6: Legend, Filter and Attribute 7: Displays the client time in
button bar and Event button real time.
In this area, you can set the
The Alarm panel collects display modes of the objects in
statistics on alarms of the a view, view the descriptions
managed objects by alarm of legends and NE attributes in
severity and state according the view. For details about how
to the current alarm to locate an operation object
template. The alarm panel quickly, see 1.6.9.1 Filtering
provides the fault status of Operation Objects in a
the entire network. It can View.
work as a monitoring panel.
8: Views the name of the 9: Views the name which is set 10: Main Topology
logged-in U2000 user. by the current U2000 client,
the IP address of the current Views NEs.
U2000 server and the In the Main Topology, you can
communication mode between perform operations such as 5.6
the client and server. Creating NEs, 5.7
Configuring the NE Data, 5.8
Creating Connections, 5.10.2
Browsing Fibers/Cables, 5.9.5
Deleting Topology Objects,
7.8.10 Browsing the Current
Alarms, and 1.19 Starting the
NE Data Collection; enter the
1.6.8.3 NE Explorer to
configure the service for the NE
and so on.
11: Displays the mouse 12: Topology navigation tree 13: Browse Current Alarm
coordinate in the Main
Topology. In this area, all NEs managed In this area, you can browse the
by the U2000 are displayed. alarms that require attention and
You can locate the desired NE processing by setting the
quickly. filtering criteria of the current
alarm.
NE types and quantity are
displayed in the NE Statistics
table below the navigation tree.
1.6.8.3 NE Explorer
The NE Explorer is the main user interface used to manage equipment. In the NE Explorer, a
user can configure, manage and maintain the NE, boards, and ports on a per-NE basis. The NE
Explorer is the main user interface for commissioning and configuration on a per-NE basis. The
NE Explorer contains a Function Tree that makes the operations easy. To display the
configuration window for an object, select the object and choose a desired function in the
Function Tree.
NOTE
l For NEs of MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except PTN 6900
series) and marine series NEs, you can open a maximum of ten NE Explorer windows at the same time.
l Currently, NEs such as the OptiX OSN 1800, OptiX OSN 1832, OptiX OSN 6800, OptiX OSN 8800
series, OptiX OSN 9800 series can be managed individually or in optical NEs.
Navigation Path
l Right-click an NE in the Main Topology and choose NE Explorer from the shortcut menu.
l In the left-hand pane of the Main Topology, right-click an NE and choose NE Explorer
from the shortcut menu.
Related Operation
Navigation Path
In the Main Topology, select Clock View from the Current View drop-down list. Select the
NE to be queried or configured from the Object Tree. Figure 1-29 shows the clock view.
NOTE
For optical NE, in the clock topology right-click the NE and choose Browse WDM Clock Graph. You
can query clock NEs, clock tracing relationships, and clock synchronization status in the displayed window.
Clock link
NOTE
Legends
l After you choose View > Display Setting > Legend from the main menu, various legends
are displayed in different colors in the clock view.
l After you choose View > Display Setting > Filter from the main menu, the required
elements are displayed in the clock view based on the filter function. Virtual clock devices
cannot be filtered by clock type.
l After you choose File > Preferences > Topology Display Settings from the main menu,
the Preferences window is displayed and you can set the width of clock link by modifying
Link distance (pixels).
l The clock view uses continuous lines to represent the tracing relationships between NEs.
The number displayed on the continuous line indicates the priority of the traceable clock.
The smaller the number, the higher the priority. The clock view displays the line clock
source IDs only. Internal clock sources are numbered, but their IDs are not displayed in the
clock view.
l The arrow direction in the clock view indicates the clock tracing direction. For example,
if NE(9-722) points to NE(9-218), NE(9-218) traces the clock information transmitted from
NE(9-722).
l In the clock view, you can search for clock tracing relationships.
NOTE
The rule of verifying an invalid clock tracing relationship is as follows: Verify whether a clock source
is in the SSM protocol mode.
l In the non-SSM protocol mode, verify the status of a clock source. The status determines whether
a clock tracing relationship is valid.
l In the SSM protocol mode, verify the status of a clock source. If the status is unavailable, the
clock tracing relationship is invalid. If the status is available, you also need to verify the S1 byte
(clock quality). When you manually cancel settings of the quality of the S1 byte and the quality
of the S1 byte is unknown, the clock tracing relationship is invalid.
l In the clock view, there are indicators on an NE to indicate the time or lock lockout status.
When the lockout status of an NE is changed, you can search for clock links to update the
status.
l The clock view can display NEs copied in the physical root view and their clock tracing
relationships. NEs copied from an NE own the same clock tracing relationships as the NE.
l When you move the pointer over a clock NE, a tooltip pops up, displaying the NE's clock
mode, master clock ID, port status, and other information.
NOTE
The following modes are private working modes of PTP clocks:
l OC mode: In this mode, the communication with the network is performed through only one
IEEE 1588 port.
l BC mode: In this mode, the communication with the network is performed through multiple IEEE
1588 ports, which can be used for connections to multiple subdomains.
l TC mode: In this mode, a device that measures the time taken for a PTP event message to transit
the device and provides this information to clocks receiving this PTP event message. That is, the
clock device functions as an intermediate clock device to transparently transmit the clock and
process the delay, but does not recover the clock. It can effectively deal with the accumulated
error resulted from the master and slave hierarchical architecture. In this manner, the TC ensures
that the clock/time synchronization precision meets the application requirement.
l TC+BC mode: In this mode, the NE has the BC feature and handles only the delay, instead of
time synchronization.
l TC+OC mode: In this mode, the NE can transmit PTP packets transparently and process PTP
packets. The TC+OC mode is a combination of the TC and OC modes.
Related Concepts
Clock link: A clock link represents the clock tracing relationships between clock NEs. For
example, a clock link from NE A to NE B represents that NE B follows the clock signal from
NE A.
Related Operations
In the clock view, you can query and configure NE clocks network-wide. For details about the
clock operations, see Table 1-10.
Creating a virtual clock In the clock view, right-click You can create a virtual clock
device in the blank area and choose device to identify a device
Create Virtual Clock that is outside the managed
Device from the shortcut domain.
menu. A virtual clock device
represents a clock device that
exits on the network but not
within the local managed
domain. Generally, virtual
clock devices are relevant to
NEs in the local managed
domain in terms of tracing
relationships. In this case,
you need to create virtual
clock links on the U2000 to
help engineers view and
identify the clock tracing
relationships between NEs.
Creating a virtual clock link In the clock view, right-click You can create a virtual clock
in the blank area and choose link to identify the tracing
Create Virtual Clock Link relationships between a local
from the shortcut menu. NE and a device that is
outside the managed domain.
Searching for clock links In the clock view, right-click You can search for clock
in the blank area and choose links of NEs network-wide to
Search Clock Link from the learn the clock tracing
shortcut menu. relationships between NEs.
By using this function, you
can specify the search scope
based on the NE or clock link
types.
When the clock source traced
by an NE has changed, re-
search for the clock trace
relationship.
NOTE
To search for clock links, you
must obtain the license for the
clock management function.
Querying Clock- In the clock view, right-click You can search for the clock
Unsynchronized/Unlocked in a blank area and choose NEs in the unsynchronized or
NE Query Clock- unlocked state. Such NEs are
Unsynchronized/Unlocked listed in the lower pane. In
NE from the shortcut menu. this list, you can select
desired NEs and export their
data.
NOTE
l If the Display NEs in the
current subnet only check
box is selected, the search is
performed within the
current subnet.
l You can click Filter to set
the search scope.
l This operation applies to
ATN series, CX series, NE
series, PTN series, and
access NEs.
Synchronize with Physical In the clock view, right-click You can synchronize the
View in the blank area and choose coordinate positions of NEs
Synchronize with Physical and subnets in the clock view
View from the shortcut with the corresponding
menu. coordinate positions in the
Physical View.
In addition, after the
synchronization:
l The subnets that have
clock NEs are
synchronized from the
Physical View to the
clock view.
l The empty subnets in the
clock view are deleted.
Switching between clock Right-click the standby clock By switching between clock
links link and choose Switch to links, you can change the
this Clock Link from the current clock tracing
shortcut menu. relationships between NEs.
This operation applies only to
transport and PTN series
NEs.
Clearing Switching In the clock view, right-click Cancels clock link switching
a clock link and choose Clear so that NEs can select clocks
Switching from the shortcut to trace based on the clock
menu. source priority.
This operation applies only to
transport and PTN series
NEs.
Clock Attribute Right-click an NE and You can query the type of the
choose Clock Attribute clock that the current NE
from the shortcut menu. traces, hop count of the clock
tracing path, and the clock
compensation setting at the
clock tracing port.
Query Clock Loop In the clock view, right-click You can query clock loops
in the blank area and choose for network-wide NE clock
Query Clock Loop from the tracing relationships. In the
shortcut menu. query results, you can view
loop information.
If there are clock loops,
double-click a record in the
query result list to locate it on
NEs in the clock view. Then,
you can modify incorrect
configurations on the NEs.
Switch to Physical View In the clock view, right-click The GUI switches to the
in the blank area and choose corresponding subnet in the
Switch to Physical View physical view. If the subnet
from the shortcut menu. does not exit in the physical
view, the GUI will switch to
the root of physical view.
Synchronize the physical
view before performing this
operation.
Querying the clock tracing In the clock view, right-click The U2000 highlights the
path an NE and choose Display current clock tracing paths of
Current Tracing Path. clock NEs. When a fault
occurs, users do not need to
draw the clock tracing path
between NEs manually. This
improves fault diagnosis
efficiency.
View Cable Transmitting Choose Inventory > Clock In routine maintenance, users
Warp Report Report > Cable often need to measure clock
Transmitting Warp delays on chain and ring
Report (traditional style) networks. However,
from the main menu or select instrument-aided onsite
Fix-Network NE measurement is costly. To
Configuration in address this issue, the
Application Center and U2000 allows users to query
choose Inventory > Clock cable transmission warp
Report > Cable values for PTP clock links
Transmitting Warp between NEs. Users can
Report (application style) easily find the sites with large
from the main menu. warp values and perform
measurement only for these
sites. This function
effectively reduces site visits
and costs.
1.6.8.5 NE Panel
The NE Panel displays boards and ports in different colors indicating their current status. On
the U2000, most operations such as equipment configuration, monitoring, and maintenance are
performed in the NE Panel window.
Navigation Path
Double-click an NE in the Main Topology to display the NE Panel.
GUI Description
l For the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs, click on the toolbar to view the legends of
the boards and ports on the right of the Slot Layout.
l For the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs, right-click the NE Panel window and choose
Always On Top, the NE Panel window to always remain on top.
l When a board occupies multiple slots, the slot ID of the main slot is displayed in boldface,
and the slot ID of the slave slot is dimmed.
l In the NE panel, when you click the processing board equipped with an interface board,
the slot ID of this interface board is orange.
l For the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs, when you move the cursor to the installed board,
the board remarks is displayed. For the WDM series, WDM (NA) series, and Marine
series NEs, if you configure the wavelength informations on the installed board, when you
move the cursor to the board, the optical ports, band type, and wavelength is displayed.
l To perform an operation related to an installed board, right-click the installed board and
choose the corresponding submenu item from the shortcut menu. For example, you can add
a remark of the board in the Modify Remark dialog box by right-clicking the installed
board and choosing Remark.
Navigation Path
l Double-click an optical NE in the Main Topology. In the window that is displayed, select
an NE and click Signal Flow Diagram. See Figure 1-30.
l Double-click an NE in the Main Topology. In the displayed window, click Signal Flow
Diagram. See Figure 1-30.
GUI Description
l As in the NE Panel, you can perform operations on each board such as viewing alarms,
viewing WDM performance data, querying versions, and configuring a WDM NE in the
signal flow diagram. More importantly, the signal flow diagram provides the relationship
of fiber connections between each board of the ONE. It visually shows the direction of
traffic and improves the ability of the U2000 to maintain optical NEs.
l In the signal flow diagram, you can also create a fiber connection, query information about
the wavelength and port of each board, and rotate a board icon by 90, 180 or 270 degrees.
You can classify the same boards into a group, and print the signal flow diagram and so
on. The smallest unit of the signal flow diagram is a board. Boards of different types have
different icons. See legends for more information.
l Signal flow diagram is not applied to idle resource optical NEs.
l You can add a remark of the board in the Modify Remark dialog box by right-clicking the
installed board and choosing Remark.
l After an OSC board reports an R_LOS alarm, the fiber connected to the IN port of the FIU
board that is connected to the OSC board turns red. After the OSC board reports the
notification of clearing the R_LOS alarm, the fiber turns green.
Context
l Current alarm displays the merged alarms. The rules for merging alarms are as follows:
– The alarms whose alarm group IDs, alarm IDs, alarm location information, and alarm
sources are the same, and whose maintenance status is Normal are merged into another
current alarm record.
– The alarms whose alarm group IDs, alarm IDs, alarm location information, and alarm
sources are the same, and whose maintenance status is not Normal are merged into a
current alarm record.
l For a newly reported alarm, if the current alarm contains the record that meets the alarm
merging rule, the alarm is merged into the previous record in the current alarm regardless
of the acknowledgment and clearance status of the record. After merging, the frequency of
the record is added by 1. The displayed acknowledgment and clearance status of the record
is subject to that of the latest alarm. After the current alarm is changed to historical alarms,
the frequency recorded for the current alarm is reduced by 1.
l You can query details of each alarm log in the Browse Alarm Logs window.
l Alarm log records all the alarms received by the U2000. In the alarm log, each alarm is
displayed as a record.
l Alarms are not displayed in the current alarm list after they are acknowledged and cleared
and their life cycles end. However, you can query these alarms in the alarm logs and
historical alarms. For details about how to set the lifecyle of an alarm, see 7.5.11 Setting
the Lifecycle of the Current Alarm.
Navigation Path
l Choose Fault > Browse Current Alarm (traditional style) from the main menu or select
Fault Management in Application Center and choose Browse Alarm > Browse Current
Alarm (application style) from the main menu.
l Choose Fault > Browse Historical Alarm (traditional style) from the main menu or select
Fault Management in Application Center and choose Browse Alarm > Query
Historical Alarm (application style) from the main menu.
l Choose Fault > Browse Alarm Logs (traditional style) from the main menu or select Fault
Management in Application Center and choose Browse Alarm > Query Alarm Logs
(application style) from the main menu.
GUI
Choose Fault > Browse Event Logs (traditional style) from the main menu or select Fault
Management in Application Center and choose Browse Alarm > Query Event Logs
(application style) from the main menu.
Context
l The topology view displays the objects selected in the Topology Filter navigation tree,
such as subnets, NEs, background images.
l When the U2000 is started, the filter criteria are blank by default, and all the topology
objects are displayed.
l When you deselect a filter criterion, the objects matching the criterion are not displayed.
l Parent nodes in the Topology Filter navigation tree have three types of icons. indicates
that some topology filter items under a parent nodes are selected; indicates none of the
topology filter items under a parent nodes is selected; indicates that all topology filter
items under this node are not displayed in the topology view.
l Modified topology filter criteria take effect for the current user only. After this user logs
in next time, the settings still take effect.
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 Choose View > Show > Filter (application style) or View > Display Setting > Filter (traditional
style) from the main menu, or click on the toolbar. Click the Filter tab in the right pane.
Step 3 In the Topology Filter navigation tree, select the topology objects to be displayed in the topology
view.
NOTE
l Topology objects that are not selected are unavailable in the topology view.
l Click Other Conditions. In the displayed panel, specify the values for NE Name, Link Name, or
Subnet Name, and click Filter to filter objects again. The NEs, links, or subnets containing this string
(case insensitive) are displayed.
After the operations are successful, current view displays topology objects based on the filter
criteria.
Step 4 Optional: Click Filter Tree and select Switch. In the Switch a Filter Tree dialog box, select
the filter tree template, and click Open.
NOTE
Filter tree templates displayed in the Switch a Filter Tree dialog box indicate that filter trees have been
used and saved as filter tree templates. If no filter tree has been saved, no filter tree template is available
in the dialog box. To save a filter tree as a template, click Filter Tree and choose Save As. In the displayed
dialog box, enter a template name and click OK.
Step 5 Optional: To close the Legend/Filter/Properties panel, choose View > Show > Filter
(application style) or View > Display Setting > Filter (traditional style) from the main menu,
or click on the toolbar.
----End
Context
l If you search for NEs in the Physical Root or Clock View navigation tree in the Main
Topology, the search operation applies to the current view.
l If you search for NEs in the window outside the Main Topology, the search operation
applies to the Physical Root navigation tree.
l You can search out only the NEs for which you have management rights.
l During NE search, the U2000 searches for NEs in dynamic and fuzzy matching mode. That
is, the Search window displays search results in real time as you specify the search criteria.
l Transport NEs can be also searched out in Remarks mode.
Procedure
Step 1 Choose File > Find (traditional style) from the main menu or select Topo View in Application
Center and choose Topology > Search (application style) from the main menu.
The Search dialog box is displayed.
NOTE
You can also perform he following operations to access the Search dialog box.
l Press Ctrl+F in the Main Topology.
l Right-click in the Main Topology, and choose Find from the shortcut menu.
l Click .
Step 2 Select the search criteria, which are Search Type and Search Mode.
Step 3 Enter a keyword in the Keyword combo box or choose a keyword record from the drop-down
list.
Step 4 Optional: You can select Match whole word only, Case Sensitive or Auto search with
specified keyword as required.
NOTE
l Match whole word only: If you select this check box, only the results that exactly meet the conditions
are displayed.
l Case Sensitive: If you select this check box, the keyword is case-sensitive during search.
l Auto search with specified keyword: If you select this check box, when you enter the keyword, the
result is displayed dynamically.
Step 7 Optional: Select the Minimized after locating check box, the Search window is minimized
after the location.
----End
Context
l By default, the NE Statistics list is displayed on the left lower corner of the Main Topology
view of the client. If it is not displayed, Choose View > Display Setting > NE Statistics
(traditional style) from the main menu or select Topo View in Application Center and
choose View > Show > NE Statistics (application style) from the main menu.
l If certain objects are selected in the current topology view, the system collects statistics on
the NE types and quantity of the selected objects.
l If no object is selected in the current topology view, the system collects statistics on the
types and number of all NEs in the current topology view.
Procedure
Step 1 Choose View > Display Setting > NE Statistics (traditional style) from the main menu or select
Topo View in Application Center and choose View > Show > NE Statistics (application style)
from the main menu.
Step 2 Check the number of NEs in the NE Statistics list displayed on the left lower corner of the Main
Topology view.
----End
Procedure
l Right-click on the top of a parameter list, and choose the desired items from the shortcut
menu. The unselected items are not shown in the parameter list.
l Choose Column Settings from the shortcut menu. The Column Settings dialog box is
displayed. You can set whether to show a column in the parameter list, set the sequence of
columns and the column width.
----End
Procedure
Step 1 Select the text in a table, and press Ctrl+C.
NOTE
l Select all texts in the table by pressing Ctrl+A. Only the current screen of the table is supported.
l To view all data in the current table, click Print or Save As.
Step 2 Switch to another program, and press Ctrl+V. The selected text is copied to the system clipboard.
----End
Procedure
Step 1 Choose Browse Alarm > Display Alarm Panel (application style) or Fault > Display Alarm
Panel (traditional style) from the main menu or click the icon on the toolbar to open the
alarm panel.
The U2000 displays the Alarm Panel window, as shown in Figure 1-33. You can add a current
alarm template to the alarm panel if you want to monitor the alarms of specified severities on
NEs. For details, see 7.6.2 Setting the Alarm Panel. The alarm panel then displays alarm
information according to the preset template.
NOTE
l The bar charts in the Query Alarm Bar Chart window correspond to the template displayed on the
alarm panel. When you add or delete an alarm bar chart (alarm template) in the Query Alarm Bar
Chart window, the corresponding alarm template is automatically added to or deleted from the alarm
panel. In the same way, when you perform the add or delete operation on the alarm panel, the bar chart
in the Query Alarm Bar Chart window is modified accordingly.
l If a user changes the name, status, or search criteria of a template in the alarm panel on client B, the
changes can be synchronized to client A only after the user restarts client A.
----End
Procedure
l View the U2000 SPC version on the System Monitor.
1. Log in to the U2000 System Monitor.
2. Click the Component Information tab to view the component version information
about the U2000.
NOTE
Only the U2000 SPC version number can be viewed on the System Monitor. To view more version
information about the U2000 software, perform View the CP version of the U2000.
l View the U2000 SPC version on the U2000 client.
1. Log in to the U2000 client.
2. Choose Help > About from the Main Menu.
3. Click the About or Component tab to view the component version information about
the U2000.
NOTE
Only the U2000 SPC version number can be viewed on the U2000 client. To view more version
information about the U2000 software, perform View the CP version of the U2000.
l View the U2000 CP version on the U2000 server.
The version information is stored on the U2000 server as a configuration file named the
version number. Access the following directory to view all version information:
– In Windows: %IMAP_ROOT%\patch, such as D:\oss\server\patch
– In Solaris and Linux: $IMAP_ROOT/patch, such as /opt/oss/server/patch
NOTE
The CP version number can be obtained only by accessing the directory. One version can have either
0 patch or multiple CP patches.
----End
Context
The ranges of client GUI effect are for Current User and for Client. On the setting page, the
effect range is displayed on the topics of all items.The two types of ranges are described as
follows:
l for Current User: The current user can view the GUI effect after logging in to the
configured server from any client.
l for Client: All users can view the GUI effect after logging in to any server from the current
client.
Context
l After setting the skin color, you need to restart the U2000 client for the setting to take effect.
l The setting takes effect for all the users that log in to different clients.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences window, choose Skin in the navigation tree on the left.
----End
Context
l Users can switch the client display style to change the overall usability of the client and the
way client is launched. User can use either of the following two styles to launch the client:
– Application style
– Traditional style
l After setting the client display style, you must re-log in to the U2000 client for the settings
to take effect.
l The settings take effect for the current user that logs in different clients, but is invalid for
other users.
NOTE
The U2000 displays the navigation path of the Online Help in the Traditional style.
The Table 1-11 table describes the differences between the traditional style and application style.
Table 1-11 Differences between the traditional style and application style
Menu items cannot be searched for. Users can search for menu items.
The Favorites feature is not supported. You can add functions and menu items that
are frequently used to the Favorites tab.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences window, choose Client Display Style in the navigation tree on the left.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 From the navigation tree on the left of the Preferences window, select Main Window Title.
Step 3 In Main Window Title, enter the title you want to display.
----End
Result
The title that you set is displayed as the main window title.
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, choose the Topology Display Settings node in the left navigation
tree.
Step 3 In the Topology Display Settings dialog box, set Background Color, Subnet, Link, Node
Icon, and Node Label.
NOTE
Only the Label items settings in the Node Label area are synchronized to the topology tree. Other settings
do not take effect in the topology tree. Other settings are invalid for the topology tree.
The Display each label item in separate lines in the topology view option allows you to quickly
view the node information such as node name, IP address, and alias in the topology view. You
can refer to Table 1-12 to set Abridged label and Display each label item in separate lines
in the topology view.
Table 1-12 Set the Abridged label and Display each label item in separate lines in the
topology view check boxes
Select Abridged label and l If you do not select any topology objects or if you right-
Display each label item in click a topology object, the labels of all topology
separate lines in the topology objects are displayed in abridged mode. The items in
view. each node label are separated by colons (:).
l If you click a node, the node label is completely
displayed. This indicates that the items in the node
label are displayed in separated lines.
l If you click a link, the link label is completely
displayed in one line, regardless of the length of the
link label.
l If you press Ctrl to select multiple topology objects at
the same time, the items in the node label for the first
topology object are displayed in separated lines, but
the node labels for the remaining topology objects are
displayed in abridged mode.
Deselect Abridged label but The labels for each node and link are completely
select Display each label item displayed. This indicates that the items in each node label
in separate lines in the are displayed in separated lines.
topology view.
Select Abridged label but l If you do not select any topology objects or if you right-
deselect Display each label item click a topology object, the labels of all topology
in separate lines in the objects are displayed in abridged mode. The items in
topology view. each node label are separated by colons (:).
l If you click a node, the node label is completely
displayed. If the label length exceeds the abridged
label length, the node label is displayed in new lines.
l If you click a link, the link label is completely
displayed in one line, regardless of the length of the
link label.
l If you press Ctrl to select multiple topology objects at
the same time, the items in the node label for the first
topology object are displayed in separated lines, but
the node labels for the remaining topology objects are
displayed in abridged mode.
Deselect Abridged label and The labels of each node and link are displayed in one line,
Display each label item in and the items in each node label are separated by colons
separate lines in the topology (:).
view.
----End
Context
l After setting the font size, you need to restart the U2000 client for the settings to take effect.
l The setting takes effect for all the users that log in to different clients.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 From the navigation tree on the left of the Preferences window, select Font.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 From the navigation tree on the left of the Preferences window, select Output Window.
----End
Follow-up Procedure
You can perform the following operations in the information output area at the bottom of the
interface.
Operations Description
Select All 1. Right-click in the output window and choose Select All.
2. Right-click again and choose Copy to copy all the displayed output
information to the clipboard.
Clear Right-click in the output window and choose Clear to clear all the displayed
output information.
Operations Description
Save As Right-click to choose Save As. In the Save dialog box, save the current output
to a .txt file.
NOTE
Code formats ISO-8859-1 and UTF-8 are supported. The default encoding format is
ISO-8859-1. You are advised to use the default encoding format if the saved file does
not need to support multiple languages; otherwise, UTF-8 is recommended.
For .txt files, code formats ISO-8859-1 and UTF-8 are supported. The default encoding
format is ISO-8859-1. You are advised to use the default encoding format if the saved
file does not need to support multiple languages; otherwise, UTF-8 is recommended.
AutoScroll Right-click in the output window and choose AutoScroll. The output
information scrolls automatically to the latest information. Right-click in the
output window again and choose AutoScroll, the auto scroll is disabled.
Parameter Right-click in the output window and choose Parameter Settings. The
Settings Output Window pane is displayed in the Preferences window.
Prerequisites
You have logged in to a client in the traditional style.
Context
l After setting the workbench display, you must re-log in to the U2000 client for the settings
to take effect.
l The maximum number of links on the workbench is 100.
l The settings take effect for the current user that logs in different clients, but is invalid for
other users.
Procedure
l You can perform the following operations on the workbench.
Option Description
Option Description
Create a shortcut for U2000 In the Workbench window, you can create
function shortcuts for U2000 functions.
Option Description
Arrange Icons by Name In the right pane of the Workbench window, right-
click in a blank area and choose Arrange Icons by
Name from the shortcut menu to sort shortcut icons.
After sorting, icons are listed horizontally.
Drag an icon to another position In the Workbench window, drag an icon to a proper
position.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences window, choose Menu Settings in the navigation tree on the left.
Step 3 Select Enable folding menus to enable the menu folding feature.
NOTE
----End
Context
l After setting, the alarm icon in the topology view, the alarm record you have queried, and
the alarm indicator on the alarm panel are displayed in the specified colors.
l By default, the U2000 provides four types of colors for alarms. critical: , major:
, minor: , and warning: .
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, choose Color Settings in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the Color Settings area, click in each row to select the colors of alarms.
----End
Context
l For the alarm that meets the highlighting condition, if the difference between the local time
of the client and the alarm occurrence time reaches the threshold time for highlighting, the
alarm is highlighted.
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, expand the Alarm Local Terminal Settings node and choose
Highlighting in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the Highlighting area, set the time and alarm status for alarms of a certain severity, and then
select Enable.
NOTE
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, in the navigation tree on the left, expand the Alarm Local
Terminal Settings node, and then select Alarm Fonts.
Step 3 In the Alarm Fonts area, set fonts, sizes, styles, and colors for alarms that are not read and that
are already read.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, expand the Alarm Local Terminal Settings node and choose
Alarm Display Mode in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the Alarm Display Mode area, select an alarm display mode, and set background colors for
different alarm states.
All the other fields The background colors of all the other fields are
displayed based on the state.
All the other fields The background colors of all the other fields are
displayed based on the state.
NOTE
The first column of the current alarm is not rendered, because it is not affected by the setting of the alarm
display mode.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, expand the Alarm Local Terminal Settings node and choose
New Alarm/Event in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the New Alarm/Event group box, select Alarm Severities Shown at Top of Screen and the
alarm severity.
Step 4 In the New Alarm/Event group box, select Display at the top or Display at the bottom.
Step 5 In the Alarm Severities Shown in Alarm Lamps group box, select the severity to be displayed
on the alarm indicator.
----End
Context
l Acknowledged and cleared alarms are not displayed in the topology view, because they
indicate that the faults are already rectified. For details about the meaning of each alarm
state, see 7.1.3 Alarm Status.
l A subnet does not generate alarms. However, when the NEs or links in the subnet generate
alarms, the subnet displays the alarms of the highest severity. The alarm display mode for
subnets is the same as that for NEs.
l A container NE can generate alarms. The alarm status display mode for a container NE is
the same as that for an NE. When an NE in a container NE generates an alarm, an alarm
icon appears on the container NE in the topology view. For details, see Icons Indicating
That Alarms Are Contained.
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the navigation tree in the Preferences dialog box, choose Topology Status Display.
Step 3 In Topology Status Display, set the alarm display properties in the topology view.
Display Style of Alarm States In Display Style of Alarm States, set the display style of
alarm states.
NOTE
Links support only the Use icon colors display style regardless of
the value of Display Style of Alarm States.
Alarm States to Display in the In Alarm States to Display in the Topology View, set the
Topology View alarm state to be displayed in the topology view.
l If you select only Unacknowledged alarms, only the
unacknowledged alarms of the highest severity are
displayed.
– For NEs, if Use icon colors is selected, the alarm
state is displayed in the color of NE icon frame. If
Use state icons is selected, the alarm state is
displayed in the round icon.
– For links, the links are rendered.
l If you select only Uncleared alarms, only the uncleared
alarms of the highest severity are displayed.
– For NEs, if Use icon colors is selected, the alarm
state is displayed in the color of NE icon. If Use state
icons is selected, the alarm state is displayed in the
triangle icon.
– For links, the links are rendered.
l If you select both Unacknowledged alarms and
Uncleared alarms, for NEs, unacknowledged alarms of
the highest severity and uncleared alarms of the highest
severity generated on NEs are displayed; for links,
unacknowledged alarms and uncleared alarms of higher
severity generated on links are displayed.
NOTE
The unacknowledged alarms and uncleared alarms generated
on links are displayed by rendering the links. Therefore, if you
select both Unacknowledged alarms and Uncleared
alarms, you cannot determine the whether generated alarms
are unacknowledged alarms or uncleared alarms. To check
whether unacknowledged alarms or uncleared alarms are
generated on a link, you can select this link, click on the
topology toolbar, and check the alarm information displayed
on Properties tab page on the Legend & Filter &
Properties panel.
----End
Context
l After setting the number format, you must re-log in to the U2000 client for the settings to
take effect.
l After you modify the number settings, the display of the number may be changed. You can
view the display effect in the Positive number text box and Negative number text box.
l The settings take effect for the current user that logs in different clients, but is invalid for
other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, select Number Format from the navigation tree on the left.
Step 3 Set the number display format in the Number Format area.
NOTE
l Digits after decimal point: To set the number of digits after the decimal point. The value ranges from
0 to 3, and the default value is 2.
l Number separator: To select the separator for the integer part of a number. The value can be empty
or comma (,), and the default value is comma (,).
l 0 before decimal point: whether to add 0 before the decimal point. By default, 0 is added before the
decimal point.
----End
Context
The U2000 provides two colors, which indicate that a board works in the normal state: gray and
green.
Procedure
Step 1 Choose Administration > NE Software Management > FTP Settings (traditional style) from
the main menu or select Fix-Network NE Software Management in Application Center and
choose NE Software Management > FTP Settings (application style) from the main menu.
Step 2 In the Preferences window, choose Board State from the navigation tree.
----End
Context
l After setting the time format, you must re-log in to the U2000 client for the settings to take
effect.
l Next time when you log in to the client, the U2000 client automatically uses the settings
that you set last time.
l The settings take effect for the current user that logs in different clients, but is invalid for
other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 From the navigation tree on the left of the Preferences window, expand the Region Settings
node and choose Time.
Step 3 In the Time group box, set the time format. The time display effect that you set is displayed in
the Time example.
----End
Context
l After setting the date format, you must re-log in to the U2000 client for the settings to take
effect.
l Next time when you log in to the client, the U2000 client automatically uses the settings
that you used last time.
l The settings take effect for the current user that logs in different clients, but is invalid for
other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the navigation tree on the left of the Preferences window, expand the Region Settings node
and select Date.
l Date separator: symbol to separate the date. There are three symbols for you to select: "/", "-", and
".". The default is "/".
l Date format: display format of the date. It can be set to "yyyy/MM/dd", "MM/dd/yyyy", or "dd/MM/
yyyy". The default is "MM/dd/yyyy".
----End
Context
l After setting the time mode, you must re-log in to the U2000 client for the settings to take
effect.
l Next time when you log in to the client, the U2000 client automatically uses the settings
that you used last time.
l The settings take effect for the current user that logs in different clients, but is invalid for
other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the navigation tree on the left of the Preferences window, select Time Mode.
NOTE
l Server time mode: If you select this option, the time on the U2000 client is displayed based on the
time zone where the server is located. For example, if the time of the client in UTC +08:00 is 10:00,
and the server is in the UTC +07:00, the time displayed on the U2000 client is 9:00. Server time
mode is used by default.
l Client time mode: If you select this option, the time on the U2000 client is displayed based on the
client OS time.
----End
Procedure
Step 1 Choose File > Customize Toolbar from the main menu.
Step 2 In the Customize Toolbar dialog box, select System, Security, Fault or Main Topology in the
Toolbars group box.
Step 4 In the Toolbar Buttons group box, set the buttons you want to display on the toolbar.
l In the Available Tools group box, select one button or hold down Ctrl or Shift to select
multiple buttons you want to display. Click to move the selected buttons to the
Customized Tools group box.
l In the Customized Tools group box, select one or hold down Ctrl or Shift to select multiple
buttons you do not want to display. Click to move the selected buttons to the
Available Tools group box.
NOTE
You can click Reset or Reset All to restore the selected or all toolbars to their initial state. These operations
help you adjust the display mode of buttons on the toolbar based on the initial state.
Step 6 Optional: Adjust the positions of the toolbars in the toolbar tray.
1. Right-click in the blank area and choose Lock Toolbar from the shortcut menu. If Lock
Toolbar is not selected, you can skip this step.
2. Drag the toolbars to change their positions.
3. After that, right-click in the blank area and choose Lock Toolbar from the shortcut menu.
The toolbars are locked, which prevent the toolbars from being moved by mistake.
NOTE
Right-click in the blank area and choose Reset Toolbar from the shortcut menu. The toolbars are restored
to their initial states.
----End
Context
l The audio files used for prompting network disconnection support only the audio files of
the WAV type in the PCM format. The audio files of the WAV type can be recorded in two
formats: PCM and Microsoft ADPCM.
l The setting takes effect for all the users that log in to different clients.
l Some computers in the sleep mode may close network connections automatically, the
U2000 plays the sound. You can change the sleep mode to solve the problem.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, select Disconnection Alert from the navigation tree on the left.
Step 3 In the Disconnection Alert group box, select Sound an alert when the client is disconnected
from the server.
Step 4 Click . In the Open dialog box, select an audio file, and then click Open.
----End
Context
If the U2000 server is upgraded but the client is not upgraded, it may cause the version of the
client does not match that of the server.
Procedure
Step 1 Choose OSS Security > Check for Upgrades (application style) or Help > Check for
Upgrades (traditional style) from the main menu to check whether the client version matches
the server version.
l When the versions match, the client does not need to be upgraded. In this case, click OK.
l When the versions do not match, you must upgrade the client. In this case, perform the
following operations to upgrade the client:
1. Click OK.
2. In the Update Wizard: Update Applications window, click Continue. The upgrade
progress is displayed.
3. In the Update Wizard: Update Applications window, click Finish.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, in the navigation tree on the left, select Upgrade.
Step 3 Select the interval for upgrade checking in the Interval drop-down list box.
Step 4 Click OK.
----End
Prerequisites
The U2000 client is not locked.
Context
In the Preferences dialog box, select Show main window when terminal locked in the Lock
Settings area. Thus, after the client is locked, the main window of the client is visible.
Procedure
l The following table describes how to set the client to be locked manually or automatically.
Automatically After you set the client to be locked automatically, the client is
automatically locked if it does not receive any operation
instructions in the specified period.
----End
Prerequisites
The U2000 client is locked.
Procedure
The following table describes how to unlock the client in different scenarios.
If the current user l A user in the SMManagers group need to reset the current user
forgets the password password. For details, see 3.3.3.2 Resetting the Password of an
NMS user. Then log in to the client again using the user name and
the new password.
NOTE
A user in the SMManagers group cannot reset the password of the
admin user. If the current user is admin, only a user in the
Administrators group can unlock the client.
l The current user must ask a user in the Administrators group to
unlock the client. After the client is unlocked, the current user is
logged out.
1. Press Ctrl+Alt+U or click .
2. Enter the user name and password of the user in the
Administrators group, and click OK.
NOTE
If the number of password retries reaches the upper limit (3 by default), the user account is locked for a
specified period (30 minutes by default). The U2000 user is automatically unlocked after the auto-unlocking
duration. The U2000 user can also be unlocked by security administrators manually. For details, see 3.3.4.4
Unlocking Users.
Context
l The settings take effect only for the current client. You need to set the log level again if the
client is restarted.
l The log file records the client running information, such as user login and logout time,
helping the maintenance personnel locate the problems on the live network.
Procedure
Step 1 Press Ctrl+Alt+Shift+L.
If you clear the Enable Logging check box, the log level cannot be set and the client does not record logs.
Step 3 In the Log Settings dialog box, click the drop-down icon next to Log Level and select the level.
NOTE
The available log levels are described as follows:
l Detail: This is the lowest and default log level. It indicates that the client records all operation logs.
l Debug: This log level is higher than Detail, and it indicates that the client records all operation logs
except those at the Detail level.
l Warning: This log level is higher than Debug, and it indicates that the client records operation logs
at the Warning and Error/Exception levels.
l Error/Exception: This is the highest log level, and it indicates that the client records logs only at the
Error/Exception level.
----End
Result
After you set the log level, the client record operation logs in Client installation directory\client
\client\var\log.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
If a large number of performance data need to be collected, this may cause communication
congestion and thus the communication between the U2000 and NEs stops. Hence, observe the
following rules to collect the performance data:
l When creating a single performance data collection task, the number of NEs related to the
same GNE does not exceed 5.
l Run the performance data collection task when network traffic is low.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
If the Run now check box is selected, a scheduled task will run immediately.
At other time except DST, the option DST is unavailable.
4. Follow the task creation wizard to set the parameters of the scheduled task and click
Next for several times until the Finish button is displayed.
5. Click Finish. A scheduled task is successfully created.
Step 3 Optional: Double-click a scheduled task to modify the parameters of the task.
Step 4 Optional: Right-click a scheduled task and choose Suspend/Resume Schedule to set the
suspend time or the resume time for the task. Click OK.
Step 5 Optional: Right-click a scheduled task and choose Run now to start executing the task.
NOTE
Run now means to immediately execute the task, no matter the scheduled time comes or not. Resume
means to start the scheduled task. The task is executed at the scheduled time.
----End
Procedure
Step 1 Choose System > Broadcast Message (application style) or Administration > Broadcast
Message (traditional style) from the main menu.
Step 3 In the Options dialog box, enter the values in Max. messages to display and Max. messages
to save, click Save.
NOTE
l Max. messages to display is valid only for the current client, not for the server.
l Max. messages to save is valid for all clients that are connected to the same server. The parameter
configured by a user affects the experience of other users.
l You are advised to set Max. messages to display only for your computer, and Max. messages to
save is set by the administrator of the U2000 server.
l The displayed messages are read from the buffer on the server, therefore, you need to set Max. messages
to display to a value that is less than or equal to Max. messages to save.
----End
Context
l The client can receive its own broadcast messages. The output area in the lower part of the
U2000 client displays corresponding prompts.
l You have both permissions to set broadcast message parameters and send broadcast
messages.
l Only the online U2000 client can receive the broadcast messages.
Procedure
Step 1 Choose System > Broadcast Message (application style) or Administration > Broadcast
Message (traditional style) from the main menu.
Step 2 In the Broadcast Message dialog box, enter the message content in the New Message field.
CAUTION
Do not enter important information such as passwords.
NOTE
The U2000 automatically adds line feeds according to the length of broadcast messages.
----End
Result
When the sending is complete, the Information dialog box is displayed on other clients. Users
can click Detail to view the message.
Context
l The license file is not delivered to customers along with the U2000 installation DVD.
Contact Huawei engineers to apply for the licenses according to the contract number and
the equipment serial numbers (ESNs) of the oss server.
l To prevent the failure in finding the license file for possible U2000 reinstallation, save the
license application email and the license file properly.
l Before using the U2000, apply for a formal U2000 license (recommended) or a temporary
U2000 license. The application of a U2000 license takes a long time. Therefore, apply for
it in advance.
l An ESN is a string consisting of 40-digit numerals or letters obtained by encrypted
calculation on the MAC addresses of the U2000 server network interface. The number of
ESNs is the same as the number of network interfaces on the U2000 server. To avoid
applying for a new license due to replacing certain network interface cards (NICs), save
all the ESNs to ensure proper use of the U2000 license.
– Generally, the ESN for a server does not change. It can be used for the U2000 license
that is normally applied for.
– If the ESN for a U2000 license is changed due to NIC or server replacement or ESN
application error, apply for a U2000 license again and contact Huawei technical support
engineers.
l The requirements for the ESNs of the server to which a license needs to be bound vary
according to the installation scheme. You must obtain ESNs of the server based on the
installation scheme.
– In a centralized single-server system scheme, the license needs to be bound to the ESNs
of the server.
– In a centralized high availability system (Veritas hot standby) scheme, the license needs
to be bound to the ESNs of the servers on both the primary site and the secondary site.
Procedure
Step 1 Obtain the contract number.
Step 2 Use the ESN tool provided by the U2000 to view ESNs of the server.
NOTE
If the U2000 has been installed, using the ESN tool of the U2000 to view the ESN is recommended.
Mode 1: View the ESN using the ESN tool of the NMS after installing the U2000.
When a high availability system scheme is used, you must log in to the OSs of the primary and
secondary sites as the ossuser user.
2. Run the following commands to view ESNs:
# cd /opt/oss/server/platform/bin
# ./esn
NOTE
If a high availability system scheme is used, you must respectively save the ESNs for the primary and secondary
sites. During the application for a formal license, you must provide the ESNs of the network interfaces of the
primary and secondary sites for external communication.
Mode 2: Use the ESN tool to generate ESNs before installing the U2000.
NOTE
Solaris or SUSE Linux is used as an example to describe how to use the downloaded ESN tool
to generate ESNs.
1. Use SFTP to upload the ESN tool to the U2000 server as the root user. For example, upload
the ESN tool to the /opt path. For details, see How to Use the FileZilla to Transfer Files by
SFTP.
2. Run the following commands to decompress the ESN tool package:
# cd /opt
# tar xvf U2000version_ESN_solaris_SPARC.tar
Step 3 After the esn command is executed, the system automatically generates the Esn.txt path. Send
the contract number and the server ESNs to Huawei engineers or the local Huawei office.
NOTE
Huawei engineers access http://license.huawei.com to obtain the license based on the contract number
and ESNs.
Step 4 Huawei engineers send the license file to you after obtaining it.
NOTE
The license file provided with the U2000 exists as a .dat file.
----End
Prerequisites
l The OS and database must run properly. For details on how to start the OS and database,
see 1.2 Starting the U2000 System.
l The processes of the U2000 must be properly started. For details on how to start the
U2000 processes, see 1.2 Starting the U2000 System.
l You must log in to the U2000 client as the admin user.
l The license file of the U2000 must be obtained. The license file name can contain digits,
letters, and special characters excluding the space or \ /:*?"<>|.
– Through the GUI of the client: Save the new U2000 license to the server where the
U2000 client is located.
– Through the CLI: The new license file must be transferred to the U2000 server through
SFTP.
– In the Solaris OS, upload the license file to the /export/home/ossuser path on the
server as the ossuser user.
– In the SUSE Linux OS, upload the license file to the /export/home/ossuser path on
the server as the ossuser user.
– In the high availability system, upload the new U2000 license file to the /export/
home/ossuser path on the server on the primary site through SFTP.
l After the U2000 is installed, you must load the U2000 license to ensure that the U2000 is
available.
For details, see the updated contents about the U2000 license in this topic.
l Confirm that the license file is transferred in text mode, that is, in ASCII mode.
Context
l If the U2000 license file is unavailable, you cannot log in to the U2000 client. Update the
U2000 license file in time.
l During the update of the U2000 license file, you can replace the formal U2000 license file
with the temporary one; It is recommended to use the formal U2000 license as soon as
possible.
l The licenses of different R versions of the U2000 are incompatible. For example, the license
of V100R001 cannot be used by V100R002.
l Determine whether to update the U2000 license file based on the U2000 license use
conditions.
– In the case that the device types supported by the new license are different from those
supported by the original license, the license is updated as follows:
– If the device types supported by the new license are more than the device types
supported by the original license and the added device types are supported by the
current version, the license can be updated. If the added device types are not
supported by the current version, the license cannot be updated.
– If the device types supported by the new license are less than the device types
supported by the original license and no NEs of the reduced device types are created
in the NMS, the license can be updated. If certain NEs of the reduced device types
are created in the NMS, the license cannot be updated.
– For IP domain, if the function items supported by the new license are less those
supported by the original license, the license cannot be updated.
– In the case that the number of clients supported by the new license is different from that
supported by the original license, the license is updated as follows:
– If the number of clients supported by the new license is less than that supported by
the original license but the number of online clients is less than the number of clients
supported by the new license, the license can be updated. If the number of online
clients is greater that the number of clients supported in the new license, the license
cannot be updated.
– If the number of clients supported by the new license is greater than that supported
by the original license, the license can be updated.
NOTE
If NE license items for the IP domain are deleted from the updated license, restart the license service
after license update. The service and process names are LicenseService and lic_agent respectively.
For details about how to restart the service, see chapter Starting and Stopping a Process in U2000
Administrator Guide.
l In scenarios where you can change the license, you can update the U2000 license and then
restart the server.
– You can update the U2000 license through the GUI or CLI.
Restart the client after you replace a license. Then, the client automatically reloads the
menu items according to the control items defined in the new license.
– Through the GUI of the Client:
– Application scenario: This method is recommended if you can log in to the
U2000 client and access the GUI.
– Operation method: Log in to the U2000 client, and then click Update License
to update the license.
Restart the client after you update the license. Then, the client automatically
reloads GUI elements according to control items defined in the new license.
– Through the CLI:
– Application scenario: This method is applicable to the scenario where you need
to remotely update the license through commands because logging in to the
U2000 client is not allowed and the client does not provide any GUI.
– Operation method: Check that the processes of the U2000 are properly started,
and then run the updateLicense -file filename command to update the license
file.
– It is recommended that you update the U2000 license through the GUI of the client.
If the license updated through the GUI of the client requires deploying the NE Explorer
or other processes, a message will be displayed when you start the U2000 processes
after updating the license. Viewing the process startup status on the System Monitor
client and performing operations after all the processes have been started are
recommended.
– To ensure the normal running of the U2000, do not manually replace the license file.
NOTE
To make both the U2000 commercial and temporary licenses take effect, use the GUI mode.
Procedure
l Through the GUI of the Client
For the single-server system:
1. On the U2000 workstation, back up the original license file.
– In the Windows OS: Create the backup folder in the default directory D:\oss
\server\etc\conf\license. Copy the original license file to the created folder.
– In the Solaris or SUSE Linux OS:
run the following commands to back up the any other license file to the /opt/oss/
server/etc/conf/license path.
$ mkdir -p /opt/oss/server/etc/conf/license_backup
$ cd /opt/oss/server/etc/conf/license
$ cp license_file_name /opt/oss/server/etc/conf/license_backup
NOTE
After SetSolaris is enabled, only the SSH service for the ossuser user has the login right. The
SSH login mode is recommended for your system security. To use another login mode such as
Telnet, you must enable the access right for the Telnet service and the login user. For details,
see How to Start/Stop the FTP, SFTP, and Telnet Services and How to Enable and Disable the
FTP/Telnet Authority of user root on Solaris OS.
2. Update the U2000 License file through the GUI of the U2000 Client.
a. Choose Help > License Management > License Information (traditional style)
from the main menu or select System Management in Application Center and
choose License Management > License Information (application style) from
the main menu.
b. In the License Information dialog box, click Update License.
c. Select the new license file and click Open.
d. Click Next.
e. Select a scenario and perform the associated operations as required:
– If Incremental is unavailable, click Next.
– If Incremental is available and only the new U2000 license needs to be
effective, select Full and click Next.
– If Incremental is available and both the new and in-use U2000 licenses need
to be effective, select Incremental and click Next. If the in-use U2000 license
has a commercial license and a temporary license, the new license will replace
the license of the same type. For example, if the new license is a commercial
license, the commercial license in the in-use U2000 license will be replaced.
f. Click Finish.
g. Click Yes and confirm the updated license.
h. Click Yes to close all windows.
i. Click Yes to log out of the system.
3. Restart the client after you replace a license. Then, the client automatically reloads
the menu items according to the control items defined in the new license.
For the HA system:
1. Log in to the U2000 server on the primary and secondary sites.
2. Back up the original U2000 license file on the primary and secondary sites.
Create the backup folder in the default path. Then, copy the original license file to
this folder.
NOTE
l The default path of U2000 license file in the Solaris or SUSE Linux OS is /opt/oss/server/
etc/conf/license.
l The default path of U2000 license file in the Windows OS is D:\oss\server\etc\conf
\license.
3. Update the license file on the primary site.
a. Log in to the OS where the U2000 client is installed.
– In Windows, log in to the OS as a user with administrator rights.
– In Solaris, log in to the OS as the ossuser user.
b. Save the license to be loaded to the server where the U2000 client is installed.
c. On the desktop, double-click U2000 Client. The Login dialog box is displayed.
d. In the Server drop-down list, select the server (server on the primary site) to be
logged in to. Then, set User Name and Password to the valid values, and click
Login. The initial password of the admin user is Changeme_123 (It is
Admin_123 for a U2000 that comes preinstalled). The password must be
changed during the first login to ensure system security. Keep the password
confidential and change it regularly.
NOTE
During data synchronization between the primary and secondary sites, do not perform
this operation.
c. Select the Clusters and Systems to be switched.
d. Click OK.
e. In the Confirm dialog box, click Yes to switch U2000 services to the secondary
site.
f. Use the U2000 client to reconnect to the system IP address of the secondary site.
NOTE
NOTE
After SetSolaris is enabled, only the SSH service for the ossuser user has the login right. The
SSH login mode is recommended for your system security. To use another login mode such as
Telnet, you must enable the access right for the Telnet service and the login user. For details,
see How to Start/Stop the FTP, SFTP, and Telnet Services and How to Enable and Disable the
FTP/Telnet Authority of user root on Solaris OS.
2. Update the U2000 license.
– In the Windows OS:
a. Log in to the OS as a user with administrator rights.
b. Run the following command to update the U2000 license file:
> updateLicense -file License_file_name
NOTE
NOTE
Create the backup folder in the default path. Then, copy the original license file to
this folder.
NOTE
l The default path of U2000 license file in the Solaris or SUSE Linux OS is /opt/oss/server/
etc/conf/license.
l The default path of U2000 license file in the Windows OS is D:\oss\server\etc\conf
\license.
3. Run the updateLicense command to update the license file on the primary site. For
details, see Step 2.
4. Transfer the updated license file on the primary site to the /opt/oss/server/etc/conf/
license path on the server on the secondary site in text mode, that is, ASCII mode.
NOTE
l The default path of U2000 license file in the Solaris or SUSE Linux OS is /opt/oss/server/
etc/conf/license.
l The default path of U2000 license file in the Windows OS is D:\oss\server\etc\conf
\license.
l In the Solaris or SUSE Linux OS: You should transfer the updated license file on the
primary site to the server on the secondary site in text mode, that is, ASCII mode. In the
Windows OS: Copy and paste the updated license file on the primary site to the server on
the secondary site.
5. Restart the client after you replace a license. Then, the client automatically reloads
the menu items according to the control items defined in the new license.
----End
Result
After the preceding operations are performed, the license file is automatically loaded to the /opt/
oss/server/etc/conf/license path.
Context
By checking the U2000 license status, you can learn whether the U2000 license control items
are correct. If a license control item is incorrect, the related functional module is unavailable.
For example, if the license control item for the U2000 E2E module is absent, tunnels cannot be
created.
Procedure
Step 1 Log in to the U2000 Client.
Step 2 Choose Help > License Management > License Information (traditional style) from the main
menu or select System Management in Application Center and choose License
Management > License Information (application style) from the main menu.
Step 3 In the License Information dialog box that is displayed to view the condition of the license.
----End
Prerequisites
You have logged in as a user who belongs to the Administrators or SMManagers user group.
Context
The Revoke License dialog box displays only available License files and does not display
revoked and invalid Licenses.
Procedure
Step 1 Choose License Management > Revoke License (application style) or Help > License
Management > Revoke License (traditional style) from the main menu.
Step 2 In the Revoke License dialog box, select the License that is not used any more, and then click
Revoke License.
NOTE
----End
Result
If you revoke a License file but do not apply a new License, the U2000 displays a dialog box
every hour, prompting you to update the License. The U2000 also displays License SN,
Revocation Time, Valid Date (indicating the date before which the revoked License can still
be used) of the License, and License File.
Procedure
Step 1 Choose License Management > Query License Revocation Code (application style) or
Help > License Management > Query License Revocation Code (traditional style) from the
main menu.
Step 2 In the Query License Revocation Code dialog box, view the License SN, License revocation
code, and revocation setting time.
NOTE
Step 3 Right-click the information about the revocation code and choose Copy to copy the information.
The copied information about the revocation code can be used to apply for a certificate.
NOTE
You can also select the information about the queried revocation code, and then press Ctrl+C to copy the
information.
----End
export tasks periodically or instantly to dump the Licenses information used by the U2000, and
save them as an XML file to the specified folder.
Context
If the current License file used by the U2000 becomes invalid due to the License initialization
failure, the exporting task is not executed, and users need to contact Huawei technical support
to update the License.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Take Type navigation tree, choose File Interface > OSS License Export.
Step 3 In the task list on the right, double-click the OSS License Export task.
Step 4 In the Attribute dialog box, set the parameters on the Common Parameters and Extended
Parameters tab pages, and then click OK.
----End
Procedure
Step 1 Choose Settings > Management Capacity Alarm Settings (application style) or
Administration > Settings > Management Capacity Alarm Settings (traditional style) from
the main menu.
Step 2 In the Management Capacity Alarm Settings dialog box, enter the License threshold in
Threshold.
Step 3 Optional: Select the Display periodical warning check box. In Warning interval(minutes),
set the interval.
----End
Result
When the proportion of the number of accessed NEs to the License capacity reaches the threshold
specified for the License capacity, the U2000 generates The NE Capacity Reached the
Threshold Alarm and periodically displays an Information dialog box. When the proportion
is less than the threshold specified for the License capacity, the U2000 clears The NE Capacity
Reached the Threshold Alarm and the Information dialog box is not displayed any more.
Prerequisites
This operation applies only to the service licenses that are consumed and charged based on ports.
Context
l License items are subtracted when you add a board rather than when you create a service.
The number of service license items is subtracted by the number of ports on the new board.
l The U2000 checks the number of service license items at scheduled time every day and
enters the grace period when the number of remaining license items reaches the threshold.
During the grace period, there is no restriction on your operations. When the grace period
expires, you cannot create services. However, existing services are still functioning
properly. Because the deleted services cannot be recreated, excise caution when deleting
the services.
l The grace period ends for the U2000 when you update the service license with a new valid
one. If resources are still insufficient, the start and end time of the grace period are
recalculated.
l The U2000 reports ALM-801 OSS License Beyond Limitation when it enters the grace
period. Contact your Huawei engineers for new licenses.
l Service licenses do not restrict NE functions. That is, NE licenses are not affected by service
licenses.
Procedure
Step 1 Choose Help > License Management > Statistics of Service Ports (traditional style) from the
main menu or select System Management in Application Center and choose License
Management > Statistics of Service Ports (application style) from the main menu.
Step 2 In the Statistics of Service Ports dialog box, view the number of ports consumed in each service
license.
NOTE
Choose Help > License Management > License Information (traditional style) from the main menu or
select System Management in Application Center and choose License Management > License
Information (application style) from the main menu. In the License Information dialog box, click the
Resource Control Item tab and view Capacity, Consumption, and Overflow Time of different resource
control items in the current licenses.
Step 3 Optional: Click Advanced. In the Advanced Settings dialog box, view the number of free
inventory resources.
Step 4 Optional: Click Export and save the port statistics to a TXT, CSV, HTML, or XLS file.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Optional: Double-click an optical NE on the topology. The NE Panel is displayed. Select an
NE from the object tree on the left.
Step 2 Right-click an NE and choose Start WEB Client from the shortcut menu. The Web LCT user
interface is displayed.
NOTE
Enter the default user name proxyuser and password Changeme_123. If the user name and password need
to be changed, see Security Management > User Security Policy Management > Managing Web Proxy
Users in the U2000 System Administrator Guide.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l It is applicable to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN
series (except PTN 6900 series) and marine series NEs.
Context
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 In the Main Topology, right-click an NE and choose Collect NE Data from the shortcut menu.
The Datacollector window is displayed.
NOTE
In the Datacollector window, press F1 to display the Online Help topic relevant to data collection
operations and troubleshooting methods of common problems.
----End
Context
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series,
ATN series, Marine series, NE series, CX series and Access series NEs.
l The naming rule is a string that comprises a series of fields. The U2000 provides some
fields by default. The user can add new fields, modify or delete the existing fields and adjust
the field position according to the actual requirements, to customize the naming rule.
Procedure
Step 1 Choose Administration > Settings > Naming Define Rule (traditional style) from the main
menu or select System Management in Application Center and choose Settings > Naming
Define Rule (application style) from the main menu.
Step 2 Choose the fiber or trail which want to be named from the Function Tree of Function
Configuration. The naming rule is displayed on the right-hand pane.
Step 3 Optional: Click Refresh to obtain the latest naming rule customized by other users.
Step 4 Click Create Rule and enter the name of the newly created rule in the first row.
l Fixed Field: This type of field defines fixed strings contained in all names. Enter the
string in Fixed Field field.
l Connector Field: This type of field defines the connector used in the name. Select the
connector in the Connector Field field.
l Dynamic Field: In this type of field, you can select some attributes of the fiber or cable
and add the value to the name, for example, contain the name of Source NE in the
naming rule. Select the attributes in the Dynamic Field field.
l Digital Field: In this type of field, the numerals contained in the naming rule can be set
to change regularly so that the names of fibers or cables following the same rule is not
repeated. In the Digital Field field, set Current Value, Min. Value, Max. Value and
Step Length.
NOTE
It is recommended that there is only one Digital Field in the naming rule. If there are multiple digital
fields, it is recommended to set others to Fixed Field.
3. Define the field name in the Name list.
4. Define the field length in the Length list.
Step 6 Optional: Delete fields. Select the field to delete in the Field Descriptions list. Right-click it
and choose Delete Field from the shortcut menu.
Step 7 Optional: Set how the field is sequenced in the naming rule. Select the field and click
Step 8 Click Apply to set the current naming rule as the default rule on the client.
Step 9 In the Such As field, you can preview the current naming rule.
Step 10 Click Save to save the current naming rule and set it as the default rule.
Step 11 Click Apply to set whether to apply the current naming rule as the naming rule of the current
client.
----End
l The name of a multi-instance process contains numbers to distinguish from a process with
the same function. Table 1-15 shows a process with numbers omitted. For example,
ds_agent refers to the ds*_agent process, with the asterisk character (*) indicating a number.
l Every instance is responsible for some independent service data. Stopping an instance will
certainly affect related services.
Table 1-15 shows the description of U2000 services and processes. Required Process specifies
the processes that a specified process depends on during startup. The System Monitor displays
the direct and indirect dependencies.
%M
%
S_*.
*
serv
er/
var/
logs/
Dev
elop/
nbi/
Age
nt_C
ORB
A/
unbi
_cor
basy
s_%
y%
m%
d_%
H%
M%
S_*.
*
serv
er/
var/
logs/
Dev
elop/
nbi/
Age
nt_C
ORB
A/
unbi
_deb
ug_
%y
%m
%d_
%H
%M
%
S_*.
*
serv
er/
var/
logs/
Dev
elop/
nbi/
Age
nt_C
ORB
A/
unbi
_sys
_%y
%m
%d_
%H
%M
%
S_*.
*
og/
Bms
Acce
ss_*
_%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
Bms
Atur
_*_p
86_
%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
og/
iMA
PBas
e_p2
42_
%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
BmsP None BmsPonAlar mc,Li 130 TCP serv PON TL1 Alarm
onAla mTL1,/ cense 28 er/ Process. This
rmTL nemgr/ Servi var/ process provides
1 nemgr_access ce logs/ PON TL1 Alarm
/bin Dev NBI
elop/ Management
Bms service.
Pon
Alar
mTL
1
serv
er/
var/
logs/
mrbl
og/
iMA
PBas
e_p4
008_
%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
BmsP BmsPonEms BmsPonEms mc,Li 130 TCP serv Access PON TL1
onEm TL1 TL1,server/ cense 27 er/ Process. Provides
sTL1 nemgr/ Servi var/ service
nemgr_access ce logs/ provisioning and
/bin Dev fault diagnosis
elop/ for PON TL1
Bms services.
Pon
Ems
TL1
serv
er/
var/
logs/
mrbl
og/
iMA
PBas
e_p4
007_
%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
var/
logs/
mrbl
og/
iMA
PBas
e_p3
8_%
y%
m%
d_%
H%
M%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
og/
iMA
PBas
e_p8
1_%
y%
m%
d_%
H%
M%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
DCSe DCServer DCServer,ser None 22, TCP, serv DC. This process
rver ver/common/ 69, UDP, er/ provides the
dc/bin var/ function of NE
23, TCP, logs/ software
140 TCP Dev management and
0 elop/ disaster recovery
DCS management.
erver The detailed
/ functions are NE
DCS software
erver upgrade, patch
*.log installation, data
serv backup and
er/ recovery for
var/ disaster recovery,
logs/ and plug-andplay
Dev automatic
elop/ upgrade of case-
DCS shaped
erver equipment.
/
Boot
Log
*.log
serv
er/
var/
logs/
Dev
elop/
DCS
erver
/
Bms
_ne*
_%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
Dev
elop/
DCS
erver
/
Dms
_ne*
_%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
Dev
elop/
DCS
erver
/
tkdll
_log/
serv
er/
var/
logs/
Dev
elop/
DCS
erver
/
back
up*/
_sys
moni
tor_
p66_
%y
%m
%d_
%H
%M
%
S.log
og/
iMA
PBas
e_p2
37_
%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
nem
gr_b
its_
%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
Dev
elop/
nem
gr_b
its/
Boot
Log
_%y
%m
%d_
%H
%M
%
S.*
Nms
logzi
pDm
_unn
orma
l.log
serv
er/
var/
logs/
Dev
elop/
Nms
logzi
pDm
_1/
Nms
logzi
pDm
_%y
%m
%d_
%H
%M
%
S.*lo
g
StdClt StdCltsiDm StdCltsiDm,s Bms 900 TCP, serv Access 112 Test .
siDm erver/ Test 2, TCP er/ This process
common/ 900 var/ provides the 112
access_comm 3 logs/ test.
on/std112/bin Dev
elop/
StdC
ltsiD
m/
StdC
ltsiD
m_
%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
Dev
elop/
StdC
ltsiD
m/
Boot
Log
_%y
%m
%d_
%H
%M
%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PBas
e_p8
8_%
y%
m%
d_%
H%
M%
S.*
Dev
elop/
nbi/
texta
gent/
dom
ain_
debu
g_te
xt-%
y.%
m.%
d-%
H.%
M.%
S.*
serv
er/
var/
logs/
Dev
elop/
nbi/
texta
gent/
uflig
ht_te
xt-%
y.%
m.%
d-%
H.%
M.%
S.*
og/
iMA
PBas
e_p4
7_%
y%
m%
d_%
H%
M%
S.*
serv
er/
var/
logs/
mrbl
og/
iMA
PMr
b_p2
_%y
%m
%d_
%H
%M
%
S.*
l Languages used in nine countries, namely, China, America, Italy, Spain, France, UAE,
Germany, Russia, and Portugal.
l Input of various types of characters.
NOTE
l The name of a rule, trail, fiber, subnet, or customer can contain "+" and ":",
l The name of an NE or a subnet can contain "+".
l The Tab key input cannot be contained in the above names or the values of overheads J0, J1, and J2.
l These rules are made in order to avoid database operation errors or errors occurred when an HTML
report is generated. The Tab key input cannot be contained in command lines.
NOTICE
When you enter characters in Microsoft Pinyin IME and keep pressing a key, too many characters
will be typed in. This leads to the exit of the U2000 client.
Directory
l When files are transferred between different OSs, both Chinese and English directories are
supported.
l When performance data is dumped at the server end, both Chinese and English directories
are supported. In other cases, only English directories are supported.
File Name
The general rule is file name + extension name. The extension name consists of letters, numerals
or underscores, and should not exceed three characters.
The naming rule is that a file name consists of letters, numerals or underscores. It cannot exceed
eight characters. A file name cannot contain spaces or any of the following characters: \ " . * ;
> [ ] ( ) ! $ { } < >. If you need to separate two characters, you may use "_".
Nine languages are supported, with each language corresponding to a naming rule.
zh_CN China
en_US America
it_IT Italy
es_ES Spain
fr_FR France
de_DE Germany
ru_RU Russia
pt_PT Portugal
IP Address
The IP address is decimal, for example, 129.9.0.254:9801 (9801 is the port ID, and can be
omitted).
MAC Address
The MAC address is hexadecimal, for example, 00-06-5B-84-50-84.
Types of Numerals
Integer type: In this mode, only integral numbers can be typed in.
Decimal fraction type: In this mode, besides numerals, characters f and e, as well as the decimal
point are allowed.
Password
Each time you enter a character in the password text box, a dot is displayed instead. The password
cannot be copied.
To navigate to the window for customizing the type of the date and time, choose File >
Preferences > Region Settings from the main menu and click the Time or Date tab.
Table
The parameters on the GUI are presented in tables to display parameter values of different
objects.
l If -- or - is displayed in the table cell of a selected record, it indicated that the parameter is
not supported. This type of table cell in not editable.
l If / or Unknown is displayed in the table cell of a selected record, the parameter is supported
but the parameter value is unavailable for a certain reason at the moment.
Figure 1-35 Mutual exclusion list for multiclient operations on ASON SDH trails
Figure 1-36 Mutual exclusion list for multiclient operations on ASON WDM trails
Example
The "script import" and "upload" operations are mutually exclusive. If "script import" is being
performed on one client, "upload" cannot be performed on another client.
This topic describes the process of managing network equipment on the U2000.
Configure and manage the MSTP network by referring to the processes as shown in Figure
2-1.
NOTE
The landscape orientation of the configuration flow chart shows the main phases of managing the MSTP network
by using the U2000. The phases include network deployment, service configuration, network maintenance, and
SDH ASON feature management. In the case of the service configuration, the end-to-end service configuration
mode requires a license that supports the end-to-end SDH management, and the SDH ASON feature management
requires a license that supports the SDH ASON feature.
The portrait orientation of the flow chart shows the relationships between operation tasks in each phase.
Configuring
Configuring DDN Deploying Report
Configuring IGMP Snooping
Services PWE3 Services Management
Protection
Deploying E- Configuring
Configuring SAN Configuring
Configuring AGGR Services LAG/DLAG
Services OAM
Board
Parameters Deploying
Configuring Composite Configuring
Broadcast Data Services BPS/RPS Configuring
Port Services Data Test
Customer Frame
Configuring F1 Management Configuring
Data Port SNCTP
Configuring
Services
BPS/RPS/PR
Configuring Built- Configuring BS
in WDM Transmux
Adjusting
Configuring Configuring Networks
MPLS Tunnel TCM
Configuring Routine
CES/ATM Configuring Maintenance
Services AU3 for an ASON
Configuring Network
Ethernet
Services Configuring
IPA Handling ASON
Configuring Network
MSTP Failures
Configuring
Configuring PW SDH ASON
APS/MS-PW Networks
Configure and manage the Metro WDM&LH WDM network by referring to the processes as
shown in Figure 2-2.
NOTE
The landscape orientation of the configuration flow chart shows the main phases of managing the WDM network
by using the U2000. The phases include network deployment, service configuration, WDM feature
configuration, network maintenance, and WDM ASON feature management. In the case of the service
configuration, the end-to-end service configuration mode requires a license that supports the end-to-end WDM
management, and the WDM ASON feature management requires a license that supports the WDM ASON
feature. The WDM ASON feature is unique to the NG WDM. An NG WDM NE can use the WDM ASON
feature management function only after the WDM ASON feature is enabled.
The portrait orientation of the flow chart shows the relationships between operation tasks in each phase.
Configuring
Configuring Broadcast Data Configuring Fiber Report
Board Port Services Link Check Management
Parameters
Configuring F1 Data
Configuring
Port Services
Protection
For the detailed process for managing the OptiX OSN 6800, refer to Figure 2-3.
NOTE
The procedure for managing the OptiX OSN 3800 is similar to the procedure for managing the OptiX OSN
6800.
For the detailed process for managing the OptiX OSN 6800A, refer to Figure 2-3.
NOTE
The procedure for managing the OptiX OSN 3800A is similar to the procedure for managing the OptiX
OSN 6800A.
Configuring Configuring
Creating a Services on a Per- End-to-End Configuring Managing the
Network NE Basis Services ROADM Optical Power
Configuring
Configuring Optical Cross- Customer Alarm
Management Configuring IPA Management
DCN Connections
Handling ASON
Network Failures
Configuring Configuring
Creating a Services on a Per- End-to-End Configuring Managing the
Network NE Basis Services ROADM Optical Power
Configuring
Configuring Optical Cross- Customer Alarm
Management Configuring IPA Management
DCN Connections
Report
Configuring
Management
Protection
For the detailed process of managing the OptiX OSN 8800 series equipment, see Figure 2-4.
NOTE
The OptiX OSN 8800 T32 V100R001 does not support orderwire and Ethernet service configuration.
The OptiX OSN 8800 T32 V100R002 or a later version supports the SDH-related functions, including
configuring SDH protection, SDH features, and SDH-ASON feature management.
Routine
Maintenance for an
Configuring Configuring ASON Network
WDM Protection SDH Protection
Handling ASON
Network Failures
For the detailed process for managing the OptiX OSN 1800, refer to Figure 2-5.
For the detailed process for managing the OptiX OSN 1800(NA), refer to Figure 2-5.
Deploying a Maintaining a
Configuring Services
Network Network
Configuring Configuring
Creating a Services on a Per- End-to-End Managing the
Network NE Basis Services Optical Power
Manage WDM
Configuring the Configuring Performance
Protection
NE Time Overhead Management
Subnet
Configuration
Configuring Manage WDM Data
Clocks Trail Management
Configuring Software
Board Management
Parameters
Configuring Report
Protection Management
Configure and manage the RTN network by referring to the processes as shown in Figure 2-6.
NOTE
The landscape orientation of the configuration flow chart shows the main phases of managing the RTN network
by using the U2000. The phases include network deployment, service configuration, and network maintenance.
In the case of the service configuration, the end-to-end service configuration mode requires a license that supports
the end-to-end RTN and SDH management.
The portrait orientation of the flow chart shows the relationships between operation tasks in each phase.
Configuring Maintaining a
Deploying a Configuring Services Feature Network
Network
Performance
DCN Configuring Deploying a Configuring
Management
Management Radio Links Tunnel ATPC
Configuration
Configuring the Deploying Configuring Data
Configuring SDH
NE Time VPLS Services XPIC Management
Services
Configuring
LAG Diagnosis &
Configuring
Maintenance
PWE3 Services
(CES/ATM/ETH)
Configure and manage the PTN network by referring to the processes as shown in Figure 2-7.
NOTE
The landscape orientation of the configuration flow chart shows the main phases of managing the PTN network
by using the U2000. The phases include network deployment, service configuration, configuring feature and
network maintenance.
The portrait orientation of the flow chart shows the relationships between operation tasks in each phase.
Configuring Configuring
Creating Services on a Configuring
End-to-End Configuring
Network Per-NE Basis Network Level
Services the MSTP
Protection
Configuring Configuring Configuring
Configuring the OAM
Communicatio Tunnel the BFD
Control Plane Management
ns
Configuring Configuring Configuring
Configuring Configuring
MPLS /IP/GRE PWE3 the LPT
Inband DCN Tunnel Orderwire
Service
Configuring
Configuring Configuring the the IGMP
Configuring Port Mirror
the NE Time QoS Policy Snooping
VPLS Service
Hop
Management
IP Network Deployment
Import the
Method 1: Deploy the network Deploy tunnels.
BoQ
Scenario using the NE Explorer.
stage
Generate the port Method 2: Deploy the network Deploy VPN
information table using the plug-and-play services.
management.
Generate the NE Deploy service
information table guarantee.
Tool and
UniStar U2000
module
Network planning
Role Software commissioning engineers
engineers
NOTE
After network planning engineers obtain the LLD document (including the port information table and NE
configuration table) based on the Bill of Quantity (BoQ) list, software commissioning engineers can use the
U2000 to complete IP network deployment. This topic does not contain network planning information. For
details about network planning, see the network planning guide associated with the solution used by the site.
Netw Deploy Deployment scenario: Use the Configuration > Router and
ork basic U2000 Plug-and-Play Router/Switch/ Switch
deplo configur Management to deploy Security Network
ymen ations, configurations. Configuration > Management >
t such as The U2000 Plug-and-Play Plug-and-Play Network
configur Management can be used to Management Deployment >
ations remotely launch multiple NEs Deploying a
for the and perform basic Network Using
manage configurations for multiple the Plug-and-
ment NEs; therefore, on-site software Play
channel, commissioning is not required Management
device and this greatly improves the
interfac deployment efficiency.
e, IGP
and
IP Network Maintenance
Perfor The U2000 supports real-time network Router and Switch Network
mance quality monitoring. The monitoring Management > Network Monitoring
monito results can be used for trend analysis and and Maintenance > Performance
ring identifying areas and nodes where Monitoring
network quality deteriorates, helping
monitoring engineers proactively respond
to network faults.
Alarm The U2000 supports alarm monitoring for Router and Switch Network
monito immediate identification of network Management > Network Monitoring
ring faults and rapid response to the faults. and Maintenance > Monitoring
Network Status
Report The U2000 allows you to analyze and l Router and Switch Network
statisti collect statistics about network running Management > Network
cs status in different ways. Monitoring and Maintenance >
collecti NE Routine Maintenance >
on Collecting Network Resource
Statistics > Using the U2000
Report System to Collect
Network Resource Statistics
l Router and Switch Network
Management > Network
Monitoring and Maintenance >
NE Routine Maintenance >
Collecting Performance
Monitoring Results
Locate If the The U2000 receives alarms Fault > Browse Fault Diagnosis
faults U2000 from IP NEs. Current Alarm > Locating
based receive Faults Based on
on s an Alarm
alarm alarm Information >
inform from an Common Alarm
ation. IP NE, Locating
rectify
the Performance alarms or TCAs Fault > Browse Fault Diagnosis
fault are generated on the U2000. Current Alarm > Locating
accordi NOTE Faults Based on
ng to The names of these alarms Alarm
the contain Performance or Information >
threshold, for example, Port Locating
alarm Performance Minor Alarm or
inform Performance
The number of BRAS accesses
ation. exceeds the threshold.
Faults
NOTE
The horizontal direction of the flowchart shows the primary stages of managing an access network with the
U2000, which include:
l Network deployment
l Feature configuration
l Network maintenance
l Bulk network configuration
The vertical direction of the flowchart shows the relationships between the operation tasks of these stages.
EPON
management
xDSL management
Multicast
management
TDM management
VoIP management
PWE3
management
ACL management
BFD management
QoS management
DHCP Relay
management
MSTP
management
It is recommended that you configure and manage a core network in accordance with the
flowchart shown in Figure 2-12.
NOTE
The horizontal direction of the flowchart shows the primary stages of managing a core network with the U2000,
which include:
l Network deployment
l Feature configuration
l Network maintenance
l Bulk network configuration
The vertical direction of the flowchart shows the relationships between the operation tasks of these stages.
Performance
Network health check
management
NE information Software
collection management
Device panel
It is recommended that you configure and manage a security NE network in accordance with
the flowchart shown in Figure 2-13.
NOTE
The horizontal direction of the flowchart shows the primary stages of managing a security NE network with the
U2000, which include:
l Network deployment
l Feature configuration
l Network maintenance
l Security service
l Network security management
The vertical direction of the flowchart shows the relationships between the operation tasks of these stages.
IPSec end-to-
Topology Device Alarm end service
management management management Security policy
management
Remote
Interface Inventory
management management access service Attack defense
management
Single-point SSL VPN
Performance
Web management service Port mapping
configuration management
NE software
management NAT
IPS
3 Security Management
The U2000 data is saved in the database. Therefore, ensure the database security with priority,
including protecting the security of the database password, backing up the database
periodically, viewing the database status, and dumping the database.
Security object U2000 objects on which only users that are authorized by
users from the SMManagers group can perform operations.
Security objects, such as devices, object sets, and subnets, are
managed by the U2000.
NOTE
Not all devices in the Main Topology are managed by the U2000. If
a user from the SMManagers group creates a common user and does
not assign any operation rights to the common user, the common user
can view some objects in the Main Topology after logging in to the
U2000. However, these objects are not security objects because they
are not managed by the U2000.
Concept Description
User A U2000 client user. The user name and password of a user
identify the user's U2000 operation and management rights.
After being added to a user group, a user inherits the operation
rights of the user group. A user can be added to multiple user
groups. The operation rights of a user comprise those of the
user and user groups to which the user belongs.
The U2000 provides the default user admin as the system
administrator. The admin user belongs to the
Administrators and SMManagers groups by default and has
more rights than the SMManagers group. You cannot change
the admin user's rights or add this user to other user groups.
NOTE
The admin user's initial password is Changeme_123. (The initial
password is Admin_123 for a preinstalled U2000.) You must change
the password upon the first login as the admin user to ensure system
security. Keep the password secure and change it regularly.
User Group A collection of U2000 users that have the same operation
rights. Adding users to user groups on the U2000 enables the
management of user rights in batches and reduces
management costs.
A user group has the following attributes: details (group name,
description, group type, and maximum number of sessions),
members, domain, operation rights, and current session.
The U2000 provides the following default user groups:
Administrators, SMManagers, Maintenance Group,
Guests, Operator Group, and NBI User Group.
User Group Administrat Only the Administrators group belongs to this type of group.
Type or Group This administrator group has a domain that contains all
network objects and has all operation rights except security
management rights. The domain and operation rights cannot
be changed, and this type of user group cannot be created.
Concept Description
Concept Description
Default User The U2000 provides three default user groups: Operator
Group Group, Guests, and Maintenance Group. The domain of a
default user group is All Objects. The operation rights for the
default user groups are described as follows:
l Users from the Guests group have the rights for default
monitor operation sets. They can perform query
operations, such as querying statistics, but cannot create
or configure objects.
l Users from the Operator Group group have the rights for
default operator operation sets. In addition to the rights of
the Guests group, users from the Operator Group group
have the rights to create, modify, and delete (rights to
perform potentially service-affecting operations are not
involved). For example, they can create NEs, change
alarm severities, and configure SDH trails.
l Users from the Maintenance Group group have the rights
for default maintenance operation sets. In addition to the
rights of the Guests and Operator Group groups, users
from the Maintenance Group group have the rights to
perform configurations that affect the running of the
U2000 and NEs. For example, they can search for SDH
protection subnets and trails, delete composite services,
and reset boards.
The default user groups are listed in descending order of rights
as follows: Maintenance Group, Operator Group, and
Guests. Operation sets of a default user group that has high-
level rights include the operations in operation sets of a user
group that has low-level rights. For example, maintenance
operation sets contain all operations in operator operation
sets.
NBI User The OSS interconnects with the U2000 through NBIs. The
Group NBI user group is created on the U2000 to manage access of
the OSS.
NOTE
NBI User Group is available only when the NBI instance is
deployed.
You can use the following methods to assign rights to a user or a user group:
l Add a user to a default user group so that the user has all the rights of this group. This
method applies to O&M scenarios in which users require only the basic rights of a
U2000 default user group.
l Create a user group and add a user to this user group. This method applies to scenarios in
which default user groups do not meet O&M requirements. For example, if a default user
group has excessive or insufficient rights, you can create a user group that has appropriate
rights and add a user to this user group.
NOTE
It is recommended that you authorize a user by adding the user to a user group that has appropriate rights.
Authorizing a user directly or by adjusting the rights of the default user groups is not recommended.
Account Policy Specifies the minimum length of a user name, login policy,
and unlocking policy. You can set the account policy to ensure
account security.
Remote Maintenance User The U2000 supports remote maintenance. It allows a remote
Management maintenance terminal to log in to the U2000 server to perform
operations on NEs that the U2000 manages. Remote
maintenance is commonly used for remote NE fault locating
and periodical checks.
The remote maintenance user is a U2000 user that logs in to
the U2000 server from the remote maintenance terminal. By
default, the remote maintenance user is disabled. Before
starting remote maintenance, enable the remote maintenance
user and set parameters for the user as required.
Concept Description
SSL Protocol The Secure Sockets Layer (SSL) protocol ensures data
security and integrity for network communication. The SSL
protocol configured for the server that communicates with
clients can efficiently protect customers' network information.
Single-User Mode The admin user uses the single-user mode to perform special
operations such as rights assignment. In single-user mode,
only one user is allowed to log in to the U2000 as the
admin user, which prevents other users' interference during
operations. When the login mode is switched to the single-
user mode, all the users except the admin user are forcibly
logged out and cannot log in again.
Client Lockout To ensure network security, the U2000 locks out a U2000
client if a user does not perform any operations on the client
for a specified period. Client lockout does not affect the
running of the U2000.
ACL
Access control lists (ACLs) are a secure access control mechanism. It restricts users to log in to
the U2000 server only from clients that have specified IP addresses.
To improve the security of the U2000, ACLs restrict what client IP addresses users can use to
log in to the U2000. If user accounts and passwords are stolen, unauthorized users cannot log
in to the U2000. The U2000 provides two types of ACLs:
l System ACL
ACL for the U2000. All the users can log in to the U2000 only from the IP addresses or
network segments specified in the system ACL.
l User ACL
ACL for a user. The current user can log in to the U2000 only from the IP addresses or
network segments specified in the ACL for the user.
NOTE
The IP addresses or network segments in a user ACL must be within the range of the IP addresses
or network segments in the system ACL.
User Monitoring
The U2000 monitors user access to resources. User monitoring comprises session monitoring
and operation monitoring. For session monitoring, the U2000 monitors users' online status. For
operation monitoring, the U2000 monitors operation objects, time, and specific operation items.
If a user performs unauthorized operations or operations that potentially affect the system, a
security administrator of the U2000 can forcibly log out the user.
the U2000. The password used to log in to the MSuite must be changed regularly to ensure
U2000 security.
Operable objects mainly involve the U2000 and NEs, which are managed as devices.
NMS users can perform operations on the U2000 or NEs only when they are authorized to access
and operate the U2000 or NEs.
Figure 3-2 shows the operations that can be performed on the U2000 and NEs.
Access
rights
U2000 application
operations
Operation
U2000
rights
Network device
operations
Access Logging in to To log in to the U2000, a user must have a valid account and
rights the U2000 password.
Authorization Methods
Security administrators can authorize users using the following methods:
l Authorize users by setting domains and operation rights for users.
l Bind users to a user group. That is, authorize a user group, which includes setting domains
and operation rights of the user group, and add users to the user group so that the users
inherit the user group's rights.
Security administrators are advised to authorize users by binding users to user groups. This
method enables the security administrators to simultaneously authorize all the users who hold
the same post. When users' posts change, the security administrators can authorize new users by
removing original users from and adding the new users to the user groups.
Table 3-1 describes operation right configuration modes. The subnet device set mode and user-
defined object set mode are commonly used.
All The default The three The All Objects This mode is This
Objects object set All modes are mode co-works rarely used mode
Objects object set with the default because few appli
provided by modes. In operation set All users except in es to
the U2000 is these modes, Object Administrators the
assigned as a security Operations or SMManagers scena
managed administrators provided by the group need to rio
object to users must assign U2000 to assign all manage all wher
or user groups. operation operation rights for devices. e
rights by all devices to users. users
binding must
operation sets mana
to object sets. ge all
If a user group devic
wants to have es.
operation
rights for an
object, the
following
conditions
must be met:
l The user
group's
object set
contains
the object.
l The
operation
set bound
to the
object set
contains
the
operations
correspond
ing to the
operation
rights.
device set is
apt to lack
objects on
which
operations
contained in
the operation
set are
performed.
Users
By default, U2000 provides the user account admin that can be used to manage all devices and
has all operation rights. By default, the admin user belongs to the Administrators and
SMManagers user groups and has the most operation rights on the U2000.
User Groups
A user group is a collection of user accounts. After a user account is added to a user group, the
user has domains and operation rights of the user group. A user account can belong to multiple
user groups.
Managing users' operation rights based on user groups makes right management convenient and
clear.
The U2000 provides six default user groups. For details, see Table 3-2.
None of the default user groups can be deleted. By default, operation rights of the
Administrators and SMManagers user groups are provided by the U2000 and cannot be
changed. Default operation rights of the Maintenance Group, Operator Group, Guests, and
NBI User Group user groups can be changed as required by operation and maintenance
personnel.
The U2000 supports user-defined user groups created based on application requirements.
NOTICE
Users in the Administrators or SMManagers user group must perform operations as required.
Any operations that may cause damages or pose risks to the U2000 are forbidden.
Administrators This user group has all operation rights except those of the
SMManagers user group. Users in the Administrators user group
can perform operations such as maintaining U2000 servers and setting
global parameters.
Users in the Administrators and SMManagers user groups can
manage all objects. Other users can manage only authorized objects.
SMManagers This user group has operation rights only for Security
Management, which include permissions to configure a security
policy, query security logs, manage users/user groups/object sets/
operation sets/use permissions/security log templates, monitor user
dialogues/operations, force users to exit, unlock users, and re-set user
passwords. The users added to the user group can manage all the users
on the U2000, except for the admin and other security administrators.
Users in the SMManagers user group are U2000 security
administrators.
Maintenance Group By default, this user group has operation rights for default maintenance
operation sets. In addition to the rights of the Guests and Operator
Group groups, users in this group have the rights to perform
configurations that affect the running of the U2000 and NEs. For
example, they can search for SDH protection subnets and trails, delete
composite services, and reset boards.
Operator Group By default, this user group has operation rights for default operator
operation sets. In addition to the rights of the Guests group, users in
this group have the rights to create, modify, and delete (rights to
perform potentially service-affecting operations are not involved). For
example, they can create NEs, change alarm severities, and configure
SDH trails.
Guests By default, this user group has operation rights for default monitor
operation sets. They can perform query operations, such as querying
statistics, but cannot create or configure objects.
NBI User Group By default, this user group has operation rights related to northbound
Service.
Objects
Objects are classified into security and non-security objects. This section focuses on security
objects.
On the U2000, a security object is an entity on which only users authorized by security
administrators can perform operations. For example, devices, subnets, and object sets are
security objects.
On the U2000, a non-security object is an entity on which users can perform operations without
the authorization by security administrators. In the Main Topology, not all devices are managed
by the U2000. If the security administrator creates a common user but does not grant any rights
to the user, the user still can view some objects in the Main Topology after logging in to the
U2000. However, these objects are not security objects because they are not managed by the
U2000.
Object Sets
An object set is a collection of objects. The U2000 provides the default object set All Objects
that includes all objects managed by the U2000. The objects in the All Objects set cannot be
modified or deleted.
A maximum number of 99 object sets is recommended in addition to the default object set. The
maximum limit helps prevent performance problems.
Item Description
Subnet Object set that the U2000 creates for a subnet in the physical topology view
device set and that shares the same name as the subnet.
A subnet device set provides the following features:
l A subnet device set contains a subnet in the physical topology view and all
objects on the subnet.
l If a subnet contains a lower-layer subnet in the physical topology view, the
corresponding subnet device set contains the lower-layer subnet and
objects on the lower-layer subnet.
l If objects on a subnet in the physical topology view are adjusted, the
adjustments are synchronized to the corresponding subnet device set in the
security management module. The U2000 does not allow security
administrators to directly adjust objects in a subnet device set in the security
management module.
l A subnet device set cannot be added to a user-defined object set.
l All subnet device sets are displayed only in the window in which security
administrators set domains. They are not displayed under the Object Set
node in the navigation tree in the Security Management window.
All objects The U2000 provides one object set by default, that is, the All Objects set. The
default object set contains all NEs managed by the U2000 and cannot be
modified or deleted.
Operation Types
On the U2000, users can perform operations on both the U2000 and NEs. Therefore, operations
are classified into two types: NMS application operations and network device operations.
The object of NMS application operations is the U2000. For example, those operations involving
topology objects constitute the Topo Management rights and those alarm-related operations
constitute the Fault Management rights. The following Figure 3-4 shows the Select Operation
Rights window. The NMS application operations are classified into more than 20 types and listed
under the Operation node in the Operation area.
The objects of network device operations are NEs. All operations for an NE on the U2000
constitute the rights for the NE. A Router NE (CX600-144) is used as an example. All rights for
it are listed under the Operation node in the Operation area as shown in the following figure.
Operation sets that contain operation subsets cannot be added to another operation set because an operation
set cannot contain two levels of operation sets.
The U2000 provides more than 20 types of default NMS application rights (corresponding to
more than 60 types of operation sets) and more than 70 types of network device rights in all
domains (corresponding to more than 200 operation sets). If the default operation sets do not
meet requirements, create operation sets manually.
NOTE
It is not recommended to assign the All Application Operations and All Object Operations operation
sets to common users. All Application Operations contains operations for all U2000 applications except
security applications. All Object Operations contains operations for all NEs managed by the U2000. A
user who is assigned both of the two operation sets has all operation rights for the U2000 and NEs.
l A default operation set of the U2000 contains all operations in the operation sets at lower levels.
l The U2000 may define the high and low levels of operation sets differently from O&M engineers'
expectations. In this situation, O&M engineers can create operation sets based on the actual O&M
scenarios.
Specifically, administrators can assign rights for topology management to a user on the New
User Group > Operation Rights > Select > Select Operation Rights GUI in the following
ways:
l Assign default operation sets to a user. The following operation sets can be assigned: Topo
Monitor Operation Set, Topo Maintainer Operation Set, and Topo Monitor Operation
Set. To view which operations are included in an operation set, right-click it and choose
View Operation Set Member from the shortcut menu. This method is used when the
default operation sets meet the requirement for rights assignment.
l Create operation sets, add desired operations in Topo Management to them, and assign
them to users. This method is used when the default operation sets cannot meet the
requirement for rights assignment.
l Assign operation rights in Topo Management to users directly. This method is
inconvenient for management and maintenance. Therefore, it is not recommended.
Transferring
Operation Sets
Start
Plan domains.
End
Table 3-4 describes the content and rules for each procedure in the process.
Table 3-4 Content and rules for each procedure in the process
Planning Classify personnel into groups based l Place personnel who have the
user on their responsibilities. same responsibilities in a user
groups group.
l Place a person whose
responsibilities are partially
different from others' in a separate
user group.
Planning Plan modes for adding managed Plan domains together for personnel
domains objects to domains to improve who have the same management
authorization and maintenance scopes. Plan domains separately for
efficiency. personnel whose management scopes
are partially different from others'.
The subnet device set mode is
preferred for planning domains.
Devices that are not included in a
subnet device set are added to a user-
defined object set to avoid repeated
authorization for individual devices.
To facilitate future adjustment, it is
recommended that a user-defined
object set not include subobject sets.
Planning Analyze operation rights required for l If user groups support the same
operation personnel to fulfill their network management application
sets responsibilities and classify the operations, plan the same network
operation rights into operation sets. management application
Plan network device operation sets operation set for the user groups.
and network management Otherwise, separately plan
application operation sets. network management application
operation sets for the user groups.
NOTE
If the device modes are used in a domain l If user groups support the same
management plan, you do not need to plan network device operations, plan
operation sets. the same network device operation
set for the user groups. Otherwise,
separately plan network device
operation sets for the user groups.
Sorting Sort data and create a user group l The domain column must specify
data and attribute table for reference during the subnet device set, user-defined
creating a authorization and right management. object set, or device mode in
user group The user group attribute table must which managed objects are added
attribute include the user group member, to a domain.
table domain, and operation right columns. l If the subnet device set mode and
user-defined object set mode are
used, the operation right column
must specify an operation set that
includes all required operations.
The following uses the organization and networking structures for region A as an example to
help you better understand original right management data.
Devices numbered from 01 to 11 of different types are located in region A. Devices numbered
from 01 to 04 are located on Subnet01, devices numbered from 07 to 10 are located on Subnet02,
and Device05, Device06, and Device11 are not located on any subnets. See Figure 3-8.
Eight persons are assigned to manage the devices in region A. Figure 3-9 shows device
management division. Table 3-5 describes the division, providing the original right management
data generated based on the organization and networking structures for region A.
Subnet01 Subnet02
Device05 Device06
Device11
A B C D E F G H
Network Data System maintenance System maintenance
configuration engineer and part- Network Data
monitoring configuration engineer and part-
engieer engineer and time data monitoring
part-time system engineer and time data
configuration engineer configuration
maintenance engineer part-time system
maintenance engineer
engineer
engineer
To help the authorization planning later, sort out the following items based on the original right
management data:
l Personnel who manage the same devices, that is, personnel who have the same domain
l Personnel who have the same responsibilities, that is, personnel who can perform the same
operations on the same devices
Sort the data in Table 3-5 based on these two items to generate Table 3-6 and Table 3-7.
Personn Responsibilities
el
C and D Work full time or part time to configure data and perform routine maintenance
for Subnet01 (Device01, Device02, Device03, and Device04), Device05,
Device06, and Device11.
l Full-time data configuration engineer C and part-time data configuration
engineer D configure data for the same managed devices.
l Part-time system maintenance engineer C and full-time system maintenance
engineer D perform routine maintenance for the same managed devices.
G and H Work full time or part time to configure data and perform routine maintenance
for Subnet02 (Device07, Device08, Device09, and Device10), Device06, and
Device11.
l Full-time data configuration engineer G and part-time data configuration
engineer H configure data for the same managed devices.
l Part-time system maintenance engineer G and full-time system maintenance
engineer H perform routine maintenance for the same managed devices.
Data configuration C and D Configure data and perform routine maintenance for
and system Subnet01 (Device01, Device02, Device03, and
maintenance Device04), Device05, Device06, and Device11.
engineer group 1
Data configuration G and H Configure data and perform routine maintenance for
and system Subnet02 (Device07, Device08, Device09, and
maintenance Device10), Device06, and Device11.
engineer group 2
Planning Domains
Domain planning aims to specify modes for adding managed objects to domains to improve
authorization and maintenance efficiency.
Plan domains together for personnel who have the same management scopes. Plan domains
separately for personnel whose management scopes are partially different from others'. Use the
management personnel in region A as an example. A, B, C, and D have the same management
scope, E, F, G, and H have the same management scope (see Table 3-6), and there is no person
whose management scope is partially different from others'. In this example, only two domains
are required: one for A, B, C, and D, and the other for E, F, G, and H.
Comply with the following rules when planning domains: Use the subnet device set mode as
the first choice. Devices that cannot be included in a subnet device set are included in a user-
defined object set, avoiding authorization for a device. It is recommended that a user-defined
object set not include subobject sets to specify a clear object set structure and facilitate
maintenance.
Table 3-9 describes domains for region A based on the rules. Figure 3-10 shows management
division based on managed objects in each domain.
Objectset01
Device05 Device06
Device03 Device04
Device09 Device10
Device11
A B C D E F G H
Network Data System maintenance Data System maintenance
monitoring configuration engineer and part- Network configuration engineer and part-
engineer engineer and time data monitoring engineer and time data
part-time system configuration engineer part-time system configuration
maintenance engineer maintenance engineer
engineer engineer
plan for region A described in Table 3-8 as an example. Table 3-10 describes operation
rights required for the user groups in this region.
The user group attribute table must include the user group member, domain, and operation right
columns. The domain column must specify modes in which managed objects are added to
domains. The operation right column must specify modes in which rights are assigned to
personnel. Table 3-12 is the user group attribute table generated based on Table 3-8, Table
3-9, Table 3-10, and Table 3-11.
Figure 3-11 shows the authorization process. You can click a procedure in the flowchart to
access the section for more details. The procedures involved in the authorization process are
described based on the example provided in 3.2.3 Authorization Plan.
NOTE
If no user-defined object set or user-defined operation set is involved in the authorization plan, you do not
need to create user-defined object sets or user-defined operation sets. That is, you can skip the first two
procedures in the authorization process.
Start
Create user-defined
object sets.
Create user-defined
operation sets.
End
Prerequisites
l You have logged in as a user in SMManagers.
l You are familiar with user roles and have planned object sets. For details, see 3.2.3
Authorization Plan.
Context
l After creating object sets during the initial phase of site deployment, you can adjust them
or create object sets during site maintenance.
l If an object set is allocated to a user group, all members in the user group can view members
of the object set in the physical topology view.
l The following operation uses the examples in 3.2.3 Authorization Plan to describe how
to create an object set.
Procedure
Step 1 Determine the object set to be created and its members based on the authorization plan.
Object sets to be created and object set members are listed in Domain. For details, see Table
3-12 of 3.2.3 Authorization Plan. The following steps use Objectset01 as an example.
Step 2 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 3 In the NMS User Management navigation tree, right-click the Object Set node and choose
New Object Set.
Step 4 On the Details tab page in the New Object Set dialog box, select the Type as Network
Device, and set Name to Objectset01 and Description to Object set for region A.
NOTE
l Members of an object set can be other object sets that do not contain subsets. However, you are not
advised to select object sets as members to simplify operation right maintenance.
l To select objects in existing object sets as members, click Copy Members from Object Sets in the
New Object Set dialog box and select one or more object sets in the Copy Members from Object
Sets dialog box. The members of the selected object sets are copied to the Members tab for the current
object set.
NOTE
l You can click and choose Sort by topology position or Sort by device type to sort available or
selected devices and object sets.
l You can enter the desired information in the Find text box and click or to search for objects
and object sets in the up or down direction.
l You can click to specify whether to set the Match whole word only or Match case rules to
search for objects and object sets.
Step 6 In the New Object Set dialog box, click OK. The object set is created.
----End
Result
The created object set is displayed in the object set list. Double-click the object set. The objects
contained in the object set are listed on the Members tab.
Follow-up Procedure
You can click Select in the lower right corner of the Members tab to adjust the members of the
object set in the dialog box displayed.
Prerequisites
l You have logged in as a user in SMManagers.
l You are familiar with user roles and have planned operation sets. For details, see 3.2.3
Authorization Plan.
Context
l Operation sets can be allocated to users or user groups.
l If an operation set is allocated to a user group, all members of the user group have the
operation rights in the operation set.
l The U2000 provides default operation sets.
l The following steps use the examples in 3.2.3 Authorization Plan to describe how to create
an operation set.
Procedure
Step 1 Determine the operation set to be created and its type and members based on the authorization
planning.
Operation sets to be created, types of operation sets, and operation set members are listed in
Operation Rights. For details, see Table 9 of 3.2.3 Authorization Plan. The following steps
use Device Monitoring Operation Set 1 of the network device operation set type as an example
to describe how to create an operation set.
Step 2 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 3 In the NMS User Management navigation tree, right-click the Operation Set node and choose
New Operation Set.
Step 4 On the Details tab in the New Operation Set dialog box, set Type to Network Device,
Name to Device Monitoring Operation Set 1, and Description to Operation of monitoring
devices in domain A.
NOTE
l Members of an operation set can be other operation sets that do not contain subsets. However, it
is recommended that you not select operation sets as members to simplify operation right
maintenance.
l To select operations in existing operation sets as members, click Copy Members from
Operation Sets in the New Operation Set dialog box and select one or more operation sets in
the Copy Members from Operation Sets dialog box. The members of the selected operation
sets are copied to the Members tab for the current operation set.
NOTE
l You can enter the desired information in the Find text box and click or to search for operations
and operation sets in the up or down direction.
l You can click to specify whether to set the Match whole word only or Match case rules to
search for operations and operation sets.
Step 6 In the New Operation Set dialog box, click OK. The operation set is created.
----End
Result
The created operation set is displayed in the operation set list. Double-click the operation set.
The operations contained in the operation set are listed on the Members tab.
Follow-up Procedure
You can click Select in the lower right corner of the Members tab to adjust the members of the
operation set in the dialog box displayed.
Prerequisites
l You have logged in as a user in SMManagers.
l You have planned user groups. For details, see 3.2.3 Authorization Plan.
l You are familiar with the responsibilities of users and the operation rights of the U2000
default user groups.
Procedure
Step 1 Determine the user group to be created based on the authorization planning.
Collect information about the user group to be created, the corresponding domain, and operation
set. For details, see Table 9 of 3.2.3 Authorization Plan. The following steps use Network
monitoring engineer group 1 as an example.
Step 2 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 3 In the NMS User Management navigation tree, right-click the User Group node and choose
New User Group.
Step 4 In the New User Group dialog box, set the properties of the user group.
1. On the Details tab, set the user group name, description, type, and maximum number of
sessions.
NOTE
If the operation rights of the created user group are the same with those of an existing user group,
you can copy operation rights from the existing user group. Click Copy Rights from User
Groups. In the Copy Rights from User Groups dialog box, select one or multiple user groups and
click OK. After the copy is complete, the selected domain rights and operation rights are displayed
on the Domain and Operation Rights tabs. Security administrator can adjust the rights as required.
2. Optional: Select members.
Click Add. In the Add User dialog box, select the desired user and click OK.
NOTE
You can add users to a user group using any of the following methods:
l When creating a user group, select users as its members.
l When creating a user, you can add the user to a user group.
l After a user or user group is created, you can add the user to a user group by setting User
Groups for the user or add users by setting Member for the user group.
3. Click Next.
Step 5 Set the domain for the user group to specify the object scope that the user group manages.
1. On the Domain tab page, click Select.
2. In the Select Domain dialog box, set domain parameters and click OK.
l In the Authorization Mode area, select Object Set. In the Available Objects area,
select Objectset01 and click . The selected object is added to the Selected
Objects area.
NOTE
Only user-defined object sets created by security administrators are displayed under the Object
Set node. If no user-defined object set has been created, no object set is displayed under the
Object Set node.
l In the Authorization Mode area, select Subnet Device Set. In the Available
Objects area, select Subnet01 and click . The selected object is added to
the Selected Objects area.
NOTE
You can select the other authorization modes in the Authorization Mode area as required.
You can click More/Hide to expand or hide the authorization mode.
NOTE
l In the Available Objects area, you can click to view selected object set and subnet device
set members.
l You can enter the desired information in the Find text box. Click to search for objects in the
up direction, click to search for objects in the down direction, and click to specify
whether to set the Match whole word only or Match case rules.
l After clicking and select the Device authorization mode, you can click and choose
Sort by topology position or Sort by device type to sort available or selected objects.
3. Click Next.
Step 6 Set operation rights for the user group to assign U2000 application rights and object operation
rights to users.
1. On the Operation Rights tab page, click Select.
2. In the Select Operation Rights dialog box, set parameters and click OK.
NOTE
After an authorized object is selected, operations that can be bound to the authorized object are
displayed in the Operations area. For details about the binding relationship between authorized
objects and operations, see Operation Rights.
NOTE
l In the Authorization Objects and Operations area, you can click to view the selected object
set, subnet device set, and operation set members.
l After binding operations to a selected device, you can click and choose Sort by topology
position or Sort by device type to sort rights for the device.
3. Click Finish.
----End
Result
The created user group is displayed in the user group list. Double-click the user group. The
objects managed by the user group are listed on the Domain tab, and the operations that users
in the user group can perform on the objects are listed on the Operation Rights tab.
Follow-up Procedure
You can click Select in the lower right corner of the Domain and Operation Rights tabs
respectively to adjust the managed objects and operations for the user group in the dialog box
displayed.
Prerequisites
l You have logged in as a user in SMManagers.
l You are familiar with the planning of user accounts and password policy. For details, see
Account Policy and Password Policy.
Context
l When you create an U2000 user, attributes of the user must comply with the account policy
and the password policy. For details about how to set an account policy and a password
policy, see 3.3.1.4 Setting Account Policies and 3.3.1.5 Setting Password Policies.
l After the NMS user is created, add it to the corresponding user group so that the operation
rights of the user group are granted to the user. Do not set domains or operation rights for
the user individually.
l You must manually set the user name and password. For the other attributes, you can use
default values or set them after you create the user account successfully.
l The following steps use the examples in 3.2.3 Authorization Plan to describe how to create
a user account and add it to a user group.
Procedure
Step 1 Determine the user account to be created based on the authorization planning.
Collect information about the user account to be created and the corresponding user group. For
details, see Table 3-12 of 3.2.3 Authorization Plan. The following steps use User A as an
example. Because the user name is too short to comply with the U2000 security policy, the user
name is changed to Network monitoring engineer A.
Step 2 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 3 In the NMS User Management navigation tree, right-click the User node and choose New
User.
Step 4 In the New User dialog box, set general attributes of the user account and add it to a user
group. For details, see New User Account.
1. Set general attributes such as the user name, password, and confirm password.
Set User name to Network monitoring engineer A, Full Name to Network monitoring
engineer Tom, and Description to Network monitoring engineer.
NOTE
l Before setting the password, click Password Policy to view the preset password policy.
l On the Password Policy tab, you can also click Advanced to optimize the user policy.
2. Click Add. In the Add User Group dialog box, select the desired user group and click
OK.
In the Add User Group dialog box, select Network monitoring engineer group 1.
Step 5 In the New User dialog box, click OK. The user account is created.
----End
Result
The created user account is displayed in the user list. Double-click the user account. The user
groups to which the user has been added are listed on the User Groups tab.
Follow-up Procedure
To add the user to another user group, click Add in the lower right corner of the User Groups
tab. To delete the user from a user group, select the user group on the User Groups tab and click
Delete in the lower right corner of the tab.
to an authorization plan, security administrators can use the operation set import and export
functions provided by the U2000 to transfer operation sets from one U2000 to other U2000, or
add or modify operation sets on one U2000 in batches.
Prerequisites
You have logged in as user admin.
Context
l For a newly installed U2000, export operation set files about the network management
application and network devices, add new operation sets to the files, and import the changed
files to the U2000 using the Import Operation Sets function. In this way, you can create
operation sets in batches at one time.
l For a U2000 that has being running for a period of time, you can export operation set files
to the local computer. This helps you restore operation sets using the Import Operation
Sets function after upgrading and bulk deleting old operation sets.
l The default U2000 operation sets Security Monitor Operation Set, All Object
Operations and All Application Operations are excluded from exported operation sets.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 On the top of the NMS User Management navigation tree, click , and then select Export
Operation Sets.
Step 3 In the Save dialog box, rename the exported file and save the file to a specified location, then
click Save.
----End
Result
l The Network Management Application and Network Device operation sets are saved in
separate files.
NOTE
All operation information is listed from columns A to E in the exported operation set files. The
information listed after column E is information about operation sets that exist on the U2000.
Members in the existing operation sets are indicated by the letter Y in the operation list.
l The formats of default file names are
Operation_Sets_YYYY_MM_DD_HH_MM_SS_Network_Device.csv and
Operation_Sets_YYYY_MM_DD_HH_MM_SS_Network_Management_Application.
csv.
NOTE
Prerequisites
l You have logged in as user admin.
l The file containing the exported operation set information should be edited by user
admin based on the right-related policy and operation set planning.
l The information about all the operation sets in the U2000 is exported and saved in a file.
For details, see 3.2.5.1 Exporting Operation Sets.
l You are familiar with the planning of system operations or operation sets. For details, see
3.2.3 Authorization Plan.
Context
l This operation does not apply to the change of operation set names.
l The information in columns from A to E in the operation set file cannot be modified. If it
is modified, importing the file will fail. If the information is modified, export operation set
file again.
l In the operation set file, the table cells in line 10 and columns except columns from A to E
contain only operation set names.
l If the operation set name in the file exists in the current U2000, the operation set fails to
import.
l The naming convention of a new operation set is the same as that of an operation set created
in the U2000.
Procedure
Step 1 Open and edit the .csv file containing the exported operation set information.
1. In the .csv file, add a column next to column E, and enter the name of the new operation
set in the first cell of the new column, such as Figure 3-12. Assume that the U2000
has Operation Set A and Operation Set B, you can add New Operation Set C next
to Operation Set B.
2. Adding members for the new operation set. You can enter Y in the line where an
operation to be performed. See Figure 3-12. The blue area stand for that Create
Subnet and Modify NE are performed for New Operation Set C.
NOTE
Only letter Y is valid.
l Modifying the operations of an operation set. Assume Operation Set A already exists in
the U2000. You can modify the operation set members as follows:
1. Enter Y in the associated table cell of operation set. If you need to delete Query
System Logs of Operation Set A, delete Y of Operation Set A. If you need to add
Create Subnet, type Y in the associated table cell of Operation Set A.
2. To prevent a file import failure due to inconsistency between operation set information
in the file and that on the U2000 client, delete the operation set modified in the previous
step from the client. In this example, delete Operation Set A.
Step 2 Save the file, and import the file by following the procedure provided in 3.2.5.3 Importing Files
Containing Operation Set Information for the file to take effect.
----End
Result
After the file is imported successfully, you can view the change of the rights in an operation set.
Prerequisites
l You have logged in as user admin.
l The information about all the operation sets in the U2000 is exported and saved in a file.
For details, see 3.2.5.1 Exporting Operation Sets.
l You are familiar with user roles and have planned operation sets. For details, see 3.2.3
Authorization Plan.
Context
l The operation set files to be imported must be exported using the Export Operation
Sets function.
l If the operation set name in the file exists in the current U2000, the operation set fails to
import.
Procedure
Step 1 Optional: In the exported operation set files, add operation sets or modify members in the
operation sets in batches.
NOTICE
l This operation does not apply to the change of operation set names.
l The information in columns from A to E in the operation set file cannot be modified. If it is
modified, importing the file will fail. If the information is modified, export operation set file
again.
l In the operation set file, the table cells in line 10 and columns except columns from A to E
contain only operation set names.
1. Open and edit the .csv file containing the exported operation set information.
Add an operation set 1. In the .csv file, add a column next to column E, and enter the
name of the new operation set in the first cell of the new
column, such as Figure 3-13. Assume that the U2000 has
Operation Set A and Operation Set B, you can add New
Operation Set C next to Operation Set B.
NOTE
The operation set name contains a maximum of 100 characters.
2. Adding members for the new operation set. You can enter
Y in the line where an operation to be performed. See Figure
3-13. The blue area stand for that Create Subnet and Modify
NE are performed for New Operation Set C.
NOTICE
Only letter Y is valid.
Modify the Assume Operation Set A already exists in the U2000. You can
operation set modify the operation set members as follows:
members 1. Enter Y in the associated table cell of operation set. If you
need to delete Query System Logs of Operation Set A,
delete Y of Operation Set A. If you need to add Create
Subnet, type Y in the associated table cell of Operation Set
A.
2. To prevent a file import failure due to inconsistency between
operation set information in the file and that on the U2000
client, delete the operation set modified in the previous step
from the client. In this example, delete Operation Set A.
Step 2 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style).
Step 3 On the top of the NMS User Management navigation tree, click and select Import
Operation Sets.
Step 4 In the Open dialog box, select the .csv file to be imported and click Open.
----End
Result
Operation sets contained in the imported file are listed under the Operation Set node in the
navigation tree on the left. After you choose an operation set, members of the operation set are
displayed in the right pane, which are the same as those specified in the imported file.
Prerequisites
l You have logged in as a user in SMManagers.
l A user group has been planned to manage the new NE.
Context
If initial authorization has met the following conditions, users in the user group automatically
have the operation rights for the new NE, and no adjustment is required.
The subnet device set to which the new NE belongs has been added to the user group's domain.
The operation set bound to the subnet device set contains all required operations on the new NE.
Figure 3-14 shows the process of adjusting operation rights after an NE is added.
Start
No
No
End
Procedure
Step 1 Viewing the Domain of a User or User Group and Viewing Operation Rights of a User or
User Group. Determine whether the user group automatically has the operation rights for the
new NE based on the context information mentioned above.
Step 2 Add the operation rights for the new NE to the user group's operation set.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the Operation Set node and select
the user group's operation set.
3. On the Members tab page in the right pane, click Select.
4. In the Available rights area of the Select Operation Set Member dialog box, select
operation rights for the type of the new NE.
The operation rights for the new NE are assigned to the user group.
l If the user group is authorized using a user-defined object set, perform the following steps:
1. Choose OSS Security > OSS User Management (application style) or
Administration > NMS Security > NMS User Management (traditional style) from
the main menu.
2. In the NMS User Management navigation tree, expand the Object Set node and select
the user group's object set.
3. On the Members tab page in the right pane, click Select.
4. In the Available Devices and Object Sets area of the Select Object Set Member dialog
box, expand all nodes and select the new NE.
5. Click to move the new NE to the Selected Devices and Object Sets area.
6. Click OK.
l If the user group is authorized using the device mode, perform the following steps:
1. Choose OSS Security > OSS User Management (application style) or
Administration > NMS Security > NMS User Management (traditional style) from
the main menu.
2. In the NMS User Management navigation tree, expand the User Group node and
choose the user group that manages the new NE.
3. On the Domain tab page in the right pane, click Select.
4. In the Select Domain dialog box, click More in the Authorization Mode area and
select Device.
5. In the Available Objects area, select the new NE.
Step 4 Verify that the user group's operation rights include the operation rights for the new NE.
l If the user group is authorized using a user-defined object set, perform the following steps:
1. In the NMS User Management navigation tree, expand the Operation Set node and
select the operation set corresponding to the user-defined object set.
2. On the Members tab page in the right pane, check whether the user group's operation
set contains the operation rights for the new NE.
– If yes, the procedure ends.
1. On the Operation Rights tab page in the right pane, click Select.
2. In the Authorization Objects navigation tree of the Select Operation Rights dialog
box, expand the Device node and select the new NE.
3. In the Operation navigation tree, select required operation rights and add them to
Selected Rights in the right pane.
4. Click OK.
The operation rights for the new NE are assigned to the user group.
----End
Prerequisites
l You have logged in as a user in SMManagers.
l You have obtained information about user groups that manage the new subnet, types of all
devices on the subnet, and operation rights required for the user groups to manage the
devices.
Context
l Based on the original authorization mode, assign operation rights for the new subnet as
follows:
– If the original authorization mode is the device mode, assign operation rights based on
subnet device sets.
– If the original authorization mode is the subnet device set mode or user-defined object
set mode, assign operation rights based on subnet device sets.
l If the new subnet is managed by multiple user groups, adjust each user group's operation
rights in a similar way. This section describes the process of adjusting a user group's
operation rights.
Figure 3-15 shows the process of adjusting operation rights after a subnet is added.
Start
Add the subnet device set corresponding to Add the subnet device set corresponding to
the new subnet to the user groups' domains. the new subnet to the user groups' domains.
End
Procedure
Step 1 Add the subnet device set corresponding to the new subnet to the user group's domain.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the User Group node and choose
the user group that manages the new subnet.
3. On the Domain tab page on the right, click Select.
4. In the Authorization Mode area of the Select Domain dialog box, select Subnet Device
Set.
5. In the Available Objects area, select the subnet device set that corresponds to the new
subnet and has the same name as the new subnet, and click to add the subnet
device set to the user group's domain.
6. Click OK to close the Select Domain dialog box.
Step 2 Query the user group's authorization mode. For details, see 3.2.8.2 Viewing Operation Rights
of a User or User Group.
l If the user group is authorized in device mode, create an operation set for the new subnet.
For details, see 3.2.4.3 Creating User-defined Operation Sets. After an operation set is
created, perform Step 5.
l If the user group is authorized in subnet device set mode or user-defined object set mode,
perform Step 3.
Step 3 Check whether the network device operation set contains all operation rights for various types
of devices on the new subnet. For details, see 3.2.8.5 Viewing Operations Contained in an
Operation Set.
l If the network device operation set does not contain all required operation rights, perform
Step 4.
l If the network device operation set contains all required operation rights, perform Step 5.
Step 4 Modify the network device operation set so that it contains all operation rights for various types
of devices on the new subnet.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the Operation Set node and
choose the network device operation set corresponding to the user group.
3. On the Members tab page in the right pane, click Select.
4. In the Available Rights area of the Select Operation Set Member dialog box, select
operation rights for various types of devices on the new subnet.
Step 5 Bind the network device operation set that contains all required operation rights for the new
subnet to the subnet device set.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the User Group node and choose
the user group that manages the new subnet.
3. On the Operation Rights tab page in the right pane, click Select.
4. In the Authorization Objects area of the Select Operation Rights dialog box, expand the
Subnet Device Set node in the navigation tree and choose the subnet device set
corresponding to the new subnet.
5. In the Operation area, select the network device operation set that contains all required
operation rights for the new subnet. Click to add the network device
operation set to the Selected Rights area.
6. Click OK to close the Select Operation Rights dialog box.
The operation rights for the new subnet are assigned to the user group.
----End
Procedure
l During NE transfer (for example, when an NE is transferred from one subnet to another),
a security administrator adjusts user groups' operation rights by deleting the NE from the
transferor user group's domain and adding the NE to the transferee user group's domain.
For details, see 3.2.6.1 Adjusting Operation Rights After an NE Is Added.
– If the NEs are assigned to the transferor user group in subnet device set mode, the
security administrator does not need to adjust the transferor user group's operation rights
after NE transfer.
– If the NEs are assigned to the transferor user group in object set mode or device mode,
delete the NEs from the user group's domain. For details, see NE Scope Change.
l During global networking structure modification, a security administrator plans
authorization and authorizes users again. For details, see Performing the Initial
Authorization.
----End
3.2.7.1 Adjusting Operation Rights After the Scope of Managed Objects Is Changed
When the topology of managed objects remains unchanged and the management rights are
transferred from a user group to another one, security administrators must adjust the user group
rights.
Prerequisites
You have logged in as a user in SMManagers.
NE Scope Change
In subnet device set mode, user groups are assigned operation rights for devices based on subnets.
Therefore, security administrators do not need to adjust operation rights after the scope of
managed objects is changed if user groups are authorized in subnet device set mode.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand User Group and select the user
group that no longer manages NEs.
3. On the Domain tab page in the right pane, delete NEs based on authorization modes.
Assign an NE to a user 1. Expand the Device node, choose the NE, and click
group in device mode. Delete in the lower right corner.
2. In the Confirm dialog box, click OK.
Step 2 Adjust the operation rights for the NEs for the transferee user group. For details about how to
adjust operation rights, see 3.2.6.1 Adjusting Operation Rights After an NE Is Added.
----End
3. On the Domain tab page right to the navigation tree, select the subnet device set and click
Delete.
4. In the Confirm dialog box, click OK.
5. For a user group that is going to manage subnet rights, assigning subnet rights to it means
adding a new subnet. For details about how to adjust operation rights, see 3.2.6.2 Adjusting
Operation Rights After a Subnet Is Added.
3.2.7.2 Adjusting Operation Rights After the Scope of Operation Rights Is Changed
If a user group's operation rights for a managed object must be added or deleted due to changes
to personnel's responsibilities, security administrators must adjust operation rights as required.
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 View the operation rights of a desired user group.
Task Operations
Adding an operation l For assigning operation rights for a single device or a device
right for a managed type:
object 1. On the Operation Rights tab page, click Select.
2. In the Select Operation Rights dialog box, expand
Device or Device Type in the Authorization Objects
navigation tree and select a device or a device type. In the
Operation navigation tree, select the desired operations
and add them to Selected rights in the right pane.
3. Click OK.
l For details about how to assign operation rights for subnet
device sets and user-defined object sets on the basis of existing
operation sets, see step 4 in 3.2.8.5 Viewing Operations
Contained in an Operation Set.
Task Operations
Deleting an operation l For assigning operation rights for a single device or a device
right for a managed type: On the Operation Rights tab page, expand Device or
object Device Type, select the desired operations, and click Delete.
l For assigning operation rights for subnet device sets and user-
defined object sets: Select the bound operation sets, right-
click, and choose View Members from the shortcut menu.
Check whether the operation sets contain operation rights that
need to be deleted. If the operation sets contain operation
rights that need to be deleted, see step 4 in 3.2.8.5 Viewing
Operations Contained in an Operation Set to delete the
operation rights.
NOTE
An operation may exist in multiple operation sets. The operation right
is deleted from a user group only when all operation sets bound to the
user group do not contain the operation.
----End
Prerequisites
You have logged in as a user in SMManagers.
Role Change
After management personnel's roles change, security administrators must perform the following
steps to adjust user groups to which the personnel belong:
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand User and select a user whose user
group is to be adjusted.
3. On the User Groups tab page in the right pane, select the user group to which the user
belongs and click Delete. In the Confirm dialog box that is displayed, click Yes.
4. On the User Groups tab page in the right pane, click Add. In the Add User Group dialog
box, select a user group to which the user is to be added and click OK.
Recruitment
If new employees are recruited, security administrators must create user accounts and assign the
user accounts to the new employees. For details about how to create user accounts and assign
operation rights to user accounts, see 3.2.4.5 Creating Users and Adding the Users to User
Groups.
Resignation
After an employee resigns, the employee's user account is no longer used or is retained.
l To delete the user account, security administrators perform the following steps:
1. Choose OSS Security > OSS User Management (application style) or
Administration > NMS Security > NMS User Management (traditional style) from
the main menu.
2. In the NMS User Management navigation tree, expand User. Right-click the user to
be deleted and choose Delete from the shortcut menu. In the Confirm dialog box that
is displayed, click Yes.
l To retain the user account for future use, security administrators perform the following
steps:
1. Choose OSS Security > OSS User Management (application style) or
Administration > NMS Security > NMS User Management (traditional style) from
the main menu.
2. In the NMS User Management navigation tree, expand User and choose a user.
3. On the Details tab page, set Disable user account to Yes.
NOTICE
l If the policy for deleting a user account when the user account is not used to log
in for a specified period has been set in Setting the Account Policy, the user
account is deleted when it has not been used to log in for the specified period.
l After an employee resigns or a user account is re-enabled, the corresponding user
password must be changed to improve account security.
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 In the NMS User Management navigation tree, expand User or User Group and select a user
or a user group.
Step 3 On the Domain tab page, view managed objects in the user domain.
The following table lists different methods for viewing domains based on the authorization
mode.
Authorization Method
Mode
Subnet device set Expand Subnet Device Set. Right-click a desired subnet device set and
choose View Member from the shortcut menu.
User-defined Expand Object Set. Right-click a desired user-defined object set and
object set choose View Member from the shortcut menu.
To change objects in object sets, see step 4 in 3.2.8.6 Viewing Objects
Contained in an Object Set.
NOTE
l If you select Show the domain of the owner user group when viewing a user's domain, managed
objects displayed include managed objects that the user inherits from user groups. Perform the
following operations to view the inherited managed objects:
1. Switch to the User Groups tab page. View the user groups to which the user belongs.
2. View the managed objects contained in each user group.
l If you select Sort by device type, objects under the Device node on the Domain tab are grouped by
type.
l By default, Show the domain of the owner user group is selected and Sort by device type is
deselected.
----End
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 In the NMS User Management navigation tree, expand User or User Group and select a user
or a user group.
Step 3 On the Operation Rights tab page, expand the object node and view the operation rights of the
user or user group on each object.
The following table lists different methods for viewing operation rights based on the
authorization mode.
Authorization Method
Mode
Subnet device set Expand Subnet Device Set. Right-click the corresponding operation set
and choose View Member from the shortcut menu.
To change operations in the operation set, see step 4 in 3.2.8.5 Viewing
Operations Contained in an Operation Set.
User-defined Expand Object Set. Right-click the corresponding operation set and
object set choose View Member from the shortcut menu.
To change operations in the operation set, see step 4 in 3.2.8.5 Viewing
Operations Contained in an Operation Set.
Device Expand Device and view operation rights of the user on different devices.
NOTE
When you view user operation rights, the displayed user operation rights contain the operation rights
inherited from the user groups if Show the operation rights of the owner user group is selected. Perform
the following operations to view the inherited operation rights:
1. View the user groups to which the user belongs.
2. View the operation rights contained in each user group.
By default, Show the domain of the owner user group is selected.
----End
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 In the NMS User Management navigation tree, expand User and select a user.
Step 3 On the User Groups tab page, view user groups to which the user belongs.
----End
Prerequisites
You have logged in as a user in SMManagers.
Context
The Administrators group contains all operation rights on the U2000 except Security
Management rights. Therefore, in the Authorization Details dialog box, the
Administrators is always displayed in the Authorized User/User Group area when any
operation or operation set is selected.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 On the top of the NMS User Management navigation tree, click .
NOTE
You can enter the desired information in the Find text box. Click to search for devices or object sets
in the up direction, click to search for devices or object sets in the down direction, and click to
specify whether to set the Match whole word only or Match case rules.
Step 3 In the Authorization Details dialog box, expand the root node or parent node and select a child
node in the navigation tree.
After a node is selected, the corresponding operation or operation set is displayed in the
Operation area.
Step 4 In the Operation area, expand the root node or parent node and select an operation or operation
set.
In the Authorized User/User Group area, you can view the user or user group to which
operation rights are assigned.
----End
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 In the NMS User Management navigation tree, expand Operation Set and select the desired
operation set.
Step 3 On the Members tab page, view operations contained in the operation set.
NOTE
l On the Details tab page, you can view the operation set type (U2000 application operation set or
network device operation set).
l On the Applicable for tab page, you can view the users and user groups to which the operation set is
assigned.
Step 4 Optional: Add an operation to or delete an operation from the operation set.
l Adding an operation: On the Members tab page, click Select. In the Select Operation Set
Member dialog box, select the desired operation set member and click OK.
l Deleting an operation: On the Members tab page, select one or multiple operation set
members and click Delete, then click Yes in the displayed Confirm dialog box.
----End
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 In the NMS User Management navigation tree, expand Object Set and select the desired object
set.
Step 3 On the Members tab page, view objects contained in the object set.
NOTE
l On the Details tab page, you can view the details of the object set.
l On the Applicable for tab page, you can view the users and user groups to which the object set is
assigned.
l After Sort by device type is selected, the members of the object set are sorted by device type. If the
object set contains no device, Sort by device type is dimmed.
Step 4 Optional: Add members to or delete members from the object set.
l For adding members: On the Members tab page, click Select. In the Select Object Set
Member dialog box, select the desired object set members and click OK.
l For deleting members: On the Members tab page, select and right-click one or multiple
object set members and choose Delete from the shortcut menu, then click Yes in the displayed
Confirm dialog box.
----End
Prerequisites
You have logged in as a user in SMManagers.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 On the top of the NMS User Management navigation tree, click .
Step 3 In the Compare Users dialog box, select a user from the Primary User and Secondary User
list boxes, click Compare.
NOTE
l During the comparison of rights between user A and user B, if user A has an operation right but user
B does not have this right, this right node of user B is displayed as a blank node.
l On the U2000, you cannot compare rights of the same user. If you select the same user in the left and
right columns, the Compare button is unavailable.
l In the Compare User Rights dialog box, the U2000 can display user rights in either of the following
modes:
l Display all rights: All user rights are displayed in the group box.
l Display only differences: Only the differences between user rights are displayed in the group box.
----End
Symptom
Users may have difficulty determining the types of operation sets when users want to create an
operation set for storing dedicated operation permission, because they are not sure whether the
operation permission belongs to the Network Management Application or Network Device
type.
Possible Causes
l Users cannot determine the type of an operation right.
l Names of some device operation rights are similar to those of some network management
application operation rights.
Procedure
Step 1 Export operation sets to your local PC by referring to Exporting the Files Containing
Operation Set Information.
NOTE
Step 2 Search for the operation right name in the following two files.
l If the operation right name is displayed in the *_Network_Device.csv file, the right is of the
Network Device type.
l If the operation right name is displayed in the *_Network_Management_Application.csv
file, the right is of the Network Management Application type.
l If the right name cannot be found in the two files, check the entered name of the operation
right.
NOTE
----End
Question
How do I adjust operation rights after an NE is added?
Answer
If a plan for authorizing users by binding users to user groups is made during initial authorization,
adjust operation rights by following the procedure provided in 3.2.6.1 Adjusting Operation
Rights After an NE Is Added. Otherwise, adjust operation rights based on site requirements
by following the procedure shown in Figure 3-16.
Start
Yes
End
Yes
No
End
Step 1 Determine users who manage the new NE, and check whether the users exist.
l If new users are required to manage the new NE, plan user authorization and authorize users
by following the procedure provided in Performing the Initial Authorization.
l If users who manage the new NE exist, perform Step 2.
Step 2 Check whether the users belong to the same user group. If the users who manage the new NE
belong to the same user group and the user group contains only the users, operations described
below are performed on the user group. Otherwise, operations described below are performed
on each user who manages the new NE.
Step 3 Query a user or user group's authorization mode by following the procedure provided in 3.2.8.2
Viewing Operation Rights of a User or User Group.
If the new NE is on a subnet and the user or user group's domain includes the subnet device set
corresponding to the subnet, perform Step 4. Otherwise, perform Step 6.
Step 4 Check whether the network device operation set corresponding to the subnet device set
(described in Step 3) to which the new NE belongs contains operation rights for the new NE.
For details, see 3.2.8.5 Viewing Operations Contained in an Operation Set.
If the operation rights for the new NE exist in the network device operation set, the user or user
group automatically has the operation rights for the new NE. The procedure is complete.
Otherwise, perform Step 5.
Step 5 Add the operation rights for the new NE to the network device operation set corresponding to
the user or user group's subnet device set.
1. In the NMS User Management navigation tree, expand the Operation Set node and
choose the network device operation set corresponding to the subnet device set.
2. On the Members tab page in the right pane, click Select.
3. In the Available Rights area of the Select Operation Set Member dialog box, select
operation rights for the type of the new NE.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand User or User Group and select a
user or the user group that manages the new NE.
3. On the Domain tab page in the right pane, click Select.
4. In the Authorization Mode area of the Select Domain dialog box, click More to display
all modes, and select Device.
5. Select the new NE in the Available Objects area.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand User or User Group and select a
user or the user group that manages the new NE.
3. On the Operation Rights tab page in the right pane, click Select.
4. In the Authorization Objects area of the Select Operation Rights dialog box, expand the
Device node and select the device corresponding to the new NE.
5. In the Operation area, select the operations for the new NE.
----End
Question
How do I adjust operation rights after a subnet is added?
Answer
If a plan for authorizing users by binding users to user groups is made during initial authorization,
adjust operation rights by following the procedure provided in 3.2.6.2 Adjusting Operation
Rights After a Subnet Is Added. Otherwise, adjust operation rights based on site requirements
by following the procedure shown in Figure 3-17.
Figure 3-17 Procedure for adjusting operation rights after a subnet is added
Start
Yes
End
Step 1 Determine users who manage the new subnet, and check whether the users exist.
l If new users are required to manage the new subnet, plan user authorization and authorize
users by following the procedure provided in Performing the Initial Authorization.
l If users who manage the new subnet exist, perform Step 2.
Step 2 Check whether the users belong to the same user group.
If the users who manage the new subnet belong to the same user group and the user group contains
only the users, operations described below are performed on the user group. Otherwise,
operations described below are performed on each user who manages the new subnet.
Step 3 Add the subnet device set corresponding to the new subnet to a user or user group's domain.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand User or User Group and select a
user or the user group that manages the new subnet.
3. On the Domain tab page in the right pane, click Select.
6. Click to move the subnet device set to the Selected Objects area.
7. Click OK. The subnet device set is added to the user or user group's domain.
Step 4 Add an operation set for the subnet device set by following the procedure provided in 3.2.4.3
Creating User-defined Operation Sets.
Step 5 Add the operation rights for the new subnet to the user or user group's operation rights.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand User or User Group and select
the user or user group that manages the new subnet.
3. On the Operation Rights tab page in the right pane, click Select.
4. In the Authorization Objects area of the Select Operation Rights dialog box, expand the
Subnet Device Set node and select the subnet device set corresponding to the new subnet.
5. In the Operation area, select the operation set for the new subnet.
6. Click to move the subnet device set to the Selected rights area.
7. Click OK. The operation set for the new subnet is bound.
----End
3.2.9.4 How to Adjust Operation Rights After the Scope of Managed NEs Is
Changed?
If NE management responsibilities must be transferred from one user to another, security
administrators must adjust the users' operation rights. If the plan is not found or users are not
authorized by binding to user groups, adjust operation rights by referring to this FAQ.
Question
How to adjust operation rights after the scope of managed NEs is changed?
Answer
If a plan for authorizing users by binding users to user groups is made during initial authorization,
adjust operation rights by referring to 3.2.7 Operation Right Adjustment After Personnel's
Responsibilities Change. Otherwise, adjust operation rights based on site requirements by
following the procedure shown in Figure 3-18.
Yes
The NEs are added to the domain in The NEs are added to the domain in The NEs are added to the domain in
single-device mode. object set mode. subnet device set mode.
No No
Query the operation set bound to Query the operation set bound to
the object set to which the NEs the subnet device set to which the
belong. NEs belong.
End
Step 1 Identify the two parties involved in NE transfer. For example, the transferor (user A) transfers
NEs to the transferee (user B).
Step 2 Query the transferor's (user A's) domain and operation rights.
Query and record the transferor's (user A's) domain and operation rights (including rights
inherited from a user group to which the transferor (user A) belongs) by referring to 3.2.8.1
Viewing a User or User Group's Domain and 3.2.8.2 Viewing Operation Rights of a User
or User Group.
Step 3 Identify the domain where the transferred NEs are configured.
Query the user group to which the transferor (user A) belongs by referring to 3.2.8.1 Viewing
a User or User Group's Domain. Check whether the transferred NEs are configured in the
domain of the transferor (user A) or the user group to which the transferor (user A) belongs.
Assume that the transferor (user A) belongs to UserGroup1.
l If the transferred NEs are configured in the domain of UserGroup1, perform Step 4.
l If the transferred NEs are configured in the transferor's (user A's) domain, perform Step 9.
Step 4 Check whether UserGroup 1 must continue managing the transferred NEs.
Step 5 Perform Step 9 to Step 20 to delete the transferred NEs from the domain of UserGroup1.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the User node and choose the user
whose operation rights are to be adjusted.
3. Select UserGroup1 and click Delete. In the Confirm dialog box, click Yes.
The transferor (user A) is deleted from UserGroup1.
Step 7 Create a user group and delete the transferred NEs from the new user's domain.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, right-click the User Group node and
choose New User Group.
3. On the Details tab, set the user group name, description, type, and maximum number of
sessions. Assume that the new user group is named UserGroup2.
4. Click Copy Rights from User Groups. In the Copy Rights from User Groups dialog
box, select UserGroup1 and click OK.
Operation rights are copied from UserGroup.
5. On the Details tab, click Finish.
6. Perform Step 9 to Step 20 to delete the transferred NEs from the domain of UserGroup2.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the User node and choose the user
whose operation rights are to be adjusted.
3. On the User Groups tab in the right pane, click Add. In the Add User dialog box, select
UserGroup2 and click OK.
The transferor (user A) is then added to UserGroup2.
Step 9 Query the mode in which the transferred NEs are added to the transferor (user A) domain.
Query the mode in which the transferred NEs are added to the transferor (user A) domain by
referring to 3.2.8.1 Viewing a User or User Group's Domain.
l If the NEs are added to the domain in object set mode, for example, the NEs are contained
in ObjectSet1, perform Step 10.
l If the NEs are added to the domain in subnet device set mode, for example NEs are contained
in SubNetObjectSet1, perform Step 15.
l If the NEs are added to the domain in device mode, perform Step 21.
Step 10 Query users and user groups that manage the object set to which the transferred NEs belong.
For details, see 3.2.8.6 Viewing Objects Contained in an Object Set.
l If ObjectSet1 is used only by the transferor (user A), or it is shared by other users and user
groups that no longer manage the devices, the deletion of the NEs from the object set takes
no effect on the other users. Perform Step 11.
l If ObjectSet1 is shared by other users and user groups that still manage the devices, perform
Step 12.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the Object Set node and choose
ObjectSet1.
3. On the Members tab in the right pane, select the NEs and click Delete.
4. In the Confirm dialog box, click OK.
After the NEs are deleted from ObjectSet1, perform Step 22.
Step 12 Query the operation set bound to the object set to which the NEs belong.
Query the operation set bound to ObjectSet1 by referring to 3.2.8.2 Viewing Operation Rights
of a User or User Group. Assume that ObjectSet1 is bound to OperationSet1.
Step 13 Create an object set (ObjectSet2). ObjectSet2 contains all NEs in ObjectSet1 except the
transferred NEs.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, right-click the Object Set node and choose
New Object Set.
3. On the Details tab in the New Object Set dialog box, select Network Device for Type,
and set Name and Description to create an object set. Assume that ObjectSet2 is created.
Click Copy Members from Object Sets.
4. In the Copy Members from Object Sets dialog box, select ObjectSet1 and click OK to
add the members of ObjectSet1 to the Members tab as the members of ObjectSet2.
5. On the Members tab in the New Object Set dialog box, select the transferred NEs and
click Delete. Click OK.
ObjectSet2 is created.
Step 14 Replace ObjectSet1 with ObjectSet2, and then bind ObjectSet2 to the operation set.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the User node and choose the
transferor (user A).
3. On the Domain tab in the right pane, click Select.
4. Replace the object set with the new one.
In the Authorization Mode area of the Select Domain dialog box, and select Object
Set.
l In the Selected Objects area, select ObjectSet1 and click to move ObjectSet1
out of the domain.
5. On the Operation Rights tab in the right pane, click Select.
6. In the Authorization Objects area of the Select Operation Rights dialog box, expand the
Object Set node and choose Objectset2. In the Operation area, select OperationSet1 and
click .Then ObjectSet1 is added to the Selected Rights area. Click OK.
After replacing ObjectSet1 with ObjectSet2 and binding ObjectSet2 to the operation set, perform
Step 22.
Step 15 Check whether the transferor (user A) must manage the other devices in the subnet device set.
After deleting the subnet device set from the transferor's (user A's) domain, perform Step 22.
Step 17 Query the operation set bound to the subnet device set to which the transferred NEs belong.
Query the operation set bound to ObjectSet1 by referring to 3.2.8.2 Viewing Operation Rights
of a User or User Group. Assume that OperationSet2 is bound to SubNetObjectSet1.
Step 18 Create an object set (ObjectSet3). ObjectSet3 contains all NEs in SubNetObjectSet1 except the
transferred NEs.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, right-click the Object Set node and choose
New Object Set.
3. On the Details tab in the New Object Set dialog box, select Network Device for Type,
and set Name and Description to create an object set. Assume that ObjectSet3 is created.
4. Click the Members tab and then click Select.
5. In the Available devices and objects sets area of the Select Object Set Member dialog
box, select the devices in SubNetObjectSet1 managed by the transferor (user A). Click
to add the devices to the Selected devices and objects sets area, and click
OK. Close the Select Object Set Member dialog box.
6. In the New Object Set dialog box, click OK.
Step 19 Delete SubNetObjectSet1 from the transferor's (user A's) domain by referring to Step 16.
Step 20 Add ObjectSet3 to the transferor's (user A's) domain and bind ObjectSet3 to OperationSet2.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the User node and choose the
transferor (user A).
3. On the Domain tab in the right pane, click Select.
4. In the Authorization Mode area of the Select Domain dialog box, and select Object
Set. In the Available Objects area, select ObjectSet3 and click .
Then ObjectSet3 is added to the Selected Objects area.
5. On the Operation Rights tab in the right pane, click Select.
6. In the Authorization Objects area of the Select Operation Rights dialog box, expand the
Object Set node and choose ObjectSet3. In the Operation area, select OperationSet2 and
click .OperationSet2 is added to the Selected Rights area. Click OK.
After the NEs are deleted from user A's domain, perform Step 22.
Step 21 Delete the transferred NEs from the transferor's (user A's) domain.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the User node and choose user A.
3. On the Domain tab in the right pane, click Select.
4. In the Authorization Mode area of the Select Domain dialog box, click More to display
all modes, and select Device.
5. In the Selected Objects area, select the NEs to be moved out. Click to move
the NEs to the Available Objects area.
6. Click OK.
After the NEs are deleted from user A's domain, perform Step 22.
Step 22 Configure the transferee's (user B's) domain and operation rights.
1. Choose OSS Security > OSS User Management (application style) or Administration
> NMS Security > NMS User Management (traditional style) from the main menu.
2. In the NMS User Management navigation tree, expand the User node and choose the
transferee (user B).
3. On the Domain tab in the right pane, click Select.
4. In the Authorization Mode area of the Select Domain dialog box, and select Device. In
the Available Objects area, select NEs to be transferred and then click .
The NEs are added to the Selected Objects area.
5. On the Operation Rights tab in the right pane, click Select.
6. In the Authorization Objects area of the Select Operation Rights dialog box, expand the
Device node and choose the transferred NEs. In the Operation area, select operations
performed on the NEs by referring to Step 2. Click to add the operations to
the Selected Rights area. Click OK.
----End
3.2.9.5 How Do I Assign User Operation Rights That Do Not Belong to the User's
User Group?
Question
How do I assign extra operation rights to a user after the user is added to a user group?
Answer
Step 1 Check whether there is a user group that has only the extra operation rights required by the user.
l If yes, add the user to the user group by referring to 3.2.4.5 Creating Users and Adding the
Users to User Groups.
l If no, perform Step 2.
Step 2 Follow steps described in 3.2.4 Assigning Rights to Users to create a user group, assign the
operation rights to the user group, and add the user to the user group.
----End
Prerequisites
You have logged in as a user in SMManagers.
Context
If the topology view is locked, Modify Object Position is unavailable even if the user has this
operation right. Only a user with the Lock/Unlock View operation right can unlock the topology
view and make Modify Object Position available. To unlock the topology view, choose
View > Lock from the main menu.
Scenario
Security administrator A needs to create a topology maintenance engineer (Topo_mtB) to
manage topological objects and ensure that the assigned rights do not contain the Modify Object
Position right.
Roadmap
Step Roadmap
Step Roadmap
Procedure
Step 1 Choose Administration > NMS Security > NMS User Management (traditional style) from
the main menu or select Security Management in Application Center and choose OSS
Security > OSS User Management (application style) from the main menu.
3. On the Members tab, configure members for the new object set. These members are the
objects managed by Topo_mtB.
3. On the Members tab, configure members for the new operation set. Select the topological
management rights other than Modify Object Position in the Topo Management node.
4. Click OK.
Step 4 Create topology maintenance user group Topo_mtgroup and set its management domain and
operation rights.
1. In the NMS User Management navigation tree, right-click User Group and choose New
User Group from the shortcut menu. Alternatively, click above the navigation tree
and choose New User Group.
2. In the New User Group dialog box, click the Details tab and set common attributes such
as User name and Description, and then click Next.
3. Click Select. In the Select Domain dialog box, select Object Set of Topo_mtGroup, click
OK, and then click Next.
4. Click Select. In the Select Operation Rights dialog box, select Operation Set of
Topo_mtB, click OK, and then click Next.
5. Click OK.
Step 5 Create topology maintenance user Topo_mtB and add it to group Topo_mtgroup.
1. In the NMS User Management navigation tree, right-click User and choose New User
from the shortcut menu. Alternatively, click above the navigation tree and choose
New User.
2. Set common attributes for the user, such as user name and password.
3. Click Add, choose Topo_mtgroup from the Add New Group dialog box, and click OK.
4. Click OK.
----End
Result
Once you have created user Topo_mtB following the preceding procedure, log in to the
U2000 as user Topo_mtB to manage the topology.
Prerequisites
l You have logged in as a user in SMManagers.
l A clear plan is required before adjusting rights for a user. Before the plan is made, the user's
role must be clear.
Scenario
Security administrator A finds out that a monitoring engineer Monitor_B has the Modify Object
Position rights. However, a monitoring engineer should not have the rights according to the plan
made before the adjustment. Therefore, the rights are to be deleted.
Configuration Roadmap
Scenario Configuration Roadmap Description
1. Monitor_B is a member of the Modify the rights of the default Guests has all
default user group Guests. operation sets in Guests. the rights of
NOTE Monitor
If other members in the Guests require Operation Set
the Modify Object Position right, you of Region XX.
must remove Monitor_B from Checking the
Guests and then grant rights to
Network
Monitor_B separately.
Management
Application
operation sets
exported from
the NMS, Topo
Monitor
Operation Set
contains
Modify Object
Position.
Therefore,
remove Modify
Object
Position from
Topo Monitor
Operation Set.
2. Monitor_B is 2.1 Topo Modify the rights of the Topo Topo Guests of
a member of the Guests of Monitor Operation Set provided Region XX is a
non-default user Region XX by the U2000 by default. service-
group Topo contains a Topo NOTE function-based
Guests of Monitor If other members in the Topo Guests user group in the
Region XX Operation Set of Region XX require the Modify service
provided by the Object Position right, you must authorization
remove Monitor_B from Topo Guests
U2000 by and planning
of Region XX and then grant rights to
default. Monitor_B separately. phase. Users in
Topo Guests of
Region XX
have the rights
of querying
topology
objects. To
adjust rights for
Monitor_B,
remove Modify
Object
Position from
Topo Monitor
Operation Set.
2.2 Topo Modify the rights of the new Topo Topo Monitor
Guests Region Monitor Operation Set of Region Operation Set
XX contains the XX. of Region XX is
new Topo NOTE a new operation
Monitor If other members in the Topo Guests set assigned to
Operation Set of Region XX require the Modify Topo Guests of
of Region XX. Object Position right, you must Region XX and
remove Monitor_B from Topo Guests
has the rights of
of Region XX and then grant rights to
Monitor_B separately. querying
topology
objects. To
adjust rights for
Monitor_B,
remove Modify
Object
Position from
Topo Monitor
Operation Set.
3. Monitor_B does not belong to Modify the rights for Monitor_B In the Select
any user groups. directly. Operation
Rights window,
deselect Modify
Object
Position for
Monitor_B.
Procedure
l Operation procedure in scenario 1 (where Monitor_B is a member of Guests):
1. Choose Administration > NMS Security > NMS User Management (traditional
style) from the main menu or select Security Management in Application Center
and choose OSS Security > OSS User Management (application style) from the
main menu.
2. Choose NMS User Management > Operation Set > Topo Monitor Operation
Set from the navigation tree.
3. On the Members tab, click Select.
4. The Select Operation Set Member dialog box is displayed. In the Selected rights
group area, expand the nodes under Network Management Application. Select
5. Click OK.
l Operation procedure in scenario 2 (where Monitor_B is a member of the non-default user
group Topo Guests of Region XX):
– The operation procedure is the same as that in scenario 1.
– The operation procedure is similar to that in scenario 1. The only difference is Topo
Monitor Operation Set of Region XX is selected from the navigation tree on step 2.
l Operation procedure in scenario 3 (where Monitor_B does not belong to any user groups):
1. Choose Administration > NMS Security > NMS User Management (traditional
style) from the main menu or select Security Management in Application Center
and choose OSS Security > OSS User Management (application style) from the
main menu.
2. Choose NMS User Management > User > Monitor_B from the navigation tree.
3. On the Operation Rights tab, click Select.
4. The Select Operation Rights dialog box is displayed. In the Selected rights group
area, expand the nodes under Network Management Application. Select Modify
5. Click OK.
Result
If Monitor_B has logged in already, restart the client and relog in to the U2000 for the settings
to take effect. Then, Monitor_B does not have the rights of modifying positions for topology
objects.
3.2.10.3 Example for Creating U2000 User Accounts and Allocating Rights in the
Rights- and Domain-based Management Scenario
This topic provides the example for creating U2000 user accounts and allocating rights in the
rights- and domain-based management scenario.
Application Scenario
In an office, all NEs are monitored and managed through the U2000 in a centralized manner and
they are classed into two categories by domain: transport NEs and IP NEs, which are monitored
and managed separately. To enable different users to monitor and manage NEs through the
U2000, you need to assign them different U2000 user accounts and rights.
transport and IP
domain maintainer
NMS
transport domain IP domain
maintainer maintainer
PTN
PTN CX600
CX600
SDH
SDH
NE80E MA5200
Data Planning
Plan the following subnets based on the NE domain division:
l Transport domain subnet: All managed transport NEs are included.
l IP domain subnet: All managed IP NEs are included.
Plan the following four user groups based on user groups' responsibilities:
NOTE
The operation sets listed in the Operation Right column refer to general operation sets associated with
NEs in the transport or IP domains. Determine the actual operation sets to be added based on the types of
managed NEs and the operation rights of user groups.
Configuration Process
On the U2000, do as follows to create a user account and allocate associated rights:
1. Create subnets.
Create a transport domain subnet and an IP domain subnet, and add NEs in the transport
and IP domains to the associated subnets.
For details about how to create a subnet, see 5.4 Creating a Subnet.
For details about how to add an NE, see 5.6 Creating NEs.
2. Create user groups and allocate management domains and operation sets for the user groups.
You can easily allocate rights to multiple users by using the user group function.
l Based on responsibilities of user groups, configure management domains for the user
groups so that different user groups can manage different NE domains.
l Based on responsibilities of user groups, configure operation rights for the user groups
so that different user groups have different operation rights.
For details about how to create a user group, see 3.2.4.4 Creating and Authorizing U2000
User Groups.
3. Create user accounts.
Create user accounts for current users, and configure user groups based on responsibilities
of users. Then, each user account has the management domain and operation rights of the
user group.
For details about how to create a user account, see 3.2.4.5 Creating Users and Adding
the Users to User Groups.
NOTE
When creating user accounts, do as follows to ensure the U2000 security:
l Set different time available for login based on the shifts.
l Bind IP addresses of area workstations to users.
l Change the user password when logging in to the U2000 for the first time.
When the configuration is complete, the administrator can provide the accounts to associated
personnel.
Prerequisites
You have logged in as a user in SMManagers.
Context
The system ACL enables all the NMS users to log in to the U2000 only on the clients using the
specific IP addresses or network segments. The user ACL is a subset of the system ACL. The
user ACL is effective for the current user only.
NOTICE
l If there are multiple network adapters on the host where the client exists, you need to add
the IP addresses of all network adapters to the ACL. This ensures that users log in to the
U2000 clients successfully.
l When the network where the client is located has both the internal network and the external
network, you need to add both the internal IP address and the external IP address to the ACL,
ensuring that users can log in the U2000 client properly.
Procedure
Step 1 Choose OSS Security > Settings > System ACL (application style) or Administration > NMS
Security > System ACL (traditional style) from the main menu.
Step 2 In the System ACL dialog box, you can view existing ACLs. You can click Add, Delete, or
Modify to add, delete, or modify access control items, and click Close for the settings to take
effect.
Add a system ACL item 1. In the System ACL dialog box, click Add.
2. In the Add System Access Control Item dialog box,
select the display mode of IP addresses, set the related
parameters, and click OK.
Delete a system ACL item 1. In the System ACL dialog box, select the system ACL
item to be deleted, and click Delete.
2. In the Confirm dialog box, click Yes.
Modify a system ACL item 1. In the System ACL dialog box, select the system ACL
item to be changed, and click Modify.
2. In the Modify System Access Control Item dialog
box, modify the related parameters, and click OK.
NOTE
You can change the IP Address Display Mode only after
deleting a system ACL item and adding a new system ACL
item.
----End
Prerequisites
You have logged in as user admin or a user in SMManagers.
Context
l User admin can set access rights for all users. Users belonging to SMManagers can set
access rights for any user except user admin.
l The system ACL enables all the NMS users to log in to the U2000 only on the clients using
the specific IP addresses or network segments. A user ACL is a subset of the system ACL
and is effective only for the current user.
NOTICE
l If multiple network adapters are installed on the host where the client is deployed, add
the IP addresses of all network adapters to the ACL to ensure that users can log in to
the U2000 client successfully.
l When the network where the client is located has both internal and external networks,
add both the internal and external IP addresses to the ACL to ensure that users can log
in to the U2000 client properly.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 In the NMS User Management navigation tree, expand the User node, and then select a user
to be modified.
Step 3 Select the policies for using ACLs on the ACL tab page in the right pane of the window by
following the procedure provided in Table 3-13. Then, click Apply.
NOTE
l Access control items on the ACL tab page for a user come from the system ACL. That is, a user ACL
derives from the system ACL and serves as a subset of the system ACL.
l In the lower right corner of the ACL tab page for a user, click Set System ACL to open the System
ACL dialog box. You can click Add, Delete, or Modify to add, delete, or modify access control items
in the dialog box.
Option Setting
Use all ACLs After this option is selected, the settings of the corresponding user ACL are
consistent with those of the system ACL.
Use specified After selecting this option, you can log in to the U2000 server by using the
ACLs client with the selected IP address or network segment.
----End
Prerequisites
l You have logged in as a user in SMManagers.
l This function applies to the Router series, Switch series, Access series and Security NEs.
Context
l Newly configured access control items applies only to new proxy connections and do not
apply to existing proxy connections. To apply the newly configured access control items
to existing proxy connections, users must re-establish the proxy connections.
l When a user uses the proxy service to connect to an NE, the U2000 compares the source
IP address with the access control items from the top to the bottom in the Proxy Service
ACL dialog box. If a matched access control item is found, the comparison is complete. If
no matched access control item is found, the proxy connection request is rejected. Users
can click Up or Down to change the access control item sequence in the Proxy Service
ACL dialog box.
l If the networking includes gateway devices such as the Network Address Translation
(NAT) device, and U2000 clients or NEs are located on the internal NAT network, users
must set IP addresses in access control items to IP addresses that are stored on the NAT
device and can be connected to by the U2000 server. Do not set IP addresses in access
control items to internal network IP addresses to which U2000 clients or NEs are bound.
l If the U2000 client and server are installed on the same machine, you must set IP addresses
in access control items to 127.0.0.1.
l If IP Address or Network Segment is set to 0.0.0.0/0 (or a value in IP address/0 format)
and Operation is set to Accept in the proxy service ACL, clients in all network segments
can connect to NEs.
Procedure
Step 1 Choose OSS Security > Settings > Proxy Service ACL (application style) or
Administration > NMS Security > Proxy Service ACL (traditional style) from the main
menu.
Step 2 In the Proxy Service ACL dialog box, view the existing access control items. Click Add,
Delete, or Modify to add, delete, or modify an access control item, and then click OK for the
settings to take effect.
Adding an access control item 1. In the Proxy Service ACL dialog box, click Add.
2. In the Add Access Control Item dialog box, enter an
IP address or network segment, set Operation, and
click OK.
NOTE
l To improve system security, you are advised to enter an IP
address but not a network segment when adding an access
control item. If the IP address is changed, modify the access
control item of the proxy service ACL in a timely manner.
l If Operation is set to Accept, users can use the entered IP
address or an IP address in the entered network segment to
connect to an NE using the proxy service.
l If Operation is set to Reject, users cannot use the entered
IP address or an IP address in the entered network segment
to connect to an NE using the proxy service.
Deleting an access control item 1. In the Proxy Service ACL dialog box, select an access
control item to be deleted, and click Delete.
2. In the Confirm dialog box, click Yes.
NOTE
After connecting to NEs from clients by using the proxy service
and performing required operations, users must manually delete
access control items that they have set to prevent other users from
connecting to the NEs based on the access control items.
Modifying an access control item 1. In the Proxy Service ACL dialog box, select an access
control item to be modified, and click Modify.
2. In the Modify Access Control Item dialog box,
change the IP address or network segment, modify
Operation, and click OK.
NOTE
l If Operation is set to Accept, users can use the entered IP
address or an IP address in the entered network segment to
connect to an NE through the proxy service.
l If Operation is set to Reject, users cannot use the entered
IP address or an IP address in the entered network segment
to connect to an NE through the proxy service.
----End
Prerequisites
You have logged in as a user in SMManagers.
Context
l Account policies must be configured after the U2000 is installed for the first time. During
maintenance, the account policies can be adjusted as required.
l New account policies do not affect the configured accounts.
Procedure
Step 1 Choose OSS Security > Settings > Security Policy (application style) or Administration >
NMS Security > Security Policies (traditional style) from the main menu.
Step 2 In the Security Policy dialog box, click the Account Policy tab, and view the current account
policies.
Step 3 According to the policy planning, set account policies by following the procedure provided in
Account Policy. Then, click OK to confirm the settings.
----End
Prerequisites
You have logged in as a user in SMManagers.
Context
l User password policies must be set during the initial phase of site deployment and can be
adjusted as required during the maintenance.
l After a password policy is changed, the new password policy takes effect immediately for
all users of the U2000. For example, after the minimum length of the user password is
changed, when an online user changes a password, the minimum password length must
comply with the corresponding password policy.
l New password policies do not affect passwords that have been set.
l Password policies specify the password complexity, update periods, and character
restrictions.
Procedure
Step 1 Choose OSS Security > Settings > Security Policy (application style) or Administration >
NMS Security > Security Policies (traditional style) from the main menu.
Step 2 In the Security Policy dialog box, click the Password Policy tab, and view the current password
policies.
NOTE
You can set account policies on the Account Policy tab page. For details, see 3.3.1.4 Setting Account
Policies.
Step 3 Set basic and advanced parameters for password policies as required.
----End
Prerequisites
l You have logged in as a user in SMManagers.
l A user or user group has been created or is being created.
Context
l A user can log in to the U2000 server through multiple terminals. The user can also start
multiple U2000 clients on one terminal to log in to the U2000 server. Setting the maximum
number of user sessions limits the total number of sessions that a user creates on multiple
login terminals.
l User groups are categorized based on user roles. To balance the access attempts of different
user roles to the system, you can set the maximum number of user group sessions to limit
the total number of sessions that the users in a user group create on all the login terminals.
l The setting of the maximum number of user sessions and user group sessions is limited by
the system login mode. If the current system login mode is the single-user login mode, only
one user admin is allowed to log in to the U2000 through one U2000 client regardless of
the setting of the maximum number of user group sessions and user sessions.
Procedure
Step 1 Select an operation mode based on the actual situation.
If... Then...
You are creating a user group or user Set the maximum number of user group sessions and
user sessions by following the procedure provided
in 3.2.4.4 Creating and Authorizing U2000 User
Groups and 3.2.4.5 Creating Users and Adding
the Users to User Groups.
You have created a user group or user 1. Choose OSS Security > OSS User
Management (application style) or
Administration > NMS Security > NMS User
Management (traditional style) from the main
menu.
2. In the NMS User Management navigation
tree, expand the User Group or User node.
3. Select a user group or a user, on the Details tab
page in the right pane, set Maximum sessions
for user groups or Maximum number of online
users for users.
----End
Prerequisites
l You have logged in as user admin.
l Plan the time of switching the login mode and ask other users to save their operations.
Context
l The setting takes effect for all the users that log in to different clients.
l In single-user login mode, only user admin is allowed to log in to the system. Therefore,
only user admin can set the system login mode to the single-user login mode.
NOTICE
Only the admin user can log in to the U2000 on a client and all the other users are forced
to exit after the U2000 login mode is switched from the multi-user mode to the single-user
mode. You need to switch to the multi-user mode after you complete the operations in
single-user mode. Therefore, other users can operate the U2000 properly.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, choose System Login Mode in the navigation tree on the left.
Single-user mode Select Single-user mode and click OK. In the Set Switch
Delay dialog box, set the delay time for switching the login
mode, and click OK.
l If the delay time is not 0, a warning dialog box is
displayed. After the specified delay time, the U2000 is
switched to the single-user mode.
l If the delay time is 0, no warning dialog box is displayed.
The U2000 is directly switched to the single-user mode
immediately.
----End
By Security Policy
Prerequisite
You have logged in as an NMS user.
Context
l After a U2000 client is locked, only the current user or user in the Administrators group
can unlock it. The current user can unlock the client by following the message displayed
in the window. To unlock the client as user in the administrators group, see 1.13 Unlocking
the Client.
l The operation is valid for all online users.
l The priority is higher than the priority of Automatically lock terminal in the
Preferences dialog box.
NOTICE
After a user in the Administrators group unlocks an U2000 client, the original logged in user
is logged out.
Procedure
Step 1 Choose OSS Security > Settings > Security Policy (application style) or Administration >
NMS Security > Security Policies (traditional style) from the main menu.
Step 2 In the Security Policy dialog box, click the Account Policy tab.
Step 3 Select Automatically lock the terminal if no activity for XX minute(s), set the time of enabling
auto-locking, and then click OK to apply the settings.
----End
By Preference
Prerequisite
Context
l After a U2000 client is locked, only the current user or user in the administrators group can
unlock it. The current user can unlock the client by following the message displayed in the
window. To unlock the client as user in the administrators group, see 1.13 Unlocking the
Client.
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
l On the Account Policy tab page in the Security Policy dialog box, if you select
Automatically lock the terminal if no activity for XX minute(s) check box,
Automatically lock terminal in the preferences dialog box is unavailable.
NOTICE
After a user in the administrators group unlocks an U2000 client, the original logged in user is
logged out.
Procedure
Step 2 From the navigation tree in the left part of the window, select Lock Settings.
Step 3 Select Automatically lock terminal, set the time of enabling auto-locking, and click OK to
apply the settings.
NOTE
In the Preferences dialog box, select Show main window when terminal locked in the Lock Settings
area. Therefore, after the client is locked, the main window of the client is visible.
----End
3.3.2.1 Setting a Secure Connection Between the U2000 Client and Server
This section describes how to set the SSL communication mode between the U2000 client and
server.
Prerequisites
The SSL communication mode is enabled on the U2000 server. For details about how to set the
SSL communication mode, see the U2000 administrator guide.
Context
Data transmission security is ensured when the SSL communication mode is set on both the
U2000 client and server.
Procedure
Step 1 Start the U2000 client. In the Login dialog box, click .
Step 2 In the Server List dialog box, select a server record, and click Modify.
In the Server List dialog box, if no server information exists, add the server information as
follows:
Step 3 In the Modify Server Information dialog box, select Security(SSL) from the Mode drop-down
list.
After change the communication mode in the Mode drop-down list, the value of Port changes
automatically. The default settings for the port and communication mode are as follows:
l If the communication mode is set to Common, the port is 31037.
l If the communication mode is set to Security(SSL), the port is 31039.
Step 4 Click OK separately in the Modify Server Information and Server List dialog boxes.
The Login dialog box is returned. The client setting is complete.
----End
Follow-up Procedure
After you click Login, if the client does not trust the server, you need to determine whether the
server is trustable using the server certificate.
l If you confirm that the server is trustable, click Yes and log in to the client. If you do not
want the system to display the dialog box again, contact the system administrator to
configure a trust certificate.
l If you confirm that the server is not trustable, click No to return to the Login dialog box
and contact the system administrator to process the issue.
3.3.2.2 Setting the FTP Transfer Policies Between the Client and Server
Files can be transferred between the U2000 client and server. You can set FTP Mode and transfer
parameters as required.
Prerequisites
You have logged in as a user who belongs to the Administrators groups.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, select OSS Client/Server File Transfer Settings.
Step 3 In the OSS Client/Server File Transfer Settings dialog box, set FTP Mode, FTP Option, and
Network timeout (5-3600s).
l FTP Mode includes FTP and SFTP.
NOTE
Using SFTP is recommended because of its higher security than FTP.
l FTP Option includes Resumable Transfer, Compression, and Passive Mode. If Passive
Mode is not selected, the default mode is active mode.
l Network timeout (5-3600s) ranges from 5 to 3600 seconds. Its default value is 120 seconds.
----End
Prerequisites
l You have logged in as an NMS user.
l You are familiar with password policies. For details, see 3.3.1.5 Setting Password
Policies.
Procedure
Step 1 Choose OSS Security > Change Password (application style) or File > Change Password
(traditional style) from the main menu.
Step 2 In the Change Password dialog box, set the new password for the current user, and click OK.
Step 3 In the Confirm dialog box, click Yes to confirm the settings.
----End
Context
l The configured password must comply with all password policies except the difference
policies Previously used passwords that cannot be the same as the new password, Min.
different characters between new and old password and Password repetition not
allowed within (months). For details about how to set password policies, see 3.3.1.5
Setting Password Policies.
l The SMManagers user can re-set the passwords of all users, except for the admin user,
other security administrators, and itself. The password of a security administrator needs to
be re-set by the admin user.
l The password of the admin user must be kept secure because the admin user cannot reset
it.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 In the NMS User Management navigation tree, expand the User node. Right-click the user
whose password is to be reset and choose Reset Password.
Step 3 In the Reset Password dialog box, set New Password and Confirm Password, and then click
OK.
NOTE
If Require user to change password on next login is selected, you need to change the password when
you log in to the U2000 client next time. Otherwise, you do not need to change the user password when
you log in to the U2000 client next time. You are advised to select Require user to change password on
next login to improve the security of the U2000 system.
----End
Prerequisites
You have logged in as a user in SMManagers.
Context
l You can modify only Disable user account, Password validity period (days), New
password, Require user to change password on next login, Login period, and Auto-
logout, and cannot modify other parameters such as user group, domain, operation rights,
and ACL.
l You cannot modify the information about the current user, admin and remote user. If the
selected user list contains the current user, admin or remote user, Modify Multiple
Users is unavailable.
l You can choose Modify Multiple Users to modify information about a maximum of 100
users.
Procedure
Step 1 Choose OSS Security > OSS User Management (application style) or Administration > NMS
Security > NMS User Management (traditional style) from the main menu.
Step 2 Expand the User node In the NMS User Management navigation tree, and select one or more
users in the user list on the right.
Step 3 Right-click one of the selected users and choose Modify Multiple Users from the shortcut menu.
In the Confirm dialog box, click Yes.
Step 4 In the Modify Multiple Users dialog box, specify the parameter values.
NOTE
The configured password must meet all password policies except the policies related to user accounts and
differences between old and new passwords. The password policies related to user accounts include
Password cannot be any user name in reverse order and Max. Same Consecutive Characters Between
User Name and Password. The password policies related to differences between old and new passwords
include Previously used passwords that cannot be the same as new password, Min. different
characters between new and old password, and Password repetition not allowed within (months). For
details about how to set a password policy, see 3.3.1.5 Setting Password Policies.
----End
Result
The parameters are modified successfully according to the settings in the Modify Multiple
Users dialog box.
Prerequisites
You have logged in as an NMS user.
Context
After an U2000 client is locked, only the current user or user in the administrators group can
unlock it. The current user can unlock the client by following the message displayed in the
window. To unlock the client as user in the administrators group, see 1.13 Unlocking the
Client.
NOTICE
After a user in the administrators group unlocks an U2000 client, the original logged in user is
logged out.
Procedure
Step 1 Lock your U2000 client in either of the following ways:
l Choose File > Lock Terminal from the main menu.
----End
Prerequisites
The U2000 client is locked.
Procedure
The following table describes how to unlock the client in different scenarios.
If the current user l A user in the SMManagers group need to reset the current user
forgets the password password. For details, see 3.3.3.2 Resetting the Password of an
NMS user. Then log in to the client again using the user name and
the new password.
NOTE
A user in the SMManagers group cannot reset the password of the
admin user. If the current user is admin, only a user in the
Administrators group can unlock the client.
l The current user must ask a user in the Administrators group to
unlock the client. After the client is unlocked, the current user is
logged out.
1. Press Ctrl+Alt+U or click .
2. Enter the user name and password of the user in the
Administrators group, and click OK.
NOTE
If the number of password retries reaches the upper limit (3 by default), the user account is locked for a
specified period (30 minutes by default). The U2000 user is automatically unlocked after the auto-unlocking
duration. The U2000 user can also be unlocked by security administrators manually. For details, see 3.3.4.4
Unlocking Users.
Prerequisites
You have logged in as a user in SMManagers.
Context
l Illegal login indicates the login to the U2000 system of an NMS user with an incorrect
password. The maximum number of illegal login times and the auto-unlocking duration
can also be set when the user account policies are set. For the description of relevant
parameters, see Account Policy.
l To manually unlock a user as security administrators, see 3.3.4.4 Unlocking Users.
Procedure
Step 1 Choose OSS Security > Settings > Security Policy (application style) or Administration >
NMS Security > Security Policies (traditional style).
Step 2 On the Account Policy tab page, set the maximum number of illegal login times and the auto-
unlocking duration, and then click OK to apply the settings.
----End
Prerequisites
You have logged in as a user in the SMManagers group or a user who has the Monitor All
User Sessions right.
Context
l A session refers to the connection established between the client and the server. A session
starts when the user logs in to the client, and ends when the user logs out or exits the client.
l Multiple sessions can be created by using one NMS user account.
On the U2000, a user account can be used to log in to multiple clients concurrently. You
can set the maximum number of clients to which a user account can be used to log in
concurrently in Maximum of online users on the Details tab. If this user account is used
to log in to a certain number of clients, the same number of sessions are established.
l When the client uses multiple network adapters, the value of Operation Terminal is
selected randomly among available IP addresses.
Procedure
Step 1 Choose OSS Security > User Session Monitor (application style) or Administration > NMS
Security > User Session Monitor (traditional style) from the main menu.
Step 2 In the User Session Monitor window, view the information about login and other operations
performed by NMS users.
Session Monitor In the Session Monitor area, you can view the information about
online users and sessions.
NOTE
l After the U2000 server is restarted or the network is recovered from a
disconnection, you need to click Refresh to update the session monitor
table.
l If you select the local client in the Session Monitor area, Force User to
Log Out and Send Message becomes unavailable.
----End
Procedure
Step 1 Choose OSS Security > User Operator Monitor (application style) or Administration > NMS
Security > User Operator Monitor (traditional style) from the main menu.
Step 2 Click Filter. In the displayed Filter dialog box, set the operation information to be displayed.
Click OK.
Step 3 In the Monitor User Operation window, view information about operations performed by
U2000 users.
NOTE
l When an operation affects the U2000, you can limit the user who performs this operation according to
the actual U2000 applications. For example, you can force the user to log out in the User Session
Monitoring window.
l You can monitor the operations performed by the following users in the Monitor User Operation
window:
l Common users or Administrators: In the Query Operation Logs window, click Choose at the
lower left corner in the Filter dialog box. In the Select Operation Name dialog box, you can view
the operations that can be monitored. For details, see 4.4.1 Querying U2000 Operation Logs.
l SMManger: In the Query Security Logs window, click Choose at the lower left corner in the
Filter dialog box. In the Select Security Event dialog box, you can view the operations that can
be monitored. For details, see 4.3.1 Querying U2000 Security Logs.
----End
Context
l Only members of the SMManagers group can force a user to quit. If you force a user to
quit session, only the user corresponding to a session is logged out forcibly. For example,
a user logs in to the U2000 server as user user_z on clients A and B respectively. Sessions
a and b are generated. When user user_z on client A is forcibly logged out, session b is not
affected.
l Users who have logged in cannot force themselves to quit their corresponding sessions.
Procedure
Step 1 Choose OSS Security > User Session Monitor (application style) or Administration > NMS
Security > User Session Monitor (traditional style) from the main menu.
Step 2 From the Session Monitor table, select the records of the sessions to be quit forcibly, and then
click Force User to Log Out.
Step 3 In the Confirm dialog box, click Yes.
----End
Prerequisites
You have logged in as a user in SMManagers.
Procedure
The U2000 supports the following user account unlocking modes.
Unlocking Mode Operation Method
Manual unlocking Only a member of the SMManagers group can perform the following
operations:
1. Choose OSS Security > OSS User Management (application
style) or Administration > NMS Security > NMS User
Management (traditional style).
2. In the NMS User Management navigation tree, expand the
User node.
3. Right-click the locked user account, and choose Unlock User.
After that, the unlocked user can log in to the U2000 successfully.
Automatic unlocking The locked user can log in to the U2000 only when the preset
automatic unlocking time arrives.
NOTE
You can set the automatic unlocking time in Account Policy. The procedure
is as follows:
Choose OSS Security > Settings > Security Policy (application style) or
Administration > NMS Security > Security Policies (traditional style). In
the displayed Security Policy dialog box, click the Account Policy tab, and
set Auto-unlock (minutes).
Context
On the U2000, users of current sessions cannot send messages to themselves.
Procedure
Step 1 Choose OSS Security > User Session Monitor (application style) or Administration > NMS
Security > User Session Monitor (traditional style) from the main menu.
Step 2 In the Session Monitor area, send messages to the users of the specified sessions or all sessions.
A specified session Right-click a session and choose Send Message. Enter the message
contents, and then click Send.
Multiple sessions Use the Ctrl or Shift key to select multiple sessions. Right-click the
selected sessions and choose Send Message. Enter the message
contents, and then click Send.
All sessions Use the combination key Ctrl+A to select all sessions. Right-click the
selected sessions and choose Send Message. Enter the message
contents, and then click Send.
NOTE
You can choose System > Broadcast Message (application style) or Administration > Broadcast
Message (traditional style) to send broadcast messages to the users of all sessions. For details, see 1.16.2
Sending Broadcast Messages.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l This function applies to the MSTP series, WDM series, WDM (NA) series, RTN series,
PTN series (except PTN 6900 series) and marine series NEs.
Context
l To facilitate maintenance, the U2000 provides the remote maintenance function. A
maintenance engineer can log in to the remote maintenance terminal as the remote
maintenance user and maintain NEs. It is recommended that the remote maintenance user
be enabled only when a fault occurs.
l For security purposes, it is recommended to create the NE user name and password before,
and then you can use them directly in the interface.
Procedure
Step 1 Choose Administration > NMS Security > Remote Maintenance User Management
(traditional style) from the main menu or select Security Management in Application
Center and choose OSS Security > Remote Maintenance User Management (application
style) from the main menu.
Step 2 In the Remote Maintenance User Parameters dialog box, enable the remote maintenance user.
Step 3 Input the NE User Name and NE User Password.
Step 4 Click Select NE. In the dialog box that is displayed, select the NE.
Step 5 Click OK.
----End
Follow-up Procedure
After the remote maintenance user is enabled, an NE user can log in to the NE from the
U2000 remote maintenance terminal.
NOTE
By default, you can log in to the NE from the U2000 remote maintenance terminal only as an NMS user
that has rights of the Maintenance Group group or higher-level rights.
NE Access Control
LCT Access Control: If you need to use the U2000 LCT or Web LCT for the NE management
or commissioning, enable the LCT Access Control so that the LCT can access the NE.
ACL: The access control list (ACL) provides the basic filtering function for the data flow. All
NEs that have the ACL configured can determine whether to filter out an IP packet when the IP
packet passes the NE. The ACL controls the direction of a specific data flow as to whether the
data flow is transmitted in or out of a network.
Communication Port Access Control: An NE can access the U2000 by using the OAM, COM,
Ethernet port or serial port. You can set the port for the NE access by enabling the access control
of the port. By default, an NE is allowed to access the U2000 by Ethernet ports.
NE login management
NE login: To ensure the security of the NE data, an NE user must prevent unauthorized users
from logging in to the NE to obtain information or perform operations.
NE User Management
NE User: To ensure the security of the NE data, you must use the created NE user to log in to
the NE. In addition, you can only perform the operations that are authorized to the NE user.
NE User Level: Based on the operation types authorized to a user, the NE users are regarded as
having different operation levels. This level is known as the NE user level. The NE users of
different levels are allocated to different NE user groups. The operation rights of NE users have
different levels. The user with a higher rights level can perform all operations that are authorized
to a user with a lower right level. For example, the user of the operation level has all the operation
rights authorized to the user of the monitor level. The following describes what operations are
authorized to each level.
l For Non-NA NEs, the NE user has the following five levels in ascending order: monitor
level, operation level, maintenance level, system level, and debug level. The authorities of
the five user levels are as follows:
– Monitor level: all the query commands, login, logout, password modification
– Operation level: all the fault and performance settings, part of security settings, part of
configurations
– Maintenance level: part of security settings, part of configurations, communication
settings, log management
– System level: all the security settings, all the configurations
– Debug level: all the security settings, all the configurations, debug commands
l For the NA NEs, the NE user has the following four levels in ascending order: RTRV,
MAINT, PROV, and SUPER. The authorities of the four user levels are as follows:
– RTRV: This user level has the right to use all query commands, to log in, to log out,
and to change its own password.
– MAINT: This user level has all fault performance authorities, some security authorities,
and some configuration authorities.
– PROV: This user level has some security authorities, some configuration authorities,
the communication setting authority, and the log management authority.
– SUPER: This user level has all security and configuration authorities.
Authority Management: To ensure the security of the NE data, any one who wants to perform
operations on an NE must log in to the NE as an NE user, and can only perform the operations
authorized to this user. It is recommended that the network manager create NE users before
configuring services. Make sure that when you create a common user account that can be used
on all NEs, keep the rights levels on all NEs consistent to avoid the disorder of user rights.
NE Data Backup/Restoration
NE Data Backup: Backing up the NE database is necessary for daily maintenance. With the
backup of the database, the NE can automatically restore the NE data and run normally if the
data on the SCC is lost or the equipment is powered off.
NE Data Restoration: If an NE becomes faulty during daily maintenance, the NE data is restored
based on the data backup on the SCC or CF card.
Prerequisites
This function applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN
series (except PTN 6900 series) and marine series NEs.
Context
ACL provides the basic filtering function for data flow. All NEs that have the ACL configured
can determine whether to filter out an IP packet when the IP packet passes the NE. The ACL
controls the direction of a specific data flow whether the data flow is transmitted in or out of a
network.
The most important reason to configure ACL is for the network security. ACL can provide the
basic flow control function, so proper ACL rules, the entire network can be prevented from
security threats.
The ACL can control whether certain NEs receive or drop the IP packets. Each IP packet is
examined by the NEs based on predefined ACL rules. After the examination, the NEs determine
whether to receive or drop this packet.
Purpose
The most important reason to configure ACL is for the network security. With proper ACL rules,
the entire network can be prevented from security threats. ACL can also provide the basic flow
control function.
Implementation
The ACL can control whether certain NEs receive or drop the IP packets. Each IP packet is
examined by the NEs based on predefined ACL rules. After the examination, the NEs determine
whether to receive or drop this packet.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
NOTICE
Pay attention to using the command to set the ACL, because wrong setting of the ACL may
cause the U2000 to fail to log in to an NE.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > ACL from the Function Tree.
Step 2 On the Basic ACL tab, the basic ACL rule list is displayed.
NOTE
If the equipment only supports basic ACL settings, the basic ACL rule list is displayed after you choose
Security > ACL from the Function Tree.
Step 3 Click Query to load the basic ACL rules from the NE.
Step 6 Click Apply to apply the new configuration data to the NE.
The Result dialog box is displayed, indicating that this operation is successful.
Step 8 Optional: Repeat Step 4 to Step 7 to set more basic ACL rules for this NE.
Step 9 Optional: Repeat Step 1 to Step 8 to set the basic ACL rules for other NEs.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
NOTICE
If the setting is incorrect, the U2000 cannot communicate with the NE.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > ACL from the Function Tree.
Step 2 Click the Advanced ACL tab. The advanced ACL rule list is displayed.
Step 3 Click Query to load the advanced ACL rules from the NE.
Step 6 Click Apply to apply the new configuration data to the NE.
The Result dialog box is displayed, indicating that operation is successful.
Step 8 Optional: Repeat Step 4 to Step 7 to set more advanced ACL rules for this NE.
Step 9 Optional: Repeat Step 1 to Step 8 to set the advanced ACL rules for other NEs.
----End
Prerequisites
Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
NOTICE
This operation may affect the communication between the U2000 and NEs.
Procedure
Step 1 In the NE Explorer, choose Communication > Access Control from the navigation tree.
Step 2 In the Ethernet Access Control area, click Refresh to check whether Ethernet access is enabled.
Step 3 Configure Ethernet access according to the GUI instructions. The configuration methods vary
with NE types.
l Select the Enable Ethernet Access check box and click Apply. Ethernet access is enabled
for the NE.
NOTE
If you want to disable this function, clear the Enable Ethernet Access check box and click Apply.
l Set The First Network Port to Enabled and click Apply. Ethernet access is enabled for
the NE.
NOTE
l If you want to disable this function, set The First Network Port to Disabled and click Apply.
l If a second network port exists, you can also enable Ethernet access for this port. For OptiX OSN
NEs, the second network port is an EXT port.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 In the NE Explorer, choose Communication > Access Control from the navigation tree.
Step 2 Configure serial port access according to the GUI instructions. The configuration methods vary
with NE types.
l Select the Enable Serial Port Access check box. Click Apply to apply the setting to the
NE.
l Select the Enable Serial Port Access check box. Click Refresh to check whether the
current NE allows serial port access. Select Access Command Line or Access NM as
required. Click Apply to apply the setting to the NE.
Step 3 Select a baud rate allowed for serial port access from the Baud Rate drop-down list and click
Apply.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l This function applies to the MSTP series NEs.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Access Control from the
Function Tree.
Step 2 Select the Enable OAM Access check box and click Apply. The OAM access of the NE is now
enabled.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l This function applies to the MSTP series, Metro WDM series, LH WDM series, RTN series,
PTN series, and Marine series NE.
Context
l The COM port directly connects to the SCC board, improper usage may affect the normal
service handling on the NE, and the rate of the COM port is slow. Therefore, it is
recommended to use Ethernet access for the U2000 LCT or Web LCT in most cases.
l Use COM port access only when the Ethernet access fails, the NE already connects to the
U2000, or certain lower layer commissioning commands need to be run.
l For security measures, the COM port access is disabled by default after NE initialization
or downloading. If necessary, use the U2000 to temporarily enable COM access.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > Access Control from the
Function Tree.
Step 2 Select the Enable COM Access check box and click Apply. The COM access of the NE is now
enabled.
----End
Prerequisites
You are an NMS user with Administrators authority.
Context
l When no U2000 user logs in to an NE and an LCT user requests to log in to the NE, the
NE does not refer to the LCT Access Control parameter and allows the LCT access
directly.
l When a U2000 user has logged in to an NE and then an LCT user requests to log in to the
NE, the NE determines whether to allow the LCT user to log in based on the LCT Access
Control parameter.
l When an LCT user has logged in to an NE and then a U2000 user requests to log in to the
NE, the login of the LCT user does not affect the login of the U2000 user, and the successful
login of the U2000 user does not affect the logged-in LCT user.
l When the LCT user and the U2000 user log in to the NE at the same time, set LCT Access
Control to Prohibit Access. This does not affect the LCT user that has already logged in.
l After the OptiX OSN 500 is disconnected to the U2000 for over 30 minutes, the OptiX
OSN 500 automatically allows the LCT access.
Procedure
l If you want to manage network-wide LCT access, use the following method to the navigate
to the LCT Access Control window.
1. Choose Administration > NE Security Management > NE Login Management
(traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > NE Login
Management (application style) from the main menu. Click the LCT Access
Control tab.
2. Select the NE to be set from the NE list and click .
3. Click Query to query whether the current NE allows LCT access.
4. Optional: Select an NE and click Access Allowed to enable LCT access.
5. Optional: Select an NE and click Prohibit Access to disable LCT access.
6. Optional: To set LCT access for multiple NEs in batches, select the NEs, right-click,
and then choose a menu item from the shortcut menu.
l If you want to manage LCT access for a certain NE, use the following method.
1. In the NE Explorer, select an NE and choose Security > LCT Access Control from
the Function Tree.
2. Click Query to query whether the current NE allows LCT access.
3. Click Access Allowed to enable LCT access.
NOTE
----End
Prerequisites
This function applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN
series (except PTN 6900 series) and marine series NEs.
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l The current NE user has the highest authority among all logged-in NE users.
l The NEs are release 4.0 transport NEs.
Procedure
Step 1 Choose Administration > NE Security Management > Lock Out NE Login (traditional style)
from the main menu or select Security Management in Application Center and choose NE
Security > Fix-Network NE > Lock Out NE Login (application style) from the main menu.
Step 2 In the NE list that contains only the available NEs, select an NE and click .
Step 4 Optional: If the value of Login Lock Status is Not Locked out, select it and click Lock
Login or right-click it and choose Lock Login from the shortcut menu.
----End
Follow-up Procedure
After the exclusive NE operation is complete, unlock the NE user immediately by performing
the following operations: Select the desired NE and click Unlock Login or right-click the NE
and choose Unlock Login from the shortcut menu.
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l The current NE user has the highest authority among all logged-in NE users.
Context
The user occupies its setting authority until it unlocks the module. NEs can be divided into
configuration module, alarm module, communication module, performance module, protect
switching module, database module and security module, and these modules can be locked
respectively or simultaneously.
After a user locks an NE, only the user has the configuration authority, so that the NE data can
be kept consistent when multiple users manage NEs at the same time. This function features the
following:
l This function takes effect immediately after the lockout.
l An NE user at any level can perform the lockout.
Procedure
Step 1 Choose Administration > NE Security Management > Lock Out NE Settings (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > Lock Out NE Settings (application style) from the main
menu.
Step 2 In the NE list that contains only the available NEs, select an NE and click .
Step 4 Select an NE functional module, if the value of Set Lock Status is No, select it and click
Lockout or right-click it and choose Lockout from the shortcut menu.
Step 5 In the Set Lock Window dialog box, select the Lock Permanently check box to permanently
lock the current NE settings or enter the value of Continues Time to temporarily lock the
settings. Click OK.
----End
Follow-up Procedure
After the exclusive NE operation is complete, unlock the NE settings immediately by performing
the following operations: Select the desired NE and click Clear Lockout or right-click the NE
and choose Clear Lockout from the shortcut menu.
Prerequisites
You are an NMS user with Administrators authority.
Procedure
Step 1 Choose Administration > NE Security Management > NE Login Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > NE Login Management (application style) from the main
menu. Click the Online User Management tab.
----End
Prerequisites
l You are an NMS user with Administrators authority.
l NE users are created.
Context
l Only one NE user can log in to an NE from the same U2000 server at a time to manage the
NE.
l One NE user cannot log in to or manage an NE at multiple clients at the same time. If you
use an NE user to log in to the same NE through U2000 server A and B in turn, both NE
login attempts fail and indicators are blinking on different clients indicating that the NE
user has already logged in or exited.
l For an NE managed by multiple network management systems (NMSs), create a login
account for each NMS to prevent conflicts and frequent changes of the NE between the
online and offline status. In addition, upload NE data before performing operations on the
NE to ensure data consistency.
Procedure
Step 1 Choose Administration > NE Security Management > NE Login Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > NE Login Management (application style) from the main
menu.
Step 2 Click NE Login Management or DC Login User Management tab.
On the NE Login Management tab, switching a logged-in NE user in offline mode is supported; this is
not supported on the DC Login User Management tab.
----End
Prerequisites
l You are an NMS user with Administrators authority.
l An NE user has been created.
l The NE user has logged in.
Procedure
Step 1 Choose Administration > NE Security Management > NE Login Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > NE Login Management (application style) from the main
menu.
Step 2 Select the NE to log out of the U2000 from the NE list and click .
Step 3 On the NE Login Management or Online User Management tab, select the NE and click
Logout or Force Logout.
Step 4 In the Result dialog box indicating that the operation succeeded, click Close.
----End
Prerequisites
l You are an NMS user with Administrators authority.
l Log in to the NE as a user with the system level or higher rights.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Security Parameters from the
Function Tree.
Step 3 Select an NE, double-click Warning Screen Switching and choose whether to enable the
warning screen.
Step 4 Double-click Warning Screen Information and enter the NE login prompt message
information.
NOTE
You can enter information in the Warning Screen Information field only when you set Warning Screen
Switching to Enabled.
Step 5 Click Apply. The Result dialog box is displayed, indicating that this operation was successful.
Click Close.
----End
Prerequisites
The following functions apply to the MSTP series, WDM series, WDM (NA) series, RTN series,
PTN series (except PTN 6900 series) and marine series NEs.
Prerequisites
l You are an NMS user with Administrators authority.
l The level of the NE user to be queried is lower than that of the logged-in NE user.
Procedure
Step 1 Choose Administration > NE Security Management > NE User Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > NE User Management (application style) from the main
menu.
Step 3 Optional: Click Query to query NE user information from the NE.
Step 4 Click View Additional User Info to query additional information about this NE user.
----End
Prerequisites
l You are an NMS user with Administrators authority.
l The level of the NE user to be created is lower than that of the logged-in NE user.
NOTE
Choose Administration > NE Security Management > NE User Management (traditional style)
from the main menu or select Security Management in Application Center and choose NE
Security > Fix-Network NE > NE User Management (application style) from the main menu. You
can view the level information about NE users on the NE User Management window.
Context
To ensure NE data security, it is recommended that you allocate NE users with different
authorities as required.
Procedure
Step 1 Choose Administration > NE Security Management > NE User Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > NE User Management (application style) from the main
menu.
Step 6 In the NE User Flag field, select a user type based on the type of the terminal through which
the user logs in to the NE.
Step 7 Click the after the New Password, enter the new password in the output dialog box, click
OK.
NOTE
The password must meet the following requirements to safeguard your user account.
1. The password consists of 8 to 16 characters.
2. The password cannot duplicate or reverse the user name.
3. The password consists at least three of the following characters:
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ? and space
NOTE
You also need to set the Immediate Password Change, Valid Permanently, Valid From, Valid Until,
Password Permanently Valid and Password Valid Days.
For the NA NE, you also need to set the Canceling User Automatically, Log Out User After (min),
User Permanently Valid, User Valid Days, Password Permanently Valid and Password Valid Days.
Step 8 Optional: Select the Hide NEs already using this user name check box, the NEs that already
use the user name are not included in the NE Name field.
NOTE
Selecting the Hide NEs already using this user name check box makes it easier to create NE users in
batches.
Step 9 In the NE Name field, select one or more NEs that this NE user is allowed to manage.
----End
Prerequisites
l You are an NMS user with Administrators authority.
l The NE user is created.
l The level of the NE user to be modified is lower than that of the logged-in NE user.
NOTE
Choose Administration > NE Security Management > NE Login Management (traditional style)
from the main menu or select Security Management in Application Center and choose NE
Security > Fix-Network NE > NE Login Management (application style) from the main menu.
You can view the login information about NE users on the NE Login Management tab.
Procedure
Step 1 Choose Administration > NE Security Management > NE User Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > NE User Management (application style) from the main
menu.
Step 3 In the NE User Management Table, select the NE user to be modified and click Modify. The
Modify NE User dialog box is displayed.
Step 4 In the Modify NE User dialog box, modify the settings of the attributes of the NE user. Click
Apply.
----End
Prerequisites
l You are an NMS user with Administrators authority.
l An NE user has been created.
Context
If the default NE user password is not changed, the NE reports the
PASSWORD_NEED_CHANGE alarm to the U2000, prompting for immediate change to the
default password.
NOTICE
Change NE user passwords regularly and keep them secure for security purposes.
Procedure
Step 1 Choose Administration > NE Security Management > NE User Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > NE User Management (application style) from the main
menu.
Step 2 Select one or multiple NEs from the NE list and click .
The level of the currently logged-in NE user must be higher than that of the NE user whose password
is to be changed.
NOTE
The password must meet the following requirements to safeguard your user account.
1. The password consists of 8 to 16 characters.
2. The password cannot duplicate or reverse the user name.
3. The password consists at least three of the following characters:
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ? and
space
3. Click OK.
l Currently logged-in NE user:
1. Click Set Current User Password.
NOTE
Alternatively, you can Choose Administration > NE Security Management > NE Login
Management (traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > NE Login
Management (application style) from the main menu. click the NE Login Management tab,
select the currently logged-in NE user, and click Set Current User Password.
2. In the Set Password of NE User dialog box, set the New Password of the NE name.
NOTE
The password must meet the following requirements to safeguard your user account.
1. The password consists of 8 to 16 characters.
2. The password cannot duplicate or reverse the user name.
3. The password consists at least three of the following characters:
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ? and
space
3. Click OK.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l This function applies to the release 5.0 transport NEs.
l Log in to the NE as a user with the system level or higher rights.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Security Parameters from the
Function Tree.
----End
Prerequisites
You are an NMS user with Administrators authority.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE User Group Management from
the Function Tree.
Step 2 Click Query to query NE users included in various U2000 user groups of the NE.
----End
Prerequisites
l You are an NMS user with Administrators authority.
l The NE user is created.
l The level of the NE user to be deleted is lower than that of the logged-in NE user.
NOTE
Choose Administration > NE Security Management > NE Login Management (traditional style)
from the main menu or select Security Management in Application Center and choose NE
Security > Fix-Network NE > NE Login Management (application style) from the main menu.
You can view the log in information about NE users on the NE Login Management tab.
Procedure
Step 1 Choose Administration > NE Security Management > NE User Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > NE User Management (application style) from the main
menu.
Step 3 In the NE User Management Table, select the NE user to be deleted and click Delete. The
Confirm dialog box is displayed asking you whether to delete the NE user.
----End
Prerequisites
l You are an NMS user with Administrators authority.
l It applies to the MSTP series, WDM series, WDM (NA) series, RTN series and marine
series NEs.
Context
The procedure for configuring a specific NE as an SSH server is as follows.
Procedure
Step 1 Set the communication service mode of the NE.
1. Choose Administration > NE Security Management > NE Communication Services
Management (traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > NE Communication
Services Management (application style) from the main menu.
2. Click the Communication Service Management tab.
3. In the NE list, select the desired NE and click . The query dialog box is displayed,
listing querying results in the right pane.
4. Click Query to query the current communication service mode of the NE.
5. Enable all the communication service modes for the NE.
NOTE
l You can set the NE login mode (Telnet or STelnet) and NE upgrade and backup mode (FTP
client or SFTP client).
l STelnet is recommended because of STelnet protocol higher security than Telnet. SFTP client
is recommended because of SFTP protocol higher security than FTP.
6. Click Apply.
You can determine whether an NE can be configured as an SSH server by querying the SSH server
information on the NE and choose to use the Telnet or STelnet mode to log in to the NE based on actual
requirements.
1. Choose Administration > NE Security Management > NE Communication Services
Management (traditional style) from the main menu or select Security Management in
If the NE functions as the SSH server, among the created NE key pair, the private key is saved on the NE,
and the public key is on the U2000 client. You need to export the public key information from the
U2000 and save the information for follow-up deployment on the SFTP server. In addition, during package
loading or package diffusion upgrade using the NE Software Management (DC), the NE can be
authenticated in SFTP key mode.
1. Choose Administration > NE Security Management > NE Communication Services
Management (traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > NE Communication
Services Management (application style) from the main menu.
2. Click the NE Key Management tab.
3. In the NE list, select the desired NE and click . The query dialog box is displayed,
listing querying results in the right pane.
4. Click Query to query key management information of the NE.
5. Click New Key Pair.
The New Key Pair dialog box is displayed.
6. Set Key Type to S-RSA (NE As the Server) and select Overwrite Mode.
7. Click OK. In the dialog box that is displayed, click Close.
8. Click Export Public Keys. In the Export Public Keys dialog box, set Key Type to S-
RSA, set File Name, and click OK.
9. In the dialog box that is displayed, click Close.
Step 4 Generate a pair of SSH client keys and prepare a public key file.
NOTE
The generated pair of SSH client keys is mainly used for Client Key Management. When accessing an
NE in Stelnet mode, a user requires a pair of SSH client keys to pass the key authentication.
1. A key pair, including a private key and public key, can be generated by using a key generator
PUTTYGEN.EXE.
2. In the Parameters area, set Type of key to generate to SSH-2 RSA and Number of bits
in a generated key to 2048.
NOTE
To ensure security, you must enter a password phrase for generating the key pair files. In addition,
the password phrase must meet U2000 password complexity requirements. For details, see Password
Policy.
3. Click Generate, and then click Save public key and Save private key to save the public
key and the private key respectively after they are generated.
NOTE
To ensure security, you are advised to save the private key file and keep it secure.
4. Copy the public key content to a file, as shown in the following figure. Ensure that all
content in the file is put in one line. The file will be used to import public key information.
This setting can be performed in two ways. One is copying public key information in the public key
set exported in step 4. The other is importing the information into the U2000.
7. Optional: Select the Private Key File. Click the Browse to select the desired directory to
store client private key files, and then set the Passphrase for the client private key.
8. Click OK. In the dialog box that is displayed, click Close.
Public key information generated on the NE is saved to the authorized_keys file in
the .ssh directory for specific NE login users.
The SSH client public keys are usually shared by multiple NEs. SSH client public keys need to be bound
to NE user names that are usually the same. The U2000 provides SSH User Management to bind NE users
with SSH client public keys. By default, SSH users are security NE users.
1. Choose Administration > NE Security Management > NE Communication Services
Management (traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > NE Communication
Services Management (application style) from the main menu.
2. Click the SSH User Management tab.
3. In the NE list, select the desired NE and click . The query dialog box is displayed,
listing querying results in the right pane.
4. Click Query to query user authentication information of the NE.
5. Set Authentication Mode and Client Public Key Name.
6. Click Apply. In the dialog box that is displayed, click Close.
----End
NOTE
This function applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
3.5.1 Overview
Using the User Datagram Protocol (UDP) as the transmission protocol, RADIUS features good
and real-time performance. Owing to the retransmission mechanism and standby server
mechanism, RADIUS possesses high reliability. RADIUS is easy to implement and applies to
the multithreading structure of the server when there are a large number of users.
RADIUS Protocol
AA (Authentication, Authorization) is a technology used for user authentication, authorization,
and accounting. RADIUS is one of the commonly used protocols to implement AA. The
RADIUS protocol is an information exchange protocol used to authenticate remote connections
to the system and prevent unauthorized users from accessing the network.
RFC 2865 is the standard and protocol compliance of the RADIUS protocol.
Authenticator
Attribute
An RADIUS client communicates with the server by using the user datagram protocol (UDP).
Figure 3-21 shows the structure of the RADIUS protocol stack.
RADIUS
IP
PPP Ether
NOTE
The reasons for using the UDP protocol instead of the TCP protocol for communication are as follows:
l The data transmitted between the network access server (NAS, namely, the RADIUS client) and the
RADIUS server is of tens of or even a hundred bits. The RADIUS protocol is required to provide a
retransmission mechanism and standby server mechanism. The RADIUS protocol demands for a
good timer management mechanism. A user can accept the authentication that lasts only tens of
seconds.
l In the case of many users, multiple threads are required on a server. The UDP protocol helps the
server to achieve this by simplifying the procedure.
l The TCP protocol, however, cannot be used to transmit data until a connection is created successfully.
Therefore, the TCP protocol is weak in the real-time performance when many users are involved. In
addition, the TCP protocol cannot meet the timing requirements of the RADIUS.
Implementation Principles
RADIUS adopts a distributed client/server model. Generally, the model is used to manage a
huge number of distributed dial-in users.
Figure 3-22 shows the networking structure of the RADIUS. An NE is set as an RADIUS client
or a proxy server. By managing a simple user database, the RADIUS server implements
authentication and accounting and adjusts the user service information based on the service type
and rights of a user. The RADIUS protocol specifies how the NAS and the RADIUS server
exchange the user information and the accounting information.
l The NAS extracts configuration information of a user, encapsulates the information into a
standard RADIUS packet, and send the packet to the RADIUS server for processing.
l The RADIUS server receives the connection request of the user, authenticates the user
request, and returns to the NAS the configuration information required for delivering
services to the user.
l The NAS and RADIUS exchange authentication information by using a key. The password
of a user is encrypted before being transmitted on the network, which prevents the password
from being intercepted on an insecure network.
l An RADIUS server can be used as a proxy client for other RADIUS servers or as an
authentication server of other types.
U2000 Server
User B
RADIUS
Client
RADIUS
Client
User C
Authentication Process
The password authentication protocol (PAP) is used for transmitting RADIUS packets between
RADIUS clients and RADIUS servers.
Figure 3-23 shows the main process of transmitting RADIUS messages between the server and
the client.
NOTE
l If no response is returned within the retransmission interval, the RADIUS client transmits the
request packet to the RADIUS server repeatedly. The packet retransmission interval and
retransmission times can be set by the user.
l The RADIUS server can be configured with one active server and zero or multiple standby
servers. The RADIUS client can forward the request to the standby or proxy server if the active
server is down or unreachable.
3. If the request is valid, the server completes the authentication and sends the required
authorization information back to the client.
4. Then the RADIUS client returns the authentication response to the user.
Figure 3-23 Process of transmitting messages between the RADIUS server and the client
(1) User name password (2) Request
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE communicates with the U2000 successfully.
Context
l The RADIUS parameters on an NE can be set only after the NE is set as an RADIUS client.
l If an NE is set as a RADIUS client without an RADIUS server, the NE cannot implement
RADIUS authentication.
Procedure
Step 1 Choose Administration > NE Security Management > RADIUS Configuration
Management (traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > RADIUS Configuration
Management (application style) from the main menu.
Step 3 Select the NE and subnet to be queried from the navigation tree on the left. Click to
query the current configuration of the NE RADIUS function from the U2000.
Step 4 Click Query to query the current configuration of the NE RADIUS function from the NE.
Step 5 Double-click RADIUS Client and Proxy Server and set them to Open respectively.
----End
Follow-up Procedure
After an NE is set as a RADIUS client or proxy server, you need to add a RADIUS server.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l An NE is set as an RADIUS client.
Procedure
Step 1 Choose Administration > NE Security Management > RADIUS Configuration
Management (traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > RADIUS Configuration
Management (application style) from the main menu. In the NE RADIUS Configurations
window, click the NE RADIUS Configurations tab.
Step 2 Click RADIUS Server Configuration. The RADIUS Server Information dialog box is
displayed.
Step 3 Click Query to query the current configuration of the RADIUS server from the NE.
Step 4 Click New. The New RADIUS Server Information dialog box is displayed.
l When adding a RADIUS server, identify the RADIUS server uniquely by entering the IP address of the NE.
l When adding a proxy server, identify the proxy server by entering the IP address or the NE name.
l Before adding a proxy server, you need to set the NE as an RADIUS proxy server.
Step 7 Optional: In the RADIUS Server Information dialog box, select the RADIUS server to be
deleted. Then, click Delete. In the Hint box, click OK.
----End
Follow-up Procedure
After the RADIUS server is added, you need to configure the RADIUS parameters on the NE.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l An RADIUS server has been added.
Procedure
Step 1 Choose Administration > NE Security Management > RADIUS Configuration
Management (traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > RADIUS Configuration
Management (application style) from the main menu. In the RADIUS Configuration
Management window, click the NE RADIUS Configurations tab.
Step 2 Select the NE and subnet to be queried from the navigation tree on the left. Click to
query the current configuration of the RADIUS from the U2000.
Step 3 Click Query to query the current configuration of the RADIUS from the NE.
Step 4 Click New. The New NE RADIUS Configuration dialog box is displayed.
NOTE
If the type of the server to be added is Proxy Server, you do not need to set Shared Key.
----End
l Entity changes
The system generates a change history after the change of the device entity is found by
polling or manually refreshing the device.
l Device configuration changes
After the device configuration file is backed up in DC management, you can find the change
of the device configuration file by comparing it with the previous configuration file. A
device configuration change history is generated.
l Software image changes
The change history is generated when the system polls the device and finds the change of
the software image version.
NOTE
The following functions only apply to the Router series, Switch series and Security NEs.
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Administration > NE Security Management > Change Audit (traditional style) from
the main menu or select Security Management in Application Center and choose NE
Security > Change Audit (application style) from the main menu.
Step 3 In the Filter Criteria dialog box, set the querying criteria and click OK.
Step 4 Click a record. The details about the record are displayed in the Details area.
NOTE
l For a record with Change Type being Software Image, the Details tab displays two records. The
upper one shows software version information before change and the lower one shows the latest
software version information after change.
l For a record with Change Type being Entity, the Details tab displays the specific change type, either
Add or Delete.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
The U2000 deletes the records in the database after information about change audit is dumped.
Therefore, you cannot query the dumped records through the U2000 client.
Procedure
Step 1 Choose Administration > NE Security Management > Change Audit (traditional style) from
the main menu or select Security Management in Application Center and choose NE
Security > Change Audit (application style) from the main menu.
Step 2 In the Change Audit window, click Filter, set filter criteria, and click OK.
All records meeting the filter criteria are displayed in the query result area.
Step 3 In the querying result area, select one or more records to be dumped, right-click them and choose
Dump from the shortcut menu.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
The U2000 deletes the records in the database after information about change audit is deleted.
Therefore, you cannot query the deleted records through the U2000 client.
Procedure
Step 1 Choose Administration > NE Security Management > Change Audit (traditional style) from
the main menu or select Security Management in Application Center and choose NE
Security > Change Audit (application style) from the main menu.
Step 2 In the Change Audit window, click Filter, set filter criteria, and click OK.
All records meeting the conditions are displayed in the query result area.
Step 3 In the query result area, select one or more records to be deleted, right-click them and choose
Delete from the shortcut menu.
----End
4 Log Management
The log records the operations and important system events on the U2000. With the log
management function, you can query, collect statistics about, synchronize, forward, and dump
the log information.
syslog operation logs on the U2000 after the logs of the managed NEs are synchronized to the
U2000.
NMS Log
The U2000 records operations performed by all the U2000 users and the operation results.
l U2000 system log: System logs record operations or tasks that the U2000 performs
automatically, such as scheduled and system tasks.
l U2000 operation log: Operation logs record the information about the non-security
operations that the user performs on the U2000, for example, muting and displaying the
alarm sound.
l U2000 security log: Security logs record the security operations that the user performs in
the U2000, for example, login, logout, and unlocking.
By querying logs, the administrator can track and check user operations. Pay close attention to
operation logs. This helps you to learn about the running information of the system. The logs
record of events related to the equipment operations. For example, querying, creating, and
deleting an NE or other objects. The logs also help you to learn user activities. For example, you
can view operations performed by a user in the system.
You can query the preceding three types of logs on a client. In addition, all user activities and
operation instructions on the U2000 management plane are recorded as events to the OS logs
which are stored in the C: \Windows\System32\winevt\Logs\Application.evtx (Windows), /
var/adm/localmessages (Solaris), and /var/log/localmessages (Linux) directories. If the
number of recorded logs reaches the threshold, new logs will overwrite logs recorded earlier.
NE Log
Operations and operation results of all the NE users are recorded in the NE. The U2000 supports
the query of NE logs encapsulated by the syslog protocol of IP and access NEs and the query of
original security logs of transport NEs.
l NE syslog run log: Syslog run logs record running information about managed NEs. You
can view the NE syslog run logs on the U2000, rather than viewing them on each NE. The
U2000 allows users to browse syslog run logs of IP NEs.
l NE syslog operation log: Syslog operation logs record operation information about
managed NEs. You can view the NE syslog operation logs on the U2000, rather than
viewing them on each NE. The U2000 allows users to browse syslog operation logs of
access NEs.
l NE security log: NE security logs record security-based operations that all NE users
perform on an NE. You can view the NE security logs on the U2000, rather than viewing
them on each NE. The U2000 allows users to browse security logs of transport NEs.
Log Dumping
By setting the scheduled task dump, you can enable the U2000 to periodically save the log in a
specified directory. This function facilitates log viewing, reduces records in the database, and
speeds up the running of the system. By default, the dump path of the log is $IMAP_ROOT/
var/ThresholdExport/Log(Solaris/Linux) or %IMAP_ROOT%\var\ThresholdExport
\Log(Windows). The dumped log can be saved as .csv, .xml, .txt or .html files.
Log Forwarding
U2000 log forwarding: The U2000 forwards logs to the syslog server and save them. This
function provides references for maintenance and relieves the storage burden of the U2000
server.
NE log forwarding: The U2000 forwards various types of NE information to the system log
server in a format that complies with the system log protocol. Network management personnel
and network maintenance personnel can learn the NE status according to emergency of the
information. The U2000 can forward logs of only IP and transport NEs. You can configure a
syslog server on an access NE and run commands to forward access NE logs.
Description
The system log records the tasks that are performed on the U2000 server and affect the running
of the U2000. These tasks are triggered on the U2000 client, such as starting and executing
scheduled tasks, or triggered on the U2000 server, such as starting and stopping the U2000
service.
Path
System logs are stored in the database. You can query them through the client. The entry for
querying system logs through the client is Log Management > Query System Logs (application
style) or Administration > Log Management > Query System Logs (traditional style).
You can dump system logs from the database to a file. The entry for dumping system logs is
Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style). In the Task Type navigation tree, choose
Database Capacity Management > System Log Dump. The default dump paths are /opt/oss/
server/var/ThresholdExport/Log (Solaris, SUSE Linux) or D:\oss\server\var
\ThresholdExport\Log (Windows).
After the system logs are dumped, the U2000 generates the associated folder and log file:
l Folder: In the dump path, the U2000 generates a folder named the date of the dump
operation. The format of the name is YYMMDD.
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-system-
log-dateThreshold_info.xml and YYMMDDHHMMSS-system-log-dateThreshold-
number.extension. The file with the suffix _info.xml saves the configuration information
of the dumped logs, and the file with the suffix -number.extension saves the information
about the dumped logs.
NOTE
l System logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be compressed
to a .zip package.
l To avoid insufficient space of the database, you can set the U2000 system log dump to dump the
U2000 system logs periodically or immediately. The dump logs are saved as files and deleted
from the database.
Parameters
Risk Level Levels of risks caused by the operations performed on the U2000:
Warning, Minor, and Risk.
l Successful means that the operation is successful and all results are
returned.
l Failed means that the operation fails.
l Unknown means that an operation result is unknown.
Description
Security logs record the security operations that the user performs in the U2000, for example,
login, logout, and unlocking.
Path
Security logs are stored in the database. You can query them through the client. The entry for
querying security logs through the client is Log Management > Query Security Logs
(application style) or Administration > Log Management > Query Security Logs (traditional
style).
You can also dump security logs from the database to a file. The entry for dumping security logs
is Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style). In the Task Type navigation tree, choose
Database Capacity Management > Security Log Dump. The default dump paths are /opt/oss/
server/var/ThresholdExport/Log (Solaris, SUSE Linux) or D:\oss\server\var
\ThresholdExport\Log (Windows).
After the security logs are dumped, the U2000 generates the associated folder and log file:
l Folder: In the dump path, the U2000 generates a folder named the date of the dump
operation. The format of the name is YYMMDD.
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-
security-log-dateThreshold_info.xml and YYMMDDHHMMSS-security-log-
dateThreshold-number.extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix -
number.extension saves the information about the dumped logs.
NOTE
l System logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be compressed
to a .zip package.
l To avoid insufficient space of the database, you can set the U2000 security log dump to dump
the U2000 security logs periodically or immediately. The dump logs are saved as files and deleted
from the database.
Parameters
Risk Level Levels of risks caused by the operations that are performed on the
U2000: Warning, Minor, and Risk.
l Successful means that the operation is successful and all results are
returned.
l Failed means that the operation fails.
l Partially successful means that the operation is partially successful
and all results are returned.
Description
The operation log records the operations that are performed on the U2000 client but do not affect
the U2000 security, such as creating NEs, creating views, acknowledging alarms, and clearing
alarms.
Path
Operation logs are stored in the database. You can query them through the client. The entry for
querying operation logs through the client is Log Management > Query Operation Logs
(application style) or Administration > Log Management > Query Operation Logs
(traditional style).
You can dump operation logs from the database to a file. The entry for dumping operation logs
is Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style). In the Task Type navigation tree, choose
Database Capacity Management > Operation Log Dump. The default dump paths are /opt/
oss/server/var/ThresholdExport/Log (Solaris, SUSE Linux) or D:\oss\server\var
\ThresholdExport\Log (Windows).
After the operation logs are dumped, the U2000 generates the associated folder and log file:
l Folder: In the dump path, the U2000 generates a folder named the date of the dump
operation. The format of the name is YYMMDD.
l Log file: The following two files are generated in the folder: YYMMDDHHMMSS-
operation-log-dateThreshold_info.xml and YYMMDDHHMMSS-operation-log-
dateThreshold-number.extension. The file with the suffix _info.xml saves the
configuration information of the dumped logs, and the file with the suffix -
number.extension saved the information about the dumped logs.
NOTE
l Operation logs can be dumped to a CSV, XML, TXT, or HTML file, and the file can be
compressed to a .zip package.
l To prevent insufficient space in the database, you can configure the U2000 to dump operation
logs periodically or immediately. Dumped operation logs are saved to files, and the original
operation logs are deleted from the database.
Parameters
Parameter Name Parameter Meaning
Operation Name Name of an operation that the user performs on the U2000.
Risk Level Levels of risks caused by the operations that are performed on the
U2000: Warning, Minor, and Risk.
l Successful means that the operation is successful and all results are
returned.
l Failed means that the operation fails.
l Partially successful means that the operation is partially successful
and all results are returned.
Description
The syslog run logs record running information about IP NEs. By obtaining all syslog run logs
from NEs, you can view the syslog run logs on the U2000, rather than viewing them on each
NE.
Path
Run logs of NEs are saved on NEs. You can query syslog run logs encapsulated by using the
syslog protocol on the U2000 client. The navigation path for querying NE syslog run logs through
the client is choose Administration > NE Security Management > NE Syslog Run Log
(traditional style) from the main menu or select Security Management in Application
Center and choose Log Management > NE Syslog Run Log (application style) from the main
menu.
Parameters
Parameter Description
Module Name Display the module name of creating NE syslog run log.
Description
The syslog operation logs record the operations of access NEs. By obtaining all NE syslog
operation logs from NEs, you can view the NE syslog operation logs managed on the U2000,
rather viewing them on each NE.
Path
Operation logs of NEs are saved on NEs. You can query NE syslog operation logs encapsulated
by using the syslog protocol on the U2000 client. The navigation path for querying NE syslog
operation logs through the client is choose Administration > NE Security Management > NE
Syslog Operation Logs (traditional style) from the main menu or select Security
Management in Application Center and choose Log Management > NE Syslog Operation
Logs (application style) from the main menu.
Parameters
Parameter Description
Definition
Security logs record security-based operations that all NE users perform on an NE. Users can
query the security logs for transport NEs by logging in to the U2000 client rather than querying
them on each NE.
Navigation Path
In the NE Explorer, choose Security > NE Security Log from the Function Tree.
Log Parameters
Parameter Description
Parameter Description
Definition
l The syslog server is a workstation or a server that stores syslogs of the NEs on the live
network.
l Syslog GNE is an NE that receives syslogs from other NEs and transmits them to the syslog
server.
Networking Solution
Considering system log security, a transmission network must be connected to at least two syslog
servers. The NEs and syslog servers usually communicate with each other by an IP protocol.
NEs can use various methods to communicate. For example, the NEs can communicate with
each other by ECC channels.
Case 1
Figure 4-1 shows the networking for the scenario where core NEs use IP protocols to
communicate with each other and different syslog servers are connected to different NEs.
IP IP IP IP
NE1
NE2 NE3
NE4
IP IP
ECC
ECC ECC
NE5
NE6 NE8
NE7
ECC ECC
NE1, NE2, NE3, and NE4 form an IP network. NE5, NE6, NE7, and NE8 form an ECC network.
NE2 and NE3 use IP protocols to communicate with syslog server 1 and syslog server 2
respectively. NE4 communicates with NE5 through the ECC channel.
In this situation, NE1, NE2, NE3, and NE4 use IP protocols to communicate with two different
syslog servers. Set the IP address and port ID for the syslog servers for these NEs. An NE
transmits NE syslogs to the syslog servers using IP protocols. You do not need to set the syslog
GNE.
NE5, NE6, NE7, and NE8 cannot communicate with syslog servers directly. Their syslogs are
transmitted to the syslog GNE through the ECC channel and then transmitted to the syslog
servers. Therefore, you need to set the syslog GNE for these NEs. For example, set NE2 as the
syslog GNE for NE5.
Case 2
Figure 4-2 shows the networking in the scenario where core NEs use IP protocols to
communicate with each other and different syslog servers are connected to the same NE. This
type of networking is similar to that shown in Figure 4-1.
IP IP
IP IP
NE1
NE2 NE3
NE4
IP IP
ECC
ECC ECC
NE5
NE6 NE8
NE7
ECC ECC
In this situation, NE1, NE2, NE3, and NE4 can also use IP protocol to communicate with two
different syslog servers. Therefore, all NE settings are the same as that in Table 4-1.
Case 3
Figure 4-3 shows the networking in the scenario where core NEs use ECC protocols to
communicate with each other and different syslog servers are connected to different NEs.
IP ECC ECC IP
NE1
NE2 NE3
NE4
ECC ECC
ECC
ECC ECC
NE5
NE6 NE8
NE7
ECC ECC
NE1, NE2, NE3, and NE4 form an ECC network. NE5, NE6, NE7, and NE8 form another ECC
network. NE2 and NE3 use IP protocols to communicate with syslog server 1 and syslog server
2 respectively. NE4 communicates with NE5 through the ECC channel.
In this situation, NE2 can only communicate with syslog server 1 directly. NE2 cannot
communicate with syslog server 2 directly. Therefore, you must set the IP address and port ID
for syslog server 1 for NE2 and the syslog GNE which can transmit syslogs to syslog server 2.
Consequently, NE2 uses IP protocols to transmit the syslogs to syslog server 1 and uses the
syslog GNE to transmit system logs to syslog server 2. The setting of NE3 is similar to that of
NE2. Set the IP address and port ID for syslog server 2 and the syslog GNE which can transmit
syslogs to syslog server 1.
All other NEs cannot communicate with two syslog servers directly. Their syslogs are
transmitted to the syslog GNE through the ECC channel. Then, the syslog GNE transmits the
syslogs to the syslog servers. Therefore, you only need to set the syslog GNE for these GNEs.
For example, NE2 and NE3 may be the syslog GNEs for NE5. For details about the
configurations, see Table 4-2.
Context
Statistical results are generated based on the existing data in the database. If the database is
empty, no statistical result is displayed.
Procedure
Step 1 Choose Log Management > Query System Logs (application style) or Administration > Log
Management > Query System Logs (traditional style) from the main menu.
Step 2 In the Filter dialog box, set filter criteria, and click OK.
NOTE
You can also click Cancel in the Filter dialog box, and query logs in the Query System Logs window in
the following ways:
l Click Template Filter, and select Open. Select a template from the template list, and click Open to
use an existing template to query logs. If no template exists on the U2000, see 4.5 Setting U2000 Log
Templates to create a template.
l Click Filter. Set the search criteria in the Filter dialog box, and click OK to query logs.
Step 3 In the Query System Logs window, double-click a record to view the log details.
l Click a field in the header of the query result table to sort the query results by field.
l A white upward triangular icon indicates that you can sort the results by field. A black
upward triangular icon indicates that the results are sorted in the ascending order by
field. The black downward triangular icon indicates that the results are sorted in the
descending order by field.
----End
Context
Statistical results are generated based on the existing data in the database. If the database is
empty, there is no statistical result.
Procedure
Step 1 Choose Log Management > System Log Statistics (application style) or Administration >
Log Management > System Log Statistics (traditional style) from the main menu.
Step 2 In the Filter window, set the statistics settings and filter criteria, and click OK.
NOTE
You can also click Cancel, and collect statistics in the System Log Statistics window in the following
ways:
l Click Template, and select Open. Select a template from the template list, and click Open to use an
existing template to collect statistics on system logs. If no template exists on the U2000, see 4.5 Setting
U2000 Log Templates to create a template.
l Click Filter. Set Statistics Settings and Filter Criteria in the Filter window, and click OK to collect
statistics on system logs.
----End
Result
In the System Log Statistics window, the statistical result is displayed.
The display mode of statistical results varies according to the settings on the Statistics
Settings tab page in the Filter dialog box. The display mode of statistical results varies according
to the settings on the Statistics Settings tab page. Table 4-3 describes the settings and display
mode of the Statistics Settings tab page.
Table 4-3 Settings and display mode of the Statistics Settings tab page
Item 1 Item
Context
l Users in the SMManagers group can query security logs of all users.
l Users who have the Query All Security Logs permission can query security logs of all
users.
l Statistical results are generated based on the existing data in the database. If the database
is empty, no statistical result is displayed.
l If a value in the Operation User column in the log query results is an unauthorized user,
the system may have been attacked.
Procedure
Step 1 Choose Log Management > Query Security Logs (application style) or Administration >
Log Management > Query Security Logs (traditional style) from the main menu.
Step 2 In the Filter dialog box, set filter criteria, and click OK.
NOTE
l You can also click Cancel in the Filter dialog box, and query logs in the Query Security Logs window
in the following ways:
l Click Template Filter, and select Open. Select a template from the template list, and then click
Open to use an existing template to query logs.
If no template exists on the U2000, see 4.5 Setting U2000 Log Templates to create a template.
l Click Filter. Set search criteria in the Filter dialog box, and click OK to query logs.
l In the Filter dialog box, click Choose in Security Event, and view the operations that can be monitored
in the Select Security Event dialog box. Click Choose in Operation Object, and view the operation
objects that can be monitored in the Select Operation Object dialog box.
Step 3 In the Query Security Logs window, double-click a record to view the log details.
l Click a field in the header of the query result table to sort the query results by field.
l A white upward triangular icon indicates that you can sort the results by field. A black
upward triangular icon indicates that the results are sorted in the ascending order by
field. The black downward triangular icon indicates that the results are sorted in the
descending order by field.
----End
Context
l Users in the SMManagers or Administrators group, or users who have the Query All
Security Logs permission can collect statistics on security logs of all users.
l Statistical results are generated based on the existing data in the database. If the database
is empty, there is no statistical result.
Procedure
Step 1 Choose Log Management > Security Log Statistics (application style) or Administration >
Log Management > Security Log Statistics (traditional style) from the main menu.
Step 2 In the Filter window, set the statistics settings and filter criteria, and click OK.
NOTE
You can also click Cancel, and collect statistics in the Security Log Statistics window in the following
ways:
l Click Template, and select Open. Select a template from the template list, and click Open to use an
existing template to collect statistics on security logs. If no template exists on the U2000, see 4.5 Setting
U2000 Log Templates to create a template.
l Click Filter. Set Statistics Settings and Filter Criteria in the Filter window, and click OK to collect
statistics on security logs.
----End
Result
In the Security Log Statistics window, the statistical result is displayed.
The display mode of statistical results varies according to the settings on the Statistics
Settings tab page in the Filter dialog box. The display mode of statistical results varies according
to the settings on the Statistics Settings tab page. Table 4-4 describes the settings and display
mode of the Statistics Settings tab page.
Table 4-4 Settings and display mode of the Statistics Settings tab page
Do not set it to Do not set it to Set it to (Count). The statistical result is displayed
(None). (None). as follows:
l The statistical result is
displayed in a collapsed tree
with Item 1 as the level-1
node and Item 2 as the level-2
node.
l The statistical result is
achieved based on the items
selected in Row.
Do not set it to Set it to (None). Set it to (Count). The statistical result is displayed
(None). as follows:
l The statistical result is
Set it to (None). Do not set it to Set it to (Count).
displayed by Item 1 or Item
(None).
2.
l The statistical result is
achieved based on the item
selected in Row.
Do not set it to Do not set it to Do not set it to The statistical result is displayed
(None). (None). (Count). as follows:
l The statistical result is
displayed in a collapsed tree
with Item 1 as the level-1
node and Item 2 as the level-2
node.
l The statistical result is
achieved based on the
combination of the items
selected in Row and the item
selected in Column.
Do not set it to Set it to (None). Do not set it to The statistical result is displayed
(None). (Count). as follows:
l The statistical result is
Set it to (None). Do not set it to Do not set it to
displayed by Item 1 or Item
(None). (Count).
2.
l The statistical result is
achieved based on the
combination of the item
selected in Row and that
selected in Column.
Context
l When you query operation logs by user name, only names of the users that have performed
operations are displayed under Available Operation User in the Select Operation User
dialog box.
l Operation log query scopes vary according to the user.
– Users in the Administrators group can query operation logs of all users.
– Users in the SMManagers group who have the Query Operation Logs permission can
query operation logs of all users.
– Common users who do not belong to the Administrators or SMManagers group and
who have the Query Operation Logs permission can query only their own operation
logs.
l Statistical results are generated based on the existing data in the database. If the database
is empty, no statistical result is displayed.
l If a value in the Operation User column in the log query results is an unauthorized user,
the system may have been attacked.
Procedure
Step 1 Choose Log Management > Query Operation Logs (application style) or Administration >
Log Management > Query Operation Logs (traditional style) from the main menu.
Step 2 In the Filter dialog box, set filter criteria, and click OK.
NOTE
l You can also click Cancel in the Filter dialog box, and query logs in the Query Operation Logs
window in the following ways:
l Click Template Filter, and then select Open. Select a template from the template list, and click
Open to use an existing template to query logs. If no template exists on the U2000, see 4.5 Setting
U2000 Log Templates to create a template.
l Click Filter. Set search criteria in the Filter dialog box, and click OK to query logs.
l In the Filter dialog box, click Choose in Operation Name, and view the operations that can be
monitored in the Select Operation Name dialog box. The Log out the server operation is not
monitored. Click Choose in Operation Object, and view the operation objects that can be monitored
in the Select Operation Object dialog box.
Step 3 In the Query Operation Logs window, double-click a record to view the log details.
l Click a field in the header of the query result table to sort the query results by field.
l A white upward triangular icon indicates that you can sort the results by field. A black
upward triangular icon indicates that the results are sorted in the ascending order by
field. The black downward triangular icon indicates that the results are sorted in the
descending order by field.
----End
Context
Statistical results are generated based on the existing data in the database. If the database is
empty, there is no statistical result.
Procedure
Step 1 Choose Log Management > Operation Log Statistics (application style) or Administration
> Log Management > Operation Log Statistics (traditional style) from the main menu.
Step 2 In the Filter window, set the statistics settings and filter criteria, and click OK.
NOTE
You can also click Cancel, and collect statistics in the Operation Log Statistics window in the following
ways:
l Click Template, and select Open. Select a template from the template list, and click Open to use an
existing template to collect statistics on operation logs. If no template exists on the U2000, see 4.5
Setting U2000 Log Templates to create a template.
l Click Filter. Set Statistics Settings and Filter Criteria in the Filter window, and click OK to collect
statistics on operation logs.
----End
Result
In the Operation Log Statistics window, the statistical result is displayed.
The display mode of statistical results varies according to the settings on the Statistics
Settings tab page in the Filter dialog box. The display mode of statistical results varies according
to the settings on the Statistics Settings tab page. Table 4-5 describes the settings and display
mode of the Statistics Settings tab page.
Table 4-5 Settings and display mode of the Statistics Settings tab page
Do not set it to Do not set it to Set it to (Count). The statistical result is displayed
(None). (None). as follows:
l The statistical result is
displayed in a collapsed tree
with Item 1 as the level-1
node and Item 2 as the level-2
node.
l The statistical result is
achieved based on the items
selected in Row.
Do not set it to Set it to (None). Set it to (Count). The statistical result is displayed
(None). as follows:
l The statistical result is
Set it to (None). Do not set it to Set it to (Count).
displayed by Item 1 or Item
(None).
2.
l The statistical result is
achieved based on the item
selected in Row.
Do not set it to Do not set it to Do not set it to The statistical result is displayed
(None). (None). (Count). as follows:
l The statistical result is
displayed in a collapsed tree
with Item 1 as the level-1
node and Item 2 as the level-2
node.
l The statistical result is
achieved based on the
combination of the items
selected in Row and the item
selected in Column.
Do not set it to Set it to (None). Do not set it to The statistical result is displayed
(None). (Count). as follows:
l The statistical result is
Set it to (None). Do not set it to Do not set it to
displayed by Item 1 or Item
(None). (Count).
2.
l The statistical result is
achieved based on the
combination of the item
selected in Row and that
selected in Column.
Context
l Choose Log Management > Query Operation Logs (application style) or
Administration > Log Management > Query Operation Logs (traditional style), Log
Management > Query System Logs (application style) or Administration > Log
Management > Query System Logs (traditional style), Log Management > Query
Security Logs (application style) or Administration > Log Management > Query
Security Logs (traditional style), Log Management > Operation Log Statistics
(application style) or Administration > Log Management > Operation Log Statistics
(traditional style), Log Management > System Log Statistics (application style) or
Administration > Log Management > System Log Statistics (traditional style), Log
Management > Security Log Statistics (application style) or Administration > Log
Management > Security Log Statistics (traditional style) from the main menu. Click
Template Filter to set the template.
l The operations for setting the log query and statistic collection templates are similar. The
following is an example of setting the log query template.
Procedure
Step 1 Choose Log Management > Query Operation Logs (application style) or Administration >
Log Management > Query Operation Logs (traditional style) from the main menu.
Step 3 You can perform the following operations in the Query Operation Logs window.
Modify a template If there is already a log query template or a log statistics template on
the U2000, you can do as follows to modify the template:
1. Choose Template Filter > Open. Select a template in the Open
dialog box, and click Open.
2. In the Query Operation Logs window, click Filter.
3. In the Filter dialog box, modify the query conditions in the log
template, and click OK.
4. In the Query Operation Logs window, choose Template Filter >
Save.
Save As You can do as follows to save and modify a log query or statistics
template:
Delete a template If there is already a log query template or a log statistics template on
the U2000, you can do as follows to delete the template:
----End
Context
NOTE
By default, scheduled log dump, overflow log dump, and log export impose the following restrictions on
the files generated in the specified directories:
l The total size of the files is equal to or smaller than 1024 MB.
l The files are saved for 15 days at most.
l The quantity of the files is equal to or fewer than 1000.
If any one of these restriction is violated, the U2000 will delete the earliest files to eliminate the violation.
These parameters can be modified as required.
Context
Each of the types Operation Log Dump, Security Log Dump and System Log Dump has a
default system task that is provided by the U2000. You are not allowed to delete the system task,
but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Type navigation tree, expand the Database Capacity Management node, choose
Operation Log Dump, Security Log Dump or System Log Dump.
Step 3 In the Task Management window, double-click the task in the task list.
Step 4 In the displayed Attribute dialog box, set the parameters on the Common Parameters and
Extended Parameters tabs.
The time displayed in the U2000 log record is the start time of an operation. If the start time of the operation
is within the time range for dumping logs, but the operation is not complete when the time for dumping
logs is reached, this log record is not dumped to the log file.
----End
Result
You can view the U2000 log file in File path on the Extended Parameters tab page.
Context
Each of the types Operation Log Overflow Dump, Security Log Overflow Dump and System
Log Overflow Dump has a default system task that is provided by the U2000. You are not
allowed to delete the system task, but you can modify its setting. In addition, you cannot create
new tasks of these three types.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Type navigation tree, choose Overflow Dump > Operation Log Overflow
Dump, Overflow Dump > Security Log Overflow Dump or Overflow Dump > System Log
Overflow Dump. Select the type of the log overflow dump task, and then double-click the
selected log dump task in the right area.
Step 4 In the Attribute dialog box, modify the parameters on the Common Parameters and Extended
Parameters tabs.
NOTE
Set parameters as required. The U2000 log database saves 100,000 logs. An alarm is reported if the log
quantity reaches the preset threshold (80% by default). When the log quantity reaches 100,000, overflow
dump is triggered and 30% of these logs are dumped.
NOTE
The time displayed in the U2000 log record is the start time of an operation. If the start time of the operation
is within the time range for dumping logs, but the operation is not complete when the time for dumping
logs is reached, this log record is not dumped to the log file.
----End
Result
You can view the U2000 log file in File path on the Extended Parameters tab page.
Context
Each of the types Operation Log Manual Dump, Security Log Manual Dump and System
Log Manual Dump has a default system task that is provided by the U2000. You are not allowed
to delete the system task, but you can modify its setting. In addition, you cannot create new tasks
of these three types.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the navigation tree on the left of the Task Management window, choose Manual Dump >
Operation Log Manual Dump, Manual Dump > Security Log Manual Dump or Manual
Dump > System Log Manual Dump.
Step 3 In the Task Management window, right-click manual dump task and choose Run.
The time displayed in the U2000 log record is the start time of an operation. If the start time of the operation
is within the time range for dumping logs, but the operation is not complete when the time for dumping
logs is reached, this log record is not dumped to the log file.
----End
Context
Each of the types Operation Log Export, Security Log Export and System Log Export has
a default system task that is provided by the U2000. You are not allowed to delete the system
task, but you can modify its setting. In addition, you cannot create new tasks of these three types.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Type navigation tree, choose File Interface > Operation Log Export,File
Interface > Security Log Export or File Interface > System Log Export.
Step 3 Double-click the task in the Task Management window.
Step 4 In the displayed Attribute dialog box, set the parameters on the Common Parameters and
Extended Parameters tabs.
Step 5 Click OK.
NOTE
The time displayed in the U2000 log record is the start time of an operation. If the start time of the operation
is within the time range for exporting logs, but the operation is not complete when the time for exporting
logs is reached, this log record is not exported to the log file.
----End
Result
You can view the U2000 log file in File path on the Extended Parameters tab page.
Context
There is only one default system task of the Device Log Dump type, which is provided by the
U2000. You are not allowed to delete this system task, but you can modify its setting. In addition,
you cannot create new task of this type.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Type navigation tree, expand the Database Capacity Management node, choose
Device Log Dump.
Step 3 In the Task Management window, double-click the log dump task in the task list.
Step 4 In the displayed Attribute dialog box, set the parameters on the Common Parameters and
Extended Parameters tabs.
Step 5 Click OK.
NOTE
The time displayed in the U2000 log record is the start time of an operation. If the start time of the operation
is within the time range for dumping logs, but the operation is not complete when the time for dumping
logs is reached, this log record is not dumped to the log file.
----End
Result
You can view the device log file in File path on the Extended Parameters tab page.
The U2000 log forwarding service reads logs from the U2000 Syslog database, converts the logs
into Syslog packets and sends them to the third-party Syslog server. During this process, the
BSD Syslog protocol defined by RFC3164 UDP, RFC3195 TCP and RFC5424 TLS is used.
The logs of the U2000 Syslog database are written by service modules such as fault, topology,
and security modules.
Figure 4-4 shows the position of the log forwarding service in the entire log forwarding system.
Topo Service
DB Syslog Forwarding agent Syslog Server
Security Service
... ...
The following two conditions must be satisfied to achieve the log forwarding function:
l There are logs in the Syslog database.
l The U2000 communicates with the third-party Syslog server properly.
The function of writing logs in to the Syslog database must be enabled on the U2000 server, and
this function is controlled by the administrator. The interconnection between the U2000 and the
third-party Syslog server is configured on the U2000 client.
Context
After this function is enabled, the U2000 logs are written to the Syslog database.
Procedure
Step 1 Log in to the U2000 server.
l Solaris/SUSE Linux:
Run the vi command to open the $IMAP_ROOT/etc/conf/IMAP_logsvc.xml file.
vi $IMAP_ROOT/etc/conf/IMAP_logsvc.xml
l Linux:
Open the %IMAP_ROOT%\etc\conf\IMAP_logsvc.xml file using tools such as UltraEdit
or Notepad.
Step 3 Set syslogReportFlag of the log to 1. The function of writing the logs into the Syslog database
is enabled.
The following is an example of writing the system logs, operation logs, and security logs of the
U2000 into the Syslog database.
<syslog name="syslogReport">
<logType name="41">
<!-- Report switch: 0 - Off; 1 - On. This swtich is for system logs. The
switch is turned off by default.-->
<param name="syslogReportFlag">1</param>
<!-- Report level control: Only the logs at the same level or a higher level
are reported. The default value is 2 (Risk). -->
<!-- Log level are 0:warning, 1:minor, 2:risk -->
<param name="syslogReportLevel">2</param>
</logType>
<logType name="42">
<!-- Report switch: 0 - Off; 1 - On. This swtich is for operation logs. The
switch is turned off by default. -->
<param name="syslogReportFlag">1</param>
</logType>
<logType name="43">
<!-- Report switch: 0 - Off; 1 - On. This swtich is for security logs. The
switch is turned off by default. -->
<param name="syslogReportFlag">1</param>
<!-- Report level control: Only the logs at the same level or a higher level
are reported. The default value is 1 (Minor). -->
<!-- Log level are 0:warning, 1:minor, 2:risk -->
<param name="syslogReportLevel">1</param>
</logType>
</syslog>
NOTE
Log level selection is not provided for operation logs (42) because operation logs at all levels are reported.
Step 4 After the modification is complete, save the file. In the Solaris/SUSE Linux OS, exit from the
VSI editor after the file is saved.
NOTE
l When log service is restarted, all the dependent services will also be restarted.
l View other services that depend on the log service. For details, see Monitoring the U2000 Processes.
----End
4.6.6.3 Setting the Interconnection Between the U2000 and the Syslog Server
The U2000 can forward logs from the Syslog database to a third-party Syslog server only if the
U2000 communicates with the third-party Syslog server properly; therefore, you need to
configure the information about the Syslog server on the U2000 client.
Prerequisites
Contact the administrator to ensure that the function of writing the logs from the U2000 server
to the database is enabled.
Context
The log forwarding server forwards only security logs, operation logs, and system logs.
Procedure
Step 1 Choose Settings > Log Forwarding Servers (application style) or Administration >
Settings > Log Forwarding Servers (traditional style) from the main menu.
Step 2 You can perform the following operations in the Log Forwarding Servers window.
Add Click Add. In the Create Log Forwarding Server dialog box, set the
server that receives the logs. See Log Forwarding Servers.
NOTE
l To enable the log forwarding function, select Yes from the Enable drop-down
list.
l The IP address cannot be set to a loopback address.
l String Filter does not support wildcards.
l If the value of Protocol is TCP or TLS, the log forwarding service tries to
connect to the master server first. If the log forwarding service fails to connect
to the master server, it tries to connect to the standby server. When the primary
server recovers, it takes over the service back from the standby server. If the
value of Protocol is UDP, log forwarding service sends the Syslog records only
to master server.
l If Protocol is set to UDP, the U2000 cannot determine whether the IP addresses
and ports on the remote Syslog server are valid, because the UDP cannot ensure
transmission reliability. Therefore, State in the Log Forwarding Servers
dialog box indicates whether the U2000 log forwarding server can successfully
send logs in Syslog packet mode, but not indicates that these packets can be
successfully received by the Syslog server.
l The Transport Layer Security (TLS) protocol secures data transfer through data
encryption. If Protocol is set to TLS, the U2000 log forwarding server encrypts
and sends logs to the Syslog server.
l You can set a maximum of five servers to receive logs.
Modify Select a server record, and click Modify. In the displayed Modify Log
Forwarding Server dialog box, set the server information included in
logs.
Refresh After another user updates the information about the log forwarding
server, you can click Refresh to obtain the updated information.
----End
4.6.6.4 Managing the Connection Between the U2000 and Syslog Server
If the U2000 connects to the Syslog server abnormally, alarms are generated and are sent to the
U2000 client. You need to clear the alarms in a timely manner to ensure normal communication
between the U2000 and the Syslog server.
Context
When TCP or TLS mode is configured for a Syslog server, there are three situations:
1. If the U2000 successfully connects to the master Syslog server, it forwards the logs to only
this Syslog server.
2. If the U2000 fails to connect to the master Syslog server, it tries to connect to the standby
Syslog server. If the connection is successful, it forwards the logs to only this Syslog server.
3. If U2000 fails to connect to any of the master and standby Syslog server, the log forwarding
is unavailable for the Syslog server.
Log forwarding service raises the following two alarms to the fault module when the connection
status are not proper:
l ALM-119 Alarm of the Switchover to the Standby Syslog Server: When the log
forwarding service fails to connect to the master Syslog server and tries to connect to the
standby Syslog server, this alarm will be reported.
l ALM-118 Alarm of the Failure to Connect the Master and Standby Syslog Servers:
When log forwarding service fails to connect to any of the master and standby Syslog server,
this alarm will be reported.
To ensure proper communication between the U2000 and Syslog server, you must clear the
alarm in time.
Procedure
l Clear the ALM-119 Alarm of the Switchover to the Standby Syslog Server by following
the procedure provided in ALM-119 Alarm of the Switchover to the Standby Syslog
Server.
l Clear the ALM-118 Alarm of the Failure to Connect the Master and Standby Syslog
Servers by following the procedure provided in ALM-118 Alarm of the Failure to Connect
the Master and Standby Syslog Servers.
----End
NOTE
NOTICE
On Solaris, the function of receiving remote logs for the syslog service is enabled by default,
and port UDP 514 is occupied. The U2000 SyslogCollectorDM service also uses port UDP 514
to receive remote logs, therefore, the port for the two services conflicts. Therefore, the syslog
service function for receiving remote logs must be disabled, you can use the following method
to do it:
1. Log in to the U2000 server as user root.
2. Run the following command to set environment variables.
# . /opt/oss/server/svc_profile.sh
5. Disable the syslog service function for receiving remote logs on the OS.
1. Run the following command to stop the syslog service on the OS:
# svcadm disable system-log
Context
l After the information center is enabled, the classification and output of information
(especially much information for processing) may affect the system performance to some
extent.
l By default, the information center is enabled. You can run the display info-center
command to view the information center status.
A message similar to the following is displayed, indicating the information center is
enabled.
Information Center:enabled
If this information is not displayed, perform the following steps to enable the information
center.
Procedure
Step 1 Telnet or STelnet to an NE. Run the system-view command to enter the system view.
NOTE
Using STelnet (if supported) to log in to the device is recommended. STelnet is more secure.
Step 2 Run the info-center enable command to enable the information center.
----End
Prerequisites
l The selected NE supports the log service function on the U2000.
l The NE is configured with Telnet/STelnet parameters and its configurations are
synchronized to the U2000.
l The syslog source interface and its IP address are known.
Procedure
Step 1 In the topology navigation tree or the topology view, select the NE to be operated and right-click
it. Then select NE Explorer on the shortcut menu.
Step 2 In the Service Tree, choose System Management > NE Channel Management > Syslog
Service.
Step 3 Click Enable or Disable to change the service status of the syslog source interface.
NOTE
If the syslog source of the host is in use, you cannot select the syslog source interface from the drop-down
list. The status button is Disable. Click Disable to disable the log source. Then you can select the syslog
source interface from the drop-down list. The status button changes to Enable.
Step 4 When the syslog source is disabled, select the source interface for sending syslog files and click
Enable.
----End
Prerequisites
The IP address of the log host is known.
Context
To view NE logs on the U2000, set Log Host IP Address to U2000 Server IP Address to set
the U2000 server as the NE syslog receiver.
NOTE
The system supports the configuration of a maximum of eight log hosts to realize backup among log hosts.
Procedure
Step 1 In the Main Topology, right-click an NE and choose NE Explorer from the shortcut menu.
Step 2 In the Service Tree, choose NE Channel Management > Syslog Service from the navigation
tree.
Step 3 On the Syslog Service tab, right-click in a blank area and choose Create from the shortcut menu.
Step 4 In the Create Log Host dialog box, set the parameters.
NOTE
l If the U2000 manages NEs in inband VPN networking mode, the VRF name must be specified.
l If the U2000 is a high availability system, the IP addresses of both the primary and secondary sites
must be added to the Log Host IP Address list.
If more than one log host is added, the Create Log Host progress bar is displayed.
After all log hosts are added, click OK.
----End
Procedure
Step 1 In the topology navigation tree or the topology view, select the NE to be operated and right-click
it. Then select NE Explorer on the shortcut menu.
Step 2 In the Service Tree, choose System Management > NE Channel Management > Syslog
Service.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l An information center on the NE side is configured so that the NE syslog run logs can be
sent to the U2000. For details about how to configure an information center on the NE side,
see 4.7.1 Configuring the Information Center on the NEs.
l You have configured the U2000 server as the receiver of NE logs and set Log Host IP
Address to that of the U2000 server. For details, see 4.7.1.3 Adding a Syslog Host.
Context
Only user admin can query the NE syslog run logs of all NEs.
Procedure
Step 1 Choose Administration > NE Security Management > NE Syslog Run Log (traditional style)
from the main menu or select Security Management in Application Center and choose Log
Management > NE Syslog Run Log (application style) from the main menu.
Step 2 In the DRL File List navigation tree, double-click an NE syslog run log file, such as
20120601061544. In the right pane, click a record to view log details.
NOTE
l The files in the device run log (DRL) file list are listed by time.
l You can enter the file name in the text box above the DRL File List navigation tree to filter the DRL
files. Only numbers from 0 to 9 are allowed. Then, the matched files are displayed in the DRL File
List navigation tree.
----End
NOTE
This operation is applies to the management of syslog operation log for access NEs.
Prerequisites
You are an NMS user with Guests authority or higher.
NOTICE
On Solaris, the function of receiving remote logs for the syslog service is enabled by default,
and port UDP 514 is occupied. The U2000 SyslogCollectorDM service also uses port UDP 514
to receive remote logs, therefore, the port for the two services conflicts. Therefore, the syslog
service function for receiving remote logs must be disabled, you can use the following method
to do it:
1. Log in to the U2000 server as user root.
2. Run the following command to set environment variables.
# . /opt/oss/server/svc_profile.sh
5. Disable the syslog service function for receiving remote logs on the OS.
1. Run the following command to stop the syslog service on the OS:
# svcadm disable system-log
Context
l This feature allows users to browse syslog operation logs of all access NEs.
l Common users can query only the logs of the NEs of their own management domains.
l User admin can query NE logs of all users.
Procedure
Step 1 Log in to the System Monitor client, and check whether SyslogCollectorDM is started. If not,
select the process, right-click, and choose Start Process from the shortcut menu.
Step 2 STelnet to the device whose log needs to be viewed, and switch to the privilege mode. Run the
loghost add ip-addr hostname command to add a syslog server.
NOTE
The ip-addr indicates the IP address of the U2000 server, and the hostname parameter indicates the name
of the U2000 server.
Step 3 Run the loghost activate name hostname command to activate the Syslog server.
NOTE
Step 4 Run the display loghost list command. If the returned message includes the IP address and name
of the added syslog server, and Terminal state is Normal, the syslog server is configured
successfully.
Step 7 Choose Administration > NE Security Management > NE Syslog Operation Logs
(traditional style) from the main menu or select Security Management in Application
Center and choose Log Management > NE Syslog Operation Logs (application style) from
the main menu.
Step 8 In the NE Syslog Operation Logs window, double-click a record to view the log details.
l Click a field in the header of the query result table to sort the query results by field.
l A white upward triangular icon indicates that you can sort the results by field. A black
upward triangular icon indicates that the results are sorted in the ascending order by
field. The black downward triangular icon indicates that the results are sorted in the
descending order by field.
l Click the Device Name, or Access Method field. Different from other table header fields,
these fields are displayed in groups. Therefore, they are not sorted in alphabetic order.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Administration > NE Security Management > LCT User Management (traditional
style) from the main menu or select Security Management in Application Center and choose
NE Security > Fix-Network NE > LCT User Management (application style) from the main
menu.
Step 2 On the User Logs tab select the desired device type from the Device Type drop-down list.
Step 3 Click Filter and set the parameters to display the required NE user logs.
Step 4 Select a log record in the user log list and view the details of the log in the lower pane.
----End
Prerequisites
l This operation applies to MSTP, WDM and RTN series NEs.
l NOTICE
On Solaris, the function of receiving remote logs for the syslog service is enabled by default,
and port UDP 514 is occupied. The U2000 SyslogCollectorDM service also uses port UDP
514 to receive remote logs, therefore, the port for the two services conflicts. Therefore, the
syslog service function for receiving remote logs must be disabled, you can use the
following method to do it:
1. Log in to the U2000 server as user root.
2. Run the following command to set environment variables.
# . /opt/oss/server/svc_profile.sh
5. Disable the syslog service function for receiving remote logs on the OS.
1. Run the following command to stop the syslog service on the OS:
# svcadm disable system-log
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE must be able to directly communicate with the syslog server.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Log Forwarding from the Function
Tree.
Step 2 Click the Syslog Server tab. The syslog server list is displayed.
Step 3 Click Query to load configurations of the syslog server from the NE.
Step 4 Click New. The Add Syslog Server dialog box is displayed.
Step 5 Set IP Address, Send Mode, and Port according to actual networking.
Step 6 Click OK. A message will be displayed indicating that the operation is successful.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Log Forwarding from the Function
Tree.
Step 2 Click the Syslog GNE tab. The syslog GNE list is displayed.
Step 3 Click Query to load the syslog GNE configurations from the NE.
Step 6 Click OK. A message will be displayed indicating that the operation is successful.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Log Forwarding form the Function
Tree.
Step 2 On the Basic Info tab, click Query to load the configurations from the NE.
Step 4 In the Add Basic Info dialog box, set Log Type and Log Severity based on network
requirements.
Step 5 Click OK. A message will be displayed indicating that the operation is successful.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 In the NE Explorer, select an NE and choose Security > NE Log Forwarding from the Function
Tree.
Step 2 On the Basic Info tab, click Query to load configurations from the NE.
Step 3 Select the Start the log forwarding service check box.
Step 4 Click Apply to deploy the latest configurations. A message will be displayed indicating that the
operation is successful.
----End
Prerequisites
l This function applies to the MSTP series, WDM series, RTN series, PTN series and marine
series NEs.
l You are an NMS user with Maintenance Group authority or higher.
Context
l NE security logs are saved in the U2000 database by default. You can view information
about NE security on the U2000.
l NE logs are forwarded to the syslog server only and are not saved in the U2000 database.
You can view NE logs on the syslog server only.
Procedure
Step 1 In the NE Explorer, choose Security > NE Security Log from the Function Tree.
Query Operation
Query on Select the Query from the NE check box and click Query.
NEs NOTE
It takes a long time for you to query security logs on NEs.
You can filter the query results to view the desired information.
After the query is complete, information about the NE security-related operations is displayed
in the lower pane of the Browse NE Logs window.
Step 3 Click Save As to save NE security information.
----End
Prerequisites
l Apply to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series and
marine series NEs.
l You are an NMS user with Guests authority or higher.
Context
NOTE
Operation logs are recorded for all operations except queries.
l Choose Administration > Log Management > Query Operation Logs (traditional style)
from the main menu or select Security Management in Application Center and choose
Log Management > Query Operation Logs (application style) from the main menu. The
queried logs display only operations by the current U2000. Alternatively, in the NE
Explorer, you can choose Security > NE Operation Log from the function tree. Then, logs
are displayed indicating operations performed by all U2000 clients connecting to the NE.
l NE operation logs are forwarded to the syslog server, you can view information about NE
operation security on the syslog server.
Procedure
Step 1 In the NE Explorer, choose Security > NE Operation Log from the Function Tree.
Step 2 In the Log Query Criteria area, specify the time range for the queried NE operation logs.
Step 4 Optional: Click Filter. In the dialog box that is displayed, specify the filter criteria to view the
desired information.
----End
Follow-up Procedure
Current users can query the operation information on specific U2000 clients by viewing User
Name and NMS IP Address displayed in the window.
5 Topology Management
Topology management is basic network O&M functions that the U2000 provides. By using the
topology management functions, network maintenance personnel can construct and manage the
topology structure of a network and monitor the status of the entire network in real time.
Specifically, after associating NEs in a real network with visualized operation objects in the
topology, maintenance personnel can learn networking of the NEs and NE status based on colors
of NE icons, alarm status of NEs, connection status between NEs in the topology view. By using
the topology management functions, maintenance personnel can manage NEs conveniently.
create NEs: creating NEs one by one and creating NEs in batches. When a large number of NEs
need to be created, for example, during deployment, it is recommended that you create NEs in
batches. When you need to create just a few NEs, it is recommended that you create the NEs
one by one.
Overview
Subnet
l Navigation Tree: In this area, all NEs managed by the U2000 are displayed. Using this tree,
you can locate the required NE quickly.
l Topology view:
– The U2000 topology view displays physical and logical objects on the network to reflect
the network architecture, and provides navigation paths for different operations.
– You can set gif pictures, jpg pictures, or the maps provided by the U2000 as the
background of the Main Topology.
– Right-click in a blank area of the topology view and choose Save Picture from the
shortcut menu to save the topology view as a picture.
– For users with permissions at the level of Operator Group or higher, if the topology
locations are stored on different clients connected to the same server, a user can click
– Collects NE statistics in the Main Topology to learn the types and quantity of NEs being
managed in the view.
– Filters topology objects by object types.
l Managing topology objects:
– Monitors the statuses of all devices on the Main Topology view in a centralized manner.
The Main Topology view displays the device alarms of all severities and devices statuses
with multiple types of icons, and provides alarm information in tips. The user can
customize the display effect of alarms as required.
– Creates, modifies, and deletes subnets, NEs, links.
– Queries the information about NEs and links between NEs.
– Conducts automatic NE searches and scheduled NE searches.
– Conducts automatic searches and link creation.
Physical View
In the Main Topology Window, select Physical Root from the Current View drop-down list.
The physical root reflects the relations of NEs in functional services in the entire network through
NEs, links and subnets. You can create subnets, NEs, and links in the physical view.
Custom View
In the Main Topology Window, select a custom view in the Custom View from the Current
View drop-down list.
The custom view is a subset of the Main Topology view. The network entities can be NEs,
NMSs, and subnets. Typically, the network management personnel need to customize views,
and choose network entities within their authority scope from the Main Topology view. For
details on how to create a custom view, see 5.9.1 Creating Custom Views.
Clock View
In the Main Topology Window, select Clock View from the Current View drop-down list.
In the clock view, you can perform the following operations: set NE clocks, query the network-
wide clock synchronization status, search for clock tracing relationships, synchronize with the
Physical View, view the master clock ID, query clock attributes, and view the clock lock state.
The U2000 supports passive optical network (PON) clock, Physical clock, PTP clock, and ACR
clock. In the clock view, a variety of NEs can be displayed, such as MSTP series, NG WDM
series, RTN series, PTN series and router series NEs.
Figure 5-4 shows the clock view of the U2000 and its functions.
l Discovering the clock topology automatically: The U2000 searches for clock links between
all NEs in the entire network to obtain the clock tracing relationships of all NEs. You can
search for clock links by NE or by clock link type. When the NE traced clock source has
changed, you need to re-search for the clock trace relationship.
l Viewing the clock topology: After the U2000 automatically discovers the clock topology,
you can view the clock tracing relationships in the entire network. To adjust the clock
topology, you can manually create and delete topological nodes and links.
l Configuring clocks: In the clock configuration window of the NE Explorer, you can
configure NE clocks, including Physical clock, PTP clock, ACR clock and PON clock. The
clock configuration function varies with NE types.
l Monitoring the change of clocks: When an NE or a link fails or a switching of clock sources
occurs in a network, the U2000 automatically updates the clock tracing relationships and
the clock synchronization status in the topology view. According to the clock alarms
generated on the NE where a clock was changed, you can identify the fault.
l Switching clocks manually: You can select a clock link and set its clock tracing relationship
as the current clock tracing relationships of the NE.
l Synchronizing with Physical View: You can synchronize the coordinate positions of NEs
and subnets in the Clock View with those in the Physical View. After the synchronization,
the subnets that have clock NEs are synchronized from the Physical View to the Clock
View. The empty subnets in the Clock View are deleted.
l Querying the clock attributes: You can query the type, hop count, and port name for clocks
currently traced by NEs, and view the compensation value for clock traced by ports.
l Viewing master clock ID: When you place the cursor over an NE where clock tracing
relationships exist, the displayed screen tip indicates the ID of the master clock that the NE
traces in the following format: NE name-Clock type-Clock ID.
l Viewing the clock lock state and time lock state: In the Clock View, the time lockout state,
time unlock state, clock lockout state and clock unlock state of each NE are indicated by
icons on the NE. When the lock state of an NE is changed, you can search for clock links
to update the state.
FTTx View
Right-click an OLT or ONU in the Main Topology and choose FTTx View from the shortcut
menu.
For FTTx networks, all OLTs and ONUs are displayed in the Main Topology and FTTx view.
Based on management domains and rights, you can create subnets flexibly to achieve separate
management of OLTs and ONUs. In addition, you can locate specific ONUs in the FTTx view
for fault diagnosis and routine maintenance.
Subnet
On the U2000, a large network can be divided into several smaller networks based on a specific
rule (for example, by region), for the convenience of network management. On the U2000, these
smaller networks are called subnets. Subnets are located in the physical view and custom view.
l A subnet is created to group and manage NEs together without impact on the NEs.
l Common subnets are created in the Physical Root or Clock View. Logical subnets are
created in the Custom view.
l The NMS supports the creation of a maximum of 20 layers of subnets.
NE
NEs are used to identify concrete entity devices, such as switches and routers.
l NE can be classified into physical NEs and virtual NEs based on their relationships with
the U2000.
– Physical NEs: These NEs are directly managed by the U2000.
– Virtual NEs:
– A virtual NE is an abstraction of an NE or a network that cannot be directly managed
by the U2000. If an NE that is not managed by the U2000 exists in the network and
there are trails created on the NE, the equipment can be represented by creating a
virtual NE on the U2000. Virtual NEs represent the topological relationships
between NEs that the U2000 manages directly and the equipment the U2000
manages indirectly on the topology.
– Currently, virtual NE concept applies to just the SDH series, PTN series and NG
WDM series NEs, and the virtual NEs can only simulate the SDH NE features.
– Different from actual NEs, a virtual NE does not need to be hardware-specific. It
can be used to represent any unknown equipment. On the U2000, it is usually used
to simulate the equipment that cannot be directly managed by the U2000, such as
the third-party equipment.
– You can customize the boards in a virtual NE on the U2000. The process of creating
and deleting a virtual NE is similar to that of an actual NE.
– Virtual NEs are not restricted by the license. The license does not define the
maximum number of virtual NEs on the U2000. Virtual NEs, however, occupy CPU
and memory resources, decreasing the management capacity of the U2000.
l NEs can be grouped into gateway NEs and non-gateway NEs based on whether they
communicate with the U2000 directly through the network.
The U2000 communicates with the NEs through the network to manage the network NE.
This type of NE that communicates directly with the U2000 through the network is called
gateway NE (GNE). The other NEs that communicate with the U2000 through the GNE
are called non-gateway NEs.
The GNE and non-gateway NE concept applies to the MSTP series, WDM series, WDM
(NA) series, RTN series, PTN series (except PTN 6900 series) and marine series NEs.
– GNE
– The U2000 manages the network NE through the GNE. The communication protocol
of GNE is IP or OSI.
– Each U2000 must connect to at least one GNE. NEs that directly communicate with
the U2000 are GNEs.
– If the number of non-gateway NEs that connect to a GNE is more than 50, a
GNE_MGR_LIMIT_OVER alarm is reported to the U2000.
– Non-Gateway NE
– The non-gateway NE communicates with the GNE by using the ECC or the extended
ECC. Therefore, it can communicate with the U2000.
– The recommended number of non-gateway NEs (including non-gateway NEs that
connect to the GNE by using the extended ECC) that connect to each GNE is fewer
than 50.
l Optical NE
– An optical NE represents a type of WDM series NEs, for example, OTM. The WDM
series NEs belong to an optical NE and each optical NE can contain multiple WDM
series NEs. The optical NE concept applies to the WDM series NEs only.
– Optical Network Element (ONE) is the transport entity that implements the NE
functions (terminal multiplexing, add/drop multiplexing, cross-connection and
regeneration) in a DWDM layer network.
– The locating of an ONE is equivalent to that of a common NE. In a view, an ONE is
displayed with an icon, like a common NE and its alarm status can be displayed with
colors. Logically, an ONE consists of different subracks.
– As an NE, an ONE cannot be expanded or entered like a sub-network. Similar to a
common NE, an ONE provides a list of the subracks that form the NE to display the
board layout.
– The U2000 manages the WDM series NEs by means of optical NEs. The WDM series
NEs are no longer referred to as NEs, but as subracks. The SDH series NEs have only
one subrack. Therefore, the NE layer does not need to be distinguished from the subrack
layer.
– There are four types of optical NEs, which are WDM_OTM, WDM_OLA,
WDM_OADM and WDM_OEQ.
NOTE
Currently, the OptiX OSN 1800, OptiX OSN 1832, OptiX OSN 6800, OptiX OSN 8800 series, OptiX
OSN 9800 series NE can be managed both separately as an NE and in an optical NE.
Connection
U2000 can manage connections, including links and fiber/cables in a centralized manner.
l Link
A link is used to connect signaling points (SPs) and signaling transfer points (STPs) and
transmit signaling messages.
Type Description
L2 Link A Layer-2 link is the Layer-2 link between equipment in the physical
root view. The U2000 supports the creation of the Layer-2 links, such
as the LLDP links and RPR links, and supports the display of the
links as the Layer-2 links that support the IPv6 protocol or IPv4 and
IPv6 protocol stacks in the physical root view.
l LLDP link: It refers to the Link Layer Discovery Protocol
(LLDP) link. The LLDP is a Layer 2 protocol defined in the IEEE
802.1ab. When the LLDP protocol runs on the NEs, the U2000
can obtain the Layer 2 information about all the NEs to which
the U2000 is connected and the details about the network
topology. This expands the scope of network management. LLDP
also helps find unreasonable configurations on the network and
reports the configurations to the U2000. This helps to remove the
errors in configurations timely.
l RPR link: It refers to the Resilient Packet Ring (RPR) link. The
RPR protocol is a new MAC layer protocol defined by IEEE
802.17. It is defined with the purpose of optimizing the
transmission of data packages and establishing an Ethernet MAN
standard of sharing bandwidth fairly over transmission media.
Based on the high bandwidth usage, multi-server access, high
bandwidth of optical network, and powerful self-healing
capability, the RPR technology has the following features:
– Two-ring structure
– Space multiplexing mechanism
– Flexible service bandwidth granularity
– Dynamic bandwidth sharing and allocation
– Statistic multiplexing
– Service level
– Automatic recognition of the structure of network topology
– Protection switching based on the source route
Extended ECC When there is no optical path between two or more NEs, the Ethernet
ports of the NEs can be used to achieve the extended ECC
communication. By default, the NEs use the auto-extended ECC
communication. If the amount of Huawei equipment that uses the
extended ECC communication exceeds four, the manually extended
ECC communication must be used instead.
Dummy Link A dummy link is used to identify the logical connection relationship
between two managed objects. Hence, a dummy link is also referred
to as a dummy connection.
l Fiber/Cable
Fiber & Cable refers to the physical entities that connect NEs, carry transmission objects
(user information and network management information) and perform transmission
function in the network. The optical fiber transmits optical signal, while the cable transmits
electrical signal. The fiber/cable between NEs represents the optical fiber connection or
cable connection between NEs.
Type Description
Serial Port Line A serial port line is used to connect the ports that are used for
serial communication. The ports can transmit and receive the
communication data.
Microwave Back To When an RTN station needs to converge services, multiple RTN
Back NE needs to be connected through fibers or 2 Mbit/s or 155 Mbit/
s cables. In this manner, low-capacity services are converged to
the high-capacity NE.
Virtual Fiber Virtual fiber is a logical concept. It may contain several physical
fibers, microwave links, or even one or more complete networks.
Ethernet Line The Ethernet line that the U2000 can manage is used to connect
the communication interface of the gateway NE and the U2000
server.
As available IPv4 addresses become insufficient, users tend to widely use IPv6 addresses for
service configuration. At present, the U2000 can display IPv6 NEs/links and dual-stack NEs/
links shown in Figure 5-6. This helps users to view required information.
NEs that support the IPv6 protocol include routers and switches series NEs.
The IPv6-related topology and link management functions supported by the U2000 are as
follows:
l IPv6 NEs and links are displayed as icons in the physical view, which is convenient to view.
– In the physical view, IPv6 NEs are represented by and . represents an IPv6 single-
stack NE; represents a dual-stack NE that supports both IPv6 and IPv4.
NOTE
l An NE for which IPv6 is enabled globally and only IPv6 addresses are set for interfaces is
displayed as an IPv6 single-stack NE.
l When IPv6 is globally enabled on an NE whose interfaces are configured with both IPv4 and
IPv6 addresses, the NE is displayed as a dual-stack NE.
– In the physical view, IPv6 links are represented by and .
NOTE
A link whose source and sink ports are configured with IPv6 can carry IPv6 packets.
l If the link can carry only IPv6 packets, the link is represented by .
l If the link can carry both IPv6 and IPv4 packets, the link is represented by .
l When the configurations of an IPv6 NE or IPv6 link change, the U2000 automatically
refreshes the topology or link in the physical view. The physical view can be automatically
refreshed in cases such as NE-level IPv6 is globally enabled or the IPv4 address or IPv6
address of an interface changes.
l IPv6 NEs and IPv6 links displayed in the physical view can be filtered according to
Protocol Type. The available options of Protocol Type include IPv4, IPv6, and Dual-
stack.
NOTE
To filter and view NEs and links on the topology, you can do as follows:
1. Choose View > Display Setting > Filter from the main menu.
2. On the Filter tab, click Type of Borne Network Protocol and select the protocol types as
required.
l When an IPv6-related alarm is reported to the U2000, the alarm is displayed for the
associated IPv6 NE or IPv6 link in the physical view. In addition, different colors are used
to indicate the severities of alarms.
l Batch NE creation
– Creating NEs over SNMP or ICMP in batches: If the U2000 successfully communicates
with NEs, it discovers these NEs by IP address or network segment and creates these
NEs in batches. The supported NE types are Router series, Switch series, PTN 6900
series, Access series and Security NEs.
– Creating transport or PTN series NEs: Based on the IP address, network segment, or
network service access point (NSAP) address of a gateway NE (GNE), the U2000
discovers all the transport or PTN series NEs that communicate with the GNE and
creates these NEs in batches.
– Importing/Exporting NEs in batches: The U2000 can import the IP addresses of the NEs
through files, and create NEs in batches. Users can also export the NEs managed in the
U2000 to files.
l Automatic NE discovery: The U2000 automatically discovers PTN series NEs, creates the
NEs, adds the NEs to topology views, and uploads the configuration data of the NEs.
l Scheduled NE search: The U2000 automatically searches the specified network segment
for desired types of NEs at intervals and adds the discovered NEs to topology views. The
supported NE types are Router series, Switch series, PTN 6900 series, Access series and
Security NEs.
l Automatic creation of fibers/cables and links: The U2000 automatically discovers fibers/
cables and links and creates them in batches.
You can select objects at different levels from the Physical Root navigation tree, such as a
subnet, a node, or an NE, to browse current alarms.
The U2000 indicates alarms in two ways: color-coding and icon. Color-coding is used by default.
l The color of a topology object indicates its operating and alarm status.
NOTE
For NEs, the operating status includes Critical Fault (the highest severity), Major Fault, Minor
Fault, Warning, Test, Loopback, Offline, Unknown, and Normal (the lowest severity) in
descending order.
l If multiple alarms of different severities occur on an NE, the color or icon that indicates
the highest severity of these alarms is displayed for the NE in the topology view.
l If alarms occur on multiple nodes in a subnet, the color or icon that indicates the highest
severity of these alarms is displayed for the subnet in the topology view.
l You can open the current alarm browsing window of an NE in the topology view and query
details about current alarms on the NE Panel.
l When is displayed on an NE, it indicates that the NE include boards, subboards and
ports is in the Maintenance status. That is, the NE is being installed, commissioned, or
tested. In this case, alarms generated for the NE can be ignored, the color of topology NEs
is not changed. For details about how to set the NE status to Maintenance, see 7.12.4
Setting the Alarm Maintenance Status.
The flow for constructing network topology is not fixed, but varied based on users' habits. Figure
5-9 shows the simplest network topology construction process and recommended topology
management operations.
Designing a Physical
Topology
Manage subnets
Creating a topology
Subnet
Modifying Fiber/Cable
Manage Information (Optional)
Creating Connections
connections
Naming a Fiber/Cable
(Optional)
NOTE
l Clock function on NEs is displayed automatically in the Clock View. For details, see 1.6.8.4 Clock
View.
l After creating subnets, NEs and connections in the Main Topology, you can customize the topology
view to manage some NEs separately. For details, see 5.9.1 Creating Custom Views.
Flow Description
For details about the flow for constructing the network topology shown in Figure 5-9, see Table
5-1.
5.3 Designing a Design the way in which subnets are divided N/A
Physical before deploying NEs in the topology view. The
Topology physical topology should reflect the topology
Ma structure of the actual communication network,
nag and should also facilitate the routine
e maintenance operations.
sub
nets 5.4 Creating a To facilitate management, you can put N/A
Subnet topological objects that are in the same area of
a network or with similar attributes to the same
topology subnet.
5.7.4 Uploading By uploading the NE data, you can synchronize The operation is
the NE Data the current NE configuration data to the network optional for the
(Optional) management system (NMS) directly. For MSTP series,
example, upload NE configuration and alarm WDM series,
and performance data to the U2000. WDM (NA)
series, RTN
series, PTN
series (except
PTN 6900
series) and
marine series
NEs only.
5.7.6 Adding After configuring the NE data, you need to add The operation is
Boards boards on the NE Panel if physical boards are optional for the
(Optional) added. You can add either the physical boards MSTP series,
that actually work on the NE or the logical WDM series,
boards that do not exist on the actual NE. WDM (NA)
series, RTN
series, PTN
series (except
PTN 6900
series) and
marine series
NEs only.
5.9.2.9 You can modify the name, designed attenuation, The operation is
Modifying length, and type of a fiber/cable according to its optional for the
Fiber/Cable connection status and physical features. MSTP series,
Information WDM series,
(Optional) WDM (NA)
series, RTN
series, PTN
series (except
Ma PTN 6900
nag series) and
e marine series
con NEs only.
nect
ions 5.9.2.10 In the network management, the fiber/cable The operation is
Naming a needs to be strictly named to ensure that faults optional for the
Fiber/Cable/ can be located quickly during maintenance and MSTP series,
Microwave troubleshooting. On the U2000, the pre-defined WDM series,
Link(Optional) naming rules are used to name the fibers/cables. WDM (NA)
series, RTN
series, PTN
series (except
PTN 6900
series) and
marine series
NEs only.
The topology management window consists of a navigation tree on the left and a topology view
on the right. The navigation tree displays all the topology objects and their hierarchical
relationships in a tree, and the topology view displays all the topology objects and their positions
in the physical topology view.
Based on the networking, the U2000 provides the following suggestions for dividing the physical
view to meet various management requirements:
l By region: based on regions where NEs are located.
l By NE type: based on types of NEs.
l By IP address: based on IP addresses of NEs.
l By responsible person: based on responsible persons of NEs.
NOTE
You can also choose a combination of more than a few methods to divide the physical view.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l Subnets can reside in the physical root, clock, and custom views.
l Subnets are classified into physical subnets and logical subnets. Subnets in the physical
root and clock views are physical subnets. Those in custom views are logical subnets.
l Subnets are used to simplify the topology view without impact on NEs. It is recommended
that a subnet contain a maximum number of 20 layers.
Procedure
Step 1 Choose View > Main Topology (traditional style) from the main menu or select Topo View in
Application Center and choose Topology > Main Topology (application style) from the main
menu.
Step 2 Select a type of view from the Current View drop-down list.
l When creating a physical subnet, select Physical Root or Clock View.
l When creating a logical subnet, select a custom view.
l In the Main Topology, right-click in a blank area and choose New > Subnet from the shortcut
menu.
Step 4 In the dialog box that is displayed, click the Property tab and set Name, Alias, Parent
Subnet, Coordinate, and Remarks.
Step 5 Optional: Click the Select Objects tab. Select objects from the Available Objects area and
click to add them to the Selected Objects area. Alternatively, click to add
all objects to the Selected Objects area.
NOTE
Step 6 In the Create Physical Subnet or Create Logical Subnet dialog box, click OK.
The subnet is successfully created in the selected view. You can enter the new subnet by double-
clicking it.
----End
Table 5-2 Protocols for communication between the U2000 and NEs
Transp TCP/IP The IP over DCC communication Make sure that transport
ort NE transmits DCC data by the using IP data NEs and the U2000
packets. The IP over DCC directly communicate with each
operates and maintains remote NEs by other using the same
using standard TCP/IP protocol. In gateway NE. Protocol
addition, it realizes the application configuration is not
functions, such as FTP, Telnet, and required.
SNMP. As essential parts of the IP over
DCC communication, the dynamic and
static routing protocols are used to create
route information.
Access SNMP The SNMP protocol is used for basic Refer to 5.5.2.1
NE functions such as discovering NEs, Configuring the Default
synchronizing service configuration SNMP Parameters
data, managing faults, and managing Template and 5.5.2.2
performance. Setting NE SNMP
Parameters.
NOTE
l IP NE: Router series, Switch series, Security series NEs, ATN series NEs.
l Transport NE: MSTP series, WDM series, RTN series, PTN series and Marine series NEs.
l Access NE: OLT series, MDU series, MSAN series, DSLAM series.
Figure 5-10 Topology for communication between the U2000 and NEs in the IP or access
domain
U2000
SNMP/Telnet/STelnet/FTP/SFTP/TFTP
GGSN
Enterprise1
2G/3G RAN
PE P P PE
Enterprise2 Switch
IPv6 IPv6 IPv6 IPv6
IP/MPLS CORE ATM/FR
Internet
Figure 5-11 Topology for communication between the U2000 and NEs in the transport domain
U2000
IP/OSI
DCN Extenal DCN
HW ECC or
IP/OSI over
DCC
Internal DCN
LAN switch
NOTE
The MSTP series, WDM series, RTN series, PTN series and Marine series NEs support the TCP/IP and
OSI protocols. The NG WDM series NEs and the OTN (NA) series NEs, however, do not support the OSI
protocol.
NOTE
l The U2000 server has the access permission on NEs. In a high availability (HA) system, both the
primary and secondary sites should have the access permission.
l Using SNMPv3 is recommended because of its higher security than SNMPv1 and SNMPv2c.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l This operation is applicable to the Router series, Switch series, PTN 6900 series, Access
series and Security NEs.
l Ensures that SNMP parameters with the same settings on U2000 have been configured on
the NE. For details about configuration commands, refer to Configuration.
Context
Do not delete the default access protocol parameter template.
Procedure
Step 1 Choose Administration > NE Communicate Parameter > Default Access Protocol
Parameters (traditional style) from the main menu or select Fix-Network NE Configuration
in Application Center and choose Administration > NE Communicate Parameter > Default
Access Protocol Parameters (application style) from the main menu.Click Display.
Step 2 In the Default Access Protocol Parameters dialog box, click the related tab to switch to the
page for configuring protocol parameters. The following figure shows how to set SNMPv3
parameters.
Task Operations
Delete a parameter template. 1. Select the template to be deleted in the parameter template
list and then click Delete.
2. In the Confirm dialog box, click Yes.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the Router series, Switch series, PTN 6900 series, Access series and Security
NEs.
l When setting SNMP parameters on the U2000, ensure that SNMP parameters with the same
settings have been configured on the NE for successful communication.
l For all SNMPv3 NEs that are managed by the same U2000, if different NEs need to use
the same user name, ensure that the private protocol, encryption password, authentication
protocol, and authentication password are consistent on these NEs.
Context
l The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure proper
collection of service performance data. However, SNMPv3 is recommended as it is more
secure than SNMPv2c.
l If the Simple Network Management Protocol version 3 (SNMPv3) is used, plan NE
communication parameters in a unified manner. Group NEs and ensure that NEs within the
same group use the same communication parameters and different NE groups use different
user names. The communication parameters include the user name, private protocol,
encryption password, authentication protocol, and authentication password.
l If SNMP parameters are configured incorrectly on NEs and the U2000, the NE icon in the
U2000 topology view is blue.
l If ACL control is added to the SNMP read and write community on NEs, the ACL must
allow the IP address of the U2000 server to access the NEs using SNMP.
Procedure
Step 1 Choose Administration > NE Communicate Parameter > NE Access Protocol
Parameters (traditional style) from the main menu or select Fix-Network NE Configuration
in Application Center and choose Administration > NE Communicate Parameter > NE
Access Protocol Parameters (application style) from the main menu.
Step 2 In the NE Access Protocol Parameters window, click the related tab to switch to the page for
configuring protocol parameters.
Step 3 Optional: Click Filter. In the Filter dialog box, set the NE name, NE IP address, or both.
NOTE
l If the NE name and IP address in the Filter dialog box are empty, access protocol parameters of all
NEs are displayed.
l If you set the NE name and IP address in the dialog box, the NE access protocol parameters that meet
the filter criteria are displayed.
NE access protocol parameters that meet the filter criteria are displayed.
NOTE
If the details about the SNMP parameters of an NE are already displayed, the Display button changes
to the Hide button.
l In the NE Access Protocol Parameters window, double-click a record in the NE parameter
list.
The details about the selected record are displayed in the lower part of the window.
NOTE
l In the NE Access Protocol Parameters window, click Reset. In the Default Access Protocol
Parameters dialog box, select a template and click Display. The details about the selected template
are displayed and the parameters of this template cannot be set in the Default Access Protocol
Parameters dialog box.
l Click Reset, in the Default Access Protocol Parameters dialog box, click Add or Delete to add or
delete the template of a specific SNMP version.
l Set parameters of a protocol template. Choose Administration > NE Communicate Parameter >
Default Access Protocol Parameters (traditional style) from the main menu or select Fix-Network
NE Configuration in Application Center and choose Administration > NE Communicate
Parameter > Default Access Protocol Parameters (application style) from the main menu. Double-
click a record in the parameter list and set parameters of the template. Then, click Apply to save the
modification.
----End
NOTICE
The U2000 client accesses NEs using a proxy. To keep network users secure, configure a proxy
service ACL. Before using the telnet function to connect to an NE, ensure that port 31035 is
enabled between the U2000 server and client and that a client ACL has been configured. If no
client ACL is configured, choose Administration > NMS Security > Proxy Service ACL from
the main menu and configure one by following the steps provided in 3.3.1.3 Setting the Proxy
Service ACL.
l If the U2000 client is installed on the same computer as the U2000 server, set the IP address
in an access control item to 127.0.0.1.
l To allow the clients in all network segments to access NEs, set IP Address or Network
Segment in the ACL to 0.0.0.0/0 (or a value in the IP address/0 format) and set
Operation to Accept.
l If the network includes gateway NEs, such as Network Address Translation (NAT) NEs, and
the U2000 client is located inside a NAT network, set the IP address in the access control
item to an IP address that, after being translated, is accessible to the U2000 server. Do not
set the IP address to the intranet IP address bound to the U2000 client.
NOTE
Prerequisites
l Telnet template: The user name and password have been configured on the NE. Telnet
parameter settings are consistent between the U2000 and the NE.
l STelnet template: The SSH user name and password have been configured on the NE, and
the NE authentication mode is set to SSH. STelnet parameter settings are consistent between
the U2000 and the NE.
Procedure
Step 1 Choose Administration > NE Communicate Parameter > NE Telnet/STelnet Template
Management (traditional style) from the main menu or select Fix-Network NE
Configuration in Application Center and choose Administration > NE Communicate
Parameter > NE Telnet/STelnet Template Management (application style) from the main
menu.
In the scenario where only part of the parameters of a default template or created template need to be modified,
select the desired template, and then modify associated parameters in the Details area.
Step 3 In the dialog box that is displayed, select the desired protocol type, set Template Name, and
click OK. The following figure shows how to create a STelnet template.
Step 4 Select the created template. Then, set associated parameters in the Details area.
NOTE
l Access series NEs do not support the function of setting Enable Privilege.
l The login user name and password must be the same as those configured on the NE.
l When creating a performance monitoring instance that supports Y.1731, you need to set Telnet/STelnet
information for this NE on the U2000. Set the Auth.Mode parameter to User Auth because other
modes are not supported. Keep the User Name and Password parameters for Telnet and STelnet to
be the same as the FTP and SFTP user names and passwords respectively.
l When configuring an STelnet parameter template, you must import a private key file for configuring
Private Key if Auth. Mode is RSA Auth or RSA&Pwd Auth. If a key generator is used to generate
a key pair file and a password phrase has been set for the file, you must enter the password phrase in
the Please enter the password phrase area for configuring Private Key. The entered password phrase
must be the same as the preset one.
l A key pair, including a private key and public key, can be generated by using a key generator
PUTTYGEN.EXE. In PuTTY Key Generator, Type of key to generate is set to SSH-2 RSA and
Number of bits in a generated key is set to 2048. To ensure security, enter a password phrase
during key pair file generation.
l A public key file is set to the NE through the NE CLI after being converted by using a key converter
sshkey_en.exe.
l To ensure security, you are advised to delete the local private key file after it is imported into the
U2000.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The Telnet/STelnet template must be configured on the U2000.
l The related parameters, such as the user name and password, must be set on NE. Telnet/
STelnet parameter settings are consistent between the U2000 and the NE.
Procedure
Step 1 Choose Administration > NE Communicate Parameter > Set NE Telnet/STelnet
Parameter (traditional style) from the main menu or select Fix-Network NE Configuration
in Application Center and choose Administration > NE Communicate Parameter > Set NE
Telnet/STelnet Parameter (application style) from the main menu.
Step 2 In the Device Telnet/STelnet Parameter Management window, select the desired NEs from
the navigation tree in the left pane and click .
NOTE
Alternatively, select the desired NEs in the Main Topology, right-click, and choose Set NE Telnet/STelnet
Parameter from the shortcut menu.
Step 4 In the Select Telnet/STelnet Template dialog box, select the template to be used, and then click
OK.
Step 6 In the Operation Result dialog box, click Close. The template import operation takes effect
automatically.
Step 8 Optional: Click Export. Then, set Start row, End row, and File name, and click OK to export
details about the Telnet/STelnet parameters.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l For .txt files, code formats ISO-8859-1 and UTF-8 are supported. For .csv files, only code format
UTF-8 is supported. For .html and .xls files, code format is unconfigurable. You are advised to use the
default encoding format if the saved file does not need to support multiple languages; otherwise,
UTF-8 is recommended.
----End
Follow-up Procedure
The configured Telnet/STelnet parameters can be deleted if the Telnet/STelnet protocol is not
required for remote NE login and management. Perform the following steps to delete configured
Telnet/STelnet parameters.
NOTICE
l The Telnet/STelnet parameters can be deleted only by NMS users with "maintainer" rights
or higher.
l Once the Telnet/STelnet parameters of an NE are deleted, users cannot log in to or manage
the NE remotely.
1. In the Device Telnet/STelnet Parameter Information list, select one or multiple records.
2. Click Delete Parameter in the lower pane. In the confirmation dialog box, click OK.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The related parameters, such as the user name and password, must be set on NE.
Procedure
Step 1 Choose Administration > NE Communicate Parameter > Set NE Telnet/STelnet
Parameter (traditional style) from the main menu or select Fix-Network NE Configuration
in Application Center and choose Administration > NE Communicate Parameter > Set NE
Telnet/STelnet Parameter (application style) from the main menu.
Step 2 In the Device Telnet/STelnet Parameter Management window, select the desired NEs from
the navigation tree in the left pane and click .
NOTE
Alternatively, select the desired NEs in the Main Topology, right-click, and choose Set NE Telnet/STelnet
Parameter from the shortcut menu.
Step 3 In the Device Telnet/STelnet Parameter Management dialog box, set the Telnet/STelnet
parameters as required in the Details group box.
NOTE
l Access series NEs do not support the function of setting Enable Privilege.
l The login user name and password must be the same as those configured on the NE.
l When creating a performance monitoring instance that supports Y.1731, you need to set Telnet/STelnet
information for this NE on the U2000. Set the Auth.Mode parameter to User Auth because other
modes are not supported. Keep the User Name and Password parameters for Telnet and STelnet to
be the same as the FTP and SFTP user names and passwords respectively.
l When configuring an STelnet parameter template, you must import a private key file for configuring
Private Key if Auth. Mode is RSA Auth or RSA&Pwd Auth. If a key generator is used to generate
a key pair file and a password phrase has been set for the file, you must enter the password phrase in
the Please enter the password phrase area for configuring Private Key. The entered password phrase
must be the same as the preset one.
l A key pair, including a private key and public key, can be generated by using a key generator
PUTTYGEN.EXE. In PuTTY Key Generator, Type of key to generate is set to SSH-2 RSA and
Number of bits in a generated key is set to 2048. To ensure security, enter a password phrase
during key pair file generation.
l A public key file is set to the NE through the NE CLI after being converted by using a key converter
sshkey_en.exe.
l To ensure security, you are advised to delete the local private key file after it is imported into the
U2000.
Step 7 Optional: Click Export. Then, set Start row, End row, and File name, and click OK to export
details about the Telnet/STelnet parameters.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l For .txt files, code formats ISO-8859-1 and UTF-8 are supported. For .csv files, only code format
UTF-8 is supported. For .html and .xls files, code format is unconfigurable. You are advised to use the
default encoding format if the saved file does not need to support multiple languages; otherwise,
UTF-8 is recommended.
----End
Follow-up Procedure
The configured Telnet/STelnet parameters can be deleted if the Telnet/STelnet protocol is not
required for remote NE login and management. Perform the following steps to delete configured
Telnet/STelnet parameters.
NOTICE
l The Telnet/STelnet parameters can be deleted only by NMS users with "maintainer" rights
or higher.
l Once the Telnet/STelnet parameters of an NE are deleted, users cannot log in to or manage
the NE remotely.
1. In the Device Telnet/STelnet Parameter Information list, select one or multiple records.
2. Click Delete Parameter in the lower pane. In the confirmation dialog box, click OK.
Prerequisites
You have logged in to the U2000 client as a user who belongs to the Administrators groups.
Context
l The newly installed U2000 automatically completes the configuration for the xFTP
information after being successfully started. You cannot modify the default xFTP
configuration unless otherwise specified.
l When the U2000 manages more than 5000 NEs, you are advised to use third-party xFTP
servers in file transfer between NEs and the U2000 server.
NOTE
SFTP is recommended because it is more secure than FTP.
Procedure
Step 1 Choose Settings > xFTP Settings > Local xFTP Settings (application style) or
Administration > Settings > Local xFTP Settings (traditional style) from the main menu.
Step 2 Perform operations based on the operating system running on the U2000 server.
Operating Operation
System
Solaris or SUSE 1. Optional: Set the user name and password. Ensure that the user name
Linux and password on the client are consistent with those on the server.
The default user name and password on the server are ftpuser and
Changeme_123 respectively.
NOTE
l After being successfully set, the information is automatically synchronized
to U2000 clients. You do not need to set it on clients.
l For details about the method of changing the user name and password on
the server, see the description of the modify_ftp_setting command in U2000
Administrator Guide.
l FTP port, SFTP port, and Home directory are automatically set during
U2000 installation and do not need to be modified. If you modify any of the
parameters, the local xFTP function may be unavailable.
2. Test the xFTP function of the local xFTP server.
l To test the FTP function, click Test FTP.
l To test the SFTP function, click Test SFTP.
3. Click OK.
Operating Operation
System
Windows 1. To change the home directory as required, set Home directory in the
Local xFTP Information dialog box.
NOTE
The value of Home directory must be the working directory of the xFTP user
in the operating system of the local xFTP server.
2. Optional: Select Change password to change the password of the
xFTP user.
NOTE
l User name, FTP port, and SFTP port are automatically set during
U2000 installation and do not need to be modified. If you modify any of the
parameters, the local xFTP function may be unavailable.
l The default password is Changeme_123. It is recommended that the
password be a string of 8 to 32 characters, containing lowercase and
uppercase letters, digits, and special characters (excluding " ` \).
3. Test the xFTP function of the local xFTP server.
l To test the FTP function, click Test FTP.
l To test the SFTP function, click Test SFTP.
4. Click OK.
NOTE
After the home directory and password are changed, the changes are
automatically synchronized to the U2000 server. You do not need to specify
them on the server.
----End
Prerequisites
l The FTP/SFTP server must be configured successfully. The FTP/SFTP service must be
enabled.
l This operation is applicable to the Router series, Switch series, PTN 6900 series, Access
series and Security NEs.
Context
Network Address Translation (NAT) helps ease IP address insufficiency and facilitates address
planning inside a network. It hides computers inside a network and protects them against attacks
outside the network.
The following figure shows a network with NAT between the U2000 server and NEs. When NE
1 and NE 2 report traps or initiate xFTP service requests to the U2000 server, the traps or requests
are converted via NAT to the U2000 server IP3 address.
Procedure
Step 1 Choose Administration > Settings > NAT Configuration Management (traditional style)
from the main menu or select System Management in Application Center and choose
Settings > NAT Configuration Management (application style) from the main menu.
Step 2 In the dialog box that is displayed, click New to add a record and configure the IP addresses.
NOTE
l Starting NE IP address and Ending NE IP address: Specify the IP address range of NEs.
l NMS IP address: Indicates the external IP address that the U2000 at a site uses to communicate with
NEs. The IP address ranges of the NEs at different sites can overlap.
In HA networking mode, configure IP address translation modes at the primary sites as follows:
1. Starting NE IP address Ending NE IP address Primary site IP address Translated primary site IP address
2. Starting NE IP address Ending NE IP address Secondary site IP address Translated secondary site IP
address
Example
l Single-server system networking and distributed networking: The IP address of the
U2000 server is 136.12.36.2 and it changes to 198.168.23.25 after NAT translation by the
firewall. In order to ensure that NEs that are on the subnet 198 can communicate with the
U2000 server, complete the NAT configuration as follows:
l High availability system networking: An example assumes that the IP address of the
primary site is 136.12.36.2 and that of the secondary site is 136.12.36.3. The IP address of
the primary site changes to 198.168.23.25 and the IP address of the secondary site changes
to 198.168.23.26 after NAT translation by the firewall. NEs are located on network segment
198. To ensure the normal communication between the U2000 server and NEs, complete
the NAT configuration on the primary site as follows:
l High availability system networking (the U2000 server uses the dual-NIC IPMP solution):
On the primary site, the IP address of NIC 1 is 136.12.36.1, the IP address of NIC 2 is
136.12.36.2, and the system IP address is 198.168.23.3. On the secondary site, the IP
address of NIC 1 is 136.12.36.11, the IP address of NIC 2 is 136.12.36.12, and the system
IP address is 198.168.23.13. Some devices are located on network segment 198, some other
devices are located on network segment 136. The devices on the two network segments
can access the system IP address of the U2000 server. Configure the IP address for NAT
configuration management on the primary site as follows:
create NEs: creating NEs one by one and creating NEs in batches. When a large number of NEs
need to be created, for example, during deployment, it is recommended that you create NEs in
batches. When you need to create just a few NEs, it is recommended that you create the NEs
one by one.
Context
NOTE
l When you create a transport, router, or switch NE, the name of the new NE cannot be the same as an
existing one. When you create an access NE, however, the name of the new NE can be the same as an
existing one. It is recommended that access NEs use different names.
l When you manually add NEs to the U2000, NE names cannot be automatically obtained if the
communication between these NEs and the U2000 server is blocked by the firewall.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l U2000 communicates with the GNE normally.
l The NE Explorer instance of the NEs has been created.
l If the Huawei-predefined certificate is not deployed for NEs, you cannot create the NEs in
Security SSL connection mode directly. You need to create them in Common connection
mode and then load their SSL certificates and change their connection modes to Security
SSL. Otherwise, these NEs cannot communicate with the U2000. Whether the NE is
preconfigured with the Huawei-developed digital certificate, refer to the NE list of 5.6.4
Setting the Security SSL Connection Mode for Transport NEs.
Context
l In the case of tran or PTN NEs, the function of creating an NE uses the license for dedicated
upgrade items or the license for NE resources. If there is no remaining license for dedicated
upgrade items or license for NE resources, a message is displayed indicating that NE
creation fails. It is recommended that you apply for a new license for NE resources.
NOTE
l NE licenses will be deducted for NE creation. If NE licenses are insufficient, the U2000 enters
the grace period.
l No operation is limited within the grace period that lasts 60 days. If the grace period ends, NEs
of the same type cannot be created, but the NEs that have been created can still be used. In
addition, users cannot add NEs that have been deleted.
l The grace period ends for the U2000 when you update the service license with a new valid one.
If resources are still insufficient, the start and end time of the grace period are recalculated.
l The U2000 reports ALM-801 OSS License Beyond Limitation when it enters the grace period.
Contact your Huawei engineers for new licenses.
l Except the OptiX OSN 1800, OptiX OSN 1832, OptiX OSN 6800, OptiX OSN 8800 series,
OptiX OSN 9800 series NE, to facilitate management, 5.6.2.1 Creating Optical NEs
before creating WDM NEs in batches. Otherwise, the new WDM NEs are allocated to idle
optical NEs automatically.
l If the number of equivalent NEs managed by an NE management instance exceeds the
upper limit, but does not reach the maximum number of NEs that the License permits, it is
recommended that you create another NE management instance before creating NEs. For
details about how to add NE management instances, see section "Adding an Instance" in
the Administrator Guide.
l Security SSL is recommended because of its higher security than Common. For the NEs
that cannot be created in Security SSL connection mode directly, for details, see 5.6.4
Setting the Security SSL Connection Mode for Transport NEs.
Procedure
Step 1 Choose File > Discovery > NE (traditional style) from the main menu or select Topo View in
Application Center and choose File > Discovery > NE (application style) from the main menu.
Step 3 Select the search mode from the drop-down list of Search Mode.
l Set the Search Mode to Search for NE.
1. Enter the network segment or IP addresses of NEs to search for the NEs.
a. Click Add and the Input Search Domain dialog box is displayed.
b. Set the address type to IP Address Range of GNE, IP Address of GNE, or
NSAP Address. Enter the Search Address, User Name, and Password. Click
OK.
NOTE
l The default NE user is root. The default password is password. For WDM NEs (NA),
both the default user name and the default password are SONET. If the NE user name
or password has been changed, use the actual user name or password of the NE.
l If you search by IP address:
l Only the NEs (not across routers) in the same network segment can be searched
out normally if you select the IP Address Range of GNE because broadcasting
is usually disabled for the routers in the network (to prevent network storm).
l Search out the NEs in the network segment by using the IP Address of GNE if
you need to search for the NEs across routers.
l Only NSAP Address can be selected If you search for NEs by using the NSAP
address.
l Repeat the above steps to add more search domains. You can also delete the system-
default search domain.
2. In the Search for NE area, perform the following operations:
– Select Create NE after search, click Common Connection Mode or Security
SSL Connection Mode (preferred), and then enter the NE User and Password.
NOTE
You can select Create NE after search and Upload after being created to search for NEs,
create NEs, and upload the NE data at a time.
l Set the Search Mode to IP auto discovery.
NOTE
If you fail to enter a network segment correctly, enable IP auto discovery. After enabling IP auto
discovery, you can obtain the IP address of the GNE and search out all the NEs related to the GNE.
NOTICE
In the case of NEs that are connected to the U2000 through the router, these NEs cannot
be searched out by IP auto discovery. They can be searched out only by network segment.
Step 5 Optional: If you select only Search for NE, you can select uncreated NEs from the Relusts list
and click Create after the U2000 completes the search. In the Create dialog box, enter the NE
User and Password. Click OK.
Step 6 Optional: Click Change NE ID, and the Change NE ID dialog box is displayed. Users can
check the value of Bar Code against the Bar Code List, and then modify the NE Name, Extend
NE ID, Base NE ID, and IP Address fields accordingly.
NOTE
The Bar Code List is provided by the hardware installation personnel to the software commissioning
personnel. The list contains the bar codes of stations.
Step 7 Optional: Click Set Gateway NE, and the Set Gateway NE dialog box is displayed. Set the
parameters, and click OK.
----End
Follow-up Procedure
To prevent unauthorized operations on a new NE, change the default password for the NE user
as soon as possible and subsequently change the non-default password at regular intervals.
If you fail to log in to an NE after creating it, the probable causes are as follows:
l The password for the NE user is incorrect. Enter the correct password.
l The NE user is invalid or is already logged in. Specify a valid NE user.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE management instance of the NEs has been created.
l For access NEs, the xFTP server is configured correctly and the xFTP service is enabled.
l For third-party NEs, make sure that common device processes of the U2000 is started
successfully.
l The U2000 communicates with NEs successfully. That is, correct IP addresses are
configured for NEs and the U2000 and managed NEs can ping each other.
l Before automatic ICMP NE searches, disable ICMP packet blocking in the firewall of the
U2000 server, because the ICMP packet blocking interrupts communication between the
U2000 and ICMP NEs.
l For SNMP NEs, SNMP parameters in the SNMP parameter template on the U2000 are the
same as those on SNMP NEs.
l Assume NE A and NE B are at each end of a Link Layer Discovery Protocol (LLDP) link.
After NE A is created on the U2000, NE B and this LLDP link will be automatically
discovered and added to the topology view by the U2000 if the following requirements are
met:
– NE A can be either a Huawei NE or a third-party NE while NE B must be a Huawei
NE.
– NE B and NE A can communicate with each other.
– LLDP is supported by and has been enabled on NE B and NE A.
– The management IP address in the LLDP configuration is correctly configured for NE
B. That is, this IP address is used to manage communication with the U2000.
Specifically, you can run the lldp management-address command to configure this IP
address.
– SNMP parameters configured for NE B are the same as those in the SNMP parameter
templates on the U2000.
Context
l In the case of switch, router NEs and security NEs, the NE creation consumes upgrade
licenses or NE resource licenses. If there is no available upgrade or NE resource license, a
prompt message is displayed indicating that NE creation fails. It is recommended that you
apply for a new NE resource license.
NOTE
l NE licenses will be deducted for NE creation. If NE licenses are insufficient, the U2000 enters
the grace period.
l No operation is limited within the grace period that lasts 60 days. If the grace period ends, NEs
of the same type cannot be created, but the NEs that have been created can still be used. In
addition, users cannot add NEs that have been deleted.
l The grace period ends for the U2000 when you update the service license with a new valid one.
If resources are still insufficient, the start and end time of the grace period are recalculated.
l The U2000 reports ALM-801 OSS License Beyond Limitation when it enters the grace period.
Contact your Huawei engineers for new licenses.
l If you select the Name NE Using IP Address check box but clear the Create NEs
Automatically check box when specifying the filter criteria, you can set the physical path,
Telnet/STelnet parameter template for required NEs. For details about how to configure a
Telnet/STelnet parameter template, see 5.5.3.1 Configuring a Telnet/STelnet Parameter
Template.
l If you clear the Automatically Create NEs check box, the discovered NEs are not
automatically created. You need to manually create these NEs.
l Use Method 2 to set extending parameters for SNMP/ICMP NEs when you create them in
batches. Otherwise, use Method 1.
l If the number of equivalent NEs managed by an NE management instance exceeds the
upper limit, but does not reach the maximum number of NEs that the License permits, it is
recommended that you create another NE management instance before creating NEs. For
details about how to add NE management instances, see section "Adding an Instance" in
the Administrator Guide.
l When the U2000 automatically discovers NEs, it automatically discovers and adds the IP
links, side-by-side links, LLDP links, and PRP links between NEs to the topology view.
For details about links, see Objects in a Topology View.
l The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure proper
collection of service performance data. However, SNMPv3 is recommended as it is more
secure than SNMPv2c.
l Only one client performs the automatic search function at a time.
l The existing NEs cannot be discovered. In the Detail Information list, those NEs are
displayed as the existing NEs.
Procedure
l Method 1:
1. Choose File > Discovery > NE (traditional style) from the main menu or select Topo
View in Application Center and choose File > Discovery > NE (application style)
from the main menu.
2. Click the SNMP/ICMP NE Search tab. Specify the filter criteria such as NE Type
and Ping Times.
NOTE
l If you select the Automatically Create NEs check box, NEs are created automatically in
the physical root after a successful search on the U2000.
l If you clear the Automatically Create NEs check box, NEs are created manually after a
successful search. In the NE Data area, select required NEs and click Create.
3. Click Default SNMP Parameter to set SNMP parameters to the same values as those
on NEs.
NOTICE
If the settings of the SNMP parameters are inconsistent with those on the NEs, the NE
cannot be searched out.
NOTE
If multiple SNMP parameter templates are selected, use these templates one by one to perform
SNMP-based communication until the communication succeeds.
4. Optional: Click Advanced to set the Telnet/STelnet or Netconf protocol template
and click OK.
NOTE
l If the Telnet/STelnet/Netconf settings on the NE are consistent with those in the default
Telnet/STelnet/Netconf template on the U2000, use the default template without clicking
Advanced to modify the template parameters.
l If the Telnet/STelnet/Netconf settings on the NE are inconsistent with those in the default
Telnet/STelnet/Netconf template on the U2000, click Advanced and modify the template
parameters according to the communication parameters on the NE.
l Setting method: Click next to Telnet/STelnet Settings or Netconf Settings in the Set
NE Communication Parameters dialog box. In the Telnet/STelnet Template
Management or NETCONF Template Management dialog box, select an existing
template or create a template.
l V8–based NEs support Netconf parameter settings. The Router series, Switch series and
Security NEs supports Telnet/STelnet parameter settings.
5. In the IP Address Range (History Records are already loaded) area, click Add and
the IP Address Range dialog box is displayed. Set Start IP Address, End IP
Address, and Subnet Mask and click OK.
6. Optional: In the IP Address Range (History Records are already loaded) area,
click Import IP Address, select a CSV file containing the imported IP addresses, and
click Open.
NOTE
l Before importing the IP addresses, save the target Excel file to a CSV file.
l When using an Excel file to plan IP addresses to be imported in the Start IP Address, End
IP Address, and Subnet Mask sequence, you do not need to add any table heading but
directly enter the IP addresses.
l Each row in the Excel file corresponds to an IP address range on the U2000.
7. Click Next. On the SNMP/ICMP NE Search tab page, required NEs and operation
records are displayed.
8. Optional: Click Detail. In the dialog box that is displayed, view Undiscovered
Equipment in the operation records.
l Method 2:
1. Choose File > Discovery > NE (traditional style) from the main menu or select Topo
View in Application Center and choose File > Discovery > NE (application style)
from the main menu.
2. Click the SNMP/ICMP NE Search tab. Specify the filter criteria such as NE Type
and Ping Times. Select the Name NE Using IP Address check box and clear the
Automatically Create NEs check box.
3. Click Default SNMP Parameter to set SNMP parameters to the same values as those
on NEs.
NOTICE
If the settings of the SNMP parameters are inconsistent with those on the NEs, the NE
cannot be searched out.
NOTE
If multiple SNMP parameter templates are selected, use these templates one by one to perform
SNMP-based communication until the communication succeeds.
4. Optional: Click Advanced to set the Telnet/STelnet or Netconf protocol template
and click OK.
NOTE
l If the Telnet/STelnet/Netconf settings on the NE are consistent with those in the default
Telnet/STelnet/Netconf template on the U2000, use the default template without clicking
Advanced to modify the template parameters.
l If the Telnet/STelnet/Netconf settings on the NE are inconsistent with those in the default
Telnet/STelnet/Netconf template on the U2000, click Advanced and modify the template
parameters according to the communication parameters on the NE.
l Setting method: Click next to Telnet/STelnet Settings or Netconf Settings in the Set
NE Communication Parameters dialog box. In the Telnet/STelnet Template
Management or NETCONF Template Management dialog box, select an existing
template or create a template.
l V8–based NEs support Netconf parameter settings. The Router series, Switch series and
Security NEs supports Telnet/STelnet parameter settings.
5. In the IP Address Range (History Records are already loaded) area, click Add. In
the IP Address Range dialog box, set Start IP Address, End IP Address, and
Subnet Mask and click OK.
6. Click Next. On the SNMP/ICMP NE Search tab page, required NEs and operation
records are displayed.
a. In the NE Data list, select one or multiple NEs in the Create or Not column.
b. Click Configure. In the Configure dialog box, set the physical path, Telnet/
STelnet template for NEs.
c. Click OK.
NOTE
Configure is highlighted and available only when Router series, Switch series and Security
NEs is searched.
8. Optional: Click Detail. In the dialog box that is displayed, view Undiscovered
Equipment in the operation records.
9. Select one or multiple NEs and click Create.
----End
Prerequisites
l You have logged in to the U2000 client.
l The mediation software of the NE to be created is successfully installed.
Context
NOTE
The U2000 does not support the batch creation of virtual NEs.
Procedure
Step 1 Open the Create Topo Object dialog box.
1. Choose View > Main Topology (traditional style) from the main menu or select Topo
View in Application Center and choose Topology > Main Topology (application style)
from the main menu.
2. In the topology navigation tree or physical topology view, right-click the subnet of the NE
to be created, and then choose Bulk Create Topo Objects from the shortcut menu.
Step 2 Export the script file template for creating NEs in batches.
1. Select the NE node under the Bulk Create node from the navigation tree of the Create
Topo Object dialog box.
2. In the right Export Template pane, select INI File or CSV File, and then click Export.
l If INI File is selected, the information about multiple NE types can be exported to a
file all at a time.
l If CSV File is selected, the information about an NE type can be exported to a file all
at a time.
Step 3 Enter the information about NEs to be created in the exported script file template.
For format description of INI templates and CSV templates, see Description of the .ini Template
Used for the Core Network NE Script and Description of the .csv Template Used for the Core
Network NE Script.
1. In the right pane of the Create Topo Object dialog box, click to select a script file.
2. Click Verify to check the configuration of the script file.
If any error occurs on the configuration, correct the error by referring to Template Verify
Information.
3. You can select Stop Creating in Case of Errors according to the actual requirement.
l If Stop Creating in Case of Errors is selected, the U2000 creates NEs that are
configured correctly but does not create NEs whose configuration information contains
errors or alarms that are detected in the script file when verifying results.
l If Stop Creating in Case of Errors is not selected, the U2000 creates NEs that are
configured correctly and NEs whose configuration information contains alarms but does
not create NEs whose configuration information contains errors that are detected in the
script file when verifying results.
4. Click OK to start creating NEs.
The Create NE Progress dialog box is displayed, showing the progress of NE creation
and results.
5. Click Close to close the Create NE Progress dialog box.
----End
Result
After an NE is created, it is displayed in the topology navigation tree and topology view. At the
same time, the U2000 automatically synchronizes NE configuration data. If the NE is in an
abnormal status, the U2000 displays an NE status icon to the upper-left of the NE icon. Typical
NE status is as follows:
l : indicates the NE and the U2000 server are disconnected. In this case, you need to check
whether the connection between the NE and the U2000 is normal or whether the IP address
of the NE is correctly set.
l : indicates the NE has not been configured or the NE version does not match the mediation
version installed on the U2000 server. In this case, you need to check whether the NE is
correctly configured or whether the matching mediation version is installed.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE management instance of the NEs has been created.
l The function applies to only the routers, switches, and security series NEs.
l The U2000 and the NE must communicate properly. That is, the IP address of the NE must
be correct, and the U2000 and the NE can ping each other.
l SNMP access parameters on the NE must be the same as those in the existing SNMP
parameter template on the U2000.
Context
l If the number of equivalent NEs managed by an NE management instance exceeds the
upper limit, but does not reach the maximum number of NEs that the License permits, it is
recommended that you create another NE management instance before creating NEs. For
details about how to add NE management instances, see section "Adding an Instance" in
the Administrator Guide.
l The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure proper
collection of service performance data. However, SNMPv3 is recommended as it is more
secure than SNMPv2c.
Procedure
l Import NEs in batches.
1. Choose File > Import/Export NE in Batches (traditional style) from the main menu
or select Topo View in Application Center and choose File > Import/Export NE
in Batches (application style) from the main menu.
2. Click Import NE in Batches in the window that is displayed, and configure Root
Path, SNMP Parameter, and Telnet Template.
To make sure that the NEs are created successfully, the SNMP parameter settings need
to be consistent with those on the NEs.
3. Obtain the NE IP address to be imported.
– Import IP Address From File
a. Optional: Click Import > Download Template to download the file
template in Excel and fill with the NE information.
b. Click Import > Import IP Address From File to obtain the IP list from an
Excel file. In the IP Address List area, select the NEs to be imported.
Or manually create an Excel file to fill with the NE information.
By default, U2000 imports data from the second row. The imported excel is shown
as Figure 5-12. The description of the imported excel is shown as Table 5-3.
Area Indicates the path from the main topology to the Optional
Name upper subnet of the subnet where the NEs reside.
For example, the NE is on subnet subnet1/
subnet2/subnet3, and the area name is subnet1/
subnet2.
Alias - Optional
Rema - Optional
rks
NOTE
l If you select Import IP Address From File, but do not configure NE names, NEs are
named with the sysnames.
l In the IP Address List area, double-click or right-click a record, and choose Modify NE
Name from the shortcut menu to modify the name of an NE.
l In the IP Address List area, right-click in the Selection area and choose Select All or
Deselect All from the shortcut menu to select or clear the NEs to be imported.
4. Click Create.
In the Import NE dialog box, the progress bar displays the progress of importing
selected NEs.
The details about the import operation are displayed in the information area under the
progress bar, as shown in the following figure.
5. Click Export Result To File to specify the path and the folder name, and click
Save.
Column Description
Name
6. Click OK to save the information of the imported NEs in batches to the file in a
specified folder.
7. Click Close.
The NEs imported in batches are displayed in the Main Topology.
l Export NEs in batches.
1. Choose File > Import/Export NE in Batches (traditional style) from the main menu
or select Topo View in Application Center and choose File > Import/Export NE
in Batches (application style) from the main menu.
2. Click Export NE in Batches in the window that is displayed, and select All
Records from the drop-down list, or click Filter to set the filtering conditions.
3. Click Save As and set the path and the File Name for the saving. You can export all
the NE information to the file in a specified folder.
The exported file is considered as the backup file of the NE. You can import the backup
file to other NMSs.
----End
Prerequisites
l When creating an NE on the U2000, ensure that the IP address of the NE does not conflict
with the IP address of any existing NE. If the IP addresses conflict with each other, the NE
will fail to be created.
l Before manual ICMP NE creation, disable ICMP packet blocking in the firewall of the
U2000 server, because the ICMP packet blocking interrupts communication between the
U2000 and ICMP NEs.
Context
NOTE
l When an NE is added, mass data is loaded from the NE, and this process takes a certain period (the
default timeout period is 180 seconds). During this period, the GUI does not respond to any other
operations.
l If the new NE is not displayed in the topology view in a long period, refresh the view to check whether
the NE is successfully added.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the WDM NE and OptiX BWS 1600S.
Procedure
Step 1 In the Main Topology, right-click in the blank area and choose New > NE from the shortcut
menu.
Step 2 In the dialog box that is displayed, select an optical NE type for the optical NE .
Step 3 In the Basic Attributes tab, set the attributes of the optical NE.
NOTE
An OEQ NE is an OLA NE that enables the equalization of optical power and dispersion. If an OLA NE
has the boards for dispersion compensation and power compensation, the OLA NE should be changed to
an OEQ NE.
Step 4 Click the Resource Division tab. Select NEs or boards from the Idle ONE and click
.
Step 6 In the Main Topology, click in the blank area and the NE icon appears where you clicked.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l It is applicable to MSTP series, WDM series, WDM (NA) series, RTN series, Marine series
NEs.
l The NE Explorer instance of the NE has been created.
l If the Huawei-predefined certificate is not deployed for NEs, you cannot create the NEs in
Security SSL connection mode directly. You need to create them in Common connection
mode and then load their SSL certificates and change their connection modes to Security
SSL. Otherwise, these NEs cannot communicate with the U2000. Whether the NE is
preconfigured with the Huawei-developed digital certificate, refer to the NE list of 5.6.4
Setting the Security SSL Connection Mode for Transport NEs.
Context
l In the case of tran NEs, the function of creating an NE uses the license for dedicated upgrade
items or the license for NE resources. If there is no remaining license for dedicated upgrade
items or license for NE resources, a message is displayed indicating that NE creation fails.
It is recommended that you apply for a new license for NE resources.
NOTE
l NE licenses will be deducted for NE creation. If NE licenses are insufficient, the U2000 enters
the grace period.
l No operation is limited within the grace period that lasts 60 days. If the grace period ends, NEs
of the same type cannot be created, but the NEs that have been created can still be used. In
addition, users cannot add NEs that have been deleted.
l The grace period ends for the U2000 when you update the service license with a new valid one.
If resources are still insufficient, the start and end time of the grace period are recalculated.
l The U2000 reports ALM-801 OSS License Beyond Limitation when it enters the grace period.
Contact your Huawei engineers for new licenses.
l Before creating a non-gateway NE, you need to create a GNE first.
l For the WDM series NE except for the OptiX OSN 1800, OptiX OSN 1832, OptiX OSN
6800, OptiX OSN 8800 series, OptiX OSN 9800 series, you can 5.6.2.1 Creating Optical
NEs before creating an NE to facilitate management. Otherwise, the new NE is allocated
to an idle optical NE automatically.
l If the NE is not created properly or the communication between the NE and the U2000 is
abnormal, the NE is displayed in gray.
l If you do not know the NE IP address or the correct network segment, use the automatic
IP discovery function to create an NE by entering a correct NE user name and password.
For details, see 5.6.1.1 Creating Transport/PTN NEs in Batches.
l If the number of equivalent NEs managed by an NE management instance exceeds the
upper limit, but does not reach the maximum number of NEs that the License permits, it is
recommended that you create another NE management instance before creating NEs. For
details about how to add NE management instances, see section "Adding an Instance" in
the Administrator Guide.
l Security SSL is recommended because of its higher security than Common. For the NEs
that cannot be created in Security SSL connection mode directly, for details, see 5.6.4
Setting the Security SSL Connection Mode for Transport NEs.
Procedure
Step 1 You can add an NE by using one of the following methods:
l Choose File > New > NE (traditional style) from the main menu or select Topo View in
Application Center and choose File > New > NE (application style) from the main menu.
Step 2 On the Object Type tree of the displayed dialog box, select the NE type of the NE to be created.
For example, add the OptiX 2500 in the product family of SDH series NE. The NE attributes
are shown in the following figure:
NOTE
When you create an NE, its default name is expressed in the NE(extended ID-NE ID) format, such as NE
(9-81).
If the NE of the version does not support the OSI protocol, you cannot create a communication
connection between the U2000 and the NE even if you select the OSI protocol when you create the
NE.
OSI protocol Select OSI from the Protocol drop-down list. Enter the
NSAP Address of the GNE.
NOTE
The NSAP address consists of hexadecimal digits of a maximum of 20 bytes, and is of the
following format: domain address+08003e+NE ID+NSEL. The Domain Address comprises
of 13 bytes and is entered by the user. NSEL is the port number of the network-layer protocol,
with a fixed value of 1d (one byte).
3. Enter the IP address of the NE.
4. Select the connection mode.
NOTE
Step 5 Optional: In the case of a WDM NE, select an optical NE for the WDM NE.
The default NE user is root and the default password is password. For WDM NEs (NA), both the default
user name and the default password are SONET.
Step 7 Optional: If the NE data on the U2000 is not delivered to the NE, select the NE Pre-
configuration check box, and set NE Software Version.
NOTE
l The configuration data of preconfigured NEs is stored only at the NE layer on the U2000 and does not
affect actual configurations on the NEs. Preconfigured NEs are used for large-scale service adjustment
or expansion.
l After an NE is set as a preconfigured NE, the Maintenance Status parameter will be displayed for it
and can be set manually, but the Upload automatically button will not be displayed for it.
l If the configuration data of a preconfigured NE is inconsistent with the configuration data of the actual
NE, delivering the configuration data of the preconfigured NE affects the actual services on the NE.
l The SONET, RTN, NG WDM, WDM (NA), and Marine series NEs do not support NE
preconfiguration.
l The RTN series NEs do not support NE preconfiguration.
Step 8 Select the NE maintenance status, Normal or Maintenance. If Maintenance is selected, the
task will be added to the construction task list and its alarms will be automatically filtered out.
Step 9 Optional: Select the Upload automatically check box to automatically upload NE data after
the NE is created.
Step 11 In the Main Topology, click in the blank area and the NE icon appears where you clicked.
----End
Result
After you create the NE successfully, the system automatically saves the IP address, NSAP
address, subnet mask, and ID of the NE to the U2000 database.
Follow-up Procedure
To prevent unauthorized operations on a new NE, change the default password for the NE user
as soon as possible and subsequently change the non-default password at regular intervals.
If you fail to log in to an NE after creating it, the probable causes are as follows:
l The communication between the U2000 and the NE is abnormal. Check the settings of
communication parameters, such as IP address and ID of the NE.
l The password for the NE user is incorrect. Enter the correct password.
l The NE user is invalid or is already logged in. Specify a valid NE user.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE Explorer instance of the NEs has been created.
l Before creating a non-gateway NE, you need to create a GNE first.
l If the Huawei-predefined certificate is not deployed for NEs, you cannot create the NEs in
Security SSL connection mode directly. You need to create them in Common connection
mode and then load their SSL certificates and change their connection modes to Security
SSL. Otherwise, these NEs cannot communicate with the U2000. Whether the NE is
preconfigured with the Huawei-developed digital certificate, refer to the NE list of 5.6.4
Setting the Security SSL Connection Mode for Transport NEs.
Context
l In the case of PTN NEs, the function of creating an NE uses the license for dedicated
upgrade items or the license for NE resources. If there is no remaining license for dedicated
upgrade items or license for NE resources, a message is displayed indicating that NE
creation fails. It is recommended that you apply for a new license for NE resources.
NOTE
l NE licenses will be deducted for NE creation. If NE licenses are insufficient, the U2000 enters
the grace period.
l No operation is limited within the grace period that lasts 60 days. If the grace period ends, NEs
of the same type cannot be created, but the NEs that have been created can still be used. In
addition, users cannot add NEs that have been deleted.
l The grace period ends for the U2000 when you update the service license with a new valid one.
If resources are still insufficient, the start and end time of the grace period are recalculated.
l The U2000 reports ALM-801 OSS License Beyond Limitation when it enters the grace period.
Contact your Huawei engineers for new licenses.
l If the NE is not created properly or the communication between the NE and the U2000 is
abnormal, the NE is displayed in gray.
l If the number of equivalent NEs managed by an NE management instance exceeds the
upper limit, but does not reach the maximum number of NEs that the License permits, it is
recommended that you create another NE management instance before creating NEs. For
details about how to add NE management instances, see section "Adding an Instance" in
the Administrator Guide.
l Security SSL is recommended because of its higher security than Common. For the NEs
that cannot be created in Security SSL connection mode directly, for details, see 5.6.4
Setting the Security SSL Connection Mode for Transport NEs.
Procedure
Step 1 You can add an NE by using one of the following methods:
l Choose File > New > NE (traditional style) from the main menu or select Topo View in
Application Center and choose File > New > NE (application style) from the main menu.
Step 2 In the dialog that is displayed, select the NE type to be created from the Object Type tree.
For example, add an OptiX PTN 3900 NE in the product family of PTN series NEs. The NE
attributes are shown in the following figure:
NOTE
The default name of a new NE is expressed in the NE(extended ID-NE ID) format, such as NE(9-81).
If the NE of the version does not support the OSI protocol, you cannot create a communication
connection between the U2000 and the NE even if you select the OSI protocol when you create the
NE.
OSI protocol Select OSI from the Protocol drop-down list. Enter the
NSAP Address of the GNE.
NOTE
The NSAP address consists of hexadecimal digits of a maximum of 20 bytes, and is of the
following format: domain address+08003e+NE ID+NSEL. The Domain Address comprises
of 13 bytes and is entered by the user. NSEL is the port number of the network-layer protocol,
with a fixed value of 1d (one byte).
3. Enter the IP address of the NE.
Step 6 Select the NE maintenance status, Normal or Maintenance. If Maintenance is selected, the
task will be added to the construction task list and its alarms will be automatically filtered out.
Step 7 Optional: Select the Upload automatically check box to automatically upload NE data after
the NE is created.
Step 9 In the Main Topology, click in the blank area and the NE icon appears where you clicked.
----End
Result
After an NE is successfully created, the system automatically saves the information, such as the
IP address, NSAP address, subnet mask, and NE ID to the U2000 database.
Follow-up Procedure
To prevent unauthorized operations on a new NE, change the default password for the NE user
as soon as possible and subsequently change the non-default password at regular intervals.
If you fail to log in to the NE after it is created, possible causes are listed as follows:
l The communication between the U2000 and the NE is abnormal. Check the settings of
communication parameters, such as the IP address of the NE and NE ID.
l The password for the NE user is incorrect. Enter the correct password for the NE user.
l The NE user is invalid or the NE user is already logged in. Change to a valid NE user.
Prerequisites
l The NE management instance of the NEs has been created.
l It is applicable to router NEs, such as NE/MA/ME series, CX series and PTN6900 NEs.
l The U2000 communicates with NEs successfully. That is, the IP addresses of NEs are
correct and the U2000 and managed NEs can ping each other.
l SNMP parameters set on U2000 must be the same as those set on the NEs. For details about
configuring SNMP parameters, see 5.5 Setting Parameters for the Communication
Between the U2000 and NEs.
l After an NE (such as NE A) is successfully created at one end of the LLDP link on the
U2000, the LLDP link can be searched in batches and added to the topology view by the
U2000 if the NE (such as NE B) at the other end of the LLDP link meets the following
requirements:
– NE A can be a Huawei NE or a third-party NE, and NE B must be a Huawei NE.
– NE B and NE A can communicate with each other.
– NE B supports LLDP function and the LLDP is enabled on NE B.
– The management IP address in the LLDP configuration is correctly configured on NE
B. Specifically, you can run the lldp management-address command to configure the
IP address of the management port of NE B.
– The SNMP access protocol parameters exist in the existing SNMP parameter profile on
the U2000.
Context
l In the case of router NEs, the function of creating an NE uses the license for dedicated
upgrade items or the license for NE resources. If there is no remaining license for dedicated
upgrade items or license for NE resources, a message is displayed indicating that NE
creation fails. It is recommended that you apply for a new license for NE resources.
NOTE
l NE licenses will be deducted for NE creation. If NE licenses are insufficient, the U2000 enters
the grace period.
l No operation is limited within the grace period that lasts 60 days. If the grace period ends, NEs
of the same type cannot be created, but the NEs that have been created can still be used. In
addition, users cannot add NEs that have been deleted.
l The grace period ends for the U2000 when you update the service license with a new valid one.
If resources are still insufficient, the start and end time of the grace period are recalculated.
l The U2000 reports ALM-801 OSS License Beyond Limitation when it enters the grace period.
Contact your Huawei engineers for new licenses.
l If Telnet parameters are not set during creation of a single NE and the NE management
function needs to be used after the NE is created, you must set the Telnet/STelnet parameters
on the U2000 and NEs. For details, see 5.5.3.2 Setting Telnet/STelnet Parameters with
a Template and 5.5.3.3 Manually Setting Telnet/STelnet Parameters.
l If the number of equivalent NEs managed by an NE management instance exceeds the
upper limit, but does not reach the maximum number of NEs that the License permits, it is
recommended that you create another NE management instance before creating NEs. For
details about how to add NE management instances, see section "Adding an Instance" in
the Administrator Guide.
l The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure proper
collection of service performance data. However, SNMPv3 is recommended as it is more
secure than SNMPv2c.
Procedure
Step 1 You can add an NE by using one of the following methods:
l Choose File > New > NE (traditional style) from the main menu or select Topo View in
Application Center and choose File > New > NE (application style) from the main menu.
Step 2 On the Object Type tree of the dialog box that is displayed, select the NE type of the NE to be
created.
----End
Result
The system automatically saves NE data to the database after the NE is successfully created.
Prerequisites
l The NE management instance of the NEs has been created.
l It is applicable to switch NEs, such as CX200D and S series NEs.
l The U2000 communicates with NEs successfully. That is, the IP addresses of NEs are
correct and the U2000 and managed NEs can ping each other.
l SNMP parameters set on U2000 must be the same as those set on the NEs. For details about
configuring SNMP parameters, see 5.5 Setting Parameters for the Communication
Between the U2000 and NEs.
l After an NE (such as NE A) is successfully created at one end of the LLDP link on the
U2000, the LLDP link can be searched in batches and added to the topology view by the
U2000 if the NE (such as NE B) at the other end of the LLDP link meets the following
requirements:
– NE A can be a Huawei NE or a third-party NE, and NE B must be a Huawei NE.
– NE B and NE A can communicate with each other.
– NE B supports LLDP function and the LLDP is enabled on NE B.
– The management IP address in the LLDP configuration is correctly configured on NE
B. Specifically, you can run the lldp management-address command to configure the
IP address of the management port of NE B.
– The SNMP access protocol parameters exist in the existing SNMP parameter profile on
the U2000.
Context
l In the case of switch NEs, the function of creating an NE uses the license for dedicated
upgrade items or the license for NE resources. If there is no remaining license for dedicated
upgrade items or license for NE resources, a message is displayed indicating that NE
creation fails. It is recommended that you apply for a new license for NE resources.
NOTE
l NE licenses will be deducted for NE creation. If NE licenses are insufficient, the U2000 enters
the grace period.
l No operation is limited within the grace period that lasts 60 days. If the grace period ends, NEs
of the same type cannot be created, but the NEs that have been created can still be used. In
addition, users cannot add NEs that have been deleted.
l The grace period ends for the U2000 when you update the service license with a new valid one.
If resources are still insufficient, the start and end time of the grace period are recalculated.
l The U2000 reports ALM-801 OSS License Beyond Limitation when it enters the grace period.
Contact your Huawei engineers for new licenses.
l If Telnet parameters are not set during creation of a single NE and the NE management
function needs to be used after the NE is created, you must set the Telnet/STelnet parameters
on the U2000 and NEs. For details, see 5.5.3.2 Setting Telnet/STelnet Parameters with
a Template and 5.5.3.3 Manually Setting Telnet/STelnet Parameters.
l If the number of equivalent NEs managed by an NE management instance exceeds the
upper limit, but does not reach the maximum number of NEs that the License permits, it is
recommended that you create another NE management instance before creating NEs. For
details about how to add NE management instances, see section "Adding an Instance" in
the Administrator Guide.
l The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure proper
collection of service performance data. However, SNMPv3 is recommended as it is more
secure than SNMPv2c.
Procedure
Step 1 You can add an NE by using one of the following methods:
l Choose File > New > NE (traditional style) from the main menu or select Topo View in
Application Center and choose File > New > NE (application style) from the main menu.
Step 2 On the Object Type tree of the displayed dialog box, select the NE type of the NE to be created.
----End
Result
The system automatically saves NE data to the database after the NE is successfully created.
Prerequisites
l The NE management instance of the NEs has been created.
l It is applicable to security NEs, such as Eudemon series, USG series, SRG series, EGW
series, SVN series, SIG series, ASG series, NE40E/80E series NEs. Security NEs that fail
to be identified by the U2000 are added as third-party NEs. If the security NEs can be
identified by the U2000, see Manageable Security NE.
l The U2000 communicates with NEs successfully. That is, the IP addresses of NEs are
correct and the U2000 and managed NEs can ping each other.
l The SNMP parameters configured in the SNMP parameter template that already exists on
the U2000 are consistent with the SNMP access protocol parameters configured on NEs.
For details about configuring SNMP parameters, see 5.5 Setting Parameters for the
Communication Between the U2000 and NEs.
Context
l In the case of security NEs, the function of creating an NE uses the license for dedicated
upgrade items or the license for NE resources. If there is no remaining license for dedicated
upgrade items or license for NE resources, a message is displayed indicating that NE
creation fails. It is recommended that you apply for a new license for NE resources.
NOTE
l NE licenses will be deducted for NE creation. If NE licenses are insufficient, the U2000 enters
the grace period.
l No operation is limited within the grace period that lasts 60 days. If the grace period ends, NEs
of the same type cannot be created, but the NEs that have been created can still be used. In
addition, users cannot add NEs that have been deleted.
l The grace period ends for the U2000 when you update the service license with a new valid one.
If resources are still insufficient, the start and end time of the grace period are recalculated.
l The U2000 reports ALM-801 OSS License Beyond Limitation when it enters the grace period.
Contact your Huawei engineers for new licenses.
l If you need to use the NE management function after creating NEs, set the Telnet/STelnet
parameters on the U2000 and NEs. For details, see 5.5.3.2 Setting Telnet/STelnet
Parameters with a Template and 5.5.3.3 Manually Setting Telnet/STelnet
Parameters.
l If the number of equivalent NEs managed by an NE management instance exceeds the
upper limit, but does not reach the maximum number of NEs that the License permits, it is
recommended that you create another NE management instance before creating NEs. For
details about how to add NE management instances, see section "Adding an Instance" in
the Administrator Guide.
l The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure proper
collection of service performance data. However, SNMPv3 is recommended as it is more
secure than SNMPv2c.
Procedure
Step 1 You can add an NE by using one of the following methods:
l Choose File > New > NE (traditional style) from the main menu or select Topo View in
Application Center and choose File > New > NE (application style) from the main menu.
Step 2 On the Object Type tree of the displayed dialog box, select the Security NE.
----End
Result
The system automatically saves NE data to the database after the NE is successfully created.
Prerequisites
The xFTP server must be configured correctly and the xFTP service must be enabled.
Context
l SNMP parameters on the U2000 must be the same as those on the device. These parameters
include the protocol version, read community name, and write community name.
l If a device fails to be added, check whether SNMP parameter settings on the U2000 are
the same as those on the device. For details, see 5.5.2.2 Setting NE SNMP Parameters.
l You need to create a subnet for the NE. Then, other users will see this NE after they log in
to the same server from different clients.
l The U2000 uses SNMPv1, SNMPv2c or SNMPv3 to communicate with NEs to ensure
proper collection of service performance data. However, SNMPv3 is recommended as it is
more secure than SNMPv1 and SNMPv2c.
Procedure
l To add an OLT, do as follows:
1. Add an OLT NE using one of the following methods:
– Choose File > New > NE (traditional style) from the main menu or select Topo
View in Application Center and choose File > New > NE (application style) from
the main menu.
For example, add an MA56OOT in the product family of Access NE. The NE attributes
are shown in the following figure:
4. Click OK.
l To add an MDU, do as follows:
1. In the Main Topology, right-click the OLT to which MDUs are connected in the
Physical Root navigation tree and choose ONU Topology View from the shortcut
menu.
2. In the window that is displayed, choose the target PON port from the navigation tree,
right-click in a blank area of the right pane, and choose New > ONU from the shortcut
menu.
3. In the dialog box that is displayed, set parameters on the Basic Parameters and
Network Management Channel Parameters tabs (An ONU with GPON upstream
ports is used as an example).
4. Click OK.
If the NE icon in the Main Topology is gray or has a gear-shaped sign in the upper
left corner, right-click the NE and choose Synchronize NE Configuration Data from
the shortcut menu.
----End
Result
The system automatically saves NE data to the database after the NE is successfully created.
Context
l Ensure that the SNMP parameters, including the protocol version, read community name,
and write community name, are the same as those on the NE to be created.
l If the NE fails to be created, check whether the SNMP parameter settings on the U2000
are the same as those on the NE. For details, see 5.5.2.2 Setting NE SNMP Parameters.
l The U2000 uses SNMPv1, SNMPv2c or SNMPv3 to communicate with NEs to ensure
proper collection of service performance data. However, SNMPv3 is recommended as it is
more secure than SNMPv1 and SNMPv2c.
Procedure
Step 1 In the Main Topology, right-click and choose New > NE from the shortcut menu.
Step 2 In the dialog box that is displayed, choose the required NE type from the object type navigation
tree.
For example, add an V6 in the product family of BITS. The NE attributes are shown in the
following figure:
If the icon of the new NE is dimmed or a gear-shaped sign is displayed on the upper left corner
of the NE icon in the Main Topology, right-click the NE and choose Synchronize NE
Configuration Data from the shortcut menu to synchronize NE data.
----End
Result
The system automatically saves NE data to the database after the NE is successfully created.
Prerequisites
l This operation is applicable to third-party NEs such as third-party ICMP NEs and SNMP
NEs.
l The common device processes of the U2000 starts successfully.
l The U2000 communicates with SNMP or ICMP NEs successfully. That is, the IP addresses
of NEs are correct and the U2000 and managed NEs can ping each other.
l The SNMP protocol parameters set on the SNMP NE must be the same as those set in the
SNMP parameter profile specified on the U2000.
Procedure
Step 1 You can add an NE by using one of the following methods:
l Choose File > New > NE (traditional style) from the main menu or select Topo View in
Application Center and choose File > New > NE (application style) from the main menu.
Step 2 In the navigation tree of the dialog box that is displayed, choose a subtype of a node with the
NE type as 3rd-Party.
----End
Result
The system automatically saves NE data to the database after the NE is successfully created.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the SDH, PTN, and NG WDM series NEs.
Context
U2000 creates a virtual NE to manage each third-party NE. For virtual NEs, the U2000 can only
display their topological relationships. It cannot monitor alarms or performance and does not
support configuration for these NEs.
Procedure
Step 1 In the Main Topology, right-click in a blank area and choose New > NE from the shortcut menu.
Step 2 In the dialog box that is displayed, choose SDH Series > SDH Virtual NE or PTN Series >
Virtual L2 NE or PTN Series > Virtual L3 NE or PTN Series > Virtual Physical Layer
NE or NG WDM Series > WDM Virtual NE from the Object Type Tree.
Step 5 In the Main Topology, click in the blank area and the NE icon appears where you clicked.
----End
Prerequisites
l It is applicable to NGN NEs, such as SoftX3000, FIXMGW, MiniMGW, MRS6100, and
iGWB.
l The mediation software of connected NEs has been installed.
l Connected NEs communicates with the U2000 server properly.
l You have logged in to the U2000 client.
l You must set parameters for communication between NEs and the U2000 on the NEs before
create NGN NEs. For details, see the step Set parameters for communication between
NEs and the U2000 of 5.11.5 Creating a NGN Network Topology.
Context
The following takes creating SoftX3000 as an example, the operations for creating other NEs
are similar with SoftX3000.
Procedure
Step 1 You can add an NE by using one of the following methods:
l Choose File > New > NE (traditional style) from the main menu or select Topo View in
Application Center and choose File > New > NE (application style) from the main menu.
Step 2 On the Object Type tree of the dialog box that is displayed, choose Core Network Series >
SOFTX3000.
Step 5 The Create NE Progress dialog box is displayed, after the progress reaches 100%, click
Close.
Step 6 Right-click the SoftX3000 and choose Synchronize NE Configuration Data from the shortcut
menu, synchronize the data to the U2000 database.
----End
Result
The system automatically saves NE data to the database after the NE is successfully created.
Prerequisites
l It is applicable to IMS NEs, such as CGPOMU, CSCF, ATS, AIM, MRFP, UGC, CCF,
MEDIAX, ENUM, SPG, OSG, CSE, SE2600, RM, UPCC, and PGM.
l The mediation software of connected NEs has been installed.
l Connected NEs communicates with the U2000 server properly.
l You must set SNMP parameters on the U2000before create IMS NEs. For details, see the
step Create NEs of 5.11.6 Creating an IMS Network Topology.
Context
The IMS NEs are those on the ATCA platforms and SNMP NEs. You can create IMS NEs in
either of the following cases:
l The IMS NEs based on the ATCA platform can be connected to the U2000 through the
automatic searching function of the CGPOMU, the physical devices and resources of these
NEs are uniformly managed by the CGPOMU. The following IMS NEs on the ATCA
platform can be automatically searched for: CSCF, ATS, AIM, MRFP, CCF, MEDIAX,
UGC, ENUM, SPG, OSG, and CSE.
l The SNMP NEs can be created in the topology view.
Procedure
Step 1 Create IMS NEs based on the ATCA platform.
1. You can add an NE by using one of the following methods:
l Choose File > New > NE (traditional style) from the main menu or select Topo View
in Application Center and choose File > New > NE (application style) from the main
menu.
4. Click OK.
5. The Create NE Progress dialog box is displayed, after the progress reaches 100%, click
Close.
6. Right-click the CGPOMU and choose Synchronize NE Configuration Data from the
shortcut menu, synchronize the data to the U2000 database.
NOTE
4. Click OK.
5. The Create NE Progress dialog box is displayed, after the progress reaches 100%, click
Close.
6. Right-click the SE2600 and choose Synchronize NE Configuration Data from the
shortcut menu, synchronize the data to the U2000 database.
----End
Result
The system automatically saves NE data to the database after the NE is successfully created.
Prerequisites
Before scheduled ICMP NE searches, disable ICMP packet blocking in the firewall of the
U2000 server, because the ICMP packet blocking interrupts communication between the
U2000 and ICMP NEs.
Context
l The time discovery supports the SNMP/ICMP NEs.
l SNMP/ICMP NEs include Router series, Switch series, PTN 6900 series, Access series
and Security NEs.
l If you clear Start periodic search, click OK. The U2000 saves only the preset parameters
and does not perform the time discovery.
l The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure proper
collection of service performance data. However, SNMPv3 is recommended as it is more
secure than SNMPv2c.
l Using STelnet is recommended because of its higher security than Telnet.
Procedure
Step 1 Choose File > Discovery > Time Discovery (traditional style) from the main menu or select
Topo View in Application Center and choose File > Discovery > Time Discovery (application
style) from the main menu.
Step 2 Click on the right of NE Type. In the Select NE Types dialog box, select the type of the
NE to be searched for.
Step 3 In the Ping Times spin box, select the times to ping the NE.
Step 4 In the Timeout(s) spin box, select the timeout for the ping operation.
Step 5 In the Layers spin box, select the number of layers you want to search.
Step 6 Click Default SNMP Parameter. In the Set Default SNMP Parameters dialog box, select the
SNMP parameters template used for adapting the searched NEs.
NOTE
The default SNMP parameters template is used for adapting the searched NEs.
Step 7 Optional: Select Name NEs using IP addresses. Then the name of the found NE is its IP
address.
Step 8 Optional: Click Advanced to set the Telnet/STelnet or Netconf protocol template and click
OK.
NOTE
l If the Telnet/STelnet/Netconf settings on the NE are consistent with those in the default Telnet/STelnet/
Netconf template on the U2000, use the default template without clicking Advanced to modify the
template parameters.
l If the Telnet/STelnet/Netconf settings on the NE are inconsistent with those in the default Telnet/
STelnet/Netconf template on the U2000, click Advanced and modify the template parameters
according to the communication parameters on the NE.
l Setting method: Click next to Telnet/STelnet Settings or Netconf Settings in the Set NE
Communication Parameters dialog box. In the Telnet/STelnet Template Management or
NETCONF Template Management dialog box, select an existing template or create a template.
l V8–based NEs support Netconf parameter settings. The Router series, Switch series and Security
NEs supports Telnet/STelnet parameter settings.
Step 9 Click next to Physical Path. In the Select Path of Parent Subnet dialog box, select the
target subnet of the searched NEs. The path of the target subnet is displayed in Path. Click
OK.
Step 10 Click Add. In the IP Address Range dialog box, set the start IP address, end IP address, and
subnet mask of the found NE, and click OK. A new IP address range is added to the IP Address
Range table.
NOTE
The record lists the start IP addresses, end IP address, and subnet mask of the IP network segment to be
searched. If you want to select the IP address range to search the NEs, select Enable.
Step 11 Click Filter to mask the IP addresses of the NEs that you do not want to search.
Step 12 Click Import IP Address to import IP addresses from a local CSV file.
NOTE
l Before importing the IP addresses, save the target Excel file to a CSV file.
l When using an Excel file to plan IP addresses to be imported in the Start IP Address, End IP
Address, and Subnet Mask sequence, you do not need to add any table heading but directly enter the
IP addresses.
l Each row in the Excel file corresponds to an IP address range on the U2000.
Step 13 In the Set Timing Search Parameters dialog box, select Start periodic search. In Start
Time, set the start time for the U2000 Time Discovery.
Step 14 Click OK to save the settings. The U2000 searches the specific IP network segment and NE
type at the specific intervals based on the settings.
----End
5.6.4 Setting the Security SSL Connection Mode for Transport NEs
If the Huawei-predefined certificate is not deployed for NEs, you cannot create the NEs in
Security SSL connection mode directly. You need to create them in Common connection mode
and then load their SSL certificates and change their connection modes to Security SSL.
Otherwise, these NEs cannot communicate with the U2000.This topic describes how to deploy
an SSL certificate for the NEs with no Huawei-predefined certificate and set the NE connection
mode to Security SSL to protect communication between the U2000 and NEs.
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l You must be a user with "NE Software Management Maintainer" authority or higher.
l Confirm whether the NE type and version is below the Table 5-5 shown, if NE version is
not in the Table 5-5, you need to follow the steps to configure and load the SSL certificate
for NEs.
l The NEs has been created with the Common connection mode on the U2000.
Context
The table below lists the NEs for which the Huawei-predefined certificate has been deployed.
When creating an NE on the U2000, you can select the Security SSL connection mode directly.
NE Type NE Version
NE Type NE Version
NOTE
The table above shows the version of mainstream NEs to be delivered. For other NEs, refers to the latest
documents relevant to the NE.
– Data encryption: After a key is negotiated using a handshake protocol, all the transmitted
messages are encrypted using a single-key encryption algorithm.
– Identity authentication: A public key encryption algorithm is used to add signatures to
all the involved communication parties.
– Data integrity guarantee: A hash algorithm is used to generate a digest and Message
Authentication Code (MAC) and add digital signatures to all messages transmitted. This
guarantees the data integrity of the messages.
Operation Guidance
l The U2000 communicates with NEs. The U2000 is on the SSL client side and uses the
client certificate. NEs are on the SSL server side and uses the server certificate. The SSL
certificate for NEs need to be deployed through the U2000.
l The default SSL certificates for the U2000 server and NEs are stored in the following
directory: oss\server\etc\ssl\nemanager\default (Windows); /oss/server/etc/ssl/
nemanager/default (Solaris and SUSE Linux).
– The server.p12 certificate contains the server certificate and key files. The passwords
for encrypting the file and key need to be obtained.
– The trust.cer certificate contains the files issued by the client, server, and upper-layer
system.
NOTE
Users can apply for NE SSL certificates and upload them to the following directory on the U2000
server: oss\server\etc\ssl\nemanager (Windows); /oss/server/etc/ssl/nemanager (Solaris and
SUSE Linux). Users can specify the top directory for storing certificates, for example, oss\server
\etc\ssl\nemanager\user1 (Windows) or /oss/server/etc/ssl/nemanager/user1 (Solaris and SUSE
Linux). For details on how to upload the certificates, see MSuite > Managing Certificate File in
the Administrator Guide.
Procedure
Step 1 Obtain an SSL certificate from an NE.
NOTE
A U2000 server and its NE SSL certificate are used as examples in the following procedure. If you need
to use the SSL certificate applied by yourself, change default in the following description to the name of
the path for storing the uploaded certificates.
1. Copy the trust.cer file in the oss\server\etc\ssl\nemanager\default\trust\PEM path and
rename it as CA.CRT.
2. Copy the server.p12 file in the oss\server\etc\ssl\nemanager\default\keyStore\PFX path
to the oss\server\common\apache\bin path. Then run the following command:
openssl pkcs12 -in server.p12 -out server.cer -nodes
Enter the password (The initial password is Changeme_123) for the server.p12 file and
key as prompted to obtain the server.cer certificate in PEM format.
3. Copy the server.cer file twice and name the copied files CERTNE.CRT and
CERTNE.KEY. Note that the file names use uppercase letters. After the files are copied,
delete the server.cer and server.p12 file.
4. Copy the CA.CRT, CERTNE.CRT, and CERTNE.KEY certificates on the server to the
PC client.
Step 2 Load the NE SSL certificate to the U2000 and activate it.
1. Choose Administration > NE Software Management > Board Software Upgrade
(traditional style) from the main menu or select Fix-Network NE Software
Management in Application Center and choose NE Software Management > Board
Software Upgrade (application style) from the main menu.
NOTE
By default, the DC accounts of NEs are blank, after enter the Board Software Upgrade, the navigator
tree can not automatic filter the NE list of the subnet. You need to configure the DC account of the
NE in the DC Login User Management (Choose Administration > NE Security Management >
NE Login Management (traditional style) from the main menu or select Security Management in
Application Center and choose NE Security > Fix-Network NE > NE Login Management
(application style) from the main menu.) first, then enter the Board Software Upgrade again, the
navigator tree will filter the specific NEs.
2. Right-click a desired NE in the navigation tree and choose Login NE from the shortcut
menu.
NOTE
You can also choose Set Login Account from the shortcut menu and set the other DC account of the
NE in the dialog box that is displayed.
3. Right click the NE and choose Query Board from the shortcut menu. Then board
information about the NE is displayed.
NOTE
It may take a period of time for the board information to display, which is normal.
5. Select the check box before the desired main control board and click to add the
board to the operation list.
6. In the Upgrade Version field, click . The Board software setting window is displayed.
7. Set the software load type to Certificate and click Add Software. The Choose File window
is displayed.
NOTE
You can click Add Software to add multiple files at the same time.
8. In the Choose File dialog box, select the CA.CRT, CERTNE.CRT, and
CERTNE.KEY certificates obtained in step 1.
NOTE
If the file path contains non-alphanumeric characters, you may fail to access the file.
9. In the Board software setting dialog box, click OK. The upgrade software selection is
complete.
10. Select a board in the Operation List, and click Start.
NOTE
During the process, you can click Stop to stop the loading.
11. When the loading is complete, click Activate. The Warning dialog box is displayed.
Confirm whether to activate the software.
12. Click Yes to start activating the software.
13. After the activation, the Operation Result dialog box is displayed indicating that the
activation succeeds. Click Close.
1. Choose Administration > DCN Management (traditional style) from the main menu or
select Fix-Network NE Configuration in Application Center and choose
Administration > DCN Management (application style) from the main menu.
2. In the Filter dialog box, set filter criteria and click OK to filter NEs.
NOTE
The filter criteria have an AND relationship. Retain the default values of the parameters that do not
need to be filtered.
3. Click the GNE tab. In the Filter GNE dialog box, set the GNE query conditions. Click
OK to filter the GNEs.
NOTE
The filter parameters are an AND relationship. Retain the default values of the parameters that do
not need to be filtered.
4. Select the GNE to be modified, right-click and choose Modify GNE from the shortcut
menu.
5. In the Modify GNE dialog box, change the value of Connection Mode (preferred:
SSL) from Common to Security SSL and click OK.
6. In the dialog box that is displayed, set SSL Certificate. Click . In the Select
SSL Certificate dialog box, select the SSL certificate for NEs and click OK.
NOTE
The SSL certificate must be consistent with the path of the certificate obtained in step 1.
7. In the Modify GNE dialog box, click OK. In the warning dialog box that is displayed, click
OK.
NOTICE
This is a potential service affecting operation. Specifically, it may interrupt the
communication between a GNE and the U2000, and the communication between the GNE
and the non-gateway NEs that the GNE manages.
----End
Context
NOTE
The function of Synchronizing NE Configuration Data is applicable to all series NEs. The other functions
of Configuring the NE Data Manually, Replicating the NE Data, Uploading the NE Data, and
Configuring Virtual NE Data are applicable to MSTP series, WDM series, WDM (NA) series, RTN
series, PTN series (except PTN 6900 series) and marine series NEs only.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l For the Router series, Switch series, PTN 6900 series, Access series and Security NEs, the
SNMP and Telnet/STelnet parameters must be correct.
l For the Router series, Switch series, PTN 6900 series, Access series and Security NEs, the
FTP/SFTP/TFTP service has been configured and the xFTP service has been started and
operated.
Context
l When an NE is managed by several U2000s, the NE will fail to be added and the NE
configuration data synchronization will also fail.
l For the NEs that support synchronization and are not unconfigured or preconfigured, the
U2000 displays the inconsistency mark after the scripts of these NEs are imported.
l For the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs, if data on the U2000 is inconsistent with data on
NEs. The sign will be displayed on NE icons.
l For switch series NEs, enable the privilege function and set the privilege level and password
when setting Telnet/STelnet parameters before synchronizing Layer 2 VLAN data.
l NE configuration data synchronization does not synchronize resource information in the
performance monitoring instance. If the resource information needs to be synchronized,
perform resource synchronization in the Performance Monitoring Management window.
NOTE
When data on NEs in the right pane of the Synchronize NE Configuration Data window are being
synchronized:
l You can select NEs in the right pane to synchronize data.
l You can select NEs from the Object Tree to synchronize data.
l You can select NEs from the Main Topology to synchronize data.
l You can stop the data synchronization on one or multiple NEs.
l You can delete NEs only after the data is synchronized.
Procedure
l Method 1
1. Choose Configuration > Sychronize NE Configuration Data (traditional style)
from the main menu or select Fix-Network NE Configuration in Application
Center and choose Configuration > Synchronize NE Configuration Data
(application style) from the main menu.
2. Click Filter. In the dialog box that is displayed, specify the filter criteria and click
OK. The synchronization information meeting the filter criteria is displayed in the
right pane.
NOTE
l You can also choose one or more NEs from the navigation tree and click .
l You can filter synchronization information by specifying the following filter criteria: NE,
NE Type, NE Address, Synchronization Type, Synchronization Status,
Synchronization Result, and Remaining Time. Router, switch, security, and VMF NEs
do not support some filter criteria such as Synchronization Type, Synchronization
Status, Synchronization Result, and Remaining Time.
3. Select one or multiple unsynchronized NEs, click the Synchronize or right-click an
NE and choose Synchronize from the shortcut menu. The U2000 begins to
synchronize the data.
NOTE
l Buttons in the Option column apply to routers, switches, metro service platforms, security
gateways, service interception gateways NEs.
l Click the buttons in the Option column and select the advanced attributes to be
synchronized.
l Data synchronization on access NEs initiated by another client can be stopped temporarily.
l Method 2
NOTE
This method applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
1. In the Main Topology, select an NE that is marked with . Right-click the NE and
choose Synchronize NE Configuration Data from the shortcut menu.
l Method 3
NOTE
This method applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
2. Select one or multiple NEs from the Object Tree and click .
3. Select one or multiple unsynchronized NEs, click the Synchronize or right-click an
NE and choose Synchronize from the shortcut menu.
4. Click OK. The U2000 begins to synchronize the data.
5. Click Close in the Operation Result dialog box.
l Method 4
NOTE
This method applies to the Router series, Switch series and Security NEs.
1. Right-click an NE in the Main Topology and choose NE Explorer from the shortcut
menu.
2. In the NE Explorer, after querying the services information, click the Synchronize
or right-click a record and choose Synchronize from the shortcut menu.
3. Click OK in the Confirm dialog box.
In the Synchronize Feature dialog box, the U2000 begins to synchronize the data.
4. After data synchronization is complete, click Close to exit.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE has been created successfully.
Context
NOTICE
Manual configuration interrupts services on the NE.
Procedure
Step 1 Select the NE whose data you want to configure.
Step 2 Choose Manual Configuration and click Next. The Confirm dialog box is displayed indicating
that manual configuration clears the data on the NE.
Step 3 Click Yes. The Confirm dialog box is displayed indicating that manual configuration interrupts
services on the NE.
Step 5 Optional: If you need to modify the NE Attribute, set NE Name, Equipment Type, NE
Remarks and Shelf Type.
Step 7 Optional: Click Query Logical Information to query the logical boards of the NE.
Step 8 Optional: Click Query Physical Information to query the physical boards of the NE.
NOTE
The Query Logical Information and Query Physical Information operations cannot be performed for
a preconfigured NE.
Verification is to run the verification command. Click Finish to deliver the configuration to NEs and the
basic configuration of the NEs is complete. After the successful verification, the NEs start to work normally.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE type and NE software version of the source NE must be the same as those of the
target NE.
l The NE has been created successfully.
Procedure
Step 1 Select the NE whose data you want to Replicate.
Step 2 Choose Copy NE Data and click Next. The NE Replication dialog box is displayed.
Step 3 Select the NE in the drop-down list and click Start. The Confirm dialog box is displayed
indicating that the replication operation will overwrite all the data of the selected NE.
NOTE
l After the NE data is replicated, only the data on the U2000 is changed, but the data on the NE is not
changed.
l If you select different NE type, the Confirm dialog box is displayed indicating that whether you sure
to force to copy data from different NE type.
l Copying and copied the data of an NE, set to be preconfigured state.
Step 4 Click Yes. The Confirm dialog box is displayed indicating that the replication operation will
result in the U2000 data loss.
Step 5 Click Yes to start the replication. Wait for a few seconds. The Operation Result dialog box is
displayed.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE has been created successfully.
Context
When you upload WDM NE configuration data, fiber data on NEs is automatically uploaded to
the U2000. In the case of fibers that exist on the U2000 only (not on NEs), these fibers are deleted
from the U2000; in the case of fibers that exist on NEs only (not on the U2000), created these
fibers on the U2000.
Procedure
Step 1 Select the NE whose data you want to upload.
Step 2 Choose Upload and click Next. The Confirm dialog box is displayed indicating that the upload
may take a long time.
Step 3 Click Yes to start the upload. The Operation Result dialog box is displayed when the uploading
is completed.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE type and NE software version of the source NE must be the same as those of the
target NE.
l Applies to the SDH, PTN, and NG WDM series NEs.
Context
If a large amount of same NE data needs to be configured, NE data can be configured in batches
to simplify the operation. As a result, the working efficiency is improved. To configure NE data
in batches, copy the specified NE data to one or multiple NEs so that the data of the virtual NEs
is consistent with each other.
NOTE
l Duplicating the NE configuration data leads to the loss of the original data of the target NE on the
U2000 side.
l Data duplication between the virtual NE and non-virtual NE is not supported.
Procedure
l Configure Data Separately:
1. On the Main Topology, double-click an unconfigured NE to display the NE Panel.
2. Right-click the NE Panel and choose Add a New Board.
NOTE
Add a New Board is used to add the board type of the virtual NE. Then add the board according
to the board type.
3. After setting Name, Port Type, Level and Port Number for the board, click OK.
In this case, you can right-click the NE Panel to query the added board type.
4. Right-click the NE slot and choose the board type. Then add the board. After adding
the board, exit from the NE Panel.
l Configure Data in Batches:
1. Choose Configuration > NE Configuration Data Management (traditional style)
from the main menu or select Fix-Network NE Configuration in Application
Center and choose Configuration > NE Configuration Data Management
(application style) from the main menu.
2. Select the source NE and the required virtual NE from the Object Tree, and then click
.
NOTE
The source NE refers to the virtual NE that is configured with the NE data. Its data needs to be
copied to other unconfigured NEs.
3. Select the source NE from the NE list. Right-click it and choose Copy.
4. Select one or multiple target NEs, right-click and choose Paste from the shortcut
menu.
A confirmation dialog box is displayed, indicating that duplicating the NE
configuration data leads to the loss of the original data of the target NE on the
U2000.
5. Click Yes to start the duplication. Wait for several seconds and the Result dialog box
is displayed.
6. Click Close.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l This operation does not apply to the Routers series, Switches series, Security series, and
some MxU series NEs.
l The NE has been created.
Context
The physical boards are the actual boards inserted in the subrack. The logical boards are created
on the U2000 and are saved on the SCC board, but may not exist on the actual NE.
NOTE
The NE panel indicates the mapping relationship between slots on house processing boards and interface
boards. When you click a processing board that is paired with an interface board in the NE panel, the ID
of the slot that houses the mapping interface board is displayed in orange.
Procedure
Step 1 In the Main Topology, double-click the icon of the NE to open the NE Panel.
NOTE
For the optical NE, select the NE to be added in the left pane on the NE Panel after performing the preceding
operation.
Step 3 Optional: For the PTN NE, click the to add physical boards in batches.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NEs and boards must be created.
l A regenerator (REG) is a device that regenerates electrical signals. You must create a REG
before creating a fiber that passes the REG.
l The dynamic port must be created.
Context
l Two-fiber bidirectional links are created for NEs except WDM NEs.
l Normally, single-fiber unidirectional links are created for WDM NEs. Two-fiber
bidirectional links are created to connect to the SDH ports.
l Single-fiber bidirectional links are created to connect to a board where the single-fiber
bidirectional optical module is installed.
NOTE
Fibers can be created between optical ports, between WDM ports, and between optical and WDM ports.
Procedure
l Method 1:
1. Right-click in the Main Topology and choose New > Link from the shortcut menu.
2. In the dialog box that is displayed, choose Fiber/Cable > Fiber from the Object Type
tree.
3. Set Create Ways to Common in the right pane.
4. In the Name text box, enter the name of the fiber.
5. Select the source NE and source port.
NOTE
l You can click next to Source NE. Then the cursor is display as + and you
can click the source NE of the fiber/cable in the Main Topology. In the dialog box that is
displayed, select the source board and source port and click OK. The Create Link dialog
box is displayed. If you select an incorrect source NE, right-click and click OK in the
Coordinate Selection dialog box to exit.
l You can select a source port from the Source NE Shelf-Slot-Board Type-Port drop-down
list.
6. Select the fiber medium type from the Medium Type drop-down list.
7. Select the sink NE and sink port.
NOTE
l You can click next to Sink NE. Then the cursor is display as +, and you can
click the sink NE of the fiber/cable in the Main Topology. In the dialog box that is displayed,
select the sink board and sink port. Click OK. The Create Link dialog box is displayed.
If you select an incorrect sink NE, right-click and click OK in the Coordinate Selection
dialog box to exit.
l You can select a sink port from the Sink NE Shelf-Slot-Board Type-Port drop-down list.
NOTE
If the source and sink NEs are Router series, Switch series and Security NEs, and you have
selected the source and sink ports, the smaller rate among the source and sink port rates is
displayed as the Rate value.
8. In the Create Link dialog box, set the attributes of the fiber.
NOTE
When creating a fiber, the Automatically Allocate IP Address can be set only when ports at
the two ends are both microwave ports, Ethernet ports, or POS ports on PTN NEs.
9. Click OK.
The created fiber is displayed between the source and sink NEs in the Main Topology.
10. For the MSTP series, WDM series, WDM (NA) series, RTN series, Marine series
NEs, right-click the new fiber and choose Detect Link from the shortcut menu.
The Result dialog box is displayed indicating the detection result.
l Method 2:
1. In the Main Topology window, click the shortcut icon . The cursor is displayed
as + in the Main Topology.
2. Click the source NE of the fiber in the Main Topology.
3. In the dialog box that is displayed, select the source board and source port.
4. Click OK. The cursor is displayed as + again in the Main Topology.
5. Click the sink NE of the fiber in the Main Topology.
6. In the dialog box that is displayed, select the sink board and sink port.
7. Click OK. In the Create Fiber/Cable dialog box, set the attributes of the fiber.
8. Click OK.
The created fiber is displayed between the source and sink NEs in the Main Topology.
9. For the MSTP series, WDM series, WDM (NA) series, RTN series, Marine series
NEs, right-click the new fiber and choose Detect Link from the shortcut menu.
The Result dialog box is displayed indicating the detection result.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The optical interfaces of every NE have been connected using fibers.
l The boards of every NE have been created on the U2000.
l Apply to the MSTP series, WDM series, WDM (NA) series, RTN series, Marine series
NEs, but the OptiX OSN 1800 does not support this operation. For details about creating
fibers/cables for PTN NEs automatically, see 5.8.5 Creating Links Automatically.
Context
l If conflicting fibers are found during the creation, delete the conflicting fibers on the
U2000 before you start creating fibers.
l When a fiber between two MSTP NEs passes through a WDM NE, if the normal fiber
between an MSTP NE and a WDM NE has been created on the U2000, the fiber found by
the trail search function is created as a virtual fiber. If the WDM NE is not created on the
U2000, the fiber is created as a normal fiber.
l Fibers that connect two WDM NEs cannot be searched out.
l Two-fiber bidirectional links are created for NEs except WDM NEs.
l Normally, single-fiber unidirectional links are created for WDM NEs. Two-fiber
bidirectional links are created to connect to the SDH ports.
l Single-fiber bidirectional links are created to connect to a board where the single-fiber
bidirectional optical module is installed.
NOTE
For the OptiX OSN 7500 II, fibers between optical ports on PID boards can be automatically discovered,
but there are the following limitations:
1. Only the fibers between optical ports on PID boards can be discovered.
2. The discovery is performed at the NE level. Fibers may be discovered between optical amplifier boards
without fiber connections.
Procedure
Step 1 Choose File > Discovery > Fiber/Cable/Microwave Link (traditional style) from the main
menu or select Topo View in Application Center and choose File > Discovery > Fiber/Cable/
Microwave Link (application style) from the main menu.
Step 2 In the left pane select some ports from one or multiple NEs and click Search to search for the
fibers or cables.
Step 3 Click OK in the dialog box that is displayed. A progress bar is displayed indicating the progress
of the search.
NOTE
l If the Do not search the ports with fibers/cables created on the NMS check box is selected, the
system only searches for the ports that do not have fibers.
l To check if the created fiber is consistent with the actual fiber connection, clear the check box.
l If the Do not search the ports with fibers/cables created on the NMS check box is selected and all
the selected ports have fibers created, the system displays a message indicating that the search field is
null.
Step 4 A dialog box is displayed indicating that the operation is successful. Click Close.
Step 5 To create fibers, select one or multiple fibers from the Physical Fiber/Cable/Microwave
Link List list and click Create Fiber/Cable.
NOTE
l The WDM NEs (NA) do not support the function of conflicting fiber.
l When one or multiple fibers are selected in the Physical Fiber/Cable/Microwave Link List list, fibers
that conflict with the selected fibers, are shown in the Logical Fiber/Cable/Microwave Link List list.
If there is any conflicting fiber, proceed to Step 6 and delete it before creating fibers.
l During fiber creation, if all the selected fibers are in the Already created state, the system displays
the message as follows: No fiber to create.
Step 6 To delete the conflicting fibers, from the Logical Fiber/Cable/Microwave Link List list select
one or multiple fibers whose values are Yes for the Conflict with logical link(Y/N) parameter
in the Misconnected Fiber/Cable/Microwave Link list. Click Delete Fiber/Cable.
----End
Follow-up Procedure
If the information about the fiber/cable that is created through search is incomplete, you can
supplement the information about the fiber/cable by modifying the fiber/cable information.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Boards of each NE have been added on the U2000.
Context
l Two-fiber bidirectional links are created for NEs except WDM NEs.
l Normally, single-fiber unidirectional links are created for WDM NEs. Two-fiber
bidirectional links are created to connect to the SDH ports.
l Single-fiber bidirectional links are created to connect to a board where the single-fiber
bidirectional optical module is installed.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 Click Create, and the Bulk Create Fibers/Cables dialog box is displayed.
NOTE
The NEs adopt the two-fiber bidirectional mode to achieve bidirectional transmission. When the created
fiber connection is single-fiber unidirectional, you need to create another fiber connection in the other
direction.
Step 5 In the Result dialog box, view the operation results. Then, click Close.
Step 7 Click Cancel to complete the settings. The created fiber/cable connections are displayed in the
Fiber/Cable/Microwave Link Information list.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NE has been added to the U2000 and the interface data has been loaded successfully.
l The NE data has been synchronized to the U2000.
l This operation is applicable to the Router series, Switch series and Security NEs, and also
applicable to the SSP series NEs, third-party series NEs, Hybrid MSTP NE, OSN 500/550
NE, RTN series, NG WDM NEs, and PTN series NEs. You can also create links between
cross-domain NEs, for example, RTN 600 series or RTN 900 series NEs and CX 600 series
NEs, or RTN 900 series NEs and PTN 3900 series NEs.
Context
If the created LLDP link is not available, check whether SNMP, mib-view, and Trap are
configured on NEs and whether the global LLDP is enable on the NE or the U2000. For details,
see the topic LLDP Management for each NE Explorer in the topic Security NE Network
Management.
Procedure
l Method 1
1. Right-click in the Main Topology and choose New > Link.
NOTE
You can also click the , select the Link from the drop-down list.
2. In the dialog box that is displayed, choose Link > IP Link or Link > L2 Link or
Link > Dummy Link in the left pane.
3. In the dialog box, select the Network Protocol Type in the right pane.
NOTE
This parameter is displayed only when IP Link or L2 Link has been chosen.
4. In the dialog box, select the Source NE, Source Port, Sink NE, Sink Port in the right
pane.
– Select NE:
Enter a keyword in the text box next to the Content, and select a value from the
fuzzy-matched keyword list.
d. In the Find Object dialog box, click Select. After selecting the NE, click
Close in the dialog box
e. In the Select NE dialog box, click OK.
– Select Port:
NOTE
Enter a keyword in the text box next to the Filter, and select a value from the fuzzy-
matched keyword list.
c. In the Select Port dialog box, click OK.
NOTE
After you specify Source NE, Source Port, Sink NE, and Sink Port, a name is created
automatically in the Link Name field. You can rename the link according to your naming
conventions .
5. Optional: In the dialog box that is displayed, set the Remarks, User Label,
Owner, or Weight in the right pane.
6. Click OK.
The created link appears between the source and sink NEs in the Main Topology.
l Method 2
1. Choose Inventory > Link Management (traditional style) from the main menu or
select Bearer Network Service Configuration in Application Center and choose
Inventory > Link Management (application style) from the main menu.
2. In the Link Management window, click New.
NOTE
Alternatively, right-click in the query area and choose New from the shortcut menu.
3. In the Create Link dialog box, click New, set Link Type and Network Protocol
Type, and specify Source NE, Source Port, Sink NE, and Sink Port.
NOTE
l Network Protocol Type can be set only when Link Type is set to IP Link or L2 Link.
l After you specify Source NE, Source Port, Sink NE and Sink Port, a name is created
automatically in the Link Name text box. You can rename the link according to your
naming habits.
l When specify the Source NE or Sink NE, you can select the NE from the drop-down list
box directly, and you can also enter a keyword and select a value from the fuzzy-matched
keyword list.
l In the Select Port dialog box, set the filter mode, such as Port Name, Port IP, and Port
Alias to search for source or sink ports. Then select the desired source or sink port from
the search result.
4. Optional: Set the Remarks, User Label, Owner, or Weight.
5. Click Apply. In the Operation Result dialog box containing Operation succeeded,
click Close.
The created link is displayed in the query result area of link management.
NOTE
If a fault occurs during the link creation, the cause is displayed in the Operation Result dialog
box. You can rectify the fault based on the cause.
6. In the Create Link dialog box, click Cancel.
----End
newly created network, you can use Search Link function to create network-wide links on the
U2000 after you complete configuration on the U2000. In this way, you can monitor the actual
working state of each link.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l This operation is applicable to the Router series, Switch series and Security NEs, and also
applicable to the SSP series NEs, third-party series NEs, Hybrid MSTP NE, OSN 500/550
NE, RTN series, NG WDM NEs, and PTN series NEs. You can also create links between
cross-domain NEs, for example, RTN 600 series or RTN 900 series NEs and CX 600 series
NEs, or RTN 900 series NEs and PTN 3900 series NEs.
l Frame-shaped PTN V100R002C01 and later versions and case-shaped PTN V100R002C00
and later versions begin to support automatic Layer 2 link search.
l NEs have been created on the U2000 and the interface data have been successfully loaded.
l Perform the following operations for LLDP links:
– Set SNMP parameters on NEs. For details, expand Security NE Network
Management and choose LLDP Management > Configuring an LLDP Service >
Setting Parameters on the Equipment from the nodes for managing NEs.
– Enable the LLDP function on the U2000 for the NEs and related interfaces. For details,
expand Security NE Network Management and choose LLDP Management >
Configuring an LLDP Service > Configuring LLDP Globally and LLDP
Management > Configuring an LLDP Service > Configuring LLDP on
Interfaces from the nodes for managing NEs.
l After an NE (such as NE A) is successfully created at one end of the LLDP link on the
U2000, the LLDP link can be automatically discovered and added to the topology view by
the U2000 if the NE (such as NE B) at the other end of the LLDP link meets the following
requirements:
– NE A can be a Huawei NE or a third-party NE, and NE B must be a Huawei NE.
– NE B and NE A can communicate with each other.
– NE B supports LLDP function and the LLDP is enabled on NE B.
– The management IP address in the LLDP configuration is correctly configured on NE
B. Specifically, you can run the lldp management-address command to configure the
IP address of the management port of NE B.
– SNMP settings used by NE B are included in an existing SNMP profile.
l When the U2000 automatically searches for links whose Type of Borne Network
Protocol is IPv6, the following requirements must be satisfied:
– The NE interfaces are configured with IPv6 addresses.
– IPv6 links exist between NEs.
– The LLDP is enabled on NEs and the SNMP parameters are set correctly.
– The U2000 and its interface feature data are synchronized with NEs.
Context
NOTE
l The U2000 can only automatically discover links on physical ports on NEs, cannot automatically
discover links on logical ports on NEs.
l Delete the IP addresses of the source and sink ports on a side-by-side link before allotting these IP
addresses to other ports. This prevents a failure to discover the new link due to duplicate IP addresses
in one network.
l Links are logic and they cannot present the fiber/cable connections between devices.
Certain links must be imported to the U2000 as fibers/cables for management.
l When the U2000 automatically discovers NEs, it automatically discovers and adds the IP
links, side-by-side links, LLDP links, and PRP links between NEs to the topology view.
For details about links, see Objects in a Topology View.
l The NEs that are configured with the IPv6 protocol and the links that carry the IPv6 protocol
packets are displayed as the nodes that support the IPv4 and IPv6 protocol stacks or only
the IPv6 protocol stack in the topology view.
l When the U2000 client restarts, IP Link and Second Layer Link are automatically
deselected as the link types; therefore, links that were automatically added to the U2000
will not be displayed. If you want to display a type of link, choose View > Display
Setting > Filter from the main menu. In the right pane, choose Link > Type and select the
type.
Procedure
Step 1 Choose File > Discovery > Link (traditional style) from the main menu or select Topo View
in Application Center and choose File > Discovery > Link (application style) from the main
menu.
Step 2 Optional: Above Object Tree on the left, select Do you want to synchronize LLDP data on
the equipment? as required.
NOTE
The Do you want to synchronize LLDP data on the equipment? function is applicable to only the Router
series, Switch series and Security NEs.
Step 3 Select one or multiple NEs from the Object Tree and click .
Step 4 Optional: In the LLDP Status Management dialog box, perform the following operations:
NOTE
l The LLDP Status Management function is applicable to only the Router series and Switch series
NEs.
l If a network does not have the preceding NE, the LLDP Status Management dialog box is not
displayed.
1. Set LLDP Status of the NEs to Open, Click OK.
2. A dialog box is displayed indicating that the operation is successful. Click Close.
3. A dialog box is displayed indicating that It takes 30s before the enabled LLDP takes
effect. Are you sure to perform search? You can make the confirmation according to the
actual situation.
The progress bar shows the operation progress.
Step 5 In the dialog box that indicates the success, click Close. In the window, the search results for
each links are displayed.
Step 6 Optional: You can select Links not exist in the NMS, Links exist in the NMS, or Conflicting
links to view the status of links.
NOTE
l Links not exist in the NMS: The link exists only on NEs and is not created on the U2000.
l Links exist in the NMS: The link exists on both the U2000 and the NEs.
l Conflicting links: The link has certain different data on NEs and the U2000. According to the link
plan, determine whether to adjust the links that are actually connected to the NEs or delete conflicting
links on the U2000 to ensure data consistency between the NEs and U2000. If you need to delete
conflicting links on the U2000, select conflicting links and click Delete Conflicting links.
Step 7 Optional: Double-click the Name of a link whose Status is Not exist. Then change the name
as required.
Step 8 In the window, select one or multiple links whose Status is Not exist and click Create.
The progress bar is displayed indicating the progress of link creation.
Step 9 In the dialog box that prompts the success, click Close.
Step 10 In the Confirm dialog box that prompts Are you sure to import links as fibers/cables, perform
the following operations:
l Click OK in the Confirm dialog box.
1. The Import Link dialog box is displayed, select one or multiple links and do as
follows:
– Click . The selected link is moved to the Selected Link area.
– Click . All links in the Available Link area are moved to the Selected Link
area. This operation is applicable to batch import.
– Click . The selected link is moved to the Available Link area.
– Click . All links in the Selected Link area are moved to the Available Link
area.
NOTE
l For PTN/NE/ATN/CX/RTN series NEs, you can set whether to allot IP address automatic
on the ports of the fiber/cable when importing the fiber/cable.
l For RTN series NEs, because no real fiber exists, you need to perform the following
operations after the IP addresses of the ports at the two ends of a microwave link are
automatically assigned:
1. Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network
Service Configuration in Application Center and choose Inventory > Fiber/Cable/
Microwave Link > Fiber/Cable/Microwave Link Management (application style)
from the main menu.
2. In the Fiber/Cable/Microwave Link Management window, select the previously
imported fiber and click Delete Fiber/Cable.
l If Automatically Allocate IP Address has not been enabled for the source and sink ports
of fibers/cables during import, you can open the Interface Information window in the NE
Explorer to set port IP addresses.
2. Click OK. In the dialog box that prompts the success, click Close.
NOTE
l After you successfully create a link on the U2000, the status of the link is displayed as Exist.
l The created links are displayed in the Link Management area. Navigation path: Choose
Inventory > Link Management (traditional style) from the main menu or select Bearer
Network Service Configuration in Application Center and choose Inventory > Link
Management (application style) from the main menu.
l The imported fibers/cables are displayed in the Fiber/Cable/Microwave Link Management
area. Navigation path: Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/
Microwave Link Management (traditional style) from the main menu or select Bearer Network
Service Configuration in Application Center and choose Inventory > Fiber/Cable/
Microwave Link > Fiber/Cable/Microwave Link Management (application style) from the
main menu.
l Click Cancel in the Confirm dialog box.
NOTE
l After you successfully create a link on the U2000, the status of the link is displayed as Exist.
l The created links are displayed in the Link Management area.
----End
Follow-up Procedure
If you want to import links as fibers/cables after clicking the Cancel in the Import Link
displayed dialog box, you can perform the follow steps:
1. Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main
menu.
2. In the Fiber/Cable/Microwave Link Management area, right-click in a blank area and
choose Import Link from the shortcut menu.
3. In the Import Link dialog box, select one or multiple links and do as follows:
l Click . The selected link is moved to the Selected Link area.
l Click . All links in the Available Link area are moved to the Selected Link area.
This operation is applicable to batch import.
l Click . The selected link is moved to the Available Link area.
l Click . All links in the Selected Link area are moved to the Available Link area.
NOTE
l For PTN/NE/ATN/CX/RTN series NEs, you can set whether to allot IP address automatic on the
ports of the fiber/cable when importing the fiber/cable.
l For RTN series NEs, because no real fiber exists, you need to perform the following operations
after the IP addresses of the ports at the two ends of a microwave link are automatically assigned:
1. Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main
menu.
2. In the Fiber/Cable/Microwave Link Management window, select the previously imported
fiber and click Delete Fiber/Cable.
l If Automatically Allocate IP Address has not been enabled for the source and sink ports of
fibers/cables during import, you can open the Interface Information window in the NE Explorer
to set port IP addresses.
4. Click OK. In the dialog box that prompts the success, click Close. The imported fibers/
cables are displayed in the Fiber/Cable/Microwave Link Management area.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Optical NEs and NEs have been created.
l Line boards that have ports of the same level have been properly created.
l It is applicable to WDM NE.
Context
l Normally, single-fiber unidirectional links are created for WDM NEs. Two-fiber
bidirectional links are created to connect to the SDH ports.
l Boards that require fiber connection are the wavelength conversion, multiplexer,
demultiplexer, and optical amplifier.
l If wavelength pass-through exists, ensure a direct fiber connection from the demultiplexer
to the multiplexer. No cross-connection is allowed.
l Fiber levels consist of WDM (for long fibers) and WDM CORD (for short fibers). Long
fibers usually have custom information.
l Fibers between two FIU s, OLP s, or DCP s are defined as long fibers and their fiber level
is WDM.
l Fibers within an NE or betweens other than FIU, OLP, and DCP s are defined as short
fibers, and their fiber level is WDM CORD.
NOTE
Users can set the fiber level to either WDM CORD or WDM.
Procedure
Step 1 On the NE panel of WDM NEs, click the Signal Flow Diagram tab.
Step 2 In the signal flow diagram, right-click in a blank area and choose Create Fiber from the shortcut
menu. The cursor is displayed as +.
Step 3 Select the source port and click OK. The cursor is displayed as +.
When selecting an incorrect source or sink port, right-click and click Yes in the Object Select dialog box
to exit.
Step 5 In the Create Fiber/Cable dialog box, set the attributes of the fiber.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The corresponding logical board has been created.
l It is applicable to the OptiX OSN 1832, OptiX OSN 3800, OptiX OSN 3800A, OptiX OSN
6800, OptiX OSN 6800A, OptiX OSN 8800 T16, OptiX OSN 8800 T32, OptiX OSN 8800
T64, OptiX OSN 8800 T16(NA), OptiX OSN 8800 T32(NA), OptiX OSN 8800 T64
(NA), OptiX OSN 9800 P16, OptiX OSN 9800 P18, OptiX OSN 9600 P18, OptiX OSN
9600 U32, OptiX OSN 9600 U64 NEs.
Context
Conflicting fibers/cables refer to fibers configured on the NE and U2000 differently. Click
Synchronize and Create Fiber/Cable, and the conflicting fibers/cables are displayed in the
Fiber/Cable on the NE Only and Fiber/Cable on the NMS Only user interfaces. The
conflicting fibers/cables cannot be synchronized between the U2000 and the NE. In this case,
delete the incorrect fibers/cables based on the networking design. After that, click Create Fiber/
Cable to recreate the remaining fibers/cables.
Procedure
Step 1 In the Main Topology, double-click an optical NE, right-click an NE from the Object Tree and
choose NE Explorer from the shortcut menu.
NOTE
For the OptiX OSN 1832, OptiX OSN 3800, OptiX OSN 6800, OptiX OSN 8800 T16, OptiX OSN 8800
T32, OptiX OSN 8800 T64, OptiX OSN 9800 U32, OptiX OSN 9800 U64, OptiX OSN 9800 P16, OptiX
OSN 9800 P18, OptiX OSN 9600 P18, OptiX OSN 9600 U32, OptiX OSN 9600 U64 NEs, you can right-
click an NE in the Main Topology and choose NE Explorer from the shortcut menu.
Step 2 In the NE Explorer, select an NE and choose Function Tree > Configuration > Fiber/Cable
Synchronization.
Step 3 Click Synchronize. In the dialog box that prompts the success, click Close. The data of the
internal fiber connections on the U2000 and that on the NE is displayed.
NOTE
l Synchronized Fiber/Cable: Indicates the fibers/cables that exist on both the U2000 and NE.
l Fiber/Cable on the NE Only: Indicates the fibers/cables that only exist on the NE.
l Fiber/Cable on the NMS Only: Indicates the fibers/cables that exist on only the U2000.
----End
Follow-up Procedure
l If Fiber/Cable on the NE Only or Fiber/Cable on the NMS Only exists, select all the
fibers/cables and click Create Fiber/Cable. The Result dialog box is displayed. Click
Close. The synchronized fibers/cables are displayed in the Synchronized Fiber/Cable list.
l If conflicting fibers/cables exist and you fail to create the fibers/cables, click Delete Fiber/
Cable to delete the incorrect uncreated fibers/cables on the U2000 or NE. Click Create
Fiber/Cable to recreate the remaining fibers/cables.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the MSTP series and RTN series NEs.
l The IF board for each NE has been created on the U2000.
Context
The microwave frequency wireless signals within the frequency range of 300 MHz to 300 GHz
are called microwave signals. The links that transmit microwave signals are called microwave
links.
Procedure
Step 1 Choose File > Discovery > Fiber/Cable/Microwave Link (traditional style) from the main
menu or select Topo View in Application Center and choose File > Discovery > Fiber/Cable/
Microwave Link (application style) from the main menu.
Step 2 In the left pane select IF interfaces for one or multiple NEs and click Search.
Step 3 Click OK in the dialog box that is displayed. A progress bar is displayed showing the progress
of the search.
NOTE
l If you select the Do not search the ports with fibers/cables created on the NMS check box, the
system does not search for the ports at which microwave links are already created.
l If you need to check consistency between the created microwave links and the actual microwave links,
clear this check box.
l If you select this check box and all the selected ports microwave links are created, a dialog box is
displayed after the search is complete, telling that the search domain is empty.
Step 4 After the search is complete, a dialog box is displayed, telling that the operation was successful.
Click Close.
Step 5 In the Physical Fiber/Cable/Microwave Link List list, select one or multiple microwave links.
Click Create Fiber/Cable.
NOTE
l When you select one or multiple microwave links in the Physical Fiber/Cable/Microwave Link
List list, the microwave links that conflict with the selected ones are automatically displayed in the
Logical Fiber/Cable/Microwave Link List list. In this case, refer to Step 6 to delete the conflicting
microwave links before the creation.
l During the creation of microwave links, if the selected links are all in the Already created state, the
system prompts No fiber to create.
Step 6 In the Logical Fiber/Cable/Microwave Link List list, select one or multiple conflicting
microwave links (the Conflict with logical link (Y/N) value of which in the Misconnected
Fiber/Cable/Microwave Link list is displayed as Yes), Click Delete Fiber/Cable.
----End
Subsequent Handling
When the information about the microwave link that is created through search is incomplete,
you can supplement the information about the microwave link by modifying the fiber/cable
information.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the MSTP series, PTN series and RTN series NEs.
l The IF board for each NE has been created on the U2000.
Context
Usually, the microwave frequency wireless signal within the frequency range of 300 MHz to
300 GHz is called a microwave signal. The link that transmits microwave signals is called a
microwave link.
Procedure
l Method 1:
1. Right-click in the Main Topology and choose New > Link from the shortcut menu.
2. In the dialog box that is displayed, choose Fiber/Cable > Microwave Link from the
Object Type tree.
3. In the Name text box, enter the name of the microwave link.
4. Select the source NE and source port.
NOTE
l You can click next to Source NE. Then the cursor is display as + and you
can click the source NE of the fiber/cable in the Main Topology. In the dialog box that is
displayed, select the source board and source port and click OK. The Create Link dialog
box is displayed. If you select an incorrect source NE, right-click and click OK in the
Coordinate Selection dialog box to exit.
l You can select a source port from the Source NE Shelf-Slot-Board Type-Port drop-down
list.
5. Select the sink NE and sink port.
NOTE
l You can click next to Sink NE. Then the cursor is display as +, and you can
click the sink NE of the fiber/cable in the Main Topology. In the dialog box that is displayed,
select the sink board and sink port. Click OK. The Create Link dialog box is displayed.
If you select an incorrect sink NE, right-click and click OK in the Coordinate Selection
dialog box to exit.
l You can select a sink port from the Sink NE Shelf-Slot-Board Type-Port drop-down list.
6. In the Create Link dialog box, set the attributes of the microwave link.
7. Click OK.
The created microwave link is displayed between the source and sink NEs in the Main
Topology.
l Method 2:
1. In the Main Topology window, click the shortcut icon . The cursor is displayed
as + in the Main Topology.
2. Click the source NE of the microwave link in the Main Topology.
3. In the dialog box that is displayed, select the source board and source port.
4. Click OK. The cursor is displayed as + again in the Main Topology.
5. Click the sink NE of the microwave link in the Main Topology.
6. In the dialog box that is displayed, select the sink board and sink port.
7. Click OK. In the Create Fiber/Cable dialog box, set the attributes of the microwave
link.
8. Click OK.
The new microwave link is displayed between the source and sink NEs in the Main
Topology.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
l Method 1:
1. Right-click in the Main Topology and choose New > Link from the shortcut menu.
2. In the dialog box that is displayed, choose Fiber/Cable > Cable from the Object Type
tree.
3. In the Name text box, enter the name of the cable.
4. Select the source NE and source port.
NOTE
l You can click next to Source NE. Then the cursor is display as + and you
can click the source NE of the fiber/cable in the Main Topology. In the dialog box that is
displayed, select the source board and source port and click OK. The Create Link dialog
box is displayed. If you select an incorrect source NE, right-click and click OK in the
Coordinate Selection dialog box to exit.
l You can select a source port from the Source NE Shelf-Slot-Board Type-Port drop-down
list.
5. Select the cable medium type from the Medium Type drop-down list.
6. Select the sink NE and sink port.
NOTE
l You can click next to Sink NE. Then the cursor is display as +, and you can
click the sink NE of the fiber/cable in the Main Topology. In the dialog box that is displayed,
select the sink board and sink port. Click OK. The Create Link dialog box is displayed.
If you select an incorrect sink NE, right-click and click OK in the Coordinate Selection
dialog box to exit.
l You can select a sink port from the Sink NE Shelf-Slot-Board Type-Port drop-down list.
7. In the Create Link dialog box, set the attributes of the cable.
8. Click OK.
The created cable is displayed between the source and sink NEs in the Main Topology.
l Method 2:
1. In the Main Topology window, click the shortcut icon . The cursor is displayed
as + in the Main Topology.
2. Click the source NE of the cable in the Main Topology.
3. In the dialog box that is displayed, select the source board and source port.
4. Click OK. The cursor is displayed as + again in the Main Topology.
5. Click the sink NE of the cable in the Main Topology.
6. In the dialog box that is displayed, select the sink board and sink port.
7. Click OK. In the Create Fiber/Cable dialog box, set the attributes of the cable.
8. Click OK.
The new cable is displayed between the source and sink NEs in the Main Topology.
----End
Follow-up Procedure
If the NEs at the two ends of the DCN (Data Communication Network) communication cables
do not belong to the same subnet, you have to return to the upper-level view of the subnet to
view the created DCN communication cables.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l To create virtual fibers for SDH or PTN NEs with WDM NEs in between, the following
requirements have been met:
– The U2000 manages the SDH, PTN and WDM NE at the same time.
– The source and sink ports of the virtual fibers must be the SDH ports. On the source
and sink ports, there must be two physical fibers that are connected to the WDM NE.
– The source and sink ports of the virtual fibers must be the PTN ports. On the source and
sink ports, there must be two physical fibers that are connected to the WDM NE.
l In a network with MS-OTN boards or a network where MS-OTN boards and common OTN
boards are housed interchangeably, the source and sink ports or either of them must be SDH
virtual ports generated by service mapping.
Context
l In a physical network, WDM NEs exist between SDH or PTN NEs. On the U2000, the
SDH or PTN network is managed separately from the WDM network, that is, there is no
WDM NE between SDH or PTN NEs. You can create virtual fibers between two SDH or
PTN NEs to form a trail for management.
l For SDH NE, the virtual fibers ensure the independence of automatic fiber search and SDH
trail management.
l For WDM NE, when actual fibers change into virtual fibers at the bearer layer, wavelength
management is not affected even if the actual fibers are deleted.
l The virtual fiber does not support the expansion function.
Procedure
l Method 1:
1. In the Main Topology, right-click in a blank area and choose New > Link from the
shortcut menu.
2. In the dialog box that is displayed, choose Fiber/Cable > Virtual Fiber from the
Object Type tree.
3. In the Name text box, enter the name of the virtual fiber.
4. Select the source NE and source port.
NOTE
l You can click next to Source NE. Then the cursor is display as + and you
can click the source NE of the fiber/cable in the Main Topology. In the dialog box that is
displayed, select the source board and source port and click OK. The Create Link dialog
box is displayed. If you select an incorrect source NE, right-click and click OK in the
Coordinate Selection dialog box to exit.
l You can select a source port from the Source NE Shelf-Slot-Board Type-Port drop-down
list.
5. Select the sink NE and sink port.
NOTE
l You can click next to Sink NE. Then the cursor is display as +, and you can
click the sink NE of the fiber/cable in the Main Topology. In the dialog box that is displayed,
select the sink board and sink port. Click OK. The Create Link dialog box is displayed.
If you select an incorrect sink NE, right-click and click OK in the Coordinate Selection
dialog box to exit.
l You can select a sink port from the Sink NE Shelf-Slot-Board Type-Port drop-down list.
6. In the Create Link dialog box, set the attributes of the virtual fiber.
NOTE
When creating a fiber, the Automatically Allocate IP Address can be set only when ports at
the two ends are both microwave ports, Ethernet ports, or POS ports on PTN NEs.
7. Click OK.
The created virtual fiber is displayed between the source and sink NEs in the Main
Topology.
l Method 2:
1. In the Main Topology window, click the shortcut icon . The cursor is displayed
as + in the Main Topology.
2. Click the source NE of the virtual fiber in the Main Topology.
3. In the dialog box that is displayed, select the source board and source port.
4. Click OK. The cursor is displayed as + again in the Main Topology.
5. Click the sink NE of the virtual fiber in the Main Topology.
6. In the dialog box that is displayed, select the sink board and sink port.
7. Click OK. In the Create Fiber/Cable dialog box, set the attributes of the virtual fiber.
8. Click OK.
The created virtual fiber is displayed between the source and sink NEs in the Main
Topology.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
NOTE
Except the method describes in this section, you can search out the actual fiber connections of the equipment
by using the fiber search function, and restore the fiber connection on the U2000. For details, see 5.8.2
Creating Fibers/Cables Automatically.
Procedure
Step 1 Choose Administration > Log Management > Query Operation Logs (traditional style) from
the main menu or select Security Management in Application Center and choose Log
Management > Query Operation Logs (application style) from the main menu.
Step 2 According to the operation user that deletes the fiber and the time, select the corresponding
operation log. Double click the operation log. The Log Details dialog box is displayed.
Step 3 In Log Details, view the information of the source and sink.
Step 4 According to the information of the source and sink, create the fiber again.
NOTE
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l Subnets in the custom view are independent of those in the physical view.
l NEs, subnets, and links in the custom view can be mapped to the corresponding objects in
the physical view or NE list.
l You can create logical subnets in the custom view only. According to the management
requirements, you can map the NEs, subnets, and links created in the physical view to a
logical subnet.
l When an NE is deleted successfully from the custom view, the NE still exists in the
corresponding physical view.
l A user can create a maximum of five custom views.
l When the selected two devices are connected with a link, the link is added to the Selected
Links table.
l Custom views are bound to users. Users can view only the custom views created by
themselves. If a user is deleted, all the custom views created by the user are also deleted.
NOTE
l When you create a custom view, do not select devices in access domain, because they cannot be
configured or managed in custom views.
l You cannot create trails by switching to the Create WDM/SDH/MSTP Trail window from a custom
view on the U2000.
Procedure
Step 1 Choose View > New > View (traditional style) from the main menu or select Topo View in
Application Center and choose File > New > View (application style) from the main menu.
Step 2 In the Create Custom View dialog box, set general properties of the custom view:
1. Click the General tab, and then set the Name and Remarks of the view on the tab.
2. Click Topology. In the Main Topology, click and drag the left mouse button to select the
desired topology objects. Right-click the desired topology objects and choose Select from
the shortcut menu. The icons are displayed for the selected topology objects.
NOTE
l When selecting objects, you can switch the physical view, clock view and custom view to select
objects from them.
l When selecting objects, right-click the NE or link to be cleared and choose Cancel Selection if
you want to clear the selected objects.
After the selection is successful, click Selected Object in the Select Object dialog box to
view the selected topology objects.
3. In the Select Object dialog box, click Finish to finish the selection.
Step 3 In the Create Custom View dialog box, view the object selected in the custom view on the
Selected Nodes and Selected Links tabs.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l The NMS maintenance suite (MSuite) server has been started.
Context
NOTE
The type of the new NE management process must be the same as that of the original overloaded process.
Procedure
l For Router series, Switch series, Security NEs and Access series NEs:
1. Choose Administration > Settings > NE Partition (traditional style) from the main
menu or select Fix-Network NE Configuration in Application Center and choose
Administration > Settings > NE Partition (application style) from the main menu.
2. In the left pane, select a node. The NE name and other information of the node are
displayed in the right pane.
3. In the information area of the right pane, select the NEs to be migrated.
NOTE
You can also locate to an NE partition by using the NE search function to migrate or adjust an
NE. The steps are as follows:
1. Press Ctrl+F in the Main Topology, or choose File > Find from the main menu, or right-
click in the Main Topology, and choose Find from the shortcut menu, or click .
2. Set the search criteria in Search dialog box, and click Search.
3. In the search result list, select the desired NE. Click Locate and choose Locate to NE
Partition. The NE Partition dialog box is displayed and the desired NE is selected by
default.
4. Click Move To in the lower right corner. The NE Transfer dialog box is displayed.
7. Click Close.
l For MSTP, WDM, WDM (NA), RTN, PTN, and submarine series NEs, the procedure is
as follows:
1. Choose Administration > Settings > NE Partition (traditional style) from the main
menu or select Fix-Network NE Configuration in Application Center and choose
Administration > Settings > NE Partition (application style) from the main menu.
2. In the left pane, select a node. The NE name and other information of the node are
displayed in the right pane.
NOTE
You can also locate to an NE partition by using the NE search function to migrate or adjust an
NE. The steps are as follows:
1. Press Ctrl+F in the Main Topology, or choose File > Find from the main menu, or right-
click in the Main Topology, and choose Find from the shortcut menu, or click .
2. Set the search criteria in Search dialog box, and click Search.
3. In the search result list, select the desired NE. Click Locate and choose Locate to NE
Partition. The NE Partition dialog box is displayed and the desired NE is selected by
default.
3. Click Migrate NE in the lower right corner. The Migrate NE dialog box is displayed.
4. Select the NE to be migrated in the Available NEs box and click . If the
selected NE is connected to a gateway NE, a dialog box is displayed advising you to
migrate the GNE and other NEs under the GNE at the same time. Click Yes. Then the
NE is added to the Selected NEs box.
NOTE
l You can search out the NE to be migrated in fuzzy matching mode by entering the NE
name or part of the NE name in the Keywords text box and pressing Enter.
l When migrating an NE that is connected to a GNE, you are advised to migrate the GNE
and other NEs under the GNE at the same time. Allocating a GNE and its affiliated NEs
to the same NE management process facilitates the diagnosis of communication faults
between the U2000 and NEs.
5. Select a record in the Select Target NE Management Process area and click OK.
6. The Move NE dialog box is displayed showing the migration progress. Wait until the
progress reaches 100%.
7. Click Close.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l The NE has been created.
NOTICE
Modifying the NE ID may interrupt NE communication and reset the NE.
Procedure
Step 1 In the Main Topology, right-click an NE and choose NE Explorer from the shortcut menu.
Step 2 In the NE Explorer, select an NE and choose Function Tree > Configuration > NE
Properties.
Step 3 Click Modify NE ID, and the Modify NE ID dialog box is displayed.
Step 4 Enter the New ID and the New Extended ID. Click OK.
Step 5 Click OK in the Warning dialog box.
Step 6 In the Operation Result dialog box, click Close.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 In the topology navigation tree or physical root, right-click an NE and choose Properties from
the shortcut menu.
Step 2 In the Properties dialog box, click the Properties or NE Properties tab. Then, enter a new NE
name, and click Apply.
NOTE
l For Router series, Switch series, PTN 6900 series, Access series and Security NEs, the NE name
contains a maximum of 128 characters. For other NEs, the NE name contains a maximum of 64
characters.
l The NE name can contain digits, letters, Chinese characters, and some special characters.
l Access NEs do not support the following special characters:
!"'[]~$%^&*+=|\{};<>?
l Routers, switches, and PTN 6900 series NEs do not support the following special characters:
@!"'[]\,
l MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except PTN 6900 series) and
marine series NEs support spaces and the following special characters:
/\()-.& @;+
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
NOTICE
l After you change the NE IP address, the communication between the U2000 and the NE is
normal if the IP address of the NE and the IP address of the U2000 server are in the same
network segment. Re-log the NE.
l After you change the NE IP address, the communication between the U2000 and the NE
stops if the IP address of the NE and the IP address of the U2000 server are in different
network segments. In this case, the communication can be restored by setting a new IP address
for the U2000 server in the same IP address subnet segment as the original NE IP address.
Because of the restriction of the SQL database, you must shut down the U2000 client/server,
restart the computer and start the U2000 server/client again after you change the IP address
of the computer.
Procedure
Step 1 In the Main Topology, right-click an NE and choose NE Explorer from the shortcut menu.
Step 2 In the NE Explorer, select an NE and choose Function Tree > Communication >
Communication Parameters.
Step 4 Click Yes in the Confirm dialog boxes that are displayed twice.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 In the Main Topology, right-click an optical NE and choose Properties from the shortcut menu.
Step 2 In the dialog box that is displayed, enter the new optical NE name, and click OK.
NOTE
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l The optical NE or idle optical NE must have the resource.
Context
l This function does not apply to the WDM NEs that have fiber connections in the Main
Topology.
l This function does not apply to the OptiX OSN 9600, OptiX OSN 9800, OptiX OSN 1800V
and OptiX OSN 1832 X8.
Procedure
Step 1 In the Main Topology, right-click an optical NE and choose Properties from the shortcut menu.
Step 2 In the dialog box that is displayed, click the Resource Division tab. In the Available Boards
pane, select the NE or board that you want to add and click to add it to the optical
NE.
Step 3 In the Selected Boards pane, select the NE or board that you want to delete and click
to release it to the idle optical NE.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The preconfigured NE has been created.
l Applies to the SDH, Metro WDM and LH WDM NE.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
Step 3 Select all preconfigured NEs that you want to modify, right-click in the NE Preconfiguration
list and choose No from the shortcut menu.
Step 5 A message is displayed indicating that the operation is successful. Click Close.
Step 6 A dialog box is displayed asking you whether to download the NEs immediately.
l If you want to download the NEs immediately, click Yes, and do step 7.
l If you do not want to download the NEs immediately, click No.
NOTICE
Downloading data of a preconfigured NE applies the NE settings on the U2000 to the physical
NE. If the data is incorrect, this may cause service interruption.
Step 7 A message is displayed indicating that the operation may affect services. Click OK.
Step 8 A message is displayed again indicating that the operation may affect services. Click OK. A
progress bar is displayed.
Step 9 After the download is complete, a message is displayed indicating that the operation is
successful. Click Close.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Right-click the NMS icon in the Main Topology and choose Properties from the shortcut menu.
Step 2 In the NMS Properties dialog box, enter a new NMS name. Click OK.
NOTE
The name of the NMS can contain letters, symbols, and numbers.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 Select one or multiple fibers/cables in the list and click Modify Fiber/Cable.
Step 3 In the Modify Fiber/Cable dialog box, set the Name, Length (km), Designed Attenuation
(EOL), Medium Type, Maintainer and Remarks of fibers/cables as required, and click OK.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
Choose Administration > Settings > Naming Define Rule (traditional style) from the main
menu or select System Management in Application Center and choose Settings > Naming
Define Rule (application style) from the main menu. To view the specified naming rules.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
The information about all the fibers/cables/microwave links is displayed in the Fiber/Cable/
Microwave Link Management window.
Step 2 Right-click one or multiple fibers/cables/microwave links and choose Name by Rule from the
shortcut menu.
The value in the Name field automatically changes according to the configured naming rule.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l The same NE or subnet cannot be pasted to the target subnet.
l You can press and hold Ctrl to select multiple objects at a time.
l Only the Copy, Paste and Copy To operations on NEs are supported.
l You can perform the Copy, Paste and Copy To operations only in the current view.
Procedure
Step 1 Choose View > Main Topology (traditional style) from the main menu or select Topo View in
Application Center and choose Topology > Main Topology (application style) from the main
menu.
Step 2 In the Current View drop-down list box, select a view in which you want to copy an NE, for
example, Physical Root.
You can select multiple NEs to be copied by using the Ctrl key.
Step 4 You can copy the NE to the target subnet by using either of the following methods.
Copying an NE Operations
Using the Copy menu 1. Choose Edit > Copy from the main menu.
2. Switch to the target subnet to which you want paste the
NE. Choose Edit > Paste from the main menu to copy the
object on the clipboard to this subnet.
NOTE
You can also use the shortcut menus Edit > Copy and Edit >
Paste to copy and paste the NE to the subnet.
Using the Copy To menu 1. Choose Edit > Copy to from the main menu.
2. In the Select Path of Parent Subnet dialog box, select
the subnet where you want place the NE. Click OK.
NOTE
You can also use the shortcut menu Edit > Copy To to copy the NE
to the subnet.
NOTE
There is a slight difference between the original and copied NE icons. A small icon is attached to the new
NE icon in the lower left corner, indicating this icon was copied from another icon. The following figure
illustrates an original NE icon of NE40E.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l When you cut and paste an object, the object is copied to the target subnet and deleted from
the source subnet.
l You cannot paste the same NE or subnet to the target subnet.
Procedure
l Change the NE or subnet position in the subnet.
1. Select an NE or subnet in the topology view, and drag it to the new position.
NOTE
If the view is locked, the NE or subnet cannot be moved. To unlock the view. Choose View >
Lock (traditional style) from the main menu or select Topo View in Application Center and
choose View > Lock View (application style) from the main menu. Or click on the toolbar.
in their clients, the new position of topology objects is refreshed on their clients.
l Move an NE or subnet to another subnet.
1. In the topology view, select the object whose position you want to change.
NOTE
To select multiple topology objects, hold the Ctrl key and select topology objects in the
topology navigation tree or topology view.
2. Move the topology object to another subnet by using either of the following methods:
– Choose Edit > Move to (traditional style) from the main menu or select Topo
View in Application Center and choose Edit > Move To (application style) from
the main menu. Or right-click the object and choose Edit > Move To. In the Select
Path of Parent Subnet dialog box, set the path where the object is placed. Click
OK. The topology object is moved to the target subnet and disappears from the
source subnet.
– Choose Edit > Cut (traditional style) from the main menu or select Topo View in
Application Center and choose Edit > Cut (application style) from the main
menu. Or right-click the object and choose Edit > Cut. Switch to the target subnet.
Choose Edit > Paste (traditional style) from the main menu or select Topo
View in Application Center and choose Edit > Paste (application style) from the
main menu. The topology object is moved to the target subnet and disappears from
the source subnet.
----End
Context
l To select multiple NEs, links, and subnets, you can hold down Ctrl to select them in the
topology navigation tree or topology view.
l You can modify the property of a virtual NE in the physical view, such as the name,
coordinates, and memo.
l You can modify the properties of dummy links in the physical view.
l The following uses the operation of modifying properties of a subnet as an example. The
operation is similar to the modification of an NE or a link.
Procedure
Step 1 In the topology navigation tree or physical root, select a subnet to be modified.
Step 2 Right-click the subnet and choose Properties from the shortcut menu.
Step 3 In the Properties dialog box, select a record from the property list on the Subnet tab page.
The parameter setting area in the lower part displays the details about this record.
Step 4 Modify the properties of the subnet, such as the name, coordinates, icon size, icon style and
memo.
----End
Context
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Choose OSS Security > NE Maintenance Information (application style) or
Administration > NMS Security > NE Maintenance Information (traditional style) from the
main menu.
Step 2 In the NE Maintenance Information window, select the required NE and click Display.
Step 3 In the NE Maintenance Information dialog box, set the following information:
l To set the location information, do as follows:
In the Location Information group box, set the NE location information.
l To set the maintenance personnel information, do as follows:
In the Maintenance Personnel Information group box, click Personnel Information. In
the displayed NE Personnel Information dialog box, set Maintainer, Company,
Phone, Email. For details, see 5.9.4 Setting the Maintenance Personnel Information.
----End
Context
You are not recommended to name a maintenance personnel All.
Procedure
Step 1 Choose OSS Security > Maintenance Personnel Information (application style) or
Administration > NMS Security > Maintenance Personnel Information (traditional style)
from the main menu.
Step 2 In the Maintenance Personnel Information dialog box, set the maintenance personnel
information.
Add the maintenance Click Add. Set the parameters in the parameter setting area
personnel information at the bottom of the dialog box. Click OK. The new
maintenance personnel information is displayed in the
information list.
Delete the maintenance In the maintenance personnel information list, select the
personnel information information to be deleted, and then click Delete. In the
displayed confirm dialog box, click Yes.
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
----End
Context
The root node in the topology navigation tree and the local NMS cannot be deleted.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
Deleting a subnet cannot delete the objects of this subnet. The objects automatically move to
the upper layer.
Procedure
Step 1 Right-click the subnet in the Main Topology, and choose the Delete shortcut menu.
Step 2 In the Confirm dialog box, click Yes to delete the subnet.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l This operation is not applicable to the Router series, Switch series and Security NEs and
some MxU series NEs.
l The services and protection groups of the boards has been deleted.
Procedure
Step 1 Double-click an NE to open the NE Panel.
Step 2 Right-click the desired board and choose Delete from the shortcut menu.
NOTE
When you delete the board, the inactive NE-level optical cross-connections are also deleted.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l Before deleting the sub-board, delete fibers/cables connected to the sub-board, and make
sure that the sub-board is in the idle state.
l Applies to the MP1 and CXP boards of PTN series NEs and the PTD boards of NG WDM
NEs.
Procedure
Step 1 Double-click an NE in the Main Topology and the NE Panel is displayed in the user interface.
Step 2 Right-click the sub-board to be deleted and choose Delete from the shortcut menu. A dialog box
is displayed. Click Yes.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The inventory management process InventoryDM is enabled before fibers/cables are
deleted. You can log in to the System Monitor client to check the running status of this
process.
Context
NOTICE
l The deletion of fibers/cables will lead to the deletion of related protection subnets, trails and
customer information. Exercise caution before you delete fibers/cables. You can export the
script of the entire network first to avoid deletion by mistake.
l The U2000 cannot delete automatically discovered links.
Procedure
l Delete the fibers/cables/microwave links between NEs.
1. Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave
Link Management (traditional style) from the main menu or select Bearer Network
Service Configuration in Application Center and choose Inventory > Fiber/Cable/
Microwave Link > Fiber/Cable/Microwave Link Management (application style)
from the main menu.
2. Right-click the desired fibers/cables/microwave links and choose Delete Fiber/
Cable from the shortcut menu. The Warning dialog box is displayed. Click OK to
delete the fibers/cables/microwave links.
3. In the Result dialog box, click Close.
l Delete the links between NEs.
1. Choose Inventory > Link Management (traditional style) from the main menu or
select Bearer Network Service Configuration in Application Center and choose
Inventory > Link Management (application style) from the main menu.
2. Right-click the desired link and choose Delete from the shortcut menu. The
Confirm dialog box is displayed. Click Yes to delete the link.
3. In the Result dialog box, click Close.
l Delete the connections between the U2000 and NEs.
1. In the Main Topology, right-click the desired connection and choose Delete from the
shortcut menu.
NOTE
The Ethernet Line or Serial Port Line connections are created between the U2000 and NEs.
----End
Prerequisites
You are an NMS user with Maintenance Group authority or higher.
Context
l If you delete an NE, all the related NE nodes generated after you copy the NE are deleted.
If you delete an NE node generated by the NE that you have copied, only this related NE
node is deleted, and the source NE node and the other related NE nodes are not deleted.
l When the NE is not logged in, you can delete the NE on the U2000.
l In the case of switch and router NEs, the function of deleting an NE uses the license for
dedicated upgrade items or the license for NE resources. If the sum of the returned license
and the remaining license exceeds the limit in the license for dedicated upgrade items or
the license for NE resources, a message is displayed indicating that NE deletion fails. It is
recommended that you apply for a new license for NE resources.
l Deleting an OLT NEs, all ONUs under an OLT are deleted, and all user-defined attributes
are discarded.
NOTICE
l For Router series, Switch series, PTN 6900 series, Access series and Security NEs, the
connections associated with the deleted NEs are also deleted.
l For MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except PTN
6900 series) and marine series NEs, you must delete the links, fibers, and services associated
with the NEs before the NEs are deleted.
Procedure
l Delete a single NE.
1. Right-click the NE in the Main Topology and choose Delete from the shortcut menu.
2. The Confirm dialog box is displayed, and click Yes.
3. In the operation result dialog box, click Close.
l Delete NEs in batches.
NOTE
Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except PTN
6900 series) and marine series NEs.
1. Choose Configuration > NE Configuration Data Management (traditional style)
from the main menu or select Fix-Network NE Configuration in Application
Center and choose Configuration > NE Configuration Data Management
(application style) from the main menu.
2. In the left pane, select multiple NEs and click . The NE Configuration pane
displays the configuration data of all the selected NEs.
3. Right-click the desired NEs and choose Delete from the shortcut menu.
4. The Confirm dialog box is displayed, and click Yes.
5. In the operation result dialog box, click Close.
NOTE
When bulk deleting transport NEs on a Solaris-based server in an HA system, pay attention to the
following rules:
l If the active/standby replication bandwidth is 2 Mbit/s, storage replicator log (SRL) overflow
will not occur due to slow data synchronization.
l If the active/standby replication bandwidth is 4 Mbit/s, SRL overflow will occur due to fast data
synchronization. Therefore, you are advised to delete a maximum of 10 NEs at a time and perform
bulk NE deletion every 30 minutes.
l If the active/standby replication bandwidth is 10 Mbit/s or more, there is no limit on the number
of deleted NEs at a time.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the WDM series NEs.
Context
NOTE
After the optical NE is deleted, the OptiX OSN 1800 V, OptiX OSN 3800, OptiX OSN 1800, OptiX OSN
1832, OptiX OSN 6800, OptiX OSN 8800 series, OptiX OSN 9800 series, OptiX OSN 9600 series are
divided to the Main Topology, all the other NEs of WDM series are moved to an idle optical NE.
Procedure
Step 1 Right-click an optical NE in the Main Topology and choose Delete from the shortcut menu.
Step 3 The Deletion Result dialog box is displayed, and click Close.
----End
Context
l If you search for NEs in the Physical Root or Clock View navigation tree in the Main
Topology, the search operation applies to the current view.
l If you search for NEs in the window outside the Main Topology, the search operation
applies to the Physical Root navigation tree.
l You can search out only the NEs for which you have management rights.
l During NE search, the U2000 searches for NEs in dynamic and fuzzy matching mode. That
is, the Search window displays search results in real time as you specify the search criteria.
l Transport NEs can be also searched out in Remarks mode.
Procedure
Step 1 Choose File > Find (traditional style) from the main menu or select Topo View in Application
Center and choose Topology > Search (application style) from the main menu.
The Search dialog box is displayed.
NOTE
You can also perform he following operations to access the Search dialog box.
l Press Ctrl+F in the Main Topology.
l Right-click in the Main Topology, and choose Find from the shortcut menu.
l Click .
Step 2 Select the search criteria, which are Search Type and Search Mode.
Step 3 Enter a keyword in the Keyword combo box or choose a keyword record from the drop-down
list.
Step 4 Optional: You can select Match whole word only, Case Sensitive or Auto search with
specified keyword as required.
NOTE
l Match whole word only: If you select this check box, only the results that exactly meet the conditions
are displayed.
l Case Sensitive: If you select this check box, the keyword is case-sensitive during search.
l Auto search with specified keyword: If you select this check box, when you enter the keyword, the
result is displayed dynamically.
Step 7 Optional: Select the Minimized after locating check box, the Search window is minimized
after the location.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l A connection exists in the Main Topology of the U2000.
Context
The U2000 automatically refreshes the statuses of connections in the Main Topology in real
time. When the O&M status of the port on a Huawei NE or third-party SNMP NE changes, you
can view the changes of the colors of the connections relevant to the port in the Main Topology
to learn the statuses of the connections. For example, if the color of a connection turns red,
critical alarms, such as R_LOS and Linkdown, arise on the ports at both ends of the connection
or on the connection. You need to immediately identify and resolve the problem because such
alarms may interrupt services. Alternatively, the data on NEs and the U2000 is inconsistent with
each other and you need to synchronize it.
NOTE
After you associate alarms with fibers by using the U2000, the statuses of the fibers change accordingly
in the Main Topology when theU2000 receives the associated alarms. To view or set associations between
alarms and fibers: Choose Fault > Correlation Analysis > Fiber Relating Alarm (traditional style) from
the main menu or select Fault Management in Application Center and choose Alarm Diagnosis >
Correlation Analysis > Fiber Relating Alarm (application style) from the main menu. For details, see
7.5.12 Configuring Fiber-Related Alarms.
A virtual NE is an abstraction of an NE or a network that cannot be directly managed by the U2000. When
fibers between NEs and virtual NEs are broken, no alarm is reported. You need to check the actual devices.
Procedure
Step 1 In the Main Topology, you can view the connections between NEs and connection status.
NOTE
If no connections are displayed in the Main Topology, click on the toolbar. On the Filter tab, select
the connections to be displayed, as shown in Figure 5-13. You can click the Legend tab to view the
meanings of topological icons and colors.
Step 2 In the Main Topology, double-click a required connection. In the dialog box that is displayed,
view the attributes of the connection, such as the name, type, end A node, and end Z node.
NOTE
To query the details of relevant alarms, right-click a connection in the Main Topology and choose Query
Relevant Alarms or Browse Current Alarms from the shortcut menu.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Information about all the fibers/cables/microwave links is displayed in the Fiber/Cable/
Microwave Link Management window.
Step 2 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 3 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l Applies to MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
The information about all the fibers/cables is displayed in the Fiber/Cable/Microwave Link
Management window.
Step 2 Right-click a fiber/cable in the pane and choose Browse Relevant Trails from the shortcut
menu.
Trails that the fiber/cable carries are displayed in the trail management window.
Step 3 Optional: Click Print. After setting the range in the window displayed, you can set parameter
for the printing in the Print dialog box.
Step 4 Optional: Click Save As. After setting the range in the window displayed, you can save the
information about the trail within the specified range as a file.
NOTE
The trail information can be saved as a .xls, .txt, .html, or .csv file.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l It is applicable to PTN 6900 series NEs running VRP 5.0 or later, MSTP series, WDM
series, RTN series, PTN series, NE series, CX series, ATN series and ME series NEs.
Context
If the fibers/cables color turned to red which is in the Main Topology, that is because the fibers/
cables had R_LOS, MUT_LOS, ETH_LOS alarm.
Procedure
Step 1 On the Main Topology or a subnet topology, right-click a fiber/cable. Choose Query Relevant
Optical Power from the shortcut menu.
Step 2 Click the Port Optical Power tab on the Optical Power Management window.
The input and output optical power of fiber/cable ports are displayed in the upper pane and the
fiber/cable connection is displayed in the lower pane.
NOTE
On the Port Optical Power tab, the signal flow of fiber/cable helps you quickly view boards with improper
optical power.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l A microwave link has been configured on the U2000.
l The source and sink NEs of a microwave link must work in the normal state.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 In the Fiber/Cable/Microwave Link Management window , right-click a microwave link and
choose Microwave Link Performance Statistics from the shortcut menu.
NOTE
Alternatively, you can right-click a microwave link in the Main Topology and choose Microwave Link
Performance Statistics from the shortcut menu.
Step 3 Click Query in the Microwave Link Performance Statistics dialog box. You can view the
performance statistics of the microwave link in a chart.
NOTE
If the performance monitoring function is disabled on the sink and source NEs of a microwave link, the
system will display an error message and prompt you to enable the function before starting the performance
measurement jobs.
Step 4 Optional: Set Monitor Period to the desired time for collecting performance statistics about
microwave links.
NOTE
If you set invalid query conditions, for example, the start time is later than the end time, the system will
prompt you to modify the conditions.
Step 5 Optional: Set the performance parameters about microwave links in the Options area to query
the diagrams for different statistics items.
Step 6 Optional: Click Print or Save as to print or save the queried performance data diagram.
----End
Prerequisites
In the Topology Filter navigation tree, Background is selected. If Background is deselected,
you need to set the background. For details, see Displaying the Filtered Topology View.
Context
l On the U2000, only image files in .gif or .jpg format can be imported, and the file size
cannot exceed 1 MB.
l Container NEs refer to multi-subrack devices on a network. NEs in a container NE refer to
boards in subracks of a multi-subrack device. If a subrack of a multi-subrack device has
multiple boards, the subrack is also a container NE. This indicates that container NEs.
Container NEs provide the same functions as those provided by subnets and common NEs
except the following:
– Differences between container NEs and subnets:
– NEs in container NEs cannot be moved in or out, but NEs in subnets can be moved
in or out.
– A container NE can generate alarms. The alarm status display mode for a container
NE is the same as that for an NE. When an NE in a container NE generates an alarm,
an alarm icon appears on the container NE in the topology view. For details, see
Icons Indicating That Alarms Are Contained.
– A subnet does not generate alarms. However, when the NEs or links in the subnet
generate alarms, the subnet displays the alarms of the highest severity. The alarm
display mode for subnets is the same as that for NEs.
– Differences between container NEs and common NEs: Container NEs provide some
functions of subnets, but common NEs do not.
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 Choose Topology > Set Background (application style) or View > Set Background (traditional
style) from the main menu or right-click the topology view and choose Set Background from
the shortcut menu.
Step 3 In the Set Background dialog box, select a subnet or container NE in the table on the left, and
click Select Background.
Step 4 In the Select Background dialog box, select the image to be used as a background, and click
Open.
NOTE
To cancel the background setting, click Set Blank Background in the Set Background dialog box.
----End
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 In the Current View drop-down list, select the view that you want to browse. The current view
is switched to the selected view.
----End
Context
l The topology view displays the objects selected in the Topology Filter navigation tree,
such as subnets, NEs, background images.
l When the U2000 is started, the filter criteria are blank by default, and all the topology
objects are displayed.
l When you deselect a filter criterion, the objects matching the criterion are not displayed.
l Parent nodes in the Topology Filter navigation tree have three types of icons. indicates
that some topology filter items under a parent nodes are selected; indicates none of the
topology filter items under a parent nodes is selected; indicates that all topology filter
items under this node are not displayed in the topology view.
l Modified topology filter criteria take effect for the current user only. After this user logs
in next time, the settings still take effect.
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 Choose View > Show > Filter (application style) or View > Display Setting > Filter (traditional
style) from the main menu, or click on the toolbar. Click the Filter tab in the right pane.
Step 3 In the Topology Filter navigation tree, select the topology objects to be displayed in the topology
view.
NOTE
l Topology objects that are not selected are unavailable in the topology view.
l Click Other Conditions. In the displayed panel, specify the values for NE Name, Link Name, or
Subnet Name, and click Filter to filter objects again. The NEs, links, or subnets containing this string
(case insensitive) are displayed.
After the operations are successful, current view displays topology objects based on the filter
criteria.
Step 4 Optional: Click Filter Tree and select Switch. In the Switch a Filter Tree dialog box, select
the filter tree template, and click Open.
NOTE
Filter tree templates displayed in the Switch a Filter Tree dialog box indicate that filter trees have been
used and saved as filter tree templates. If no filter tree has been saved, no filter tree template is available
in the dialog box. To save a filter tree as a template, click Filter Tree and choose Save As. In the displayed
dialog box, enter a template name and click OK.
Step 5 Optional: To close the Legend/Filter/Properties panel, choose View > Show > Filter
(application style) or View > Display Setting > Filter (traditional style) from the main menu,
or click on the toolbar.
----End
Procedure
Step 1 Choose View > Show > Legend (application style) or View > Display Setting > Legend
(traditional style) from the main menu. Alternatively, click .
The Legend/Filter/Properties panel is displayed in the right pane of the topology view.
Step 2 In the Legend/Filter/Properties panel, click the Legend tab, and view the legend and its
description.
----End
Context
The following uses the operations of viewing NE information as an example. The operations of
viewing link and subnet information are similar to these operations.
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 In the topology navigation tree or topology view, select the NE to be viewed.
Step 3 Choose View > Show > Properties (application style) or View > Display Setting > Property
(traditional style) from the main menu, or click on the toolbar. Click the Properties tab in
the right pane.
If alarms are generated on the topology objects, the alarm information displayed on the
Properties tab page is the same as that configured in 1.8.14 Setting the Alarm Display in the
Topology View.
NOTE
You can also right-click an object in the topology navigation tree or topology view and choose
Properties from the shortcut menu. Then view the parent subnet, coordinates, icon size, and icon type
about the NE in the Properties dialog box.
----End
Context
The resolution is determined by the screen size of the client, and is not always 1024 x 768 pixels.
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 Choose View > Show > Overview (application style) or View > Display Setting > Aerial
View (traditional style) from the main menu or click on the toolbar.
The Overview window is displayed. The rectangle area is visible in the current view.
Step 3 In the Overview window, drag the rectangle area to change the visible area of the current view.
NOTE
When you switch to another topology view, the Overview window is closed.
----End
Procedure
l Four methods to zoom in the topology view:
– On the topology toolbar, click . In the topology view, drag the mouse to generate a
rectangle. Topology objects in this rectangle are magnified.
l Three methods to zoom out the topology view:
On the topology toolbar, click the drop-down list to change the size of the
topology view.
----End
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 In the topology view, double-click the subnet you want to access.
The topology view is switched to the selected subnet, and displays the topology structure of the
subnet.
Step 3 Choose View > Back to Parent (application style) or View > Up (traditional style) from the
main menu or click on the toolbar to switch to the parent subnet.
----End
Result
The topology view is switched to the parent subnet of the current subnet, and displays the
topology structure of the parent subnet.
Context
NOTE
Topology objects in the navigation tree are sorted according to the following rules:
l No matter whether topology objects are sorted in ascending or descending order, the order of the types
of topology objects is unchanged, namely, OSS, subnets, NEs with subnodes, and NEs without
subnodes. The OSS is always displayed on the top.
l Each type of topology objects are sorted by name in alphabetical order. Object names are case
insensitive.
Procedure
l On the toolbar, click .
Each type of topology objects in the navigation tree are sorted by name in ascending
alphabetic order.
Context
The settings in the Set My Topology dialog box are saved on the server, and are valid to the
current user only.
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 Choose Topology > Set My Topology (application style) or View > Set My Topology
(traditional style) from the main menu.
Step 3 In the Set My Topology dialog box, set the subnet to be displayed when the U2000 is started,
and click OK.
NOTE
In addition, you can right-click a subnet in the navigation tree or topology view, and choose Set to My
Topology from the shortcut menu. The selected subnet is the one to be displayed when the U2000 is started.
----End
Result
After the current subnet is set to the startup subnet, this subnet is displayed upon the next login
to the U2000.
Prerequisite
l You are an NMS user with Operator Group authority or higher.
l The U2000 can communicate with NEs using the TCP/IP protocol and can manage and
maintain the NEs.
Context
To meet service growth requirements, an operator bought one OptiX OSN 1500, two OptiX
OSN 3500s, and one OptiX OSN 7500. These devices have been installed and commissioned
on the network. To manage these devices on the U2000, administrators need to create a transport
network topology for them on the U2000.
Networking diagram
The networking diagram below shows a transport ring network consisting of the OptiX OSN
1500, OptiX OSN 3500s, and OptiX OSN 7500 in a subnet (subnet SZA).
NE(9-501) NE(9-4)
NE(9-7)
Data Plan
l Data plan 1
l Data plan 2
Provincial
backbone
fiber [NE Dual- 11-
(9-7)-NE fiber N4SLQ1 4-
(9-501)] bidirect 6-2 NE N2SLQ16-
F003/fiber STM-16 ional NE(9-7) (SDH-2) (9-501) 2(SDH-2)
Provincial
backbone
fiber [NE Dual- 11-
(9-7)-NE fiber N4SLQ1 5-
(9-4)] F004/ bidirect 6-1 N1SLQ16-
fiber STM-16 ional NE(9-7) (SDH-1) NE(9-4) 1(SDH-1)
Provincial
backbone
fiber [NE Dual- 4-
(9-501)-NE fiber N2SLQ1 12-
(9-19)] bidirect NE 6-1 N4SL16-1
F005/fiber STM-16 ional (9-501) (SDH-1) NE(9-19) (SDH-1)
Provincial
backbone
fiber [NE Dual-
(9-19)-NE fiber 4-
(9-4)] F006/ bidirect NE Q1SL4-1 4-N1SL4-1
fiber STM-4 ional (9-19) (SDH-1) NE(9-4) (SDH-1)
Process
No. Step Description
5.6 Creating NEs Create NEs on the U2000 for actual devices.
Each NE on the U2000 represents an actual
device. You can create NEs in two ways: 5.6.2.2
Creating a Single Transport NE or 5.6.1.1
Creating Transport/PTN NEs in Batches. If a
3 large number of NEs need to be created (for
example, in a deployment scenario), 5.6.1.1
Creating Transport/PTN NEs in Batches is
recommended. If only a few NEs need to be
created, 5.6.2.2 Creating a Single Transport
NE is recommended.
4 5.7 Configuring the NE Data Configure NE data. After being created on the
U2000, NEs are in the unconfigured state. The
U2000 can manage the NEs only after the NEs
are configured.
Procedure
Step 1 Design the physical topology.
l In addition to showing the actual network topology, the physical topology should also
facilitate routine O&M. Allocate all these new NEs into subnet SZA because they are in the
same area.
l Ensure that subnet SZA contains fewer than 300 NEs so that NE icons are displayed
separately from each other and NEs are easy to find.
Skip this step if a subnet has been created for this area.
By default, the U2000 names a new NE in the format of NE(Extended ID-NE ID), for example, NE
(9-7).
The procedure provided below is used to configure NEs manually. NE configuration can also be completed
by synchronizing, copying, or uploading NE data.
1. Double-click subnet SZA. In subnet SZA, double-click NE(9-7).
2. In the NE Configuration Wizard dialog box, select Manual Configuration and click
Next.
3. In the Confirm dialog box informing you that manual configuration will delete data on the
NE, click OK.
4. In the Confirm dialog box informing you that manual configuration will interrupt services
on the NE, click OK.
5. In the Set NE Attribute dialog box, click Next.
6. In the dialog box that is displayed, right-click a slot to install an N4SLQ16 board that will
be used to create a fiber.
7. Click Next.
8. In the Send Configuration dialog box, select Verify and Run and click Finish.
9. Repeat steps a-h to configure other NEs.
The procedure provided below is used to create a fiber manually. Fibers can also be created automatically.
----End
Result
The four NEs and a fiber are successfully created in subnet SZA. You can double-click subnet
SZA to view the NEs and fiber.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
To meet service growth requirements, an operator bought two ATN 910s and two CX600-X3s.
To manage these devices on the U2000, administrators need to create an IP network topology
for them on the U2000.
Networking Diagram
The networking diagram below shows an IP ring network consisting of the ATN 910s and
CX600-X3s.
CX 600 -X3 -2
Data Plan
NE Name IP Address Mask Port SNMP Subnet
Version Name
Process
No. Step Description
2 5.4 Creating a Subnet Allocate topology objects in the same area or of similar
attributes to one subnet to facilitate management.
4 5.6 Creating NEs Create NEs on the U2000 for actual devices. Each NE
on the U2000 represents an actual device. You can create
NEs in two ways: Creating a Single Router NE or
Creating SNMP/ICMP NEs in Batches. If a large
number of NEs need to be created (for example, in a
deployment scenario), Creating SNMP/ICMP NEs in
Batches is recommended. If only a few NEs need to be
created, Creating a Single Router NE is recommended.
5.5.3 Setting Telnet/ Set Telnet/STelnet parameters if you need to manage the
STelnet Parameters NE but did not set them when creating a single NE.
Ensure that Telnet/STelnet parameter settings on the
5 U2000 and NEs are the same. For details about how to
set the parameters, see 5.5.3.2 Setting Telnet/STelnet
Parameters with a Template and 5.5.3.3 Manually
Setting Telnet/STelnet Parameters.
Procedure
Step 1 Design the physical topology and pay attention to the following points:
l Set fewer than five layers of subnets to facilitate O&M.
l Ensure that each subnet contains fewer than 300 NEs so that NE icons are displayed
separately from each other and NEs are easy to find.
Step 3 Set SNMPv3 parameters consistently between the U2000 and NEs.
NOTE
The U2000 uses SNMPv2c or SNMPv3 to communicate with NEs to ensure proper collection of service
performance data. However, SNMPv3 is recommended as it is more secure than SNMPv2c.
1. Set SNMPv3 parameters on NEs.
a. Log in to the router NE ATN910-1 and run the following command to enter the system
view:
system-view
b. Run the following command to start the SNMP agent service:
snmp-agent
Parameter Value
Retries 3
Timeout Interval 10
NE Port 161
NE User ipneuser
Context Engine ID -
Parameter Value
----End
Result
The four NEs and a link are successfully created in subnet IP-test. You can double-click subnet
IP-test to view the NEs and link.
Prerequisites
Before creating NEs, ensure that the xFTP server has been correctly configured and the xFTP
service is running.
Context
To meet service growth requirements, an operator bought one MA5600T, one MA5616, and one
MA5620. To manage these devices on the U2000, administrators need to create an access
network topology for them on the U2000.
Networking Diagram
Figure 5-16 shows an access network topology.
MA5620
Data Plan
Table 5-6 provides the data plan for creating an access network topology.
Process
No. Step Description
Procedure
Step 1 Set parameters for communication between the U2000 and NEs.
NOTE
Set SNMP parameters consistently between the U2000 and NEs according to the data plan.
In practice, set SNMP parameters based on actual conditions.
d. Click OK.
e. Select the previously configured SNMP template and click OK.
f. In the dialog box that is displayed, click Yes to test SNMP parameters automatically.
g. When the Loading dialog box indicates that the test is complete, click OK.
a. In the topology view, right-click in a blank area and choose New > NE from the
shortcut menu.
b. In the dialog box that is displayed, choose Access NE from the navigation tree and
set parameters such as IP Address, Device Name, Device Alias, Physical path,
Maintenance Info, SNMP Parameters, and Coordinate.
3. Click the Select Objects tab. Select the three NEs from the Available Objects list and
click to add them to the Selected Objects list.
4. Click OK.
Subnet district B city A is successfully created.
----End
Result
Subnet district B city A is added to the current view.
NEs are added to subnet district B city A. Their icons are green, indicating that the NEs are
manageable and maintainable to the U2000.
The MDUs (MA5620 and MA5616) connected to the OLT (MA5600T) are displayed in the
ONU topology view of the OLT.
Prerequisites
The U2000 can communicate with the intranet NEs.
l NEs running on the live network need to be added to the U2000 so that the U2000 can
monitor the running status of the entire network in real time.
l Two core devices exist on the network and the link between them needs to be closely
monitored. The U2000 needs to monitor the physical connections between B-NE1, B-NE2,
and B-NE3.
l NEs are distributed in two areas. The operating status of the entire network needs to be
monitored in the topology view, and the operating status of each area can be monitored in
an independent view.
l A USG3030 needs to be created in the Main Topology without affecting the monitoring of
other NEs.
Networking Diagram
Figure 5-17 shows a security network topology.
Data Plan
Item Data
NE
Item Data
U2000
IP address 192.168.1.1/24
Subnet name A
B
Process
No. Step Description
2 Setting SNMP and Set SNMP and STelnet parameters on NEs so that NEs can
STelnet be created on the U2000. To create NEs in batches, set the
Parameters on NEs SNMP and STelnet parameters the same on all NEs.
3 Creating NEs Create NEs in batches using an existing SNMP template and
STelnet template.
4 Creating a Link Create a link between the interconnect interfaces of the two
core NEs that are connected at Layer 3. If Link Layer
Discovery Protocol (LLDP) is enabled on NEs before NEs are
created in the Main Topology, links are also created during
NE creation. If LLDP is enabled after NEs are created in the
Main Topology, search for and create links on the U2000.
5 Creating Subnets Create two subnets in the Main Topology. After copying the
NEs in area one into subnet one and the NEs in area two into
subnet two, you can monitor the running status of each area
by monitoring the subnet.
7 Creating a Single Create the USG3030 in the Main Topology and synchronize
NE the data of the USG3030 without affecting other NEs on the
U2000.
Procedure
Step 1 Configure routes to ensure that they are reachable to each other.
NOTE
Routes between the U2000 and NEs must be correctly configured. For details about how to configure the routing
protocol on an NE, refer to the related NE configuration guide.
Step 2 Set SNMP and STelnet parameters on NEs for the NEs to communicate with the U2000. The
configuration procedure provided below uses the SRG as an example. The procedure is the same
for other NEs.
1. On the RSG, set SNMP parameters.
[SRG]snmp-agent sys-info version v3
[SRG]snmp-agent group v3 testgroup
[SRG]snmp-agent usm-user v3 testuser testgroup authentication-mode md5
87654321 privacy-mode aes128 87654321
# Create an SSH user u2000_user and set the authentication mode to password.
[SRG]ssh user u2000_user
[SRG]ssh user u2000_user authentication-type password
# Set the password for u2000_user to U2000_password and the service type to SSH.
[SRG]aaa
[SRG-aaa]local-user u2000_user password simple U2000_password
[SRG-aaa]local-user u2000_user service-type ssh
[SRG-aaa]local-user u2000_user level 3
[SRG-aaa]quit
NOTE
To ensure the security of the U2000, passwords must be complex enough, and obey the passwords
setting rules of NEs. For example, a password must contain characters of more than two types. The
allowed characters are digits, capital letters, small letters and special characters. Remember to change
passwords regularly.
3. On the RSG, set detailed SNMP and LLDP parameters. Perform this step only on the NEs,
for example, B-NE1, B-NE2, and B-NE3, whose links need to be automatically created on
the U2000.
Step 3 Create NEs in batches using an existing SNMP template and STelnet template.
1. Configure an SNMP template on the U2000.
a. Choose Administration > NE Communicate Parameter > Default Access Protocol
Parameters (traditional style) from the main menu or select Fix-Network NE
Configuration in Application Center and choose Administration > NE
Communicate Parameter > Default Access Protocol Parameters (application
style) from the main menu.
b. In the Default Access Protocol Parameters dialog box, click the SNMPv3
Parameters tab.
c. Click Add and set all parameters in the lower pane.
d. Click OK.
2. Configure an STelnet template on the U2000.
a. Choose Administration > NE Communicate Parameter > NE Telnet/STelnet
Template Management (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Administration >
NE Communicate Parameter > NE Telnet/STelnet Template Management
(application style) from the main menu.
b. In the dialog box that is displayed, click Create, set the protocol name and template
name, and click OK.
e. Click Next. The U2000 starts to search for NEs on the network. After the search is
complete, click Close.
All successfully created NEs are displayed in the Main Topology.
f. Right-click in the Main Topology and choose Layout from the shortcut menu. In the
dialog box that is displayed, set the layout type and other parameters and click OK.
NOTE
If the default layout does not meet requirements, you can drag NEs in the topology view to change
the layout.
NOTE
l If LLDP is enabled before NEs are created in the Main Topology, links are also created during
NE creation.
l If LLDP is enabled after NEs are created in the Main Topology, search for and create links on
the U2000.
a. On NEs B-NE1, B-NE2, and B-NE3, set detailed SNMP and LLDP parameters. For
information about the parameters, see Setting SNMP and LLDP Parameters.
b. Choose File > Discovery > Link (traditional style) from the main menu or select
Topo View in Application Center and choose File > Discovery > Link (application
style) from the main menu.
c. In the dialog box that is displayed, select Do you want to synchronize LLDP data
on the equipment? and the NEs to be searched for links and click . The
discovered links are listed in the right pane.
d. In the link list, select the links to be added to NEs and click Create. In the Result
dialog box, click Close. In the confirmation dialog box, click Cancel. Only Layer 2
links can be added in this step.
Step 5 Create two subnets in the Main Topology and copy the NEs in area one into subnet one and the
NEs in area two into subnet two.
1. In the topology view, right-click in a blank area and choose New > Subnet from the shortcut
menu. In the dialog box that is displayed, set the subnet name to A.
----End
Result
l NEs are successfully created.
l Subnets are successfully created.
l IP links and LLDP links are successfully created.
Prerequisites
l Connected NEs communicates with the U2000 server properly.
l The mediation application package of connected NEs is available.
l The U2000 services are functional.
Example Network
l Scenario:
Office A recently purchased two NGN devices: the SoftX3000 and FIXMGW. The
administrator needs to add these devices to the subnet district B, city A on the U2000.
l Networking:
The following takes the IP address of the U2000 and the IP address of the NE are in the
same network segment as an example, Figure 5-18 shows an example network for
configuring the NGN network topology.
Figure 5-18 Example network for configuring the NGN network topology
Data Plan
Table 5-7 provides the data plan for creating the NGN network topology.
Item Data
Configuration Procedure
No. Configuration Procedure Configuration Roadmap
Procedure
Step 1 Set parameters for communication between NEs and the U2000.
1. Configuring U2000 parameters on the SoftX3000.
a. Log in to the SoftX3000 BAM by using the maintenance client.
b. In the command input area, type ADD WS, and then press Enter.
c. In the parameter input area, enter the IP address of the U2000 workstation (the IP
address of the U2000 server) and the name of the U2000, and then press F9.
ADD WS: WS="U2000", IP="10.10.20.100";
NOTE
For SoftX3000 V300R003, you also need to set the rights of the U2000 workstation to
G_ADMIN, and skip step 1.1.d and 1.1.e.
d. In the command input area, type SET WSCG, and then press Enter.
e. In the parameter input area, enter the name of the U2000 workstation, set the rights
of the U2000 workstation to G_ADMIN (the highest right), and then press F9.
SET WSCG: WS="U2000", CG=G_ADMIN;
The U2000 workstation is added to the SoftX3000 BAM. You can run the LST WS
command on the SoftX3000 BAM to view the parameters.
2. Configuring U2000 parameters on the FIXMGW.
a. Run LST ROUTE to query the route of the U2000 server on the BAM server of the
FIXMGW.
If the route information is displayed, the route has been added. If no route information
is displayed, go to the 1.2.b.
b. Run ADD ROUTE to add the route.
After you enter this command, a dialog box is displayed. Set the parameters in the
dialog box by referring to the following command.
ADD ROUTE: BT=OMU, BN=0, DSTIP="10.10.20.4",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, PREF=60,
NEXTHOP="10.10.20.5";
3. Click OK.
5. Click OK.
The NE is displayed in the current view.
6. Right-click the SoftX3000 and choose Synchronize NE Configuration Data from the
shortcut menu, synchronize the data to the U2000 database.
----End
Result
The NEs and subnets are created successfully, you can double-click subnet district B city A to
check them.
Prerequisites
l Connected NEs communicates with the U2000 server properly.
l The mediation application package of connected NEs is available.
l The U2000 services are functional.
Example Network
l Scenario:
Office A recently purchased two IMS devices: the CGPOMU and SE2600. The
administrator needs to add these devices to the subnet district B, city A on the U2000.
l Networking:
The following takes the IP address of the U2000 and the IP address of the NE are in the
same network segment as an example, Figure 5-19 shows an example network for
configuring the IMS network topology.
Figure 5-19 Example network for configuring the IMS network topology
Data Plan
Table 5-8 provides the data plan for creating the IMS network topology.
Item Data
Item Data
Configuration Procedure
No. Configuration Procedure Configuration Roadmap
Procedure
Step 1 Installing the NE mediation application.
For details, see Installing the NE mediation application of the U2000 commissioning guide.
3. Click OK.
e. Click OK.
The NE is displayed in the current view.
f. Right-click the NE and choose Synchronize NE Configuration Data from the
shortcut menu, synchronize the data to the U2000 database.
g. Right-click the CGPOMU again, and then choose Search CORE NE from the
shortcut menu.
After the operation is successful, the detected core network NEs and the CGPOMU
are connected using a virtual link in the topology view.
2. Create SE2600.
a. Double-click the district B city A subnet in the Main Topology to open the subnet.
b. Right-click in the district B city A subnet and choose New > NE from the shortcut
menu.
c. In the dialog box that is displayed, choose Core Network Series > SE2600 from the
navigation tree.
d. Configure the name, IP address, and SNMP of the SE2600 in the right pane. For details,
seeNE Properties.
e. Click OK.
The NE is displayed in the current view.
f. Right-click the SE2600 and choose Synchronize NE Configuration Data from the
shortcut menu, synchronize the data to the U2000 database.
----End
Result
The NEs and subnets are created successfully, you can double-click subnet district B city A
Subnet to check them.
Context
If an NE (NE 1) changes because the entire network changes during network management and
maintenance, administrators need to move the NE from the original subnet (subnet A) to another
subnet (subnet B). To help administrators complete this work more efficiently, the U2000
provides the subnet movement function.
Procedure
Step 1 In the Main Topology, select Physical Root from the Current View drop-down list.
----End
Follow-up Procedure
l If the clock function has been configured for NE 1, right-click in a blank area of the clock
view and choose Synchronize with Physical View from the shortcut menu. NE 1 is then
automatically moved to subnet B.
l If subnet A, subnet B, and NE 1 also exist in a custom view, repeat the preceding operations
in the custom view so that NE 1 can be monitored in the custom view.
If managed devices on a network are deployed in different time zones, you can localize
U2000 and NE system time to ensure the correct time display on the U2000 and facilitate network
maintenance.
UTC
Universal time coordinated (UTC) was also called Greenwich Mean Time (GMT). UTC is
absolute time used by many communications standards.
All data on the U2000 and NEs are stored in UTC format.
Time Zone
Time Zone: The world is split into 24 time zones, each spanning a 15 degree-wide longitudinal
band. The time offset between adjacent time zones is one hour.
If the preset time zone of the system is incorrect, the backup operation timed at 04:00 am (the
time when the network traffic is small) may be performed in the daytime (the time when the
network traffic is heavy). As a result, the CPU is overloaded and this problem is difficult to
locate. Therefore, the system time zone must be set to the device location time zone.
Countries have different stipulations for DST. Many countries in the world are using the legal
form and moving the clock one hour forward during summer days. Few of them also move the
clock half an hour or several hours forward. In winter, they adjust the time to its normal state.
Such time is called DST, a legal form of time.
If the U2000 or the NE is in a DST observing country or region, synchronize the system time
and network elements time with DST and adjust time sensitive services based on DST to ensure
that time information in accounting, billing, alarm, and log records is correct.
Time Localization
The U2000 supports time localization. That is, the time it displays is the local time. The local
time is calculated based on the UTC time, time zone, and DST.
The time on the U2000 client is displayed in two modes: client local time and server local
time. For details about how to set the time display mode, see the 1.8.17.3 Setting the Time
Mode of the Client.
The U2000 also allows users to set the alarm/event time display mode to NE time, server time,
or client time. For details, see 7.8.18 Setting the Time Display Mode for Queried Alarms or
Events.
Context
l The correct U2000 time depends on a correct U2000 timing source. That is, the operating
system (OS) on which the U2000 server runs must be correct.
l After setting the time format, you need to log in to the server again to make the settings
take effect.
l When you log in to the client next time, the U2000 client automatically uses your last
settings.
l The new time display format is listed in the Appearance Example area.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 3 Set the time display format in the Specify the time display format area according to the
instructions displayed in the Time Format Notation area. Then, select the required record from
the Time Format drop-down list. You can set the time format to determine whether the time
zone and DST flag.
NOTE
If the Time Format is hh:mm:ss tt, you can setting the Time Indicator.
----End
Context
l After setting the time mode, you must re-log in to the U2000 client for the settings to take
effect.
l Next time when you log in to the client, the U2000 client automatically uses the settings
that you used last time.
l The settings take effect for the current user that logs in different clients, but is invalid for
other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the navigation tree on the left of the Preferences window, select Time Mode.
l Server time mode: If you select this option, the time on the U2000 client is displayed based on the
time zone where the server is located. For example, if the time of the client in UTC +08:00 is 10:00,
and the server is in the UTC +07:00, the time displayed on the U2000 client is 9:00. Server time
mode is used by default.
l Client time mode: If you select this option, the time on the U2000 client is displayed based on the
client OS time.
----End
NOTE
Prerequisites
You are an NMS user with Operator Group authority or higher.
Background Information
For the MSTP series, WDM series, WDM (NA) series, PTN series, Marine series, RTN series,
Router series, Switch series NEs, the time zone of the U2000 are automatically synchronized
with those on the NE, though you do not change them by using the U2000. Meanwhile, the NE
reports an event indicating that the time zone is changed at the NE side.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Configuration > NE Batch Configuration > NE Time Localization
Management (application style) from the main menu.
NOTE
For router series, switch series, access series NEs, right-click the desired NE in the Main Topology and
choose Properties. In the dialog box that is displayed, click the Time Zone and DST tab.
Step 5 Click Apply. In the Result dialog box that displayed, click Close.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Background Information
For the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series, Marine series,
Router series, Switch series NEs, the DST rule of the U2000 are automatically synchronized
with those on the NE, though you do not change them by using the U2000. Meanwhile, the NE
reports an event indicating that the DST rule is changed at the NE side.
After you set the DST time for an NE, a time gap is generated between the non-DST time and
DST time. An error message is displayed if you configure data on the U2000 for this time gap.
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Configuration > NE Batch Configuration > NE Time Localization
Management (application style) from the main menu.
NOTE
For router series, switch series, access series NEs, right-click the desired NE in the Main Topology and
choose Properties. In the dialog box that is displayed, click the Time Zone and DST tab.
Step 6 Click Apply. A prompt appears telling you that the operation was successful. Click Close.
----End
7 Alarm Management
By viewing alarms, you can learn network and NE status, and locate faults. Therefore, alarms
need to be obtained and managed effectively. To ensure the normal running of the network, the
network management or maintenance engineer must monitor and handle alarms periodically.
This topic describes how to manage an alarm/event template. You can set frequently used query
conditions or statistical conditions of alarms/events as a template to facilitate operations. The
U2000 provides the customized alarm/event browsing template and alarm/event attributes
template. You can quickly set the alarm/event browsing filter criteria and the alarm/event
attributes, by using the preset customized alarm/event template.
Similarities
In the U2000, alarms and events refer to the messages that are sent to the U2000. These messages
are generated when the status of the U2000 or a managed object (MO) changes.
Differences
Alarms differ from events as follows:
l An alarm is reported if a fault occurs on the U2000 or an MO, and immediate measures
must be taken to rectify the fault. Otherwise, the U2000 services cannot run properly
because the fault affects the functions of the U2000 or its devices. Users can acknowledge
and clear an alarm.
l An event is reported if the status of the U2000 or an MO changes, but the change may not
affect the U2000 services. Users cannot acknowledge and clear an event.
Table 7-1 describes the alarms of different severities and the corresponding handling methods.
Critical A critical alarm indicates that a service- The alarm must be handled
affecting fault has occurred and a immediately. Otherwise, the
corrective action must be taken system may break down.
immediately.
Major A major alarm indicates that a service- The alarm must be handled timely.
affecting fault has occurred. If the fault Otherwise, the important functions
is not rectified immediately, it will lead will be affected.
to a serious result.
Minor A minor alarm indicates that a non- Such alarms are used to remind the
service affecting fault has occurred and maintenance engineer to
that corrective action should be taken in efficiently locate the alarm causes
order to prevent a more serious (service- and eliminate the possible faults.
affecting) fault. An alarm of this severity
can be reported when the detected alarm
condition is not currently degrading the
capacity of the managed object.
Alarm States
On the U2000, alarms have four states based on alarm acknowledgment and clearance:
l Unacknowledged and uncleared
l Acknowledged and uncleared
l Unacknowledged and cleared
l Acknowledged and cleared
NOTE
Alarms that have been acknowledged and cleared are historical alarms. All the other alarms are current
alarms.
Therefore, the alarm state changes from uncleared to cleared. You can also manually clear
an alarm.
l Changing the acknowledgment status
If an alarm is acknowledged, the alarm has been processed or will be processed. After
acknowledgment, the alarm state changes from unacknowledged to acknowledged.
You can unacknowledge an acknowledged alarm. After the alarm is unacknowledged, the
alarm state changes from acknowledged to unacknowledged.
NOTE
The alarm state change model for the U2000 is the same as that of the NE.
The alarms can be categorized into the following two types according to the generating location:
l NE alarms: refer to the alarms generated when the NE equipment is faulty.
l U2000 alarms: refer to the alarms generated when the U2000 environment or the connection
between the U2000 and NE is faulty.
Based on the standards and functions of the U2000, alarms can be categorized into six types as
follows:
l Communication alarms: refer to the alarms related to NE communication, ECC
communication, and optical signal communication. For example, the interruption of NE
communication and the loss of optical signals.
l Process alarms: refer to the alarms related to the software processing and exception. For
example, equipment bus collision and the standby path check failure.
l Equipment alarms: refer to the alarms related to equipment hardware. For example, the
laser failure and the optical port loopback.
l Service alarms: refer to the alarms related to the service status and network QoS. For
example, the multiplex section performance threshold-crossings and the excessive B2 bit
errors.
l Environment alarms: refer to the alarms related to the power supply system and the
environment, such as temperature, humidity, and access control. For example, the
temperature of the power module exceeds the threshold.
l Security alarms: refer to the alarms related to the security of the U2000 and NEs. For
example, an NE user is not logged in.
Alarm Color
The U2000 uses evident color changes on the GUI to help you quickly locate the alarmed
monitoring point.
l The alarm indicators on the toolbar display the number of all the uncleared and
unacknowledged critical, major, minor and warning alarms network-wide. When a new
alarm is reported, the alarm indicator flashes while the statistics on the indicator change.
You can navigate to the alarm browsing window by clicking the alarm indicator to view
the network-wide alarms of this severity.
NOTE
For NA NEs, alarms in the U2000 has the following five severities: critical, major, minor, not alarmed,
and not reported.
l In the Main Topology, the alarms of Non-NA NEs and subnets are represented by colored
icons. These icons are in different colors to indicate different alarm severities, as shown in
Figure 7-2.
l In the Main Topology, the alarms of NA NEs and subnets are represented by colored icons.
These icons are in different colors to indicate different alarm severities, as shown in Figure
7-3.
l In the Main Topology, if a fiber or trail is affected by an alarm, the fiber or trail color varies
with the alarm that is currently at the highest severity on the fiber.
l On the NE Panel, the board color varies with the alarm that is at the highest severity on the
board.
l On the board view, the color of each channel varies with the alarm that is currently at the
highest severity on the corresponding channel.
l On the Path View, the alarmed trails are displayed in different colors.
By default, the U2000 displays different colors for different alarm severities. You can define
different colors for the alarms at different severities.
l For Non-NA NEs, the U2000 displays critical alarms in red, major alarms in orange, minor
alarms in yellow, and warning alarms in blue.
l For NA NEs, by default, the U2000 displays critical alarms in red, major alarms in orange,
minor alarms in yellow, and not alarmed alarms in blue.
Alarm panel
The alarm panel uses different colors of indicators to identify severities of alarms. This helps
you to understand the alarm information. It can work as a monitoring panel.
The minimization icon of the alarm panel consists of a shortcut icon and four color blocks at the
upper right corner of the toolbar on the client. See Figure 7-4. These color blocks are alarm
indicators, which indicate critical, major, minor, and warning alarms respectively. The digit in
the color block indicates the number of alarms of this severity on the U2000. When an alarm is
generated, the corresponding color block blinks. Through the minimization icon of the alarm
panel, you can know the generation of alarms, alarm severities, and the statistics of alarms of
each severity.
NOTE
NOTE
By default, four types of color blocks are displayed on the U2000 client. You can hide the color blocks of
which you do not care about the severity. For details, see 1.8.13 Setting the Display Properties of New
Alarm/Event.
Choose Browse Alarm > Display Alarm Panel (application style) or Fault > Display Alarm
Panel (traditional style) from the main menu, or click on the U2000 client to open the alarm
panel, as shown in Figure 7-4.
NOTE
l In the Alarm Panel dialog box, right-click a template that does not have icon and choose Show
On Alarm Lamp from the shortcut menu. The alarm indicator collects alarm statistics based on this
template.
l Both the alarm box and the alarm panel notify users of new alarms in audible and visual mode. Their
differences are as follows: The alarm box is the hardware and does not display the alarm statistics. You
can set the filter criteria to filter the alarms that are sent to the alarm box on the client. Compared with
the alarm box, the alarm panel is a window on the client. You can click Add at the bottom of the Alarm
Panel dialog box to bind Current alarm templates to the alarm panel. The Alarm Panel dialog box
displays the alarm statistics of the bound templates in real time based on alarm states and severities.
l If a user changes the name, status, or filter criteria of a template, or add or delete the template in the
alarm panel on client B, the changes can be synchronized to client A only after the user restarts client
A.
l icon indicates that the alarm panel is collecting the data statistics. The common cause is that NEs
are added or deleted during the U2000 running.
l icon indicates that the template in the alarm panel does not collect the alarm statistics of this severity.
When you place the pointer to alarm lamps of alarm panel, the U2000 displays the number of
alarms. For details about how to set the information, see 7.6.10 Setting the Format of the Alarm
Lamp ToolTip.
In the Browse Current Alarm window, if you select Display latest alarms, the newly reported
alarms are automatically displayed in this window. If this function is not enable, the Refresh
button flashes when a new alarm is reported. When you click the button, the alarm is immediately
displayed in this window.
Alarm Box
The U2000 client connects to the alarm box device commonly used in Huawei to provide audible
and visual alarms. You can determine the alarm severity according to the indicators and sounds
of the alarm box. When a new alarm is reported, the alarm box instantly beeps and flashes the
alarm indicator of the corresponding severity.
Sound Box
Connected to a sound box, the U2000 client uses different sounds to indicate alarms at different
severities. When a new alarm is reported, the sound box immediately beeps. The sound is muted
when the alarm is acknowledged or when the preset duration for the sound to persist elapses.
The alarm sound is realized on the U2000 client. You can set different sounds for alarms of
different severities.
Current Alarms
Category Description
Current NMS Alarms Indicates the alarm data stored in the current
alarm library of the NMS.
Whether the current NMS alarm is consistent with the current NE alarm depends on the following
factors:
Historical Alarms
Category Description
Historical NMS Alarms After the current alarms are cleared on the
NMS and then acknowledged, the alarms are
moved from the current alarm list to the
historical alarm list after a lifecycle.
Whether the historical NMS alarm is consistent with the historical NE alarm depends on the
following factors:
l Whether the automatic alarm reporting is configured.
l Whether the alarm masking is configured.
l Whether the alarm clearance or the alarm acknowledgment is performed.
l Whether the alarms generated by the U2000 exist.
Table 7-2 lists the impacts of the alarm basic operations on NEs.
Alarm browsing No
Alarm acknowledgement No
Alarm synchronization No
Alarm check No
Alarm refreshing No
Alarm filtering No
Alarm statistic No
Alarm memo No
Alarm Browsing
Alarm browsing applies to hierarchical alarms, including NE, board, interface, protocol, and
service alarms You can view the alarms of the NMS, NEs, and services on the U2000 to learn
the running status of the network or the NE.
l Browsing current alarms: You can learn the network-wide current alarms of all severities.
l Browsing all current alarms of a specified severity: By clicking the alarm icon on the
toolbar, you can quickly learn the network-wide critical, major, minor or warning alarms.
l Browsing alarms of a specified NE or U2000: You can select an NE or a U2000 on the
Main Topology to learn the current alarms of the selected object.
l Browsing current alarms of a trail: In the trail management window, you can quickly learn
the alarms or events in the managed or concerned trails. This function facilitates
maintenance.
l Browsing historical alarms: By learning all the historical alarms recorded in the U2000,
you can know the faults that once occurred on the NEs and on the U2000. This function
facilitates the long-term performance analysis.
Alarm Acknowledgement
Alarm acknowledgement indicates that an alarm has been handled by the user and does not
require attention. If you want to pay attention to the alarm again, you can unacknowledge the
alarm and take corresponding measures to handle it.
The U2000 supports manual acknowledgement and automatic acknowledgment:
l Manual acknowledgment: You can select an alarm from the current alarm browsing
window to acknowledge it.
l Automatic acknowledgment: The U2000 supports automatic acknowledgment by severity
and rule. If you enable the automatic alarm acknowledgment, the U2000 acknowledges an
alarm after it is cleared or automatically acknowledges the alarms that are cleared within
specified time at 01:00 every day.
Alarm Synchronization
Normally, U2000 synchronizes the alarm data of the NMS and NEs automatically. When the
communication between the NMS and NE restored from an interruption, or when the NMS is
restarted, the alarm data between the NMS and NEs may be inconsistent. You need to
synchronize the alarm information to keep the consistency of the alarm data. To synchronize the
alarms, the U2000 compares the alarms in the U2000 database with the alarms in the NE
database. If the alarm data is inconsistent, the U2000 uploads the NE alarm data to the U2000
database and overwrites the original information. The alarm synchronization can be performed
in the following two ways:
l Manual synchronization: You can specify an alarm in the current alarm browsing window
and synchronize it.
l Automatic synchronization: You can specify the trigger conditions for the automatic alarm
synchronization, such as when the U2000 starts, when the communication is restored from
an interruption, or when an LCT user logs out.
Alarm Check
The alarm check function is used to compare one or more uncleared alarms on the U2000 with
those on the NE. If the alarm exists as a current alarm on the NE, it means that the alarm
information remains unchanged on the U2000. If the alarm does not exist on the NE, the alarm
is cleared on the U2000.
Alarm Refreshing
When you refresh the alarms, the latest alarm information is obtained from the alarm database
of the U2000 and displayed on the U2000 client.
Alarm Clear
You can manually clear the alarms that cannot be cleared automatically or do not exist on the
NMS. After being manually cleared, an alarm may be reported to U2000 if the fault causing this
alarm is not rectified.
When you delete an alarm, the alarm is cleared from the NE and the current alarm list of the
NMS. After that, the alarm is moved to the historical alarm list.
NOTE
Alarm Filtering
By setting the filter criteria, you can filter out the unconcerned alarms in the alarm browsing
window. The filter criteria see Alarm Filter.
Alarm Statistic
l By performing statistics on alarm logs, the alarm statistics which meet the specified
conditions are displayed in a table. This function helps you to analyze the running status
of the equipment.
l On the U2000, the statistics about the current alarms can be collected. The U2000 collects
the current alarm statistics in unit of node according to the statistics items, such as alarm
severity and alarm status. You can set a time range for the U2000 to collect the alarm
statistics within this time range.
Alarm Memo
You can add remarks for the handled alarms. This is useful when you manage a large number
of alarms.
Table 7-3 lists the impact of alarm setting operations on NEs and services.
Table 7-4 lists the impact of alarm setting operations on alarms. See Alarm Reporting
Process.
Operation Impact
Operation Impact
Setting the Alarm Reversion l When you set the alarm reversion for a
Applies to the MSTP, WDM, RTN, and port, the alarm status on this port is
submarine NEs. opposite to the actual situation. That is,
alarms are not reported even if they exist.
l When you set the alarm reversion for a
port, the alarm status of the board does not
change, and the alarm indicator still
indicates the actual running status of the
equipment.
A reasonable alarm delay time effectively prevents the transient reporting and mis-reporting of
the alarms, and reduces the impact on the U2000 performance.
l Wrap: When the NE alarm register is full, the register discards the earliest alarms to save
the latest alarm information when new alarms are generated. This is the default mode that
is also most frequently used.
l Stop: When the NE alarm register is full, it does not accept any new alarms so that you
cannot be informed of the new alarms. This mode is not frequently used.
The alarm reversion has three modes: non-revertive, manual reversion and automatic reversion.
Table 7-5 shows how alarms are handled in the three modes.
NOTE
After port alarm reversion is configured, the board alarm status remains unchanged, and the alarm indicators
are consistent with the actual alarm status.
The UNEQ has the two switches, LOS and Path Not Used.
For NEs (NA), alarms on the U2000 have the following five severities: critical, major, minor, not alarmed,
and not reported.
about insufficient disk space and the communication interruption between the U2000 and an
NE.
Compared with alarm reversion and alarm masking, configuring maintenance status has the
following features:
l Managed object:
– Alarm reversion can be configured in batches only for ports.
– Alarm masking can be configured only for specific alarms.
– Configuring maintenance status can be implemented in batches for NEs, boards, and
ports.
l Processing mode:
– Different alarm reversion modes have different processing modes. For details, see
Setting the Alarm Reversion.
– The U2000 does not display masked alarms and save them to the database.
– The U2000 displays alarms reported by the managed objects in the maintenance state
and save them to the database.
Prerequisites
The License supports the remote alarm or event notification function.
Context
Contact the SMS Gateway for the IP address, port number, user name, password, and coding
protocol.
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Choose Alarm Settings > Remote Notification (application style) or Fault > Settings >
Remote Notification (traditional style) from the main menu.
Step 2 In the Remote Notification window, click Settings in the lower left part, and then choose
Communication Device.
l Select a row in the list and click Properties, then you can modify parameter setting name and
communication parameters in the Modify Communication Device dialog box.
l Select a row in the list and click Delete, then you can delete communication parameters.
Step 4 In the Add Communication Device dialog box, enter the setting name and select SMS Gateway
(SMS Center). Click Next.
NOTE
You can set the notification parameters for each device only once. If the notification parameters of this
device are already set, the device name is not displayed in the Device name drop-down list box.
Step 5 In the Add Communication Device dialog box, set the SMS gateway. Select Enable. See
Figure 7-7.
Step 6 Optional: Click Advanced. In the Message Format Settings dialog box, set the parameters.
Click OK.
----End
Prerequisites
The SMS gateway is set to sending notifications by SMS.
Context
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Choose from the main menuAlarm Settings > Remote Notification (application style) or
Fault > Settings > Remote Notification (traditional style) from the main menu.
Step 2 In the Remote Notification window, click Settings in the lower left part, and then choose
Communication Device.
Step 3 In the Communication Device Settings dialog box select a notification record. Click
Properties.
Step 4 In the Modify Communication Device dialog box click the Communication Device tab and
then select Enable.
Step 6 In the Phone number for receiving test short messages text box, enter the country code and
mobile phone number for test. Click Test.
l If the gateway is configured properly, the system prompts that the SMS is sent successfully.
Click OK. Check that you receive the SMS that contains the alarm name, location
information, alarm severity, alarm ID, and other information.
l If the gateway is configured improperly, the system prompts that the SMS fails to be sent.
Click OK. Check that the SMS center number and the mobile phone number are correct.
----End
Prerequisites
The default number of the Simple Mail Transfer Protocol (SMTP) port is 25. Ensure that the
SMTP port on the email server is available.
Context
l The U2000 client or U2000 server can connect to the SMTP mail server.
l When the client or server connects to the SMTP mail server, the user name and password
are required for authentication.
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Choose Alarm Settings > Remote Notification (application style) or Fault > Settings >
Remote Notification (traditional style) from the main menu.
Step 2 In the Remote Notification window, click Settings in the lower left part, and then choose
Communication Device.
l Select a row in the list and click Properties, then you can modify parameter setting name and
communication parameters in the Modify Communication Device dialog box.
l Select a row in the list and click Delete, then you can delete communication parameters.
Step 4 In the Add Communication Device dialog box, enter the setting name and select Email. Click
Next.
NOTE
You can set the notification parameters for each device only once. If the notification parameters of this
device are already set, the device name is not displayed in the Device name drop-down list box.
Step 5 In the Add Communication Device dialog box, specify SMTP Server and Send Party. Select
Enable. See Figure 7-8.
----End
Prerequisites
The Email notification is configured correctly.
Context
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Choose Alarm Settings > Remote Notification (application style) or Fault > Settings >
Remote Notification (traditional style) from the main menu.
Step 2 In the Remote Notification window, click Settings in the lower left part, and then choose
Communication Device.
Step 3 In the Communication Device Settings dialog box select a record of email notification. Click
Properties.
Step 4 In the Modify Communication Device dialog box select the Communication Device tab.
Confirm the email server information and the selected sending point. Ensure that you select
Enable.
Step 6 In Email Address, enter the email address for test. Click Test.
l If the email notification is configured properly, the system prompts that the email is sent
successfully. Click OK. Open your email box and check whether you receive the email that
contains the alarm name, location information, alarm severity, alarm ID, and other
information.
l If the Email notification is not configured properly, the system prompts that the email fails
to be sent. Click OK. Check that the email addresses of the sender and the receiver are correct
and that the SMTP is properly set.
----End
Prerequisites
The U2000 client has been shut down before you install hardware.
Context
l The U2000 supports the following modems:
– GSM Modem: E-TEK GSM modem TD-8011, wavecom WMOD2B GSM/GPRS
modem
– CDMA Modem: E-TEK CDMA modem TD-8022R, E-TEK CDMA modem TD-8022
l If the workstation COM port or PC COM port is a female connector or DB-25 pin, they
cannot connect to the COM port cable of the modem. You need to use a converter.
l If you select a modem as the sending device type, the modem must be installed on the server
that runs in a 32-bit operating system so that GSM Modem, CDMA Modem, and related
parameters can be displayed on clients. In this case, you can set modem-related parameters
on any client that is connected to the server to send SMS messages.
NOTICE
A wireless modem can be used only on a 32-bit operating system.
Procedure
Step 1 Check the occupancy of the serial ports on the U2000 client to ensure that required serial ports
are available during installation.
Idle serial ports are available and 1. Log in to the U2000 client.
one of them is occupied by the alarm 2. Choose Alarm Settings > Options (application
box style) or Fault > Settings > Options (traditional
style) from the main menu. In the displayed Alarm
Options window, check the value of the Serial
port.
Only one serial port is available and 1. Log in to the U2000 client.
it is occupied by the alarm box 2. Choose Alarm Settings > Options (application
style) or Fault > Settings > Options (traditional
style) from the main menu. In the displayed Alarm
Options window, clear the Enable alarm box
check box. Then, click OK.
3. Remove the physical connection between the
alarm box and the serial port on the client.
NOTICE
Before installing the hardware, ensure that the U2000 client is shut down.
Use the serial port cable of the modem to connect the modem and the U2000 server. One end
connects the modem, and the other end connects the idle serial port on the U2000 server. For
details, see the specifications delivered with the modem.
NOTE
Use a connector delivered with the modem if the interface of the serial port cable is different from the serial
port on the U2000 server.
Use the DC power cable delivered with the modem. For details, see the specifications delivered
with the modem. After the power cable is connected, switch on the power. Normally, the
indicator of the modem blinks regularly. Table 7-6 shows how the indicator indicates the running
status of the modem.
Table 7-6 Relations between the status of the indicator and the modem
Indicator Modem
Blinks slowly The modem is connected to the network and is in idle mode.
To install the modem driver, see the specifications delivered with the modem.
NOTE
You need to install the driver only when the installation of the driver is required in the specifications
delivered with the modem.
----End
Context
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Run the tip command to enable the COM port and then set the baud rate. In the following
command, 9600 indicates the baud rate (The baud rate varies according to the modem. Obtain
the baud rate for a modem from the user manual for a modem); /dev/term/a indicates COM port
A.
# at
# atdt88812345;
# ath
OK
Step 5 Press Enter and then type ~ to exit the tip command.
# ~.
[EOT]
----End
Prerequisites
l The wireless modem has been installed.
l When the wireless modem is used as the sending device, the serial port baud rate of the
U2000 client is the same as that of the U2000 server.
– For details about how to query the serial port baud rate of the U2000 client, see 7.3.3.4
Setting Parameters for Alarm Notification by the Wireless Modem.
– The method for querying the serial port baud rate of the U2000 server is as follows:
1. Right-click My Computer and choose Properties from the shortcut menu.
2. In the System Properties dialog box, click the Hardware tab and click Device
Manager.
3. In the Device Manager dialog box, expand the Ports node, right-click a port, and
choose Properties from the shortcut menu.
4. In the Communications Port Properties dialog box, click the Port Settings tab
and select a baud rate from the Bits per second drop-down list box for the port.
Context
This section uses wireless commissioning on Windows Server 2003 as an example.
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Log in to the Windows operating system of the U2000 server as administrator.
Step 3 In Windows, choose Start > Programs > Accessories > Communications >
HyperTerminal.
NOTE
You need to set the location information only when you open the HyperTerminal for the first time.
Step 4 Set up a connection. Enter the connection name, such as modem, and then click OK.
Step 5 Select the serial port for the connection. For example, select COM1, as shown in Figure 7-10,
and then click OK.
Step 6 Set the properties of the serial port according to Figure 7-11, and then click OK.
Step 7 Dial a number in the HyperTerminal window as shown in Figure 7-12 to check if the dial-up is
normal. If the dial-up is normal, OK is returned.
If the system displays OK, then the modem is connected. Otherwise, check whether the
cable is loosely connected to the serial port and whether the serial port configuration
conflicts with each other. If the connection of serial cables is normal and you set the
attributes of the serial port properly, change the value of Bits per seconds if the
communication cannot be set up. If the problem persists, contact Huawei technical support
engineers for assistance.
2. Run the command at+csq.
+CSQ: x,y
In the displayed message, x represents the signal strength. For details, see Table 7-7. y
represents whether the check is right. If the value of y is 0, then the check is right.
11 - 31 Sufficient
If the modem is not registered to the network, check whether the modem is properly
connected to the antenna and whether the signals are sufficient.
Step 8 Run the following command to use a number to test the dialing:
atdtelephone number;
OK
NOTICE
l The previous command must end up with a ; mark.
l The telephone number in the command can be a fixed-line telephone number. For example,
88812345. And the telephone number in the command can also be a mobile phone number.
You need to add the country code preceding the mobile phone number. For example,
8699912345678.
----End
Prerequisites
The modem has been installed and commissioned.
Context
l The GSM Modem notification, CDMA Modem notification and SMS center notification
are mutually exclusive. You can choose only one of them at a time.
l Configurations of the GSM Modem and CDMA Modem are similar. Here, take the GSM
Modem for example.
l In the Phone number for receiving test short messages text box, enter a plus (+), a country
code, and an SMS center number. Assume that the country code for China is 86 and the
SMS center number is 13900001234. Enter +8613900001234.
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Choose Alarm Settings > Remote Notification (application style) or Fault > Settings >
Remote Notification (traditional style) from the main menu.
Step 2 In the Remote Notification window, click Settings in the lower left part, and then choose
Communication Device.
l Select a row in the list and click Properties, then you can modify parameter setting name and
communication parameters in the Modify Communication Device dialog box.
l Select a row in the list and click Delete, then you can delete communication parameters.
Step 4 In the Add Communication Device dialog box, enter the setting name and select GSM
Modem and click Next.
NOTE
You can set the notification parameters for each device only once. If the notification parameters of this
device are already set, the device name is not displayed in the Device name drop-down list box.
Step 5 In the Add Communication Device dialog box as shown in Figure 7-13, set the Send Party
and select Enable.
----End
Prerequisites
l The wireless modem is set to send notifications by short message.
l The wireless modem has been installed and verified.
Context
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Choose Alarm Settings > Remote Notification (application style) or Fault > Settings >
Remote Notification (traditional style) from the main menu.
Step 2 In the Remote Notification window, click Settings in the lower left part, and then choose
Communication Device.
Step 3 In the Communication Device Settings dialog box select a record of notification sent by the
modem. Click Properties.
Step 4 In the Modify Communication Device dialog box select the Communication Device tab.
Confirm the selected sending point and ensure that you select Enable.
Step 6 In Phone number for receiving test short messages, enter the country code and mobile phone
number that are used for test. Click Test.
l If the modem is configured properly, the system prompts that the SMS is sent successfully.
Click OK. Check whether you receive a SMS, which contains the alarm name, location
information, alarm severity, alarm ID, and other information.
l If the modem is configured improperly, the system prompts that the SMS fails to be sent.
Click OK and check whether the SMS center number and the mobile phone number are
correct.
----End
Procedure
Step 1 Choose Alarm Settings > Remote Notification (application style) or Fault > Settings >
Remote Notification (traditional style) from the main menu.
Step 2 In the Remote Notification window, click Settings and select Message Format in the lower
left corner.
Step 3 In the Message Format Settings dialog box, set the format of emails or short messages.
Step 4 Click Email Content. Select the contents in an email, such as the NE name and location
information.
Step 5 Click the SMS tab. Click SMS Content, and select the contents in a short message, such as the
NE name and location information.
----End
Context
The delay specified in an alarm remote notification rule takes precedence over the global remote
notification delay. If a delay is specified in an alarm remote notification rule, this delay prevails
when the rule is implemented. If no delay is specified in an alarm remote notification rule, the
global remote notification delay prevails when the rule is implemented.
Procedure
l Set a delay in an alarm remote notification rule.
1. Choose Alarm Settings > Remote Notification (application style) or Fault >
Settings > Remote Notification (traditional style) from the main menu.
2. In the Remote Notification window, click the Delay Time (min) column
corresponding to an alarm remote notification rule. Then, select the check box that is
displayed and specify a delay in the text box.
3. Click Apply.
l Set the global remote notification delay.
1. Choose Alarm Settings > Remote Notification (application style) or Fault >
Settings > Remote Notification (traditional style) from the main menu.
2. In the Remote Notification window, click Settings in the lower left part, and then
choose Delay.
3. In the Delay Time dialog box, set a delay for remote alarm notification.
4. Click OK.
----End
Context
l In notification conditions, you can set the alarm name, severity, and other properties for
remote notification. The notification time indicates the time when the remote notification
is sent. The notification mode indicates the email address and mobile phone number of the
receiver.
l The U2000 supports at most 50 remote notification rules for alarms or events.
l In an email or SMS, the alarm or event occurrence time and the alarm clearance time are
subject to the time of the U2000 server.
l The procedures for setting remote event notification rule and remote alarm notification rule
are the same. The following uses the remote alarm notification rule as an example:
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
Procedure
Step 1 Choose Alarm Settings > Remote Notification (application style) or Fault > Settings >
Remote Notification (traditional style) from the main menu.
Step 2 In the Remote Notification window, click Add, and then choose Alarm Notification Rule.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 On the Basic Settings tab page of the Add Alarm Remote Notification Rule dialog box, set
the parameters such as Alarm name and Severity.
Step 4 Optional: Click the Alarm Source tab. On the Alarm Source tab page, select All objects, or
select Custom to set alarm sources. Click Next.
Step 5 In the Add Alarm Remote Notification Rule dialog box, set the notification weekday, time
segment, time zone, and delay time. Click Next.
Step 6 In the Add Alarm Remote Notification Rule dialog box, set the email addresses and telephone
numbers.
NOTE
To instantly enable the rule, select Enable. In the Remote Notification window, you can select or deselect
Enable for this rule, and then click Apply to save the setting.
----End
Procedure
Step 1 Choose Browse Alarm > Download Remote Notification Logs (application style) or Fault >
Download Remote Notification Logs (traditional style) from the main menu.
Step 2 In the Download Remote Notification Logs window, select one or more remote notification
log files, and then click Download.
NOTE
You can double-click a remote notification log file and then open or save the file in the Download File
dialog box. The file in use cannot be opened or saved.
Step 3 In the Save dialog box, select a path and click Save to save the remote notification log files.
NOTE
By default, remote notification log files are stored in Client installation directory\client\client
\downloadFile.
Step 4 In the displayed Information dialog box that indicates the download result, click OK.
NOTE
----End
Result
You can view details about email or SMS message sending, such as the sending status and time,
in the remote notification logs.
Correlation Analysis
Correlation analysis involves two windows: Default Correlation and Correlation Analysis.
The Default Correlation window displays the alarm correlation rules defined by the U2000.
You can set whether to use these rules. On the Correlation Analysis interface, you can create
correlation rules.
Correlative alarms are alarms whose causes are related. One alarm has the root cause for the
other alarms. Alarm correlation analysis identifies these alarms.
Faults may result in multiple types of alarms, among which non-root alarms affect fault locating
and analyzing. To help handle root alarms and quickly locate and rectify faults, you can set
correlation rules on the U2000 based on some correlative alarm features, such as the alarm
generation time and physical locations, to raise root alarm severities by one, redefine severities
of non-root alarms that meet the rules, set the non-root alarms as correlative alarms, or discard
them.
Figure 7-14 shows the relationships between a root alarm and its correlative alarms.
Figure 7-14 Relationships between a root alarm and its correlative alarms
The high service memory usage alarm leads to two alarms: high memory usage alarm and high
CPU usage alarm. The high CPU usage alarm leads to another alarm: abnormal U2000 service
exit alarm. Therefore, the high service memory usage alarm is the root alarm, and the other
alarms are its correlative alarms.
An event is defined as a repeat event when it occurs within a time that is less than or equal to a
specified value.
Faults may result in multiple duplicate alarms or events in a short period. These alarms or events
are redundant for maintenance personnel. Therefore, for these potential intermittent alarms and
repeat events, you can set an intermittent alarm and repeat event analysis rule on the U2000.
Therefore, the U2000 discards the intermittent alarms and repeat events that meet the rule and
displays only the first repeat event or cleared intermittent alarm.
Prerequisites
Users have purchased the alarm correlation rules and have imported them into the U2000.
Context
The Default Correlation page displays the default correlation rules provided by the U2000.
You can set whether to use these rules, but cannot modify them.
Procedure
Step 1 Choose Alarm Settings > Correlation (application style) or Fault > Settings > Correlation
(traditional style) from the main menu.
Step 2 Select a rule on the Default Correlation tab page, set whether to enable the default correlation
rules.
NOTE
The fields displayed in can be changed. The fields displayed in cannot be changed. The fields
displayed in are already changed but are not used. Click Apply to save the changes. The Apply
button is available after a field is changed regardless of selection of a record.
----End
Context
The U2000 carries out the correlation rule in higher severity, and then the rule in lower severity.
When the severities of two correlation rules are the same, the U2000 carries out them according
to the sequence they are loaded to the correlation analysis template.
Procedure
Step 1 Choose Alarm Settings > Correlation (application style) or Fault > Settings > Correlation
(traditional style) from the main menu.
----End
NOTICE
The alarm correlation rules are the basis for alarm correlation analysis and are closely related to
the analysis result. Exercise caution when you set the alarm correlation rules. You are advised
to use the default alarm correlation analysis rules.
Trail alarm correlation analysis is categorized into dynamic analysis and static analysis.Choose
Fault > Correlation Analysis > Trail Alarm Correlation Rules (traditional style) from the
main menu or select Fault Management in Application Center and choose Alarm
Diagnosis > Correlation Analysis > Trail Alarm Correlation Rules (application style) from
the main menu. Select the Enable Automatic Correlation Analysis check box in the dialog
box that appears to enable dynamic analysis. To enable static analysis, clear the Enable
Automatic Correlation Analysis check box.
NOTE
l Dynamic analysis: Alarm correlation analysis starts automatically 5 seconds after an alarm is reported.
l Static analysis: Alarm correlation analysis starts only after you choose Fault > Correlation
Analysis > Analyze Trail Alarm Correlation (compatibility style) from the main menu or select
Fault Management in Application Center and choose Alarm Diagnosis > Correlation Analysis >
Analyze Trail Alarm Correlation (application style) from the main menu.
NE1, NE2, and NE3 form a non-protection (NP) chain with services running between each two
of them. If the fiber between NE1 and NE2 is disconnected, NE2 reports the R_LOS alarm.
Meanwhile NE2 and NE3 report a large number of TU_AIS alarms. The alarm cause shows that
these TU_AIS alarms are derived from the R_LOS alarm on NE2. You can set alarm correlation
rules to analyze the root alarm R_LOS, which reduces the number of alarms and facilitates fault
location.
The alarm correlation rules can be used to adjust root alarms and correlative alarms to higher
severities on condition that the alarms comply with the alarm correlation rules. For example,
TU_AIS is a major alarm. If you set TU_AIS as a correlative alarm of R_LOS and adjust TU_AIS
to a higher severity, a TU_AIS alarm is adjusted to a critical alarm only when the TU_AIS alarm
is derived from R_LOS. If the TU_AIS alarm is not derived from R_LOS, it is still displayed
as a major alarm on the U2000.
NE1, NE2, and NE3 form an NP chain with services running between each two of them. If the
fiber between NE1 and NE2 is disconnected, NE2 reports the R_LOS alarm. Meanwhile NE2
and NE3 report a large number of OCH_LOS-P alarms. The alarm cause shows that these
OCH_LOS-P alarms are derived from the R_LOS alarm on NE2. You can set alarm correlation
rules to analyze the root alarm R_LOS, which reduces the number of alarms and facilitates fault
location.
The alarm correlation rules can be used to adjust root alarms and correlative alarms to higher
severities on condition that the alarms comply with the alarm correlation rules. For example,
OCH_LOS-P is a major alarm. If you set OCH_LOS-P as the correlative alarm of R_LOS and
adjust OCH_LOS-P to a higher severity, an OCH_LOS-P alarm is adjusted to a critical alarm
only when the OCH_LOS-P alarm is derived from R_LOS. If the OCH_LOS-P alarm is not
derived from R_LOS, it is still displayed as a major alarm on the U2000.
For example, if a fiber is cut, the SPI function module of the optical board detects the R_LOS
alarm (root alarm). For SDH equipment, this alarm in turn causes the RST function module in
the regenerator section (RS) to generate alarms (correlative alarm) such as RLOF, R_OOF,
B1_SD and B1_EXC. For WDM equipment, the correlative alarms, such as OCH_LOS-P,
OTU2_SSF, OTU2_AIS, OTU2_LOM, and OTU1_SSF, may be generated. To prevent this
problem, you can enable alarm correlation suppression to mask correlative alarms, which helps
you identify root alarms.
Figure 7-15 illustrates the alarm flow of each function module of the SDH equipment. In this
flow, you can view the relationship among alarm maintenance signals generated by each function
module of the SDH equipment.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Only SDH NEs, WDM NEs, and WDM NEs (NA) support trail alarm correlation analysis.
Procedure
Step 1 Choose Fault > Correlation Analysis > Trail Alarm Correlation Rules (traditional style)
from the main menu or select Fault Management in Application Center and choose Alarm
Diagnosis > Correlation Analysis > Trail Alarm Correlation Rules (application style) from
the main menu.
Step 3 Set Alarm 1, Alarm 2, Conditions, and Action for the new trail alarm correlation rule.
Step 4 Optional: Select the Enable Automatic Correlation Analysis check box as required.
NOTE
If you select Enable Automatic Correlation Analysis, alarm correlation analysis is automatically
performed when alarms are reported and you can view root alarms in the Browse Current Alarm window.
If you do not select Enable Automatic Correlation Analysis, you must manually perform alarm
correlation analysis and view root alarms in the trail alarm analysis window.
If the Enable Alarm Correlation Rules check box is selected during the setting of trail alarm correlation
rules, the U2000 analyzes alarm correlations based on the preset rules. If the check box is not selected, the
U2000 analyzes alarm correlations based on the default rules. If an alarm does not meet user-defined rules,
the U2000 analyzes the alarm correlation based on the default rules.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Only SDH NEs, WDM NEs, and WDM NEs (NA) support trail alarm correlation analysis.
l The trail alarm correlation rules have been created.
Context
l Trail alarm correlation rules apply only to trail alarms.
l Root alarms can be analyzed in two modes: dynamic analysis and static analysis.
– In dynamic analysis, the U2000 performs correlation analysis automatically when an
alarm is reported.
– In static analysis, you must manually perform correlation analysis.
l Alarm correlation analysis rules can be used only when an alarm triggers another alarm
within 5 seconds.
l The rules do not apply to alarms on protection routes.
Procedure
l Analyze root alarms in static mode.
1. Choose Fault > Correlation Analysis > Analyze Trail Alarm Correlation
(traditional style) from the main menu or select Fault Management in Application
Center and choose Alarm Diagnosis > Correlation Analysis > Analyze Trail
Alarm Correlation (application style) from the main menu.
2. In the dialog box that is displayed, select a time segment and click OK.
3. In the dialog box that is displayed, click OK. Obtain the root alarm information in the
Browse Root Alarm window.
l Analyze root alarms in dynamic mode.
NOTE
In dynamic mode, each alarm is analyzed for three times. The U2000 displays the analysis result
after 1 minute. The total analysis time depends on the number of alarms.
1. Choose Fault > Correlation Analysis > Trail Alarm Correlation Rules (traditional
style) from the main menu or select Fault Management in Application Center and
choose Alarm Diagnosis > Correlation Analysis > Trail Alarm Correlation
Rules (application style) from the main menu.
2. If you select Enable Automatic Correlation Analysis, alarm correlation analysis is
automatically performed when alarms are reported.
3. Choose Fault > Browse Current Alarm (traditional style) from the main menu or
select Fault Management in Application Center and choose Browse Alarm >
Browse Current Alarm (application style) from the main menu. Right-click a root
alarm and choose Query Correlative Alarms from the shortcut menu.
The Correlative Alarms dialog box is displayed, showing the correlative alarms
suppressed by this root alarm.
----End
Procedure
Step 1 Choose Alarm Settings > Correlation (application style) or Fault > Settings > Correlation
(traditional style) from the main menu.
Step 2 On the Alarm/Event Frequency Analysis tab page, set an alarm or event frequency analysis
rule.
----End
Context
l An alarm is defined as an intermittent alarm when the time taken to clear the alarm is less
than or equal to a specified value.
l An event is defined as a repeat event when it occurs within a time that is less than or equal
to a specified value.
l The U2000 discards the intermittent alarms or repeat events that meet the rule. Only the
first repeat event or cleared intermittent alarm is displayed.
Procedure
Step 1 Choose Alarm Settings > Correlation (application style) or Fault > Settings > Correlation
(traditional style) from the main menu.
Step 2 On the Intermittent Alarm/Repeat Event Analysis tab page, set an intermittent alarm or repeat
event analysis rule.
----End
Procedure
Step 1 Choose Alarm Settings > Correlation (application style) or Fault > Settings > Correlation
(traditional style) from the main menu.
Step 2 On the Acknowledged and Uncleared Alarm Time Analysis tab page, set the acknowledged
and uncleared alarm time analysis rule.
----End
Operation Guide
Parameter Setting
When a link to an NE is faulty, alarm M is generated for the NE. At the same time, a large number
of similar alarms N are generated by this NE or other NEs because of this faulty link. Therefore,
the root alarm of fault alarms N is fault alarm M. In correlation analysis, you only need to analyze
and handle alarm M but do not need to analyze alarm N. By setting an alarm correlation analysis
rule, you can suppress alarm N that is generated after alarm M and ignore alarms N.
Operation Guide
Choose Alarm Settings > Correlation (application style) or Fault > Settings >
Correlation (traditional style) from the main menu. In the Correlation window, click the
Correlation Analysis tab.
2. Create an alarm correlation analysis rule and set the associated parameters.
Click Add and set the parameters according to the following table.
Parameter Setting
Background
If major alarm M is reported more than 5 times in 30 minutes, the service availability is
considered be greatly decreased. You need to rectify the fault to recover the service availability.
To handle the alarm in a timely manner, you can set the alarm or event frequency analysis rules.
You can set the triggering condition to 5 times within 30 minutes. If major alarm M is reported
more than 5 times in 30 minutes, the alarm severity changes to critical.
Operation Guide
Parameter Setting
Background
If you receive minor alarm M frequently in a short period of time, the state of a device or service
frequently switches between normal and abnormal. To deal with the situation, you can set
intermittent alarm or repeat event analysis parameters. If alarm M is reported and cleared 5 times
in 10 seconds, it is discarded.
Operation Guide
Parameter Setting
Intermittence/ Set it to 5.
Repeat Times
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The alarm attribute template that meets the alarm reporting status is customized first.
l It applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
l If you use the template to set the alarm automatic reporting status, you are an NMS user
with "Maintenance Group" authority or higher.
l After you set alarms to be not automatically reported, if alarms are generated on an NE,
the NE does not automatically report them to the U2000. You can use the U2000, however,
to synchronize and query the alarms so that the alarms are reported to the U2000.
Procedure
Step 1 Choose Fault > Settings > NE Alarm/Event Config (traditional style) from the main menu or
select Fault Management in Application Center and choose Alarm Settings > NE Alarm/
Event Config (application style) from the main menu.
Step 2 Choose SDH/WDM/NAWDM from the Function Tree. In the right pane, select the pre-
customized template from the Template drop-down list and click Apply to. The Apply Alarm
Attribute Template to NE dialog box is displayed.
NOTE
If the appropriate alarm attribute template is not available, you need to 7.7.4 Customizing Alarm/Event
Attribute Template first.
Step 3 Select the Alarm Auto-Report in the Alarm Attribute group box.
Step 4 Select the NE you need from the List of Optional Objects, and then click to move
NEs to List of Selected Objects. Click OK.
NOTE
When you select more than five NEs for a batch operation, a confirmation dialog box is displayed informing
you that the operation will be time-consuming. You can cancel or continue the operation.
Step 5 After the operation is complete, the Operation Result dialog box is displayed. Click Close.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l If you use the template to set the alarm suppression status, you are an NMS user with
"Maintenance Group" authority or higher.
l It applies to the MSTP, WDM, WDM (NA), RTN, marine, PTN 9x0 series NEs.
Context
After you set alarms to be not automatically reported, if alarms are generated on an NE, the NE
does not automatically report them to the U2000. You can use the U2000, however, to
synchronize and query the alarms so that the alarms are reported to the U2000.
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > Alarm Severity and Auto Reporting
from the Function Tree.
Step 2 Set the Auto Reporting Status for the alarms and click Apply. The Operation Result dialog
box is displayed.
NOTE
If you have already created an alarm attribute template, you can click Use Template to set the automatic
reporting status for the alarms.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The security equipment does not support the function of synchronizing the network-wide
current alarms.
Procedure
Step 1 Choose Fault > Settings > Options (traditional style) from the main menu or select Fault
Management in Application Center and choose Alarm Settings > Options (application style)
from the main menu.
Step 2 In the Alarm Options dialog box, in the navigation tree on the left, select Auto Synchronize.
In the dialog box that is displayed, set the alarm synchronization parameters.
l Synchronize all alarms at NMS start indicates that the U2000 automatically synchronizes
the alarms with those on all the NEs when it is started.
The After LCT user logout parameter is available only when you select the Transmit Common
component during the installation of the U2000.
----End
Context
l Different user groups have different operation rights to set alarm or event mask rules.
– You are an NMS user with Operator Group authority or higher can add, delete, modify,
import, and export alarm or event mask rules.
– The users in the operator group can delete and modify the shielding rules created only
by other users in the operator group or users in the maintenance user group.
– The users in the maintenance user group can delete and modify the shielding rules
created only by other users in the maintenance user group or users in the operator group.
– The users in the Administrators group can delete and modify the shielding rules created
by users in the administrator, operator, and maintenance user groups.
– Only users in the Administrators group can add or delete NE Type on the Alarm
Source and Event Source tab pages.
l The mask operation takes effect only for the alarms reported in the validity period after the
mask rule is enabled. The mask operation does not take effect for the alarms reported before
the mask rule is set.
l If both the alarm or event redefinition and alarm mask rule are set for an alarm or event,
the alarm or event is masked and then redefined. Therefore, the alarm or event is masked
based on the original attributes (the attributes before redefinition) of the alarm or event.
l A maximum of 200 alarms or events mask rules are supported.
l If the following conditions are met, all alarms or events are masked and cannot be reported.
– The mask rule is enabled.
– The alarm or event name is not selected.
– All severities of the alarms or events are selected.
– All types of the alarms or events are selected.
– The selection mode on the Alarm Source tab is All objects for the mask rule.
Procedure
Step 1 Choose Alarm Settings > Mask Rules (application style) or Fault > Settings > Mask Rules
(traditional style) from the main menu.
Step 2 In the Mask Rules window, set an alarm or event mask rule.
----End
Example
Background:
l The Start time and End time in the mask rule refer to the time for generating the alarm
instead of the time when the alarm is reported to the U2000.
l In the mask rule, the U2000 supports alarm or event masking in three time modes: NE
time, Server time, and Client time. The local time varies according to time zones. For
example, assume that the NE is in the GTM+4 zone, the U2000 server is in the GTM+8
zone, and the user monitors the server in the GTM+9 zone. That is, the U2000 client is in
the GTM+9 zone. If the NE generates an alarm on 01/20/2012 17:00:00 in the local time,
the corresponding server time is 01/20/2012 21:00:00, and the corresponding client time
is 01/20/2012 22:00:00.
l In an alarm or event mask rule, Validity Period and Time Period (Server Time) are in
the AND relationship. That is, the alarm or event rule is applied on the days and in the time
segments specified in Time Period (Server Time) within the validity period specified by
Start time and End time.
Scenario:
l Assume that the NE is in the GTM+4 zone, the U2000 server is in the GTM+8 zone, and
the U2000 client is in the GTM+9 zone. Create an alarm mask rule that masks the ALM-34
The Disk Usage Is Too High (Warning) alarms reported by the NE from client time
01/20/2012 20:00:00 to 01/21/2012 10:00:00, and the alarm mask rule is applied from 09:00
to 18:00 on Friday, Saturday, and Sunday.
l The NE generated anALM-34 The Disk Usage Is Too High (Warning) alarm at 01/20/2012
17:00:00 and 01/21/2012 07:00:00 local time.
Procedure:
1. In the Mask Rules window, click Add and select Alarm Mask Rule.
2. In the Add Alarm Mask Rule dialog box, select the ALM-34 The Disk Usage Is Too High
(Warning) alarms and NEs. Set Time Mode to By client time, Start time to 01/20/2012
20:00:00, and End time to 01/21/2012 10:00:00, and click Next. Set Rule priority to
Very high, select Enable, and click Finish.
The U2000 masks the alarms that are generated between 01/20/2012 20:00:00 and
01/21/2012 10:00:00 (including 01/20/2012 20:00:00 and 01/21/2012 10:00:00) at client
time and whose corresponding server time is between 09:00 and 18:00 on Friday, Saturday,
and Sunday.
Result:
The following table describes the results of masking the ALM-34 The Disk Usage Is Too High
(Warning) alarms generated at 01/20/2012 17:00:00 and 01/21/2012 07:00:00 local time based
on the configured alarm mask rule.
Context
After an alarm is acknowledged automatically and reaches the life cycle (see 7.5.11 Setting the
Lifecycle of the Current Alarm), the alarm becomes a historical alarm. For details about how
to query a historical alarm, see 7.8.12 Browsing the Historical Alarms.
Procedure
Step 1 Choose Alarm Settings > Options (application style) or Fault > Settings > Options (traditional
style) from the main menu.
Step 2 In the Alarm Options dialog box, select Auto Acknowledgment from the navigation tree on
the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the Auto Acknowledgment area, set an automatic alarm acknowledgment rule.
----End
Context
l The redefinition rule takes effect only for the alarms reported during the validity period of
the redefinition rule.
l The query and statistical results are displayed based on alarm or event redefinition.
l The redefinition for alarm or event names takes effect for all NEs. It cannot take effect only
for the specified NEs. The redefinition of types and severities can take effect for either the
specified NEs or all NEs. Only a user in the Administrators user group is allowed to
redefine the alarm or event names.
l In redefinition setting, the validity period takes effect for the redefinition of types and
severities, and does not take effect for the redefinition of names. The validity period is
subject to the server time.
Procedure
Step 1 Choose Alarm Settings > Redefine (application style) or Fault > Settings > Redefine
(traditional style) from the main menu.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The alarm attribute template that meets the alarm severity customized first. You can refer
7.7.4 Customizing Alarm/Event Attribute Template.
l It applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
NOTE
If you apply the alarm template that contains the changed alarm severity and reporting mode to another
NE, the settings of alarm suppression and alarm reversion for the NE are lost.
Procedure
Step 1 Choose Fault > Settings > NE Alarm/Event Config (traditional style) from the main menu or
select Fault Management in Application Center and choose Alarm Settings > NE Alarm/
Event Config (application style) from the main menu.
The NE Alarm/Event Config tab is displayed.
Step 2 Choose SDH/WDM/NAWDM from the Function Tree. In the right pane, select the pre-
customized template from the Template drop-down list and click Apply to. The Apply Alarm
Attribute Template to NE dialog box is displayed.
NOTE
If the appropriate alarm attribute template is not available, you need to customize a template first.
Step 3 Select the Alarm Severity in the Alarm Attribute group box.
Step 4 Select the NE you need from the List of Optional Objects, and move it to List of Selected
Objects. Click Apply. After the operation is complete, the Operation Result dialog box is
displayed.
Step 5 Click Close.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l It applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 In the Main Topology, right-click the failed object and choose NE Explorer from the shortcut
menu.
Step 2 In the NE Explorer, select a board and choose Alarm > Alarm Severity and Auto Reporting
from the Function Tree.
----End
Prerequisites
l For NE/CX/ME serial NEs: You are an NMS user with Operator Group authority or
higher.
l For SDH/WDM/NAWDM serial NEs: You are an NMS user with Operator Group
authority or higher.
Procedure
l For NE/CX/ME serial NEs:
1. Choose Fault > Settings > NE Alarm/Event Config (traditional style) from the main
menu or select Fault Management in Application Center and choose Alarm
Settings > NE Alarm/Event Config (application style) from the main menu.
2. Choose NE/CX/ME from the NE Alarm/Event Config navigation tree.
l If you need to modify a non-default template, select the template from the Template
name drop-down list and modify the alarm/event suppression time on the template. Then,
click Save.
l You can select an existing template and set parameters on this template. After the settings,
click Save as to save the new template.
5. In the Create Template dialog box, enter Template name and Template
description. Then, click OK.
6. On the created attribute template, you can select alarms/events to be suppressed
according to actual situations, and set Cause Persist Time and Clear Persist Time
for these alarms/events.
NOTE
l During settings the alarm/event suppression time, the value turns red if the value range is
changed.
l During settings the alarm/event suppression time, the suppression time restores the default
value after clicking Default.
7. After the suppression time is set, click Save.
l For SDH/WDM serial NEs:
1. Choose Fault > Settings > NE Alarm/Event Config (traditional style) from the main
menu or select Fault Management in Application Center and choose Alarm
Settings > NE Alarm/Event Config (application style) from the main menu.
2. Choose SDH/WDM/NAWDM from the NE Alarm/Event Config navigation tree.
3. In the NE Alarm/Event Config window, the Template is Default Template.
NOTE
l If you need to modify a non-default template, select the template and modify the alarm/
event suppression status on the template. Then, click Save.
l You can select a template and set parameters on this template. After the settings, click Save
as to save the new template.
4. In the NE Alarm/Event Config window, click Refresh to update the information
displayed in the window.
5. In the NE Alarm/Event Config window, you can select alarms/events to be
suppressed according to actual situations, and set Status for these alarms/events.
NOTE
During setting the alarm/event suppression time, the Event turns purple if the value range of
Status is changed.
6. After the suppression time is set, click Save.
----End
Follow-up Procedure
Apply the created template to NEs or boards for alarm/event suppression.
Context
l NOTICE
Running commands rashly may have a negative impact on the system. The following types
of alarm or event postprocessing commands are prohibited: infinite-loop commands and
GUI commands. The postprocessing scripts can start and stop automatically. You are
advised to test the scripts before you use them. For details about the example of the
postprocessing script, see 7.5.8 An Instance of the Alarm or Event Postprocessing
Script.
l The procedure for setting an alarm postprocessing rule is the same as that for setting an
event postprocessing rule. The following example describes how to set an alarm
postprocessing rule.
Procedure
Step 1 Choose Alarm Settings > Postprocessing (application style) or Fault > Settings >
Postprocessing (traditional style) from the main menu.
Step 2 In the Postprocessing window, click Add, and then choose Alarm Postprocessing Rule.
Step 3 On the Basic Settings tab page of the Add Alarm Postprocessing Rule dialog box, set the
parameters such as Alarm name, Severity, and Type.
Step 4 Click the Alarm Source tab. On the Alarm Source tab page, set the alarm source. Click
Next.
Step 5 In the Add Alarm Postprocessing Rule dialog box, set the Postprocessing Action , Start
time, End time, and Remarks. Select Enable.
NOTE
The name of the script in Postprocessing Action can be in the format script name+parameters. The script
must meet the following requirements:
l The script exists in common/alarm/bin/fm/action in the installation directory of the U2000 server on
Solaris or SUSE Linux. The file format of the script is *.sh.
l The script exists in common\alarm\bin\fm\action in the installation directory of the U2000 server on
Windows. The file format of the script is *.cmd.
l The syntax of the script is correct, and the script is executable.
----End
An Instance of a Script
l On Solaris
/opt/oss/server/common/alarm/bin/fm/action/action.sh
#!/bin/sh
cnt=0;
total=$#;
while [ $cnt -lt $total ]
do
echo $1>>/opt/oss/server/common/alarm/bin/fm/action/a.txt;
shift;
cnt='expr $cnt + 1';
done
Prerequisites
You have the right of Manage Rules for the Summarized Parallel Alarm.
Context
After the setting, ALM-831 Summarized Parallel Alarm is generated if the summarized parallel
alarm rules are met.
Procedure
Step 1 Choose Fault > Settings > Summarize Parallel Alarm (traditional style) from the main menu
or select Fault Management in Application Center and choose Alarm Settings > Summarize
Parallel Alarm (application style) from the main menu.
Step 2 In the Summarize Parallel Alarm window, set summarized parallel alarm rules.
For details about the parameter description, see Summarized Parallel Alarm Rule.
Operation Procedure
Deleting alarm rules 1. Select the rule you want to delete. Click Delete.
NOTE
You can choose more than one record by using Shift or Ctrl.
2. In the Confirm dialog box, click Yes.
----End
Context
l An ADMC alarm is defined with a specific fault generation condition but without a fault
rectification condition. When the fault generation condition is met, an alarm is generated,
but a clear alarm cannot be generated. Maintenance personnel needs to check whether the
fault is already rectified. If the fault is already rectified, maintenance personnel needs to
clear the alarm manually.
l After you set conversion from an event to an ADMC alarm, the alarm is displayed only in
the current alarm. After you cancel the settings, the newly reported events are displayed in
the event list.
Procedure
Step 1 Choose Alarm Settings > Set Events as ADMC Alarms (application style) or Fault >
Settings > Set Events as ADMC Alarms (traditional style) from the main menu.
Step 2 In the Set Events as ADMC Alarms dialog box, select an event from Available Events and
move it to Selected Events.
You can also enter an event name in Filter by name of Available Events or Selected Events,
and press Enter to query the event.
NOTE
The icons in the lower part of the Filter by name text box are described as follows:
----End
Context
The alarm record is deleted from the current alarm if the later time between the acknowledgment
time and the clear time for the auto detected auto cleared (ADAC) alarm, or the acknowledgment
time of the automatically detected and manually cleared (ADMC) alarm meets the lifecycle
conditions.
Procedure
Step 1 Choose Alarm Settings > Options (application style) or Fault > Settings > Options (traditional
style) from the main menu.
Step 2 In the Alarm Options dialog box, choose Lifecycle from the navigation tree on the left.
Step 3 In the Lifecycle area, set the length of time acknowledged and cleared alarms are displayed in
the current alarm.
Step 4 Click OK.
----End
alarm is reported to the ports connected by fibers. This helps the maintenance engineer to focus
on the root alarms or the highly concerned services.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series,
Marine series, Router series, Switch series and Security NEs.
Context
l Fiber Relation Alarm includes only fiber-related alarms.
l The setting of Status takes effect only on subsequent alarms that will be reported to the
U2000. For the existing alarms on the U2000, fibers are not related to the alarm status.
l For multiple clients, if Status of an alarm is changed on one client, the latest configuration
of the alarm can be displayed on the U2000 by the query function of the other clients.
Procedure
Step 1 Choose Fault > Correlation Analysis > Fiber Relating Alarm (traditional style) from the main
menu or select Fault Management in Application Center and choose Alarm Diagnosis >
Correlation Analysis > Fiber Relating Alarm (application style) from the main menu.
Step 2 In the dialog box that is displayed, click Query to query the status of the fiber-related alarm.
Step 3 In the dialog box that is displayed, select the alarm to be related, and then select Related or Not
Related from the drop-down list in the Status column.
NOTE
If you do not need to monitor a certain type of alarms, select the alarm, and then select Not Related from
the drop-down list in the Status column. Then alarm's relation to fibers is deleted.
Step 5 Click Query to query the latest configuration of the alarm from the database. The query result
is displayed on the U2000.
----End
Context
l Alarm or event northbound filtering rules are applicable only to alarms or events that are
generated after the rules are set. Alarms or events generated before the rules are set cannot
be filtered based on the rules. Alarm or event northbound filtering rules take effect for
multiple upper-layer OSS.
l If you do not set the northbound filtering rules, all alarms or events are reported by default.
If you set the northbound filtering rules, only the alarms or events that meet the filtering
rules are reported.
l The alarms filtered by the northbound filtering rules and their acknowledged,
unacknowledged, and cleared alarms are not reported to the upper-layer OSS even the
northbound filtering rules are deleted, modified, or disabled.
Procedure
Step 1 Choose Alarm Settings > Northbound Filtering Rules (application style) or Fault >
Settings > Northbound Filtering Rules (traditional style) from the main menu.
Step 2 In the Northbound Filtering Rules window, set an alarm or event northbound filtering rule.
----End
Alarm Panel
The alarm panel consists of a shortcut icon and four color blocks in the upper right corner of the
toolbar on the client. For details, see Figure 7-16. These color blocks are alarm lamps, which
indicate critical, major, minor, and warning alarms respectively. The number in each color block
indicates the number of alarms at this severity on the U2000. When an alarm is generated, the
corresponding color block blinks. Through the alarm lamps, you can know the generation of
alarms, alarm severity, and statistics of alarms of each severity. When you move the pointer to
alarm lamps, the U2000 displays the number of alarms. For details about how to set the tooltip
information, see 7.6.10 Setting the Format of the Alarm Lamp ToolTip.
NOTE
By default, four types of color blocks are displayed on the U2000 client. You can hide the color blocks of
which you do not care about the severity. For details, see 1.8.13 Setting the Display Properties of New
Alarm/Event.
Choose Browse Alarm > Display Alarm Panel (application style) or Fault > Display Alarm
Panel (traditional style) from the main menu, or click on the U2000 client to open the alarm
panel. Click the alarm panel next to Option. See Figure 7-17.
NOTE
l Alarm indicator blinking during alarm generation must meet the following conditions:
l You do not choose Browse Alarm > Disable Alarm Sound (application style) or Fault > Stop
the Alarm Sound Permanently (traditional style) from the main menu.
l You do not merge the newly reported alarms. For details about the rules for merging alarms, see
7.8.10 Browsing the Current Alarms.
l The new alarm meets the rule of generating a sound. For details about how to set the rule for
generating a sound, see 7.6.3 Setting the Alarm Sound.
l You have selected Alarm lamps blink when alarm is received on the alarm panel.
l Generating a sound during alarm generation must meet the following conditions:
l You do not choose Browse Alarm > Disable Alarm Sound (application style) or Fault > Stop
the Alarm Sound Permanently (traditional style) from the main menu.
l You do not merge the newly reported alarms. For details about the rules for merging alarms, see
7.8.10 Browsing the Current Alarms.
l The new alarm meets the rule of generating a sound. For details about how to set the rule for
generating a sound, see 7.6.3 Setting the Alarm Sound.
NOTE
l If the Alarm panel pops up when alarm is received check box is selected but the newly reported
alarm logs are merged, the message about alarm generation is not displayed.
l In the Alarm Panel dialog box, right-click a template that does not have and choose Show On
Alarm Lamp from the shortcut menu. The alarm indicator collects alarm statistics based on this
template.
l Both the alarm box and the alarm panel notify users of new alarms in audible and visual mode. The
alarm box is the hardware and does not display alarm statistics. You can set search criteria to find the
alarms that are sent to the alarm box on the client. Compared with the alarm box, the alarm panel is a
window on the client. You can click Add at the bottom of the Alarm Panel dialog box to bind current
alarm templates to the alarm panel. The Alarm Panel dialog box displays alarm statistics based on
alarm states and severities according to templates in real time.
l If a user changes the name, status, or search criteria of a template in the alarm panel on client B, the
changes can be synchronized to client A only after the user restarts client A.
Icon Description
Indicates that the template in the alarm panel does not collect
information about the alarms of this severity.
NOTE
l The color of this icon is the same as the color of the corresponding
alarm severity.
l You can specify colors for various alarm severities in
Preferences.
Procedure
l Set properties of the alarm panel.
1. Choose Browse Alarm > Display Alarm Panel (application style) or Fault > Display
Alarm Panel (traditional style) from the main menu or click on the toolbar.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor,
Not Alarmed.
2. In the Alarm Panel dialog box, click Option, and then set whether to display the
alarm panel on startup, and whether to enable the alarm panel to display or the alarm
indicator to blink when alarm received.
l Add alarm templates to the alarm panel.
1. In the Alarm Panel dialog box, click Add.
NOTE
You can select a template except All objects in the Alarm Panel dialog box, and then click
Delete to delete the template.
2. In the Choose dialog box, select one or more current alarm templates. Then click
OK.
NOTE
l In the Choose dialog box, only the templates whose types are Current alarm template
are displayed. For details about how to create an alarm template, see 7.7.2 Creating an
Alarm/Event Template.
l In the Choose dialog box, do not select the template that already exists in the Alarm
Panel dialog box.
l If you select Display the templates created by the current user only, the Choose dialog
box displays only the template created by yourself.
3. In the Alarm Panel dialog box, right-click a template and choose Show On Alarm
Lamp from the shortcut menu.
NOTE
The template with the icon is the alarm indicator display template that you set.
4. In the Confirm dialog box, click Yes.
The alarm indicator on the right of the toolbar counts alarms of all severities according
to the filter criteria defined in the template.
----End
Context
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
l Either the audio file in the U2000 or a user-defined audio file is used.
l The U2000 supports .au and .wav audio files. The audio files of the .wav type can be
recorded in two formats: PCM and Microsoft ADPCM. Only the audio files of the .wav
type in the PCM format are supported.
l The audio files of the four alarm severities are located in client\client\plugins
\alarmclientbase\style\conf\ in the U2000 client installation folder. The file names are
Critical.wav, Major.wav, Minor.wav and Warning.wav.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, choose Sound Settings in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 You can perform the following operations on each row in the Sound Settings area:
1. Select the check boxes in the Enable column for required alarms.
You can set the alarm sound based on the severity and status of the alarm or alarm name.
For details, see Table 7-10.
Sound by alarm name 1. Click Sound by alarm If the alarm meets the Sound by
name. alarm name rule and alarm
2. In the Sound Settings severity such as Critical,
area, click Major, Minor, or Warning,
the sound is generated based on
and the alarm severity.
select the alarm name.
2. Click the path of audio files and then click on the right. Select the file for the alarm
sound.
3. Click the play time, and then click the fine tune button to set the duration of the alarm sound.
NOTE
l The alarm length ranges from 0 to 1000, in the unit of second. 0 indicates that the alarm length
is unlimited.
l If you enable automatic blinking of alarm indicators on the alarm panel, when an alarm is reported,
the alarm indicator corresponding to this alarm blinks for the preset duration. If alarms at different
severities are generated, only the alarm indicator corresponding to the highest alarm severity
blinks.
l If you set the alarm length of the alarm sound of an alarm severity to 0, when an alarm of this
severity is reported, the alarm indicator keeps blinking until the alarm is cleared.
----End
Context
l After setting, the alarm icon in the topology view, the alarm record you have queried, and
the alarm indicator on the alarm panel are displayed in the specified colors.
l By default, the U2000 provides four types of colors for alarms. critical: , major:
, minor: , and warning: .
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, choose Color Settings in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the Color Settings area, click in each row to select the colors of alarms.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l The alarm box is assembled and functioning correctly. To check whether an alarm box is
assembled correctly, perform the following steps:
Connect the power and serial cables of the alarm box. Do not connect the alarm box to the
U2000 for the moment. Power on the alarm box. Wait until the alarm box plays a sound
that indicates a disconnection. This indicates that the alarm box is assembled. If the alarm
box is not assembled, contact Huawei technical support engineers.
l The computer serial port number is available.
Context
l If several clients of the same version are running on a host, you can set an alarm box only
on the client that is first started on the host.
l The setting takes effect for all the users that log in to different clients.
l For the U2000 to control the alarm box, you need to correctly set the communication
parameters of the alarm box on the Communication Parameters tab, and enable the alarm
box.
l The alarm box beeps in two ways. In the case of a critical and major alarm, the alarm box
keeps beeping until it is manually stopped or until the alarm is cleared. In the case of a
minor and warning/not alarmed alarm, the alarm box beeps for a fixed time period (one
minute) and stops. It can also be manually stopped.
Procedure
Step 1 Choose Fault > Settings > Options (traditional style) from the main menu or select Fault
Management in Application Center and choose Alarm Settings > Options (application style)
from the main menu.
Step 2 In the Alarm Options dialog box, choose Alarm Box from the navigation tree in the left pane.
Step 4 Select the serial port that communicates with the alarm box, and then select the Enable alarm
box check box.
l If the alarm box starts successfully, a message is displayed at the bottom of the client, indicating that
the alarm box is successfully set, the serial port is successfully initialized, and the U2000 successfully
connects to the alarm box.
l If the alarm box fails to start, a message is displayed at the bottom of the client, indicating that the
U2000 fails to connect to the alarm box or the serial port fails to be initialized. Check whether cables
are properly connected to the alarm box and whether the serial port is available.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
l Choose Fault > Stop the Current Alarm Sound (traditional style) from the main menu
or select Fault Management in Application Center and choose Browse Alarm > Disable
Current Alarm Sound (application style) from the main menu. The current alarm sound
played by the audio adapter or alarm box on the client is stopped.
NOTE
The alarm sound is resumed when a new alarm is prompted by the audio adapter or alarm box on the
client.
l Choose Fault > Stop the Alarm Sound Permanently (traditional style) from the main
menu or select Fault Management in Application Center and choose Browse Alarm >
Disable Alarm Sound (application style) from the main menu. The alarm sound is disabled
when an alarm is reported.
NOTE
Choose Browse Alarm > Disable Alarm Sound (application style) or Fault > Stop the Alarm
Sound Permanently (traditional style) again, the alarm sound is resumed when a new alarm is
reported.
l To stop the alarm sound for an alarm severity
1. Choose File > Preferences from the main menu.
2. In the Preferences dialog box, choose Sound Settings from the navigation tree.
3. In the Sound Settings area, clear the check boxes in the Enable column for the alarm
severities whose alarm sounds are to be stopped.
4. Click OK.
l Stopping the Alarm sound of an NE Rack Temporarily
NOTE
It applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except PTN
6900 series) and marine series NEs.
The alarm sound is resumed when a new alarm is prompted by the audio adapter or alarm box on the
client.
1. Right-click an NE on the Main Topology and choose More Alarm Operations >
Clear Alarm Indication from the shortcut menu.
The Operation Result dialog box is displayed.
2. Click Close.
l Stopping the Alarm sound of an NE Rack Permanently
NOTE
l It applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
l The OptiX OSN 1800V V100R003C05 is not equipped with a buzzer and therefore does not
support alarm sounds. Alarm Sound cannot be set for this NE.
l If you enable the alarm sound and the alarm indicator again on the U2000, the alarm sound is
resumed when a new alarm is prompted by the audio adapter or alarm box on the client.
1. In the NE Explorer, select an NE and choose Alarm > NE Alarm Attributes from
the Function Tree.
NOTE
To set alarm sound for multiple NEs: Choose Configuration > NE Batch Configuration >
NE Alarm Attributes (traditional style) from the main menu or select Fix-Network NE
Configuration in Application Center and choose Configuration > NE Batch
Configuration > NE Alarm Attributes (application style) from the main menu.
2. Click Query to query the settings of audible and visual alarm notifications of the NE
from the NE side.
3. Set Alarm Sound and Alarm Indicator of the NE:
– Double-click the Alarm Sound and Alarm Indicator lists respectively, and select
Disabled or Enabled from the drop-down list.
– If you want to set Alarm Sound and Alarm Indicator to Enabled, click
Default.
4. Click Apply. The Confirm dialog box is displayed asking you whether to proceed.
5. Click OK. A prompt message is displayed indicating that the operation is successful.
6. Click Close.
----End
Context
l For the alarm that meets the highlighting condition, if the difference between the local time
of the client and the alarm occurrence time reaches the threshold time for highlighting, the
alarm is highlighted.
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, expand the Alarm Local Terminal Settings node and choose
Highlighting in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the Highlighting area, set the time and alarm status for alarms of a certain severity, and then
select Enable.
NOTE
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, in the navigation tree on the left, expand the Alarm Local
Terminal Settings node, and then select Alarm Fonts.
Step 3 In the Alarm Fonts area, set fonts, sizes, styles, and colors for alarms that are not read and that
are already read.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, expand the Alarm Local Terminal Settings node and choose
Alarm Display Mode in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the Alarm Display Mode area, select an alarm display mode, and set background colors for
different alarm states.
All the other fields The background colors of all the other fields are
displayed based on the state.
All the other fields The background colors of all the other fields are
displayed based on the state.
NOTE
The first column of the current alarm is not rendered, because it is not affected by the setting of the alarm
display mode.
Context
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
l On the alarm panel, alarms lamps in different colors stand for alarms of different severities.
For details about the alarm panel, see 7.6.1 Introduction to the Alarm Panel.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the navigation tree in the Preferences dialog box, expand the Alarm Local Terminal
Settings node and choose Alarm Lamp ToolTip.
Step 3 Under Display mode, set the format of the alarm indicator tip.
If you need to query the number of unacknowledged and uncleared, unacknowledged and
cleared, acknowledged and uncleared, or acknowledged and cleared alarms, select Detailed. If
you need to query the number of uncleared or unacknowledged alarms, select Basic.
Step 4 Click OK.
----End
Context
The settings take effect immediately. They are valid on your other logged-in clients after you
log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the Preferences dialog box, expand the Alarm Local Terminal Settings node and choose
New Alarm/Event in the navigation tree on the left.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 3 In the New Alarm/Event group box, select Alarm Severities Shown at Top of Screen and the
alarm severity.
Step 4 In the New Alarm/Event group box, select Display at the top or Display at the bottom.
Step 5 In the Alarm Severities Shown in Alarm Lamps group box, select the severity to be displayed
on the alarm indicator.
----End
Context
l Acknowledged and cleared alarms are not displayed in the topology view, because they
indicate that the faults are already rectified. For details about the meaning of each alarm
state, see 7.1.3 Alarm Status.
l A subnet does not generate alarms. However, when the NEs or links in the subnet generate
alarms, the subnet displays the alarms of the highest severity. The alarm display mode for
subnets is the same as that for NEs.
l A container NE can generate alarms. The alarm status display mode for a container NE is
the same as that for an NE. When an NE in a container NE generates an alarm, an alarm
icon appears on the container NE in the topology view. For details, see Icons Indicating
That Alarms Are Contained.
l The settings take effect immediately. They are valid on your other logged-in clients after
you log in again. The settings are invalid for other users.
Procedure
Step 1 Choose File > Preferences from the main menu.
Step 2 In the navigation tree in the Preferences dialog box, choose Topology Status Display.
Step 3 In Topology Status Display, set the alarm display properties in the topology view.
Display Style of Alarm States In Display Style of Alarm States, set the display style of
alarm states.
NOTE
Links support only the Use icon colors display style regardless of
the value of Display Style of Alarm States.
Alarm States to Display in the In Alarm States to Display in the Topology View, set the
Topology View alarm state to be displayed in the topology view.
l If you select only Unacknowledged alarms, only the
unacknowledged alarms of the highest severity are
displayed.
– For NEs, if Use icon colors is selected, the alarm
state is displayed in the color of NE icon frame. If
Use state icons is selected, the alarm state is
displayed in the round icon.
– For links, the links are rendered.
l If you select only Uncleared alarms, only the uncleared
alarms of the highest severity are displayed.
– For NEs, if Use icon colors is selected, the alarm
state is displayed in the color of NE icon. If Use state
icons is selected, the alarm state is displayed in the
triangle icon.
– For links, the links are rendered.
l If you select both Unacknowledged alarms and
Uncleared alarms, for NEs, unacknowledged alarms of
the highest severity and uncleared alarms of the highest
severity generated on NEs are displayed; for links,
unacknowledged alarms and uncleared alarms of higher
severity generated on links are displayed.
NOTE
The unacknowledged alarms and uncleared alarms generated
on links are displayed by rendering the links. Therefore, if you
select both Unacknowledged alarms and Uncleared
alarms, you cannot determine the whether generated alarms
are unacknowledged alarms or uncleared alarms. To check
whether unacknowledged alarms or uncleared alarms are
generated on a link, you can select this link, click on the
topology toolbar, and check the alarm information displayed
on Properties tab page on the Legend & Filter &
Properties panel.
----End
Alarm/Event Template
Alarm/event template consists of the alarm/event browsing template and the alarm/event
attribute template.
Type Description
Browse current alarm by status template Used for browsing the current alarm by status.
Browse current alarm by severity template Used for browsing the current alarm by severity.
Alarm log statistics template Used for collecting statistics on alarm logs.
Event log statistics template Used for collecting statistics on event logs.
Template Sharing
When you create a template, you can set it to be shared. The shared template is visible to all
users.
l The users other than Administrators can open only templates created by users themselves
and shared by other users. Administrators can open all templates.
l The users other than Administrators can set only the templates created by users themselves
to be shared. Administrators can set the templates created by any user to be shared.
Template States
On the U2000 client, you can set the monitoring template, auto loaded template , and default
template for the current user.
l Monitoring template: It is used for the alarm indicator at the upper right corner on the
U2000 client GUI to display the statistics of alarms at different severities. It must be the
current alarm templates.
l Auto loaded template: The U2000 opens some current alarm windows automatically
according to this type of templates after you successfully log in to the U2000 client. You
can set a maximum of five start templates.
l Default template: When a user chooses the menu for querying or collecting statistics on
alarms or events, the U2000 uses this template to open the window corresponding to this
menu. You can set only one default template for a functional window.
Context
l Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style), Browse Alarm > Browse Alarm Logs (application
style) or Fault > Browse Alarm Logs (traditional style), Browse Alarm > Query Event
Logs (application style) or Fault > Browse Event Logs (traditional style), Browse
Alarm > Browse Current Alarm by Severity (application style) or Fault > Browse
Current Alarm by Severity (traditional style), Browse Alarm > Browse Current Alarm
by Status (application style) or Fault > Browse Current Alarm by Status (traditional
style) or Browse Alarm > Query Historical Alarm (application style) or Fault > Browse
Historical Alarm (traditional style) from the main menu. In the Filter dialog box, set search
criteria, and click OK. In the query window, you can click Template in the lower left part
to display a menu list. By choosing a menu from this menu list, you can create, open, save,
save as or delete a query template.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
l Choose Browse Alarm > Alarm Log Statistics (application style) or Fault > Query
Alarm Log Statistics (traditional style) or Browse Alarm > Event Log Statistics
(application style) or Fault > Query Event Log Statistics (traditional style) from the main
menu. In the Filter dialog box, set statistical criteria, and click OK. In the statistics window,
click Template in the lower left part to display a menu list. By choosing a menu from this
menu list, you can create, open, save, save as or delete a statistics template.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
Procedure
Step 1 Choose Alarm Settings > Template Management (application style) or Fault > Settings >
Template Management (traditional style) from the main menu.
Step 3 In the Add Template dialog box, enter a template name and description, select a template type
and template sharing, and then click Next.
NOTE
If you need to add an alarm template to the alarm panel, (see Adding an Alarm Template to the Alarm
Panel), set Type to Current alarm template in the Add Template dialog box.
Step 4 In the Add Template dialog box, set the filter criteria.
----End
Follow-up Procedure
In the Template Management window, you can perform the following operations to set an
alarm or event template.
Delete a template 1. Select one or more templates that do not belong to All
objects, and then click Delete.
2. In the Confirm dialog box, click Yes.
Rename a template 1. Select a template that does not belong to All objects, and
then click Rename.
2. In the Enter the template name dialog box, change the
template name.
3. Click OK.
Modify template attributes 1. Select a template that does not belong to All objects, and
then click Properties.
2. In the Properties dialog box, change the template name,
set the template sharing, and change the description and
filter criteria.
3. Click OK.
NOTE
Right-click a template that does not belong to All objects. Choose
Monitor Template, Default Template, or Startup Template from
the shortcut menu to change the template status, or choose Share to
share the template with other users who have connected to the same
server.
Set template status for the Click Configuration. For details, see 7.7.3 Setting Template
current user Status for the Current User.
Refresh a template Click Refresh. The alarm or event template displayed in the
Template Management window is updated.
Open a template Right-click a template and choose Open from the shortcut
menu.
Save as another template 1. Right-click a template that does not belong to All
objects and choose Save as from the shortcut menu.
2. In the Save Template dialog box, enter a name that is
different from all existing template names, select Shared
template, Default template or Auto loaded template as
required, and click OK.
Context
l Monitoring template: It is used for the alarm indicators in the upper right corner on the
U2000 client GUI to display the statistics of alarms of different severities. It must be the
current alarm templates.
l Startup template: The U2000 opens some current alarm windows automatically based on
the templates after you successfully log in to the U2000 client. You can set a maximum of
five startup templates.
l Default template: When a user chooses the menu for querying or collecting statistics on
alarms or events, the U2000 uses this template to open the window corresponding to this
menu. You can set only one default template for a functional window.
Procedure
Step 1 Choose Alarm Settings > Template Management (application style) or Fault > Settings >
Template Management (traditional style) from the main menu.
Step 3 In the Configuration dialog box, click on the right of Monitor template. Select a
template in the Choose Template dialog box, and click OK.
Step 4 Click on the right of Startup template. In the Available Template navigation tree
in the Choose Template dialog box, select one or more templates, click and click
OK.
NOTE
Step 5 In the Default Template area, click on the right of each type of template. Select a
template in the Choose Template dialog box, and click OK.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The alarm/event attribute template function applies to the MSTP series, WDM series,
WDM (NA) series, RTN series, PTN series (except PTN 6900 series) and marine series
NEs.
Context
l If the alarm/event attribute template is not created, the U2000 handles the alarms or events
reported from NEs according to the default alarm/event attribute template.
l If a template servers is customized on a U2000 server, you are recommended to customize
the same template on other U2000 servers, to ensure that the alarms or events are
consistently monitored on each server.
l You can set different alarm/event management templates for different NEs.
l After a customized alarm/event attribute template is applied to NEs, the alarm/event settings
on the NEs are updated according to the alarm/event attribute template. If the alarm severity
and reporting mode are modified in the alarm/event attribute template and the alarm/event
attribute template is applied to NEs, the settings of the NEs, such as alarm masking and
alarm reversion, are invalid.
Procedure
Step 1 Choose Fault > Settings > NE Alarm/Event Config (traditional style) from the main menu or
select Fault Management in Application Center and choose Alarm Settings > NE Alarm/
Event Config (application style) from the main menu.
After the alarm/event attribute template is applied to the NE, the U2000 automatically handles the alarms
or events reported from the NE according to the settings in the template.
----End
Context
NOTE
l If the Router series, Switch series, PTN 6900 series, Access series and Security NEs support the SNMP
protocol, the trap receiver needs to be configured before network alarms/events can be monitored. For
details, see the 7.8.2 Setting Trap Parameters on an NE.
l The U2000 can monitor alarms/events reported by the third-party NEs whose IP addresses are in the
same network segment as the U2000.
Context
The U2000 displays only the initial 100,000 alarms. Other alarms are invisible and stored in the
U2000 database. These alarms can be filtered out and viewed by specifying filter criteria in the
alarm browsing window.
When alarms are generated at a very high speed and it exceeds the NMS processing ability, the
alarm buffer space is exhausted. In this case, the NMS will work in an alarm storm state and
discard some alarms.
If the communication between the U2000 and the NE is interrupted, when the NE is restarted,
the U2000 automatically synchronizes the alarm library of the SCC to keep the alarm data on
the U2000 synchronous with the alarm data on NEs.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l This operation applies to the following SNMP NE: Router series, Switch series, PTN 6900
series, Access series and Security NEs.
l Ensure that the source port of trap packets configured on the NE is consistent with the
source port for sending packets configured on the NMS. Otherwise, the NMS cannot receive
trap packets.
Context
To start the trap receiver on the U2000, ensure that Trap Receiver Process on the Process
Monitor tab is in the running state. This process is automatically started by default. If it is not
automatically started, log in to the System Monitor client, click the Process Monitor tab, right-
click Trap Receiver Process, and then choose Start the Process from the shortcut menu.
NOTE
The following section uses routers as an example to describe how to set trap parameters on the NE. For
details, see the documents relevant to the NE.
Procedure
Step 1 Select a NE in the Main Topology, right-click the NE and choose Tools > SSH from the shortcut
menu.
Step 2 In the dialog box that is displayed, set related parameters and click OK.
After logging in to a remote server or host remotely, you can perform operations on the NE
through command lines.
Step 4 Run the following command to enable the function of sending trap packets:
snmp-agent trap enable
Step 5 Run the following command to set the target host, that is, the NMS server:
NOTE
l v1 | v2c | v3 in the command must be the same as the SNMP version used by the NE. Otherwise, the
U2000 cannot receive trap packets sent by the NE.
l In an HA system, the IP address of the trap destination NE must be set to the IP addresses of the primary
and secondary sites.
l Using SNMPv3 is recommended because of its higher security than SNMPv1 and SNMPv2c.
Step 6 Run the following command to specify the source interface for sending trap packets:
snmp-agent trap source interface-type interface-number
----End
Context
Normally, the U2000 synchronizes the alarm data between the U2000 and NEs automatically.
Procedure
Step 1 Choose Browse Alarm > Synchronize NE Alarms (application style) or Fault > NE Alarm
Synchronize (traditional style) from the main menu.
Step 2 In the Synchronize NE Alarms dialog box, set the NEs whose alarms you want to synchronize.
Click OK.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l The security NE does not support the function of synchronizing the current alarms.
Procedure
Step 1 In the Workbench window, double-click the icon. The Main Topology is then displayed.
If you select a topology subnet from the Main Topology, all NEs in that topology subnet are selected.
Step 3 Right-click a selected NE and choose More Alarm Operations > Synchronize Current
Alarms from the shortcut menu.
A progress bar is displayed. After the operation is complete, a prompt message appears telling
you that the operation is successful.
----End
Procedure
Step 1 Choose Browse Alarm > Display Alarm Panel (application style) or Fault > Display Alarm
Panel (traditional style) from the main menu or click the icon on the toolbar to open the
alarm panel.
The U2000 displays the Alarm Panel window, as shown in Figure 7-20. You can add a current
alarm template to the alarm panel if you want to monitor the alarms of specified severities on
NEs. For details, see 7.6.2 Setting the Alarm Panel. The alarm panel then displays alarm
information according to the preset template.
NOTE
l The bar charts in the Query Alarm Bar Chart window correspond to the template displayed on the
alarm panel. When you add or delete an alarm bar chart (alarm template) in the Query Alarm Bar
Chart window, the corresponding alarm template is automatically added to or deleted from the alarm
panel. In the same way, when you perform the add or delete operation on the alarm panel, the bar chart
in the Query Alarm Bar Chart window is modified accordingly.
l If a user changes the name, status, or search criteria of a template in the alarm panel on client B, the
changes can be synchronized to client A only after the user restarts client A.
----End
Context
l In the topology view, the color of an NE icon depends on the alarm severity. If an NE
generates multiple alarms at the same time, its icon displays the color of the highest severity
among these generated alarms.
l By default, the U2000 provides four types of colors for alarms. critical: , major:
, minor: , and warning: .
l In the Main Topology, click on the toolbar. The current alarm is displayed in the lower
area of the topology view. Click again. The current alarm is hidden. Select a topology
object in the topology view, and then select the Display alarms of selected objects check
box. Only the alarms of the selected object are displayed.
Procedure
Step 1 Choose Topology > Main Topology (application style) or View > Main Topology (traditional
style) from the main menu.
Step 2 In the Main Topology, right-click the icon of an NE that generates alarms and choose menu
items such as Browse Current Alarm from the shortcut menu.
In the window such as Browse Current Alarm-Alarm Source, all alarms generated by the NE
are displayed.
----End
Context
l The U2000 provides the bar chart named All objects by default. The default bar chart is
used to monitor all the alarms in the current alarm and cannot be deleted.
l The bar charts in the Query Alarm Bar Chart window correspond to the template
displayed on the alarm panel. When you add or delete an alarm bar chart in the Query
Alarm Bar Chart window, the corresponding alarm template is automatically added or
deleted on the alarm panel. In the same way, when you perform the add or delete operation
on the alarm panel, the bar chart in the Query Alarm Bar Chart window is modified
accordingly.
Procedure
Step 1 Choose Browse Alarm > Query Alarm Bar Chart (application style) or Fault > Alarm Bar
Chart (traditional style) from the main menu.
The statistical results of the added current alarm templates are displayed in the Query Alarm
Bar Chart window.
NOTE
For NA NEs, alarms in the U2000 has the following four severities: Critical, Major, Minor, Not Alarmed.
Step 2 In the Query Alarm Bar Chart window, you can perform the following operations.
Delete a bar chart 1. Select one bar chart that does not belong to All objects,
and click Delete.
2. In the Confirm dialog box, click Yes.
Locate a bar chart to the Select one bar chart, and then click Locate to Current
current alarm Alarm to display the Browse Current Alarm window.
Set as the monitor template 1. Select one bar chart that does not belong to All objects and
click Show On Alarm Lamp.
2. In the Confirm dialog box, click Yes. Set the bar chart to
the monitor template.
NOTE
The alarm indicator on the right of the toolbar counts alarms of all
severities according to the filter criteria defined in the template.
----End
Context
The icon of the event indicator is located in the upper right corner of the U2000 UI.
Procedure
Step 1 Observe the event indicator.
NOTE
If no event occurs, the event indicator is displayed as ; if a new event occurs, the event indicator is
displayed as ; if the event reporting interval is shorter than the specified value, the event indicator
blinks.
Step 2 Click the event indicator to open the window for browsing event logs.
If new events occur according to the event indicator, these events are displayed directly in the
window for browsing events; if no event occurs according to the event indicator, the window
for browsing events or the Filter dialog box is displayed.
----End
Context
If the following alarms/events are reported to the U2000, the Emergency Maintenance
Notification dialog box will be displayed, prompting you to handle the alarms/events
immediately.
l Veritas High Availability System Waits for Restoration
l Veritas Resource Group is Frozen
l The Server Is Disconnected from the Database
l The Disk Usage Is Too High
l The Database Usage Is Too High
l GNE_NUM_LIMIT_OVER
l The size of Sybase logs exceeds the threshold
l The usage of the paged kernel memory on Windows exceeds the alarm threshold
l The usage of the non-paged kernel memory on Windows exceeds the alarm threshold
l The virtual memory of Windows is insufficient
l The swap space is insufficient
Procedure
Step 1 If an alarm/event is generated on the U2000, the Emergency Maintenance Notification dialog
box will be displayed on the client, prompting you to perform system maintenance immediately.
NOTE
l The name, generation time and location about the alarm/event are displayed in the Emergency
Maintenance Notification dialog box.
l Move your curse to the alarm/event identification area and click the identification information. The
Browse Alarms/Events window is then displayed, displaying maintenance advice on alarms/events.
l The Emergency Maintenance Notification dialog box is displayed on all clients that connected to the
U2000 server. It covers part of the operation area on clients, but does not affect your operations.
l You can click Minimize to suspend the Emergency Maintenance Notification dialog box on the
upper pane of the U2000 toolbar. This does not affect your operations.
l You may also click Close to close the Emergency Maintenance Notification dialog box. If the alarm/
event is not maintained, the dialog box will be displayed one hour later by default, prompting you to
handle the alarm/event in a timely manner.
Step 2 You can handle the alarm/event in a timely manner by following the maintenance suggestions
in the Alarm and Event Reference.
NOTE
After the alarm/event is cleared, a dialog box or window is displayed, indicating that the alarm/event is
cleared. The dialog box or window will be closed in 5 seconds.
----End
Context
l Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style), Browse Alarm > Browse Alarm Logs (application
style) or Fault > Browse Alarm Logs (traditional style), Browse Alarm > Query Event
Logs (application style) or Fault > Browse Event Logs (traditional style), Browse
Alarm > Browse Current Alarm by Severity (application style) or Fault > Browse
Current Alarm by Severity (traditional style), Browse Alarm > Browse Current Alarm
by Status (application style) or Fault > Browse Current Alarm by Status (traditional
style) or Browse Alarm > Query Historical Alarm (application style) or Fault > Browse
Historical Alarm (traditional style) from the main menu. In the Filter dialog box, set search
criteria, and click OK. In the window, right-click the table header or the blank area at the
bottom of the table, and choose Configure Columns from the shortcut menu.
l In the Browse Current Alarm, Browse Historical Alarms, Browse Alarm Logs, Browse
Current Alarm by Status, or Browse Current Alarm by Severity window, right-click
a correlative alarm and choose Query Root Alarms from the shortcut menu. Alternatively,
click the Root Alarms tab in the lower part of the window. In the Root Alarms dialog box
or on the Root Alarms tab, right-click the table header or the blank area at the bottom of
the table, and choose Configure Columns from the shortcut menu.
l In the Browse Current Alarm, Browse Historical Alarms, Browse Alarm Logs, Browse
Current Alarm by Status, or Browse Current Alarm by Severity window, right-click
a root alarm or select multiple alarms and right-click, and choose Query Correlative
Alarms from the shortcut menu. Alternatively, click the Correlative Alarms tab in the
lower part of the window. In the Correlative Alarms dialog box or on the Correlative
Alarms tab, right-click the table header or the blank area at the bottom of the table, and
choose Configure Columns from the shortcut menu.
l In the Browse Current Alarm, Browse Current Alarm by Status, or Browse Current
Alarm by Severity window, right-click an alarm and choose Query Associated Alarms
from the shortcut menu. Alternatively, click the Associated Alarms tab in the lower part
of the window. In the Associated Alarms dialog box or on the Associated Alarms tab,
right-click the table header or the blank area at the bottom of the table, and choose
Configure Columns from the shortcut menu.
l In the Browse Current Alarm, Browse Current Alarm by Status, or Browse Current
Alarm by Severity window, right-click an alarm and choose Query Alarm Logs from the
shortcut menu. Alternatively, click the Alarm Logs tab in the lower part of the window.
In the Alarm Logs dialog box or on the Alarm Logs tab, right-click the table header or
the blank area at the bottom of the table, and choose Configure Columns from the shortcut
menu.
l Setting columns to be displayed applies only to the current user. If the current user saves
a template after setting the columns, the column settings are saved to the template.
l The methods of setting columns to be displayed in different windows are the same. The
following describes how to set columns to be displayed in the Browse Current Alarm
window.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style) from the main menu, or click the on the toolbar. In the
Filter dialog box, set search criteria, and click OK.
Step 2 In the Browse Current Alarm window, right-click the table header or the blank space at the
bottom of the table, and choose Configure Columns from the shortcut menu.
Step 3 In the Configure Columns dialog box, set the fields to be displayed and select Take effect for
the current window and the current alarm windows to be opened or Take effect for the
current pane only as required.
NOTE
l Specify a field name on the right of the dialog box and click or to
change the order for displaying fields in the alarm list.
l You can click Default to restore the default display sequence of fields.
----End
Prerequisites
Before you browse alarms reported by NEs to the U2000, the U2000 fault process ifms_agent
is enabled. You can log in to the System Monitor client to check the running status of this process.
Context
l Current alarm displays the merged alarms. The rules for merging alarms are as follows:
– The alarms whose alarm group IDs, alarm IDs, alarm location information, and alarm
sources are the same, and whose maintenance status is Normal are merged into another
current alarm record.
– The alarms whose alarm group IDs, alarm IDs, alarm location information, and alarm
sources are the same, and whose maintenance status is not Normal are merged into a
current alarm record.
l For a newly reported alarm, if the current alarm contains the record that meets the alarm
merging rule, the alarm is merged into the previous record in the current alarm regardless
of the acknowledgment and clearance status of the record. After merging, the frequency of
the record is added by 1. The displayed acknowledgment and clearance status of the record
is subject to that of the latest alarm. After the current alarm is changed to historical alarms,
the frequency recorded for the current alarm is reduced by 1.
l Be default, a maximum of 100,000 alarms can be reported. If the number of reported alarms
exceeds the maximum number, the U2000 automatically transfers the earlier reported
5,000 alarms to historical alarms. Therefore, you are advised to handle alarms in time
because excessive alarms will affect the real-time monitoring of alarms.
l By performing operations in 7.8.11 Querying Alarm Logs, you can query logs of all
alarms, which include alarms in the current and historical alarm lists. Alarms that have been
acknowledged and cleared and whose life cycles have ended are saved to the historical
alarm list and are not displayed in the current alarm list. However, you can query alarm
logs for these alarms. For details about how to specify the life cycle for an alarm and set
an automatic acknowledgment rule, see 7.5.11 Setting the Lifecycle of the Current
Alarm and 7.5.4 Setting an Automatic Alarm Acknowledgment Rule.
l When you filter current alarm based on the template, if a user has modified the parameters
in the template, you can click No in the Confirm window that is displayed after you close
the Browse Current Alarm window to cancel the template modification.
l By default, alarms in the alarm list are sorted by Log Serial Number, and new alarms or
events are displayed on the top or at the bottom of the alarm list depending on the setting
in New Alarm/Event.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style) from the main menu, or click on the toolbar.
If you set the default template, you need to click Filter to open the Filter dialog box.
The query result may contain the current alarm, and acknowledged and cleared alarms in the life cycle (see
7.5.11 Setting the Lifecycle of the Current Alarm).
The first column in the alarm list is the identity column. Table 7-14 describes the icons in this
column.
Icon Description
Intermittent alarm.
Correlative alarm.
Root alarm.
Toggling alarm.
Indicates that the U2000 has sent the remote alarm notification
by email or short message.
NOTE
l The operation for sorting table headers of an alarm list by dragging them takes effect for the current
window and the newly-opened Browse Current Alarm window.
l If you sort alarms by Alarm Source, alarms are sorted by the NE FDN (an NE identity) of alarm source,
rather than the alarm source name.
l Select Show latest alarms to refresh alarms displayed in the window in real time.
l Select Scroll lock to keep the alarms displayed in the window unchanged.
l Click Template and choose Open. In the Choose window, you can reselect a template for filtering.
l Click Filter to reset the criteria for filtering alarms.
l Click Refresh to read the latest alarm data from the database and display the data in the active window.
However, the alarm data is not synchronized from NEs to the U2000. For details about how to
synchronize alarms, see Synchronizing NE Alarms Manually.
l After you click in the browse window. The Expanded alarm area is hidden. After you click
in the browse window, the Expanded alarm area is shown.
l Select one or more alarms in the window, and press Ctrl+C to copy the contents to the clipboard.
----End
Context
l Alarm logs record all the alarms received by the U2000. In alarm logs, each alarm is
displayed as a record.
l Current alarm displays the merged alarms. The rules for merging alarms are as follows:
– The alarms whose alarm group IDs, alarm IDs, alarm location information, and alarm
sources are the same, and whose maintenance status is Normal are merged into another
current alarm record.
– The alarms whose alarm group IDs, alarm IDs, alarm location information, and alarm
sources are the same, and whose maintenance status is not Normal are merged into a
current alarm record.
l In the Browse Alarm Logs window, you can query logs of all alarms, which include alarms
in the current and historical alarm lists. Alarms that have been acknowledged and cleared
and whose life cycles have ended are saved to the historical alarm list and are not displayed
in the current alarm list. However, you can query alarm logs for these alarms. For details
about how to specify the life cycle for an alarm and set an automatic acknowledgment rule,
see 7.5.11 Setting the Lifecycle of the Current Alarm and 7.5.4 Setting an Automatic
Alarm Acknowledgment Rule.
l By default, a maximum of 300,000 alarm logs are displayed. When the number of alarm
logs exceeds this maximum number, only the latest alarm logs are displayed. You can set
filter criteria to query earlier alarm logs.
l When you filter alarm logs based on the template, if a user has modified the parameters in
the template, you can click No in the Confirm window that is displayed after you close the
Browse Alarm Logs window to cancel the template modification.
l In the Browse Current Alarm window, you can right-click an alarm and choose Query
Alarm Logs from the shortcut menu to query the log of the alarm in the Alarm Logs dialog
box.
Procedure
Step 1 Choose Browse Alarm > Browse Alarm Logs (application style) or Fault > Browse Alarm
Logs (traditional style) from the main menu, or click on the toolbar.
Step 2 In the Filter dialog box, set the alarm query conditions.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
Icon Description
Intermittent alarm.
Icon Description
Correlative alarm.
Root alarm.
Toggling alarm.
Indicates that the U2000 has sent the remote alarm notification
by email or short message.
NOTE
l The operation for sorting table headers of an alarm list by dragging them takes effect for the current
window and the newly-opened Browse Alarm Logs window.
l If you sort alarms by Alarm Source, alarms are sorted by the NE FDN (an NE identity) of alarm source,
rather than the alarm source name.
l Click Template and choose Open. In the Choose window, you can reselect a template for filtering.
l Click Filter to reset the criteria for filtering alarms.
l Click Refresh to read the latest alarm data from the database and display the data in the active window.
However, the alarm data is not synchronized from NEs to the U2000. For details about how to
synchronize alarms, see Synchronizing NE Alarms Manually.
l After you click in the browse window. The Expanded alarm area is hidden. After you click
in the browse window, the Expanded alarm area is shown.
l Select one or more alarms in the window, and press Ctrl+C to copy the contents to the clipboard.
----End
Context
l Alarms that have been acknowledged and cleared are historical alarms. All the other alarms
are current alarms.
l By default, a maximum of 300,000 historical alarms are displayed. When the number of
historical alarms exceeds this maximum number, only the latest historical alarms are
displayed. You can set filter criteria to query earlier historical alarms.
Procedure
Step 1 Choose Browse Alarm > Query Historical Alarm (application style) or Fault > Browse
Historical Alarm (traditional style) from the main menu.
Step 2 In the Filter dialog box, set search criteria, and click OK.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
The result is displayed in the Browse Historical Alarms window.
The first column in the alarm list is the identity column. Table 7-16 describes the icons in this
column.
Icon Description
Intermittent alarm.
Correlative alarm.
Root alarm.
Toggling alarm.
Indicates that the U2000 has sent the remote alarm notification
by email or short message.
NOTE
l The operation for sorting table headers of an alarm list by dragging them takes effect for the current
window and the newly-opened Browse Historical Alarms window.
l Click Template and choose Open. In the Choose window, you can reselect a template for filtering.
l Click Filter to reset the criteria for filtering alarms.
l Click Refresh to read the latest alarm data from the database and display the data in the active window.
However, the alarm data is not synchronized from NEs to the U2000. For details about how to
synchronize alarms, see Synchronizing NE Alarms Manually.
l After you click in the browse window. The Expanded alarm area is hidden. After you click
in the browse window, the Expanded alarm area is shown.
l Select one or more alarms in the window, and press Ctrl+C to copy the contents to the clipboard.
----End
Context
l By default, a maximum of 100,000 event logs are displayed. When the number of event
logs exceeds this maximum number, only the latest event logs are displayed. You can set
filter criteria to query earlier event logs.
l When you filter event logs based on the template, if a user has modified the parameters in
the template, you can click No in the Confirm window that is displayed after you close the
Query Event Logs window to cancel the template modification.
Procedure
Step 1 Choose Browse Alarm > Query Event Logs (application style) or Fault > Browse Event
Logs (traditional style) from the main menu.
If you set the default template, you need to click Filter to open the Filter dialog box.
Icon Description
Repeat event.
NOTE
l The operation for sorting table headings of an event list by dragging them takes effect for the current
window and the newly-opened Browse Event Logs window.
l Select Show latest events to refresh events displayed in the window in real time.
l Select Scroll lock to keep the events displayed in the window unchanged.
l If you sort events by Event Source, events are sorted by the NE FDN (an NE identity) of event source,
rather than the event source name.
l Click Template and choose Open. In the Choose window, you can reselect a template for filtering.
l Click Filter to reset the conditions for filtering events.
l After you click Refresh to read the latest event data from the database and display the data in the active
window.
l Click in the browse window, the Details panel is hidden. After you click in the
browse window, the Details panel is shown.
l Select one or more events in the window, and press Ctrl+C to copy the contents to the clipboard.
----End
Context
By default, alarms in the alarm list are sorted by Log Serial Number, and new alarms or events
are displayed on the top or at the bottom of the alarm list depending on the setting in New Alarm/
Event.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm by Severity (application style) or Fault >
Browse Current Alarm by Severity (traditional style) from the main menu.
If you set the default template, you need to click Filter to open the Filter dialog box.
NOTE
l The operation for sorting table headers of an alarm list by dragging them takes effect for the current
window and the newly-opened Browse Current Alarm by Severity window.
l If you sort alarms by Alarm Source, alarms are sorted by the NE FDN (an NE identity) of alarm source,
rather than the alarm source name.
l Select Show latest alarms to refresh alarms displayed in the window in real time.
l Select Scroll lock to keep the alarms displayed in the window unchanged.
l Click Template and choose Open. In the Choose window, you can reselect a template for filtering.
l Click Filter. In the Filter dialog box, reset filter criteria to filter current alarms.
If you have already set filtering by template, resetting the filter criteria will modify the template
parameters. In this case, you can click No in the Confirm window that is displayed after you close the
Browse Current Alarm by Severity window to cancel the template modification.
l Click the buttons 1, 2, 3, and 4 to open or close the panes corresponding to the numbers.
l Click Refresh to read the latest alarm data from the database and display the data in the active window.
However, the alarm data is not synchronized from NEs to the U2000. For details about how to
synchronize alarms, see Synchronizing NE Alarms Manually.
l After you click in the browse window. The Expanded alarm area is hidden. After you click
in the browse window, the Expanded alarm area is shown.
l Select one or more alarms in the window, and press Ctrl+C to copy the contents to the clipboard.
----End
Context
l By default, alarms in the alarm list are sorted by Log Serial Number, and new alarms or
events are displayed on the top or at the bottom of the alarm list depending on the setting
in New Alarm/Event.
l For details about the alarm status classification and transition relationships between alarm
states, see 7.1.3 Alarm Status.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm by Status (application style) or Fault >
Browse Current Alarm by Status (traditional style) from the main menu.
If you set the default template, you need to click Filter to open the Filter dialog box.
NOTE
l The operation for sorting table headers of an alarm list by dragging them takes effect for the current
window and the newly-opened Browse Current Alarm by Status window.
l In the Acknowledged and cleared alarm window, the acknowledged and cleared alarms in the life
cycle are displayed. (See 7.5.11 Setting the Lifecycle of the Current Alarm)
l If you sort alarms by Alarm Source, alarms are sorted by the NE FDN (an NE identity) of alarm source,
rather than the alarm source name.
l Select Show latest alarms to refresh alarms displayed in the window in real time.
l Select Scroll lock to keep the alarms displayed in the window unchanged.
l Click Template and choose Open. In the Choose window, you can reselect a template for filtering.
l Click Filter. In the Filter dialog box, reset filter criteria to filter current alarms.
If you have already set filtering by template, resetting the filter criteria will modify the template
parameters. In this case, you can click No in the Confirm window that is displayed after you close the
Browse Current Alarm by Status window to cancel the template modification.
l Click the buttons 1, 2, 3, and 4 to open or close the panes corresponding to the numbers.
l Click Refresh to read the latest alarm data from the database and display the data in the active window.
However, the alarm data is not synchronized from NEs to the U2000. For details about how to
synchronize alarms, see Synchronizing NE Alarms Manually.
l After you click in the browse window. The Expanded alarm area is hidden. After you click
in the browse window, the Expanded alarm area is shown.
l Select one or more alarms in the window, and press Ctrl+C to copy the contents to the clipboard.
----End
Prerequisites
To query the alarms of the opposite port, ensure that the NEs are connected by optical fibers.
Context
The following are entries to the Query Opposite Port Alarms function: Choose Browse
Alarm > Browse Current Alarm (application style) or Fault > Browse Current Alarm
(traditional style), Browse Alarm > Browse Current Alarm by Severity (application style) or
Fault > Browse Current Alarm by Severity (traditional style) or Browse Alarm > Browse
Current Alarm by Status (application style) or Fault > Browse Current Alarm by Status
(traditional style) from the main menu. In the Filter dialog box, set search criteria, and click
OK. Right-click an alarm and choose Query Opposite Port Alarms from the shortcut menu.
The methods for querying opposite port alarms in different windows are similar. The following
describes how to query opposite port alarms in the Browse Current Alarm window.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style) from the main menu.
Step 2 In the Filter dialog box, set the alarm query conditions. Click OK.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
Step 3 In the alarm browsing window, select an alarm, right-click, and then choose Query Opposite
Port Alarms.
Step 4 On the Browse Alarms Related to Opposite Port tab, view the alarms of the opposite port
associated to this port.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l This operation is not applicable to the subrack NEs affiliated to an Optical NE.
Context
l Each NE belongs to only one maintenance region.
l Maintenance regions cannot be nested.
l The user can add only visible NEs to maintenance regions.
Procedure
Step 1 Choose File > Maintenance Region Management (application style) or Administration >
Settings > Maintenance Region Management (traditional style) from the main menu.
Step 2 In the Maintenance Region Management window, you can perform the following operations
to set maintenance regions.
----End
7.8.18 Setting the Time Display Mode for Queried Alarms or Events
You can set the time display mode for queried alarms or events to ensure that the time of the
queried alarms or events displayed in the window for querying alarms or events is the same as
the NE time, server time, or client time.
Context
l The time displayed modes are NE Time, Server Time, and Client Time.
NOTE
The setting methods are similar. The following describes how to set the time display mode
in the Browse Current Alarm window.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style) from the main menu. In the Filter dialog box, set the alarm
query conditions, click OK.
Step 2 In the window, right-click the table header or the blank area below the table, and choose
Displayed Time Mode from the shortcut menu.
NOTE
Reopen the alarms or events window. The default value of Display Time Mode is consistent with that in
File > Preferences > Time Mode.
l The NE Time mode affects only the values of the following parameters: First Occurred, Last
Occurred, and Cleared On.
l The Server Time mode affects only the values of the following parameters: First Occurred, Last
Occurred, Cleared On and Acknowledged On.
l The Client Time mode affects only the values of the following parameters: First Occurred, Last
Occurred, Cleared On and Acknowledged On.
----End
Context
The locating function of topology is applicable for one alarm/event at a time.
Procedure
l Navigation Path:
– Method 1:
If you set the default template, you need to click Filter to open the Filter dialog box.
3. Select a concerned alarm, right-click, and then choose Locate in Topology or
Locating to NE Panel\Locate To NE Panel.
NOTE
Only the alarms that are related to the hardware can be located on the NE panel.
l Locating objects:
– Choose Locate in Topology, the NE that raises the alarm is identified on the client.
– Choose Locating to NE Panel\Locate To NE Panel, the faulty port is displayed in
the NE panel.
NOTE
----End
Context
l In the statistical results, the records whose values are 0 are not displayed.
l The statistical results can be displayed in a table or pie chart. By default, they are displayed
in a table.
l When you filter alarm logs based on the template, if a user has modified the parameters in
the template, you can click No in the Confirm window that is displayed after you close the
Alarm Log Statistics window to cancel the template modification.
Procedure
Step 1 Choose Browse Alarm > Alarm Log Statistics (application style) or Fault > Query Alarm
Log Statistics (traditional style) from the main menu.
Step 2 In the Filter dialog box, set the statistical criteria of alarm logs, and click OK.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
Step 3 In the Alarm Log Statistics window, you can perform the following operations.
Task Operations
Display statistical results in Click the Table tab in the lower left corner, and then expand
a table the collapsed items in the statistical result table to view all
statistics.
Display statistical results in Click the Pie tab in the lower left corner, and then click a tab
a pie chart named a statistical item in the upper left corner to view the
statistics based on the statistical settings.
NOTE
Multiple pie charts are generated only after you set multiple statistical
items in the Filter dialog box, and the tab is displayed in the upper left
corner of statistical results.
Task Operations
Print statistical results 1. Click the Table tab in the lower left corner, and then click
Print.
NOTE
The U2000 does not support the ability of printing pie charts. When
you click the Pie tab, the Print button is unavailable.
2. In the Print dialog box, set the print parameters, and then
click Print.
----End
Context
l In the statistical results, the records whose values are 0 are not displayed.
l The statistical results can be displayed in a table or pie chart. By default, they are displayed
in a table.
l When you filter event logs based on the template, if a user has modified the parameters in
the template, you can click No in the Confirm window that is displayed after you close the
Event Log Statistics window to cancel the template modification.
Procedure
Step 1 Choose Browse Alarm > Event Log Statistics (application style) or Fault > Query Event Log
Statistics (traditional style) from the main menu.
Step 2 In the Filter dialog box, set the statistical criteria of event logs, and click OK.
Step 3 In the Event Log Statistics window, you can perform the following operations.
Task Operations
Display statistical results in Click the Table tab in the lower left corner, and then expand
a table the collapsed items in the statistical result table to view all
statistics.
Display statistical results in Click the Pie tab in the lower left corner, and then click a tab
a pie chart named a statistical item in the upper left corner to view the
statistics based on the statistical settings.
NOTE
Multiple pie charts are generated only after you set multiple statistical
items in the Filter dialog box, and the tab is displayed in the upper left
corner of statistical results.
Task Operations
Open a statistical template 1. Click Template, and then click Open.
2. Select one template in the Choose Template window, and
click OK.
Reset the statistical criteria 1. Click Statistics Filter.
2. In the Filter dialog box, set the statistical criteria of alarm
logs, and click OK.
Refresh statistical results Click Refresh to read the latest alarm data from the database
and collect statistics. However, the alarm data is not
synchronized from NEs to the U2000. For details about how to
synchronize the alarms of the NE, see 7.8.3.1 Synchronizing
NE Alarms Manually.
Save statistical results 1. Click Save As.
2. In the Save dialog box, select the path for saving records.
3. In the Save dialog box, set File Name, File Type or
Encoding, and then click Save.
NOTE
l The statistical results in a table can be saved as
a .txt, .html, .csv, .pdf, .xlsx or .xls file.
l For .txt files, code formats ISO-8859-1 and UTF-8 are supported.
The default encoding format is ISO-8859-1. You are advised to
use the default encoding format if the saved file does not need to
support multiple languages; otherwise, UTF-8 is recommended.
l The statistical results in a pie chart can be saved as a .jpg file.
l The Encoding parameter is not provided if you save the statistical
results in a pie chart to a .jpg file.
Print statistical results 1. Click the Table tab in the lower left corner, and then click
Print.
NOTE
The U2000 does not support the ability of printing pie charts. When
you click the Pie tab, the Print button is unavailable.
2. In the Print dialog box, set the print parameters, and then
click Print.
----End
Context
l An NE object group is a collection of NEs.
l When you set the alarm or event query and statistical criteria, the NE object group can be
considered as a type of user-defined alarm or event source. If you select an object group,
you select multiple NEs.
l Only users of the administrator group or the creator of an object group are allowed to modify
the object group.
l You can add only NEs to an object group.
Procedure
Step 1 Choose Alarm Settings > Object Group Management (application style) or Fault >
Settings > Object Group Management (traditional style) from the main menu.
Step 2 In the Object Group Management dialog box, set the object group.
----End
Context
l An alarm name group is a collection of alarm names. An event name group is a collection
of event names.
l If you select an alarm or event name group, you select multiple alarms or events at a time.
l Only users in the administrator group or the creator of a name group are allowed to modify
a name group.
Procedure
Step 1 Choose Alarm Settings > Alarm/Event Name Group Management (application style) or
Fault > Settings > Alarm/Event Name Group Management (traditional style) from the main
menu.
Step 2 In the Alarm/Event Name Group Management dialog box, set the name group.
----End
Procedure Chart
Figure 7-21 shows the alarm handling procedure.
Procedure Description
Figure 7-21 lists the procedure for handling an alarm.
1 Receive an alarm Follow the alarm handling procedure after you receive an
alarm. To ensure that you are notified in a timely manner
after an alarm occurs, you need to set alarm notification
methods on the U2000.
2 View the alarm View the alarm details, including the alarm location, alarm
details help, and alarm maintenance experience after an alarm
occurs.
3 Acknowledge the Acknowledge the alarm to show that the alarm is being
alarm tracked in case that others may process an alarm at the same
time.
4 Collect the fault Identify the alarm and query the alarm information to collect
information the fault information of the alarm.
5 Analyze the causes of Analyze the causes for the alarm based on the alarm
the alarm symptom.
6 Work out the fault Work out the fault handling scheme based on the alarm
handling scheme details, device manuals, network status, and maintenance
experience.
7 Carry out the fault Carry out the fault handling scheme to rectify the fault that
handling scheme leads to the alarm.
8 Clear the alarm Clear the conditions that cause the alarm. After the alarm is
cleared, the U2000 receives a clear alarm. You can also
clear the alarm manually. For details, see Clear alarms
manually.
9 Check whether the Check the handling results after you rectify the fault.
fault is rectified
Context
The method of viewing alarm details is as follows: Double-click a record or right-click a record
Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style), Browse Alarm > Browse Alarm Logs (application style)
or Fault > Browse Alarm Logs (traditional style), Browse Alarm > Query Event Logs
(application style) or Fault > Browse Event Logs (traditional style), Browse Alarm > Browse
Current Alarm by Severity (application style) or Fault > Browse Current Alarm by
Severity (traditional style), Browse Alarm > Browse Current Alarm by Status (application
style) or Fault > Browse Current Alarm by Status (traditional style) or Browse Alarm >
Query Historical Alarm (application style) or Fault > Browse Historical Alarm (traditional
style) from the main menu. In the Filter dialog box, set search criteria, and click OK. Then,
choose Details from the shortcut menu.
The methods of viewing alarm details in different windows are similar. The following describes
how to view alarm details in the Browse Current Alarm window.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style) from the main menu. In the Filter dialog box, set search
criteria, and click OK.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
Step 2 After you select a record, the alarm details and handling suggestions are displayed at the bottom
of the window. Right-click a record and choose Details from the shortcut menu, the Details
dialog box is displayed.
View the details about how to clear Click Click here for details.
the current alarm
Step 3 Optional: In the Details dialog box, click on the left of Experience, and then click Modify.
In the Experience dialog box, enter the alarm maintenance experience. Then click OK.
----End
Prerequisites
To perform the following operations, you must have relevant operation rights:
l To acknowledge alarms, you must have the operation rights of the Operator Group or
higher-level user groups.
l To unacknowledge alarms, you must have the operation rights of the Operator Group or
higher-level user groups.
For details about how to check whether you have corresponding rights, see 3.2.8.2 Viewing
Operation Rights of a User or User Group. If you do not have corresponding rights, contact
SMManagers for user authorization.
Context
l To request other users to pay attention to an alarm, you can right-click the alarm and choose
Unacknowledge to restore the alarm state to unacknowledged.
l The following are entries to the Acknowledge function: Choose Browse Alarm > Browse
Current Alarm (application style) or Fault > Browse Current Alarm (traditional
style),Browse Alarm > Browse Current Alarm by Severity (application style) or
Fault > Browse Current Alarm by Severity (traditional style) or Browse Alarm >
Browse Current Alarm by Status (application style) or Fault > Browse Current Alarm
by Status (traditional style) from the main menu. In the Filter dialog box, set search criteria,
and click OK. Select one or more alarms and click Acknowledge.
The methods for acknowledging alarms in different windows are similar. The following
describes how to acknowledge alarms in the Browse Current Alarm window.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style) from the main menu. In the Filter dialog box, set search
criteria, and click OK. Select one or more alarms and click Acknowledge.
Step 2 In the Confirm dialog box, click Yes.
----End
Context
The locating function of topology is applicable for one alarm/event at a time.
Procedure
l Navigation Path:
– Method 1:
Logs (application style) or Fault > Browse Alarm Logs (traditional style),
Browse Alarm > Browse Current Alarm by Severity (application style) or
Fault > Browse Current Alarm by Severity (traditional style) or Browse
Alarm > Browse Current Alarm by Status (application style) or Fault >
Browse Current Alarm by Status (traditional style) from the main menu.
2. In the dialog box that is displayed, set the alarm filter criteria, and click OK, as
shown in the following figure.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
3. Select a concerned alarm, right-click, and then choose Locate in Topology or
Locating to NE Panel\Locate To NE Panel.
NOTE
Only the alarms that are related to the hardware can be located on the NE panel.
l Locating objects:
– Choose Locate in Topology, the NE that raises the alarm is identified on the client.
– Choose Locating to NE Panel\Locate To NE Panel, the faulty port is displayed in
the NE panel.
NOTE
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
l The reasons that the alarms on the U2000 are different from the alarms on the NE:
– The U2000 fails to receive alarms from the NE due to network interruption.
– The U2000 discards the NE alarms that comply with the alarm mask rules.
l Check the navigation path to the alarm: Choose Browse Alarm > Browse Current
Alarm (application style) or Fault > Browse Current Alarm (traditional style), Browse
Alarm > Browse Current Alarm (application style) or Fault > Browse Current
Alarm (traditional style), Browse Alarm > Browse Current Alarm by Severity
(application style) or Fault > Browse Current Alarm by Severity (traditional style) or
Browse Alarm > Browse Current Alarm by Status (application style) or Fault > Browse
Current Alarm by Status (traditional style) from the main menu, or click or on the
toolbar. In the Filter dialog box, set the alarm query conditions, chick OK. Select one or
more alarms and click Check.
The methods for checking alarms are similar. The following describes how to check alarms
in the Browse Current Alarm window.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style) from the main menu.
Step 2 In the Filter dialog box, set the alarm query conditions. Click OK.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
Step 3 Right-click one or more uncleared alarms and choose Check from the shortcut menu.
NOTE
If the selected alarms include cleared alarms, the U2000 ignores the cleared alarms and processes only
uncleared alarms.
----End
Result
l If the alarm exists in the NE alarm list, it remains unchanged on the U2000.
l If the alarm does not exist in the NE alarm list, it is automatically acknowledged and cleared
on the U2000 and becomes a historical alarm after its lifecycle.
You can take proper measures to rectify a fault and recover the system.
1. Rectify the fault based on the handling suggestion contained in alarm details, maintenance
experience, or solutions in related fault cases.
2. If you need assistance from field engineers, notify them of the fault and guide them to
rectify the fault.
3. Check whether the fault is rectified. If not, submit it to senior engineers.
Before contacting technical support engineers of Huawei Technologies Co., Ltd., prepare the
following to help to rectify the fault quickly and reduce loss:
l Collect necessary information about the fault, such as the version, fault condition, and
location.
l Prepare for debugging.
During fault rectification, technical support engineers of Huawei Technologies Co., Ltd. may
guide you to perform operations. This helps to collect the fault information and rectify the fault.
Therefore, you need to make preparations before seeking technical support from engineers.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l The function of masking alarms or events does not take effect for the alarms or events that
are already reported. That is, after you set a masking policy, only the newly reported alarms
that meet the masking conditions are masked.
l During the device maintenance, test, or deployment, the device may report numerous
alarms. In this case, you can set the alarm masking rules to mask the alarms or events that
do not require attention. The masked alarms are not displayed or saved. For detail see 7.5.3
Setting an Alarm or Event Mask Rule.
l You can mask alarms by navigating to either of the following paths: Choose Browse
Alarm > Browse Current Alarm (application style) or Fault > Browse Current
Alarm (traditional style), Browse Alarm > Browse Alarm Logs (application style) or
Fault > Browse Alarm Logs (traditional style), Browse Alarm > Query Event Logs
(application style) or Fault > Browse Event Logs (traditional style), Browse Alarm >
Browse Current Alarm by Severity (application style) or Fault > Browse Current
Alarm by Severity (traditional style) or Browse Alarm > Browse Current Alarm by
Status (application style) or Fault > Browse Current Alarm by Status (traditional
style) from the main menu.
Browse Current Alarm is used as an example because the alarm masking operations are
similar.
Procedure
Step 1 Choose Fault > Browse Current Alarm (traditional style) from the main menu or select Fault
Management in Application Center and choose Browse Alarm > Browse Current Alarm
(application style) from the main menu.
Step 2 In the Filter dialog box, set the alarm query conditions.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
Step 3 Select an alarm or event from the alarm or event browse window, right-click, and then choose
Mask.
Step 4 In the Mask dialog box that is displayed, you can set the Mask Scope and Validity Period
according to the requirements.
----End
Result
A new masking policy is displayed in the Mask Rules dialog box. The same alarms that are
reported later continue to be masked.
Follow-up Procedure
l If you want to see the mask rules set on the U2000, choose Alarm Settings > Mask
Rules (application style) or Fault > Settings > Mask Rules (traditional style) from the
main menu. All of the masking policy will be displayed in the Mask Rules.
l If you need to receive the masked alarms again, choose Alarm Settings > Mask Rules
(application style) or Fault > Settings > Mask Rules (traditional style) from the main
menu. In the Mask Rules dialog box, select the required masking policy, and clear the
Enable check box or delete the policy.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
The method of viewing suppress alarm details is as follows: Choose Fault > Browse Current
Alarm (traditional style) from the main menu or select Fault Management in Application
Center and choose Browse Alarm > Browse Current Alarm (application style) from the main
menu. Choose Fault > Browse Current Alarm by Status (traditional style) from the main menu
or select Fault Management in Application Center and choose Browse Alarm > Browse
Current Alarm by Status (application style) from the main menu. Choose Fault > Browse
Current Alarm by Severity (traditional style) from the main menu or select Fault
Management in Application Center and choose Browse Alarm > Browse Current Alarm
by Severity (application style) from the main menu.
The methods of viewing other suppress alarm details are similar. The following describes how
to view suppress alarm details in the Browse Current Alarm window.
Procedure
Step 1 Choose Fault > Browse Current Alarm (traditional style) from the main menu or select Fault
Management in Application Center and choose Browse Alarm > Browse Current Alarm
(application style) from the main menu.
Step 2 In the Filter dialog box, set filter criteria and click OK.
NOTE
If you set the default template, you need to click Filter to open the Filter dialog box.
Step 3 Select an alarm from the current alarms window, right-click, and then choose Suppress NE
Alarm.
----End
Result
l After the alarm suppression is set successfully for an alarm, NEs do not report this alarm
any more.
l After the alarm suppression is set successfully for an alarm, the alarm that has been reported
is cleared.
Follow-up Procedure
If you need to receive the suppressed alarms again from an NE, select the NE on the Main
Topology, right-click, and then choose NE Explorer from the shortcut menu. On the left-hand
Function Tree, expand Alarm > NE Alarm Suppression branches, select the required alarm
event, and then set Status to Not Suppressed.
Prerequisites
To manually clear alarms, you must have the operation rights of the Operator Group or higher-
level user groups.
Context
l When you manually clear an alarm, the OSS sends the alarm clearance command to the
NE or the OSS, and the NE or the OSS clears the alarm.
l The clear alarm corresponds to the alarm. When a fault occurs, an alarm is generated. When
the fault is rectified, a clear alarm is generated and the alarm is cleared. If the U2000 fails
to receive the clear alarm due to a network fault, you need to manually clear the alarm.
l The method of manually clearing alarms is as follows: Choose Browse Alarm > Browse
Current Alarm (application style) or Fault > Browse Current Alarm (traditional
style), Browse Alarm > Browse Current Alarm by Severity (application style) or
Fault > Browse Current Alarm by Severity (traditional style) or Browse Alarm >
Browse Current Alarm by Status (application style) or Fault > Browse Current Alarm
by Status (traditional style) from the main menu. In the Filter dialog box, set search criteria,
and click OK. Select one or more uncleared alarms, and click Clear.
The methods of manually clearing alarms in different windows are similar. The following
describes how to manually clear alarms in the Browse Current Alarm window.
Procedure
Step 1 Choose Browse Alarm > Browse Current Alarm (application style) or Fault > Browse
Current Alarm (traditional style) from the main menu. In the Filter dialog box, set search
criteria, and click OK.
Step 2 Select one or more uncleared alarms, and then click Clear.
----End
Result
l If the fault related to the alarm has been rectified, the alarm will not be reported again. If
the fault related to the alarm persists, the alarm may be reported again.
l After the alarm is cleared manually, the board indicator on the U2000 turns green. If the
fault that causing this alarm still exists, the alarm may be reported again, and the board
indicator will change to a color corresponding to the alarm severity.
Context
The initial experience library is empty.
Procedure
Step 1 Choose Alarm Settings > Experience (application style) or Fault > Settings > Experience
(traditional style) from the main menu.
Step 2 In the Experience window, click Range to specify a search range in the Search Range dialog
box, and click OK.
Step 3 Enter an alarm or event name, group name, or maintenance experience in the Filter by name
text box.
In the Alarm/Event Name navigation tree, alarm or event names with the keyword are listed.
Step 4 In the Alarm/Event Name navigation tree, select an alarm or event name, and then click
Modify.
NOTE
l You can select an alarm or event and double-click the blank area in the Experience area to open the
Experience dialog box.
l Click one or more icons from , , , and to classify alarms or events and increase the speed
of locating alarm or event names in the navigation tree.
Step 5 In the Experience dialog box, enter alarm or event maintenance experience. Click OK.
----End
Overflow Dumping
You can set the maximum storage capacity of the alarms/events using the U2000. The U2000
periodically checks the number of historical alarms/events. Once the historical alarm/event data
exceeds the capacity, the U2000 automatically dumps the data in the historical alarm/event
library to a file to relieve the burden of the U2000 computer. This alarm/event dumping mode
is known as the overflow dumping.
Usually, you do not need to manually configure the overflow dumping parameters. However,
on some occasions such as in a larger-scaled network, or when a large amount of alarms/events
are generated within a short period, you can set the upper threshold value. Before you perform
this operation, ensure that sufficient database and disk spaces are available.
Periodical Dumping
The U2000 automatically dumps the alarm/event data stored in the U2000 to a specified directory
according to the preset period. This alarm/event dumping mode is known as the periodical
dumping.
l You can save the alarm/event records in recent days in Alarm/Event Log Dump.
l You can set the dumping period in Alarm/Event Log Export.
NOTE
The U2000 automatically perform scheduled alarm/event dumping task every day, and alarm/event
overflow dumping task every 10 minutes. The U2000 may perform the two tasks simultaneously. Data in
the same table is deleted when either task is performed. As a result, failure messages are displayed when
both tasks are performed simultaneously.
Manual Dumping
By using this function, you can dump the historical alarm/event data in the U2000 database to
a specified directory at any time. This mode is known as the manual dumping. In this mode, you
can specify the period for manual dumping. All alarms/events cleared within this period are
dumped to the specified directory. You can manually back up or delete these files.
NOTE
l In Windows, the dump files are usually saved to the %IMAP_ROOT%\var directory.
l In Solaris and SUSE Linux, the dump files are usually saved to the $IMAP_ROOT/var directory.
Context
In an alarm or event log scheduled dumping task and an alarm or event log overflow dumping
task, dumped alarm or event logs are deleted from the same database table. If one task starts
when the other task is still running, the task startup fails. The failed task will restart in the next
execution period.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the navigation tree on the left of the Task Management window, choose Database Capacity
Management.
Step 3 In the Task Management window, double-click the Alarm/Event Log Dump task in the task
list.
Step 4 In the Attribute dialog box, modify common and extended parameters.
Step 5 Click OK.
----End
Context
In an alarm or event log scheduled dumping task and an alarm or event log overflow dumping
task, dumped alarm or event logs are deleted from the same database table. If one task starts
when the other task is still running, the task startup fails. The failed task will restart in the next
execution period.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the navigation tree on the left of the Task Management window, choose Overflow Dump.
Step 3 In the Task Management window, double-click the Alarm Overflow Dump or Event
Overflow Dump task in the task list.
Step 4 In the Attribute dialog box, modify common and advanced parameters.
----End
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the navigation tree on the left of the Task Management window, choose Manual Dump.
Step 3 In the Task Management window, right-click the Alarm Manual Dump or Event Manual
Dump task in the task list, then choose Run.
NOTE
Dump path indicates the path of the dump file. Dumped files are stored on the U2000 server.
l The dump path of alarm data is /opt/oss/server/var/AlarmManualDump/FM on Solaris and SUSE
Linux and D:\oss\server\var\AlarmManualDump\FM on Windows.
l The dump path of event data is /opt/oss/server/var/EventManualDump/FM in Solaris and SUSE
Linux and D:\oss\server\var\EventManualDump\FM on Windows.
----End
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the navigation tree on the left of the Task Management window, choose File Interface.
Step 3 In the Task Management window, double-click the Alarm/Event Log Export task in the task
list.
Step 4 In the Attribute dialog box, modify common and extended parameters.
Step 5 Click OK.
----End
Context
The initial experience library is empty.
Procedure
Step 1 Choose Alarm Settings > Experience (application style) or Fault > Settings > Experience
(traditional style) from the main menu.
Step 2 In the Experience window, click Range to specify a search range in the Search Range dialog
box, and click OK.
Step 3 Enter an alarm or event name, group name, or maintenance experience in the Filter by name
text box.
In the Alarm/Event Name navigation tree, alarm or event names with the keyword are listed.
Step 4 In the Alarm/Event Name navigation tree, select an alarm or event name, and then click
Modify.
NOTE
l You can select an alarm or event and double-click the blank area in the Experience area to open the
Experience dialog box.
l Click one or more icons from , , , and to classify alarms or events and increase the speed
of locating alarm or event names in the navigation tree.
Step 5 In the Experience dialog box, enter alarm or event maintenance experience. Click OK.
----End
Context
l Alarm or event experience can be exported only to TXT, HTML, CSV, PDF, XML, XLSX
or XLS files. Only an XML file can be imported back into the U2000 for backup or
synchronization on another server.
l For .txt files, code formats ISO-8859-1 and UTF-8 are supported. The default encoding
format is ISO-8859-1. You are advised to use the default encoding format if the saved file
does not need to support multiple languages; otherwise, UTF-8 is recommended.
NOTICE
Modifying the XML exported files may damage these files.The damaged files cannot be
imported back into the U2000.
Procedure
Step 1 Choose Alarm Settings > Experience (application style) or Fault > Settings > Experience
(traditional style) from the main menu.
Step 4 In the Export dialog box, set the path, file name, and file type for the exported file. Then click
OK.
Step 5 In the Export Experience dialog box, select Export all or Export by NE type, and click
Export.
----End
Context
Only the files in XML format can be imported to the alarm or event experience library.
NOTICE
Modifying the XML exported files may damage these files.The damaged files cannot be
imported back into the U2000.
Procedure
Step 1 Choose Alarm Settings > Experience (application style) or Fault > Settings > Experience
(traditional style) from the main menu.
Step 4 In the Open dialog box, select the target file, and then click Open.
Step 5 In the Import Experience dialog box, select Add or Update, and then click Import.
----End
NOTE
The product feature you have purchased may use personal information of users when providing services
or maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws
of the countries concerned and the user privacy policies of your company, to ensure that the personal data
of users is fully protected.
You can set alarm maintenance status for an object in either of the following ways:
l Directly set alarm maintenance status. For details, see 7.12.4 Setting the Alarm
Maintenance Status.
l Create a construction task.
Figure 7-22 shows the methods available for creating a construction task.
Mandatory Optional
Method 1 Method 2
Configure a
Configure a
Construction Task for
construction task
NEs
Method 1 Method 2
Advantages: Advantages:
The managed objects of the construction You can create a construction task for NEs
task can be NEs, boards, subboards, or in the Main Topology directly.
ports.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
NOTE
Procedure
Step 1 In the Main Topology, select one or more NEs to be maintained, right-click, and choose
Construction Task > Configure Construction Task from the shortcut menu.
Step 2 In the Configure Construction Task dialog box, set Construction Task Name, Start Time,
and End Time.
----End
Result
When the construction task is valid:
Follow-up Procedure
NEs that are commissioned, installed, or tested must be deleted from construction tasks to restore
the NEs from the maintenance state by referring to Remove an object from a construction
task in 7.12.3 Configuring Objects for a Construction Task.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
The default construction task is created automatically by the U2000 without any objects. It is
permanently valid and cannot be deleted or modified. Objects need to be added manually.
Procedure
Step 1 Choose Fault > Configure Construction Task (traditional style) from the main menu or select
Fault Management in Application Center and choose Alarm Settings > Configure
Construction Task (application style) from the main menu.
Step 2 In the Configure Construction Task window, you can perform the operations that are listed in
the following table.
Option Description
Create a construction task 1. Click Create. The Create Construction Task dialog box is
displayed.
2. In the Construction Task Information area, enter task
information.
3. Optional: In the Object List area, click Add. In the dialog
box that is displayed, select the desired object or objects.
4. Click OK to save the settings.
----End
Follow-up Procedure
You need to add managed objects to a new construction task to maintain the objects. For details,
see 7.12.3 Configuring Objects for a Construction Task.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l An object can be added to different created construction tasks but cannot be added to both
the default construction task and created construction tasks.
l The maintenance status of objects in a created construction task is automatically set based
on the task status. If the construction task of an object is in the Active state,
Maintenance is displayed as the maintenance status of the alarms reported by the object,
Procedure
Step 1 In the Main Topology, right-click an NE in the maintenance state and choose Construction
Task > Query Construction Task from the shortcut menu.
NOTE
Alternatively, perform the following operation to open the Query Construction Task dialog box:
Choose Fault > Configure Construction Task (traditional style) from the main menu or select Fault
Management in Application Center and choose Alarm Settings > Configure Construction Task
(application style) from the main menu.
Step 2 In the dialog box, you can select All Records from the drop-down list to view all
construction tasks on the U2000, The following figure lists the operations you can perform in
the Query Construction Task dialog box.
Option Description
Query objects in a construction task Select a construction task and view its objects in
the Object List area in the lower pane.
Option Description
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
The U2000 provides the following two methods to set maintenance status for objects. You can
use either of them to set maintenance status for objects based on actual requirements.
l Method 1: Set maintenance status for selected NEs directly in the Main Topology, which
is easy. After you set the status of an NE to Maintenance, the NE is automatically added
to the default construction task.
NOTE
Procedure
l Method 1:
1. In the Main Topology, select one or more desired NEs, right-click, and choose Set
Maintenance Status > Maintenance or Set Maintenance Status > Normal from
the shortcut menu.
2. In the Result dialog box, click Close.
l Method 2:
1. Choose Fault > Configure Construction Task (traditional style) from the main menu
or select Fault Management in Application Center and choose Alarm Settings >
Configure Construction Task (application style) from the main menu.
2. Select one or multiple objects in the default construction task.
NOTE
For objects in created construction tasks, alarm maintenance status changes automatically when
the construction task start time or end time is due. It cannot be set manually.
3. Right-click and choose Set Maintenance Status > Normal or Set Maintenance
Status > Maintenance from the shortcut menu. Then Normal or Maintenance is
displayed in the Status column for the selected object or objects.
----End
Result
l After the maintenance status of an object is set to Maintenance:
– The Browse Current Alarm window displays Maintenance in the Maintenance
Status column for alarms reported by the object.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
This function suppresses only NE-level alarms. For details on suppression of board- or port-
level alarms, see 7.13.1.2 Suppressing Alarms of a Board or Port.
Procedure
Step 1 In the NE Explorer, click an NE and choose Alarm > NE Alarm Suppression from the Function
Tree.
NOTE
Network-wide alarm attribute setting: Choose Configuration > NE Batch Configuration > NE Alarm
Attributes (traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Configuration > NE Batch Configuration > NE Alarm Attributes (application style)
from the main menu.
Step 2 Select an alarm that you want to suppress, and set the Status of the alarm as Suppressed.
NOTE
l If you have already created an alarm attribute template, click Use Template to select the template, and
then set alarm suppression for the NE.
l To suppress alarms for multiple NEs, you can customize an alarm attribute template, and apply the
alarm attribute template to these NEs.
----End
Result
l After an alarm is suppressed, the NE does not monitor the alarm.
l After an alarm is suppressed, the U2000 does not clear the reported alarms, until an alarm
cleared notification is received.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > Alarm Suppression from the Function
Tree.
Step 2 Select a port from the Monitored Object drop-down list in the right-hand pane.
NOTE
In the Monitored Object field, you can select the current board to include all ports of the board, or select
multiple individual ports at the same time.
Step 3 Set the Status of the alarms that need to be suppressed to Suppressed.
NOTE
If you have already created an alarm template for a board, click Use Template to select a suitable template.
Click Apply and the Operation Result dialog box is displayed.
----End
Result
l After an alarm is suppressed, the board does not monitor the alarm.
l After an alarm is suppressed, the U2000 does not clear the reported alarms, until an alarm
cleared notification is received.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Cross-connections must be created on the ATM board (For example: the AL1 board on the
4.0 equipment).
Procedure
Step 1 In the NE Explorer, select an ATM board and choose Alarm > ATM Connection Alarm
Suppression from the Function Tree.
Step 2 Click Query to query the alarm information from the NE.
Step 3 Click Select Connection. The Select Connection dialog box is displayed.
Step 4 In the Select Connection dialog box, select a connection and click OK.
Step 5 You can use any of the following ways to set alarm suppression:
l Click Default.
l Click Use Template. Select a template from the Select Template dialog box displayed,
and click OK.
l Set Status for each Event.
----End
Result
l After an alarm is suppressed, the board does not monitor the alarm.
l After an alarm is suppressed, the U2000 does not clear the reported alarms, until an alarm
cleared notification is received.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l To set the alarm suppression status, you are an NMS user with "Operator Group" authority
or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 Click the networkwide maintenance status icon on the toolbar, and the Networkwide
Maintenance Status dialog box is displayed.
Step 2 Choose Alarm Suppression, select one or more NEs from the Function Tree and click
, view the alarm suppression status for a path.
NOTE
If the queried information is null, the alarm suppression is not set for any path.
Step 3 Optional: To restore the suppression status to the default value, right-click and choose
Default from the shortcut menu. Click Apply. A prompt is displayed indicating that the operation
is successful. Click Close.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
l After you set the alarm reversion for an NE, the alarm status of the NE in the U2000 is
contrary to the actual alarm status on the NE. To be specific, when alarms are generated
on the NE, the NE does not report the alarms to the U2000.
l Currently, you can set the alarm reversion for the following alarms:
– MSTP equipment: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, and
DDN_ALOS
– WDM equipment: R_LOS, MUT_LOS and ETH_LOS
– RTN equipment: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, and DDN_ALOS
– PTN equipment: R_LOS, T_ALOS, and ETH_LOS
– submarine equipment: R_LOS, MUT_LOS, MUT_TLOS, OSC_LOS, and T_ALOS
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Alarm Attributes (traditional style)
from the main menu or select Fix-Network NE Configuration in Application Center and
choose Configuration > NE Batch Configuration > NE Alarm Attributes (application style)
from the main menu.
Step 2 In the Object Tree on the left, select one or more NEs, and click .
Step 3 In the dialog box that is displayed, click Close.
Step 4 Click Query to query the alarm reversion modes of NEs from the NE side.
Step 5 In the dialog box that is displayed, click Close.
Step 6 Select an NE and set Alarm Reversion to Enable (Auto Restore) or Enable (Manually
Restore).
NOTE
l If you set Alarm Reversion to Enable (Auto Restore), when an alarm of an NE ends, the alarm
reversion is automatically disabled on the NE and the alarm status returns to normal.
l If you set Alarm Reversion to Enable (Manually Restore), the alarm status can return to normal only
after the alarm reversion is manually disabled.
l When you set Alarm Reversion to Disable, the alarm reversion cannot be set for the NE and the NE
reports alarms in the normal state.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to some alarms of the MSTP and WDM equipment.
l Alarm Reversion of the NE where the alarm is generated must be set to Enable (Auto
Restore) or Enable (Manually Restore). For details, see 7.13.2.1 Setting the Alarm
Reversion Mode of an NE.
Context
Currently, you can set the alarm reversion for the following alarms:
l MSTP equipment: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, and DDN_ALOS
l WDM equipment: R_LOS, MUT_LOS and ETH_LOS
Procedure
Step 1 Choose Fault > Browse Current Alarm (traditional style) from the main menu or select Fault
Management in Application Center and choose Browse Alarm > Browse Current Alarm
(application style) from the main menu.
Step 2 In the Filter dialog box, set filter criteria and click OK.
When setting filter criteria, you can filter alarms by equipment according the actual situation.
This helps you to fast locate and analyze the fault of a certain set of equipment.
NOTE
l Alternatively, you can click Copy From Template. In the dialog box that is displayed, select a template
and click OK to import the filter criteria that are defined in the template to the Filter dialog box.
l If you set the startup template for viewing current alarms, the Filter dialog box is not displayed and
the alarms that meet the filter criteria are displayed directly.
Step 3 In the alarm list, select one or more alarms, right-click, and choose Alarm Reversion from the
shortcut menu.
NOTE
If one or more alarms of the selected alarms support the alarm reversion, the Alarm Reversion shortcut
menu item is available. The alarm reversion is set for only the alarms that support the function.
If all selected alarms do not support the alarm reversion, the Alarm Reversion shortcut menu item is grayed
out.
----End
Result
l On the corresponding ports of the specified resources, Reversion Status of the alarms is
changed to Enabled.
l If the alarm of the specified resource is in the uncleared state, the alarm is changed to the
cleared state automatically.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
If you set the alarm reversion for a port, the displayed status of all alarms that support the alarm
reversion on this port is contrary to their actual status. Currently, you can set the alarm reversion
for the following alarms:
l MSTP equipment: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, and DDN_ALOS
l WDM equipment: R_LOS, MUT_LOS and ETH_LOS
l RTN equipment: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, and DDN_ALOS
l PTN equipment: R_LOS, T_ALOS, and ETH_LOS
l submarine equipment: R_LOS, MUT_LOS, MUT_TLOS, OSC_LOS, and T_ALOS
Procedure
Step 1 In the NE Explorer, select the NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
Step 2 Set Alarm Reversion to Enable (Auto Restore) or Enable (Manually Restore). Click
Apply.
NOTE
After the port alarm is cleared, if you set the Alarm Reversion to Enable (Auto Restore), the reversion
setting is automatically cancelled at the NE side. Thus, the alarm status returns to normal. If the Alarm
Reversion is set to Enable (Manually Restore), the alarm status can return to normal only after the alarm
reversion setting is manually cancelled. If the Alarm Reversion is set to Disable, you cannot set alarm
reversion at the port.
Step 3 In the NE Explorer, select a board and choose Alarm > Alarm Reversion from the Function
Tree.
----End
Result
l When you set the alarm reversion for a port, the alarm status on this port is opposite to the
actual situation. That is, alarms are not reported even if they exist.
l When you set the alarm reversion for a port, the alarm status of the board does not change,
and the alarm indicator still indicates the actual running status of the equipment.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The trail must be activated.
l Alarm Reversion of the NE where the alarm is generated must be set to Enable (Auto
Restore) or Enable (Manually Restore).
Context
If you set alarm reversion for a trail, all alarms of this trail which support the function are reverted.
You cannot set alarm reversion for a single alarm of the trail. Currently, you can set the alarm
reversion for the following alarms: R_LOS, MUT_LOS, T_ALOS, ETH_LOS, P_LOS, and
DDN_ALOS.
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Trail (traditional style) from the main menu or
select Bearer Network Service Configuration in Application Center and choose Service >
SDH Trail > Manage SDH Trail (application style) from the main menu.
Step 2 In the Set Trail Browse Filter Criteria dialog box, set the filter criteria and click Filter All.
The trails are displayed in the list.
NOTE
l Click Filter All to refresh and display all the qualified trails.
l Click Secondary Filter to filter the trails that are already displayed.
l Click Incremental Filter to add newly qualified trails to the list without refreshing the trails that are
already displayed.
Step 3 Select one or more trails, click Alarm and select Alarm Reversion from the drop-down list.
NOTE
Step 4 In the Alarm Reversion dialog box, set Reversion Status of the trail to Enabled.
Step 5 Click Apply. In the Operation Result dialog box, click Close.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l To set the alarm reversion status, you are an NMS user with "Operator Group" authority
or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 Click the networkwide maintenance status icon on the toolbar, and the Networkwide
Maintenance Status dialog box is displayed.
Step 2 Choose Alarm Reversion, select one or more NEs from the Function Tree and then click
to view the alarm reversion status for a path.
NOTE
If the queried information is null, the alarm reversion is not set for any port.
Step 3 Optional: Set the alarm reversion status and then click Apply. A prompt is displayed indicating
that the operation is successful. Click Close.
NOTE
If the alarm reversion is set for a port, the alarm status of this port is opposite to the actual status. That is,
when an alarm exists, the status is displayed as normal. This setting helps filter out negligible alarms. When
alarm suppression is set for a LOS alarm of the port, you cannot set alarm reversion at the same time.
----End
7.13.3 Setting the Types of Lower Order Services in the VC4 Path
The LP_UNEQ indication can be inserted for the port timeslots that are not configured with
lower order services, only after you set the TUG structure of the VC4 path in the transmit
direction.
Prerequisites
l You are an NMS user with "Maintenance Group" authority or higher.
l Applies to the N3SL64 and N4SL16 boards.
Context
When a third-party lower order service enters the local equipment through the VC4 path, you
can monitor the performance of this service. This helps you determine whether the performance
or alarms of this service are of the local equipment. By setting the TUG structure in the receiving
direction of the VC4 path, you can determine the class of the lower order service. If the class of
a third-party lower order service is already determined, you can enable the monitoring of lower
order alarms and set the specific alarms to be monitored, to monitor the performance of the
service.
VC4
Third-party
network
Configured Service
Unconfigured Service
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Set TUG Structure from the
Function Tree.
Step 2 Set Direction to Send, and set TUG3-1 Structure Type, TUG3-2 Structure Type and TUG3-3
Structure Type to Not Configured, VC12 or VC3 as required.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" authority or higher.
l Applies to the N3SL64 and N4SL16 boards.
Context
When a third-party lower order service enters the local equipment through the VC4 path, you
can monitor the performance of this service. This helps you determine whether the performance
or alarms of this service are of the local equipment. By setting the TUG structure in the receiving
direction of the VC4 path, you can determine the class of the lower order service. If the class of
a third-party lower order service is already determined, you can enable the monitoring of lower
order alarms and set the specific alarms to be monitored, to monitor the performance of the
service.
VC4
Third-party
network
Configured Service
Unconfigured Service
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > Set TUG Structure from the
Function Tree.
Step 2 Set Direction to Receive, and set TUG3-1 Structure Type, TUG3-2 Structure Type and
TUG3-3 Structure Type to Not Configured, VC12 or VC3 as required.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 4 Select VC4 Path, right-click, and choose Lower Order Performance Management from the
shortcut menu. In the Lower Order Performance Management window, select Monitored
Object and set Monitor Status to Enabled.
Step 5 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 7 In the NE Explorer, select a line board and choose Alarm > Lower Order Path Alarm from
the Function Tree.
Step 8 Select Level and double-click Type of Monitored Alarm to set the alarm monitoring type.
Click OK.
Step 9 Click Apply. Then, in the Operation Result dialog box, click Close.
----End
insertion mode of alarms in the channel according to the networking and service requirements,
This setting helps interconnecting management and maintenance of two operators' networks.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the OptiX OSN 3500.
Procedure
Step 1 In the NE Explorer, select an NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
The default insertion mode is UNEQ Mode. In the case of hybrid networking with the third-party network,
the insertion mode can be set to AIS Mode or UNEQ Mode according to the requirements of the third-
party network.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > QoS Alarm > Bit Error Alarm
Threshold from the Function Tree.
NOTE
Choose Configuration > NE Batch Configuration > NE Bit Error Alarm Threshold (traditional style)
from the main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Batch Configuration > NE Bit Error Alarm Threshold (application style) from
the main menu. To specify bit error alarm thresholds for multiple NEs, complete the operation by means
of NE batch configuration.
NOTE
You can set the bit error alarm thresholds for the ports that the trail traverses. In the trail management
window, select a trail, click Alarm and select Alarm Threshold from the drop-down list.
Step 2 Set the desired threshold. If error bits exceed the Signal Degrade threshold, the signal has
degraded. If error bits exceed the Excessive BER threshold, the error bits are excessive.
NOTE
There are two types of bit error thresholds for the excessive bit error and signal degrade.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the SDH, PTN, RTN series NEs and OptiX Metro 6100 NE.
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > QoS Alarm > AIS Insertion from the
Function Tree.
Step 2 Select Port/Path and set the event you concern to Enabled.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the SDH and RTN equipment. The PDH tributary board must be created.
Context
NOTE
This operation may affect services.
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > QoS Alarm > UNEQ Insertion
Switch from the Function Tree.
Step 2 Click Query to query the UNEQ insertion status of each Port/Path from the NE.
Step 3 Set the UNEQ insertion switch for each Port/Path as required.
NOTE
The UNEQ has the two switches, LOS and Path Not Used. When the board detects LOS alarms or that
the channel is not used, the service signal code will be inserted with all "0", indicating that the signal is
unavailable.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
Context
NOTICE
This operation may affect services.
Procedure
Step 1 In the NE Explorer, select a board and choose Alarm > Alarm Insertion from the Function
Tree.
Step 3 Select an alarm whose Insertion Status is Not Inserting. Click Insert.
The information about the alarm inserted to the specified path is displayed in the Inserted Alarm
List pane.
Step 5 Optional: To stop the alarm insertion, select one or more alarms from the Inserted Alarm
List pane, and click Clear.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Procedure
Step 1 Choose Service > SDH Trail > Manage SDH Trail (traditional style) from the main menu or
select Bearer Network Service Configuration in Application Center and choose Service >
SDH Trail > Manage SDH Trail (application style) from the main menu.
Step 2 In the Set Trail Browse Filter Criteria dialog box, set the filter criteria and click Filter All.
The trails are displayed in the list.
NOTE
l Click Filter All to refresh and display all the qualified trails.
l Click Secondary Filter to filter the trails that are already displayed.
l Click Incremental Filter to add newly qualified trails to the list without refreshing the trails that are
already displayed.
Step 3 Select a VC4 trail or VC4 server trail. Click Maintenance and choose Alarm Insertion from
the drop-down menu.
Step 4 In the Alarm Insertion dialog box displayed, set the value of AIS Alarm Insertion or RDI
Alarm Insertion to Insert.
Step 5 Click Apply. In the Operation Result dialog box, click Close.
Step 6 Close the Alarm Insertion dialog box. A confirmation dialog box will be displayed.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l To set the path alarm insertion status, you are an NMS user with "Operator Group" authority
or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
NOTICE
Inserting alarm may interrupt the service.
Procedure
Step 1 Click the network-wide maintenance status icon on the toolbar, and the Network-wide
Maintenance Status dialog box is displayed.
Step 2 Choose Alarm Insertion, select one or more NEs from the Object Tree and then click
to view the alarm insertion status for a path.
NOTE
If the queried information is null, the alarm insertion is not set for any path.
Step 3 Optional: Set the alarm insertion operation and then click Apply. A prompt is displayed
indicating that the operation is successful. Click Close.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the WDM series NEs.
Procedure
Step 1 In the NE Explorer, select a board and choose Configuration > WDM Interface from the
Function Tree.
Step 3 To query the details about the alarm inserted at the ODU layer from the NE, do as follows:
l Click Quick Query to query the information about the selected parameters from the NE.
l Click Query to query the information about all the parameters from the NE.
Step 4 Set AIS Insertion in the ODU Layer, LCK Insertion in the ODU Layer and OCI Insertion
in the ODU Layer as required.
NOTICE
Configuring the parameter LCK Insertion in the ODU Layer as Enabled for PM overhead
may interrupt service.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
You can set the register mode for NE alarms to Wrap or Stop.
l Wrap: When the NE alarm register is full, the register discards the earliest alarms to store
new alarms. The Wrap mode is the default mode and used more often than the Stop mode.
NOTE
The NE alarm register can store all alarms and report them in time to the U2000 when the NE is
working properly.
l Stop: When the NE alarm register is full, it does not accept any new alarms so that you
cannot be informed of the new alarms. Therefore, usually this mode is not used.
Procedure
Step 1 In the NE Explorer, select an NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
NOTE
To set alarm attributes for multiple NEs: Choose Configuration > NE Batch Configuration > NE Alarm
Attributes (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Configuration > NE Batch Configuration > NE Alarm Attributes
(application style) from the main menu.
Step 2 Click Query to query the alarm register mode of the NE from the NE.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
You can set the NE alarm correlation suppression to the following two status: Enabled and
Disabled.
l Enabled: When alarms are raised from an NE, the U2000 records only the root alarm while
suppresses the alarms generated by the root alarm.
l Disabled: When alarms are raised from an NE, the U2000 records all the alarms, including
the root alarm and correlative alarms. By default NEs use this mode.
Procedure
Step 1 In the NE Explorer, select an NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
NOTE
To set alarm attributes for multiple NEs: Choose Configuration > NE Batch Configuration > NE Alarm
Attributes (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Configuration > NE Batch Configuration > NE Alarm Attributes
(application style) from the main menu.
Step 2 Click Query to query the enabling status of the NE alarm correlation suppression from the NE.
Double-click the Correlation Analysis list and choose Enabled or Disabled from the drop-
down list.
l Double-click the Correlation Analysis list and choose Enabled or Disabled from the drop-
down list.
l To set Correlation Analysis to Disabled, you can click Default.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series NEs.
Procedure
Step 1 In the NE Explorer, select an NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
Step 2 Click the Alarm Correlation Rules tab and query the NE alarm correlation rules from the NE.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
l Alarm Reporting Delay Time (s): Indicates the duration for the alarm monitoring to persist
before the NE reports a newly raised alarm.
l Alarm Clearing Delay Time (s): Indicates the duration for the alarm monitoring to persist
before the NE reports that the alarm is cleared.
Procedure
Step 1 In the NE Explorer, select an NE and choose Alarm > NE Alarm Attribute from the Function
Tree.
NOTE
To set alarm attributes for multiple NEs: Choose Configuration > NE Batch Configuration > NE Alarm
Attributes (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Configuration > NE Batch Configuration > NE Alarm Attributes
(application style) from the main menu.
Step 2 Click Query to query the alarm delay status of the NE from the NE side.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Context
The triggered alarm insertion is applicable only to an SNCP ring network with different IF cards.
The insertion function is set on an appropriate IF card to ensure successful SNCP switching.
As shown in Figure 7-23, IF1 and IFU2 consist of a ring network. NE1 is the sink of the SNCP
service, selectively receiving services from NE2 or NE5. When NE1 detects the TU_AIS alarm,
protection switching is implemented. For example, the E1_AIS alarm is detected on IFU2 of
NE2 if the microwave link between NE3 and NE4 is detected. When signals are transmitted to
IF1 of NE2 by means of cross-connections, the signals are encapsulated with the correct TU
overhead. As a result, the downstream NE1 cannot detect the TU_AIS alarm and no SNCP
switching is triggered. The protection mechanism becomes invalid. In this case, insert the
TU_AIS alarm for the E1_AIS alarm on IFU2 of NE2 to ensure successful SNCP switching at
NE1.
Figure 7-23 SNCP protection in a ring network with IF1 and IFU2 cards
working 1 protection 1
IF1
IF1
NE1
NE2
IFU2
NE5
IFU2
NE3
IFU2
NE4
working 2 protection 2
Procedure
Step 1 In the NE Explorer, click the appropriate card and choose Alarm > Triggered Alarm
Insertion from the Function Tree.
Step 2 Select the required path, double-click the corresponding table cell in the Insert TU_AIS to
E1_AIS column, and choose Enabled from the drop-down list.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The equipment type must be OptiX OSN 1500, OptiX OSN 2500, OptiX OSN 3500, OptiX
OSN 7500, or OptiX OSN 7500II.
l Lower order service (VC3 or VC12) must be configured on the line board.
Context
During the configuration of higher order pass-through cross-connections, enabling alarm
monitoring for lower order paths broadcasts services to the lower order section of the cross-
connection board. This wastes lower order service resources if lower order services do not need
to be monitored.
Procedure
Step 1 In the NE Explorer, select a line board and choose Alarm > Lower Order Path Alarm from
the Function Tree.
Step 2 Click Query to query the alarm monitoring status of the lower order paths from the NE.
Step 4 Set whether to monitor the alarms on the VC3-1, VC3-2 and VC3-3 path.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the RTN series NEs.
l A microwave link must have been configured.
Procedure
Step 1 Right-click a microwave link in the topology and choose Microwave Link Alarm from the
shortcut menu. The important intermediate frequency information and alarm information of the
NEs on both ends of a microwave link is displayed respectively.
Step 2 After setting the auto-refresh time interval, click Auto Refresh. The parameters in the GUI will
be refreshed automatically according to the preset time interval.
Step 3 Optional: Click Details of Alarm to switch to the current alarm window and view the alarm
details.
----End
Procedure
Step 1 Troubleshoot abnormal NEs.
1. Choose Fault > Query Alarm Log Statistics (traditional style) from the main menu or
select Fault Management in Application Center and choose Browse Alarm > Alarm
Log Statistics (application style) from the main menu. In the Statistic Filter dialog box,
set Level 1 statistics item to NE and record the top N NEs by the large number of alarms.
2. Choose Fault > Browse Current Alarm (traditional style) from the main menu or select
Fault Management in Application Center and choose Browse Alarm > Browse Current
Alarm (application style) from the main menu.
3. In the Filter dialog box, click the Alarm Source tab. In the Select area, select Custom and
choose Add > Object below NE. In the Object below NE dialog box, filter alarms reported
by NEs recorded in the previous step. Then click OK.
4. Sort alarms by alarm severity and troubleshoot abnormal NEs by referring to alarm
troubleshooting suggestions.
Step 2 Synchronize NE alarms. Choose Fault > NE Alarm Synchronize (traditional style) from the
main menu or select Fault Management in Application Center and choose Browse Alarm >
Synchronize NE Alarms (application style) from the main menu.
----End
Result
If an alarm threshold-crossing notification is reported after 30 minutes, perform the preceding
steps or contact Huawei technical support.
Prerequisites
l An alarm exists in an SDH or WDM trail and the alarm is not cleared when you view the
alarm.
l You must have the license for the service fault analysis function.
Navigation Path
l In the Browse Current Alarm window, right-click an alarm and choose Service Fault
Analysis from the shortcut menu.
l In the Manage WDM Trail or Manage SDH Trail window, right-click a trail where alarms
are generated, and choose Service Fault Analysis from the shortcut menu.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
Some common fault diagnosis rules are pre-set in the U2000, such as R_LOS, TU_AIS, HP_TIM
and B1_EXC.
Procedure
Step 1 Choose Fault > Settings > Fault Diagnosis Rules (traditional style) from the main menu or
select Fault Management in Application Center and choose Alarm Settings > Fault
Diagnosis Rules (application style) from the main menu.
Step 2 In the Fault Diagnosis Rules navigation tree, select the alarm for which you want to set the
rules, right-click the alarm branch, and then choose Add Rules from the shortcut menu. The
Create Fault Diagnosis Rules dialog box is displayed.
Step 3 Select an alarm for which you want to add the diagnosis rule and click OK. The rules of the
alarm are displayed below the Fault Diagnosis Rules branch.
Step 4 Right-click the new rule and choose Add Steps from the shortcut menu. The Create Diagnosis
Steps dialog box is displayed.
Step 5 Set the Alarm Causes, Diagnosis Method and Processing Method. Click OK.
Step 7 Optional: You can right-click a step entry and choose Modify from the shortcut menu to modify
the original contents as required.
Step 8 Optional: After adding rules to the exported CSV file, you can click Import to import this file
to the U2000.
NOTE
If you want to maintain fault diagnosis rules using a CSV file, you are advised to use the CSV file exported
from the U2000.
Step 9 Optional: You can click Export to export the fault handling suggestion to a CSV file.
----End
Prerequisites
l In the window of viewing current alarms, the alarm that is not cleared and can be associated
to a certain trail must exist.
l SDH or WDM trails must exist and must be active.
l You must have the licenses for fault location and correlation analysis.
Procedure
Step 1 The navigation paths for the service fault analysis wizard are as follows:
l Choose Fault > Browse Current Alarm (traditional style) from the main menu or select
Fault Management in Application Center and choose Browse Alarm > Browse Current
Alarm (application style) from the main menu. Right-click an alarm, and choose Service
Fault Analysis from the shortcut menu.
l Choose Service > SDH Trail > Manage SDH Trail (traditional style) from the main menu
or select Bearer Network Service Configuration in Application Center and choose
Service > SDH Trail > Manage SDH Trail (application style) from the main menu. Right-
click a trail, and choose Service Fault Analysis from the shortcut menu.
l Choose Service > WDM Trail > Manage WDM Trail (traditional style) from the main
menu or select Bearer Network Service Configuration in Application Center and choose
Service > WDM Trail > Manage WDM Trail (application style) from the main menu.
Right-click a trail, and choose Service Fault Analysis from the shortcut menu.
Step 2 Navigate to the Trail Connectivity Status wizard. The information about the trail associated
with the alarm is displayed. Analyze the status of the trail to check whether it is interrupted.
NOTE
In this step, you can select two or more trails and click Query Overlapped Node to view the information
about the overlapped nodes of the selected trails.
Step 3 Select a trail and click Next. In the Trail Faulty Point Analysis window, view the analysis of
the fault that occurs in the trail. By analyzing the fault point, you can locate the point where the
fault or root alarm occurs.
NOTE
In this step, you can select a trail in Alarm Information and click Query Related Information to view
the other related functions of the trail. You can click the button of a function to switch to the corresponding
window of the function.
The Query Related Information button provides the Query Laser Status, Query History
Performance and Query Optical Power submenu items.
Step 4 In the Alarm Information area, select an alarm and click Next. In the Troubleshooting
Suggestion window, you can view the Possible Causes of the alarm, and the corresponding
Diagnosis Method and Processing Method for each cause. If all these methods do not work,
see 7.13.14.3 Starting the Fault Diagnosis Wizard for more information.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l The fault diagnosis rules must be created.
Context
l If the selected alarm does not have a relevant fault diagnosis rule, a message appears
indicating that the wizard cannot be started.
l If the fault diagnosis wizard is ever used, the handling method of the previous time is
prompted, and then you can click Diagnose Again to locate the fault.
Procedure
Step 1 Choose Fault > Browse Current Alarm (traditional style) from the main menu or select Fault
Management in Application Center and choose Browse Alarm > Browse Current Alarm
(application style) from the main menu.
Step 2 In the Filter dialog box, set the filter criteria and click OK. The result is displayed in the Browse
Current Alarm window.
When setting the filter criteria, you can filter out alarms based on the actual situation. Then, you
can use the fault diagnosis rule that is set for certain equipment in Fault Diagnosis Rules to
quickly locate and analyze a fault.
NOTE
If the startup template for browsing the current alarms is set, the Filter dialog box is not displayed. Instead,
the alarms that meet the filter conditions set in the startup template are displayed directly.
Step 3 Right-click an alarm in the alarm list and choose Fault Diagnosis from the shortcut menu. The
Fault Diagnosis dialog box is displayed.
NOTE
If the alarm is not set diagnostic rules, please refer to 7.13.14.1 Creating Fault Diagnosis Rules, set
diagnostic rules for this alarm manually.
Step 4 When you select a probable cause in the Alarm Causes area, the corresponding diagnosis
method that can be used to locate the fault is displayed in the Diagnosis Method area, and the
corresponding handling method that can be used to rectify the fault is displayed in the Processing
Method area.
NOTE
Select the probable cause of the fault according to the actual situation. If you cannot decide which cause
is the most possible, then select the first cause.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to OptiX OSN 1800(NA), OptiX OSN 3800A, OptiX OSN 6800A, OptiX OSN
8800 T32(NA), OptiX BWS 1600A, OptiX BWS 1600G(NA) NEs.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Housekeeping Management
from the Function Tree. Click the Environment Property tab.
Step 3 Click New and the Create Environment Alarm Attribute dialog box is displayed.
Step 4 Select appropriate values from AID, Severity and Alarm Type. Enter the Alarm Message.
Step 6 In the Environment Property window, set the general status of environment alarm inputs and
outputs for the NE in the Normal State field.
Step 8 The Operation Result dialog box indicating the operation is successful is displayed. Click
Close.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to OptiX OSN 1800(NA), OptiX OSN 3800A, OptiX OSN 6800A, OptiX OSN
8800 T32(NA), OptiX BWS 1600A, OptiX BWS 1600G(NA) NEs.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Housekeeping Management
from the Function Tree. Click the Control Property tab.
Step 3 Click New, and the Create Control Alarm Attribute dialog box is displayed.
Step 6 Optional: Click Release for Several Seconds or Operate for Several Seconds to set Control
State of the control property. The Control State starts counting down and returns to the original
control state after passing the persistence time.
Step 7 The Operation Result dialog box indicating the operation is successful is displayed. Click
Close.
----End
Inform Mode
In Inform mode, the U2000 obtains lost alarms from network elements (NEs) by using the manual
synchronization function. The Transmission Control Protocol (TCP) handshake is simulated at
the application layer to ensure transmission reliability. After sending an alarm, an NE waits for
an Echo packet. If the NE does not receive an Echo packet within a specified period, it sends
the alarm again. If the NE still does not receive an Echo packet after the number of retransmission
times reaches the specified value, it saves the alarm to a local management information base
(MIB) table.
ESN Mode
Alarms sent by NEs that are capable of fault management carry ESNs, and alarm synchronization
tables and active alarm tables are available for such NEs. An alarm synchronization table stores
all alarms that carry ESNs and are recently reported by NEs. An active alarm table stores only
active alarms, that is, alarms that are not cleared from NEs.
l If the software version of NEs is earlier than VRP 5.130, use SNMPv2c when configuring
the reliability of alarms in inform mode.
l If the software version of NEs is VRP 5.130 or later, use SNMPv2c or SNMPv3 when
configuring the reliability of alarms in inform mode.
1. Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
2. Choose System Management > NE Channel Management > Trap Service from the
service tree.
3. On the Trap Service tab page, click Synchronize to synchronize alarms from the NE.
4. Right-click and choose Create from the shortcut menu. In the dialog box that is displayed,
set related parameters.
NOTE
SNMPv3 is used as an example in the snapshot. You can select another SNMP version as required.
SNMPv3 is recommended when NEs use a software version of VRP 5.130 or later.
5. Click OK.
6. On the Trap Service tab page, click Advanced.
7. In the dialog box that is displayed, set Enable Alarm Log to Start.
8. Click OK.
Configuration on the NE
Perform the following steps:
snmp-agent
3. Run the following command to set the alarm sending mode to Inform:
snmp-agent remote-engineid 726563656976655F74726170 usm-user v3 user-name
group group-name
snmp-agent remote-engineid 726563656976655F74726170 usm-user v3 user-name
authentication-mode Authentication Protocol
snmp-agent remote-engineid 726563656976655F74726170 usm-user v3 user-name
privacy-mode Encryption Protocol
NOTE
l The preceding three commands need to be configured only when SNMPv3 is used. If another
SNMP version is used, directly configure the target-host command.
l 726563656976655F74726170 is the engine ID of the U2000 alarm receiver, which is a fixed
value. Therefore, only one alarm receiving host can be configured in Inform mode for an NE
when SNMPv3 is used.
l The values of user-name, group-name, Authentication Protocol, and Encryption Protocol must
be the same as those configured in NE SNMPv3 parameters on the U2000.
snmp-agent target-host inform address udp-domain X.X.X.X params securityname
user-name privacy v3
NOTE
l X.X.X.X specifies the IP address of the destination host. Here, set it to the IP address of the
U2000 server.
l The values of user-name must be the same as that configured in NE SNMP parameters on the
U2000.
l If SNMPv2c is used, add cipher next to the securityname parameter and set SNMP Version to
v2c.
4. Run the following command to set parameters for sending alarms in Inform mode:
snmp-agent inform resend-times <0-10>
snmp-agent inform timeout <1-1800>
NOTE
Set the number of retransmission times to 3 and the timeout period to 10 seconds.
5. Run the following command to enable the alarm log function:
snmp-agent notification-log enable
Simple Network Management Protocol version 3 (SNMPv3) is more secure than SNMPv1 and
SNMPv2c. Using SNMPv3 is recommended.
1. Right-click the NE in the Main Topology and choose NE Explorer from the shortcut menu.
2. Choose System Management > NE Channel Management > Trap Service from the
service tree.
3. On the Trap Service tab page, click Synchronize to synchronize alarms from the NE.
4. Right-click and choose Create from the shortcut menu. In the dialog box that is displayed,
set the associated parameters and click Huawei OSS and Extended VB.
NOTE
l If Huawei OSS is selected, the alarm generation time recorded on the U2000 is the same as that
on NEs. If Huawei OSS is not selected, the alarm generation time recorded on the U2000 is the
time the U2000 server receives Trap messages. Therefore, Huawei OSS must be selected.
l If Extended VB is selected, the information about alarms carries the extended bound variables.
Incremental synchronization and analysis on some root alarms depend on the extended
information reported by NEs. Therefore, Extended VB must be selected.
5. Click OK.
Configuration on the NE
Perform the following steps:
NOTE
l X.X.X.X specifies the IP address of the destination host. Here, set it to the IP address of the
U2000 server.
l The values of user-name must be the same as that configured in NE SNMP parameters on the
U2000.
l If the NE has been configured with the private-netmanager attribute before sending an alarm, the
NE alarm generation time recorded on the U2000 is the same as that recorded on the NE. If the
NE has not been configured with the private-netmanager attribute before sending an alarm, the
NE alarm generation time recorded on the U2000 is the U2000 server time when the U2000
receives the trap packet from the NE.
l If the SNMPv3 protocol is not used, add cipher next to the securityname. SNMPv3 is
recommended because it is more secure.
8 Performance Management
(MSTP&WDM&RTN&PTN)
To ensure the normal functioning of the network, the network management and maintenance
personnel should periodically check and monitor the network by taking proper performance
management measures.
Ethernet port performance Ethernet port performance 8.4 Viewing Ethernet Port
events monitor Ethernet Flow
services on ports.
Lower order performance Lower order performance 8.6 Viewing Lower Order
events monitor performance Performance Data
of VC4 lower order services
on N3SL64 and N4SL16
boards by setting the tributary
unit group (TUG) structure.
When a third-party lower
order service enters the local
equipment through the VC4
path, you can monitor the
performance of this service.
This helps you determine
whether the performance or
alarms of this service are of
the local equipment. By
setting the TUG structure in
the receiving direction of the
VC4 path, you can determine
the class of the lower order
service. If the class of a third-
party lower order service is
already determined, you can
enable the monitoring of
lower order alarms and set the
specific alarms to be
monitored, to monitor the
performance of the service.
For details see Figure 8-1.
Third-party
network
Configured Service
Unconfigured Service
NOTE
For details on the performance event types supported by devices, see Maintenance and Fault
Management > Alarms and Events Handling > Performance Event List in the product documentation
of the devices.
The performance is different from an alarm. When a performance event is reported, the service
is not interrupted. The transmission quality, however, is degraded compared to the normal
situation and the degradation is temporarily compensated by the error correction mechanism of
the equipment. As the degradation factors increases, the performance threshold crossing and
even an alarm may occur.
You can use the performance management function to detect the degrade trend and to handle
the trouble before the failure actually occurs.
Enable performance N
End
monitoring
Enable automatic N
End
reporting
Description
l Performance Monitoring
Performance monitoring is realized on the board. By default, the board performance
monitoring is enabled. For example, if 15-minute performance monitoring is set. Every
time when a period starts, the board finds a free performance register and clears the data.
Then, the board starts to count the performance events. When the monitoring period ends,
the performance data is updated to the register.
NOTE
Current Performance
Current performance means the data that is saved in the current performance register of an NE.
The current performance can be classified as 15-minute current and 24-hour current based on
the monitoring period. When the current performance is viewed, the U2000 queries the
performance data from the current performance register on the NE side.
History Performance
History performance means the performance data that the NE detects in a specific period in the
past. When the history performance data is queried, the system queries the performance data
from the NE side or from the NM side depending on the location in which the data is saved.
The ended current performance data is dumped to the history performance register of the NE.
The process for synchronizing the history performance data in the NE history performance
register to the database on the NM side is described as follows.
Work Principle
The performance index of the physical component on an NE develops according to its own
development trend if there are no external factors. The performance analysis function considers
this natural trend and at least five periods of history performance data to predict the trend of the
performance index.
Applied Scenario
If the fibers or services in a subnet of the network often become faulty, you can perform
performance analysis and think of solutions beforehand, such as replacing a board or fiber.
Context
Performance Type Performance Event Type
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l It is applicable to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN
series (except PTN 6900 series) and marine series NEs.
l The NE time must be synchronized with the U2000 server time.
Context
Batch configuration of performance monitoring time is implemented mainly in new deployment
and expansion scenarios. If you need to adjust a single NE, set the performance monitoring time
just for the NE.
Procedure
l Configure the performance monitoring time for multiple NEs at a time.
1. Choose Performance > Set NE Performance Monitoring Time (traditional style)
from the main menu or select Fix-Network Performance in Application Center and
choose Performance Monitoring > Set NE Performance Monitoring Time
(application style) from the main menu.
l The start time must be later than the current time of the network management system and
the end time must be later than the start time.
l If the end time is not set, this indicates that the performance monitoring starts from the start
time and does not stop.
5. Click Apply and then click Close in the Operation Result dialog box.
l Configure the performance monitoring time for a single NE.
1. In the NE Explorer, select an NE and choose Performance > NE Performance
Monitor Time from the Function Tree.
2. Click Query to query the data from the NE.
3. Set the parameters of the 15-minute and 24-hour performance monitor time according
to the requirement. Click Apply.
NOTE
l The start time must be later than the current time of the network management system and
the end time must be later than the start time.
l If the end time is not set, this indicates that the performance monitoring starts from the start
time and does not stop.
4. Click Apply and then click Close in the Operation Result dialog box.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the WDM NA series NEs.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > NE Attribute from the Function
Tree.
Step 2 Click the Status Reporting drop-down list and select Enable Performance Report to enable
the performance reporting status. A dialog box is displayed indicating that the operation was
successful.
NOTE
If you click Disable Performance Report, the NE does not report any performance events automatically
to the NM when the performance events are raised. However, you can query these performance events
from the NE manually.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
The following table lists the NE types that support the NE performance event monitoring
template.
NE Type NE Version
NE Type NE Version
Procedure
l Configure the performance event monitoring status for multiple NEs at a time.
1. Choose Performance > Performance Template Management > Performance
Event Monitor Status Template (traditional style) from the main menu or select
Fix-Network Performance in Application Center and choose Performance
Monitoring > Performance Template Management > Performance Event
Monitor Status Template (application style) from the main menu.
2. Click Performance Event Monitor Status Template tab.
3. Select a desired template from the Template Name drop-down list.
NOTE
When you customize the first performance event monitoring status template, you can set
Template Name to Default Template only.
4. Optional: Click Refresh to refresh the information about the template.
5. According to the actual monitoring requirement, select a performance event and
changes the values of the corresponding Monitor Status, 15-Minute Auto-Report,
and 24-Hour Auto-Report parameters.
NOTE
When you set the Monitor Status parameter of a performance event to Disabled, the
corresponding 15-Minute Auto-Report and 24-Hour Auto-Report parameters are
automatically changed to Disabled and dimmed.
6. You can save the performance event monitoring status template as follows:
– Click Save to directly save the modification.
NOTE
The default template cannot be directly saved. That is, the Save button is grayed out for
the default template.
– Alternatively, you can click Save As to save the template as a new template and
enter the name of the new template.
7. In the Operation Result dialog box, click Close.
8. Click Apply to. In the Apply to dialog box, select the objects that you apply the
template to and click OK. In the Operation Result dialog box, click Close to apply
the template to the selected objects in batches.
NOTE
l You can apply a performance event monitoring status template to optical NEs, NEs, and
cards.
l For the application scope of this template, see Table 1.
l Configure the performance event monitoring status for a single NE.
1. In the NE Explorer, select a board and choose Performance > Performance Monitor
Status from the Function Tree.
2. Optional: Click Default to restore the default settings.
3. Select a condition from the Monitored Object Filter Criteria drop-down list.
4. Set the Monitor Status, 15-Minute Auto-Report and 24-Hour Auto-Report.
NOTE
l For the Optix OSN 8800 series (V100R007C02 and later versions) NEs and the Optix OSN
9600/9800 series NEs, it do not support 15-Minute Auto-Report and 24-Hour Auto-
Report.
l If you have already created a performance event monitoring status template for the boards,
click Use Template and then select the desired template. Click Open.
5. Click Apply.
6. In the Operation Result dialog box, click Close.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Performance Threshold
When an NE detects that a certain performance value is beyond the specified threshold, the NE
reports the corresponding performance threshold crossing event. The performance threshold can
divided into two types.
l Single threshold: When the performance count value reaches or exceeds the single
threshold, a performance threshold crossing event is generated on the NE. When the
performance count value is smaller than the single threshold, an event is generated on the
NE indicating that the performance threshold crossing ends.
l Double Thresholds: When the performance count value is beyond the range between the
upper and lower thresholds, a performance threshold crossing event is generated on the NE.
If the performance count value is in the range between the upper and lower thresholds, an
event is generated on the NE indicating that the performance threshold crossing ends.
NOTE
If you want to set a large number of performance threshold values, you can use the template that the
U2000 provides to customize the performance threshold values.
Procedure
l Configure the performance threshold for multiple NEs at a time.
1. Choose Performance > Performance Template Management > Performance
Threshold Template (traditional style) from the main menu or select Fix-Network
Performance in Application Center and choose Performance Monitoring >
Performance Template Management > Performance Threshold Template
(application style) from the main menu.
2. Navigation Path
– For an SDH/WDM NE: Select the SDH/WDM tab.
– For an SONET/WDM NE (NA): Select the SONET/WDM (NA) tab.
3. Select a template from the Template Name drop-down list.
NOTE
If a newly-created performance threshold template does not exist, you can only select the
Default Template.
4. Modify the performance thresholds as required.
NOTE
After the performance thresholds are changed, Apply to NEs is set to Yes automatically. If
you set Apply to NEs to No manually, this performance event will not be applied to NEs or
boards, and click refresh, the performance threshold value is set to the value in the default
template.
5. Save the template, and perform one of the following operations:
NOTE
If you have already created a performance threshold template for the boards, click Use
Template and then select the desired template. Click Open.
4. Click Apply.
----End
Follow-up Procedure
You can view threshold-crossing records in the event logs.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
The Filter by Template function involves the following windows: Browse SDH
Performance, Browse WDM Performance, and Browse Control Panel Performance.
Procedure
Step 1 The navigation paths for the Filter by Template are as follows:
l Choose Performance > Browse SDH Performance (traditional style) from the main menu
or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse SDH Performance (application style) from the main menu.
l Choose Performance > Browse WDM Performance (traditional style) from the main
menu or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse WDM Performance (application style) from the main
menu.
l Choose Performance > Browse Control Plane Performance (traditional style) from the
main menu or select Fix-Network Performance in Application Center and choose
Browse Performance Data > Browse Control Plane Performance (application style)
from the main menu.
Step 2 In the Object Tree on the left of the Browse SDH Performance, Browse WDM
Performance or Browse Control Panel Performance window, select one or more NEs or
boards on NEs.
Step 3 On the lower portion of the window for viewing performance, click Filter by Template and
select Save from the drop-down list.
Step 4 In the Enter the Name dialog box, enter the template name and click OK.
NOTE
l After the template is saved, the name of the current template is displayed next to the window title.
l When you save the template, the NEs or boards in only the current window are saved.
l When you modify the original template, select Save from the drop-down list. The template does not
need to be renamed.
----End
Follow-up Procedure
In the Browse SDH Performance, Browse WDM Performance or Browse Control Panel
Performance window, you can click Filter by Template and select Open from the drop-down
list. In the dialog box that is displayed, select a template to browse the performance data.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l For details on performance event types, see 8.1.1 Introduction to Performance Events.
l The service must be configured.
l The performance monitoring parameters must be set.
l The NE time must be synchronized with the time of the computer where the U2000 is
installed.
Procedure
Step 1 Navigation Path
l Choose Performance > Browse SDH Performance (traditional style) from the main menu
or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse SDH Performance (application style) from the main
menu. Click the Current Performance Data tab.
NOTE
If you have set performance filter templates, click Filter by Template and choose Open from the
displayed menu. In the Open window, select a required template and click Open to import the
template.
l Choose Performance > Browse WDM Performance (traditional style) from the main
menu or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse WDM Performance (application style) from the main
menu. Click the Current Performance Data tab.
NOTE
If you have set performance filter templates, click Filter by Template and choose Open from the
displayed menu. In the Open window, select a required template and click Open to import the
template.
l In the NE Explorer, select an NE, and navigate to the user interface of viewing the
performance data of boards or service objects in the following ways from the Function
Tree.
SDH, WDM, PTN, RTN Physical port Select a desired board and
and Submarine equipment choose Performance >
Current Performance
from the Function Tree.
Step 2 Optional: Complete the following information: Monitored Object Filter Criteria, Monitor
Period. Select the performance event type in the Measure field and the Count field.
NOTE
All performance events supported by the board are provided as options for setting the performance event.
Step 3 Optional: In the Count area, check the Display Zero Data and Display Continuous Severely
Errored Seconds check boxes.
Step 4 Click Query to query the data from the NE.
Step 5 Optional: Click Reset to reset the performance register of the queried performance event.
NOTE
After the performance register is reset, the current performance data of this type is cleared. Then, a new
performance monitoring period is started.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l For details on performance event types, see 8.1.1 Introduction to Performance Events.
l The service must be configured.
l The performance monitoring parameters must be set.
l Time has been synchronized between the U2000 and NEs.
Context
NOTE
l If you select Query from NMS, historical performance data will be obtained from the U2000 database.
l If you select Query from NE, a message will be sent through an interface to obtain historical performance
data from NEs.
Procedure
Step 1 Navigation Path
l Choose Performance > Browse SDH Performance (traditional style) from the main menu
or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse SDH Performance (application style) from the main
menu. Click the History Performance Data tab.
NOTE
If you have set performance filter templates, click Filter by Template and choose Open from the
displayed menu. In the Open window, select a required template and click Open to import the
template.
l Choose Performance > Browse WDM Performance (traditional style) from the main
menu or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse WDM Performance (application style) from the main
menu. Click the History Performance Data tab.
NOTE
If you have set performance filter templates, click Filter by Template and choose Open from the
displayed menu. In the Open window, select a required template and click Open to import the
template.
l In the NE Explorer, select an NE, and navigate to the user interface of viewing the
performance data of boards or service objects in the following ways from the Function
Tree.
SDH, WDM, PTN, RTN Physical port Select the related board,
and Submarine equipment and then choose
Performance > History
Performance.
Step 2 Optional: Complete the information: Monitored Object Filter Criteria, Monitor Period,
Ended From/To, Data Source and Performance Event Type.
NOTE
l All performance events supported by the board are provided as options for setting the performance
event.
l Historical performance data of NEs changes with services. To query the latest historical performance
data of NEs and save the data to the U2000 database, set Data Source to Query from NE and select
Save to Database. Then the data is saved to the U2000 database and you can query it from the database
by selecting Query from NMS next time.
Step 5 Optional: Click Graph. Select the Performance Event and Monitor Object in the dialog box.
Click Show to view the graphic result.
NOTE
After the resetting, the historical performance data is deleting and a new performance monitoring period
is beginning.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l For details on performance event types, see 8.1.1 Introduction to Performance Events.
l The service must be configured.
l The performance monitoring parameters must be set.
Context
The occurrence of ten consecutive severely errored seconds (SESs) indicates the UAT. The UAT
starts at the beginning of the ten seconds. The occurrence of ten consecutive non-SESs indicates
the end of the UAT and that the available time starts.
Procedure
Step 1 Navigation Path
l Choose Performance > Browse SDH Performance (traditional style) from the main menu
or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse SDH Performance (application style) from the main
menu. Select the UAT tab.
NOTE
l If you have set performance filter templates, click Filter by Template and choose Open from
the displayed menu. In the Open window, select a required template and click Open to import
the template.
l Some boards only support queries of current and historical performance data and do not support
queries of unavailable time (UAT) and performance threshold crossing events. In the
performance browsing window, selected objects in the Object Tree remain unchanged when you
switch between the Current Performance Data and History Performance Data tabs. However,
selected objects are cleared when you switch to or from the UAT or Performance Threshold-
Crossing Record tab.
l Choose Performance > Browse WDM Performance (traditional style) from the main
menu or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse WDM Performance (application style) from the main
menu. Select the UAT tab.
NOTE
l If you have set performance filter templates, click Filter by Template and choose Open from
the displayed menu. In the Open window, select a required template and click Open to import
the template.
l Some boards only support queries of current and historical performance data and do not support
queries of unavailable time (UAT) and performance threshold crossing events. In the
performance browsing window, selected objects in the Object Tree remain unchanged when you
switch between the Current Performance Data and History Performance Data tabs. However,
selected objects are cleared when you switch to or from the UAT or Performance Threshold-
Crossing Record tab.
l In the NE Explorer, select an NE, and navigate to the user interface of viewing the
performance data of boards or service objects in the following ways from the Function
Tree.
Step 2 Optional: Complete the following information: Monitored Object Filter Criteria, Display
Options, Data Source, Functional Block Type and start/end time. The information displayed
according to your selection.
NOTE
All function blocks supported by the board are provided as options for setting the function block.
After the resetting, the UAT performance data is deleting and a new performance monitoring period is
beginning.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l For details on performance event types, see 8.1.1 Introduction to Performance Events.
l The service must be configured.
l The performance monitoring parameters must be set.
Context
After you set the automatic reporting of the performance threshold crossing, if a performance
threshold crossing event is generated on the NE, the NE automatically reports the event to the
U2000.
You can set this parameter to monitor the performance events of certain objects.
NOTE
Disable this function if a large number of performance events may affect user operations by triggering
display of dialog boxes for confirmation.
Procedure
Step 1 Navigation Path
l Choose Performance > Browse SDH Performance (traditional style) from the main menu
or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse SDH Performance (application style) from the main
menu. Select the Performance Threshold-Crossing Record tab.
NOTE
l If you have set performance filter templates, click Filter by Template and choose Open from
the displayed menu. In the Open window, select a required template and click Open to import
the template.
l Some boards only support queries of current and historical performance data and do not support
queries of unavailable time (UAT) and performance threshold crossing events. In the
performance browsing window, selected objects in the Object Tree remain unchanged when you
switch between the Current Performance Data and History Performance Data tabs. However,
selected objects are cleared when you switch to or from the UAT or Performance Threshold-
Crossing Record tab.
l Choose Performance > Browse WDM Performance (traditional style) from the main
menu or select Fix-Network Performance in Application Center and choose Browse
Performance Data > Browse WDM Performance (application style) from the main
menu. Select the Performance Threshold-Crossing Record tab.
NOTE
l If you have set performance filter templates, click Filter by Template and choose Open from
the displayed menu. In the Open window, select a required template and click Open to import
the template.
l Some boards only support queries of current and historical performance data and do not support
queries of unavailable time (UAT) and performance threshold crossing events. In the
performance browsing window, selected objects in the Object Tree remain unchanged when you
switch between the Current Performance Data and History Performance Data tabs. However,
selected objects are cleared when you switch to or from the UAT or Performance Threshold-
Crossing Record tab.
l In the NE Explorer, select an NE, and navigate to the user interface of viewing the
performance data of boards or service objects in the following ways from the Function
Tree.
SDH, WDM, PTN, RTN Physical port Select the related board,
and Submarine equipment and then choose
Performance > UAT
Event.
Step 2 Optional: Complete the information: Monitored Object Filter Criteria, Monitor Period,
Display Options, Performance Event Type, and start/end time. The information displayed
according to your selection.
NOTE
All performance events supported by the board are provided as options for setting the performance event.
----End
Follow-up Procedure
If the number of performance events exceeds the threshold, dump some performance events and
clear the performance event threshold crossing alarm. The alarm will not be reported after alarm
synchronization.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the RTN series NEs.
l A microwave link must have been configured.
l The performance monitoring parameters must be set.
l NE time must be synchronized with the U2000 server time.
Procedure
l Browse the current performance data.
1. In the Main Topology, right-click a microwave link and choose Microwave Link
Performance Statistics, In the dialog box that is displayed, click the Current
Performance tab.
NOTE
If multiple microwave links exist between two NEs, you need to expand the microwave link
group before querying the microwave link performance statistics
The performance data of the NEs on the two ends of the microwave link is displayed
in a list.
2. Select Auto Refresh as required.
3. Optional: Click Save As. The performance data of the microwave link is saved.
l Browse the historical performance data.
1. In the Main Topology, right-click a microwave link and choose Microwave Link
Performance Statistics, In the dialog box that is displayed, click the Histroy
Performance tab.
NOTE
If multiple microwave links exist between two NEs, you need to expand the microwave link
group before querying the microwave link performance statistics
The performance data of the NEs on the two ends of the microwave link is displayed
in a list.
2. Set values of the Resolution, Period Time, and Display Format parameters.
NOTE
When Display Mode is set to Report, the historical performance data of the microwave link
is displayed in a table.
When Display Mode is set to Chart, the historical performance data of the microwave link is
displayed in a graph.
l When Link Tx/Rx Power is selected, the receive power and transmit power of the
microwave link are displayed in a graph. To display only the desired power parameters,
click Legend and select the desired parameters and change their colors in the dialog box
that is displayed.
l When Links Errors is selected, the bit error statistics of the microwave link are displayed
in a chart.
After the parameters are set, the performance data of the NEs on the two ends of the
microwave link is displayed in a list or chart.
3. Optional: Click Save As. The performance data of the microwave link is saved.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l The NE time must be synchronized with the U2000 server time.
l The performance monitoring time and the performance event monitor status of the NE must
be configured. For details, see 8.2.1.1 Setting Performance Monitoring Time of NE and
8.2.1.3 Setting the NE Performance Event Monitoring Parameters.
l For NEs that support the Ethernet feature and packet feature, the RMON performance
monitoring time and the RMON performance event monitor status of the NE must be
configured. For details, see 8.3.1.1 Setting the RMON Performance Monitoring
Parameters for NE and 8.3.1.2 Setting the RMON Performance Event Monitoring
Parameters.
Procedure
l Method 1
1. Choose Performance > NE Performance Collection (traditional style) from the main
menu or select Fix-Network Performance in Application Center and choose
Performance Monitoring > NE Performance Collection (application style) from
the main menu.
2. In the window that is displayed, click the NE tab.
3. Select the desired NEs from the navigation tree in the left pane and click .
4. Click Query.
5. Set the Enabled/Disabled for the NE, and click Apply.
6. Click the Collection Parameters tab.
7. Click Query.
8. Set the performance monitoring period and the period that the U2000 collects NE
performance data.
NOTE
The U2000 starts periodical collection task based on the collection period that you set. The
CSV files containing the exported performance data are saved to U2000 installation directory/
server/var/dump/PerfFileData/trans/data/ by default.
9. Click Select Performance Event. In the Set Performance Event Collection dialog
box that is displayed, set whether the performance event to be collected by the
U2000.
NOTE
l You can click the Performance or RMON Performance tab according to the NE features.
In the lower pane of the dialog box, double-click the Collection column on the right of a
performance event and select Enable or Disable from the drop-down list.
l In the upper pane of the dialog box, you can set Performance Event and Collection and
click Filter to query the collection status of the performance event.
10. In the Set Performance Event Collection dialog box, click Apply to save the
configuration. In the dialog box that is displayed, click Closed.
11. In the Set Performance Event Collection dialog box, click Closed.
12. In the Collection Parameters window, click Apply. In the dialog box that is
displayed, click Closed.
l Method 2
1. Choose Administration > Task Schedule > Task Management (traditional style)
from the main menu or select System Management in Application Center and
choose Task Schedule > Task Management (application style) from the main menu.
2. Click New.
3. In the New Task dialog box, enter the task name, select the Run Type, and select
Transfers NE Performance Collection And Export from the Task Type drop-down
list. Then, click Next.
4. Set the time and period.
– If Execution Type is One-time, set Start time and click Next.
– If Execution Type is Periodic, set Start time and Period, and click Next.
NOTE
l Performance data collection involves abundant data. It is recommended that you perform
the 15-minute performance collection every three days, 24-hour performance collection
every six days, at the time when network traffic is light.
l The time difference between two tasks must be longer than the execution duration of the
previous task. (The execution duration approximately equals 30s multiplies the number of
boards involved in the previous task.)
You can use the search function to quickly search out the desired NE or board.
7. Set Monitored Object Filter Criteria, Monitor Period, and Performance Event
Type. Then, click Next.
NOTE
For Performance Event Type, select items on the Gauge or Count tab or on both tabs.
8. Optional: Check the Export File check box and select the type of the performance
events that you want to export from Performance Event Type. Click Finish. A
scheduled task is successfully created.
NOTE
l For Performance Event Type, select items on the Gauge or Count tab or on both tabs.
l Path displays the relative path in the /server/var/dump/PerfLog directory and cannot be
modified.
l The file is exported in .txt format.
9. Optional: Double-click a scheduled task to modify the parameters of the task.
10. Optional: Right-click a scheduled task and choose Timely Suspend/Resume to set
the suspend time or the resume time for the task.
11. Optional: Right-click a scheduled task and choose Run At Once to start executing
the task.
NOTE
Run At Once means to immediately execute the task, no matter the scheduled time comes.
Resume means to start the scheduled task. The task is executed at the scheduled time.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 Choose Performance > Analyze History Performance Data (traditional style) from the main
menu or select Fix-Network Performance in Application Center and choose Analyze History
Performance Data > Analyze History Performance Data (application style) from the main
menu.
Step 2 In the Object Tree, select one module of a board and click .
Step 3 Complete the following information: Monitor Period, Display Mode and Time Range.
Step 5 Click Query to query the data on the NE or that stored in the U2000.
----End
Context
RMON is used to monitor and evaluate the communication quality of the ports that carry data
services. It is one network management standard that is widely applied. RMON contains
Statistics Group, History Group, History Control Group, and Alarm Group.
History Control Group You can set the historical control group to
modify the method that the port obtains the
statistics information of historical groups.
Alarm Group You can set the alarm group to monitor the
specified alarm variables such as port
statistics data. When the value of the
monitored data is beyond the defined
threshold, an alarm occurs. You can handle
the alarm based on the alarm definition.
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
Batch configuration of the RMON performance monitoring time is implemented mainly in new
deployment and expansion scenarios. If you need to adjust a single NE, set the RMON
performance monitoring time just for the NE.
Procedure
l Configure the RMON performance monitoring time for multiple NEs at a time.
1. Choose Performance > RMON History Control Group Management (traditional
style) from the main menu or select Fix-Network Performance in Application
Center and choose Performance Monitoring > RMON History Control Group
Management (application style) from the main menu.
4. Select desired NEs, set Enable to Enabled for 30-Sencond, 30-Minute, Custom
Period 1, and Custom Period 2, and set History Register Count.
NOTE
You can set Period Length only after enabling Custom Period1 or Custom Period2.
5. Click Apply and then click Close in the Operation Result dialog box.
l Configure the RMON performance monitoring time for a single NE.
1. Click the NE in the NE Explorer, and choose Performance > RMON History
Control Group from the Function tree.
2. Click Query to query the data from the NE.
3. Select desired NEs, set Enable to Enabled for 30-Sencond, 30-Minute, Custom
Period 1, and Custom Period 2, and set History Register Count.
NOTE
You can set Period Length only after enabling Custom Period1 or Custom Period2.
4. Click Apply.
5. Click OK in the Confirm dialog box. A prompt is displayed indicating that the
operation is successful.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
l Configure the RMON performance event monitoring status for multiple NEs at a time.
1. Choose Performance > Performance Template Management > Performance
Event Monitor Status Template (traditional style) from the main menu or select
When you customize the first RMON performance event monitoring status template, you can
set Template Name to Default Template only.
4. Optional: Click Refresh to refresh the information about the template.
5. According to the actual monitoring requirement, select a performance event and
changes the values of the corresponding monitor status parameters.
6. You can save the RMON performance event monitoring status template as follows:
– Click Save to directly save the modification.
NOTE
The default template cannot be directly saved. That is, the Save button is grayed out for
the default template.
– Alternatively, you can click Save As to save the template as a new template and
enter the name of the new template.
7. In the Operation Result dialog box, click Close.
8. Click Apply to. In the Apply to dialog box, select the objects that you apply the
template to and click OK. In the Operation Result dialog box, click Close to apply
the template to the selected objects in batches.
NOTE
You can also select several performance events, and set the status for time monitoring.
4. Click Apply. A dialog box is displayed to show the operation result.
5. Click Close.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Applies to the MSTP series, WDM series, RTN series, PTN series, submarine series NEs.
Procedure
Step 1 In the NE Explorer, select a board and choose Performance > Automatic RMON Performance
Data Reporting Settings from the Function Tree.
Step 2 Optional: Click Query to query the status of automatic reporting of performance events.
Step 3 Select a performance event, right-click and choose 15-Min Automatic Reporting Status from
the shortcut menu, to set the status of automatic reporting in the 15-minute interval.
Step 4 Select a performance event, right-click and choose 24-Hour Automatic Reporting Status from
the shortcut menu, to set the status of automatic reporting in the 24-hour interval.
Step 5 Click Apply. A prompt appears telling you that the operation was successful.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Performance Threshold
When an NE detects that a certain performance value is beyond the specified threshold, the NE
reports the corresponding performance threshold crossing event. The performance threshold can
divided into two types.
l Single threshold: When the performance count value reaches or exceeds the single
threshold, a performance threshold crossing event is generated on the NE. When the
performance count value is smaller than the single threshold, an event is generated on the
NE indicating that the performance threshold crossing ends.
l Double Thresholds: When the performance count value is beyond the range between the
upper and lower thresholds, a performance threshold crossing event is generated on the NE.
If the performance count value is in the range between the upper and lower thresholds, an
event is generated on the NE indicating that the performance threshold crossing ends.
NOTE
If you want to set a large number of performance threshold values, you can use the template that the
U2000 provides to customize the performance threshold values.
Procedure
l Configure the performance threshold for multiple NEs at a time.
1. Choose Performance > Performance Template Management > Performance
Threshold Template (traditional style) from the main menu or select Fix-Network
Performance in Application Center and choose Performance Monitoring >
Performance Template Management > Performance Threshold Template
(application style) from the main menu.
2. Navigation Path
– For an SDH/WDM NE: Select the SDH/WDM tab.
– For an SONET/WDM NE (NA): Select the SONET/WDM (NA) tab.
3. Select a template from the Template Name drop-down list.
NOTE
If a newly-created performance threshold template does not exist, you can only select the
Default Template.
4. Modify the performance thresholds as required.
NOTE
After the performance thresholds are changed, Apply to NEs is set to Yes automatically. If
you set Apply to NEs to No manually, this performance event will not be applied to NEs or
boards, and click refresh, the performance threshold value is set to the value in the default
template.
5. Save the template, and perform one of the following operations:
NOTE
l The threshold detect attribute cannot be set for all performance events. Whether the
threshold detect attribute can be set for all performance events depends on the equipment.
l According to the Threshold Detect status, a comparison is made between the performance
event and Upper Threshold or Lower Threshold to decide whether to report the
performance event.
5. Click Apply. A dialog box is displayed to show the operation result.
6. Click Close.
----End
Follow-up Procedure
You can view threshold-crossing records in the event logs.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l The Ethernet service must be configured.
l The performance monitoring parameters must be set.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 Select the NE in the NE Explorer. To display the performance browse interface for physical
ports or service objects, follow the listed entries in the Function Tree.
SDH, WDM, PTN, RTN and Physical port Select the board and choose
Submarine equipment Performance > RMON
Performance.
Step 4 Select the performance events. Set the Query Conditions and Display Mode.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l The Ethernet service must be configured.
l The performance monitoring parameters must be set.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
NOTE
Time zones are correctly set for the U2000 and involved NEs, and time is consistent between the U2000
and NEs.
Procedure
Step 1 Select the NE in the NE Explorer. To display the performance browse interface for physical
ports or service objects, follow the listed entries in the Function Tree.
SDH, WDM, PTN, RTN and Physical port Select the board and choose
Submarine equipment Performance > RMON
Performance.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Procedure
Step 1 In the NE Explorer, select an Ethernet board or an IF board and choose Performance > Ethernet
Port Flow Monitoring from the Function Tree. Click the Set Monitoring tab.
Step 2 Select a port and set the Flow Monitoring, Physical Bandwidth Monitoring and Bandwidth
Usage Monitoring.
NOTE
An Ethernet board can monitor the flow of up to 10 Ethernet ports, including IP ports and VC TRUNK
ports. That is, you can set Flow Monitoring to Enabled for up to 10 Ethernet ports on an Ethernet board.
Step 3 Click Apply. A dialog box is displayed indicating that the operation is successful. Click
Close.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
The corresponding monitoring status must be set to Enabled for the Ethernet port flow. For
details, see 8.4.1 Setting Ethernet Port Flow Monitoring.
Background Information
The NE collects the data every 15 minutes. An NE can collect the statistics on the flow data of
the Ethernet ports in the latest 30 days from now.
Procedure
Step 1 In the NE Explorer, select an Ethernet board or an IF board and choose Performance > Ethernet
Port Flow Monitoring from the Function Tree. Click the Query Flow tab.
Step 2 Select a port from the Monitored Object drop-down list. Then, set Start Time, End Time, and
Display Mode.
NOTE
l When Display Mode is set to List, the data of the Ethernet port flow is displayed as a list in the
U2000 user interface.
l When Display Mode is set to Graphics, the data of the Ethernet port flow is displayed as a graph in
the U2000 user interface.
Step 3 Click Query. The flow data on the port within the specific period is displayed.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the SDH series NEs.
l The ATM board must be installed.
l NE time is synchronized with the U2000 server.
Procedure
Step 1 In the NE Explorer, select an NE and choose Performance > ATM Performance Monitor
Period from the Function Tree to set the monitor period.
Step 2 Click Apply. The Operation Result dialog box is displayed.
Step 3 Click Close.
Step 4 In the NE Explorer, select an NE and choose Performance > ATM Performance Monitor
Time from the Function Tree.
Step 5 Specify the Monitor Period and select the Enabled option button in the Set Monitor Time
box.
NOTE
Three options of monitor period are available. They are 15-minute, 24-hour, and custom period. To set the
custom period, refer to Steps 1 through 3.
Step 6 Set the Start Time and End Time fields and click Apply.
Step 7 The Operation Result dialog box is displayed indicating that the operation was successful.
Step 9 In the NE Explorer, select an ATM board and choose Performance > ATM Performance Event
Monitor Status from the Function Tree.
Step 10 Set the monitored object in the Monitored Object Filter Criteria.
Step 11 Select a value in the 15-Minute Monitor, 24-Hour Monitor, Custom Period Monitor, 15-
Minute Auto-Report, 24-Hour Auto-Report and Custom Period Auto-Report fields.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 In the NE Explorer, select an ATM board and choose Performance > ATM Performance Real-
Time Monitor > Port Performance Data from the Function Tree.
Step 3 Complete the following information: Monitor Period, Monitor Interval (s) and Display
Number of Data Column.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 In the NE Explorer, select an ATM board and choose Performance > ATM History
Performance > Port Performance Data from the Function Tree.
Step 2 Complete the following information: Monitored Object, Query Period and time range.
Step 3 Click Query, and the information is displayed in the Query Result pane.
----End
Context
For the concept of lower order path performance, see 8.1.1 Introduction to Performance
Events.
Prerequisites
l You are an NMS user with "Maintenance Group" authority or higher.
l Applies to the N3SL64 and N4SL16 boards.
Procedure
Step 1 In the NE Explorer, select a board and select Configuration > Set TUG Structure from the
Function Tree.
Step 2 Set Direction to Receive, and set TUG3-1 Structure Type, TUG3-2 Structure Type and
TUG3-3 Structure Type to Not Configured, VC12 or VC3 as required.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 4 Select VC4 Path, right-click, and choose Lower Order Performance Management from the
shortcut menu.
Step 5 In the Lower Order Performance Management window, select Monitored Object and set
Monitor Status to Enabled.
Step 6 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 7 In the Lower Order Performance Management window, click the Performance Threshold-
Crossing Setting tab.
Step 8 Set the Monitor Status and Threshold-Crossing Enable Status of a performance event.
Step 9 Click Apply. Then, in the Operation Result dialog box, click Close.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" authority or higher.
l Applies to the N3SL64 and N4SL16 boards.
Procedure
Step 1 In the NE Explorer, select a board and select Configuration > Set TUG Structure from the
Function Tree.
Step 2 Set Direction to Receive, and set TUG3-1 Structure Type, TUG3-2 Structure Type and
TUG3-3 Structure Type to Not Configured, VC12 or VC3 as required.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 4 Select VC4 Path, right-click, and choose Lower Order Performance Management from the
shortcut menu.
Step 5 In the Lower Order Performance Management window, click the Performance Threshold-
Crossing Setting tab.
Step 7 Click Apply. Then, in the Operation Result dialog box, click Close.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" authority or higher.
l Applies to the N3SL64 and N4SL16 boards.
Procedure
Step 1 In the NE Explorer, select a board and select Configuration > Set TUG Structure from the
Function Tree.
Step 2 Set Direction to Receive, and set TUG3-1 Structure Type, TUG3-2 Structure Type and
TUG3-3 Structure Type to Not Configured, VC12 or VC3 as required.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 4 Select VC4 Path, right-click, and choose Lower Order Performance Management from the
shortcut menu.
Step 5 In the Lower Order Performance Management window, click the Current Performance tab.
Step 6 Select the Object, Monitor Period, and duration. Click Query to view the current lower order
performance data.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" authority or higher.
l Applies to the N3SL64 and N4SL16 boards.
Procedure
Step 1 In the NE Explorer, select a board and select Configuration > Set TUG Structure from the
Function Tree.
Step 2 Set Direction to Receive, and set TUG3-1 Structure Type, TUG3-2 Structure Type and
TUG3-3 Structure Type to Not Configured, VC12 or VC3 as required.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 4 Select VC4 Path, right-click, and choose Lower Order Performance Management from the
shortcut menu.
Step 5 In the Lower Order Performance Management window, click the History Performance tab.
Step 6 Select the Object, Monitor Period, Data Source and duration. Click Query to view the history
lower order performance data.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" authority or higher.
l Applies to the MSTP equipment.
l Applies to the N3SL64 and N4SL16 boards.
Procedure
Step 1 In the NE Explorer, select a board and select Configuration > Set TUG Structure from the
Function Tree.
Step 2 Set Direction to Receive, and set TUG3-1 Structure Type, TUG3-2 Structure Type and
TUG3-3 Structure Type to Not Configured, VC12 or VC3 as required.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 4 Select VC4 Path, right-click, and choose Lower Order Performance Management from the
shortcut menu.
Step 5 In the Lower Order Performance Management window, click the UAT tab.
Step 6 Select the Object, Options, Data Source and duration, and click Query to view the UAT
records.
----End
Prerequisites
l You are an NMS user with "Maintenance Group" authority or higher.
l Applies to the N3SL64 and N4SL16 boards.
Procedure
Step 1 In the NE Explorer, select a board and select Configuration > Set TUG Structure from the
Function Tree.
Step 2 Set Direction to Receive, and set TUG3-1 Structure Type, TUG3-2 Structure Type and
TUG3-3 Structure Type to Not Configured, VC12 or VC3 as required.
Step 3 Click Apply. Then, in the Operation Result dialog box, click Close.
Step 4 Select VC4 Path, right-click, and choose Lower Order Performance Management from the
shortcut menu.
Step 5 In the Lower Order Performance Management window, click the Performance Threshold-
Crossing Setting tab.
Step 6 Select the Object, Monitor Period, Options and duration. Click Query to view threshold
crossings.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the ET1 board of the OptiX 2500+ (Metro3000). The interface board must be
configured.
l NE time is synchronized with the U2000 server.
Procedure
Step 1 In the NE Explorer, select an NE and choose Performance > IP Performance Monitor
Period from the Function Tree to set the monitor period.
Step 4 In the NE Explorer, select an NE and choose Performance > IP Performance Monitor
Time from the Function Tree.
Step 7 Click Apply and the Operation Result dialog box is displayed.
Step 9 In the NE Explorer, select a board and choose Performance > IP Performance Event Monitor
Status from the Function Tree.
Step 10 In the Monitored Object Filter Criteria, set the monitor object.
Step 11 Set the Monitor Status, 30-Second Auto-Report, 30-Minute Auto-Report and Custom
Period Auto-Report fields.
Step 12 Click Apply. The Operation Result is displayed indicates that the operation was successful.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l The Ethernet service must be configured.
l The performance monitoring parameters must be set.
l Applies to the ET1 board of the OptiX 2500+ (Metro3000). The interface board must be
configured.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > IP Performance Real-
time Monitor from the Function Tree.
Step 3 Select a value from the Monitor Interval (s) and Display Number of Data Column drop-down
lists.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l The Ethernet service must be configured.
l The performance monitoring parameters must be set.
l Applies to the ET1 board of the OptiX 2500+ (Metro3000). The interface board must be
configured.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > IP History
Performance from the Function Tree.
Step 2 Complete the information: Monitored Object, Query Period, and Time Range.
----End
Context
Performance data is dumped to .txt files in the default or user-defined directory. The default
directory varies with OS as follows:
l If the Solaris-based U2000 server is used, the default path is /opt/oss/server/var/dump/
PerfLog.
l If the Windows-based U2000 server is used, the default path is \oss\server\var\dump
\PerfLog.
A maximum of 50 Ethernet performance indicators can be queried on the U2000. If more than
50 indicators are queried, wrapping occurs.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 2 In the navigation tree on the left of the Task Management window, choose Manual Dump.
Step 3 In the task list, double-click required Performance Event Manual Dump to check the task
attribute.
----End
Result
The manually dumped performance data is saved as a file in the specified directory, but not
displayed in the History Performance Data window.
NOTE
When the value of the performance data, including bit errors, is 0, services are normal and are not displayed
in the exported dumping data.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
You can use Overflow Dump or Periodic Dump to automatically dump the data.
l If you select the overflow dump mode, the U2000 automatically dumps some data to the
specified path when the data exceeds the threshold.
l If you select the periodic dump mode, the U2000 periodically dumps the data to the
specified path.
l Overflow dump and periodic dump can work together. In this case, the U2000 dumps the
data or log according to the settings of overflow dump and periodic dump.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 2 In the navigation tree on the left of the Task Management window, choose Database Capacity
Management.
Step 3 In the task list, double-click required Performance Event Period Dump.
Step 4 In the Attribute dialog box, modify common parameters and extended parameters.
----End
Result
The automatically dumped performance data is saved as a file in the specified directory, but not
displayed in the History Performance Data window.
NOTE
When the value of the performance data, including bit errors, is 0, services are normal and are not displayed
in the exported dumping data.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
You can use Overflow Dump or Periodic Dump to automatically dump the data.
l If you select the overflow dump mode, the U2000 automatically dumps some data to the
specified path when the data exceeds the threshold.
l If you select the periodic dump mode, the U2000 periodically dumps the data to the
specified path.
l Overflow dump and periodic dump can work together. In this case, the U2000 dumps the
data or log according to the settings of overflow dump and periodic dump.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 2 In the navigation tree on the left of the Task Management window, choose Overflow Dump.
Step 3 In the task list, double-click the task of Performance Event Overflow Dump.
Step 4 In the Attribute dialog box, modify common parameters and extended parameters.
----End
Result
The dumped performance data in the overflow way is saved as a file in the specified directory,
but not displayed in the History Performance Data window.
NOTE
When the value of the performance data, including bit errors, is 0, services are normal and are not displayed
in the exported dumping data.
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l The board must support the query of performance data.
l At least five days of performance data must be collected.
Procedure
Step 1 Choose Performance > Medium-Term and Long-Term Performance Forecast (traditional
style) from the main menu or select Fix-Network Performance in Application Center and
choose Analyze History Performance Data > Medium-Term and Long-Term Performance
Forecast (application style) from the main menu.
Step 2 In the Object Tree, select one module of a board, and click .
Step 3 Complete the information: Category of Forecast Basis and Forecast Input Conditions.
Step 4 Click Forecast. The results are shown under Forecast Output Value and the corresponding
diagram is displayed.
----End
Context
Based on the type of the performance register, you can reset the following performance registers:
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Procedure
Step 1 In the NE Explorer, select a board and choose Performance > Reset Board Performance
Register from the Function Tree.
Step 2 Select the ports and registers that you want to reset and click Reset.
Step 3 Click Yes in the confirmation dialog box. A prompt appears indicating that the operation is
successful.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l The ATM board must be configured.
Procedure
Step 1 In the NE Explorer, select an ATM board and choose Performance > Reset ATM Performance
Register from the Function Tree.
Step 2 Select the ports and registers that you want to reset and click Reset.
Step 3 Click Yes in the confirmation dialog box. A prompt appears indicating that the operation is
successful.
----End
Prerequisites
l You are an NMS user with "Operator Group" authority or higher.
l The ET1 board must be configured.
Procedure
Step 1 In the NE Explorer, select an Ethernet board and choose Performance > Reset IP Performance
Register from the Function Tree.
Step 2 Select the ports and registers that you want to reset and click Reset.
Step 3 Click Yes in the confirmation dialog box. A prompt appears indicating that the operation is
successful.
----End
NOTE
If the BER is very small (close to the smallest real number of the OS 1e-307) or very big (up to 0.15) while
the transmission system functions properly, the BER before the FEC is not displayed. In this case, no Q
factor is converted from BERs.
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Procedure
Step 1 In the NE Explore, select a board and choose Configuration > WDM Interface from the
Function Tree.
Step 2 Select the By Board/Port (Channel) option button. Select Channel from the drop-down list.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 Choose Performance > Browse WDM Performance (traditional style) from the main menu
or select Fix-Network Performance in Application Center and choose Browse Performance
Data > Browse WDM Performance (application style) from the main menu. Click the Current
Performance Data tab.
Step 2 In the Object Tree, select one or more boards, and click the double-right-arrow button (red).
Step 3 Complete the following information: Monitored Object Filter Criteria and Monitor Period.
Step 4 Click the Count tab. In the Performance Event Type group box, check the Other Errors
check box.
Step 5 Optional: In the Display Options group box, check the Display Zero Data or Display
Consecutive Severely Errored Seconds check box.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 Choose Performance > Browse WDM Performance (traditional style) from the main menu
or select Fix-Network Performance in Application Center and choose Browse Performance
Data > Browse WDM Performance (application style) from the main menu. Click the History
Performance Data tab.
Step 2 In the Object Tree, select one or more boards, and click the double-right-arrow button (red).
Step 3 Complete the following information: Monitored Object Filter Criteria, Monitor Period,
From: To: and Data Source.
Step 4 Click the Count tab. In the Performance Event Type group box, check the Other Errors check
box.
Step 5 Optional: In the Display Options group box, check the Display Zero Data check box.
Step 6 Click Query. Click Close in the Operation Result dialog box.
----End
9 Inventory Management
Inventory management covers network-wide physical resources and key logical configurations.
U2000 allows you to query or collect statistics on network resources so that carriers' service
planning and capacity expansion plans can be supported.
9.3 NE Management
With the NE management function, you can query, maintain, and collect statistics on NEs.
Specifically, you can learn the following information about the NEs on the live network: NE
types, NE quantity, quantity of equivalent NEs, and physical locations. Such information helps
you quickly ascertain the network condition in your area and work out service and capacity
expansion plans.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Telecommunications Room from
the Physical Inventory Type navigation tree.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The rack has been added to the Rack List window. For details, see 9.2.1 Creating a
Rack.
l The NMS has been added to the Main Topology.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Telecommunications Room from
the Physical Inventory Type navigation tree.
Step 2 Right-click on the Telecommunications Room List tab and choose Refresh from the shortcut
menu.
All the telecommunications room records are displayed in the query result area.
Step 3 Select a telecommunications room record, and click Install Racks/NMSs. Select the rack or the
NMS to be installed and click .
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Telecommunications Room from
the Physical Inventory Type navigation tree.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Telecommunications Room from
the Physical Inventory Type navigation tree.
Step 2 Right-click on the Telecommunications Room List tab and choose Refresh from the shortcut
menu.
All the telecommunications room records are displayed in the query result area.
Step 3 Select the telecommunications room to be modified and click Modify to modify the related
parameters.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Telecommunications Room from
the Physical Inventory Type navigation tree.
Step 2 Right-click on the Telecommunications Room List tab and choose Refresh from the shortcut
menu.
All the telecommunications room records are displayed in the query result area.
Step 3 Select the telecommunications room to be deleted and click Delete. The Confirm dialog box is
displayed.
Step 4 Click OK to return to the Telecommunications Room List tab.
----End
Result
When the telecommunications room is deleted, the racks or U2000s installed in the
telecommunications room are automatically uninstalled.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Telecommunications Room from
the Physical Inventory Type navigation tree.
Step 2 Right-click on the Telecommunications Room List tab and choose Refresh from the shortcut
menu.
All the telecommunications room records are displayed in the query result area.
Step 3 Select one or more telecommunications rooms and right-click it or them. Then, choose Set User
Label from the shortcut menu.
NOTE
When you set Customized Column for a record, click Next or Previous to set the next or previous record.
Then, click Apply.
Step 4 After configuration, click OK to return to the Telecommunications Room List tab.
Step 5 Optional: You can set the name of the column with an asterisk ( ) as required by performing
the following steps.
1. Right-click on the heading of the query result area and choose Column Settings from the
shortcut menu.
2. In the Column Settings dialog box, set the name of the column with an asterisk ( ) as
required.
3. Then, click OK.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Telecommunications Room from
the Physical Inventory Type navigation tree.
Step 2 Right-click on the Telecommunications Room List tab and choose Refresh from the shortcut
menu.
All the telecommunications room records are displayed in the query result area.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Telecommunications Room from
the Physical Inventory Type navigation tree.
Step 2 Click the Telecommunications Room Statistics tab. Then, select the statistics type from the
Statistics Type drop-down list box.
The telecommunications room records conforming to the statistics type are displayed in the
query result area.
NOTE
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 3 Optional: If there is no statistics type meeting the requirements in the drop-down list, perform
the following steps to customize a new statistics type:
1. Select Customize from the Statistics Type drop-down list box.
2. In the Customize Telecommunications Room Statistics Type dialog box, click New.
3. In the New Customize Telecommunications Room Statistics Type dialog box, set the
related parameters, and click OK.
4. In the Customize Telecommunications Room Statistics Type dialog box, click OK.
The information conforming to the customized statistics type of a telecommunications room
is displayed in the query result area.
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 5 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Rack from the Physical Inventory
Type navigation tree.
Step 2 On the Rack List tab, click New.
Step 3 In the New Rack dialog box, set related parameters.
NOTE
----End
Prerequisites
l Number of Shelves is set during the installation of a new rack.
l You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Rack from the Physical Inventory
Type navigation tree.
Step 2 Right-click on the Rack List tab and choose Refresh from the shortcut menu.
All the rack records are displayed in the query result area.
Step 3 Select the rack on which the subrack is to be installed. On the Subrack Information tab, right-
click a record, and then select Install Subrack on the shortcut menu.
Step 4 In the Install Subrack dialog box, select the subrack to be installed and click . The
subrack is displayed in Select Object. Then, click OK.
Step 5 In the Operation Result dialog box that is displayed, click Close.
The added subrack is displayed on the Subrack Information tab.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Rack from the Physical Inventory
Type navigation tree.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Rack from the Physical Inventory
Type navigation tree.
Step 2 Right-click on the Rack List tab and choose Refresh from the shortcut menu.
All the rack records are displayed in the query result area.
Step 3 Select the rack to be modified and click Modify to modify the related parameters.
Step 6 Optional: If a subrack is installed on the rack, right-click the subrack record on the Subrack
Information tab and choose Uninstall Subrack from the shortcut menu. In the Uninstall
Subrack dialog box, select the subracks to be uninstalled and click OK. In the Operation
Result dialog box, click Close.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Rack from the Physical Inventory
Type navigation tree.
Step 2 Right-click on the Rack List tab and choose Refresh from the shortcut menu.
All the rack records are displayed in the query result area.
Step 3 Select the rack record to be deleted, and then click Delete.
The Confirm dialog box is displayed, prompting you whether to delete the selected rack record.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Rack from the Physical Inventory
Type navigation tree.
Step 2 Right-click on the Rack List tab and choose Refresh from the shortcut menu.
All the rack records are displayed in the query result area.
Step 3 Select one or more racks and right-click it or them. Then, choose Set User Label from the
shortcut menu.
NOTE
When you set Customized Column for a record, click Next or Previous to set the next or previous record.
Then, click Apply.
Step 5 Optional: You can set the name of the column with an asterisk ( ) as required by performing
the following steps.
1. Right-click on the heading of the query result area and choose Column Settings from the
shortcut menu.
2. In the Column Settings dialog box, set the name of the column with an asterisk ( ) as
required.
3. Then, click OK.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Rack from the Physical Inventory
Type navigation tree.
Step 2 Right-click on the Rack List tab and choose Refresh from the shortcut menu.
All the rack records are displayed in the query result area.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Rack from the Physical Inventory
Type navigation tree.
Step 2 Click the Rack Statistic tab. Then, select the statistics type from the Statistics Type drop-down
list box.
The rack records in accordance with the statistics type are displayed in the query result area.
NOTE
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 3 Optional: If there is no statistics type meeting the requirements in the drop-down list, perform
the following steps to customize a new statistics type:
1. Select Customize from the Statistics Type drop-down list box.
2. In the Customize Rack Statistics Type dialog box, click New.
3. In the New Customize Rack Statistics Type dialog box, set related parameters, and click
OK.
4. In the Customize Rack Statistics Type dialog box, click OK.
The information about the rack statistics types, which meets the set conditions, is displayed
in the query result area.
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 5 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
9.3 NE Management
With the NE management function, you can query, maintain, and collect statistics on NEs.
Specifically, you can learn the following information about the NEs on the live network: NE
types, NE quantity, quantity of equivalent NEs, and physical locations. Such information helps
you quickly ascertain the network condition in your area and work out service and capacity
expansion plans.
Prerequisites
You are an NMS user with Guests authority or higher.
Context
Statistics collection on optical NEs is not supported.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose NE from the Physical Inventory
Type navigation tree.
The information queried through the preceding method is the information in the database. The
timeliness of data cannot be guaranteed. To query the real-time data of a record directly from NEs,
do as follows:
l If the selected NE does not support queries on the NE side, the Information dialog box is
displayed indicating that the selected record does not support queries on the NE side.
l If the selected NE supports queries on the NE side, the Result dialog box is displayed
indicating the operation results.
l To query the information about the specified NEs, click Filter, set the filter criteria, and
click OK. All records meeting the filter criteria are displayed in the query result area.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose NE from the Physical Inventory
Type navigation tree.
Step 2 Right-click on the NE List tab and choose Refresh from the shortcut menu.
All NE records are displayed in the query result area.
NOTE
The information queried through the preceding method is the information in the database. The timeliness
of data cannot be guaranteed. To query the real-time data of a record directly from NEs, do as follows:
1. Select a record and click Query.
2. In the dialog box that is displayed, select Query Range. Then, click OK.
NOTE
l If the selected NE does not support queries on the NE side, the Information dialog box is
displayed indicating that the selected record does not support queries on the NE side.
l If the selected NE supports queries on the NE side, the Result dialog box is displayed indicating
the operation results.
Step 3 Select one or more NEs and right-click it or them. Then, choose Set User Label from the shortcut
menu to set Remark and Customized Column.
NOTE
When you set Customized Column for a record, click Next or Previous to set the next or previous record.
Then, click Apply.
Step 5 Optional: You can set the name of the column with an asterisk ( ) as required by performing
the following steps.
1. Right-click on the heading of the query result area and choose Column Settings from the
shortcut menu.
2. In the Column Settings dialog box, set the name of the column with an asterisk ( ) as
required.
3. Then, click OK.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose NE from the Physical Inventory
Type navigation tree.
NOTE
Click Filter. In the dialog box that is displayed, specify the filter criteria to quickly display the required
NEs.
Step 2 Right-click on the NE List tab and choose Refresh from the shortcut menu.
All NE records are displayed in the query result area.
NOTE
The information queried through the preceding method is the information in the database. The timeliness
of data cannot be guaranteed. To query the real-time data of a record directly from NEs, do as follows:
1. Select a record and click Query.
2. In the dialog box that is displayed, select Query Range. Then, click OK.
NOTE
l If the selected NE does not support queries on the NE side, the Information dialog box is
displayed indicating that the selected record does not support queries on the NE side.
l If the selected NE supports queries on the NE side, the Result dialog box is displayed indicating
the operation results.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
You are an NMS user with Maintenance Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose NE from the Physical Inventory
Type navigation tree.
Step 2 Click the Statistics by NE tab or Statistics by Subnet tab. Select the NE type from the Statistics
Type drop-down list and set Statistics Scope.
The NE records in accordance with the statistics type are displayed in the query result area.
NOTE
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 3 Optional: If there is no statistics type meeting the requirements in the drop-down list, perform
the following steps to customize a new statistics type:
1. Select Customize from the Statistics Type drop-down list box.
2. In the Customize NE Statistics Type dialog box, click New.
3. In the New Customize NE Statistics Type dialog box, set related parameters, and click
OK.
4. In the Customize NE Statistics Type dialog box, click OK.
The information about the NE statistics types, which meets the set conditions, is displayed
in the query result area.
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 5 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Context
Equivalent NEs: Features, cross-connection capacities, and the number of boards, ports and
channels vary with NE types so that system resources required by NEs of different types are
different. Therefore, the management capacity of an U2000 is changeable with NE types. For
easy description and calculation of the management capability, the concept of equivalent NEs
is defined so that NEs or ports of different types can be converted to equivalent NEs by a uniform
criterion according to the system resources. The system resources required by an equivalent NE
are equal to the resources for managing an STM-1 transport NE.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose NE from the Physical Inventory
Type navigation tree.
Step 3 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 4 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Subrack from the Physical
Inventory Type navigation tree.
l To query the information about all subracks, right-click on the Subrack List tab and choose
Refresh from the shortcut menu. Alternatively, choose All Records from the drop-down
list in front of Filter. All the subrack records are displayed in the query result area.
l To query the information about the specified subracks, click Filter, set the filter criteria,
and click OK. All records meeting the filter criteria are displayed in the query result area.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Subrack from the Physical
Inventory Type navigation tree.
Step 2 Right-click on the Subrack List tab and choose Refresh from the shortcut menu.
All the subrack records are displayed in the query result area.
Step 3 Select one or more subracks and right-click it or them. Then, choose Set User Label from the
shortcut menu to set Remark and Customized Column.
NOTE
The following NEs do not support the remark setting function (the Remark parameter is invalid):
l MSTP series
l RTN series
l PTN series
l WDM series
l WDM (NA) series
l DMT series
When you set Customized Column for a record, click Next or Previous to set the next or previous record.
Then, click Apply.
Step 4 After the configuration is complete, click OK to return to the Subrack List tab.
Step 5 Optional: You can set the name of the column with an asterisk ( ) as required by performing
the following steps.
1. Right-click on the heading of the query result area and choose Column Settings from the
shortcut menu.
2. In the Column Settings dialog box, set the name of the column with an asterisk ( ) as
required.
3. Then, click OK.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Subrack from the Physical
Inventory Type navigation tree.
Step 2 Right-click on the Subrack List tab and choose Refresh from the shortcut menu.
All the subrack records are displayed in the query result area.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Subrack from the Physical
Inventory Type navigation tree.
Step 2 Click the Subrack Statistics tab. Select the subrack type from the Statistics Type drop-down
list and set Statistics Scope.
The subrack records in accordance with the statistics type are displayed in the query result area.
NOTE
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 3 Optional: If there is no statistics type meeting the requirements in the drop-down list, perform
the following steps to customize a new statistics type:
1. Select Customize from the Statistics Type drop-down list box.
2. In the Customize Subrack Statistics Type dialog box, click New.
3. In the New Customize Subrack Statistics Type dialog box, set related parameters, and
click OK.
4. In the Customize Subrack Statistics Type dialog box, click OK.
The information about the customized statistics type of the subrack is displayed in the query
result area.
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 5 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Board from the Physical Inventory
Type navigation tree.
l To query the information about all Boards, right-click on the Board List tab and choose
Refresh from the shortcut menu. Alternatively, choose All Records from the drop-down
list in front of Filter. All the records are displayed in the query result area, including various
board information.
NOTE
The information queried through the preceding method is the information in the database. The
timeliness of data cannot be guaranteed. To query the real-time data of a record, do as follows:
l If the selected board does not support queries on the NE side, the Information dialog box
is displayed, prompting that the selected record does not support queries on the NE side.
l If the selected board supports queries on the NE side, the Result dialog box is displayed,
prompting Operation succeeded or Operation succeeded partially or Operation
failed.
l To query the information about the specified boards, click Filter, set the filter criteria, and
click OK. All records meeting the filter criteria are displayed in the query result area.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Board from the Physical Inventory
Type navigation tree.
Step 2 Right-click on the Board List tab and choose Refresh from the shortcut menu.
All the board records are displayed in the query result area.
NOTE
The information queried through the preceding method is the information in the database. The timeliness
of data cannot be guaranteed. To query the real-time data of a record directly from NEs, do as follows:
1. Select a record and click Query.
2. In the dialog box that is displayed, select Query Range. Then, click OK.
NOTE
l If the selected board does not support queries on the NE side, the Information dialog box is
displayed indicating that the selected record does not support queries on the NE side.
l If the selected board supports queries on the NE side, the Result dialog box is displayed indicating
Operation succeeded or Operation succeeded partially or Operation failed.
Step 3 Select one or more boards and right-click it or them. Then choose Set User Label from the
shortcut menu to set Remark and Customized Column.
NOTE
When you set Customized Column for a record, click Next or Previous to set the next or previous record.
Then, click Apply.
Step 5 Optional: You can set the name of the column with an asterisk ( ) as required by performing
the following steps.
1. Right-click on the heading of the query result area and choose Column Settings from the
shortcut menu.
2. In the Column Settings dialog box, set the name of the column with an asterisk ( ) as
required.
3. Then, click OK.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Board from the Physical Inventory
Type navigation tree.
NOTE
Click Filter to set board filter criteria and quickly identify the board to be queried.
Step 2 Right-click on the Board List tab and choose Refresh from the shortcut menu.
All the board records are displayed in the query result area.
NOTE
The information queried through the preceding method is the information in the database. The timeliness
of data cannot be guaranteed. To query the real-time data of a record directly from NEs, do as follows:
1. Select a record and click Query.
2. In the dialog box that is displayed, select Query Range. Then, click OK.
NOTE
l If the selected board does not support queries on the NE side, the Information dialog box is
displayed indicating that the selected record does not support queries on the NE side.
l If the selected board supports queries on the NE side, the Result dialog box is displayed indicating
Operation succeeded or Operation succeeded partially or Operation failed.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Board from the Physical Inventory
Type navigation tree.
Step 2 Click the Statistics by NE tab or Statistics by Subnet tab. Select the board type from the
Statistics Type drop-down list and set Statistics Scope.
The board records in accordance with the statistics type are displayed in the query result area.
NOTE
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 3 Optional: If there is no statistics type meeting the requirements in the drop-down list, perform
the following steps to customize a new statistics type:
1. Select Customize from the Statistics Type drop-down list box.
2. In the Customize Board Statistics Type dialog box, click New.
3. In the New Customize Board Statistics Type dialog box, set related parameters, and then
click OK.
4. In the Customize Board Statistics Type dialog box, click OK.
Information in accordance with the customized board statistics types, is displayed in the
query result area.
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 5 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
NOTE
The subboard management applies to the Router series, Switch series, Security series, and PTN series
NEs.
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Subboard from the Physical
Inventory Type navigation tree.
Step 2 Query the subboard information.
l To query the information about all subboards, right-click on the Subboard List tab and
choose Refresh from the shortcut menu. Alternatively, choose All Records from the drop-
down list in front of Filter. All the records are displayed in the query result area.
NOTE
The information queried through the preceding method is the information in the database. The
timeliness of data cannot be guaranteed. To query the real-time data of a record, do as follows:
l If the selected subboard does not support queries on the NE side, the Prompt dialog box
is displayed, prompting that the selected record does not support queries on the NE side.
l If the selected subboard supports queries on the NE side, the Operation Result dialog box
is displayed, prompting Operation succeeded or Operation succeeded partially or
Operation failed.
l To query the information about the specified subboards, click Filter, set the filter criteria,
and click OK. All records meeting the filter criteria are displayed in the query result area.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Subboard from the Physical
Inventory Type navigation tree.
Step 2 Right-click on the Subboard List tab and choose Refresh from the shortcut menu.
All the records are displayed in the query result area.
NOTE
The information queried through the preceding method is the information in the database. The timeliness
of data cannot be guaranteed. To query the real-time data of a record directly from NEs, do as follows:
1. Select a record and click Query.
2. In the dialog box that is displayed, select Query Range. Then, click OK.
NOTE
l If the selected subboard does not support queries on the NE side, the Information dialog box is
displayed indicating that the selected record does not support queries on the NE side.
l If the selected subboard supports queries on the NE side, the Result dialog box is displayed
indicating Operation succeeded or Operation succeeded partially or Operation failed.
Step 3 Select one or more subboard records and right-click it or them. Then choose Set User Label
from the shortcut menu to set Remark and Customized Column.
NOTE
When you set Customized Column for a record, click Next or Previous to set the next or previous record.
Then, click Apply.
Step 5 Optional: You can set the name of the column with an asterisk ( ) as required by performing
the following steps.
1. Right-click on the heading of the query result area and choose Column Settings from the
shortcut menu.
2. In the Column Settings dialog box, set the name of the column with an asterisk ( ) as
required.
3. Then, click OK.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Subboard from the Physical
Inventory Type navigation tree.
Step 2 Right-click on the Subboard List tab and choose Refresh from the shortcut menu.
All the records are displayed in the query result area.
NOTE
The information queried through the preceding method is the information in the database. The timeliness
of data cannot be guaranteed. To query the real-time data of a record directly from NEs, do as follows:
1. Select a record and click Query.
2. In the dialog box that is displayed, select Query Range. Then, click OK.
NOTE
l If the selected subboard does not support queries on the NE side, the Information dialog box is
displayed indicating that the selected record does not support queries on the NE side.
l If the selected subboard supports queries on the NE side, the Result dialog box is displayed
indicating Operation succeeded or Operation succeeded partially or Operation failed.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Subboard from the Physical
Inventory Type navigation tree.
Step 2 Click the Subboard Statistics tab. Select the subboard type from the Statistics Type drop-down
list and set Statistics Scope.
The subboard records in accordance with the statistics type are displayed in the query result area.
NOTE
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 3 Optional: If there is no statistics type meeting the requirements in the drop-down list, perform
the following steps to customize a new statistics type:
1. Select Customize from the Statistics Type drop-down list box.
2. In the Customize Subboard Statistics Type dialog box, click New.
3. In the New Customize Subboard Statistics Type dialog box, set related parameters, and
then click OK.
4. In the Customize Subboard Statistics Type dialog box, click OK.
The information about the subboard statistics types, which meets the set conditions, is
displayed in the query result area.
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 5 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Port from the Physical Inventory
Type navigation tree.
On the Carrier Network Port tab, select All Records from the drop-down list. Alternatively,
click Filter. In the Filter dialog box, specify the filter criteria and click OK. The desired ports
will be displayed in a list.
For the access domain, select the desired Port Type on the Access Service Port tab. And then
select NE Type and select All from the Please input query condition drop-down list.
Alternatively, click Filter. In the Filter dialog box, specify the filter criteria and click OK. The
desired ports will be displayed in a list.
NOTE
Choose Physical Inventory Type > Optical/Electrical Module from the navigation tree. In the right pane,
click the Router and Switch Optical/Electrical Module List tab and verify that routers with optical/
electrical modules are displayed in the list. Choose Physical Inventory Type > Port from the navigation
tree. In the right pane, click the Carrier Network Port tab or Access Service Port tab (access domain).
Select the related port and click the Optical Module tab in the lower pane. You can view the details about
the optical/electrical module of the port.
For the Router series, Switch series, PTN 6900 series, Access series and Security NEs, double-click a
record on the Carrier Network Port tab or Access Service Port tab (access domain). The corresponding
NE Panel will be displayed.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Port from the Physical Inventory
Type navigation tree.
On the Carrier Network Port tab, select All Records from the drop-down list. Alternatively,
click Filter. In the Filter dialog box, specify the filter criteria and click OK. The desired ports
will be displayed in a list.
Step 3 Select one or more port records and right-click it or them. Then choose Set User Label from
the shortcut menu to set Remark and Customized Column.
NOTE
You cannot add remarks for ports on access domain and transport domain NEs.
Step 4 After the configuration is complete, click OK to return to the Carrier Network Port tab.
Step 5 Optional: You can set the name of the column with an asterisk ( ) as required by performing
the following steps.
1. Right-click on the heading of the query result area and choose Column Settings from the
shortcut menu.
2. In the Column Settings dialog box, set the name of the column with an asterisk ( ) as
required.
3. Then, click OK.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Port from the Physical Inventory
Type navigation tree.
Step 2 Specify the filter criteria to query specified ports.
On the Carrier Network Port tab, select All Records from the drop-down list. Alternatively,
click Filter. In the Filter dialog box, specify the filter criteria and click OK. The desired ports
will be displayed in a list.
For the access domain, select the desired Port Type on the Access Service Port tab. And then
select NE Type and select All from the Please input query condition drop-down list.
Alternatively, click Filter. In the Filter dialog box, specify the filter criteria and click OK. The
desired ports will be displayed in a list.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Port from the Physical Inventory
Type navigation tree.
Step 2 Click the Port Statistics tab, and set NE Object to collect statistics on ports of the selected NE.
The port statistics are displayed according to the port type in the query result area.
NOTE
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 3 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 4 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Optical/Electrical Module from
the Physical Inventory Type navigation tree.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Optical/Electrical Module from
the Physical Inventory Type navigation tree.
Step 2 On the Router and Switch Optical/Electrical Module List tab, right-click and choose
Refresh from the shortcut menu.
All optical/electrical modules are displayed in the query result area.
Step 3 Right-click an optical/electrical module record and choose Set Port User Label from the
shortcut menu. Then set Remarks and Custom Column.
Step 4 Click OK to return to the Router and Switch Optical/Electrical Module List tab.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Optical/Electrical Module from
the Physical Inventory Type navigation tree.
Step 2 On the Router and Switch Optical/Electrical Module List tab, right-click and choose
Refresh from the shortcut menu.
All optical/electrical module records are displayed in the query result area.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Optical/Electrical Module from
the Physical Inventory Type navigation tree.
Step 2 Click the Router and Switch Optical/Electrical Module Statistics tab. Select the optical/
electrical module type from the Statistics Type drop-down list and set Statistics Scope.
The optical/electrical module records in accordance with the statistics type are displayed in the
query result area.
NOTE
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 3 Optional: If there is no statistics type meeting the requirements in the drop-down list, perform
the following steps to customize a new statistics type:
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 5 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose Slot Usage Statistics from the
Physical Inventory Type navigation tree.
Step 3 Click Filter. In the dialog box that is displayed, select the required NE and click OK.
The information about the slots that match the NE is displayed in the query result area.
NOTE
When selecting an NE object, in the Select NE Object dialog box that is displayed, you can select the
check box to the left of the NE on which statistics are to be collected, or click and then set Content
and Search Mode in the Find Object dialog box.
When the operation is performed on multiple clients concurrently, click Count to update the real-time data
in the server database to the client interface.
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 5 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l This function applies only to access-domain NEs.
Procedure
Step 1 Choose Inventory > Physical Inventory (traditional style) from the main menu or select Fix-
Network NE Configuration in Application Center and choose Inventory > Physical
Inventory (application style) from the main menu. Choose ONU from the Physical Inventory
Type navigation tree.
Step 2 Click Filter. In the dialog box that is displayed, set the statistics scope and click OK.
ONU information within the statistics scope is displayed in the query result area.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Boards of each NE have been added on the U2000.
Context
l Two-fiber bidirectional links are created for NEs except WDM NEs.
l Normally, single-fiber unidirectional links are created for WDM NEs. Two-fiber
bidirectional links are created to connect to the SDH ports.
l Single-fiber bidirectional links are created to connect to a board where the single-fiber
bidirectional optical module is installed.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 Click Create, and the Bulk Create Fibers/Cables dialog box is displayed.
NOTE
The NEs adopt the two-fiber bidirectional mode to achieve bidirectional transmission. When the created
fiber connection is single-fiber unidirectional, you need to create another fiber connection in the other
direction.
Step 5 In the Result dialog box, view the operation results. Then, click Close.
Step 7 Click Cancel to complete the settings. The created fiber/cable connections are displayed in the
Fiber/Cable/Microwave Link Information list.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The links are displayed on the U2000. For details, see 9.13.3 Querying a Link.
l It is applicable to the RTN series, PTN series, Router series, Switch series and Security
NEs.
Context
You can create fibers/cables between the source and sink physical ports of IP and Layer 2 links.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 In the Fiber/Cable/Microwave Link Information area, right-click and choose Import Link
from the shortcut menu.
Step 3 In the Import Link dialog box, select one or multiple links by using the following method.
NOTE
Click Filter. In the Filter Link Condition dialog box, set filter criteria to display the desired links.
l Click : Add an available link in the Available Link area to the Selected Link area.
l Click : Add all available links in the Available Link area to the Selected Link area.
This operation applies to import in batches.
l Click : Move a selected link in the Selected Link area to the Available Link area.
l Click : Move all selected links in the Selected Link area to the Available Link area.
Step 4 Optional: For PTN/NE/ATN/CX/RTN series NEs, you can set whether to allot IP address
automatic on the ports of the fiber/cable when importing the fiber/cable.
l Enable or disable Automatically Allocate IP Address for one link at a time: Right-click
a link whose Automatically Allocate IP Address is available and choose Select or
Clear from the shortcut menu. Alternatively, select or clear the Automatically Allocate
IP Address check box directly.
l Enable or disable Automatically Allocate IP Address for all links at a time: Right-click
a link and choose Select All or Clear All from the shortcut menu. Alternatively, select or
clear the Select All check box in the lower right corner.
NOTE
If Automatically Allocate IP Address has not been enabled for the source and sink ports of fibers/cables
during import, you can open the Interface Information window in the NE Explorer to set port IP addresses.
Step 6 In the dialog box that prompts the success, click Close.
The imported links are displayed on the Fiber/Cable/Microwave Link Management tab.
----End
Follow-up Procedure
For RTN series NEs, because no real fiber exists, you need to perform the following operations
after the IP addresses of the ports at the two ends of a microwave link are automatically assigned:
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Information about all the fibers/cables/microwave links is displayed in the Fiber/Cable/
Microwave Link Management window.
Step 2 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
l By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
l After the records are saved, you can open the file directly on the U2000 client.
Step 3 Optional: You can set the print parameters as required by performing the following steps.
1. Click Print. Set Start row and End row. Click OK.
2. In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 Select one or multiple fibers/cables in the list and click Modify Fiber/Cable.
Step 3 In the Modify Fiber/Cable dialog box, set the Name, Length (km), Designed Attenuation
(EOL), Medium Type, Maintainer and Remarks of fibers/cables as required, and click OK.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The inventory management process InventoryDM is enabled before fibers/cables are
deleted. You can log in to the System Monitor client to check the running status of this
process.
Context
NOTICE
l The deletion of fibers/cables will lead to the deletion of related protection subnets, trails and
customer information. Exercise caution before you delete fibers/cables. You can export the
script of the entire network first to avoid deletion by mistake.
l The U2000 cannot delete automatically discovered links.
Procedure
l Delete the fibers/cables/microwave links between NEs.
1. Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave
Link Management (traditional style) from the main menu or select Bearer Network
Service Configuration in Application Center and choose Inventory > Fiber/Cable/
Microwave Link > Fiber/Cable/Microwave Link Management (application style)
from the main menu.
2. Right-click the desired fibers/cables/microwave links and choose Delete Fiber/
Cable from the shortcut menu. The Warning dialog box is displayed. Click OK to
delete the fibers/cables/microwave links.
3. In the Result dialog box, click Close.
l Delete the links between NEs.
1. Choose Inventory > Link Management (traditional style) from the main menu or
select Bearer Network Service Configuration in Application Center and choose
Inventory > Link Management (application style) from the main menu.
2. Right-click the desired link and choose Delete from the shortcut menu. The
Confirm dialog box is displayed. Click Yes to delete the link.
3. In the Result dialog box, click Close.
l Delete the connections between the U2000 and NEs.
1. In the Main Topology, right-click the desired connection and choose Delete from the
shortcut menu.
NOTE
The Ethernet Line or Serial Port Line connections are created between the U2000 and NEs.
2. The Confirm dialog box is displayed. Click Yes.
3. The Deletion Result dialog box is displayed indicating the deletion result. Click
Close.
----End
9.11.6 Setting the Line Shape and Width for New Fiber/Cable/
Microwave Link
You can set the default line shape and width for fibers, cables, and microwave links to be
displayed in the Main Topology.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l The preset default line shape and width take effect only on new fibers, cables, and
microwave links created in the Main Topology. Existing and upgraded fibers and cables
will remain unchanged.
l You can manually modify the line shape and width for existing and upgraded fibers/cables/
microwave links in the Main Topology or the Fiber/Cable/Microwave Link
Management window.
l After the default line shape and width for fibers, cables, and microwave links are set, the
refreshed Main Topology is available for all users logging in to the current U2000 server.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Default Line Shape and Width
Setting (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Default Line Shape and Width Setting (application style) from the main menu.
Step 2 In the Set Default Line Shape and Width for Fiber/Cable dialog box, set the line shape and
width for related link types.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l When creating fibers/cables/microwave links on the U2000, you cannot set the line shape
and width for them.
l The line shape and width for fibers/cables/microwave links are not displayed on the Fiber/
Cable/Microwave Link Management tab but take effect in the Main Topology.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 Optional: On the Fiber/Cable/Microwave Link Management tab, search for the desired
fibers/cables/microwave links.
1. On the Fiber/Cable/Microwave Link Management table, click Filter.
2. In the Set Fiber/Cable Browse Filter Criteria dialog box, set the filter criteria.
3. Click Filter.
4. In the Prompt dialog box, click OK.
The desired fibers/cables/microwave links are displayed in the query result area.
Step 3 In the fibers/cables/microwave links list, right-click Fiber/Cable/Microwave Link and choose
Set Line Shape and Width from the shortcut menu.
NOTE
l You can select one or more fibers/cables/microwave links and modify the line shape and width in
batches.
l The U2000 does not allow you to modify the line shape and width for a Fiber/Cable/Microwave
Link whose sink and source are in the same NE.
Step 4 In the Set Line Shape and Width dialog box, set the line shape and width.
You can check the line shape and width for fibers/cables/microwave links in the Main Topology.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 Optional: In the window that is displayed, set Filter to filter the fibers/cables/microwave
links information to be exported.
Step 3 Click Save As. Then, set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
Step 4 Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The NEs are MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
Context
Intermediate office is a device used to manage and schedule fibers on a metropolitan area network
(MAN). It has multiple pairs of fiber connection ports. Each pair of ports connects two fibers to
form a longer physical fiber connection. For transport NEs, a physical fiber connection can
consist of two or more fibers traversing one or more intermediate offices. Therefore, some fiber
connections have an intermediate office information list containing information about the fibers
that constitute the fiber connections.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 In the window that is displayed, click in the lower pane. The Intermediate Office
Information tab is displayed.
Step 3 In the Fiber/Cable/Microwave Link Information list, select the desired fiber/cable.
Step 4 In the Intermediate Office Information area, right-click in the blank area and choose Create
Intermediate Office. A new intermediate office is displayed. You can modify its settings.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, Marine series, RTN series
NEs.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 Right-click a fiber/cable in the Fiber/Cable/Microwave Link Information list and choose
Detect Link from the shortcut menu. A progress bar of the check is displayed.
Step 3 When the check is completed, the Result dialog box is displayed indicating the check result.
----End
Result
If the fibers/cable created on the U2000 are inconsistent with the actual fibers/cables on NEs,
you can recreate the fibers/cablesby performing the following operations.
l Method one: Right-click the fiber/cable and choose Delete Fiber/Cable From NM from
the shortcut menu to delete the inconsistent fiber/cable from U2000. Then, click Create to
create a fiber/cable by referring to 5.8.3 Creating Fiber/Cable Connections in Batches.
l Method two: See 5.8.2 Creating Fibers/Cables Automatically.
Prerequisites
l You are an NMS user with Guests authority or higher.
l The fiber/cable is added to the fiber/cable pipe.
l Applies to the Router series, Switch series, MSTP series, WDM series, WDM (NA) series,
RTN series, PTN series (except PTN 6900 series) and marine series NEs.
Context
A fiber/cable can belong to multiple fiber/cable pipes. Therefore, the information about all the
pipes to which the fiber/cable belongs are listed after the query.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 In the Fiber/Cable/Microwave Link Information pane, right-click a fiber/cable and choose
Query Fiber/Cable Pipe from the shortcut menu. The Fiber/Cable Pipe Management window
is displayed.
Step 3 In the Pipe Information pane, the information about all the pipes to which the fiber/cable
belongs are displayed.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 In the window that is displayed, right-click the Fiber/Cable/Microwave Link of which the related
alarms are to be queried and choose Browse Relevant Current Alarms or Browse Relevant
Historical Alarms from the shortcut menu. The Browse Current Alarms or Browse History
Alarms window is displayed.
Step 3 In the Browse Current Alarms or Browse History Alarms window, you can browse the current
or historical alarms of the Fiber/Cable/Microwave Link and query Details and Handling
Suggestions of the alarms.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable Pipe Management
(traditional style) from the main menu or select Bearer Network Service Configuration in
Application Center and choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable
Pipe Management (application style) from the main menu.
Step 2 Click Create in the Fiber/Cable Pipe Management window. In the Create Pipe dialog that is
displayed, set Name, Memo, and Creator for the fiber/cable pipe. Click OK.
After you create a fiber/cable pipe, you can view information about the new fiber/cable pipe in
the Pipe Information pane.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l The fiber/cable and fiber/cable pipe have been created.
Context
A fiber/cable pipe can contain multiple fibers/cables and a fiber/cable can belong to multiple
fiber/cable pipes. When the probability of simultaneous interruption of fibers/cables almost
reaches 100%, you can add those fibers/cables to the same fiber/cable pipe.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable/Microwave Link
Management (traditional style) from the main menu or select Bearer Network Service
Configuration in Application Center and choose Inventory > Fiber/Cable/Microwave
Link > Fiber/Cable/Microwave Link Management (application style) from the main menu.
Step 2 Right-click a fiber cable in the Fiber/Cable/Microwave Link Information pane and choose
Query Fiber/Cable Pipe from the shortcut menu. In the Fiber/Cable Pipe Management
window, click Query.
Step 3 In the pipe list, select the fiber/cable pipe that you want to add the fiber/cable to and then click
Add Fiber/Cable.
You can select multiple fibers/cables and then add them to a certain pipe at the same time.
Step 5 In the Pipe Information window displayed, select the pipe that you want to add the fiber/cable
to and then click OK.
NOTE
When selecting a pipe, you can set filter criteria to filter fiber/cable pipes. In the Pipe Information window,
click Filter. In the Filter Pipe window that is displayed, set the filter criteria and then click Filter.
Step 6 In the Operation Result dialog box that is displayed, click Close.
Step 7 Optional: In the Fiber/Cable Pipe Management window, click the pipe where the fiber/cable
is added in the Pipe Information list and then you can view the information about the fiber/
cable in the Fiber Information pane.
Step 8 Optional: When information about a fiber/cable pipe is changed, the platinum services are
affected. Therefore, you need to synchronize the platinum services.
1. To synchronize the platinum services, click Synchronize Platinum Service.
2. In the dialog box that is displayed, select the type of platinum service to be synchronized
and click OK.
3. In the Result dialog box displayed, click Close.
NOTE
The U2000 license that is used must support the platinum services.
If the platinum services are not synchronized before you close the Fiber/Cable Pipe Management window,
a prompt is displayed, asking you to synchronize the platinum services.
You can ensure that the platinum services are in the normal state only after you synchronize them.
Otherwise, the new platinum services may use incorrect pipe information.
----End
Prerequisites
l You are an NMS user with Guests authority or higher.
l A fiber/cable pipe has been created.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable Pipe Management
(traditional style) from the main menu or select Bearer Network Service Configuration in
Application Center and choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable
Pipe Management (application style) from the main menu.
Step 2 In the Pipe Information pane, you can view the information about all fiber/cable pipes.
Step 3 Select a fiber/cable pipe and then you can view information about the fibers/cables that are
contained in the pipe in the Fiber/Cable Information pane.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l A fiber/cable pipe exists.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable Pipe Management
(traditional style) from the main menu or select Bearer Network Service Configuration in
Application Center and choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable
Pipe Management (application style) from the main menu.
Step 2 In the Pipe Information pane, double-click Pipe Name and Pipe Memo of a pipe or right-click
them and choose Modify from the shortcut menu and modify them.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l A fiber/cable has been added to a fiber/cable pipe.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable Pipe Management
(traditional style) from the main menu or select Bearer Network Service Configuration in
Application Center and choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable
Pipe Management (application style) from the main menu.
Step 2 In the Pipe Information list, select a pipe. Then, fibers/cables contained in the pipe are displayed
in the Fiber/Cable Information pane.
Step 3 In the Fiber/Cable Information list, select the fiber/cable to be removed and then click Move
Fiber/Cable.
Step 4 Optional: When information about a fiber/cable pipe is changed, the platinum services are
affected. Therefore, you need to synchronize the platinum services.
1. To synchronize the platinum services, click Synchronize Platinum Service.
2. In the dialog box that is displayed, select the type of platinum service to be synchronized
and click OK.
3. In the Result dialog box displayed, click Close.
NOTE
The U2000 license that is used must support the platinum services.
If the platinum services are not synchronized before you close the Fiber/Cable Pipe Management window,
a prompt is displayed, asking you to synchronize the platinum services.
You can ensure that the platinum services are in the normal state only after you synchronize them.
Otherwise, the new platinum services may use incorrect pipe information.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l A fiber/cable pipe exists.
Context
NOTICE
When a fiber/cable pipe is deleted, the fibers/cables that are contained in the pipe are not deleted.
However, information about the fiber/cable pipe is changed. As a result, the platinum services
are affected and need to be synchronized.
Procedure
Step 1 Choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable Pipe Management
(traditional style) from the main menu or select Bearer Network Service Configuration in
Application Center and choose Inventory > Fiber/Cable/Microwave Link > Fiber/Cable
Pipe Management (application style) from the main menu.
Step 2 In the pipe information list, select the fiber/cable pipe to be deleted and then click Delete.
Step 3 Optional: When information about a fiber/cable pipe is changed, the platinum services are
affected. Therefore, you need to synchronize the platinum services.
1. To synchronize the platinum services, click Synchronize Platinum Service.
2. In the dialog box that is displayed, select the type of platinum service to be synchronized
and click OK.
3. In the Result dialog box displayed, click Close.
NOTE
The U2000 license that is used must support the platinum services.
If the platinum services are not synchronized before you close the Fiber/Cable Pipe Management window,
a prompt is displayed, asking you to synchronize the platinum services.
You can ensure that the platinum services are in the normal state only after you synchronize them.
Otherwise, the new platinum services may use incorrect pipe information.
----End
NOTE
This function applies to Router series, Switch series, PTN 6900 series, Access series and Security NEs.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Link Management (traditional style) from the main menu or select Bearer
Network Service Configuration in Application Center and choose Inventory > Link
Management (application style) from the main menu.
Step 2 In the Link Management window, right-click in the query result area and choose Synchronize
Trunk Link from the shortcut menu.
Step 3 View the synchronization result (successful or failed) in the dialog box that is displayed.
l If Operation succeeded is displayed, click Close. The synchronized trunk links are displayed
in the physical view.
l If Operation failed is displayed, the failure cause is displayed.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l This operation is applicable to the Router series, Switch series and Security NEs, and also
applicable to the SSP series NEs, third-party series NEs, Hybrid MSTP NE, OSN 500/550
NE, RTN series, NG WDM NEs, and PTN series NEs. You can also create links between
cross-domain NEs, for example, RTN 600 series or RTN 900 series NEs and CX 600 series
NEs, or RTN 900 series NEs and PTN 3900 series NEs.
Procedure
Step 1 Choose Inventory > Link Management (traditional style) from the main menu or select Bearer
Network Service Configuration in Application Center and choose Inventory > Link
Management (application style) from the main menu.
Alternatively, right-click in the query area and choose New from the shortcut menu.
Step 3 In the Create Link dialog box, click New, set Link Type and Network Protocol Type, and
specify Source NE, Source Port, Sink NE, and Sink Port.
NOTE
l Network Protocol Type can be set only when Link Type is set to IP Link or L2 Link.
l After you specify Source NE, Source Port, Sink NE and Sink Port, a name is created automatically
in the Link Name text box. You can rename the link according to your naming habits.
l When specify the Source NE or Sink NE, you can select the NE from the drop-down list box directly,
and you can also enter a keyword and select a value from the fuzzy-matched keyword list.
l In the Select Port dialog box, set the filter mode, such as Port Name, Port IP, and Port Alias to search
for source or sink ports. Then select the desired source or sink port from the search result.
Step 5 Click Apply. In the Operation Result dialog box containing Operation succeeded, click
Close.
The created link is displayed in the query result area of link management.
NOTE
If a fault occurs during the link creation, the cause is displayed in the Operation Result dialog box. You
can rectify the fault based on the cause.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Context
The U2000 refreshes link status based on the source and sink port status of links.
Procedure
Step 1 Choose Inventory > Link Management (traditional style) from the main menu or select Bearer
Network Service Configuration in Application Center and choose Inventory > Link
Management (application style) from the main menu.
Step 2 On the Link Management tab, click Filter to set filter criteria.
Link information meeting the query conditions is displayed in the query result area.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Link Management (traditional style) from the main menu or select Bearer
Network Service Configuration in Application Center and choose Inventory > Link
Management (application style) from the main menu.
Step 2 On the Link Management tab, click Filter to set filter criteria.
Link information meeting the query conditions is displayed in the query result area.
Step 4 Select a link in the link list and right-click it. Then, select View Alarm.
Step 5 In the Browse Current Alarms window, check the alarms of NEs related to the link, including
Details and Handing Suggestions.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
Reverting the source and sink NEs of a link does not affect services on the link.
The U2000 cannot automatically identify source and sink NEs of a link after searching them out
from the NEs so that users cannot determine the status of NEs at both ends of the link. This
feature allows you to revert the source and sink NEs of the link on the U2000 according to the
actual NE status.
Procedure
Step 1 Choose Inventory > Link Management (traditional style) from the main menu or select Bearer
Network Service Configuration in Application Center and choose Inventory > Link
Management (application style) from the main menu.
Step 2 On the Link Management tab, click Filter to set filter criteria.
All the link information meeting the query conditions is displayed in the query result area.
Step 4 In the link information list, right-click a record and choose Revert from the shortcut menu.
NOTE
You can select one or more links and revert it or them in batches.
The source and sink NEs of a link are reverted on the U2000.
The Result dialog box is displayed, displaying Operation succeeded.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l When creating a link on the U2000, you are not allowed to set the line shape and width for
the link.
l The line shape and width for a link are not displayed on the Link Management tab but
take effect in the Main Topology.
Procedure
Step 1 Choose Inventory > Link Management (traditional style) from the main menu or select Bearer
Network Service Configuration in Application Center and choose Inventory > Link
Management (application style) from the main menu.
Step 2 On the Link Management tab, click Filter to set filter criteria.
Step 3 Click OK.
Link information meeting the query conditions is displayed in the query result area.
Step 4 In the link list, right-click a link and choose Set Line Shape and Width from the shortcut menu.
NOTE
You can select one or more links and modify its or their line shape and width in batches.
Step 5 In the Set Link Line dialog box, set the line shape and width for a link.
Step 6 Click OK.
Step 7 Click Close in the Result dialog box.
You can check the line shape and width of a link in the Main Topology. If the link is not displayed
in the line shape and width in the Main Topology, right-click the link and choose Expand
Link from the shortcut menu. Then, view the line shape and width of the link.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > LinkGroup Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Inventory >
LinkGroup Management (application style) from the main menu.
Step 2 Right-click in the Link View group box and select Create Link View.
Step 3 In the Create Link View dialog box, set Name and Description.
Step 4 Click OK.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l You must create a link view before creating a link group. For detailed operations, see 9.13.7
Creating a Link View.
Procedure
Step 1 Choose Inventory > LinkGroup Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Inventory >
LinkGroup Management (application style) from the main menu.
Step 2 In the Link View group box, select the link view in which the link group is to be created.
Step 3 Right-click in the Link Group box. Select Create Link Group.
Step 4 In the Create Link Group dialog box, set Name and Description.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l A link has been created. For details about how to create a link, see 9.13.2 Creating a
Link.
Context
Only the links in the physical view can be imported.
Procedure
Step 1 Choose Inventory > LinkGroup Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Inventory >
LinkGroup Management (application style) from the main menu.
Step 2 In the Link View area, select a link view containing the link group to which a link is to be added.
Information about the link group contained in this link view is displayed in the Link Group
area.
Step 3 In the Link Group area, select a link group where a link will be added.
Step 4 Right-click in the Link area, and then choose Import Link from the shortcut menu.
Step 5 In the Import Link dialog box that is displayed, set query conditions, and then click OK.
Step 6 Select one or more links you want to import to the link group. Click OK to start the importing.
If an imported link is displayed in the query result area of Link, the link is successfully added
to the link group.
Step 7 Optional: In the Link area, click Export and set Start row, End row, and File name.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in the
U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
After the records are saved, you can open the file directly on the U2000 client.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Context
Interface resources include port resources. Therefore, all port resources are displayed when you
query interface resources.
Procedure
Step 1 Choose Inventory > Router/Switch Interface (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Router/
Switch Interface (application style) from the main menu.
Step 2 In the Confirm dialog box, determine whether to start synchronizing router or switch interface
inventories.
l If you are using the function for the first time or want to view latest interface inventory
information, synchronize router or switch interface inventories at once and click OK. A
dialog box is displayed, indicating the synchronization progress. After a while, the
Step 3 To query specified router or switch interfaces, click Filter on the Router/Switch Interface tab,
set filter criteria, and click OK.
All records meeting the filter criteria are displayed in the query result area.
Step 4 Optional: The heading of the query result area supports the customization function. Concerned
parameters can be displayed as required. There are two customization methods:
Method one:
l Right-click on the heading of the query result area and choose Customize from the shortcut
menu.
l In the Customize Column dialog box that is displayed, select the check boxes of the
parameters to be displayed.
l Click OK.
Method two: Right-click on the heading of the query result area and select the parameters to be
displayed.
NOTE
Through method one, all the concerned parameters can be selected once. Through method two, only one
parameter can be selected after each right click.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Procedure
Step 1 Choose Inventory > Router/Switch Interface (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Router/
Switch Interface (application style) from the main menu.
Step 2 In the Confirm dialog box, determine whether to start synchronizing router or switch interface
inventories.
l If you are using the function for the first time or want to view latest interface inventory
information, synchronize router or switch interface inventories at once and click OK. A
dialog box is displayed, indicating the synchronization progress. After a while, the
synchronization result is displayed. Click Close. The Router/Switch Interface tab is
displayed.
l If this function has been used and the network interface data does not change frequently, you
can choose not to synchronize router or switch interface inventories at once, and click
Cancel. The system returns to the Router/Switch Interface tab.
Step 3 To query specified router or switch interfaces, click Filter on the Router/Switch Interface tab,
set filter criteria, and click OK.
All records meeting the filter criteria are displayed in the query result area.
Step 4 In the query result area, right-click an interface record and choose Set Remark from the shortcut
menu to set Remark.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Router/Switch Interface (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Router/
Switch Interface (application style) from the main menu.
Step 2 In the Confirm dialog box, determine whether to start synchronizing router or switch interface
inventories.
l If you are using the function for the first time or want to view latest interface inventory
information, synchronize router or switch interface inventories at once and click OK. A
dialog box is displayed, indicating the synchronization progress. After a while, the
synchronization result is displayed. Click Close. The Router/Switch Interface tab is
displayed.
l If this function has been used and the network interface data does not change frequently, you
can choose not to synchronize router or switch interface inventories at once, and click
Cancel. The system returns to the Router/Switch Interface tab.
Step 3 To query specified router or switch interfaces, click Filter on the Router/Switch Interface tab,
set filter criteria, and click OK.
All records meeting the filter criteria are displayed in the query result area.
NOTE
By default, the selected records are saved to an .xls, .txt, .html, or .csv file in client\client\report in
the U2000 installation folder. If necessary, change the saving path in the Saving Options dialog box.
2. Click OK. In the dialog box that is displayed, you can choose to open or not open the file.
l Click Yes to open the file.
l If you do not want to open the file, click No.
----End
Prerequisites
You are an NMS user with Guests authority or higher.
Procedure
Step 1 Choose Inventory > Access Service Statistics (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Access
Service Statistics (application style) from the main menu.
Step 2 On the tab that is displayed, choose All, Statistical Type, or Statistical Status from the
navigation tree to display the required records.
Step 3 In the access service statistics list, select a record and click the Statistics tab in the lower pane.
On the Statistics tab, click the link to the generated file to view the details of the task.
NOTE
You can view the link to the generated file on the Statistics tab only when Statistical Status is
Complete.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
Task Name automatically varies with Statistical Type or can be customized.
Procedure
Step 1 Choose Inventory > Access Service Statistics (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Access
Service Statistics (application style) from the main menu.
Step 2 On the tab that is displayed, right-click in the access service statistics list and choose Create
from the shortcut menu.
If you do not set Start at, an immediate statistics collection task is created and run automatically. In this
case, you do not need to manually start the task.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
You cannot modify a statistics collection task when Statistical Status is Unstarted, Waiting,
or In Process.
Procedure
Step 1 Choose Inventory > Access Service Statistics (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Access
Service Statistics (application style) from the main menu.
Step 2 On the tab that is displayed, right-click a record in the access service statistics list and choose
Modify from the shortcut menu.
Step 3 In the dialog box that is displayed, modify Task Name or Start at.
----End
Prerequisites
You are an NMS user with Maintenance Group authority or higher.
Context
l You cannot delete a statistics collection task when Statistical Status is Unstarted,
Waiting, or In Process.
l You can delete port statistics collection tasks in batches.
Procedure
Step 1 Choose Inventory > Access Service Statistics (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Access
Service Statistics (application style) from the main menu.
Step 2 On the tab that is displayed, right-click a record in the access service statistics list and choose
Delete from the shortcut menu.
Step 3 In the confirmation dialog box, click Yes.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l If the Start at parameter is set for a port statistics collection task, the task runs
automatically. In this case, you cannot manually start the task.
l In addition, you cannot start a statistics collection task when Statistical Status is In
Process or Waiting.
l You can start port statistics collection tasks in batches.
Procedure
Step 1 Choose Inventory > Access Service Statistics (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Access
Service Statistics (application style) from the main menu.
Step 2 On the tab that is displayed, right-click a record in the access service statistics list and choose
Start from the shortcut menu.
Step 3 In the confirmation dialog box, click Yes.
----End
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l You cannot stop a statistics collection task when Statistical Status is Stop or Complete.
l You can stop port statistics collection tasks in batches.
Procedure
Step 1 Choose Inventory > Access Service Statistics (traditional style) from the main menu or select
Fix-Network NE Configuration in Application Center and choose Inventory > Access
Service Statistics (application style) from the main menu.
Step 2 On the tab that is displayed, right-click a record in the access service statistics list and choose
Stop from the shortcut menu.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Before exporting the CEAS script files, you must check configuration data to ensure that
configuration data on the U2000 is consistent with that on NEs.
Context
With the increase of NEs on existing networks, the lack of electronic labels will lead to difficult
NE maintenance and management and rising costs.
An electronic label is the unique traceable identifier of a board throughout the lifecycle. With
electronic labels, you can perform the following operations:
l Operation and maintenance engineers can obtain board manufacturer information such as
the production date and place, software version information, and hardware version
information through the U2000 or remote STelnet NEs.
l Maintenance engineers can learn the board source and destination, whether the board has
been back to fix, and the current version, which facilitates board maintenance, management,
and tracing and reduces maintenance and management costs throughout the lifecycle.
Procedure
l Method 1
NOTE
This method applies to MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
1. Choose Administration > Back Up/Restore NMS Data > Import/Export Script
File (traditional style) from the main menu or select System Management in
Application Center and choose System > Back Up/Restore NMS Data > Import/
Export Script File (application style) from the main menu.
2. Set the format of the exported script file as TXT.
3. Select CEAS as the script file type from the Script File Type drop-down list.
4. Set the script file to the Export form.
5. In Export NE List, select the NEs where you want to export script files.
6. In Operation Directory List, specify the directory where you want to save the
exported script files.
NOTE
You can select a subdirectory in the default directory. You can also create a subdirectory.
To create a subdirectory, do as follows: Click Create File Directory. In the Input dialog box,
enter the name of the new subdirectory. Click OK.
7. Click Apply. The Confirm dialog box is displayed, indicating "Exporting will
overwrite all the script files that were previously exported. Are you sure to
continue?" You can choose whether to continue the export operation as required.
8. Click OK. A progress bar is displayed.
After the export operation is complete, the Operation Result dialog box is displayed
indicating the successful exporting operation and the directory where the exported
files are saved. You can view the exported script files in the preceding directory.
NOTE
The script file is saved on the U2000 server. On Windows, the backup directory is %
IMAP_ROOT%\script. On Solaris and SUSE Linux, the backup directory is
$IMAP_ROOT/script. You can create a subdirectory under the backup directory.
9. Click Close in the Operation Result dialog box.
l Method 2
NOTE
This method applies to Router series, Switch series, PTN 6900 series, Access series and Security
NEs.
1. Choose Inventory > Project Document > Export Electronic Label (traditional
style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > Project Document > Export Electronic Label
(application style) from the main menu.
2. In the Export Electronic Label dialog box, enter the file name according to the
prompts.
3. In the Export Electronic Label dialog box, click Select the export NE.
4. In the Select the export NE dialog box, select the objects where you want to export
electronic labels.
NOTE
l To select all NEs, select Export electronic label files of all NEs.
l To select a specific NE, clear Export electronic label files of all NEs and select the
required objects in the Navigation Tree.
5. In the Select the export NE dialog box, click OK.
6. In the Export Electronic Label dialog box, click OK.
After the electronic labels of the NEs are exported, a dialog box is displayed indicating
the directory where the exported electronic label files are saved.
NOTE
You can view exported electronic label files in the electronic label exporting path.
l On Windows, the electronic label exporting path is %IMAP_ROOT%\var\projdoc
\dump.
l On Solaris and Linux, the electronic label exporting path is $IMAP_ROOT/var/projdoc/
dump.
7. In the Confirm dialog box, click OK.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 Choose Inventory > SDH Report > Port Resource Report (traditional style) from the main
menu or select Fix-Network NE Configuration in Application Center and choose
Inventory > SDH Report > Port Resource Report (application style) from the main menu.
Step 2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red). In the
right-hand pane, view the generated report.
Step 3 Optional: Click Alarm Threshold Settings. In the Alarm Threshold Settings dialog box, you
can set parameters as required.
NOTE
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l Lower order cross-connections must be created.
Procedure
Step 1 Choose Inventory > SDH Report > Lower Order Cross-Connections Statistic Report
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > SDH Report > Lower Order Cross-Connections Statistic
Report (application style) from the main menu.
Step 2 In the Object Tree on the left, select one or more NEs and click the double-right-arrow button
(red). On the right, you can view the lower order cross-connection statistics report of the selected
NE queried from the U2000.
NOTE
Only NEs that support lower order cross-connection querying are displayed in the Object Tree.
Step 3 Click Alarm Threshold Settings, you can view or modify the threshold value. If the lower order
cross-connections occupancy reaches a specified threshold, a pre-alarm at different levels is
generated.
NOTE
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Context
You can schedule a timing task for automatic statistics collection. For details, see 9.17.8
Creating a Timing Task for Collecting Statistics on SDH Resources.
Procedure
Step 1 Choose Inventory > SDH Report > Statistics Report of SDH Tributary Port Resources
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > SDH Report > Statistics Report of SDH Tributary Port
Resources (application style) from the main menu.
Step 2 In the Object Tree in the left pane, select one or more NEs for statistics and click . In
the right pane, the details of the tributary port resources of the selected NEs is displayed.
NOTE
In the upper area, you can view the port resources. In the lower area, you can view the trails carried by these
ports.
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Context
You can schedule a timing task for automatic statistics collection. For details, see 9.17.8
Creating a Timing Task for Collecting Statistics on SDH Resources.
Procedure
Step 1 Choose Inventory > SDH Report > Statistics Report of Trails Between SDH NEs (traditional
style) from the main menu or select Fix-Network NE Configuration in Application Center
and choose Inventory > SDH Report > Statistics Report of Trails Between SDH NEs
(application style) from the main menu.
Step 2 In the Object Tree in the left pane, select one or more NEs for statistics and click . In
the right pane, the detailed information of the trail resources between NEs is displayed.
Step 3 Optional: Click Statistics Condition. In the Statistics Condition dialog box that is displayed,
set the level of the desired trails.
----End
Prerequisites
l You are an NMS user with "Guests" user group authority or higher.
l The protection subnet must exist.
Procedure
Step 1 Choose Inventory > SDH Report > Statistics Report of SDH Protection Subnet
Resources (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Inventory > SDH Report > Statistics Report of SDH
Protection Subnet Resources (application style) from the main menu.
Step 2 In the Filter window, select the protection subnet type and click Filter.
Step 3 In the Statistics Report of SDH Protection Subnet Resource window, view the resources of
the qualified protection subnets.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Context
l They can be counted in the following two ways:
Procedure
Step 1 Choose Inventory > SDH Report > Statistics Report of SDH Circuit Resources (traditional
style) from the main menu or select Fix-Network NE Configuration in Application Center
and choose Inventory > SDH Report > Statistics Report of SDH Circuit Resources
(application style) from the main menu.
Step 2 Click the Statistics by Subnet or Statistics by Customer tab in the left-hand pane.
Step 3 In the Object Tree, select one or more objects and click . You can view the generated
report in the right-hand pane.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Context
l You can schedule a timing task for automatic statistics collection. For details, see 9.17.8
Creating a Timing Task for Collecting Statistics on SDH Resources.
l ASON services are not included in this resource statistics.
Procedure
Step 1 Choose Inventory > SDH Report > SDH Fiber/Microwave Link Resource Usage Report
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > SDH Report > SDH Fiber/Microwave Link Resource Usage
Report (application style) from the main menu.
Step 3 Optional: Select Contain discrete service, you can view the information of the discrete services
in the Port Resource Report resource usage report.
Step 4 Select one or more objects from the Object Tree, and then click . The occupancy of the
relevant fiber/cable resource is displayed on the right side.
Step 5 Optional: Click Filter and set the filtering criteria to display the required information in the
fiber/cable resource usage report.
Step 6 Optional: Click Alarm Threshold Settings, you can view or modify the threshold value. If the
fiber cable resource occupancy reaches a specified threshold, a pre-alarm at different levels is
generated.
NOTE
----End
Context
l The items for timing statistics include fiber cable occupancy resources, SDH trail statistics
between NEs, and TU port resource statistics.
l ASON services are not included in this resource statistics.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 2 Click SDH Resource Statistic in Task Type in the pane on the left.
Step 4 In the displayed dialog box, enter a name for the Task Name field.
When you set Run Type to Period, you need to specify the period for running the task. When you set Run
Type to Once, you can select the Run At Once to immediately run the task and the setting of a period is
not required.
Step 7 Select Report file type, File type, and Storage path on server.
Step 8 Select Statistic by Affiliated Subnet or Statistic by protection Subnet, and select the object
in the below tab.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 Choose Inventory > Microwave Report > Microwave License Capacity Report (traditional
style) from the main menu or select Fix-Network NE Configuration in Application Center
and choose Inventory > Microwave Report > Microwave License Capacity Report
(application style) from the main menu.
Step 2 Select NEs from the Object Tree, and then click the double-right-arrow button (red). The
information of the microwave license capacity is displayed on the right side.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
l Manually collect statistics on microwave links.
1. Choose Inventory > Microwave Report > Microwave Link Report (traditional
style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > Microwave Report > Microwave Link Report
(application style) from the main menu.
2. Select NEs from the Object Tree, and then click the double-right-arrow button (red).
The occupancy of information of the microwave links is displayed on the right side.
3. Optional: Click Print or Save As to output the report.
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Context
Menu item names displayed on the U2000 vary with different licenses.
Procedure
Step 1 Choose Inventory > SDH Report > SDH Fiber/Microwave Link Resource Usage Report
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > SDH Report > SDH Fiber/Microwave Link Resource Usage
Report (application style) from the main menu.
Step 3 Select a subnet from the Object Tree, and then click the double-right-arrow button (red). The
occupancy of the relevant microwave link resource is displayed on the right side.
Step 4 Optional: Click Filter and set the filtering criteria to display the required information in the
microwave link resource usage report.
Step 5 Optional: Click Alarm Threshold Set, you can view or modify the threshold value. If the
microwave link resource occupancy reaches a specified threshold, a pre-alarm at different levels
is generated.
NOTE
----End
Procedure
Step 1 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 2 Click New. In the dialog box displayed, specify a value for Task Name, set Task Type to SDH
Resource Statistic, and then specify a value for Run Type.
Step 4 Click Next. In the dialog box displayed, set Report File Type to Fiber Cable Occupancy
Resources, specify values for File Type and Storage path on server, and then specify the
statistics range.
Step 6 Optional: In the task list, view the new scheduled task.
----End
Follow-up Procedure
In the task list, you can pause and resume a selected task.
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Procedure
Step 1 Choose Inventory > MSTP Ethernet Report > Statistics Report of Ethernet Port
Resources (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Inventory > MSTP Ethernet Report > Statistics Report of
Ethernet Port Resources (application style) from the main menu.
Step 2 In the Object Tree, select one or more NEs and click .
Step 3 Click Statistics and the statistics results are displayed in the right-hand pane. You can view
details of the Ethernet ports.
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Procedure
Step 1 Choose Inventory > MSTP Ethernet Report > Statistics Report of Service Resources
Between Ethernet NEs (traditional style) from the main menu or select Fix-Network NE
Configuration in Application Center and choose Inventory > MSTP Ethernet Report >
Statistics Report of Service Resources Between Ethernet NEs (application style) from the
main menu.
Step 2 In the Object Tree in the left pane, select one or more NEs for statistics and click .
Step 3 Click Statistics and the statistics results are displayed in the right-hand pane. You can view
details of the Ethernet service information.
Step 4 Optional: Click Print or Save As to output the details of the Ethernet inter-NE service resource
statistics.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l A WDM protection group must be created.
Context
You can query the basic information and switching status of a WDM protection group from the
U2000 in the WDM protection group switching status report. You can also print the report or
save it as a file. The navigation path for an external switching is not provided.
Procedure
Step 1 Choose Inventory > WDM Statistic Report > WDM Protection Group Switching State
Report (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Inventory > WDM Statistic Report > WDM Protection
Group Switching State Report (application style) from the main menu. Click the WDM
Protection Group Switching Status Report or WXCP Switching Status Report tab.
Step 2 In the Object Tree on the left, select one or more NEs and click the double-right-arrow button
(red). On the right, you can view the WDM protection group switching status report of the
selected NE queried from the U2000.
Step 3 Click Query to refresh the switching status of the protection groups from the NE.
Step 5 Optional: Select one or more records in the list, right-click, and choose Browse Relevant
Trails from the shortcut menu. The WDM Trail Management window is displayed. You can
view the information about the trails that are relevant to the protection.
NOTE
In the case of the TPS protection, the Browse Relevant Trails shortcut menu item is not available. That
is, you cannot switch to the WDM Trail Management window.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Context
For the OptiX OSN 6800, you can view the information of master and slave shelves only on
WDM NEs of version V100R004C04 and latter versions.
Procedure
Step 1 Choose Inventory > WDM Statistic Report > WDM NE Master/Slave Shelf Info Report
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > WDM Statistic Report > WDM NE Master/Slave Shelf Info
Report (application style) from the main menu.
Step 2 In the left-hand Object Tree, select an NE and click . In the right-hand pane, you can
view the generated WDM NE master/slave shelf information report.
Step 3 Click Query to query the actual WDM NE master/slave shelf information from the NE.
Step 4 Optional: Click Print to print the report or click Save As to export the report.
----End
Prerequisites
l You are an NMS user with "Guests" user group authority or higher.
l The trail management license must be provided for the U2000.
Context
You can schedule a timing task for automatic statistics collection. For details, see 9.20.7
Creating a Timing Task for Collecting Statistics on WDM Resources.
Procedure
Step 1 Choose Inventory > WDM Statistic Report > Statistics Report of WDM Client-Side Port
Resources (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Inventory > WDM Statistic Report > Statistics Report of
WDM Client-Side Port Resources (application style) from the main menu.
Step 2 In the left-hand pane, select one or more NEs and click .
Step 3 Click Statistics to query the resource information of the WDM client-side ports.
Step 4 Click Used Port, Idle Port or Dynamic Port tab to query details of the ports.
NOTE
l If a client-side port is not used by a trail, this port is idle. Otherwise, this port is used.
l Discrete services are taken as idle resources.
----End
Prerequisites
l You are an NMS user with "Guests" user group authority or higher.
l The trail management license must be provided for the U2000.
l You cannot collect statistics on the wavelengths that are used by WDM ASON trails at the
OCh level.
Context
To ensure that statistics are correct, it is recommended that you search for WDM trails before
you collect statistics on wavelength resources.
You can schedule a timing task for automatic statistics collection. For details, see 9.20.7
Creating a Timing Task for Collecting Statistics on WDM Resources.
Procedure
Step 1 Choose Inventory > WDM Statistic Report > Statistics Report of Inter-Station Wavelength
Resources (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Inventory > WDM Statistic Report > Statistics Report of
Inter-Station Wavelength Resources (application style) from the main menu.
NOTE
Step 3 Click Browse to select the source end and click the button again to select the sink end. Click
OK in the Search NE dialog box.
NOTE
Step 5 Click Count. The Confirm dialog box is displayed prompting you to search for trails before
collecting statistics.
Step 6 Click OK. The Operation Result dialog box is displayed indicating that the operation was
successful. Click Close. You can view the created report in the right-hand pane.
NOTE
If there is a large number of network data, it takes a long time to create the report.
----End
Prerequisites
l You are an NMS user with "Guests" user group authority or higher.
l The trail management license must be provided for the U2000.
Context
l You can schedule a timing task for automatic statistics collection. For details, see 9.20.7
Creating a Timing Task for Collecting Statistics on WDM Resources.
l ASON services are not included in this resource statistics.
Procedure
Step 1 Choose Inventory > WDM Statistic Report > Statistics Report of WDM Link Resources
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > WDM Statistic Report > Statistics Report of WDM Link
Resources (application style) from the main menu.
Step 2 In the left-hand pane, select one or more NEs and click .
Step 3 In the WDM Link Resource Stastics Report pane, view the link resources among stations.
Step 4 In the WDM Link Resource Stastics Report pane, select a record. Then, in the Link List pane,
view the details of all the OTUk links between the two stations.
Step 5 Optional: Right-click a link in the Link List pane and choose Browse Relevant Client
Trails from the shortcut menu to view the client trail of this link.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 Choose Inventory > WDM Statistic Report > Wavelength Resource Usage Report
(traditional style) from the main menu or select Fix-Network NE Configuration in Application
Center and choose Inventory > WDM Statistic Report > Wavelength Resource Usage
Report (application style) from the main menu.
Step 2 In the Object Tree on the left, select one or more NEs and click . On the right, you can
view the wavelength resource usage report.
Step 3 Optional: Click Print to print the report or click Save As to export the report.
----End
Prerequisites
The trail management license must be provided for the U2000.
Context
The items for timing statistics include WDM client port resource statistics, WDM statistics on
inter-station wavelength resource, and WDM link resource statistics.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 2 Click WDM Resource Statistic in Task Type in the left pane.
Step 4 In the dialog box that is displayed, enter a name in the Task Name field.
When you set Run Type to Period, you need to specify the period for running the task. When you set Run
Type to Once, you can select the Run At Once to immediately run the task and the setting of a period is
not required.
Step 7 Select Report file type, File type, and Storage path on server.
----End
Prerequisites
l You are an NMS user with "Guests" user group authority or higher.
Context
You can collect the information automatically through scheduled tasks. For details, see 9.20.7
Creating a Timing Task for Collecting Statistics on WDM Resources.
Procedure
Step 1 Choose Inventory > WDM Statistic Report > Browse WDM Channel Resource (traditional
style) from the main menu or select Fix-Network NE Configuration in Application Center
and choose Inventory > WDM Statistic Report > Browse WDM Channel Resource
(application style) from the main menu.
Step 2 Specify filter criteria and click . In the list on the right, the number of channels of the
OMS trails and the occupancy of the channels are displayed.
Step 3 Select a route where you want to check WDM channel resources. In the Wavelength Allocation
Table area, all channels are displayed. Meanwhile, you can learn whether the channels are
occupied by OCh trails.
NOTE
If a channel is occupied by an OCh trail, the name of the OCh trail is displayed in the OCh Trail column.
You can right-click the channel and choose Client Trail Information from the shortcut menu to switch
to the Manage WDM Trail window. In the window, you can view the details of the OCh trail.
Step 4 Select one or more trails and click Detailed Trail Information below the list to switch to the
Manage WDM Trail window. In the window, you can view the details of the OMS trail.
----End
Prerequisites
l You are an NMS user with "Guests" user group authority or higher.
Context
You can schedule a timing task for automatic statistics collection. For details, see 9.20.7
Creating a Timing Task for Collecting Statistics on WDM Resources.
Procedure
Step 1 Choose Inventory > WDM Statistic Report > Statistics Report of WDM Bandwidth
Resources (traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Inventory > WDM Statistic Report > Statistics Report of
WDM Bandwidth Resources (application style) from the main menu.
Step 2 In the left pane, choose NEs from the navigation tree and select the level of required trails from
the Level drop-down list.
Step 3 Click or Statistics. On the Span Resource Usage tab page, the resource usage of the
specified level of trails between the selected NEs is displayed in a table.
NOTE
If you set Level to Client or OCh, the Span Resource Usage table lists the trails available between two
optical NEs or NEs in the Main Topology. If you select the Count Internal Resources of Optical NE
check box, the table also lists the trails between NEs in an optical NE.
NOTE
l After you set Level to Client, Total Resources indicates the total bandwidth (unit: Mbit/s) that
you can use to create Client trails.
l After you set Level to OCh, Total Resources indicates the total number of wavelengths used to
create OCh trails for OMS trails between optical NEs or NEs.
The add and drop wavelength parameters describe the resource allocation on NEs.
In the Resource Usage column, different colors indicate different resource usage. Assume that Resource
Usage is a.
l If a is smaller than Resource Idle Threshold, resources are idle, and is displayed.
l If a is greater than Resource Idle Threshold but smaller than Resource Insufficient Threshold,
resources are in the normal state, and is displayed.
l If a is greater than Resource Insufficient Threshold, resources are insufficient, and is displayed.
l Set thresholds in the Resource Idle Threshold and Resource Insufficient Threshold text boxes. Click
Refresh to refresh values in the Resource Usage column.
If you set Level to ODUk, the Span Resource Usage table lists the ODUk trails available
between NEs by default, including the NEs in optical NEs.
If you select OCh from the Type drop-down list in the lower pane, the table lists the ODUk
trails that OCh trails can carry, such as ODU0, ODU1, and ODUflex trails.
Step 4 Click the Overall Resources tab. In the Statistics area, an overall resource report of the specified
level of trails between the selected NEs is displayed.
If the statistics level is ODUk, the Overall Resources table lists the resource usage of each level.
NOTE
l On the Span Resource Usage tab, Total resources, Total used resources, and Total available
resources indicate the sum of Total Resources, Used Resources, and Available Resources
respectively.
l Average resource usage indicates the average resource usage of all statistical objects.
l Dispersion indicates the differences between Resource Usage and Average resource usage, reflecting
the resource usage balancing status of statistical objects. The smaller the Dispersion value is, the more
balanced the resource usage will be.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 Choose Inventory > PTN Statistic Report > Interface Resource Report (traditional style)
from the main menu or select Fix-Network NE Configuration in Application Center and
choose Inventory > PTN Statistic Report > Interface Resource Report (application style)
from the main menu.
Step 2 On the Physical Root navigation tree, select the NE to be queried and click .
The existing interface resource information in the NMS database is displayed.
NOTE
You can click to refresh the NE list on the Physical Root navigation tree.
The selected records are saved to a file in the .xls, .txt, .html, or .csv format in the report folder of the
client directory by default. If necessary, change the saving path in the Saving Options dialog box.
Step 5 Optional: Click Print. Set Start row and End row. Click OK.
In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
l You are an NMS user with "Guests" authority or higher.
l The configured service must form the trail on the U2000.
Context
Querying Port-Level Usage: In the Main Topology, right-click a PTN NE and choose NE
Explorer from the shortcut menu. On the NE Panel, right-click a board and choose RMON
Performance Browse from the shortcut menu. On the Statistics Group tab, select objects and
criteria and click Start.
Procedure
Step 1 Choose Inventory > PTN Statistic Report > Port Resource Report (traditional style) from
the main menu or select Fix-Network NE Configuration in Application Center and choose
Inventory > PTN Statistic Report > Port Resource Report (application style) from the main
menu.
Step 2 In the Object Tree, select one or more NEs and click . In the right-hand pane, view the
generated report.
Step 3 Optional: Click Alarm Threshold Settings. In the Alarm Threshold Settings dialog box, you
can set parameters as required.
NOTE
The selected records are saved to a file in the .xls, .txt, .html, or .csv format in the report folder of the
client directory by default. If necessary, change the saving path in the Saving Options dialog box.
Step 6 Optional: Click Print. Set Start row and End row. Click OK.
In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
such as DCN Link Quantity, Tunnel Quantity, and L2VPN PW Quantity for checking and
modifying network configurations of NEs.
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 Choose Inventory > PTN Statistic Report > Network Resource Statistics Report (traditional
style) from the main menu or select Fix-Network NE Configuration in Application Center
and choose Inventory > PTN Statistic Report > Network Resource Statistics Report
(application style) from the main menu.
Step 2 On the Physical Root navigation tree, select the NE to be queried and click .
The existing network resource information in the NMS database is displayed.
NOTE
You can click to refresh the NE list on the Physical Root navigation tree.
The selected records are saved to a file in the .xls, .txt, .html, or .csv format in the report folder of the
client directory by default. If necessary, change the saving path in the Saving Options dialog box.
Step 5 Optional: Click Print. Set Start row and End row. Click OK.
In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Procedure
Step 1 Choose Inventory > PTN Statistic Report > LAG Resource Report (traditional style) from
the main menu or select Fix-Network NE Configuration in Application Center and choose
Inventory > PTN Statistic Report > LAG Resource Report (application style) from the main
menu.
Step 2 On the Physical Root navigation tree, select the NE to be queried and click .
The existing LAG resource information of the current network-wide PTN NEs in the NMS
database is displayed.
NOTE
You can click to refresh the NE list on the Physical Root navigation tree.
Step 4 Optional: Click Save As. Then, set Start row, End row, and File name.
NOTE
The selected records are saved to a file in the .xls, .txt, .html, or .csv format in the report folder of the
client directory by default. If necessary, change the saving path in the Saving Options dialog box.
Step 5 Optional: Click Print. Set Start row and End row. Click OK.
In the Print dialog box, set General, Page Setup, and Appearance. Then, click Print.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
The board software (of the board that you want to query) supports querying of the board version
information.
Procedure
Step 1 Choose Inventory > Project Document > Board Manufacturer Information (traditional
style) from the main menu or select Fix-Network NE Configuration in Application Center
and choose Inventory > Project Document > Board Manufacturer Information (application
style) from the main menu.
Step 2 In the Object Tree, select one or more NEs and click the double-right-arrow button (red). You
can view the generated report in the right-hand pane.
NOTE
For a transport NE, the board manufacturer information will not be uploaded together with the NE
information. To display the board manufacturer information on the U2000, click Query to obtain such
information from an NE after adding and uploading the NE to the U2000.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
The board software (of the board that you want to query) supports querying of the board version
information.
Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
Context
The boards that do not occupy slot numbers mainly include the backplane, fan board, and power
supply board. In the common manufacturer information report, the slot number is displayed as
0.
Procedure
Step 1 Choose Inventory > Project Document > Board Manufacturer Information (traditional
style) from the main menu or select Fix-Network NE Configuration in Application Center
and choose Inventory > Project Document > Board Manufacturer Information (application
style) from the main menu.
Step 3 Select one or more NEs from the left-hand Object Tree, and click the double-right-arrow button
(red). You can view the generated common manufacturer information report in the right-hand
pane.
Step 4 Click Query to query the actual common manufacturer information from the NE.
----End
Prerequisites
You are an NMS user with "Guests" authority or higher.
Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
Procedure
Step 1 Choose Inventory > Project Document > Clock Tracing Diagram (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Inventory > Project Document > Clock Tracing Diagram (application style) from the main
menu. View the information in the generated clock tracing diagram.
Step 2 Optional: In the clock tracing diagram, right-click and choose Zoom In, Zoom Out and
Restore from the shortcut menu to set the display size of the diagram.
Step 3 Optional: In the clock tracing diagram, right-click and choose Add Comments from the
shortcut menu to add comments to an object in the diagram.
NOTE
l After you add comments, use the mouse to drag the comments to the position around the corresponding
NE or subnet.
l If you want to modify the comments, double-click the comments and modify them in the Edit
Comments dialog box.
l If you want to delete the comments, right-click the comments and choose Delete Comments from the
shortcut menu.
Step 4 Optional: In the clock tracing diagram, right-click and choose Customize from the shortcut
menu to select the parameters that you want to display in the clock tracing diagram.
Step 5 Optional: In the clock tracing diagram, right-click and choose Page from the shortcut menu to
set the page size of the diagram.
Step 6 Optional: In the clock tracing diagram, right-click and choose Font Size from the shortcut menu
to select the appropriate font size.
Step 7 Optional: In the clock tracing diagram, right-click and choose Print or Save As to output the
report.
----End
of the NEs in the networking diagram are consistent with the positions of the NEs in the Main
Topology. After the networking is complete, save the networking diagram in time.
Prerequisites
You are an NMS user with "Guests" authority or higher.
Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs.
Procedure
Step 1 Choose Inventory > Project Document > Networking Diagram (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Inventory > Project Document > Networking Diagram (application style) from the main
menu. View the information in the generated networking diagram.
Step 2 In the Object Tree, select the NEs that you want to display in the networking diagram and click
the double-right-arrow button (red).
Step 3 Optional: In the networking diagram, right-click and choose Customize from the shortcut menu.
The Customize dialog box is displayed. Select the parameters that you want to display in the
networking diagram, and click OK.
Step 4 Optional: In the networking diagram, right-click and choose Add Comments from the shortcut
menu to add comments to an object in the diagram.
NOTE
l After you add comments, you can use the mouse to drag the comments to the position around the
corresponding NE or subnet.
l If you want to modify comments, double-click the comments and then modify them in the Edit
Comments dialog box.
l If you want to delete comments, right-click the comments and choose Delete Comments from the
shortcut menu.
Step 5 Optional: In the networking diagram, right-click and choose Font Size from the shortcut menu
to select a proper font size.
Step 6 Optional: In the networking diagram, right-click and choose Zoom In, Zoom Out and
Restore to set the display size of the networking diagram.
Step 7 Optional: In the networking diagram, right-click and choose Page to set the page size for the
networking diagram.
NOTE
After the networking diagram is generated, some objects and information may be overlapped. In this case,
use the mouse to drag them to proper positions.
Step 8 Optional: In the networking diagram, right-click and choose Print to print the networking
diagram or choose Save As to export the networking diagram.
----End
Result
l In the Save As field, enter the directory where you want to save reports.
l After the networking diagram is saved, you can view the saved report in the directory that
is indicated in the Save As
Prerequisites
You are an NMS user with "Guests" authority or higher.
Context
The U2000 exports the timeslot assignment diagram in SVG format. To view or print the
diagram, install the SVG Viewer. On Windows, refer to common/SVG/PC/pcreadme.txt on
how to install the SVG Viewer; On UNIX, refer to common/SVG/Unix/unixreadme.txt. The
installation process takes five minutes or less.
Procedure
Step 1 Choose Inventory > Project Document > Timeslot Allocation Diagram (traditional style)
from the main menu or select Fix-Network NE Configuration in Application Center and
choose Inventory > Project Document > Timeslot Allocation Diagram (application style)
from the main menu.
Step 2 Select a protection subnet in the Generate Timeslot Allocation Diagram dialog box. Click
Start. The U2000 generates the timeslot allocation diagram of this protection subnet and save
it in the client\report directory.
NOTE
On UNIX, the timeslot allocation diagram that the U2000 automatically creates is saved in the client/
report directory.
Step 3 Navigate to the client\report directory, double-click the SVG file to view the timeslot allocation
diagram. If there are more than three NEs in a protection subnet, use the Alt key to view all NEs
in the diagram.
----End
You can monitor the process status, hard disk status, database status, resource status, component
information of the U2000 server, and log information on system monitor operations.
Context
l Physical memory usage and swap memory usage of the server that runs Solaris or SUSE
Linux are monitored separately. The two types of usage are referred to as memory usage
in the following content.
l The parameter Server usage sampling interval indicates the sampling interval. The CPU
and memory usage is sampled at the specified interval.
l CPU overload indicates that the CPU usage is larger than the alarm generation threshold.
l If the CPU usage sampled each time is larger than the alarm generation threshold, the CPU
is continuously overloaded. In this case, the number of continuous CPU overload times is
equal to that of continuous sampling times.
Procedure
Step 1 Choose System > System Monitor > Settings (application style) from the main menu.
Step 2 In the System Monitor Settings dialog box, select the Server Monitor tab.
The following figure shows the setting interface of the server running Solaris or SUSE Linux.
The following figure shows the monitoring interface of the server running Windows.
----End
Result
l When the number of sampling times with CPU overloading reaches the specified value, a
high CPU usage alarm is generated. When the CPU usage sampled at a time is less than
the alarm clearance threshold, the high CPU usage alarm is cleared.
l On Windows, when the memory usage is equal to or greater than the alarm generation
threshold, a high memory usage alarm is generated. When the memory usage is less than
the alarm clearance threshold, the high memory usage alarm is cleared.
l On Solaris or SUSE Linux, when the physical memory usage is equal to or greater than the
alarm generation threshold, a high memory usage alarm is generated. When the physical
memory usage is less than the alarm clearance threshold, the high memory usage alarm is
cleared.
l On Solaris or SUSE Linux, when the swap memory usage is equal to or greater than the
alarm generation threshold, a high swap usage alarm is generated. When the swap memory
usage is less than the alarm clearance threshold, the high swap usage alarm is cleared.
l When a high usage alarm is generated, the round icon in the CPU Usage, Memory
Usage (Windows), Physical Memory Usage (Solaris or SUSE Linux), or Swap Memory
Usage (Solaris or SUSE Linux) column turns red on the Server Monitor tab page of the
System Monitor Browser window. If you have enabled the function of displaying pop-up
messages, you will receive messages on the status bar of the client, prompting you of
performance exceptions.
10.1.2 Setting the Parameters for Monitoring the Disk Usage of the
U2000 Server
You can set the disk monitoring parameters to monitor the disk usage of the U2000 server. This
helps you to identify and handle insufficiency of the disk space in time, thereby preventing
service exceptions. When the disk usage reaches the specified threshold, the U2000 client
receives a high disk usage alarm. You can also determine whether to display pop-up messages
on the client. After you enable this function.
Procedure
Step 1 Choose System > System Monitor > Settings (application style) from the main menu.
Step 2 In the System Monitor Settings dialog box, select the Hard Disk Monitor tab.
Step 3 On the Hard Disk Monitor tab page, set Hard disk usage sampling interval, alarm generation
thresholds and alarm clearance thresholds.
l Under the Default node, set default values shared by all hard disks. Click + before
Default, and then set the thresholds for generating and clearing alarms of different severities.
The threshold specified for generating alarms of a low severity must be smaller than that for
generating alarms of a high severity.
l Under the Custom node, set values specially for an individual hard disk. Expand Custom,
and then click + before the server name. You can view that all disks use the default thresholds.
To specify other values for a disk, click + before the disk name, and then click the cell after
the name. In the drop-down list, select Customize value. In the text box, enter the thresholds
for generating and clearing alarms of different severities. If you do not want to receive alarms
of a disk, select Disable alarm generation.
Step 4 Optional: Expand Custom until the disk name is displayed. In the Show Pop-up Message
column, select Yes or No.
----End
Result
l When the hard disk space usage reaches the threshold for generating an alarm of a certain
severity, the corresponding alarm is generated. When the usage reaches the threshold for
generating an alarm of a higher severity, the alarm of the higher severity is generated and
the existing alarm is automatically cleared. When the usage is lower than a threshold for
clearing alarms of a severity, the alarm of this severity is cleared.
l When a high disk usage alarm is generated, the round icon in the Status column turns red
on the Hard Disk Monitor tab page in the System Monitor Browser window. If you
enable the function of displaying pop-up messages, the message The hard disk partition
is abnormal is displayed on the status bar of the client.
Procedure
Step 1 Choose System > System Monitor > Settings (application style) from the main menu.
Step 2 In the System Monitor Settings dialog box, select the Database Monitor tab.
Step 3 On the Database Monitor tab page, set Database usage sampling interval and the alarm
generation thresholds.
l Under the Default node, set default values shared by all databases. Click + before Default,
and then set the thresholds for generating alarms of different severities. The threshold
specified for generating alarms of a low severity must be smaller than that for generating
alarms of a high severity.
l Under the Custom node, set values specially for an individual database. Expand Custom,
and then click + before the server name and database instance name. You can view that all
databases use the default thresholds. To specify other values for a database, click + before
the database name, and then click the cell after the name. In the drop-down list, select
Customize value. In the text box, enter the thresholds for generating alarms of different
severities. If you do not want to monitor the usage of a database, select Disabled
Monitoring.
----End
Result
l When the database usage of the U2000 server reaches the threshold for generating an alarm
of a certain severity, the corresponding alarm is generated. When the usage reaches the
threshold for generating an alarm of a higher severity, the alarm of the higher severity is
generated and the existing alarm is automatically cleared. When the usage is smaller than
the threshold, the corresponding clearance alarm is generated.
l When the condition for generating a high database usage alarm is met, the round icon in
the Status column turns red on the Database Monitor tab page in the System Monitor
Browser window.
Procedure
Step 1 Choose System > System Monitor > Settings (application style) from the main menu.
Step 2 In the System Monitor Settings dialog box, select the Service Monitor tab.
Step 3 On the Service Monitor tab page, set Service status sampling interval and determine whether
to display pop-up messages.
----End
Result
l On the Service Monitor tab page in the System Monitor Browser window, information
is refreshed at the specified interval.
l If you enable the function of display pop-up messages for some services, a status indicator
is displayed on the status bar in the lower-right corner of the client. When all of these
services are running, the status indicator turns green. When one or some of these services
is stopped, the status indicator turns red and a pop-up message is displayed.
Context
If a service is stopped or abnormal, its status icon is displayed in red.
Procedure
Step 1 Choose System > System Monitor > Browser (application style) from the main menu.
Step 2 In the System Monitor Browser window, select the Service Monitor tab.
Step 3 In the Service Monitor tab, right-click an service and choose Details from the shortcut menu.
NOTE
You can also double-click a service to access the Service Details dialog box.
Step 4 In the displayed Service Details dialog box, view the service details and dependencies.
----End
Procedure
Step 1 Choose System > System Monitor > Browser (application style) from the main menu.
Step 2 In the System Monitor Browser window, select the Process Monitor tab.
Step 3 In the Process Monitor tab,view the process status of the server.
----End
Procedure
Step 1 Choose System > System Monitor > Browser (application style) from the main menu.
Step 2 In the System Monitor Browser window, click the Hard Disk Monitor tab.
Step 3 On the Hard Disk Monitor tab page, view the disk status of the server.
Whether Status is Normal depends on the preset alarm generation thresholds. When the usage
of the item exceeds the threshold, Status changes to Abnormal.
----End
Context
If the database space is insufficient, contact huawei technical support engineers to determine an
expansion solution.
Procedure
Step 1 Choose System > System Monitor > Browser (application style) from the main menu.
Step 2 In the System Monitor Browser window, select the Database Monitor tab.
NOTE
The monitor items for the Sybase and SQL Server databases are shown in the figure above.
Step 3 On the Database Monitor tab page, view the database status of the U2000 server.
Whether Status of a database is Normal depends on the preset alarm threshold. When the
database usage exceeds the threshold, Status changes to Abnormal.
----End
Procedure
Step 1 Choose System > System Monitor > Browser (application style) from the main menu.
Step 2 In the System Monitor Browser window, select the Server Monitor tab.
The following figure shows the monitoring interface of the server running Solaris or Linux.
The following figure shows the monitoring interface of the server running Windows.
Step 3 On the Server Monitor tab page, view the resource status of the U2000 server.
----End
Procedure
Step 1 Choose System > System Monitor > Browser (application style) from the main menu.
Step 2 In the System Monitor Browser window, select the Component Information tab.
Step 3 On the Component Information tab page, view the information about all installed components.
----End
Context
l Only the current tab page is refreshed.
l After you switch to another monitor tab page, the monitoring information on this tab page
is refreshed immediately.
Procedure
Step 1 Choose System > System Monitor > Browser (application style) from the main menu.
Step 2 In the System Monitor Browser window, select the tab corresponding to the monitoring
information to be refreshed.
----End
Procedure
Step 1 Choose System > System Monitor > Browser (application style) from the main menu.
Step 2 In the System Monitor Browser window, select the tab corresponding to the monitoring
information, and then click Save As.
NOTE
l The monitoring information can be saved in the format of TXT, HTML, CSV, or XML. The default
format is XML.
l For .txt files, code formats ISO-8859-1 and UTF-8 are supported. The default encoding format is
ISO-8859-1. You are advised to use the default encoding format if the saved file does not need to
support multiple languages; otherwise, UTF-8 is recommended.
Step 3 In the Save dialog box, select a path, enter a file name, and click Save.
----End
11 Task Management
The scheduled tasks of different modules on the U2000 used to be managed separately, which
was inconvenient for user operations. To address this issue, the U2000 now manages scheduled
tasks jointly, including system and user scheduled tasks. The centralized management simplifies
network management by allowing you to perform the following operations in one window: view
scheduled tasks, ascertain task status and progress, and create, modify, copy, suspend, resume,
and delete scheduled tasks.
Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu. The Task
Management window is displayed, as shown in Figure 11-1. Table 11-1 describes the window
displayed in Figure 11-1.
1 2 3 4
1 Navigation tree You can exactly find a scheduled task in the navigation tree.
2 Task result After a task is executed, the task result is displayed. On the task
information panel result information panel, you can browse the result of the
selected task executed last time. If multiple tasks are selected
in the task list, only the result of the task selected first is
displayed.
3 Button panel The buttons used for integrated task management are available
on the button panel.
4 Task list You can browse the scheduled tasks that exist on the server and
their details.
In the task list, the task states are marked in different colors:
l Gray: finished
l Orange: suspended
l Blue: running
l White: idle
After you select a task, the color becomes darker.
Inappropriate types of scheduled tasks will lead to excessive consumption of U2000 resources.
The U2000 will fail to work properly. Therefore, the U2000 provides different messages and
suggestions for different types of scheduled tasks. To run a scheduled task, you are advised to
configure the task appropriately based on the default period and export path provided.
Execution Task
Task Type Description
Type Category
Event
Manual
Dump
Alarm
Manual
Dump
Security
Log
Manual You can manually dump data from
One-time
Dump the database to the specified files
Manual Operation on the U2000 server. Dumped data
System task
Dump Log is deleted from the database to
Manual prevent the database running out of
Dump space.
System
Log
Manual
Dump
Performanc
e Event
Periodic
Manual
Dump
Execution Task
Task Type Description
Type Category
Performanc
e Event
Period
Dump
Device Log
Dump
AMS5080 One-time,
User Task
Data Dump Periodic
Alarm/
Event Log
Export
The system periodically exports
Security data from the database to files in
File Log Export the specified directories on the
Interface Operation server, enabling you to save data
Periodic System task outside the system. The exported
Log Export
data is still stored in the database.
System
Log Export
OSS
License
Export
Event
Overflow
Dump
Alarm
Overflow An overflow dump task can dump
Dump data from the database to specified
files on the U2000 server after the
Overflow Security Periodic System task specified threshold is reached.
Dump Log Dumped data is deleted from the
Overflow database to prevent the database
Dump running out of space.
Performanc
e Event
Overflow
Dump
Execution Task
Task Type Description
Type Category
Operation
Log
Overflow
Dump
System
Log
Overflow
Dump
ATM NE
Performanc
e
Collection
MSP
Exercise
Switching
Execution Task
Task Type Description
Type Category
NA NE
Performanc
e
Collection
Performanc
e collecting
job
Script
Export
Auto Sync
NA NE
Data
Discover
composite
services
Active/
Deactive
SDH Trail
One-time
Active/
Deactive
WDM Trail
Network
Health Periodic System task
Check
Parameter Description
Execution type According to different task execution periods, the U2000 divides
execution of its managed scheduled tasks into two types: periodic
execution and one-time execution.
Parameter Description
Start time Start time of periodic tasks and one-time tasks set during task
creation, including date and time.
NOTE
If the execution interval is one month and Start time is set to a specific time
on the 31st day of a month, the task is executed at the specified time. If the
month does not have the 31st day, the task is executed at the specified time on
the last day of the month.
Interval l Interval between periodic tasks, which consists of unit and period.
l The unit can be minute, hour, day, week, or month. Second is not
supported. The supported units of period vary according to the
task type.
l The period ranges are as follows: 1-366 x 24 x 60, in units of
minutes; 1-366 x 24, in units of hours; 1-366, in units of days;
1-52, in units of weeks; 1-12, in units of months.
Times Repeat times of a periodic task. The value ranges from 0 to 65535.
The value 0 indicates no limit.
NOTE
For example, the scheduling parameters of the Operation Log Export task are set as follows:
l Execution type = Periodic
l Start time = 21/10/2006 09:07:28
l Interval = 1 day
l Times = 0
The setting indicates that the system performs the Operation Log Export task at 09:07:28 every day from
09:07:28 on Oct. 21, 2006.
For details about the states of timer tasks, see Table 11-6.
State Description
Running After being dispatched, an idle task changes to the running state.
State Description
Suspended You can suspend an idle scheduled task. Then, the task is in the suspended
state.
The suspended task changes to the idle state if you resume it.
The state of a scheduled task changes with different operations. For details, see Figure 11-2.
Start
Creating a timing task
Idle
a timing task
a timing task
Scheduling
Suspend
Restore
Finish
Running
Deleting a timing task
Yes
Suspended
R ime
Another
es t
k
as
t
ch as
t Scheduling?
ing
im ed k m
ul a
at
ng in n
g ua
ti No
a lly
ele
on
D
Deleting a timing task e-
Finished
End
Dump tasks in the idle state are not allowed to be suspended to ensure the proper running of
theU2000. In other word, these tasks are never in the suspended state.
l A suspended task is changed to the idle state after being resumed.
l If a task does not need to be scheduled when the task is complete, it is in the finished state.
If the task needs to be scheduled again, it restores to the idle state.
l A finished one-time task can be manually rescheduled. After rescheduling, the task is
changed to a running task. A finished periodic task cannot be rescheduled.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Management window, perform operations based on custom requirements.
Customize the navigation tree 1. Right-click in the navigation tree and choose Type
Filter from the shortcut menu.
2. In the Type Filter dialog box, select the type of scheduled
tasks to be displayed. By default, all types of scheduled
tasks that the current user is authorized to browse are
displayed.
Customize the task list 1. Right-click the task list and choose Filter from the
shortcut menu.
2. In the Filter dialog box, set the filter criteria, including
Created By, Category, Task Status, and Execution
Result. For details about the parameters, see Task Filter
Criteria.
----End
Prerequisites
l At least one scheduled task exists.
l You have the permission to perform operations in the Task Management window.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Management window, perform operations based on various scheduled task viewing
requirements.
Viewing Operation
Scheduled
Tasks
Viewing In the navigation tree of the Task Management window, choose the task
Task whose progress you want to view. In the Progress column of the task list in
Progress the right pane of the window, view the task progress.
Viewing In the Task Management window, choose Task Type in the navigation tree.
Task l View the execution results in the Execution Result column in the task list
Execution in the right pane.
Results l You can view the detailed results in the Result area.
----End
Context
l This topic describes the common procedure for creating a user scheduled task. The
parameter settings vary according to different user scheduled tasks. When creating a user
scheduled task on the task creation interface, you can press F1 to view the help information
about the task.
l To quickly create tasks, you can copy a multi-instance user scheduled task (this task enables
you to create multiple tasks) and then modify its parameters.
l The instance quantity of the scheduled tasks of a specific type is limited. If the instance
quantity of the existing scheduled tasks of a specific type reaches the maximum, you cannot
create or copy a scheduled task of this type.
l If right control is set for tasks of a specific type and you are not authorized, you cannot
create or copy these tasks.
l The U2000 server may respond slowly due to too many scheduled tasks. It is recommended
that the total number of scheduled tasks (including system scheduled tasks and user
scheduled tasks) be no more than 500.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 3 In the New Task or Copy Task dialog box, set the parameters of the created user scheduled
task.
Parameter Setting
NOTICE
iSStar scripts can deliver MML commands to NEs. If an iSStar script contains MML commands,
confirm the impact of the commands on NE services before they are delivered and exercise
caution.
----End
Context
l Scheduled tasks are classified into system scheduled tasks and user scheduled tasks.
l If you are not authorized to operate certain tasks, you can only view the attributes of the
tasks created by other users, but cannot modify these attributes.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Management window, modify the attributes of a scheduled task by using one of
the following methods:
l Select a task from the task list, and then click Attribute. In the Attribute dialog box, modify
common and extended parameters.
l Double-click a task in the task list. In the displayed Attribute dialog box, modify common
and extended parameters.
NOTE
Parameter modification varies according to the task type.
----End
Context
l If right control is disabled, users can delete only the tasks created by themselves. If right
control is enabled, authorized users can delete the tasks created by themselves and other
users. The users of the Administrators user group can delete the tasks created by all users.
l You can not delete system tasks.
l You can not delete the running tasks. You can only delete user tasks in the idle, suspended
or finished state.
l Deleting a scheduled task will delete the files generated during task execution. If multiple
tasks are deleted at a time, response may time out.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Management window, choose Task Type in the navigation tree.
Step 3 Select one or more user scheduled tasks in the task list in the right pane.
----End
Context
l Only idle tasks can be scheduled.
l Certain idle tasks such as dump tasks are not allowed to be suspended to ensure the proper
running of the U2000.
l If right control is disabled, users can suspend only the tasks created by themselves. If right
control is enabled, authorized users can suspend the tasks created by themselves and other
users. The users of the Administrators user group can suspend the tasks created by all
users.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Management window, choose Task Type in the navigation tree.
Step 3 Suspend one or more idle tasks with one of the following methods:
l Manual suspending
Select one or more idle tasks in the task list. Right-click the task and choose Suspend from
the shortcut menu. In the Confirm dialog box, click Yes.
NOTE
If the Suspend menu item is not displayed in the shortcut menu, the task cannot be suspended.
l Automatic suspending
Select an idle task in the task list. Right-click the task and choose Suspend/Resume
Schedule from the shortcut menu. In the Suspend/Resume Schedule dialog box, select
Suspension time and then set the time. Click OK.
NOTE
If the Suspend/Resume Schedule menu item is not displayed in the shortcut menu, the task cannot be
suspended.
For details about how to set the time for automatic suspension, see Automatic Suspension
and Resumption of a Scheduled Task.
After the task is suspended, the U2000 does not schedule it until its state is changed to idle.
----End
Context
l Only idle tasks can be scheduled.
l If right control is disabled, users can resume only the tasks created by themselves. If right
control is enabled, authorized users can resume the tasks suspended by themselves and
other users. The users of the Administrators user group can resume the tasks suspended
by all users.
Procedure
Step 1 Choose Task Schedule > Task Management (application style) or Administration > Task
Schedule > Task Management (traditional style) from the main menu.
Step 2 In the Task Management window, choose Task Type in the navigation tree.
----End
To ensure the security of network data, the U2000 provides the function of backing up and
restoring network data.
12.6 Backing Up and Restoring the U2000 Network Configuration Data by Using Scripts
This topic describes how to back up and restore the U2000 network configuration data by using
scripts.
Basic Concepts
l Backup
Back up is a method used to store important data to restore the damage of the original data.
The U2000 provides the following schemes to backup U2000 data:
– Backup of the U2000 databases
The backup object is the entire U2000 database, including the custom data at the
U2000 side (excluding the custom options of the system), network layer trail data, NE-
side configuration data, alarm data and performance data. In addition, a backup is
created for the structure of the entire database, all database tables (including the system
tables and the user tables), table structure, and stored procedures.
– Backup of the data by using scripts
The U2000 provides the function of exporting and importing script files, to back up and
restore the network configuration data of the U2000, including the user name, password,
path information, and topology coordinates. This realizes the upgrade of the
configuration data with zero loss during the U2000 upgrade.
For details on the differences between the three schemes, refer to the 12.2 Methods of
Backing Up and Restoring the U2000 Data.
NOTE
The personal information (including personal name, phone numbers and addresses) on the U2000
and all user names and passwords are also backed up. Therefore, you are obligated to take
considerable measures, in compliance with the laws of the countries concerned and the user privacy
policies of your company, to ensure that the personal data of users is fully protected.
l Restoration
Restoration coexists with backup. When certain data is damaged or destroyed, you can
restore the data.
Restoration is to restore database data from the backup file, and then overwrite the existing
data file.
l Dump
Dump is a process that saves logs (such as alarm logs, event logs, U2000 security logs,
operation logs, and system logs) and performance data on the database as OS files in text
format and deletes the logs and performance data from the database to clear database space.
The following types of dump are available:
– Overflow dump
The overflow dump is performed when the logs in the databases reach the maximum
storage capacity. You can specify the number of logs to dump.
– Scheduled dump
The scheduled dump, which is the alternative method of overflow dump, is optional.
You can set whether to create a scheduled task, and if you create a scheduled task you
can specify the schedule time and duration.
– Immediate dump
The immediate dump is also referred to as manual dump. This method is used to dump
data that was created on a specific date.
Application Scenarios
l Backup and restoration of U2000 data can be implemented in the following scenarios by
the operating system type. The available operating system types are Solaris single-server
system, SUSE Linux single-server system, Windows single-server system, Solaris high
availability system, and SUSE Linux high availability system.
l Backup and restoration of U2000 data can be implemented in the following scenarios based
on the location of backup data:
– Local data backup and restoration
Data of a specific server is backed up to a local disk and the backup data is then used
to restore U2000 data. For example, back up data of server A to disk D on server A, and
then use the backup data on disk D to restore data of server A.
It is advisable to perform remote backup when the local disk space is insufficient.
– Remote data backup and restoration
Data of the U2000 server is backed up to a remote server and the backup data on the
remote server is then used to restore U2000 data. For example, back up data of server
A to remote server B, and then use the backup data on remote server B to restore data
of server A.
l Backup and restoration of U2000 data can be implemented in the following scenarios based
on the source of data for restoration.
– Local data restoration (recommended)
Backup data of the local server is used to restore server data. For example, use backup
data of server A to restore data of server A.
– Remote data restoration
Backup data of another server is used to restore data of the specific server. For example,
use backup data of server B to restore data of server A.
all database tables (including the system tables and the user tables), table structure, and stored
procedures.
NOTE
Backup data of an OS cannot be used for data restoration of another version or type of OS.
Backup data of a database cannot be used for data restoration of another version or type of database.
The personal information (including personal name, phone numbers and addresses) on the U2000 and all
user names and passwords are also backed up. Therefore, you are obligated to take considerable measures,
in compliance with the laws of the countries concerned and the user privacy policies of your company, to
ensure that the personal data of users is fully protected.
The following data is not backed up when you back up the U2000 database:
l The data that is not saved at the NE side, that is, the data that cannot be uploaded.
l The custom options of the system. For example, font, color setting, and audio setting.
Backing up and restoring the U2000 network configuration data by using the script
files
The U2000 provides the function of exporting and importing script files, to back up and restore
the network configuration data of the U2000, including the user name, password, path
information, and topology coordinates. This realizes the upgrade of the configuration data with
zero loss during the U2000 upgrade. For details, see 12.6 Backing Up and Restoring the U2000
Network Configuration Data by Using Scripts.
NOTE
l The default coding format in a script file is UTF-8. If illegible characters are displayed, to change the
coding format of the script file, in the Windows OS, you can change encoding configuration item in
the %IMAP_ROOT%\cbb\trans\core\conf\xml\script\script_enum.xml configuration file; In the
Solaris or SUSE Linux OS, you can change encoding configuration item in the $IMAP_ROOT/cbb/
trans/core/conf/xml/script/script_enum.xml configuration file.
l By default, the name of a script file contains the NE name. To exclude the NE name from a script file
name, in the Windows OS, you can change the scriptname configuration item in the %IMAP_ROOT
%\cbb\trans\core\conf\xml\script\script_enum.xml configuration file. In the Solaris or SUSE Linux
OS, you can change the scriptname configuration item in the $IMAP_ROOT/cbb/trans/core/conf/
xml/script/script_enum.xml configuration file.
l The data are exported from the U2000 database.
l The imported script files update the data on the U2000 only, with no impact on the data on the NEs.
l The personal information (including personal name, phone numbers and addresses) on the U2000 and
all user names and passwords are also backed up. Therefore, you are obligated to take considerable
measures, in compliance with the laws of the countries concerned and the user privacy policies of your
company, to ensure that the personal data of users is fully protected.
Table 12-1 Characteristics and application scenarios of two data maintenance methods
Backing up and restoring all l Backs up the structure and This requires a large storage
data in the U2000 databases contents of the U2000 medium space. If you want to
database. back up the U2000 database
l The data is in the binary in a scheduled manner, large-
mode. size disk is recommended.
Backing up and restoring the l Exports the configuration l This method is usually
U2000 network data in the U2000 to a .txt used to upgrade the
configuration data by using file that is similar to the U2000. The new U2000
the script files MML format. This is version is compatible
done to save data. with the scripts of the old
l Backs up only some of the version.
data, including the basic l This method is usually
configuration data, port used to back up and
naming data and custom restore the basic
data. configuration data for a
l The processing speed is single NE. This method
slow. also restores the custom
data.
l The backup file is small.
occurs. The backup object is the entire U2000 database, including the custom data at the
U2000 side (excluding the custom options of the system), network layer trail data, NE-side
configuration data, alarm data and performance data. In addition, a backup is created for the
structure of the entire database, all database tables (including the system tables and the user
tables), table structure, and stored procedures.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l All users must have been logged out of the MSuite client.
l Sufficient disk space is available.
– On Windows, generally, the available disk space of the local temporary directory and
the local backup path is over 1/3 of that for the local database. The default local
temporary directory is D:\tmp. The default local database path is D:\data in a single-
server system.
– On Solaris or SUSE Linux, the available disk space of the local backup path is over 1/3
of that for the local database, not consider the disk space of the local temporary directory.
The default local database path is /opt/sybase/data. To view the disk space, run the
following command:
# du -sh Data file path
Context
l The backup process cannot be canceled once it is started.
l The default data backup path must be %IMAP_ROOT%\var\backup. During backup,
the backup data is generated in a folder named by time. For example, the path is
201306271646.
l The personal information (including personal name, phone numbers and addresses) on the
U2000 and all user names and passwords are also backed up. Therefore, you are obligated
to take considerable measures, in compliance with the laws of the countries concerned and
the user privacy policies of your company, to ensure that the personal data of users is fully
protected.
l In a high availability system, the AppService resource group automatically freezes during
backup. After backup is complete, the resource group automatically unfreezes.
Procedure
Step 1 Log in to the U2000 client. For details, see 1.2.6 Logging In to a U2000 Client.
Step 2 Choose Administration > Back Up/Restore NMS Data > Database Backup (traditional style)
from the main menu or select System Management in Application Center and choose
System > Back Up/Restore NMS Data > Database Backup (application style) from the main
menu.
NOTE
Customizing a backup path helps to avoid the effect of system reinstallation and disk formatting on
backup data. This improves the maintainability of the system.
NOTICE
l On Solaris OS or SUSE Linux OS, if the backup path already exists, assign permissions
to the backup path based on the level. The backup path needs to belong to the /opt
directory in order to prevent modification on the system directory from damaging the
U2000 environment. You do not need to change the permission to the /opt path. The
number of operation sets assigned to the /opt/oss directory is 750, and the number of
operation sets assigned to other subdirectories under the /opt directory is 770.
Run the following commands as the root user for all directories except for the last
directory of the path:
# chown ossuser:ossgroup path
# chmod 770 path
Run the following command for the last directory of the path:
# chown -R ossuser:ossgroup path
# chmod -R 770 path
For example, if the path is /opt/backup1/backup2, run the following commands as user
root:
# chown ossuser:ossgroup /opt/backup1
# chmod 770 /opt/backup1
# chown -R ossuser:ossgroup /opt/backup1/backup2
# chmod -R 770 /opt/backup1/backup2
l The backup directory must be an absolute path that contains letters, digits, underscores
(_), or hyphens (-) and excludes the space, bracket, Chinese characters and so on. The
path name cannot exceed 60 characters. For Windows, the backup directory must be
located on the disk drive of the server.
Step 5 In the warning dialog box that is displayed, click OK. The U2000 database backup starts and
a dialog box is displayed showing the backup progress.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l All users must have been logged out of the MSuite client to prevent incomplete database
backup.
l Sufficient disk space is available.
– On Windows, generally, the available disk space of the local temporary directory and
the local backup path is over 1/3 of that for the local database. The default local
temporary directory is D:\tmp. The default local database path is D:\data in a single-
server system.
– On Solaris or SUSE Linux, the available disk space of the local backup path is over 1/3
of that for the local database, not consider the disk space of the local temporary directory.
The default local database path is /opt/sybase/data. To view the disk space, run the
following command:
# du -sh Data file path
Context
l The U2000 does not support multiple periodic backup tasks at the same time. The difference
between the time points to start scheduled tasks must be greater than the maximum running
period of the tasks.
l It is recommended that you set the scheduled backup time to the time when network service
traffic is light, such as at midnight (00:00~06:00).
l The default data backup path must be %IMAP_ROOT%\var\backup. During backup,
the backup data is generated in a folder named by time. For example, the path is
201306271646.
l The personal information (including personal name, phone numbers and addresses) on the
U2000 and all user names and passwords are also backed up. Therefore, you are obligated
to take considerable measures, in compliance with the laws of the countries concerned and
the user privacy policies of your company, to ensure that the personal data of users is fully
protected.
l In a high availability system, the AppService resource group automatically freezes during
backup. After backup is complete, the resource group automatically unfreezes.
Procedure
Step 1 Log in to the U2000 client. For details, see 1.2.6 Logging In to a U2000 Client.
Step 2 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 3 Choose Task Type > Backup > DB Backup in the left pane, and click New. The New Task
dialog box is displayed.
Step 4 Enter a name for the scheduled task. Select One-time or Periodic as the run type. Then click
Next.
Step 5 In Time Setting, set the planned start time of the task. If One-time is selected, choose to start
the task immediately or not. If Periodic is selected, in the Period Setting area, specify the task
period and set Execution Times or End time. Then, click Next.
NOTICE
If multiple scheduled backup tasks are configured, their backup time ranges cannot overlap;
otherwise, backup fails.
NOTICE
l On Solaris OS or SUSE Linux OS, if the backup path already exists, assign permissions
to the backup path based on the level. The backup path needs to belong to the /opt
directory in order to prevent modification on the system directory from damaging the
U2000 environment. You do not need to change the permission to the /opt path. The
number of operation sets assigned to the /opt/oss directory is 750, and the number of
operation sets assigned to other subdirectories under the /opt directory is 770.
Run the following commands as the root user for all directories except for the last
directory of the path:
# chown ossuser:ossgroup path
# chmod 770 path
Run the following command for the last directory of the path:
# chown -R ossuser:ossgroup path
# chmod -R 770 path
For example, if the path is /opt/backup1/backup2, run the following commands as user
root:
# chown ossuser:ossgroup /opt/backup1
# chmod 770 /opt/backup1
# chown -R ossuser:ossgroup /opt/backup1/backup2
# chmod -R 770 /opt/backup1/backup2
l The backup directory must be an absolute path that contains letters, digits, underscores
(_), or hyphens (-) and excludes the space, bracket, Chinese characters and so on. The
path name cannot exceed 60 characters. For Windows, the backup directory must be
located on the disk drive of the server.
Step 7 Then click Finish. A message asking you whether to continue is displayed, click Yes.
----End
Result
On the Task Management tab page, choose Task Type > Backup > DB Backup from the
service tree. The created task is displayed in the right-hand pane of the window.
Prerequisites
l The database is running.
l In the case of remote backup and recovery, the FTP or SFTP server programs must be
running on the remote server, and the relevant port must be enabled on the local server.
The port of FTP server is 21, and the port of SFTP server is 22.
NOTE
You can run the following commands to confirm that the SFTP service can be connected normally
on the server:
1. # vi /etc/ssh/sshd_config
2. Add # to the front of "PAMAuthenticationViaKBDInt yes", and enter the :wq! command to save
the setting and exit.
3. # svcadm restart network/ssh
l The FTP or SFTP user must have the write authority in a remote FTP server.
Context
l The U2000 does not support multiple periodic backup tasks at the same time. The difference
between the time points to start scheduled tasks must be greater than the maximum running
period of the tasks.
l It is recommended that you set the scheduled backup time to the time when network service
traffic is light, such as at midnight (00:00~06:00).
l Performance data collection involves abundant data. It is recommended that you perform
the 15-minute performance collection every three days, 24-hour performance collection
every six days, at the time when network traffic is light.
l The personal information (including personal name, phone numbers and addresses) on the
U2000 and all user names and passwords are also backed up. Therefore, you are obligated
to take considerable measures, in compliance with the laws of the countries concerned and
the user privacy policies of your company, to ensure that the personal data of users is fully
protected.
Procedure
Step 1 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 3 Choose Task Type > Backup. Select DB Backup as the task type and enter a name for the
scheduled task. Select One-time or Periodic as the run type. Then click Next.
Step 4 In Time Setting, set the planned start time of the task. If Periodic is selected, in Period
Setting, set the planned period and execution times of the task. Then, click Next.
NOTICE
If multiple scheduled backup tasks are configured, ensure that times set for theses tasks do not
overlap; otherwise, backup fails.
NOTE
l The backup path on the remote Windows server must be the same as that FTP/SFTP service on the
server provide, otherwise, backup fails.
l On Solaris OS or SUSE Linux OS, change the permission to the folder that stores backup files and is
named after time to 750 to ensure system security. Run the following commands as the root user:
# chmod -R 750 Folder that stores backup files and is named after time
----End
Result
On the Task Management tab page, choose Task Type > Backup > DB Backup from the
service tree. Then, the created task is displayed.
Procedure
Step 1 Log in to the NMS maintenance suite to restore the U2000 database. The procedure for restoring
the U2000 database varies according to the OS environment. For details about how to restore
U2000 data, see Backing Up and Restoring the U2000 Database in the iManager U2000 Unified
Network Management System Administrator Guide or the U2000 data restoration procedure
described in Managing Databases in the Help of the U2000 NMS maintenance suite.
----End
Application Scenario
The scripts are used to back up U2000 network configuration data during the NMS upgrade.
The core configuration data of the NMS supports the following upgrade mode: export user data
from the original NMS into script files unrelated to the OS and database; uninstall the original
NMS and install the new NMS; import the script files into the new NMS; user data that is not
exported can be restored by synchronizing NEs or searching for trails.You are obligated to take
considerable measures, in compliance with the laws of the countries concerned and the user
privacy policies of your company, to ensure that the personal data of users is fully protected.
Of course, not all U2000 data can be backed up or restored by using scripts. Instead, backing up
and restoring all data in the U2000 database is recommended.
Precautions
You cannot back up the U2000 topology structure by backing up scripts. You need to adjust the
topology structure manually after scripts are imported during data restoration.
Using scripts to back up and restore data makes the following impacts:
l NBIs are affected:
The upper-layer OSS must use physical IDs or logical IDs of NEs as indexes to interconnect
with the U2000. During U2000 upgrade, physical IDs of NEs are constant and logical IDs
are assigned by the U2000 again. Physical IDs are recommended if the U2000 is
interconnected to an upper-layer OSS. If the upper-layer OSS uses logical IDs as indexes,
NEs must be uploaded after data restoration. Fibers/cables, subnets, and optical NEs have
only logical IDs. If the upper-layer OSS uses data about the fibers/cables, subnets, or optical
NEs, the fibers/cables, subnets, or optical NEs must be uploaded again.
l Only basic information is stored in scripts, whereas other information must be obtained by
uploading NEs. Therefore, you must manually restore customized information that is stored
on neither NEs nor scripts; otherwise, the information will be lost. Information that requires
manual restoration includes but is not limited to:
– Customized information (background and sound configurations) on clients
– Alarm performance template configurations
– Security information, such as NMS user name and password
– Path naming rule
– Access control list (ACL)
l The following information cannot be restored manually or using scripts. It is recommended
that you dump the information before restoration by using the dumping function of the
U2000.
– Historical alarm
– Historical performance
– U2000 security log
– U2000 operation log
– U2000 system log
– Abnormal event
Main Usage
The main usage of the script files is as follows:
l Realizing the upgrade of the configuration data with zero loss during the U2000 upgrade.
This is an important method for the U2000 upgrade. This is the main usage of the script
files.
l After the network data is modified, restoring the customized information of the U2000,
such as the trail name, fiber name, port name, and the customer information. Therefore,
you are obligated to take considerable measures, in compliance with the laws of the
countries concerned and the user privacy policies of your company, to ensure that the
personal data of users is fully protected.
l By modifying the script files, realizing the division and combination of the U2000 data and
realizing the import of the desired data only, such as the NE list (with no configuration
data), fiber connection, protection subnet, or trail.
l Supporting the simplified implementation of the project design.
U2000 also provides two script scenarios: Upgrade All and Upgrade NE. The network-wide
configuration data can be efficiently restored or backed up in the script scenarios by importing
or exporting a set of script of one or multiple types.
l Upgrade All script scenario consists of NE Configuration File, NE Port Naming File,
NM Computer Information File, Network Layer Information File, and NE List File.
l Upgrade NE script scenario consists of NE Configuration File, NE Port Naming File,
NE List File.
Table 12-6 lists the types of the script files in the .txt format that the U2000 provides and the
contents of the data.
l Wavelength:
Includes the basic
attributes of the
wavelength,
additional
information, the
source/sink port,
and the physical
route.
NE Port Naming File NEPort_extension This file contains the This file can be
ID-basic ID_NE naming information imported and
name_(coding about every port on exported.
format).txt, such as the NE.
NEPort_9-1_NE1_
(UTF-8).txt
clock subnet,
restoration
conditions of
clock source,
SSM output
conditions and
clock source
level.
l Overhead
configuration:
including public
overhead,
advanced
overhead,
auxiliary
overhead,
conference call,
F1 data port pass-
through,
broadcast data
port,
communication
port, data port,
ring-out route and
number of subnet
connected to
optical port.
l Environment
controlling:
including PMU
settings, EMU
settings, and
CAU settings.
l Board
configuration:
including SDH
interface, PDH
interface, WDM
interface, ATM
interface and
optical
amplification
board interface.
l Traffic
configuration:
including TDA
traffic, TDA feed
selection and
TDA clock
source settings.
l Equipment
protection:
including 1+1
protection, 1:N
equipment
protection, OLP
channel
protection, WDM
channel
protection,
wavelength
protection group
and 1:N channel
protection.
l Equipment
maintenance:
including fan
settings and
board
temperature
threshold.
l Board
information:
including slot
number, type,
BIOS version,
board software
version, FPGA
version, Flash
version. Board
information only
supports
exporting.
The U2000 supports
importing of data
about one or more
configured NEs. All
In addition, the U2000 provides the script files in the .xml format for the network planning and
design, containing the Network-wide Configuration File, NE Configuration File, Network
Layer Information File, and ASON Information File. The ASON Information File can be
imported and exported, but other types of script files in the .xml format can be exported only.
NOTE
l The default coding format in a script file is UTF-8. If illegible characters are displayed, to change
the coding format of the script file, in the Windows OS, you can change encoding configuration item
in the %IMAP_ROOT%\cbb\trans\core\conf\xml\script\script_enum.xml configuration file; In
the Solaris or SUSE Linux OS, you can change encoding configuration item in the $IMAP_ROOT/
cbb/trans/core/conf/xml/script/script_enum.xml configuration file.
l By default, the name of a script file contains the NE name. To exclude the NE name from a script
file name, in the Windows OS, you can change the scriptname configuration item in the %
IMAP_ROOT%\cbb\trans\core\conf\xml\script\script_enum.xml configuration file. In the
Solaris or SUSE Linux OS, you can change the scriptname configuration item in the
$IMAP_ROOT/cbb/trans/core/conf/xml/script/script_enum.xml configuration file.
Compatibility
l The scripts exported from the U2000 of an earlier version can be imported to the U2000
of a later version. But an error may occur if the scripts exported from the U2000 of a later
version are imported to the U2000 of an earlier version. The U2000 of an earlier version
do not support the features and functions that are added and the parameters that are modified
in the U2000 of a later version. After the scripts are imported, an error message is displayed.
But this does not affect the import of other information.
l The scripts generated on Windows and on UNIX are compatible.
l T2000 scripts can be imported to the U2000. U2000 scripts cannot be imported to the
T2000.
NOTE
After importing T2000 scripts to the U2000, network-layer trails on the U2000 are different from
those on the T2000 due to software differences. In this case, delete all network-layer trails from the
U2000 and search for trails.
Application
During the network adjustment, such as adding or deleting a node in the network, if the fiber
connection is deleted, the protection subnet and trail carried on the fiber are deleted from the
network layer of the U2000. After the network adjustment, if the source and sink ports of the
trail are not changed, you can find the trail again by performing the trail search. But the original
customized information of the trail, such as the trail name, customized information of the trail,
and remarks, cannot be restored through the search.
NOTE
l The Network Layer Information File script can be used to restore the customized information only
when the source and sink ports of the trail are not changed after the network adjustment. Otherwise,
you need restore the customized information manually.
l When the network layer information file is imported after the network adjustment, errors may be
displayed for part of the data, because certain objects, such as NEs, boards, and ports, are changed.
This does not affect the restoration of the customized information.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Before you export the script files, you must check the consistency of the configuration data
to ensure that the configuration data in the U2000 is consistent with that in the NE.
Context
The personal information (including personal name, phone numbers and addresses) on the
U2000 and all user names and passwords are also backed up. Therefore, you are obligated to
take considerable measures, in compliance with the laws of the countries concerned and the user
privacy policies of your company, to ensure that the personal data of users is fully protected.
Procedure
Step 1 Log in to the U2000 client. For details, see 1.2.6 Logging In to a U2000 Client.
Step 2 Choose Administration > Back Up/Restore NMS Data > Import/Export Script File
(traditional style) from the main menu or select System Management in Application Center
and choose System > Back Up/Restore NMS Data > Import/Export Script File (application
style) from the main menu.
Step 5 Select a script file type from the Script File Type field. For details, see 12.6.1 Script Files.
NOTE
l To export the network-wide script file, select Networkwide Configuration File. Export the following
files to a specified directory: NWCfg_NMS Name.txt, NWNeList_NMS Name.txt, NEPort_Port ID-
Basic ID_NE Name.txt, and NEData_Extended ID-Basic ID_NE Name.txt.
l The following script types are available for the export: Networkwide Configuration File, NE Port
Naming File, NE Configuration File, NE List File, NM Computer Information File, Service
Actualization Script, Network Layer Information File, Network Modeling and Design
Information File, CEAS, Network Basic Configuration Information File, NM CEAS Information
File, User-defined template and Upgrade All.
l If you want to export script files of access domain or IP domain NEs, only Upgrade All can be selected.
Step 6 Select the NE for which you want to export script files from the Export NE List.
NOTE
Specify the NE only when you export the Networkwide Configuration File, NE Port Naming File, NE
Configuration File, NE List File, Network Modeling and Design Information File, CEAS, Network
Basic Configuration Information File, NM CEAS Information File and Upgrade All.
Step 7 Click Create File Directory to create a directory where the exported script files are to be saved.
NOTE
The script file is saved on the U2000 server. On Windows, the backup directory is %IMAP_ROOT%
\script. On Solaris and SUSE Linux, the backup directory is $IMAP_ROOT/script. You can create a new
directory under it.
----End
Follow-up Procedure
If you cannot export the script file by referring to U2000 and the Unknown Device-ASON
Configuration message is displayed, check whether the ASON instance is deployed by using
the U2000 NMSuite. If the ASON instance is deployed but is not supported by the license, delete
the instance. Then, you can successfully export the script file by referring to U2000.
Prerequisites
You are an NMS user with Operator Group authority or higher.
Context
l The U2000 does not support multiple periodic backup tasks at the same time. The difference
between the time points to start scheduled tasks must be greater than the maximum running
period of the tasks.
l It is recommended that you set the scheduled backup time to the time when network service
traffic is light, such as at midnight (00:00~06:00).
l Performance data collection involves abundant data. It is recommended that you perform
the 15-minute performance collection every three days, 24-hour performance collection
every six days, at the time when network traffic is light.
l The personal information (including personal name, phone numbers and addresses) on the
U2000 and all user names and passwords are also backed up. Therefore, you are obligated
to take considerable measures, in compliance with the laws of the countries concerned and
the user privacy policies of your company, to ensure that the personal data of users is fully
protected.
Procedure
Step 1 Log in to the U2000 client. For details, see 1.2.6 Logging In to a U2000 Client.
Step 2 Choose Administration > Task Schedule > Task Management (traditional style) from the
main menu or select System Management in Application Center and choose Task
Schedule > Task Management (application style) from the main menu.
Step 4 Select Script Export as the task type and enter a name for the scheduled task. Select Periodic
as the run type. Then click Next.
Step 5 In Time Setting, set the planned start time of the task.
Step 6 In Period Setting, set the execution interval and execution times of the task. Then, click Next.
Step 7 Select the NEs and the type of the script file to be exported. For details, see 12.6.1 Script
Files. Then click Finish. Then the created scheduled task is displayed in the Task
Management window.
----End
Prerequisites
l During data restoration, the instances deployed for NMS must include the instances
deployed for NMS components during backup.
l You are an NMS user with Operator Group authority or higher.
l The imported configuration scripts are within the management capabilities of the current
NE Explorer instance and U2000 license as follows:
– The management capabilities of NE Explorer as follows:
– The number of equivalent NEs managed by each NE Explorer instance is no more
than 2,000.
– The number of gateway NEs managed by each NE Explorer instance is no more than
500.
– The number of network-wide equivalent NEs does not exceed the management
capability of the license.
l Ensure that scripts to be restored have been uploaded to the server. For details about how
to upload files to the server, see How to Use the FileZilla to Transfer Files by SFTP.
Context
NOTICE
l On a Solaris-based client, upload the configuration scripts to the server as user ossuser.
l For single-type script mode in the transport domain, you need to back up the U2000 database
before importing the script file, and then initialize the U2000 database. Then, import the
configuration file. It is recommended that you import the network-wide configuration file.
You can restore the data from a backup file if you failed to import the script file.
l After restoring the network-wide configuration file on the U2000, upload the configuration
data of NEs with 52TOM boards if any and search for WDM trails. Otherwise, the data of
52TOM board-related fibers and trails is lost on the U2000.
Procedure
Step 1 Log in to the U2000 client. For details, see 1.2.6 Logging In to a U2000 Client.
Step 2 Choose Administration > Back Up/Restore NMS Data > Import/Export Script File
(traditional style) from the main menu or select System Management in Application Center
and choose System > Back Up/Restore NMS Data > Import/Export Script File (application
style) from the main menu.
Step 5 Select the script file type from the Script File Type field.
Step 6 In the Operation Directory List, select the directory where the script file is to be imported is
located.
NOTICE
Upload the configuration script to the imported to the server as the ossuser user. The directory
must be under the $IMAP_ROOT/script directory and can be under the first-level directory
under the oss\server\script directory at most. Otherwise, the directory cannot be selected. If the
$IMAP_ROOT/script directory does not exist, create it manually and assign related
permission. Run the following commands on the server as the root user:
1. # mkdir $IMAP_ROOT/script
2. # chown -R ossuser:ossgroup $IMAP_ROOT/script
3. # chmod -R 750 $IMAP_ROOT/script
Step 7 Select the script file to import from the Import File List.
Step 8 In the Import Subnet List, select the subnets to be imported. All subnets are required to be
selected.
Step 9 Click Apply. The system prompts you twice that the import of the configuration script will result
in data inconsistency between the U2000 and the NE. For the NEs that support synchronization
and are not unconfigured or preconfigured, the U2000 displays the inconsistency mark after the
scripts of these NEs are imported.
NOTE
During script import, the U2000 calculates the number of existing equivalent NEs and imported NE scripts.
l After NE scripts are imported, the number of equivalent NEs managed by each NE Explorer instance
cannot exceed 2,000. Otherwise, the U2000 displays the message Exceeds the maximum
management capability range.
l After NE scripts are imported, the number of gateway NEs managed by each NE Explorer instance
cannot exceed 500. Otherwise, the U2000 reports the alarm GNE_NUM_LIMIT_OVER and displays
the message The number of Gateways of NE Manager nemgr_otn exceeds..
l If the number of network-wide equivalent NEs exceeds the management capability of the NE Explorer
instance, the U2000 displays a failure message and suggests you to add an NE Explorer instance.
Step 10 Click OK. A progress bar appears showing the status of the import.
----End
Follow-up Procedure
After script import, perform the following operations on the U2000 to ensure integrity of NE
and network data on the NMS.
NE Operations
Prerequisites
l Performance data for at least one day exists.
l There is sufficient memory to save the dumped performance data.
Procedure
Step 1 Choose Performance > Performance Dump Management > Manual Dump Performance
Data (traditional style) from the main menu or select Fix-Network Performance in Application
Center and choose Performance Dump Management > Manual Dump Performance Data
(application style) from the main menu.
Step 2 In the Path on Server text box, enter the path to save the dumped performance data.
Step 3 In the Specify End Date area, enter the data to the text box, or click to select the end date
to dump the performance data.
The following figure uses the Windows as an example.
Step 4 In the Specify Granularity area, in the Dump drop-down list, select the dump mode for different
granularities.
Granularities are 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 1 day and all.
The progress bar displays the status of the number of total records and the number of dumped
records.
Step 6 A dialog box is displayed, prompting that the operation succeeds. Click OK.
----End
Prerequisites
l Performance data for at least one day exists.
l There is sufficient memory to save the dumped performance data.
Procedure
Step 1 Choose Performance > Performance Dump Management > Automatic Dump Setting
(traditional style) from the main menu or select Fix-Network Performance in Application
Center and choose Performance Dump Management > Automatic Dump Setting
(application style) from the main menu.
Step 2 In the Path on Server text box, enter the path to save the dumped performance data.
Step 3 In the Granularity-based Lifecycle area, in the Lifecycle(day) text box, enter the number of
days according to the granularity.
Granularities are 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 1 day and all.
Step 4 Select Dump to File after Lifecycle check box to save the dumped performance data from the
database to a file or from one file to another file in Path on Server path.
NOTE
If you do not select the Dump to file after lifecycle check box, the performance data is deleted without
being saved.
Step 5 In the Proportion dumped(%) text box, enter the percentage of performance data to be dumped
according to the granularity.
Granularities are 5 minutes, 10 minutes, 15 minutes, 30 minutes, 1 hour, 1 day and all.
NOTE
For dumping the performance data from database to file, Maximum disk space occupied by data(%)
specifies the percentage of performance data retained in the database.
Step 6 Select Dump to File check box to save the dumped performance data from the database to a file
or from one file to another file mentioned in Path on Server path.
If you do not select the Dump to file check box, the performance data is deleted from the database
without being saved.
----End
Example
l If the number of days in the Lifecycle(day) text box is 2 days for 15 minutes granularity,
the latest 2 days performance data is stored and the remaining data is dumped.
l For performance data dump from database to file, if the performance data for the last 2 days
exceeds the percentage of performance data in Maximum disk space occupied by Data
and if the percentage of performance data in Proportion dumped(%) text box is 10, the
oldest 10 percent performance data is dumped from the database.
This topic describes how to keep data consistency between the U2000 and NEs. When you use
multiple U2000s to manage NEs and modify the NE data on a U2000, the data on other
U2000s becomes inconsistent with the data on NEs. Incorrect configuration data may lead to
misjudgment or misoperation. To manage NEs properly, keep data consistency between the
U2000 and NEs.
Basic Concepts
In the data management of the transmission network, the following basic concepts, which should
be learned first, are involved.
Figure 13-1 shows the relations between data layers.
l NE side data. NE side data is the NE data. It is saved in the DRDB database on the SCC
board of the NE.
l U2000 side data. The U2000 side data contains the data at the NE layer and the data at the
network layer. It is saved in the database of the U2000.
– NE-layer data at the U2000 side. It is the data of each NE on the U2000. The NE-layer
data at the U2000 side should be consistent with the NE-side data. To download the NE
configuration data is to issue the NE-layer data at the U2000 side to the NE. To upload
the NE configuration data is to upload the NE-side data to the U2000 to update the NE-
layer data at the U2000 side.
– Network-layer data at the U2000 side. It is the configuration data at the network layer
on the U2000. The network-layer data at the U2000 side contains the information about
fiber connections, protection subnets, and trails.
Protection subnet
NMS
NM side
NE layer data
NE NE side data
l The basic configuration data management functions include the uploading, downloading,
consistency check, synchronization, duplication, pre-configuration and the initialization of
the NE-layer data at the U2000 side.
– Uploading: For the data that supports uploading (13.7 Configuration Data
Management Information List), the uploading operation will obtain data from NEs
to overwrite the existing NE-layer data on the U2000. For the data that does not support
uploading (13.7 Configuration Data Management Information List), the uploading
operation will not overwrite the existing NE-layer data on the U2000. Besides, the NE
data that is defined by users and exists only on the U2000 will not be deleted during
uploading.
– Downloading: In the case of downloading, the NE-layer data at the U2000 side is issued
to the NE to overwrite the data at the NE side.
– Consistency check: Check whether the NE-layer data at the U2000 side is consistent
with the NE-side data. If inconsistent, you need to synchronize or upload the NE
configuration data.
– Synchronization: Upload the inconsistent data (including the collision data, and the data
that is present at the NE side but absent at the U2000 side) to the NE layer at the
U2000 side. The data that is present both at the U2000 side and the NE side is not
uploaded, and the data that is present at the U2000 side but absent at the NE side is not
deleted.
– Duplication: In the case of NEs that are of the same NE type and of the same NE software
version, if the configuration data of an NE to be configured is the same as that of an NE
already configured, you can configure the NE by duplicating the NE data. Duplicating
the NE data only changes the data at the U2000 side and does not affect the NE-side
data. To make the duplicated data take effect on the NE, you need to perform the
downloading operation.
– Pre-configuration: In the case of pre-configuration, the configuration data of an NE is
only saved on the NE layer at the U2000 side and does not affect the actual configuration
data of the NE. The pre-configuration function is used for the large-scale service
adjustment or expansion.
– Initialization of the NE-layer data at the U2000 side: The NE-layer data at the U2000
side is cleared and the NE becomes unconfigured after the initialization.
l To back up and restore the NE data, refer to 14 Backing Up and Restoring the NE
Data.
NOTE
The RTN series, PTN series, WDM (NA) series and NG WDM series NEs do not support preconfiguration
and the downloading of configuration data. Then, the U2000 provides a more reliable function, that is, the
database package backup and restoration function, to solve the data restoration problem. This is because:
l In the case of configuration data, the NE data is not complete. The complete data, however, can be
obtained by using the database package restoration function.
l During the downloading of configuration data, the U2000 needs to convert the configuration data to
the Qx interface information. Then, the data can be exchanged between the U2000 and the NE.
Therefore, the efficiency is relatively low. In the database package restoration mode, databases are
directly downloaded to the NE, which ensures a high efficiency.
l On the U2000, only one set of configuration data can be saved, but the database package can have
many backup copies. You can select the backup package as needed.
Back up NE
data Required
NE Data Configuration
In the case of the initial configuration for a new equipment, neither the U2000 nor the NE has
the configuration data. Therefore, engineers need to manually configure the data.
1. Use the U2000 to perform the NE configuration on site.
2. Back up the NE database to the SCC board.
3. In the U2000 center, create the NE and upload the NE configuration data.
4. Check whether the data on the U2000 is consistent with that on the NE.
If the pre-configuration is already performed on the U2000, download the configuration data to
the NE.
1. Use the pre-configuration function to complete the NE configuration.
2. Cancel the pre-configuration attribute of the NE and download the NE configuration data.
3. Check whether the data on the U2000 is consistent with that on the NE.
4. Back up the NE database to the SCC board.
NOTICE
Before downloading the data, verify the data in the lab environment to ensure that the data can
be normally downloaded.
NOTE
The RTN series, PTN series, WDM (NA) series and NG WDM series NEs NEs do not support
preconfiguration and the downloading of configuration data. Then, the U2000 provides a more reliable
function, that is, the database package backup and restoration function, to solve the data restoration problem.
This is because:
l In the case of configuration data, the NE data is not complete. The complete data, however, can be
obtained by using the database package restoration function.
l During the downloading of configuration data, the U2000 needs to convert the configuration data to
the Qx interface information. Then, the data can be exchanged between the U2000 and the NE.
Therefore, the efficiency is relatively low. In the database package restoration mode, databases are
directly downloaded to the NE, which ensures a high efficiency.
l On the U2000, only one set of configuration data can be saved, but the database package can have
many backup copies. You can select the backup package as needed.
NE Software Upgrade
When a software error occurs on a running NE or software codes are expanded for new services,
the NE software needs to be upgraded.
Service Expansion
When the service capability of the live network needs to be expanded, perform the following
operations:
1. Upload the NE database.
2. Back up the U2000 database.
3. Perform the expansion operation.
4. Check whether the data on the U2000 is consistent with that on the NE.
5. Back up the NE database to the SCC board.
Routine Maintenance
1. In the case of the NE configuration change, such as the service adjustment or rerouting,
back up the NE database immediately after the relevant operation is complete.
2. If the NE data is configured by using a different network NM (such as the U2000), you
need to synchronize the data on the U2000 after the configuration is complete.
3. Perform the monthly (recommended) consistency check for all NEs. In the case of any data
inconsistency, synchronize or upload the data.
4. Back up the NE database periodically. For the RTN series, PTN series, NG WDM series,
WDM (NA) series NEs and the OSN series NEs that is enabled with the ASON feature,
the database package backup mode must be adopted for the database backup.
Troubleshooting
When the database files are lost due to the SCC board replacement or NE anomalies, restore the
NE data in time.
Routine
Construct NMS data NMS software upgrade Troubleshooting
maintenance
Data construction enables you to monitor running status of NEs and the entire network on the
U2000.
1. Upload the NE configuration data to form the NE-layer data at the U2000 side.
2. Create fibers and cables.
3. Based on the NE-layer data at the U2000 side and the fiber connection information, search
the protection subnets to form the protection subnet information in the network-layer data
at the U2000 side.
4. Based on the NE-layer data at the U2000 side, the fiber connection information and the
protection subnet information, search the paths to form the path information in the network-
layer data at the U2000 side.
Before the U2000 software upgrade, you must make sure that the data on the U2000 is consistent
with the that on the NE. The U2000 software upgrade is performed as follows:
1. Export the network-wide configuration files for the data restoration after the software
upgrade.
2. Upgrade the U2000 software.
3. Based on the configuration upgrade wizard, upload the NE configuration data. Import the
network-wide configuration files and search the protection subnets and trails again.
Routine Maintenance
In daily maintenance, back up the U2000 data periodically and clear unnecessary databases to
arrange the database space in time.
1. After the important configuration data changes, backup the U2000 database immediately.
2. Back up the U2000 database periodically in a monthly (recommended) manner.
Troubleshooting
When the U2000 becomes abnormal due to the U2000 fault, computer hardware fault, or other
causes, restore the U2000 data in time.
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
l Configuration data consistency check between the U2000 and NEs does not affect the
configuration data on NEs and the U2000.
l To ensure that the U2000 properly manages the NEs, it is recommended that you run this
function on a monthly basis to keep the consistency of configuration data in NEs and the
U2000 server.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
The NE Configuration Data Management window is displayed.
Step 2 In the NE Configuration Data Management window, select one or multiple NEs in the Object
Step 3 Select one or more NEs from the NE Configuration. Click Check Consistency. Alternatively,
right-click the NE and select Check Consistency from the shortcut menu.
Step 5 Click Detail in the Operation Result dialog box to check the consistency information.
NOTE
After checking consistency information, you can click Save As to save inconsistent information to a file.
----End
Reference Standard
The check results indicate that the configuration data on NEs is the same as that on the U2000.
Follow-up Procedure
If the result indicates an inconsistency in the configuration data between the NE and the
U2000, you need to upload or download the data to achieve consistency. Please refer to 13.5
Uploading NE Configuration Data or 13.6 Downloading NE Configuration Data.
Prerequisites
l You are an NMS user with Guests authority or higher.
l The NE is in the unsynchronized state.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
Context
l If the configuration data is not synchronous between the U2000 and the NE, the NE icon
has a sign.
l If another U2000 modifies the NE data when the current U2000 uploads or synchronizes
data, asynchronous information will be displayed in the NE Config Sync Info dialog box
of the current U2000. Upload or synchronize NE data again to eliminate the asynchronous
information.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
The NE Configuration Data Management window is displayed.
Step 2 In the Object Tree, select one or more NEs, and click .
The NEs you select are shown in the NE Configuration.
Step 3 Select an NE that is in the Unsynchronized state, and then click Sync Info.
Step 4 In the NE Config Sync Info dialog box, click Query to view the details of the configuration
items.
----End
Prerequisites
l You are an NMS user with Operator Group authority or higher.
l For the Router series, Switch series, PTN 6900 series, Access series and Security NEs, the
SNMP and Telnet/STelnet parameters must be correct.
l For the Router series, Switch series, PTN 6900 series, Access series and Security NEs, the
FTP/SFTP/TFTP service has been configured and the xFTP service has been started and
operated.
Context
l When an NE is managed by several U2000s, the NE will fail to be added and the NE
configuration data synchronization will also fail.
l For the NEs that support synchronization and are not unconfigured or preconfigured, the
U2000 displays the inconsistency mark after the scripts of these NEs are imported.
l For the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series (except
PTN 6900 series) and marine series NEs, if data on the U2000 is inconsistent with data on
NEs. The sign will be displayed on NE icons.
l For switch series NEs, enable the privilege function and set the privilege level and password
when setting Telnet/STelnet parameters before synchronizing Layer 2 VLAN data.
l NE configuration data synchronization does not synchronize resource information in the
performance monitoring instance. If the resource information needs to be synchronized,
perform resource synchronization in the Performance Monitoring Management window.
NOTE
When data on NEs in the right pane of the Synchronize NE Configuration Data window are being
synchronized:
l You can select NEs in the right pane to synchronize data.
l You can select NEs from the Object Tree to synchronize data.
l You can select NEs from the Main Topology to synchronize data.
l You can stop the data synchronization on one or multiple NEs.
l You can delete NEs only after the data is synchronized.
Procedure
l Method 1
1. Choose Configuration > Sychronize NE Configuration Data (traditional style)
from the main menu or select Fix-Network NE Configuration in Application
l You can also choose one or more NEs from the navigation tree and click .
l You can filter synchronization information by specifying the following filter criteria: NE,
NE Type, NE Address, Synchronization Type, Synchronization Status,
Synchronization Result, and Remaining Time. Router, switch, security, and VMF NEs
do not support some filter criteria such as Synchronization Type, Synchronization
Status, Synchronization Result, and Remaining Time.
3. Select one or multiple unsynchronized NEs, click the Synchronize or right-click an
NE and choose Synchronize from the shortcut menu. The U2000 begins to
synchronize the data.
NOTE
l Buttons in the Option column apply to routers, switches, metro service platforms, security
gateways, service interception gateways NEs.
l Click the buttons in the Option column and select the advanced attributes to be
synchronized.
l Data synchronization on access NEs initiated by another client can be stopped temporarily.
l Method 2
NOTE
This method applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
1. In the Main Topology, select an NE that is marked with . Right-click the NE and
choose Synchronize NE Configuration Data from the shortcut menu.
l Method 3
NOTE
This method applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
1. Choose Configuration > NE Configuration Data Management (traditional style)
from the main menu or select Fix-Network NE Configuration in Application
Center and choose Configuration > NE Configuration Data Management
(application style) from the main menu.
2. Select one or multiple NEs from the Object Tree and click .
3. Select one or multiple unsynchronized NEs, click the Synchronize or right-click an
NE and choose Synchronize from the shortcut menu.
4. Click OK. The U2000 begins to synchronize the data.
5. Click Close in the Operation Result dialog box.
l Method 4
NOTE
This method applies to the Router series, Switch series and Security NEs.
1. Right-click an NE in the Main Topology and choose NE Explorer from the shortcut
menu.
2. In the NE Explorer, after querying the services information, click the Synchronize
or right-click a record and choose Synchronize from the shortcut menu.
3. Click OK in the Confirm dialog box.
In the Synchronize Feature dialog box, the U2000 begins to synchronize the data.
4. After data synchronization is complete, click Close to exit.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l Applies to the MSTP series, WDM series, WDM (NA) series, RTN series, PTN series
(except PTN 6900 series) and marine series NEs.
l The U2000 communicates with NEs successfully.
Context
When you upload NE configuration data, fiber data on NEs is automatically uploaded to the
U2000. Delete fibers that exist on the U2000 only from the U2000 and created fibers on NEs
only on the U2000.
Procedure
l Method 1
1. Choose Configuration > NE Configuration Data Management (traditional style)
from the main menu or select Fix-Network NE Configuration in Application
Center and choose Configuration > NE Configuration Data Management
(application style) from the main menu.
2. Select one or more NEs from the Object Tree and click .
3. Select one or more NEs whose Logged in is Yes from the NE Configuration.
4. Optional: For NEs whose Logged in is No. Choose Administration > NE Security
Management > NE Login Management (traditional style) from the main menu or
select Security Management in Application Center and choose NE Security > Fix-
Network NE > NE Login Management (application style) from the main menu. In
the window that is displayed, log in to the NEs.
NOTE
If the NEs cannot be logged in to, adjust the DCN between the NEs and the U2000 to ensure
proper communication, and then upload the NE data.
5. Click Upload. Alternatively, right-click and select Upload from the shortcut menu.
For NEs whose Logged in is No, the NE Configuration Data Management window is
displayed, but the NE data cannot be uploaded. You can log in to the NE based on the step 4
of the method 1, and then upload the NE data.
3. Click OK in the Confirm dialog box.
4. Click Close in the Operation Result dialog box.
----End
Follow-up Procedure
After uploading, perform a consistency check. For details on how to perform a consistency check,
please refer to 13.2 Checking Consistency of Configuration Data Between an NE and the
U2000.
Prerequisites
l The U2000 communicates with NEs successfully.
l You are an NMS user with Maintenance Group authority or higher.
l This operation applies to the MSTP and WDM series NEs.
Background Information
NOTICE
Downloading NE configuration data can interrupt the services.
l In scenarios of new deployment and where NE data is lost, you need to use the
Downloading NE Configuration Data function to create or restore NE data. However,
this method only restores the services and core configuration data on the NE.
l MSTP and WDM NEs support the downloading of configuration data, but NG WDM NEs
do not support the downloading of configuration data.
l When you download the NE configuration data from the U2000 to the NE, the U2000 first
initializes the NE, and then downloads the configuration data to the NE. If you cancel the
download before it is complete, the configuration data may be incomplete.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
Step 2 In the Object Tree, select one or more NEs and click .
Step 3 Select one or more NEs whose login status is Yes from the NE Configuration.
Step 4 Optional: For NEs whose login status is No, choose Administration > NE Security
Management > NE Login Management from the main menu. In the window that is displayed,
log in to the NEs.
NOTE
If the NEs cannot be logged in to, adjust the DCN between the NEs and the U2000 to ensure proper
communication, and then upload the NE data.
Step 5 Click Download. Alternatively, right-click and choose Download from the shortcut menu.
The download function supports only some types of NEs. If you select some unsupported NEs, the
Operation Result dialog box will be displayed after the download is complete for the supported NEs, then
you can click Details to view the result. For these unsupported NEs, you can click NE Data Backup/
Restoration in the Operation Result dialog box, the U2000 switches to the NE Data Backup/
Restoration window, you can click Recover to back up configuration data of these unsupported NEs for
the same purpose.
----End
Follow-up Procedure
After uploading, perform a consistency check by referring to 13.2 Checking Consistency of
Configuration Data Between an NE and the U2000
The following is the configuration data management information list for the transport domain.
Consiste Data
Function Uplo Downl
Function ncy Replicat
Category ad oad
Check ion
Virtual NE ID N N N N
Basic virtual Virtual NE name N N N N
NE
configuration Card installed in a virtual NE N N N Y
Remarks N N N Y
Card type
definition for Card type definition N N N N
a virtual NE
NE name Y Y Y N
NE location N N N N
NE remarks Y Y N Y
Serious overvoltage Y Y Y Y
Common overvoltage Y Y Y Y
Serious undervoltage Y Y Y Y
Consiste Data
Function Uplo Downl
Function ncy Replicat
Category ad oad
Check ion
Use or not Y Y Y Y
Working mode Y Y Y Y
Corresponding input Y Y Y Y
Alarm mode Y Y Y Y
CAU interface N Y N N
FAN interface N N N N
F1 data port Y Y Y Y
Conference call Y Y Y Y
OHP interface
Setting the broadcast data port Y Y Y Y
COMM Y Y Y Y
Advanced ACL N N N N
NE security
Syslog N N N N
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
Tributary loopback Y N N N
Path protection Y Y Y Y
Path impedance N N N N
Retiming mode Y Y Y Y
PDH interface
External retiming clock source Y Y Y Y
CRC4 Y Y Y Y
E1 frame structure Y Y Y Y
T1 frame structure Y Y Y Y
J2 byte to be transmitted Y Y Y Y
J2 byte to be received Y Y Y Y
J2 byte received N N N N
Path name N N N N
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
VC4 loopback Y N N N
Laser-in-position status N N N N
VC3 loopback Y N N N
VC12 loopback Y N N N
DCC/GCC mode Y Y Y Y
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
J0 byte to be transmitted Y Y Y Y
Regenerator
section J0 byte to be received Y Y Y Y
overhead
J0 byte received N N N N
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
V5 byte to be transmitted
N N N N
(VC12 path)
V5 byte to be transmitted
Y Y Y Y
(VC12 path; EFGS)
Synchronization status N N N N
Clock subnet Y Y Y Y
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
Clock ID status Y Y Y Y
2M phase-locked source
Y Y Y Y
priority list
Clock binding Y Y Y Y
2M PRBS test N N N N
Test function Frame overhead information
N N N N
management
PRBS test N N N N
Hold-off time Y Y Y Y
Service group Y Y Y Y
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
Service type Y Y Y Y
Current status N N N N
Overhead
Overhead service Y Y Y Y
service
Hold-off time N N N N
Revertive mode N N N N
SNC service
attribute of a Monitoring condition N N N N
virtual NE
Service group N N N N
Service type N N N N
Current status N N N N
Hold-off time Y Y N Y
Multi-trail Switching WTR time Y Y N Y
service
attribute Revertive mode Y Y N Y
Monitoring condition Y Y N Y
Logical system ID Y Y Y Y
Name Y Y Y Y
Type Y Y Y Y
STM level Y Y Y Y
Service direction Y Y Y Y
Node type Y Y Y Y
Protection type Y Y Y Y
Slot mapping Y Y Y Y
MS westbound node ID Y Y Y Y
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
MS eastbound node ID Y Y Y Y
MS maximum node ID Y Y Y Y
MS SD enabling flag Y Y Y Y
Configuration of MS
N Y N N
suppression on all spans
Logical system ID N N N Y
Name N N N Y
Type N N N Y
STM level N N N Y
Topology type N N N Y
Fiber/Cable number N N N Y
Service direction N N N Y
MS local node ID N N N Y
MS westbound node ID N N N Y
MS eastbound node ID N N N Y
MS SD enabling flag N N N Y
Switching mode Y Y Y Y
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
Slot mapping Y Y Y Y
MS SD enabling flag Y Y Y Y
Protection group ID Y Y Y Y
Active card Y Y Y Y
Equipment 1
Standby card Y Y Y Y
+1 protection
Service level Y Y Y Y
Protection type Y Y Y Y
Protection group ID Y Y Y Y
Enabled or not Y Y Y Y
Revertive time Y Y Y Y
TPS
Protection unit ID Y Y Y Y
protection
Protection unit slot Y Y Y Y
Switching/Lock status N N N N
64 kbit/s
64 kbit/s service Y Y Y Y
service
Equipment
TDA feeding choice Y Y Y Y
maintenance
Basic
Dynamic port Y Y Y Y
configuration
Wavelength
SF64 wavelength adjustment N N N N
adjustment
MCPPS
MCPPS protection Y Y Y Y
protection
Protection group ID Y Y Y Y
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
Switching/Lock status N N N N
NE Y Y N N
Time zone Y Y N N
Start time Y Y N N
End time Y Y N N
Single-port
multiple Enabling the single-port
Y Y Y Y
multiplex multiple multiplex section
section
Group ID Y Y Y Y
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
Multiplex
Check the standby channel Y Y Y Y
section
Protection group ID Y Y Y Y
Working mode Y Y Y Y
Revertive mode Y Y Y Y
WTR time Y Y Y Y
Protection group ID Y Y Y Y
Working mode Y Y Y Y
Revertive mode Y Y Y Y
WTR time Y Y Y Y
V-UNI group Y N Y Y
Service QoS Y N Y Y
MSTP+packet
Ethernet OAM Y N Y Y
feature
Port management: basic port Y N Y Y
Port OAM Y N Y Y
Consist Data
Function Uplo Downl
Function ency Replica
Category ad oad
Check tion
Static tunnel Y N Y Y
Tunnel OAM Y N Y Y
PW management Y N Y Y
QinQ link Y N Y Y
MCSP Y N Y Y
MC-LAG Y N Y Y
MS_PW Y N Y Y
VLAN_VPORT Y N Y Y
BFD Y N Y Y
VRRP Y N Y Y
L3VPN Y N Y Y
DHCP_REALY Y N Y Y
L2VPN Y N Y Y
Tunnel Y N Y Y
TUNNEL_APS Y N Y Y
ARP Y N Y Y
CES Y N Y Y
Overhead Y N Y Y
NOTE
The service mirroring function complies with universal standards followed by the telecommunication
industry. When this function is enabled, other devices or instruments that receive mirrored service packets
may need to analyze some information of end users' communications based on the requirements for
operation and maintenance. Huawei alone is unable to collect or save the content of users' communications.
It is suggested that you activate the interception-related functions based on the applicable laws and
regulations in terms of purpose and scope of usage. You are obligated to take considerable measures to
ensure that the content of users' communications is fully protected when the content is being used and
saved.
Consiste Data
Function Downlo
Function Upload ncy Replicat
Category ad
Check ion
E-LAN/E-LINE/E-
Ethernet service Y N Y Y
AGGR
1588 clock
1588 clock service Y N Y Y
service
Basic port Y N Y Y
Serial port Y N Y Y
LAG Y N Y Y
MLPPP Y N Y Y
Port management
Microwave port Y N Y Y
MCSP Y N Y Y
ADSL2+ Y N Y Y
MCLAG Y N Y Y
Consiste Data
Function Downlo
Function Upload ncy Replicat
Category ad
Check ion
PW management PW management Y N Y Y
PW OAM PW OAM Y N Y Y
IP tunnel IP tunnel Y N Y Y
TPS TPS Y N Y Y
Card 1+1
Card 1+1 protection Y N Y Y
protection
Basic
Basic configuration Y N Y Y
configuration
NE Time NE Time
Y N Y Y
Synchronization Synchronization
Overhead Overhead
Y N Y Y
Management Management
MPLS LDP
MPLS LDP tunnel Y N Y Y
tunnel
PW APS Y N Y Y
MC PW APS Y N Y Y
PW protection
group PW APS slave
Y N Y Y
protection pair
PW redundancy Y N Y Y
MS PW MS PW Y N Y Y
ACR clock
ACR clock service Y N Y Y
service
Consiste Data
Function Downlo
Function Upload ncy Replicat
Category ad
Check ion
TOP clock
TOP clock service Y N Y Y
service
DS domain DS domain
Y N Y Y
management management
IP line IP line Y N Y Y
LMSP LMSP Y N Y Y
802.1X/RADIUS 802.1X/RADIUS
Y N Y Y
Authentication Authentication
MPLS_TP
MPLS_TP Shared
Shared Protection
Protection Ring Y N Y Y
Ring
Management
Management
BFD
BFD Management Y N Y Y
Management
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Monitor wavelength Y Y Y Y
Board receiving/transmitting
Y N N N
attribute
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Laser status Y N N N
Input power N N N N
Output power N N N N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Service type Y Y Y Y
Nominal gain Y Y N Y
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Wavelength ID received Y N N N
Wavelength ID to be received Y Y Y Y
Service rate Y Y Y Y
LPT enabling Y Y Y Y
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Input status N N N N
Output status N N N N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
FEC mode Y Y Y Y
FE transparent transmission Y Y Y Y
FC distance expansion N N N N
J0 byte to be received Y Y Y Y
J0 byte received Y N N N
J0 byte to be transmitted Y Y Y Y
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
1-byte J0 to be transmitted Y Y Y Y
1-byte J0 to be received Y Y Y Y
SDH
1-byte J0 received N N N N
overhead
64-byte J0 to be received Y Y Y Y
64-byte J0 received N N N N
Revertive mode Y Y Y Y
WTR Y Y Y Y
Lock status Y Y Y Y
Clock source ID Y Y Y Y
WTR status N N N N
Revertive mode Y Y Y Y
Revertive time Y Y Y Y
Optical line
Working channel N N N N
protection
Switching status N N N N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Revertive flag Y Y Y Y
Optical Revertive time Y Y Y Y
channel
protection Switching status N N N N
Protection type Y Y Y Y
Revertive mode Y Y Y Y
WTR time Y Y Y Y
1:N optical
channel Remaining WTR time N N N N
protection
SD switching enabling flag Y Y Y Y
Protection priority Y Y Y Y
Protection group ID Y Y Y N
Band Y Y Y N
Detection board Y Y Y N
Raman amplifier Y Y Y N
IPA status Y Y Y N
IPA (APR)
protection Restart mode Y Y Y N
pair
Off period Y Y Y N
On period Y Y Y N
Testing period Y Y Y N
Start latency Y Y N N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Link ID Y Y Y N
Node type Y Y Y N
Node ID Y Y Y N
Working mode Y Y Y N
Reference unit Y Y Y N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Link ID Y Y Y N
Node ID Y Y Y N
Direction Y Y Y N
Band type Y Y Y N
Number of nodes Y Y Y N
Monitored NE N N N N
Working mode Y Y Y N
Reference unit Y Y Y N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Group ID Y Y Y Y
Protection type Y Y Y Y
Revertive mode Y Y Y Y
Revertive time Y Y Y Y
Switching mode Y Y Y Y
Wavelength
protection Switching time Y Y Y Y
group
Active path Y Y Y Y
SD enabling Y Y Y Y
Slot mapping Y Y Y Y
Board mapping Y Y Y Y
SD event N N N N
Revertive mode Y Y Y Y
WTR time Y Y Y Y
SD enabling flag Y Y Y Y
WXCP
service SD trigger condition Y Y Y Y
attribute
Current status N N N N
Trail status N N N N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
OTU mapping Y Y Y N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
OTU mapping Y Y Y N
Wavelength pass-through/blocking
OCCE Y Y Y N
flag
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
Wavelength Y N N N
Adding a mapping N N N N
Wavelength
Deleting a mapping N N N N
lockout
Calculating the OTU N N N N
Application N N N N
Compensation value N N N N
Dispersion Fine-tune mode Y Y Y Y
compensatio
n OTU Y Y Y Y
E1 cross-
E1 cross-connection Y Y Y Y
connection
Object N N N N
Layer N N N N
Source mode Y Y Y Y
Sink mode Y Y Y Y
TTI to be transmitted Y Y Y Y
TTI to be received Y Y Y Y
TTI received N N N N
DEG threshold Y Y Y Y
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
LCK insertion Y Y Y Y
Protection type Y Y Y Y
Revertive mode Y Y Y Y
WTR time Y Y Y Y
Hold-off time Y Y Y Y
Protection priority Y Y Y Y
Fiber
Intra-NE fiber Y N N N
uploading
Port Y N N N
Logical board Y N N N
SFP
Physical board Y N N N
inventory
Serial number Y N N N
CLEI Y N N N
Consist Data
Function Upl Dow
Function ency Replic
Category oad nload
Check ation
BOM Y N N N
Manufacture date Y N N N
Remarks Y N N N
User ID Y N N N
Manufacturer Y N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Monitor wavelength Y N N N
Laser status Y N N Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Input power N N N N
Output power N N N N
Input status N N N N
Output status N N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Service type N N N N
Wavelength ID N N N N
Nominal gain N N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
WDM ID received N N N N
WDM ID to be received N N N N
Service rate N N N N
Port loopback Y N N N
Laser status Y N N Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
1-byte J0 to be transmitted N N N N
1-byte J0 to be received N N N N
SDH
1-byte J0 received N N N N
overhead
64-byte J0 to be received N N N N
64-byte J0 received N N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Revertive mode N N N N
WTR N N N N
Lock status N N N N
Clock source ID N N N N
WTR status N N N N
Detection board Y N Y N
Raman amplifier Y N Y N
Enabling flag Y N Y N
Restart mode Y N Y N
IPA (APR) Off period Y N Y N
protection
pair On period Y N Y N
Testing period Y N Y N
Start latency Y N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Link ID Y N Y N
Subrack ID Y N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Group ID Y N Y Y
Protection type Y N Y Y
Slot mapping Y N Y Y
Revertive mode Y N Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
OTU mapping N N N N
Cross-connection level Y N Y Y
Service type Y N Y Y
Electrical Direction Y N Y Y
cross-
Source channel Y N Y Y
connection
managemen Sink channel Y N Y Y
t
Activation status Y N Y Y
Service source Y N Y Y
Service sink Y N Y Y
Protection type Y N Y Y
SNCP Level Y N Y Y
managemen
t Revertive mode Y N Y Y
WTR time Y N Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
SD enabling Y N Y Y
SD trigger condition Y N Y Y
Level Y N N Y
WTR Y N N Y
Span ID Y N N Y
Hold-off time Y N N Y
Cross-connection level Y N N N
Service type Y N N N
ASON
electrical Direction Y N N N
cross-
Source channel Y N N N
connection
managemen Sink channel Y N N N
t
Activation status Y N N N
Service source Y N N N
Service source Y N N N
Service sink Y N N N
Protection type Y N N N
Level Y N N N
Revertive mode Y N N N
ASON
SNCP WTR Y N N N
managemen
t Delay time of the working channel Y N N N
SD enabling flag Y N N N
SD triggering condition Y N N N
Service source Y N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Master/ Subrack ID Y N Y Y
slave
subrack
managemen Subrack name Y N Y Y
t
Fiber
Intra-NE fiber Y N N N
uploading
Port Y N N N
Logical board Y N N N
Physical board Y N N N
Serial number Y N N N
CLEI Y N N N
SFP
BOM Y N N N
inventory
Manufacture date Y N N N
Remarks Y N N N
User ID Y N N N
Manufacturer Y N N N
Physical Clock N N N N
PTP Clock N N N N
Board-Level Protection N N N N
NE shelf type Y Y Y
NE location Y Y Y
NE memo Y Y Y
NE timezone Y Y Y
NE auto-configuration status Y Y Y
NE MAC address Y Y Y
NE IP address Y Y Y
Subrack name Y Y Y
Subrack memo Y Y Y
Subrack state Y Y Y
Card
Logical unit type provisioned by user Y Y Y
installation
Payload
Payload type of LWM client port Y Y Y
type
Band type Y Y Y
Automatic adjustment Y Y Y
Monitoring flag Y Y Y
Band type Y Y Y
IPA
Detection card Y Y Y
Shutdown card Y Y Y
Enabling flag Y Y Y
Restart mode Y Y Y
Off duration Y Y Y
On duration Y Y Y
Testing duration Y Y Y
Restart pulse Y Y Y
Optical
wavelength
WTR time Y Y Y
shared
protection
Revertive mode Y Y Y
Band type Y Y Y
WDM From Y Y Y
service
configuratio To Y Y Y
n
Protection path Y Y Y
Working path Y Y Y
Revertive mode Y Y Y
WTR time Y Y Y
Optical cross ID Y Y Y
Band type Y Y Y
Parent cross ID Y Y Y
State of cross Y Y Y
Band type Y Y Y
Optical
Parity attribute of the OXC logic group Y Y Y
cross-
connection State of the OXC logic group Y Y Y
power
equalization TID of the MCA card which is used to
check the power equalization of the Y Y Y
wavelength
Fiber
Intra-NE fiber Y N N
Uploading
Consist
Function Uploa Synchro
Function ency
Category d nize
Check
Type Y Y Y
Name Y Y Y
Location Y Y Y
Remarks N N N
Subrack type Y Y Y
Gateway type Y Y Y
Timezone Y Y Y
Auto-card installation Y Y Y
MAC address Y Y Y
IP address Y Y Y
Subnet mask Y Y Y
Gateway N N N
Buzzer on-off Y Y Y
Country code Y Y Y
Card
Input optical power N N N
parameter
Consist
Function Uploa Synchro
Function ency
Category d nize
Check
Input status N N N
Output status N N N
Port name N N N
Loopback N N N
Service type Y N Y
Laser status N N N
Using status Y Y Y
Alarm mode Y Y Y
Housekeepi
Alarm severity Y Y Y
ng
Control type N N N
Control state Y Y Y
Consist
Function Uploa Synchro
Function ency
Category d nize
Check
TTI to be transmitted N N N
TTI to be received N N N
TTI received N N N
Trace J0 mode N N N
J0 received N N N
Band Y Y Y
Detection card Y Y Y
IPA (APR)
protection Shut off card Y Y Y
pair
Enabling flag Y Y Y
Restart mode Y Y Y
Consist
Function Uploa Synchro
Function ency
Category d nize
Check
On duration (s) Y Y Y
Testing period Y Y Y
Band Y Y Y
Automatic adjustment Y Y Y
Monitoring flag Y Y Y
Link ID Y Y Y
Subrack ID N N N
Consist
Function Uploa Synchro
Function ency
Category d nize
Check
Reference unit Y Y Y
Group ID Y Y Y
Protection type Y Y Y
SD enabling Y Y Y
Activation status Y Y Y
Direction Y Y Y
Consist
Function Uploa Synchro
Function ency
Category d nize
Check
Adjustment mode Y Y Y
Remarks Y Y Y
Cross-connection level Y Y Y
Service type Y Y Y
Electrical
cross- Direction Y Y Y
connection Source slot/port/channel Y Y Y
management
Sink slot/port/channel Y Y Y
Activation status Y Y Y
Service source Y Y Y
Service sink Y Y Y
Service type Y Y Y
Protection type Y Y Y
Level Y Y Y
SD enabling Y Y Y
Direction Y Y Y
Remarks Y Y Y
Subrack ID Y Y Y
Master/
Slave Subrack name Y Y Y
subrack Subrack FIC Y Y Y
management
Subrack type Y Y Y
Fiber
Intra-NE fiber Y N N
uploading
Port Y N N
SFP
Logical board Y N N
inventory
Physical board Y N N
Consist
Function Uploa Synchro
Function ency
Category d nize
Check
Serial number Y N N
CLEI Y N N
BOM Y N N
Manufacture date Y N N
Remarks Y N N
User ID Y N N
Manufacturer Y N N
The service mirroring function complies with universal standards followed by the telecommunication
industry. When this function is enabled, other devices or instruments that receive mirrored service packets
may need to analyze some information of end users' communications based on the requirements for
operation and maintenance. Huawei alone is unable to collect or save the content of users' communications.
It is suggested that you activate the interception-related functions based on the applicable laws and
regulations in terms of purpose and scope of usage. You are obligated to take considerable measures to
ensure that the content of users' communications is fully protected when the content is being used and
saved.
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Laser state N N N N
Ethernet
user
User ID and name Y Y Y Y
managemen
t
TAG flag Y Y Y Y
VLAN ID Y Y Y Y
User priority Y Y Y Y
User ID Y Y Y Y
Flow control Y Y Y Y
Encapsulation protocol Y Y Y Y
PPT enabling Y Y Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Scramble Y Y Y Y
CRC reverse Y Y Y Y
LPT enabling Y Y Y Y
Stack VLAN ID Y Y Y Y
LAPS/HDLC/GFP encapsulation
Y Y Y Y
parameter
Default VLAN ID Y Y Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
MAC loopback Y N N N
PHY loopback Y N N N
Laser switch Y N N N
Forwarding priority Y Y Y Y
Non-auto-negotiation mode Y Y Y Y
Port type Y Y Y Y
Entrance detection Y Y Y Y
QinQ enabling Y Y Y Y
Default QinQ ID Y Y Y Y
QinQ priority Y Y Y Y
Traffic threshold Y Y Y Y
Tag Y Y Y Y
Loopback detection Y Y Y Y
Port blocking Y Y Y Y
Port mirroring N N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Tag Y Y Y Y
Entrance detection Y Y Y Y
P/PE attribute Y Y Y Y
Encapsulation protocol Y Y Y Y
Scramble Y Y Y Y
CRC reverse Y Y Y Y
Point-to-point attribute Y Y Y Y
QinQ enabling Y Y Y Y
Default QinQ ID Y Y Y Y
QinQ priority Y Y Y Y
QinQ type Y Y Y Y
Port enabling Y Y Y Y
Port priority
(ATTR_ETHOVERSDH_MAC_
PRIMODE) Y Y Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Port priority
(ATTR_ETHOVERSDH_VCG_
PRIMODE) Y Y Y Y
LCAS mode Y Y Y Y
Working mode Y Y Y Y
Non-auto-negotiation mode Y Y Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
VLAN table N N Y Y
Ethernet port N N Y N
Activated or not N N Y N
LPT direction N N Y N
VLAN unicast Y Y Y Y
New FDB
MAC address disabling Y Y Y Y
Aging time Y Y Y Y
CAR information Y Y Y Y
CoS information Y Y Y Y
New QoS
Flow shaping information Y Y Y Y
Flow information Y Y Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Shaping parameter N N Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Node name N N Y Y
WTR time N N Y Y
Restoration time N N Y Y
Point-to-point attribute Y Y Y Y
Bridge parameter Y Y Y Y
Port role N N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
GARP
GARP protocol management
protocol
(including management of GVRP, Y Y Y Y
managemen
GMRP, and GMRP in VLAN)
t module
CAR configuration Y Y Y Y
EPL/EVPL/transit service
Y Y Y Y
configuration
EPLn/EVPLn service
Y Y Y Y
configuration
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Flow classification Y Y Y Y
Miscellaneo
us Other attribute management of the
N N N N
bridge
Card IP address Y Y Y Y
Protection mode Y Y Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Node name Y Y Y Y
RPR node ID Y Y Y Y
RPR enabling Y Y Y Y
RPR node ID N N N N
RPR direction N N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
LAG information N N N N
LAG priority N N N Y
Link group ID N N Y N
Main port N N Y N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
LAG record N N N Y
LAG record N N Y N
Service
N N N N
mirroring Ethernet service mirroring
Service ID N N Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Port ID N N Y Y
Port type N N Y Y
VLAN ID N N Y Y
MP level (0-7) N N Y Y
MP type N N Y Y
MP direction N N Y Y
CC sending period N N Y Y
LB timeout period N N Y Y
LT timeout period N N Y Y
CC activation status N N Y Y
Unidirectional operation Y Y Y Y
Loopback status N N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
MP Y Y Y Y
MP attribute Y Y Y Y
Tunnel type Y Y Y Y
Inbound port ID Y Y Y Y
Outgoing label Y Y Y Y
Next-hop IP address Y Y Y Y
Static ARP
IP address Y Y Y Y
entry
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
configuratio
MAC address Y Y Y Y
n
VLAN
VLAN Group N N N N
Group
Ethernet
Remote Ethernet Remote Maintenance
N N N N
Maintenanc Point
e Point
Distributed
Board- Distributed Board-Level
N N N N
Level Protection
Protection
Ethernet
Ring Ethernet Ring Protection
N N N N
Protection Switching
Switching
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Port type Y Y Y Y
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Activation status Y N N N
UPC/NPC enabling/disabling Y Y Y Y
Loopback Y N N N
VC trunk
managemen VC trunk bandwidth binding Y Y Y Y
t
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
Port name N N N N
Laser switch N N N N
Consist Data
Function Uploa Dow
Function ency Replica
Category d nload
Check tion
NE LLID Y Y Y Y
J0 byte to be transmitted Y Y Y Y
J0 byte to be received Y Y Y Y
J0 byte received N N N N
J1 byte to be transmitted Y Y Y Y
ATM port
J1 byte to be received Y Y Y Y
overhead
J1 byte received N N N N
C2 byte to be received Y Y Y Y
C2 byte to be transmitted Y Y Y Y
C2 byte received N N N N
Consiste Data
Function Downlo
Function Upload ncy Replicati
Category ad
Check on
Intelligent
Channel status refreshing N N N N
trail
OSPF authentication
Y N Y Y
parameter
SDH ASON
disaster RSVP authentication
Y N Y Y
recovery parameter
Consiste Data
Function Uploa Down
Function ncy Replicati
Category d load
Check on
Severity N N N N
Alarm masking N N N N
Alarm reversion N N N N
Alarm insertion N N N N
Consiste Data
Function Uploa Down
Function ncy Replicati
Category d load
Check on
This topic describes how to back up and restore NE data to ensure NE data security. Backing
up and restoring NE data apply to MSTP series, WDM series, WDM (NA) series, RTN series,
PTN series (except PTN 6900 series) and marine series NEs.
This topic describes how to restore the NE database from the CF card. When the database file
is lost due to NE maintenance or NE fault, you can restore the NE database from the database
file that is backed up on the CF card.
Back up the NE database to Flash database on the SCC NE fault recovery scenario
the SCC board/Restore the board such as data loss for the
NE database from the SCC DRDB database of an NE
board control board, NE power-off,
or replacement of an NE
control board
l Backs up the NE
configuration data in the
DRDB database of the
control board (no CF card
is configured) to the flash
database.
During the restoration,
after a warm or cold reset
on the control board, the
control board reads the
configuration from the
flash database and issues
the configuration to other
boards.
l NE data can also be
backed up to the flash
memory of the control
board to ensure data
security in case of NE
power-off within half an
hour after NE
configuration
modification.
Refer to 14.2 Backing Up
the NE Database to the
SCC Board or14.5
Restoring the NE Database
From the SCC Board.
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l You have logged in to the NE as an NE user with system level authority.
l Backing up and restoring NE data apply to MSTP series, WDM series, WDM (NA) series,
RTN series, PTN series (except PTN 6900 series) and marine series NEs.
Context
The volume of NE data is large. To ensure that all NE data can be successfully backed up, do
not select many NEs at a time. If the U2000 displays an error message during the backup, retry
the backup on a per-NE basis.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
Step 6 The Operation Result dialog box is displayed. After the backup is successful, click Close.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l You must log in to the NE as an NE user with system level authority.
l It is suitable for OptiX OSN 1500, OptiX OSN 2000, OptiX OSN 2500, OptiX OSN 3500,
OptiX OSN 7500, OptiX OSN 7500 II, OptiX OSN 9500.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
Step 5 After the backup is successful, in the Operation Result dialog box, click Close.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l Log in to the NE as an NE user with "System Level" authority.
l The SCC board must be configured with the CF card. Applies to the MSTP, WDM, PTN,
RTN, and Marine series NE whose SCC boards are configured with CF cards.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
Step 4 Choose Back Up NE Data > Automatically Back Up Database to CF Card. In the
Automatically Back Up NE Data to CF Card window, set Automatic Backup and Automatic
Backup Period(min).
NOTE
Before the setting, you can click Query to query the status of the automatic backup of NE data to a CF
card.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l Log in to the NE as an NE user with "System Level" authority.
l The SCC board must be configured with the CF card. Applies to the MSTP, WDM, PTN,
RTN, and Marine series NE whose SCC boards are configured with CF cards.
Context
l The timeout time for the following operations on WDM NEs (NA) is as follows:
– Querying information about the current control board: 30s
– Backing up NE data to the CF board: 600s
l The timeout time for the following operation on the other NEs is as follow:
Backing up NE data to the CF board: 600s
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l You must log in to the NE as an NE user with system level authority.
l The DRDB database has been backed up to the flash database on the SCC board.
l Backing up and restoring NE data apply to MSTP series, WDM series, WDM (NA) series,
RTN series, PTN series (except PTN 6900 series) and marine series NEs.
Context
NOTICE
This operation causes service interruption. Exercise caution when you perform this operation.
Procedure
Step 1 In the Main Topology, double-click an NE or ONE to display the NE panel.
Step 2 Right-click the active SCC board and choose Warm Reset or Cold Reset or SCC Reset.
NOTE
l The reset modes for different SCC board are different. You need to choose the reset mode as required.
l When you choose Cold Reset or SCC Reset, the Warning dialog box is displayed. Click OK to start
the reset.
Step 3 Step 3 In the dialog box that is displayed, click OK to complete the reset.
----End
Prerequisites
l You are an NMS user with Maintenance Group authority or higher.
l You must log in to the NE as an NE user with system level authority.
l The NE database has been backed up to the CF card.
l Applies to the MSTP, WDM, PTN, RTN, and Marine series NE whose SCC boards are
configured with CF cards.
Context
NOTICE
This operation causes service interruption. Exercise caution when you perform this operation.
Procedure
Step 1 Choose Configuration > NE Configuration Data Management (traditional style) from the
main menu or select Fix-Network NE Configuration in Application Center and choose
Configuration > NE Configuration Data Management (application style) from the main
menu.
Step 4 Click Restore NE Data from CF Card. The Confirm dialog box is displayed, indicating that
the restoration of the NE database may lead to service interruption.
----End
Follow-up Procedure
After the NE database is restored, the database on the CF card is restored to the memory of the
SCC board, but not issued to the boards. If you want to restore the configuration data of the
boards, perform a warm reset on the SCC board. Then, perform warm resets on other boards.
During the reset, the NE issues the configuration data to the boards again.
15 Customer Management
By using the U2000, you can manage and maintain the customer data as required.
NOTE
The product you have purchased may use personal information of users when providing services or
maintenance. Therefore, you are obligated to take considerable measures, in compliance with the laws of
the countries concerned and the user privacy policies of your company, to ensure that the personal data of
users is fully protected.
User: You can log in to the U2000 client as a user. The user's operation rights are determined
by the user group and operation sets assigned to the user.
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
In the Customer Management window, all customers that managed by the current NMS user
are displayed in a list in the right pane.
Step 2 Select a customer group or root in the left pane and click Create. The Create Customer window
is displayed.
Step 3 According to actual requirements, enter the new customer information, such as Customer
Name, Legal Rep, and Telephone.
NOTE
If the customer is required to perform the ASON OVPN management, set OVPN ID or select the Auto
match OVPN ID check box.
Step 4 Click OK. The new customer information is displayed in the customer list.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
Step 2 Right-click an existing customer group in the left pane and choose Create Group from the
shortcut menu.
Step 3 In the displayed dialog box, enter a name for the Group Name field.
----End
Prerequisites
l You are an NMS user with "Administrators" authority.
l The U2000 user that performs such an operation must have the Right- and domain-based
authorization (transport domain) right. It is recommended that the U2000 user be
authorized to manage all customers on the network.
l The U2000 user and the customer to be authorized to the U2000 user must exist.
Procedure
Step 1 Authorize a U2000 user to manage a specified customer.
1. Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service
Resource Management > Customer Management (application style) from the main
menu.
2. Right-click the customer from the list in the right pane and choose Authorize to User from
the shortcut menu.
3. In the displayed dialog box, select the U2000 user from Available Users in the pane on
the left, and then click .
4. Click OK.
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
In the Customer Management window, all customers that managed by the current NMS user
are displayed in a list in the right pane.
Step 2 Optional: If the customer information is changed, you can click Refresh to browse the changed
customer information.
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
In the Customer Management window, all customers that managed by the current NMS user
are displayed in a list in the right pane.
Step 2 You can view the SDH, WDM, Ethernet, ATM trails separately.
l Right-click a record of customer information, and choose Browse Relevant Trails > SDH
Trail from the shortcut menu.
l Right-click a record of customer information, and choose Browse Relevant Trails > WDM
Trail from the shortcut menu.
l Right-click a record of customer information, and choose Browse Relevant Trails > WDM
Ethernet Trail from the shortcut menu.
l Right-click a record of customer information, and choose Browse Relevant Trails >
MSTP Ethernet Trail from the shortcut menu.
l Right-click a record of customer information, and choose Browse Relevant Trails > ATM
Trail from the shortcut menu.
The SDH, WDM, Ethernet, and ATM trails of the customer are displayed in the SDH/WDM/
Ethernet/ATM Trail Management window.
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
In the Customer Management window, all customers that managed by the current NMS user
are displayed in a list in the right pane.
Step 2 You can view the SDH, WDM, Ethernet, ATM and IP service current alarms separately.
l Right-click a customer and choose Browse Relevant Alarms > SDH Current Alarms.
l Right-click a customer and choose Browse Relevant Alarms > WDM Current Alarms.
l Right-click a customer and choose Browse Relevant Alarms > WDM Ethernet Current
Alarms.
l Right-click a customer and choose Browse Relevant Alarms > MSTP Ethernet Current
Alarms.
l Right-click a customer and choose Browse Relevant Alarms > ATM Current Alarms.
l Right-click a customer and choose Browse Relevant Alarms > IP Service Current
Alarms.
The current SDH, WDM, Ethernet, ATM and IP service alarms of the customer are displayed
in the Browse Current Alarms dialog box.
Step 3 To display the latest alarms, select the Show latest alarms check box in the bottom-left corner.
Step 4 Select an alarm. The details and handling suggestions of the alarm are displayed in the following
list.
Step 5 Optional: To acknowledge the alarms, select one or more alarms and click Acknowledge. In
the Confirm dialog box, click Yes. The Acknowledgement On, Acknowledgement Status
and Acknowledged By columns of the selected alarm shows the relevant values.
NOTE
Acknowledged and cleared alarms become historical alarms after you set the lifecycle.
Step 6 Optional: To clear the alarms, select one or more alarms and click Clear. In the Confirm prompt
box, click Yes. The Cleared On, Clearance Status and Cleared By columns of the selected
alarm shows the relevant values.
NOTE
l If you select the alarm that is in the Unacknowledged & Uncleared state, click the button to change
the status to Unacknowledged & Cleared.
l you select the alarm that is in the Acknowledged & Uncleared state, click the button to move the
alarm to the alarm log database.
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
In the Customer Management window, all customers that managed by the current NMS user
are displayed in a list in the right pane.
Step 2 You can view the SDH, WDM, Ethernet, ATM and IP service historical alarms separately.
l Right-click a customer and choose Browse Relevant Alarms > SDH Historical
Alarms.
l Right-click a customer and choose Browse Relevant Alarms > WDM Historical
Alarms.
l Right-click a customer and choose Browse Relevant Alarms > WDM Ethernet
Historical Alarms.
l Right-click a customer and choose Browse Relevant Alarms > MSTP Ethernet
Historical Alarms.
l Right-click a customer and choose Browse Relevant Alarms > ATM Historical
Alarms.
l Right-click a customer and choose Browse Relevant Alarms > IP Service Historical
Alarms.
The historical alarms of the SDH, WDM, Ethernet, ATM and IP service are displayed in the
Browse Historical Alarms dialog box.
Step 3 Optional: Select an alarm. The details and handling suggestions of the alarm are displayed in
the following list.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
In the Customer Management window, all customers that managed by the current NMS user
are displayed in a list in the right pane.
Step 2 In the customer list, select a customer, double-click the required field, and modify the
information. Then, click Apply.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Context
NOTICE
If an OVPN customer is deleted, the OVPN resources of the NE may not be managed.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
In the Customer Management window, all customers that managed by the current NMS user
are displayed in a list in the right pane.
Step 2 Select the customer to be deleted. Click Delete. In the Warning dialog box, select Yes.
NOTE
Deleting the customer does not affect the information of the trails and alarms that are related to the customer.
----End
Prerequisites
You are an NMS user with "Guests" user group authority or higher.
Procedure
Step 1 Choose Fault > Browse Current Alarm (traditional style) from the main menu or select Fault
Management in Application Center and choose Browse Alarm > Browse Current Alarm
(application style) from the main menu. Or Choose Fault > Browse Historical Alarm
(traditional style) from the main menu or select Fault Management in Application Center and
choose Browse Alarm > Query Historical Alarm (application style) from the main menu. The
window of viewing alarms is displayed.
Step 2 Right-click an alarm and choose Alarm-affecting Object > Customer from the shortcut menu.
NOTE
You can query the customers affected by only the alarms that occur on trails.
Step 3 In the Customer Management window, view the information about the customers that are
affected by the alarm.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Context
l For WDM trails, you cannot specify the customers of OTS, OMS, OSC level trails.
l For SDH trails, you cannot specify the customers of VC4 server trails.
l For Ethernet service, you cannot specify the customers of Trunk Link trails.
l For IP service, you cannot specify the customers of tunnel service.
Procedure
Step 1 Choose the following paths and related trail or service management window is displayed.
l Choose Service > SDH Trail > Manage SDH Trail (traditional style) from the main menu
or select Bearer Network Service Configuration in Application Center and choose
Service > SDH Trail > Manage SDH Trail (application style) from the main menu.
l Choose Service > WDM Trail > Manage WDM Trail (traditional style) from the main
menu or select Bearer Network Service Configuration in Application Center and choose
Service > WDM Trail > Manage WDM Trail (application style) from the main menu.
l Choose Service > MSTP Trail > Manage ATM Trail (traditional style) from the main
menu or select Bearer Network Service Configuration in Application Center and choose
Service > MSTP Trail > Manage ATM Trail (application style) from the main menu.
l Choose Service > MSTP Trail > Manage Ethernet Trail (traditional style) from the main
menu or select Bearer Network Service Configuration in Application Center and choose
Service > MSTP Trail > Manage Ethernet Trail (application style) from the main menu.
l Choose Service > Native Ethernet Service > Manage Native Ethernet Service
(traditional style) from the main menu or select Bearer Network Service Configuration
in Application Center and choose Service > Native Ethernet Service > Manage Native
Ethernet Service (application style) from the main menu.
l Choose Service > L3VPN Service > Manage L3VPN Service (traditional style) from the
main menu or select Bearer Network Service Configuration in Application Center and
choose Service > L3VPN Service > Manage L3VPN Service (application style) from the
main menu.
l Choose Service > VPLS Service > Manage VPLS Service (traditional style) from the
main menu or select Bearer Network Service Configuration in Application Center and
choose Service > VPLS Service > Manage VPLS Service (application style) from the
main menu.
l Choose Service > E-AGGR Service > Manage E-AGGR Service (traditional style) from
the main menu or select Bearer Network Service Configuration in Application
Center and choose Service > E-AGGR Service > Manage E-AGGR Service (application
style) from the main menu.
l Choose Service > PWE3 Service > Manage PWE3 Service (traditional style) from the
main menu or select Bearer Network Service Configuration in Application Center and
choose Service > PWE3 Service > Manage PWE3 Service (application style) from the
main menu.
Step 2 Right-click a trail and choose Details from the shortcut menu.
Step 3 Select the required customer for the trail in the drop-down list.
----End
Prerequisites
You are an NMS user with "Operator Group" authority or higher.
Context
VCN(Virtual Customer Network): A network provided for VIP customers of a carrier so that
they can view certain service information on the Web-based VCN system as VCN users.
Procedure
Step 1 Choose Service > Customer Management (traditional style) from the main menu or select
Bearer Network Service Configuration in Application Center and choose Service Resource
Management > Customer Management (application style) from the main menu.
In the Customer Management window, all customers that managed by the current NMS user
are displayed in a list in the right pane.
Step 2 Optional: If the customer information is changed, you can click Refresh to browse the changed
customer information.
Step 3 In the customer list, select a customer whose VCN Status is Disable, double-click the VCN
Status field, and then choose Enable from the shortcut menu.
----End
The Data Communications Channel (DCC) View is a graphical topology view showing NE
communication status and inter-NE transmission links. In the DCC view, you can query
information and perform related operations for network deployment and maintenance.
9 8 7 6
DCC Link Inside Management Domain DCC Link Outside Management Domain
No. Description
1 Navigation tree
l In the Physical Root navigation tree, you can perform the same
operations as those in the DCC topology view.
l A DCN subnet is named in DCN-GNE name format by default, where
GNE name indicates the name of a gateway NE (GNE). A DCN subnet
that contains multiple GNEs randomly selects a GNE name.
3 NE
NE status in the DCC view is the same as that in the DCC topology view.
No. Description
4 Unmanaged NE
l The U2000 cannot manage the NEs that exist on networks but are not
created on the U2000.
l Unmanaged NEs can communicate with other NEs in the inside
management domain if there are communication links between them.
8 DCC subnet
DCC subnets are composed of NEs communicating with each other
through protocols such as Huawei Embedded Control Channel (HWECC),
TCP/IP (IP over DCC), or OSI over DCC.
9 Statistics
l If Physical Root is selected, all NEs in DCC subnets and discrete NEs
on the panel are counted.
l If a subnet node is selected, NE types are displayed, and NEs of each
NE type in the subnet are counted.
l If an NE node is selected, its NE type is displayed.
l Information in Statistics can be printed or stored. The files are saved
to U2000 installation directory\client\client\report\ by default.
Prerequisites
l You are an NMS user with "Administrators" authority.
l The basic functions are applicable to the following NEs: NG WDM series, PTN series,
RTN 900 series, OptiX Metro 1000, OptiX OSN 500, OptiX OSN 550, OptiX OSN 1500,
OptiX OSN 3500/3580, OptiX OSN 7500, OptiX OSN 7500II, OptiX Metro 6040V2, and
OptiX Metro 6100V1E, OptiX BWS 1600G, OptiX BWS 1600G OLA, OptiX BWS 1600S,
SLM 1630 NEs.
Context
l For a new or expanded site, new gateway network elements (GNEs) may be created together
with new DCC subnets. You can synchronize network-wide DCC data to obtain the latest
data.
l In DCC subnet division, synchronize network-wide DCC data to refresh the DCC view and
obtain the latest data.
l In multi-client mode, if the operations on a client change DCC subnet data, the changes
will be reported to other clients.
l You can open the DCC view only with operation rights for all NEs.
Procedure
Step 1 Choose View > DCC View (traditional style) from the main menu or select Topo View in
Application Center and choose Topology > DCC View (application style) from the main menu.
Step 2 In the DCC topology view, right-click and choose Synchronize from the shortcut menu.
A progress bar is displayed. When the progress is 100%, the synchronization is complete.
NOTE
The synchronization duration depends on the number of network-wide NEs. If there are 1,000 NEs on a
network, the synchronization usually takes 5 to 15 minutes. The duration may be longer due to network
exceptions or busy NMS.
The following are some possible causes and handling suggestions for a failed or partially successful
synchronization:
l NE data is being loaded on the U2000. In this condition, synchronize DCC subnet data after the NE
data loading is complete.
l Another user is synchronizing data of network-wide subnets or data of a subnet. In this condition, wait
until the user completes the synchronization.
----End
Follow-up Procedure
After the data is synchronized, you can view the DCC subnet or link changes in the DCC view.
Prerequisites
l You are an NMS user with "Administrators" authority.
l The basic functions are applicable to the following NEs: NG WDM series, PTN series,
RTN 900 series, OptiX Metro 1000, OptiX OSN 500, OptiX OSN 550, OptiX OSN 1500,
OptiX OSN 3500/3580, OptiX OSN 7500, OptiX OSN 7500II, OptiX Metro 6040V2, and
OptiX Metro 6100V1E, OptiX BWS 1600G, OptiX BWS 1600G OLA, OptiX BWS 1600S,
SLM 1630 NEs.
Context
l In routine maintenance, you can periodically synchronize DCC subnet data to obtain the
latest DCC subnet data.
l For a newly allocated NE, you can synchronize data of its subnet to display it in the subnet.
l In network optimization and expansion, to-be-adjusted NEs and subnets are known.
Synchronize only the data of related subnets to obtain the latest data quickly.
l In communication fault locating and troubleshooting, if fiber/cable or GNE data is changed,
synchronize DCC subnet data to obtain the latest data.
Procedure
Step 1 Choose View > DCC View (traditional style) from the main menu or select Topo View in
Application Center and choose Topology > DCC View (application style) from the main menu.
Step 2 Right-click the target DCC subnet and choose Synchronize from the shortcut menu.
A progress bar is displayed. When the progress is 100%, the synchronization is complete.
NOTE
The synchronization duration depends on the number of network-wide NEs. If there are 50 NEs on a
network, the synchronization usually takes 30 seconds. The duration may be longer due to network
exceptions or busy NMS. A subnet contains a maximum of 50 NEs.
The following are some possible causes and handling suggestions for a failed or partially successful
synchronization:
l NE data is being loaded on the U2000. In this condition, synchronize DCC subnet data after the NE
data loading is complete.
l Another user is synchronizing data of network-wide subnets or data of a subnet. In this condition, wait
until the user completes the synchronization.
----End
Follow-up Procedure
After the data is synchronized, you can view the fiber/cable or link changes in the DCC subnet
view.
Prerequisites
l You are an NMS user with "Administrators" authority.
l The basic functions are applicable to the following NEs: NG WDM series, PTN series,
RTN 900 series, OptiX Metro 1000, OptiX OSN 500, OptiX OSN 550, OptiX OSN 1500,
OptiX OSN 3500/3580, OptiX OSN 7500, OptiX OSN 7500II, OptiX Metro 6040V2, and
OptiX Metro 6100V1E, OptiX BWS 1600G, OptiX BWS 1600G OLA, OptiX BWS 1600S,
SLM 1630 NEs.
Context
l In network adjustment, after data in the DCC view or DCC subnet view is synchronized,
real-time data is displayed in the DCC view or DCC subnet view for easy comparison with
data plan.
l In routine maintenance, after data in the DCC view or DCC subnet view is synchronized,
real-time data is displayed in the DCC view or DCC subnet view for easy location of
abnormal DCC subnets, fibers/cables, and links.
Procedure
Step 1 Choose View > DCC View (traditional style) from the main menu or select Topo View in
Application Center and choose Topology > DCC View (application style) from the main menu.
Step 2 Optional: Choose either of the following ways to view DCC subnet information:
l Right-click the target DCC subnet in the Physical Root navigation tree and choose Enter
from the shortcut menu. In the topology view, view information about the DCC subnet.
l Right-click the target DCC subnet in the DCC topology view and choose Enter from the
shortcut menu. In the topology view, view information about the DCC subnet.
----End
Prerequisites
l You are an NMS user with "Administrators" authority.
l The basic functions are applicable to the following NEs: NG WDM series, PTN series,
RTN 900 series, OptiX Metro 1000, OptiX OSN 500, OptiX OSN 550, OptiX OSN 1500,
OptiX OSN 3500/3580, OptiX OSN 7500, OptiX OSN 7500II, OptiX Metro 6040V2, and
OptiX Metro 6100V1E, OptiX BWS 1600G, OptiX BWS 1600G OLA, OptiX BWS 1600S,
SLM 1630 NEs.
Context
l If an NE is disconnected from the U2000, use the ping function to identify the cause. Ping
all NEs between the unreachable NE and its GNE (source NE). If a hop can be pinged but
the next hop cannot, the fault point can be identified in the link between these two hops.
l When a DCC storm occurs, NEs may lose communication with the U2000. Use the trace
function to locate this fault.
l In the scenarios of DCC storms, you can test reachable NEs for an NE whose
communication with others is unstable to find out two NEs that should not have
communication and locate faults using traceroute function.
Context
l If an NE is disconnected from the U2000, use the ping function to identify the cause. Ping
all NEs between the unreachable NE and its GNE (source NE). If a hop can be pinged but
the next hop cannot, the fault point can be identified in the link between these two hops.
l When a DCC storm occurs, NEs may lose communication with the U2000. Use the trace
function to locate this fault.
l When a DCC storm occurs, perform the reachable NE test for an intermittently disconnected
NE. The test result will list all the NEs reachable to the tested NE. You can find the two
NEs that should not be reachable to each other and use the traceroute function to locate this
fault.
Procedure
l Ping
1. In the DCC view or DCC subnet view, right-click and choose Ping from the shortcut
menu.
2. In the Ping window, set Source NE, NE, and IP Address (the last two are for the
sink NE).
NOTE
When pinging a target NE on the source NE, you can select either of the following methods:
l If you know the ID of the target NE, select the target NE from the NE drop-down list;
l The Attempt value ranges between 1 and 100 and the default value is 3.
l The Interval(s) value ranges between 0 and 60 and the default value is 5.
3. Click Start. The ping result will be displayed in the Output area.
l Test NE can be selected from the drop-down list. Alternatively, click and
select an from the NE Tree.
l The Attempt value ranges from 1 to 10. The Attempt value determines how many times
the message is broadcast. After you choose Test Reachable NEs, the tested NE broadcasts
a message network-wide. NEs that receive the message will make a reply.
3. Click Start. Wait until the test results are displayed.
– If the test fails, an error will be reported with the failure causes provided.
– If the test succeeds, you can see the names, DCC subnets, and gateways of all the
NEs reachable to the tested NE in the Output area of the Test Reachable NEs
window. For example, after a reachable NE test on NE A with Attempt set to 3,
NE B can establish communication with NE A if NE B receives the broadcast
message once or more. All the NEs that can establish communication with NE A
are listed in the Output area, one row for each NE.
NOTE
If the tested NE is an isolated NE, the Output area will be empty.
----End
Navigation Path
Choose View > DCC View (traditional style) from the main menu or select Topo View in
Application Center and choose Topology > DCC View (application style) from the main menu.
Table 16-2 NE
Parameter Description
l Click . In the NE
Tree window, choose the
desired NE from the navigation
tree or click Search to specify
the NE.
l Click . In the NE
Tree window, choose the
desired NE from the navigation
tree or click Search to specify
the NE.
l Click . In the NE
Tree window, choose the
desired NE from the navigation
tree or click Search to specify
the NE.
l Click . In the NE
Tree window, choose the
desired NE from the navigation
tree or click Search to specify
the NE.
l Click . In
the NE Tree window,
choose the desired NE
from the navigation
tree or click Search to
specify the NE.
Navigation Path
Choose View > DCC View (traditional style) from the main menu or select Topo View in
Application Center and choose Topology > DCC View (application style) from the main
menu. Double-click a DCC subnet. In the subnet, right-click a DCC link and choose
Properties from the shortcut menu.
Parameter Description
Link Type For example: DCC Link Indicates the type of a link.
Local/Peer Port For example: NE (71-9)-Shelf5 Indicates the local or peer DCC port
(subrack)-5-12SC2-2 (RM2/TM2) used by two NEs to communicate
with each other.
Local Protocol HWECC, TCP/IP, OSI Indicates the protocol used by the
Type local or peer DCC port.
Protocol Type HWECC, TCP/IP, OSI Indicates the protocol used by DCC
ports.