SJ-20141121113158-022-NetNumen U31 R06 (V12.14.30) Unified Element Management System VAS Equipment Management

NetNumen U31 R06
Unified Element Management System

VAS Equipment Management
Version: V12.14.30
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://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-12-30 First edition
Serial Number: SJ-20141121113158-022
Publishing Date: 2014-12-30 (R1.0)
SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Chapter 1
Connecting to the OMMP
The NetNumen U31 system can be connected to the OMM NE (OMMP) of the service
product. After that, you can configure the service product parameters on the ZTE
AnyService UniPortal.
Prerequisite
l The OMM NE version is 5.02.01 or later.
l The EMB service process is started on the NetNumen U31 server.
[com.zte.ums.uep.pfl.emb.service.EmbInit]EMB Started
Steps
Creating the Service OMM NE
1. Select Topology > View Topology, and then select the Topology Management tab.
2. Right-click the blank area on the Topology Management tab and select Create
Object > Add Wireline NE. The Management—New dialog box for adding an NE is
displayed.
3. Select an NE type (such as MMSC), and then enter the OMM NE name in the Display
name text box.
4. Select the Base tab. From the Device Type tab, select OMMSERVER, and then enter
the IP address of the OMMP NE.
1-1

NetNumen U31 R06 VAS Equipment Management
Figure 1-1 Management—New Dialog Box—Base Tab
5. Select the SNMP tab. Use the default parameter settings.

6. Select the OMM Attribute tab, see Figure 1-2. Configure the OMM attributes.
Figure 1-2 OMM Attribute Tab
1-2

Chapter 1 Connecting to the OMMP
Table 1-1 OMM Attribute Descriptions
Parameter Description
Integration Mode l Yes: The OMM NE is connected in integration mode. After this NE is
connected, you can enter the corresponding ZTE AnyService Uniportal
directly without login authentication.
l No: The OMMP NE is connected in non-integration mode. After this
NE is connected, you can enter the corresponding ZTE AnyService
Uniportal after passing the login authentication.
Use Proxy Select this option if a client cannot directly access the OMMP from the
network where the client exists.
Other parameters Use the default values.
7. Click New.
A success message is displayed. Click OK.
8. Select Maintenance > VAS Management > OMMP Management. The OMMP
Management tab is displayed.
9. Right-click the EMS Server node and select OMM Access Management from the
short-cut menu. The OMM Access Management dialog box is displayed, see Figure
1-3.
Figure 1-3 OMM Access Management Dialog Box
10. Select the connected service OMM NE, and then click Connect.
A success message is displayed. Click OK.
1-3

11. On the OMMP Management tab, double-click the newly connected OMM NE node
under the EMS server node. The ZTE Anyservice UniPortal page corresponding to
the OMMP node is displayed.
If the OMM NE is connected in non-integration mode, you must enter the user name
and password before logging in to the ZTE Anyservice UniPortal. On the ZTE Any-
service UniPortal page, you can perform the service, device, and permission man-
agement for the NEs managed by the OMM NE.
– End of Steps –
1-4

Chapter 2
Customizing a Polling Task
This procedure describes how to customize a polling task for the VAS NEs. The
NetNumen U31 system periodically detects the links to the VAS NEs. If the unified
network management system detects a disconnected NE, the NetNumen U31 system
reports a link disconnection alarm.
Prerequisite
l The NetNumen U31 server processes are started.
l The VAS NE for which the polling task is to be customized is already created.
Steps
1. Select Maintenance > VAS Management > Customize Polling Management. The
Customize Polling Management dialog box is displayed, see Figure 2-1.
Figure 2-1 Customize Polling Management Dialog Box
2. Click Add. The Add Polling Task dialog box is displayed, see Figure 2-2.
2-1

Figure 2-2 Add Polling Task Dialog Box
3. Select the Select Node tab. From the NE type list, select an NE type, and then select
NEs.
4. Select the Polling Task Information tab. Set the polling task parameters, see Figure
2-3. For a description of the parameters, refer to the following table.
Figure 2-3 Polling Task Information Tab
2-2

