1

Nmsux_Conf_Data_Export Ed.1 12/04/09

NMS5UX/LX
CONFIGURATION DATA EXPORT
Application Note



















Issue: 01 (Ed.1)
Date: 12-04-2009


2
Nmsux_Conf_Data_Export Ed.1 12/04/09
INDEX
1. ABBREVIATIONS ........................................................................... 3
2. GENERAL OVERVIEW ................................................................... 4
3. GENERAL CHARACTERISTICS .................................................... 4
4. CONF. DATA FILE GENERATION POLICY ................................... 6
5. USER COMMANDS ........................................................................ 8
5.1 CONFIG. DATA HISTORY FILE MNGT. ........................................................ 8
5.2 CONFIG. DATA FILE MNGT. ......................................................................... 8
6. INSTALLATION AND CONFIGURATION ....................................... 9
6.1 APPLICATIONS LOG AND TRACE .............................................................. 9
7. HARDWARE REQUIREMENTS ...................................................... 9
8. SOFTWARE REQUIREMENTS ...................................................... 9

3
Nmsux_Conf_Data_Export Ed.1 12/04/09

1. ABBREVIATIONS

AL Access Link
ALFO Access Link Full Outdoor
ADM Add Drop Multiplexer
IP Internet Protocol
MIB Management Information Base
NE Network Element
NMS Network Management System
PDH Plesiochronous Digital Hierarchy
SNMP Simple Network Management Protocol
TMN Telecommunication Management Network
UDP User Datagram Protocol
US Urban SDH Radio
WAN Wide Area Network

4
Nmsux_Conf_Data_Export Ed.1 12/04/09

2. GENERAL OVERVIEW


This document describes the tool provided by SIAE Microelettronica to export from
NMS5UX/LX configuration data related to the SIAE


3. GENERAL CHARACTERISTICS
The aim of the application is to provide a tool to export through a "XML" file the
Configuration Data of the managed NE
The supported equipment type are the following ones:
AL/ALC
ALPlus
ALCPlus
ALPlus2
ALCPlus2
ALS
ALFO

The exported data are according to the equipment type.

In general the following data are exported:

Network Element Identifier
IP Addresses (LAN and Point-to-Point ports) and Routing table
Equipment Configuration (according to NE Type)
o Hardware configuration
o Radio parameters
o Ethernet switch parameters
o Tributary (E1, STM1, Ethernet Lan)
o Cross Connection
User Input
User Output
Software inventory data
Hardware inventory data


5
Nmsux_Conf_Data_Export Ed.1 12/04/09

The below window reports an example of exported data for an "ALS" radio terminal



6
Nmsux_Conf_Data_Export Ed.1 12/04/09

4. CONF. DATA FILE GENERATION POLICY

The application can generate the following "XML" file:
For all managed Network Element
The NE are sorted per Equipment Type and per NE identifier
For a specific NE type
The NE are sorted per NE identifier
For a specific NE

In order to support the interface toward an higher level system the application
supports two policies:

1. Incremental
It generates a file with the export data for all the managed NE and then it is
able to periodically generate a file (incremental file) reporting all the change to
the full network file.

2. Differential
It generates a single file per managed NE and the file is automatically
updated to report all the change to the NE

Only one policy can be active at time.
Because "Differential" policy generates a number of files according to the number of
managed NE, it is suggested to use it only for small network.


The incremental and differential files report the following changes:
NE changes
NE delete
NE add

Within the XML file there is a field, named "Status" that is used to trace changes:
NE changes : Status equal "Modified"
NE delete: Status equal "Not Present"
NE add: Status equal "Present"

The incremental and differential files are automatically generated.
According to Unix "crontab" rules, the user can fix when the application has to check
for the differences generating incremental or differential files


7
Nmsux_Conf_Data_Export Ed.1 12/04/09
All the described files are generated in a predefined system directory.
The file names are build according to the following rule:

Incremental policy:
/opt/nms5ux/tools/nmsConfigData/data/History/NMS5_$hostname_Full_$date.xml
/opt/nms5ux/tools/nmsConfigData/data/History/NMS5_$hostname_Incr_$date.xml

Differential policy:
/opt/nms5ux/tools/nmsConfigData/data/History/NMS5_$hostname_$NEId_$date.xml

where:

$hostname: represents the name of the unix server where NMS5 is running
$NEId: NE Identifier (Logical name)
$date: represents the time when the file as been generated
time format:
YYMMDD_HHMM
(e.i.: 20090509_1310 is for the 09
th
of May 2009 1:10 p.m. )

No housekeeping tools are foreseen.
Procedure and policy to export the file toward higher level systems has to be agreed
with the customer.



8
Nmsux_Conf_Data_Export Ed.1 12/04/09

5. USER COMMANDS

The following options are added to the menu "Tools" of NMS5UX/LX to manage the
configuration files:
Config. Data History File Mngt.
Config. Data File Mngt.


5.1 CONFIG. DATA HISTORY FILE MNGT.
The command supports the generation of full network and incremental files to export
toward an higher level system (NBI North Bound Interface).
The options available are the following ones:
Start new history (Incremental or Differential)
A new system directory is created (the old one is maintained for maintenance)
According to the selected policy a new full network file or a file per each
managed NE are created
List history log
Each time the application check for the differences, it traces in a file the
actions taken. The option is used to show to the user one of the log files.


5.2 CONFIG. DATA FILE MNGT.
It is a general purpose command supporting the following options:
XML file creation.
When started, the option shows to the user the list of the managed NE sorted
per equipment type and per Logical address.
The user can select directly on the list or using filters the NE for that the XML
file creation is required.
The filters available are on:
o The logical name (using "*" as wildcard character)
o The Equipment Type
The maximum number of selected NE is one hundred.
The user is asked for the name to be assigned to the file.
The files are generated in a predefined system directory
/opt/nms5ux/tools/nmsConfigDataExport/data/Generic


9
Nmsux_Conf_Data_Export Ed.1 12/04/09
XML file MNGT.
The options shows to the user all the XML files present into the directory.
Three options are available:
o Delete all files
o Delete a file
o Send a file by e-mail

6. INSTALLATION AND CONFIGURATION

The tool provided by SIAE is composed by:
One binary application nmsConfigDataExport
One binary application nmsHistoryDataFileMngt
One binary application nmsDataFileMngt
One script file nmsConfigDataExport.sh

These applications must be installed under directory
/opt/nms5ux/tools/nmsConfigDataExport.

Output files will be created under directory
/opt/nms5ux/tools/nmsConfigDataExport/data.

6.1 APPLICATIONS LOG AND TRACE
The applications trace their activity in log file
/opt/nms5ux/tools/nmsConfigData/log/nmsConfigDataExport.log
This log file can reach maximum dimensions of 2MB and then it is switched in
/opt/nms5ux/tools/nmsConfigData/log/nmsConfigDataExport.log.old file and a
new log file is created.

7. HARDWARE REQUIREMENTS
10MB of disk space in /opt file system for the application. The disk space required
for the data is according to the customer usage and to the network dimension.
The disk space required is about 30Kbyte per NE

8. SOFTWARE REQUIREMENTS
It requires a version equal or greater than the following ones:
HP-UX 11.0 or HP-UX 11.i
LINUX SUSE 9.3
ORACLE DB 10.g
NMS5UX /NMS5LX 6.4.4