3al88354aaaa - V1 - 1359 Ioo Administration

Alcatel-Lucent
1359IOO | Release 5.4

Administration Guide
3AL 88354 AAAA

March 2009
Issue 5
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.
All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for
inaccuracies contained herein.
Copyright © 2007 Alcatel-Lucent
3AL 88354 AAAA

Edition 05
Status: DELIVERY
All rights reserved.

Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel-Lucent.
1350OMS-OI/IOO 5.4
ADMINISTRATION GUIDE
3AL 88354 AAAA Ed. 05
2/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
3/116
TABLE OF CONTENTS
TABLE OF CONTENTS .........................................................................................................................1
LIST OF FIGURES .................................................................................................................................5
LIST OF TABLES ..................................................................................................................................7
PREFACE.................................................................................................................................................9
Preliminary Information ................................................................................................................... 9
Applicability ..................................................................................................................................... 9
Scope 11
History 11
Related Documents ...................................................................................................................... 12
Handbook Structure ...................................................................................................................... 12
General Information on Documentation ........................................................................................ 12
1 PRODUCT OVERVIEW .............................................................................................................13
1.1 Technical Objectives ................................................................................................... 13
1.2 Product Characteristics ............................................................................................... 13
1.3 Product Relationship ................................................................................................... 17
1.4 Network Releases Compatibility.................................................................................. 17
2 IOO License management and policy .......................................................................................17
2.1 Operator side ............................................................................................................... 17
3 USER GUIDE ............................................................................................................................19
3.1 Starting of User Configuration Tool ............................................................................. 19
4 ALARMS ASCII DATA INTERFACE CONFIGURATION ..........................................................25
4.1 Graphic User Interface for EOS .................................................................................. 25
4.1.1 Fill/Change Configuration Parameters ......................................... 29
4.1.2 Save Configuration Parameters ................................................... 35
4.2 Graphic User Interface for AS ..................................................................................... 36
4.2.1 Fill/Change/Add/Remove Configuration Parameters ................... 37
4.3 No Graphic Configuration for Alarms ASCII Interface ................................................. 40
4.3.1 NEDATA_INFO_FLAG................................................................. 40
4.3.2 ENABLE_ACK_NOTIF ................................................................. 40
4.3.3 ENABLE_UNACK_NOTIF............................................................ 41
4.3.4 ENABLE_OPERATOR_NAME .................................................... 41
4.3.5 ENABLE_OPERATOR_NAME_FOR_UNACK ............................ 41
4.3.6 ENABLE_PURGE_NOTIF ........................................................... 41
4.3.7 ENABLE_RESERVE_NOTIF ....................................................... 41
4.3.8 ENABLE_OPERATOR_NAME_FOR_RESERVE ........................ 42
4.3.9 ENABLE_UNRESERVE_NOTIF .................................................. 42
4.3.10 ENABLE_OPERATOR_NAME_FOR_UNRESERVE ................... 43
4.3.11 AS POLLING MECHANISM TIME VALUE................................... 43
4.3.12 ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE 43
5 Alarms SNMP DATA INTERFACE CONFIGURATION .............................................................44
5.2 Graphic User Interface for AS ..................................................................................... 52
5.2.1 Fill/Change/Add/Remove Configuration Parameters ................... 53
5.3 No Graphic Configuration for Alarms SNMP Data Interface ....................................... 55
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
1/116
5.3.1 NEDATA_INFO_FLAG................................................................. 55
5.3.2 ENABLE_ACK_NOTIF ................................................................. 57
5.3.3 ENABLE_UNACK_NOTIF............................................................ 57
5.3.4 ENABLE_OPERATOR_NAME .................................................... 57
5.3.5 ENABLE_OPERATOR_NAME_FOR_UNACK ............................ 57
5.3.6 ENABLE_PURGE_NOTIF ........................................................... 57
5.3.7 ENABLE_RESERVE_NOTIF ....................................................... 58
5.3.8 ENABLE_OPERATOR_NAME_FOR_RESERVE ........................ 58
5.3.9 ENABLE_UNRESERVE_NOTIF .................................................. 59
5.3.10 ENABLE_OPERATOR_NAME_FOR_UNRESERVE ................... 59
5.3.11 AS POLLING MECHANISM TIME VALUE................................... 59
5.3.12 ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE 59
5.3.13 NEDATA_INFO_FLAG................................................................. 61
6 NE Directory DATA INTERFACE Configuration ........................................................................62
6.2 No Graphic Configuration for NE Directory Data Interface ......................................... 66
7 PM Data INTERFACE Configuration .........................................................................................67
7.2 No Graphic Configuration for PM Data Interface ........................................................ 72
7.2.1 ANALOGUE ................................................................................. 72
7.2.2 UNSOL_EXPORT_FILTER.......................................................... 72
8 PM FTP DATA INTERFACE CONFIGURATION ......................................................................73
8.2 No Graphic Configuration for PM FTP Data Interface................................................. 76
8.2.1 ANALOGUE ................................................................................. 76
8.2.2 UNSOL_EXPORT_FILTER.......................................................... 76
8.2.3 Configuration of FTP Session ...................................................... 78
9 REMOTE INVENTORY Data INTERFACE Configuration.........................................................79
9.2 No Graphic Configuration for Remote Inventory Data Interface ................................. 84
10 SYSTEM STATISTICS DATA INTERFACE CONFIGURATION...............................................84
10.2 No Graphic Configuration for System Statistics Data Interface .................................. 88
10.2.1 Configuration of FTP Session ...................................................... 88
11 BACKUP/RESTORE FEATURE ................................................................................................91
11.1 Backup/Restore Data Types ....................................................................................... 92
11.2 Backup/Restore Run Levels ........................................................................................ 94
11.3 Backup/Restore Restriction ......................................................................................... 94
12 INSTALLATION GUIDE (HPUX PLATFORM)...........................................................................94
12.1 Scope .......................................................................................................................... 94
12.2 Pre-installation ............................................................................................................. 94
12.3 Previous Version De-Installation ................................................................................. 96
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
2/116
12.3.1 Stop Processes ............................................................................ 96
12.3.2 Delete GENOS instances............................................................. 96
12.3.3 De-Customization ........................................................................ 97
12.3.4 Software Removal ........................................................................ 98
12.4 Installation ................................................................................................................... 98
12.4.1 Installation from scratch ............................................................... 98
12.4.2 Installation from an already installed previous release ................. 99
12.5 Post Installation ........................................................................................................... 99
12.5.1 System Customization ................................................................. 99
12.5.2 System/Process Configuration ................................................... 102
12.5.3 GENOS Configuration on NMS co-hosted ................................. 105
12.5.4 Locating the GENOS files .......................................................... 105
12.5.5 Considerations about the Configuration Tools ........................... 105
12.5.6 SNMP restrictions ...................................................................... 106
12.5.7 Starting the Processes ............................................................... 107
13 TROUBLESHOOTING .............................................................................................................108
13.1 HP-UX Platform ......................................................................................................... 108
ABBREVIATIONS ................................................................................................................................112
INDEX ...................................................................................................................................................114
CUSTOMER DOCUMENTATION FEEDBACK ...................................................................................115
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
3/116
LIST OF FIGURES
Figure 1: Position of IOO within Network Management .........................................................................13
Figure 2: Structure of IOO GENOS ........................................................................................................16
Figure 3: 1359IOO Start Configuratio .....................................................................................................20
Figure 4: User Authorization GUI ...........................................................................................................21
Figure 5: Error message for wrong User Authorization ..........................................................................21
Figure 6: User Configuration GUI ...........................................................................................................22
Figure 7: View/Add/Remove Data Buttons .............................................................................................24
Figure 8: EOS ASCII Configuration GUI - 1 ...........................................................................................25
Figure 9: EOS ASCII Configuration GUI - 2 ...........................................................................................26
Figure 10: EOS ASCII Configuration GUI - 3 .........................................................................................26
Figure 15: AS ASCII Configuration GUI - 1 ............................................................................................30
Figure 18: EOS SNMP Configuration GUI - 1 ........................................................................................44
Figure 21: AS SNMP Configuration GUI - 1 ...........................................................................................47
Figure 24: EOS NED Configuration GUI - 1 ...........................................................................................62
Figure 25: EOS NED Configuration GUI - 2 ...........................................................................................62
Figure 26: EOS PMD Configuration GUI - 1...........................................................................................67
Figure 27: EOS PMD Configuration GUI - 2...........................................................................................68
Figure 28: EOS PMFTP Configuration GUI - 1 ......................................................................................73
Figure 29: EOS PMFTP Configuration GUI - 2 ......................................................................................74
Figure 30: EOS RID Configuration GUI - 1 ............................................................................................80
Figure 31: EOS RID Configuration GUI - 2 ............................................................................................80
Figure 32: EOS SSD Configuration GUI - 1 ...........................................................................................84
Figure 33: EOS SSD Configuration GUI - 2 ...........................................................................................84
Figure 34: SMF Application for Backup/Restore ....................................................................................91
Figure 35: Backup for GENOS Domain ..................................................................................................92
Figure 36: System Customization window - 1 ......................................................................................100
Figure 37: System Customization window - 2 ......................................................................................101
Figure 38: System Configuration starting .............................................................................................102
Figure 39: Select Subsystems List in System Configuration................................................................103
Figure 40: Check License File presence without success ...................................................................104
Figure 41: Quit Subsystems Selection .................................................................................................104
Figure 42: Check License File presence with success ........................................................................104
Figure 43: Starting GENOS processes via PMC ..................................................................................107
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
5/116
LIST OF TABLES
Table 1 IOO Subsystem interfaces on HP-UX Platform .........................................................................15
Table 2 IOO Genos Tools on HP-UX Platform .......................................................................................16
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
7/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
8/116
Preface
Preliminary Information
WARNING
ALCATELLUCENT makes no warranty of any kind with regards to this manual, and specifically
disclaims the implied warranties of merchantability and fitness for a particular purpose.
ALCATELLUCENT will not be liable for errors contained herein or for damages, whether direct,
indirect, consequential, incidental or special, in connection with furnishing, performance or use of this
material.
NOTICE
The product specification and/or performance level contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATELLUCENT.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATELLUCENT and must not be copied,
reproduced or disclosed to a third party without written consent.
Applicability
This handbook applies to the following product-releases:
PRODUCT ANV P/N
1359IOO 3AL 88301 AAAA
PRODUCT RELEASE VERSION (N.B.) ANV P/N
1359IOO 5.4 5.4.0.5 3AL 88354 AAAA
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
9/116
N.B. NOTE FOR HANDBOOKS RELEVANT TO SOFTWARE APPLICATIONS
Handbooks relevant to software applications (typically the Operator’s Handbooks) are not
modified unless the new software “version” distributed to Customers implies man machine
interface changes or in case of slight modifications not affecting the understanding of the
explained procedures.
Moreover, should the screen prints included in the handbook contain the product release’s
“version” marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
10/116
Scope
The list of handbooks given here below is valid on the issue date of this Handbook and
can be changed without any obligation for ALCATELLUCENT to update it in this
Handbook.
Some of the handbooks listed here below may not be available on the issue date of this
handbook.
The standard customer documentation, in the English language for product whose product-release-
version is stated in par.Error! Reference source not found. on page Error! Bookmark not defined.,
consists of the following handbooks:
History
As internal Document
EDITION DATE CHANGE NOTE
Ed 01p01 08/02/2007 First Proposal Edition for IOO 5.4.0 at DR2
Ed 02 27/03/2008 Update documents icon/images of brand, to align with ALcatelLucent
Ed03 17/04/2008 Add Unack related description for align with AS P10
Ed04 06/05/2008 Apply the new document template
As handbook P/N 3AL 88354 AAAA (this handbook)
EDITION DATE CORRESPONDING TO INTERNAL EDITION DOC.
Ed 04 05/05/2008 Edition 04 Iteration 01
Ed 05 03/27/2009 Add reserveStatus config
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
11/116
Related Documents
THIS
HANDBOOK ANV Part No.
HANDBOOK
IOO Release. 5.4
ADMINISTRATION GUIDE 3AL 88354 AAAA YES
1359IOO Release. 5.4

INSTALLATION GUIDE 3AL 88354 BAAA
Handbook Structure
Pls refer to Table of Contents 0
General Information on Documentation
Pls refer to Preliminary Information.0
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
12/116
1 PRODUCT OVERVIEW
1.1 Technical Objectives

To meet the need for an interface towards such umbrella systems, ALcatelLucent, within the 1350
Management Suite Product Line, provides the 1359IOO designed to export data to multiple External
OS.
IOO actually refers to a set of OS-to-OS interfaces (GENOS) each one providing a specific service,
which can be separately installed on top of the ALcatelLucent OS, plug & play application, or collective
to handoff data to several External OS in a default form of notifications.
Requests
Data
Ioo A gent
Figure 1: Position of IOO within Network Management
1.2 Product Characteristics

The available applications are the following:
• IOO Alarm Data Handoff Interfaces (IOO ALM)
• Exports alarms through ASCII interface data via TCP/IP using either CSV or AVA formats
• Exports alarms using SNMP v1,v2c interface via UDP/IP
• IOO Performance Monitoring Data Handoff Interfaces (IOO PM)
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
13/116
• Exports performance monitoring through ASCII interface data via TCP/IP using either
CSV or AVA formats
• Exports performance monitoring through ASCII interface data via FTP, the format of the
file to be transfer is very similar to the one exported via socket base interface
• IOO NE Directory Data Handoff Interfaces (IOO NED)

• Exports the list of the Networks Elements managed through ASCII interface via TCP/IP
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
14/116
• IOO Remote Inventory Handoff Interfaces (IOO RI)
• Exports the remote inventory data of the Network Elements managed through ASCII
interface via TCP/IP
• IOO System Statistics Handoff Interfaces (IOO SS)

• Exports the System Statistic data via FTP, the format of the file to be transfer is CSV or
AVA formats
• IOO Web Genos Tool