Chapter 2 Customizing a Polling Task
Table 2-1 Polling Task Parameter Descriptions
Task Status Initial status of the task. Options: Start and Stop.
Interval Interval for the NetNumen U31 system to poll an NE.
Timeout This parameter sets the timeout time. The NetNumen U31
system polls an NE, but the NE does not respond after this
timeout period is over. In this case, the NetNumen U31 system
determines that the NE times out.
Retries Number of times that the NetNumen U31 system attempts to

poll the NE after a timeout occurs.
Alarm Threshold An alarm is generated after the NE does not respond within
the specified time period for the number of times specified
by this parameter.
5. Click OK.
2-3

This page intentionally left blank.
2-4

Chapter 3
Configuring NE Parameters
in Batches
This procedure describes how to query or modify NE configuration parameters in batches.
You can store the query condition as a template for later use.
Steps
1. Select Maintenance > VAS Management > Batch Config. The Batch Config dialog
box is displayed.
Figure 3-1 Batch Config Dialog Box
2. In the NE area, select an NE type from the NE type list, and then select the NEs to be
configured or queried.
3. In the Object and value area, select the parameter to be configured or queried, and
then click the arrow pointing to the right.
3-1

Note:
You cannot modify any parameter with the value being Read only. The parameter
value cannot be left blank.
4. Perform the following operations as needed.
To... Do...
Query the parameter value Click Query.
Modify the parameter value Click Modify.
Store the current query condition as Click Save as template. A dialog box is displayed.
a template Enter the template name, and then click Save.
3-2

Chapter 4
Loading Alarm Codes
The NetNumen U31 system supports dynamically loading the newly defined alarm codes
to the NetNumen U31 system model, and you do not need to update the NetNumen U31
program.
Prerequisite
The .xls file containing alarm codes is ready.
Steps
1. Select Maintenance > VAS Management > Load Alarm Code. The Select File
dialog box is displayed.
2. Select the alarm code file, and then click Open. A message box is displayed. Click
OK.
Wait for a while. Click Logout as prompted. Log in to the NetNumen U31 client to
validate the loaded alarm codes.
4-1

4-2

Chapter 5
Loading Performance
Objects
The NetNumen U31 system supports dynamically loading the newly defined Performance
Objects (POs) to the NetNumen U31 system model, and you do not need to update the
NetNumen U31 program.
Prerequisite
The PO zip package is ready.
Steps
1. Select Maintenance > VAS Management > Dynamic Load. The Select File dialog
box is displayed.
2. Select the zip packet to be loaded, and then click Open. A message box is displayed.
Click OK.
Wait for a while. Click Log Out Now as prompted. Log in to the NetNumen U31 client
to validate the loaded POs.
5-1

5-2

Chapter 6
VAS Inventory Management
This chapter describes how to add VAS resources, scheduled VAS inventory
synchronization tasks, and scheduled VAS inventory northbound tasks.
Table of Contents
Adding a VAS Asset ...................................................................................................6-1
Creating a Scheduled Task That Exports VAS Inventory Files for the Northbound
Interface .....................................................................................................................6-4
Creating a Scheduled Inventory Synchronization Task ...............................................6-7
6.1 Adding a VAS Asset

This procedure describes how to add a physical asset record to the NetNumen U31 system
to manage the VAS assets centrally.
Steps
Adding a Subnet
1. Select Maintenance > VAS Management > VAS Inventory Management. The VAS
Inventory Management tab is displayed.
2. In Inventory Management Tree, right-click the Inventory Maintenance node and
select Add Subnet from the short-cut menu. The Subnet Maintenance tab is
displayed, see Figure 6-1.
Figure 6-1 Subnet Maintenance Tab
3. Enter Subnet Name and Subnet Type. Click on the toolbar, and click OK in the
message box.
6-1

The subnet node is generated under the Inventory Maintenance node.

