Ionos Nms p5 Ems User Guide 253153962-05

8/17/2019 Ionos Nms p5 Ems User Guide 253153962-05

1/205

IONOS-NMS P5

EMS Management

Installation and User Guide

253 153 962-05

May 2011 – Issue 05


2/205

LIST OF CHANGES

(A new edition replaces all previous versions)

N° Date Change description Page

253 153 962-05

3 000 322 859 000 03

October 2008 Creation of original user guide forversion P5.3

All pages

253 153 962-05

3 000 322 859 000 04

April 2009 Update of user guide for version P5.4 All pages

253 153 962-05

3 000 322 859 000 05

May 2011 Update of user guide for version P5.5 All pages


3/205

WARNING

SAGEMCOM follows all the technical evolutions assiduously and continuously seeks the improvement of itsproducts so as to make some profit fully its customers.

Consequently, it thus assumes the right to make evolve without notice its documentation.

ENVIRONMENT

Preservation of the environment as part of a sustainable development logic is an essential concern ofSAGEMCOM.

The desire of SAGEMCOM is to operate systems observing the environment and consequently it has decidedto integrate environmental performances in the life cycle of its products, from manufacturing to commissioning,use and elimination.

PACKING :

The presence of the logo (green dot) means that a contribution is paid to an approvednational organisation to improve packaging recovery and recycling infrastructures.

To facilitate recycling, please respect the sorting rules set up locally for this kind ofwaste

BATTERIES :

If your product contains batteries, they must be disposed of at appropriate collection points.

THE PRODUCT :

The crossed-out waste bin stuck on the product (or on its accessories) means that the productbelongs to the family of electrical and electronic equipment.

In this respect, the European regulations ask you to dispose of it selectively :• At sales points in the event of the purchase of similar equipment.• At the collection points made available to you locally (drop-off centre, selective

collection, etc.).


4/205

TABLE OF CONTENTS

LIST OF FIGURES .............................................................................................................................................................9

LIST OF ABBREVIATIONS ............................................................................................................................................12

TYPOGRAPHICAL CONVENTIONS.............................................................................................................................13

GLOSSARY.......................................................................................................................................................................14

1. SYSTEM INSTALLATION AND MANAGEMENT...................................................................................................15

1.1 - GENERAL INFORMATION..........................................................................................................................................15 1.1.1 - IONOS-NMS ..................................................................................................................................................15 1.1.2 - Architecture ....................................................................................................................................................16

1.1.2.1 - General architecture .................................................................................................................................................16 1.1.2.2 - Software architecture ...............................................................................................................................................17

1.1.3 - Workstations ..................................................................................................................................................17

1.1.4 - Man-Machine Interface (MMI) .....................................................................................................................17 1.2 - INSTALLING THE CD WITH WINDOWS .....................................................................................................................18

1.2.1 - To install the Server + Client Applications ................................................................................................18 1.2.1.1 - To install the Server Application (with Client) .......................................................................................................18 1.2.1.2 - To install the Client Application ...............................................................................................................................20 1.2.1.3 - To install the Proxy Application ...............................................................................................................................21 1.2.1.4 - To install the NMSperftool Application ...................................................................................................................22

1.2.2 - To install LCT application for equipment (FMX, Sagem-Link, FSP2000, FSP3000, ADR155E) ......22 1.2.2.1 - To install LCT application for equipment of type FMX, Sagem-Link, FSP2000, FSP3000 ............................22 1.2.2.2 - To install LCT application for equipment ADR155E.............................................................................................23

1.2.3 - Available configurations on Server IONOS-NMS .....................................................................................24 1.2.3.1 - To configure TFTP server ........................................................................................................................................24 1.2.3.2 - To configure IP address of the server seen by the equipment ...........................................................................24 1.2.3.3 - To configure the backup directories .......................................................................................................................24 1.2.3.4 - To configure the HTTP Proxy Function .................................................................................................................25 1.2.3.5 - To configure the function Traps Forward...............................................................................................................25 1.2.3.6 - To configure the parameters associated with the collection of performance ...................................................25 1.2.3.7 - To authorize the data entry of the accents and the special characters in the "Name" of the equipment .....27 1.2.3.8 - To inhibit control on the name of cross-connections in the audit of the equipment.........................................27 1.2.3.9 - To configure the time interval between IONOS-NMS and equipment ...............................................................28 1.2.3.10 - To configure the performance parameters used by equipment .......................................................................28 1.2.3.11 - To configure the IONOS-NMS server name .......................................................................................................28 1.2.3.12 - To configure the send of mail on alarm change .................................................................................................28 1.2.3.13 - To configure the timers used for the send of mail ..............................................................................................29 1.2.3.14 - To configure the send of mail on critical alarm..................................................................................................29 1.2.3.15 - To configure the send of mail on a “system” alarm...........................................................................................30 1.2.3.16 - To configure the send of mail on a specific event type .....................................................................................30


5/205

1.2.3.34 - To configure the SNMP trap generator................................................................................................................41 1.2.3.35 - Configuration file to display the long name of the trail(s) in relation to its alarm pk ......................................43 1.2.3.36 - To run the getTrailLongNames script...................................................................................................................44 1.2.3.37 - To configure the FMX backup configuration file .................................................................................................44

1.2.3.38 - To configure the user rights to perform actions from the Federator application ............................................45 1.2.4 - Available configurations on Client IONOS-NMS ......................................................................................46 1.2.4.1 - To configure the help on line ...................................................................................................................................46 1.2.4.2 - To configure Internet Explorer to use HTTP Browser on the equipment of type ADR....................................46 1.2.4.3 - To configure Internet Explorer to use HTTP Proxy ..............................................................................................47 1.2.4.4 - To inhibit the data entry of spaces in the M1400 name of the equipment ........................................................47 1.2.4.5 - To activate the data entry of upercase in the M1400 name and longname......................................................47 1.2.4.6 - To configure the automatic deconnection of client after inactivity period .........................................................48 1.2.4.7 - To configure the number of NEs for which a warning message is displayed in NML View ............................48 1.2.4.8 - To deactivate the automatic routing of trails/bearer SDH ...................................................................................48

1.2.4.9 - To configure the use of Proxy for SLF-v1 and SLF-N..........................................................................................49 1.2.4.10 - To configure the use of Proxy for SLF-H .............................................................................................................49 1.2.4.11 - To configure the use of client without an alarm window....................................................................................49 1.2.4.12 - To display the ADR10000 Proxy menu ...............................................................................................................49 1.2.4.13 - To configure the launching of the Equipment View (ADR10000) ....................................................................49

1.2.5 - The Application Easy Launcher under Windows .....................................................................................50 1.2.6 - To start the Server Application with Windows ..........................................................................................51

1.2.6.1 - To start the Server with Easy Launcher.................................................................................................................51 1.2.6.2 - To start the server without Easy Launcher ............................................................................................................51

1.2.7 - To start the Client Application with Windows ............................................................................................52 1.2.7.1 - To configure the time difference between client and server ...............................................................................53

1.2.8 - To close the Server Application with Windows .........................................................................................53 1.2.8.1 - To close the Server with Easy Launcher ...............................................................................................................53 1.2.8.2 - To close the Server without Easy Launcher. ........................................................................................................53

