SJ-20140724091740-009-NetNumen U31 R18 (V12.13.50) Maintenance Management Operation Guide

NetNumen™ U31 R18
Unified Element Management System

Maintenance Management Operation Guide
Version: V12.13.50
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2014-09-03 First edition
Serial Number: SJ-20140724091740-009
Publishing Date: 2014-09-03 (R1.0)
SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Maintenance Management ....................................................... 1-1
1.1 Overview ........................................................................................................... 1-1
1.1.1 Remote Backup Path Configuration ........................................................... 1-1
1.1.2 Task Management .................................................................................... 1-1
1.1.3 System Backup and Restoration................................................................ 1-3
1.1.4 System Monitoring.................................................................................... 1-3
1.1.5 IT Device Monitoring................................................................................. 1-4
1.2 Implicit Prerequisites .......................................................................................... 1-5
Chapter 2 Remote Backup Path Configuration ....................................... 2-1

Chapter 3 Task Management ..................................................................... 3-1
3.1 Task Management Window ................................................................................. 3-1
3.2 Pre-defined Scheduled Task Management ........................................................... 3-2
3.2.1 Modifying the Start Time of Predefined Scheduled Tasks ............................ 3-2
3.2.2 Managing the Log Data Backup and Deletion Task ..................................... 3-4
3.2.3 Managing the Performance Data Backup and Deletion Task ....................... 3-7
3.2.4 Managing the Alarm Data Backup and Deletion Task .................................. 3-9
3.2.5 Managing the Basic Data Backup Task .................................................... 3-12
3.2.6 Managing the Entire Database Structure Backup Task.............................. 3-14
3.2.7 Managing the File Backup Task............................................................... 3-16
3.2.8 Managing Directory Monitoring................................................................ 3-18
3.2.9 Setting the Historical Alarms Acknowledgement Task ............................... 3-20
3.3 Managing MML Tasks....................................................................................... 3-21
3.3.1 Creating an MML Task............................................................................ 3-21
3.3.2 Displaying the Settings of an MML Task................................................... 3-25
3.3.3 Modifying an MML Task .......................................................................... 3-26
3.3.4 Activating an MML Task .......................................................................... 3-27
3.3.5 Suspending an MML Task....................................................................... 3-27
3.3.6 Displaying the Execution Log of an MML Task.......................................... 3-27
3.3.7 Displaying the Execution Result of an MML Task...................................... 3-28
3.3.8 Deleting an MML Task ............................................................................ 3-30
Chapter 4 System Backup and Restoration............................................. 4-1

4.1 System Backup and Restore Window .................................................................. 4-1

4.2 Backup Operations............................................................................................. 4-2
4.2.1 Backing Up the Entire Database Structure ................................................. 4-2
4.2.2 Backing Up the Basic Data ....................................................................... 4-3
4.2.3 Backing Up Files ...................................................................................... 4-4
4.2.4 Backing Up and Deleting Log Data ............................................................ 4-5
4.2.5 Backing Up and Deleting Alarm Data ......................................................... 4-7
4.2.6 Backing Up and Deleting Performance Data ............................................ 4-10
4.3 Restore Operations .......................................................................................... 4-12
4.3.1 Restoring Log Data ................................................................................ 4-12
4.3.2 Restoring Alarm Data ............................................................................. 4-13
4.3.3 Restoring Performance Data ................................................................... 4-13
Chapter 5 System Monitoring.................................................................... 5-1

5.1 System Monitoring Window................................................................................. 5-1
5.2 Application Server Monitoring.............................................................................. 5-2
5.2.1 Viewing the Application Server Information ................................................ 5-2
5.2.2 Setting Application Server Performance Monitoring Parameters .................. 5-2
5.2.3 Starting the Application Server Monitoring.................................................. 5-5
5.2.4 Suspending the Application Server Monitoring ........................................... 5-5
5.2.5 Viewing the Application Server Performance .............................................. 5-6
5.3 Database Monitoring .......................................................................................... 5-7
5.3.1 Viewing the Database Information ............................................................. 5-7
5.3.2 Setting Database Monitoring Parameters ................................................... 5-8
5.3.3 Starting the Database Monitoring ............................................................ 5-10
5.3.4 Suspending the Database Monitoring ...................................................... 5-10
5.3.5 Viewing Database Resources ..................................................................5-11
Chapter 6 IT Device Monitoring................................................................. 6-1

6.1 IT Monitoring Window ......................................................................................... 6-1
6.2 Adding an IT Device ........................................................................................... 6-2
6.2.1 Adding a Server Node .............................................................................. 6-2
6.2.2 Adding a Database Node .......................................................................... 6-5
6.2.3 Adding a Router Node .............................................................................. 6-7
6.2.4 Adding a Switch Node .............................................................................. 6-9
6.2.5 Adding a Firewall Node........................................................................... 6-12
6.2.6 Adding a Cluster Node............................................................................ 6-14
6.2.7 Adding a Storage Device Node ............................................................... 6-16
6.2.8 Adding an Application Node .................................................................... 6-19
6.2.9 Adding Other Nodes ............................................................................... 6-21
II

6.3 Configuring the Component Information for an IT Device .................................... 6-24
6.4 Configuring Status Monitoring for an IT Device................................................... 6-26
6.5 Viewing Alarms of an IT Device ......................................................................... 6-28
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
III

This page intentionally left blank.
IV

About This Manual
Purpose
This manual provides instructions for maintenance management operations in the
NetNumenTM U31 R18 Unified Element Management System (NetNumen U31), including
maintenance task management, data backup and restoration, system monitoring, and IT
device monitoring.
Intended Audience
This manual is intended for:
l Maintenance engineers
l Debugging engineers
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
1, Maintenance Management Provides an overview of maintenance management

functional modules of the NetNumen U31 system.
2, Remote Backup Path Configuration Describes how to set a remote backup path.
3, Task Management Provides the instructions for managing maintenance tasks,

including backup and deletion tasks, file clean-up tasks, and
scheduled MML tasks.
4, System Backup and Restoration Describes data backup and restore operations.
5, System Monitoring Describes how to monitor the application server and the
database of the NetNumen U31 system.
6, IT Device Monitoring Describes how to monitor an IT device and how to configure

the monitoring settings.
Related Documentation
The following documentation is related to this manual:
l NetNumen U31 R18 Unified Element Management System Performance
Management Operation Guide
l NetNumen U31 R18 Unified Element Management System System Management
Operation Guide
l NetNumen U31 R18 Unified Element Management System Security Management
Operation Guide
l NetNumen U31 R18 Unified Element Management System MML Command
Reference

Conventions
This manual uses the following typographical conventions:
Typeface Meaning
Note: provides additional information about a certain topic.
II

Chapter 1
Maintenance Management
Table of Contents
Overview ....................................................................................................................1-1
Implicit Prerequisites ..................................................................................................1-5
1.1 Overview
The NetNumen U31 system provides the following modules for system maintenance and
monitoring:
l Task management module
l System backup and restoration module
l System monitoring module
l IT device monitoring module (optional)
IT monitoring is an optional function. Users need to apply for the software license from
ZTE and select ITMP when installing the NetNumen U31 server and client.
1.1.1 Remote Backup Path Configuration

This procedure describes how to set a remote backup path for scheduled backup tasks.
After this path is set, users can select whether to back up data to the specified path on the
remote server.
The remote backup bath is effective for the following scheduled tasks:
l Log data backup and deletion task
l Performance data backup and deletion task
l Alarm data backup and deletion task
l Basic data backup task
l Entire database structure backup task
l File backup task
1.1.2 Task Management

The task management module predefines multiple maintenance tasks and organizes
these tasks by type in a navigation tree on the client GUI. When the start time of a
maintenance task is reached, the system automatically executes the task in accordance
with the default settings. For a description of the predefined maintenance tasks and
allowable task operations, refer to Table 1-1.
1-1

NetNumen™ U31 R18 Maintenance Management Operation Guide
Table 1-1 Predefined Maintenance Task Description
Task Type Description Allowable Operation
Historical Data Backs up and deletes log data, l Refreshing task settings
Archiving performance data, and alarm data l Modifying task settings
periodically to maintain database l Saving task settings
capacity. l Cancelling task modification
l Displaying the task execution
exceptions
l Displaying the task execution log
l Stopping the ongoing backup
process
l Enabling the data monitoring
function
Configuration Data Backs up the basic data of l Modifying task settings

Backup the system, meaning all data l Saving task settings
except large historical data such l Cancelling task modification
as historical alarms, logs, and l Displaying the task execution log
original performance data. l Stopping the ongoing backup
process
l Activating the task
l Suspending the task
File and Database Backs up the entire database l Modifying task settings
Backup with its structure and basic data l Saving task settings
(except historical data), and backs l Cancelling task modification
up version files, configuration l Displaying the task execution log
files, and runtime files in the l Stopping the ongoing backup
system. process
l Activating the task
l Suspending the task
File Clean-up Clears data backup files and l Modifying task settings
result files generated by other l Executing a task instantly
management operations to l Viewing the task execution log
maintain hard drive capacity. l Viewing file information
l Customizing columns to be
displayed
l Searching for specific directory for
file clean-up
Alarm Background Automatically acknowledges l Refreshing task settings

Task historical alarms that are older l Modifying task settings
than the specified number of days. l Saving task settings
l Cancelling task modification
l Viewing the task execution log
1-2

Chapter 1 Maintenance Management
In addition to the five task types described in Table 1-1, the task management module
allows users to schedule tasks in which Man Machine Language (MML) commands are
used to specify the actions to be performed. The following operations can be performed
to a scheduled MML task:
l Suspending an MML task
l Activating an MML task
l Modifying an MML task
l Viewing an MML task
l Viewing the execution log of an MML task
l Deleting an MML task
1.1.3 System Backup and Restoration

The system backup and restoration module supports backup and restoration in the
NetNumen U31 system.
l A backup task enables the system to back up the required data to a specified path
and clear the database in the specified time range. It includes:
à Entire database structure backup
à Basic data backup
à File backup
à Log data backup and deletion
à Alarm data backup and deletion
à Performance data backup and deletion
l A restoration task enables data to be restored from a data file to the corresponding
database table. It includes:
à Log data restoration
à Alarm data restoration
à Performance data restoration
Entire database structure restoration, basic data restoration, and file restoration are
performed through the offline tool.
1.1.4 System Monitoring

The system monitoring module automatically identifies the application server and the
database server of the NetNumen U31 system and displays the server information on the
client GUI. The system monitoring functions include:
l Monitoring the application server, including the memory usage, CPU usage, and hard
disk usage.
l Monitoring the database, including the database usage, table spaces, data tables,
and processes.
1-3

1.1.5 IT Device Monitoring

The NetNumen U31 can monitor and manage a variety of IT devices and provide their
performance data and alarm information.
Before adding an IT device node in the NetNumen U31 system, users must properly
configure the IT device to ensure successful connection between the system and the
device.
Supported Devices
The IT device monitoring module of the NetNumen U31 system can monitor the following
IT devices:
Type Model
Server Solaris, AIX, HP-UX, RedHat Linux, SUSE Linux, CGS Linux, Windows.
Database Oracle, SQL Server, Sybase IQ, Sybase.
Router Cisco, ZTE, Juniper.
Switch AT, Cisco, ZTE, Juniper.
Firewall CheckPoint, Juniper, Cisco, H3C, ZTE, Cisco dual-homed firewall.
Cluster AIX HACMP, HP ServiceGuide, Symantec VCS, NewStartHA, NEC.
Storage device IBM, HP, ZTE, SUN, Fujitsu, EMC, NetApp.
Applications BIND service, DNS service, TOMCAT service, , NTP service, NetNumen,
IBM Tivoli storage management, Trend Micro anti-virus software, WebLogic
application.
Others F5 traffic manager, HP BLC chassis, HP GBE2C blade switch module, HP