Adding a Management Object
4. Right-click the subnet node and select Add ME from the short-cut menu. The Add
Inventory tab is displayed, see Figure 6-2.
Figure 6-2 Add Inventory Tab
5. Enter ME Name, select an NE object to be managed in the EMS Server tree, and click
on the toolbar. A message box is displayed. Click OK.
The NetNumen U31 system synchronizes the asset information automatically. After
the synchronization succeeds, the object node is generated under the subnet node
automatically.
Adding a Rack
6. Right-click the object node and select Add Rack from the short-cut menu. The Add
Inventory tab is displayed, see Figure 6-3.
6-2

Chapter 6 VAS Inventory Management
Figure 6-3 Add Inventory Tab—Adding a Rack
7. Set the rack parameters. For a description of the parameters, refer to the following
table.
Table 6-1 Rack Parameter Descriptions
Inventory Type The default value is Rack, which cannot be modified.
Inventory Number Range: 1–9999999.
Serial Number The serial number must be unique.
Inventory Station l In Service

l Not in Service
l Anomaly (Exception)
Note:
Other parameters are optional.
8. Click on the toolbar. A message box is displayed. Click OK.
Adding a Shelf, Host, or Attachment Device
9. Perform the following operations to add a shelf, host, and accessory device.
6-3

To... Do...
Add a shelf, slot, and

i. Right-click the rack node and select Add Shelf from the shortcut
board
menu.
ii. Enter the shelf information, and then click on the toolbar. A
message box is displayed. Click OK.
iii. Right-click the shelf node and select Add Slot from the shortcut menu.
iv. Enter the slot information, and then click on the toolbar. A
v. Right-click the slot node and select Add Pack from the shortcut menu.
vi. Enter the board information, and then click on the toolbar. A
Add a host
i. Right-click the rack node and select Add Host from the shortcut menu.
ii. Enter the host information, and then click on the toolbar. A
Add an accessory device

i. Right-click the rack node and select Add Accessory from the shortcut
menu.
ii. Enter the accessory device information, and then click on the
toolbar. A message box is displayed. Click OK.
6.2 Creating a Scheduled Task That Exports VAS

Inventory Files for the Northbound Interface
This procedure describes how to create a scheduled task to export the VAS inventory
files from the NetNumen U31 system to the specified location at the scheduled time. The
northbound interface obtains these files from this location.
Context
By default the northbound inventory files are exported to the ums-server\works\glob
al\runtime\northbound\ftp\vas\im path on the NetNumen U31 server.
Steps
1. Select Maintenance > Task Management > Show Timing Task. The Task
Management window is displayed.
2. Select Task Management > VAS Task > Inventory NorthBound in the left Task
Management tree. Click in the right area. The Create Task dialog box is displayed.
6-4

3. Enter a task name (such as VAS Inventory Northbound Task), and use the default
values of other parameters. Click Next.
Figure 6-4 Creating a VAS Inventory Northbound Task
4. Set the scheduling conditions, see Figure 6-5. Click Next.
6-5

Figure 6-5 Setting the Scheduled Task Period
5. (Optional) To export the inventory files to a third-party FTP server, enter the parameters
for the third-party FTP server, see Figure 6-6.
6-6

Figure 6-6 Configuring the FTP Server Information
6. Click Finish.
6.3 Creating a Scheduled Inventory Synchronization

Task
This procedure describes how to create a scheduled inventory synchronization task. You
can view the current VAS inventory data in the VAS Inventory Management window.
Steps
1. Select Maintenance > Task Management > Show Timing Task. The Task
2. Select Task Management > VAS Task > Inventory Sync in the left Task
Management tree. Click in the right area. The Create Task dialog box is
displayed.
3. Enter a task name (such as VAS Inventory Sync Task), and use the default values
of other parameters. Click Next.
6-7

Figure 6-7 Creating a Scheduled Inventory Synchronization Task
6-8

5. Click Finish.
6-9

6-10

Chapter 7
Performance Data Export
This chapter describes how to create scheduled tasks for reporting VAS performance files,
and the performance file formats in the NetNumen U31 system.
Table of Contents
Creating a Performance File Reporting Task ..............................................................7-1
Description of Performance File Format .....................................................................7-7
7.1 Creating a Performance File Reporting Task

