Ionos Nms p5 Ems User Guide 253153962-05

IONOS-NMS P5
EMS Management
Installation and User Guide
253 153 962-05
May 2011 Issue 05
LIST OF CHANGES
(A new edition replaces all previous versions)
Date
Change description
Page
253 153 962-05
October 2008
Creation of original user guide for

version P5.3
All pages
April 2009
Update of user guide for version P5.4
All pages
May 2011
Update of user guide for version P5.5
All pages
3 000 322 859 000 03

253 153 962-05
3 000 322 859 000 04
253 153 962-05
3 000 322 859 000 05
IONOS-NMS P5 EMS Installation and User Guide 253 153 962-05

Page 2/205
SAGEMCOM document. Reproduction and disclosure prohibited
WARNING
SAGEMCOM follows all the technical evolutions assiduously and continuously seeks the improvement of its
products 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 of
SAGEMCOM.
The desire of SAGEMCOM is to operate systems observing the environment and consequently it has decided
to 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 approved
national organisation to improve packaging recovery and recycling infrastructures.
To facilitate recycling, please respect the sorting rules set up locally for this kind of
waste
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 product
belongs 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.).
In this way you can participate in the re-use and upgrading of Electrical and Electronic
Equipment Waste, which can have an effect on the environment and human health.

Page 3/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 W INDOWS .....................................................................................................................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
1.2.3.17 - To send a mail in relation to one sub-network, NE type and NE name ..........................................................31
1.2.3.18 - To configure the format of the sent mail..............................................................................................................32
1.2.3.19 - To configure a timer for the send of mails...........................................................................................................32
1.2.3.20 - To configure the feature of trails supervised in real time ..................................................................................32
1.2.3.21 - To allow the duplication of IP address .................................................................................................................33
1.2.3.22 - To configure the duration of the inactivity period and the number of attempts authorised before locking a
user.............................................................................................................................................................................................33
1.2.3.23 - To activate the CORBA interface TMF814..........................................................................................................33
1.2.3.24 - To configure the scheduled task for Standby trail..............................................................................................34
1.2.3.25 - To configure the Ldap connection ........................................................................................................................35
1.2.3.26 - To configure SSH protocol ....................................................................................................................................36
1.2.3.27 - To configure the alarm multi-criteria filtering.......................................................................................................37
1.2.3.28 - To manage the inaccessibility status of the FOT155A by a trap......................................................................38
1.2.3.29 - To configure parameters for the ADR10000.......................................................................................................38
1.2.3.30 - To configure ssh protocol with EMS-ADR (ADR10000)....................................................................................39
1.2.3.31 - ADR10000 includes STM or data cards with electrical interfaces ...................................................................40
1.2.3.32 - To configure the number of Client sessions to the server.................................................................................40
1.2.3.33 - To configure the number of Client sessions per PC Client...............................................................................41
Page 4/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 - To restart a SUN station with Solaris.......................................................................................................58
1.3.12 - To restart the Oracle database and the IONOS-NMS server with Solaris .........................................58
1.4 - TO INSTALL THE IONOS FEDERATOR ......................................................................................................................58
1.4.1 - To install the Client Application of IONOS-NMS ......................................................................................58
1.4.2 - To modify the configuration file...................................................................................................................58
1.4.3 - To start the Ionos Federator........................................................................................................................59
1.4.4 - To close the Ionos Federator ......................................................................................................................60
1.5 - DATABASE MANAGEMENT .......................................................................................................................................60
1.5.1 - To backup the database ..............................................................................................................................60
1.5.1.1 - Backup on line from the client application .............................................................................................................60
1.5.1.2 - Backup on line from a script with Solaris...............................................................................................................61
1.5.1.3 - To configure a Periodic backup off line with Solaris......................................................................................61
1.5.1.4 - Copy of backup directories on magnetic tape with Solaris ................................................................................61
1.5.2 - To restore the database...............................................................................................................................62

1.5.2.1 - To restore of a backup with Windows ...................................................................................................................62
1.5.2.2 - List of available backup with Solaris ......................................................................................................................62
1.5.2.3 - Restore of a backup with Solaris ............................................................................................................................62
Page 5/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
2.4.13 - To display and modify the SNMP parameters......................................................................................111
2.4.14 - To Back up the database of a network element...................................................................................112
2.4.15 - To restore the database of a network element.....................................................................................114
2.4.16 - To restore the database of ADR10000..................................................................................................115
2.4.17 - To update the software on a network element .....................................................................................116
2.4.18 - To Export the configuration of a network element ...............................................................................120
2.4.19 - To visualize the counters of performance for SLF-v1, Sagem-Link, SLF-N and SLF-H equipment
...................................................................................................................................................................................121
2.4.19.1 - To Visualize the graphs of performance collect ...............................................................................................121
2.4.19.2 - To export the collects of performance ...............................................................................................................123
2.4.20 - EMS API Integration.................................................................................................................................123

2.4.21 - To discover NE from Network (IP discovery) .......................................................................................126
2.4.22 - To seek an equipment using its name or of its address IP.................................................................129
3. NML VIEW ...................................................................................................................................................................130
Page 6/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
7.2.14 - To unlock a user .......................................................................................................................................175
8. IONOS SERVERS FEDERATOR ............................................................................................................................177
8.1 - INTRODUCTION ......................................................................................................................................................177
8.2 - DESCRIPTION OF IONOS SERVERS FEDERATOR ..................................................................................................177
8.2.1 - The map of Federator.................................................................................................................................177
8.2.2 - To visualize the alarms of a server ..........................................................................................................178
8.2.3 - To filter current alarms of a server by criteria .........................................................................................179
8.2.4 - To open a IONOS-NMS Client on a server.............................................................................................181
8.2.5 - To open a IONOS-NMS Client on a server with another user .............................................................181
8.2.6 - To force the connection of a server not connected................................................................................182
8.2.7 - To force the refresh of the map ................................................................................................................182
8.2.8 - To start a server ..........................................................................................................................................182
8.2.9 - To stop a server ..........................................................................................................................................182
8.2.10 - To backup the database of a server ......................................................................................................182
Page 7/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

Page 8/205
LIST OF FIGURES
FIGURE 1.1 : GENERAL ARCHITECTURE OF IONOS-NMS.................................................................................................16
FIGURE 1.2 : IONOS-NMS SOFTWARE PLATFORM ...........................................................................................................17
FIGURE 1.3 : W INDOW - IONOS SOLUTIONS SERVER DIAGNOSTIC.................................................................................18
FIGURE 1.4 : W INDOW - IONOS SOLUTIONS CLIENT DIAGNOSTIC ..................................................................................20
FIGURE 1.5 : W INDOW - NMSPERFTOOL SCHEDULED TASK...........................................................................................22
FIGURE 1.6 : EASY LAUNCHER (1).......................................................................................................................................50
FIGURE 1.9 : W INDOW - START IONOS-NMS SERVER .......................................................................................................51
FIGURE 1.10 : DOS COMMANDS WINDOW ..........................................................................................................................52
FIGURE 1.11 : W INDOW - CONNECT TO WHICH NAME SERVER .........................................................................................52
FIGURE 1.12 : LOGIN W INDOW ...........................................................................................................................................52
FIGURE 1.13 : W INDOW HTTP PROXY APPLICATION .....................................................................................................54
FIGURE 1.14 : W INDOW SLF-V1 SLF-N PROXY APPLICATION .........................................................................................55
FIGURE 1.15 : W INDOW SLF-H PROXY APPLICATION ....................................................................................................55
FIGURE 1.16 : FORCE BACKUP W INDOW ............................................................................................................................60
FIGURE 1.17 : BACKUP /DATABASE W INDOW .....................................................................................................................61
FIGURE 2.1 : TOPOLOGY MAIN VIEW ..................................................................................................................................75
FIGURE 2.2 : W INDOW CREATE SUB-NETWORK (1).........................................................................................................77
FIGURE 2.5 : W INDOW SUB-NETWORK PROPERTIES / GENERAL ....................................................................................79
FIGURE 2.6 : W INDOW SUB-NETWORK PROPERTIES / ADDITIONAL INFORMATION .........................................................80
FIGURE 2.7 : W INDOW SUB-NETWORK PROPERTIES / ALARMS ......................................................................................81
FIGURE 2.8 : W INDOW OPEN ...........................................................................................................................................82
FIGURE 2.9 : W INDOW CREATE A NETWORK ELEMENT (1)..............................................................................................83
FIGURE 2.10 : W INDOW CREATE NE / SECONDARY IP ADDRESS).................................................................................84
FIGURE 2.11 : W INDOW CREATE A NETWORK ELEMENT (2) ...........................................................................................84
FIGURE 2.16 : W INDOW NETWORK ELEMENT PROPERTIES ...............................................................................................90
FIGURE 2.17 : W INDOW NETWORK ELEMENT PROPERTIES / ALARMS ...............................................................................91
FIGURE 2.18 : W INDOW NETWORK ELEMENT PROPERTIES ...............................................................................................92
FIGURE 2.19 : W INDOW RENAME NE M1400 NAME (1) ....................................................................................................92
FIGURE 2.26 : W INDOW AUDIT RESULTS / GENERAL .........................................................................................................97
FIGURE 2.27 : W INDOW AUDIT RESULTS / INVENTORY / CARDS .......................................................................................97
FIGURE 2.28 : W INDOW AUDIT RESULTS / INVENTORY / MSPS ........................................................................................98
FIGURE 2.29 : W INDOW AUDIT RESULTS / CROSS-CONNECTIONS ....................................................................................98
FIGURE 2.30 : W INDOW AUDIT RESULTS / BRIDGING POINTS ............................................................................................99
FIGURE 2.31 : W INDOW AUDIT RESULTS / VCGROUPS .....................................................................................................99
FIGURE 2.32 : W INDOW AUDIT RESULTS / MONITORING .................................................................................................100
FIGURE 2.33 : W INDOW AUDIT RESULTS / ETH/VCG PORTS .........................................................................................100
FIGURE 2.34 : W INDOW AUDIT RESULTS / MEPIDS ........................................................................................................101
FIGURE 2.35 : W INDOW AUDIT RESULTS / CONTINUITY-CHECK PROBES ........................................................................101
FIGURE 2.36 : W INDOW AUDIT RESULTS / SDH PORTS ..................................................................................................102
FIGURE 2.37 : W INDOW AUDIT RESULTS / MS-SPRING ................................................................................................102
FIGURE 2.38 : W INDOW AUDIT RESULTS / MS-SPRING / DETAIL ...................................................................................103
FIGURE 2.39 : W INDOW AUDIT RESULTS / FMX INVENTORY ...........................................................................................104
FIGURE 2.40 : W INDOW AUDIT / GENERAL REAPPLICATION ...........................................................................................105
Page 9/205
FIGURE 2.41 : W INDOW GENERAL PARAMETERS REAPPLICATION RESULTS..................................................................105

FIGURE 2.42 : W INDOW GENERAL PARAMETERS REAPPLICATION RESULTS/DETAILS ...................................................106
FIGURE 2.43 : W INDOW AUDIT / CAPACITY PARAMETERS ALIGNMENT ...........................................................................106
FIGURE 2.44 : W INDOW GENERAL CAPABILITY PARAMETERS ALIGNMENT RESULTS ......................................................107
FIGURE 2.45 : W INDOW AUDIT / INVENTORY ALIGNMENT ...............................................................................................108
FIGURE 2.46 : W INDOW INVENTORY ALIGNMENT RESULTS .............................................................................................108
FIGURE 2.47 : W INDOW SAGEM-LINK EQUIPMENT VIEW .............................................................................................110
FIGURE 2.48 : W INDOW SAGEM-LINK LIGHT EQUIPMENT VIEW .................................................................................110
FIGURE 2.49 : W INDOW SLF-A EQUIPMENT VIEW ...........................................................................................................110
FIGURE 2.50 : W INDOW NETWORK ELEMENT PROPERTIES / FMX INVENTORY ..............................................................111
FIGURE 2.51 : EXAMPLE OF SNMP VIEW W INDOW .........................................................................................................112
FIGURE 2.52 : W INDOW NETWORK ELEMENT BACKUP RESULTS ....................................................................................112
FIGURE 2.53 : W INDOW NETWORK ELEMENT BACKUP FAILED RESULT........................................................................113
FIGURE 2.54 : W INDOW CRITICAL FMX BACKUP MISSING ALARM IN FAULT VIEW .......................................................114
FIGURE 2.55 : W INDOW W ARNING CONFIGURATION CHANGED ALARM IN FAULT VIEW ..............................................114
FIGURE 2.56 : W INDOW NETWORK ELEMENT RESTORATION ..........................................................................................114
FIGURE 2.57 : W INDOW NETWORK ELEMENT RESTORATION RESULTS ..........................................................................115
FIGURE 2.58 : W INDOW SOFTWARE MANAGEMENT WINDOW ..........................................................................................116
FIGURE 2.59 : W INDOW SOFTWARE MANAGEMENT WINDOW / INVENTORY ....................................................................118
FIGURE 2.60 : W INDOW PERF VIEW ON SLF-V1..............................................................................................................121
FIGURE 2.61 : W INDOW PERF VIEW / NMSPERFTOOL ON SLF-V1.................................................................................122
FIGURE 2.62 : W INDOW PERF VIEW / NMSPERFTOOL ON SLF-H (ETHERNET COUNTERS) ..........................................123
FIGURE 2.63 : DISCOVER NETWORK ELEMENTS W INDOW ..............................................................................................126
FIGURE 2.64 : W INDOW DISCOVER NETWORK ELEMENTS/SEEDS ...............................................................................126
FIGURE 2.65 : W INDOW DISCOVER NETWORK ELEMENTS/COMMUNITIES ...................................................................127
FIGURE 2.66 : W INDOW DISCOVER NETWORK ELEMENTS/DISCOVERING ...................................................................127
FIGURE 2.67 : W INDOW DISCOVER NETWORK ELEMENTS/STATUS .............................................................................128
FIGURE 2.68 : W INDOW TOPOLOGY VIEW/TREE ............................................................................................................128
FIGURE 2.69 : W INDOW 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 : W INDOW TOPOLOGY VIEW / FAULT VIEW ...................................................................................................136
FIGURE 4.2 : W INDOW TOPOLOGY VIEW / FAULT VIEW / POP-UP MENU .........................................................................137
FIGURE 4.3 : W INDOW TOPOLOGY VIEW / FAULT VIEW / LIST CONFIGURATION..............................................................139
FIGURE 4.4 : W INDOW ALARMS PROPERTIES / INFORMATION..........................................................................................140
FIGURE 4.5 : W INDOW UNACKNOWLEDGED CLEARED AND NEW ALARMS .......................................................................141
FIGURE 4.6 : W INDOW UNACKNOWLEDGED CLEARED AND NEW ALARMS .......................................................................142
FIGURE 4.7 : W INDOW TOPOLOGY VIEW /FAULT VIEW / LIST CONFIGURATION / MULTI-CRITERIA FILTERING ...............144
FIGURE 5.1 : W INDOW LOG VIEW / EVENT LOG ...............................................................................................................149
FIGURE 5.2 : W INDOW LOG VIEW / FAULT LOG ................................................................................................................149
FIGURE 5.3 : W INDOW LOG VIEW / SERVER LOG .............................................................................................................150
FIGURE 5.4 : W INDOW LOG VIEW / DATABASE LOG .........................................................................................................150
FIGURE 5.5 : W INDOW LOG VIEW / SDH TRAILS LOG .....................................................................................................151
FIGURE 6.1 : W INDOW PREFERENCES / IONOS-NMS....................................................................................................152
FIGURE 6.2 : W INDOW PREFERENCES / TOPOLOGY VIEW ...............................................................................................153
FIGURE 6.3 : W INDOW PREFERENCES / NES....................................................................................................................154
FIGURE 6.4 : W INDOW PREFERENCES / SOUNDS.............................................................................................................155
FIGURE 7.1 : W INDOW ADMIN VIEW / RESEARCH TREE ...................................................................................................157
FIGURE 7.2 : W INDOW ADMIN VIEW / USERS ...................................................................................................................158
FIGURE 7.3 : W INDOW ADMIN VIEW / GROUPS ................................................................................................................158
FIGURE 7.4 : W INDOW ADMIN VIEW / PROFILES...............................................................................................................159
FIGURE 7.5 : W INDOW PROFILE CREATION (1).................................................................................................................159
FIGURE 7.8 : W INDOW TOPOLOGY VIEW / PROFILE PROVIDER ACCESS..........................................................................161
FIGURE 7.9 : W INDOW GROUP CREATION (1)...................................................................................................................162
FIGURE 7.10 : W INDOW GROUP CREATION (2) ................................................................................................................162
FIGURE 7.11 : W INDOW USER CREATION (1) FIGURE 7.12 : W INDOW LDAP USER CREATION (1) ..............................163
FIGURE 7.13 : W INDOW USER CREATION (2) ...................................................................................................................163
Page 10/205
FIGURE 7.15 : W INDOW ADMIN VIEW / PROFILES / DEFINITION .......................................................................................165

FIGURE 7.16 : W INDOW ADMIN VIEW / PROFILES / AUTHORIZATION ...............................................................................165
FIGURE 7.17 : W INDOW ADMIN VIEW / GROUPS / DEFINITION ........................................................................................167
FIGURE 7.18 : W INDOW ADMIN VIEW / GROUPS / ADDITIONAL INFORMATION.................................................................167
FIGURE 7.19 : W INDOW ADMIN VIEW / USERS / DEFINITION............................................................................................168
FIGURE 7.20 : W INDOW ADMIN VIEW / LDAP USERS / DEFINITION ..................................................................................168
FIGURE 7.21 : W INDOW ADMIN VIEW / USERS / PASSWORD ...........................................................................................169
FIGURE 7.22 : W INDOW ADMIN VIEW / USERS / ADDITIONAL INFORMATION ...................................................................169
FIGURE 7.23 : W INDOW PROFILE CREATION (1)...............................................................................................................170
FIGURE 8.1 : W INDOW IONOS FEDERATOR.......................................................................................................................177
FIGURE 8.2 : W INDOW IONOS FEDERATOR / ALARMS ......................................................................................................178
FIGURE 8.3 : W INDOW IONOS FEDERATOR / ALARMS / LIST ............................................................................................179
FIGURE 8.4 : W INDOW IONOS FEDERAOR / LIST CONFIGURATION ...................................................................................180
FIGURE 8.5 : W INDOW IONOS FEDERATOR / LOGIN ON CLIENT .......................................................................................181

Page 11/205
LIST OF ABBREVIATIONS
AU
Administrative Unit
BBE
Background Block Error (Bloc erron rsiduel)
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 Interface
MCP
Management Control Panel
MIB
Management Information Base
NE
Network Element
PDH
Plesiochronous Digital Hierarchy
PIR
Peak Information Rate
QOS
Quality Of Service
SIA
Signal dIndication dAlarme
SNMP
Simple Network Management Protocol
TPI
Terminal Portable Intelligent
TU
Tributary Unit
TUG
Tributary Unit Group
UAP
Unavailable Period
UAS
Unavailable Second
VC
Virtual Container : VC-4, VC-3, VC-12
VNE
Virtual Network Element (not managed by NMS)

Page 12/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
The modified fields are colored in green.
The fields where the input is not correct are colored in red.
Active button in a window.
Ex : [Apply]
Interactive button in the window shown above

Page 13/205
GLOSSARY
Virtual network elements (VNE)

A network managed by the network manager is generally connected to another SDH network which is
either the network of another operator or the SDH equipment of another manufacturer managed by
another manager
The Virtual Network Elements (VNE) are used to represent the SDH equipment which is not managed
by 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 no
event 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.
Client :
refers to an application software run on the Console.
Server :
refers to the application software run on the main workstation.
User :
run
refers to the person working on the Console on which the Client application software is
Customer :
refers to the company using the service.

Page 14/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 network
including:
- 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, SLFN, 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 eXtra
and 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
IONOS-NMS provides a CORBA interface TMF814.
Different licences are proposed by SAGEMCOM to our customers :
Licence with EMS functions only
Licence with EMS and NMS functions
Licence with EMS and Metering functions

Page 15/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 several
physical machines connected to the same server.
The interface between the network element (NE equipment) and IONOS-NMS uses the SNMP V1 or SNMP N
protocol 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 HTTP
server).
The management data are stored on the server.
Windows
CLIENT Plateform
IONOS-NMS
CLIENT
Generic functions
Internet
Explorer
run
Specific functions to
equipment
TFTP CLIENT
RMI, TCP
SERVER Plateform
HTTP
Windows or Solaris
IONOS-NMS
SERVER
SGBD
Topology
Alarms
Scurity
Performances
HTTP
PROXY
TFTP SERVER
SNMP, TFTP
HTTP
SAGEMCOM Equipment
SNMP
Agent
HTTP
Server
Figure 1.1 : General architecture of IONOS-NMS

Page 16/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 interface
elements (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 IONOSNMS 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.
Network
Manager
Faults on
circuits
Configuration
of circuits
Security
Network
Element
Manager
Faults on NE
NE
configuration
NE
performances
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 UNIX
platform. For small networks, the Client Application can be run on the same PC platform as the server, in
stand-alone mode.
The hardware platform thus remains flexible, open-ended and modular in terms of hard disk, RAM and
computing power in order to grow with the system, which entirely depends on the number of network elements
to be managed.
1.1.4 - Man-Machine Interface (MMI)

The Man-Machine interface of the administration software is similar to the Windows interface.
When the values of a field are limited, they can be selected in a drop-down box .
The current values are displayed in the fields which the user wishes to modify.
The mandatory fields are displayed with a different colour when their input is not supplied.
When an action is performed, there are two working modes:

If the action is short, the window closes during the operation: if an error occurs, a message is
displayed.
Page 17/205

If the action is long (example: activation/deactivation of trail, audit, etc.), a waiting window is
displayed. 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 server
application 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 qualified
Sagemcom.
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.
Figure 1.3 : Window - Ionos Solutions Server Diagnostic

Page 18/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 (IonosNMS\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 key
CTRL pressed)
Note: (1) The Client application is also installed on the same PC. It will be used only for the standalone 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.
In this file, update eventually the IP address of the database server (localhost), the database name
(DBNMS), the username (NMSserver) and the password (nmssmn).
<properties name="OracleJDBCManager">
<property name="database"
value="@(description=(address=(host=localhost)(protocol=tcp)(port=1521))
(connect_data=(sid=DBNMS)))"/>
<property name="username" value="NMSserver"/>
<property name="passwd" value="nmssmn"/>
<property name="drvtype" value="thin"/>
<property name="deadLockErrorCode" value="60"/>
</properties>

Page 19/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-to
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 the
proxy 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]

At the end of the installation procedure, short cuts are available in menu Start :
Ionos-NMS 5.5 (Client) : Client Application.
Ionos-NMS 5.5 (Federator) : Federator Application (see 1.4 -)
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 an installation of the stand-alone configuration (the client is launched on the
PC server) to use menu "Installation of a server PC (with client).

Page 20/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-to
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 of
type 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, it
is possible to add IP address of the server with a habilitation "Supervisor" in each NE of type
ADR155C, ADR155CPE, ADR2500C, ADR2500 EXTRA, ADR622 or ADR63E1 which will be
managed by
IONOS-NMS. For that to use HTTP browser : Menu "Equipment/Management" to
add 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
ADR2500 EXTRA
ADR155CPE
ADR 622

Page 21/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 is
used by the Client IONOS-NMS.
Notes: The LCT applications for equipment FOTC and Sagem-Link light are embedded. No particular
installation is needed
The LCT of the ADR10000HN and of the equipment ADR155c, ADR2500C, ADR2500 EXTRA,
ADR63E1, ADR155CPE are included in the equipment. No particular installation is needed
The LCT of equipment 3@Pack 4400, 3@Pack 4048, 3@Pack 4450 and 3@Pack 4900 are delivered
separately from IONOS-NMS application.
1.2.2.1 - To install LCT application for equipment of type FMX, Sagem-Link, FSP2000,
FSP3000
Insert CD on the PC used as Client. A menu appears automatically. If it does not appear, double-to
Select the language ("English")
Click on "Installation of a client PC"
Click on "Optional TPI installation"
Page 22/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".
Double-click on "python-2-4.1.msi" to install the application "Python 2.4" in folder "C:\Python24".
Unzip "pysnmp.zip" in folder "C:\Python24\lib\site-packages"
Unzip "LCT-PC.zip" in folder "C:" (for example).
Launch "FTP" Application of IONOS.
In folder "LCT\nex", modify the file "Config.py" You must declare your FTP server 's root folder in this
file,
For instance :
ROOT = r'C:\Program Files\IONOS-NMS-4420\tftproot'
And modify if necessary the type of transfer selecting ftp :
TYPE = r'ftp'
In folder LCT\snakelets, launch "serv.py" (or "python serv.py")

Page 23/205

Note: The LCT of the 155E is using ftp server. Refer to 1.2.5 - The Application Easy Launcher
under 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 by
the 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. The
directory by default can be modified :
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" by
default.
Backup directory for the Equipment databases
The backup files (backup of equipment configuration) will be copied in the directory given in the File.xml file.
The directory by default can be modified :
In the folder, open the File.xml file
In this file, update the field "equipement-backup-xxx" path (c:\Program Files\Ionos-NMS\backup\eqpt
by default)
Note: This modification will be effective only after launching of Server IONOS-NMS.
The NE database files are saved in directory "../IONOS-NMS/backup/eqpt/AAAA/AAAA-MM/JJ" by
default.
Page 24/205
Caution: If the directory of the NE database has been modified, it is necessary to update the
equipmentbackup.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 is
generally 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 NE
type ((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.
<manager>
<ipAddress value="x.x.x.x"/>
<hostPort value="162"/>
<community value="public"/>
<neTrap neType="ADR2500C" trapType="default"/>
<neTrap neType="ADR155C" trapType="LogTrap"/>
</manager>
The traps can be forwarded to several managers.
Note: This modification will be effective only after launching of Server IONOS-NMS.
1.2.3.6 - To configure the parameters associated with the collection of performance
The file of configuration used for the collection of the points of performance is installed on the PC used as
Server IONOS-NMS.
Page 25/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 the
collection of the counters 15mn - > by default 600min
- the deadline between two collections for the periods of unavailabilities associated with the
collection 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 the
points with collection 15mn - > by defect 4000
- the maximum number of the log for the points of collection 24h - > by defect 10000
points with collection 24h - > by defect 4000
- the maximum number of the log for the periods of unavailability - > per defect 10000
periods with unavailability - > by defect 4000
<?xml version="1.0" encoding="UTF-8"?>
<config>

<var name="InitDelay" type="java.lang.Integer" value="3"/>

<var name="15mnPeriod" type="java.lang.Integer" value="180"/>

<var name="24hPeriod" type="java.lang.Integer" value="1320"/>

<var name="UAPShortPeriod" type="java.lang.Integer" value="600"/>

<var name="UAPLongPeriod" type="java.lang.Integer" value="1320"/>

<var name="RetryPeriod" type="java.lang.Integer" value="15"/>

<var name="MaxCollectionThreads" type="java.lang.Integer" value="3"/>

<var name="Max15mnCollectionPoints" type="java.lang.Integer" value="15000"/>

<var name="Max24hCollectionPoints" type="java.lang.Integer" value="18000"/>

<var name="15mnLogHighWaterMark" type="java.lang.Integer" value="10000"/>

<var name="15mnLogLowWaterMark" type="java.lang.Integer" value="4000"/>
Page 26/205


<var name="24hLogHighWaterMark" type="java.lang.Integer" value="10000"/>

<var name="24hLogLowWaterMark" type="java.lang.Integer" value="4000"/>

<var name="UAPLogHighWaterMark" type="java.lang.Integer" value="10000"/>

<var name="UAPLogLowWaterMark" type="java.lang.Integer" value="4000"/>

<var name="LogExportFileColumnSeparator" type="java.lang.String" value=" "/>
</config>
Caution: The taking into account of the file modification will be effective only after launching of Server
IONOS-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:
<var name="DescendLongName" type="java.lang.Boolean" value="true"/>
by
<var name="DescendLongName" type="java.lang.Boolean" value="false"/>
Note: By default, the data entry of the accents and characters special in the "Name" of the
equipment are not authorized.
If the data entry of the accents and the special characters is authorized, the "Name" is not updated in
the equipment and control on this parameter (General tab) is not made in the Audit of NE
(see 2.4.8 -).
IONOS-NMS.
1.2.3.8 - To inhibit control on the name of cross-connections in the audit of the equipment
Replace the line:
by
<var name="MisalignOnXCNameDiff" type="java.lang.Boolean" value="true"/>

<var name="MisalignOnXCNameDiff" type="java.lang.Boolean" value="false"/>
Note: By default, control on the name of cross-connections in the audit of NE is done (see 2.4.8 -).
This function of suppression of the control of the name of cross-connections makes it possible to
manage equipment ADR2500C version < P2.4 (P1 or P2), ADR155E P2.1 and ADR10000HN P1.1 to
avoid the misalignment of NEs.
IONOS-NMS.

Page 27/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) :
<property name="DeltaMaximum" type="java.lang.Integer" value="60"/>
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 date
and time of IONOS exceeds the defined value.
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 and
ADR2500 EXTRA P2.1) can be modify in a file xml.
In this folder, open the file server.xml
Modify eventually the the following lines :
<var name="PerfThreshodTrapEnable" type="java.lang.Boolean" value="false"/>
The equipment will send threshold performance trap if it is set to "true"
<var name="PseudoTCMEnable" type="java.lang.Boolean" value="true"/>
Make it possible to synchronize the performances counter on NE time modulo 15 minutes
<var name="ToleranceDate" type="java.lang.Integer" value="30"/>
<var name="Start24hCountTime" type="java.lang.Integer" value="0"/>
Note: After the modification of this file and restart of server, launch an audit on each NE of type
ADR155 P4.1 rev AF or ADR2500 EXTRA P2.1 and realign the general parameters.
IONOS-NMS.
1.2.3.11 - To configure the IONOS-NMS server name
Modify the the following line :
<var name="NMSName" type="java.lang.String" value=""/>
Note: If no value is given for the NMSName (value by default), the name of IONOS-NMS server will be
the name of machine used as server.
IONOS-NMS.
1.2.3.12 - To configure the send of mail on alarm change
This procedure is used to configure the send of mail on alarm change (apparition, clear, acknowledgement,
unacknowledgement) (see 4.2.10 - Alarms management).
In the repertory chosen for the installation (by default Ionos-NMS), select the Config/mail folder.
In this folder, open the file emailParameters.xml
The send of mail is activated if :
<emailSender activate="yes" >
Give if necessary the sender address (for example [email protected])
Page 28/205