Virtual Connect (VC) module, Radware AppDirector, ZTE power supply, Cisco
UCS, IMM, F5 traffic manager dual-server, IBM blade, SeGW, ZXSDR NT8200,
DCS.
Note:
The supported IT devices vary with different NetNumen U31 versions.
Operating Environment
The IT device monitoring module can operate on various platforms. The following provides
the operating systems and databases that support the module operation:
Environment Version
Operating system Windows 2003 Server (SP2 or later), Windows 2008 Server, Solaris 10,
CGS Linux, IBM AIX
1-4

Chapter 1 Maintenance Management
Environment Version
Database MS SqlServer 2005/2008 Enterprise Edition, Oracle9i/10g/11g
Operation Procedure
Figure 1-1 shows the operation procedure of IT device monitoring.
Figure 1-1 IT Device Monitoring Procedures
For details about how to create a measurement task, create a threshold task, and query
performance data, refer to the NetNumen U31 R18 Unified Element Management System
Performance Management Operation Guide.
1.2 Implicit Prerequisites

For all operations subsequent to this section, the following prerequisites are presumed to
have been met.
l The NetNumen U31 client is started and successfully connected to the server.
l The permissions for maintenance management operations have been acquired.
1-5

1-6

Chapter 2
Remote Backup Path
Configuration
Prerequisite
l The FTP service is enabled on the remote server.
l The information related to the remote server has been obtained, including the host
address, port number, user name and password. If not, contact the administrator.
Steps
1. On the menu bar, select Maintenance > Remote Backup Path Configuration. The
Configuration of Remote Backup Path dialog box is displayed, see Figure 2-1.
Figure 2-1 Configuration of Remote Backup Path Dialog Box
2. Set the required parameters of the remote server.

For a description of the server parameters, refer to Table 2-1.
Table 2-1 Description of Remote Backup Path Parameters
Parameter Description
File Transfer Protocol File transfer protocol. The options are: SFTP and FTP.
Host Address IP address of the remote server.
Port Port number on the remote server for file transfer.
User Name User name for logging in to the remote server.
User Password Password for logging in to the remote server.
2-1

Note:
The Remote Backup Path text box and the Browse button are available only when
the server parameters are properly set.
3. Click Browse. The Open dialog box is displayed.

4. Select the path for backing up data on the remote server, and then click Open. The
backup path is displayed in the Remote Backup Path text box.
5. Click OK. The Remote Backup Path check box in the task information pane is
activated, see Figure 2-2.
Figure 2-2 Remote Backup Path
6. If data backup to the remote server is not required any longer, perform the following
operations:
a. Select Maintenance > Remote Backup Path Configuration on the menu bar.
The Configuration of Remote Backup Path dialog box is displayed.
b. Click Clear. The parameter settings are cleared in the dialog box.
c. Click OK. The Remote Backup Path check box in the task information pane
becomes unavailable and the remote path disappears.
– End of Steps –
2-2

Chapter 3
Task Management
Table of Contents
Task Management Window ........................................................................................3-1
Pre-defined Scheduled Task Management .................................................................3-2
Managing MML Tasks ..............................................................................................3-21
3.1 Task Management Window

Users can specify tasks for scheduled backup and deletion in the Task Management
window on the client GUI.
Figure 3-1 shows the Task Management window.
Figure 3-1 Task Management Window
1. Task management toolbar 2. Task information pane 3. Navigation tree
In the left pane of the Task Management window, all scheduled tasks are displayed by
type in a navigation tree. The right pane displays the information of a task selected in
the navigation tree. The task management toolbar provides multiple buttons for managing
scheduled tasks. The toolbar buttons vary with different tasks.
3-1

3.2 Pre-defined Scheduled Task Management

3.2.1 Modifying the Start Time of Predefined Scheduled Tasks
This procedure describes how to modify the start time of the five predefined scheduled
tasks.
Context
The system defines a default start time (a specific hour) for each scheduled task type. A
scheduled task may be started from the exact default hour or a time offset. The time offset
is a random value generated by the system, and is an integer multiple of 10 ranging from
0 to 60. For example, if the start time of historical data archiving tasks is 22:00:00, the log
data backup and deletion task may be started at 22:20:00.
Note:
l Users do not need to modify the start time of scheduled tasks unless absolutely
necessary because the default start time is optimal in most cases.
l The start time should be unique for each type of scheduled tasks.
Steps
1. Select Maintenance > Task Management > Modify Task Start Time. The Modify
Task Start Time dialog box is displayed, see Figure 3-2.
3-2

Chapter 3 Task Management
Figure 3-2 Modify Task Start Time Dialog Box
2. Select File Clean-up, and then click (Alternatively, double-click the selected task
type). The Modify Time dialog box is displayed, see Figure 3-3.
Figure 3-3 Modify Time Dialog Box
3. Enter or select a new hour, and then click OK. The Modify Time dialog box is closed.
4. Click OK. The Modify Task Start Time dialog box is closed.
3-3

3.2.2 Managing the Log Data Backup and Deletion Task

This procedure describes how to manage the log data backup and deletion.
The system automatically executes the task for log data backup and deletion once a day to
delete the log data whose storage period expires to prevent massive log data from affecting
system operations.
The system also provides a log data monitoring function. If this function is enabled, the
system compares the number of log records with the preset thresholds when executing the
log data backup and deletion task. If the number of log records exceeds a threshold, the
system raises an alarm and deletes some of the existing log records that are not expired.
Users can determine whether to back up the log data of the previous day.
Steps
1. Select Maintenance > Task Management from the menu bar. The Task
Management window is displayed.
2. Click Log Data Backup and Deletion Task in the Task Management tree. The task
information is displayed in the right pane, see Figure 3-4.
Figure 3-4 Log Data Backup and Deletion Task
For a description of the toolbar buttons for managing the log data backup and deletion
task, refer to Table 3-1.
Table 3-1 Toolbar Buttons for Managing the Log Data Backup and Deletion Task
Button Description
Refreshes the task to obtain the latest settings from the NetNumen
U31 server.
3-4

Button Description
Modifies the backup settings.
Saves the modification of task settings.
Cancels the modification of task settings.
Displays the execution exceptions of the task.
Displays the task execution log.
Enables the log data monitoring function and sets monitoring

thresholds.
Stops the ongoing backup process.

This button is activated when the system is backing up log data during
the task execution.
3. To enable the log data monitoring function and set monitoring thresholds, perform the
following steps:
a. Click on the toolbar. The Set Capacity dialog box is displayed, see Figure
3-5.
Figure 3-5 Set Capacity Dialog Box
Note:
All thresholds must be lower than the corresponding capacity limits.
b. Click Run, and then set thresholds for the operation log, system log, and security
log as required.
3-5

For a description of the parameters in the Set Capacity dialog box, refer to Table
3-2.
Table 3-2 Set Capacity Dialog Box Parameter Descriptions
Run Enables the log data monitoring function.
Suspend Disables the monitoring of all log types.
Type Provides optional threshold types: Percentage, Record, or NO.

To disable the monitoring of a specific log, select NO from the
corresponding cell in the Type column.
Threshold (Critical) Set four thresholds for each log type as required.
Threshold (Major) If the number of log records exceeds a preset threshold, the system
Threshold (Minor) will raise a threshold crossing alarm at the corresponding severity
Threshold (Warning) level and delete older log records to reduce the log records in the
database.
After the alarm-raising thresholds for different severity levels are set, the system
checks the storage usage. If the system detects that the storage of the log backup
directory exceeds a specified threshold, an alarm of the corresponding severity
is raised, and the backup data is deleted to a size below 80% of the Warning
threshold.
Note:
When the capacity thresholds are set, the log saving duration in the database may
be shorter than the duration set in the configuration center.
The database space occupied by log data can be calculated as follows:
l In the system log table: 1024 log records occupy 1 MB.
l In the security log table: 3300 log records occupy 1 MB.
l In the operation log table: 1024 log records occupy 1 MB.
c. Click OK. The Set Capacity dialog box is closed.

4. To modify the backup settings, perform the following steps:
a. Click on the toolbar. The Backup Description area is activated, see Figure
3-6.
3-6

Figure 3-6 Backup Description Area
b. Select Operation Log, System Log, and/or Security Log as required.
c. (Optional) To back up the log data in both the default path and a remote path,
select Remote Backup Path in the Backup Path area.
Note:
The Remote Backup Path is only available when the remote backup path is set.
For how to set a remote backup path, refer to "Chapter 2 Remote Backup Path
Configuration".
d. Click .
3.2.3 Managing the Performance Data Backup and Deletion Task

This procedure describes how to manage the performance data backup and deletion.
The system automatically executes the task for performance data backup and deletion
once a day to delete performance data whose storage period expires. The purpose of this
task is to prevent massive data from affecting the system stability when performance data
is collected. Users can determine whether to back up the performance data of the previous
day.
Steps
2. Click PM Data Backup and Deletion Task in the Task Management tree. The task
3-7

Figure 3-7 PM Data Backup and Deletion Task
For a description of the toolbar buttons for managing the performance data backup
and deletion task, refer to Table 3-3.
Table 3-3 Toolbar Buttons for Managing the Performance Data Backup and Deletion
Task
Button Description
U31 server.

This button is activated when the system is backing up performance
data during the task execution.
a. Click on the toolbar. The Backup Description area is activated.

b. Select the performance data tables to be backed up.
3-8

c. (Optional) To back up the performance data in both the default path and a remote
path, select Remote Backup Path.
Note:
Configuration".
d. Click .
3.2.4 Managing the Alarm Data Backup and Deletion Task

This procedure describes how to manage the alarm data backup and deletion.
The system automatically executes the task for alarm data backup and deletion once a
day to delete the alarm data whose storage period expires to prevent massive alarm data
from impacting system operations.
The system also provides an alarm data monitoring function. If this function is enabled, the
system will compare the number of alarm or notification records with the preset thresholds
when executing the task for alarm data backup and deletion. If the number of alarm or
notification records exceeds a threshold, the system will raise an alarm and delete some
of the existing records that are not expired. Users can determine whether to back up the
alarm and/or notification records of the previous day.
Steps
2. Click Alarm Data Backup and Deletion Task in the Task Management tree. The
task information is displayed in the right pane, see Figure 3-8.
3-9

Figure 3-8 Alarm Data Backup and Deletion Task
For a description of the toolbar buttons for managing the alarm data backup and
deletion task, refer to Table 3-4.
Table 3-4 Toolbar Buttons for Managing the Alarm Data Backup and Deletion Task
Button Description
U31 server.
Enables the alarm data monitoring function and sets monitoring

thresholds.

This button is activated when the system is backing up alarm data
during the task execution.
3. To enable the data monitoring function and set monitoring thresholds, perform the
following steps:
3-10

a. Click on the toolbar. The Set Capacity dialog box is displayed, see Figure
3-9.
Figure 3-9 Set Capacity Dialog Box
Note:
All thresholds must be less than the corresponding capacity limits.
b. Click Run, and then set thresholds for the operation log, system log, and security
log as needed.
For a description of the parameters in the Set Capacity dialog box, refer to Table
3-5.
Table 3-5 Set Capacity Dialog Box Parameter Descriptions
Run Enables the log data monitoring function.
Suspend Disables the monitoring of all log types.
Type Provides optional threshold types: Percentage, Record, or NO.

To disable the monitoring of a specific log, select NO from the
corresponding cell in the Type column.
Threshold (Critical) Set four thresholds for each log type as required.
Threshold (Major) If the number of log records exceeds a preset threshold, the system
Threshold (Minor) will raise a threshold crossing alarm at the corresponding severity
Threshold (Warning) level and delete older log records to reduce the log records in the
database.
After the alarm-raising thresholds for different severity levels are set, the system
checks the storage usage. If the system detects that the storage of the log backup
3-11