1.2.9 - To close the Client Application ...................................................................................................................53 1.2.10 - To start the HTTP Proxy Application with Windows ..............................................................................53 1.2.11 - To close the HTTP Proxy Application with Windows ............................................................................54 1.2.12 - To start the Proxy Application for SLF-v1 and SLF-N ...........................................................................54 1.2.13 - To close the Proxy Application for SLF-v1 and SLF-N .........................................................................55

1.2.14 - To start the Proxy Application for SLF-H under Windows ....................................................................55 1.2.15 - To close the Proxy Application for SLF-H ...............................................................................................55 1.3 - TO INSTALL THE CD FOR SOLARIS .........................................................................................................................56

1.3.1 - To install the Server and Client Applications ............................................................................................56 1.3.1.1 - To install the Server Application with Solaris ........................................................................................................56 1.3.1.2 - To install the Client Application with Windows......................................................................................................56 1.3.1.3 - To install the HTTP Proxy Application with Solaris ..............................................................................................56

1.3.2 - To install LCT application for equipment (FMX, Sagem-Link, FSP2000, FSP3000, ADR155E) ......57 1.3.3 - Available configurations on Server IONOS-NMS .....................................................................................57 1.3.4 - Available configurations on Client IONOS-NMS ......................................................................................57 1.3.5 - To start the Server Application with Solaris ..............................................................................................57 1.3.6 - To start the Client Application with Windows ............................................................................................57 1.3.7 - To close the Server Application with Solaris .............................................................................................57 1.3.8 - To close the Client Application with Windows ..........................................................................................57 1.3.9 - To start the Proxy Applications with Solaris ..............................................................................................57 1.3.10 - To stop the Proxy Application with Solaris ..............................................................................................58 1 3 11 T t t SUN t ti ith S l i 58


6/205

1.5.2.4 - Restore of backup directories copied on magnetic tape with Solaris ................................................................62 1.5.3 - To migrate a database .................................................................................................................................63

1.5.3.1 - Migration of a database with Windows. .................................................................................................................63 1.5.3.2 - Migration of a database with Solaris. .....................................................................................................................64

1.5.4 - Database Management (Split & Merge) ....................................................................................................64 1.5.4.1 - To split a IONOS-NMS database............................................................................................................................65 1.5.4.2 - Split with Solaris ........................................................................................................................................................65 1.5.4.3 - Split with Windows ....................................................................................................................................................66 1.5.4.4 - To merge two IONOS-NMS databases .................................................................................................................66 1.5.4.5 - Merge with Solaris ....................................................................................................................................................67 1.5.4.6 - Merge with Windows ................................................................................................................................................67

1.5.5 - Updating the traps managers table of NEs after a merge or a split ......................................................67 1.6 - EMS-ADR DATABASE MANAGEMENT (ADR 10000) .............................................................................................68

1.6.1 - To backup the EMS-ADR database ...........................................................................................................68 1.6.2 - To restore the EMS-ADR database in R7.2 ..............................................................................................68 1.6.3 - To restore the EMS-ADR database in R8.1 ..............................................................................................69

1.7 - TO SAVE THE EQUIPMENT DATABASES (EXCEPT METERING)..................................................................................71 1.8 - TO EXPORT EQUIPMENT INVENTORY IN A FILE XML.................................................................................................71 1.9 - TO EXPORT EQUIPMENT INVENTORY IN A FILE TXT.................................................................................................72 1.10 - TO EXPORT DETAILED EQUIPMENT INVENTORY IN A FILE TXT ..............................................................................72 1.11 - ALARMS RESYNCHRONIZATION OF IONOS-NMS FOR THE SERVER NETCOOL ..............................................73 1.12 - TO RUN THE FORCE POLLING SCRIPT ..................................................................................................................73 1.13 - TO RUN THE ALIGN-NES SCRIPT...........................................................................................................................73

2. TOPOLOGY MANAGEMENT ....................................................................................................................................75

2.1 - INTRODUCTION........................................................................................................................................................75 2.2 - TOPOLOGY VIEW WINDOW .....................................................................................................................................75 2.3 - SUB-NETWORK ADMINISTRATION............................................................................................................................77

2.3.1 - To create a sub-network ..............................................................................................................................77 2.3.2 - To display/modify the properties of a sub-network ..................................................................................79 2.3.3 - To move a sub-network ...............................................................................................................................81 2.3.4 - To delete a sub-network ..............................................................................................................................82 2.3.5 - To rename a sub-network ............................................................................................................................82 2.3.6 - To change the sub-network background image .......................................................................................82 2.3.7 - To delete the sub-network background image .........................................................................................82

2.4 - ADMINISTRATION OF NETWORK ELEMENTS (NE, VNE) .........................................................................................83 2.4.1 - To create a network element .......................................................................................................................83 2.4.2 - To copy a network element (NE, VNE) ......................................................................................................89 2.4.3 - To move a network element (NE, VNE) ....................................................................................................89 2.4.4 - To delete a network element (NE, VNE) ...................................................................................................89 2.4.5 - To rename a network element (NE, VNE) .................................................................................................90

2.4.6 - To display and modify the properties of a network element ...................................................................90 2.4.7 - To modify the M1400 name of a network element (NE, VNE) ...............................................................92 2.4.8 - To audit a network element (NE) ................................................................................................................95 2.4.9 - To reapplicate the general parameters in a network element (NMS to NE) ......................................104 2.4.10 - To align the capacity parameters from a network element (NE to NMS) .........................................106 2.4.11 - To perform an inventory alignment for a network element (NE) ........................................................107 2 4 12 To display and modify the configuration of an equipment 109


7/205

3.1 - INTRODUCTION......................................................................................................................................................130 3.2 - NML VIEW WINDOW ..............................................................................................................................................130

3.2.1 - To display / filter a list of objects ...............................................................................................................132 3.2.2 - To use an element of a list as input filter .................................................................................................134 3.2.3 - List of objects in search area ....................................................................................................................134

4. ALARMS MANAGEMENT........................................................................................................................................135

4.1 - INTRODUCTION......................................................................................................................................................135 4.2 - MANAGEMENT OF CURRENT ALARMS....................................................................................................................136

4.2.1 - To display the current alarms ....................................................................................................................136 4.2.2 - To acknowledge a current alarm ..............................................................................................................138 4.2.3 - To unacknowledge a current alarm ..........................................................................................................138 4.2.4 - To filter current alarms by criteria .............................................................................................................138 4.2.5 - To locate a current alarm ...........................................................................................................................140 4.2.6 - To display the properties of a current alarm ...........................................................................................140 4.2.7 - To display the alarms unacknowledged cleared alarms .......................................................................141 4.2.8 - To display the new alarms .........................................................................................................................142 4.2.9 - To filter current alarms by multi-criteria ...................................................................................................143 4.2.10 - To activate the send of mails on alarms modification .........................................................................145 4.2.11 - To activate the send of mails on critical alarm .....................................................................................146

5. HISTORIES MANAGEMENT ...................................................................................................................................148

6. PREFERENCES MANAGEMENT ...........................................................................................................................152

6.1 - INTRODUCTION......................................................................................................................................................152 6.2 - PREFERENCES ......................................................................................................................................................152

6.2.1 - To change the IP address of the server ..................................................................................................152 6.2.2 - To change an icon image ..........................................................................................................................153 6.2.3 - To change the default properties of the Nes ...........................................................................................154 6.2.4 - To change the default properties of sounds ...........................................................................................155