• Web Graphic User Interface to configure IOO subsystems
The IOO is a flexible, powerful and effective output set of interfaces which allows an external
management application to keep synchronized with the ALcatelLucent Network Management OS
application as far as Alarms, Performance Monitoring, Network Inventory, Remote Inventory and
System Statistics Data.
Table, below, outlines the Interfaces available for each IOO subsystem supported on HP-UX Platform
and the format in which the data will be handed off.
Table 1 IOO Subsystem interfaces on HP-UX Platform

SUB Systems Interface Format
ASCII SNMP FILE
Platforms HP-UX HP-UX HP-UX
Alarms Data Handoff Y Y N

PM Data Handoff Y N Y
NE Directory Handoff Y N N
RI Data Handoff Y N N
System Statistics Data N N Y
Handoff
Key:
Y = Supported
N = Not Supported
For the format:

ASCII indicates the data will be handed off using ASCII strings
SNMP indicates the data will be handed off using SNMP Traps
FILE indicates the data will be sent to files for retrieval via FTP
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
15/116
IOO (GENOS)
IOO ALM IOO NED IOO RI IOO PM IOO SS

Data Data Data Data Data
Handoff Handoff Handoff Handoff Handoff
ASCII SNMP ASCII ASCII ASCII FTP FTP

I/Fs I/Fs I/Fs I/Fs I/Fs I/Fs I/Fs
Figure 2: Structure of IOO GENOS
Table, below, outlines the Web Graphic User Interfaces available for each IOO subsystem supported
on HP-UX Platform.
Table 2 IOO Genos Tools on HP-UX Platform

SUB Systems Web Genos Tool
Platforms HP-UX
Alarms Data Handoff ASCII Itf Y
Alarms Data Handoff SNMP Itf Y
PM Data Handoff ASCII Itf Y
PM Data Handoff FTP Itf Y
NE Directory Handoff Y
RI Data Handoff Y
System Statistics Data Handoff Y
Key: Y = Supported N = Not Supported
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
16/116
1.3 Product Relationship
IOO interfaces are available on the following Network Management System:
– 1353NM-E
– Alarm Handoff Data Subsystem
– Performance Handoff Data Subsystem
– Network Elements Handoff Data Subsystem
– Remote Inventory Subsystem
– System Statistics Handoff Data Subsystem
– 1354RM / 1354BM-ETH/1354BM-PR/1354BM-ATM /1353NM-A (GEM)

– 1354SN
– Performance Handoff Data Subsystem
1.4 Network Releases Compatibility

The NR8.1-PL2 is the scope of 1359IOO Release 5.4 on HP-UX Platform.
The Network Releases
NR7.0
NR71T & NR71T-PL1
NR71D & NR71D-PL1/NR72
NR73
NR7.4
NR8.1
NR8.1 PL1
NR8.1 PL2
are supported too.
2 IOO License management and policy
2.1 Operator side

The policy for HPUX license management is node-locked; this means that it is allowed using of
1359IOO only on a single computer system.
From release 5.4 on, the 1359IOO licenses procedure will cover the single IOO SUBSYSTEM, so,
after the installation of IOO product and the configuration of the single wanted IOO Subsystem, to
receive the license file, the operator have to send the Mac address of the machine and the
identification of each wanted IOO Subsystem (i.e. ALM_ASCII, ALM_SNMP, NE, RI, PM and SS) to
the product manager of the 1359IOO.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
17/116
The operator after receiving each single license file must move it into following directory:
HPUX Platform
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin
The license is verified on HPUX Platform both during the step of System Configuration, giving a
warning message if the license file for any 1359IOO Subsystem isn’t present, and when each single
IOO Subsystem starts.
The operator can check about the license in the associated trace and out 1359IOO Subsystems files.
RESTRICTION
If the license is not verified a demo version starts for about thirty minutes only for ASCII/SNMP Alarm
and NED Subsystems, while the RID, the PMD and the SSD Subsystems do not start at all.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
18/116
3 USER GUIDE
3.1 Starting of User Configuration Tool

A new Web Graphic User Interface (GUI) called Web Genos Configuration Tools has been developed
to have a better user-friendly tool to configure the 1359IOO product on HP-UX platform.
The following recommendations are suggested to view and use the new Web Genos Tools:
• Screen resolution for Plug & Play Monitor: 1280 x 960
• Java Plug-in : at least version 1.2
• Web Browser: Explorer 6.0/Firefox_1509/Netscape 7.2
This new tool can be started from any Web Browser typing the address of the Web Genos Tools main
window, i.e. http:// followed by the IP address of the machine where the 1359IOO product is installed.
Then the user can select in the first displayed window the folder related to NMS instance where the
1359IOO is installed and where it has to be configured, this folder has the following format:
1359IOO_<NMS_SYSTEM>_<NMS_INSTANCE>
Where:
NMS_SYSTEM is the network management system name (i.e. 1353NM, 1354RM, etc….)
NMS_INSTANCE is the instance (e.g. for NM machine the first instance can be 1353NM_1-7.4)
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
19/116
Figure 3: 1359IOO Start Configuratio
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
20/116
The figure below shows the next window where the user is requested to provide the UNIX user name
and password in order to avoid non-authorized access to 1359IOO machine:
Figure 4: User Authorization GUI
A valid login is the couple NMS username and password so as defined on 1359IOO machine.
For security reason the password value will be passed encrypted towards the application.
If a valid login is issued the Web Genos Configuration Tools GUI is displayed (see Figure 6) otherwise
the following error message is given:
Figure 5: Error message for wrong User Authorization
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
21/116
Figure 6: User Configuration GUI
The Figure 6 shows the new GUI of 1359IOO Web Genos Configuration Tools for HP-UX platform.
The Genos Configuration Tools window consists of two parts:
1. On the left side of the window, five Icon Menu buttons are present to execute view, add,
remove and save actions.
Under these Icon Menu buttons a Tree object is present to navigate across configuration files
related to EOS configurations. In this Tree object the elements to the first level are the
1359IOO Subsystem names and opening them the user can choose which 1359IOO
Subsystem to configure.
2. On the right side of the window all needed fields for EOS/AS configuration action are present.
Selecting “ALM_Ascii” the EOS Configuration GUI and the multi AS Configuration GUI to export
alarms got from more AS-IM (from 1 to 5) for each configured EOS will be displayed for the
Alarm ASCII Subsystem.
Selecting “ALM_Snmp” the EOS Configuration GUI and the multi AS Configuration GUI to export
alarms got from more AS-IM (from 1 to 5) for each configured EOS will be displayed for the Alarm
SNMP Subsystem.
Selecting “NED” the EOS Configuration GUI will be displayed for the NE Directory Data Subsystem.
Selecting “PMD” the EOS Configuration GUI will be displayed for the PMD ASCII Subsystem.
Selecting “PMFTP” the EOS Configuration GUI will be displayed for the PMD FTP Subsystem.
Selecting “RID” the EOS Configuration GUI will be displayed for the Remote Inventory Data
Subsystem.
Selecting “SSD” the EOS Configuration GUI will be displayed for the System Statistics Data
Subsystem.
Selecting “Back” button from the Toolbars will cause the User Configuration GUI to be closed.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
22/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
23/116
The figure below shows the “Five Icon Buttons” in the top left side that allows the user to
View/Add/Remove/Save data for more External OS. Each of the buttons is disabled if the situation
does not allow for that action to be carried out.
Figure 7: View/Add/Remove Data Buttons
From left to right:
Previous External OS - will change the GUI to display data for the Previous External OS (in the
above example this button is green colored because data for more than one External OS exist).
Next External OS - will change the GUI to display data for the Next External OS (in the above
example this button is grayed out because no data for next External OS exists).
Add a New External OS - will create data for a new external OS (using some default values, once
created the user can then add/change the information as required).
Remove Current External OS - will remove the information about the External OS currently being
displayed (in the above example this button isn’t grayed out because data for more than one external
OS exist).
Save - will cause any configuration changes made in the GUI to be saved into Configuration File
related to each Subsystem.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
24/116
4 ALARMS ASCII DATA INTERFACE CONFIGURATION
4.1 Graphic User Interface for EOS
Figure 8: EOS ASCII Configuration GUI - 1
The above Figure 8 and the following figures from 9 to 13 show the “EOS ASCII Configuration GUI”.
This window allows the user to view and edit the configuration fields in use by the Alarms ASCII
Interface for each External OS allowed to connect.
The “Scroll Bar” on the right side and on the bottom of the window allows scrolling of the interface to
reveal more of the EOS ASCII Configuration GUI.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
25/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
26/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
27/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
28/116
4.1.1 Fill/Change Configuration Parameters
From the “EOS ASCII Configuration GUI” the user can change:
Port Number, the port number that the EOS must connect to.
The EOS PORT NUMBER value is assigned by OS-Kernel during the customization step, whereas all
other setting are on External OS basis, but this value can be changed by web configuration tools.

NOTE
The value of EOS PORT NUMBER has to be different for each different NMS co-hosted.
in fact if this value is equal for more then one instance of NMS on the same host, it will give
rise to a conflict between the CPA processes for each Alarms ASCII Interface.
So it's needed to differentiate the value of EOS PORT NUMBER for each Alarms ASCII Interface
configured on more than one instance of NMS on the same host (NMS co-hosted).
WARNING!!!
After the successful modification of the value for EOS PORT NUMBER the operator must perform the
following actions:
a. Line-up of configuration file of the External OS with the new value for EOS PORT
NUMBER
b. Stop and start of the External OS Application
c. Stop and start via PMC the Alarm_ASCII_IH and Alarm_ASCII_CPA processes
For each External OS for which Configuration information is stored, the user can change:
Identifier, the name or IP address of the External OS.
Port Identifier, the port number the External OS will use when connecting.
A value of 0 indicates the EOS can use any port number.
Note: these two parameters (EOS identifier and EOS Port identifier) uniquely identify one specific
External OS that will be allowed to connect.
Key, expected from the External OS in a CONNECT-REQUEST. Always contains * characters as

encrypted password.
Warning: the number of * character is not equal to the length of encrypted password
e.g. the password ‘ALcatelLucent’ is showed as ‘*************’.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
29/116
AS_identity_namex, (for x=1:5) this indicates whether the EOS want to get alarms from the AS-
IM x (on the same or different host); this AS-IM has to be configured via AS_Ascii_x Configuration
window (see Figure 16).
Check box selected means that the EOS want to get alarms from the AS-IM x,
Check box no selected means that the EOS doesn’t want to get alarms from the AS-IM x.
The Default Value is selected for AS_identity_name1 and no selected for all the others (see
Figure 8).
Figure 15: AS ASCII Configuration GUI - 1
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
30/116
Heartbeat Period, this is the time of inactivity in seconds before a Heartbeat is sent from Alarm
ASCII Handoff Interface. A value of 0 indicates that Heartbeats are not to be sent.
Response Period, this is the time in seconds within which a response, to a Heartbeat Request,
from the External OS is expected. If a response is not received within this time Period, it is
assumed a problem with the communications has occurred and the link is closed. A value of 0
indicates no response is expected from the External OS.
Send Heartbeat Response, this indicates whether the Alarm ASCII Handoff Interface has to send
an Heartbeat Response when an Heartbeat Request is received from the External OS, check box
selected means YES else NO.
String Format, circular check box to indicate if Notifications have to be sent in CSV or AVA format
(see Figure 9).
Message Formatter’s that can be changed are:
a. Start Data Indicator
b. End Data Indicator
c. Attribute Delimiter Indicator
d. Attribute Separator Indicator
e. Nesting Indicator Open
f. Nesting Indicator
Alarm Raise and Alarm List Parameter Check-boxes, these allow the user to indicate
which data fields are required in an Alarm Raise and Alarm List Notification (see Figure 9).
Alarm Clear Parameter Check-boxes, these allow the user to indicate which data fields are
required in an Alarm Clear Notification.
MAX NBR Notif Lost, this is the maximum numbers of Alarms lost (Raise/Clear) handled by
IOO per EOS; the default value is: 1000 (see Figure 10).
Notif Lost Available, this indicates whether the EOS wants to request the Alarms
(Raise/Clear) lost during the EOS TCP/IP disconnection;
Check box selected means that EOS, by START-UNSOLICITED-REQUEST, can ask to IOO
the list of Alarms (Raise/Clear) lost during the TCP/IP disconnection,
Checks box no selected means that the facility is NOT Available.
The Default Value is “facility not available” (see Figure 10).
Disable Purge Notif, this indicates whether the EOS wants to receive the PURGE Notifications;
Check box selected means that the PURGE Notifications haven’t to be sent (disabled),
Checks box no selected means that the PURGE Notifications have to be sent.
The Default Value is no selected (see Figure 10).
Disable Ack Notif, this indicates whether the EOS wants to receive the ACK Notifications;
Check box selected means that the ACK Notifications haven’t to be sent (disabled),
Checks box no selected means that the ACK Notifications have to be sent.
Disable UnAck Notif, this indicates whether the EOS wants to receive the UNACK Notifications;
Check box selected means that the UNACK Notifications haven’t to be sent (disabled),
Checks box no selected means that the UNACK Notifications have to be sent.
Disable Reserve Notif, this indicates whether the EOS wants to receive the RESERVE
Notifications;
Check box selected means that the RESERVE Notifications haven’t to be sent (disabled),
Checks box no selected means that the RESERVE Notifications have to be sent.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
31/116
Disable Unreserve Notif, this indicates whether the EOS wants to receive the UNRESERVE
Notifications;
Check box selected means that the UNRESERVE Notifications haven’t to be sent (disabled),
Checks box no selected means that the UNRESERVE Notifications have to be sent.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
32/116
List-Box to allow the editing of a list of Regular Expression of:
NE Location Names for which Alarms are required (if this list is empty then no filtering by
Location Names occurs).
Friendly Names for which Alarms are required (if this list is empty then no filtering by
Friendly Names occurs).
Probable Causes for which Alarms are required (if this list is empty then no filtering by
Probable Causes occurs).
Event Types for which Alarms are required (if this list is empty then no filtering by Event
Types occurs).
Specific Problems for which Alarms are required (if this list is empty then no filtering by
Specific Problems occurs).
Alarm Severities for which Alarms are required (if this list is empty then no filtering by
Alarm Severities occurs)
Additional Info for which Alarms are required (if this list is empty then no filtering by
Additional Info occurs).
Managed Object Instance for which Alarms are required (if this list is empty then no
filtering by Managed Object Instance occurs).
Example: of Additional Information filtering constraint
additionalInfo={AID=ESC_SC-1-2-
1|CONDTYPE=CONTEQPT|AIDTYPE=EQPT|SID=Rome|SRVEFF=SA|NTFCNCDE=
MJ}
It can be observed that "=" and "|" separators are used in the string.
The additionalInformation filter can be: .*SID=Rome.*
The "=" separator can be used in the filtering pattern, the "|" separator cannot, because of the
already use of the "|" to separate more filter fields.
Two List-Boxes to allow the editing of Regular Expressions of:
Alarm Severity’s in the Left List-Box for which the Alarm Severity is to be changed to the Exact
Expression of an Alarm Severity in the Right List-Box. (The Two List-Boxes must have the same
number of entries. If the List-Boxes are Empty then no Alarm Severity Mapping occurs).
Event Types in the Left List-Box for which the Alarm Severity is to be changed to the Exact
Expression of an alarm Severity in the Right List-Box. (The Two List-Boxes must have the same
number of entries. If the List-Boxes are Empty then no Alarm Severity Mapping by Event Type
occurs.)
Probable Causes in the Left List-Box and Regular Expression of Friendly Names in the Right
List-Box. An Alarm, for which the Probable Cause and the Friendly name match the two Regular
Expressions, is to be suppressed. (The Two List-Boxes must have the same number of entries. If
the List-Boxes are Empty then no Suppression of Alarms by Probable Cause and Friendly Name
occurs).
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
33/116
Friendly Names of NE’s in the Left List-Box and Regular Expression for the Event Type which
are to be suppressed for this NE on the right If this list is empty then all Alarms are Handed Off
(see figure 15).
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
34/116
List of NE Name’s for which the Sync Hard coded Filter is applied (see figure 13).
If this list is empty then all Alarms are handed off.
Example: For the NE Name’s = NE1, NE2, … the Sync Hard coded Filter applies to all
Alarms with the following rules:
For each Alarm Notification if “event type <> communicationAlarm” then REPORT ALARM
THROUGH IOO;
If “event type == communicationAlarm” then verify as follows:

If the NE-name of the NE presents in the notification is NOT in the List of NE Name’s then REPORT
ALARM THROUGH IOO;
If the NE-name of the NE presents in the notification is in the List of NE Name’s (NE1, NE2, ....) then
verify as follows
If (“friendlyName == *timingGenerator OR friendlyName == SyncPu* OR friendlyName = *2MbpsT*)

THEN REPORT ALARM THROUGH IOO;
ELSE DISCARD ALARM;
4.1.2 Save Configuration Parameters

From the “Five Icon Buttons” in the top left side of window related to Genos Configuration Tools
(Fig. 7), the user can choose “Save” button that will cause any configuration changes made in the
user interface to be saved into the ASCII Alarms Interface Configuration File and this file will be again
read by Alarms ASCII CPA process.
Location of the Configuration File for Alarms ASCII Interface

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/alm.cfg
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
35/116
4.2 Graphic User Interface for AS
The previous figures show the new GUI for AS ASCII Configuration related to AS_identity_name 1 and
2: the AS_identity_name1 is related to default NMS, i.e. the NM System where the ASCII Alarm
Interface is running, while the configuration for AS_identity_name2 has to be created (added to whole
configuration).
This GUI allows the user to view and edit, for each External OS allowed connecting, the configuration
options for any AS-IM (up to 5 different AS identities) from which the EOS wants to get alarms (on the
same or different host).
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
36/116
4.2.1 Fill/Change/Add/Remove Configuration Parameters
From the “AS ASCII Configuration GUI”, the users can change/add/remove the values of the
parameters indicated below.
The default values, i.e. the values related to the NM System where the ASCII Alarm Interface is
running, are associated only to AS_identity_name 1.
The first four parameters can be obtained opening the file NameServerFile.nr6 in the
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/conf directory on the local or remote host and
reading the line related to SISTEM ASCUR.........., e.g.:
DN 2.4.5.1.2.0.7.1 = "1353NM_1-7.0" : SYSTEM 2.9.3.2.7.4 =

"ASCUR1353NM170" : HOST=albh09 : PORT = 5645;
NMS IDENTIFIER, the <NMS_SYSTEM>_<NMS_INSTANCE> (string value of DN field in the

NameServerFile.nr6 file) on which the ASCII Alarm Interface can run (e.g. 1353NM_1,
1354RM_2, etc.), on the same Host or on a different host.
The default value of the NMS Identifier will be, only for AS_identity_name1, the NM System where
the ASCII Alarm Interface is running.
Note: The format of <NMS_INSTANCE> depends on OS Kernel version installed on the host
where the specified AS-IM is running; more precisely, from OS Kernel version 7.1.2 on (NR7.1D),
the value of <NMS_INSTANCE> is equal to <NMS_INSTANCE_NUM>-<NMS_VERSION> (i.e. 1-
7.1, 2-7.4, etc…).
This value is very important to establish a right communication between the ASCII Alarm IH
process and the AS-IM process.
WARNING!!!
The NMS_IDENTIFIER value has to be different for each AS_identity_name, as it has to identify an
NMS in univocal way (e.g. 1353NM_1, 1353NM_2, 1354RM_5, 1354SN_1).
SYSTEM, the string value of SYSTEM field in the NameServerFile.nr6 file
AS HOST IDENTIFIER, the logical name (no IP address) of the host where AS-IM is running and
the Alarm ASCII Interface wants to interface with. The default value of the AS-IM Identifier will be,
only for AS_identity_name1, the host Identifier of the NM System where the Alarm ASCII Interface
is running.
IP HOST IDENTIFIER, the IP address of the host where AS-IM is running and with which the
Alarm ASCII Interface wants to interface. The default value of this field will be, only for
AS_identity_name1, the IP address of the host where the Alarm ASCII Interface is running.
AS PORT IDENTIFIER, the port number of the AS-IM to use when connecting the Alarm ASCII
Interface, on the local or remote Host. The default value of the AS-IM Port will be, only for
AS_identity_name1, the AS-IM Port Identifier of the NM System where the Alarm ASCII Interface
is running.
FORCE LINE UP, this parameter allows starting a "forced remote copy" (only if the AS HOST
IDENTIFIER is a remote host) from the remote host to the local host of all Object Identifier/user-
friendly name-mapping tables (i.e. probable causes, specific problems, registration identities).
The default value for this parameter will be no selected.
NOTE
The action of "forced remote copy" can be needed in any moment after an AS Configuration of a
remote AS if the contents of the mapping tables changes and so they have to be again lined up.
The normal remote copy from the remote host to the local host of all Object Identifier/user-friendly
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
37/116
name-mapping tables is automatically performed whenever a new AS belonging to a remote host
is configured for the first time.
REMOVE AS, this parameter allows removing, for each External OS allowed to connect, the
configuration for a given AS_identity_name in case of an EOS doesn’t want more to get alarms
from this AS-IM. The default value for this parameter will be no selected.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
38/116
user interface to be saved, into the Alarm ASCII Configuration file holding the routing information for
the ASCURIM
(i.e.
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/data/alm_ho/NameServerFile_ascii.cfg).
If the value of field NMS IDENTIFIER is changed or added then also the Parameter Configuration File
for the Alarm ASCII Handoff IH Process will be saved (i.e.
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/data/alm_ho/param_ascii.cfg).
If the specified AS HOST IDENTIFIER is a remote host, the following actions will be automatically
started:
• Configuration of the remote hostname - IP address on the /etc/hosts file on the machine
where the Alarm ASCII Interface is running in case of already not present.
• Configuration of the remote hostname in Kerberos Data Base in case of already not present.
• Remote copy of all Object Identifier/user-friendly name mapping tables, via the OS_Kernel
utility Remotizer, from remote host to local host (i.e. host where Alarm ASCII Interface is
running).
WARNING!!!
The local host and the remote host must to have a synchronized value for the DATE, i.e. a value of
DATE different for at the most 5 minutes.
WARNING!!!
After updating of the configuration parameters for the AS Interface, the operator must stop and again
start the involved processes (IH and CPA for ASCII) to cause the rereading of the Alarms ASCII
Interface Configuration Files and the registration of the configuration of the new AS-IM by Alarms
ASCII IH process.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
39/116
4.3 No Graphic Configuration for Alarms ASCII Interface
Outside the graphic mode the user can redefine the default value of the following parameters:
– NEDATA_INFO_FLAG
– ENABLE_ACK_NOTIF
– ENABLE_OPERATOR_NAME
– ENABLE_PURGE_NOTIF
– ENABLE_RESERVE_NOTIF
– ENABLE_OPERATOR_NAME_FOR_RESERVE
– ENABLE_UNRESERVE_NOTIF
– ENABLE_OPERATOR_NAME_FOR_UNRESERVE
– AS_POLLING_MECHANISM_TIME_VALUE
– ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE
Location of the files containing the parameters declaration
If you need to change value for each of these parameters it can be done in the following files:
Platform type: HPUX (OS-CONF & OS-KERNEL)

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/alm_ho/param_ascii.c
fg
4.3.1 NEDATA_INFO_FLAG
If you need to change value of this parameter, taking in account the constraint arising from the
different NMS installation environments (1353xx and 1354xx) and from platforms as described below.
Parameter meaning
NEDATA_INFO_FLAG = 0 (default) means nedata.txt file IS NOT available, this is
mandatory if you are installing on 1354xx NMS (i.e. 1354RM, BM) or if you are installing on
1353xx NMS (i.e. 1353NM,…) and it doesn’t need to export “NeLocationName” information.
NEDATA_INFO_FLAG = 1 means nedata.txt file IS available, only if you are installing on 1353xx
NMS (i.e.1353NM) and it needs to export “NeLocationName” information.
4.3.2 ENABLE_ACK_NOTIF
Parameter meaning
ENABLE_ACK_NOTIF = 0 if it doesn’t need to export the alarm notifications for
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
40/116
acknowledged alarms.
ENABLE_ACK_NOTIF = 1 (default) if it needs to export all alarm notifications for
4.3.3 ENABLE_UNACK_NOTIF
Parameter meaning
ENABLE_UNACK_NOTIF = 0 if it doesn’t need to export the alarm notifications for
unacknowledged alarms.
ENABLE_UNACK_NOTIF = 1 (default) if it needs to export all alarm notifications for
4.3.4 ENABLE_OPERATOR_NAME
Parameter meaning
ENABLE_OPERATOR_NAME = 0 if it doesn’t need to export in Alarm Ack notification the
field containing the name of the operator that performed acknowledge on AS
ENABLE_OPERATOR_NAME = 1 (default) if it needs to export receive in Alarm Ack
notification the field containing the name of the operator that performed acknowledge on AS
4.3.5 ENABLE_OPERATOR_NAME_FOR_UNACK
Parameter meaning
ENABLE_OPERATOR_NAME_FOR_UNACK = 0 if it doesn’t need to export in Alarm UnAck
notification the field containing the name of the operator that performed unacknowledge on AS
ENABLE_OPERATOR_NAME_FOR_UNACK = 1 (default) if it needs to export receive in
Alarm UnAck notification the field containing the name of the operator that performed
unacknowledge on AS
4.3.6 ENABLE_PURGE_NOTIF
Parameter meaning
ENABLE_PURGE_NOTIF = 0 if it doesn’t need to export the alarm notifications for purged
alarms.
ENABLE_PURGE_NOTIF = 1 (default) if it needs to export all alarm notifications for purged
alarms.
4.3.7 ENABLE_RESERVE_NOTIF
Parameter meaning
ENABLE_RESERVE_NOTIF = 0 if it doesn’t need to export the alarm notifications for
reserved alarms.
ENABLE_RESERVE_NOTIF = 1 (default) if it needs to export all alarm notifications for
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
41/116
reserved alarms.
4.3.8 ENABLE_OPERATOR_NAME_FOR_RESERVE
Parameter meaning
ENABLE_OPERATOR_NAME_FOR_RESERVE = 0 if it doesn’t need to export in Alarm
Reserve notification the field containing the name of the operator that performed reserve action
on AS
ENABLE_OPERATOR_NAME_FOR_RESERVE = 1 (default) if it needs to export in Alarm
on AS
4.3.9 ENABLE_UNRESERVE_NOTIF
Parameter meaning
ENABLE_UNRESERVE_NOTIF = 0 if it doesn’t need to export the alarm notifications for
unreserved alarms.
ENABLE_UNRESERVE_NOTIF = 1 (default) if it needs to export all alarm notifications for
unreserved alarms.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
42/116
4.3.10 ENABLE_OPERATOR_NAME_FOR_UNRESERVE
Parameter meaning
ENABLE_OPERATOR_NAME_FOR_UNRESERVE = 0 if it doesn’t need to export in Alarm
Unreserve notification the field containing the name of the operator that performed unreserve
action on AS
ENABLE_OPERATOR_NAME_FOR_UNRESERVE = 1 (default) if it needs to export in Alarm
action on AS
REMARK
Starting from AS 6.5.1 P5.1, at the time of the Alarm Unreservation, the information related to the
previous Alarm Reservation (reservation time and user name) can be cleared or
not according to a new configuration parameter (CLEAN_FIELDS_ON_UNRESERVE) in
ASCURIM param.cfg and independently from the setting at default value of
ENABLE_OPERATOR_NAME_FOR_UNRESERVE parameter.
Starting from OS-Kernel 7.1.2 P17, it's always guaranteed the export in Alarm Unreserve
notification of the field containing the name of the operator that performed the unreserve action on
AS because the new configuration parameter (CLEAN_FIELDS_ON_UNRESERVE) is set to
False value (to ensure the backward compatibility).
4.3.11 AS POLLING MECHANISM TIME VALUE