This procedure describes how to create a performance file report task for a third-party
device to obtain the performance data of the NEs managed by the NetNumen U31. After
the task is created, the NetNumen U31 system generates the performance files containing
the data obtained by the performance measurement tasks, and reports these files to the
third-party device through the FTP interface.
There are three default performance file tasks: Default (corresponding to all NEs), CDMA
(corresponding to the SMSC-type NEs), and VAS (corresponding to the VAS-type NEs).
Prerequisite
l The unified performance northbound parameters are already configured on the
configuration center.
l The performance measurement task of the specified NE is already created.
Steps
1. Select Maintenance > VAS Management > VAS Performance File Interface
Setting. The VAS Performance File Interface Setting dialog box is displayed, see
Figure 7-1.
7-1

Figure 7-1 VAS Performance File Interface Setting Dialog Box
2. Click Add.
3. Click the Base Setting tab. Set the basic attributes. For a description of the
parameters, refer to the following table.
Table 7-1 Basic Attribute Parameter Descriptions
Parameter Description Setting
Task Name Name of the task reporting the performance files Enter a string contain
a maximum of 20
characters.
Task Delay Sets the delay time for generating a performance

Click . The
file after the execution period of the performance
delay time cannot
measurement task is over. For example, the
be longer than the
performance measurement task is executed once per
execution period.
hour, and the delay time is set to 30 minutes. The
The default setting
system generates a performance file 30 minutes later
is recommended.
containing the data collected at the previous hour.
File Name Name of the performance file to be generated. The Double-click the File
file name can contain the following contents to Name text box. The
correspond to the file format: File Name Setting
l [EMSID]: EMS server ID dialog box is displayed.
l [MOC]: NE type In the Name List area:
l [NENAME]: NE name l Double-click a file
l [NEIP]: IP address of the NE name item that is
l [PONAME]: performance object name already contained
l [STARTTIME]: start time of the collected in the file name to
performance data cancel this item.
7-2

Chapter 7 Performance Data Export
l [ENDTIME]: End time of the collected l Double-click an

performance data unselected file
If the file name does not contain "PONAME", this file name item to add
contains the data of all performance objects of this this item to the file
NE. Otherwise, a performance file contains the data name.
of a performance object of this NE.
The files in the UEMS format are named in the form of
EMSID-MOC-NENAME-STARTTIME-ENDTIME.txt,
which means that the performance file of each NE
is generated every week.
File Format The performance files can be configured with the Select an option from
following content formats: the drop-down list.
l UEMS Format: used for an office only containing
VAS NEs.
l UEP3X format: used for the VAS NEs using
version 4.XX.
l UEMS IMS Format: used for an office containing
IMS NEs.
l UEP3X Ningxia Format
Interval Interval for generating a performance file. Options: Select an option from
l Hour the drop-down list.
l Day
l Quarter: 15 minutes
l Minute: 1 minute
l 5 Minutes
Export Path Path to which the performance files are stored. A Default path: \ums-se
third-party device can obtain performance files by rver\works\global
accessing this path through an FTP server. \runtime\northbou
nd\ftp\vas\pm.
4. Select the PO Setting tab to set the performance object for statistics, see Figure 7-2.
7-3

Figure 7-2 PO Setting Tab
a. From the NE Type list, select the NE type whose performance data is to be
reported. In the PO list area, the available performance objects of this NE type
are displayed.
b. Select a performance object whose performance data is to be reported, and

then click Add. In the PO selected area, the selected performance objects are
displayed. For a description of the buttons on the PO Setting tab, refer to the
following table.
Note:
You cannot select a performance object that is already added to the performance
file reporting task.
Table 7-2 Buttons on the PO Setting Tab
Button Name Function
All Click All to select all performance objects as the performance objects
whose performance data is to be reported. All performance objects of
this NE type are displayed in the PO selected area.
7-4

Button Name Function
Add Select a performance object whose performance data is to be reported,