7. USERS MANAGEMENT ...........................................................................................................................................157 7.1 - INTRODUCTION......................................................................................................................................................157 7.2 - ADMIN VIEW WINDOW............................................................................................................................................157

7.2.1 - To create a profile .......................................................................................................................................159 7.2.2 - To create a group ........................................................................................................................................161 7.2.3 - To create a user ..........................................................................................................................................163 7.2.4 - To display/modify the properties of a profile ...........................................................................................164 7.2.5 - To display/modify the properties of a group ............................................................................................166 7.2.6 - To display/modify the properties of a user ..............................................................................................168

7.2.7 - To copy a profile ..........................................................................................................................................170 7.2.8 - To copy a group ..........................................................................................................................................171 7.2.9 - To copy a user .............................................................................................................................................172 7.2.10 - To delete a profile .....................................................................................................................................174 7.2.11 - To delete a group ......................................................................................................................................174 7.2.12 - To delete a user ........................................................................................................................................174 7 2 13 To lock a user 174


8/205

8.2.11 - To Restore the database on a server ....................................................................................................183 8.2.12 - To Change a server ..................................................................................................................................183 8.2.13 - Backup 1+1 of IONOS NMS servers (Option) ......................................................................................183

8.2.13.1 - Introduction ............................................................................................................................................................183

8.2.13.2 - Procedure of backup ............................................................................................................................................184 APPENDIX - SPECIAL FUNCTIONS UPON OBJECTS ........................................................................................187

APPENDIX - SNMP VIEW TABLE ..............................................................................................................................190

MIB II MENU ..................................................................................................................................................................190 EQUIPMENT MENU.........................................................................................................................................................195 SESSION MENU..............................................................................................................................................................198

APPENDIX – EXAMPLE OF SPLIT/MERGE SCENARIO.......................................................................................199

APPENDIX – EXAMPLE OF SNMP TRAP GENERATOR CONFIGURATION ...................................................202

APPENDIX – EXAMPLE OF GETTRAILLONGNAMES SCRIPT USAGE ...........................................................204


9/205

LIST OF FIGURES

FIGURE 1.1 : GENERAL ARCHITECTURE OF IONOS-NMS.................................................................................................16 FIGURE 1.2 : IONOS-NMS SOFTWARE PLATFORM ...........................................................................................................17 FIGURE 1.3 : WINDOW - IONOS SOLUTIONS SERVER – DIAGNOSTIC.................................................................................18 FIGURE 1.4 : WINDOW - IONOS SOLUTIONS CLIENT – DIAGNOSTIC ..................................................................................20 FIGURE 1.5 : WINDOW - NMSPERFTOOL – SCHEDULED TASK...........................................................................................22 FIGURE 1.6 : EASY LAUNCHER (1) .......................................................................................................................................50 FIGURE 1.7 : EASY LAUNCHER (2) .......................................................................................................................................50

FIGURE 1.8 : EASY LAUNCHER (3) .......................................................................................................................................51 FIGURE 1.9 : WINDOW - START IONOS-NMS SERVER .......................................................................................................51 FIGURE 1.10 : DOS COMMANDS WINDOW ..........................................................................................................................52 FIGURE 1.11 : WINDOW - CONNECT TO WHICH NAME SERVER .........................................................................................52 FIGURE 1.12 : LOGIN WINDOW ...........................................................................................................................................52 FIGURE 1.13 : WINDOW – HTTP PROXY APPLICATION .....................................................................................................54 FIGURE 1.14 : WINDOW SLF-V1 SLF-N PROXY APPLICATION .........................................................................................55 FIGURE 1.15 : WINDOW – SLF-H PROXY APPLICATION ....................................................................................................55 FIGURE 1.16 : FORCE BACKUP WINDOW............................................................................................................................60

FIGURE 1.17 : BACKUP / DATABASE WINDOW .....................................................................................................................61 FIGURE 2.1 : TOPOLOGY MAIN VIEW ..................................................................................................................................75 FIGURE 2.2 : WINDOW – CREATE SUB-NETWORK (1).........................................................................................................77 FIGURE 2.3 : WINDOW – CREATE SUB-NETWORK (2).........................................................................................................78 FIGURE 2.4 : WINDOW – CREATE SUB-NETWORK (3).........................................................................................................78 FIGURE 2.5 : WINDOW – SUB-NETWORK PROPERTIES / GENERAL ....................................................................................79 FIGURE 2.6 : WINDOW – SUB-NETWORK PROPERTIES / ADDITIONAL INFORMATION .........................................................80 FIGURE 2.7 : WINDOW – SUB-NETWORK PROPERTIES / ALARMS ......................................................................................81 FIGURE 2.8 : WINDOW – OPEN ...........................................................................................................................................82

FIGURE 2.9 : WINDOW – CREATE A NETWORK ELEMENT (1)..............................................................................................83 FIGURE 2.10 : WINDOW – CREATE NE / SECONDARY IP ADDRESS).................................................................................84 FIGURE 2.11 : WINDOW – CREATE A NETWORK ELEMENT (2) ...........................................................................................84 FIGURE 2.12 : WINDOW – CREATE A NETWORK ELEMENT (3) ...........................................................................................85 FIGURE 2.13 : WINDOW – CREATE A NETWORK ELEMENT (4) ...........................................................................................86 FIGURE 2.14 : WINDOW – CREATE A NETWORK ELEMENT (5) ...........................................................................................87 FIGURE 2.15 : WINDOW – CREATE A NETWORK ELEMENT (6) ...........................................................................................88 FIGURE 2.16 : WINDOW NETWORK ELEMENT PROPERTIES ...............................................................................................90 FIGURE 2.17 : WINDOW NETWORK ELEMENT PROPERTIES / ALARMS...............................................................................91

FIGURE 2.18 : WINDOW NETWORK ELEMENT PROPERTIES ...............................................................................................92 FIGURE 2.19 : WINDOW RENAME NE M1400 NAME (1) ....................................................................................................92 FIGURE 2.20 : WINDOW RENAME NE M1400 NAME (2) ....................................................................................................93 FIGURE 2.21 : WINDOW RENAME NE M1400 NAME (3) ....................................................................................................93 FIGURE 2.22 : WINDOW RENAME NE M1400 NAME (4) ....................................................................................................93 FIGURE 2.23 : WINDOW RENAME NE M1400 NAME (5) ....................................................................................................93 FIGURE 2.24 : WINDOW RENAME NE M1400 NAME (6) ....................................................................................................94


10/205

FIGURE 2.41 : WINDOW GENERAL PARAMETERS REAPPLICATIONRESULTS..................................................................105 FIGURE 2.42 : WINDOW GENERAL PARAMETERS REAPPLICATIONRESULTS /DETAILS ...................................................106 FIGURE 2.43 : WINDOW AUDIT / CAPACITY PARAMETERS ALIGNMENT...........................................................................106 FIGURE 2.44 : WINDOW GENERAL CAPABILITY PARAMETERS ALIGNMENT RESULTS ......................................................107