Parameter meaning
This parameter indicates the value (minutes) of the AS polling mechanism.
The default value is 2 minutes.
4.3.12 ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE
Parameter meaning
ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE = 0 if it doesn’t need to

export in Alarm Purge notification the fields containing Friendlyname and ProbableCause of
relevant alarm
ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE = 1 (default) if it needs to
relevant alarm
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
43/116
5 Alarms SNMP DATA INTERFACE CONFIGURATION
Figure 18: EOS SNMP Configuration GUI - 1
The above Figure 18 and the following figures from 19 to 20 show the “EOS SNMP Configuration
GUI”.
This window allows the user to view and edit the configuration fields in use by the Alarms SNMP
reveal more of the EOS SNMP Configuration GUI.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
44/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
45/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
46/116
For each External OS for which Configuration Information is stored the user can change:
Community Name, expected from the External OS.
GET NEXT TIMEOUT is the timeout value within which the next GET NEXT request is expected,
when the External OS is getting the list of SNMP Alarms.
START UNSOL HANDOFF can have a value AUTO or SNMP.

- AUTO indicates any Unsolicited Alarms are to be handed off to the External OS from startup;
- SNMP indicates Unsolicited Alarms are only handed off once a Start-Unsolicited-Alarms
Request has been received from the External OS.
AS_identity_namex, (for x=1:5) this indicates whether the EOS want to get alarms from the AS-
IM x (on the same or different host); this AS-IM has to be configured via AS_Snmp_x
Configuration window (see Figure 21).
Check box selected means that the EOS want to get alarms from the AS-IM x,
Check box no selected means that the EOS doesn’t want to get alarms from the AS-IM x.
The Default Value is selected for AS_identity_name1 and no selected for all the others (see
Figure 18).
Figure 21: AS SNMP Configuration GUI - 1
Alarm Raise Parameter Check Boxes, these allow the user to indicate which data fields are
required in an Alarm Raise Trap.
Alarm Clear Parameter Check-Boxes, these allow the user to indicate which data fields are
required in an Alarm Clear Trap.
Disable Purge Notif, this indicates whether the EOS wants to receive the PURGE Notifications;
Check box selected means that the PURGE Notifications haven’t to be sent (disabled),
Checks box no selected means that the PURGE Notifications have to be sent.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
47/116
Disable Ack Notif, this indicates whether the EOS wants to receive the ACK Notifications;
Check box selected means that the ACK Notifications haven’t to be sent (disabled),
Checks box no selected means that the ACK Notifications have to be sent.
Disable UnAck Notif, this indicates whether the EOS wants to receive the UNACK Notifications;
Check box selected means that the UNACK Notifications haven’t to be sent (disabled),
Checks box no selected means that the UNACK Notifications have to be sent.
Disable Reserve Notif, this indicates whether the EOS wants to receive the RESERVE
Notifications;
Check box selected means that the RESERVE Notifications haven’t to be sent (disabled),
Checks box no selected means that the RESERVE Notifications have to be sent.
Disable Unreserve Notif, this indicates whether the EOS wants to receive the UNRESERVE
Notifications;
Check box selected means that the UNRESERVE Notifications haven’t to be sent (disabled),
Checks box no selected means that the UNRESERVE Notifications have to be sent.
• List of Friendly Names of NE’s in the Left List-Box and Regular Expression for the Event
Type that are to be suppressed for this NE on the right, if this list is empty then all Alarms are
Handed Off.
FOR each NE Name’s = NE1, NE2… and Event Types = communicationAlarm the Filtering
criteria are applied with the following rules:
a. If the NE-name of the NE presents in the notification is NOT in the List of NE Name’s then
REPORT ALARM THROUGH IOO;
b. If the NE-name of the NE presents in the notification is in the List of NE Name’s (NE1, NE2…)
and (“eventType matching Regular Expression of “communicationAlarm”)
Then DISCARD ALARM
Else REPORT ALARM THROUGH IOO;
1. The first way to obtain a list of Ne Name’s is adding the corresponding list of NE Types and a
regular expression of EventType in snmp_filtering.cfg for which alarms are going to be filtered,
e.g.:
If we have in snmp_filtering.cfg an entry equal to:
neType “eventType”
“1641ADM” “communicationsAlarm”
It means that all NE Name belonging to this neType will be loaded in the List of NE Name’s
for which alarms the Filtering criteria is applied.
Note: the snmp_alarms process reads changes done in “snmp_filtering.cfg” file when
REREAD TIME expires, eventual change at REREAD TIME value is done by
“user_config.tcl” editing the corresponding field.
2. The second way is to make the above changes in “snmp_filtering.cfg” immediately active by
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
48/116
executing the following commands as “axadmin” user:
$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin /Ioodbread >

$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/neData.txt
$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin/update.pl
$
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin/snmp_alm_update.pl
Restriction: the mechanism is applicable only if the interface is installed on an instance of

1353xx NMS on HP-UX platform.
• List of NE Name’s for which the Sync Hard Coded Filter is applied, if this list is empty then
all Alarms are Handed Off.
FOR each NE Name’s = NE1, NE2… the Sync Hard coded Filter applies to all Alarms with
the following rules:
a. FOR each Alarm Notification verify IF “event type <> communicationAlarm” THEN
REPORT ALARM THROUGH IOO;
b. FOR each Alarm Notification verify IF “event type == communicationAlarm”

THEN verify as follows:
IF NE-name of the NE present in the notification is NOT in the List of NE Name’s

THEN REPORT ALARM THROUGH IOO;
IF NE-name of the NE present in the notification IS in the List of NE Name’s (NE1,

NE2, …) then verify as follows:
If (“friendlyName == timingGenerator OR friendlyName == SyncPu* OR

friendlyName = *2MbpsT*) THEN REPORT ALARM THROUGH IOO;
ELSE DISCARD ALARM;
• The first way to obtain a List of Ne Name’s is adding the corresponding list of NE Types in
neTypeAlarm_Sync_list.cfg for which alarms are going to be filtered by the Sync Hard
coded Filter, e.g.: if we have in “neTypeAlarm_Sync_list.cfg” an entry equal to “1641ADM”
, this means that all NeName belonging to this neType will be loaded in the “List of Ne Name’s
for which the Sync Hard coded Filter is applied”.
Changes done in “neTypeAlarm_Sync_list.cfg” file are read by the snmp_alarms process
when REREAD TIME expires.
Eventual change at REREAD TIME value is done by “user_config.tcl” editing the
corresponding field.
• The second way is to make the above changes in “neTypeAlarm_Sync_list.cfg” immediately

active, executing the following commands as “axadmin” user:
$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin /Ioodbread >
$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/neData.txt
$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin/update.pl
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
49/116
$
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin/snmp_alm_update.pl
Restriction: this mechanism is applicable only if the interface is installed on an instance of

1353xx NMS on HP-UX platform.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
50/116
Friendly Names for which Alarms are required. (If this list is empty then no filtering by Friendly
Names occurs).
Probable Causes for which Alarms are required, (if this list is empty then no filtering by Probable
Causes occurs).
Specific Problems for which Alarms are required, (if this list is empty then no filtering by Specific
Problems occurs).
Location Names for which Alarms are required, (if this list is empty then no filtering by Location
Names occurs).
Alarm Severities for which Alarms are required, (if this list is empty then no filtering by Alarm
Severities occurs).
Additional Information for which Alarms are required, (if this list is empty then no filtering by
Additional Information occurs).
Event Types for which Alarms are required, (if this list is empty then no filtering by Event Types
occurs).
Managed Object Instance for which Alarms are required (if this list is empty then no filtering by
Managed Object Instance occurs).

user interface to be saved into the Alarms SNMP Interface Configuration File and this file will be again
read by Alarms SNMP CPA process.
Location of the Configuration File for Alarms SNMP Interface

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/snmp_alm.cfg
Anyway, all changes done for all configuration parameters are read by the CPA process when the
REREAD TIME expires or when the following script is manually executed:
$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin/snmp_alm_update.pl
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
51/116
5.2 Graphic User Interface for AS
The previous figures show the new GUI for AS SNMP Configuration related to AS_identity_name 1
and 2: the AS_identity_name1 is related to default NMS, i.e. the NM System where the Alarm SNMP
Interface is running, while the configuration for AS_identity_name2 has to be created (added to whole
configuration).
This GUI allows the user to view and edit, for each External OS allowed connecting, the configuration
options for any AS-IM (up to 5 different AS identities) from which the EOS wants to get alarms (on the
same or different host).
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
52/116
5.2.1 Fill/Change/Add/Remove Configuration Parameters
From the “AS SNMP Configuration GUI”, the user can change/add/remove the values of the
parameters indicated below.
The default values, i.e. the values related to the NM System where the Alarm SNMP Interface is
running, are associated only to AS_identity_name1.
The first four parameters can be obtained opening the file NameServerFile.nr6 in the
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/conf directory on the local or remote host and
reading the line related to SISTEM ASCUR........, e.g.:
DN 2.4.5.1.2.0.7.1 = "1353NM_1-7.0" : SYSTEM 2.9.3.2.7.4 =

"ASCUR1353NM170" : HOST=albh09 : PORT = 5645;
NMS_IDENTIFIER, the <NMS_SYSTEM>_<NMS_INSTANCE> (string value of DN field in the

NameServerFile.nr6 file) on which the Alarm SNMP Interface can run (e.g. 1353NM_1,
1354RM_1, etc.), on the local Host or on a remote host.
The default value of the NMS Identifier will be, only for AS_identity_name1, the NM System where
the Alarm SNMP Interface is running.
Note: The format of <NMS_INSTANCE> depends on OS Kernel version installed on the host
where the specified AS-IM is running; more precisely, from OS Kernel version 7.1.2 on (NR7.1D),
the value of <NMS_INSTANCE> is equal to <NMS_INSTANCE_NUM>-<NMS_VERSION> (i.e. 1-
7.1, 2-7.4, etc…).
This value is very important to establish a right communication between the SNMP Alarm
IH process and the AS-IM process.
WARNING!!!
The NMS_IDENTIFIER value has to be different for each AS_identity_name, as it has to identify an
NMS in univocal way (e.g. 1353NM_1, 1353NM_2, 1354RM_5, 1354SN_1).
SYSTEM, the string value of SYSTEM field in the NameServerFile.nr6 file
AS HOST IDENTIFIER, the logical name (no IP address) of the host where AS-IM is running and
the Alarm SNMP Interface wants to interface with. The default value of the AS-IM Identifier will be,
only for AS_identity_name1, the host Identifier of the NM System where the Alarm SNMP
Interface is running.
IP HOST IDENTIFIER, the IP address of the host where AS-IM is running and with which the
Alarm SNMP Interface can interface. The default value of this field will be, only for
AS_identity_name1, the IP address of the host where the Alarm SNMP Interface is running.
AS PORT IDENTIFIER, the port number of the AS-IM to use when connecting the Alarm SNMP
Interface, running on local or remote Host. The default value of the AS-IM Port will be, only for
AS_identity_name1, the AS-IM Port Identifier of the NM System where the Alarm SNMP Interface
is running.
FORCE LINE UP, this parameter allows starting a "forced remote copy" (only if the AS HOST
IDENTIFIER is a remote host) from the remote host to the local host of all Object Identifier/user-
friendly name-mapping tables (i.e. probable causes, specific problems, registration identities).
The default value for this parameter will be no selected.
NOTE: The action of "forced remote copy" can be needed in any moment after an AS
Configuration of a remote AS if the contents of the mapping tables changes and so they have to
be again lined up.
The normal remote copy from the remote host to the local host of all Object Identifier/user-friendly
name-mapping tables is automatically performed whenever a new AS belonging to a remote host
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
53/116
is configured for the first time.
REMOVE AS, this parameter allows removing, for each External OS allowed to connect, the
configuration for a given AS_identity_name in case of an EOS doesn’t want more to get alarms
from this AS-IM. The default value for this parameter will be no selected.

user interface to be saved, into the Alarm SNMP Configuration file holding the routing information for
the ASCURIM
(i.e. /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/data/alm_ho/NameServerFile.cfg).
If the value of field NMS IDENTIFIER is changed or added then also the Parameter Configuration File
for the Alarm SNMP Handoff IH Process will be saved (i.e.
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/data/alm_ho/param.cfg).
If the specified AS HOST IDENTIFIER is a remote host, the following actions will be automatically
started:
• Configuration of the remote hostname - IP address on the /etc/hosts file on the machine
where the Alarm SNMP Interface is running in case of already not present.
• Configuration of the remote hostname in Kerberos Data Base in case of already not present.
• Remote copy of all Object Identifier/user-friendly name mapping tables, via the OS_Kernel
utility Remotizer, from remote host to local host (i.e. host where Alarm SNMP Interface is
running).
WARNING!!!
The local host and the remote host must to have a synchronized value for the DATE, i.e. a value of
DATE different for at the most 5 minutes.
WARNING!!!
After updating of the configuration parameters for the AS Interface, the operator must stop and again
start the involved processes (IH and CPA for SNMP) to cause the rereading of the Alarms SNMP
Interface Configuration Files and the registration of the configuration of the new AS-IM by Alarms
SNMP IH process.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
54/116
5.3 No Graphic Configuration for Alarms SNMP Data Interface
Outside the graphic mode the user can redefine the default value of the following parameters:
– NEDATA_INFO_FLAG
– ENABLE_ACK_NOTIF
– ENABLE_UNACK_NOTIF
– ENABLE_OPERATOR_NAME
– ENABLE_OPERATOR_NAME_FOR_UNACK
– ENABLE_PURGE_NOTIF
– ENABLE_RESERVE_NOTIF
– ENABLE_OPERATOR_NAME_FOR_RESERVE
– ENABLE_UNRESERVE_NOTIF
– ENABLE_OPERATOR_NAME_FOR_UNRESERVE
– AS_POLLING_MECHANISM_TIME_VALUE
– ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE
Location of the files containing the parameters declaration
If you need to change the value for each of these parameters it can be done in the following files:
Platform type: HPUX (OS-CONF & OS-KERNEL)

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/alm_ho/p
aram.cfg
If you need to change value of this parameter, please take in account the constraint arising from the
different NMS installation environments (1353xx and 1354xx) and from platforms as described below.
Parameter meaning
NEDATA_INFO_FLAG = 0 (default) means nedata.txt file IS NOT available under the
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/monitor directory,
this is mandatory if you are installing on 1354xx NMS (i.e. 1354RM, BM) or if you are installing
on 1353xx NMS (i.e. 1353NM,…) and it doesn’t need to export “NeLocationName”
information.
NEDATA_INFO_FLAG = 1 means nedata.txt file IS available under the
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
55/116
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/monitor directory,
only if you are installing on 1353xx NMS (i.e.1353NM) and it needs to export
“NeLocationName” information.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
56/116
5.3.2 ENABLE_ACK_NOTIF
Parameter meaning
ENABLE_ACK_NOTIF = 0 if it doesn’t need to export the alarm notifications for