and then click Add to add this object to the PO selected area.
Delete In the PO selected area, select a performance object to be deleted,

and then click Delete.
Up In the PO selected area, select a performance object, and then click

Up to move this object up.
Down In the PO selected area, select a performance object, and then click
Down to move this object down.
5. (Optional) To automatically upload the generated performance files to a path, select

the Upload Setting tab.
Figure 7-3 Uploading Setting Tab
a. Select the Upload Initiatively check box to validate the text boxes below the check
box.
b. Set the parameters as needed. For a description of the parameters, refer to the
following table.
7-5

Table 7-3 Upload Setting Tab Parameter Descriptions
IPAddress Destination IP address to which the Set it as needed.

performance files to be uploaded
Port Destination port number to which Set it as needed.

the performance files to be
uploaded
User FTP user name used for uploading Set it as needed.

performance files.
Port FTP password used for uploading Set it as needed.

performance files.
Path Path to which performance files are Set it as needed.

to be uploaded
6. Click Add OK. This performance file reporting task is created successfully. This task
is in active status by default.
You can verify that the performance files can be generated under the specified path at
specified intervals. The default path is /ums-server/works/global/runtime/n
orthbound/ftp/vas/pm/date (year to date).
Related Task
Perform the following operations as needed:
To... Do...
Modify a performance file 1. Select the performance file reporting task to be modified.
reporting task 2. Modify the performance file reporting task as needed. For the
operation procedure, refer to 1.–5.
3. Click Modify. A message box is displayed, indicating that the
modification is successful.
Delete a performance file 1. Select the performance file reporting task to be deleted.
reporting task 2. Click Delete. The Confirm dialog box is displayed.
3. Click OK. Result: A dialog box appears to indicate deletion is
successful.
Suspend/activate a 1. Select the performance file reporting task to be suspended (or

performance file reporting activated).
task 2. Click Active/Deactive. The selected performance file reporting task
is activated or suspended. If a task is suspended, generating the
performance files is suspended.
7-6

7.2 Description of Performance File Format

Overview
The NetNumen U31 system supports generating performance files in the following three
formats:
l UEMS Format
l UEP3X Format
l UEMS IMS Format
UEMS Format
The UEMS format is used in a NetNumen U31 system for the VAS service only. The file
format includes three parts:
1. File head
The file head includes the file start ID and basic information. The start of a file head is
identified by “<Start of ZTE_NE type ID>”. The basic information includes:
l NE type vas.cp_up10
l Start time and end time of performance statistics, both in the format of
YYYY-MM-DD HH:mm:ss
2. Performance data
This part includes the data of each performance object. The start of performance data
is identified by “<NE type ID_Counters>”, as explained below:
l The first line is the performance object of the statistics. POID is the unique ID of
this performance object, and the content within the parenthesis is the performance
object name.
l The second line lists names of all counters of the statistics performance object.
The first three items — begintime, endtime, and granularity indicate the start time,
the end time and the collection granularity. From the fourth item are the counters
for this performance object.
3. File end
The file end is identified by “<End of ZTE_NE type ID>”.
The following is an example of the UEMS performance file:
Note:
The fields in the UEMS file are separated by commas.
<Start of ZTE_vas.cp_up10>
NeType:vas.cp_up10
7-7