FIGURE 2.45 : WINDOW AUDIT / INVENTORY ALIGNMENT ...............................................................................................108 FIGURE 2.46 : WINDOW INVENTORY ALIGNMENT RESULTS .............................................................................................108 FIGURE 2.47 : WINDOW SAGEM-LINK EQUIPMENT VIEW .............................................................................................110 FIGURE 2.48 : WINDOW SAGEM-LINK LIGHT EQUIPMENT VIEW.................................................................................110 FIGURE 2.49 : WINDOW SLF-A EQUIPMENT VIEW...........................................................................................................110 FIGURE 2.50 : WINDOW NETWORK ELEMENT PROPERTIES / FMX INVENTORY ..............................................................111 FIGURE 2.51 : EXAMPLE OF SNMP VIEW WINDOW .........................................................................................................112 FIGURE 2.52 : WINDOW NETWORK ELEMENT BACKUP RESULTS ....................................................................................112 FIGURE 2.53 : WINDOW – NETWORK ELEMENT BACKUP FAILED RESULT........................................................................113

FIGURE 2.54 : WINDOW – CRITICAL FMX BACKUP MISSING ALARM IN FAULT VIEW .......................................................114 FIGURE 2.55 : WINDOW – WARNING CONFIGURATIONCHANGED ALARM IN FAULT VIEW ..............................................114 FIGURE 2.56 : WINDOW NETWORK ELEMENT RESTORATION ..........................................................................................114 FIGURE 2.57 : WINDOW NETWORK ELEMENT RESTORATION RESULTS ..........................................................................115 FIGURE 2.58 : WINDOW SOFTWARE MANAGEMENT WINDOW ..........................................................................................116 FIGURE 2.59 : WINDOW SOFTWARE MANAGEMENT WINDOW / INVENTORY ....................................................................118 FIGURE 2.60 : WINDOW PERF VIEW ON SLF-V1..............................................................................................................121 FIGURE 2.61 : WINDOW PERF VIEW / NMSPERFTOOL ON SLF-V1 .................................................................................122 FIGURE 2.62 : WINDOW PERF VIEW / NMSPERFTOOL ON SLF-H (ETHERNET COUNTERS) ..........................................123

FIGURE 2.63 : DISCOVER NETWORK ELEMENTS WINDOW ..............................................................................................126 FIGURE 2.64 : WINDOW – DISCOVER NETWORK ELEMENTS /SEEDS...............................................................................126 FIGURE 2.65 : WINDOW – DISCOVER NETWORK ELEMENTS /COMMUNITIES...................................................................127 FIGURE 2.66 : WINDOW – DISCOVER NETWORK ELEMENTS /DISCOVERING ...................................................................127 FIGURE 2.67 : WINDOW – DISCOVER NETWORK ELEMENTS /STATUS .............................................................................128 FIGURE 2.68 : WINDOW – TOPOLOGY VIEW / TREE............................................................................................................128 FIGURE 2.69 : WINDOW – TOPOLOGY VIEW / SEARCH NE ..............................................................................................129 FIGURE 3.1 : NML VIEW : SEARCH AREA (1) ...................................................................................................................130 FIGURE 3.2 : NML VIEW : DETAILS AREA (2) ....................................................................................................................131

FIGURE 3.3 : NML VIEW / MAIN FILTER / TRAILS / FILTER ...............................................................................................132 FIGURE 3.4 : NML VIEW / MAIN FILTER / TRAILS / FILTER / LIST CONFIGURATION .........................................................133 FIGURE 4.1 : WINDOW TOPOLOGY VIEW / FAULT VIEW ...................................................................................................136 FIGURE 4.2 : WINDOW TOPOLOGY VIEW / FAULT VIEW / POP-UP MENU .........................................................................137 FIGURE 4.3 : WINDOW TOPOLOGY VIEW / FAULT VIEW / LIST CONFIGURATION..............................................................139 FIGURE 4.4 : WINDOW ALARMS PROPERTIES / INFORMATION..........................................................................................140 FIGURE 4.5 : WINDOW UNACKNOWLEDGED CLEARED AND NEWALARMS .......................................................................141 FIGURE 4.6 : WINDOW UNACKNOWLEDGED CLEARED AND NEWALARMS .......................................................................142 FIGURE 4.7 : WINDOW TOPOLOGY VIEW /FAULT VIEW / LIST CONFIGURATION / MULTI-CRITERIA FILTERING ...............144

FIGURE 5.1 : WINDOW LOG VIEW / EVENT LOG ...............................................................................................................149 FIGURE 5.2 : WINDOW LOG VIEW / FAULT LOG................................................................................................................149 FIGURE 5.3 : WINDOW LOG VIEW / SERVER LOG.............................................................................................................150 FIGURE 5.4 : WINDOW LOG VIEW / DATABASE LOG.........................................................................................................150 FIGURE 5.5 : WINDOW LOG VIEW / SDH TRAILS LOG .....................................................................................................151 FIGURE 6.1 : WINDOW PREFERENCES / IONOS-NMS....................................................................................................152 FIGURE 6 2 : WINDOW PREFERENCES / TOPOLOGY VIEW 153


11/205

FIGURE 7.15 : WINDOW ADMIN VIEW / PROFILES / DEFINITION .......................................................................................165 FIGURE 7.16 : WINDOW ADMIN VIEW / PROFILES / AUTHORIZATION...............................................................................165 FIGURE 7.17 : WINDOW ADMIN VIEW / GROUPS / DEFINITION........................................................................................167 FIGURE 7.18 : WINDOW ADMIN VIEW / GROUPS / ADDITIONAL INFORMATION.................................................................167

FIGURE 7.19 : WINDOW ADMIN VIEW / USERS / DEFINITION............................................................................................168 FIGURE 7.20 : WINDOW ADMIN VIEW / LDAP USERS / DEFINITION..................................................................................168 FIGURE 7.21 : WINDOW ADMIN VIEW / USERS / PASSWORD...........................................................................................169 FIGURE 7.22 : WINDOW ADMIN VIEW / USERS / ADDITIONAL INFORMATION ...................................................................169 FIGURE 7.23 : WINDOW PROFILE CREATION (1)...............................................................................................................170 FIGURE 7.24 : WINDOW PROFILE CREATION (2)...............................................................................................................170 FIGURE 7.25 : WINDOW PROFILE CREATION (3)...............................................................................................................171 FIGURE 7.26 : WINDOW GROUP CREATION (1) ................................................................................................................171 FIGURE 7.27 : WINDOW GROUP CREATION (2) ................................................................................................................172

FIGURE 7.28 : WINDOW ADMIN VIEW / USERS / DEFINITION............................................................................................172 FIGURE 7.29 : WINDOW USER CREATION (1) ...................................................................................................................173 FIGURE 7.30 : WINDOW USER CREATION (2) ...................................................................................................................173 FIGURE 7.31 : WINDOW USER CREATION (3) ...................................................................................................................173 FIGURE 7.32 : WINDOW ADMIN VIEW / USERS / DEFINITION............................................................................................175 FIGURE 7.33 : WINDOW ADMIN VIEW / USERS / DEFINITION............................................................................................176 FIGURE 8.1 : WINDOW IONOS FEDERATOR.......................................................................................................................177 FIGURE 8.2 : WINDOW IONOS FEDERATOR / ALARMS ......................................................................................................178 FIGURE 8.3 : WINDOW IONOS FEDERATOR / ALARMS / LIST ............................................................................................179

FIGURE 8.4 : WINDOW IONOS FEDERAOR / LIST CONFIGURATION...................................................................................180 FIGURE 8.5 : WINDOW IONOS FEDERATOR / LOGIN ON CLIENT.......................................................................................181


12/205

LIST OF ABBREVIATIONS