ENABLE_ACK_NOTIF = 1 (default) if it needs to export all alarm notifications for
5.3.3 ENABLE_UNACK_NOTIF
Parameter meaning
ENABLE_UNACK_NOTIF = 0 if it doesn’t need to export the alarm notifications for

ENABLE_UNACK_NOTIF = 1 (default) if it needs to export all alarm notifications for
5.3.4 ENABLE_OPERATOR_NAME
Parameter meaning
ENABLE_OPERATOR_NAME = 0 if it doesn’t need to export in Alarm Ack notification the

field containing the name of the operator that performed acknowledge on AS
ENABLE_OPERATOR_NAME = 1 (default) if it needs to export receive in Alarm Ack
notification the field containing the name of the operator that performed acknowledge on AS
5.3.5 ENABLE_OPERATOR_NAME_FOR_UNACK
Parameter meaning
ENABLE_OPERATOR_NAME_FOR_UNACK = 0 if it doesn’t need to export in Alarm UnAck

notification the field containing the name of the operator that performed unacknowledge on AS
ENABLE_OPERATOR_NAME_FOR_UNACK = 1 (default) if it needs to
export receive in Alarm UnAck notification the field containing the name of the
operator that performed unacknowledge on AS
5.3.6 ENABLE_PURGE_NOTIF
Parameter meaning
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
57/116
ENABLE_PURGE_NOTIF = 0 if it doesn’t need to export the alarm notifications for purged
alarms.
ENABLE_PURGE_NOTIF = 1 (default) if it needs to export all alarm notifications for purged
alarms.
5.3.7 ENABLE_RESERVE_NOTIF
Parameter meaning
ENABLE_RESERVE_NOTIF = 0 if it doesn’t need to export the alarm notifications for

reserved alarms.
ENABLE_RESERVE_NOTIF = 1 (default) if it needs to export all alarm notifications for
reserved alarms.
5.3.8 ENABLE_OPERATOR_NAME_FOR_RESERVE
Parameter meaning
ENABLE_OPERATOR_NAME_FOR_RESERVE = 0 if it doesn’t need to export in Alarm

on AS
ENABLE_OPERATOR_NAME_FOR_RESERVE = 1 (default) if it needs to export in Alarm
on AS
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
58/116
5.3.9 ENABLE_UNRESERVE_NOTIF
Parameter meaning
ENABLE_UNRESERVE_NOTIF = 0 if it doesn’t need to export the alarm notifications for
unreserved alarms.
ENABLE_UNRESERVE_NOTIF = 1 (default) if it needs to export all alarm notifications for
unreserved alarms.
5.3.10 ENABLE_OPERATOR_NAME_FOR_UNRESERVE
Parameter meaning
ENABLE_OPERATOR_NAME_FOR_UNRESERVE = 0 if it doesn’t need to export in Alarm

action on AS
ENABLE_OPERATOR_NAME_FOR_UNRESERVE = 1 (default) if it needs to export in Alarm
action on AS
REMARK
Starting from AS 6.5.1 P5.1, at the time of the Alarm Unreserve, the information related to the
previous Alarm Reserve (reserve time and user name) can be cleared or
ASCURIM param.cfg and independently from the setting at default value of
ENABLE_OPERATOR_NAME_FOR_UNRESERVE parameter.
Starting from OS-Kernel 7.1.2 P17, it's always guaranteed the export in Alarm Unreserve
notification of the field containing the name of the operator that performed the unreserve action on
AS because the new configuration parameter (CLEAN_FIELDS_ON_UNRESERVE) is set to
False value (to ensure the backward compatibility).
5.3.11 AS POLLING MECHANISM TIME VALUE

Parameter meaning
This parameter indicates the value (minutes) of the AS polling mechanism.
The default value is 2 minutes.
5.3.12 ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE
Parameter meaning
ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE = 0 if it doesn’t need to

relevant alarm
ENABLE_FRIENDLYNAME_PROBABLECAUSE_FOR_PURGE = 1 (default) if it needs to
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
59/116
relevant alarm
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
60/116
If you need to change the value of this parameter, please take in account the constraint arising from
the different NMS installation environments (1353xx and 1354xx).
Parameter meaning
NEDATA_INFO_FLAG = 0 (default) means nedata.txt file IS NOT available under the

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config directory, this is
mandatory if you are installing on 1354xx NMS (i.e. 1354RM, BM, …) or if you are installing on
1353xx NMS (i.e. 1353NM,…) and it doesn’t need to export “NeLocationName” information.
NEDATA_INFO_FLAG = 1 means nedata.txt file IS available under the
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config directory, only if you
are installing on 1353xx NMS (i.e.1353NM) and it needs to export “NeLocationName”
information.
Location of the files containing the parameter declaration
If you need to change the value of this parameter it can be done in the following file:
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/snmp_ho/sn
mp_param.cfg
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
61/116
6 NE Directory DATA INTERFACE Configuration
Figure 24: EOS NED Configuration GUI - 1
Figure 25: EOS NED Configuration GUI - 2
The above Figures 24 and 25 show the “EOS NED Configuration GUI”.
This window allows the user to view and edit the configuration fields in use by the NE Directory
reveal more of the EOS NED Configuration GUI.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
62/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
63/116
From the “EOS NED Configuration GUI”, the user can change:
The EOS PORT NUMBER value is assigned by OS-Kernel during the customization step,
whereas all other setting are on External OS basis, but this value can be changed(see figure 24).
NOTE
This recommendation is due to the assigned fixed value for the EOS socket port; in fact if this
value is equal for more then one instance of NMS on the same host, it will give rise to a conflict
between the CPA processes for each NED Interface.
So it's needed to differentiate the value of EOS PORT NUMBER for each NED Interface
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
64/116
WARNING!!!
following actions:
a. Line-up of configuration file of the External OS with the new value for EOS PORT NUMBER
c. Stop and start via PMC the NE_Inventory_IH and NE_Inventory_CPA processes

encrypted password.
Heartbeat Period, this is the time of inactivity in seconds before a Heartbeat is sent from NED
Handoff Interface. A value of 0 indicates that Heartbeats are not to be sent.
Send Heartbeat Response, this indicates whether the NED Handoff Interface has to send an
Heartbeat Response when an Heartbeat Request is received from the External OS, check box
(see Figure 24).

1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
65/116
NE Create and NE List Notification check boxes to allow the user to indicate which data
fields are required:
o NE Element Id,
o User Label,
o Location Name,
o NE Type,
o NE Release,
o NE Creation Data
o Operational State
o MIB Alignment State
o Supervision State
o Local Access Control State
o NE Alarm Status
o NSAP Address
o Logical Number
NE State Change Notification check boxes to allow the user to indicate which data fields are
required:
o Element Id
o User Label
o Operational State
o MIB Alignment State
o Supervision State
o Local Access Control State
o NE Alarm Status
User Labels for which NE's are required (if this list is empty then no filtering by User
Labels occurs and all NE's will be handed off).

user interface to be saved into the NED Interface Configuration File and this file will be again read by
NED CPA process.
Location of the Configuration File for NED Interface

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/ned.cfg
6.2 No Graphic Configuration for NE Directory Data Interface

None.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
66/116
7 PM Data INTERFACE Configuration
Figure 26: EOS PMD Configuration GUI - 1
The above Figure 26 and the next Figure 27show the “EOS PMD Configuration GUI”.
This window allows the user to view and edit the configuration fields in use by the Performance
Monitoring Data Interface for each External OS allowed to connect.
reveal more of the EOS PMD Configuration GUI.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
67/116
Figure 27: EOS PMD Configuration GUI - 2
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
68/116
From the EOS PMD Configuration GUI, the user can change:
NOTE
between the CPA processes for each PMD Interface.
So it's needed to differentiate the value of EOS PORT NUMBER for each PMD Interface
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
69/116
WARNING!!!
following actions:
c. Stop and start via PMC the PM_Handoff_IH and PM_Handoff_ASCII_CPA processes

encrypted password.
Heartbeat Period, this is the time of inactivity in seconds before a Heartbeat is sent from PMD
Send Heartbeat Response, this indicates whether the PMD Handoff Interface has to send an
(see Figure 26).

PM Point Notification Parameter Check Boxes, these allow the user to indicate which data fields
are required in a PM Point Notification.
PM Data Notification Parameter Check-Boxes, these allow the user to indicate which data fields
are required in a PM Data Notification.
List-Box, to allow the editing of a list of Regular Expressions of Friendly Name’s of NE’s for which
PMD Data is required. (If this list is empty then PMD Data for all NE’s is handed off.)
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
70/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
71/116
user interface to be saved into the PMD Interface Configuration File and this file will be again read by
PMD CPA process.

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/pmd.cfg
7.2 No Graphic Configuration for PM Data Interface

Outside the graphic mode the user can redefine the default value of the following
parameter:
– ANALOGUE
– UNSOL_EXPORT_FILTER
Location of the file containing the parameter declaration
If you need to change the value for each of these parameters it can be done in the following file:
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/pmd_ho/par
am.cfg
7.2.1 ANALOGUE
Parameter meaning
ANALOGUE parameter is a flag that allows defining the applicable range of period Types valid for
analogue Database types (Submarines) and not analogue Database types (SDH, ATM, ETH).
ANALOGUE = 0 only period Type equal to 15m, 1h and 24h will be exported (default value);
Valid for not analogue Database types (SDH, ATM, ETH).
ANALOGUE = 1 all period Types will be exported (15m, 24h, peak, FL,
immediate, 30, RM1, RM2, RM3, RM4, RM5, day, month, IM);
Valid for analogue Database types (Submarines).
7.2.2 UNSOL_EXPORT_FILTER
Parameter meaning
UNSOL_EXPORT_FILTER parameter is a filter flag applied on periodType, which gives a criterion to
export unsolicited pm_point_notif (pmPointChange) and pm_data_notif (pmNewData) events.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
72/116
UNSOL_EXPORT_FILTER = 0 periodType equal to 15 or 1h or 24h will be exported (default
value)
UNSOL_EXPORT_FILTER = 1 only periodType equal to 15 will be exported,
UNSOL_EXPORT_FILTER = 2 only periodType equal to 1h will be exported,
UNSOL_EXPORT_FILTER = 3 only periodType equal to 24 h will be exported,
UNSOL_EXPORT_FILTER = 4 only periodType equal to 15 and 1h will be exported,
UNSOL_EXPORT_FILTER = 6 only periodType equal to 1h and 24 h will be exported.
8 PM FTP DATA INTERFACE CONFIGURATION
Figure 28: EOS PMFTP Configuration GUI - 1
The above Figure 28 and the next Figure 29 show the “EOS PMFTP Configuration GUI”.
This window allows the user to view and edit the configuration fields in use by the PM FTP Data
reveal more of the EOS PMFTP Configuration GUI.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
73/116
Figure 29: EOS PMFTP Configuration GUI - 2

From the EOS PMFTP Configuration GUI, the user can change:
NOTE
between the CPA processes for each PMFTP Interface.
So it's needed to differentiate the value of EOS PORT NUMBER for each PMFTP Interface
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
74/116
WARNING!!!
following actions:
c. Stop and start via PMC the PM_Handoff_IH and PM_Handoff_FTP_CPA processes

encrypted password.
UNSOLICITED PERIOD, the time period in seconds, after which unsolicited FTP Data files are
checked for and sent to the External OS.
Heartbeat Period, this is the time of inactivity in seconds before a Heartbeat is sent from PMD
FTP Handoff Interface. A value of 0 indicates that Heartbeats are not to be sent.
Send Heartbeat Response, this indicates whether the PMD FTP Handoff Interface has to send
an Heartbeat Response when an Heartbeat Request is received from the External OS, check box
(see Figure 28).

List-Box, to allow the editing of a list of Regular Expressions of Friendly Name’s of NE’s for which
PM FTP Data is required. (If this list is empty then PM FTP Data for all NE’s is handed off.)
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
75/116
user interface to be saved into the PMFTP Interface Configuration File and this file will be again read
by PMFTP CPA process.

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/pmdftp.cfg
8.2 No Graphic Configuration for PM FTP Data Interface