directory exceeds a specified threshold, an alarm of the corresponding severity

is raised, and the backup data is deleted to a size below 80% of the Warning
threshold.
Note:
The database space occupied by alarm data can be calculated as follows:
l In the history alarm table: 300 alarm records occupy 1 MB.
l In the notification table: 300 alarm records occupy 1 MB.
c. Click OK.
a. Click on the toolbar. The Backup Description area is activated.

b. Select History Alarm Table and/or Notification Table as required for backing up
history alarm records and/or notification records.
c. (Optional) To back up the history alarm and notification records in both the default
path and a remote path, select Remote Backup Path.
Note:
Configuration".
d. Click .
3.2.5 Managing the Basic Data Backup Task

This procedure describes how to manage the basic data backup task.
Context
Users can perform the following management operations on the basic data backup task:
l Modifying task settings.
l Saving and cancelling task modifications.
l Viewing the task execution log. Each log record contains the information of task
source, task rank, log name, details, host IP address, start time, end time, and related
log.
3-12

l Stopping the backup process during task execution.

l Activating the scheduled backup task (in suspended status).
l Suspending the task.
Steps
2. Click Backup Basic Data in the Task Management tree. The task information is
displayed in the right pane, see Figure 3-10.
Figure 3-10 Backup Basic Data Task
Note:
l The button used to stop the basic data backup process is only available when
the system is backing up basic data during task execution.
l The Remote Backup Path is only available when the remote backup path is set.
Configuration".
3. (Optional) To modify task settings, click . The Remote Backup Path check box is
available.
4. (Optional) Select the Remote Backup Path check box for saving the backup data both
in the default path and on the remote server.
3-13

5. (Optional) To save modified settings, click .
6. (Optional) To cancel modified settings, click
7. (Optional) To view the execution log of the task, click on the toolbar. The View
Log dialog box is displayed, listing the log records of the task.
8. (Optional) To stop the ongoing backup process, click on the toolbar. The system
stops backing up the basic data.
9. (Optional) To suspend the basic data backup task, perform the following steps:
a. Click on the toolbar. A confirmation box is displayed.

b. Click Yes to continue.
The basic data backup task is suspended and the button on the toolbar is
available.
10. (Optional) To activate the suspended scheduled task, click .
11. Click .
3.2.6 Managing the Entire Database Structure Backup Task

This procedure describes how to manage the task for backing up the entire database
structure.
Users can perform the following management operations on the task for backing up the
entire database structure, including:
l Saving and cancelling task modification.
l Viewing the task execution log. Each log record contains the information of task
log.
l Stopping the backup process during task execution.
Steps
2. Click Backup Whole DB Structure in the Task Management tree. The task
3-14

Figure 3-11 Backup Whole DB Structure Task
Note:
l The button used to stop the database structure backup process is only
available when the system is backing up the entire database structure during
task execution.
l The Remote Backup Path is only available when the remote backup path is set.
Configuration".
available.
4. (Optional) Select the Remote Backup Path check box for saving backup data both in
the default path and on the remote server.
8. (Optional) To stop the ongoing backup process, click on the toolbar. The system
stops backing up the entire database structure.
3-15

9. (Optional) To suspend the entire database structure backup task, perform the following
steps:

The entire database structure backup task is suspended and the button on the
toolbar is available.
11. Click .
3.2.7 Managing the File Backup Task

This procedure describes how to manage the file backup task.
Users can perform the following management operations on the file backup task:
l Saving and cancelling task modification.
l Viewing the execution log of the task. Each log record contains the information of task
log.
Steps
2. Click Backup File in the Task Management tree. The task information is displayed
in the right pane, see Figure 3-12.
3-16

Figure 3-12 Backup File Task
Note:
Configuration".
available.
4. (Optional) Select the Remote Backup Path check box for saving backup data both in
the default path and on the remote server.
8. (Optional) To suspend the file backup task, perform the following steps:
The file backup task is suspended and the button on the toolbar is available.
3-17

10. Click .
3.2.8 Managing Directory Monitoring

The system can monitor directory sizes and clean the dynamically generated files based
on the directory threshold and clean-up conditions on the application server. This ensures
sufficient hard disk space is available in the application server.
This procedure describes how to manage a directory monitoring task that monitors the
performance data backup directory as an example.
Steps
1. Modify the directory monitoring task.
a. Select Maintenance > Task Management from the menu bar. The Task
b. In the Task Management tree, click Directory Monitoring under File Clean-up.
All directory monitoring tasks are listed in the right pane, see Figure 3-13.
Figure 3-13 Directory Monitoring Task
c. Select the Performance Data Backup Directory Monitoring task and click .
The Performance Data Backup Directory Monitoring dialog box is displayed,
see Figure 3-14.
3-18

Figure 3-14 Performance Data Backup Directory Monitoring Dialog Box
d. Modify the required parameters and click OK.

2. (Optional) If the execution time is not reached, click to implement the monitoring
task immediately. A dialog box is displayed.
3. Click Yes. A prompt box is displayed, indicating that the monitoring task is completed.
4. View the log information of the directory monitoring task.
a. Click . The View Log dialog box is displayed.

b. Right-click a log and then click View Log Detail.
5. Click . The Directory Monitor File Information dialog box is displayed, see
Figure 3-15.
3-19

Figure 3-15 Directory Monitor File Information Dialog Box
6. View the file information.

3.2.9 Setting the Historical Alarms Acknowledgement Task

This procedure describes how to set the number of days.
The system executes the historical alarms acknowledgement task once per day to
automatically acknowledge historical alarms that are older than the preset number of
days. Users can set the number of days.
Steps
1. Click Automatically Acknowledge History Alarms in the Task Management tree.
The task information is displayed in the right pane, see Figure 3-16.
Figure 3-16 Automatically Acknowledge History Alarms Task
3-20

For a description of the toolbar buttons for managing the historical alarms
acknowledgement task, refer to Table 3-6.
Table 3-6 Toolbar Buttons for Managing the History Alarms Acknowledgement Task
Button Description
Obtains the latest task settings from the server.
Modifies the number of days to determine historical alarms to be

automatically acknowledged.
Activates the task.
Suspends the task.
2. Click on the toolbar. The spin box under Day Setting is activated.
3. Enter or select a new number in the spin box.
4. Click .
3.3 Managing MML Tasks

3.3.1 Creating an MML Task
Users can schedule a Man Machine Language (MML) task that specifies the actions to be
performed in MML commands. The system executes the MML commands in the task in
accordance with the preset schedule.
This procedure describes how to create an MML task.
Steps
2. Click MML Timing Task in the Task Management tree. All existing MML tasks (if
there are any in the system) are displayed in the right pane, see Figure 3-17.
3-21

Figure 3-17 MML Tasks
For a description of the toolbar buttons for managing MML tasks, refer to Table 3-7.
Table 3-7 Toolbar Buttons for Managing MML Timing Tasks
Button Description
Creates an MML task.
Displays the settings of an MML task.
Modifies an MML task.
Deletes an MML task.
Activates an MML task.
Suspends an MML task.
Displays the execution results of an MML task.
Displays the execution log of an MML task.
Searches for specific MML tasks by keyword.
Determines the columns displayed in the task list.
3. Click on the toolbar. The Create Task dialog box is displayed, see Figure 3-18.
3-22

Figure 3-18 Create Task Dialog Box (Basic Information Tab)
4. Enter or set necessary parameters on the Base Information tab.

For a description of the parameters on the Basic Information tab, refer to Table 3-8.
Table 3-8 Basic Information Tab Parameter Descriptions
Task Name Task name
Task Description Task description
Task Status Select an initial status for the new MML task. The options are:
l Active: The system will execute an active task when the preset
start time is reached.
l Suspended: The system will not execute a suspended task
even when the preset start time is reached.
Edit Command A mode for command line editing, which requires users to enter MML
commands in the dialog box.
MML Available when Edit Command is selected.

Enter MML commands to be executed line by line with each line
ending with a semicolon.
For details about MML commands, refer to the NetNumen U31 R18
Unified Element Management System MML Command Reference.
3-23

Refer to Script Files A mode for command line editing. Users must select an operation
object from the Operation Object drop-down list and select a script
file in which MML commands to be executed have been edited in
advance, and click Import. The imported script file is displayed in
the Command text box.
Operation Object Select an object on which the system will perform operations in
accordance with the MML commands in the selected script file.
File Path Displays the path of the selected script file.
Command Displays the MML commands in the selected script file.
5. Click the Policy tab, see Figure 3-19.
Figure 3-19 Create Task Dialog Box (Policy Tab)
6. Perform the following steps to set a task schedule:

a. Under Plan Type, select an execution period type from the drop-down list (By Day,
By Week, By Month, Hourly, or Once), and then set necessary parameters.
3-24

Note:
If Once is selected from the drop-down list, proceed to Step 7 after setting the
execution time.
For example, if an MML task is to be executed on Monday every two weeks, users
need to select By Week from the drop-down list, enter 2 in the text box, and select
Monday in the Plan Type area (see Figure 3-20).
Figure 3-20 Plan Type Area
Note:
The Execution Time area is only available when By Day, By Week, or By Month
is selected under Plan Type.
b. Under Execution Time, set the execution time.

l To set the execution time at a point, click Execute at, and enter the time in
the text box.
l To set the execution time in a period of time, click By time period, and enter
the time period and Granularity.
c. Under Duration, select a start date, and then select an end date or select Never
End as needed.
7. Click OK. A new MML task is displayed in the right pane of the Task Management
window.
3.3.2 Displaying the Settings of an MML Task

This procedure describes how to display the settings of an MML task.
Steps
3-25

2. Click MML Timing Task in the Task Management tree. All existing MML tasks are
displayed in the right pane.
3. Locate the MML task to be displayed, and then do one of the following:
l Click the task, and then click on the toolbar.
l Right-click the task, and then click View Task.
l Double-click the task.
The View Task dialog box is displayed, showing the basic information of the task on
the Basic Information tab by default.
4. Click the Policy tab. The task schedule is displayed on the Policy tab.
5. Click OK.
3.3.3 Modifying an MML Task

This procedure describes how to modify an MML task.
Prerequisite
The status of the MML task to be modified is “Suspend”.
Steps
3. Locate the MML task to be modified, and then do one of the following:
l Right-click the task, and then click Modify Task.
The Modify Task dialog box is displayed.
Note:
For a description of the parameters on the Basic Information and Policy tabs, refer
to “3.3.1 Creating an MML Task”.
The task name and status cannot be modified.
4. On the Base Information tab, modify the task description and the MML commands
as needed.
5. Click the Policy tab, and then modify the task schedule as needed.
3-26

6. Click OK.
3.3.4 Activating an MML Task

This procedure describes how to activate an MML task.
Steps
3. Locate the MML task to be activated, and then do one of the following:
l Right-click the task, and then click Activate Task.
A confirmation box is displayed.
4. Click Yes to continue. The MML task status changes from “Suspend” to “Active”.
3.3.5 Suspending an MML Task

This procedure describes how to suspend an MML task.
Steps
3. Locate the MML task to be suspended, and then do one of the following:
l Right-click the task, and then click Suspend Task.
A confirmation box is displayed.
4. Click Yes to continue. The MML task status changes from “Active” to “Suspend”.
3.3.6 Displaying the Execution Log of an MML Task

This procedure describes how to display the execution log of an MML task.
3-27

Steps
3. Locate the MML task whose execution log is to be displayed, and then do one of the
following:
l Right-click the task, and then click View Log.
The View Log dialog box is displayed, listing all log records of the task.
4. To display the details of a log record, double-click the record, or right-click the record
and click Display Log Detail. The Log Detail dialog box is displayed.
5. Click Close. The Log Detail dialog box is closed.
6. Click OK. The View Log dialog box is displayed.
3.3.7 Displaying the Execution Result of an MML Task