AU Administrative Unit

BBE Background Block Error (Bloc erroné résiduel)

CIR Committed Information Rate

EML Equipment Management Layer

EMS Equipment Management System

LCT Local Craft Terminal

ES Errored Second

SES Severely Errored Second

GUI Graphic User InterfaceMCP Management Control Panel

MIB Management Information Base

NE Network Element

PDH Plesiochronous Digital Hierarchy

PIR Peak Information Rate

QOS Quality Of ServiceSIA Signal d’Indication d’Alarme

SNMP Simple Network Management Protocol

TPI Terminal Portable Intelligent

TU Tributary Unit

TUG Tributary Unit Group

UAP Unavailable PeriodUAS Unavailable Second

VC Virtual Container : VC-4, VC-3, VC-12

VNE Virtual Network Element (not managed by NMS)


13/205

TYPOGRAPHICAL CONVENTIONS

Window or screen.Ex : Create a network element name of window or screen displayed

Screen access path from menu bar or pop-up menu.Ex : Topology > New > NE sequence of functions selected from menu bar to display the

following screen

Create a Network Element / General

Network Element (NE), Sub-network, Tab or Function selected in explorer, in a window or in a menu.Ex : General Tab selected in window shown above

Text insertion or selection field.Ex : “Name“ field forming part of window shown above


14/205

GLOSSARY

Virtual network elements (VNE)

A network managed by the network manager is generally connected to another SDH network which iseither the network of another operator or the SDH equipment of another manufacturer managed byanother manager

The Virtual Network Elements (VNE) are used to represent the SDH equipment which is not managedby the manager and to create links between the Network Elements and the Virtual Network Elements.

Alarm

An alarm is a fault detected on a network element (NE) : a severity degree (major, minor or non-alarm)is associated to each alarm. This information is sent to the manager using the SNMP protocol.

Event

An event is an information item sent by the equipment using the SNMP protocol. Though there is noevent severity range, there are several types of events:

Protection event when connection occurs

Startup event when equipment is activated

Session event when user initiates a « login » or a « logout »

Maintenance event when a loop is created or cancelled

Loading event when downloading occurs

Change of attribute event (change of HTTP session)

Performance event

Console/Client/Server/User/”Customer”

Console : refers to the user workstation.

Cli f li i f h C l


15/205

1. SYSTEM INSTALLATION AND MANAGEMENT

1.1 - GENERAL INFORMATION

1.1.1 - IONOS-NMS

The IONOS-NMS system provides an efficient solution for management of a digital data transmission networkincluding:

- SAGEMCOM SDH equipment : ADR155C, ADR155CPE, ADR155E, ADR63E1, EXT155HA, ADR2500C,ADR2500 EXTRA, ADR622, ADR10000, ADR10000HN, FOT155A, FOT155C

- SAGEMCOM PDH equipments : FMX, Sagem-Link, Sagem-Link 2, Sagem-Link Light, SLA, SLF-v1, SLF-N, SLF-H, SLT, SLF-A

- SAGEMCOM WDM equipments : FSP2000 and FSP3000,

- SAGEMCOM DSLAM equipments : 4400, 4048, 4450 and 4900

- SAGEMCOM TV Num equipment : DTX and DTX2

- SAGEMCOM Data Concentrator : XP3000

IONOS-NMS offers EMS functions for all the SAGEMCOM equipments

Equipment configuration and alarm management

Cf Installation and user guide EMS management 253 153 959-05

IONOS-NMS offers NMS functions for the following SAGEMCOM equipments :ADR155C, ADR155CPE,ADR155E, ADR63E1, EXT155HA, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000HN, ADR10000,FSP2000 and FSP3000

Configuration and management for links, bearers and trails

Alarm management for trails

Management of SDH protections: SNCP, MSP MS-SPRing (for ADR2500C, ADR2500 eXtraand ADR10000HN only)

Management of DWDM protections : SNC optique

Cf Installation and user guide EMS/NMS management 253 153 897-05

IONOS-NMS offers EMS functions for all the SAGEMCOM Data Concentrators

Cf Installation and user guide Metering 253 153 941 05


16/205

SYSTEM INSTALLATION AND MANAGEMENT

1.1.2 - Architecture

1.1.2.1 - General architecture

The general architecture is built on a client-server architecture: the various clients can be installed on severalphysical machines connected to the same server.The interface between the network element (NE equipment) and IONOS-NMS uses the SNMP V1 or SNMP Nprotocol to send the alarm messages and to configure the end-to-end trails (« provisioning »).This interface also uses the HTTP protocol to configure the equipment (NE integrating an on-card HTTPserver).

The management data are stored on the server.

CLIENT Plateform Windows

SGBD

SERVER Plateform Windows or Solaris

run

RMI, TCP

SNMP TFTP HTTP

IONOS-NMSSERVER

TopologyAlarmsSécurity

Performances

IONOS-NMSCLIENT

Generic functions

InternetExplorer

Specific functions toequipment

HTTPPROXY

HTTP

TFTP CLIENT

TFTP SERVER


17/205


1.1.2.2 - Software architecture

IONOS-NMS is built on software modules implementing independent functional blocks developed in JAVA:each block only processes a function subset of the complete software.

IONOS-NMS is based on the LUMOS software environment which supplies: an SNMP interface.

base services on which the main functions of the network elements manager are based(alarms, logs, etc.)

a Client application (MCP) based on use of Java Beans and providing the graphic interfaceelements (topology, etc.)

The main application, developed by SAGEMCOM, integrates the network level functions.

The access to HTML pages for equipment of type ADR is done via a HTTP Proxy installed on the IONOS-NMS Server.

IONOS NMS comprises the following modules:

The Client Application , which contains the functions for data presentation to the operator(commonly called the client terminal).

The Server Application which implements the core functions.

The IONOS-NMS platform contains a Network element manager and a Network manager.

Figure 1.2 : IONOS-NMS software platform

1.1.3 - Workstations

The Client Applications are run on a PC whereas the Server Application is run either on a PC or on a UNIXplatform. For small networks, the Client Application can be run on the same PC platform as the server, instand-alone mode.The hardware platform thus remains flexible, open-ended and modular in terms of hard disk, RAM and

Network

Manager

Network

Element

Manager

Faults on NE NEconfiguration

Faults oncircuits

Security

Configurationof circuits

NEperformances


18/205


If the action is long (example: activation/deactivation of trail, audit, etc.), a waiting window isdisplayed. When the action is completed, a window indicates the result or an error message.

1.2 - INSTALLING THE CD WITH WINDOWS

The IONOS-NMS software is supplied on a CD with a manual.Two installations exist :

The installation of a server PC (with client)

The installation of a client PC

1.2.1 - To install the Server + Client Applications

The operating system and the database Oracle have been installed beforehand on the PC where the serverapplication is installed.

1.2.1.1 - To install the Server Application (with Client)

Caution: The installation of the Server Application must be carried out by a personnel qualifiedSagemcom.

Insert CD on the PC used as server. A menu appears automatically. If it does not appear, double-to

click on the file "menu.vbs".

Select the language ("English").

Click on "Installation on a windows PC".

Click on "Ionos-NMS 5.5 installation".

Click on "Full (server with client)"

Follow the installation instructions: choose a directory (Ionos-NMS by default).

Click on [Quit].

A screen of diagnosis is displayed and gives the results of installation.