BeginTime:2011-08-10 14:00:00
EndTime:2010-08-10 15:00:00
<vas.cp_up10_Counters>
PO=10008(Device Hardware Performance)
begintime,endtime,granularity,module,bureau,CpuUseRatio,MemoryUseRatio,HardDisk
UseRatio,HardDiskIOBusy,SwapRatio,IORecePacket,IOSendPacket
2011-08-10 14:45:00,2011-08-10 14:50:00,300,129,23,0.03,0.1,0.47,9,0,1663722,69358
9
2011-08-10 14:50:00,2011-08-10 14:55:00,300,129,23,0.03,0.1,0.47,9,0,1678228,68075
6
2011-08-10 14:55:00,2011-08-10 15:00:00,300,129,23,0.03,0.1,0.47,10,0,1664786,6746
67
PO=10009(Device System Performance)
begintime,endtime,granularity,module,bureau,UsedMemory,FreeMemory,UsedDisk,Fre
eDisk,UsedSwap,FreeSwap
2011-08-10 14:45:00,2011-08-10 14:50:00,300,129,23,3218,28966,23689,26714,0,2055
2011-08-10 14:50:00,2011-08-10 14:55:00,300,129,23,3218,28966,23689,26714,0,2055
2011-08-10 14:55:00,2011-08-10 15:00:00,300,129,23,3218,28966,23689,26714,0,2055
<End of ZTE_vas.cp_up10>
UEP3X Format
The UEP3X format is used in the V4.XX old version of the NetNumen U31 system. The
file includes the counter information of all statistics performance objects.
The following is an example of the UEP3X performance file:
Note:
The fields in the UEP3X file are separated commas.
PO=10008 (Device Hardware Performance)

module,bureau,CpuUseRatio,MemoryUseRatio,HardDiskUseRatio,HardDiskIOBusy,Swa
pRatio,IORecePacket,IOSendPacket,STARTTIME,PERIOD
129,23,0.03,0.1,0.47,9,0,1663722,693589,2011-08-10 14:45:00,5
129,23,0.03,0.1,0.47,9,0,1678228,680756,2011-08-10 14:50:00,5
129,23,0.03,0.1,0.47,10,0,1664786,674667,2011-08-10 14:55:00,5
PO=10009(Device System Performance)
7-8

module,bureau,UsedMemory,FreeMemory,UsedDisk,FreeDisk,UsedSwap,FreeSwap,ST
ARTTIME,PERIOD
129,23,3218,28966,23689,26714,0,2055,2011-08-10 14:45:00,5
129,23,3218,28966,23689,26714,0,2055,2011-08-10 14:50:00,5
129,23,3218,28966,23689,26714,0,2055,2011-08-10 14:55:00,5
UIMS Format
The UIMS format is used in a NetNumen U31 system for IMS only. The file includes three
parts:
1. File header
The file header includes the file start ID and basic information. The file header start is
identified by “<ZTE_NE type ID_Header>”. The basic information includes:
l NE type, vas.cp_up10
l Node No: NodeID
l The start and end time of the performance statistics, both in the format of
YYYY-MM-DD HH:mm:ss
l Version No
2. Performance data
This part includes the data of each performance object. The start of performance data
is identified by “<NE type ID_Counters>”, as explained below:
l POName indicates the name of this performance object.
l Granularity indicates the granularity of this performance object, in the unit of
minute.
l The second line lists out the names of all counters of the statistics object. The
first item EndTime is fixed, indicating the end time. From the second item are the
counters of this performance object.
3. File end
The file end is identified by “<End of ZTE_NE Type ID File>”.
The following is an example of the UIMS performance file:
Note:
The fields in the UIMS file are separated by the tab sign “\t”.
<ZTE_vas.cp up10_Header>
NeType:vas.cp_up10
NodeId:100001
StartTime:2011-08-10 14:00:00 EndTime:2011-08-10 15:00:00
7-9

Ver:1.0
<vas.cp up10_Counters>
POName=Device Hardware Performance Granularity=5
EndTime module bureau CpuUseRatio MemoryUseRatio HardDiskUseRatio HardDiskIO
Busy SwapRatio IORecePacket IOSendPacket
2011-08-10 14:50:00 129 23 0.03 0.1 0.47 9 0 1663722 693589
2011-08-10 14:55:00 129 23 0.03 0.1 0.47 9 0 1678228 680756
2011-08-10 15:00:00 129 23 0.03 0.1 0.47 10 0 1664786 674667
POName=Device System Performance Granularity=5
EndTime module bureau UsedMemory FreeMemory UsedDisk FreeDisk UsedSwap Free
Swap
2011-08-10 14:50:00 129 23 3218 28966 23689 26714 0 2055
2011-08-10 14:55:00 129 23 3218 28966 23689 26714 0 2055