The result on each MML task execution is saved in a ZIP file, which contains the execution
result of each MML command specified in the task. Users can view and export the
execution result of an MML task.
This procedure describes how to display the execution result of an MML task.
Steps
3. Locate the MML task whose execution result is to be displayed, and then do one of
the following:
l Right-click the task, and then click View Execution Result.
The View Execution Result dialog box is displayed, listing all result files of the task,
see Figure 3-21.
3-28

Figure 3-21 View Execution Result Dialog Box (Result Files)
4. Select a result file, and then click in the View Execution Result dialog box.
Another View Execution Result dialog box is displayed, showing the execution result
of each MML command, see Figure 3-22.
Figure 3-22 View Execution Result Dialog Box (Command Execution Results)
3-29

5. Double-click a command. The details of the command execution result are displayed
under Execution Command Result.
6. Click Close.
3.3.8 Deleting an MML Task

This procedure describes how to delete an MML task.
Prerequisite
The status of the MML task to be deleted is “Suspend”.
Steps
3. Locate the MML task to be deleted, and then do one of the following:
l Right-click the task, and then click Delete Task.
A confirmation dialog box is displayed.
4. Click Yes to continue. The MML task disappears from the Task Management window.
3-30

Chapter 4
System Backup and
Restoration
Table of Contents
System Backup and Restore Window.........................................................................4-1
Backup Operations.....................................................................................................4-2
Restore Operations ..................................................................................................4-12
4.1 System Backup and Restore Window

Users can manually perform system backup and restoration operations in the System
Backup and Restore window on the client GUI.
Figure 4-1 shows the System Backup and Restore window.
Figure 4-1 System Backup and Restore Window
In the left pane of the System Backup and Restore window, all available backup and
restoration operations are listed in a navigation tree.
Being different from the scheduled backup and deletion tasks in the Task Management
window, which are automatically executed by the system, the backup and deletion
operations in the System Backup and Restore window are manually performed. In
4-1

addition, users can modify the backup or restore settings in the System Backup and
Restore window before performing a backup or restore operation.
Methods for Opening the Window

Users can use either of the following method to open the System Backup and Restore
window.
l On the menu bar, select Maintenance > System Backup and Restore.
l On the toolbar, click .
If the button is not available on the toolbar, right-click a blank area on the toolbar,
and then select Customize from the shortcut menu to customize buttons to be
displayed on the toolbar.
4.2 Backup Operations

4.2.1 Backing Up the Entire Database Structure
This procedure describes how to back up the entire database structure, including table
structures, indexes, views, triggers, functions, and processes.
Steps
1. Select Maintenance > System Backup and Restore from the menu bar. The System
Backup and Restore window is displayed.
2. Click Backup Whole DB Structure in the Backup and Restore tree. The backup
settings are displayed in the right pane, see Figure 4-2.
Figure 4-2 Backup Whole DB Structure
3. To change the path for saving backup files, perform the following operations:
a. Click Browse... next to the Backup File Save Path at Server box. The Open
dialog box is displayed.
4-2

Chapter 4 System Backup and Restoration
b. Select a new path, and then click Open. The new path is displayed in the Backup
File Save Path at Server text box.
4. To download the backup files from the server to the local client upon backup
completion, perform the following operations:
a. Select the Backup File Download Path at Client check box. The text box and
the Browse... button are activated.
b. To change the path, click Browse.... The Open dialog box is displayed.
c. Select a new path on the local client, and then click Open.
5. Click Execute. The system starts backing up the entire database structure and
displays the backup process and result in the Execution Result area.
4.2.2 Backing Up the Basic Data

This procedure describes how to back up the basic data in the system. The basic data
refers to the data indispensible for server operation, including the application performance
data, application resource data, ITMP basic data, common platform data, common alarm
data, and common performance data. The backup only includes the data records.
Steps
2. Click Backup Basic Data in the Backup and Restore tree. The backup settings are
displayed in the right pane, see Figure 4-3.
Figure 4-3 Backup Basic Data
4-3

a. Click Browse... next to the Backup File Save Path at Server text box. The Open
5. Click Execute. The system starts backing up all basic data and displays the backup
process and result in the Execution Result area.
4.2.3 Backing Up Files

This procedure describes how to back up version files, configuration files, and/or runtime
files in the system.
Context
The system supports backing up three types of files on the server: version files,
configuration files, and runtime files.
l Version files are all files generated on the server except those generated during
runtime.
l Configuration files are all configuration-related files on the server.
l Runtime files are all files generated during runtime on the server.
Note:
The runtime files backed up by this operation do not contain log files generated during
runtime.
Steps
2. Click Backup File in the Backup and Restore tree. The backup settings are displayed
4-4

Figure 4-4 Backup File
3. Select Version files, Configuration files, and/or Runtime files as required.

6. Click Execute. The system starts backing up the version files, configuration files,
and/or runtime files on the server, and displays the backup process and result in the
Execution Result area.
4.2.4 Backing Up and Deleting Log Data

This procedure describes how to back up and delete the operation logs, system logs,
and/or security logs in the system.
Steps
4-5

2. Click Backup and Deletion Log Data in the Backup and Restore tree. The backup
and deletion settings are displayed in the right pane, see Figure 4-5.
Figure 4-5 Backup and Deletion Log Data
3. Change the backup and/or deletion settings as required.

For a description of the parameters for log data backup and deletion, refer to Table
4-1.
Table 4-1 Parameter Descriptions for Log Data Backup and Deletion
Backup and Deletion Log data backup and/or deletion operation to be performed. The
Operation options are:
l Backup Only: used for backing up log data only
l Backup and Deletion: used for backing up and deleting log data
l Deletion Only: used for deleting log data only
Backup and Deletion Types of log data to be backed up and/or deleted. The options are:
Operation Content Operation Log, System Log, and Security Log.
Backup Filter Type Set a period during which the log data is to be backed up by selecting
a backup filter type and entering a number (T) in T Time next to
Backup Filter Type.
The Backup Filter Type options are:
l All: used for backing up all log data
l Latest T Day(s) (default): used for backing up the log data
generated in the last T days.
l T Day(s) Ago: used for backing up the log data generated T
days ago.
l Latest T Month(s): used for backing up the log data generated in
the last T months.
4-6

l T Month(s) Ago: used for backing up the log data generated

T months ago.
Users can click the corresponding button to display the exact

period during which the log data is to be backed up in a callout.
Deletion Filter Type Set a period during which the log data is to be deleted by selecting
a deletion filter type and entering a number (T) in T Time next to
Deletion Filter Type.
The Deletion Filter Type options vary with the selected backup filter
type. For example, if Latest T Day(s) is selected from Backup Filter
Type, the Deletion Filter Type options are:
l T Day(s) Ago (default): used for deleting the log data generated T
days ago.
l Latest T Day(s): used for deleting the log data generated in the
last T days.

period during which the log data is to be deleted in a callout.
6. Click Execute. The system starts backing up and/or deleting the required log data and
displays the backup and/or deletion process and result in the Execution Result area.
4.2.5 Backing Up and Deleting Alarm Data

This procedure describes how to back up and delete historical alarm data and/or
notification data in the system.
4-7

Steps
2. Click Backup and Deletion Alarm Data in the Backup and Restore tree. The backup
Figure 4-6 Backup and Deletion Alarm Data
3. Change the backup and/or deletion settings as required.

For a description of the parameters for alarm data backup and deletion, refer to Table
4-2.
Table 4-2 Parameter Descriptions for Alarm Data Backup and Deletion
Backup and Deletion Alarm data backup and/or deletion operation to be performed. The
Operation options are:
l Backup Only: used for backing up alarm data only
l Backup and Deletion: used for backing up and deleting alarm
data
l Deletion Only: used for deleting alarm data only
Backup and Deletion Types of alarm data to be backed up and/or deleted. The options are:
Operation Content History Alarm Table and Notification Table.
4-8

Backup Filter Type Set a period during which the alarm data is to be backed up by
selecting a backup filter type and entering a number (T) in T Time
next to Backup Filter Type.
l All: used for backing up all alarm data
l Latest T Day(s) (default): used for backing up the alarm data
generated in the last T days.
l T Day(s) Ago: used for backing up the alarm data generated T
days ago.
l Latest T Month(s): used for backing up the alarm data generated
in the last T months.
l T Month(s) Ago: used for backing up the alarm data generated
T months ago.

period during which the alarm data is to be backed up in a callout.
Deletion Filter Type Set a period during which the alarm data is to be deleted by selecting
a deletion filter type and entering a number (T) in T Time next to
Deletion Filter Type.
Type, the Deletion Filter Type options are:
l T Day(s) Ago (default): used for deleting the alarm data generated
T days ago.
l Latest T Day(s): used for deleting the alarm data generated in
the last T days.

period during which the alarm data is to be deleted in a callout.
4-9

6. Click Execute. The system starts backing up and/or deleting the required alarm data
and displays the backup and/or deletion process and result in the Execution Result
area.
4.2.6 Backing Up and Deleting Performance Data

This procedure describes how to back up and delete specific performance data in the
system, including raw data table (origin table), hourly-summarized data table (hour table),
and daily-summarized data table (day table).
Steps
2. Click Backup and Deletion PM Data in the Backup and Restore tree. The backup
Figure 4-7 Backup and Deletion PM Data
3. Set necessary parameters to determine the backup and deletion settings.
For a description of the parameters for performance data backup and deletion, refer
to Table 4-3.
4-10

Table 4-3 Parameter Descriptions for Performance Data Backup and Deletion
Backup and deletion Performance data backup and/or deletion operation to be performed.
operation The options are:
l Backup Only: used for backing up performance data only
l Backup and Deletion: used for backing up and deleting
performance data
l Deletion Only: used for deleting performance data only
NE type Select appropriate NE type(s) from the drop-down list in accordance

with the performance data to be backed up and/or deleted.
Backup and deletion Types of performance data to be backed up and/or deleted. The
operation content options are: Origin Table, Hour Table, and Day Table.
Performance Select performance objects whose measurement data (performance

Management Object data) is to be backed up and/or deleted.
Table l After NE type(s) are selected from the NE type list, all
corresponding performance objects are listed in this table.
l Select the check boxes in the Valid column, or click Select All,
Deselect All to determine the performance data to be backed
up and/or deleted.
Users can also enter a keyword in the Enter the Keyword to filter
text box to display only related performance object.
Backup filter type Set a period during which the performance data is to be backed up by
selecting a backup filter type and entering a number (T) in T Time
next to Backup Filter Type.
l All: used for backing up all performance data
l Latest T Day(s) (default): used for backing up the performance
data generated in the last T days.
l T Day(s) Ago: used for backing up the performance data
generated T days ago.
l Latest T Month(s): used for backing up the performance data
generated in the last T months.
l T Month(s) Ago: used for backing up the performance data
generated T months ago.

period during which the performance data is to be backed up in a
callout.
4-11

Deletion filter type Set a period during which the performance data is to be deleted by
entering a number (T) in T Time next to Deletion Filter Type.
Type,, only one option, T Day(s) Ago, is available in Deletion Filter
Type.

period during which the performance data is to be deleted in a callout.
4. (Optional) To change the path for saving backup files, perform the following operations:
5. (Optional) To download the backup files from the server to the local client upon backup
6. Click Execute. The system starts backing up and/or deleting the required performance
data and displays the backup and/or deletion process and result in the Execution
Result area.
4.3 Restore Operations

4.3.1 Restoring Log Data
This procedure describes how to restore log data in the database from a backup file.
Prerequisite
The log data backup file to be used is available.
Steps
4-12

2. Click Restore Log Data in the Backup and Restore tree. The restore settings are
3. Click Browse.... The Open dialog box is displayed.
4. Select the backup file (ZIP file) from which the log data is to be restored, and then click
Open. The file path is displayed in Select the Backup File box.
5. Click Execute. The system starts restoring the log data from the selected backup file
and displays the restore process and result in the Execution Result area.
4.3.2 Restoring Alarm Data