19/205


Notes: It is possible to modify:- the repertory used by default for backup of the database

(c:\temp\oracle.backup) (see § 1.2.3.3 - )

- the repertory used by default for backup of the databases of equipment (Ionos-NMS\backup\equipment) (see §1.2.3.3 - )

To check that:- IP address of the server seen by the equipment corresponds to IP address of

the PC on which the server is installed (see § 1.2.3.2 - )

To use a HTTP Proxy, see § 1.2.4.3 - .

Click on [Save configuration].

Click on [Quit] to quit the installation.

At the end of the installation procedure, short cuts are available in menu Start :

Ionos-NMS 5.5 Client : Client Application (1).

Ionos-NMS 5.5 Server : Server Application.

TFTP : downloading software.

Ionos-NMS 5.5 (Easy Launcher) : used for Server starting.

Ionos-NMS 5.5 (Federator) : Federator Application (see § 1.4 -)

Copy the short cuts on the computer desktop (Drag and Drop of short cut of menu Start with the keyCTRL pressed)

Note: (1) The Client application is also installed on the same PC. It will be used only for the stand-alone configuration (Server + 1 Client on the same computer).

Modification of license file

In the directory chosen for installation (Ionos-NMS by default), select the Config. folder.

Copy the file LICENSE.DAT, provided with application.

Note: With a license "CORE", only the functions EMS are available.

Modification of database configuration file (for a no standard configuration)

In the directory chosen for installation (Ionos-NMS by default), select the Config folder.

In the folder open the oracle ext assembly xml file


20/205


1.2.1.2 - To install the Client Application

Insert CD on the PC used as Client. A menu appears automatically. If it does not appear, double-toclick on the file "menu.vbs".

Select the language ("English").

Click on "Installation on a windows PC".

Click on "Ionos-NMS 5.5 installation".

Click on "Client".

Follow the installation instructions: choose a directory (Ionos-NMS by default).

Click on [Quit].

A screen of diagnosis is displayed and gives the results of installation. The two parameters concerning theproxy are not used (see § 1.2.4.2 - ).

Figure 1.4 : Window - Ionos Solutions Client – Diagnostic

Note: To use a HTTP Proxy, see § 1.2.4.3 -

Click on [Save configuration]


21/205


1.2.1.3 - To install the Proxy Application

Insert CD on the PC used as Server. A menu appears automatically. If it does not appear, double-toclick on the file "menu.vbs".

Select the language ("English")

Click on "Installation of a server PC (with client)"

Click on "Ionos HTTP Proxy 3.2 installation "

Follow the installation instructions: choose a directory (Ionos HTTP Proxy by default).

Click on "HTTP" to install an HTTP proxy only.

Click on "SLF-v1 F-N" to install a proxy for equipment of type SLF-v1 and SLF-N.

Click on "SLF-H" to install a proxy for equipment of type SLF-H

Click on "Full" to install the two proxy : HTTP proxy and proxy for equipment of type SLF-v1 SLF-N,and SLF-H.

Click on [Quit].

A screen of diagnosis is displayed and gives the results of installation. (see § 1.2.1.1 - )


At the end of the installation procedure, short cut are available in menu Start :

Ionos HTTP Proxy 3.2 : HTTP Proxy Application.

Start Ionos Proxy 3.2 (SLF-H) : to launch the Proxy Application for equipment of type SLF-H

Start Ionos Proxy 3.2 (SLF-v1 SLF-N) : to launch the Proxy Application for equipment oftype SLF-v1 and SLF-N.

Stop Ionos Proxy 3.2 (SLF-v1 SLF-N) : to stop the Proxy Applicationfor equipment of type

SLF-v1 and SLF-N. Copy the short cut on the computer desktop (Drag and Drop of short cut of menu Start with the key

CTRL pressed).

Caution: In the case of the use of HTTP Proxy, to guarantee the access security to the equipment, itis possible to add IP address of the server with a habilitation "Supervisor" in each NE of typeADR155C, ADR155CPE, ADR2500C, ADR2500 EXTRA, ADR622 or ADR63E1 which will bemanaged by IONOS-NMS. For that to use HTTP browser : Menu "Equipment/Management" – toadd IP address of the server in the table "List Managers" while clicking on "Supervisor". To

validate the modification with "Apply".

The HTTP Proxy is available with :

- ADR155C P3.5 and > P3.5- ADR2500C P2.4 and > P2.4

ADR63E1 P2 0 and > P2 0


22/205


1.2.1.4 - To install the NMSperftool Application

The NMSPerftool allows to collect the performance counters on equipment of type Sagem-Link , SLF-v1, SLF-N

and SLF-H.

Insert CD on the PC used as Server.

Open the Folder "Install"

Double-Click on "nmsperftool.exe"

Confirm the installation directory.

Wait several minutes: some windows are displayed, then closed.

A scheduled task is automatically created and the next window is displayed, in case of password.

Give the password.

Figure 1.5 : Window - NMSperftool – Scheduled task

The NMSperftool Application is installed.

1.2.2 - To install LCT application for equipment (FMX, Sagem-Link, FSP2000,

FSP3000, ADR155E)

The LCT application for FMX, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H, FSP2000, FSP3000, ADR155E isused by the Client IONOS-NMS.

Notes: The LCT applications for equipment FOTC and Sagem-Link light are embedded. No particularinstallation is needed


23/205


Click on "TPI-FMX / FSP2000 / FSP3000 / Sagem-Link 2 / SLF-v1 / SLF-N / SLF-H / SLA installation "

Follow the installation instructions

Don't reboot immediately the PC.

A window of diagnosis gives the results of installation.

Click on [Save configuration].


Reboot the PC.

1.2.2.2 - To install LCT application for equipment ADR155E

Insert CD on the PC used as Server.

Open the folder "Install/TPI/ADR155E".


24/205


Note: The LCT of the 155E is using ftp server. Refer to § 1.2.5 - “ The Application Easy Launcherunder Windows ” to know how to launch ftp server under Windows

1.2.3 - Available configurations on Server IONOS-NMS

1.2.3.1 - To configure TFTP server

Launch the TFTP server.

In the Settings, enter:Timeout = 20 s ;Base Directory = C:\Program Files\Ionos-NMS\tftproot (if Ionos-NMS chosen by default)

Note: This configuration is made automatically after the installation of the Server on PC.It is imperative on the Unix server.

1.2.3.2 - To configure IP address of the server seen by the equipment

In the directory chosen for the installation (by default Ionos-NMS), Select the Config folder.

In the folder, open the file Server.xml

Update the field "LocalServerAdress" so that it corresponds to IP address of the PC server seen bythe equipment.

This modification will be effective only after launching of Server IONOS-NMS.

Note: This configuration is made automatically after the installation of the Server on PC.It is imperative on the Unix server.

1.2.3.3 - To configure the backup directories

Backup directory for the Server database

The backup files (backup of database Oracle) will be copied in the directory given in the File.xml file. Thedirectory by default can be modified :

In the directory chosen for installation (Ionos-NMS by default), select the Config folder.

In the folder, open the File.xml file

In this file, update the field "oracle-backup-dat" path.

Note:This modifcation will be effective only after launching of Server IONOS-NMS.The database back-up files are saved in directory "c:/temp/oracle.backup/AAAA/AAAA-MM/JJ" byd f lt


25/205