2011-08-10 15:00:00 129 23 3218 28966 23689 26714 0 2055
<End of ZTE_vas.cp up10 File>
7-10

Chapter 8
Creating a Scheduled
Resource Synchronization
Task
This procedure describes how to create a scheduled VAS resource synchronization task
to obtain the VAS resource information at the scheduled time.
Steps
1. Select Maintenance > Task Management > View Timing Task. The Task
2. Select Task Management > VAS Task > Resource Sync in the left Task
Management tree. Click in the right area. The Create Task dialog box is
displayed.
3. Enter a task name (such as VAS NE Resource Sync Task), and use the default values
of other parameters. Click Next.
8-1

Figure 8-1 Creating a Scheduled Resource Synchronization Task
8-2

Chapter 8 Creating a Scheduled Resource Synchronization Task
5. Click Finish.
8-3

8-4

Chapter 9
Creating a Scheduled Alarm
Synchronization Task
This procedure describes how to set a scheduled task to synchronize the front-end alarm
data of the VAS.
Steps
1. Select Maintenance > Task Management > View Timing Task. The Task
2. Select Task Management > VAS Task > Alarm Sync in the left Task Management
tree. Click in the right area. The Create Task dialog box is displayed.
3. Enter a task name (such as VAS NE Alarm Sync Task), and use the default values
of other parameters, see Figure 9-1. Click Next.
Figure 9-1 Creating a Scheduled Alarm Synchronization Task
9-1

5. Click Finish.
9-2

Glossary
EMB
- Enterprise Message Bus
OMM
- Operation & Maintenance Module
PO
- Performance Object
SMSC
- Short Message Service Center

SJ-20141121113158-022-NetNumen U31 R06 (V12.14.30) Unified Element Management System VAS Equipment Management

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-20141121113158-022-NetNumen U31 R06 (V12.14.30) Unified Element Management System VAS Equipment Management

Uploaded by

Copyright:

Available Formats

NetNumen U31 R06

Unified Element Management System

Revision No. Revision Date Revision Reason

R1.0 2014-12-30 First edition

Serial Number: SJ-20141121113158-022

Publishing Date: 2014-12-30 (R1.0)

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Figure 1-1 Management—New Dialog Box—Base Tab

5. Select the SNMP tab. Use the default parameter settings.

Figure 1-2 OMM Attribute Tab

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Table 1-1 OMM Attribute Descriptions

Other parameters Use the default values.

Figure 1-3 OMM Access Management Dialog Box

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-1 Customize Polling Management Dialog Box

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Figure 2-2 Add Polling Task Dialog Box

Figure 2-3 Polling Task Information Tab

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Table 2-1 Polling Task Parameter Descriptions

Interval Interval for the NetNumen U31 system to poll an NE.

Retries Number of times that the NetNumen U31 system attempts to

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Figure 3-1 Batch Config Dialog Box

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

4. Perform the following operations as needed.

Query the parameter value Click Query.

Modify the parameter value Click Modify.

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

6.1 Adding a VAS Asset

Figure 6-1 Subnet Maintenance Tab

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

The subnet node is generated under the Inventory Maintenance node.

Figure 6-2 Add Inventory Tab

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Figure 6-3 Add Inventory Tab—Adding a Rack

Table 6-1 Rack Parameter Descriptions

Inventory Type The default value is Rack, which cannot be modified.

Inventory Number Range: 1–9999999.

Serial Number The serial number must be unique.

Inventory Station l In Service

Other parameters are optional.

8. Click on the toolbar. A message box is displayed. Click OK.

Adding a Shelf, Host, or Attachment Device

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Add a shelf, slot, and

Add an accessory device

6.2 Creating a Scheduled Task That Exports VAS

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Figure 6-4 Creating a VAS Inventory Northbound Task

4. Set the scheduling conditions, see Figure 6-5. Click Next.

SJ-20141121113158-022|2014-12-30 (R1.0) ZTE Proprietary and Confidential

Figure 6-5 Setting the Scheduled Task Period