This procedure describes how to restore alarm data in the database from a backup file.
Prerequisite
The alarm data backup file to be used is available.
Steps
2. Click Restore Alarm Data in the Backup and Restore tree. The restore settings are
4. Select the backup file (ZIP file) from which the alarm data is to be restored, and then
click Open. The file path is displayed in Select the Backup File box.
5. Click Execute. The system starts restoring the alarm data from the selected backup
file and displays the restore process and result in the Execution Result area.
4.3.3 Restoring Performance Data

This procedure describes how to restore performance data in the database from a backup
file.
Context
Before restoring performance data, the system first checks whether the target PO table
contains data. If yes, the existing data needs to be cleared before importing data.
Prerequisite
The performance data backup file to be used is available.
4-13

Steps
2. Click Restore PM Data in the Backup and Restore tree. The restore settings are
4. Select the backup file (ZIP file) from which the performance data is to be restored, and
then click Open. The file path is displayed in Select the Backup File box.
5. Click Execute. The system starts restoring the performance data from the selected
backup file and displays the restore process and result in the Execution Result area.
4-14

Chapter 5
System Monitoring
Table of Contents
System Monitoring Window ........................................................................................5-1
Application Server Monitoring.....................................................................................5-2
Database Monitoring ..................................................................................................5-7
5.1 System Monitoring Window

Users can monitor the NetNumen U31 server (application server) and the system database
in the System Monitoring window on the client GUI.
Figure 5-1 shows the System Monitoring window.
Figure 5-1 System Monitoring Window
In the left pane of the System Monitoring window, the application server and the database
of the NetNumen U31 system are listed in a navigation tree. The right pane displays the
monitoring status and server information of the application server or database selected in
the navigation tree, and provides the buttons for monitoring functions.

Users can use either of the following method to open the System Monitoring window.
5-1

l On the menu bar, select Maintenance > System Monitoring.

5.2 Application Server Monitoring

5.2.1 Viewing the Application Server Information
This procedure describes how to view the basic information of the application server.
Steps
1. Select Maintenance > System Monitoring from the menu bar. The System
Monitoring window is displayed.
2. Click the application server under Server in the left navigation tree.
The basic server information is displayed in the Server Information area in the right
pane, including device name, device type, Java Name and Directory Interface (JNDI)
port, host IP address, host name, Operating System (OS) name, and EMS version,
see Figure 5-2.
Figure 5-2 Application Server Information
5.2.2 Setting Application Server Performance Monitoring

Parameters
This procedure describes how to set parameters for monitoring the application server.
5-2

Chapter 5 System Monitoring
Users can set thresholds for monitoring the CPU, RAM, and each partition of the hard disk
on the application server. If the actual usage of the CPU, RAM, or a partition of the Hard
Disk (HD) exceeds a preset threshold, the system may raise an alarm, prompting possible
performance degradation of the application server.
Steps
2. In the left navigation tree, click the application server under Server.
3. In the right pane, click Configure... under Monitor Server Performance. The
Configure Performance Monitor dialog box is displayed, see Figure 5-3.
Figure 5-3 Configure Performance Monitoring Dialog Box
4. Set necessary thresholds and monitoring periods for monitoring the CPU, RAM, and
hard disk of the application server as required.
For a description of the monitoring parameters in the Configure Performance

Monitoring dialog box, refer to Table 5-1.
Table 5-1 Parameter Descriptions for the Configure Performance Monitoring Dialog
Box
Monitoring Item Selection Area
5-3

Monitoring Item Select the items to be monitored. The options are:

Selection l CPU, RAM Monitoring for enabling CPU and RAM monitoring
l HD Monitoring for enabling hard disk monitoring
CPU, RAM Monitoring Threshold Setup Area
Usage Alarm CPU/RAM usage threshold crossing frequency

Threshold Value range: 1–10
Threshold (Critical) Set four thresholds for CPU usage and RAM usage.
Threshold (Major)
Threshold (Minor)
Threshold (Warning)
Monitoring Period CPU and RAM monitoring period

Value range: 20–120 seconds
Change the monitoring period as required by dragging the slider.
For example, the monitoring period is 120 seconds. The system will
obtain the CPU and RAM usage every 120 seconds and compare the
obtained usage with the corresponding thresholds. If the threshold
crossing frequency of the CPU or RAM usage exceeds the preset
frequency threshold, the system will raise an alarm.
HD Monitoring Threshold Setup Area
Type Select a space usage threshold type for each hard disk partition to be
monitored from the corresponding drop-down list. The options are:
l Percentage for setting thresholds in percentage
l Absolute for setting thresholds in size
l NO for disabling the monitoring of the corresponding partition
Threshold (Critical) Set four thresholds for each hard disk partition to be monitored.
Threshold (Major)
Threshold (Minor)
Threshold (Warning)
Monitoring Period HD monitoring period

Value range: 30–300 seconds
For example, the monitoring period is 300 seconds. The system will
obtain the usage of each monitored hard disk partition every 300
seconds and compare the obtained usage with the preset thresholds.
If the usage exceeds a preset threshold, the system will raise an alarm
at the corresponding severity level.
5. Click OK.
5-4

5.2.3 Starting the Application Server Monitoring

This procedure describes how to start the application server monitoring.
Context
Note:
The Run button used for starting the application server monitoring is only available when
the monitoring is suspended.
Steps
3. In the right pane, click Run under Monitor Server Performance. The system starts
monitoring the application server, including the CPU, RAM, and/or hard disk usage of
the server.
5.2.4 Suspending the Application Server Monitoring

This procedure describes how to suspend the application server monitoring.
Note:
Users do not need to suspend the application server monitoring unless absolutely
necessary.
Steps
3. In the right pane, click Suspend under Monitor Server Performance. The system
stops monitoring the application server.
5-5

5.2.5 Viewing the Application Server Performance

This procedure describes how to view the application server performance in real time.
Steps
3. In the right pane, click View... under View Server Performance. The View
Application Server Performance dialog box is displayed, see Figure 5-4.
Figure 5-4 View Application Server Performance Dialog Box
For a description of the information areas in the View Application Server

Performance dialog box, refer to Table 5-2.
5-6

Table 5-2 Area Descriptions for the View Application Server Performance Dialog
Box
Area Description
Monitoring Period Determines the frequency for refreshing the CPU, RAM, and hard disk
usage displayed in the dialog box. Users can modify a monitoring
period by dragging the corresponding slider as needed.
RAM Information Displays the information of the application server RAM.
CPU Usage Displays the CPU usage.
RAM Usage Displays the RAM usage.
HD Information Displays the usage of each hard disk partition being monitored.
4. Click OK. The View Application Server Performance dialog box is closed.
5.3 Database Monitoring

5.3.1 Viewing the Database Information
This procedure describes how to view the basic information of the database.
The database of the NetNumen U31 system can be installed on the application server or
an independent server, depending on the system configuration.
Steps
2. Click the database under Database in the left navigation tree.

The basic database information is displayed in the Basic Information of Database
Server area in the right pane, including device name, device type, database type,
database port, database version, and host IP address, see Figure 5-5.
5-7

Figure 5-5 Basic Information of Database Server
5.3.2 Setting Database Monitoring Parameters

Users can set a threshold to limit the size of the entire database on the hard disk, and/or
set thresholds for monitoring the usage of individual table spaces of the database. If the
actual database size or a table space usage exceeds a preset threshold, an alarm will be
raised.
This procedure describes how to set parameters for monitoring the database.
Steps
2. Click the database under Database in the left navigation tree.
3. In the right pane, click Configure... under Monitor Database Resource. The
Configure Database Monitoring dialog box is displayed, see Figure 5-6.
5-8

Figure 5-6 Configure Database Monitoring Dialog Box
4. Set necessary parameters for monitoring the database as required.

For a description of the monitoring parameters in the Configure Database Monitoring
dialog box, refer to Table 5-3.
Table 5-3 Parameter Descriptions for the Configure Database Monitoring Dialog Box
Monitoring Item Select the items to be monitored. The options are:

Selection l Total Database Usage Monitoring: used for monitoring the size
of the entire database
l Table Space Usage Monitoring: used for monitoring the usage
of individual table spaces
Monitoring Period Database monitoring period

Value range: 2–60 minutes
For example, the monitoring period is 2 minutes. The system will
obtain the database usage and the usage of each monitored table
space every 2 minutes and compare the obtained usage with the
corresponding preset thresholds. If the database usage or table space
usage exceeds a threshold, the system will raise an alarm.
Usage Threshold Set a database size threshold, meaning a usage threshold of the hard
disk space that is allocated for the database.
Table Space Usage Monitoring Area
5-9

Type Select a usage threshold type for each table space to be monitored
from the corresponding drop-down list. The options are:
l Percentage for setting thresholds in percentage
l Absolute for setting thresholds in size
l NO for disabling the monitoring of the corresponding table space
Threshold (Critical) Set four thresholds for each table space to be monitored.
Threshold (Major)
Threshold (Minor)
Threshold (Warning)
5. Click OK. The Configure Database Monitoring dialog box is closed.

5.3.3 Starting the Database Monitoring

This procedure describes how to start the database monitoring.
Note:
The Run button used for starting the database monitoring is only available when the
database monitoring is suspended.
Steps
2. In the left navigation tree, click the database under Database.
3. In the right pane, click Run under Monitor Database Resource. The system starts
monitoring the database size and the usage of individual table spaces.
5.3.4 Suspending the Database Monitoring

This procedure describes how to suspend the database monitoring.
Note:
Users do not need to suspend the database monitoring unless absolutely necessary.
5-10

Steps
3. In the right pane, click Suspend under Monitor Database Resource. The system
stops monitoring the database.
5.3.5 Viewing Database Resources

This procedure describes how to view the information of database resources in the
system, including table spaces, tables and processes. The displayed information can be
synchronized and exported.
Steps
1. Select Maintenance > System Monitoring from the menu bar. The System Monitor
window is displayed.
3. In the right pane, click View... under View Database Resource.
The View Database Resources dialog box is displayed, see Figure 5-7. The Table
Space Information tab displays the information of all table spaces of the database.
Figure 5-7 View Database Resources Dialog Box
4. Click the Table Information tab, and click a table space in the left pane. The
information of all tables in the selected table space is displayed in the right pane.
5-11

5. Click the Process Information tab. All database processes are displayed on this tab.
6. To refresh the resource information in dialog box, click Synchronize.
7. To export the data in the table to a local file, click Export Data.
8. Click Close. The View Database Resources dialog box is closed.
5-12

Chapter 6
IT Device Monitoring
Table of Contents
IT Monitoring Window.................................................................................................6-1
Adding an IT Device ...................................................................................................6-2
Configuring the Component Information for an IT Device..........................................6-24
Configuring Status Monitoring for an IT Device.........................................................6-26
Viewing Alarms of an IT Device ................................................................................6-28
6.1 IT Monitoring Window

IT monitoring is an optional function. Users need to apply for the software license from
ZTE and select ITMP when installing the NetNumen U31 server and client.
Users can add IT devices to be monitored and set necessary monitoring parameters in the
IT Monitoring window.
Figure 6-1 shows the IT Monitoring window.
Figure 6-1 IT Monitoring Window
6-1

The navigation tree in the left pane shows all supported IT device types. Users can add
IT devices to be monitored under the corresponding device type node.

Users can use either of the following method to open the IT Monitoring window:
l On the menu bar, select Maintenance > IT Monitoring.
6.2 Adding an IT Device

6.2.1 Adding a Server Node
Through the IT device monitoring module, users can monitor the operating status of a
server in the IT network and view alarms reported by the server. For a list of the servers
that can be monitored, refer to Table 6-1.
Table 6-1 Supported Servers
Server (Operating System) Version
AIX AIX 5.1, 5.2, and 5.3
HP-UX 10.x and 11