Caution: If the directory of the NE database has been modified, it is necessary to update theequipmentbackup.xml file to be able to display the NE database list available and to restore it. The

directory by default can be modified :

In the directory chosen for installation (Ionos-NMS by default), select the Config Folder.

In the folder, open the equipmentbackup.xml file

In this file, update the field "backup repository" so as to match to the specified directory that isgenerally the same as the previously modified in the File.xml file.

1.2.3.4 - To configure the HTTP Proxy Function

In the directory chosen for installation of Proxy (Ionos HTTP Proxy), select the Config. folder.

In the folder, open the HttpProxy.cfg file

After the tag [SERVER], insert a line which gives IP address of the server (x.x.x.x)

After the tag [Allow], remove the line "x.x.x.x:x.x.x.x=OBSERVER".

Note: This configuration will be effective only after launching of Proxy Application.

Caution: the Proxy HTTP rejects all the addresses which are not true IP adress. (for example :sagem.com will be rejected and an error message will be logged.)

1.2.3.5 - To configure the function Traps Forward

The function Traps Forward is installed on the Server IONOS-NMS.By default, this function is not activated. The file "forward.xml " must be configured to activate the function.

In the directory chosen for installation (Ionos-NMS by default), select the Config/Forward folder.

In the folder, open the forward.xml file