Outside the graphic mode the user can redefine the default value of the following
parameter:
– ANALOGUE
– UNSOL_EXPORT_FILTER
Location of the file containing the parameter declaration
If you need to change the value for each of these parameters it can be done in the following file:
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/pmd_ho/par
am.cfg
8.2.1 ANALOGUE
Parameter meaning
ANALOGUE parameter is a flag that allows defining the applicable range of period Type for analogue
Database types (Submarines) and not analogue Database types (SDH, ATM, ETH).
ANALOGUE = 0 only period Type equal to 15m, 1h and 24h will be exported (default value);
Valid for not analogue Database types (SDH, ATM, ETH).
ANALOGUE = 1 all period Types will be exported (15m, 24h, peak, FL, immediate, 30, RM1,
RM2, RM3, RM4, RM5, day, month, IM);
Valid for analogue Database types (Submarines).
8.2.2 UNSOL_EXPORT_FILTER
Parameter meaning
UNSOL_EXPORT_FILTER parameter is a filter flag applied on periodType, which gives a criterion to
export unsolicited pm_point_notif (pmPointChange) and pm_data_notif (pmNewData) events.
UNSOL_EXPORT_FILTER = 0 periodType equal to 15 or 1h or 24h will be exported (default

value)
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
76/116
UNSOL_EXPORT_FILTER = 1 only periodType equal to 15 will be exported,
UNSOL_EXPORT_FILTER = 2 only periodType equal to 1h will be exported,
UNSOL_EXPORT_FILTER = 3 only periodType equal to 24 h will be exported,
UNSOL_EXPORT_FILTER = 6 only periodType equal to 1h and 24 h will be exported.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
77/116
8.2.3 Configuration of FTP Session
In order that an External OS (operator) can connect to a PMD FTP server, to perform an FTP session,
the user has to configure the parameters PMDFTPUSERNAME & PMDFTPPASSWD for each
External OS.
Each External OS (operator) is identified with an EOS_Identifier, i.e. an IP address (e.g.
151.98.22.48) or a host name (e.g. albh08).
The PMDFTPUSERNAME is the unique FTP login name associated to each External OS Identifier
(e.g. user1).
The PMDFTPPASSWD is a cleared Password of the FTP login name (e.g. ALcatelLucent).
The configuration of PMDFTPUSERNAME & PMDFTPPASSWD (FTP secure) is

made executing the following script:
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/script/run_ftpS
ecure
WARNING
This script must be launched after running the PM FTP Interface configuration and as
root user (using the root profile) otherwise an error message is displayed.
It' is not allowed to assign more than one user name & password to the same EOS
Identifier.
Before to start with the PM FTP user & password configuration, please check if
another EOS identifier already uses this PM FTP user checking its presence in the
/etc/passwd file and if you want to remove it, please use the following script
(launch it as root user):
$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin/ftpdel
<PMDFTPUSERNAME>
If the PM FTP operator user is already defined, an error message is displayed during
the configuration script.
If a PM FTP session is started without running the run_ftpSecure script, then it's not
possible to download the PM FTP data files.
Below there is an example of configuration of an FTP Secure user and password

associated to following specific External OS:
EOS 1= tlbh07
EOS 2= 192.168.114.71
Login as root (su -):

$ cd /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/script
$ ./run_ftpSecure
Before to continue, please check if the user is already defined in the

/etc/passwd as PMDFTP Ftp user, if you want to remove it, please use as
root user the script -> ftpdel <user>
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
78/116
The script run_ftpSecure will ask the following parameters for each External OS configured in
PMDFTP:
Eos identifier tlbh07:0

Do you want to setup ftp user and password for eos identifier tlbh07 on port 0 (y/n)? y
Please insert the pmdftp user for Eos identifier tlbh07 on port 0,
default eos0 (max 8 characters):eos0
Please insert the pmdftp password for user eos0, default ALcatelLucent:ALcatelLucent
Starting FTP user creation
Executing 'eos0' user creation
Define password for user 'eos0'
FTP user creation end successfully.
Eos identifier 192.168.114.71:0

Do you want to setup ftp user and password for eos identifier 192.168.114.71 on port 0 (y/n)? y
Please insert the pmdftp user for Eos identifier 192.168.114.71 on port 0,
default eos1 (max 8 characters):eos1
Please insert the pmdftp password for user eos1, default ALcatelLucent:ALcatelLucent
Executing 'eos1' user creation
Define password for user 'eos1'
9 REMOTE INVENTORY Data INTERFACE Configuration
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
79/116
Figure 30: EOS RID Configuration GUI - 1
The above Figure 30 and the next Figure 31 show the “EOS RID Configuration GUI”.
This window allows the user to view and edit the configuration fields in use by the Remote Inventory
Data Interface for each External OS allowed to connect.
reveal more of the EOS RID Configuration GUI.
Figure 31: EOS RID Configuration GUI - 2
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
80/116
From the EOS RID Configuration GUI, the user can change:
whereas all other setting are on External OS basis, but this value can be changed( see figure 30).
NOTE
between the CPA processes for each RID Interface.
So it's needed to differentiate the value of EOS PORT NUMBER for each RID Interface
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
81/116
WARNING!!!
following actions:
c. Stop and start via PMC the Remote_Inventory_IH and Remote_Inventory_CPA processes

encrypted password.
Heartbeat Period, this is the time of inactivity in seconds before a Heartbeat is sent from RID
Send Heartbeat Response, this indicates whether the RID Handoff Interface has to send an
(see Figure 30).

1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
82/116
QB3* Data Notification check boxes to allow the user to indicate which data fields are
required:
o neName
o neLocationName
o protocolType
o blockNumber
o blockLabel
o ALcatelLucentCompany
o unitType
o unitPartNumber
o softwarePartNumber
o cleiCode
o manufacPlant
o serialNumber
o manufacDate
o operatorInvData
Q3 Data Notification check boxes to allow the user to indicate which data fields are required:
o neName
o neLocationName
o protocolType
o userLabel
o locationName
o ALcatelLucentCompany
o unitType
o unitPartNumber
o softwarePartNumber
o cleiCode
o manufacPlant
o serialNumber
o manufacDate
o operatorInvData
NE Names of NE's for which RI Data are required (if this list is empty then no filtering by
NE Names occurs and RI Data for all NE's will be handed off).

user interface to be saved into the Remote Inventory Interface Configuration File and this file will be
again read by RID CPA process.

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/rid.cfg
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
83/116
9.2 No Graphic Configuration for Remote Inventory Data Interface
None
10 SYSTEM STATISTICS DATA INTERFACE CONFIGURATION

Figure 32: EOS SSD Configuration GUI - 1
The above Figure 32 and the next Figure 33 show the “EOS SSD Configuration GUI”.
This window allows the user to view and edit the configuration fields in use by the SS Data Interface
for each External OS allowed to connect.
reveal more of the EOS SSD Configuration GUI.
Figure 33: EOS SSD Configuration GUI - 2
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
84/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
85/116
From the EOS SSD Configuration GUI, the user can change:
whereas all other setting are on External OS basis, but this value can be afterwards changed( see
figure 32)
NOTE
between the CPA processes for each SSD Interface.
So it's needed to differentiate the value of EOS PORT NUMBER for each SSD Interface
WARNING!!!
following actions:
c. Stop and start via PMC the SSD_Handoff_IH and SSD_Handoff_CPA processes

encrypted password.
UNSOLICITED PERIOD, the time period in seconds, after which unsolicited SSD Data files are
checked for and sent to the External OS.
Heartbeat Period, this is the time of inactivity in seconds before a Heartbeat is sent from SSD
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
86/116
Send Heartbeat Response, this indicates whether the SSD Handoff Interface has to send an
(see Figure 32).

1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
87/116
user interface to be saved into the SSD Interface Configuration File and this file will be again read by
SSD CPA process.

/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/config/ssd.cfg
10.2 No Graphic Configuration for System Statistics Data Interface
None.
10.2.1 Configuration of FTP Session

In order that an External OS (operator) can connect to a SSD FTP server, to perform an FTP session,
the user has to configure the parameters SSDUSERNAME & SSDPASSWD for each External OS.
Each External OS (operator) is identified with an EOS_Identifier, i.e. an IP address (e.g.
151.98.22.48) or a host name (e.g. albh08).
The SSDUSERNAME is the unique FTP login name associated to each External OS Identifier (e.g.
user1).
The SSDPASSWD is a cleared Password of the FTP login name (e.g. ALcatelLucent).
The configuration of SSDUSERNAME & SSDPASSWD (FTP secure) is made

executing the following script:
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/script/run_ssdf
tpSecure
WARNING
This script must be launched after running the SSD Interface configuration and as
root user (using the root profile) otherwise an error message is displayed.
It' is not allowed to assign more than one user name & password to the same EOS
Identifier.
Before to start with the SSD FTP user & password configuration, please check if
another EOS identifier already uses this SSD FTP user checking its presence in the
/etc/passwd file and if you want to remove it, please use the following scrip
(launch it as root user):
$ /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin/ftpdel
<SSDUSERNAME>
If the SSD FTP operator user is already defined, an error message is displayed
during the configuration script.
If an SSD FTP session is started without running the run_ssdftpSecure script, then
it's not possible to download the SSD data files.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
88/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
89/116
Below there is an example of configuration of an FTP Secure user and password
associated to following specific External OS:
EOS 1= tlbh07
EOS 2= 192.168.114.71
Login as root (su -):

$ cd /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/script
$ ./run_ssdftpSecure
Before to continue, please check if the user is already defined in the

/etc/passwd as SSD Ftp user, if you want to remove it, please use as
root user the script -> ftpdel <user>
The script run_ssdftpSecure will ask the following parameters, for each External OS configured in
SSD:
Eos identifier tlbh07:0

Do you want to setup ssd ftp user and password for eos identifier tlbh07 on port 0 (y/n)? y
Please insert the ssdftp user for Eos identifier tlbh07 on port 0,
default eos0 (max 8 characters):ssd0
Please insert the ssdftp password for user ssd0, default ALcatelLucent:ALcatelLucent
Executing 'ssd0' user creation
Define password for user 'ssd0'
Eos identifier 192.168.114.71:0

Do you want to setup ftp user and password for eos identifier 192.168.114.71 on port
0 (y/n)? y
Please insert the ssdftp user for Eos identifier 192.168.114.71 on port 0,
default eos0 (max 8 characters):ssd1
Please insert the ssdftp password for user ssd1, default

ALcatelLucent:ALcatelLucent
Executing 'ssd1' user creation
Define password for user 'ssd1'
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
90/116
11 BACKUP/RESTORE FEATURE
Backup and Restore is normally done using SMF. From TMNOS window, selects the NMS instance
(e.g. 1353NM_1), apply Actions -> SMF -> Backup or Restore Management and then choose the
GENOS domain to apply the wanted operation (e.g. Backup operation before to launch a new
Customization and Restore operation after the Customization).
Figure 34: SMF Application for Backup/Restore
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
91/116
Figure 35: Backup for GENOS Domain
11.1 Backup/Restore Data Types
The GENOS component has a specific “DataGroup.cfg” file containing a group of data for
Backup/Restore and for this group the files involved in backup and restore operation and the
automatic procedure executed after the restore process.
Location of the file DataGroup.cfg
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/Kernel/conf
Backup/Restore data group:
GENOS_Domain
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
92/116
The involved files are:
FILE: GENOS/config/alm* -s
FILE: GENOS/config/ned.cfg -s
FILE: GENOS/config/pmd.cfg -s
FILE: GENOS/config/pmdftp.cfg -s
FILE: GENOS/config/rid.cfg -s
FILE: GENOS/config/snmp_alm.cfg -s
FILE: GENOS/config/ssd.cfg -s
FILE: GENOS/config/neData.txt
FILE: GENOS/config/neTypeAlarmSync_list.cfg
FILE: GENOS/config/snmp_filtering.cfg
FILE: GENOS/data/alm_ho/param* -s
FILE: GENOS/data/alm_ho/cpa_param*
FILE: GENOS/data/alm_ho/NameServerFile* -s
FILE: GENOS/data/alm_ho/probableCauses*
FILE: GENOS/data/alm_ho/registrationIds*
FILE: GENOS/data/alm_ho/specificProblems*
FILE: GENOS/data/pmd_ho/param.cfg -s
#FILE: GENOS/data/pmd_ho/pmd_cfg_files/ -t
#FILE: GENOS/data/pmd_ho/pmd_file_dump/ -t
#FILE: GENOS/data/pmd_ho/pmd_notif_store/ -t
#FILE: GENOS/data/pmdftp_ho/ftp_file_dump/ -t
FILE: GENOS/data/rid_ho/rid_file_dump/ -t
FILE: GENOS/data/rid_ho/rid_list_dump/ -t
FILE: GENOS/data/snmp_ho/snmp_param.cfg
FILE: GENOS/data/snmp_ho/probableCauses*
FILE: GENOS/data/snmp_ho/registrationIds*
FILE: GENOS/data/snmp_ho/specificProblems*
FILE: GENOS/data/ssd_ho/ssd_file_dump/ -t
FILE: GENOS/data/alm_ho/AS_remote_hosts
The automatic procedure executed after the restore process is:
GENOS/Kernel/script/RestorePostProc.pl
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
93/116
Location of RestorePostProc.pl
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/Kernel/script
This procedure is used to update all files holding the dynamic Socket Ports values as
they change after a new Customization.
11.2 Backup/Restore Run Levels
Backup can be applied also if GENOS is running; Restore is preferred when GENOS is not running.
The specific run levels are one belonging to specific NMS, since GENOS can be a component of
1353NM, 1354RM, 1354BM, etc….
11.3 Backup/Restore Restriction
At the moment the Backup/Restore feature is applicable only if the GENOS release doesn’t change
after a new Customization.
12 INSTALLATION GUIDE (HPUX PLATFORM)