HP UX
HP-UX 11i v1 and v2
Solaris Solaris 8, 9, and 10
RedHat Enterprise Linux AS release 2.1, 3, and 4

RedHat Enterprise Linux ES release 3 and 4
RedHat Linux RedHat Enterprise Linux WS release 3 and 4
RedHat Linux 8 and 9
Redhat Enterprise Linux Server 6, Standard
SUSE Linux SUSE Linux Enterprise Server 8, 9, 10, and 11
Embsys CGS Linux V3.1 (2.6.18-92.1.22.zte)

CGS Linux
CGSL V3.01.12.P2
Windows Windows Server 2000, 2003, and 2008
This procedure describes how to add an AIX server node.
Prerequisite
l The root user password of the AIX server is known.
l The Telnet or SSH service is started on the AIX server, and an appropriate Telnet or
SSH port is used.
l The AIX server can be successfully pinged from the NetNumen U31 server.
l The AIX server is started up and a command prompt (# or $) is displayed.
6-2

Chapter 6 IT Device Monitoring
Steps
1. Select Maintenance > IT Monitoring from the menu bar. The IT Monitoring window
is displayed.
2. In the IT Monitoring window, right-click Server in the navigation tree and select Add
Node from the shortcut menu. The Add Node dialog box is displayed.
3. Click AIX Server in the left pane. The server parameters are displayed in the right
pane, see Figure 6-2.
Figure 6-2 Add Node Dialog Box (AIX Server)
For a description of the AIX server parameters, refer to Table 6-2.
Table 6-2 AIX Server Parameter Descriptions
Node Label (Required) Node name.
IP Address (Required) IP address of the server to be monitored.
Login User (Required) User name for logging in to the server.
Login Password (Required) Password for logging in to the server.
Login Protocol (Required) Protocol for logging in to the server.

The options are: TELNET and SSH.
Login Port (Required) Port for logging in to the server.

Default: 23 (TELNET) or 22 (SSH)
The same port must be set on the server to be monitored.
6-3

Packet Count (Required) Number of ICMP echo request messages that are sent
when the IT device monitoring module pings the server.
Value range: 1 to 4
Packet Size (Required) Size of the data field in each ICMP echo request message
that is sent when the IT device monitoring module pings the server.
Unit: bytes.
Default: 64.
Value range: 8 to 128.
TTL (Required) Maximum number of hops of ICMP messages that are

sent when the IT device monitoring module pings the server.
Default: 128.
Timeout (Required) Timeout value for an echo reply to an echo request

message sent by the IT device monitoring module.
Unit: seconds.
Trap Listen Enables the IT device monitoring module to receive traps from the
server hardware. Necessary trap configuration is required on the
server to support this function.
When the check box is selected, the Server Model drop-down list
box is displayed. Users are required to select an appropriate server
model from the drop-down list.
Node Model (Optional) Device model, depending on the actual server.
Asset ID (Optional) Inventory ID, depending on the actual server.
Join Net Date Date when the server node is added in the NetNumen U31 system.
Memo (Optional) Server description.
4. Configure the parameters as required.

5. Click Access Test. A message confirming the successful connection between the
NetNumen U31 server and the AIX server is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added server node is displayed under
Server in the navigation tree in the IT Monitoring window.
6-4

6.2.2 Adding a Database Node

Through the IT device monitoring module, users can monitor the operating status of
a database management system in the IT network and view alarms reported by the
database. For a list of the databases that can be monitored, refer to Table 6-3.
Table 6-3 Supported Databases
Database Type Version
Oracle Oracle database 8i/, 9i, 10g, and 11g
SQL Server SQL Server 2000, 2005, and 2008
Sybase Sybase 12.5, and 15.0
Sybase IQ Sybase IQ 12.7, and 15.1
This procedure describes how to add an Oracle database node.
Prerequisite
l The system user password, System Identifier (SID), and the listener port number of
the Oracle database are known.
l The NetNumen U31 server can access the database through Java Database
Connectivity (JDBC).
Steps
is displayed.
2. In the IT Monitoring window, right-click Database in the navigation tree and select
Add Node from the shortcut menu. The Add Node dialog box is displayed.
3. Click Oracle DataBase in the left pane. The database parameters are displayed in
the right pane, see Figure 6-3.
6-5

Figure 6-3 Add Node Dialog Box (Oracle DataBase)
For a description of the Oracle database parameters, refer to Table 6-4.
Table 6-4 Oracle Database Parameter Descriptions
IP Address (Required) IP address of the Oracle database to be monitored.
SID (Required) Database SID.
Database User (Required) User name for logging in to the database.

Default: system.
Database Password (Required) Password for logging in to the database.
Database Port (Required) Port used by Oracle database listener.

Default: 1521.
Oracle Database Click this check box when two Oracle databases are configured for
Streams Duplication streams duplication in the system.
Node Model (Optional) Database model, depending on the actual database.
Asset ID (Optional) Inventory ID, depending on the actual database.
Join Net Date Date when the database node is added in the NetNumen U31
system.
Memo (Optional) Database description.
6-6


NetNumen U31 server and the Oracle database is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added database node is displayed under
Database in the navigation tree in the IT Monitoring window.
6.2.3 Adding a Router Node

Through the IT device monitoring module, users can monitor and manage a router in the
IT network. For a list of the routers that can be monitored, refer to Table 6-5.
Table 6-5 Supported Routers
Vendor Model
Cisco 2600, 2800, 3600, 3700, and 3800 series

7200, 7300, 7400, 7500, and 7600 series
10000 and 12000 series
ASR 9000 series
ZTE ZXR10 router series
Juniper J series (J2320, J2350, J4350, and J6350)

M series (M7i and M10i)
MX series (MX240, MX480, and MX960)
T series (T320, T640, and T1600)
This procedure describes how to add a Cisco router node.
Prerequisite
l The router can be successfully pinged from the NetNumen U31 server.
l The NetNumen U31 server can access the router via Simple Network Management
Protocol (SNMP).
Steps
is displayed.
2. In the IT Monitoring window, right-click Router in the navigation tree and select Add
3. Click Cisco Router in the left pane. The router parameters are displayed in the right
6-7

Figure 6-4 Add Node Dialog Box (Cisco Router)
For a description of the router parameters, refer to Table 6-6.
Table 6-6 Router Parameter Descriptions
IP Address (Required) IP address of the router to be monitored.
SNMP Port (Required) SNMP port number.

Default: 161.
(Required) SNMP version.

The options are: V1, V2C, and V3.
SNMP Version
If V3 is selected, additional parameters are required, including SNMP
User Name, SNMP Context Name, and SNMP Security Level.
(Required) SNMP read-only community string for authentication.

SNMP Community
Default: public.
when the IT device monitoring module pings the router.
Value range: 1 to 4
6-8

that is sent when the IT device monitoring module pings the router.
Unit: bytes.
Default: 64.

sent when the IT device monitoring module pings the router.
Default: 128.

Unit: seconds.
Node Model (Optional) Router model, depending on the actual router.
Asset ID (Optional) Inventory ID, depending on the actual router.
Join Net Date Date when the router node is added in the NetNumen U31 system.
Memo (Optional) Router description.

NetNumen U31 server and the Cisco router is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added router node is displayed under
Router in the navigation tree in the IT Monitoring window.
6.2.4 Adding a Switch Node

Through the IT device monitoring module, users can monitor and manage a switch in the
IT network. For a description of the switches that can be monitored by the system, refer
to Table 6-7.
Table 6-7 Supported Switches
Vendor Model
AT AT-FS750, GS950, 8000, 8300, 850, 8000S, and 9400 Series.

AT-8600, 8700, 8800, 8900, 9700, 9400s, 9800, 9900, and 9900s series.
Cisco Cisco Catalyst 2960, 2970, 3400, 3750, 4500, and 6500 series.
ZTE ZXR10 switch series and L3 ROS switch series.
Juniper EX series.
6-9

This procedure describes how to add a Cisco switch node.
Prerequisite
l The switch can be successfully pinged from the NetNumen U31 server.
l The NetNumen U31 server can access the switch via SNMP.
Steps
is displayed.
2. In the IT Monitoring window, right-click Switch in the navigation tree and select Add
3. Click Cisco Switch in the left pane. The switch parameters are displayed in the right
Figure 6-5 Add Node Dialog Box (Cisco Switch)
For a description of the switch parameters, refer to Table 6-8.
Table 6-8 Switch Parameter Descriptions
IP Address (Required) IP address of the switch to be monitored.
6-10


Default: 161.
SNMP Version (Required) SNMP version.

SNMP Community (Required) SNMP read-only community string for authentication.

Default: public.
when the IT device monitoring module pings the switch
Value range: 1 to 4
Packet Size (byte) (Required) Size of the data field in each ICMP echo request message
that is sent when the IT device monitoring module pings the switch.
Unit: bytes.
Default: 64.

sent when the IT device monitoring module pings the switch.
Default: 128.
Timeout (S) (Required) Timeout value for an echo reply to an echo request
Unit: seconds.
Node Model (Optional) Switch model, depending on the actual switch.
Asset ID (Optional) Inventory ID, depending on the actual switch.
Join Net Date Date when the switch node is added in the NetNumen U31 system.
Memo (Optional) Switch description.

NetNumen U31 server and the Cisco switch is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added switch node is displayed under
Switch in the navigation tree in the IT Monitoring window.
6-11

6.2.5 Adding a Firewall Node

Through the IT device monitoring module, users can monitor and manage a firewall in the
IT network. For a list of the firewalls that can be monitored by the system, refer to Table
6-9.
Table 6-9 Supported Firewalls
Vendor Model
CheckPoint R65, R70, and CPPWR-APP-M2070
Juniper NetScreen series, SSG series, and ISG series
Cisco PIX series and ASA series
H3C F5000
ZTE ZXSEC U1612 and US350
Cisco (dual) PIX series and ASA series
This procedure describes how to add a Juniper firewall node.
Prerequisite
l The firewall can be successfully pinged from the NetNumen U31 server.
l The NetNumen U31 server can access the firewall via SNMP.
Steps
is displayed.
2. In the IT Monitoring window, right-click Firewall in the navigation tree and select Add
3. Click Juniper Firewall in the left pane. The firewall parameters are displayed in the
right pane, see Figure 6-6.
6-12

Figure 6-6 Add Node Dialog Box (Juniper Firewall)
For a description of the firewall parameters, refer to Table 6-10.
Table 6-10 Firewall Parameter Descriptions
IP Address (Required) IP address of the firewall to be monitored.
Device Model (Required) Firewall model.

Default: NetScreen/SSG/ISG.

Default: 161.
SNMP Version (Required) SNMP version.

SNMP Community (Required) SNMP read-only community string for authentication.

Default: public.
when the IT device monitoring module pings the firewall
Value range: 1 to 4
6-13

that is sent when the IT device monitoring module pings the firewall.
Unit: bytes.
Default: 64.

sent when the IT device monitoring module pings the firewall.
Default: 128.
Unit: seconds.
Node Model (Optional) Firewall model, depending on the actual firewall.
Asset ID (Optional) Inventory ID, depending on the actual firewall.
Join Net Date Date when the firewall node is added in the NetNumen U31 system.
Memo (Optional) Firewall description.

NetNumen U31 server and the Juniper firewall is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added firewall node is displayed under
Firewall in the navigation tree in the IT Monitoring window.
6.2.6 Adding a Cluster Node

Through the IT device monitoring module, users can monitor and manage a cluster in the
IT network. For a list of the clusters that can be monitored by the system, refer to Table
6-11.
Table 6-11 Supported Clusters
Cluster Model
AIX HACMP HACMP 5.1, 5.2, and 5.3 for AIX.
HP MC ServiceGuard MC/ServiceGuard A 11.09, A 11.12, and A 11.16.
Symantec VCS VCS 4.1 and 5.0.
NewStart HA Cluster 3.0, 3.0b-4175A, or later version.
NEC NEC ExpressCluster X 2.0 for Linux.
6-14

This procedure describes how to add a VCS cluster node.
Prerequisite
The NetNumen U31 server can access the cluster via SNMP.
Steps
is displayed.
2. In the IT Monitoring window, right-click Cluster in the navigation tree and select Add
3. Click VCS Cluster in the left pane. The cluster parameters are displayed in the right
Figure 6-7 Add Node Dialog Box (VCS Cluster)
For a description of the cluster parameters, refer to Table 6-12.
Table 6-12 Cluster Parameter Descriptions
IP Address (Required) IP address of the cluster to be monitored.
Host Operating System (Required) Operating system installed on the host of the cluster.
Type Cluster model.
6-15

when the IT device monitoring module pings the cluster.
Value range: 1 to 4
that is sent when the IT device monitoring module pings the cluster.
Unit: bytes.
Default: 64.

sent when the IT device monitoring module pings the cluster.
Default: 128.
Unit: seconds.
Node Model (Optional) Cluster model, depending on the actual cluster.
Asset ID (Optional) Inventory ID, depending on the actual cluster.
Join Net Date Date when the cluster node is added in the NetNumen U31 system.
Memo (Optional) Cluster description.
4. Set the parameters as required.

NetNumen U31 server and the cluster is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added cluster node is displayed under
Cluster in the navigation tree in the IT Monitoring window.
6.2.7 Adding a Storage Device Node

Through the IT device monitoring module, users can monitor the operating status of a
storage device in the IT network and manage alarms raised by the device. For a list of the
storage devices that can be monitored by the system, refer to Table 6-13.
Table 6-13 Supported Storage Devices
Disk Array Model
EMC (CX3/AX4) disk arrays CX300, CX320, and AX4-5
EMC (NX4/NS) disk arrays NX4, NS-120, and VNXe.
6-16

Disk Array Model
NetApp disk arrays FAS270c, FAS2020A, FAS2050, and FAS 3070 (with Data
ONTAP Release 7.2.6.1)
BakBone NetVault NetVault
Brocade SAN switches SW200E, SW300, SW4100, and SW5100 (with Brocade Fabric
OS V6.1.0 or earlier versions)
SUN disk arrays 6100, 6140, 6180, 2510, 2540, and 3320
SUN tape library SL24 and SL48
HDS disk arrays AMS200, AMS500, and AMS2100
Fujitsu disk arrays DX60, DX80, DX90, E2K M100, E4K M600, and E8K M1200
IBM disk systems DS4700, DS4800, DS5020, DS3200, DS3300, DS3400,

DS3500, DS3512, and N6210
HP MSA disk array MSA2000sa, MSA2000fc, and P2000G3
HP MSL tape library 2024 and 4048
HP EVA disk array 4400
HP AiO disk array S600c
HP SAN switch B-Series (The HP StorageWorks Fabric OS 6.x)
Dell MD disk array MD3000.
ZTE disk arrays S260V2, S300V3, S510, S2100, and S2200
Cisco MDS fabric switches 9000 series
IBM TS tape libraries TS3100, TS3200, and TS3310
OpsCenter NBU 7.0
This procedure describes how to add an IBM disk system node.
Prerequisite
l The IBM disk system can be successfully pinged from the NetNumen U31 server.
l The disk system is configured with the IP address of the NetNumen U31 server as an
SNMP trap address.
l The SNMP community string of the disk system is set to “public”.
Steps
is displayed.
2. In the IT Monitoring window, right-click Storage in the navigation tree and select Add
6-17

3. Click IBM SM in the left pane. The disk system parameters are displayed in the right
Figure 6-8 Add Node Dialog Box (IBM SM)
For a description of the disk system parameters, refer to Table 6-14.
Table 6-14 Disk System Parameter Descriptions
IP Address (Required) IP address of the disk system.
when the IT monitoring module pings the disk system.
Value range: 1 to 4
that is sent when the IT monitoring module pings the disk system.
Unit: bytes.
Default: 64.

sent when the IT monitoring module pings the disk system.
Default: 128.
6-18


Unit: seconds.
Node Model (Optional) Device model, depending on the actual storage device.
Asset ID (Optional) Inventory ID, depending on the actual storage device.
Join Net Date Date when the storage device node is added in the NetNumen U31
system.
Memo (Optional) Storage device description.

NetNumen U31 server and the IBM disk system is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added storage device node is displayed
under Storage in the navigation tree in the IT Monitoring window.
6.2.8 Adding an Application Node

Through the IT device monitoring module, users can monitor and manage applications in
the IT network. For a list of the supported applications, refer to Table 6-15.
Table 6-15 Supported Applications
Application Type Version
BIND BIND9.2.3 to BIND9.4.3P4
TOMCAT TOMCAT5.5 and TOMCAT6.x series
NTP Windows Server 2000 and 2003

Solaris 8, 9, and 10
NetNumen (EMS) UEP V4.11.10B4 and later versions
Tivoli storage manager Tivoli Storage Manager Version 6.3
WEBLOGIC WebLogic10.3.6
Trend antivirus WFBS6.0

software
DNS Windows 2003 server DNS
This procedure describes how to add a BIND service node.
6-19

Steps
is displayed.
2. In the IT Monitoring window, right-click Application in the navigation tree and select
Add Node from the shortcut menu. The Add Node dialog box is displayed.
3. Click BIND Service in the left pane. The service parameters are displayed in the right
Figure 6-9 Add Node Dialog Box (BIND Service)
For a description of the BIND service parameters, refer to Table 6-16.
Table 6-16 BIND Service Parameter Descriptions
(Optional) Click this button to obtain the host information automatically

Choose the host server when the host (server) providing the BIND service has been added in
the IT device monitoring module.
(Required) IP address of the server where the BIND service is

IP Address
installed.
(Required) User name for logging in to the server where the BIND
Login User
service is installed.
6-20

(Required) Password for logging in to the server where the BIND

Login Password
service is installed.
(Required) Protocol for logging in to the server where the BIND

Login Protocol service is installed.
The options are: TELNET (default) and SSH.
(Required) Port for logging in to the server where the BIND service
is installed.
Login Port
Default: 23 (TELNET) or 22 (SSH)
The port configuration must be consistent with that on on the server.
The Server is (Optional) Select this check box if the BIND service to be monitored is
WINDOWS host installed on a WINDOWS server.
Install Dir (Required) Directory where the BIND service is installed.
Node Model (Optional) BIND service type, depending on the actual BIND service.
(Optional) BIND service inventory ID, depending on the actual BIND

Asset ID
service.
Date when the BIND service node is added in the NetNumen U31
Join Net Date
system.
Memo (Optional) BIND service description.

NetNumen U31 server and the host of the BIND service is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added BIND service is displayed under
Application in the navigation tree in the IT Monitoring window.
6.2.9 Adding Other Nodes

The IT device monitoring module also supports the monitoring and management of other
IT devices, such as traffic manager and shelves. For a list of the additional supported
devices, refer to Table 6-17.
Table 6-17 Additional Supported IT Devices
Device Type Model
F5 traffic manager F5 BIGIP V9.1.2, V9.3.0, and later versions
HP BLC BLC7000 and BLC3000
6-21

Device Type Model
HP GBE2C blade switch GBE2C blade switch in HP BLc7000
HP VC module VC module in HP BLc7000
AD508, 1008, 2008, and 4008 (ODS VL)

Radware AppDirector AD1016, AD2016, and AD4016 (ODS2 V2)
AD8016, AD12016, and AD16016 (ODS3V2)
ZTE power supply PPC44 D004
Cisco UCS Cisco UCS
IMM IBM X3200, X3250, X3500, X3550, X3650, and X3850
F5 traffic manager (dual) F5 BIGIP V9.1.2, V9.3.0, and later versions
IBM blade IBM PS702, HS22, and PS700
SeGW SeGW
ZXSDR NT8200 ZXSDR NT8200
DCS DCS
ATCA_LB10 LB10
This procedure describes how to add a Security Gateway (SeGW) node.
Prerequisite
The SeGW can be successfully pinged through the NetNumen U31 server.
Steps
is displayed.
2. In the IT Monitoring window, right-click Other in the navigation tree and select Add
3. Click SeGW in the left pane. The server parameters are displayed in the right pane,
see Figure 6-10.
6-22

Figure 6-10 Add Node Dialog Box (SeGW Node)
For a description of the SeGW parameters, refer to Table 6-18.
Table 6-18 SeGW Parameter Descriptions
SeGW Address (Required) IP address of the SeGW.
ATCA_CMM Address (Required) IP address of the ATCA_CMM.
(Required) SNMP port number.

SNMP Port
Default: 161.
(Required) SNMP version.

SNMP Version If V3 is selected, additional parameters are required, including
SNMP User Name, SNMP Context Name, and SNMP Security
Level.
(Required) SNMP read-only community string.

SNMP Community
Default: public.
(Required) SNMP write-only community string.

SNMP Write Community
Default: public.
(Required) Number of ICMP echo request messages that are sent

Packet Count when the IT device monitoring module pings the SeGW
Value range: 1 to 4
6-23

(Required) Size of the data field in each ICMP echo request

message that is sent when the IT device monitoring module pings
the SeGW.
Packet Size (byte)
Unit: bytes.
Default: 64.
(Required) Maximum number of hops of ICMP messages that are

sent when the IT device monitoring module pings the SeGW.
TTL
Default: 128.
(Required) Timeout value for an echo reply to an echo request

Timeout (s)
Unit: seconds.
Node Model (Optional) SeGW model, depending on the actual SeGW.
Asset ID (Optional) Inventory ID, depending on the actual SeGW.
Join Net Date Date when the SeGW node is added in the NetNumen U31 system.
Memo (Optional) SeGW description.

NetNumen U31 server and the SeGW is displayed.
6. Click OK.
7. Click OK in the Add Node dialog box. The added SeGW node is displayed under
Other in the navigation tree in the IT Monitoring window.
6.3 Configuring the Component Information for an IT

Device
Some IT devices have multiple components, such as network adapters, file systems, disk
drives, and processes. After a node is added for such an IT device in the NetNumen U31
system, some components are monitored by the system and the others are not monitored,
depending on the default device settings. Users can enable or cancel the monitoring of
specific components as needed.
This procedure describes how to configure the components to be monitored for a database
node.
6-24

Prerequisite
l The IT device has component information.
l The IT device has been connected to the IT monitoring module.
Steps
is displayed.
2. In the IT Monitor window, click the database node to be configured in the navigation
tree. The basic information of the database is displayed on the Basic Information tab
Figure 6-11 Basic Information Tab
3. Click the Component Information tab. The database components (table spaces) that
are being monitored are displayed, see Figure 6-12.
6-25

Figure 6-12 Component Information Tab
4. Click Set. The Component Set dialog box is displayed, see Figure 6-13.
Figure 6-13 Component Set Dialog Box
5. Select the table spaces to be monitored or cancel the selection of specific table spaces
as required, and the click OK. The table space list on the Component Information
tab changes accordingly.
6.4 Configuring Status Monitoring for an IT Device

This procedure describes how to configure status monitoring for an IT device. Users can
start or stop monitoring the status, configure the polling time, and modify the settings of
some parameters, such as log filter keyword and port configuration.
6-26

The status monitoring items that can be configured in the NetNumen U31 system vary with
different IT devices.
Steps
is displayed.
2. In the IT Monitor window, click the database node to be configured in the navigation
tree. The basic information of the database is displayed on the Basic Information tab
Figure 6-14 Basic Information Tab
3. Click the Status Monitoring tab. The status monitoring settings are displayed, see
Figure 6-15.
6-27

Figure 6-15 Status Monitoring Tab
For a description of the buttons for configuring the status monitoring settings, refer to
Table 6-19.
Table 6-19 Descriptions for the Buttons on the Status Monitoring Tab
Button Description
Start Starts the status monitoring
Stop Stops the status monitoring
Set Sets conditions for alarm reporting
4. Click an appropriate button to start, stop, or set the monitoring of logs, database status,
or the database analyzer.
6.5 Viewing Alarms of an IT Device

After an IT device node is added in the NetNumen U31 system, users can view alarm
information reported by the IT device on the client GUI.
This procedure describes how to view alarms of a database monitored by the IT device
monitoring module.
Steps
is displayed.
2. In the IT Monitor window, right-click the monitored database in the navigation tree. A
shortcut menu is displayed, see Figure 6-16.
6-28

Figure 6-16 Shortcut Menu for Alarm Display
3. Select a command from the shortcut menu as required. The Fault Management
window is displayed in which a tab shows the required alarms, see Figure 6-17.
Figure 6-17 Fault Management Window
6-29

6-30

Figures
Figure 1-1 IT Device Monitoring Procedures ............................................................. 1-5
Figure 2-1 Configuration of Remote Backup Path Dialog Box ................................... 2-1
Figure 2-2 Remote Backup Path ............................................................................... 2-2
Figure 3-1 Task Management Window ...................................................................... 3-1
Figure 3-2 Modify Task Start Time Dialog Box........................................................... 3-3
Figure 3-3 Modify Time Dialog Box ........................................................................... 3-3
Figure 3-4 Log Data Backup and Deletion Task ........................................................ 3-4
Figure 3-5 Set Capacity Dialog Box .......................................................................... 3-5
Figure 3-6 Backup Description Area.......................................................................... 3-7
Figure 3-7 PM Data Backup and Deletion Task ......................................................... 3-8
Figure 3-8 Alarm Data Backup and Deletion Task ................................................... 3-10
Figure 3-9 Set Capacity Dialog Box ........................................................................ 3-11
Figure 3-10 Backup Basic Data Task ...................................................................... 3-13
Figure 3-11 Backup Whole DB Structure Task......................................................... 3-15
Figure 3-12 Backup File Task.................................................................................. 3-17
Figure 3-13 Directory Monitoring Task..................................................................... 3-18
Figure 3-14 Performance Data Backup Directory Monitoring Dialog Box ................. 3-19
Figure 3-15 Directory Monitor File Information Dialog Box ...................................... 3-20
Figure 3-16 Automatically Acknowledge History Alarms Task.................................. 3-20
Figure 3-17 MML Tasks .......................................................................................... 3-22
Figure 3-18 Create Task Dialog Box (Basic Information Tab)................................... 3-23
Figure 3-19 Create Task Dialog Box (Policy Tab) .................................................... 3-24
Figure 3-20 Plan Type Area .................................................................................... 3-25
Figure 3-21 View Execution Result Dialog Box (Result Files) .................................. 3-29
Figure 3-22 View Execution Result Dialog Box (Command Execution
Results) ................................................................................................ 3-29
Figure 4-1 System Backup and Restore Window ...................................................... 4-1
Figure 4-2 Backup Whole DB Structure .................................................................... 4-2
Figure 4-3 Backup Basic Data .................................................................................. 4-3
Figure 4-4 Backup File.............................................................................................. 4-5
Figure 4-5 Backup and Deletion Log Data................................................................. 4-6
Figure 4-6 Backup and Deletion Alarm Data ............................................................. 4-8

Figure 4-7 Backup and Deletion PM Data ............................................................... 4-10

Figure 5-1 System Monitoring Window...................................................................... 5-1
Figure 5-2 Application Server Information ................................................................. 5-2
Figure 5-3 Configure Performance Monitoring Dialog Box......................................... 5-3
Figure 5-4 View Application Server Performance Dialog Box .................................... 5-6
Figure 5-5 Basic Information of Database Server ...................................................... 5-8
Figure 5-6 Configure Database Monitoring Dialog Box.............................................. 5-9
Figure 5-7 View Database Resources Dialog Box ................................................... 5-11
Figure 6-1 IT Monitoring Window .............................................................................. 6-1
Figure 6-2 Add Node Dialog Box (AIX Server) .......................................................... 6-3
Figure 6-3 Add Node Dialog Box (Oracle DataBase)................................................. 6-6
Figure 6-4 Add Node Dialog Box (Cisco Router) ....................................................... 6-8
Figure 6-5 Add Node Dialog Box (Cisco Switch) ..................................................... 6-10
Figure 6-6 Add Node Dialog Box (Juniper Firewall)................................................. 6-13
Figure 6-7 Add Node Dialog Box (VCS Cluster) ...................................................... 6-15
Figure 6-8 Add Node Dialog Box (IBM SM)............................................................. 6-18
Figure 6-9 Add Node Dialog Box (BIND Service) .................................................... 6-20
Figure 6-10 Add Node Dialog Box (SeGW Node).................................................... 6-23
Figure 6-11 Basic Information Tab........................................................................... 6-25
Figure 6-12 Component Information Tab ................................................................. 6-26
Figure 6-13 Component Set Dialog Box .................................................................. 6-26
Figure 6-14 Basic Information Tab .......................................................................... 6-27
Figure 6-15 Status Monitoring Tab .......................................................................... 6-28
Figure 6-16 Shortcut Menu for Alarm Display.......................................................... 6-29
Figure 6-17 Fault Management Window.................................................................. 6-29
II

Tables
Table 1-1 Predefined Maintenance Task Description ................................................. 1-2
Table 2-1 Description of Remote Backup Path Parameters ....................................... 2-1
Table 3-1 Toolbar Buttons for Managing the Log Data Backup and Deletion
Task ......................................................................................................... 3-4
Table 3-2 Set Capacity Dialog Box Parameter Descriptions ...................................... 3-6
Table 3-3 Toolbar Buttons for Managing the Performance Data Backup and
Deletion Task ........................................................................................... 3-8
Table 3-4 Toolbar Buttons for Managing the Alarm Data Backup and Deletion
Task ....................................................................................................... 3-10
Table 3-5 Set Capacity Dialog Box Parameter Descriptions .................................... 3-11
Table 3-6 Toolbar Buttons for Managing the History Alarms Acknowledgement
Task ....................................................................................................... 3-21
Table 3-7 Toolbar Buttons for Managing MML Timing Tasks .................................... 3-22
Table 3-8 Basic Information Tab Parameter Descriptions ........................................ 3-23
Table 4-1 Parameter Descriptions for Log Data Backup and Deletion........................ 4-6
Table 4-2 Parameter Descriptions for Alarm Data Backup and Deletion .................... 4-8
Table 4-3 Parameter Descriptions for Performance Data Backup and Deletion
.............................................................................................................. 4-11
Table 5-1 Parameter Descriptions for the Configure Performance Monitoring
Dialog Box ............................................................................................... 5-3
Table 5-2 Area Descriptions for the View Application Server Performance Dialog
Box .......................................................................................................... 5-7
Table 5-3 Parameter Descriptions for the Configure Database Monitoring Dialog
Box .......................................................................................................... 5-9
Table 6-1 Supported Servers .................................................................................... 6-2
Table 6-2 AIX Server Parameter Descriptions ........................................................... 6-3
Table 6-3 Supported Databases................................................................................ 6-5
Table 6-4 Oracle Database Parameter Descriptions.................................................. 6-6
Table 6-5 Supported Routers .................................................................................... 6-7
Table 6-6 Router Parameter Descriptions.................................................................. 6-8
Table 6-7 Supported Switches .................................................................................. 6-9
Table 6-8 Switch Parameter Descriptions................................................................ 6-10
Table 6-9 Supported Firewalls................................................................................. 6-12
Table 6-10 Firewall Parameter Descriptions ............................................................ 6-13
III

Table 6-11 Supported Clusters ................................................................................ 6-14

Table 6-12 Cluster Parameter Descriptions ............................................................. 6-15
Table 6-13 Supported Storage Devices ................................................................... 6-16
Table 6-14 Disk System Parameter Descriptions..................................................... 6-18
Table 6-15 Supported Applications.......................................................................... 6-19
Table 6-16 BIND Service Parameter Descriptions ................................................... 6-20
Table 6-17 Additional Supported IT Devices............................................................ 6-21
Table 6-18 SeGW Parameter Descriptions.............................................................. 6-23
Table 6-19 Descriptions for the Buttons on the Status Monitoring Tab ..................... 6-28
IV

Glossary
ATCA
- Advanced Telecommunications Computing Architecture
CMM
- Chassis Management Module
CPU
- Central Processing Unit
GUI
- Graphical User Interface
HD
- Hard disk
ICMP
- Internet Control Message Protocol
JDBC
- Java Database Connectivity
JNDI
- Java Name and Directory Interface
MML
- Man Machine Language
OS
- Operating System
RAM
- Random Access Memory
SID
- System Identifier
SNMP
- Simple Network Management Protocol
SSH
- Secure Shell
SeGW
- Security Gateway

SJ-20140724091740-009-NetNumen U31 R18 (V12.13.50) Maintenance Management Operation Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ-20140724091740-009-NetNumen U31 R18 (V12.13.50) Maintenance Management Operation Guide

Uploaded by

Copyright:

Available Formats

NetNumen™ U31 R18

Unified Element Management System

Revision No. Revision Date Revision Reason

R1.0 2014-09-03 First edition

Serial Number: SJ-20140724091740-009

Publishing Date: 2014-09-03 (R1.0)

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

Chapter 2 Remote Backup Path Configuration ....................................... 2-1

Chapter 4 System Backup and Restoration............................................. 4-1

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

Chapter 5 System Monitoring.................................................................... 5-1

Chapter 6 IT Device Monitoring................................................................. 6-1

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

1, Maintenance Management Provides an overview of maintenance management

3, Task Management Provides the instructions for managing maintenance tasks,

6, IT Device Monitoring Describes how to monitor an IT device and how to configure

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

Note: provides additional information about a certain topic.

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

1.1.1 Remote Backup Path Configuration

1.1.2 Task Management

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

Table 1-1 Predefined Maintenance Task Description

Task Type Description Allowable Operation

Configuration Data Backs up the basic data of l Modifying task settings

Alarm Background Automatically acknowledges l Refreshing task settings

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

1.1.3 System Backup and Restoration

1.1.4 System Monitoring

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

1.1.5 IT Device Monitoring

Database Oracle, SQL Server, Sybase IQ, Sybase.

Router Cisco, ZTE, Juniper.

Switch AT, Cisco, ZTE, Juniper.

Firewall CheckPoint, Juniper, Cisco, H3C, ZTE, Cisco dual-homed firewall.

Cluster AIX HACMP, HP ServiceGuide, Symantec VCS, NewStartHA, NEC.

Storage device IBM, HP, ZTE, SUN, Fujitsu, EMC, NetApp.

Others F5 traffic manager, HP BLC chassis, HP GBE2C blade switch module, HP

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

Database MS SqlServer 2005/2008 Enterprise Edition, Oracle9i/10g/11g

Figure 1-1 IT Device Monitoring Procedures

1.2 Implicit Prerequisites

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

Figure 2-1 Configuration of Remote Backup Path Dialog Box

2. Set the required parameters of the remote server.

Host Address IP address of the remote server.

Port Port number on the remote server for file transfer.

User Name User name for logging in to the remote server.

User Password Password for logging in to the remote server.

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

3. Click Browse. The Open dialog box is displayed.

Figure 2-2 Remote Backup Path

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

3.1 Task Management Window

Figure 3-1 Task Management Window

1. Task management toolbar 2. Task information pane 3. Navigation tree

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential

3.2 Pre-defined Scheduled Task Management

SJ-20140724091740-009|2014-09-03 (R1.0) ZTE Proprietary and Confidential