In this file, update the parameters of manager which will receive the traps : the IP address, the NEtype ((default, ADR2500C, ADR2500EXTRA, ADR10000HN, ADR155C, ADR155CPE,

ADR155C_P2_6, ADR63E1, ADR622, ADR155E, EXT155HAPHYSICAL, FOT155C, FOT155A,FHLINK, FHLINKLIGHT, FHLINK_2, FHLINK-F, FHLINK-A, FHLINK_HC, FSP2000, FSP3000 FMX,TRIPACK4048, TRIPACK4400, TRIPACK4450, TRIPACK4900) and the trap type (default, LogTrap,ThresholdTrap, EquipstatusTrap) for the traps filtering.


26/205


In the repertory chosen for the installation (by default Ionos-NMS), Select the Config/Perf folder.

In this folder, Open the Config.xml file.

Update the following parameters:

- the deadline between two collections for the counters 15mn - > by default 180min- the deadline between two collections for the counters 24h - > by default 1320 min- the deadline between two collections for the periods of unavailabilities associated with thecollection of the counters 15mn - > by default 600min- the deadline between two collections for the periods of unavailabilities associated with thecollection of the counters 24h - > by default 1320min- the deadline between two attempts in the event of failure with the first reading - > 15min- the maximum number of points collected on 15min - > by defect 15000- the maximum number of points collected on 24h - > by defect 18000

- the maximum number of the log for the points of collection 15mn - > by defect 10000- the maximum number of remaining lines after automatic export for the log associated with thepoints with collection 15mn - > by defect 4000- the maximum number of the log for the points of collection 24h - > by defect 10000- the maximum number of remaining lines after automatic export for the log associated with thepoints with collection 24h - > by defect 4000- the maximum number of the log for the periods of unavailability - > per defect 10000- the maximum number of remaining lines after automatic export for the log associated with theperiods with unavailability - > by defect 4000

"R t P i d" t "j l I t " l "15"/


27/205


Caution: The taking into account of the file modification will be effective only after launching of ServerIONOS-NMS.

1.2.3.7 - To authorize the data entry of the accents and the special characters in the"Name" of the equipment

In the repertory chosen for the installation (by default Ionos-NMS), select the Config folder.

In this folder, open the file server-advanced.xml

Replace the line:

by

Note: By default, the data entry of the accents and characters special in the "Name" of theequipment are not authorized.If the data entry of the accents and the special characters is authorized, the "Name" is not updated inthe equipment and control on this parameter (General tab) is not made in the Audit of NE(see § 2.4.8 -).


1.2.3.8 - To inhibit control on the name of cross-connections in the audit of the equipment




28/205


1.2.3.9 - To configure the time interval between IONOS-NMS and equipment


In this folder, open the file lfserver_ext_parameters.xml

Modify the line (by default 60 seconds) :

Note: When IONOS-NMS starts, The time set is done for all the NEs.Then, the time set of a NE is done if the time interval between the date and time of NE and the dateand time of IONOS exceeds the defined value.

Caution: The taking into account of the file modification will be effective only after launching of Server

IONOS-NMS.

1.2.3.10 - To configure the performance parameters used by equipment

The parameters used by equipment for performance collect ( available for ADR155 ≥ P4.1 rev AF andADR2500 EXTRA ≥ P2.1) can be modify in a file xml.


In this folder, open the file server.xml

Modify eventually the the following lines :

The equipment will send threshold performance trap if it is set to "true"

Make it possible to synchronize the performances counter on NE time modulo 15 minutes

Note: After the modification of this file and restart of server, launch an audit on each NE of typeADR155 ≥ P4.1 rev AF or ADR2500 EXTRA ≥ P2.1 and realign the general parameters.


1.2.3.11 - To configure the IONOS-NMS server name

In the repertory chosen for the installation (by default Ionos-NMS), select the Config folder. In this folder, open the file server.xml

Modify the the following line :

Note If l i gi f th NMSN m ( l b d f lt) th m f IONOS NMS ill b



29/205


[email protected]

Give the address of destination (for example [email protected])

[email protected]

Repeat several times this sequence (one sequence by address of destination)

It is possible to choose the format of the mail : “short” or “complete”With the “short” format, you get only a summary of all alarms

Give if you want a subject

NMSAlarms

If this item is present, you will get this text in the header of your message in your mail box. If

this item is not present, you will get a text with the severity of the alarm in the header of your

message in your mail box.

Give the address and the port of mail server

10.142.3.103

25

The taking into account of the file modification will be effective only after launching of Server IONOS-NMS..

Caution: It's not possible to activate "critical alarm sending mail" and "report sending mail"at the same time.

1.2.3.13 - To configure the timers used for the send of mail

The timers are used for the send of mail (see § 4.2.10 -). A mail is sended after X minutes for an alarm change( raised of alarm indeterminate/ warning/ minor/ major/ critical/ inaccessible, cleared, acknowledged,unacknowledged)



30/205


In the repertory chosen for the installation (by default Ionos-NMS), select the Config/mail folder.

In this folder, open the file criticAlarmConfig.xmlTo enable critical alarm mail for “system” alarm, change:

false

by

true

Save and close the file criticAlarmConfig.xml

The taking into account of the file modification will be effective only after launching of Server IONOS-NMS.


1.2.3.15 - To configure the send of mail on a “system” alarm

This procedure is used to configure the send of mail on critical alarm appartion (see § 4.2.11 -To activate the

send of mails on critical alarm).First step : do the described actions of § 1.2.3.12 - To configure the send of mail on alarm changeSecond step :


In this folder, open the file criticAlarmConfig.xml To enable critical alarm mail for “system” alarm, change:

false

by

true


The taking into account of the file modification will be effective only after launching of Server IONOS-

NMS.


1 2 3 16 - To configure the send of mail on a specific event type



31/205


Caution The event type name in criticAlarmConfig.xml must be strickly identical to the one seen in thecurrent alarm window (or in the fault log)


The taking into account of the file modification will be effective only after launching of Server IONOS-NMS.


1.2.3.17 - To send a mail in relation to one sub-network, NE type and NE name

This procedure is used to configure the send of mail (in short mail format only) on critical alarm in relation to

one sub-network (recursively), NE type and NE name.

First step: do the described actions of § 1.2.3.12 - To configure the send of mail on alarm change

Second step:


In this folder, open the file emailParameters.xml

To enable the critical alarm mails sending for a “sub-network”, a “NE type” or a “NE name”, add or modify:

[email protected]

[email protected]

[email protected]

In this example, a mail will be sent on critical alarm to the [email protected] receiver for all NetworkElement type ‘SLF-H’ belonging to the ‘Region Paris’ sub-network (and each sub-network included into thissub-network).Also, a mail will be sent on critical alarm to the [email protected] receiver for all Network Element type‘SLF-N’



32/205


Caution (2): The taking into account of the file modification will be effective only after launching of ServerIONOS-NMS.

Note: If a Network Element is moved from one sub-network to another, it is not mandatory to restart theIONOS-NMS server in order to get the mail to be send to the right receiver.

1.2.3.18 - To configure the format of the sent mail

This procedure is used to configure the format of the sent mail (the length of the message) in short mode oncritical alarm. (see § 4.2.11 - To activate the send of mails on critical alarm)


In this folder, open the file criticAlarmConfig.xml

Modify if necessary these labels.

Equipment: $EQUIPEMENT - Location: $LOCATION - Event type: $EVENT_TYPE - Begindate: $BEGIN_DATE - End date: $END_DATE (by default)

You can modify or remove the labels. (e.g. Equipment to Eqpt, or delete the word ‘Equipment’)You can remove the label and its variableIf the variable exits, don’t modify its value (e.g. $EVENT is not correct, must be $EVENT_TYPE)


Example: Eqpt: $EQUIPEMENT - $LOCATION - Evt: $EVENT_TYPE - Begin date: $BEGIN_DATE

Caution: The taking into account of the file modification will be effective only after launching of Server IONOS-

NMS.1.2.3.19 - To configure a timer for the send of mails

This timer is used for the send of mail on critical alarm (see § 1.2.3.12, refer to the main document: Ionos-NMS Installation and User Guide N 253 153 959-04 or 253 153 962-04 ).A mail is sent after X seconds for an alarm change, if during this length of time a clear of this alarm was sent,the sending of e-mail is cancelled


In this folder, open the file criticAlarmConfig.xml Modify if necessary the value of this timer (in seconds), 0 is the value by default.

30

Caution: The taking into account of the file modification will be effective only after launching of Server IONOS-



33/205


1.2.3.21 - To allow the duplication of IP address

This procedure is used to allow the duplication of IP address.



Modify if necessary the following line :

by :

Caution: The taking into account of the file modification will be effective only after launching of ServerIONOS-NMS.The duplication of IP address is forbidden by defaultIn case of duplication, the following alarm is generated for each equipment: “Duplicate address IP”

1.2.3.22 - To configure the duration of the inactivity period and the number of attemptsauthorised before locking a user

By default, the lock of user after a period of inactivity is not activated.

By default, the lock of user is performed after 5 wrong attempts

In the repertory chosen for the installation (by default IONOS-NMS), select the Config folder.

In this folder, open the file lfserver_ext_advanced.xml

Replace the lines:

By:

Notes: - "MaxUserInactivityPeriod" stands for the number of full days of inactivity before a user isbeing locked.

- "maxLoginAttempts" stands for the number of attempts authorised before a user is being locked.

User with admin profile and default users can't be locked



34/205

Save and open the file lfserver_ext_parameters.xml

Modify the following lines :

- ->

by :

Once the TMF814 northbound interface has been set up, two external applications are required tolaunch the Ionos NMS Server:

- Corba name server- Corba notification service

Caution: Once the TMF814 northbound interface has been set up, it will be no longer possible to launchthe NMS Server if Name server and Notifications server have not been launched will previously.

In the repertory chosen for the installation (by default Ionos-NMS), select the Bin folder.

In this folder, execute the following scripts:- start_TransientNameServer.bat (PC) or ./start_TransientNameServer.sh (solaris) (starts the

name server)- start_NotificationService.bat (PC) or ./start_NotificationService.sh (solaris ) (starts thenotification service)

IONOS-NMS server can be restarted.

Note: If you want to step back, you just have to replace the two modified files in the config directory bytheir backup ones.

1.2.3.24 - To configure the scheduled task for Standby trail



35/205

PPI-LOS alarms will not be inverted

PPI-AIS alarms will be inverted

PPI-AIS alarms will not be inverted

Adjust the variable StandbyLimitDelay which unit is hour (default value is 720 equals 30 days)

give the delay for an alarm to be present before to be inverted

Adjust the variable StandbyTaskTime for the starting time of the scheduled task

If you don’t want this task to be run, then you should configure the server_advanced.xml file according

:

Restart the IONOS-NMS server

Note : If you want log informations about this function in the server.log file or for manual actions aboutStandby trail from the NML View, modify

In the repertory chosen for the installation (by default Ionos-NMS), select the Config folder. In this folder, open the file ems_trace.properties

Uncomment line “log4j.category.com.sagem.ionos.nms.server.fault.priv.ext.standby=DEBUG” to getdebug informations on the Standby trail activities. The debug infos are saved in file Ionos-NMS\log\app\server.log

Idem for :”log4j.category.com.sagem.ionos.nms.server.nml.priv.sec.SecNmlServiceImpl=DEBUG” and“log4j.category.com.sagem.ionos.nms.server.nml.priv.impl.NmlServiceLocal=DEBUG” about manualactivation

Nota: this feature is designed for debug purposes only.


1.2.3.25 - To configure the Ldap connection

This procedure is used to activate the LDAP connection:


In this folder, save and open the file server.xml

Modify the following lines :



36/205


1.2.3.26 - To configure SSH protocol

This procedure is used to configure SSH server to replace FTP for BDD transferts with Backup 1+1 ofIONOS-NMS servers and TFTP for equipment software upgrade ( for transfert between IONOS-NMS Clientand IONOS-NMS server)

In the directory chosen for the installation (by default Ionos-NMS), select the Config folder.


Modify the following line

is replaced by :

Save and close the file server-advanced.xml

On UNIX server :

In the directory chosen for installation (Ionos-NMS by default), select the bin folder.

Execute sftp_Install.sh (in order to create two users : "download" and "backup")

PassWord for users "download" and "backup" is "$agem001"

The default values can be changed (users and password)

The last input is the path for the directory chosen for the installation (by default /tools/Ionos-NMS)

On Windows server :

In the directory chosen for installation (Ionos-NMS by default), select the bin. folder.This command file installs the CopSSH application and sets CopSSH installation folder and IONOS-NMS.It creates two users : "download" and "backup".

Execute install_sftp.cmd (in order to create two users : "download" and "backup"

PassWord for users "download" and "backup" is "$agem001" The default values can be changed (users and password)

Add environnement variable $CoppSHHInstall-Directoriy\bin in the system environnement variable :

PATH



37/205

The CopSSH server is launched as a windows' service.

Note : If the default values of SFTP username and SFTP password of Software Upgrade are changed,they must be changed in the server-advanced.xml file.

In the directory chosen for the installation (by default Ionos-NMS), select the Config folder.


open the file the server-advanced.xml file

Modify the following line

Note : If the default

Documents

Ionos Nms p5 Ems User Guide 253153962-05