12.1 Scope
This appendix is an installation guide for Release 5.4 packages of the Generic OS-OS Interfaces
(IOO). This installation is no driven by INSTALL_WIZARD facility and it has to be done on top of the
NMS with OS-Kernel version 7.1.2 and OS-Conf version 7.1.1 (NR8.1-PL2).
12.2 Pre-installation
In case you are going to install GENOS 5.4.0 above an OS-Kernel version where the native version is
GENOS 5.2.x, first of all it is mandatory to check some NMS configuration files since they could refer
the native GENOS version. In particular the following files could need updating as “root” user:
In the file
/alcatel/NMS/<NMS_SYSTEM>/<version>/conf/Kernel/Composition.cfg
Add or Update this line NMC: GENOS 5.* OPTIONAL
In the file
/alcatle/NMS/<NMS_SYSTEM>/<version>/conf/Kernel/GroupComposition.cfg
1. When NMS is 1353 (EML: NM) add GENOS as in the following way:
SECTION: INDEX
GROUP: STACK
GROUP: EMLIM
GROUP: EMLIMGEM
GROUP: PNM
GROUP: AS
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
94/116
GROUP: PM
GROUP: SIMULATOR
GROUP: ONBOARD_SIMULATOR
GROUP: GENOS
GROUP: STACK_SERVICES
GROUP: FTSERVICES
GROUP: FTSCHEDULER
RUNLEV: RL_0
RUNLEV: RL_1
RUNLEV: RL_2
SECTION_END:
And add the following lines for GENOS group definition:
SECTION: GENOS
COMPOSEDBY: GENOS
NAME: Genos
LEVEL: 1
START: none
STOP: none
START_WAIT: 5
STOP_WAIT: 5
TRACE_LOC: none
CRASH: none
SECTION_END:
2. When NMS is 1354 (NML: RM, BM, SN) add GENOS as in the following way:
SECTION: INDEX
GROUP: DATABASE
GROUP: ALARMS
GROUP: FAGENTS
GROUP: PMAGENTS
GROUP: TFEP
GROUP: ISNAGENT
GROUP: ISNDISPATCHER
GROUP: GENOS
RUNLEV: RL_0
RUNLEV: RL_1
RUNLEV: RL_2
RUNLEV: RL_3
RUNLEV: RL_4
RUNLEV: RL_5
SECTION_END:
And add the following lines for GENOS group definition:
SECTION: GENOS
COMPOSEDBY: GENOS
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
95/116
NAME: Genos
LEVEL: 2
START: none
STOP: none
START_WAIT: 5
STOP_WAIT: 5
TRACE_LOC: none
CRASH: none
SECTION_END:
In the file /alcatel/NMS/<NMS_SYSTEM>/<version>/conf/Kernel/GENOS.cfg
Add or modify these contents when NMS is 1353 (EML: NM):
SECTION: INDEX
SUBSYSTEM: MONITOR
SUBSYSTEM: ALARMASCII
SUBSYSTEM: ALARMSNMP
SUBSYSTEM: NE
SUBSYSTEM: PM
SUBSYSTEM: RI
SUBSYSTEM: SS
SUBSYSTEM: COMMON
SECTION_END:
Add or modify these contents when NMS is 1354 (NML: RM, BM, and SN):
SECTION: INDEX
SUBSYSTEM: ALARMASCII
SUBSYSTEM: ALARMSNMP
SUBSYSTEM: PM (only for SN)
SUBSYSTEM: SS
SUBSYSTEM: COMMON
SECTION_END:
12.3 Previous Version De-Installation
It’s needed to execute the following pre-installation steps before to proceed with a normal installation,
in case of there is a previous release of the 1359IOO package already installed on the target machine.
12.3.1 Stop Processes

Before to de-install the GENOS component from NMS, log as “NMS” user and stop (by Process
Monitoring) all processes running related to current NMS instance.
12.3.2 Delete GENOS instances

Only if there is a previous and different release of GENOS package already installed and
configured (e.g. R5.2 on top of NMS for NR7.4/NR8.1),
it’s recommended to delete from PMC, via an update of System Configuration, the multiple
instances of GENOS Alarms ASCII Interface previously configured on the installation machine,
before removing the old GENOS package (if required) and before starting a new OS Kernel
Customization.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
96/116
This recommendation is due to the changed configuration criteria of the GENOS ALARM ASCII
INTERFACE for the release 5.4. Infact now the Alarms ASCII Handoff Subsystem consists of only one
instance of the process couple (Alarm_ASCII_IH, Alarm_ASCII _CPA) and so it's needed to remove
the multiple couples, if any, created with 5.2.0. * Package.
Execute as “NMS” user the following actions:
1.) Stop all NMS processes (by PMC)

2.) Launch a SystemConfig Update (from TMN-OS) to "delete" the configured
Alarms ASCII instances
deselecting the following components from the Subsystems List frame area:
- OS-OS_Alarm_ASCII_First_Instance
- OS-OS_Alarm_ASCII_Next_Instance
12.3.3 De-Customization
OS-Kernel (from7.0.5 version on) doesn’t include any complete software removal routine. That means,
before software removal, the user can need to de-customize the GENOS processes (i.e. to de-
customize the system instance too). This step will de-configure the NMS System instance together
the instance of the GENOS NMC installed.
Execute as “root” user the following command:
$ /alcatel/Kernel/script/Decustom <NMS_SYSTEM> <NMS_INSTANCE>
At this point, the de-customization will run. Wait until it has to finish.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
97/116
12.3.4 Software Removal
After OS-Kernel de-customization, if the user wants to remove the installed components of GENOS it
has to execute as “root” user either of the following two steps:
$ rm –Rf /alcatel/<NR_VERSION>/NMC/GENOS
$ rm –Rf /alcatel/<NR_VERSION>/NMC/GENOS_INT
Where <NR_VERSION> = 8.1 (or other supported Network Release)
12.4 Installation
The commands needed to perform the installation are given in the following sections.
The software packages for Release 5.4 are delivered in the Frozen Image Format and archived in the
file 1359IOO_5.4.0.<BUILD-ID>_HPUX.tar.gz.
12.4.1 Installation from scratch
In this case, we haven’t any GENOS installation running on target machine.
To install in right way GENOS package on top of NMS (for NR8.1) we have to execute as “root” user
the following steps:
1. Create (if it does not exist) a directory to store software packages

$ mkdir /alcatel/DEPOT
and retrieve the complete delivery on this directory
2. $ cd /alcatel/DEPOT
3. Execute the get action by starting an ftp login to the lab server
The package can be retrieved from the following ftp area:
Home Page Address: http://tlbphn.btp.fac.ALcatelLucent.it/design/1359IOO/genos_area/

How to Reach Delivery: Releases -> IOO GENOS Releases -> IOO5.4 -> Deliveries
Package: 1359IOO_5.4.0.<BUILD-ID>_HPUX.tar.gz
4. Transfer the tar file 1359IOO_5.4.0.<BUILD-ID>_HPUX.tar.gz

to /alcatel/DEPOT directory
Warning: after download completion, it is recommended to check the package file checksum
5. Unzip the file:

$ cd /alcatel/<NR_VERSION>
$gzip –cd /alcatel/DEPOT/1359IOO_5.4.0.<BUILD-ID>_HPUX.tar.gz |tar xf -
6. Add the GENOS to NMS Instance.
$/alcatel/<NR_VERSION>/Kernel/script/updateInstance.pl -sys <Instance

name> -inst <Instance number> -type NMC -comp GENOS -skipconfig
7. Now you can start the “Post Installation Phase”, i.e. the System Customization (see 14.5.1)
and the System/Process Configuration (see 14.5.2).
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
98/116
12.4.2 Installation from an already installed previous release
Example 1
In this first example, we assume already to have on the installation machine a previous release of the
package.
Execute as “NMS” user the following actions:

1.) Stop all NMS processes (by PMC)
2.) Launch a SystemConfig Update (from TMN-OS) to "delete" the
configured Alarms ASCII instances (see 14.3.2)
Execute as “root” user the following actions:

3.) rm - Rf /ALcatelLucent/<NR_VERSION>/NMC/GENOS
4.) rm -Rf /ALcatelLucent/<NR_VERSION>/NMC/GENOS_INT
5.) Copy the package to /alcatel/DEPOT
6.) Unzip the GENOS package:
$ cd /alcatel/<NR_VERSION>
$gzip –cd /alcatel/DEPOT/1359IOO_5.4.0.<BUILD-ID>_HPUX.tar.gz |tar xf -
7.) Now you can start the “Customization Phase” (see 14.5.1)
$/alcatel/<NR_VERSION>/Kernel/script/updateInstance.pl -sys <Instance name> -inst
<Instance number> -type NMC -comp GENOS -skipconfig
8.) Launch again a new SystemConfig Update to configure the GENOS Alarms
ASCII Interface (see 14.5.2)
9.) Start all NMS processes
12.5 Post Installation
The following actions are required to make in order for the Handoff Interfaces to be correctly
configured.
12.5.1 System Customization
After the installation, proceed to the OS Kernel Customization.

This will configure the NMS System instance together with an instance of the GENOS NMC installed.
Execute as “root” user one of the following commands:
$ /ALcatelLucent/Kernel/script/Custom
or
$ /ALcatelLucent/Kernel/script/updateInstance.pl -sys <NMS_SYSTEM>
-inst <NMS_INSTANCE> -type NMC -comp GENOS -skipconfig
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
99/116
In the first case the following customization window will appear:
Figure 36: System Customization window - 1
Choose as selectedInstance “New Instance” and select “Actions > Apply & Exit”.
A next customization window will appear.
The main parameters to set in the Custom window (see the figure below) are:
- System_Version <Name of NMS and version installed>
- System_Instance <Instance to be created, e.g. 1,2….>
- System_Instance_Role <role of the System Instance. Default value:Master>
- System_Instance_Name <System Instance logical Name>
- Master_HostName <HostName of the System Instance >
- Master_kernel_type <Os-Kernel>
- Driver_Version <Version Kernel Instance driver>
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
100/116
The following Graphical Interface is displayed in order to collect the user input:
Figure 37: System Customization window - 2
At the end select “Actions > Apply & Exit".
Choose as Customization type “PARTIAL” and select “Actions > Apply & Exit”.
At this point, the customization will run. Wait until it has finished.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
101/116
12.5.2 System/Process Configuration
After the Customization ended, execute the process configuration.
As “NMS” user, execute the Process Configuration for the customized System Instance.
Example:
If the customized NMS is 1353NM with instance number 1, execute:
$ /alcatel/Kernel/script/ProcessConfig.ptk –sys 1353NM –inst 1
by “ALcatelLucent” user.
Another way to start the System Configuration application is selecting it from TMNOS:
Figure 38: System Configuration starting
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
102/116
The following System Configuration window will appear:
Figure 39: Select Subsystems List in System Configuration
Select and configure the following components in the Subsystems List frame area:
o OS-OS_Alarm_ASCII
o OS-OS_Alarm_SNMP
o OS-OS_NE_Inventory
o OS-OS_Remote_Inventory
o OS-OS_PM_Handoff
o OS-OS_PMFTP_Handoff
o OS-OS_SSD_Handoff
o OS-OS_Ioo_Monitor
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
103/116
Selecting each OS-OS Component in the Subsystems List, a check on the presence of the License
File will be done and the following Warning window will appear in case of this License File isn't present
under the directory /usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin:
Figure 40: Check License File presence without success
Pressing the Actions: Close the next window will appear (e.g for the OS-OS_Alarm_ASCII
Subsystem):
Figure 41: Quit Subsystems Selection
Press OK button and “Quit” the Process Configuration window.
If the check on the presence of the License File for each 1359IOO Subsystem is successfully then the
following Window will appear:
Figure 42: Check License File presence with success
Press the Action:Apply and exit and launch the System Configuration pressing the “Update Config”
item in the Main menu.
After done, “Quit” the Process Configuration window.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
104/116
12.5.3 GENOS Configuration on NMS co-hosted
!!! WARNING!!!
The same 1359IOO Interface cannot be configured for more than one instance of NMS on the
same host (NMS co-hosted) unless the related fixed EOS socket port was changed so as to be
different for each different NMS co-hosted. This is valid for all the 1359IOO Interfaces but Alarms
SNMP (see 14.5.6).
The reason of this recommendation is due to the fixed values for EOS socket ports; in fact if these
values are equal for more then one instance of NMS on the same host, they will give rise to a conflict
between the CPA processes of the related GENOS Interface.
If the same 1359IOO Interface has to be configured for more than one instance of an NMS on the
same host then it's strongly recommended to differentiate (via GENOS Configuration Tools) the value
of EOS Port Number for each different NMS co-hosted.
Anyway, for Alarms ASCII and SNMP Interface this recommendation can be avoided thanks to
multi AS feature, this means that the ASCII & SNMNP Interfaces can be configured only under
one instance of NMS on the same host and each Interface will be able to handoff the alarms
coming from any other NMS co-hosted.
12.5.4 Locating the GENOS files

At this point, the processes are instantiated and configured.
The location of the GENOS files is under the related System Instance root directory:
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS
Example:
Taking in account the configured system instance as the 1353NM_1, GENOS files will be located
under the root directory:
/usr/Systems/1353NM_1/GENOS
12.5.5 Considerations about the Configuration Tools

OS Kernel (from 7.0.5 version on) provides the dynamic allocation of ports for different System
Instances of the Applications.
A new feature of the Release 5.2 for GENOS foresees the dynamic allocation by OS Kernel only of
the socket ports used for the internal communication between GENOS processes while all external
socket ports, for communication between the EOS and the GENOS processes, will be hard coded. All
these socket ports are present in the GENOS configuration files and only the dynamic values change
after each new customization.
However the user can modify the EOS Port Number, i.e. the parameter indicating the port used by
the processes to listen for connections from the EOS, for all Subsystems but SNMP Alarms using the
new GENOS Configuration Tools and the allowed range of values [20001:21000].
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
105/116
12.5.6 SNMP restrictions
Actually, only one Alarm_SNMP_CPA instance is allowed. This means that if two or more instances
of the same NMS are active on the same machine, the Alarm_SNMP_IH & Alarm_SNMP_CPA
processes have to be configured only on one of these instances.
In order to do that, deselect the OS-OS_Alarm_SNMP when executing the step related to process
configuration for all instances except for that one where the Alarm SNMP interface has to be
configured.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
106/116
12.5.7 Starting the Processes
Before to start the 1359IOO processes ensure that the License File for each configured 1359IOO
Subsystem is present under the directory:
To start the 1359IOO processes, launch the Process Monitoring Control from TMNOS management
menu and start the GENOS group of processes from the GUI. The green arrow will indicate the right
start of processes.
Figure 43: Starting GENOS processes via PMC
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
107/116
13 TROUBLESHOOTING
This appendix aims to give solutions to most frequent problems that occur during the 1359IOO
installation and configuration procedures.
13.1 HP-UX Platform