<SenderAdress>
<EmailAdress>
[email protected]
</EmailAdress>
</SenderAdress>
Give the address of destination (for example [email protected])
<DestinationsAdresses>
<Receiver mail=short>
<EmailAdress>
[email protected]
</EmailAdress>
</Receiver>
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
<Subject>
NMSAlarms
</Subject>
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
<SmtpServer>
<IpAdress>
10.142.3.103
</IpAdress>
<Port>
25
</Port>
</SmtpServer>
The taking into account of the file modification will be effective only after launching of Server IONOSNMS..
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).
In this folder, open the file timers.xml
Modify if necessary the values of timers.
IONOS-NMS.
1.2.3.14 - To configure the send of mail on critical 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 change
Second step :
Page 29/205

In this folder, open the file criticAlarmConfig.xml
To enable critical alarm mail for system alarm, change:
<systemt>
false
</systemt>
by
<systemt>
true
</systemt>
Save and close the file criticAlarmConfig.xml
The taking into account of the file modification will be effective only after launching of Server IONOSNMS.
at the same time.
1.2.3.15 - To configure the send of mail on a system alarm
Second step :
To enable critical alarm mail for system alarm, change:
<systemt>
false
</systemt>
by
<systemt>
true
</systemt>
at the same time.
1.2.3.16 - To configure the send of mail on a specific event type
Second step :
To add an event type in the list to send a critical alarm mail, change or add:
<Except>
<Event_type>RadioLinkFailure</Event_type>
<Event_type>MODEM1:Modulation</Event_type>
<Event_type>ODU1:TxPower</Event_type>
</Except>
(This is only an example)
Page 30/205

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

at the same time.
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:
<ShortCriticalReceiver Subnetwork="Region Paris" NeType="SLF-H">
<EmailAdress>
[email protected]
</EmailAdress>
</ShortCriticalReceiver>
<ShortCriticalReceiver NeType="SLF-N">
<EmailAdress>
[email protected]
</EmailAdress>
</ShortCriticalReceiver>
<ShortCriticalReceiver NeName="Lyon">
<EmailAdress>
[email protected]
</EmailAdress>
In this example, a mail will be sent on critical alarm to the [email protected] receiver for all Network
Element type SLF-H belonging to the Region Paris sub-network (and each sub-network included into this
sub-network).
Also, a mail will be sent on critical alarm to the [email protected] receiver for all Network Element type
SLF-N.
A mail will be only sent on critical alarm to the [email protected] receiver for the Network Element with
the name Lyon.
Save and close the file emailParameters.xml
Caution (1):
The name of sub-network must be unique.
The name of sub-network must not include some characters like >, <, &, , , etc ...
The tag NeType must be equal to the Equipment type name displayed in the combox box of the
Create a network element window or in the NE properties (Type field).
The tag NeName must be equal to the Network Element name displayed in the field Name of the
NE properties.
Page 31/205

Caution (2): The taking into account of the file modification will be effective only after launching of Server
IONOS-NMS.
Note: If a Network Element is moved from one sub-network to another, it is not mandatory to restart the
IONOS-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 on
critical alarm. (see 4.2.11 - To activate the send of mails on critical alarm)
Modify if necessary these labels.
<object_short> Equipment: $EQUIPEMENT - Location: $LOCATION - Event type: $EVENT_TYPE - Begin
date: $BEGIN_DATE - End date: $END_DATE </object_short> (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 variable
If the variable exits, dont modify its value (e.g. $EVENT is not correct, must be $EVENT_TYPE)
Example:
<object_short> Eqpt: $EQUIPEMENT - $LOCATION - Evt: $EVENT_TYPE - Begin date: $BEGIN_DATE
</object_short>
Caution: The taking into account of the file modification will be effective only after launching of Server IONOSNMS.
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: IonosNMS 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
Modify if necessary the value of this timer (in seconds), 0 is the value by default.
<Timer>30 </ Timer >
Caution: The taking into account of the file modification will be effective only after launching of Server IONOSNMS.
1.2.3.20 - To configure the feature of trails supervised in real time
This procedure is used to modify the number maximum of trails supervised in real time by user (2000 by
default) and the update frequency of the status for the trails supervised in real time.
Modify if necessary, to modify the number maximum of trails, the following line:
<var name="MaxRTS" type="java.lang.Integer" value="2000"/>
Modify if necessary, to update the refresh frequency, the following line (value in ms):
<var name="RTSRefreshRate" type="java.lang.Integer" value="5000"/>
IONOS-NMS.
Page 32/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 :
<var name="AcceptIpDuplicates" type="java.lang.Boolean" value="false"/>
by :
<var name="AcceptIpDuplicates" type="java.lang.Boolean" value="true"/>
IONOS-NMS.
The duplication of IP address is forbidden by default
In 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 attempts
authorised 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:
<properties name="SCFrameworkExtension">
<property name="lumos.scontainer.sec.SessTO" type="Long" value="-1"/>
</properties>
By:
<properties name="SCFrameworkExtension">
<property name="lumos.scontainer.sec.SessTO" type="Long" value="-1"/>
<property name="lumos.scontainer.sec.MaxUserInactivityPeriod" type="Long" value="60"/>
<property name="lumos.scontainer.sec.maxLoginAttempts" type="Integer" value="5"/>
</properties>
Notes: - "MaxUserInactivityPeriod" stands for the number of full days of inactivity before a user is
being 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.
- To unlock a user, refer to 7.2 - > Admin View window.
1.2.3.23 - To activate the CORBA interface TMF814
This procedure is used to activate the CORBA interface TMF814.

Stop IONOS-NMS server
In this folder, save and open the file lfserver_ext_assembly.xml
Modify the following line :

by :
Page 33/205

<jar name="ext/e-stmf814.jar" />
Save and open the file lfserver_ext_parameters.xml
Modify the following lines :
<!- <properties name="TMF814 Northbound">
<property name="lumos.leape.north.tmf.nameServiceUrl"
value="corbaloc::localhost:900/NameService" />
<property name="lumos.leape.north.tmf.lfUrl"
value="rmi://localhost:1099/srleap" />
</properties>
- ->
by :
<properties name="TMF814 Northbound">
<property name="lumos.leape.north.tmf.nameServiceUrl"
value="corbaloc::localhost:900/NameService" />
<property name="lumos.leape.north.tmf.lfUrl"
value="rmi://localhost:1099/srleap" />
</properties>
Once the TMF814 northbound interface has been set up, two external applications are required to
launch 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 launch
the 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 the
notification 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 by
their backup ones.
1.2.3.24 - To configure the scheduled task for Standby trail
This procedure is used to schedule a task for Standby trail

In this folder, open the file server_advanced.xml

<var name="LosEnabled" type="java.lang.Boolean" value="true"/>
<var name="AisEnabled" type="java.lang.Boolean" value="true"/>
<var name="StandbyLimitDelay" type="java.lang.Integer" value="720"/>
<var name="StandbyTaskTime" type="java.lang.String" value="05:00:00"/>
Modify if needed the following line :
<var name="LosEnabled" type="java.lang.Boolean" value="true"/>
PPI-LOS alarms will be inverted
Page 34/205

<var name="LosEnabled" type="java.lang.Boolean" value="false"/>
PPI-LOS alarms will not be inverted
<var name="AisEnabled" type="java.lang.Boolean" value="true"/>
PPI-AIS alarms will be inverted
<var name="AisEnabled" type="java.lang.Boolean" value="false"/>
PPI-AIS alarms will not be inverted
Adjust the variable StandbyLimitDelay which unit is hour (default value is 720 equals 30 days)
<var name="StandbyLimitDelay" type="java.lang.Integer" value="720"/>
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 dont want this task to be run, then you should configure the server_advanced.xml file according
:
<var name="LosEnabled" type="java.lang.Boolean" value="false"/>
<var name="AisEnabled" type="java.lang.Boolean" value="false"/>
Restart the IONOS-NMS server
Note : If you want log informations about this function in the server.log file or for manual actions about
Standby trail from the NML View, modify
In this folder, open the file ems_trace.properties
Uncomment line log4j.category.com.sagem.ionos.nms.server.fault.priv.ext.standby=DEBUG to get
debug informations on the Standby trail activities. The debug infos are saved in file IonosNMS\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 manual
activation
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 :
<var name="URL" type="java.lang.String" value=""/>
<var name="UserLogin" type="java.lang.String" value="admin"/>
<var name="UserPassword" type="java.lang.String" value="secret"/>
<var name="SecurityAuthentication" type="java.lang.String" value="simple"/>
<var name="Domain" type="java.lang.String" value=""/>
<var name="UserBase" type="java.lang.String" value="dc=sagem,dc=com"/-->
- URL: Type the string "ldap:// and set the IP address value with the IP address of the Ldap server and
the TCP port number (ie : ldap://192.168.75.75:389).
- UserLogin: Set this value with the name of a user registered in the Active Directory
- UserPassword: Set this value with the password of the UserLogin
- SecurityAuthentication should not be modified
This UserLogin/password is used to check the ldap connection.
Save and close the file server.xml

Page 35/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 of
IONOS-NMS servers and TFTP for equipment software upgrade ( for transfert between IONOS-NMS Client
and IONOS-NMS server)
In the directory chosen for the installation (by default Ionos-NMS), select the Config folder.
Modify the following line

<var name="SftpEnablead" type="java.lang.Boolean" value="false" />
is replaced by :

<var name="SftpEnablead" type="java.lang.Boolean" value="true" />
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

Page 36/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.
open the file the server-advanced.xml file

<var name="SFTPServerUserName" type="java.lang.String" value="download" />

<var name="SFTPServerPwd" type="java.lang.String" value="$agem001" />
Note : If the default values of SFTP username and SFTP password of Database Backup Secure 1+1
are changed, they must be changed in the server.xml file.
<var name="RemoteSFTPServerUserName" type="java.lang.String" value="backup" />
<var name="RemoteSFTPServerPwd" type="java.lang.String" value="$agem001" />
<var name="SFTPServerDir" type="java.lang.String" value="/tools/$IONOS-NMS" />
1.2.3.27 - To configure the alarm multi-criteria filtering
This procedure is used to give the capability to apply filter with muti-criteria (several filters in the same colum
or between columns with And/Or condition) on alarm/event in the Fault View, Fault Log, NML View and in the
Event Log and to save these filters. See 4.2.9 - To filter current alarms by multi-criteria
Page 37/205

In this folder, open the server.xml file
To configure the filter multi-criteria, replace the line:

<var name="multiFilters" type="java.lang.Boolean" value="false"/>
by

<var name="multiFilters" type="java.lang.Boolean" value="true"/>
Save and close the server.xml file
1.2.3.28 - To manage the inaccessibility status of the FOT155A by a trap
This procedure is used to manage the inaccessibility status (blue icon) of the FOT155A in relation to the trap
of inaccessibility and not by the polling.
To activate the treatment of inaccessibility status by the trap instead of the polling, replace the line
!-- FOT155A polling by trap -->
<var name="FOT155APollingByTrapEnabled" type="java.lang.Boolean" value="false" />
by
!-- FOT155A polling by trap -->
<var name="FOT155APollingByTrapEnabled" type="java.lang.Boolean" value="true" />
1.2.3.29 - To configure parameters for the ADR10000
This procedure is used to manage the ADR10000 R7.2 and R8.1:

In this folder, open the file server_advanced.xml

<var name="CorbaPort" type="java.lang.String" value="5075" />
<var name="CorbaSession" type="java.lang.String" value="11" />
<var name="CorbaVersion" type="java.lang.String" value="3.5" />
<var name="EMSADRVersion" type="java.lang.String" value="8.1" />
<var name="CorbaUser" type="java.lang.String" value="ems" />
<var name="CorbaPassword" type="java.lang.String" value="SaGeM" />
<var name="HostAdress" type="java.lang.String" value="127.0.0.1" />
<var name="OracleEMSADRHostAdress" type="java.lang.String" value="127.0.0.1" />
<var name="OracleEMSADRUser" type="java.lang.String" value="oracle10" />
<var name="OracleEMSADRPassword" type="java.lang.String" value="oracle10" />
<var name="SchemaNameEMSADR" type="java.lang.String" value="" />
<var name="OracleEMSADRFullBackupDir" type="java.lang.String"
value="/sdh_home/oracle10/backupdir/" />

<var name="EMSADRVersion" type="java.lang.String" value="8.1" />
Page 38/205

Type the EMS-ADR version number:
7.2 for ADR10000 / EMS-ADR R7.2
8.1 for ADR10000 / EMS-ADR R8.1
<var name="HostAdress" type="java.lang.String" value="127.0.0.1" />
Type the IP address of the ADR10000 proxy (EMS-ADR).
The next variables only concern the ADR10000 / EMS-ADR R8.1:

<var name="OracleEMSADRHostAdress" type="java.lang.String" value="127.0.0.1" />
Type the IP address of the.Oracle10 zone of the EMS-ADR 8.1
<var name="OracleEMSADRUser" type="java.lang.String" value="oracle10" />
<var name="OracleEMSADRPassword" type="java.lang.String" value="oracle10" />
Enter the login / password of the Oracle10 zone of the EMS-ADR 8.1
<var name="SchemaNameEMSADR" type="java.lang.String" value="" />
Enter the schema name (Oracle DB user) of the EMS-ADR 8.1
In order to know the schema name, from the EMS-ADR zone with EMS user, type the SetupEMS command
and choose the option 1: the field Oracle DB user is the schema name.
Ex:
ems(z2-primepower) ~ > SetupEMS.sh
EMS XDM Oracle Setup Menu
1
2
3
4
5
6
7
Show Current Configuration

Check Oracle DB status
Apply Infrastructure Layer to DB
Insert EMS XDM schema to DB
Remove EMS XDM schema from DB
Empty EMS XDM Database data
Reconfigure EMS XDM Database settings
Select an action (q to quit) [1...7,q] --> 1

Database Settings:
Database Server:
10.66.220.52
Oracle DB user:
z2_primepower is the schema name
Oracle service name: z2_primepower
<var name="OracleEMSADRFullBackupDir" type="java.lang.String"
value="/sdh_home/oracle10/backupdir/" />
Enter the path where the EMS-ADR databases are saved into the Oracle10 zone of the EMS-ADR 8.1
Note: check that the backupdir folder exists or create it if necessary
Save and close the server-advanced.xml file
1.2.3.30 - To configure ssh protocol with EMS-ADR (ADR10000)
Page 39/205

This procedure is used to configure SSH protocol to replace FTP for database transfer with Backup 1+1 of
EMS-ADR
Note : Enter the correct values for the SFTP username and SFTP password according to EMSADR SFTP server configuration.
If necessary, modify the following line into the section

<var name="RemoteSftpEmsLogin" type="java.lang.String" value="root" />

<var name="RemoteSftpEmsPwd" type="java.lang.String" value="SaGeM" />

1.2.3.31 - ADR10000 includes STM or data cards with electrical interfaces
This procedure is used when an ADR10000 includes STM or data cards with electrical interfaces instead of
optical interfaces.
Replace the line
<var name="UseETRAllowed" type="java.lang.Boolean" value="false" />
by
<var name="UseETRAllowed" type="java.lang.Boolean" value="true" />
1.2.3.32 - To configure the number of Client sessions to the server
This procedure is used to configure the number of Client sessions allowed to connect to the IONOS-NMS
Server.
To activate the control number of Client sessions, replace the line

<var name="maxSessionsEnabled" type="java.lang.Boolean" value="false" />
by

<var name="maxSessionsEnabled" type="java.lang.Boolean" value="true" />
To configure the number of Client sessions allowed, modify if necessary the value into the following section
(20 is the value by default).

<var name="maxSessions" type="java.lang.Integer" value="20" />
Then, it is possible to connect up to 20 Client sessions using different user profiles (administrator, operator,
observer)
Page 40/205

Note: (1) When the limitation of maximum Client sessions is reached, a message Maximum
session X exceeded is displayed
(2) It is always possible to open a client session using an administrator profile (whatever the
number of allowed sessions configured in the server-advanced.xml file).
(3) In case of not properly disconnection of Client session, there is a delay allowing a
reconnection after about 5 minutes.
1.2.3.33 - To configure the number of Client sessions per PC Client
This procedure is used to configure the number of Client sessions allowed per PC Client to connect to the
IONOS-NMS Server.
To activate the control number of Client sessions per PC Client, replace the line

<var name="maxPCSessionsEnabled" type="java.lang.Boolean" value="false" />
by

<var name="maxPCSessionsEnabled" type="java.lang.Boolean" value="true" />
To configure the number of Client sessions allowed per PC Client, modify if necessary the value into the
following section (1 is the value by default).

<var name="maxPCSessions" type="java.lang.Integer" value="1" />
Then, it is possible to open only one session Client from the PC Client to the IONOS-NMS Server (whatever
the user profile used, administrator, operator or observer)
Note: (1) When the limitation of maximum PC Client sessions is reached, a message Only X
maxPCSession(s) is allowed on <IP_Address_of_PC_Client> is displayed
(2) In case of not properly disconnection of Client session, there is a delay allowing a
reconnection after about 5 minutes.
1.2.3.34 - To configure the SNMP trap generator
This procedure is used to configure the SNMP trap generator. It generates SNMP traps (alarms and events)
following IONOS-NMS server traps reception sent by the equipments type ADR155C, ADR622 and
ADR2500EXTRA to one or several receivers.
It is possible to apply some filters before the traps sending.
Note : (1) System alarms and NE inaccessibility alarms are not generated.
(2) Clear alarms are generated to the trap receiver.
In the directory chosen for the installation (by default Ionos-NMS), select the Config/forward
folder.
In this folder, open the file generation.xml
<netype>
Page 41/205




</netype>
In the netype section, define the NE type criteria.
For example, to activate the traps sending for a ADR155C, replace (uncomment) the line:

by
<Type value="ADR155C"/>
In the distant section, define the IP address and port number of the traps receivers.
Uncomment and modify the line:
<distant>

</distant>
by
<IpAddress value="10.0.0.1/163"/>
with
IP address of one trap receiver: 10.0.0.1
Associated port number:
163
Note : The maximun number of traps receivers is 4.
In the filter-alarm section, it is possible to define some criterias of alarm trap sending.
If necessary, modify and duplicate these lines:
<filter nename=""/>
Enter the NE long name of one equipment, ex: <filter nename="Dijon"/>
Alarm traps of this equipment will be generated
No tag means there is no filtering on this field.
<filter status=""/>
Enter the level of security of alarm (critical, major, minor, warning), ex <filter status="major"/>
Alarm trap with major status will be generated.
<filter eventtype=""/>
Enter the type of alarm, ex <filter eventtype="los"/>
Alarm trap with a type los will be generated.
<filter location="" match="begin"/>
Enter the location of the alarm (board, port ), ex <filter location="PPI" match="begin"/>
All alarm traps with the string beginning by PPI will be generated.
<filter location="" match="exact"/>
Enter the location of the alarm, ex <filter location="PPI-LTU 5:1" match="exact"/>
Note: In this case, the field must be filled with the exactly string of the alarm location
Alarm trap with exactly the "PPI-LTU 5:1" location will be generated.
<filter nedatebegin="2010-03-01 05:00:00" nedateend="2010-03-31 09:00:00"/>
Enter the range of begin/end dates at which alarm was sent by the NE
Alarm traps between the NE begin date nedatebegin and the NE end date nedateend will be generated.
<filter nmsdatebegin="2010-03-01 05:00:00" nmsdateend="2010-03-31 09:00:00"/>
Enter the range of begin/end dates at which alarms were received by manager.
Page 42/205

Alarm traps between the NMS begin date nmsdatebegin and the NMS end date nmsdateend will be
generated
In the filter-event section, it is possible to define some criterias of event trap sending.
If necessary, modify and duplicate these lines:
<filter nename=""/>
Enter the NE long name of one equipment, ex: <filter nename="Dijon"/>
Event traps of this equipment will be generated
<filter eventtype=""/>
Enter the type of event, ex <filter eventtype="Login"/>
Event trap with a type Login will be generated.
Enter the location of the event, ex <filter location="SNC-TRIB" match="begin"/>
All event traps with the string beginning by SNC-TRIB will be generated.
<filter location="" match="exact"/>
Enter the location of the event, ex <filter location="SESSION" match="exact"/>
Note: In this case, the field must be filled with the exactly string of the event location
Event trap with exactly the "SESSION" location will be generated.
Enter the range of begin/end dates at which events were received by manager
Event traps between the NMS begin date nmsdatebegin and the NMS end date nmsdateend will be
generated
Save and close the file generation.xml
Note (1): Absence of tag in nename, status, eventtype, location, nedate, nmsdate means
there is no filtering on these fields.
Note (2): If more tags have been defined, they will be interpreted by a condition of type OR.
Note (3): If more different filtering have been defined in the generation.xml file, they will be interpreted
by a condition of type AND.
An usage example of generation.xml file is available in Appendix Example of SNMP trap generator
configuration
1.2.3.35 - Configuration file to display the long name of the trail(s) in relation to its alarm
pk
This procedure is used to set the parameters used by a java program to be able to obtain the long name of the
trail(s) in relation to its alarm pk.
In this folder, open the file traplongname.xml

Page 43/205


<var name="TrapLongNameServer" type="java.lang.String" value="127.0.0.1" />
Enter the IP address of the Ionos-NMS server
<var name="TrapLongNameUser" type="java.lang.String" value="observer" />
<var name="TrapLongNamePassword" type="java.lang.String" value="public" />
Enter the login and password of a Ionos-NMS user
Save and close the file traplongname.xml
1.2.3.36 - To run the getTrailLongNames script
This script is used to display the long name of the trail(s) in relation to its alarm pk.
It can be run from the IONOS-NMS server or in a DOS commands window from any PC client (in this case fill
the TrapLongNameServer variable with the correct IP address of the Ionos-NMS server in the
traplongname.xml file) (see 1.2.3.35 - Configuration file to display the long name of the trail(s) in relation to
its alarm pk)
In the directory chosen for installation (Ionos-NMS or /tools/IONOS-NMS by default), select the
bin folder.
Run the command : getTrailLongNames.bat <alarm pk>
(with Windows)
Or
Run the command : ./getTrailLongNames.sh <alarm pk>
(with Solaris)
With <alarm pk> as input parameter

An usage example of this script is available in Appendix Example of getTrailLongNames script usage
1.2.3.37 - To configure the FMX backup configuration file
This procedure is used to configure the FMX backup configuration file. This is available only for a FMX-GIES
type and on a Windows Ionos-NMS server.
To configure the time lapse to read the file backup size and its conversion after the execution of the tpimms
and tpimmsconverter processes during the FMX backup configuration files, modify if necessary the value (5
seconds by default):

<var name="FMXBackupTimeout" type="java.lang.Integer" value="5" /> (in seconds)
To activate the periodic backup for all FMX-GIES, replace the line:

<var name="FMXDailyBackupEnabled" type="java.lang.Boolean" value="false" />
by
<var name="FMXDailyBackupEnabled" type="java.lang.Boolean" value="true" />
To configure the delay between two FMX database backup, modify if necessary the value (1440 minutes, by
default):

<var name="DelayBetweenTwoFmxBackupInventory" type="java.lang.Integer" value="1440" /> (in
minutes)
No automatic backup (ex: in case of NE audit) is done if this delay is not exceeded.
To activate or not the auto-discovery of the FMX-GIES inventory, modif if necessary the line:

<var name="isFmxInventoryLikeVne" type="java.lang.Boolean" value="false" />
Auto-discovery of the FMXGIES inventory is available.
by
Page 44/205

<var name="isFmxInventoryLikeVne" type="java.lang.Boolean" value="true" />
The behaviour of the FMX-GIES is like a VNE: no auto-discovery of the inventory is done, need to add
manually container(s) and interface(s) from the NE properties.
Caution: After the restart of the Ionos-NMS server, if no FMX database backup has been already done, it is
necessary to wait the end of the sequentialy task of backups (before to run a FMX audit for example).
1.2.3.38 - To configure the user rights to perform actions from the Federator application
This procedure is used to configure the user rights to perform actions from the Federator application.
Actions are: Backup server, Change server, Restore from last backup, Start server and Stop server.
In the directory chosen for
Config/EasyLauncher folder.
the
installation
(by
default
Ionos-NMS),
select
the
In this folder, open the file Federator_users.xml

To add new user(s) and allocate rights to perform action(s), duplicate and/or modify the following
section:
<user name="admin" password="secret">
<action name="backupServer"
value="true"/>
<action name="changeServer"
value="true"/>
<action name="lastRestoreServer"
value="true"/>
<action name="startServer"
value="true"/>
<action name="stopServer"
value="true"/>
</user>
Enter the user name and its associated password.
For each action name, enter the true value to allow the user to perform the action or false to not allow the
action.
Note : These users must also exist in the Admin View of Ionos-NMS server (7- USERS
MANAGEMENT)
Save and close the file Federator_users.xml

Stop and restart the EasyLauncher application
On Solaris, from the Ionos-NMS folder/bin folder, run the following scripts:
- stopEasyLaunch.sh (to stop the easylauncher process)
- startEasyLaunchmanual.sh in ksh mode (to start the easylauncher process)
On Windows, right-click on the Easy Launcher icon in the task bar and select Exit menu: The
Ionos-NMS server and any process launched by Easy Launcher will be stopped.
Then, restart the Ionos-NMS server using the menu Start/All Programs/IONOS-NMS/Ionos-NMS
(easy launcher) shortcut.
Note : (1) When a user is not allowed to perform an action a message You dont have privileges to
perform this action is displayed
(2) If the password of the user is not correct, a message <action> failed of
<IP_Address_Ionos-NMS> :wrong password is displayed.

Page 45/205

1.2.4 - Available configurations on Client IONOS-NMS
1.2.4.1 - To configure the help on line
In the folder, open the file Profiler.xml.
Replace the line :
by
<HELP html="${BROWSER} ${ROOTDIR}/help/fr/hh_start1.htm"/>

<HELP html="${BROWSER} C:/Program Files/Ionos-NMS/help/en/hh_start.htm">
When the Client application is started, check the help on line works correctly (menu Help>Help on line).
1.2.4.2 - To configure Internet Explorer to use HTTP Browser on the equipment of type
ADR
Open Internet Explorer/ menu Tools / sub-menu Internet Options.

In the General tab, click on [Delete cookies] and validate the removal
In the General tab, click on [ Parameters ].
Tick the button [On each page visit ]

Define the disk space to be used to 30 Mo (if Internet Explorer version < 5.5 put 1 Mo)
Click on [OK]
In the zone "Temporary Internet Files", click on [Delete files ]
Tick [Delete all content outside connection], then click on [OK].

click on [OK] in the [Internet Options] dialog box
Close Internet Explorer.
Page 46/205

1.2.4.3 - To configure Internet Explorer to use HTTP Proxy
Open Internet Explore menu Tools / sub-menu Internet Options.

In the tab Advanced, for Parameters HTTP 3.2
- Tick Use HTTP 3.2
- Tick Use HTTP 3.2 with a connection by proxy
In the tab Connections, click on [ LAN Parameters ]
Tick [ Use a proxy server ]
Click on [ Advanced ]
Tick [ Use the same proxy server for all the protocols ]
-
On the level of type "HTTP", to fill address IP of the proxy server (x.x.x.x) as well as the
number of the port of the proxy (4002)
Note : if FTP must be launched on the client PC, tick off the case Use the same proxy server
the protocols.
for all
In Exceptions, list all the primary and secondary addresses of ADRs not supporting the
proxy (case of the ADR155C P2.6, EXT155HA, ADR155E, ADR10000 or ADR10000HN ),
separated by ";".
Apply these modifications then to close Internet Explorer.

1.2.4.4 - To inhibit the data entry of spaces in the M1400 name of the equipment
In this folder, open the file lfclient_ext_parameters.xml
Replace the line:
< property name="allowM1400Blank" type="Boolean" value = "true"
by
< property name="allowM1400Blank" type="Boolean" value = "false"
Caution: The taking into account of the file modification will be effective only after launching of Client
IONOS-NMS.
Note: By default, the data entry of spaces in the M1400 name of the equipment is authorized.
1.2.4.5 - To activate the data entry of upercase in the M1400 name and longname
Page 47/205

In this folder, open the file client-advanced.xml
Replace the lines:
<var name="SubnetworkNameUpperCaseMask" type="java.lang.Boolean" value="false"/>
<var name="NEM1400NameUpperCaseMask" type="java.lang.Boolean" value="false"/>
<var name="NELongNameUpperCaseMask" type="java.lang.Boolean" value="false"/>
<var name="TrafficCarrierLongNameUpperCaseMask" type="java.lang.Boolean" value="false"/>
<var name="ETHNormalizedNameUpperCaseMask" type="java.lang.Boolean" value="false"/>
by :
<var name="SubnetworkNameUpperCaseMask" type="java.lang.Boolean" value="true"/>
<var name="NEM1400NameUpperCaseMask" type="java.lang.Boolean" value="true"/>
<var name="NELongNameUpperCaseMask" type="java.lang.Boolean" value="true"/>
<var name="TrafficCarrierLongNameUpperCaseMask" type="java.lang.Boolean" value="true"/>
<var name="ETHNormalizedNameUpperCaseMask" type="java.lang.Boolean" value="true"/>
IONOS-NMS.
Note: By default, the data entry using lowercase and upercase is authorized.
These parameters are concerning respectively sub-networks, name M1400 and longname of network
elements, longname of trail and bearer SDH.
1.2.4.6 - To configure the automatic deconnection of client after inactivity period
In this folder, open the file client_advanced.xml
Modify the line (time in minutes)
<var name="MaxInactivityDuration" type="java.lang.Integer" value="0"/>
IONOS-NMS.
Note: By default, the automatic deconnection is not configured.
1.2.4.7 - To configure the number of NEs for which a warning message is displayed in
NML View
Modify the line (by default, number of NEs = 50)
<var name="NesNumberTreshold" type="java.lang.Integer" value="50"/>
IONOS-NMS.
1.2.4.8 - To deactivate the automatic routing of trails/bearer SDH
Replace the lines:
<var name="SDHAutoRoutingActivated" type="java.lang.Boolean" value="true"/>
by
<var name="SDHAutoRoutingActivated" type="java.lang.Boolean" value="false"/>

Page 48/205

IONOS-NMS.
Note: By default, the automatic routing is not activated.
1.2.4.9 - To configure the use of Proxy for SLF-v1 and SLF-N
Uncomment and modify the line :
<FHPROXY value="-ipproxy ${IP_SRV} portproxy 5588 SUPERVISOR"/>
Comment the line :

IONOS-NMS.
1.2.4.10 - To configure the use of Proxy for SLF-H
Uncomment and modify the line :
<FHPROXY_SNMP value="-ipproxy ${IP_SRV}:5590"/>
Comment the line :
<!FHPROXY_SNMP value=""/-->
IONOS-NMS.
1.2.4.11 - To configure the use of client without an alarm window
In the folder, open the file client-advanced.xml.
Add the line :
<<var name="FaultViewEnabled" type="java.lang.Boolean" value="false"/>
IONOS-NMS.
1.2.4.12 - To display the ADR10000 Proxy menu
Replace the line:
<var name="ProxyADR10000Enabled" type="java.lang.Boolean" value="false"/>
by
<var name="ProxyADR10000Enabled" type="java.lang.Boolean" value="true"/>
IONOS-NMS.
1.2.4.13 - To configure the launching of the Equipment View (ADR10000)
This procedure is used to configure how to launch the ADR10000 Equipment View.
To open the EMS-ADR application instead of to open the shelf view of the selected NE,
Page 49/205

Replace the line:
<var name="adr10kview" type="java.lang.Boolean" value="false"/>
by
<var name="adr10kview" type="java.lang.Boolean" value="true"/>
In this case, you have to type the User Name and Password of EMS-ADR application.
Caution: The taking into account of the file modification will be effective only after launching of
Client IONOS-NMS.
Note: By default, the double-click to display the Equipment View opens the shelf view of the
selected NE.
1.2.5 - The Application Easy Launcher under Windows

Easy Launcher is a utility which allows:
to start the server and the client of IonosNMS,
to permanently know the state of the server according to the icon displayed,
to be able to visualize the log of the server and the log of errors,
to start backups and restores
Easy Launcher Menus
Figure 1.6 : easy launcher (1)

Start client
to start the client
Start server
to start the server (grayed when the server is started)
Stop server
to stop the server (grayed when the server is stopped)
Exit
to quit Easy Launcher
About :
to display client and server version
Other
to launch the following pop up menu :

Page 50/205

Backup oracle database
to perform a backup of oracle database
Restore oracle database

the server is started
to perform a restore of oracle database (grayed when
Backup equipement database :
to perform a backup of equipment configuration
Display log files
to display logs of servers and the logs errors
Configuration
to configure easy launcher
Tools
to launch the following pop up menu :

Start TFTP server
to start TFTP server
Start SFTP server
to start SFTP server
Start FTP server
to start FTP server
HTTP Proxy
installed)
to perform a Proxy configuration (grayed if the software is not
Generate Pack trace
to generate a zipped file of several files used for debug
1.2.6 - To start the Server Application with Windows

1.2.6.1 - To start the Server with Easy Launcher
The license server has been run beforehand.

In Windows, double-click the IONOS-NMS Easy Launcher icon : according to the configuration, the server is
launched automatically or click on menu Start Server of Easy Launcher. The following screen is displayed.
Figure 1.9 : Window - Start Ionos-NMS server

Click on [Terminate] when "IonosNMS server is started" is ticked.
Launch also the server TFTP by clicking on the menu Start TFTP Server.
1.2.6.2 - To start the server without Easy Launcher
Caution: The launching of server without Easy Launcher in not recommended.
The license server has been run beforehand.

Under Windows, double-click on the Ionos-NMS Server icon (or use the menu To start/Programs) : The DOS
commands window opens.
Page 51/205

Caution: Always keep this window open or reduce it.
Figure 1.10 : DOS commands window

The server is ready when the following line appears "TMS up in secure mode".
Launch also the server TFTP by double-clicking on the TFTP icon.
1.2.7 - To start the Client Application with Windows

The Server Application has been started beforehand (see 1.2.5 -).
In Windows, double-click the IONOS-NMS Client icon (or use the menu Start/Programs).
The window Connect to which Name Server ? is displayed
Figure 1.11 : Window - Connect to which Name Server

enter the server name (Localhost for local server) and its port number (always 1099).
Click [OK] : The Login window is displayed (if an error is detected, a message is displayed).
Figure 1.12 : Login Window

In this window, enter the user name (User name field) and password (Password field) : by default,
the passwords corresponding to the default users admin, operator and observer are respectively
secret, private and public.
Caution:To connect a Ldap user to the Ionos-NMS server, type for the user, the name in the same
form that it has been created in the Ionos database and its associated password.(ie: olivier.dupont)
(see :Figure 7.20)
Page 52/205

Click [OK] to validate the window: the main view is displayed (see 2.2 -).
Remarks :The user profile defines the user rights on the Application:
. the administrator has all rights.
. the operator has all rights except the rights on the Admin view.
. the observer can only consult the application.
Refer to the table in Appendix : Rights linked to each profile created by default.
1.2.7.1 - To configure the time difference between client and server
This procedure is used to give the capability to start the client application using a time zone different from
Ionos-NMS server.
In this case, the begin date and NE date of the alarms displayed in the PC client are adjusted on the IonosNMS server (and not on the Client).
Create a new shortcut or modify the command line in the properties of the shortcut for Ionos-NMS client.
Open the properties of the Start/All Programs/Ionos-NMS 5.4 (client) shortcut, and add at the end of the line
tdiff H- or tdiff H option.
With H- in hour(s) if Time Zone of the Ionos-NMS Server is GMT HH:00
or
With H in hour(s) if Time Zone of the Ionos-NMS Server is GMT +HH:00
Example:
Time Zone of the Ionos-NMS Server is GMT 06:00
Time Zone of the Ionos-NMS Client is GMT + 01:00
The line command to start the Client must be:
"C:\Program Files\Ionos-NMS-54rev7\bin\client.exe" -f --begin -client -Xms15m -Xmx512m --end -tdiff 7Note: Only the Time zone in hour(s) is managed (ex: GMT +05:30 is not managed).
1.2.8 - To close the Server Application with Windows

1.2.8.1 - To close the Server with Easy Launcher
Click on the Easy Launcher icon in the tools bar.

Click on the menu Stop Server.
1.2.8.2 - To close the Server without Easy Launcher.
In the DOS commands window (see Figure 1.10 above) click [Ctrl] [C] on the [X] button at the top right.
1.2.9 - To close the Client Application

In the menus bar, select File > Exit.
1.2.10 - To start the HTTP Proxy Application with Windows

Under Windows, double-to click on the Ionos Proxy 3.2 (HTTP) icon (or to use the menu To start Programs):
the following window is displayed.

Page 53/205
Figure 1.13 : Window HTTP Proxy Application

The proxy is operational if the IP address of server IONOS-NMS is present in "List of NMS Servers" (see
1.2.3.4 - ).
1.2.11 - To close the HTTP Proxy Application with Windows

In the menus bar, select File > Exit.
Confirm the closing.
1.2.12 - To start the Proxy Application for SLF-v1 and SLF-N

Under Windows, double-to click on the Start Ionos-Proxy 3.2 (SLF-v1 F-N) icon (or to use the menu To start
Programs) : a DOS command window is displayed.

Page 54/205
Figure 1.14 : Window SLF-v1 SLF-N Proxy Application

1.2.13 - To close the Proxy Application for SLF-v1 and SLF-N

Under Windows, double-to click on the Stop Ionos-Proxy 3.2 (SLF-v1 and SLF-N) icon (or to use the menu
To start Programs) : the DOS command window is closed.
1.2.14 - To start the Proxy Application for SLF-H under Windows

Under Windows, double-to click on the Start Ionos-Proxy 3.2 (SLF-H) icon (or to use the menu To start
Programs) : the DOS command window is displayed.
Figure 1.15 : Window SLF-H Proxy Application
1.2.15 - To close the Proxy Application for SLF-H

Under Windows, close the DOS command window to stop Ionos-Proxy 3.2 (SLF-H)

Page 55/205
1.3 - TO INSTALL THE CD FOR SOLARIS

The IONOS-NMS software is supplied on a CD with an user guide.
The CD contains in the directory Install :
nmsserver_setup.sh (for the installation of Server Application with Solaris).
proxy_setup.sh (for the installation of Proxy Applications with Solaris).
The license server is installed automatically, when the server is installed.
1.3.1 - To install the Server and Client Applications

The operating system and the database Oracle have been installed beforehand on the workstation where the
server application is installed.
1.3.1.1 - To install the Server Application with Solaris
Caution: The installation of the Server Application must be carried out by a personnal qualified
Sagemcom.
Run the server_setup.sh executable (Server Applications) which is in the directory /install.
Follow the installation instructions : choose a directory (the server is installed by default in
/tools/IONOS-NMS/).
a/ All the scrtipts are installed in the scripts folder of the directory chosen for the installation
(by default, /tools/IONOS-NMS/scripts).
b/ The backup files will be saved in the db-backup folder of the selected directory (by default,
/data/IONOS-NMS/db-backup/server and /data/IONOS-NMS/db-backup/eqpt).
Copy of license file
In the directory chosen for installation (IONOS-NMS by default), select the Config. folder.
In the Config. folder, copy the LICENSE.DAT file.
Edit this file and add the path of directory in which it has been copied.
1.3.1.2 - To install the Client Application with Windows
Follow the installation instructions: see 1.2.1.2 1.3.1.3 - To install the HTTP Proxy Application with Solaris
Run on the executable proxy_setup.sh (Proxy Application) which is in the directory /install.
Follow the installations instructions : choose a directory (the proxy is installed by default in
/tools/IONOS-PROXY).
Close the window "run" at the end of the installation.
Caution: In the case of the use of HTTP Proxy, to guarantee the access security to the equipment, it is
possible to add IP address of the server with a habilitation "Supervisor" in each NE of type ADR155C
P3, ADR2500C, ADR2500 EXTRA or ADR63E1 which will be managed by IONOS-NMS. For that use
HTTP browser: menu "Equipment/Management to add IP address of the server in the table "List
Managers" while clicking on "Supervisor". 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
- ADR2500 EXTRA
Page 56/205

-
ADR155CPE
ADR 622
1.3.2 - To install LCT application for equipment (FMX, Sagem-Link, FSP2000,

FSP3000, ADR155E)
See 1.2.2 -
1.3.3 - Available configurations on Server IONOS-NMS

See 1.2.3 -
1.3.4 - Available configurations on Client IONOS-NMS

See 1.2.3.28 -
1.3.5 - To start the Server Application with Solaris

At the boot of the workstation, the database server (ORACLE), the license server and the server IONOS-NMS
automatically start : if the server stopped, to restart it:
Log on as root.
Enter the command ksh [].
Enter the command /tools/IONOS-NMS/scripts/startnmsserver []
Check with the command ps ef | grep bootstrap the java process is activated.
Do a logout.
1.3.6 - To start the Client Application with Windows

See 1.2.7 -
1.3.7 - To close the Server Application with Solaris

Log on as root.
Enter the command /tools/IONOS-NMS/scripts/stopnmsserver []
Do a logout.
1.3.8 - To close the Client Application with Windows

See 1.2.9 -
1.3.9 - To start the Proxy Applications with Solaris

At the boot of the workstation, the database server (ORACLE), the license server, the server IONOS-NMS and
the HTTP Proxy, the SLF-v1, the SLF-N and the SLF-H automatically start : if one Proxy is stopped, to restart
it:
Log on as root.
Enter the command /tools/IONOS-NMS/scripts/startproxy []
Check with the command ps ef | grep proxy if the process is activated.
Page 57/205

Logout.
1.3.10 - To stop the Proxy Application with Solaris

Log on as root.
Enter the command /tools/IONOS-NMS/scripts/stopproxy []
Logout.
1.3.11 - To restart a SUN station with Solaris

Log on as root.
Enter the command /tools/IONOS-NMS/scripts/globalrestart []
Do a logout.
1.3.12 - To restart the Oracle database and the IONOS-NMS server with Solaris
Log on as root.
Enter the command /tools/IONOS-NMS/scripts/oracle-and-nmsserver-restart []
Do a logout.
This script stops the server IONOS-NMS and the database Oracle, then restarts the database oracle and
restarts the server IONOS-NMS.
1.4 - TO INSTALL THE IONOS FEDERATOR

A Ionos Federator is supplied with the Client Application of IONOS-NMS. It is used to supervise the alarm
state of several Ionos-NMS servers.
1.4.1 - To install the Client Application of IONOS-NMS

The Client Apllication of IONOS-NMS have been installed beforehand on the PC where the alarms Federator
is launched.
See 1.1.3 -Workstations
After the installation of Client application, a new icon is created on the desk :
- Ionos-NMS 5.3 (Federator)
1.4.2 - To modify the configuration file

Before launching the Ionos Federator, the configuration file must be updated.
In the folder, open the Federator.xml file.
Modify, if necessary, the background image updating the path of "Background File"
Modify, if necesary, the time intervall between two refreshes in second (30 seconds by default)
Modify, if necessary, the time intervall between two attempts of connection with each server in
second (120 seconds by default)
Page 58/205

Define the list of servers IONOS-NMS controlled by the federator. For each server, give :
- The name of server which will displayed on the map
- The IP address of server
- The type ("none", and if function Backup 1+1 of IONOS-NMS Servers is used "principal" or
"backup")
- The port (always 1099)
- The position XY of the icon on the map in pixels
<federator>
<background file="../resources/background.jpg" />
<refresh pool_refresh_value="30" />
<reconnect pool_reconnect_value="120" />
<client open_mcp_client="../bin/client.exe --begin -client -Xms15m -Xmx256m --end" />
<servers>
<server name="10.142.63.173" ip_adress="10.142.63.173" type="backup" port="1099" location_x="400"
location_y="150"/>
<server name="10.142.33.119" ip_adress="10.142.33.119" type="principal" port="1099" location_x="500"
location_y="300"/>
<server name="10.142.33.115" ip_adress="10.142.33.115" type="none" port="1099" location_x="300"
location_y="300"/>
</servers>
</federator>
Note :This configuration will be effective only after launching of Federator Apllication.
1.4.3 - To start the Ionos Federator

Double-click on the icon of federator .
The window federator Login is displayed :
In this window, enter the user name (User name field) and password (Password field) : by default,
the passwords corresponding to the default users admin, operator and observer are respectively
secret, private and public. The same passwors is used for the connection of Federator with all the
servers IONOS-NMS defined in the configuration file.
Click [OK] to validate the window : the main view of Federator is displayed.
Notes : The user name and the password entered in the window "Login" of Federator will be used to
Open a Client.
The user profile defines the user rights on the Application:
Notes : It is possible to start Ionos Federator with a fixed Login/Password. For this, you have to modify
the command line in the properties of the shorcut for Ionos Federator.
Page 59/205

Open the properties Start/All Programms/IONOS-NMS/IONOS-NMS(federator) and add at the end
of the line : -username Your-login-name -password Your-password
For example with user admin:
"C:\Program Files\Ionos-NMS\jre\bin\javaw.exe" -jar ..\lib\beans\sfederatorapp.jar cfg
..\config\Federator.xml username admin -password secret
The user name and the password entered in the window "Login" of Federator will be used to Open a
Client.
The user profile defines the user rights on the Application:
1.4.4 - To close the Ionos Federator

In the menus bar of Federator application, select File > Exit.
1.5 - DATABASE MANAGEMENT

The used database is ORACLE version 10.2 or 11.2 with Windows 7 (x64 bits)/ Windows 200SRV R2 (x64
bits)
It must be installed before the server application, on the same workstation.
1.5.1 - To backup the database

Two types of backup on line are provided:
a menu provided in the IONOS-NMS application.

a command script.
These two commands backup the data used by IONOS-NMS application.
1.5.1.1 - Backup on line from the client application
In the menus bar, select File > Forced backup : the Force Backup window is displayed.
Figure 1.16 : Force Backup Window

In this window, enter eventually a comment.
Click [Launch backup] to launch the backup.
Page 60/205
Figure 1.17 : Backup /database Window

Click [Close] when export terminated is displayed.
Notes :
The backup is copied in the directory given in the File.xml file, which is in the
Config folder in the directory chosen for installation (backup directory by default :
c:\temp\oracle.backup with Windows and /data/IONOS-NMS/db-backup/server
with Solaris).
Le filename with Windows has the following format:
IONOS-NMS-Database-yyyy-mm-dd.dat
IONOS-NMS-Database-yyyy-mm-dd--nn.dat if several backups are launched the
same day.
The comment is written in the file.txt (same name).
Le file with Solaris is copied in:
/yyyy/yyyy-mm/yyyy-mm-ddnn.dat.gz
Yyyy-mm-dd is the date of backup launching and nn is the number of backup in the
day.
1.5.1.2 - Backup on line from a script with Solaris
Log on as root.
Run the /tools/IONOS-NMS/scripts/db-backup[parameters] script.
Indicate the following parameter values between parentheses:

a/ blank (backup with automatic filename in rule)
b/ -f filename (backup with file filename).
c/ -c comment (backup by inserting commentary file).
1.5.1.3 - To configure a Periodic backup off line with Solaris
Log on as root.
Enter the command /tools/IONOS-NMS/scripts/configure-periodic-backup with the hour of periodic
backup.
For example : configure-periodic-backup 03 15 (for a backup at 3h15 every days).
Accept the warning if a periodic backup is already defined.
The periodic backup will be launched once by day.
1.5.1.4 - Copy of backup directories on magnetic tape with Solaris
Log on as root.
Put a tape not write protected in the tape drive
Page 61/205

Run the /tools/IONOS-NMS/scripts/backup-on-tape script.
1.5.2 - To restore the database

The restoration on line allows to restore one of the backup of IONOS-NMS, by using a script. In this case, the
server IONOS-NMS is stopped, but the database ORACLE is always operational. This command restores the
data used by IONOS-NMS application (backed-up data with Force Backup or with the backup script) .
1.5.2.1 - To restore of a backup with Windows
Stop the IONOS-NMS server.

Run the import.cmd in the bin folder of the directory selected for installation (by default Ionos-NMS) .
Enter the filename (with path).
Note : The ORACLE database must be in operation.
The path should not contain of space.
1.5.2.2 - List of available backup with Solaris
Log on as root.
Run the /tools/IONOS-NMS/scripts/backup-list script
This script is used to recover the list of all the backups in the server.
1.5.2.3 - Restore of a backup with Solaris
Log on as root.
If necessary, run the /tools/IONOS-NMS/scripts/backup-list script
Notes : The filenames are displayed in the following form: yyyy-mm-dd-nn.dat.gz
Run the /tools/IONOS-NMS/scripts/db-restore[parameters] script to restore the database from a

backup file.
Indicate the following parameter values between parentheses:
yyyy mm dd nn (recovers the file yyyy-mm-dd---nn.dat.gz)
This script displays the data entered for the forced backup (user, data and comment if available) and the user
must confirm its choice. The server IONOS-NMS is stopped and the restoration is launched. Then the server
IONOS-NMS is restarted automatically.
1.5.2.4 - Restore of backup directories copied on magnetic tape with Solaris
Log on as root.
Put the tape in the tape drive
Run the script: /tools/IONOS-NMS/scripts/restore-from-tape.
Then, restore one of the backups using the restore procedure.
This script copies the backup directories of the tape on the disk.

Page 62/205
1.5.3 - To migrate a database

This procedure makes it possible to migrate a database version P3 (P3.4) or P4 (P4.1, P4.2, P4.3, P4.4, P5.1,
P5.2, P5;3, P5.4) towards a database version P5.5, starting from a script of command, the server of
application being stopped but not the data base.
Note: For migrations starting from previous version refer to the technical support
Caution: The used database since the version P5.1 change. (see 1.5 - Database management)
1.5.3.1 - Migration of a database with Windows.
Launch a Forced Backup on IONOS-NMS P3 (P3.4) or P4 or P5 (menu Forced Backup).

Export the logs (Fault Log and Event Log).
Stop the server IONOS-NMS P3 or P4. or P5
Rename the directory of installation of IONOS-NMS P3 or P4 or P5.
Install, if necessary, the database used with the current IONOS-NMS version (see 1.5 -Database
Management).
Install the new IONOS-NMS Server P5.5 (see 1.2 -)
Run the script dbmig in the folder bin of directory chosen for the installation of IONOS-NMS P5.5 (by
default Ionos-NMS ) with the following parameters:
dbmig sys dbnms [username old database ] [passwd] [username new database] [passwd]
Note : It is not necessary to give the usernames and passwords if the database is the migration is
done in the same user.
If the "user" of new database is different, it will be created automatically by IONOS-NMS during the
migration. If the user was created before, the migration doesn't work.
The migration starts. The results are displayed during the processing.
The indication of end of processing is displayed.
Note :The database ORACLE must be in operation.
Start the server IONOS-NMS P5.5

Install a new IONOS-NMS Client P5.5 and run the client.
Check the database has been migrated correctly.
Purge the logs (Fault Log and Event Log).
Note: An executable file is supplied to re-align the general parameters and the capability parameters
of Network Element (see section To audit a network element (NE)) after a migration.
- Launch the IONOS-NMS server
- Modify the value of SNMP time-out in the Preferences of NE ("SNMP
requests configuration for all NEs " in menu Tools/Preferences/NE). Put 2s
instead of 30s.
- In the directory chosen for installation (Ionos-NMS or /tools/IONOS-NMS by
default), select the bin folder.
- Run the command: run ./bsh/align-NEs.bsh (PC), then give the login ad
password of the user IONOS-NMS and the IP address of the server.
- Relaunch the server and set back the initial value of the SNMP time-out

Page 63/205

1.5.3.2 - Migration of a database with Solaris.
Launch a Forced Backup on IONOS-NMS P3 (P3.4), P4 or P5 (menu Forced Backup).

Export the logs (Fault Log and Event Log).
Stop the server IONOS-NMS P3, P4 or P5
Move the directory of installation of IONOS-NMS P3, P4 or P5(for example in IONOS-NMS.old).
Install, if necessary, the database used with the current IONOS-NMS version (see 1.5 - Database
Management).
Install the new IONOS-NMS Server P5.5 (see 1.2 -)
Log on as root
To position on the directory /tools/IONOS-NMS/bin
Run :
/dbmig sys dbnms [username old database ] [passwd] [username new database] [passwd]
Note : It is not necessary to give the usernames and passwords if the database is the migration is
done in the same user.
If the "user" of new database is different, it will be created automatically by IONOS-NMS during the
migration. If the user was created before, the migration doesn't work.
The migration starts. The results are displayed during the processing.
The indication of end of processing is displayed.
Note : The database ORACLE must be in operation.
Start the server IONOS-NMS P5.5.

Install a new IONOS-NMS Client P5.5 and run the client
Check the database has been migrated correctly.
Purge the logs (Fault Log and Event Log)
Note: An executable file is supplied to re-align the general parameters and the capability parameters
of Network Element (see section To audit a network element (NE)) after a migration.
- Launch the IONOS-NMS server
- Modify the value of SNMP time-out in the Preferences of NE ("SNMP
requests configuration for all NEs " in menu Tools/Preferences/NE). Put 2s
instead of 30s.
- In the directory chosen for installation (Ionos-NMS or /tools/IONOS-NMS by
default), select the bin folder.
- Run the command: ./run.sh ./bsh/align-NEs.bsh (solaris), then give the login
ad password of the user IONOS-NMS and the IP address of the server.
- Relaunch the server and set back the initial value of the SNMP time-out
1.5.4 - Database Management (Split & Merge)

Caution : Split/merge scripts and ORACLE database must run on the same machine
- Split and merge of databases can take a long (very long) time to do their job. It is possible to
follow them with the SplitMerge.log file which is in the same directory ( IONOSNMS/bin/SplitMerge).
- The SplitMerge.log file contains data about errors. Do not hesitate to consult the last lines.
- In the SplitMerge.log file, lines with the word "ERROR" are not necessarily errors.
- Split and merge work only with version 5.4 of IONOS-NMS database (or later).
- In the following text, the word "user" is used in the ORACLE way ( which is a IONOS-NMS
database ).
Page 64/205

Note: An executable file is supplied to re-align the management table of Network Element in order to
update the IP address where the alarm traps must be sent(see 1.5.5 - Updating the traps managers
table of NEs after a merge or a split)
An example of split/merge scenario is available in Appendix Example of split/merge scenario

1.5.4.1 - To split a IONOS-NMS database
This command split the database used by IONOS-NMS in two IONOS-NMS databases
Split.sh (or .bat) extract a subnetwork from a IONOS-NMS database
Requirements :
- The Splited Subnetwork must not be connected to others subnetworks or Network-Elements.
- The Splited Subnetwork must have a unique name.
- The name of the Splited Subnetwork must contain only figures and\or letters :
- No spaces, neither of punctuation marks, nor special characters. It is necessary to respect
lowercase/uppercase letter.
- During a split, IONOS-NMS server must be stopped.
- Free space in the Oracle database must be sufficient.
For a split, the free space volume must be at least 2 times the size of the user to split.
The split makes two copies of the original user.

In the fist copy, it keeps only the subnetwork chosen.
In the second copy, it remove only the subnetwork chosen.
At the end we get two distinct Oracle "users" (database).
original "USER" (NMSSERVER):
Main View
/ | \
Sub_1 Sub_2 Sub_3
We start a split with the Sub_2 subnetwork

Split.bat DBNMS NMSSERVER nmssmn NMSSERVER_SPLIT_A NMSSERVER_SPLIT_B Sub_2
or
./split.sh DBNMS NMSSERVER nmssmn NMSSERVER_SPLIT_A NMSSERVER_SPLIT_B Sub_2
We get :
original "USER" (NMSSERVER):
Main View
/ | \
Sub_1 Sub_2 Sub_3
New User 1 (NMSSERVER_SPLIT_A):
Main View
|
Sub_2
New User 2 (NMSSERVER_SPLIT_B):
Main View
/
\
Sub_1 Sub_3
Notes :
-If some Network Elements are present in the main view, they will be present in the second User New User 2
(NMSSERVER_SPLIT_B) but not in the first one
-If some Network Elements are present in the "Unassigned Zone", they will be found in both "Users"
(NMSSERVER_SPLIT_A and NMSSERVER_SPLIT_B)
- If the subnetwork name is not unique, the split will fail.
1.5.4.2 - Split with Solaris
Page 65/205

split.sh can be found in the directory ...IONOS-NMS/bin/SplitMerge
Log on as root.
# cd /tools/IONOS-NMS/bin/SplitMerge
Run the split [parameters] script.
./split.sh SID user_original password_original user_split_1 user_split_2 subnetwork_to_split
Indicate the following parameter values
SID
: SID (by default DBNMS)
user_original
: DB user to split (by default NMSSERVER)
password_original
: password of DB user to split (by default nmssmn)
user_split_1
: username of the first new split user
user_split_2
subnetwork_to_split
: username of the second new split user

: subnetwork to split
1.5.4.3 - Split with Windows
split.bat can be found in the directory ...IONOS-NMS/bin/SplitMerge

# cd C:\Program Files\IONOS-NMS\bin\SplitMerge
Run the split [parameters] script.
split.bat SID user_original password_original user_split_1 user_split_2 subnetwork_to_split
SID
user_original
: DB user to split (by default NMSSERVER)
password_original
: password of DB user to split (by default nmssmn)
user_split_1
: username of the first new split user
user_split_2
subnetwork_to_split
: username of the second new split user

: sub network to split
1.5.4.4 - To merge two IONOS-NMS databases
This command merge two databases used by IONOS-NMS in a new one.

Requirements :
- Both "users" to merge must have the same version number.
- The free available space volume must be at least equal to the sum of the two "users" sizes to merge.
- It is not possible to merge a user with itself.
- The " Unassigned" zones must be empty.( no NE or no Sub-network). If there are some elements in the
"Unassigned zone", it is possible to move them in a temporary sub-network.
Notes :
- Preferences, passwords ... for the new NMSSERVER_MERGED "user" are the ones from the
NMSSERVER_A "user"
- The merge process does not control the quantity of NEs. So you have to check if the quantity of NEs after
the merge is compatible with your license.
- The NE names in NMSSERVER_A "user" should not have a homonym in the NMSSERVER_B "user". The
same for M1400 names.
This script creates a new IONOS-NMS database with the two "users" defined in the parameters of the
command line
original "USER" 1 (NMSSERVER_A):
Main View
/ | \
Sub_1 Sub_2 Ne1

Page 66/205

original "USER" 2 (NMSSERVER_B):
Main View
/ | \
Sub_1 NeA NeB
New "USER" (NMSSERVER_MERGED):
Main View
/
\
Main View 1
Main View 2
/ | \
/
|
\
Sub_1 Sub_2 Ne1 Sub_1 NeA... NeB
We find the two original "users" as subnetworks in the new "user"

1.5.4.5 - Merge with Solaris
merge.sh can be found in the directory ...IONOS-NMS/bin/SplitMerge

Log on as root.
# cd /tools/IONOS-NMS/bin/SplitMerge
Run the merge [parameters] script.
./merge.sh SID user_A password_A user_B password_B merged_user
Indicate the following parameter values:
SID
user_A
: first user to merge
password_A
: password of first user to merge
user_A
: second user to merge
password_A
: password of second user to merge
merged_user : merged user
1.5.4.6 - Merge with Windows
merge.bat can be found in the directory ...IONOS-NMS/bin/SplitMerge

# cd C:\Program Files\IONOS-NMS\bin\SplitMerge
Run the merge [parameters] script.
merge.bat SID user_A password_A user_B password_B merged_user
SID
user_A
: first user to merge
password_A
: password of first user to merge
user_A
: second user to merge
password_A
: password of second user to merge
merged_user : merged user
1.5.5 - Updating the traps managers table of NEs after a merge or a split
This command updates the traps managers tables in the NE if needed. It will replace an IP address by an
other in order to align the NE with the new IP address of the IONOS-NMS server
trapreceiverupdate.bsh gets all NEs in the IONOS-NMS database and update the traps manager
table of the NE if this is possible and if the NE are accessible
List of the NE which can be updated
ADR155c, ADR2500c, ADR2500extra, ADR 63E1, ADR155CCPE, ADR622, SLF-H, SLF-N
Page 67/205
FSP3000
FMX GIES
On a SOLARIS server :
Launch the IONOS-NMS server (and wait the server is started)
# cd /tools/IONOS-NMS/bin
# ./run.sh ./bsh/trapreceiverupdate.bsh
log as admin and (password for admin)
Unused IP address: 111.112.113.114 (example)
Newer IP address: 192.168.10.88
On a WINDOWS server :
Launch the IONOS-NMS server (and wait the server is started)
> cd C:\Program Files\IONOS-NMS\bin
> run.bat ./bsh/trapreceiverupdate.bsh
log as admin and (password for admin)
Unused IP address: 111.112.113.114 (example)
Newer IP address: 192.168.10.88
1.6 - EMS-ADR DATABASE MANAGEMENT (ADR 10000)

1.6.1 - To backup the EMS-ADR database
In case of ADR10000 management, there is also a EMS-ADR database backup when a backup action is done
(from the menu of IONOS-NMS application or from the script command).
Notes :
(1) The FTP server must be launched as a preliminary on the machine used
like IONOS-NMS server.
(2) The backup is copied in the directory given in the file.xml file, which is
in the Config folder in the directory chosen for installation (backup directory
by default : c:\Program Files\Ionos-NMS\backup\db with Windows and
/data/IONOS-NMS/db-backup/server with Solaris).
The filename has the following format:
EMS-ADR-Server-Database-yyyy-mm-dd.zip with ADR10000 / EMS-ADR R7.2
And EMS-ADR-Server-Database-yyyy-mm-dd.dmp with ADR10000 / EMS-ADR
R8.1
EMS-ADR-Server-Database-yyyy-mm-dd--nn.zip or .dmp if several backups
are launched the same day.
The file with Windows and Solaris is copied in:
/yyyy/yyyy-mm/dd/yyyy-mm-ddnn.zip or dmp
yyyy-mm-dd is the date of backup launching and nn is the number of backup
in the day.
With ADR10000 / EMS-ADR R7.2:

The EMS-ADR database is also transferred to the EMS-ADR in the /sdh_home/ems/ENMConfig folder.
With ADR10000 / EMS-ADR R8.1:
The EMS-ADR database is also transferred to the Oracle zone of the EMS-ADR in the
/sdh_home/oracle10/backupdir folder.
Note: check that the backupdir folder exists or create it if necessary.
1.6.2 - To restore the EMS-ADR database in R7.2

Page 68/205

This command restores the data used by EMS-ADR proxy application (backup data with Force Backup or
with the backup script).
Refer to the main document Element Management System for ADR Platforms N 253 216 157-A (chapt
2-3) Starting EMS-ADR from Client Windows section To start EMS-ADR start up configuration
Caution: Be sure that the EMS-ADR application is not working before to start the EMSADR in Start-up configuration. To stop the EMS-ADR application, open a Unix
window and perform the command: E.sh stop
From the START-UP configuration options window, choose:

From Backup copy
Click Restore from
Confirm the action of erase the exported log files
Select the EMS-ADR database to restore
Then, click Restore
Caution: After a EMS-ADR database restoration you have to set the Users
access rights
Refer to the main document Element Management System for ADR Platforms N 253 216 157-A (chapt
3-3) Managing users acces Editing users, and Adding new users
-
Edit the user admin, and set its password (to secret by default)
Add two users, operator with its associated password (private by default), and observer with its
associated password (public by default) in case of DB empty retoration.
Caution: The label of cross-connection are not recovered following a EMS-ADR
database restoration.
To restore cross-connection labels, launch an audit, select the
Crossconnections tab and click on the Global NMS to NE crossconnections reactivation button to launch the reactivation of all cross-connections in the NE.
From IONOS-NMS P5.4rev3 version, to restore cross-connection labels from the
EMS-ADR, select a NE and open the Shelf View, and on the menu bar select
System Import XC. The XC labels of all NE will be restored.
1.6.3 - To restore the EMS-ADR database in R8.1

ADR10000 R8.1 can be managed from IONOS-NMS P5.4rev5 version.
Caution: Be sure that the EMS-ADR application is not working before to restore the
EMS-ADR database. To stop the EMS-ADR R8.1 application, open an Unix
window in the EMS-ADR zone and perform the command: ENMdown.sh stop
To restore from the last backup, open an Unix window in the Oracle zone of the EMS-ADR and
perform the command from the home directory:
EmsDBRestore -d /sdh_home/oracle10/backupdir -f EMS_ADR_Server_Database.dmp -s
<schema_name>
e.g.:
[oracle10@z1-primepower ~] $ EmsDBRestore -d /sdh_home/oracle10/backupdir -f
EMS_ADR_Server_Database.dmp -s z2_primepower
<Schema_name> is the name of the schema that was backuped
In order to know the schema name, from the EMS-ADR zone with EMS user, type the SetupEMS command
and choose the option 1: the field Oracle DB user is the schema name.
Ex:
Page 69/205

ems(z2-primepower) ~ > SetupEMS.sh
EMS XDM Oracle Setup Menu
1
2
3
4
5
6
7
Show Current Configuration

Check Oracle DB status
Apply Infrastructure Layer to DB
Insert EMS XDM schema to DB
Remove EMS XDM schema from DB
Empty EMS XDM Database data
Reconfigure EMS XDM Database settings
Select an action (q to quit) [1...7,q] --> 1

Database Settings:
Database Server:
10.66.220.52
Oracle DB user:
z2_primepower is the schema name
Oracle service name: z2_primepower
To restore a previous EMS-ADR database saved, open an Unix window in the IONOS-NMS
zone, and from the backup directory perform the following command in order to copy the EMSADR database file in the correct place before to restore it:
Example of procedure (using the scp command):
# scp EMS-ADR-Server-Database-YYYY-MM-DD-000n.dmp
[email protected]:/sdh_home/oracle10/backupdir/EMS_ADR_Server_Database.dmp
EMS-ADR-Server-Database-YYYY-MM-DD-000n.dmp is the EMS-ADR database file stored into the /data/IONOSNMS/backup/server/yyyy/yyyy-mm/dd folder of the IONOS-NMS server.
oracle10 is the login (Oracle zone of the EMS-ADR), you must enter the password later.
10.66.220.52 is the IP address of the Oracle10 zone of the EMS-ADR.
/sdh_home/oracle10/backupdir/ is the path to copy the file
EMS_ADR_Server_Database.dmp is the name of the destination file. It is mandatory to respect this syntax name of the
destination file.
Note (1) : In case of Backup 1+1 secure (see 8.2.13 - Backup 1+1 of IONOS NMS
servers (Option), to restore the EMS-ADR database, you have to copy the
file ( .dmp) from the EMS-ADR zone to the Oracle10 zone of EMS-ADR server.
Also, you must perform the command of database restoration using the "-n
new_schema_name " optional flag.
From the EMS-ADR zone into the ENMConfig directory, enter the command:
scp File_source Login_destination@Ip_destination:/Rep_destination/File
e.g.:
#scp EMS-ADR-Server-Database-2010-06-04-0002.backup.dmp
[email protected]:/sdh_home/oracle10/backupdir/EMS_ADR_Server_Database.dmp
EMS-ADR-Server-Database-YYYY-MM-DD-000n.dmp is the EMS-ADR database
file stored into the /sdh_home/ems/ENMConfig folder of the EMS-ADR zone.
Oracle10 is the login (Oracle zone of the EMS-ADR), you must enter the
password later.
10.66.220.52 is the IP address of the Oracle10 zone of the EMS-ADR
/sdh_home/oracle10/backupdir/ is the path to copy the file.

Page 70/205

EMS_ADR_Server_Database.dmp is the name of the destination file. It is
mandatory to respect this syntax name of the destination file.
Note (2) : Also, in case of Backup 1+1 secure see 8.2.13 - Backup 1+1 of IONOS
NMS servers (Option) , you must perform the command of database
restoration using the "-n new_schema_name " optional flag.
To restore a database coming from an other server / zone, open an Unix window in the Oracle
zone of the EMS-ADR and perform the command from the home directory:
EmsDBRestore -d /sdh_home/oracle10/backupdir -f EMS_ADR_Server_Database.dmp -s
<schema_name> -n new_schema_name
with
<schema_name> is the name of the schema that you will restore into the current schema
<new_schema_name> is the name of the current schema.
e.g.:
[oracle10@z1-M3000 ~] $ EmsDBRestore -d /sdh_home/oracle10/backupdir -f
EMS_ADR_Server_Database.dmp -s z2_primepower n z2_M3000
1.7 - TO SAVE THE EQUIPMENT DATABASES (EXCEPT METERING)

The backup of equipment database is started on Server IONOS-NMS.
In the directory chosen for installation (Ionos-NMS or /tools/IONOS-NMS by default), select the bin
folder.
Run the command : eqpt-backup <login> / <password> start
For example eqpt-backup admin/secret start (with wIndows )
For example /tools/IONOS-NMS/bin/eqpt-backup admin/secret start (with solaris)
The database of all equipment will be uploaded once.
The backup can be interrupted by the following command :
eqpt-backup <login>/<password> stop
For example eqpt-backup admin/secret stop (with windows)
For example /tools/IONOS-NMS/bin/eqpt-backup admin/secret stop (with Solaris)
This command stops the uploads, but the current upload is finished.
The launching of the same command :
eqpt-backup <login>/<password> start
the uploads will be continue, beginning with the first equipment which has not been uploaded.
In the case where the upload is finished, the command stop has no effect.
In the case where the upload is in progress, the command start has no effect.
The backup files are stored :
- on PC in the folder \backup\eqpt of directory chosen for the installation (c:\Program Files\Ionos-NMS by
default).
- on UNIX in the directory /data/IONOS-NMS/db-backup/eqpt.
Note : This backup is available for ADR155C-P2.6, FOTC, ADR155C (release P3 / P4 /P5),
ADR155CPE, ADR155E, ADR63E1, ADR2500C, ADR2500 EXTRA, ADR1000, EXT155HA and
FSP3000.
1.8 - TO EXPORT EQUIPMENT INVENTORY IN A FILE XML

The export of inventory equipment is launched on the Server IONOS-NMS.
bin folder.
Or
Run the command : xmlexport <login> / <password> <file name> <export.xml>

xmlexport <login> / <password> <file name> <exportComplete.xml> (4)
Page 71/205

For example xmlexport admin/secret file.xml export.xml (with Windows )
For example /tools/IONOS-NMS/bin/xmlexport admin/secret file.xml export.xml (with solaris)
The file name with its path (2) must be given. By default the file is created in the bin folder.
The export of inventory allows to list :
- the boards present in equipment
- the software associated to boards
Notes : (1)The path has not to contain "blank".
(2)The export of inventory equipment uses a file of configuration export.xml (in folder
Config/xmlexport). This file can be modified.
(3)This export is available for ADR155C (release P3 / P4 /P5), ADR2500C, ADR155CPE, ADR63E1,
ADR2500 EXTRA, ADR622, ADR10000, EXT155HA., Sagem-Link, SLF-v1, SLF-N, SLF-H, 3P@C
4400, 3P@C 4450, 3P@C 4900, FSP2000 and FSP3000.
(4)The exportComplete is only available for SLF-v1, SLF-N and SLF-H. This is a detailed equipment
inventory.
1.9 - TO EXPORT EQUIPMENT INVENTORY IN A FILE TXT

The export of inventory equipment is launched on the Server IONOS-NMS.
folder.
Run the command : inventoryexport <login> / <password> <file name>
For example inventoryexport admin/secret file.txt (with Windows )
For example /tools/IONOS-NMS/bin/inventoryrexport admin/secret file.txt (with solaris)
The file name with its path (2) must be given. By default the file is created in the Bin folder.
The export of inventory allows to list :
The file can be visualized with a spreadsheet.
Note : (1) The server IONOS-NMS must be started
(2) The path has not to contain "blank".
(3) This export is available for ADR155C (release P3 / P4 / P5), ADR2500C, ADR155CPE,
ADR63E1, ADR2500 EXTRA, EXT155HA, ADR622, Sagem-Link, SLF-v1, SLF-N, SLF-H,
3P@C 4048, 3P@C 4400, 3P@C 4450, FSP2000 and FSP3000.
(4) The action may last a long time according to the number of Network elements
1.10 - TO EXPORT DETAILED EQUIPMENT INVENTORY IN A FILE TXT

The export of detailed inventory equipment is launched on the Server IONOS-NMS. It's only availble for SLFv1, SLF-N, SLF-H equipments.
folder.
Run the command : inventoryexportSLF <login> / <password> <file name>
For example inventoryexportSLF admin/secret file.txt (with Windows )
For example /tools/IONOS-NMS/bin/inventoryrexportSLF admin/secret file.txt (with solaris)
The file name with its path (2) must be given. By default the file is created in the Bin folder.
The export of detailed inventory allows to list :
- the type of link
- the static ODU configuration
- the ODU parameters
Page 72/205

- the channel used
- the IDU parameters
- the RSL
The file can be visualized with a spreadsheet.
Note : (1) The server IONOS-NMS must be started
(2) The path has not to contain "blank".
(3) This export is available for SLF-v1, SLF-H and
SLF-N.
(4) The action may last a long time according to the number of Network elements
1.11 - ALARMS RESYNCHRONIZATION OF IONOS-NMS FOR THE SERVER

NETCOOL
In case of use of a server Micromuse of Netcool, it is possible to launch a resynchronization of alarms
for the alarms present on IONOS-NMS.
In the directory chosen for installation (by default Ionos-NMS on Windows or /tools/IONOS-NMS under
Solaris), select the bin folder.
Run the command : omnibus <login> / <pasword> resynchro
For example /tools/IONOS-NMS/bin/omnibus admin/secret resynchro (under Solaris)
1.12 - TO RUN THE FORCE POLLING SCRIPT

This script is used to perform a Force Polling to all equipments of the network.
It must be run from the IONOS-NMS server.
bin folder.
Run the command : run.bat ./bsh/forcepolling.bsh (with Windows)
Or
Run the command : ./run.sh ./bsh/forcepolling.bsh (with Solaris)
ex:
# ./run.sh ./bsh/forcepolling.bsh
Logging into secure dsServer, please enter the following ...
User name: admin
Password: secret
****************FSP3000 : FSP46****************
force polling on FSP46
Result force polling on FSP46: Timeout
****************FSP2000 : nemi****************
force polling on nemi
Response from nemi
****************FSP3000 : FSP44****************
force polling on FSP44
Response from FSP44
****************ADR155C : Paris****************
force polling on Paris
Response from Paris
1.13 - TO RUN THE ALIGN-NES SCRIPT

Page 73/205

This script is used to re-align the General parameters and the Capability parameter to all Network
Equipments after a migration or an Oracle database merge. (See chapters To migrate a database and
To Merge two IONOS-NMS databases)
It is possible to activate or not a test of accessibility to the Network Elements.
To activate the test of NE accessibility in order to accelerate the process of re-alignment:
bin/bsh folder.
In this folder, open the file align-NEs.bsh and replace the line:
boolean testAccessibility = false;
by
boolean testAccessibility = true;
Save and close the file align-NEs.bsh.
Caution: After the restart of the Ionos-NMS server, it is necessary to wait the end of the polling towards all
NEs before to run the script (the control of the NEs accessibility is done from the Oracle database)
To run the script:

bin folder.
Run the command : run.bat ./bsh/align-NEs.bsh (with Windows)
Or
Run the command : ./run.sh ./bsh/align-NEs.bsh (with Solaris)
Then give the login and password of the user Ionos-NMS and the IP addres of the server.
ex:
# ./run.sh ./bsh/align-NEs.bsh
User name: admin
Password: secret
Host: 10.66.212.122
Logging in as 'admin' on 10.66.212.122
Aligning NE 'Paris' of type ADR155C
- general parameters
Failed to align general parameters! : NE is inaccessible
- capability parameters
Failed to align capability parameters! : NE is inaccessible
Aligning NE 'Nice' of type ADR155C
Aligning NE 'Lyon of type ADR155C
Failed to align general parameters! : NE is inaccessible
...
Aligning NE 'Brest' of type ADR155C
Maintenance finished!
logging of!

Page 74/205
TOPOLOGY MANAGEMENT
2. TOPOLOGY MANAGEMENT
2.1 - INTRODUCTION
Topology administration involves in managing the physical elements of the sub-networks.
This consists in:
creating and positioning the sub-networks and its network elements on a geographic map
with the corresponding optional administrative information.
creating links between these elements with the corresponding optional administrative
information.
The topology function enables creating any type of sub-network hierarchy. Elementary sub-networks
can thus be moved within a main sub-network with the possibility for creating any type of structure.
2.2 - TOPOLOGY VIEW
WINDOW
The Topology View window displays the network map and provides access to the network editing and
administration functions.
Figure 2.1 : Topology Main View

Page 75/205
TOPOLOGY MANAGEMENT
The Topology View window comprises 5 parts:
a menus bar, which gives access to the main function menus of the software: File, Edit, Creation,
Action, Tools, Help.
Use the File menu to perform a backup on line, change password.(except for Ldap users) or
exit the Customer Application
Use the Edit menu to modify data: copy/cut, delete, rename, properties on the various
objects.
Use the View menu to display the various views: Topology View, Log View, NML View and
Admin View.
Use the Creation menu to create a Sub-network, a Network element (NE), an STM-n link, an
Ethernet Link, a VCGroup, an Ethernet service, a WDM link, a WDM Trail.
Use the Action to run the various actions associated to each object.
Uses the Tools menu to define the preferences or access the Software Management.
Use the Help menu to get help or to determine the application version.
a tools bar (under the menu bar), which gives access to the editing functions: create, cut, copy,
paste, delete, show properties.
Use the first icon on the left in the tools bar to create a sub-network, a network element (NE,
VNE) an STM-n link, an Ethernet Link, a VCGroup, an Ethernet service, a WDM Link, a
WDM Trail.
Use the icon "Locks/unlocks the map and tree views" to lock the Topology view and to
prevent any displacement of icon.
Select the "Layer" ("all", "WDM", "SDH", "Ethernet" or "Others") to display the topology view :
only the links belonging to selected layer are displayed. The list of available layers depend
on the type of license.
an explorer (left window, below the tools bar) to obtain the list of sub-networks and network elements.
Use the explorer to locate, select or move an object: each object is animated in accordance
with the alarms present (see 4 :ALARMS MANAGEMENT).
a network elements view (right window, below the tools bar)
Use this window to locate, select edit or move and NE: each object is animated in
accordance with the alarms present (see 4 : ALARMS MANAGEMENT).
a current alarms window at the bottom of the screen.
Use this window to display the current alarms (acknowledged or not, or filtered) received
from the network elements.
Notes:
The user name is displayed in the title bar.

In the Topology View, several sub-networks can be displayed in different
windows (button at top right of window).
By clicking the mouse right button on the icon of a sub-network or a network
element (NE) in the Topology View or in the explorer, a pop-up menu
containing the functions of the tools bar is displayed.
To access a sub-network or a network element, double-click on the
corresponding icons in the Topology View.

Page 76/205
TOPOLOGY MANAGEMENT
2.3 - SUB-NETWORK ADMINISTRATION

2.3.1 - To create a sub-network
This procedure is used to add a new sub-network and place it in the sub-network hierarchy (explorer): a
sub-network continues to be a container for the standard sub-networks and for the network elements
(NE).
In the explorer, select Main View or another sub-network.
In the menus bar, select Creation > Sub-network : the Create Sub-network window is displayed.
Figure 2.2 : Window Create sub-network (1)
In this window, in the Name field, enter a single, mandatory name with no more than 40 characters
for the sub-network.
Select the type of sub-network (default value), ADR2500/1 ADR63E1, ADR2500/2 ADR63E1,
custom1, custom2, custom3, custom4, custom5.
Click [Browse] to select a background image for the sub-network.
Click [Remove] to remove the background image, already selected.
Click [Finish] if you have finished or [Next] if you want to customize certain data: the following screen
is displayed.

Page 77/205
TOPOLOGY MANAGEMENT

In the Customer name field, indicate the customer name (40 characters max.). In the Location
field, indicate the location (40 characters max.), and in the Info field, indicate any other
necessary information (80 characters max.).
Click [Previous] if you want to return to the previous screen or [Finish] if you have finished: The
results window Creation subnetwork action results qui suit s'affiche.

Click [Finish] : the new icon for the sub-network will appear in both the explorer and in the Topology
View window.

Page 78/205
TOPOLOGY MANAGEMENT
Notes:
In this window, the Creation Date", Last Modification Date and User
Name fields are automatically updated.
The customized data are saved in the database and can be modified by
selecting the Properties function (Edit menu or pop-up menu).
In the Topology View window, the name is displayed below the sub-network
icon.
The icon of the sub-network will take the color corresponding to maximum
severity of alarm for all NEs and sub-networks which it contains.
the point of exclamation indicates that the sub-network contains at least
one disaligned NE or a disaligned sub-network;
the question mark indicates that the sub-network contains at least one
potentially disaligned NE or a potentially disaligned sub-network, other NEs
and sub-networks being aligned.
2.3.2 - To display/modify the properties of a sub-network
In the explorer or in the Topology View (Figure 2.1), click left on the sub-network to be displayed or
modified.
In the pop-up menu, select Properties : the Sub-network properties window is displayed with three
tabs.
Figure 2.5 : Window Sub-network properties / General

Page 79/205
TOPOLOGY MANAGEMENT
Use this window to modify the unique and mandatory name (60 characters max.).
Click [Browse] if you want to change the network background image.
Click [Remove] if you want to remove the selected background image.
Click [Finish] if you have finished or click on the Additional Info tab if you want to display or modify
customized data: in this case, the following Sub-network properties window is displayed.
Figure 2.6 : Window Sub-network properties / Additional information
In the Customer name field, indicate the customer name (60 characters max.); in the Location
field, indicate the location (60 characters max.), and in the Info field, any other necessary
information (80 characters max.).
Click [Apply] to validate the modification: a results window is displayed.
Click [Finish] if you have finished or click on the Alarms tab if you want to display the list of alarms of
the NE present in the sub-network.

Page 80/205
TOPOLOGY MANAGEMENT
Figure 2.7 : Window Sub-network properties / Alarms

Notes :
In this window, the Creation Date", Last Modification Date and User
In the Topology View window (Figure
sub-network icon.
2.1), the name is displayed below the
It is possible to display the properties of an alarm: select the alarm in the

alarms table and click right to bring up the pop-up menu. Select properties
.
2.3.3 - To move a sub-network

In the explorer or Topology View (Figure 2.1), click left on the sub-network to be moved.
In the pop-up menu, select Cut.
Click left on the sub-network to which you want to move the selected sub-network.
In the pop-up menu, select Paste : the sub-network selected is pasted to the target sub-network.
Notes:
The links and the network elements are preserved in the sub-network which
has been moved.
You can also use the Drag and Drop technique to move a sub-network to
another sub-network.

Page 81/205
TOPOLOGY MANAGEMENT
2.3.4 - To delete a sub-network
Caution : This operation is only allowed provided the sub-network is empty.
In the Explorer or in the Topology View (Figure 2.1),, click left on the sub-network to be deleted.
In the pop-up menu, select Delete : a confirmation message is displayed.

Click [Yes] to validate the deletion.
2.3.5 - To rename a sub-network

In the Explorer or in the Topology View (Figure 2.1),, click left on the sub-network to be renamed.
In the pop-up menu, select Rename.
Enter a new name in the editing field.
2.3.6 - To change the sub-network background image

In the Explorer or in the Topology View (Figure 2.1), select a sub-network.
In the pop-up menu, select Properties : the Properties window is displayed.
Click [Browse] : the following window is displayed.
Figure 2.8 : Window Open

Using the Look in field, select the folder containing the image.
Select the type of file : *.gif, *.jpg, *.jpeg or *.png and the image file.
Click [Open] to validate the change of image.
Click [Finish] to validate the modification
2.3.7 - To delete the sub-network background image

In the Explorer or in the Topology View (Figure 2.1), select a sub-network
In the pop-up menu, select Properties : the Properties window is displayed
Click [Remove]
Click [Finish] to validate

Page 82/205
TOPOLOGY MANAGEMENT
2.4 - ADMINISTRATION OF NETWORK ELEMENTS (NE, VNE)

2.4.1 - To create a network element
This procedure is used to add a new network element (NE or VNE) and to position it in the sub-network
hierarchy (explorer).
In the Explorer or in the Topology View (Figure 2.1), select a sub-network.
In the menus bar, select Creation > NE : the Create a Network Element window is displayed.
Figure 2.9 : Window Create a network element (1)

Use the fields as follows:
Name to enter the mandatory name (60 characters max.) The name can contain any
alphabetical character except the accentuated alphabetical characters (except if the
configuration of the server allows it - 1.2.3.7 - ) , numbers or spaces.
Note: For a NE type ADR10000, the length of the name is 31 characters max. The Space character is
not allowed.
M1400 name to enter the type M1400 name which comprises a city name (mandatory
name with 12 characters max.) and a suffix (3 characters) : the suffix does not need to be
filled in. The name of city can contain not accentuated alphabetical characters, numbers or
spaces (if configuration of the customer allows it - 1.2.4.4 - ). The suffix contains only
numbers.
Type to enter the equipment type : ADR155C, ADR155CPE, ADR155E, ADR2500C,

ADR2500 EXTRA, ADR622, ADR10000HN, ADR10000, FOT155A, FOT155C, ADR155C P2,
ADR63E1, VNE, FMX, Sagem-Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA, SLF-N,
SLF-H, SLT, SLF-A ,FSP2000, FSP3000, Sagem DTX, SHDSL, 3P@C4048, 3P@C4400,
3P@C4450, 3P@C4900, IP equipment, XP3000.
Page 83/205
TOPOLOGY MANAGEMENT
IP address to enter the IP address (not used for a VNE): if the network element has not
been installed, it will be viewed as inaccessible by IONOS-NMS.
Under Proxy must be activated if the chosen Type of NE is FMX and if it is under a
proxy (board GIEP). In this case, enter the Equip No .
Secondary IP addresses to enter the secondary IP addresses (up to 4 max.; not used
for a VNE or a FMX): to add a new address, click [Add], to delete one, click [Delete].
Figure 2.10 : Window Create NE / Secondary IP Address)

Poll interval to enter the polling interval (by default, 10 min.- 6.2.3 -): in seconds,
minutes or hours. This duration is used to adjust the time interval between two polling
operations to detect any inaccessibility (not valid for a VNE): the value 0 implies that the NE
is not polled.
A value lower than 10 min is not recommended.
Click [Next] when you have filled in the fields: the data customization window is displayed.

In the Customer name field, indicate the customer name (40 characters max.); in the Location
field, indicate the location (40 characters max.), and in the Info field, enter any other necessary
information (200 characters max.).
Click [Previous] if you want to return to the previous screen or [Next] to go to the next screen.
Note:
In this window, the Creation Date , Last Modification Date and User

Page 84/205
TOPOLOGY MANAGEMENT

Use the SNMP Community field to define the SNMP community. Use the Password fields to
define the equipment passwords for the three types of users: supervisor, operator and observer. By
clicking [Default values], the default values defined in the NE preferences are automatically
assigned for each type of NE.(see 6.2.3 -)
Notes :
The "SNMP community" is used to access the equipment by SNMP.

The 3 passwords are used to access the equipment by HTTP browser.
The community and passwords must correspond to those stored in the
equipment; otherwise, it will not be accessible by the IONOS-NMS manager:
the passwords can be modified in the equipment using the SNMP View menu.
see 2.4.13 - To display and modify the SNMP parameters
For a FMX, enter "bmx" for the community and the three passwords.
For a Sagem-Link or a Sagem-Link Light, enter "private" for community,
"passwd4" for the password SUPERVISOR, "passwd2" for password
OPERATOR and OBSERVER.
For a Sagem-Link 2 or a SLF-v1 enter "public" for community, "2345" for the
password SUPERVISOR, "1234" for password OPERATOR and "0" for
password OBSERVER.
For a SLA, enter "private" for community, and "admin" for the passwords.
For a SLF-N enter "secret" for community, "2345" for the password
SUPERVISOR, "1234" for password OPERATOR and "0" for password
OBSERVER.
For a SLF-H enter "secret" for community, "2345" for the password
SUPERVISOR, "1234" for password OPERATOR and "0" for password
OBSERVER.

Page 85/205
TOPOLOGY MANAGEMENT
For a FSP2000 or a FSP3000, enter "private" for community, "private" for the
password SUPERVISOR, "private" for password OPERATOR and "public" for
password OBSERVER.
For an equipment SHDSL, enter "private" for community, "super" for
password SUPERVISOR and OPERATOR, "observ" for password OBSERVER.
Use on IONOS the users "Superviser" and "observer" or create a user
"admin" on equipment SHDSL.
For an equipment DSLAM, enter "secret" for community, "secret" for
password SUPERVISOR, enter "private" for password OPERATOR, "public"
for password OBSERVER.
For an equipment ADR155E enter public for community. For an equipment
ADR10000HN, enter "private" for community. For both types, enter "secret"
for password SUPERVISOR, "private" for password OPERATOR and "public"
for password OBSERVER.
Caution : The Security window is not taken into account for a NE type ADR10000.
If the admin password has been changed from the EMS-ADR, it must be
updated from the PREFERENCES MANAGEMENT (6.2.3 -To change the
default properties of the Nes): In the Default community passwords
section, set the new Password SUPERVISOR for ADR10000 NE type. It will be
common for all ADR10000 in the network.
a/ Click [Create NE] to validate the NE creation for an ADR155C, ADR63E1, ADR155CPE,
ADR155E, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000HN, ADR10000, SLF-A, FSP2000 or
a FSP3000. The results window Create a network element (4) is displayed.

And click [Finish] to finish the operation.
Notes :
When the network element (type ADR155C , ADR63E1, ADR155CPE,

ADR155E, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000HN, ADR10000,
FMX with board GIES, SLF-N, SLF-H, SLF-A, FSP2000 or FSP3000) is created
and is accessible, the IONOS-NMS manager reads the useful information in
the equipment and saves it in the database.
For a NE of type ADR, ADR2500 EXTRA, ADR10000HN, FMX with board GIES,
SLF-N or FSP3000 the manager updates the general parameters in the
equipment : the name of NE (long name), the table of traps (Traps Manager
Dest/IP adress of IONOS-NMS Server), and the variable of traps sending (Logs
Traps Enable). The name of NE is not always updated in according to the
configuration used in the server (see 1.2.3.7 - ). A time set is done
automatically on the NE (with time of Server IONOS-NMS excepted for
ADR155E and ADR10000HN).
For the IONOS-NMS server to receive the traps of the equipment FSP2000
which has just been created, the traps table in the equipment must be
updated with the server IP address. To do so, use the TPI.

Page 86/205
TOPOLOGY MANAGEMENT
For a ADR622, the managed cards are: TSI, CCU-622, CTRL-622, AUX-622,
GFP150-622, GFP2500-2GE, GE-DM, 2XSTM1-SFP, 42E1, 42E1FA, 3E3DS3,
3E3DS3FA, LTUE120P, LTUE75P, LTU3E3DS3-622, FAN622 and STM1/4
Caution: in the case of use of Proxy HTTP, to guarantee the access security to
the equipment, it is possible to update with browser HTTP the table of
managers address IP in each NE created of type ADR155C, ADR63E1,
ADR155CPE, ADR2500C, ADR2500 EXTRA or ADR622: to add IP address of
the server in the table of the managers with rights "Supervisor".
In the Topology View Figure 2.1, and in the explorer, the icon of the NE
created is displayed in the color corresponding to its alarm degree and with
its name written below:
The exclamation point means that the equipment is misaligned;
The question mark means that the equipment is potentially misaligned.
The icon of the sub-network will take the color corresponding to
degree of all NEs and sub-networks which it contains.
alarm
the point of exclamation indicates that the sub-network contains at least

one disaligned NE or a disaligned sub-network;
the question mark indicates that the sub-network contains at least one
potentially disaligned NE or a potentially disaligned sub-network, other NEs
and sub-networks being aligned.
b/ Click [Next] for a VNE, a FOT155A, a FOT155C, a FMX, a Sagem-Link, a Sagem-Link Light, a
Sagem-Link 2, a SLF-v1, SLA, SLF-N, SLF-A, Sagem DTX, SHDSL, DSLAM, IP equipment or an
ADR155C P2. The following window is displayed.
Use this window to define the NE resources: click [Add container] or [Add Interface] to respectively
add a container or an interface to the network element created (only valid for FOT155A, FOT155C,
Page 87/205
TOPOLOGY MANAGEMENT
ADR155C P2, FMX, Sagem-Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H,
SLF-A , Sagem DTX, SHDSL, IP equipment, DSLAM and VNE).
Notes :
The [Add Container] button is used to create:

. a rack after having selected an NE/VNE,
. a shelf after having selected a rack ,
. a card after having selected a shelf .
The [Add Interface] button is used to add:
. a rack , a shelf , a card and an interface under card after
having selected an NE/VNE,
. a shelf , a card and an interface under card after having
selected a rack ,
. a card and an interface under card after having selected a
shelf .
. an interface under card after having selected a card .
Click [Create NE] to validate the creation. The results window Create a network element (6) is
displayed.

And click [Finish] to finish the operation.
Caution : When the network element (type FOTC, ADR155C P2, FMX, Sagem-Link,
Sagem-Link Light, Sagem-Link 2, SLF-v1, SLF-N, SLF-H, SLA, Sagem DTX,
SHDSL, DSLAM, IP equipment ) is created and accessible, the IONOS-NMS
manager reads the useful information in the equipment.
For the IONOS-NMS server to receive the traps of the equipment which has
just been created, the traps table in the equipment must be updated with the
server IP address. To do so, use the HTTP browser or the TPI.
FMX-GIES (1) : For a FMX-GIES, to get the inventory of Ethernet board, it is necessary to
create and fill the c:\Program Files\Ionos-NMS\tpifmx\backup\carteETH.lst file.
See below,

Page 88/205
TOPOLOGY MANAGEMENT
One line per board, with :
<long name of FMX>=<slot number>,ETH
Example of carteETH.lst file:
FMX5=3,ETH
FMX6=4,ETH
FMX7=3,ETH
Otherwise, the Ethernet Boards are indicated as empty in Ionos-NMS.
(2) At the end of FMX-GIES creation, a NE database backup is done in order to

get the inventory.
2.4.2 - To copy a network element (NE, VNE)

In the explorer or in the Topology View, click left on the network element to be copied.
In the pop-up menu, select Copy.
Click left on the sub-network to which you want to copy the selected network element.
In the pop-up menu, select Paste : the network element selected is copied to the target sub-network
and the Create NE window is displayed.
Perform the same procedures used to create a network element ( 2.4.1 -.)
Note :
Except for the network element type, all the parameters of the new network
element can be modified.
2.4.3 - To move a network element (NE, VNE)

In the explorer or in the Topology View (Figure 2.1), click left on the network element to be moved.
In the pop-up menu, select Cut.
Click left on the sub-network to which you want to move the selected network element.
In the pop-up menu, select Paste : the network element selected is pasted to the target sub-network.
Notes :
The links of the network element moved are preserved.

You can also use the Drag and Drop technique to move a network
element.
2.4.4 - To delete a network element (NE, VNE)

Caution :
This operation is only allowed provided the resources (trails, links) of the
network element are not used.
In the explorer or in the Topology View (Figure 2.1), click left on the network element to be deleted.
In the pop-up menu, select Delete : a confirmation message is displayed.
Note :
When the operation is confirmed, the data of the network element are deleted
from the database.

Page 89/205
TOPOLOGY MANAGEMENT
If the element is not managed by the IONOS-NMS, the traps table in the
equipment must be updated by removing the IP address from the server. Use
the HTTP browser for this purpose.
2.4.5 - To rename a network element (NE, VNE)

In the explorer or in the Topology View (Figure 2.1), click left on the network element to be renamed.
In the pop-up menu, select Rename.
Enter a new name in the editing field ( any alphabetical character except the accentuated alphabetical
characters, numbers and spaces).
2.4.6 - To display and modify the properties of a network element

In the explorer or in the Topology View (Figure 2.1), click left on the network element to be displayed
and modified.
In the pop-up menu, select Properties : the NE Properties window is displayed.
Figure 2.16 : Window Network Element properties

a/ Select the General tab if you want to modify:
the name (60 characters max.). This name can contain any alphabetical character except the
accentuated alphabetical characters (except if the configuration of the server allows it -
1.2.3.7 - ), numbers or spaces.
the unique M1400 name, which comprises a city name (12 characters) and a suffix (3
characters) : the suffix does not need to be filled in. The name of city can contain not
accentuated alphabetical characters, numbers or spaces (if configuration of the customer
allows it - 1.2.4.4 - ). The suffix contains only numbers.

the equipment type cannot be modified.

the IP address (not used for a VNE): if the network element has not been installed
beforehand, it will be inaccessible.

Page 90/205
TOPOLOGY MANAGEMENT
The Equip.No for a FMX with card GIEP.
the secondary IP addresses (up to 4 max., not used for a VNE). To add a new address, click
[Add].
the polling interval (by default, 10 min - 1.2.3.3 - ) : in seconds, minutes or hours. This
duration is used to adjust the time interval between two polling operations to detect NE
inaccessibility (not valid for a VNE): the value 0 implies that the NE will not be polled.
b/ Select the Additional Information tab to customize certain data (see 2.4.1 - Creation of a
network element).
c/ Select the Security tab to modify the equipment community and equipment passwords for the
three types of users (supervisor, operator and observer) in the Password fields (see 2.4.1 Creation of a network element).
d/ Select the Alarms tab to display all the alarms of NE.
Figure 2.17 : Window Network Element properties / Alarms
e/ Select the Inventory tab to read/modify the inventory:

Click [Add container] to add a container (only valid for FOT155A, FOT155C, ADR155 P2,
FMX, Sagem-Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H, SLF-A,
Sagem DTX, SHDSL, DSLAM, IP equipment and VNE).
Click [Add Interface] to add an interface to the network elements (only valid for FOT155A,
FOT155C, ADR155 P2, FMX, Sagem-Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA,
SLF-N, SLF-H, SLF-A, Sagem DTX, SHDSL, DSLAM, IP equipment and VNE) (see 2.4.1 Creation of a network element).
Click [Add Interface] to add an interface of type "OTHER" on any card (valid for all type of
NE).
Click [Apply] to validate the modifications.

Notes :
In the Topology View, the name is displayed below the NE icon, whereas the
M1400 name is only displayed when the mouse pointer is placed on the icon.
The NE can also be selected in NML View.

Page 91/205
TOPOLOGY MANAGEMENT
2.4.7 - To modify the M1400 name of a network element (NE, VNE)
In the explorer or in the Topology View (Figure 2.1), click left on the network element to be modified.
In the pop-up menu, select Properties : the NE Properties window is displayed.
Figure 2.18 : Window Network Element properties

Select the General tab and modify the M1400 name :
the unique M1400 name comprises a city name (12 characters) and a suffix (3 characters) :
the suffix does not need to be filled in. The name of city can contain not accentuated
alphabetical characters, numbers or spaces (if configuration of the customer allows it - 1.2.4.4
- ). The suffix contains only numbers.

If Links (STM-n Links, no-STM-n Links, Ethernet, WDM), trails SDH, trails WDM, VCGRoups, Ethernet
services are present on, a confirmation window is displayed.
Figure 2.19 : Window Rename NE M1400 name (1)
Confirm the modification ("Yes") : the results window is displayed.

Page 92/205
TOPOLOGY MANAGEMENT

Double-to click on the line of result (or click on [Details]) to obtain the results, in particular the list of
cross-connections and bridging points renamed in each NE, following the renaming of the trails,
bearers, Ethernet services present in IONOS-NMS.

Page 93/205
TOPOLOGY MANAGEMENT
Close all the windows (with [Close]), then close the Properties window (with [Cancel])
Notes :
On modification of the M1400 name of a NE :

the name of the links which finish on it (STM-n Links, Ethernet Links, WDM
Links and no-STM-n Links) is modified
- the name of the bearers, trails and VCGroups which finish on it is modified.
For the bearers and the trails activated or partially activated, the name of
cross-connections is modified in equipment.
- the name of Ethernet services which finish on it is modified. For the
Ethernet services activated or partially activated, the name of bridging
points is modified in equipment.
- The name of Trails WDM which finish on it is modified.
In the window Topology View, the M1400 name is displayed if you move the
pointer of mouse on the NE icon.
If the type of NE is EXT155HA, the modifications are done in the two
physical NEs.

Page 94/205
TOPOLOGY MANAGEMENT
2.4.8 - To audit a network element (NE)

Caution : This operation is not valid for virtual network elements (VNE), FOT155A,
FOT155C and multiplexers ADR155C P2 and FMX, Sagem-Link, Sagem-Link
Light, Sagem-Link 2, SLF-v1 , SLA equipment, DSLAM equipment, SHDSL
equipment, Sagem DTX equipment, IP equipment . it is valid for SLF-N, SLF-H,
and for a FMX with card GIES, tab General.
This task is used to check the differences in general parameters, cards, "cross-connections", MSP
protection MS-Spring protection and monitoring between the database of the NE and that of the IONOSNMS manager.
In the explorer or in the Topology View (Figure 2.1), click left on the network element to be checked.
In the pop-up menu, select Audit : the Audit Results window is displayed.
Notes :
If there is an inconsistency between the manager data and the NE data, the
audit line is displayed red: a message at the top left of the window will then
indicate that the NE is not aligned.
At the end of the audit, an ( !) is displayed on the NE icon.
If the type of NE is EXT155HA, the audit must be launched on one of two
physical NEs (Working or Protection). Launch before the menu Show
physical NEs.
a/ Select the General tab to display the general parameters

the name of NE
the indication (#Yes or No) of inscription of the IP address of IONOS-NMS server in the table
of the receivers of traps of NE + case "log traps enable" ticked (by HTTP, menu
Equipment/Management)
the indication of inscription in Supervisor mode of IP address IP of server IONOS-NMS in the

table of the Managers of NE (always Supervisor in NMS, Supervisor in NE if the table of the
managers is empty, or if the IP address of IONOS-NMS Server is registered in Supervisor)
(by HTPP, menu Equipment/Management).
The parameters of performance collect (ADR155C P4.1 and ADR25000 EXTRA P2.1
only, ADR622):
- Start 24h count time (hour top 24h)
- Tolerance Date : tolerance of time set on performances (in secondes)rance de
remise l'heure sur les performances (en seconds)
- Nea correlation Enable (mode Near correlation activ ou non in equipment)
- Performance Threshold Trap Enable (send of threshold trap or not)
The values of these parameters can be modified in the flle "server.xml" in folder Config of
application (see 1.2.3.10 - ).
The parameters associated with ethernet service (ADR25000 EXTRA P2.2 only with GFP
card):
- MSTP configuration
- Traffic Class Configuration
the indication of VC12 cross-connecting switch.
the possibility to manage NUT channels (ADR2500C or ADR2500 EXTRA only)
the maximum of LO monitored points (the maximum is 28 for equipment of type ADR2500C
or ADR2500 EXTRA with a VC12 cross-connecting switch).
Page 95/205
TOPOLOGY MANAGEMENT
the maximum of LO monitored points (the maximum is 1008 for equipment of type ADR622 with a
VC12 cross-connecting switch).
The possibility to manage the mode SNC/N (ADR155 P4.1 only, ADR2500 EXTRA P2.2
and ADR622)
The possibility to manage the bridging points (ADR155C P4.1 rev AF or ADR25000
EXTRA P2.1 only with card GFP, ADR622 with card GFP).
The possibility to manage MSTP for Ethernet services (ADR2500 EXTRA P2.2, only with
GFP card, ADR622 with card GFP)
The possibility to manage the sharing EVP-Line/LAN Support for Ethernet services
(ADR2500 EXTRA P2.2 only with GFP card, ADR622 with card GFP)
The possibility to manage the probes of continuity-check OAM-CC Support for Ethernet
services (ADR2500 EXTRA P2.2 only with GFP card, ADR622 with card GFP)
The possibility to manage the Tandem Connection sur les trails VC4 et VC3 (ADR2500
EXTRA P2.2 only, ADR622 with card GFP).

The possibility to configure RS Path Trace for SDH links

Standby support : this function is available with version ADR155C P5.5, ADR2500 EXTRA
version P3.0.5 and not supported on ADR622
Note :
For a FSP2000, the tab "General" is empty.
b/ Select the Inventory tab, then:

the Cards tab to display the cards of an NE: shelf no., shelf name, type of card family and
card type.
the MSPs tab to display the MSP protections.
c/ Select the Cross-Connections tab to display the cross-connections activated (not

available for FSP2000 and FSP3000).
d/ Select the Bridging points tab to display the "switch" activated on GFP cards and used for
Ethernet services.
e/ Select the VCGroup tab to display the VC of activated VCGroups in which trails are
allocated.
f/ Select the Monitoring tab to display all the points checked relative to the STMn link created, to
the activated Ethernet links, to the activated WDM links, to the activated cross-connections, to the
activated Ethernet services, to the activated WDM trails and to activated ring (ADR2500C or
ADR2500 EXTRA only).
g/ Select the MS-SPRing tab to display the MS-SPRing protection parameters: the window
displays all the protection rings (ADR2500C or ADR2500 EXTRA only).
h/ Select the ETH/VCG ports tab to display the Ethernet/VCG ports parameters, relative to the
activated Ethernet links and VCGRoups (ADR2500 EXTRA P2.2 only, ADR622).
i/ Select the MEPIDs tab to display the identifications of GFP cards used by continuity-check
probes (sink) of activated ethernet service (ADR2500 EXTRA P2.2 only, ADR622).
j/ Select the Continuity-check probes to display the continuity-check probes (source and sink)
of activated ethernet services(ADR2500 EXTRA P2.2 only, ADR622).
k/ Select the SDH Ports to display the configuration of the ports involved in activated RS Path
Trace
Page 96/205
TOPOLOGY MANAGEMENT
Figure 2.26 : Window Audit Results / General
Figure 2.27 : Window Audit Results / Inventory / Cards

Page 97/205
TOPOLOGY MANAGEMENT
Figure 2.28 : Window Audit Results / Inventory / MSPs
Figure 2.29 : Window Audit Results / Cross-connections

Page 98/205
TOPOLOGY MANAGEMENT
Figure 2.30 : Window Audit Results / Bridging points
Figure 2.31 : Window Audit Results / VCGroups

Page 99/205
TOPOLOGY MANAGEMENT
Figure 2.32 : Window Audit Results / Monitoring
Figure 2.33 : Window Audit Results / ETH/VCG ports

Page 100/205
TOPOLOGY MANAGEMENT
Figure 2.34 : Window Audit Results / MEPIDs
Figure 2.35 : Window Audit Results / Continuity-check probes

Page 101/205
TOPOLOGY MANAGEMENT
Figure 2.36 : Window Audit Results / SDH Ports
Figure 2.37 : Window Audit Results / MS-SPRING

Page 102/205
TOPOLOGY MANAGEMENT
In the Audit Results / MS-SPRING window, you can display the details of a protection ring by clicking
[Detail] : the window displayed has 4 tabs :
The General tab lists the general parameters of the MS-SPRing protection,
The Topology tab lists the topology table for the equipment,
The NUT tab lists the table of channels structure.
The Misconnection tab lists the table used to generate the SIA signal in the failed trails in
the event of a multiple failure.
Figure 2.38 : Window Audit Results / MS-SPRing / Detail

Click [Close] to close the current window.
Note :
(1) For a FMX-GIES, the Inventory tab is present if the variable

"isFmxInventoryLikeVne" is set to false in the server-advanced file. (see
1.2.3.37 - To configure the FMX backup configuration file)
(2) For a FMX-GIES, the Inventory tab is updated when a NE database is
successfully done. See Figure 2.39 : Window Audit Results / FMX
inventory

Page 103/205
TOPOLOGY MANAGEMENT
Figure 2.39 : Window Audit Results / FMX inventory
2.4.9 - To reapplicate the general parameters in a network element (NMS to NE)
Caution :
This operation is not valid for virtual network elements (VNE), FOT155A,
Light, Sagem-Link 2, SLF-v1 , SLA equipment, DSLAM equipment, SHDSL
equipment, Sagem DTX equipment, IP equipment. This operation is valid for
SLF-N, SLF-H, SLF-A, or FMX with ard GIES, tab General.
This task allows to reapplicate the general parameters (name of NE, inscription of IP address of
IONOS-NMS server in the table of receivers of traps of and updated of variable "Log Traps Enable") in
the NE.

Page 104/205
TOPOLOGY MANAGEMENT
Figure 2.40 : Window Audit / General Reapplication

Select the General tab to reapplicate the general parameters.
Notes :
indicate that the general parameters are not aligned.
Click [NMS to NE general parameters reapplication] to launch the reapplication of general

parameters in the NE : the results window is displayed.
Figure 2.41 : Window General Parameters Reapplication Results

Page 105/205
TOPOLOGY MANAGEMENT
Double-to click on the line of result to obtain the details of reapplication for general parameters.
Figure 2.42 : Window General Parameters Reapplication Results/Details

Click [Close] and [Finish] : the General tab is updated after the reapplication.
Notes :
The table of the Managers is not updated automatically. It must be updated

manually by using HTTP browser.
The long name can not be updated in the equipment according to the used
configuration (see 1.2.3.7 - ).
For a NE of type EXT155HA, the parameters are updated in the physical NE
on which the menu Audit has been launched (Working or Protection).
2.4.10 - To align the capacity parameters from a network element (NE to NMS)
Light, Sagem-Link 2, SLF-v1 , SLA, SLF-N, SLF-H, SLF-A, equipment, DSLAM
equipment, SHDSL equipment, Sagem DTX equipment, WDM FSP2000
equipment, IP equipment .
This task allows to align the capacity parameters (indication of a VC12 cross-connecting switch,
management of NUT channels, maximum number of LO monitored points, management of SNC/N
mode, management of bridging points for Ethernet services, MSTP support, EVP-Line/LAN support,
OAM-CC support, Tandem Connection support) in IONOS-NMS.
Figure 2.43 : Window Audit / Capacity parameters Alignment

Page 106/205
TOPOLOGY MANAGEMENT
Select the General tab to align the capacity parameters.
Notes :
indicate that the capacity parameters are not aligned.
Click [NE to NMS capabitlity parameters alignment] to launch the alignment of the capacity
parameters in IONOS database : the results window is displayed.
Figure 2.44 : Window General capability parameters alignment Results

Double-click on the result line to obtain the details of capability parameters alignment.
Click [Close] and [Finish] : the General tab is updated after the alignment.
2.4.11 - To perform an inventory alignment for a network element (NE)

Light, Sagem-Link 2, SLF-v1 , SLA, SLF-N, SLF-H, SLF-A, equipment, DSLAM
equipment, SHDSL equipment, Sagem DTX equipment, IP equipment .
This task is used to align the inventory of an NE (cards and MSP protections) in the manager with the
actual database of the NE.
In the pop-up menu, select Audit : the configuration Audit Results window is displayed.

Page 107/205
TOPOLOGY MANAGEMENT
Figure 2.45 : Window Audit / Inventory Alignment

Select the Inventory tab.
Select the Cards sub-tab to align the cards.
Note :
If there is an inconsistency between the manager data and that of the NE in

the inventory, the audit line is displayed red: a message at the top left of the
window in the inventory tab will indicate that the cards are not aligned.
For a NE of type EXT155HA, the alignment command must be launched on
the physical NE. Activate before the menu Show Physical NEs to launch the
Audit.
Ciick [NE to NMS Inventory alignment] to launch an NE inventory alignment to the manager: the
result window is displayed with the list of basic actions (Insert Card, Delete Card, Update Card).
Figure 2.46 : Window Inventory Alignment Results

Click [Close] and [Finish]: the Inventory tab is updated after the alignment.

Page 108/205
TOPOLOGY MANAGEMENT
Notes :
A card can only be deleted provided its interfaces are free (no Link, no
VCGroup, no trail, no service Ethernet ).
A card can always be replaced by a card of an equivalent family (For ADR2500
: 4STM1_ELEC and 4STM1_OPT, for ADR155C : ADRSTM1_OPT and
ADRSTM1-ELEC).
A card can be replaced by a card of a different family provided its interfaces
are free (no Link, no VCGroup, no trail, no service Ethernet).
Following the audit, when the NE is aligned, the exclamation point ( !) or the
question mark ( ?) disappears from the NE icon.
2.4.12 - To display and modify the configuration of an equipment

Caution : This operation is not valid for the VNEs.
In the explorer or in the Topology View (Figure 2.1), click left to select the network element to be
displayed: you can obtain the equipment configuration directly by double-clicking.
In the pop-up menu, select Equipment View : the graphic application is started up and displays the
equipment configuration.
Notes :
For the ADR155C, ADR63E1, ADR155CPE, ADR2500C, ADR2500 EXTRA or

ADR622, ADR10000HN, EXT155HA equipment, the Equipment View function is
validated, the HTTP browser is initiated via the HTTP PROXY installed on the
IONOS-NMS Server which activates the HTTP server integrated in the
equipment in accordance with the user profile (see 1.2.4.2 - et 1.2.4.3 - ).
For an EXT155HA, ADR155C P2.6, ADR155E and ADR10000HN, the HTTP
PROXY cannot be used.
For ADR155E, the FMX equipment, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H,
equipment and FSP2000, FSP3000 equipment, when the Equipment View
function is validated, the LCT Application is launched (installed beforehand).
For ADR10000, when the Equipment View function is validated, the ADR10000
proxy is launched.
For the FOT155C equipment, when the Equipment View function is validated,
a customer application is initiated and uses the SNMP protocol and the
associated MIB to communicate with the equipment in accordance with the
user profile.
For the Sagem-Link and Sagem-Link Light Equipment, when the Equipment
View function is validated, a customer application is initiated and uses the
SNMP protocol and the associated MIB to communicate with the equipment in
accordance with the user profile.

Page 109/205
TOPOLOGY MANAGEMENT
Figure 2.47 : Window SAGEM-LINK Equipment View
Figure 2.48 : Window SAGEM-LINK LIGHT Equipment View
For the SLF-A the Mozilla Firefox browser must be installed on the PC client.
Figure 2.49 : Window SLF-A Equipment View

Notes: For a FMX-GIES, if the the variable "isFmxInventoryLikeVne" is set to true in the server-advanced file
(see 1.2.3.37 - SYSTEM INSTALLATION AND MANAGEMENT), it is possible to add container(s) and
interface(s), otherwise the FMX inventory is automatically discovery.
Page 110/205
TOPOLOGY MANAGEMENT
Click [Add container] to add a container.
Click [Add Interface] to add an interface to the network elements.
Click [Add Interface] to add an interface of type "OTHER" on any card.

Note :
(1) For a FMX-GIES, the Inventory tab is updated if the variable

"isFmxInventoryLikeVne" is set to false in the server-advanced file. (see
1.2.3.37 - SYSTEM INSTALLATION AND MANAGEMENT) and when
a NE database is successfully done. See Figure 2.50
Figure 2.50 : Window Network Element properties / FMX Inventory
2.4.13 - To display and modify the SNMP parameters

This procedure is only valid for ADR equipment (ADR155C, ADR155CPE, ADR63E1, EXT155HA,
ADR2500C, ADR2500 EXTRA or ADR622) in accordance with the user profile (administrator, operator
or observer).
In the explorer or in the Topology View, click left to select the network element for which you want to
display the SNMP parameters.
In the pop-up menu, select SNMP View (see the tables in Appendix "SNMP view table").
Select MIB II to display and modify the tables of MIB II : System Info, IP Info, IP Addresses,
Interfaces, Routing Tables.
Select Equipment (1) to display the tables of the equipment MIB: Security, Traps, Up and
Download, Manager Table.
Select Session to display and modify the session tables.

Page 111/205
TOPOLOGY MANAGEMENT
Figure 2.51 : Example of SNMP View Window

Click [Refresh] to refresh the table (2).
Modify the values as desired (3).
Click [Apply] to validate the new configuration.
Notes :
(1) To modify the equipment parameters, you must have an administrator

profile.
(2) Use the [Stop] button to stop the table refresh procedure.
(3) Only the parameters displayed in blue can be modified: double-click on
these parameters to modify them.
2.4.14 - To Back up the database of a network element

This procedure is used to back up the database of a NE of type ADR155C P2, ADR155C, ADR63E1,
ADR155CPE, ADR155E, ADR10000HN, ADR10000, EXT155HA, ADR2500C, ADR2500 EXTRA,
ADR622, FSP3000 and FOTC.
In the explorer or in the Topology View (Figure 2.1), click left to select the network element for which
you want to back up the database.
In the pop-up menu, select NE database backup : a message of confirmation is displayed.
Confirm the operation to launch the backup of the data (1) : the result window is displayed.
Figure 2.52 : Window Network Element Backup Results

Page 112/205
TOPOLOGY MANAGEMENT
Click [Finish] to close the window, when it is finished.
Notes :
(1) The TFTP server must be launched as a preliminary on the machine used
(2)The backup is done in the repertory, specified in the file
"Equipementbackup.xml" contained in the folder Config of the repertory
chosen for the installation (by default c:\Program Files\IonosNMS\Backup\Eqpt under Windows and /data/IONOS-NMS/Backup/Eqpt under
Solaris).
The file is stored under the repertory yyyy/yyyy-mm/yyyy-mm-dd.
The name of the file is form:
NEdatabase-M1400 name-addresses IP-YYYY-MM-DD.
(3) For the ADR155C, ADR155CPE, EXT155HA and ADR63E1 two files are
generated (db and net).
For the EXT155HA, the command must be launched on each physical NE
(Working and Protection).
For the ADR2500C and ADR2500 eXtra, ADR622, ADR155E and ADR10000HN,
only one file is generated (db).
For the FSP3000, only one file is generated (dbs).
For a FMX-GIES, there are two generated files (.tpi and .lst)
(4) If the backup is not finished correctly with a status "Unknown error",
modify the value of SNMP time-out in the Preferences of NE ("SNMP requests
configuration for all NEs " in menu Tools/Preferences/NE). Put by example
60s instead of 30s. and do again the backup.
ADR10000: (1) The FTP server must be launched as a preliminary on the machine used
(2) The backup is done in the repertory, specified in the file
"Equipementbackup.xml" contained in the folder Config of the repertory
chosen for the installation (by default c:\Program Files\IonosNMS\Backup\Eqpt under Windows and /data/IONOS-NMS/Backup/Eqpt under
Solaris).
The files are stored under the repertory yyyy/yyyy-mm/dd.
There are two files and the name of the files is form:
NEDatabase-M1400 name- IP address-YYYY-MM-DD-nnnn.db and .install
nnnn is the index of the file.
(3) In case of Backup 1+1 secure see 8.2.13 - Backup 1+1 of IONOS
NMS servers (Option) , the NE database is also transferred to the remote
Ionos-NMS server.
FMX-GIES: (1) For a FMX-GIES, in case of backup failed, the result window is displayed
with a failed result after the time-out configured in server-advanced.xml file
("FMXBackupTimeout" variable). See Figure 2.53.
Figure 2.53 : Window Network Element Backup failed result

Page 113/205
TOPOLOGY MANAGEMENT
Also, a critical alarm is displayed in the Fault View with a Backup FMX
missing event type. See Figure 2.54.
This alarm automatically disappears when the FMX backup is done
successfully.
Figure 2.54 : Window Critical FMX backup missing alarm in Fault View
FMX-GIES): (2) For a FMX-GIES, when a modification of configuration (provisioning,
cross-connections ) is done, a warning alarm is displayed in the Fault View
with a Configuration Changed event type. It appears at the next FMX
database backup. See Figure 2.55.
Figure 2.55 : Window Warning Configuration Changed alarm in Fault View
2.4.15 - To restore the database of a network element

This procedure is used to restore the database of a NE of type ADR155C P2, ADR155C, ADR63E1,
ADR155CPE, EXT155HA, ADR155E, ADR2500C, ADR2500EXTRA, ADR622, ADR10000HN,
FSP3000 and FOTC.
In the explorer or in the Topology View (Figure 2.1), click left to select the network element for which
you want to restore the database.
In the pop-up menu, select NE database restore : a message of confirmation is displayed.
Confirm the operation : the list of the files available is displayed.
Figure 2.56 : Window Network Element Restoration

Select one of lines (1) and click [Restore] to launch the restoration of data (2): the result window is
displayed.
Page 114/205
TOPOLOGY MANAGEMENT
Figure 2.57 : Window Network Element Restoration Results

Click [Finish] to close the window when it is finished.
Launch an audit of the equipment to align parameters if necessary.
Notes :
(1) In the name of the file, the "/" of M1400 name is replaced by a "(".
(2) The TFTP server must be launched as a preliminary on the machine used
(3) For the EXT155HA, the command must be launched on each physical NE
(4) If the restoration is not finished correctly with a status "Unknown error",
modify the value of SNMP time-out in the Preferences of NE ("SNMP requests
configuration for all NEs " in menu Tools/Preferences/NE). Put by example
60s instead of 30s. and do again the restoration.
2.4.16 - To restore the database of ADR10000

You have to use the ADR10000 Proxy (EMS-ADR) to restore the NE database.
Refer to the main document Element Management System for ADR Platforms version 7 N 253 216 157A or EMS-ADR User Manual version 8.1 N 253 359 465-A Upgrading NE software To update a
software of a selected NE, Load DB to NE option.
Note : (1) Use Load DB to NE option to restore the last NE backuped database.
Note : (2) To restore another NE backuped database, you have to copy first the two files (
.db and .install) from the IONOS-NMS server to the EMS-ADR server with its IP
address instead of its name.
From the IONOS-NMS server into the backup directory, enter the command:
scp File_source Login_destination@Ip_destination:/Rep_destination/File
e.g.:
#scp NEDatabase-ADR10K-2009-09-16-0001.install
[email protected]:/sdh_home/ems/DownLoad/DB05.8120/50.0.0.1.install
ADR10K-2009-09-16-0001.install is the NE database file stored into the
/data/IONOS-NMS/backup/eqpt/yyyy/yyyy-mm/dd folder of the main server
or into the /tools/IONOS-NMS/securelog/<Ip address of the main
server>/backup/eqpt/yyyy/yyyy-mm/dd folder of the Backup server
ems is the login (EMS-ADR), you must enter the password later.
10.0.01 is the IP address of the EMS-ADR
Page 115/205
TOPOLOGY MANAGEMENT
/sdh_home/ems/DownLoad/DB05.8120/ is the path to copy the file
50.0.0.1.install is the name of the destination file using the IP address of the
NE instead of its name
You have to apply the same procedure to copy the .db file.
Caution with EMS-ADR R7.2 : The label of cross-connection are not recovered following
a NE database restoration from the EMS-ADR in R7.2 version.
To restore cross-connection labels, launch an audit, select the
Crossconnections tab and click on the Global NMS to NE crossconnections
re-activation button to launch the reactivation of all cross-connections in the
NE.
To restore cross-connection labels from the EMS-ADR R7.2, select a NE and
open the Shelf View, and on the menu bar select System Import XC. The XC
labels of all NE will be restored.
2.4.17 - To update the software on a network element

This procedure is used to manage the software installed on the network. It provides the administrator
with the version installed on the NE and allows the administrator to update the version.
In the menus bar of the Topology View (Figure 2.1), click Tools > Software Management : the
Software Management window is displayed.
Figure 2.58 : Window Software Management window

Select the mode in which you want to work by ticking the corresponding button:
a/ Inventory to read the inventory
b/ Update to download a new software in the reserve location.
c/ Switch to switch the reserve software to the current software.
Note : The "Update" is the most complete mode.
Page 116/205
TOPOLOGY MANAGEMENT
a/ Inventory mode
Click [Browse] to select, in the tree, the sub-network or NE on which you want to work.
Tick the equipment type selected : ADR155C, ADR2500C, ADR63E1, EXT155HA, ADR2500 EXTRA,
ADR622, FSP2000, FSP3000, ADR155CPE, ADR155E, XP3000, 3@Pack 4400, 3@Pack 4048,
3@Pack 4450, 3P@C 4900, SLF-H.
Give the soft type:
For an ADR155C equipment, Mother Board, ADRIMA Board, ADRLAN Board, or ADRGFP
Board
For an ADR2500C equipment, CTRL Board, GIG-E Board, FPGA, HTTP Custom, Default
Config
For an ADR63E1 equipment, Mother Board only
For an ADR155CPE, Mother Board
For an EXT155HA, Mother Board only
For an ADR2500 EXTRA, Shelf Pack, Gig-E Pack, or GFP150-eXtra
For an ADR622 equipment, SHELF Pack ACTIVE, SHELF Pack STANDBY, GFP150-622
ACTIVE, GFP150-622 STANDBY, GFP2500-2GE ACTIVE, GFP2500-2GE STANDBY
For a FSP2000, NEMI only
For an ADR155E, Program pack only
For 3@Pack 4400, XDU and OS
For 3@Pack 4048, GTIOOCT and OS
For SLF-H , Program pack, ODU1 and ODU2
The switch type is given automatically; according to the soft type.
Click [Show list] : the inventory of the various current and reserve software versions is
automatically displayed for the equipment selected.
Click [End session] when you have finished.

Page 117/205
TOPOLOGY MANAGEMENT
Figure 2.59 : Window Software Management window / Inventory

Notes :
For an EXT155HA, the inventory is displayed for the two Physical NEs
b/ Update mode
Tick the equipment type selected : ADR155C, ADR2500C, ADR63E1, EXT155HA, ADR2500 EXTRA,
ADR622, FSP2000, FSP3000, ADR155CPE, ADR155E, 3@Pack 4400, 3@Pack 4048, 3@Pack
4450, 3@Pack 4900, SLF-H
Give the soft type:
Board
For an ADR2500C equipment, CTRL Board, GIG-E Board, FPGA, HTTP Custom, Default
Config
For an ADR155E, Program only
For 3@Pack 4048, GTIOOCT and OS
For SLF-H , Program pack, ODU1 and ODU2

Page 118/205
TOPOLOGY MANAGEMENT
Click [Browse] on the line of selected equipment to select the software to be downloaded.
Click [Download] to run the downloading operation: the results are displayed in the Result area.
Notes :
The downloading will take place if the version to be downloaded is already

present in the current or reserve list (Button [Reserve download]).
The TFTP server must be launched as a preliminary on the machine used like
IONOS-NMS server.
For an EXT155HA, the download is done for the two physical NEs (Working
and Protection). The result is given for each physical NE.
Click [Refresh inventory] to read and update the display of the version numbers of the softwares
installed on the NEs.
Click [End session] if you have finished.
c/ Switch Mode
Tick the equipment type selected : ADR155C, ADR2500C, ADR63E1, ADR155CPE, EXT155HA,
ADR2500 EXTRA, ADR622, FSP2000, FSP3000, SLF-H
Give the soft type:
Board
For an ADR2500C equipment, CTRL Board, GIG-E Board, FPGA,
For SLF-H , ODU1 and ODU2
Click [Switch] to run the software switchover operation.
Notes :
The switchover operation will not take place if the current version is
identical to the reserve version.
For an EXT155HA, the switch is done for the two physical NEs (Working and
Protection). The result is given for each physical NE.
Click [End session] when you have finished.

Page 119/205
TOPOLOGY MANAGEMENT
Configuration file : software.xml
The configuration file is located in the Config folder of the directory selected for installation (by default,
Ionos-NMS).
This is used to set:
tftp root : directory used by tftp.
softrepository : directory used for default selection in Software management.
<?xml version="1.0" encoding="UTF-8"?>
<software>




<tftp root="../tftproot"/>




<download softrepository="\"/>
</software>
This file is updated automatically when the server is installed under Windows.(see 1.2.3.2 - )
2.4.18 - To Export the configuration of a network element

This procedure is used to export the configuration of a NE or several NEs in a file xml.
Display the NML View by clicking View > NML View.
In the search window, select NEs : the list of NEs is displayed.
Select the NE(s) then click right to bring up the pop-up menu.
Click [Exportxml] : a file xml is created on the Server in the folder (according to the configuration of
file "file.xml" in folder Config) :
/IONOS-NMS_install_dir/log/xml//aaaa/aaaa-mm/jj is the folder by default with Windows.
/data/IONOS-NMS_install_dir/log/xml//aaaa/aaaa-mm/jj is the folder by default with Solaris.
The name of file is ne-yyyy-mm-dd-000n.xml
To obtain a file of format "text", select the bin folder and run the command :
NEsToExcel.cmd filename1 filename2 with filename1 : output file and filename2 : file.xml
Notes : This file give for each NE :
M1400 name
Name
Type
IP Address
Secondary IP address
Indication of proxy and n
Additional information
Hard inventory (rack, shelf, cards and ports)

Page 120/205
TOPOLOGY MANAGEMENT
2.4.19 - To visualize the counters of performance for SLF-v1, Sagem-Link, SLFN and SLF-H equipment
This procedure is used to collect and visualize the counters of performance of equipment of type
SLF-v1, Sagem-Link, SLF-N or SLF-H. This is performed by means external tool NMSperftool, installed
on the machine used by the server.
A scheduled task allows to collect the performance data of equipment once by day at 12h 00. The
collect is done for all equipment of type SLF-v1, Sagem-Link, SLF-N and SLF-H created in IONOS
NMS database.
2.4.19.1 - To Visualize the graphs of performance collect
Display the Topology View (Figure 2.1) by clicking View > Topology View.
Select a NE of type SLF-v1, SLF-N, SLF-H, or Sagem-Link then click right to bring up the pop-up
menu.
Click [Perf view] : the graphs of performance data for this equipment are displayed.
Figure 2.60 : Window Perf View on SLF-v1

The collected counters are :
UAS (Unavailable Seconds) counter 24h in mode G821
SES (Severely Errored Seconds) counter 24h in mode G821
ES (Errored Seconds) counter 24h in mode G821
BBE (Background Block Errors) counter 24h in mode G826. except for SLF-H
UAP (Unavailable Periods) counter 24h in mode G821.

Page 121/205
TOPOLOGY MANAGEMENT
And for SLF-N : RSL (Radio Signalling Link) counter : RSL DAY HIGH1, RSL DAY HIGH2,
RSL LOW1, RSL LOW2, RSL DAY LOW HIGH, RSL DAY MAX1, RSL DAY MAX2, RSL DAY
MIN1, RSL DAY MIN2 and RLS DAY MIN MAX
Figure 2.61 : Window Perf View / NMSperftool on SLF-v1

Notes:
The displayed priod can be modified with button [Presets].

Button [Tree View] allows to display the list of all SLF-v1 created in IONOSNMS and to activate the visualization of different graphs for each equipment.
The collect of performance data is automatically activated for each SagemLink, SLF-v1, SLF-N and SLF-H created in IONOS-NMS.
The collected data are displayed 24h after the collect.
Also, for SLF-N, the collected counters include the Ethernet performances:
Receive Total Packets Port 1 and 2
Receive Unicast Packets Port 1 and 2
Receive Multicast Packets Port 1 and 22
Receive Broadcast Packets Port 1 and 2
Receive Packets With Errors Port 1 and 2
Receive Pause Frames Port 1 and 2
Transmit Total Bytes Port 1 and 2
Transmit Total Packets Port 1 and 2
Transmit Unicast Packets Port 1 and 2
Transmit Multicast Packets Port 1 and 2
Transmit Broadcast Packets Port 1 and 2
Transmit Pause Frames Port 1 and 2
CRC Align Errors Port 1 and 2
Drop Events Port 1 and 2
Undersize Packets Port 1 and 2
Oversize Packets Port 1 and 2

Page 122/205
TOPOLOGY MANAGEMENT
Internal Mac Receive Errors Port 1 and 2
Common counters to Port 1 and Port 2:

PerformancePERInfoMantisse
PerformancePERInfoExposant
Figure 2.62 : Window Perf View / NMSPerftool on SLF-H (Ethernet counters)
2.4.19.2 - To export the collects of performance
An executable file is supplied to launch an exportation of collects on 365 days and generate a CSV file.
This CSV file can be processed with external application.
The export of performance collect for SLF-v1, Sagem-Link, SLF-N or SLF-H equipment is launched on
the Server IONOS-NMS.
folder.
Run the command : exportSLFperfs <file name>
2.4.20 - EMS API Integration

The EMS API Edition 1 enables a partner to integrate its own equipment at EMS level into Ionos-NMS
for equipment with SNMP traps.This API offers 2 features :
- double-clic on a NE, that opens the TPI / Equipment view on the Ionos-NMS client PC, to allow the
user to access avanced menus of management, provided by the external windows application provided
by the equipment vendor
Page 123/205
TOPOLOGY MANAGEMENT
- alarms and events management on these equipment :
to read the current alamrs list
to receive informations (alarms appearance, alarms disappearance,events)
to detect the traps losses
One type of equipment is defined by :

A code name in IONOS-NMS
An icon which will be displayed on the map
A name will be displayed on the map
The API is provided at SNMP level, by modifiying the files .bsh given in example
Following files are needed to integrate the equipment in Ionos-NMS :
Ionos-NMS\config\topo\types.xml
Contains the list of all NE-Types managed by ionos. EmsApi NE-Type must use the "EmsApiNe"
category, like following example :
Note : that the name is an unique ID that will be used to identify this NE-Type in Ionos. This ID must be
returned by SnmpEmsApi.getManagedNETypes () method. The size of this ID must not exceed 20
cars.
Ionos-NMS\config\EmsApi\EMSAPIAdr.bsh
This file contains the implementation of SnmpEmsApi.java methods. There is not constraints on its
name.
The file supplied as example must be modified according to the MIB SNMP provided by the equipment.
Ionos-NMS\netype\ADR2500EXTRA_EMSAPI_EXAMPLE.xml
This file is needed by the Ionos-NMS framework. You must copy the template defined in
ADR2500EXTRA_EMSAPI_EXAMPLE.xml and modify only the name of the NE-Type :
Note : The name must be the same as the ID of the NE-Type defined in types.xml (case
sensitive)
Ionos-NMS\netpilot\webapps\root\resources\topo\default\
Page 124/205
TOPOLOGY MANAGEMENT
ADR2500EXTRA_EMSAPI_EXAMPLE.gif
The .gif that represents the NE must be stored in that directory.
NOTE: The name of the file must be the same as the ID of the NeType defined in types.xml (case
sensitive).
Ionos-NMS\lib\beans\lb-sclientcustom.jar
Open this .jar file and modify \properties\custom_resources_en.properties to add the label of the NEType you want to add :
This is the label of the NE-Types as they appears in Ionos-Nms. This file is mandatory, the NE-Type
wont be available in Ionos-NMS if its label is not defined.
Ionos-NMS\config\profiler.xml
This file defines how to launch the TPI (Equipment View).

When user double-click on a NE in the Topology View, the Ionos-NMS system parses the profiler.xml
file and finds the relevant command.
The commands contain parameters fields, identified by the syntax ${PARAMETER}
For instance the following line defines the launching command of a SHDSL equipment TPI:
<SHDSL html="${BROWSER} http://${IP}/?community=${PWD}&;,user=${USER}"/>
Before executing this command line Ionos-NMS makes somme substitutions :${Browser} is replaced by
the http browser to launch (IE, Mozilla, etc) ; ${IP} is replaced by the IP of the equipment; and ${PWD}
and ${USER} are replaced by the login/passwd of the TPI user.
Available parameters are :
${BROWSER}
${PWD}
${USER}
${COMMUNITY}
${USEREQUIPMENTLOGIN}
Ionos-NMS\config\ems_trace.properties
Uncomment line
log4j.category.com.sagem.ionos.nms.server.emsapi=DEBUG to get debug
informations on the EmsApi module. The debug infos are saved in file Ionos-NMS\log\app\server.log
Nota: this feature is designed for debug purposes only. It can help the development of BSH, but do not
enable it in a real-life environment as it may slow down the server.

Page 125/205
TOPOLOGY MANAGEMENT
2.4.21 - To discover NE from Network (IP discovery)
This procedure is used to scan a range of IP address in order to discover and create Network Elements.
In the menus bar, select Tools > Discover Network Elements: the Discover Network Elements
window is displayed.
Click on the Seeds tab.
Figure 2.63 : Discover Network Elements Window

Configure the Polling Time Delay. The Polling Time Delay is the maximum waiting period to detect
equipment. The default value is 50 milliseconds.
Click [Add] to add one or several ranges of IP address to be scanned.
Fill the From IP and the To IP fields to determinate the range of IP addresses.
Click [Delete] to delete one range of IP address
Figure 2.64 : Window Discover Network Elements/Seeds
Click on tab [Communities] to define extra SNMP community password.

Page 126/205
TOPOLOGY MANAGEMENT
Figure 2.65 : Window Discover Network Elements/Communities

Click [Add] or [Delete] to update the list.
Notes:
The "SNMP community" is used to access equipment by SNMP.

Only new SNMP community not predefined in menu "tools > Preference >
Network Element" should be added.
Predefined values are used by default to scan the IP address of the range.
Click [Start] to discover Network Element. The list of NE discovered is displayed on top of the right
part of the window. The currently scanned IP address is displayed on the Discovery Service Status
part on the bottom of the right part of the window.
Figure 2.66 : Window Discover Network Elements/Discovering

Click [Stop], if necessary, to stop the discovering of Network Element.
Click on [OK] on the Status window when the scan of the range is completed.

Page 127/205
TOPOLOGY MANAGEMENT
Figure 2.67 : Window Discover Network Elements/Status

Notes:
The Status window is displayed when the scan of the range of IP address is
completed.
Caution: The list of discovered Network Elements may be updated a little while later
The discovered equipment are created in the Unassigned sub-network
Figure 2.68 : Window Topology view/tree

Notes:
The NE are created with the following fields values:

- Name , the name set for the created Network Element is:
1- The "NE name" read, configured in the discovered equipment.
2- The IP address is used as NE name if the NE name read is not valid
(already used in IONOS-NMS or empty).
Caution: If the NE name read and the IP address of the discovered
Network Element are already used, the NE is not created.
- M1400 name , the M1400 name is build with the four numbers (3
characters each) of the IP address of the discovered NE. The suffix is not
filled.
Example: a NE discovered with the IP address 192.168.17.2 will be
created with the M1400 name: 192168017002 (192 168 017 002)
Caution: If the M1400 name built from the IP address of the discovered
Network Element is already used, the NE is not created
- Type , the type of the discovered equipment (only ADR155C, ADR155CPE,
ADR155E, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000HN, ADR63E1,
FSP2000, FSP3000, SLF-v1, SLF-N, SLF-H, SLA, SLT,FOT C,XP3000)
- IP address Caution: If a NE with the same IP address (primary or
secondary address) is already created, the discovered NE is not created (no
duplication)

Page 128/205
TOPOLOGY MANAGEMENT
The traps table of the equipment is automatically updated with the server IP
address if possible.
Caution: The discovery of Network Element is not a multi-client application:
only one discovery should be launch at a time per server. The interruption
(stop) can be performed from any IONOS-NMS client.
An executable file is supplied to launch the discovery of Network Element. To
initialise the range of IP address perform a first NE discovery using IONOSNMS client.
- In the directory chosen for installation (Ionos-NMS or /tools/IONOSNMS by default), select the bin folder.
- Run the command : autodiscovery.bat (PC) or ./autodiscovery.sh
(solaris), then give the login ad password of the user IONOS-NMS and the IP
address of the server.
2.4.22 - To seek an equipment using its name or of its address IP

This procedure is used to seek an equipment in the Topology View .
In the menus bar, select Edit -> Search NE: the Search NE window is displayed.
Click on Long Name and propose a long name for a research using from the field long name
of the equipment.
Click on M1400 Name and propose a name M1400 for a research using from the field
M1400 Name of the equipment
Click on IP Address and propose an IP address for a research using from the field IP
Address of the equipment
Figure 2.69 : Window Topology view / Search NE

Click on [Search] to start the research
If an equipment corresponds to the search criterion, the sub-network in which it is present, is displayed
and the equipment is selected
Note : It is possible to launch a search of an equipment since the contextual menu of a
sub-network or of an equipment, then select "Search NE"

Page 129/205
NML VIEW
3. NML VIEW
3.1 - INTRODUCTION
The network object administration (trails, bearers, rings) is now handled through the NML view (Network
Management Layer).
This view enables you to:
select the objects which you want to list.
list the objects according to presentation criteria.

access operations to be performed on the objects (add, delete, activate, deactivate, show
properties, add a protection, etc.).
display the details of the objects (graphic representation, etc.).
3.2 - NML VIEW WINDOW

The NML View window comprises two areas:
the search area at the left
the details area at the right
Figure 3.1 : NML View : search area (1)

Page 130/205
NML VIEW
Figure 3.2 : NML View : details area (2)

The NML View window comprises 5 parts:
a menus bar, which gives access to the main function menus of the software: File, Edit, Creation,
Action, Tools, Help.
CAUTION : The functions displayed on the menus depend on the object processed by the
manager: sub-network, NE, trails, STM-n link, ring, VCGroups, alarms, points
of performance (see appendix 1: special functions on objects).
a tools bar (under the menu bar), which gives access to the following functions: create, delete,
dissociate, activate, deactivate, show properties, refresh.
Use the first icon to the left in the tools bar to create a trail, an STM-n link, a WDM Link, an
Ethernet Link, a WDM trail, an Ethernet service or a ring.
a search area (left window, below the tools bar), to list the network objects by domains
(All/SDH/WDM/Ethernet/Others) : SDH trails, bearers, rings, alarms, Links, Ethernet Links, WDM
Links, VCGroups, Ethernet services, WDM Links, WDM Trails, NE and points of performance.
Use this window to locate, select and edit the properties of an object.
a details area (right window, below tools bar) to generate a detailed display of the content of the
objects selected in the search area.
a current alarms window at the bottom of the screen.
Use this window to display the alarms which have been acknowledged or not, or filtered, from
the network elements.

Page 131/205
NML VIEW
3.2.1 - To display / filter a list of objects
This procedure is used to display and filter a list of objects.
In the Main filter area of the search area, click [Browse] to select a sub-network or an NE.
Notes :
By selecting All, you select all the sub-networks and all the network elements
(value by default).
By ticking the Recursive button, you also select the sub-networks contained
in the selected sub-network.
In the Result area of the search area, select one or several objects to be listed: Trails, Bearers,
Rings, Alarms, STM-n links, Ethernet Links, VCGroups, Ethernet Services, WDM Links, WDM
Trails, NEs.
Notes :
By selecting All, you select all the objects.
Click [Show result] to display the results.

Notes :
The lists selected can each be displayed in a tab.

Use the [Back] and [Next] buttons (at the top left) to recover the previous Main
filter and Result selections.
Then, select a line in the list and click right to bring up the pop-up menu.
Figure 3.3 : NML View / Main Filter / Trails / Filter

In the pop-up menu, click [Filter] then [Customize] : the Filter screen is displayed with around ten
tabs to adjust the filtering.

Page 132/205
NML VIEW
Figure 3.4 : NML View / Main Filter / Trails / Filter / List configuration
Tick off [Filters] and configure the values for one or several filters. (For example, in the Activation
filter, enter the value "Activated" or "Reserved" or "Partially Activated").
Use Automatic column resize to modify the size of displayed columns.
Use Visible columns to select the columns displayed in the list.
Use Row coloration to select the column which gives the color.
Use Configuration persistency to save the configuration of the list in database (saved by user)
Click [Apply] when you have finished, to validate the modifications.
Dans In the tools bar click [Enable filtering function] to activate or deactivate the filter
Note :
(1) To add a filter, it is also possible to select a cell then to activate in the
tools bar [Add a filter on the contents of the selected celll]. A filter is activated
on the cell contents.

Page 133/205
NML VIEW
In contextual menu, click [Save as] to export the displayed list in a file.
In contextual menu, click [Print] to print the displayed list.
Note:
The menus Customize/ Save as/ Print apply to all the lists: lists of the NML
View, lists of the result windows for activation/ deactivation (Trail/Bearer,
VCGroups, Ethernet services, MSP, SNC, Ring), List of the screen "Software
management", list of the screen "Show Links" , lists of the Logs (Event Log,
Fault Log, Server Log), list of "Alarms Propagation", list of the counters of
performance.
To use the buttons [ Back ] and [ Next ] (in top on the left) to recover the
preceding selections Main filter and Result.
3.2.2 - To use an element of a list as input filter

This procedure enables you to use one of the lines displayed in the list of results as an input filter (main
filter) of another list.
Example
List NEs of a sub-network.
In the result list, select a NE, then activate the pop-up menu.
In this menu, select the function [Set as new input filter] : the NE appears in the editing chain
(Browse) of the Main Filter.
Then, select "All" in the Result area: this gives all the information for this NE or select only what
you need
3.2.3 - List of objects in search area
The lists of objects in the search area relates to the following objects:
NEs. The actions associated with this type of object are detailed in the paragraph 2.4 - the
administration of the elements of network.
Alarms. The actions associated with this type of object are detailed in the paragraph 4
Alarms management.

Page 134/205
ALARMS MANAGEMENT
4. ALARMS MANAGEMENT
4.1 - INTRODUCTION
The NMS manager enables network supervision and checks NE accessibility by a configurable polling
mechanism.
All the alarms are generated by the NE to the manager by SNMP messages. IONOS-NMS then computes the
status of the NE alarms and that of the sub-networks and STM-n links.
The status of the trails, VC4 bearer trails and STM-n links is only defined when the user activates the trail
alarm Propagation menu.
Alarm types
The alarms belong to two categories:
EML alarms.

Network alarms (faults on traffic).
Certain alarms, such as loss of signal on the STM-n interfaces, form part of both categories (alarms on
reception or transmission card, alarms on STM-n link, etc.).
Alarm states
Operation of an alarm forms part of a cycle which comprises 4 states:
no alarm :
alarm not acknowledged:
alarm acknowledged : alarm ACK.
Alarm disappeared : alarm OFF.
alarm OFF.
alarm ON.
Status of trails
The trails, VC-4 bearer trails and STM-n links can have the following statuses:
not valid (extremities inaccessible).
no input signal.
alarm: traffic cut or traffic degraded according to the alarm.
no alarm (OK).
Animation of icons and links

In the explorer and in the sub-network view, the color of the icons (networks, Nes and links) change in
accordance with the level of severity of the alarms which they contain:
no alarm on NE or on link (or warning alarm): green
minor alarm on NE or on link: yellow
major alarm on NE or on link: red
critical alarm on NE or on link : pink
NE inaccessible : blue
Two colors are displayed on NE icon or subnetwok icon :

- the color of background icon corresponds to the maximum level of severity of the not acknowledged alarms
which the server contains.
- the color of edge icon corresponds to the maximum level of the all alarms (acknowledged and not
acknowledged) which the server contains.
The sub-network takes the colors of the NE having the alarm with the highest severity level.

Page 135/205
ALARMS MANAGEMENT
Note :
In the case of an EXT155HA, there are three colored icons, one for the logical
NE which gives the synthesis of color of two pfysical Nes.
4.2 - MANAGEMENT OF CURRENT ALARMS

4.2.1 - To display the current alarms
You can display all the current alarms (EMS and NMS alarms) at the bottom of the main view window, tab
Alarms (1).
Each alarm from the SNMP messages is registered and updated in real time in the log.
Figure 4.1 : Window Topology View / Fault View

In the table, each line takes the color corresponding to the level of severity of the alarm which it contains:
gray : warning.
yellow: for a minor alarm.
red: for a major alarm.
Pink : for a critical alarm.

blue : inaccessibility alarm.
The alarms are displayed in accordance with the selection in increasing alphabetical order () or decreasing
alphabetical order () (Begin represents the default sort) with the following parameters (2) (3) :
Equipment : equipment name
Location : card and port, cause of alarm.
Event type : type of alarm.
Status : level of severity of alarm.
Ack : indicates if alarm has been acknowledged (yes or no).
Ack user : indicates the name of user who acknowledged the alarm.

Page 136/205
ALARMS MANAGEMENT
Ack date : indicates the date on which alarm was acknowledged by user.
Begin date : date on which alarm was received by manager.
NE date : date at which alarm was sent by NE.
The menus bar gives access to the following functions (also accessible in pop-up menu when you select an
alarm):
Add a filter on the contents of the selected cell
Disable filtering function
Marks the alarms as treated (Acknowledge)
Marks the alarms back as not treated (Unacknowledge)
Clear selected Alarms
Show alarm properties and propagation
Locate the NE impacted by the alarm
Enabled unacknowledge cleared Alarm gestion (not accessible in pop-up menu)
Show unacknowledge cleared Alarm window (not accessible in pop-up menu)
Figure 4.2 : Window Topology View / Fault View / Pop-up menu

Notes :
(1) At the bottom of the main menu to the right, you can immediately check
the number of current alarms by 4 numbers: polling alarms (blue), major
alarms (red), minor alarms (yellow) and other alarms (blue or gray).
(1) The current alarms table can be detached (to use the drawing pin at the
top on the right of the list) in a window which can be always visible (to use the
icon in tools bar Activate/Deactivate the window always visible).
(2) To sort on another parameter, click on the parameter in the parameters bar
of the log: once selected, choose the appropriate marker ( by increasing
order by decreasing order).
(3) To update the date and time of the equipment, use the menu: SNMP View >
Equipment.
(4) use the pop-up menu to access to following functions :
. [Filter selection] to add a filter on the contents of the selected cell
. [Enable filters] to activate/deactivate filters
. [Customize] to configure filters and the display of the list
. [Find] to search a display string
. [Save as] to export the displayed list
. [Print] to print displayed list

Page 137/205
ALARMS MANAGEMENT
4.2.2 - To acknowledge a current alarm
This procedure is used to acknowledge an alarm.
In the alarms table, select an alarm.
Click right to bring up the pop-up menu.
In this menu, select [Acknowledge] : Yes is displayed in the Ack field (1) (2) (3).
Notes :
(1) You can use the Acknowledge function in the tools bar to directly
acknowledge several alarms selected using the Ctrl keys.
(2) This operation contributes to changing the color of the NE icon in the
Topology View; the alarm is no longer taken into account in the icon
animation computation.
(3) The user name and date of acknowledgement are updated in
corresponding columns.
4.2.3 - To unacknowledge a current alarm

This procedure is used to unacknowledge an alarm: the alarm returns to its initial status before
acknowledgement.
Select the alarm in the alarms table.
In this menu, select [Unacknowledge] : No is displayed in the Ack field (1) (2) (3).
Notes :
(1) You can use the Unacknowledge function in the tools bar to directly
unacknowledge several alarms selected using the Ctrl key.
(2) This operation contributes to changing the color of the NE icon in the
Topology View; the alarm is again taken into account in the icon animation
computation.
(3) The user name and date of acknowledgement are cleared in corresponding
columns.
4.2.4 - To filter current alarms by criteria

This procedure is used to filter the alarms which you want to display .
In this menu, select [List] : A new pop-up menu is displayed.
Select [Customize] : The List Configuration window is displayed (1) (2) (3) (4) (5) (6).

Page 138/205
ALARMS MANAGEMENT
Figure 4.3 : Window Topology View / Fault View / List configuration

Check [Filters] and give all the criteria to be applied for the alarms filtering.
Click on [Apply] to validate the operation : the alarms corresponding to the filtering criteria defined
are displayed in the alarms table.
In the tools bar, click on the button [Enable filtering function] to activate or to deactivate the filter:
Notes :
(1) To add a filter, it is also possible to select a cell, then to activate the button
[Add a filter on the contents of the selected cell] in the tools bar. A filter
activated on the contents of the selected cell.
(2) Use Automatic column resize to modify the size of displayed columns.
(3) Use visible columns to choose the columns displayed in the list.
(4) Use Row coloration to color the alarms table, according to the severity
of alarms.
(5) Use line wrap mode to display the contents of a cell on several lines.
(6) Use Configuration persistency to back up the configuration of the list of
current alarms table (the backup in database is made for each user when the
IONOS-NMS client will be closed.

Page 139/205
ALARMS MANAGEMENT
Note :
To display the status of alarm for SDH and WDM links, bearers, and SDH and
WDM trails, use visible columns to add the Status column and use Row
coloration to color according to the severity of the Status.
This function is available by default for a user with the administrator rights.
4.2.5 - To locate a current alarm

This procedure is used to locate the equipment in which an alarm is located.
In this menu, select [Locate] : the NE in which the alarm is located is selected in the explorer and in
the view.
Note :
You can also use the Locate function in the tools bar to directly locate the NE
in the Topology View.
4.2.6 - To display the properties of a current alarm

This procedure is used to display the properties of an alarm.
In this menu, select [Properties] : the Alarm Properties / Information window is displayed.
Figure 4.4 : Window Alarms properties / Information

In Details area, the NE name, event type, its location, its severity, the date on which alarm was received by
manager, the date at which alarm was sent by NE and acknowledgement informations can be visualized.
Notes :
(1) You can also use Properties in the tools bar to display the properties of
an alarm.

Page 140/205
ALARMS MANAGEMENT
(2) it is also possible to visualize the properties of an alarm, by using menu
Properties in the contextual menu of an alarm selected in the list of alarms of the
NML View (Alarms tab).
4.2.7 - To display the alarms unacknowledged cleared alarms

This procedure is used to display the cleared alarms, never acknowledged.
To activate the function, in tool bar click icon
In tool bar, Click icon
: the window Unacknowledged cleared and new Alarms is displayed.
Check [Show Cleared Alarms list]

The function is activated. All the alarms unacknowledged and cleared are displayed on top of the
window.
Figure 4.5 : Window Unacknowledged cleared and new Alarms

Page 141/205
ALARMS MANAGEMENT
Click, if necessary, [Clear New Alarms] to clear all the alarms of this list.
Click [Close] to close the window.
To deactivate the function, uncheck [Show Cleared Alarms list] in the window.
Notes :
(1) If the function is activated, the window is displayed automatically when a

new alarm not acknowledged is cleared.
(2) The menus [Filter] and [Save as] are available in pop-up menu.
(3) To deactivate both functions of the window, in tool bar click on icon
4.2.8 - To display the new alarms

This procedure is used to display the new alarms.
To activate the function, in tool bar click icon
In tool bar, Click icon
: the window Unacknowledged cleared and new Alarms is displayed.
Check [Show New Alarms list]

The Function is activated. All the alarms new are displayed on the bottom of the window
Figure 4.6 : Window Unacknowledged cleared and new Alarms

Click, if necessary, [Clear New Alarms] to clear all the alarms of this list.
Page 142/205
ALARMS MANAGEMENT
Click [Close] to close the window.
To deactivate the function, un-check [Show New Alarms list] in the window.
Notes :
(1) If the function is activated, the window is displayed automatically when a

new alarm appears.
(2) The menus [Filter] and [Save as] are available in pop-up menu.
(3) To deactivate both functions of the window, in tool bar click on icon
4.2.9 - To filter current alarms by multi-criteria

This procedure is used to filter the alarm or event which you want to display.
New fields are displayed when the multi-criteria filtering is activated. See
the alarm multi-criteria filtering.
1.2.3.27 - To configure
Then, its possible to apply filters with multi-criteria on alarm in the Fault View, Fault Log, NML View,
Properties/Alarms, Unknownledge cleared and New Alarms windows and to save them. Also, its
possible to apply filters with multi-criteria in the Log View for the Event Log tab.
Notes :
Only the columns with a string value as filter condition can be used for multi-criteria
filters.
There is no multi-criteria filter for Status, Ack and Date columns.
Right-click to bring up the pop-up menu.

In this menu, select [List]: A new pop-up menu is displayed.
Select [Customize] : The List configuration window is displayed.

Page 143/205
ALARMS MANAGEMENT
Figure 4.7 : Window Topology View /Fault View / List Configuration / Multi-criteria filtering
Check [Filters] and give all the criteria to be applied for alarms or events filtering
Click [Next] to add another filter for the same column
Note(s) : On the last [Next] action, if the field is empty, the next [Next] action is to display the
first filter.
To delete a filter, select the filter by clicking on the [Next] button and erase the
content of the string value in the combobox.
Do the same actions for each column (if necessary)
Select a And or Or condition for the choice between columns
Select a And or Or condition for the choice between filter in the same column. This filter is
applied in all columns.
Click on [Apply] button to validate the operation: the alarms or events corresponding to the
filtering criteria defined are displayed.
And/Or
Enter a filter name in the Save Filter as field. Only alphanumeric characters are valid and the
maximum length is 20 characters for the filter name
Click on [Save Filter as] button to register the filter. The filter name is added in the Filters list
combobox.
To load a filter previously saved:
Page 144/205
ALARMS MANAGEMENT
Select the filter name from the Filter list combobox.
Click on [Load] button.
Click on [Apply] button if necessary: the alarms or events corresponding to the filter are
displayed.
Note: It exists two filters by default in the Filters list to reset the alarm filtering (empty) and to reset
the event filtering (emptyEventlog).
To delete a filter saved:

Select the filter name from the Filter list combobox.
Click on [Delete] button and confirm by clicking on the [Yes] button.
To export the Filters configuration file(s) from one client to another one:
In the repertory chosen for the installation (by default Ionos-NMS), select the Config/Filters folder.
In this folder, select and copy the alarmsFilters.xml file (it containts the filters description) to the
DIR_IONOS/config/Filters folder of the client destination.
IONOS-NMS.
4.2.10 - To activate the send of mails on alarms modification

This procedure is used to send a mail on alarms modification :
raised alarm
cleared alarm
acknowledged alarm

unacknowledged alarm.
A mail is send X minutes (maximum) after alarm modification (see 1.2.3.12 - to activate this function).
X is defined for each type of alarm severity in file timers.xml. (see 1.2.3.13 The mail gives :
the alarms modification of higher level since the last mail
the total of raised alarms
the total of raised and unacknowledgedalarms
the number of raised alarms by level of severity (since the last mail)
the number of cleared alarms by level of severity (since the last mail)
the number of acknowledged alarms by level of severity (since the last mail)
the number of unacknowledged alarms by level of severity (since the last mail)

the detail for each alarm
Example for a short mail:
Subject: Alarms activity : 5 Inaccessible alarms raised on VZY-P1198715
5 Inac raised on Y-P1198715
Status :
Unack : 5 Inac,1 Critic,10 Maj,8 Min,21 Warn
All : 5 Inac,1 Critic,10 Maj,8 Min,21 Warn
Example for a complete mail:
Subject: Alarms activity : 1 Inaccessible alarm raised on P1198383
Page 145/205
ALARMS MANAGEMENT
1 Inaccessible alarm raised on P1198383
Alarm Status :
Unack alarms
All alarms
:
:
Activity Summary :
Raised
Cleared
Acknowledged
Unacknowledged
:
:
:
:
Activity
26 Major, 10 Minor, 81 Warning

26 Major, 10 Minor, 81 Warning
1 Inaccessible, 1 Major
2 Inaccessible, 1 Critical, 1 Major
Equipment
Location
Raised and cleared 155c104/104

14:37:36
Event type
BOARD SLOT B
Cleared
63e99/99
03/12/04 14:37:16
Raised and cleared 63e99/99
Cleared
Nice26/1
Status
defective
Ack
Begin date
Major
no
03/12/04
Synchro NE Data failure (Configuration Number) Critical
Polling
Inaccessible
Polling
Inaccessible no
no
no
03/12/04 14:38:44
03/12/04 14:37:28
4.2.11 - To activate the send of mails on critical alarm

This procedure is used to send a mail on critical alarms :
A mail is send a few second after a critical alarm is raised (see 1.2.3.14 - to activate this function).
It is possible to sent a mail on critical alarm in short mode in relation to the sub-network, NE type and NE
name and to configure the format of the sent mail (the length of the message).
The mail gives the detail for the alarm.
Example for short mail:
<format>short</format>
<object_short> Eqpt: $EQUIPEMENT - $LOCATION - Evt: $EVENT_TYPE - Begin: $BEGIN_DATE
</object_short>
Subject: Eqpt: Paris - LocalIdu
- Evt: FERMETURE_1 - Begin: 29/09/10 10:25:12
Example for short mail (event type in the list)

<format>short</format>
In the following exemple the event type is RadioLinkFailure with a major severity
Subject: Eqpt: SLF-HC_137 - Loc: LocalIdu - Evt: RadioLinkFailure Beg: 03/03/09 15:50:28 - End:
Example for long mail:
<format>long</format>
Subject : 1 Critical alarm raised on Ionos-NMS

Content :
Equipment: SagemLinkParis
Location: Main Board
Page 146/205
ALARMS MANAGEMENT
Event type: Power Failure
Begin date: 03/12/08 14:37:36
Example for complete mail:
<format>complete</format>
Subject: Alarms activity : 1 Inaccessible alarm raised on VZY-P1198715

Alarm Status :
Unack alarms : 1 Inaccessible
All alarms
: 1 Inaccessible
Activity Summary :
Raised
: 1 Inaccessible
Cleared
:
Acknowledged :
Unacknowledged :
Activity
Raised
Equipment
Location
SLF-N-62.122
Event type
Status
Ack
Polling
Inaccessible no
Begin date
03/12/08 10:39:47

Page 147/205
HISTORIES MANAGEMENT
5. HISTORIES MANAGEMENT
In the menus bar, select View > Log View : the Log View screen is displayed and replaces the topology
main view (1).
This screen has five tabs corresponding to the five logs (2) :
Event Log, to display the events history send by the Nes.
Fault Log, to display the alarms history.
Server Log to display the history of user actions.
Database Log to display the history of used database (Oracle database).
SDH Trails Log to display the history of the status of real time supervised SDH trails.
Notes :
(1) To return to the main view, select View > Topology View in the menus bar.
(2) The number of lines per page in the logs can be configured from 200 to
10000 by clicking on button [View Size]
(3) Use the tools bar to access the following functions:
[Add a filter on the contents of the selected cell] to add a filter.
[Disable filtering function] to activate/deactivate the filters.
[Show log record details] to display the properties of a recording.
[Purge all log entries from database] to purge the opened log.

[Refresh the log records] to refresh the selected log or to return to the first
page.
[Stop the log records reload] to stop the display of the log.
(3) Use the pop-up menu to access the following functions:
. [Filter selection ] to add a filter on the contents of a selected cell.
. [Enable filters] to activate/deactivate the filters.
. [Customize] to configure filters and the display of the list.
. (Find] to search a display string.
. [Save as] to export the displayed list.
. [Print] to print the current list.

Page 148/205
a/ By selecting the Event Log, the following screen is displayed (3).
Figure 5.1 : Window Log View / Event Log
b/ By selecting the Fault Log, the following screen is displayed (3).
Figure 5.2 : Window Log View / Fault Log

Page 149/205
Notes :
The parameters are the same as for the current alarms log (see 4.2.1 -) with
the added End field to indicate the date on which the end of alarm was
received by the manager.
Each line takes a color corresponding to the level of severity of the alarms
contained in the equipment :
. gray : warning.
. yellow : minor alarm.
. red : major alarm.
. blue : polling alarm.
c/ By selecting the Server Log tab, the following screen is displayed (3):
Figure 5.3 : Window Log View / Server Log

d/ By selecting the Database Log tab, the following screen is displayed (3):
Figure 5.4 : Window Log View / Database Log

Page 150/205
Note :
The actions which are stored in the dtabase log are:

- The database creation
- The last forced backup or automatic backup
- The database restoration
- The database migration
The database log cannot be purged.
e/ By selecting the SDH Trails Log tab, the following screen is displayed (3):
Figure 5.5 : Window Log View / SDH Trails Log

Page 151/205
PREFERENCES MANAGEMENT
6. PREFERENCES MANAGEMENT
6.1 - INTRODUCTION
The preferences management functions are used to modify the default values initialized at the start of the
application, concerning the icons used for sub-network and for Nes, the IP address of server, the default
configuration of sounds, the default parameters of Nes, the default parameters of STM-n Links, the default
parameters of trails, the default parameters of rings, the default parameters of VCGroups, the default
parameters of Ethernet Links, the default parameters of Ethernet services, the default configuration of profiles
used for QOS parameters of Ethernet services.
6.2 - PREFERENCES
6.2.1 - To change the IP address of the server
In the menus bar, select Tools > Preferences : the Preferences screen is displayed.
In this screen, select the Name Server tab.
Figure 6.1 : Window Preferences / IONOS-NMS

In the Host field, specify the IP address of the server.
In the Port field, specify the port number (always 1099).
Click [OK] when you have finished.
Note :
This modification will be taken into account only on one new launching of the
Application Client (after closing of IONOS-NMS Client).

Page 152/205
6.2.2 - To change an icon image

This procedure is used to modify the icon displayed on Topology View for each type of NE or each type of
sub-network.
In this screen, select the Topology View tab.
Figure 6.2 : Window Preferences / Topology View
Select the NE Types tab (for the NE, VNE, FOT, ADR, FMX, FH icons) or the Group Types tab (for
the sub-network icons).
In the left window, click on the icon for which you want to change the image: the current icon is then
displayed in the right window.
Click [Browse] to browse for a new image.
Click [Apply] to apply the new image selected.
Note :
By clicking [Default Icon], you select the default icon assigned to represent
the network element.
The icons by default are stored in directory
netpilot/webapp/root/resources/topo/default.
New icons can be created by taking the existing icons as model.

Page 153/205
6.2.3 - To change the default properties of the Nes

This procedure is used to modify the default values of NE parameters.
In this screen, select the Nes tab.
Figure 6.3 : Window Preferences / Nes
In the SNMP request configuration for all Nes area, enter the timeout between two polling requests.
In the Default community passwords area, enter for each type of NE :
a/ the SNMP community ( secret by default)
b/ the Supervisor password ( secret by default)
c/ the Operator password ( private by default)
d/ the Observer password ( public by default)
In the Default value for NE creation area, enter:
a/ the default NE type in the Default NE type field
b/ the default poll interval in the Default Poll Interval field

Page 154/205
6.2.4 - To change the default properties of sounds

This procedure is used to activate or deactivate the sounds on alarm apparition or end of alarm.
In this screen, select the Sounds tab.
Figure 6.4 : Window Preferences / Sounds
Activate the sounds (the case No sound is not ticked) and if required the repetitions (the case
No repetition is not ticked).
In the sound definition area, give the configuration (file.wav) for each event type (On Occurrence),
for the associated repetition (For Repetition) and the time between two repetitions :
New critical alarm and repetition
New major alarm and repetition
New minor alarm and repetition
New warning alarm and repetition
New inaccessible alarm and repetition
End of critical alarm
End of major alarm
End of minor alarm
End of warning alarm
End of inaccesible alarm

Page 155/205
Use [Browse] to select a new file.
Use [Clear] to delete the configuration of selected line.
Notes :
The configuration sounds is defined for each client.

By default, the sounds are not activated.
The sound for repetition is done only for the event type of more important
severity (inacc > critical > major > minor > warning)

Page 156/205
USERS MANAGEMENT
7. USERS MANAGEMENT
7.1 - INTRODUCTION
User administration is now performed using the Admin View window.
This window enables :
creation of new profiles, new groups and new users.
operations on the profiles (add, delete, copy/cut, display and modify properties).
operations on the groups (add, delete, copy/cut, display and modify properties).
operations on the users (add, delete, copy/cut, display and modify properties).
listing the network domains and their associated groups.
7.2 - ADMIN VIEW WINDOW

The Admin View window has two parts:
a search area (left) with 4 tabs : Research tree, Users, Groups, Profiles.
a details area (on the right).
Figure 7.1 : Window Admin View / Research tree

Page 157/205
USERS MANAGEMENT
Figure 7.2 : Window Admin View / Users
Figure 7.3 : Window Admin View / Groups

Page 158/205
USERS MANAGEMENT
Figure 7.4 : Window Admin View / Profiles
7.2.1 - To create a profile

This procedure is used to create a profile.
In the Admin View tools bar, click the New icon (left): the drop-down menu is displayed with three
options: Profile, Group and User.
In this menu, click [Profile] : the Profile creation window (1) is displayed.
Figure 7.5 : Window Profile creation (1)

Page 159/205
USERS MANAGEMENT
Enter the profile name in the Profile name field.
Enter the profile description in the Profile description field.
Click [Next] to continue: the functions accessible to the profile are displayed.

Modify the functions accessible to the profile .
Click [Next] to continue: the customized data entry window is displayed.
Enter :
a/ the customer name in the Customer name field (40 characters max.)
b/ the location in the Location field (40 characters max.)
c/ any other necessary information in the Info field (200 characters max.).
Page 160/205
USERS MANAGEMENT
Click [Finish] when you have finished, to validate the creation.
Note:
Two types of profiles can be defined:

- type provider access: the user will be able to only visualize all the
network with animation of his domain (see Figure 7.8) or of all the
network (to activate menu View/View all alarms).
- Type No provider access: the user will be able to visualize only his
domain.
Figure 7.8 : Window Topology View / Profile provider access

-
Note:
Three profiles are created by default:
Admin: with all the rights
- Operator: with all the rights except the administration
- Observer: with rights in reading only.
7.2.2 - To create a group

This procedure is used to create a group of users.
In this menu, click [Group] : the Group creation window (1) is displayed.

Page 161/205
USERS MANAGEMENT
Figure 7.9 : Window Group creation (1)

Enter the group name in the Group name field.
Enter the group description in the Group description field.
In the Profile name field, select a profile from the list proposed.
Click [Browse] to select the domain accessible to the group of users.
Notes :
A domain corresponds to a sub-network (with all the sub-networks contained

in it).
A user in a group can only display the trails belonging to its domain or those
crossing it.

Enter :
a/ the customer name in the Customer name field (40 characters max.),
b/ the location in the Location field (40 characters max.),
c/ any necessary additional information in the Info field (200 characters max.).
Click [Finish] when you have finished.

Page 162/205
USERS MANAGEMENT
7.2.3 - To create a user
This procedure is used to create a user.
Caution : LDAP users must be defined in the LDAP Directory Service before to defined in
IONOS-NMS
In this menu, click [User] : the User creation window (1) is displayed.
Figure 7.11 : Window User creation (1)
Figure 7.12 : Window LDAP User creation (1)
Caution : If the connection to a LDAP server is enabled (see 1.2.3.25 - ), the check box LDAP
user is ticked. The user should be defined in the LDAP Directory Service.
Enter the user name in the User name field, then select a Group in the list proposed. The domain
used by this group is displayed.
Caution : If the connection to a LDAP server is enabled (see 1.2.3.25 - ), the LDAP user should
be created using the Name of the user defined in the LDAP Directory Service (for
example olivier.dupont . The maximun length of the name depends of your LDAP
directory)
Click [Next] to continue: the password entry window is displayed.

Page 163/205
USERS MANAGEMENT
In the Password and Confirm password fields, enter the user password then click [Next] : the
data entry window is displayed.
Caution : If the connection to a LDAP server is enabled (see 1.2.3.25 - ), the password could be
not changed.

Enter :
c/ any necessary additional information in the Info field (200 characters max.).
Click [Finish] when you have finished.
7.2.4 - To display/modify the properties of a profile

This procedure is used to display/modify the properties of a profile.
Display the Admin View by clicking View > Admin View.
In the search window, select the Profiles tab.
In the list, select the profile then activate the Properties menu: the profile data are displayed in 3 tabs in
the right window: Definition, Authorization and Additional information.

Page 164/205
USERS MANAGEMENT
Figure 7.15 : Window Admin View / Profiles / Definition
If necessary, modify the profile name and the profile description (Definition tab).
Figure 7.16 : Window Admin View / Profiles / Authorization

If necessary, modify the functions accessible to the profile (Authorization tab).
If necessary, modify the additional data (Additional information tab).
Click [Apply] to validate the changes.

Page 165/205
USERS MANAGEMENT
7.2.5 - To display/modify the properties of a group
This procedure is used to display and modify the properties of a group.
Display the Admin View window by clicking View > Admin View.
In the search window, select the Groups tab.
n the list, select the group then activate the Properties menu: the group data are displayed in 2 tabs to
the right: Definition, Additional information.

Page 166/205
USERS MANAGEMENT
Figure 7.17 : Window Admin View / Groups / Definition
If necessary, modify the group name, the profile and the domain (Definition tab).
Figure 7.18 : Window Admin View / Groups / Additional information
If necessary, modify the customized data (Additional information tab).

Click [Apply] to validate the data changes.

Page 167/205
USERS MANAGEMENT
7.2.6 - To display/modify the properties of a user

This procedure is used to display and modify the properties of a user (not Ldap).
Display the Admin View window by clicking View > Admin View.
In the search window, select the Users tab.
In the list, select the user then activate the Properties menu: the user data is displayed in three tabs on
the right: Definition, Password, Additional information.
Figure 7.19 : Window Admin View / Users / Definition

If necessary, modify the user name in the User name field except for Ldap user .
Figure 7.20 : Window Admin View / Ldap Users / Definition

Page 168/205
USERS MANAGEMENT
Figure 7.21 : Window Admin View / Users / Password

If necessary, modify the password in the Password field except for Ldap user (Password tab).
Figure 7.22 : Window Admin View / Users / Additional information

If necessary, modify the additional data (Additional information tab).
Click [Apply] to validate the changes.

Page 169/205
USERS MANAGEMENT
7.2.7 - To copy a profile
In the list, select the profile which you want to copy.
In the menus bar, click Edit > Copy/Paste : the following Profile creation window is displayed.

In the Profile name field, enter a new name for the profile and modify the description if necessary
Click [Next] to continue: the functions accessible to the profile are displayed.

Modify the functions accessible to the profile, if necessary.

Page 170/205
USERS MANAGEMENT

Enter the customer name in the Customer name field (40 characters max.); enter the location in the
Location field (40 characters max.); enter any other necessary information in the Info field
(200 characters max.).
Click [Finish] when you have finished : the new profile appears in the list of profiles.
7.2.8 - To copy a group

In the list, select the group which you want to copy.
In the menus bar, click Edit > Copy/Paste : the following Group creation window is displayed.

In the Group name field, enter a new name for the group.
Select a new profile and a new domain if necessary.

Page 171/205
USERS MANAGEMENT

Enter the customer name in the Customer name field (40 characters max.); enter the location in the
Location field (40 characters max.); enter any other necessary information in the Info field
(200 characters max.).
Click [Finish] when you have finished : the new group appears in the list of groups.
7.2.9 - To copy a user

In the list, select the user which you want to copy.

In the menus bar, click Edit > Copy/Paste : the User creation window is displayed.

Page 172/205
USERS MANAGEMENT

Enter a new user name in the User name field.
Select a new group if necessary.
Click [Next] to continue: the password entry window is displayed.

In the Password and Confirm password fields, enter the user password then click [Next] : the
data entry window is displayed.

Page 173/205
USERS MANAGEMENT
Enter :
c/ any other necessary information in the Info field (200 characters max.).
Click [Finish] when you have finished : the new user appears in the list of users.
7.2.10 - To delete a profile

In the list, select the profile which you want to delete.
In the menus bar, click Edit > Delete : a confirmation message is displayed.
7.2.11 - To delete a group

In the list, select the group which you want to delete.
7.2.12 - To delete a user

In the list, select the user which you want to delete.
7.2.13 - To lock a user

In the list, select the user you want to lock and click on the Definition tab.

Page 174/205
USERS MANAGEMENT
In the LockState field, select the lock value from the list
Do [Apply] : the user s is locked. LockReason is FORCED.
Notes:
Only users with admin profile can lock a user

Users created with default profile admin and default users can not be
locked
A user locked can not open a session
7.2.14 - To unlock a user

In the list, select the user you want to unlock and click on the Definition tab.

Page 175/205
USERS MANAGEMENT
In the LockState field, select the unlock value from the list
Do [Apply] : the user is unlocked.
Note:
Only users with admin profile can unlock a user

Page 176/205
IONOS SERVERS FEDERATOR
8. IONOS SERVERS FEDERATOR

8.1 - INTRODUCTION
The Ionos Federator enables supervision of alarms for multiple Ionos-NMS servers via IP network and checks
servers accessibility by a configurable polling mechanism.
This application enables :
the visualization of each server on the map (represented by an icon)
the alarm state visualization of each server (animation of color)
the alarms list visualization of each server
the start of a client on each server
In the case of backup 1+1 of IONOS NMS servers, the Ionos Federator allows to :
to activate switching from main server to backup server
To activate conversely switching from backup server to main server

Note :
In case of ADR10000 management, you have to do some manually operations:

to start/stop the EMS-ADR server and restore the EMS-ADR database.
Refer to the EMS-ADR User Manual version 7 N 253 216 157-A or EMS-ADR User Manual version 8.1 N
253 359 465-A to start/stop the EMS-ADR server and to restore the EMS-ADR database.
8.2 - DESCRIPTION OF IONOS SERVERS FEDERATOR

8.2.1 - The map of Federator
Figure 8.1 : Window Ionos Federator

Page 177/205

Each server defined in the configuration file is represented by an icon on the map. Each icon is colored.
If the server is connected to Federator, the color of icon corresponds to the maximum level of severity of the
alarms which the server contains.
The color of background icon corresponds to the maximum level of severity of the alarms not acknowledged
which the server contains.
The color of edge icon corresponds to the maximum level of the all alarms (acknowledged and not
acknowledged) which the server contains.
The animations are the following :
no alarm on network elements which the server contains (or warning alarm) : green
minor alarm on one of network elements which the server contains : yellow
major alarm on one of network elements which the server contains : red
critical alarm on one of network elements which the server contains : pink
inaccessibilty alarm on one of network elements which the server contains : blue
The server icon has the color of NE which contains the alarm of highest severity level.
The map is refreshed all the n seconds (n = value of PoolRefreshValue in the configuration file).
When the connection between the server and the Federator failed, the icon is blue with the cause of failure:
Unreacheable : the server is inaccessible
Unompatible : the version number of server is not compatible with the version number of
Federator
Unknown user : the login has failed with the user name and password enterd in the window
login of Federator
When the server is not connected with the Federator, the Federator tries a connection all the m seconds (m =
value of PoolReconnectValue in the configuration file).
8.2.2 - To visualize the alarms of a server

This procedure is used to visualize all the alarms (alarms of type EMS and NMS) which a server contains.
In the map, click right on the server to be displayed.
In the pop-up menu, select Faults : the Ionos Federator / Alarms window is displayed.
Figure 8.2 : Window Ionos Federator / Alarms

Page 178/205

In the table, each line takes the color corresponding to the level of severity of the alarm which it contains :
gray : warning.
yellow : for a minor alarm.
red : for a major alarm
pink : for a critical alarm
blue : for inaccessibility alarm
The alarms are displayed in accordance with the selection in increasing alphabetical order () or decreasing
alphabetical order () (Begin represents the default sorts) with the following parameters :
Equipment : equipment name.
Location : card and port, cause of alarm.
Event type : type of alarm.
Status : level of severity of alarm.
Ack : indicates if alarm has been acknowledged (yes or no)
Begin date : date on which alarm was received by manager.
NE date : date at which alarm was sent by NE.
8.2.3 - To filter current alarms of a server by criteria

This procedure is used to filter the alarms which you want to display.
In this menu, select [List] : a new pop-up menu is displayed.
Figure 8.3 : Window Ionos Federator / Alarms / List
Select [Save as] to export the list of alarms in a file.

Select [Print] to print the list of alarms.
Select [Customize] : the List configuration window is displayed (1) (2) .

Page 179/205
Figure 8.4 : Window Ionos Federaor / List configuration
Check [Filters] and give all the criteria to be applied for the alarms filtering.
Click on [Apply] to validate the operation : the alarms corresponding to the filtering criteria defined
are displayed in the alarms table.
In the menu, click on the button [Enable filters] to activate or deactivate the filter.
Notes :
(1)Use Automatic column resize to modify the size of displayed columns.

(2) Use visible columns to choose the columns displayed in the list.

Page 180/205
8.2.4 - To open a IONOS-NMS Client on a server

This procedure is used to open a Client application on one of servers managed by the Federator.
In the map, click right on the server IONOS-NMS.
In the pop-up menu, select [Open client) : a Client is launched on this server , with the user name
and the password entered on the window Login of Federator when the Federator has been
launched.The main view of Client is displayed.
8.2.5 - To open a IONOS-NMS Client on a server with another user

This procedure is used to open a Client application on one of servers managed by the Federator, with another
user name and password.
In the map, click right on the server IONOS-NMS.
In the pop-up menu, select [Open client with another user] : a client is launched on this server. The
window login is displayed to enter the new user name and the password.
Figure 8.5 : Window Ionos Federator / Login on Client
In this window, enter the user name (User name field) and the password (Password field) : by
default, the passwords corresponding to the default users admin, operator et observer are
respectively secret, private et public.
Click [OK] to validate the window : the main view of Client is displayed.
Notes :
The user profile defines the user rights on the Application :

. The administrator has all rights.
. The operator has all rights except the rights on the Admin view.
. The observer can only consult the application.
Refer to the table in Appendix : Rights linked to each profile created by
default.

Page 181/205
8.2.6 - To force the connection of a server not connected

The connection between the Federator and a server which is not connected is launched all the m seconds
(m = value defined in the configuration file).
This procedure is used to force the connection of Federator with a server which is not connected.
In the map, click right on the server IONOS-NMS which is not connected.
In the pop-up menu, select [Force re-connection] : if the connection failed, an error message is
displayed (Connection failure).
8.2.7 - To force the refresh of the map

On the map, the refresh of the alarm state is done all the n seconds (n value defined in the configuration file)
for all the servers which are connected.
This procedure is used to force the refresh of the map for all the servers which are connected with the
Federator.
In the map, click right on the server connected IONOS-NMS
In this menu, select [Refresh servers].
8.2.8 - To start a server

This procedure is used to start a server which is stopped. The application Easy Launcher must be launched
on the machine on which the server is started.
In the map, click right the server IONOS-NMS.
In the pop-up menu, select [Start Server].
Note :
In case of ADR10000 management, you have to start manually the EMS-ADR

associated to the Ionos-NMS server.
Refer to the EMS-ADR User Manual version 7 N 253 216 157-A or EMS-ADR User Manual version
8.1 N 253 359 465-A to start/stop the EMS-ADR server and to restore the EMS-ADR database
8.2.9 - To stop a server

This procedure is used to start a server which is stopped. The application Easy Launcher must be launched
on the machine on which the server is stopped.
In the pop-up menu, select [Stop Server].
Note :
In case of ADR10000 management, you have to stop manually the EMS-ADR

associated to the Ionos-NMS server.
Refer to the EMS-ADR User Manual version 7 N 253 216 157-A or EMS-ADR User Manual version
8.1 N 253 359 465-A to start/stop the EMS-ADR server and to restore the EMS-ADR database
8.2.10 - To backup the database of a server

This procedure is used to backup the database of a server which is not stopped.
Page 182/205

In the pop-up menu, select [Backup Server].
The user must have the rights to perform this action (see 1.2.3.38 - To configure the user rights to perform
actions from the Federator application).
Note :
In case of ADR10000 management, an EMS-ADR database backup will be done

on the EMS-ADR backup server associated to the Ionos-NMS server.
In the case of backup 1+1, a backup of Ionos-NMS and EMS-ADR databases will be done on the backup
servers via FTP or SFTP protocol.
8.2.11 - To Restore the database on a server

This procedure is used to restore the last backup of database on a server The server must be stopped.
In the pop-up menu, select [Restore from last backup].
Note :
In case of ADR10000 management, you have to restore manually the EMS-ADR

database.
Refer to the EMS-ADR User Manual version 7 N 253 216 157-A or EMS-ADR User Manual version 8.1 N
253 359 465-A to restore the EMS-ADR database.
8.2.12 - To Change a server

This procedure is used to change a server by another server. In the case of backup 1+1 of IONOS NMS
servers, this menu is used to replace a principal server by a backup server.
In the pop-up menu, select [Change server].
Note :

8.2.13 - Backup 1+1 of IONOS NMS servers (Option)

Caution : This function requires a specific license. It is not provided with the basic version of
IONOS-NMS.
8.2.13.1 - Introduction
Backup 1+1 of IONOS-NMS servers feature aims at making n IONOS-NMS server machines secure thanks to
an additional one able to run IONOS-NMS in case of main one has collapsed.
Switching from principal IONOS-NMS server to backup IONOS-NMS server is done by human action. No
automatic switching will be implemented, also about the switching from principal EMS-ADR to backup EMSADR.
Backup 1+1 is based on :
Page 183/205

- A Federator application.
- An Oracle database per server (main / backup) running permanently on all servers.
- n IONOS-NMS servers (1 main / 1 backup). IONOS-NMS servers run without interruption, but the backup
server is not launched if the main server runs. One of them must be in standby mode. If not, the backup is not
possible.
- An Easy Launcher application per server (main / backup); running at any time on each NMS server. It allows
to launch on the backup server periodic backups of databases od fifferent main servers and It controls all
steps of switching main server to backup server.
- A FTP or SFTP server per machine, running permanently. It enables to receive periodical backup performed
by the twin NMS server when it runs.
- Protection of servers does not concern the proxy that must be protected independently.
Note :

Also, if the ssh protocol is used, it can be necessary to configure the username
and password of the SFTP server on the EMS-ADR server. (see 1.2.3.30 - To
configure ssh protocol with EMS-ADR (ADR10000).
8.2.13.2 - Procedure of backup
First, you have to configure the main and backup servers using the secureUpdate.sh script and answer to the
questions.
Note :
In case of ADR10000 management, you have to enter the IP address of EMSADR and the path of backup in EMS-ADR: /sdh_home/ems/ENMConfig (by
default)
Then, you have to configure the Federator application using the configurationFederator.vbs script and answer
to the questions
Note:
In case of ADR10000 management, you have to confirm if a EMS-ADR exists
and to enter the IP address of the associated EMS-ADR.
Each server main is described in the file Federator.xml (folder Config) with a type principal.
The server of backup is described in the file Federator.xml (folder Config) with a type backup.
The backup server is stopped.
The icons of all servers of type main are displayed on the map of Federator.
The icon of backup server is displayed on the map of Federator. It is colored in blue, because the server is
unreacheable (stopped).
On each server main, a scheduled task is defined to launch automatically and regularly a backup of
database on the server main and on the server backup via FTP.
In case of ADR10000 management, a backup of EMS-ADR is also done.
On each server main, the applications Easy Launcher, FTP or SFTP, and IONOS-NMS server have been
launched.
On the server backup, the applications Easy Launcher and FTP or SFTP have been launched, but the
server IONOS-NMS is stopped.
From Federator, launch the menu [Change server] on the server main.
Note : A dialog box is displayed for each step (to launch, abort or continue the actions, and to inform).
Case 1 : the server main is running.
A backup of databse is done on the server main and sent on the server backup via FTP.
The server main is stopped.
The last backup of database of main server is restored on server backup.
Page 184/205

The server backup is started.
A client can be started on the server backup. The map is identical.
Case 2 : the server main is stopped.
The last backup of database of main server is restored on the server backup.
The server backup is started.
A client can be started on the server backup. The map is updated.
Notes :
The table of traps is updated with the IP address of backup server. The IP
address of main server is removed from the table. This update is not done for
equipment of type ADR155C P2.6, and for all equipment inaccessible or in
session locked.
Notes : In the following drawing the word FTP can be replaced by SFTP according your
configuration

Page 185/205
Main server use

Server 1
Easy
Launcher
Client PC
NMS
Server
Federator
Oracle
FTP
server
Backup Server (alive or stopped)

Easy
Launcher
...
Server n
Easy
Launcher
NMS
Server
(stopped)
FTP
server
NMS
Server
Oracle
content
not used
Oracle
FTP
server
Backup server use

Server 1
Easy
Launcher
Client PC
NMS
Server
Federator
Oracle
FTP
server
Backup Server
...
Easy
Launcher
Server i (alive or stopped)

Easy
Launcher
FTP
server
NMS
Server
(stopped)
NMS
Server
Oracle
NMS
Server
Oracle
FTP
server
Oracle
database
server i
content
not used
...
Changing server main <->backup

Client PC
Federator
Server origin (alive or stopped)

Easy
Launcher
FTP
server
NMS
Server
Server destination
Oracle
Easy
Launcher
FTP
server
(stopped)

Page 186/205
empty
database
APPENDIX - SPECIAL FUNCTIONS UPON OBJECTS

Object
Functions
Menus
Sub-network
Copy
Cut
Delete
Paste
Properties Read / Write
Rename
New Sub-Network
Edit
Creation
Network element (NE)
Copy
Cut
Delete
Paste
Rename
New NE
Audit/Inventory
NE to NMS aligns
Audit/NMS to NE
parameters reapplication
Audit/NMS to NE
parameters reactivation
Equipment View
Force Polling
NE database backup
NE database restoration
NE extraction
Export XML
SNMP View
Software Management
NE Discovering
Edit
Creation
Action
Tools
Links SDH
Delete
Rename
Switch MSP
New STM-n Link
Activate MSP
Add MSP
De-Activate MSP
Delete MSP
Dissociate MSP
NE extraction
NE insertion
Export XML
Show Links
RS Path trace configuration
Edit
Edit / Properties
Creation
Action
Links Ethernet
Delete
Edit
Page 187/205

Object
Functions
New Ethernet Link

Activate
De-Activate
Dissociate
Show Links
Menus
Creation
Action
Links WDM
Delete
Properties Read
New WDM Link
Activate
De-Activate
Dissociate
Show Links
Edit
Creation
Action
Trails SDH
Delete
Switch SNC
New Trail
Activate
De-Activate
Dissociate
Split / Merge
Protection activation
Protection de-activation
Export XML
Enable Real Time
Supervision
Disable Real Time
Supervision
Edit
Edit / Properties
Creation
Action
VCGRoup
Delete
Properties Read/Write
New VCGroup
Activate
De-Activate
Dissociate
Edit
Creation
Action
Ethernet Services
Delete
Properties Read /Write
New Ethernet Service
Activate
De-Activate
Dissociate
Edit
Creation
Action
Trails WDM
Delete
Edit
Properties Read /Write

New WDM Trail
Creation
Activate
De-Activate
Dissociate

Page 188/205
Action

Object
Functions
Menus
MS-Spring
Delete
Switch MS-SPRing
New Ring
Activate
De-Activate
Dissociate
Edit
Edit / Properties
Creation
Action
Alarms
Properties Read
Propagation
Clear
Acknowledge
Export
Unacknowledge
Edit
Edit/Properties
Properties Read
Edit
Change password
File
Forced backup
File
Tool-bar
Performances
Users
Applications
Administration
User
Groups
Profiles
New user
Copy / Paste
Delete
Properties
New groups
Copy / Paste
Delete
Properties
New profiles
Copy/Paste
Delete
Properties
Creation
Preferences
Tools
Edit
Creation
Edit
Creation
Edit
Preferences
Note : Whatever the object (Sub-network, NE, STM-Link, etc.), the Tools menu
presents the same functions : preferences and software management.

Page 189/205
APPENDIX - SNMP View Table

The SNMP parameter display and modification procedure is only valid for the ADR (ADR155C,
ADR63E1, EXT155HA, ADR2500C, ADR2500 EXTRA, ADR622) multiplexers in accordance with the
user profile (administrator, operator or observer).
See section 2.4.13 -To display and modify the SNMP parameters
MIB II MENU
System Infos
By clicking on SNMP View > MIB II > System Infos, the following window is displayed:
Figure: SNMP View : System Infos

Descr (read only) : system description.
ObjectID (read only) : identification of network management sub-system.
UpTime (read only) : duration (in hundredth of s.) since last initialization.
Contact (read/write) : identification of person contacted by node controlled.
Name (read/write) : administrative name assigned to node controlled.
Location (read/write) : physical location of node.
Services (read only) : value indicating services offered by system.
IP Infos
By clicking SNMP View > MIB II > IP Infos, the following window is displayed:
Figure: SNMP View : IP Infos

Page 190/205
Forwarding (read/write) : indicates if system is acting as an IP portal as concerns data

received, but not addressed to the system ("forwarding" = acting as portal; "not-forwarding" =
not acting as portal).
DefautTTL (read/write) : default value inserted in Time-To-Live field of IP header relative to

data generated on the system, each time a TTL value is not supplied by the transport layer
protocol.
InReceives (read only) : total number of input data received at the interfaces, errors
included.
InHdrErrors (read only) : number of input data ignored due to errors contained in IP header.
InAddrErrors (read only) : number of input data ignored since IP address in destination
header is not an address which is valid for reception on system.
ForwDatagrams (read only) : number of input data for which the system does not have a
final IP destination address.
InUnknownProtos (read only) : number of data locally addressed and received

successfully, but ignored due to an unknown or unsupported protocol.
InDiscards (read only) : number of input IP data for which no problem has been
encountered to prevent reception, but which are ignored.
InDelivers (read only) : total number of input data supplied successfully to IP protocols
(ICMP included).
OutRequests (read only) : total number of IP data whose local IP protocols (ICMP included)
supply the IP with transmission requests.
OutDiscards (read only) : number of output IP data for which no problem has been
encountered to prevent transmission to their destination, but which are ignored.
OutNoRoutes (read only) : number of IP data ignored since no route has been found to
transmit the data to its destination.
ReasmTimeout (read only) : maximum duration in seconds held by fragments received

before reassembly on system.
ReasmReqds (read only) : number of IP fragments received prior to reassembly.
ReasmOKs (read only) : number of IP data reassembled successfully.

ReasmFails (read only) : number of failures detected by IP reassembly algorithm (for

whatever reason: duration, errors, etc.).
FragOKs (read only) : number of IP data which have been fragmented successfully.
FragFails (read only) : number of IP data which have been ignored since they should have
been fragmented but which could not be fragmented.
FragCreates (read only) : number of fragments of IP data generated subsequent to system

fragmentation.

Page 191/205

IP Addresses
By clicking on SNMP View > MIB II > IP Addresses, the following window is displayed:
Figure: SNMP View : IP Addresses
Addr (read only) : IP address to which the input information address belongs.
IfIndex (read only) : unique index identifying interface to which this input is applicable.
NetMask (read only) : sub-network mask associated to system IP address.
BcastAddr (read only) : value of least significant bit in IP address generated; bit used to
send data on logical interface associated to IP address of this input
ReasmMaxSize (read only) : maximum size of address which the system can reorganize
using the fragmented IP data received on the interface.

Page 192/205

Routing Tables
By clicking SNMP View > MIB II > Routing Tables, the following window is displayed:
Figure: SNMP View : Routing Table

Dest (read/write) : destination IP address for this route.
IfIndex (read/write) : unique index which identifies the local interface through which the next
hop of this route should be achieved.
Metric1, Metric2, Metric3, Metric4 (read/write) : original or alternate routing measurement

for this route.

NextHop (read/write) : IP address of next hop of this route.

Type (read/write) : type of route which can be "other" (different from following types),
"invalid" (invalid route), "direct" (route directly connected to network), "indirect" (route
connected to a host/network/non-local sub-network).
Proto (read only) : routing mechanism by which the route has been ascertained.
Age (read/write) : number of seconds since last route update or otherwise defined as
correct.
Mask (read/write) : mask to be applied to destination address.
Metric5 (read/write) : alternate routing measurement for this route.
Info (read only) : reference to MIB definition.
Interfaces
By clicking on SNMP View > MIB II > System Infos, the following window is displayed:
Index (read only) : unique value for each interface.
Descr (read only) : text sequence containing information concerning the interface.
Type (read only) : type of interface.
Mtu (read only) : size of largest frame (specified in bytes) received or sent on an interface.
Speed (read only) : estimated passband of interface in bits per second.
PhysAddress (read only) : address of interface in intermediate layer under network layer in
protocol stack.
Page 193/205
AdminStatus (read only) : desired state of interface which can be "up" (ready to pass
packets), "down" or "testing" (in certain test modes).
OperStatus (read only) : current operational status of interface which can be "up" (ready to
pass packets), "down" or "testing" (in certain test modes).
LastChange (read only) : value of sysUpTime at moment when interface goes into its
current operational status.
InOctets (read only) : total number of bytes received on interface, shaping characters
included.
InUcastPkts (read only) : number sub-network packets delivered to a high layer protocol.
InNUcastPkts (read only) : number of multicast packets (i.e. sub-network, broadcast or

multicast sub-network) delivered to a high layer protocol.
InDiscards (read only) : number of incoming packets which have been selected to be
ignored even though no error has been detected to prevent transmission of the packets to a
high layer protocol.
InErrors (read only) : number of incoming packets containing errors preventing delivery by a
high layer protocol.
InUnknownProtos (read only) : number of packets received by interface and ignored due to
an unknown or unsupported protocol.
OutOctets (read only) : total number of bytes transmitted outside interface, shaping
characters included.
OutUcastPkts (read only) : total number of packets which the high layer protocols require in
order to be transmitted to a uniform sub-network address, including those which have been
ignored or which have not been sent.
OutNUcastPkts (read only) : total number of packets which the high layer protocols require
in order to be transmitted to a multicast address (i.e. a multicast sub-network), including those
which have been ignored or which have not been sent.
OutDiscards (read only) : number of peripheral packets which have been chosen to be
ignored even though no error has been detected to prevent transmission of the packets.
OutErrors (read only) : number of peripheral packets which cannot be transmitted due to
errors.
OutQLen (read only) : length of output packet queue (in packets).
Specific (read only) : reference to MIB definitions.

Page 194/205
EQUIPMENT MENU
Security
By clicking SNMP View > Equipment > Security, the following window is displayed and can only be
modified by an administrator:
Figure: SNMP View : Security
IONOSANMobserver, IONOSANMoperator, IONOSANMsupervisor : passwords which

can only be modified: these correspond to those entered in the window: Create a network
element / Security (see 2.4.1 - To create a network element ). These passwords are used for
the community of SNMP, SET and GET requests (IONOS-NMS will use the
IONOSANMsupervisor community) and to run the HTTP browser from IONOS-NMS in
accordance with the user profile.
directACCESSobserver, directACCESSoperator, directACCESSsupervisor : passwords

which can only be modified: these correspond to those of the HTTP protocol directly run from
Internet Explorer or Nescape (without IONOS-NMS).
directACCESSclientobserver, directACCESSclientoperator : not used.

Page 195/205

Traps
By clicking on SNMP View > Equipment > Traps, the following table is displayed and can only be
modified by an administrator
This table contains up to 10 lines which correspond to the operators receiving messages from the
equipment.
Figure: SNMP View : Traps
Up and Download
By clicking on SNMP View > Equipment > Up and Download, the following table is displayed and can
only be modified by an administrator
Figure SNMP View : Up and Download

Page 196/205
This table is used:

- to do a software download on equipment
- to do an upload or download of equipment configuration
- to do an upload or download of equipment configuration for network
LocalFile : gives the type of operation
Serveraddress : is the IP address of the TFTP server
RemoteFile :is the name of the file to be downloaded or uploaded
Direction : selects the direction of data stream (upload or download).
LoadProceed : is used to start loading
LoadDiagnostic : gives the result of loading
Manager Table
By clicking on SNMP View > Equipment > Manager Table, the following table is displayed and can
only be modified by an administrator
Figure SNMP View : Managers

This table is used to define the addresses of authorized IP addresses as manager (10 lines maximum).
If this table contains only address values which are equal to 0.0.0.0, no access filter is done.

Address : is the IP address of manager

ADM, OPR, OBS : are used to define the maximum authorized level for the corresponding
manager.

Page 197/205
SESSION MENU
Session Table
By clicking on SNMP View > Session, the following table is displayed and can only be modified by an
administrator
Figure SNMP View : Session
Lock : This variable is used to update the number of minutes for which a write session will
be active on equipment.
IP : is the IP address of the application which holds the write session.
Type : is the type of the application which holds the write session (HTTP or SNMP)
Lockdefault : is the initial value given for the number of minutes for which a write session
will be active on equipment (10 minutes by default)
Inactivity : is the number of minutes at the end of which the write session with a HTTP
manager is closed by equipment if there is no activity.

Page 198/205
APPENDIX Example of split/merge scenario

See Below, the procedure (on Windows O.S.) to be implemented to achieve the following scenario:
Alpha server divides its database in AP and AS sub-networks.
Original database (NMSSERVER):
Main View
/
\
Sub_AP
Sub_AS
Result database 1 :
Main View
|
Sub_AP
Result database 2 :
Main View
|
Sub_AS
The AP database is transferred to the Beta server where is the B database
We merge of AP and B databases to get a BP database
Procedure on the Alpha server :
Stop the Alpha server.
Check if the free space of Oracle database is sufficient (the space required must be at least equal
to twice of the initial database.
1- Run the split [parameters] script from the IONOS-NMS/bin/SplitMerge folder:
> split.bat DBNMS NMSSERVER nmssmn NMSSERVER _AP NMSSERVER_ AS Sub_AP
Two new additional users are created : NMSSERVER _AP and NMSSERVER_ AS
The NMSERVER_AP user contains the SUP_AP subnetwork (with nmssmn password)
The NMSERVER_AS user contains the SUP_AS subnetwork (with nmssmn password)
2- Perform an export of database (NMSSERVER _AP) to be transferred.
Update the Ionos-NMS/config/oracle_ext_assembly.xml file:
Replace NMSSERVER by NMSSERVER _AP
Run the export script from the IONOS-NMS/bin folder :
> export.bat fileAP.dat
Copy the fileAP.dat file from the Alpha server to the Beta server into the Ionos-NMS/bin folder:
3- Update the Ionos-NMS/config/oracle_ext_assembly.xml file:
Replace NMSSERVER_AP by NMSSERVER _AS
There are two possibilities :
Start the IONOS-NMS server with the NMSSERVER _AS user
Or (in order to keep the NMSSERVER user )

Perform an export of the NMSSERVER _AS database
From the Ionos-NMS/bin folder run the command :
> export.bat fileAS.dat
Replace NMSSERVER_AS by NMSSERVER
Perform an import of database:
From the Ionos-NMS/bin folder run the command:
> import.bat fileAS.dat
Start the IONOS-NMS server with the NMSSERVER user
Procedure on the Beta server :
Stop the Beta server.
Check if the free space of Oracle database is sufficient (the space required must be at least equal
to the sum of the both databases to merge)
1- Create a new Oracle user : NMSSERVER_AP (with nmssmn password)
2- Perform an import of NMSSERVER _AP database :
Replace NMSSERVER by NMSSERVER_AP
> import.bat fileAP.dat
3- Perform the merge of the both databases:
Run the merge [parameters] script from the IONOS-NMS/bin/SplitMerge folder:
> merge.bat DBNMS NMSSERVER _AP nmssmn NMSSERVER nmssmn NMSSERVER_MERGE
(in order to keep the IONOS-NMS Preferences of the NMSSRVER_AP user )
or
> merge.bat DBNMS NMSSERVER nmssmn NMSSERVER_AP nmssmn NMSSERVER_MERGE
(in order to keep the IONOS-NMS Preferences of the NMSSRVER user )
A new user NMSSERVER_MERGE is created in Oracle database
4- Update the Ionos-NMS/config/oracle_ext_assembly.xml file:
Replace NMSSERVER_AP by NMSSERVER_MERGE
There are two possibilities to start the IONOS-NMS server:

Start the IONOS-NMS server with the NMSSERVER _MERGE user
Or (in order to keep the NMSSERVER user )

Perform an export of the NMSSERVER _MERGE database
From the Ionos-NMS/bin folder run the command :
> export.bat fileMERGE.dat
Replace NMSSERVER_MERGE by NMSSERVER
> import.bat fileMERGE.dat
Start the IONOS-NMS server with the NMSSERVER user
5- Updating the traps managers table of the Network Elements
Check the Beta server is started.
From the IONOS-NMS\bin folder run the command:
> run.bat ./bsh/trapreceiverupdate.bsh
Enter the previous unused IP address of the Alpha server and the newer IP address of the Beta
server.
APPENDIX Example of SNMP trap generator configuration

See Below, an example of generation.xml file:
<generation>
<netype>
<Type value="ADR2500Extra"/>
</netype>
<distant>
</distant>
<filter-alarm>
<filter nename="Dijon"/>
<filter nename="Paris"/>
<filter status="critical"/>
<filter status="major"/>
<filter status="minor"/>
<filter eventtype="los"/>
<filter eventtype="ais"/>
<filter eventtype="defect"/>
<filter location="PPI" match="begin"/>
<filter location="BOARD" match="begin"/>
<filter location="TRIB 8 VCG#3" match="exact"/>
</filter-alarm>
<filter-event>
<filter nename="Lyon"/>
<filter eventtype="Login"/>
<filter location="SESSION" match="exact"/>
</filter-event>
</generation>
Interpretation of the different filtering criterias:

<generation>
<netype>
<Type value="ADR2500Extra"/>
</netype>
<distant>
</distant>
<filter-alarm>
<filter nename="Dijon"/>
OR
AND
<filter status="critical"/>
OR
<filter status="major"/>
OR
<filter status="minor"/>
AND
<filter eventtype="los"/>
OR
<filter eventtype="ais"/>
OR
<filter eventtype="defect"/>
AND
<filter location="PPI" match="begin"/>
OR
<filter location="BOARD" match="begin"/>
OR
<filter location="TRIB" match="exact"/>
AND
OR
AND
</filter-alarm>
<filter-event>
OR
<filter nename="Lyon"/>
AND
<filter eventtype="Login"/>
AND
OR
<filter location="SESSION" match="exact"/>
AND
</filter-event>
</generation>
APPENDIX Example of getTrailLongNames script usage

See Below, some examples of getTrailLongNames script usage:
# ./getTrailLongNames.sh 4ece884c143
host=10.66.212.122
Searching for trails : 4ece884c143
name[0]=My Trail Long Name 1
TrailLongName : end : nb = 1 : delay = 624
Note: 4ece884c143 is the alarm pk and name[x] = is the long name of the trail
>getTrailLongNames.bat 6cde884c1b2
host=10.66.212.122
Searching for trails : 6cde884c1b2
no trail for this alarm
Note: 6cde884c1b2 is the alarm pk, and there is no trail affected for this alarm pk
# ./getTrailLongNames.sh
host=10.66.212.122
Ionos server has 254 alarms
Searching for trails (0) : 741a9a4c0
....
Note: the script is run without input argument
Note :
If the Ionos-NMS server is not accessible, stopped or the IP address of the

server is not correct in the traplongname.xml file, there is a java exception with
connection refused or time-out result.
If the traplongname.xml file is not correct about the user name or password, an
error message is displayed with bad password or user name result.
SAGEMCOM SAS
Headquarters : 250, route de lEmpereur
92500 Rueil-Malmaison France
www.sagemcom.com
All rights reserved. The information and specifications included are subject to change without prior notice. Sagem Communications SAS tries to ensure that all information in this
document is correct, but does not accept liability for error or omission. Non contractual document. All trademarks are registered by their respective owners. Simplified joint stock
company - Capital 158.291.895 Euro - 440 294 510 RCS Paris

Ionos Nms p5 Ems User Guide 253153962-05

Uploaded by

Copyright:

Available Formats

Ionos Nms p5 Ems User Guide 253153962-05

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ionos Nms p5 Ems User Guide 253153962-05

Uploaded by

Copyright:

Available Formats

IONOS-NMS P5

Installation and User Guide

253 153 962-05

May 2011 Issue 05

(A new edition replaces all previous versions)

253 153 962-05

Creation of original user guide for

Update of user guide for version P5.4

Update of user guide for version P5.5

3 000 322 859 000 03

IONOS-NMS P5 EMS Installation and User Guide 253 153 962-05

IONOS-NMS P5 EMS Installation and User Guide 253 153 962-05

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

1.2.3 - Available configurations on Server IONOS-NMS.....................................................................................24

1.2.3.34 - To configure the SNMP trap generator................................................................................................................41

1.2.4 - Available configurations on Client IONOS-NMS ......................................................................................46

1.2.5 - The Application Easy Launcher under Windows .....................................................................................50

1.2.7 - To start the Client Application with Windows............................................................................................52

1.2.8 - To close the Server Application with Windows.........................................................................................53

1.2.9 - To close the Client Application ...................................................................................................................53

1.5.2 - To restore the database...............................................................................................................................62

1.5.3 - To migrate a database .................................................................................................................................63

1.5.4 - Database Management (Split & Merge) ....................................................................................................64

2.4.20 - EMS API Integration.................................................................................................................................123

3.1 - INTRODUCTION ......................................................................................................................................................130

8.2.11 - To Restore the database on a server ....................................................................................................183

APPENDIX - SPECIAL FUNCTIONS UPON OBJECTS ........................................................................................187

IONOS-NMS P5 EMS Installation and User Guide 253 153 962-05

FIGURE 2.41 : W INDOW GENERAL PARAMETERS REAPPLICATION RESULTS..................................................................105

FIGURE 7.15 : W INDOW ADMIN VIEW / PROFILES / DEFINITION .......................................................................................165

IONOS-NMS P5 EMS Installation and User Guide 253 153 962-05

Background Block Error (Bloc erron rsiduel)

Committed Information Rate

Equipment Management Layer

Equipment Management System

Local Craft Terminal

Severely Errored Second

Graphic User Interface

Management Control Panel

Management Information Base

Plesiochronous Digital Hierarchy

Peak Information Rate

Signal dIndication dAlarme

Simple Network Management Protocol

Terminal Portable Intelligent

Tributary Unit Group

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

Virtual Network Element (not managed by NMS)

IONOS-NMS P5 EMS Installation and User Guide 253 153 962-05

Create a Network Element / General

IONOS-NMS P5 EMS Installation and User Guide 253 153 962-05

Virtual network elements (VNE)

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)

refers to the user workstation.

refers to an application software run on the Console.