• Stop of 1359IOO Subsystem processes after thirty minutes:
In the trace file for each Subsystem-> 1359IOO License not verified! A demo 1359IOO
application will starts for thirty minutes.
Solution:
• If the license file is not present under directory
Get the MAC address of the host where 1359IOO is installed through the UNIX
command “lanscan –a” and request the license file generation to 1359IOO product
manager.
• If the license file is present under directory
Get the MAC address of the host where 1359IOO is installed through the UNIX
command “lanscan –a” and check if it is equal to the name of license file under
directory
Verify if it has the read permissions for user, group and all through the
command ls –l; if the license file has no read permissions then give it the right
permission with the command chmod 444 or chmod 777
• Wrong RID, PMD and SSD processes start-up:
Check if the license file is present under directory
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/bin;
If it doesn’t present, find the MAC Address of the host where IOO is installed through the UNIX
command “lanscan –a” and send this address to 1359IOO product manager to request the
license file generation.
• Socket error: CMISsocket error = 5018 -Connection refused.
Can't open a socket connection with Agent root instance.
(in the trace file alm_ih_ascii.trace/alm_ih.trace)
Reason:
Wrong AS configuration (NMS_IDENTIFIER, SYSTEM, AS_HOST_IDENTIFIER,
IP_HOST_IDENTIFIER, AS_PORT_IDENTIFIER)
Solution:
• Open the files param_ascii.cfg/param.cfg and
NameServerFile_ascii.cfg/ NameServerFile.cfg under
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/alm_ho
directory, on local host where 1359IOO is running, and check if the value of
ASCURIM_ID present in the first files is equal to string value for DN, related to
SYSTEM ASCUR, present in the second files
• Open the file NameServerFile.nr6 under
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/conf directory and check if
the values of DN, SYSTEM, HOST and PORT, related to SYSTEM ASCUR, are equal
to values of
NMS_IDENTIFIER, SYSTEM, AS_HOST_IDENTIFIER and AS_PORT_IDENTIFIER
specified on AS configuration GUI and stored in the files
NameServerFile_ascii.cfg/NameServerFile.cfg.
The file NameServerFile.nr6 can be related to ASCURIM running on the same local
host where 1359IOO is installed or on a different remote host.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
108/116
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
109/116
• Wrong unsolicited notification for Alarms ASCII/SNMP I/F exporting alarms
got from different AS:
More Raise/Clear notifications are received for the same alarm identities.
Reason:
wrong AS configuration i.e. the same value for NMS IDENTIFIER is used for different AS
Identities.
Solution:
Stop the Alarms ASCII/SNMP IH & CPA processes
Change the AS configurations so that the NMS IDENTIFIER value is different for each AS
Identity
Start again the Alarms ASCII/SNMP IH & CPA processes
• No response from Alarms ASCII/SNMP Interface following a request from an
External OS (after an OS-Resilience switchover)
(In the trace file alm_ih_ascii. trace/alm_ih.trace: “Connection refused. Can’t open a socket
connection with Agent root instance”)
Check if the value for AS_PORT_IDENTIFIER related to local host (new active machine) in all
the configuration files NameServerFile_ascii.cfg/NameServerFile.cfg under
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/alm_ho/ directory
is equal to value of PORT related to SYSTEM ASCUR in file NameServerFile.nr6 under
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/conf directory on the new active
machine.
• Wrong GENOS CPA processes start-up:
In the trace file for each 1359IOO Interface TCP: connecting to host ……. port ……
errored
Reason:
The same 1359IOO Interface cannot be configured for more than one instance of NMS on the
same host (NMS co-hosted) if the related fixed value for EOS socket port is equal for each
different NMS co-hosted.
Solution:
Use the GENOS configuration tools via Web to change the EOS Port Number, i.e. the
parameter indicating the port used by the each process to listen for connections from the
EOS, so as this value be different for each Subsystem on different NMS co-hosted. This is
valid for all Subsystems but Alarms SNMP.
NOTE: for Alarms ASCII and SNMP Interface this restriction can be avoided thanks to multi
AS feature, this means that the ASCII & SNMNP Interfaces will be configured only under one
instance of NMS on the same host but each Interface will be able to handoff the alarms
coming from any other NMS co hosted.
• UNRESERVE NOTIFICATION OPERATOR NAME NOT
AVAILABLE FROM AS:
The operator name for alarm unreserve notification isn’t exported even if the parameter
ENABLE_OPERATOR_NAME_FOR_UNRESERVE is equal to 1 in param_ascii.cfg/param.cfg files
under directory
/usr/Systems/<NMS_SYSTEM>_<NMS_INSTANCE>/GENOS/data/alm_ho.
Reason:
Starting from AS 6.5.1 P5.1, at the time of the Alarm Unreservation, the information related to
the previous Alarm Reservation (reservation time and user name) can be cleared or
ASCURIM param.cfg and independently from setting of GENOS parameter
ENABLE_OPERATOR_NAME_FOR_UNRESERVE at default value.
* If CLEAN_FIELDS_ON_UNRESERVE is set to True or is missed in ASCURIM
param.cfg, these fields are cleaned (default behaviour)
* If CLEAN_FIELDS_ON_UNRESERVE is set to False, the alarm will be unreserved,
but the Reservation Time and the Reservation User Name keep the last user that
reserved it and the time of the last reservation.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
110/116
Solution:
If you want to export in Alarm Unreserve notification the field containing the
name of the operator that performed the reserve action on AS then the new
configuration parameter has to be present in ASCURIM param.cfg with
False value.
Check in ASCURIM param.cfg, related to AS connected to Alarm ASCII/SNMP Interface,
the presence of the parameter CLEAN_FIELDS_ON_UNRESERVE with false value.
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
111/116
• LIST-PM-DATA Request provides an empty list even if PMDS DB contains
relevant PM data
Reason:
This happens when startPeriod and endPeriod fields are not filled
accordingly with periodType value.
Solution:
Take in account that LIST_PM_DATA_REQ command for periodType
belongs to the set (1h, RM1, RM2, RM3, RM4, RM5, FL, immediate, peak,
30-day, IM, day, month) requires that the startPeriod and endPeriod
cannot be blank. Whereas LIST_PM_DATA_REQ command handles
startPeriod and endPeriod "blank" as default value only when periodType
is "15Minute" or "24Hour. For 15 min the default is mapped into the first
period of current day. For 24hr the default is mapped into the earliest
available time period.
Abbreviations
For Abbreviations and Terms refer to the following list:
ALM Alarm
AS Alarm Surveillance
ASCII American Standard Code for Information Interchange
AVA Attribute Value Assertion
BM 1354BM Broad Band Manager
CSV Command Separated Value
EML Element Manager Layer
EOS External OS
FTP File Transfer Protocol
GEM Generic EML
GNE Gateway NE
GUI Graphic User Interface
I/O Input/Output
IOO Generic OS-OS Interfaces (GENOS)
IP Internet Protocol
ITF Interface
MOI Managed Object Identifier
NE Network Element
NED NE Directory
NM Network Management
NML NM Layer
NMS NM System
NR Network Release
OND Optical Network Division
OS Operator System
PDH Pre-synchronous Digital Hierarchy
PM Performance Monitoring
PMC Process Monitoring Control
PMD PM Data
PMDS Performance Monitoring Data System
PNM Physical Network Manager
RI Remote Inventory
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
112/116
RID RI Data
RM 1354 Network Manager
SDH Synchronous Digital Hierarchy
SH 1353SH (new name is 1353NM)
SNMP Simple Network Management Protocol
SONET Synchronous Optical Network
SW Software
TCP Transport Control Protocol
USM User Service Manager
1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
113/116
INDEX
None.
ADMINISTRATION GUIDE 1350OMS-OI/IOO 5.4
Index 3AL 88354 AAAA Ed. 05 114/116

CUSTOMER DOCUMENTATION FEEDBACK
The meaning of this section is to collect customer feedback about this handbook.
Scope of this activity is the improvement and innovation of customer documentation through the
understanding of customer needs.
Your comments are welcome.
Please send your comment also if you appreciate the handbook.
You can send them to your Local Alcatel Technical Assistance Center.
They will be addressed to the team in charge of the relevant manual.
The following form supplies an example only of useful info, as a guide of the type of expected
feedback.
It is possible fill part of the form, add other data and so on.
How to send feedback:
• copying the example form, filling it and sending it to your Local Alcatel Technical Assistance
Center. In this case handbook data are already available at the page bottom.
• using the same form available as a file in the relevant documentation CD-ROM, saving,
filling and sending it by e-mail to your Local Alcatel Technical Assistance Center.
• creating a dedicated form on paper or file and sending it to your Local Alcatel Technical
Assistance Center.
We’ll take into account of your suggestion.
We reserve to modify consequently the handbook according to the correctness and congruence of the
suggestion and requests.
ADMINISTRATION GUIDE 1350OMS-OI/IOO 5.4
Customer Documentation Feedback 3AL 88354 AAAA Ed. 05 115/116

CUSTOMER DOCUMENTATION FEEDBACK
Handbook data
Handbook title, release, version:
Handbook type:
Handbook part number and edition
General evaluation
SUBJECT 5 (max.) 4 3 2 1 (min.)
Total evaluation
Info quantity
Info quality
Info structure
Consulting facility
Layout
Chapter evaluation
PREFACE 5 (max.) 4 3 2 1 (min.)
CHAPTER 1
CHAPTER 2
……
….
…….
APPENDICES
Your comments (strictly necessary when value is less than 3)
Suggestion for improvements

Which subject to deepen:
How to deepen:
Subject to eliminate or reduce:
Other comments/suggestions:
Error identified
Reader Info
Name: Date;
Company: Job:
Address:
E-mail:
Phone: Fax:
1350OMS-OI/IOO 5.4 ADMINISTRATION GUIDE
116/116 3AL 88354 AAAA Ed. 05 Customer Documentation Feedback

1350OMS-OI/IOO 5.4
3AL 88354 AAAA Ed. 05
117/116
3AL 88354 AAAA
Edition 05
05
03 30 2009
ECR xxxx
DELIVERY
3AL 88354 AAAA
1350OMS-OI/IOO
1359IOO
5.4
5.4.0.5
S. App1 - S. App2
S. Aut
Wireline Optics OMSN Vimercate
All rights reserved.

Passing on and copying of this document,
use and communication of its contents is not permitted
without written authorization from Alcatel-Lucent.
www.alcatel-lucent.com

3al88354aaaa - V1 - 1359 Ioo Administration

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

3al88354aaaa - V1 - 1359 Ioo Administration

Hochgeladen von

Copyright:

Verfügbare Formate

Alcatel-Lucent

1359IOO | Release 5.4

3AL 88354 AAAA

All other trademarks are the property of their respective owners.

Copyright © 2007 Alcatel-Lucent

3AL 88354 AAAA

All rights reserved.

This handbook applies to the following product-releases:

PRODUCT ANV P/N

1359IOO 3AL 88301 AAAA

PRODUCT RELEASE VERSION (N.B.) ANV P/N

1359IOO 5.4 5.4.0.5 3AL 88354 AAAA

EDITION DATE CHANGE NOTE

Ed 01p01 08/02/2007 First Proposal Edition for IOO 5.4.0 at DR2

Ed 02 27/03/2008 Update documents icon/images of brand, to align with ALcatelLucent

Ed04 06/05/2008 Apply the new document template

As handbook P/N 3AL 88354 AAAA (this handbook)

EDITION DATE CORRESPONDING TO INTERNAL EDITION DOC.

Ed 04 05/05/2008 Edition 04 Iteration 01

Ed 05 03/27/2009 Add reserveStatus config

1359IOO Release. 5.4

Pls refer to Table of Contents 0

General Information on Documentation

Pls refer to Preliminary Information.0

1.1 Technical Objectives

Figure 1: Position of IOO within Network Management

1.2 Product Characteristics

• IOO Performance Monitoring Data Handoff Interfaces (IOO PM)

• IOO NE Directory Data Handoff Interfaces (IOO NED)

• IOO System Statistics Handoff Interfaces (IOO SS)

• IOO Web Genos Tool

Table 1 IOO Subsystem interfaces on HP-UX Platform

Alarms Data Handoff Y Y N

For the format:

IOO ALM IOO NED IOO RI IOO PM IOO SS

ASCII SNMP ASCII ASCII ASCII FTP FTP

Figure 2: Structure of IOO GENOS

Table 2 IOO Genos Tools on HP-UX Platform

Alarms Data Handoff SNMP Itf Y

PM Data Handoff ASCII Itf Y

PM Data Handoff FTP Itf Y

Key: Y = Supported N = Not Supported

– 1354RM / 1354BM-ETH/1354BM-PR/1354BM-ATM /1353NM-A (GEM)

1.4 Network Releases Compatibility

2 IOO License management and policy

2.1 Operator side

3.1 Starting of User Configuration Tool

Figure 4: User Authorization GUI

Figure 5: Error message for wrong User Authorization

Figure 7: View/Add/Remove Data Buttons

From left to right:

4.1 Graphic User Interface for EOS

Figure 8: EOS ASCII Configuration GUI - 1

Figure 10: EOS ASCII Configuration GUI - 3

Figure 12: EOS ASCII Configuration GUI - 5

Figure 14: EOS ASCII Configuration GUI - 7

Identifier, the name or IP address of the External OS.

Key, expected from the External OS in a CONNECT-REQUEST. Always contains * characters as

Figure 15: AS ASCII Configuration GUI - 1

Example: of Additional Information filtering constraint

Two List-Boxes to allow the editing of Regular Expressions of:

If “event type == communicationAlarm” then verify as follows:

If (“friendlyName == *timingGenerator OR friendlyName == SyncPu* OR friendlyName = *2MbpsT*)

If (“friendlyName == timingGenerator OR friendlyName == SyncPu OR friendlyName = 2MbpsT)