ionos nms p5 ems_nms user guide 253153959-05

IONOS-NMS P5

EMS / NMS Management

Installation and User Guide

253 153 959-05

May 2011 – Issue 05

IONOS-NMS P5 EMS/NMS Installation and User Guide – 253 153 959-05 /562 SAGEMCOM document. Reproduction and disclosure prohibited

LIST OF CHANGES

(A new edition replaces all previous versions)

N° Date Change description Page

253 153 959-05

3 000 322 858 000 03

October 2008

Creation of original user guide for version P5.3

All pages

253 153 959-05

3 000 322 858 000 04

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

253 153 959-05

3 000 322 858 000 05

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

IONOS-NMS P5 EMS/NMS Installation and User Guide – 253 153 959-05 SAGEMCOM document. Reproduction and disclosure prohibited /562

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 u pgrading of Electrical and Electronic Equipment Waste, which can have an effect on the en vironment and human health .


TABLE OF CONTENTS

LIST OF FIGURES ...........................................................................................................................................................12

LIST OF ABBREVIATIONS ............................................................................................................................................22

TYPOGRAPHICAL CONVENTIONS .............................................................................................................................23

GLOSSARY .......................................................................................................................................................................24

GLOSSARY .......................................................................................................................................................................24

1. SYSTEM INSTALLATION AND MANAGEMENT ...................................................................................................26

1.1 - GENERAL INFORMATION..........................................................................................................................................26 1.1.1 - IONOS-NMS ..................................................................................................................................................26 1.1.2 - Architecture....................................................................................................................................................27

1.1.2.1 - General architecture .................................................................................................................................................27 1.1.2.2 - Software architecture ...............................................................................................................................................28

1.1.3 - Workstations ..................................................................................................................................................28 1.1.4 - Man-Machine Interface (MMI) .....................................................................................................................28

1.2 - INSTALLING THE CD WITH WINDOWS .....................................................................................................................29 1.2.1 - To install the Server + Client Applications ................................................................................................29

1.2.1.1 - To install the Server Application (with Client) .......................................................................................................29 1.2.1.2 - To install the Client Application...............................................................................................................................31 1.2.1.3 - To install the Proxy Application...............................................................................................................................32 1.2.1.4 - To install the NMSperftool Application ...................................................................................................................33

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

1.2.3 - Available configurations on Server IONOS-NMS.....................................................................................35 1.2.3.1 - To configure TFTP server ........................................................................................................................................35 1.2.3.2 - To configure IP address of the server seen by the equipment...........................................................................35 1.2.3.3 - To configure the backup directories .......................................................................................................................35 1.2.3.4 - To configure the HTTP Proxy Function .................................................................................................................36 1.2.3.5 - To configure the function Traps Forward...............................................................................................................36 1.2.3.6 - To configure the parameters associated with the collection of performance ...................................................36 1.2.3.7 - To authorize the data entry of the accents and the special characters in the "Name" of the equipment .....38 1.2.3.8 - To inhibit control on the name of cross-connections in the audit of the equipment.........................................38 1.2.3.9 - To configure the time interval between IONOS-NMS and equipment...............................................................39 1.2.3.10 - To configure the performance parameters used by equipment .......................................................................39 1.2.3.11 - To configure the IONOS-NMS server name .......................................................................................................39 1.2.3.12 - To configure the send of mail on alarm change .................................................................................................39 1.2.3.13 - To configure the timers used for the send of mail ..............................................................................................40 1.2.3.14 - To configure the send of mail on critical alarm..................................................................................................40 1.2.3.15 - To configure the send of mail on a “system” alarm...........................................................................................41 1.2.3.16 - To configure the send of mail on a specific event type .....................................................................................41 1.2.3.17 - To send a mail in relation to one sub-network, NE type and NE name ..........................................................42 1.2.3.18 - To configure the format of the sent mail ..............................................................................................................43 1.2.3.19 - To configure a timer for the send of mails...........................................................................................................43 1.2.3.20 - To configure the feature of trails supervised in real time ..................................................................................43 1.2.3.21 - To allow the duplication of IP address .................................................................................................................44 1.2.3.22 - To configure the duration of the inactivity period and the number of attempts authorised before locking a user.............................................................................................................................................................................................44 1.2.3.23 - To activate the CORBA interface TMF814..........................................................................................................44 1.2.3.24 - To configure the scheduled task for Standby trail ..............................................................................................45 1.2.3.25 - To configure the Ldap connection ........................................................................................................................46 1.2.3.26 - To configure SSH protocol ....................................................................................................................................47 1.2.3.27 - To configure the alarm multi-criteria filtering.......................................................................................................48 1.2.3.28 - To manage the inaccessibility status of the FOT155A by a trap......................................................................49 1.2.3.29 - To configure parameters for the ADR10000 .......................................................................................................49 1.2.3.30 - To configure ssh protocol with EMS-ADR (ADR10000)....................................................................................50 1.2.3.31 - ADR10000 includes STM or data cards with electrical interfaces ...................................................................51


1.2.3.32 - To configure the number of Client sessions to the server.................................................................................51 1.2.3.33 - To configure the number of Client sessions per PC Client ...............................................................................52 1.2.3.34 - To configure the SNMP trap generator................................................................................................................52 1.2.3.35 - Configuration file to display the long name of the trail(s) in relation to its alarm pk ......................................54 1.2.3.36 - To run the getTrailLongNames script...................................................................................................................55 1.2.3.37 - To configure the FMX backup configuration file .................................................................................................55 1.2.3.38 - To configure the user rights to perform actions from the Federator application ............................................56

1.2.4 - Available configurations on Client IONOS-NMS ......................................................................................57 1.2.4.1 - To configure the help on line ...................................................................................................................................57 1.2.4.2 - To configure Internet Explorer to use HTTP Browser on the equipment of type ADR....................................57 1.2.4.3 - To configure Internet Explorer to use HTTP Proxy ..............................................................................................58 1.2.4.4 - To inhibit the data entry of spaces in the M1400 name of the equipment ........................................................58 1.2.4.5 - To activate the data entry of upercase in the M1400 name and longname......................................................58 1.2.4.6 - To configure the automatic deconnection of client after inactivity period .........................................................59 1.2.4.7 - To configure the number of NEs for which a warning message is displayed in NML View............................59 1.2.4.8 - To deactivate the automatic routing of trails/bearer SDH ...................................................................................59 1.2.4.9 - To configure the use of Proxy for SLF-v1 and SLF-N..........................................................................................60 1.2.4.10 - To configure the use of Proxy for SLF-H.............................................................................................................60 1.2.4.11 - To configure the use of client without an alarm window....................................................................................60 1.2.4.12 - To display the ADR10000 Proxy menu ...............................................................................................................60 1.2.4.13 - To configure the launching of the Equipment View (ADR10000) ....................................................................60

1.2.5 - The Application Easy Launcher under Windows .....................................................................................61 1.2.6 - To start the Server Application with Windows ..........................................................................................62

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

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

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

1.2.9 - To close the Client Application ...................................................................................................................64 1.2.10 - To start the HTTP Proxy Application with Windows ..............................................................................64 1.2.11 - To close the HTTP Proxy Application with Windows ............................................................................65 1.2.12 - To start the Proxy Application for SLF-v1 and SLF-N ...........................................................................65 1.2.13 - To close the Proxy Application for SLF-v1 and SLF-N .........................................................................66 1.2.14 - To start the Proxy Application for SLF-H under Windows ....................................................................66 1.2.15 - To close the Proxy Application for SLF-H ...............................................................................................66

1.3 - TO INSTALL THE CD FOR SOLARIS .........................................................................................................................67 1.3.1 - To install the Server and Client Applications ............................................................................................67

1.3.1.1 - To install the Server Application with Solaris ........................................................................................................67 1.3.1.2 - To install the Client Application with Windows......................................................................................................67 1.3.1.3 - To install the HTTP Proxy Application with Solaris ..............................................................................................67

1.3.2 - To install LCT application for equipment (FMX, Sagem-Link, FSP2000, FSP3000, ADR155E) ......68 1.3.3 - Available configurations on Server IONOS-NMS.....................................................................................68 1.3.4 - Available configurations on Client IONOS-NMS ......................................................................................68 1.3.5 - To start the Server Application with Solaris ..............................................................................................68 1.3.6 - To start the Client Application with Windows............................................................................................68 1.3.7 - To close the Server Application with Solaris.............................................................................................68 1.3.8 - To close the Client Application with Windows ..........................................................................................68 1.3.9 - To start the Proxy Applications with Solaris..............................................................................................68 1.3.10 - To stop the Proxy Application with Solaris..............................................................................................69 1.3.11 - To restart a SUN station with Solaris.......................................................................................................69 1.3.12 - To restart the Oracle database and the IONOS-NMS server with Solaris .........................................69

1.4 - TO INSTALL THE IONOS FEDERATOR ......................................................................................................................69 1.4.1 - To install the Client Application of IONOS-NMS ......................................................................................69 1.4.2 - To modify the configuration file ...................................................................................................................69 1.4.3 - To start the Ionos Federator........................................................................................................................70 1.4.4 - To close the Ionos Federator ......................................................................................................................71

1.5 - DATABASE MANAGEMENT .......................................................................................................................................71 1.5.1 - To backup the database ..............................................................................................................................71

1.5.1.1 - Backup on line from the client application .............................................................................................................71 1.5.1.2 - Backup on line from a script with Solaris...............................................................................................................72 1.5.1.3 - To configure a Periodic backup « off line » with Solaris......................................................................................72 1.5.1.4 - Copy of backup directories on magnetic tape with Solaris ................................................................................72

1.5.2 - To restore the database...............................................................................................................................73 1.5.2.1 - To restore of a backup with Windows ...................................................................................................................73


1.5.2.2 - List of available backup with Solaris ......................................................................................................................73 1.5.2.3 - Restore of a backup with Solaris ............................................................................................................................73 1.5.2.4 - Restore of backup directories copied on magnetic tape with Solaris ................................................................73

1.5.3 - To migrate a database .................................................................................................................................74 1.5.3.1 - Migration of a database with Windows. .................................................................................................................74 1.5.3.2 - Migration of a database with Solaris. .....................................................................................................................75

1.5.4 - Database Management (Split & Merge) ....................................................................................................75 1.5.4.1 - To split a IONOS-NMS database............................................................................................................................76 1.5.4.2 - Split with Solaris........................................................................................................................................................76 1.5.4.3 - Split with Windows ....................................................................................................................................................77 1.5.4.4 - To merge two IONOS-NMS databases .................................................................................................................77 1.5.4.5 - Merge with Solaris ....................................................................................................................................................78 1.5.4.6 - Merge with Windows ................................................................................................................................................78

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

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

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

2. TOPOLOGY MANAGEMENT ....................................................................................................................................87

2.1 - INTRODUCTION ........................................................................................................................................................87 2.2 - TOPOLOGY VIEW WINDOW .....................................................................................................................................87 2.3 - SUB-NETWORK ADMINISTRATION ............................................................................................................................89

2.3.1 - To create a sub-network ..............................................................................................................................89 2.3.2 - To display/modify the properties of a sub-network ..................................................................................91 2.3.3 - To move a sub-network ...............................................................................................................................93 2.3.4 - To delete a sub-network ..............................................................................................................................94 2.3.5 - To rename a sub-network............................................................................................................................94 2.3.6 - To change the sub-network background image .......................................................................................94 2.3.7 - To delete the sub-network background image .........................................................................................94

2.4 - ADMINISTRATION OF NETWORK ELEMENTS (NE, VNE) .........................................................................................95 2.4.1 - To create a network element.......................................................................................................................95 2.4.2 - To copy a network element (NE, VNE)....................................................................................................101 2.4.3 - To move a network element (NE, VNE) ..................................................................................................101 2.4.4 - To delete a network element (NE, VNE) .................................................................................................101 2.4.5 - To rename a network element (NE, VNE)...............................................................................................102 2.4.6 - To display and modify the properties of a network element .................................................................102 2.4.7 - To modify the M1400 name of a network element (NE, VNE) .............................................................104 2.4.8 - To audit a network element (NE)..............................................................................................................107 2.4.9 - To reapplicate the general parameters in a network element (NMS to NE) ......................................116 2.4.10 - To align the capacity parameters from a network element (NE to NMS) .........................................118 2.4.11 - To perform an inventory alignment for a network element (NE)........................................................119 2.4.12 - To display and modify the configuration of an equipment ..................................................................121 2.4.13 - To display and modify the SNMP parameters......................................................................................123 2.4.14 - To Back up the database of a network element...................................................................................124 2.4.15 - To restore the database of a network element.....................................................................................126 2.4.16 - To restore the database of ADR10000..................................................................................................127 2.4.17 - To update the software on a network element .....................................................................................128 2.4.18 - To Export the configuration of a network element ...............................................................................132 2.4.19 - To visualize the counters of performance for SLF-v1, Sagem-Link, SLF-N and SLF-H equipment...................................................................................................................................................................................133

2.4.19.1 - To Visualize the graphs of performance collect ...............................................................................................133 2.4.19.2 - To export the collects of performance ...............................................................................................................135

2.4.20 - EMS API Integration.................................................................................................................................135 2.4.21 - To discover NE from Network (IP discovery) .......................................................................................138 2.4.22 - To seek an equipment using its name or of its address IP.................................................................141


2.5 - ADMINISTRATION OF NETWORK ELEMENTS (NE, VNE) .......................................................................................142 2.5.1 - To create a network element EXT155HA................................................................................................142 2.5.2 - Display and modify the properties of a network element EXT155HA .................................................144 2.5.3 - To display the properties of physical NEs on an EXT155HA ...............................................................147 2.5.4 - To reactivate the MSPs protections in a network element (NMS to NE)...........................................148 2.5.5 - To reactivate the cross-connections in a network element (NMS to NE) ...........................................150 2.5.6 - To reactivate the bridging points in a network element (NMS to NE) .................................................152 2.5.7 - To reactivate the parameters of ETH/VCG ports in a network element (NMS to NE) ......................154 2.5.8 - To reactivate the MEPIDs in a network element (NMS to NE) ............................................................156 2.5.9 - To reactivate the continuity-check probes in a network element (NMS to NE) .................................158 2.5.10 - To reapplicate the monitoring in a network element (NMS to NE) ....................................................160

2.6 - SDH LINKS ADMINISTRATION................................................................................................................................164 2.6.1 - To create an STM-n link.............................................................................................................................164 2.6.2 - To delete an STM-n link .............................................................................................................................170 2.6.3 - To rename an STM-n link ..........................................................................................................................172 2.6.4 - To display / modify the properties of an STM-n link ..............................................................................172 2.6.5 - To visualize / modify the performances of an STM-n link .....................................................................180 2.6.6 - To add an MSP protection on an STM-n link..........................................................................................185 2.6.7 - To display / modify the properties of an STM-n link with an MSP protection.....................................187 2.6.8 - To visualize / modify the performances of an STM-n Link with an MSP protection..........................188 2.6.9 - To activate an MSP protection..................................................................................................................188 2.6.10 - To deactivate an MSP protection ...........................................................................................................189 2.6.11 - To delete an MSP protection ..................................................................................................................190 2.6.12 - To send MSP protection switchover commands..................................................................................190 2.6.13 - To dissociate the MSP protection ..........................................................................................................191 2.6.14 - To create a graphical link "no-STM-n"...................................................................................................192 2.6.15 - To delete a link "no-STM-n" ....................................................................................................................196 2.6.16 - To rename a link "no-STM-n"..................................................................................................................196 2.6.17 - To display / modify the properties of a link "no-STM-n" ......................................................................196 2.6.18 - To Insert a NE in an STM-n link .............................................................................................................198 2.6.19 - To extract an NE in an STM-n link .........................................................................................................204 2.6.20 - To Export the configuration of a link ......................................................................................................208

2.7 - ETHERNET LINK ADMINISTRATION .........................................................................................................................209 2.7.1 - To create an Ethernet link .........................................................................................................................209 2.7.2 - To activate an Ethernet link .......................................................................................................................212 2.7.3 - To deactivate an Ethernet link ..................................................................................................................213 2.7.4 - To delete an Ethernet link..........................................................................................................................215 2.7.5 - To dissociate an Ethernet link ...................................................................................................................215 2.7.6 - To display / modify the properties of an Ethernet link ...........................................................................216

2.8 - OPTICAL LINK ADMINISTRATION ............................................................................................................................220 2.8.1 - To create a WDM link.................................................................................................................................220 2.8.2 - To activate a WDM link ..............................................................................................................................224 2.8.3 - To deactivate a WDM link..........................................................................................................................226 2.8.4 - To delete a WDM link .................................................................................................................................227 2.8.5 - To dissociate a WDM link ..........................................................................................................................227 2.8.6 - To display / modify the properties of a WDM link...................................................................................227

3. NML VIEW ...................................................................................................................................................................232

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

3.2.1 - To display / filter a list of objects...............................................................................................................234 3.2.2 - To use an element of a list as input filter.................................................................................................236 3.2.3 - To display a list of SDH trails filtered by customer ................................................................................236 3.2.4 - List of objects in search area ....................................................................................................................237 3.2.5 - Points of performance ................................................................................................................................237

3.2.5.1 - To visualize information of a point of collection ..................................................................................................237 3.2.5.2 - To export the collections of current SDH performances points ........................................................................240 3.2.5.3 - To export the extremities points of performances 24h for SDH trails in “text” format ...................................240

4. SDH TRAILS MANAGEMENT .................................................................................................................................242

4.1 - INTRODUCTION ......................................................................................................................................................242 4.2 - DESCRIPTION OF "USER" TASKS ...........................................................................................................................243

4.2.1 - To create a VC4 bearer trail ......................................................................................................................243


4.2.2 - To create a trail (VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C) ....................................................249 4.2.3 - To create a trail with adoption (VC4 bearer, VC12, VC3, VC4, VC4-4C, VC4-16C) ........................258 4.2.4 - To create a bearer or trail (VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C) with automatic selection of the route ..............................................................................................................................................265 4.2.5 - To adopt a trail from a NE (VC4 bearer, VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C) ............271 4.2.6 - To adopt partially a trail from a NE (VC4 bearer, VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C )...................................................................................................................................................................................278 4.2.7 - To activate a trail.........................................................................................................................................285 4.2.8 - To deactivate a trail ....................................................................................................................................287 4.2.9 - To delete a trail............................................................................................................................................287 4.2.10 - To dissociate a trail ..................................................................................................................................288 4.2.11 - To add a SNC protection to a trail..........................................................................................................288 4.2.12 - To add a SNC protection to a trail by using adoption. ........................................................................294 4.2.13 - To adopt a trail with SNC protection from a NE (VC4 bearer, VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C) ........................................................................................................................................................301 4.2.14 - To adopt the SNC protection of a trail from a NE (VC4 bearer, VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C) ........................................................................................................................................................309 4.2.15 - To delete a SNC protection of a trail......................................................................................................318 4.2.16 - To activate the SNC protections of a trail .............................................................................................318 4.2.17 - To deactivate the SNC protections of a trail .........................................................................................319 4.2.18 - To send SNCP protection switchover commands ...............................................................................319 4.2.19 - To display/modify the properties of a trail .............................................................................................320 4.2.20 - Visualize / modify the performances of a trail.......................................................................................327 4.2.21 - Visualize / modify the performances of a trail with Near correlation .................................................332 4.2.22 - To create a Tandem Connection............................................................................................................336 4.2.23 - To activate a Tandem Connection .........................................................................................................338 4.2.24 - To deactivate a Tandem Connection.....................................................................................................339 4.2.25 - To delete a Tandem Connection ............................................................................................................341 4.2.26 - To dissociate a Tandem Connection .....................................................................................................341 4.2.27 - To display / modify the properties of a Tandem Connection..............................................................342 4.2.28 - To visualize / modify the performances of a trail with TCM................................................................343 4.2.29 - To audit the TCM parameters in a network element (NE) ..................................................................345 4.2.30 - To merge two VC4 bearers .....................................................................................................................347 4.2.31 - To split a VC4 bearer ...............................................................................................................................351 4.2.32 - To swap a SNC protection ......................................................................................................................355 4.2.33 - To invert the direction of a traffic carrier................................................................................................356 4.2.34 - To supervise in real time the trail status................................................................................................358 4.2.35 - To remove a trail from real time supervision ........................................................................................358 4.2.36 - Standby Mode management ...................................................................................................................359 4.2.37 - To Export the configuration of a trail ......................................................................................................360

5. VCGROUPS MANAGEMENT ..................................................................................................................................361

5.1 - INTRODUCTION ......................................................................................................................................................361 5.2 - DESCRIPTION OF “USER” TASKS ...........................................................................................................................363

5.2.1 - To create a VCGRoup................................................................................................................................363 5.2.1.1 - To create a VCGoup with ADR10000 ..................................................................................................................366

5.2.2 - To activate a VCGroup...............................................................................................................................371 5.2.3 - To deactivate a VCGroup ..........................................................................................................................373 5.2.4 - To delete a VCGroup .................................................................................................................................375 5.2.5 - To dissociate a VCGroup...........................................................................................................................376 5.2.6 - To display/modify the properties of a VCGRoup....................................................................................376 5.2.7 - To add a trail in a VCGroup.......................................................................................................................381 5.2.8 - To remove a trail from a VCGroup ...........................................................................................................382 5.2.9 - To activate the allocation of a trail in a VCGroup...................................................................................383 5.2.10 - To deactivate the allocation of a trail in a VCGRoup ..........................................................................385

6. ETHERNET POINT-TO-POINT SERVICES MANAGEMENT .............................................................................387


6.2.1 - To create an Ethernet Point-To-Point Service........................................................................................387 6.2.2 - To Activate an Ethernet Point-To-Point Service.....................................................................................393 6.2.3 - To Deactivate an Ethernet Point-To-Point Service ................................................................................394


6.2.4 - To delete an Ethernet Point-To-Point Service ........................................................................................395 6.2.5 - To dissociate an Ethernet Point-To-Point Service .................................................................................395 6.2.6 - To display/modify the properties of an Ethernet Point-To-Point Service............................................396

7. ETHERNET MULTIPOINT SERVICES MANAGEMENT .....................................................................................402


7.2.1 - To create an Ethernet MultiPoint Service................................................................................................402 7.2.2 - To add an ethernet port in an Ethernet Multipoint Service ...................................................................406 7.2.3 - To activate an ethernet port in an Ethernet MultiPoint Service............................................................409 7.2.4 - To deactivate an ethernet port in an Ethernet MultiPoint Service .......................................................410 7.2.5 - To delete an ethernet port in an Ethernet MultiPoint Service...............................................................413 7.2.6 - To dissociate an ethernet port in an Ethernet MultiPoint Service........................................................413 7.2.7 - To display/modify the properties of an ethernet port in an Ethernet MultiPoint Service .................413 7.2.8 - To add an internal Point-To-Point in an Ethernet Multipoint Service ..................................................415 7.2.9 - To activate an internal point-to-point in an Ethernet Multipoint Service .............................................421 7.2.10 - To deactivate an internal point-to-point d’un service ethernet multipoint .........................................422 7.2.11 - To delete an internal point-to-point in an Ethernet MultiPoint Service..............................................423 7.2.12 - To dissociate an internal point-to-point in an Ethernet MultiPoint Service.......................................423 7.2.13 - To visualize / modify the properties of an internal point-to-point in an Ethernet MultiPoint...........424 7.2.14 - To activate an Ethernet MultiPoint Service ...........................................................................................428 7.2.15 - To deactivate an Ethernet MultiPoint Service ......................................................................................429 7.2.16 - To delete an Ethernet MultiPoint Service..............................................................................................431 7.2.17 - To dissociate an Ethernet MultiPoint Service .......................................................................................431 7.2.18 - To visualize/modify the properties of an Ethernet MultiPoint Service...............................................432

8. OPTICAL TRAILS MANAGEMENT ........................................................................................................................436


8.2.1 - To create an Optical Trail ..........................................................................................................................436 8.2.2 - To activate an Optical Trail........................................................................................................................442 8.2.3 - To Deactivate an Optical Trail...................................................................................................................443 8.2.4 - To delete an Optical Trail...........................................................................................................................444 8.2.5 - To dissociate an Optical Trail....................................................................................................................445 8.2.6 - To add a O-SNC protection to an Optical Trail.......................................................................................445 8.2.7 - To delete an O-SNC protection of an Optical trail..................................................................................449 8.2.8 - To activate the O-SNC protections of an Optical trail............................................................................449 8.2.9 - To deactivate the O-SNC protections of an Optical trail .......................................................................450 8.2.10 - To send O-SNC protection switchover commands..............................................................................450 8.2.11 - To display / modify the properties of an Optical Trail ..........................................................................452

9. MS-SPRING PROTECTION MANAGEMENT .......................................................................................................459

9.1 - INTRODUCTION ......................................................................................................................................................459 9.2 - DESCRIPTION OF « USER » TASKS ........................................................................................................................459

9.2.1 - To create a ring ...........................................................................................................................................459 9.2.2 - To activate a ring ........................................................................................................................................464 9.2.3 - To deactivate a ring ....................................................................................................................................467 9.2.4 - To delete a ring ...........................................................................................................................................469 9.2.5 - To dissociate a ring ....................................................................................................................................469 9.2.6 - To display and modify the properties of a ring .......................................................................................469 9.2.7 - To send switchover commands ................................................................................................................475

10. ALARMS MANAGEMENT ......................................................................................................................................476

10.1 - INTRODUCTION ....................................................................................................................................................476 10.2 - MANAGEMENT OF CURRENT ALARMS .................................................................................................................477

10.2.1 - To display the current alarms..................................................................................................................477 10.2.2 - To acknowledge a current alarm ............................................................................................................478 10.2.3 - To unacknowledge a current alarm........................................................................................................479 10.2.4 - To filter current alarms by criteria...........................................................................................................479 10.2.5 - To locate a current alarm.........................................................................................................................481 10.2.6 - To display the properties of a current alarm .........................................................................................481 10.2.7 - To display the alarms unacknowledged cleared alarms .....................................................................482


10.2.8 - To display the new alarms.......................................................................................................................483 10.2.9 - To filter current alarms by multi-criteria .................................................................................................484 10.2.10 - To activate the send of mails on alarms modification .......................................................................486 10.2.11 - To activate the send of mails on critical alarm ...................................................................................487 10.2.12 - To propagate current alarms on the trails ...........................................................................................476 10.2.13 - To display the trails supervised in real time. ......................................................................................489 10.2.14 - To activate the Standby trail management. ........................................................................................490

11. HISTORIES MANAGEMENT .................................................................................................................................492

12. PREFERENCES MANAGEMENT .........................................................................................................................496

12.1 - INTRODUCTION ....................................................................................................................................................496 12.2 - PREFERENCES ....................................................................................................................................................496

12.2.1 - To change the IP address of the server ................................................................................................496 12.2.2 - To change an icon image ........................................................................................................................497 12.2.3 - To change the default properties of the Nes ........................................................................................498 12.2.4 - To change the default properties of sounds .........................................................................................499 12.2.5 - To change the default properties of trails..............................................................................................500 12.2.6 - To change the default properties of STM-n Links................................................................................501 12.2.7 - To change the default properties of VCGroups ...................................................................................503 12.2.8 - To change the default properties of MS-SPRings ...............................................................................504 12.2.9 - To change the default properties of “gravity failure” profiles ..............................................................505 12.2.10 - To change the default properties of QOS profiles .............................................................................506 12.2.11 - To change the default properties of Ethernet Links ..........................................................................507 12.2.12 - To change the default properties of Ethernet Services ....................................................................508 12.2.13 - To change the default properties of Optical Links .............................................................................509 12.2.14 - To change the default properties of Optical Trails.............................................................................510

13. USERS MANAGEMENT .........................................................................................................................................511

13.1 - INTRODUCTION ....................................................................................................................................................511 13.2 - ADMIN VIEW WINDOW .........................................................................................................................................511

13.2.1 - To create a profile.....................................................................................................................................513 13.2.2 - To create a group .....................................................................................................................................515 13.2.3 - To create a user ........................................................................................................................................517 13.2.4 - To display/modify the properties of a profile.........................................................................................518 13.2.5 - To display/modify the properties of a group .........................................................................................520 13.2.6 - To display/modify the properties of a user ............................................................................................522 13.2.7 - To copy a profile .......................................................................................................................................524 13.2.8 - To copy a group ........................................................................................................................................525 13.2.9 - To copy a user ..........................................................................................................................................526 13.2.10 - To delete a profile...................................................................................................................................528 13.2.11 - To delete a group ...................................................................................................................................528 13.2.12 - To delete a user ......................................................................................................................................528 13.2.13 - To lock a user..........................................................................................................................................528 13.2.14 - To unlock a user .....................................................................................................................................529

14. IONOS SERVERS FEDERATOR ..........................................................................................................................531

14.1 - INTRODUCTION ....................................................................................................................................................531 14.2 - DESCRIPTION OF IONOS SERVERS FEDERATOR ................................................................................................531

14.2.1 - The map of Federator ..............................................................................................................................531 14.2.2 - To visualize the alarms of a server ........................................................................................................532 14.2.3 - To filter current alarms of a server by criteria .......................................................................................533 14.2.4 - To open a IONOS-NMS Client on a server...........................................................................................535 14.2.5 - To open a IONOS-NMS Client on a server with another user ...........................................................535 14.2.6 - To force the connection of a server not connected .............................................................................536 14.2.7 - To force the refresh of the map ..............................................................................................................536 14.2.8 - To start a server ........................................................................................................................................536 14.2.9 - To stop a server ........................................................................................................................................536 14.2.10 - To backup the database of a server ....................................................................................................536 14.2.11 - To Restore the database on a server ..................................................................................................537 14.2.12 - To Change a server ...............................................................................................................................537 14.2.13 - Backup 1+1 of IONOS NMS servers (Option)....................................................................................537


14.2.13.1 - Introduction..........................................................................................................................................................537 14.2.13.2 - Procedure of backup ..........................................................................................................................................538

APPENDIX – SPECIAL FUNCTIONS UPON OBJECTS .........................................................................................541

APPENDIX – USER PROFILE RIGHTS .....................................................................................................................544

APPENDIX - SNMP VIEW TABLE ..............................................................................................................................547

MIB II MENU ..................................................................................................................................................................547 EQUIPMENT MENU .........................................................................................................................................................552 SESSION MENU..............................................................................................................................................................555

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

APPENDIX – EXAMPLE OF SNMP TRAP GENERATOR CONFIGURA TION ...................................................559

APPENDIX – EXAMPLE OF GETTRAILLONGNAMES SCRIPT USAG E ...........................................................561


LIST OF FIGURES

FIGURE 1.1 : GENERAL ARCHITECTURE OF IONOS-NMS .................................................................................................27 FIGURE 1.2 : IONOS-NMS SOFTWARE PLATFORM ...........................................................................................................28 FIGURE 1.3 : WINDOW - IONOS SOLUTIONS SERVER – DIAGNOSTIC.................................................................................29 FIGURE 1.4 : WINDOW - IONOS SOLUTIONS CLIENT – DIAGNOSTIC ..................................................................................31 FIGURE 1.5 : WINDOW - NMSPERFTOOL – SCHEDULED TASK...........................................................................................33 FIGURE 1.6 : EASY LAUNCHER (1) .......................................................................................................................................61 FIGURE 1.7 : EASY LAUNCHER (2) .......................................................................................................................................61 FIGURE 1.8 : EASY LAUNCHER (3) .......................................................................................................................................62 FIGURE 1.9 : WINDOW - START IONOS-NMS SERVER .......................................................................................................62 FIGURE 1.10 : DOS COMMANDS WINDOW ..........................................................................................................................63 FIGURE 1.11 : WINDOW - CONNECT TO WHICH NAME SERVER .........................................................................................63 FIGURE 1.12 : LOGIN WINDOW ...........................................................................................................................................63 FIGURE 1.13 : WINDOW – HTTP PROXY APPLICATION .....................................................................................................65 FIGURE 1.14 : WINDOW SLF-V1 SLF-N PROXY APPLICATION .........................................................................................66 FIGURE 1.15 : WINDOW – SLF-H PROXY APPLICATION ....................................................................................................66 FIGURE 1.16 : FORCE BACKUP WINDOW............................................................................................................................71 FIGURE 1.17 : BACKUP /DATABASE WINDOW .....................................................................................................................72 FIGURE 2.1 : TOPOLOGY MAIN VIEW ..................................................................................................................................87 FIGURE 2.2 : WINDOW – CREATE SUB-NETWORK (1).........................................................................................................89 FIGURE 2.3 : WINDOW – CREATE SUB-NETWORK (2).........................................................................................................90 FIGURE 2.4 : WINDOW – CREATE SUB-NETWORK (3).........................................................................................................90 FIGURE 2.5 : WINDOW – SUB-NETWORK PROPERTIES / GENERAL ....................................................................................91 FIGURE 2.6 : WINDOW – SUB-NETWORK PROPERTIES / ADDITIONAL INFORMATION .........................................................92 FIGURE 2.7 : WINDOW – SUB-NETWORK PROPERTIES / ALARMS ......................................................................................93 FIGURE 2.8 : WINDOW – OPEN ...........................................................................................................................................94 FIGURE 2.9 : WINDOW – CREATE A NETWORK ELEMENT (1)..............................................................................................95 FIGURE 2.10 : WINDOW – CREATE NE / SECONDARY IP ADDRESS).................................................................................96 FIGURE 2.11 : WINDOW – CREATE A NETWORK ELEMENT (2) ...........................................................................................96 FIGURE 2.12 : WINDOW – CREATE A NETWORK ELEMENT (3) ...........................................................................................97 FIGURE 2.13 : WINDOW – CREATE A NETWORK ELEMENT (4) ...........................................................................................98 FIGURE 2.14 : WINDOW – CREATE A NETWORK ELEMENT (5) ...........................................................................................99 FIGURE 2.15 : WINDOW – CREATE A NETWORK ELEMENT (6) .........................................................................................100 FIGURE 2.16 : WINDOW NETWORK ELEMENT PROPERTIES .............................................................................................102 FIGURE 2.17 : WINDOW NETWORK ELEMENT PROPERTIES / ALARMS.............................................................................103 FIGURE 2.18 : WINDOW NETWORK ELEMENT PROPERTIES .............................................................................................104 FIGURE 2.19 : WINDOW RENAME NE M1400 NAME (1) ..................................................................................................104 FIGURE 2.20 : WINDOW RENAME NE M1400 NAME (2) ..................................................................................................105 FIGURE 2.21 : WINDOW RENAME NE M1400 NAME (3) ..................................................................................................105 FIGURE 2.22 : WINDOW RENAME NE M1400 NAME (4) ..................................................................................................105 FIGURE 2.23 : WINDOW RENAME NE M1400 NAME (5) ..................................................................................................105 FIGURE 2.24 : WINDOW RENAME NE M1400 NAME (6) ..................................................................................................106 FIGURE 2.25 : WINDOW RENAME NE M1400 NAME (7) ..................................................................................................106 FIGURE 2.26 : WINDOW AUDIT RESULTS / GENERAL.......................................................................................................109 FIGURE 2.27 : WINDOW AUDIT RESULTS / INVENTORY / CARDS .....................................................................................109 FIGURE 2.28 : WINDOW AUDIT RESULTS / INVENTORY / MSPS ......................................................................................110 FIGURE 2.29 : WINDOW AUDIT RESULTS / CROSS-CONNECTIONS ..................................................................................110 FIGURE 2.30 : WINDOW AUDIT RESULTS / BRIDGING POINTS..........................................................................................111 FIGURE 2.31 : WINDOW AUDIT RESULTS / VCGROUPS...................................................................................................111 FIGURE 2.32 : WINDOW AUDIT RESULTS / MONITORING .................................................................................................112 FIGURE 2.33 : WINDOW AUDIT RESULTS / ETH/VCG PORTS .........................................................................................112 FIGURE 2.34 : WINDOW AUDIT RESULTS / MEPIDS ........................................................................................................113 FIGURE 2.35 : WINDOW AUDIT RESULTS / CONTINUITY-CHECK PROBES ........................................................................113 FIGURE 2.36 : WINDOW AUDIT RESULTS / SDH PORTS ..................................................................................................114 FIGURE 2.37 : WINDOW AUDIT RESULTS / MS-SPRING ................................................................................................114 FIGURE 2.38 : WINDOW AUDIT RESULTS / MS-SPRING / DETAIL ...................................................................................115 FIGURE 2.39 : WINDOW AUDIT RESULTS / FMX INVENTORY ...........................................................................................116 FIGURE 2.40 : WINDOW AUDIT / GENERAL REAPPLICATION ...........................................................................................117


FIGURE 2.41 : WINDOW GENERAL PARAMETERS REAPPLICATION RESULTS..................................................................117 FIGURE 2.42 : WINDOW GENERAL PARAMETERS REAPPLICATION RESULTS/DETAILS...................................................118 FIGURE 2.43 : WINDOW AUDIT / CAPACITY PARAMETERS ALIGNMENT...........................................................................118 FIGURE 2.44 : WINDOW GENERAL CAPABILITY PARAMETERS ALIGNMENT RESULTS ......................................................119 FIGURE 2.45 : WINDOW AUDIT / INVENTORY ALIGNMENT ...............................................................................................120 FIGURE 2.46 : WINDOW INVENTORY ALIGNMENT RESULTS .............................................................................................120 FIGURE 2.47 : WINDOW SAGEM-LINK EQUIPMENT VIEW .............................................................................................122 FIGURE 2.48 : WINDOW SAGEM-LINK LIGHT EQUIPMENT VIEW .................................................................................122 FIGURE 2.49 : WINDOW SLF-A EQUIPMENT VIEW...........................................................................................................122 FIGURE 2.50 : WINDOW NETWORK ELEMENT PROPERTIES / FMX INVENTORY ..............................................................123 FIGURE 2.51 : EXAMPLE OF SNMP VIEW WINDOW .........................................................................................................124 FIGURE 2.52 : WINDOW NETWORK ELEMENT BACKUP RESULTS ....................................................................................124 FIGURE 2.53 : WINDOW – NETWORK ELEMENT BACKUP FAILED RESULT........................................................................125 FIGURE 2.54 : WINDOW – CRITICAL FMX BACKUP MISSING ALARM IN FAULT VIEW .......................................................126 FIGURE 2.55 : WINDOW – WARNING CONFIGURATION CHANGED ALARM IN FAULT VIEW ..............................................126 FIGURE 2.56 : WINDOW NETWORK ELEMENT RESTORATION ..........................................................................................126 FIGURE 2.57 : WINDOW NETWORK ELEMENT RESTORATION RESULTS ..........................................................................127 FIGURE 2.58 : WINDOW SOFTWARE MANAGEMENT WINDOW ..........................................................................................128 FIGURE 2.59 : WINDOW SOFTWARE MANAGEMENT WINDOW / INVENTORY ....................................................................130 FIGURE 2.60 : WINDOW PERF VIEW ON SLF-V1..............................................................................................................133 FIGURE 2.61 : WINDOW PERF VIEW / NMSPERFTOOL ON SLF-V1 .................................................................................134 FIGURE 2.62 : WINDOW PERF VIEW / NMSPERFTOOL ON SLF-H (ETHERNET COUNTERS) ..........................................135 FIGURE 2.63 : DISCOVER NETWORK ELEMENTS WINDOW ..............................................................................................138 FIGURE 2.64 : WINDOW – DISCOVER NETWORK ELEMENTS/SEEDS...............................................................................138 FIGURE 2.65 : WINDOW – DISCOVER NETWORK ELEMENTS/COMMUNITIES ...................................................................139 FIGURE 2.66 : WINDOW – DISCOVER NETWORK ELEMENTS/DISCOVERING ...................................................................139 FIGURE 2.67 : WINDOW – DISCOVER NETWORK ELEMENTS/STATUS .............................................................................140 FIGURE 2.68 : WINDOW – TOPOLOGY VIEW/TREE............................................................................................................140 FIGURE 2.69 : WINDOW – TOPOLOGY VIEW / SEARCH NE ..............................................................................................141 FIGURE 2.70 : WINDOW CREATE A NETWORK ELEMENT/EXT155HA (1)........................................................................142 FIGURE 2.71 : WINDOW CREATE A NETWORK ELEMENT/EXT155HA (2)........................................................................143 FIGURE 2.72 : WINDOW CREATE A NETWORK ELEMENT/EXT155HA (3)........................................................................143 FIGURE 2.73 : WINDOW NETWORK ELEMENT PROPERTIES/GENERAL/EXT155HA .......................................................145 FIGURE 2.74 : WINDOW NETWORK ELEMENT PROPERTIES/INVENTORY/EXT155HA ....................................................146 FIGURE 2.75 : WINDOW NETWORK ELEMENT PROPERTIES/PHYSICAL NES/EXT155HA ..............................................147 FIGURE 2.76 : WINDOW SHOW PHYSICAL NES/EXT155HA...........................................................................................148 FIGURE 2.77 : WINDOW AUDIT / INVENTORY MSPS RE-ACTIVATION .............................................................................149 FIGURE 2.78 : WINDOW GLOBAL NMS TO NE MSPS RE-ACTIVATION RESULTS ...........................................................149 FIGURE 2.79 : WINDOW GLOBAL NMS TO NE MSPS RE-ACTIVATION RESULTS/ MSP DETAILS..................................150 FIGURE 2.80 : WINDOW GLOBAL NMS TO NE MSPS RE-ACTIVATION RESULTS/ MONITORING DETAILS .....................150 FIGURE 2.81 : WINDOW AUDIT / CROSSCONNECTIONS RE-ACTIVATION ........................................................................151 FIGURE 2.82 : WINDOW GLOBAL NMS TO NE CROSSCONNECTIONS RE-ACTIVATION RESULTS ..................................151 FIGURE 2.83 : WINDOW GLOBAL NMS TO NE CROSSCONNECTIONS RE-ACTIVATION RESULTS/DETAILS CNX ...........152 FIGURE 2.84 : WINDOW GLOBAL NMS TO NE CROSSCONNECTIONS RE-ACTIVATION RESULTS/DETAILS MONITOR ...152 FIGURE 2.85 : WINDOW AUDIT / BRIDGING POINTS RE-ACTIVATION...............................................................................153 FIGURE 2.86 : WINDOW GLOBAL NMS TO NE BRIDGING POINTS RE-ACTIVATION RESULTS.........................................153 FIGURE 2.87 : WINDOW GLOBAL NMS TO NE BRIDGING POINTS RE-ACTIVATION RESULTS/DETAILS ..........................154 FIGURE 2.88 : WINDOW AUDIT / ETH/VCG PORTS RE-ACTIVATION ..............................................................................155 FIGURE 2.89 : WINDOW GLOBAL NMS TO NE ETH/VCG PORTS RE-ACTIVATION RESULTS ........................................155 FIGURE 2.90 : WINDOW GLOBAL NMS TO NE ETH/VCG PORTS RE-ACTIVATION RESULTS/DETAILS .........................156 FIGURE 2.91 : WINDOW AUDIT / MEPIDS PORTS RE-ACTIVATION .................................................................................157 FIGURE 2.92 : WINDOW GLOBAL NMS TO NE MEPIDS RE-ACTIVATION RESULTS .......................................................157 FIGURE 2.93 : WINDOW GLOBAL NMS TO NE MEPIDS RE-ACTIVATION RESULTS/DETAILS ........................................158 FIGURE 2.94 : WINDOW AUDIT / CONTINUITY-CHECK PROBES RE-ACTIVATION .............................................................159 FIGURE 2.95 : WINDOW GLOBAL NMS TO NE CONTINUITY-CHECK PROBES RE-ACTIVATION RESULTS .......................159 FIGURE 2.96 : WINDOW GLOBAL NMS TO NE CONTINUITY-CHECK PROBES RE-ACTIVATION RESULTS/DETAILS ........160 FIGURE 2.97 : WINDOW AUDIT / MONITORING REAPPLICATION......................................................................................161 FIGURE 2.98 : WINDOW GLOBAL NMS TO NE MONITORING REAPPLICATION RESULTS................................................161 FIGURE 2.99 : WINDOW GLOBAL NMS TO NE MONITORING REAPPLICATION RESULTS/DETAILS .................................162 FIGURE 2.100 : WINDOW AUDIT /MSSPRINGS RE-ACTIVATION ....................................................................................162 FIGURE 2.101 : WINDOW NMS TO NE MSSPRINGS RE-ACTIVATION RESULTS ............................................................163 FIGURE 2.102 : WINDOW NEW .........................................................................................................................................164


FIGURE 2.103 : WINDOW CREATE STM-N LINK (1) .........................................................................................................164 FIGURE 2.104 : WINDOW CREATE STM-N LINK (2) .........................................................................................................165 FIGURE 2.105 : WINDOW CREATE STM-N LINK (3) .........................................................................................................166 FIGURE 2.106 : WINDOW CREATE STM-N LINK (4) .........................................................................................................167 FIGURE 2.107 : WINDOW CREATE STM-N LINK (5) .........................................................................................................167 FIGURE 2.108 : WINDOW CREATE STM-N LINK (6) .........................................................................................................168 FIGURE 2.109 : WINDOW CREATE STM-N LINK (7) .........................................................................................................169 FIGURE 2.110 : WINDOW CREATE STM-N LINK (8) .........................................................................................................169 FIGURE 2.111 : WINDOW CREATE STM-N LINK (9) .........................................................................................................169 FIGURE 2.112 : TOPOLOGY VIEW WITH A "SHORT-CUT" ICON..........................................................................................170 FIGURE 2.113 : WINDOW TOPOLOGY VIEW / SÉLECTION OF STM-N LINK......................................................................171 FIGURE 2.114 : WINDOW SHOW LINKS.............................................................................................................................171 FIGURE 2.115 : WINDOW RENAME STM-N LINK ..............................................................................................................172 FIGURE 2.116 : WINDOW STM-N LINK DETAILS / LINEAR DISPLAY (1) ...........................................................................173 FIGURE 2.117 : WINDOW STM-N LINK DETAILS / LINEAR DISPLAY (2) ...........................................................................174 FIGURE 2.118 : WINDOW STM-N LINK DETAILS / INFORMATION (3) ...............................................................................175 FIGURE 2.119 : WINDOW STM-N LINK DETAILS / INFORMATION (4) ...............................................................................176 FIGURE 2.120 : WINDOW STM-N LINK DETAILS / ADDITIONAL INFORMATION (5) ...........................................................177 FIGURE 2.121 : WINDOW STM-N LINK DETAILS / ALARMS (6) ........................................................................................178 FIGURE 2.122 : WINDOW STM-N LINK DETAILS /STATUS HISTORY (7)...........................................................................179 FIGURE 2.123 : WINDOW STM-N LINK DETAILS /OCCUPATION (8) .................................................................................180 FIGURE 2.124 : WINDOW STM-N LINK DETAILS /PERFORMANCES/DEFINITION/NEAR COUNTERS...............................181 FIGURE 2.125 : WINDOW STM-N LINK DETAILS /PERFORMANCES/DEFINITION/FAR COUNTERS..................................181 FIGURE 2.126 : WINDOW STM-N LINK DETAILS /PERFORMANCES/COLLECTED COUNTERS..........................................182 FIGURE 2.127 : WINDOW STM-N LINK DETAILS /PERFORMANCES/TEMPORAL GRAPHIC ..............................................183 FIGURE 2.128 : WINDOW TIME INTERVAL SELECTION ......................................................................................................184 FIGURE 2.129 : WINDOW POINT SELECTION ....................................................................................................................185 FIGURE 2.130 : WINDOW CREATE MSP...........................................................................................................................186 FIGURE 2.131 : WINDOW STM-N LINK DETAILS / INFORMATION .....................................................................................187 FIGURE 2.132 : WINDOW MSP ACTIVATION RESULT........................................................................................................188 FIGURE 2.133 : WINDOW MSP ACTIVATION RESULT/DETAILS.........................................................................................188 FIGURE 2.134 : WINDOW MSP DEACTIVATION RESULT...................................................................................................189 FIGURE 2.135 : WINDOW PROPERTIES STM-N LINK / INFORMATION ..............................................................................191 FIGURE 2.136 : WINDOW NEW .........................................................................................................................................192 FIGURE 2.137 : WINDOW CREATE LINK (1) ......................................................................................................................193 FIGURE 2.138 : WINDOW CREATE LINK (2) ......................................................................................................................194 FIGURE 2.139 : WINDOW CREATE LINK (3) ......................................................................................................................195 FIGURE 2.140 : WINDOW CREATE LINK (4) ......................................................................................................................195 FIGURE 2.141 : WINDOW RENAME LINK ...........................................................................................................................196 FIGURE 2.142 : WINDOW LINK DETAILS / LINEAR DISPLAY (1) ........................................................................................197 FIGURE 2.143 : WINDOW LINK DETAILS / INFORMATION (2) ............................................................................................197 FIGURE 2.144 : WINDOW LINK DETAILS / ADDITIONAL INFORMATION (3) ........................................................................198 FIGURE 2.145 : WINDOW NE INSERTION (1) ....................................................................................................................199 FIGURE 2.146 : WINDOW NE INSERTION (2) ....................................................................................................................200 FIGURE 2.147 : WINDOW NE INSERTION (3) ....................................................................................................................201 FIGURE 2.148 : WINDOW NE INSERTION (4) ....................................................................................................................201 FIGURE 2.149 : WINDOW NE INSERTION (5) ....................................................................................................................202 FIGURE 2.150 : WINDOW NE INSERTION (6) ....................................................................................................................203 FIGURE 2.151 : WINDOW NE EXTRACTION (1) ................................................................................................................204 FIGURE 2.152 : WINDOW NE EXTRACTION (2) ................................................................................................................205 FIGURE 2.153 : WINDOW NE EXTRACTION (3) ................................................................................................................206 FIGURE 2.154 : WINDOW NE EXTRACTION (4) ................................................................................................................206 FIGURE 2.155 : WINDOW NE EXTRACTION (5) ................................................................................................................207 FIGURE 2.156 : WINDOW NEW .........................................................................................................................................209 FIGURE 2.157 : WINDOW CREATE ETHERNET LINK (1) ...................................................................................................209 FIGURE 2.158 : WINDOW CREATE ETHERNET LINK (2) ...................................................................................................210 FIGURE 2.159 : WINDOW CREATE ETHERNET LINK (3) ...................................................................................................211 FIGURE 2.160 : WINDOW CREATE ETHERNET LINK (4) ...................................................................................................211 FIGURE 2.161 : WINDOW SHOW LINKS.............................................................................................................................212 FIGURE 2.162 : WINDOW ETHERNET LINK ACTIVATION RESULTS (1) ..............................................................................213 FIGURE 2.163 : WINDOW ETHERNET LINK ACTIVATION RESULTS (2) ..............................................................................213 FIGURE 2.164 : WINDOW ETHERNET LINK ACTIVATION RESULTS (3) ..............................................................................213


FIGURE 2.165 : WINDOW SHOW LINKS.............................................................................................................................214 FIGURE 2.166 : WINDOW ETHERNET LINK DE-ACTIVATION RESULTS (1) ........................................................................214 FIGURE 2.167 : WINDOW ETHERNET LINK DE-ACTIVATION RESULTS (2) ........................................................................215 FIGURE 2.168 : WINDOW ETHERNET LINK DE-ACTIVATION RESULTS (3) ........................................................................215 FIGURE 2.169 : WINDOW ETHERNET LINK PROPERTIES / INFORMATION (1)...................................................................216 FIGURE 2.170 : WINDOW ETHERNET LINK PROPERTIES / ADDITIONAL INFORMATION (2) ..............................................217 FIGURE 2.171 : WINDOW ETHERNET LINK PROPERTIES / OCCUPATION (3) ...................................................................217 FIGURE 2.172 : WINDOW ETHERNET LINK PROPERTIES / ALARMS (4) ...........................................................................218 FIGURE 2.173 : WINDOW ETHERNET LINK PROPERTIES /STATUS HISTORY (5)..............................................................219 FIGURE 2.174 : WINDOW NEW .........................................................................................................................................220 FIGURE 2.175 : WINDOW CREATE WDM LINK (1) ...........................................................................................................220 FIGURE 2.176 : WINDOW CREATE WDM LINK (2) ...........................................................................................................221 FIGURE 2.177 : WINDOW CREATE WDM LINK (3) ...........................................................................................................223 FIGURE 2.178 : WINDOW CREATE WDM LINK (4) ...........................................................................................................223 FIGURE 2.179 : WINDOW SHOW LINKS.............................................................................................................................224 FIGURE 2.180 : WINDOW WDM LINK ACTIVATION RESULTS (1) ......................................................................................225 FIGURE 2.181 : WINDOW WDM LINK ACTIVATION RESULTS (2) ......................................................................................225 FIGURE 2.182 : WINDOW WDM LINK ACTIVATION RESULTS (3) ......................................................................................225 FIGURE 2.183 : WINDOW WDM LINK DEACTIVATION RESULTS (1)..................................................................................226 FIGURE 2.184 : WINDOW WDM LINK DEACTIVATION RESULTS (2)..................................................................................226 FIGURE 2.185 : WINDOW WDM LINK DEACTIVATION RESULTS (3)..................................................................................226 FIGURE 2.186 : WINDOW WDM LINK PROPERTIES / LINEAR DISPLAY (1) ......................................................................228 FIGURE 2.187 : WINDOW WDM LINK PROPERTIES / INFORMATION (2) ..........................................................................229 FIGURE 2.188 : WINDOW WDM LINK PROPERTIES / ADDITIONAL INFORMATION (3) ......................................................229 FIGURE 2.189 : WINDOW WDM LINK PROPERTIES / OCCUPATION (4) ...........................................................................230 FIGURE 2.190 : WINDOW WDM LINK PROPERTIES / ALARMS (5) ...................................................................................230 FIGURE 2.191 : WINDOW WDM LINK PROPERTIES /STATUS HISTORY (6)......................................................................231 FIGURE 3.1 : NML VIEW : SEARCH AREA (1) ...................................................................................................................232 FIGURE 3.2 : NML VIEW : DETAILS AREA (2) ....................................................................................................................233 FIGURE 3.3 : NML VIEW / MAIN FILTER / TRAILS / FILTER ...............................................................................................234 FIGURE 3.4 : NML VIEW / MAIN FILTER / TRAILS / FILTER / LIST CONFIGURATION .........................................................235 FIGURE 3.5 : WINDOW – NML VIEW / BROWSE / SDH TRAIL CUSTOMER........................................................................236 FIGURE 3.6 : WINDOW NML VIEW/PERFORMANCES/INFORMATION ................................................................................238 FIGURE 3.7 : WINDOW NML VIEW /PERFORMANCES/COLLECTED COUNTERS ...............................................................238 FIGURE 3.8 : WINDOW NML VIEW /PERFORMANCES/TEMPORAL GRAPHIC....................................................................239 FIGURE 3.9 : WINDOW TIME INTERVAL SELECTION...........................................................................................................240 FIGURE 4.1 : WINDOW NEW ..............................................................................................................................................243 FIGURE 4.2 : WINDOW CREATE TRAIL/BEARER (1)..........................................................................................................243 FIGURE 4.3 : WINDOW CREATE TRAIL/BEARER : VC4 BEARER (2) .................................................................................244 FIGURE 4.4 : WINDOW CREATE TRAIL/BEARER : VC4 BEARER (3) .................................................................................245 FIGURE 4.5 : WINDOW CREATE TRAIL/BEARER : VC4 BEARER (4) .................................................................................246 FIGURE 4.6 : WINDOW CREATE TRAIL/BEARER : VC4 BEARER (5) .................................................................................247 FIGURE 4.7 : WINDOW CREATE TRAIL/BEARER : VC4 BEARER (6) .................................................................................248 FIGURE 4.8 : WINDOW CREATE TRAIL/BEARER : VC4 BEARER (7) .................................................................................248 FIGURE 4.9 : WINDOW CREATE TRAIL/BEARER : VC4 BEARER (8) .................................................................................249 FIGURE 4.10 : WINDOW NEW............................................................................................................................................249 FIGURE 4.11 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (1) ................................................................................250 FIGURE 4.12 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (2) ................................................................................250 FIGURE 4.13 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (3) ................................................................................252 FIGURE 4.14 : WINDOW CREATE TRAIL: VC12/VC3 STANDBY MODE TRAIL .................................................................252 FIGURE 4.15 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (4) ................................................................................253 FIGURE 4.16 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (5) ................................................................................254 FIGURE 4.17 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (6) ................................................................................255 FIGURE 4.18 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (7) ................................................................................255 FIGURE 4.19 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (8) ................................................................................257 FIGURE 4.20 : WINDOW NEW............................................................................................................................................258 FIGURE 4.21 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL WITH ADOPTION (1).......................................................258 FIGURE 4.22 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL WITH ADOPTION (2).......................................................259 FIGURE 4.23 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL WITH ADOPTION (3).......................................................260 FIGURE 4.24 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL WITH ADOPTION (4).......................................................261 FIGURE 4.25 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL WITH ADOPTION (5).......................................................262 FIGURE 4.26 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL WITH ADOPTION (6).......................................................263


FIGURE 4.27 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL WITH ADOPTION (7).......................................................263 FIGURE 4.28 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL WITH ADOPTION (8).......................................................264 FIGURE 4.29 : WINDOW NEW............................................................................................................................................265 FIGURE 4.30 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (1) ................................................................................265 FIGURE 4.31 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (2) ................................................................................266 FIGURE 4.32 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (3) ................................................................................267 FIGURE 4.33 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (4) ................................................................................268 FIGURE 4.34 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (5) ................................................................................269 FIGURE 4.35 : WINDOW CREATE TRAIL/BEARER: VC12 TRAIL (6) .................................................................................269 FIGURE 4.36 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (7) ................................................................................270 FIGURE 4.37 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (8) ................................................................................270 FIGURE 4.38 : WINDOW CREATE TRAIL/BEARER : VC12 TRAIL (8) ................................................................................271 FIGURE 4.39 : WINDOW AUDIT RESULTS..........................................................................................................................272 FIGURE 4.40 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (1) ...........................................272 FIGURE 4.41 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (2) ...........................................272 FIGURE 4.42 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (3) ...........................................273 FIGURE 4.43 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (4) ...........................................274 FIGURE 4.44 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (5) ...........................................275 FIGURE 4.45 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (6) ...........................................276 FIGURE 4.46 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (7) ...........................................277 FIGURE 4.47 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (8) ...........................................277 FIGURE 4.48 : WINDOW AUDIT RESULTS..........................................................................................................................278 FIGURE 4.49 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (1) .....................................278 FIGURE 4.50 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (2) .....................................279 FIGURE 4.51 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (3) .....................................279 FIGURE 4.52 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (4) .....................................280 FIGURE 4.53 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (5) .....................................281 FIGURE 4.54 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (6) .....................................281 FIGURE 4.55 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (7) .....................................282 FIGURE 4.56 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (8) .....................................283 FIGURE 4.57 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (9) .....................................284 FIGURE 4.58 : WINDOW TRAIL/BEARER/PROTECTION DISCOVERY (PARTIALLY) FROM NES (10)...................................284 FIGURE 4.59 : WINDOW TRAIL / ACTIVATE TRAIL .............................................................................................................285 FIGURE 4.60 : WINDOW TRAIL/BEARER ACTIVATION RESULTS ........................................................................................286 FIGURE 4.61 : WINDOW TRAIL/BEARER ACTIVATION RESULTS / DETAILS / CROSS-CONNECTIONS ................................286 FIGURE 4.62 : WINDOW TRAIL/BEARER ACTIVATION RESULTS / DETAILS / MONITORING RESULTS................................286 FIGURE 4.63 : WINDOW TRAIL/BEARER DE-ACTIVATION RESULTS / DETAILS..................................................................287 FIGURE 4.64 : WINDOW NML VIEW / TRAIL / ADD PROTECTION.....................................................................................288 FIGURE 4.65 : WINDOW CREATE PROTECTION PATH (1) .................................................................................................289 FIGURE 4.66 : WINDOW CREATE PROTECTION PATH (2) .................................................................................................290 FIGURE 4.67 : WINDOW CREATE PROTECTION PATH (3) .................................................................................................291 FIGURE 4.68 : WINDOW CREATE PROTECTION PATH (4) .................................................................................................292 FIGURE 4.69 : WINDOW CREATE PROTECTION PATH (5) .................................................................................................292 FIGURE 4.70 : WINDOW CREATE PROTECTION PATH (6) .................................................................................................293 FIGURE 4.71 : WINDOW CREATE PROTECTION WITH ADOPTION (1)................................................................................294 FIGURE 4.72 : WINDOW CREATE PROTECTION WITH ADOPTION (2)................................................................................295 FIGURE 4.73 : WINDOW CREATE PROTECTION WITH ADOPTION (3)................................................................................296 FIGURE 4.74 : WINDOW CREATE PROTECTION WITH ADOPTION (4)................................................................................297 FIGURE 4.75 : WINDOW CREATE PROTECTION WITH ADOPTION (5)................................................................................298 FIGURE 4.76 : WINDOW CREATE PROTECTION WITH ADOPTION (6)................................................................................299 FIGURE 4.77 : WINDOW CREATE PROTECTION WITH ADOPTION (7)................................................................................299 FIGURE 4.78 : WINDOW CREATE PROTECTION WITH ADOPTION (8)................................................................................300 FIGURE 4.79 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (1)............................................301 FIGURE 4.80 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (2)............................................301 FIGURE 4.81 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (3)............................................302 FIGURE 4.82 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (4)............................................302 FIGURE 4.83 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (5)............................................303 FIGURE 4.84 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (6)............................................304 FIGURE 4.85 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (7)............................................305 FIGURE 4.86 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (8)............................................306 FIGURE 4.87 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (9)............................................307 FIGURE 4.88 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (10)..........................................307


FIGURE 4.89 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (11)..........................................308 FIGURE 4.90 : WINDOW CREATE TRAIL/BEARER/PROTECTION DISCOVERY FROM NES (12)..........................................309 FIGURE 4.91 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (1) ....................................................................309 FIGURE 4.92 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (2) ....................................................................310 FIGURE 4.93 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (3) ....................................................................310 FIGURE 4.94 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (4) ....................................................................311 FIGURE 4.95 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (5) ....................................................................312 FIGURE 4.96 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (6) ....................................................................313 FIGURE 4.97 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (7) ....................................................................314 FIGURE 4.98 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (8) ....................................................................315 FIGURE 4.99 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (9) ....................................................................316 FIGURE 4.100 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (10)................................................................316 FIGURE 4.101 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (11)................................................................317 FIGURE 4.102 : WINDOW CREATE PROTECTION DISCOVERY FROM NES (12)................................................................317 FIGURE 4.103 : WINDOW SNC SWITCH COMMANDS .......................................................................................................320 FIGURE 4.104 : WINDOW TRAIL / PROPERTIES / LINEAR DISPLAY (1) .............................................................................321 FIGURE 4.105 : WINDOW TRAIL / PROPERTIES / LINEAR DISPLAY (2) .............................................................................322 FIGURE 4.106 : WINDOW TRAIL / PROPERTIES / INFORMATION.......................................................................................323 FIGURE 4.107 : WINDOW TRAIL / PROPERTIES / PROTECTION PATH...............................................................................324 FIGURE 4.108 : WINDOW TRAIL / PROPERTIES / ADDITIONAL INFORMATION...................................................................324 FIGURE 4.109 : WINDOW TRAIL / PROPERTIES / ALARMS................................................................................................325 FIGURE 4.110 : WINDOW TRAIL / PROPERTIES / STATUS HISTORY .................................................................................326 FIGURE 4.111 : WINDOW TRAIL / PROPERTIES / CC........................................................................................................326 FIGURE 4.112 : WINDOW TRAIL / PROPERTIES / OCCUPATION (BEARER) ......................................................................327 FIGURE 4.113 : WINDOW TRAIL /PERFORMANCES/DEFINITION/NEAR COUNTERS .........................................................328 FIGURE 4.114 : WINDOW TRAIL /PERFORMANCES/COLLECTED COUNTERS ...................................................................329 FIGURE 4.115 : WINDOW TRAIL /PERFORMANCES/TEMPORAL GRAPHIC........................................................................330 FIGURE 4.116 : WINDOW TIME INTERVAL SELECTION ......................................................................................................330 FIGURE 4.117 : WINDOW POINT SELECTION ....................................................................................................................331 FIGURE 4.118 : WINDOW - TRAIL /PERFORMANCES/DEFINITION/NEAR CORRELATION (1) ............................................333 FIGURE 4.119 : WINDOW - TRAIL /PERFORMANCES/DEFINITION/NEAR CORRELATION (2) ............................................333 FIGURE 4.120 : WINDOW – TRAIL /PERFORMANCES/COLLECTED COUNTERS OF NEAR CORRELATION POINT..............334 FIGURE 4.121 : WINDOW - /PERFORMANCES/TEMPORAL GRAPHIC OF NEAR CORRELATION POINT ..............................335 FIGURE 4.122 : WINDOW - /PERFORMANCES/TEMPORAL GRAPHIC OF NEAR CORRELATION POINT AND ASSOCIATED

POINTS. ......................................................................................................................................................................335 FIGURE 4.123 : WINDOW – TRAIL / CREATE TCM (1) .....................................................................................................336 FIGURE 4.124 : WINDOW – TRAIL / CREATE TCM (2) .....................................................................................................337 FIGURE 4.125 : WINDOW – TRAIL / CREATE TCM (3) .....................................................................................................337 FIGURE 4.126 : WINDOW – TRAIL /BEARER / ACTIVATE TCM .........................................................................................338 FIGURE 4.127 : WINDOW – TRAIL / BEARER / TCM ACTIVATION RESULTS......................................................................339 FIGURE 4.128 : WINDOW – TRAIL / BEARER /TCM WARNING WINDOW ..........................................................................339 FIGURE 4.129 : WINDOW – TRAIL /BEARER / DEACTIVATE TCM ....................................................................................340 FIGURE 4.130 : WINDOW – TRAIL / BEARER / TCM DEACTIVATION RESULTS .................................................................340 FIGURE 4.131 : WINDOW – TRAIL / BEARER / TCM DEACTIVATION RESULTS .................................................................340 FIGURE 4.132 : WINDOW – TRAIL / BEARER /TCM ..........................................................................................................342 FIGURE 4.133 : WINDOW – TRAIL / BEARER / TCM WARNING WINDOW ........................................................................342 FIGURE 4.134 : WINDOW – TRAIL /PERFORMANCES/DEFINITION WITH TCM .................................................................343 FIGURE 4.135 : WINDOW – TRAIL /PERFORMANCES/COLLECTED COUNTERS OF NEAR TCM POINT.............................344 FIGURE 4.136 : WINDOW – TRAIL /PERFORMANCES/TCM SELECTION POINT ................................................................344 FIGURE 4.137 : WINDOW - /PERFORMANCES/TEMPORAL GRAPHIC OF NEAR TCM POINT.............................................345 FIGURE 4.138 : WINDOW – AUDIT RESULTS / GENERAL..................................................................................................346 FIGURE 4.139 : WINDOW - AUDIT RESULTS / CROSSCONNECTIONS ..............................................................................346 FIGURE 4.140 : WINDOW MERGE OF VC4 BEARERS (1) .................................................................................................348 FIGURE 4.141 : WINDOW MERGE OF VC4 BEARERS (2) .................................................................................................349 FIGURE 4.142 : WINDOW MERGE OF VC4 BEARERS (3) .................................................................................................350 FIGURE 4.143 : WINDOW MERGE OF VC4 BEARERS (4) .................................................................................................350 FIGURE 4.144 : WINDOW SPLIT OF VC4 BEARER (1).......................................................................................................351 FIGURE 4.145 : WINDOW SPLIT OF VC4 BEARER (2).......................................................................................................352 FIGURE 4.146 : WINDOW SPLIT OF VC4 BEARER (3).......................................................................................................353 FIGURE 4.147 : WINDOW SPLIT OF VC4 BEARER (4).......................................................................................................354 FIGURE 4.148 : WINDOW SPLIT OF VC4 BEARER (5).......................................................................................................354 FIGURE 4.149 : WINDOW SWAP OF BEARER/TRAIL (1).....................................................................................................355


FIGURE 4.150 : WINDOW SWAP OF BEARER/TRAIL (2).....................................................................................................356 FIGURE 4.151 : WINDOW SWAP OF BEARER/TRAIL (3).....................................................................................................356 FIGURE 4.152 : WINDOW INVERT TRAIL/BEARER DIRECTION (1) ....................................................................................357 FIGURE 4.153 : WINDOW INVERT TRAIL/BEARER DIRECTION (2) ....................................................................................357 FIGURE 4.154 : WINDOW INVERT TRAIL/BEARER DIRECTION (3) ....................................................................................357 FIGURE 4.155 : WINDOW INVERT TRAIL/BEARER DIRECTION (4) ....................................................................................357 FIGURE 4.156 : WINDOW ENABLE REAL TIME SUPERVISION TRAIL / RESULT .................................................................358 FIGURE 4.157 : WINDOW DISABLE REAL TIME SUPERVISION TRAIL / RESULT ................................................................359 FIGURE 4.158 : WINDOW MODIFICATION STANDBY MODE FOR VC3/VC12 TRAILS.......................................................359 FIGURE 4.159 : WINDOW RESULT FOR STANDBY MODE (VC3/VC12 TRAILS)...............................................................360 FIGURE 5.1 : MCSM PORT NUMBERING AND ASSIGNMENT..............................................................................................362 FIGURE 5.2 : WINDOW NEW ..............................................................................................................................................363 FIGURE 5.3 : WINDOW CREATE VCGROUP (1) ................................................................................................................363 FIGURE 5.4 : WINDOW CREATE VCGROUP (2) ................................................................................................................364 FIGURE 5.5 : WINDOW CREATE VCGROUP (3) ................................................................................................................365 FIGURE 5.6 : WINDOW CREATE VCGROUP (4) ................................................................................................................365 FIGURE 5.7 : WINDOW CREATE VCGROUP (5) ................................................................................................................366 FIGURE 5.8 : WINDOW CONFIGURING GEOS PORTS (1) – ADR10000 .........................................................................367 FIGURE 5.9 : WINDOW CONFIGURING GEOS PORTS (2) – ADR10000 .........................................................................367 FIGURE 5.10 : WINDOW CREATE GFP TRAIL ...................................................................................................................368 FIGURE 5.11 : WINDOW CREATE VCGROUP....................................................................................................................368 FIGURE 5.12 : WINDOW CONFIGURING EOS PORTS (1) – ADR10000 ..........................................................................369 FIGURE 5.13 : WINDOW CONFIGURING EOS PORTS (2) – ADR10000 ..........................................................................370 FIGURE 5.14 : WINDOW CONFIGURING EOS PORTS (3) – ADR10000 ..........................................................................370 FIGURE 5.15 : WINDOW VCGROUP ACTIVATION RESULTS ..............................................................................................371 FIGURE 5.16 : WINDOW VCGROUP ACTIVATION RESULTS / DETAILS (1) ........................................................................372 FIGURE 5.17 : WINDOW VCGROUP ACTIVATION RESULTS / DETAILS (2)........................................................................372 FIGURE 5.18 : WINDOW VCGROUP TRAIL ALLOCATION ACTIVATION RESULTS / DETAILS ..............................................372 FIGURE 5.19 : WINDOW VCGROUP A-END TRAILS ALLOCATION ACTIVATION RESULTS / DETAILS ................................373 FIGURE 5.20 : WINDOW VCGROUP DE-ACTIVATION RESULTS........................................................................................373 FIGURE 5.21 : WINDOW VCGROUP DE-ACTIVATION RESULTS / DETAILS ........................................................................374 FIGURE 5.22 : WINDOW VCGROUP TRAIL ALLOCATION DE-ACTIVATION RESULTS / DETAILS ........................................374 FIGURE 5.23 : WINDOW VCGROUP A-END TRAILS ALLOCATION DE-ACTIVATION RESULTS / DETAILS ...........................375 FIGURE 5.24 : WINDOW VCGROUP / PROPERTIES / LINEAR DISPLAY .............................................................................377 FIGURE 5.25 : WINDOW VCGROUP / PROPERTIES / INFORMATION.................................................................................377 FIGURE 5.26 : WINDOW VCGROUP / PROPERTIES / ADDITIONAL INFORMATION ............................................................378 FIGURE 5.27 : WINDOW VCGROUP / PROPERTIES / GROUP ...........................................................................................378 FIGURE 5.28 : WINDOW VCGROUP / PROPERTIES / ALARMS..........................................................................................379 FIGURE 5.29 : WINDOW VCGROUP / PROPERTIES / OCCUPATION .................................................................................380 FIGURE 5.30 : WINDOW VCGROUP / PROPERTIES / STATUS HISTORY ...........................................................................380 FIGURE 5.31 : WINDOW VCGROUP / PROPERTIES / GROUP / TRAIL INCORPORATION ...................................................381 FIGURE 5.32 : WINDOW VCGROUP / PROPERTIES / GROUP / TRAIL INCORPORATION RESULT......................................382 FIGURE 5.33 : WINDOW VCGROUP / PROPERTIES / GROUP / REMOVE MEMBER FROM VCGROUP RESULT.................382 FIGURE 5.34 : WINDOW VCGROUP / ACTIVATE ALLOCATION .........................................................................................383 FIGURE 5.35 : WINDOW TRAIL ACTIVATION ALLOCATION RESULTS..................................................................................384 FIGURE 5.36 : WINDOW TRAIL ACTIVATE ALLOCATION RESULTS / DETAILS ....................................................................384 FIGURE 5.37 : WINDOW A-END TRAILS ALLOCATION ACTIVATION RESULTS / DETAILS ...................................................384 FIGURE 5.38 : WINDOW VCGROUP DE-ACTIVATE ALLOCATION......................................................................................385 FIGURE 5.39 : WINDOW VCGROUP TRAIL ALLOCATION DE-ACTIVATION RESULTS / DETAILS.........................................386 FIGURE 5.40 : WINDOW VCGROUP TRAIL DE-ACTIVATE ALLOCATION RESULTS / DETAILS............................................386 FIGURE 5.41 : WINDOW VCGROUP A-END ALLOCATION DEACTIVATION RESULTS / DETAILS .........................................386 FIGURE 6.1 : WINDOW NEW ..............................................................................................................................................387 FIGURE 6.2 : WINDOW CREATE ETHERNET POINT-TO-POINT SERVICE (1) ....................................................................388 FIGURE 6.3 : WINDOW CREATE ETHERNET POINT-TO-POINT SERVICE (2) ....................................................................388 FIGURE 6.4 : WINDOW C-VLAN CLASSIFICATION (3).......................................................................................................389 FIGURE 6.5 : WINDOW CREATE ETHERNET POINT-TO-POINT SERVICE (3) ....................................................................390 FIGURE 6.6 : WINDOW CREATE ETHERNET POINT-TO-POINT SERVICE (4) ....................................................................391 FIGURE 6.7 : WINDOW CREATE ETHERNET POINT-TO-POINT SERVICE (5) ....................................................................392 FIGURE 6.8 : WINDOW CREATE ETHERNET POINT-TO-POINT SERVICE (6) ....................................................................392 FIGURE 6.9 : WINDOW ETHERNET POINT-TO-POINT SERVICE ACTIVATION RESULTS .....................................................393 FIGURE 6.10 : WINDOW ETHERNET POINT-TO-POINT SERVICE ACTIVATION RESULTS / DETAILS (1) ............................393 FIGURE 6.11 : WINDOW ETHERNET POINT-TO-POINT SERVICE DEACTIVATION RESULTS ..............................................394


FIGURE 6.12 : WINDOW ETHERNET POINT-TO-POINT SERVICE DEACTIVATION RESULTS / DETAILS (1) ........................395 FIGURE 6.13 : WINDOW ETHERNET POINT-TO-POINT SERVICE / PROPERTIES / LINEAR DISPLAY (1) ...........................396 FIGURE 6.14 : WINDOW ETHERNET POINT-TO-POINT SERVICE / PROPERTIES / LINEAR DISPLAY (2) ...........................397 FIGURE 6.15 : WINDOW ETHERNET POINT-TO-POINT SERVICE / PROPERTIES / INFORMATION.....................................398 FIGURE 6.16 : WINDOW ETHERNET POINT-TO-POINT SERVICE / PROPERTIES / ADDITIONAL INFORMATION ................399 FIGURE 6.17 : WINDOW ETHERNET POINT-TO-POINT SERVICE / PROPERTIES / ROUTE/ LINK CONNECTION................399 FIGURE 6.18 : WINDOW ETHERNET POINT-TO-POINT SERVICE / PROPERTIES / ROUTE/ CROSSCONNECTION............400 FIGURE 6.19 : WINDOW ETHERNET POINT-TO-POINT SERVICE / PROPERTIES / ALARMS .............................................400 FIGURE 6.20 : WINDOW ETHERNET POINT-TO-POINT SERVICE / PROPERTIES / STATUS HISTORY ...............................401 FIGURE 7.1 : WINDOW NEW ..............................................................................................................................................402 FIGURE 7.2 : WINDOW CREATE ETHERNET MULTIPOINT SERVICE (1)............................................................................403 FIGURE 7.3 : WINDOW CREATE ETHERNET MULTIPOINT SERVICE (2)............................................................................403 FIGURE 7.4 : WINDOW CREATE ETHERNET MULTIPOINT SERVICE (3)............................................................................404 FIGURE 7.5 : WINDOW CREATE ETHERNET MULTIPOINT SERVICE (4)............................................................................405 FIGURE 7.6 : WINDOW CREATE ETHERNET MULTIPOINT SERVICE (5)............................................................................405 FIGURE 7.7 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD PORT (1) .....................................................................406 FIGURE 7.8 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD PORT (2) .....................................................................407 FIGURE 7.9 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD PORT (3) .....................................................................407 FIGURE 7.10 : WINDOW C-VLAN CLASSIFICATION (3) ....................................................................................................408 FIGURE 7.11 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD PORT (4) ...................................................................409 FIGURE 7.12 : WINDOW ETHERNET PORT ACTIVATION RESULTS .....................................................................................410 FIGURE 7.13 : WINDOW ETHERNET PORT ACTIVATION RESULTS / DETAILS ....................................................................410 FIGURE 7.14 : WINDOW ETHERNET PORT DEACTIVATION RESULTS ................................................................................412 FIGURE 7.15 : WINDOW ETHERNET PORT ACTIVATION RESULTS / DETAILS ....................................................................412 FIGURE 7.16 : WINDOW ETHERNET PORT / PROPERTIES / INFORMATION.......................................................................414 FIGURE 7.17 : WINDOW ETHERNET PORT / PROPERTIES / ALARMS ...............................................................................415 FIGURE 7.18 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD INTERNAL P2P (1) ....................................................416 FIGURE 7.19 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD INTERNAL P2P (2) ....................................................416 FIGURE 7.20 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD INTERNAL P2P (3) ....................................................417 FIGURE 7.21 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD INTERNAL P2P (4) ....................................................418 FIGURE 7.22 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD INTERNAL P2P (5) ....................................................419 FIGURE 7.23 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD INTERNAL P2P (6) ....................................................420 FIGURE 7.24 : WINDOW ETHERNET MULTIPOINT SERVICE / ADD INTERNAL P2P (7) ....................................................420 FIGURE 7.25 : WINDOW INTERNAL POINT-TO-POINT ACTIVATION RESULTS .....................................................................421 FIGURE 7.26 : WINDOW INTERNAL POINT-TO-POINT ACTIVATION RESULTS / DETAILS ....................................................421 FIGURE 7.27 : WINDOW INTERNAL POINT-TO-POINT DEACTIVATION RESULTS.................................................................422 FIGURE 7.28 : WINDOW INTERNAL POINT-TO-POINT DEACTIVATION RESULTS / DETAILS ................................................422 FIGURE 7.29 : WINDOW INTERNAL POINT-TO-POINT / PROPERTIES / LINEAR DISPLAY (1)..............................................424 FIGURE 7.30 : WINDOW INTERNAL POINT-TO-POINT / PROPERTIES / LINEAR DISPLAY (2)..............................................425 FIGURE 7.31 : WINDOW INTERNAL POINT-TO-POINT / PROPERTIES / INFORMATION .......................................................426 FIGURE 7.32 : WINDOW INTERNAL POINT-TO-POINT / PROPERTIES / ROUTE/ LINK CONNECTION ..................................427 FIGURE 7.33 : WINDOW INTERNAL POINT-TO-POINT / PROPERTIES / ROUTE/ CROSSCONNECTION ..............................427 FIGURE 7.34 : WINDOW INTERNAL POINT-TO-POINT / PROPERTIES / ALARMS ................................................................428 FIGURE 7.35 : WINDOW ETHERNET SERVICE MULTIPOINT ACTIVATION RESULTS ..........................................................428 FIGURE 7.36 : WINDOW ETHERNET SERVICE ACTIVATION RESULTS / DETAILS ...............................................................429 FIGURE 7.37 : WINDOW ETHERNET SERVICE DEACTIVATION RESULTS ...........................................................................430 FIGURE 7.38 : WINDOW ETHERNET SERVICE DEACTIVATION RESULTS / DETAILS...........................................................430 FIGURE 7.39 : WINDOW ETHERNET SERVICE MULTIPOINT / PROPERTIES / INFORMATION ............................................432 FIGURE 7.40 : WINDOW ETHERNET SERVICE MULTIPOINT / PROPERTIES / COMPOSITION............................................433 FIGURE 7.41 : WINDOW ETHERNET SERVICEMULTIPOINT / PROPERTIES / ADDITIONAL INFORMATION.........................433 FIGURE 7.42 : WINDOW ETHERNET SERVICE MULTIPOINT / PROPERTIES / ALARMS .....................................................434 FIGURE 7.43 : WINDOW ETHERNET SERVICE MULTIPOINT / PROPERTIES / STATUS HISTORY.......................................435 FIGURE 8.1 : WINDOW NEW ..............................................................................................................................................436 FIGURE 8.2 : WINDOW CREATE WDM TRAIL (1)..............................................................................................................437 FIGURE 8.3 : WINDOW CREATE WDM TRAIL (2)..............................................................................................................437 FIGURE 8.4 : WINDOW CREATE WDM TRAIL (3)..............................................................................................................438 FIGURE 8.5 : WINDOW CREATE WDM TRAIL (4)..............................................................................................................439 FIGURE 8.6 : WINDOW CREATE WDM TRAIL (5)..............................................................................................................440 FIGURE 8.7 : WINDOW CREATE WDM TRAIL (6)..............................................................................................................440 FIGURE 8.8 : WINDOW CREATE WDM TRAIL (7)..............................................................................................................441 FIGURE 8.9 : WINDOW WDM TRAIL ACTIVATION RESULTS ..............................................................................................442 FIGURE 8.10 : WINDOW WDM TRAIL ACTIVATION RESULTS / DETAILS (1)......................................................................442


FIGURE 8.11 : WINDOW WDM TRAIL ACTIVATION RESULTS / DETAILS (2)......................................................................443 FIGURE 8.12 : WINDOW WDM TRAIL ACTIVATION RESULTS / DETAILS (3)......................................................................443 FIGURE 8.13 : WINDOW WDM TRAIL DEACTIVATION RESULTS........................................................................................443 FIGURE 8.14 : WINDOW WDM TRAIL DEACTIVATION RESULTS / DETAILS (1) .................................................................444 FIGURE 8.15 : WINDOW WDM TRAIL DEACTIVATION RESULTS / DETAILS (2) .................................................................444 FIGURE 8.16 : WINDOW NML VIEW / WDM TRAIL / PROTECTION ...................................................................................445 FIGURE 8.17 : WINDOW CREATE PROTECTION O-SNC (1) .............................................................................................446 FIGURE 8.18 : WINDOW CREATE PROTECTION O-SNC (2) .............................................................................................447 FIGURE 8.19 : WINDOW CREATE PROTECTION O-SNC (3) .............................................................................................447 FIGURE 8.20 : WINDOW CREATE PROTECTION O-SNC (4) .............................................................................................448 FIGURE 8.21 : WINDOW CREATE PROTECTION O-SNC (5) .............................................................................................448 FIGURE 8.22 : WINDOW O-SNC SWITCH COMMANDS .....................................................................................................451 FIGURE 8.23 : WINDOW WDM TRAIL / PROPERTIES / LINEAR DISPLAY (1).....................................................................452 FIGURE 8.24 : WINDOW WDM TRAIL / PROPERTIES / INFORMATION ..............................................................................454 FIGURE 8.25 : WINDOW WDM TRAIL / PROPERTIES / PROTECTIONS .............................................................................455 FIGURE 8.26 : WINDOW WDM TRAIL / PROPERTIES / ADDITIONAL INFORMATION ..........................................................455 FIGURE 8.27 : WINDOW WDM TRAIL / PROPERTIES / ROUTE/ LINK CONNECTION .........................................................456 FIGURE 8.28 : WINDOW WDM TRAIL / PROPERTIES / ROUTE/ CROSSCONNECTION .....................................................456 FIGURE 8.29 : WINDOW WDM TRAIL / PROPERTIES / ALARMS .......................................................................................457 FIGURE 8.30 : WINDOW WDM TRAIL / PROPERTIES / STATUS HISTORY.........................................................................457 FIGURE 9.1 : WINDOW NEW ..............................................................................................................................................459 FIGURE 9.2 : WINDOW CREATE RING : SELECT FIRST NE ..............................................................................................460 FIGURE 9.3 : WINDOW CREATE RING : SELECT STMLINK...............................................................................................461 FIGURE 9.4 : WINDOW CREATE RING : SELECT PROPERTIES .........................................................................................462 FIGURE 9.5 : WINDOW CREATE RING : SELECT ADDITIONAL INFORMATION....................................................................463 FIGURE 9.6 : WINDOW TRAIL / ACTIVATE RING ................................................................................................................464 FIGURE 9.7 : WINDOW ACTIVATION RESULTS / RING .......................................................................................................465 FIGURE 9.8 : WINDOW ACTIVATION RESULTS / RING / DETAILS.......................................................................................465 FIGURE 9.9 : WINDOW ACTIVATION RESULTS / RING / DETAILS MONITORING .................................................................466 FIGURE 9.10 : WINDOW DEACTIVATION RESULTS / RING.................................................................................................467 FIGURE 9.11 : WINDOW DEACTIVATION RESULTS / RING / DETAILS ................................................................................467 FIGURE 9.12 : WINDOW DEACTIVATION RESULTS / RING / DETAILS MONITORING ..........................................................468 FIGURE 9.13 : WINDOW MS-SPRING PROPERTIES / LINEAR DISPLAY (1) .....................................................................470 FIGURE 9.14 : WINDOW MS-SPRING PROPERTIES / LINEAR DISPLAY (2) .....................................................................471 FIGURE 9.15 : WINDOW MS-SPRING MAP DISPLAY .......................................................................................................472 FIGURE 9.16 : WINDOW RING / PROPERTIES / PROPERTIES ...........................................................................................472 FIGURE 9.17 : WINDOW MS-SPRING / PROPERTIES / ADDITIONAL INFORMATION .........................................................473 FIGURE 9.18 : WINDOW MS-SPRING / PROPERTIES / DETAILS ......................................................................................474 FIGURE 9.19 : WINDOW MS-SPRING / PROPERTIES / ALARMS ......................................................................................474 FIGURE 9.20 : WINDOW MS-SPRING / PROPERTIES / DETAILS / SWITCH COMMANDS ..................................................475 FIGURE 10.1 : WINDOW TOPOLOGY VIEW / FAULT VIEW .................................................................................................477 FIGURE 10.2 : WINDOW TOPOLOGY VIEW / FAULT VIEW / POP-UP MENU.......................................................................478 FIGURE 10.3 : WINDOW TOPOLOGY VIEW / FAULT VIEW / LIST CONFIGURATION ...........................................................480 FIGURE 10.4 : WINDOW ALARMS PROPERTIES / INFORMATION .......................................................................................481 FIGURE 10.5 : WINDOW UNACKNOWLEDGED CLEARED AND NEW ALARMS .....................................................................482 FIGURE 10.6 : WINDOW UNACKNOWLEDGED CLEARED AND NEW ALARMS .....................................................................483 FIGURE 10.7 : WINDOW TOPOLOGY VIEW /FAULT VIEW / LIST CONFIGURATION / MULTI-CRITERIA FILTERING .............485 FIGURE 10.8 : WINDOW ALARM PROPERTIES / PROPAGATION ........................................................................................488 FIGURE 10.9 : WINDOW TOPOLOGY VIEW / SDH TRAILS (1) ...........................................................................................489 FIGURE 10.10 : WINDOW TOPOLOGY VIEW / SDH TRAILS (2).........................................................................................490 FIGURE 10.11 : WINDOW TOPOLOGY VIEW / SDH TRAILS ..............................................................................................490 FIGURE 11.1 : WINDOW LOG VIEW / EVENT LOG .............................................................................................................493 FIGURE 11.2 : WINDOW LOG VIEW / FAULT LOG..............................................................................................................493 FIGURE 11.3 : WINDOW LOG VIEW / SERVER LOG...........................................................................................................494 FIGURE 11.4 : WINDOW LOG VIEW / DATABASE LOG.......................................................................................................494 FIGURE 11.5 : WINDOW LOG VIEW / SDH TRAILS LOG ...................................................................................................495 FIGURE 12.1 : WINDOW PREFERENCES / IONOS-NMS..................................................................................................496 FIGURE 12.2 : WINDOW PREFERENCES / TOPOLOGY VIEW.............................................................................................497 FIGURE 12.3 : WINDOW PREFERENCES / NES .................................................................................................................498 FIGURE 12.4 : WINDOW PREFERENCES / SOUNDS ..........................................................................................................499 FIGURE 12.5 : WINDOW PREFERENCES / TRAIL ...............................................................................................................500 FIGURE 12.6 : WINDOW PREFERENCES / STMNLINK ......................................................................................................502


FIGURE 12.7 : WINDOW PREFERENCES / VCGROUPS.....................................................................................................503 FIGURE 12.8 : WINDOW PREFERENCES / RING ................................................................................................................504 FIGURE 12.9 : WINDOW PREFERENCES / GRAVITY PROFILES .........................................................................................505 FIGURE 12.10 : WINDOW PREFERENCES / QOS PROFILES .............................................................................................506 FIGURE 12.11 : WINDOW PREFERENCES / ETHERNET LINKS ..........................................................................................507 FIGURE 12.12 : WINDOW PREFERENCES / ETHERNET SERVICES ...................................................................................508 FIGURE 12.13 : WINDOW PREFERENCES / WDM LINKS ..................................................................................................509 FIGURE 12.14 : WINDOW PREFERENCES / WDM TRAILS ................................................................................................510 FIGURE 13.1 : WINDOW ADMIN VIEW / RESEARCH TREE .................................................................................................511 FIGURE 13.2 : WINDOW ADMIN VIEW / USERS .................................................................................................................512 FIGURE 13.3 : WINDOW ADMIN VIEW / GROUPS ..............................................................................................................512 FIGURE 13.4 : WINDOW ADMIN VIEW / PROFILES ............................................................................................................513 FIGURE 13.5 : WINDOW PROFILE CREATION (1)...............................................................................................................513 FIGURE 13.6 : WINDOW PROFILE CREATION (2)...............................................................................................................514 FIGURE 13.7 : WINDOW PROFILE CREATION (3)...............................................................................................................514 FIGURE 13.8 : WINDOW TOPOLOGY VIEW / PROFILE PROVIDER ACCESS .......................................................................515 FIGURE 13.9 : WINDOW GROUP CREATION (1) ................................................................................................................516 FIGURE 13.10 : WINDOW GROUP CREATION (2) ..............................................................................................................516 FIGURE 13.11 : WINDOW USER CREATION (1) FIGURE 13.12 : WINDOW LDAP USER CREATION (1) ..........................517 FIGURE 13.13 : WINDOW USER CREATION (2) .................................................................................................................517 FIGURE 13.14 : WINDOW USER CREATION (3) .................................................................................................................518 FIGURE 13.15 : WINDOW ADMIN VIEW / PROFILES / DEFINITION.....................................................................................519 FIGURE 13.16 : WINDOW ADMIN VIEW / PROFILES / AUTHORIZATION.............................................................................519 FIGURE 13.17 : WINDOW ADMIN VIEW / GROUPS / DEFINITION......................................................................................521 FIGURE 13.18 : WINDOW ADMIN VIEW / GROUPS / ADDITIONAL INFORMATION ..............................................................521 FIGURE 13.19 : WINDOW ADMIN VIEW / USERS / DEFINITION .........................................................................................522 FIGURE 13.20 : WINDOW ADMIN VIEW / LDAP USERS / DEFINITION................................................................................522 FIGURE 13.21 : WINDOW ADMIN VIEW / USERS / PASSWORD .........................................................................................523 FIGURE 13.22 : WINDOW ADMIN VIEW / USERS / ADDITIONAL INFORMATION .................................................................523 FIGURE 13.23 : WINDOW PROFILE CREATION (1) ............................................................................................................524 FIGURE 13.24 : WINDOW PROFILE CREATION (2) ............................................................................................................524 FIGURE 13.25 : WINDOW PROFILE CREATION (3) ............................................................................................................525 FIGURE 13.26 : WINDOW GROUP CREATION (1) ..............................................................................................................525 FIGURE 13.27 : WINDOW GROUP CREATION (2) ..............................................................................................................526 FIGURE 13.28 : WINDOW ADMIN VIEW / USERS / DEFINITION .........................................................................................526 FIGURE 13.29 : WINDOW USER CREATION (1) .................................................................................................................527 FIGURE 13.30 : WINDOW USER CREATION (2) .................................................................................................................527 FIGURE 13.31 : WINDOW USER CREATION (3) .................................................................................................................527 FIGURE 13.32 : WINDOW ADMIN VIEW / USERS / DEFINITION .........................................................................................529 FIGURE 13.33 : WINDOW ADMIN VIEW / USERS / DEFINITION .........................................................................................530 FIGURE 14.1 : WINDOW IONOS FEDERATOR ....................................................................................................................531 FIGURE 14.2 : WINDOW IONOS FEDERATOR / ALARMS....................................................................................................532 FIGURE 14.3 : WINDOW IONOS FEDERATOR / ALARMS / LIST..........................................................................................533 FIGURE 14.4 : WINDOW IONOS FEDERAOR / LIST CONFIGURATION.................................................................................534 FIGURE 14.5 : WINDOW IONOS FEDERATOR / LOGIN ON CLIENT.....................................................................................535


LIST OF ABBREVIATIONS

AU Administrative Unit

BBE Background Block Error

CIR Commited 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

MSP Multiplex Section Protection

MS-SPRing Multiplex Section Shared Protection Ring

NE Network Element

NML Network Management Layer

NMS Network Management System

PDH Plesiochronous Digital Hierarchy

PIR Peak Information Rate

QOS Quality Of Service

SDH Synchronous Digital Hierarchy

AIS Alarm indication signal

SNCP Sub-Network Connection Protection

SNMP Simple Network Management Protocol

STM-n Synchronous Transport Module n

TCM Tandem Connection Monitoring

TMN Telecommunication Management Network

TU Tributary Unit

TUG Tributary Unit Group

UAP Unavailable Period

UAS Unavailable second

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

VC4-4C 4 concatenated VC4 circuits

VC4-4V 4 virtually concatenated VC4 circuits

VNE Virtual Network Element (not managed by NMS)

WDM Wave lenght Density Multiplex

WTR Wait Time to Restore


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


GLOSSARY

Review of SDH

A SDH equipment carries data via a virtual container (VC) which can have three sizes: VC-12 for 2Mbit/s, VC-3 for 34Mbit/s or 45Mbit/s and VC-4 for 140Mbit/s.

In this way, a VC-4 can contain either traffic at 140Mbit/s, or VC-3 and VC-12. A header is added to the VC-4 to generate an STM-1 flow: n STM-1 can be multiplexed together to form an STM-n flow (n=1, 4, 16, 64).

The following types of multiplexer can be implemented:

� total connectivity", capable of cross connecting VC-12, VC-3 or VC-4 (ex : l’ADR155C)

� "limited connectivity", only capable of cross connecting VC-4.

An SDH equipment can carry traffic at a rate exceeding 140 Mbit/s using n VC-4 to create a concatenated flow of the order n (n=4).

SDH network element

An SDH network element comprises:

� interface boards with the PDH or SDH ports

� a switch to set up “cross-connections” between the VC-i (VC-3, VC-4, VC-12) carried on the various ports

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.

STM-n links

The SDH multiplexers implement optical and electrical interfaces to carry the STM-n traffic between 2 multiplexers. The links are connections between two SDH interfaces of two multiplexers having the same rate (STM-1, STM-4, STM-16 or STM-64).

The links are always bi-directional.

An STM-n link can carry:

� n VC-4 bearer trails

� n VC-4 trails

� n/4 VC4-4C concatenated trails

� a combination of VC-4 trails, VC-4 bearer trails and concatenated trails.

VC-4 bearer trails

The SDH multiplexing structure provides for a VC-4 to carry a 140Mbit/s flow, or 3 VC-3 or 63 VC-12 or a combination of VC-3 and VC-12. The VC-4 bearer trails are VC-4 trails in which VC-12 or VC-3 client trails may be inserted.

Multiplexers with limited connectivity only allow creation of VC-4 trails or VC-4 bearer trails. Multiplexers with full connectivity allow creation of VC-4 bearer trails and insertion of VC-12 and VC-3 client trails which can be routed via multiplexers with limited connectivity.


Link connection

A link connection is a VC-i (VC-3 or VC-12) in a VC-4 bearer. It is also a VC-4 in an STM-n link (a VC-4 bearer comprises one or several VC-4 link connections).

With a contiguous concatenated traffic, you have m VC-4 in a STM-n link (with n ≥ m).

Cross-connections

Cross-connections are connections set up within an equipment. This can be a relation between a PDH port on an interface board and a link connection, or between two link connections, or between two PDH ports on interface boards.

Trails

There are three types of trails: VC-12, VC3 or VC-4 which respectively carry 2Mbit/s traffic (VC-12), 34Mbit/s or 45Mbit/s (VC-3) and 140Mbit/s (VC-4). These end-to-end trails terminate on PDH or SDH interfaces.

Concatenated VC-4 trails

The SDH protocol enables carrying traffic with a rate greater than that of the STM-1: this is made possible through the use of concatenated VC-4 trails.

Contiguous concatenation

The traffic is carried by n consecutive VC-4 (n=4,16 …) linked to a single header of the first VC-4 in the group (same pointer value for VC-4s). In this case, all the multiplexers must be capable of carrying such a traffic.

Virtual concatenation

The traffic is carried by independent n VC-4. The interface operates as a reverse multiplexer. In this case, you simply need two interfaces providing the function on each end of the trail: it is recommended but not indispensable that the n VC-4 follow the same path through the network to minimize propagation time differences.

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 : refers to the person working on the Console on which the Client application software is run

Customer : refers to the company using the service.


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, SLF-N, SLF-H, SLT, SLF-A

- SAGEMCOM WDM equipments : FSP2000 and FSP3000,

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

- SAGEMCOM TV Num equipment : DTX and DTX2

- SAGEMCOM Data Concentrator : XP3000

IONOS-NMS offers EMS functions for all the SAGEMCOM equipments

� Equipment configuration and alarm management

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

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

� Configuration and management for links, bearers and trails

� Alarm management for trails

� Management of SDH protections: SNCP, MSP MS-SPRing (for ADR2500C, ADR2500 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

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.

CLIENT Plateform Windows

SGBD

SERVER Plateform Windows or Solaris

run

RMI, TCP

SNMP, TFTP HTTP

SAGEMCOM Equipment

SNMP Agent

HTTP Server

IONOS-NMS SERVER

Topology Alarms Sécurity

Performances

IONOS-NMS CLIENT

Generic functions

Internet Explorer

Specific functions to equipment

HTTP PROXY

HTTP

TFTP CLIENT

TFTP SERVER

Figure 1.1 : General architecture of IONOS-NMS



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 IONOS-NMS Server. IONOS NMS comprises the following modules:

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

� The Server Application which implements the core functions. The IONOS-NMS platform contains a Network element manager and a Network manager.

Figure 1.2 : IONOS-NMS software platform

1.1.3 - Workstations

The Client Applications are run on a PC whereas the Server Application is run either on a PC or on a 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.

Network

Manager

Network

Element

Manager

Faults on NE NE configuration

Faults on circuits

Security

Configuration of circuits

NE performances



� 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 C lient)

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

� 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 – Dia gnostic



Notes : It is possible to modify:

- the repertory used by default for backup of the database (c:\temp\oracle.backup) (see § 1.2.3.3 -)

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

To check that:

- IP address of the server seen by the equipment corresponds to IP address of the PC on which the server is installed (see § 1.2.3.2 -)

To use a HTTP Proxy, see § 1.2.4.3 -.

� Click on [Save configuration].

� Click on [Quit ] to quit the installation. At the end of the installation procedure, short cuts are available in menu Start :

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

� Ionos-NMS 5.5 Server : Server Application.

� TFTP : downloading software.

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

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

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

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

alone configuration (Server + 1 Client on the same computer).

Modification of license file

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

� Copy the file LICENSE.DAT, provided with application.

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

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

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

� In the folder, open the oracle_ext_assembly.xml file.

� 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>



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 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 "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]

� 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.

� 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).



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 click on the file "menu.vbs".

� Select the language ("English")

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

� Click on "Ionos HTTP Proxy 3.2 installation "

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

� Click on "HTPP" 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 -)

� Click on [Quit ] to quit the installation. 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 Sagem-Link 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 Sagem-Link F 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



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 (F MX, 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 click on the file "menu.vbs".

� Select the language ("English")

� Click on "Installation of a client PC"

� Click on "Optional TPI installation"



� 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].

� Click on [Quit ] to quit the installation.

� 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")



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-NM S

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 see n 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.



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 wi th 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.

� 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 - the maximum number of remaining lines after automatic export for the log associated with the points with collection 24h - > by defect 4000 - the maximum number of the log for the periods of unavailability - > per defect 10000 - the maximum number of remaining lines after automatic export for the log associated with the 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"/>

<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 accent s 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 -).


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



� Replace the line:

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



1.2.3.9 - To configure the time interval between IO NOS-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.


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.


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.


1.2.3.12 - To configure the send of mail on alarm c hange

This procedure is used to configure the send of mail on alarm change (apparition, clear, acknowledgement, unacknowledgement) (see § 10.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])



<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 IONOS-NMS..

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

1.2.3.13 - To configure the timers used for the sen d of mail

The timers are used for the send of mail (see § 10.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.


1.2.3.14 - To configure the send of mail on critic al alarm

This procedure is used to configure the send of mail on critical alarm appartion (see § 10.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 :




� 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 IONOS-NMS.


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



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

<systemt> false </systemt> by <systemt> true </systemt>




1.2.3.16 - To configure the send of mail on a speci fic event type



� In this folder, open the file criticAlarmConfig.xml 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)



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)




1.2.3.17 - To send a mail in relation to one sub-ne twork, 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.



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 § 10.2.11 - To activate the send of mails on critical alarm)


� In this folder, open the file criticAlarmConfig.xml

� 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, don’t modify its value (e.g. $EVENT is not correct, must be $EVENT_TYPE)

� Save and close the file criticAlarmConfig.xml 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 IONOS-NMS.

1.2.3.19 - To configure a timer for the send of mai ls

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


� In this folder, open the file criticAlarmConfig.xml

� Modify if necessary the value of this timer (in seconds), 0 is the value by default.

<Timer>30 </ Timer > Caution : The taking into account of the file modification will be effective only after launching of Server IONOS-NMS.

1.2.3.20 - To configure the feature of trails super vised 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"/>


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"/>


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 inactiv ity 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 § 13.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 :

<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 Stan dby 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



<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 don’t 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 Ionos-NMS\log\app\server.log

� Idem for :”log4j.category.com.sagem.ionos.nms.server.nml.priv.sec.SecNmlServiceImpl=DEBUG” and “log4j.category.com.sagem.ionos.nms.server.nml.priv.impl.NmlServiceLocal=DEBUG” about 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 c onnection .

� Save and close the file server.xml

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

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

� Modify the following line  <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.



� Modify the following line <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 fi ltering

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 § 10.2.9 - To filter current alarms by multi-criteria

� 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 " />

� Save and close the file server-advanced.xml


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/" />



� Modify the following line : <var name="EMSADRVersion" type="java.lang.String" value="8.1" />



Type the EMS-ADR version number: 7.2 for ADR10000 / EMS-ADR R7.2 8.1 for ADR10000 / EMS-ADR R8.1

� Modify the following line : <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:

� Modify the following line : <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

� Modify if necessary the following line : <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

� Modify the following line : <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 Show Current Configuration 2 Check Oracle DB status 3 Apply Infrastructure Layer to DB 4 Insert EMS XDM schema to DB 5 Remove EMS XDM schema from DB 6 Empty EMS XDM Database data 7 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

� Modify if necessary the following line : <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)

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 EMS-ADR 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 sessio ns 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)

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 sessio ns 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 sessio ns is reached, a message “Only X maxPCSession(s) is allowed on <IP_Address_of_PC_Cli ent> “ 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>

</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"/>

<IpAddress value="10.0.0.2/164"/> <IpAddress value="10.0.0.3/165"/> <IpAddress value="10.0.0.4/166"/>

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. No tag means there is no filtering on this field. <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. No tag means there is no filtering on this field.

<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 t he exactly string of the alarm location Alarm trap with exactly the "PPI-LTU 5:1" location will be generated. No tag means there is no filtering on this field. <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. No tag means there is no filtering on this field. <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.



Alarm traps between the NMS begin date “nmsdatebegin” and the NMS end date “nmsdateend” will be generated No tag means there is no filtering on this field.

� 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 No tag means there is no filtering on this field.

<filter eventtype=""/> Enter the type of event, ex <filter eventtype="Login"/> Event trap with a type “Login” will be generated. No tag means there is no filtering on this field.

<filter location="" match="begin"/> 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. No tag means there is no filtering on this field.

<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 t he exactly string of the event location Event trap with exactly the "SESSION" location will be generated. No tag means there is no filtering on this field. <filter nmsdatebegin="2009-12-31 05:00:00" nmsdateend="2010-03-31 09:00:00"/> 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 No tag means there is no filtering on this field.

� Save and close the file generation.xml


Note (1): Absence of tag in “nename”, “status”, “ev enttype”, “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 def ined in the generation.xml file, they will be inter preted 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 n ame 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

<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 usag e

1.2.3.37 - To configure the FMX backup configuratio n 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 FMX–GIES inventory is available. by



<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 the installation (by default Ionos-NMS), select the Config/EasyLauncher folder.

� 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 Io nos-NMS server (§13- 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 don’t 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 displaye d.



1.2.4 - Available configurations on Client IONOS-NM S

1.2.4.1 - To configure the help on line


� In the folder, open the file Profiler.xml. Replace the line :

<HELP html="${BROWSER} ${ROOTDIR}/help/fr/hh_start1.htm"/> by <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 HTT P 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.



1.2.4.3 - To configure Internet Explorer to use HTT P 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 for all the protocols.

- 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 th e 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




� 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"/>


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 o f 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"/>


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"/>


1.2.4.8 - To deactivate the automatic routing of tr ails/bearer SDH



� Replace the lines: <var name="SDHAutoRoutingActivated" type="java.lang.Boolean" value="true"/>

by

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

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


� In the folder, open the file Profiler.xml.

� Uncomment and modify the line : <FHPROXY value="-ipproxy ${IP_SRV} portproxy 5588 SUPERVISOR"/>

� Comment the line : 


1.2.4.10 - To configure the use of Proxy for SLF-H


� In the folder, open the file Profiler.xml.

� Uncomment and modify the line : <FHPROXY_SNMP value="-ipproxy ${IP_SRV}:5590"/>

� Comment the line : <!—FHPROXY_SNMP value=""/-->


1.2.4.11 - To configure the use of client without a n alarm window


� In the folder, open the file client-advanced.xml.

� Add the line : <<var name="FaultViewEnabled" type="java.lang.Boolean" value="false"/>


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 "/> Caution: The taking into account of the file modification will be effective only after launching of Client IONOS-NMS.

1.2.4.13 - To configure the launching of the Equipm ent 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,



� 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.


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 :




� Backup oracle database : to perform a backup of oracle database

� Restore oracle database : to perform a restore of oracle database (grayed when the server is started

� 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 : to perform a Proxy configuration (grayed if the software is not installed)

� Generate Pack trace : to generate a zipped file of several files used for debug

1.2.6 - To start the Server Application with Window s

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 ser ver 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 Launc her 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.



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 Window s

� 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 13.20)



� 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 Ionos-NMS 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 7- Note: 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 Window s

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 W indows

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.



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 W indows

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.



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 Sagem-Link 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 u nder 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)



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 Applicatio ns

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 So laris

Caution: The installation of the Server Application must be carried out by a personnal qualified Sagem.

� 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 Wi ndows

� Follow the installation instructions: see § 1.2.1.2 -

1.3.1.3 - To install the HTTP Proxy Application wit h 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



- ADR155CPE - ADR 622

1.3.2 - To install LCT application for equipment (F MX, Sagem-Link, FSP2000, FSP3000, ADR155E)

See § 1.2.2 -

1.3.3 - Available configurations on Server IONOS-NM S

See § 1.2.3 -

1.3.4 - Available configurations on Client IONOS-NM S

See § 1.2.3.28 -

1.3.5 - To start the Server Application with Solari s

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 Window s

See § 1.2.7 -

1.3.7 - To close the Server Application with Solari s



� Enter the command /tools/IONOS-NMS/scripts/stopnmsserver [↵]

� Do a logout.

1.3.8 - To close the Client Application with Window s

See § 1.2.9 -

1.3.9 - To start the Proxy Applications with Solari s

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:



� Enter the command /tools/IONOS-NMS/scripts/startproxy [↵]

� Check with the command ps –ef | grep proxy if the process is activated.



� Logout.

1.3.10 - To stop the Proxy Application with Solaris



� Enter the command /tools/IONOS-NMS/scripts/stopproxy [↵]

� Logout.

1.3.11 - To restart a SUN station with Solaris



� Enter the command /tools/IONOS-NMS/scripts/globalrestart [↵]

� Do a logout.

1.3.12 - To restart the Oracle database and the ION OS-NMS server with Solaris



� 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)



�

� 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:

. 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.

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.



Open the properties Start/All Programms/IONOS-NMS/I ONOS-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:

. 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.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 applicatio n

� 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.



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-dd—nn.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 Solari s



� 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 lin e » with Solaris



� 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 ta pe with Solaris



� Put a tape not write protected in the tape drive



� 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


� Enter the command ksh [↵].

� 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



� If necessary, run the /tools/IONOS-NMS/scripts/backup-list script

Notes : The filenames are displayed in the followin g 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 m agnetic tape with Solaris



� 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.



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



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 ( IONOS-NMS/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 ).



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



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 : username of the second new split user subnetwork_to_split : 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

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 : username of the second new split user subnetwork_to_split : 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



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 : SID (by default DBNMS) 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

Indicate the following parameter values SID : SID (by default DBNMS) 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 af ter 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



• 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 pr eliminary 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 in stallation (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 ADR1000 0 / EMS-ADR R7.2 And EMS-ADR-Server-Database-yyyy-mm-dd.dmp with ADR 10000 / 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-dd—nn.zip or dmp yyyy-mm-dd is the date of backup launching and nn i s 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



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 no t working before to start the EMS-

ADR 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 h ave 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 reco vered following a EMS-ADR database restoration.

To restore cross-connection labels, launch an audit , select the Crossconnections tab and click on the “Global NMS t o NE crossconnections re-activation” button to launch the reactivation of al l cross-connections in the NE.

From IONOS-NMS P5.4rev3 version, to restore cross-c onnection 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 restore d.

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 no t working before to restore the EMS-ADR database. To stop the EMS-ADR R8.1 applicat ion, 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:



ems(z2-primepower) ~ > SetupEMS.sh EMS XDM Oracle Setup Menu 1 Show Current Configuration 2 Check Oracle DB status 3 Apply Infrastructure Layer to DB 4 Insert EMS XDM schema to DB 5 Remove EMS XDM schema from DB 6 Empty EMS XDM Database data 7 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 EMS-ADR 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/IONOS-

NMS/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 § 14. 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 res toration using the "-n new_schema_name " optional flag.

Example of procedure (using the “scp” command): From the EMS-ADR zone into the ENMConfig directory, enter the command: scp File_source Login_destination@Ip_destination:/R ep_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 t he file.



EMS_ADR_Server_Database.dmp is the name of the dest ination file. It is mandatory to respect this syntax name of the destin ation file.

Note (2) : Also, in case of Backup 1+1 secure see § 14.2.13 - Backup 1+1 of IONOS NMS servers (Option) , you must perform the command of database restoration using the "-n new_schema_name " option al 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.


� 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.


� Run the command : xmlexport <login> / <password> <file name> <export.xml> Or xmlexport <login> / <password> <file name> <exportComplete.xml> (4)



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.


� 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 boards present in equipment - the software associated to boards

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 SLF-v1, SLF-N, SLF-H equipments.


� 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 boards present in equipment - the software associated to boards - the type of link - the static ODU configuration - the ODU parameters



- 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.


� 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



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:

� In the directory chosen for installation (Ionos-NMS or /tools/IONOS-NMS by default), select the 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:


� 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 - general parameters - capability parameters Aligning NE 'Lyon’ of type ADR155C - general parameters Failed to align general parameters! : NE is inaccessible ... - capability parameters Aligning NE 'Brest' of type ADR155C - general parameters - capability parameters Maintenance finished! logging of!

1.14 - SCRIPT TO MANAGE THE FOT155A



A script is supplied to give the capability to put the equipment type FOT155A in / out management.

� In the repertory chosen for the installation (by default Ionos-NMS), select the bin/fotA folder.

� To put the FOT155A out management, run the following script:

On Windows,

snmpsetft.bat <IP_Address> <Eqpt_No> off

On Solaris,

./snmpsetft.sh <IP_Address> <Eqpt_No> off

ex: ./snmpsetft.sh 10.11.12.13 2 off

The FOT155A becomes not accessible.

Note: The modification will be effective after the restart of the Proxy FOT155A in order to manage again the NE.

� To put the FOT155A in management, run the following script:

On Windows,

snmpsetft.bat <IP_Address> <Eqpt_No> on

On Solaris,

./snmpsetft.sh <IP_Address> <Eqpt_No> on

ex: ./snmpsetft.sh 10.11.12.13 2 on

The FOT155A becomes accessible.

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

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 § 10 :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 § 10 : 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 differen t

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 displa yed.

To access a sub-network or a network element, doubl e-click on the corresponding icons in the Topology View .

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.

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.

TOPOLOGY MANAGEMENT


Notes: In this window, the “Creation Date", “Last M odification 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-networ k icon.

The icon of the sub-network will take the color co rresponding to maximum

severity of alarm for all NEs and sub-networks whic h it contains.

the point of exclamation indicates that the sub-net work contains at least one disaligned NE or a disaligned sub-network;

the question mark indicates that the sub-network co ntains at least one potentially disaligned NE or a potentially disalign ed sub-network, other NEs and sub-networks being aligned.

2.3.2 - To display/modify the properties of a sub-n etwork

� 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 propertie s / General

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 propertie s / 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.

TOPOLOGY MANAGEMENT


Figure 2.7 : Window – Sub-network properties / Alar ms

Notes : In this window, the “Creation Date", “Last Modification Date“ and “User

Name” fields are automatically updated.

In the Topology View window ( Figure 2.1 ), the name is displayed below the sub-network icon.

It is possible to display the properties of an ala rm: 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 prese rved in the sub-network which has been moved.

You can also use the « Drag and Drop » technique t o move a sub-network to another sub-network.

TOPOLOGY MANAGEMENT


2.3.4 - To delete a sub-network

Caution : This operation is only allowed provided t he 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

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 menus bar, select Creation > NE : the Create a Network Element window is displayed.

Figure 2.9 : Window – Create a network elem ent (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 nam e 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, Sagem-Link T, SLF-A ,FSP2000, FSP3000, Sagem DTX, SHDSL, 3P@C4048, 3P@C4400, 3P@C4450, 3P@C4900, IP equipment, XP3000.

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 Add ress)

� « Poll interval » to enter the polling interval (by default, 10 min.- § 12.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.

Figure 2.11 : Window – Create a network element (2)

� 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 Name » fields are automatically updated.

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 § 12.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 th ose stored in the equipment; otherwise, it will not be accessible by the IONOS-NMS manager: the passwords can be modified in the equipment usin g 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 th ree passwords.

For a Sagem-Link or a Sagem-Link Light, enter "priv ate" for community, "passwd4" for the password SUPERVISOR, "passwd2" fo r password OPERATOR and OBSERVER.

For a Sagem-Link 2 or a SLF-v1 enter "public" for c ommunity, "2345" for the password SUPERVISOR, "1234" for password OPERATOR a nd "0" for password OBSERVER.

For a SLA, enter "private" for community, and "admi n" for the passwords.

For a SLF-N enter "secret" for community, "2345" fo r the password SUPERVISOR, "1234" for password OPERATOR and "0" fo r password OBSERVER.

For a SLF-H enter "secret" for community, "2345" fo r the password SUPERVISOR, "1234" for password OPERATOR and "0" fo r password OBSERVER.

TOPOLOGY MANAGEMENT


For a FSP2000 or a FSP3000, enter "private" for com munity, "private" for the password SUPERVISOR, "private" for password OPERATO R and "public" for password OBSERVER.

For an equipment SHDSL, enter "private" for communi ty, "super" for password SUPERVISOR and OPERATOR, "observ" for pass word OBSERVER. Use on IONOS the users "Superviser" and "observer" or create a user "admin" on equipment SHDSL.

For an equipment DSLAM, enter "secret" for communit y, "secret" for password SUPERVISOR, enter "private" for password O PERATOR, "public" for password OBSERVER.

For an equipment ADR155E enter “public” for communi ty. For an equipment ADR10000HN, enter "private" for community. For both types, enter "secret" for password SUPERVISOR, "private" for password OPE RATOR and "public" for password OBSERVER.

Caution : The Security window is not taken into acc ount for a NE type ADR10000.

If the admin password has been changed from the EMS -ADR, it must be updated from the PREFERENCES MANAGEMENT (§12.2.3 - To change the default properties of the Nes ): In the “Default community passwords” section, set the new Password SUPERVISOR for ADR100 00 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 , AD R63E1, ADR155CPE, ADR155E, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000H N, ADR10000, FMX with board GIES, SLF-N, SLF-H, SLF-A, FSP2000 o r 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, FM X with board GIES, SLF-N or FSP3000 the manager updates the general pa rameters in the equipment : the name of NE (long name), the table o f traps (Traps Manager Dest/IP adress of IONOS-NMS Server), and the variab le 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 th e 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 t he TPI.

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 th e access security to the equipment, it is possible to update with browse r HTTP the table of managers address IP in each NE created of type ADR1 55C, ADR63E1, ADR155CPE, ADR2500C, ADR2500 EXTRA or ADR622: to ad d 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 m isaligned;

The question mark means that the equipment is pote ntially misaligned.

The icon of the sub-network will take the color cor responding to alarm degree of all NEs and sub-networks which it contain s.

the point of exclamation indicates that the sub-net work contains at least one disaligned NE or a disaligned sub-network;

the question mark indicates that the sub-network co ntains at least one potentially disaligned NE or a potentially disalign ed 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.

Figure 2.14 : Window – Create a network ele ment (5)

� 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,

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 creat e: . 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 « inte rface » under « card » after having selected an NE/VNE, . a « shelf », a « card » and an « interface » unde r « card » after having selected a « rack », . a « card » and an « interface » under « card » af ter having selected a « shelf ». . an « interface » under « card » after having sele cted 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, ADR1 55C 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 accessi ble, the IONOS-NMS manager reads the useful information in the equipme nt.

For the IONOS-NMS server to receive the traps of th e 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 o r 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\tpif mx\backup\carteETH.lst file.

See below,

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 em pty 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 t o move a network

element.

2.4.4 - To delete a network element (NE, VNE)

Caution : This operation is only allowed provided t he 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.

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 addres s 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 n etwork 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.

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 / A larms

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.

TOPOLOGY MANAGEMENT


2.4.7 - To modify the M1400 name of a network eleme nt (NE, VNE)

� In the explorer or in the Topology View (Figure 2.1), click left on the network element to be modified.


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.

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.




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 Lin ks, 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 partial ly 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 modifi ed.

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.

TOPOLOGY MANAGEMENT


2.4.8 - To audit a network element (NE)

Caution : This operation is not valid for virtual n etwork 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 i s 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 IONOS-NMS 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 ma nager data and the NE data, the audit line is displayed red: a message at the top l eft 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).

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

TOPOLOGY MANAGEMENT


Figure 2.26 : Window Audit Results / General

Figure 2.27 : Window Audit Results / Inventory / Ca rds

TOPOLOGY MANAGEMENT


Figure 2.28 : Window Audit Results / Inventory / MS Ps

Figure 2.29 : Window Audit Results / Cross-connecti ons

TOPOLOGY MANAGEMENT


Figure 2.30 : Window Audit Results / Bridging point s

Figure 2.31 : Window Audit Results / VCGroups

TOPOLOGY MANAGEMENT


Figure 2.32 : Window Audit Results / Monitoring

Figure 2.33 : Window Audit Results / ETH/VCG ports

TOPOLOGY MANAGEMENT


Figure 2.34 : Window Audit Results / MEPIDs

Figure 2.35 : Window Audit Results / Continuity-che ck probes

TOPOLOGY MANAGEMENT


Figure 2.36 : Window Audit Results / SDH Ports

Figure 2.37 : Window Audit Results / MS-SPRING

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 / De tail

� Click [Close ] to close the current window.

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

"isFmxInventoryLikeVne" is set to “false” in the se rver-advanced file. (see 1.2.3.37 -To configure the FMX backup configuration file )

(2) For a FMX-GIES, the Inventory tab is updated w hen a NE database is successfully done. See Figure 2.39 : Window Audit Results / FMX inventory

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 v irtual 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. This operation is valid for SLF-N, SLF-H, SLF-A, or FMX with ard GIES, tab Gene ral.

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.



TOPOLOGY MANAGEMENT


Figure 2.40 : Window Audit / General Reapplication

� Select the General tab to reapplicate the general parameters.

Notes : If there is an inconsistency between the ma nager data and the NE data, the audit line is displayed red: a message at the top l eft of the window will then indicate that the general parameters are not aligne d.

� 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 Reapplicati on Results

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 Reapplicati on Results/Details

� Click [Close ] and [Finish ] : the General tab is updated after the reapplication.

Notes : The table of the Managers is not updated au tomatically. It must be updated manually by using HTTP browser.

The long name can not be updated in the equipment a ccording to the used configuration (see § 1.2.3.7 -).

For a NE of type “EXT155HA”, the parameters are upd ated in the physical NE on which the menu “Audit” has been launched (Workin g or Protection).

2.4.10 - To align the capacity parameters from a ne twork element (NE to NMS)

Caution : This operation is not valid for virtual n etwork elements (VNE), FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1 , SLA, SLF-N, SLF-H, S LF-A, equipment, DSLAM equipment, SHDSL equipment, Sagem DTX equipment, WD M 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 A lignment

TOPOLOGY MANAGEMENT


� Select the General tab to align the capacity parameters.

Notes : If there is an inconsistency between the ma nager data and the NE data, the audit line is displayed red: a message at the top l eft of the window will then indicate that the capacity parameters are not align ed.

� 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 ne twork element (NE)

Caution : This operation is not valid for virtual n etwork elements (VNE), FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1 , SLA, SLF-N, SLF-H, SL F-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.

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 man ager data and that of the NE in the inventory, the audit line is displayed red: a m essage 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 Phy sical 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.

TOPOLOGY MANAGEMENT


Notes : A card can only be deleted provided its int erfaces are free (no Link, no VCGroup, no trail, no service Ethernet ). A card can always be replaced by a card of an equiv alent family (For ADR2500 : 4STM1_ELEC and 4STM1_OPT, for ADR155C : ADRSTM1_O PT and ADRSTM1-ELEC).

A card can be replaced by a card of a different fam ily 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, ADR250 0C, ADR2500 EXTRA or ADR622, ADR10000HN, EXT155HA equipment, the Equipme nt View function is validated, the HTTP browser is initiated via the HT TP PROXY installed on the IONOS-NMS Server which activates the HTTP server in tegrated 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-v 1, SLA, SLF-N, SLF-H, equipment and FSP2000, FSP3000 equipment, when the Equipment View function is validated, the LCT Application is launc hed (installed beforehand).

For ADR10000, when the Equipment View function is v alidated, the ADR10000 proxy is launched.

For the FOT155C equipment, when the Equipment View function is validated, a customer application is initiated and uses the SN MP 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.

TOPOLOGY MANAGEMENT


Figure 2.47 : Window SAGEM-LINK Equipment View

Figure 2.48 : Window SAGEM-LINK LIGHT Equipment Vie w

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.

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 upd ated if the variable

"isFmxInventoryLikeVne" is set to “false” in the se rver-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 / F MX 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.

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 refres h 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 eleme nt

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

TOPOLOGY MANAGEMENT


� Click [Finish ] to close the window, when it is finished.

Notes : (1) The TFTP server must be launched as a p reliminary on the machine used

like IONOS-NMS server. (2)The backup is done in the repertory, specified in the file

"Equipementbackup.xml" contained in the folder Conf ig of the repertory chosen for the installation (by default c:\Program Files\Ionos-NMS\Backup\Eqpt under Windows and /data/IONOS-NMS/B ackup/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 ADR63 E1 two files are generated (db and net). For the EXT155HA, the command must be launched on e ach 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 Preference s of NE ("SNMP requests configuration for all NEs " in menu Tools/Preferenc es/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 like IONOS-NMS server.

(2) The backup is done in the repertory, specified in the file "Equipementbackup.xml" contained in the folder Conf ig of the repertory chosen for the installation (by default c:\Program Files\Ionos-NMS\Backup\Eqpt under Windows and /data/IONOS-NMS/B ackup/Eqpt under Solaris).

The files are stored under the repertory yyyy/yyy y-mm/dd. There are two files and the name of the files is f orm:

NEDatabase-M1400 name- IP address-YYYY-MM-DD-nnnn.d b and .install ‘nnnn’ is the index of the file.

(3) In case of Backup 1+1 secure see § 14.2.13 - Backup 1+1 of IONOS NMS servers (Option) , the NE database is also transferred to the remot e Ionos-NMS server.

FMX-GIES: (1) For a FMX-GIES, in case of backup fai led, 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 faile d result

TOPOLOGY MANAGEMENT


Also, a critical alarm is displayed in the Fault Vi ew 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 di splayed in the Fault View with a “Configuration Changed” event type. It appea rs at the next FMX database backup. See Figure 2.55 .

Figure 2.55 : Window – Warning Configuration Change d alarm in Fault View

2.4.15 - To restore the database of a network eleme nt

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.

TOPOLOGY MANAGEMENT


Figure 2.57 : Window Network Element Restoration Re sults

� 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 M14 00 name is replaced by a "(".

(2) The TFTP server must be launched as a prelimina ry on the machine used like IONOS-NMS server. (3) For the EXT155HA, the command must be launched on each physical NE (Working and Protection).

(4) If the restoration is not finished correctly w ith a status "Unknown error", modify the value of SNMP time-out in the Preference s of NE ("SNMP requests configuration for all NEs " in menu Tools/Preferenc es/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 157-A 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.

Example of procedure (using the “scp” command): From the IONOS-NMS server into the backup directory , enter the command: scp File_source Login_destination@Ip_destination:/R ep_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 pass word later. 10.0.01 is the IP address of the EMS-ADR

TOPOLOGY MANAGEMENT


/sdh_home/ems/DownLoad/DB05.8120/ is the path to co py the file 50.0.0.1.install is the name of the destination fil e using the IP address of the NE instead of its name You have to apply the same procedure to copy the .d b file.

Caution with EMS-ADR R7.2 : The label of cross-conn ection 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 t o NE crossconnections re-activation” button to launch the reactivation of all cross-connections in the NE.

To restore cross-connection labels from the EMS-AD R R7.2, select a NE and open the Shelf View, and on the menu bar select Sys tem �� Import XC. The XC labels of all NE will be restored.

2.4.17 - To update the software on a network elemen t

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.

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.

TOPOLOGY MANAGEMENT


Figure 2.59 : Window Software Management w indow / Inventory

Notes : For an EXT155HA, the inventory is displayed for the two Physical NEs (Working and Protection).

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



� 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


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 vers ion to be downloaded is already present in the « current » or « reserve » list (But ton [Reserve download]). The TFTP server must be launched as a preliminary o n the machine used like IONOS-NMS server. For an EXT155HA, the download is done for the two p hysical NEs (Working and Protection). The result is given for each physi cal 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



� 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 plac e if the « current » version is identical to the « reserve » version. For an EXT155HA, the switch is done for the two phy sical NEs (Working and Protection). The result is given for each physical NE.

� Click [End session ] when you have finished.

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 e lement

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)

TOPOLOGY MANAGEMENT


2.4.19 - To visualize the counters of performance f or SLF-v1, Sagem-Link, SLF-N 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 c ollect

� 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.

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 périod can be modified with bu tton [Presets]. Button [Tree View] allows to display the list of a ll SLF-v1 created in IONOS-

NMS and to activate the visualization of different graphs for each equipment. The collect of performance data is automatically a ctivated for each Sagem-

Link, SLF-v1, SLF-N and SLF-H created in IONOS-NMS. The collected data are displayed 24h after the col lect.

� 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

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.


� 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

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 N E-Type defined in types.xml (case sensitive)

Ionos-NMS\netpilot\webapps\root\resources\topo\defa ult\

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 NE-Type 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 won’t 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.

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/Se eds

� Click on tab [Communities ] to define extra SNMP community password.

TOPOLOGY MANAGEMENT


Figure 2.65 : Window – Discover Network Elements/Co mmunities

� Click [Add ] or [Delete ] to update the list.

Notes: The "SNMP community" is used to access equip ment 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/Di scovering

� 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.

TOPOLOGY MANAGEMENT


Figure 2.67 : Window – Discover Network Elements/St atus

Notes: The Status window is displayed when the scan of the range of IP address is completed.

Caution: The list of discovered Network Elements m ay 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 cre ated.

- « M1400 name », the M1400 name is build with the four numbers ( 3 characters each) of the IP address of the discovere d NE. The suffix is not filled.

Example: a NE discovered with the IP address 192.16 8.17.2 will be created with the M1400 name: « 192168017002 » (192 168 017 002) Caution: If the M1400 name built from the IP addres s of the discovered Network Element is already used, the NE is not crea ted

- « Type », the type of the discovered equipment (only ADR1 55C, ADR155CPE, ADR155E, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000H N, ADR63E1, FSP2000, FSP3000, SLF-v1, SLF-N, SLF-H, SLA, SLT,FO T C,XP3000) - « IP address » Caution: If a NE with the same IP address (primary or secondary address) is already created, the discover ed NE is not created (no duplication)

TOPOLOGY MANAGEMENT


The traps table of the equipment is automatically u pdated 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 s erver. The interruption (stop) can be performed from any IONOS-NMS client.

An executable file is supplied to launch the discov ery of Network Element. To initialise the range of IP address perform a first NE discovery using IONOS-NMS client.

- In the directory chosen for installation (Ionos-N MS or /tools/IONOS-NMS by default), select the bin folder.

- Run the command : autodiscovery.bat (PC) or ./autodiscovery.sh (solaris), then give the login ad password of the u ser 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 equ ipment since the contextual menu of a

sub-network or of an equipment, then select "Search NE"

TOPOLOGY MANAGEMENT


2.5 - ADMINISTRATION OF NETWORK ELEMENTS (NE, VNE)

2.5.1 - To create a network element EXT155HA

This procedure is used to add a new network element of type EXT155HA and to position it in the sub-network hierarchy (explorer).


� In the menus bar, select Creation > NE : the Create a Network Element window is displayed.

Figure 2.70 : Window Create a network element/EXT1 55HA (1)

� Use the fields as follows:

� « Name » to enter the mandatory name (60 characters max.)

� « 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.

� « Type » to enter the equipment type : EXT155HA.

� « IP address (Working)» to enter the IP address of Working equipment: if the network element has not been installed, it will be viewed as inaccessible by IONOS-NMS.

� « IP address (Protection)» to enter the IP address of Protection equipment: if the network element has not been installed, it will be viewed as inaccessible by IONOS-NMS.

� « Poll interval » to enter the polling interval (by default, 10 min.) of two NEs Working and Protection: in seconds, minutes or hours. This duration is used to adjust the time interval between two polling operations to detect any inaccessibility. The value 0 implies that the two NEs are not polled.

� Click [Next ] when you have filled in the fields: the data customization window is displayed.

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, 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 Name » fields are automatically updated.


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.(see §2.4.13 -)

� Click [Create NE ] to validate the NE creation.

Notes : The "SNMP community" is used to access the two physical equipments (Working and Protection) by SNMP.

The 3 passwords are used to access the two physical equipments by HTTP browser.

The community and passwords must correspond to th ose stored in the equipment; otherwise, it will not be accessible by the IONOS-NMS manager: the passwords can be modified in the equipment usin g the SNMP View menu (see § .

In the Topology View , and in the explorer, the icon of logical NE is di splayed for the EXT155HA. It takes the color corresponding to the synthesis of the alarms of two physical NEs (Working and Protection) . EXT155HA name is written below.

! The exclamation point means that the Working e quipment or/and the Protection equipment is misaligned;

? The question mark means that the Working equipm ent or/and the Protection equipment is potentially misaligned.

When the network element EXT155HA is created and is accessible, the IONOS-NMS manager reads the cards inventory in the Working equipment and saves it in the database. The time and date of two physical NEs is updated automatically (with the date and time of IO NOS server). For each STM1 card (ADRS1.1, ADRIC1.1, ADRIC1.2, ADRERE, ADR MM1, ADRL1.1, a virtual card "-MSP" will be added in the inventory. This virtual card will be used to create the MSP protection between the EXT15 5HA and the ADR2500. The alarms are read in the two physical NEs (Workin g and Protection).

Caution: The Proxy HTTP cannot be used with EXT155H A.

2.5.2 - Display and modify the properties of a netw ork element EXT155HA

� In the explorer or in the Topology View (Figure 2.1), click left on the network element to be displayed and modified.


TOPOLOGY MANAGEMENT


Figure 2.73 : Window Network Element properties/Gen eral/EXT155HA

� a/ Select the General tab if you want to modify:

� the name (40 characters max.).

� 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 equipment type cannot be modified.

� the IP address for Working Equipment: if the network element has not been installed beforehand, it will be inaccessible.

� the IP address for Protection Equipment: if the network element has not been installed beforehand, it will be inaccessible.

� the polling interval (by default, 10 min.) : in seconds, minutes or hours. This duration is used to adjust the time interval between two polling operations to detect NE inaccessibility (Working and Protection equipment) : the value 0 implies that the two NEs will not be polled.

b/ Select the Additional Information tab to customize certain data (see § 2.5.1 -Creation of a network element).

c/ Select the Alarms tab to display all the alarms of NE (working and protection).

d/ Select the Security tab to modify the SNMP community in the “SNMP community” field and equipment passwords for the three types of users (supervisor, operator and observer) in the “Password“ fields (see § 2.5.1 - Creation of a network element).

e/ Select the Inventory tab to read/modify the inventory.

TOPOLOGY MANAGEMENT


Figure 2.74 : Window Network Element properties/Inv entory/EXT155HA

Click [Add Interface ] to add an interface of type "OTHER" on any card.

f/ Select the Physical NEs tab to :

� read the alarm state of two physical NEs: the color gives the alarm state (green = no alarm, red = major alarm, yellow = minor alarm, blue = inaccessible).

� To know the NE used for the traffic (Working ou Protection),

� Launch éventually a manual switch command between the two physical NEs of EXT155HA. In this case, click button [Send ].

� Launch an action on one of physical NEs of EXT155HA.

TOPOLOGY MANAGEMENT


Figure 2.75 : Window Network Element properties/Phy sical NEs/EXT155HA

The actions on each NE (Working and Protection) are:

� Force Polling

� Audit

� Equipment View to launch the HTTP browser

� SNMP View

� NE database backup

� NE database restore

Note : These actions are launched on one of physica l NEs.


2.5.3 - To display the properties of physical NEs o n an EXT155HA

� In the explorer or in the Topology View (Figure 2.1), click left on the network element EXT155HA to be displayed.

� In the pop-up menu, select Show Physical NEs : the Show Physical NEs window is displayed (or double-click on the EXT155HA icon).

TOPOLOGY MANAGEMENT


Figure 2.76 : Window Show Physical NEs/EXT155HA

This window enables you to:

� read the alarm state of two physical NEs: the color gives the alarm state (green = no alarm, red = major alarm, yellow = minor alarm, blue = inaccessible).

� To know the NE used for the traffic (Working ou Protection),

� Launch éventually a manual switch command between the two physical NEs of EXT155HA. In this case, click button [Send].

� Launch an action on one of physical NEs of EXT155HA. The actions on each NE (Working and Protection) are:

- Force Polling

- Audit

- Equipment View to launch the HTTP browser

- SNMP View

- NE database backup

- NE database restore

Note : These actions are launched on one of physica l NEs.

2.5.4 - To reactivate the MSPs protections in a net work element (NMS to NE)

Caution : This operation is not valid for virtual n etwork elements (VNE), FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1 , SLA, SLF-N, SLF-H, eq uipment, DSLAM equipment, SHDSL equipment, Sagem DTX equipment, IP equipment, FSP2000 and FSP3000.

This task is used to reactivate the MSP protections in the NE.



TOPOLOGY MANAGEMENT


Figure 2.77 : Window Audit / Inventory MSPs Re-act ivation

� Select the Inventory tab.

� Select the MSPs sub-tab.

Note : If there is an inconsistency between the ma nager data and that of the NE in the inventory/MSPs, the audit line is displayed red : a message at the top left of the window in the inventory/MSPs tab will indica te that the MSPs are not aligned.

� Click [Global NMS to NE MSPs re-activation ] to launch the reactivation of all MSPs protections in the NE : the results window is displayed.

Figure 2.78 : Window Global NMS to NE MSPs Re-activ ation Results

� Double-click on the line of results to obtain the details of activation of MSP protection and associated monitoring.

TOPOLOGY MANAGEMENT


Figure 2.79 : Window Global NMS to NE MSPs Re-activ ation Results/ MSP Details

� Click on the Monitoring Results tab to obtain the details of associated monitoring.

Figure 2.80 : Window Global NMS to NE MSPs Re-activ ation Results/ Monitoring Details

� Click [Close ] and [Finish ] : the MSPs tab is updated after the reactivation.

� Click [Close ] to close the Audit

Notes : A MSP protection cannot be activated in the NE, if the port of protection is used in a cross-connection or if the port of protec tion is used like DCC port.

A MSP protection cannot be activated in the NE, if there is already a different MSP protection on the port of protection.

The control of ports used by MSP protection in the equipment depends on the value of monitoring "yes" or "no".

2.5.5 - To reactivate the cross-connections in a ne twork element (NMS to NE)

Caution : This operation is not valid for virtual n etwork elements (VNE), FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H, equ ipment, DSLAM equipment, SHDSL equipment, Sagem DTX equipment, IP equipment, FSP2000 and FSP3000 .

This task is used to reactivate the cross-connections in the NE, for the bearers and the trails activated in IONOS-NMS.



TOPOLOGY MANAGEMENT


Figure 2.81 : Window Audit / Crossconnections Re-a ctivation

� Select the Crossconnections tab : the list of bearers and trails is displayed in the database of IONOS-NMS, the list of activated cross-connections is displayed in the database of the NE.

Note : If there is an inconsistency between the ma nager data and that of the NE in

the cross-connections, the audit line is displayed red: a message at the top left of the window in the cross-connections tab wil l indicate that the cross-connections are not aligned.

For a NE of type “EXT155HA”, the reactivation must be launched on the Physical NE “Working”. Activate before the menu “Sh ow Physical NEs” to launch the audit. (see § 2.5.3 -)

� Click [Global NMS to NE crossconnections re-activation ] to launch the reactivation of all cross-connections in the NE (1) : the result window is displayed.

Figure 2.82 : Window Global NMS to NE Crossconnecti ons Re-activation Results

� Double-click on the line of result to obtain the details of the activation of cross-connections and associated monitoring (2).

TOPOLOGY MANAGEMENT


Figure 2.83 : Window Global NMS to NE Crossconnecti ons Re-activation Results/Details Cnx

� Click on the Monitoring Results tab to obtain the details of results of associated controlled points.

Figure 2.84 : Window Global NMS to NE Crossconnecti ons Re-activation Results/Details Monitor

� Click [Close ] and [Finish ] : the Crossconnections tab is updated after the reactivation.


Notes : (1) All the activated cross-connections of the database of IONOS-NMS are reactivated. The cross-connections "reserved" are n ot activated in the NE.

(2) A cross-connection cannot be activated in the N E, if the port or the CTP is already used in a cross-connection, or if the card supporting the port or the CTP is different.

(3) The window Details/Cross-connections display th e list of all cross-connections showing if those were created or not (i n this case the cause of the error). (4) The window Details/Monitoring display the list of the controlled points indicating if they were updated or not (in this cas e, the cause of the error).

2.5.6 - To reactivate the bridging points in a netw ork element (NMS to NE)

Caution : This operation is not valid for virtual n etwork elements (VNE), FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H, equ ipment, DSLAM equipment, SHDSL equipment, Sagem DTX equipment, IP equipment, FSP2000 and FSP3000.

TOPOLOGY MANAGEMENT


This task is used to reactivate the bridging points in the NE, for the Ethernet services activated in IONOS-NMS.



Figure 2.85 : Window Audit / Bridging points Re-ac tivation

� Select the Bridging points tab : the list of bridging points for activated ethernet services of this NE are displayed in the database of IONOS-NMS, the list of bridging points (switch) create in the NE are displayed in the database of the NE.


the bridging points, the audit line is displayed re d: a message at the top left of the window in the bridging points tab indicate that the bridging points are not aligned.

� Click [Global NMS to NE bridging points re-activation ] to launch the reactivation of all bridging points n the NE (1) : the result window is displayed.

Figure 2.86 : Window Global NMS to NE Bridging poin ts Re-activation Results

TOPOLOGY MANAGEMENT


� Double-click on the line of result to obtain the details of the activation of bridging points (2).

Figure 2.87 : Window Global NMS to NE Bridging poin ts Re-activation Results/Details

� Click [Close ] and [Finish ] : the Bridging points tab is updated after the reactivation.


Notes : (1) All the bridging points of the IONOS-NM S database are reactivated.

(2) A bridging point cannot be activated in the NE, if the port or the CTP is already used in another bridging point, or if the c ard supporting the port or the CTP is different.

(3) The window Details/Bridging points display the list of all bridging points showing if those were created or not (in this case the cause of the error).

2.5.7 - To reactivate the parameters of ETH/VCG por ts in a network element (NMS to NE)

Caution : This operation is not valid for virtual n etwork elements (VNE), FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H, equ ipment, DSLAM equipment, SHDSL equipment, Sagem DTX equipment, IP equipment, FSP2000, FSP3000.

This task is used to reactivate the parameters of ETH/VCG ports in the NE, for the Ethernet Links and VCGRoups activated in IONOS-NMS.



TOPOLOGY MANAGEMENT


Figure 2.88 : Window Audit / ETH/VCG ports Re-acti vation

� Select the ETH/VCG ports tab : the list of ETH/VCG ports parameters used by activated ethernet links or VCGroups of this NE is displayed in the database of IONOS-NMS (type UNI/NNI, with mutualization or not), the list of parameters is displayed in the database of the NE for the same ports.

Note : If there is an inconsistency between the ma nager data and that of the NE for

the ETH/VCG ports parameters, the audit line is dis played red: a message at the top left of the window in the ETH/VCG ports tab indicate that the parameters of ETH/VCG ports are not aligned.

� Click [Global NMS to NE ETH/VCG ports re-activation ] to launch the reactivation of ports not aligned in the NE : the result window is displayed.

Figure 2.89 : Window Global NMS to NE ETH/VCG ports Re-activation Results

� Double-click on the line of result to obtain the details of the activation of parameters of ETH/VCG ports (1).

TOPOLOGY MANAGEMENT


Figure 2.90 : Window Global NMS to NE ETH/VCG ports Re-activation Results/Details

� Click [Close ] and [Finish ] : the ETH/VCG ports tab is updated after the reactivation.


Notes : (1) All the ETH/VCG ports not aligned are r eactivated.

2.5.8 - To reactivate the MEPIDs in a network eleme nt (NMS to NE)

Caution : This operation is not valid for virtual n etwork elements (VNE), FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1 , SLA, SLF-N, SLF-H, eq uipment, DSLAM equipment, SHDSL equipment, Sagem DTX equipment, IP equipment, FSP2000, FSP3000.

This task is used to reactivate the MEPIDS (identification of GFP cards) in the NE, used by the continuity-check probes.



TOPOLOGY MANAGEMENT


Figure 2.91 : Window Audit / MEPIDs ports Re-activ ation

� Select the MEPIDs tab : the list of MEPIDs (identification of GFP cards) used by activated continuity-check probes is displayed in the database of IONOS-NMS and in the database of the NE.


the MEPIDs parameters, the audit line is displayed red: a message at the top left of the window in the MEPIDs tab indicate that the values are not aligned.

� Click [Global NMS to NE MEPIDs re-activation] to launch the reactivation of MEPIDs not aligned in the NE : the result window is displayed.

Figure 2.92 : Window Global NMS to NE MEPIDs Re-act ivation Results

� Double-click on the line of result to obtain the details of the activation of parameters of MEPIDs (1).

TOPOLOGY MANAGEMENT


Figure 2.93 : Window Global NMS to NE MEPIDs Re-act ivation Results/Details

� Click [Close ] and [Finish ] : the MEPIDs tab is updated after the reactivation.


Notes : (1) All the MEPIDs not aligned are reactiva ted.

2.5.9 - To reactivate the continuity-check probes i n a network element (NMS to NE)

Caution : This operation is not valid for vi rtual network elements (VNE), FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H, equ ipment, DSLAM equipment, SHDSL equipment, Sagem DTX equipment, IP equipment, FSP2000, FSP3000.

This task is used to reactivate the continuity-check probes in the NE, used by the activated ethernet services.



TOPOLOGY MANAGEMENT


Figure 2.94 : Window Audit / Continuity-check prob es Re-activation

� Select the Continuity-check probes tab : the list of continuity-check probes (source and sink) used by activated ethernet services is displayed in the database of IONOS-NMS and in the database of the NE.


the continuity-check probes, the audit line is disp layed red: a message at the top left of the window in the Continuity-check prob es tab indicate that the values are not aligned.

� Click [Global NMS to NE Continuity-check probes re-activat ion] to launch the reactivation of Contniuity-check probes not aligned in the NE : the result window is displayed.

Figure 2.95 : Window Global NMS to NE Continuity-ch eck probes Re-activation Results

� Double-click on the line of result to obtain the details of the activation of parameters of MEPIDs (1).

TOPOLOGY MANAGEMENT


Figure 2.96 : Window Global NMS to NE Continuity-ch eck probes Re-activation Results/Details

� Click [Close ] and [Finish ] : the Continuity-check probes t ab is updated after the reactivation.


Notes : (1) All the Continuity-check probes not ali gned are reactivated.

2.5.10 - To reapplicate the monitoring in a network element (NMS to NE)

Caution : This operation is not valid for virtual n etwork elements (VNE),FOT155A, FOT155C and multiplexers ADR155C P2 and FMX, Sagem- Link, Sagem-Link Light, Sagem-Link 2, SLF-v1, SLA, SLF-N, SLF-H, equ ipment, DSLAM equipment, SHDSL equipment, Sagem DTX equipment, IP equipment .

This task is used to reapplicate the monitoring of all the controlled points in the NE, relating to the STM-n links created, to the MSP created and activated, to the activated VCGRoups and Ethernet links, to the activated ethernet services, to the activated WDM links, to the activated cross-connections, to the activated WDM trails and to the activated ring (ADR2500 only).



TOPOLOGY MANAGEMENT


Figure 2.97 : Window Audit / Monitoring Reapplicat ion

� Select the Monitoring tab : the list of all the controlled points, relating to the STM-n links created, to the activated ethernet links, to the activated WDM links, to the activated VCGroups, to the activated cross-connections, to the activated ethernet services to the activated WDM Trails, and to the activated ring is displayed.


the control of points, the audit line is displayed red: a message at the top left of the window in the monitoring tab will indicate t hat the monitoring is not aligned.

For a NE of type “EXT155HA”, the reapplication mus t be launched on the Physical NE “Working”. Activate before the menu “Sh ow Physical NEs” to launch the audit.

� Click [Global NMS to NE monitoring reapplication] to launch the reapplication of monitoring in the NE (1) : the result window is displayed.

Figure 2.98 : Window Global NMS to NE Monitoring Re application Results

� Double-click on the line of result to obtain the details of the monitoring reapplication.

TOPOLOGY MANAGEMENT


Figure 2.99 : Window Global NMS to NE Monitoring Re application Results/Details

� Click [Close ] and [Finish ] : the Monitoring tab is updated after the reapplication.


Notes : (1) The monitoring is reapplicated for all the disaligned points.

(2) The PPI-LOS/PPI-AIS level (normal/inverted) mo nitoring is only for equipments which support the capability “Standby Mo de”

To reactivate a MS-Spring protection in a network e lement (NMS to NE)

Caution : This operation is valid only for the ADR2 500C or ADR2500 EXTRA.

This task is used to reactivate a MS-SPRing protection in a NE.



Figure 2.100 : Window Audit /MSSPRings Re-activati on

TOPOLOGY MANAGEMENT


� Select the MS-SPRing tab : The MS-SPRing protection is not aligned between the database of IONOS-NMS and the database of the NE.

� Click [Show Details ]: the displayed window presents the tabs General , Topology , NUT and Misconnection .


the MS-Spring protection, the audit line is display ed red: a message at the top left of the window in each tab will indicate that t he ring is not aligned.

� Click [NMS to NE MSSPRings re-activation ] to launch the reactivation of ring in the NE : A window of confirmation is displayed, indicating that the ring will be deactivated, then reactivated, what could involve a cut of traffic if the protection is used.

� Confirm the reactivation : the result window is displayed.

Figure 2.101 : Window NMS to NE MSSPRings Re-activa tion Results

� Click [Close ] and [Finish ] : the MS-SPRing tabs are updated after the reactivation of ring and the Monitoring tab is also updated.


Note : On MS-SPRing reactivation, the ring is deact ivated, then reactivated in the NE and the monitoring associated to the ring is reappl icated in the NE (according the value of ring monitoring).

TOPOLOGY MANAGEMENT


2.6 - SDH LINKS ADMINISTRATION

2.6.1 - To create an STM-n link

This procedure is used to set up a link between two network elements : an « inter-nodal » link is an SDH physical connection set up using the SDH, STM-1, STM-4, STM-16 or STM-64 interfaces of the two NEs (their interfaces must have the same transmission rate).

� In the Topology View tools bar, click left on the New icon: the New window is displayed.

Figure 2.102 : Window New

� In this window, select the Traffic carrier icon then click [OK] : the Create Traffic Carrier window is displayed.

Figure 2.103 : Window Create STM-n Link (1)

� Sélect the type of Traffic Carrier : SDH for Domain, Links for Family, and STMn Link for Type, then Click [Next ] : the next window is displayed with all the interfaces (1).

TOPOLOGY MANAGEMENT



� In the Source area, select a source STM-n interface.

� In the Destination area, select a destination STM-n interface (2).

� In the name part of the window, enter a serial number for the new link. By clicking Default Value ], you will obtain a default number.

� Cllick [Next ] to display the following screen.

Notes: (1) Incompatible interfaces, already reserve d or not valid (grayed in) are not accessible.

(2) The source and destination interfaces must be identical: the STM1 links can be created with the ADR155C, ADR63E1, ADR155CPE , ADR155E, EXT155HA, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000 HN, ADR10000 and VNE; The STM-4 links can be created with the AD R155C, ADR155E, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000HN,ADR1000 0 and VNE; the STM-16 links with the ADR2500C, ADR2500 EXTRA, ADR1 0000HN, ADR10000 and VNE, the STM-64 with the ADR10000, ADR10000HN a nd VNE.

TOPOLOGY MANAGEMENT



� In the Additional Information part, 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.).

� In the Monitoring part (4), if necessary modify the value of monitoring which involves the update in the equipment : Extremities or None .

� In the Gravity Profiles part (4), if necessary modify the mode by ticking or not the case "manual" and if the case "manual " is ticked, modify the value of Gravity Profile with the proposed list.

� In the RS Path trace configuration part (4), if necessary activate the configuration of the RS path trace by ticking or not the cases "automatic " and "Disable TIM " (3).

Notes: (3) the cases "Automatic" and "Disable TIM" are greyed if the feature RS Path

Trace is not supported by one of the equipment or t he cards.

The consequent actions (“Disable TIM” unselected) w ill be activated only if RS Path traces expected and received values match t ogether.

� In the Performance part (4), if necessary modify the mode and activate or not the collection of performance by ticking or not la case "Collect defined counters ".

� Click [Create Link ] to validate the new link: the following screen is displayed.

Note: (4) the value displayed by default for monit oring, the Gravity Profiles and the

parameters of performance are those defined in the preferences of STM-n Link ( menu Tools/Preferences/STM-n Link see § 12.2 .6 - ).

TOPOLOGY MANAGEMENT



� Click [Finish ] if you have finished or click [AddMSP ] to add an MSP protection to the link which you have just created. In this case, the following Create MSP screen is displayed with all the available protections (5).


TOPOLOGY MANAGEMENT


� In the Source part of the window, select a source protection.

� In the Destination part of the window, select a destination protection.

� In the MSP Parameters part, tick or enter the protection parameters (6) (7):

a/ Revertive : when the box is ticked, the revertive function enables return to the normal trail when ready, taking in account the value of WTR.

b/ SFSD Priority : protection priority level.

c/ WTR (from 30 to 900 seconds) : time while the status of normal trail is correct before the return on this normal trail..

d/ Hold Off Time (in 1/10 s.) : time after appearance of an alarm.

e/ Mode : bidirectional or unidirectional.

� Click [OK] to validate the protection: the following screen is displayed.

Notes: (5) Incompatible protections, already reserv ed or not valid (grayed in) are not accessible.

(6) The values displayed by default for MSP parame ters are those defined in the Preferences of STM-n Link (menu Tools/Preferenc es/STM-n Link ).

(7) The configuration of the RS Path traces for th e protecting link is identical to that of the protected link if the function is su pported by the card of the ports of the MSP.

The configuration of the RS Path Trace for the por ts of the protection is carried out during the activation of the protection .


� Click [Finish ] : the following Create STM-n link window (6) is displayed, with the result of creation.

TOPOLOGY MANAGEMENT



� By double-clicking on the « monitoring » results line, the result details are displayed in the Details window.


� Click [Close ] then [Finish ] to exit.

� The following window is displayed. It gives the possibility to create VC4 bearer trail :


� Click [Yes] to launch the creation of bearer within the new STM-n Link. See the procedure to define a VC4 bearer trail within a STM-n link at § 4.2.1 - "To create a VC4 bearer trail"

TOPOLOGY MANAGEMENT


Notes : If you create a link with two network eleme nts belonging to two different sub-networks, the graphic representation with the "shor tcut" will be used: see window below.

When creating a link, the extremity port monitori ng function for the link is updated in the equipment as well as the protection port monitoring function (case of MSP protection in accordance with "extremi ties" or "no" activation for the monitoring).

When the STM-n Link is created, a graphical link w ith a number (x AU) (number of STM-1 links) is created between the two NEs in the Topology View . The link is animated with the color corresponding t o its alarm state. If you place the mouse pointer on the graphical link, the name of link is displayed.

Example of "Shortcut" graphic representation

The icons for Paris25/94, Nice26/1 and Agen25/1 are represented in sub-network « sud-ouest » with shortcuts since it belongs to another sub-network.

Figure 2.112 : Topology View with a "short-cut" ico n

2.6.2 - To delete an STM-n link

Caution : This operation is only possible provided no trails use this link.

� Display the Topology View, then select the STM-n link to be deleted.

TOPOLOGY MANAGEMENT


Figure 2.113 : Window Topology View / Sélection of STM-n Link

� Click right to bring up the pop-up menu, then click [Show Links ] : the Show Links window is displayed with the list of links.

Figure 2.114 : Window Show Links

TOPOLOGY MANAGEMENT


� In the list, select [STMn] tab, then the link to be deleted then click right to bring up the pop-up menu.

� Click [Delete ] : a confirmation message is displayed (1).


� Click [Close ] when you have finished.

Note: (1) The unconfiguration of the RS Path Trace for the ports is carried out during the deletion of the link. The consequent act ions in the equipment are disabled (“Disable TIM” checked).

2.6.3 - To rename an STM-n link

� Display the Topology View (Figure 2.1), then click right on the STM-n to be renamed.

� Click right to bring up the pop-up menu, then click on [Show Links ] : the Show Links window is displayed .

� In the list, select [STMn] tab, then the link to be renamed then click right to bring up the pop-up menu.

� Click [Rename ] to rename the STM-n link: the following screen is displayed.

Figure 2.115 : Window Rename STM-n Link

� Modify the serial number.

� Click [Apply ] to validate the operation.

Note : The name of each link is unique: only the se rial number can be renamed.

2.6.4 - To display / modify the properties of an ST M-n link

This procedure is used to display/modify the attributes of a link (ports used and customized data).

� Display the Topology View (Figure 2.1), then select the STM-n link to be modified.

� Click right to bring up the pop-up menu, then click [Show Links ] : the Show Links window is displayed .

� In [STMn] tab, select the link to be modified then click right to bring up the pop-up menu.

� Click [Properties] to modify the STM-n link: the Properties STM-n Link screen is displayed with following tabs : Linear display, Information, Additional information, Alarms, Occupation, Status History, Performances.

� Click [Activation ] (Linear Display Tab) in "Animation" area to display the state of activation of STM-n Link.

TOPOLOGY MANAGEMENT


Figure 2.116 : Window STM-n Link Details / Linear D isplay (1)

Color of the link:

- for the path "Working": always green

- for the path of MSP protection : green if MSP protection is activated, orange if MSP protection is reserved or partially activated.

Color of the NE name:

- In green if MSP protection is activated on the NE

- In orange if MSP protection is not activated on the NE.

� Click [Alarms ] (Linear display tab) in "Animation" area to display the state of alarm of STM-n Link according to the direction (unidirectional or bidirectional).

TOPOLOGY MANAGEMENT


Figure 2.117 : Window STM-n Link Details / Linear D isplay (2)

Color of the link:

- For the path Working and a given direction

� in green if not of alarm or alarm of maximum severity = warning

� in gray if it "output" NE is a VNE

� in blue if alarm of inaccessibility

� in red if alarm of maximum severity = major

� in yellow if alarm of maximum severity = minor

- For the path "Working" and the bidirectional mode:

� the synthesis of the colors of the two directions according to the command gray, green, yellow, red and blue.

- For the path "Protection" (MSP protection ) and a given direction


� In gray if it "output" NE is a VNE

� In blue if alarm of inaccessibility

� In red if alarm of maximum severity = major

� In yellow if alarm of maximum severity = minor

- For the path "Protection" (protection #MSP) and the bidirectional mode:


TOPOLOGY MANAGEMENT


Color of NE :

- The color of "the output" NE for a given direction :


� without color if it "output" NE is a VNE




- The color of "the input" NE for a given direction is without color

- For each NE and bidirectional mode:

� the synthesis of the colors of the two directions according to the command without color, green, yellow, red and blue.

Note: all alarms acknowledged or not are taken int o account..

The direction of traffic is not taken into account. The alarms on the port of MSP protection are taken into account only if the MSP is activated on both NEs.

� Click on [Traffic Indic .] (Linear display tab) to display if the traffic passes by the path "Working" or the path of protection according to the direction.

� Select one of the both NEs or the Link and activate the Pop-up menu (click right). This menu allows to launch the actions on the NE or the Link.

Figure 2.118 : Window STM-n Link Details / Informat ion (3)

TOPOLOGY MANAGEMENT


Figure 2.119 : Window STM-n Link Details / Informat ion (4)

� If necessary, modify the serial number of the name (Information tab) or click [AddMSP ] if you want to add an MSP protection.

� If necessary and supported by the equipment and the cards, modify the configuration of the RS Path Trace Configuration.

TOPOLOGY MANAGEMENT


Figure 2.120 : Window STM-n Link Details / Addition al information (5)

� If necessary, modify the customized data: customer name, location and info (Additional Information tab).

TOPOLOGY MANAGEMENT


Figure 2.121 : Window STM-n Link Details / Alarms ( 6)

Note: If the traffic is not "OK", the list of alar ms of STM-n Link is displayed.

The value of the "Failure #gravity" displayed corre sponds to the value of the "Gravity Profiles" according to the status of STM-n Link. This value is given in menu "Tools/Preferences/Failure Gravity Configurati on" (§ 12.2.9 - ).

� If necessary, modify the value of the monitoring which involves the update in the equipment: Yes or No (Alarms tab).

Note: It is not possible to modify the monitoring of STM-n Link with "No" if it is used

by a monitored ring.

� If necessary, modify the profile of gravity of STM-n Link: tick or nor the case "Manual" and give a value of the "Gravity Profiles" in the proposed list.

� Click [Apply ] when you have finished to validate the modifications.

TOPOLOGY MANAGEMENT


Figure 2.122 : Window STM-n Link Details /Status hi story (7)

� Visualize the status history of the STMn Link since its creation (Status History Tab) clicking on Status History tab: if the two NEs are misaligned, the history is not given.

Note: Following a stop of the server or change of monitoring of STM-n Link, the history is not available any more during a few minu tes.

TOPOLOGY MANAGEMENT


Figure 2.123 : Window STM-n Link Details /Occupatio n (8)

� Visualize the occupation of the STM-n Link (all the VC4 bearers and VC4 trails which go through this Link).

� Visualize the collection of performances associated with a STM-n Link (Performances tab): see § 2.6.5 -.

2.6.5 - To visualize / modify the performances of a n STM-n link

This procedure is used to visualize / modify the collection of the points of performance associated with an STM-n link.



� In the list, select the link to be modified then click right to bring up the pop-up menu.

� Click [Properties] to modify the STM-n link: the Properties STM-n Link screen is displayed with following tabs : Linear display, Information, Additional information, Alarms, Occupation, Status History, Performances.

� Click on the Performances tab : the three tabs Definition, Temporal Graphic and Collected counters are available.

TOPOLOGY MANAGEMENT


Figure 2.124 : Window STM-n Link Details /Performan ces/Definition/NEAR counters

Figure 2.125 : Window STM-n Link Details /Performan ces/Definition/FAR counters

TOPOLOGY MANAGEMENT


� Visualize in the Definition tab the list of all the points which accept a collection of performance. Two types of counters are defined : the counters NEAR and the counters FAR for each direction Forward and Reverse.

Notes: (1) The STM-n link can also be selected in the NML View.

(2) the collection of performance is started only i f:

- the STM-n Link is monitored - the case "Collected defined counters" is ticked - the mode is not equal to "none".

If a MSP protection exists on the STM-n Link, the c ollection of the points associated with this protection is made only if the MSP is activated. The number of really collected points is given for the periods of 15mn and the periods of 24h. The collection of performance is launched periodica lly on each equipment according to the values of parameters configure in file config.xml on server IONOS-NMS (see § 1.2.3.6 -).

� If necessary, modify the mode of collection and tick or not the case "Collected counters" (2). The mode of collection makes it possible to select the points automatically. The possible values are:

� none (2)

� extremities 24h (or all 24h)

� extremities 24h/15mn (or all 24h/15mn or all 24h + extremities 15mn)

� Click [Apply ] to validate all the modifications when you finished.

Figure 2.126 : Window STM-n Link Details /Performan ces/Collected counters

TOPOLOGY MANAGEMENT


� Visualize in the Collected Counters tab the values of the counters UAS, ES, SES and BBE which were collected on 15mn and on 24h (according to the mode chosen in the Definition tab) and the periods of unavailability since activation of the collection (3)

� Use the button [Force collection ] to force a collection of the points of performance 15mn and 24h in the equipment (3).

Note: (3) information associated with a forced col lection will be available later only a few minutes if the collection is activated for a certain time. They will not be available before half an hour if the collection has been just activated.

Figure 2.127 : Window STM-n Link Details /Performan ces/Temporal Graphic

� Visualize in the temporal Graphic tab the values of the counters UAS, ES, SES and BBE which were collected on 15mn and on 24h in the form of graph: the errors are represented in red, the not collected periods (lost values, unexpected values, not collected values) are represented in blue.

Note: By moving the pointer of mouse on the graph, you can obtain information of

each period: error count, dates.

� Modify the period displayed on the axis of times (X-axis) by using the button [Change ]. The following window is displayed.

TOPOLOGY MANAGEMENT


Figure 2.128 : Window Time interval selectio n

� Use the buttons [Last hour ], [Last day ], [Last week ], [Last month ] or to manually modify the date of beginning and the date of end.

� Click [Apply ] to validate the update.

� Select the type of counter : UAS, ES, SES or BBE.

� Select the period "15mn" or "24h".

� Select the mode:

� MST Outputs :

2 graphs for STM-n Link without MSP protection, in top the graph of the NEAR/MST/Reverse point and in bottom the graph of the NEAR/MST/Forward point.

4 graphs for STM-n Link with MSP protection, in top two graphs for the points of Working and in bottom two graphs for the points of protection.

� RST Outputs :

2 graphs for STM-n Link without MSP protection, in top the graph of the NEAR/RST/Reverse point and in bottom the graph of the NEAR/RST/Forward point.

4 graphs for STM-n Link with MSP protection, in top two graphs for the points of Working and in bottom two graphs for the points of protection.

� 1 free point :

1 graph for the point NEAR selected with the button [Change ]. The points NEAR of protection can also e selected (validate the selection with [Apply ]).

TOPOLOGY MANAGEMENT


Figure 2.129 : Window Point selection

Note: In the mode "1 free point", it is possible t o display four graphs, one by type of

counter, while selecting like type of counter "UAS/ SES/ES/BBE".

� 2 free points :

2 graphs for two points NEAR selected with the button [Change ]. The points NEAR of protection can also be selected.

� 4 free points :

4 graphs for four points NEAR selected with the button [Change ]. The points NEAR of protection can also be selected.

� Visualize, if necessary, on the graph periods of unavailability by ticking "Unavailable period". They are represented in gray.

� Visualize the counter FAR, if necessary, corresponding to the graph (Forward or Reverse). The values are represented on a black line. When the value misses, the line is not represented any more. One period of unavailability colors the line in gray.

Note: The counter FAR is displayed only for two mo des "MST Outputs" or "RST

Outputs".

2.6.6 - To add an MSP protection on an STM-n link

This procedure is used to add an MSP protection on an STM-n link.

� Display the Topology View (Figure 2.1), then select the STM-n link where the MSP protection will be added.

� Click right to bring up the pop-up menu, then click [Show Links ] : the Show Links window is displayed.

� In the [STMn] tab, select the link to be protected then click right to bring up the pop-up menu.

� Click [Add MSP ] : the Create MSP screen is displayed with the available protections (1).

TOPOLOGY MANAGEMENT


Figure 2.130 : Window Create MSP

� In the Source part of the window, select a source protection.

� In the Destination part of the window, select a destination protection.

� In the MSP Parameters part, tick or enter the protection parameters (2):


b/ SFSD Priority : protection priority degree.

c/ WTR (from 30 to 900 seconds) : time while the status of the normal trail is correct before the return to this normal trail..

d/ Hold Off Time (in 1/10 s) : protection activation time following appearance of an alarm.


� Click [OK] to validate the protection.

Notes: (1) Incompatible protections, already reserv ed or not valid (grayed in) are not accessible.

(2) the default values of MSP parameters correspon d to the values of the preferences of STM-n Link (menu Tools/Preferences/S TM-nLink ).

(3) To create a MSP between an ADR2500 and an EXT1 55HA, use the virtual card on slot B or slot D. (4) The configuration of the RS Path traces for the protecting link is identical to that of the protected link if the function is su pported by the card of the ports of the MSP.

The configuration of the RS Path Trace for the por ts of the protection is carried out during the activation of the protection .

(5) The MSP must be created on ADR10000 using the ADR10000 Proxy. (6) The MSP is not revertive and the priority of t he protection is high G783 on

ADR10000.

TOPOLOGY MANAGEMENT


2.6.7 - To display / modify the properties of an ST M-n link with an MSP protection

This procedure is used to display or modify the attributes of an MSP protected link.



� In the [STMn] tab, select the link to be modified then click right to bring up the pop-up menu.

� Click [Properties ] : the Properties STM-n Link screen is displayed with tabs : Linear display, Information, Additional information, Alarms, Status history.

� Select the Information tab.

Figure 2.131 : Window STM-n Link Details / Informat ion

� Modify the MSP parameters as desired :

a/ Revertive : when this box is ticked, the revertive feature enables return to the normal trail when ready, taking in account the value of WTR.

b/ SFSD Priority : protection priority degree.

c/ WTR (from 30 to 900 seconds) : time while the status of normal trail is correct before the return on this normal trail..

d/ Hold Off Time (in 1/10 s.) : protection activation time after appearance of an alarm.

d/ Mode : bidirectional or unidirectional.

� Click [Apply ] when you have finished.

TOPOLOGY MANAGEMENT


Notes: (1) The MSP protection can be "activated" or not. (2) The created MSP on a STM1 Link between an EXT15 5HA and an ADR2500 is always "undirectional" type and "no revertive" (3) The MSP is not revertive and the SFSD priority parameter is High G783 on ADR10000

2.6.8 - To visualize / modify the performances of a n STM-n Link with an MSP protection

See § 2.6.5 - .

2.6.9 - To activate an MSP protection

This procedure is used to activate a "reserve" or "partially activated" MSP protection (1). During the operation, commands are sent to create the protection and to update monitoring of the ports concerned in each equipment.



� In the [STMn] tab, select the link to be activated then click right to bring up the pop-up menu.

� Click [Activate MSP ] : the MSP Activation result screen is displayed.

Figure 2.132 : Window MSP activation result

� Double-click on the result line to obtain the details of the MSP protection activation and the associated monitoring function (2).

Figure 2.133 : Window MSP activation result/Details

� Click [Close ] then [Finish ] when you have finished.

TOPOLOGY MANAGEMENT


Notes : (1) Status of an MSP :

. an MSP which has just been created is in the "r eserved" status.

. an MSP goes to the "activated" status if the MSP protection has been created in each extremity equipment of the link.

. an MSP activated remains in the "reserved" statu s if the two equipments are inaccessible.

. an MSP activated goes to the "partially activate d" status if the MSP protection is not created in one of the two extremi ty equipments of the link.

(2) The port monitoring function used by the MSP protection in the equipment depends on the value set for the monitoring functio n "yes" or "no".

(3) in the case of MSP activation on an EXT155HA, no command is sent to Physical NEs.

(4) The configuration of the RS Path Trace for the ports of the protection is carried out during the activation of the protection

(5) in the case of MSP activation on an ADR10000, i t must be activated via the ADR10000 Proxy.

(6) The value “Monitoring of the MSP protection” is displayed in the monitoring tab of the audit window

2.6.10 - To deactivate an MSP protection

This procedure is used to deactivate an MSP which is "activated" or "partially activated" (1).



� In the [STMn] tab, select the link to be deactivated then click right to bring up the pop-up menu.

� Click [Deactivate MSP ] : a confirmation message is displayed.

� Click [Yes] to confirm the deactivation.

Figure 2.134 : Window MSP Deactivation result

� Double-click on the result line to obtain the details concerning the MSP protection deactivation.

Notes : (1) Status of an MSP :

. an MSP deactivated goes to the "partially activ ated" status if the MSP protection has not been deleted in one of the two e xtremity equipments of the link.

. an MSP deactivated goes to the "reserved" statu s if the MSP protection has been deleted in both of the extremity equipments of the link.

TOPOLOGY MANAGEMENT


(2) After a deactivation of protection MSP, the mo nitoring of ports is modified to "no".

(3) The unconfiguration of the RS Path Trace for th e ports of the protection is carried out during the deactivation of the protecti on. The consequent actions in the equipment are disabled (“Disable TIM” checke d).

(4) In the case of MSP activation on an ADR10000, i t must be deactivated via the ADR10000 Proxy.

2.6.11 - To delete an MSP protection

This procedure is used to delete an MSP protection.

Caution: To be deleted, a protection must be in the "reserved" status.

� Display the Topology View (Figure 2.1), then select the STM-n link for which the protection is to be deleted.


� In the [STMn] tab, select the link then click right to bring up the pop-up menu.

� Click [Delete MSP ] : a confirmation message is displayed.

� Click [Yes] to confirm the deletion.

� Click [Close ] to close.

2.6.12 - To send MSP protection switchover commands

This procedure is used to send switchover commands.

Caution : Commands can only be sent to an activated MSP protection.

� Display the Topology View (Figure 2.1), then select the STM-n link to which you want to send switchover commands.


� In the [STMn] tab, select the link to be modified then click right to bring up the pop-up menu.

� Click [Properties ] : the Properties Link screen is displayed.

� Select the Information tab, then the Switch command tab.

TOPOLOGY MANAGEMENT


Figure 2.135 : Window Properties STM-n Link / Infor mation

� Select the command which you want to send, then click [Send ].

� Click [Apply ] or [Cancel ] when you have finished.

2.6.13 - To dissociate the MSP protection

This procedure is used to delete an "activated" or "partially activated" MSP protection from the manager base while keeping the protection in each NE.

� Display the Topology View (Figure 2.1), then select the STM-n link for which the protection is to be dissociated.


� In the [STMn] tab, select the link then click right to bring up the pop-up menu.

� Click [Dissociate MSP ] : the MSP protection is dissociated.

� Click [Close ] to close.

TOPOLOGY MANAGEMENT


2.6.14 - To create a graphical link "no-STM-n"

This procedure is used to set up a graphical link "no-STM-n" between two network elements. This link can be created with two PDH-2 Mbit/s interfaces (1) or two "OTHER" interfaces.



� In this window, select the Traffic Carrier icon then click [OK] : the Create Traffic Carrier window is displayed.

� In this window, select the type of Taffic Carrier : Others for Domain, Links for Family, and Other Link for Type, then click [Next ] : the next window is displayed all the interfaces (2).

TOPOLOGY MANAGEMENT


Figure 2.137 : Window Create Link (1)

� In the Source area, select a source interface of type "OTHER" or "PDH-2M" (1) (2) (3).

� In the Destination area, select a destination interface of type "OTHER" or "PDH-2M" (1) (2) (3).

� In the name part of the window, enter a serial number for the new link. By clicking Default Value ], you will obtain a default number. (4)

� Click [Next ] to display the following screen.

Note: (1) Use always a port of type "OTHER" to car ry out a graphic link "not STM-n" starting from the equipment of the type SDH (ADR155 C, ADR155CPE, ADR155E, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000H N, ADR10000 ADR63E1, EXT155HA). (2) the incompatible interfaces, already reserved o r invalid (in grayed) are not accessible.

(3) the interfaces source and destination must be identical (in the same type). (4) the "Function Code" of name is not filled for this type of link.

TOPOLOGY MANAGEMENT



� In the Customer Data part, enter




Note : The monitoring, the graviy profile and the p erformance parameters do not concern this link type.

� Click [Create Link ] to validate the new link: the following screen is displayed.

TOPOLOGY MANAGEMENT



Note: Animations of Linear Display according to ac tivation or alarms are not

provided for this type of link.

� Click [Finish ] if you have finished, the following Create link screen is displayed.


Note: the monitoring, the Gravity Profile and the parameters of performance do not relate to this type of link.

� Click [Close ] then [Finish ] to exit.

Notes : If you create a link with two network eleme nts belonging to two different sub-networks, the graphic representation with the "shor tcut" will be used.

When the graphical Link is created, a graphical li nk is displayed between the two NEs in the Topology View . The link is not animated.

TOPOLOGY MANAGEMENT


2.6.15 - To delete a link "no-STM-n"

� Display the Topology View (Figure 2.1), then select the link "no-STM-n" to be deleted.


� In the [Others ] tab, select the link to be deleted then click right to bring up the pop-up menu.

� Click [Delete ] : a confirmation message is displayed.



2.6.16 - To rename a link "no-STM-n"

� Display the Topology View (Figure 2.1), then click right on the link "no-STM-n" to be renamed.

� Click right to bring up the pop-up menu, then click on [Show Links ] : the Show Links window is displayed.

� In the [Others ] tab, select the link to be renamed then click right to bring up the pop-up menu.

� Click [Rename ] to rename the link: the following screen is displayed.

Figure 2.141 : Window Rename Link

� Modify the serial number.

� Click [Apply ] to validate the operation.

Note : The name of each link is unique: only the se rial number can be renamed.

2.6.17 - To display / modify the properties of a li nk "no-STM-n"

This procedure is used to display/modify the attributes of a link (ports used and customized data).



� In the [Others ] tab, select the link to be modified then click right to bring up the pop-up menu.

� Click [Properties ] to modify the link: the Properties Link screen is displayed with following tabs : Linear display, Information, Additional information .

TOPOLOGY MANAGEMENT


Figure 2.142 : Window Link Details / Linear Display (1)

Note: Animations of Linear Display according to ac tivation or alarms are not provided for this type of link.

Figure 2.143 : Window Link Details / Information (2 )

TOPOLOGY MANAGEMENT


� If necessary, modify the serial number of the name (Information tab).

Figure 2.144 : Window Link Details / Additional inf ormation (3)


� Click [Apply ] when you have finished.

2.6.18 - To Insert a NE in an STM-n link

This procedure is used to insert a network element (NE) in an STM-n link: this link will be destroyed and replaced by two links. All the trails (bearer or not) which go through the original link will be dissociated then re-associated between the NEs (except for the split VC4 bearer).

Caution : Be sure that a new NE of same type (with the same cards SDH) has been created in the database of IONOS-NMS.

� Display the Topology View (Figure 2.1), then select the STM-n link in which you want to insert an NE.


� In the list, select the link then click right to bring up the pop-up menu.

� Click [Insert NE into STM-n ] : the NE Insertion screen is displayed.

TOPOLOGY MANAGEMENT


Figure 2.145 : Window NE Insertion (1)

� Select port 2 of the NE inserted : port 2 will be connected to port 1.

� Select port 3 of the NE inserted : port 3 will be connected to port 4.

� Enter the serial no. for the two links created: by clicking [Default value ], you can call up a default no.

� In the Bearer splitting area, select [Yes] if you split the bearer trails.

� Click [Next ] to go to the next screen.

TOPOLOGY MANAGEMENT



� For each STM-n link created, enter the following data in the Customer Data area:





TOPOLOGY MANAGEMENT



� For each bearer trail created, enter:

a/ the new name in the « long name » field,

b/ the serial number: by clicking on [Default Serial Values ], you can call up a default number.

Caution: Do not insert equipment in a link crossed by a trail/bearer whose route used already the inserted node

� Click [More ] to enter customized data of bearer: customer name, location and information.

� . Click [Next ] to go to the next screen.


TOPOLOGY MANAGEMENT


Note : This screen has two tabs indicating the trai ls impacted by insertion of the new NE.


� If a ring is used, the following screen is displayed :


Note : For the NE to be inserted, the ring must swi tch to its protection function.

� Click [Next ] to proceed with the switchover.

TOPOLOGY MANAGEMENT



Note : When the ring has correctly switched over to its protection, the NE can be inserted.

� Proceed with physical insertion of the NE.

� Click [Next ] : a confirmation message is displayed.

� Click [Yes] to launch the procedure.

� Once the operation has been carried out, result windows are displayed to give:

a/ the connections created in the NE inserted,

b/ the bearer trails renamed in the equipment (case of split VC4-bearer),

c/ the ring activation results (when applicable).

Note: Check for each created bearer and each creat ed STM-n Link the values of

parameters of performance and the Gravity Profile.

TOPOLOGY MANAGEMENT


2.6.19 - To extract an NE in an STM-n link

This procedure is used to extract a network element (NE) from an STM-n link: the two links leading from the NE will be deleted and replaced by a single link. All the trails (bearer or not) which go through the link will be dissociated then re-associated between the NEs. The two bearer trails terminating on the NE removed can then be merged.

� Display the Topology View (Figure 2.1).

� Select the NE which you want to extract.

� Click right to bring up the pop-up menu.

� Click [Extract NE from STM-n] : the NE Extraction screen is displayed.

Figure 2.151 : Window NE Extraction (1)

� Select link no. 1 on the NE to be extracted.

� Select link no. 2 on the NE to be extracted.

� Enter the serial number for the new link created: click [Default value ] to obtain a default value.


TOPOLOGY MANAGEMENT



� In the Customer Data area, enter the following data for the new link created:

a/ customer name in the « Customer name » field (40 characters max.),

b/ location in the « Location » field (40 characters max.),


� When bearer trails are merged, enter the following data for each bearer trail:

a/ new name in « Longname » field,

b/ serial number: click [Default value ] to obtain a default no..

� Click [More ] : the Additional Information window is displayed for additional data: customer name, location and information.


TOPOLOGY MANAGEMENT



Note : This window contains two tabs to indicate th e trails impacted by extraction of

the NE.


� If a ring is used, the following screen is displayed :


Note : For the NE to be extracted, the ring must sw itch over to its protection.

TOPOLOGY MANAGEMENT


� Click [Next ] to proceed with the switchover.


Note : When the ring has correctly switched over to its protection, the NE can be inserted.

� Proceed with physical extraction of the NE.

� Click [Next ] : a confirmation message is displayed.

� Click [Yes] to launch the procedure.

� Once the operation is completed, result windows are displayed indicating:

a/ the connections deleted in the NE extracted,

b/ the bearer trails renamed in the equipment (case of VC4-bearer merging),

c/ the ring activation results (if applicable).

Note: Check for each created bearer and each create d STM-n Link the values of parameters of performance and the Gravity Profile.

TOPOLOGY MANAGEMENT


2.6.20 - To Export the configuration of a link

This procedure is used to export the configuration of a link or several links in a file xml.


� In the search window, select Links : the list of Links is displayed.

� Select the Link(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) :



The name of file is link-yyyy-mm-dd-000n.xml

� To obtain a file of format "text", select the bin folder and run the command :

linksToExcel.cmd filename1 filename2 with filename1 : output file and filename2 : file.xml

Notes : This file give for each Link : - M1400 name - Type - Port source Working - Port destination working - Port source protection MSP - Port destination protection MSP - Monitoring - Gravity profile - Manual profile - List of bearers and trails using this link - Additional information - Performance parameters

TOPOLOGY MANAGEMENT


2.7 - ETHERNET LINK ADMINISTRATION

2.7.1 - To create an Ethernet link

This procedure is used to set up an Ethernet link between two network elements : an « inter- nodal » link is an Ethernet physical connection set up using the Ethernet 10-100Mb or 1Gb interfaces of GFP cards on two NEs (ADR155C, ADR155CPE, ADR2500 EXTRA, ADR622 or ADR10000 ).




Figure 2.157 : Window Create Ethernet Link (1)

� Select the type of traffic carrier : "Ethernet " for Domain, "Links " for Family and "ETH10-100 link " or "ETH1G Link" for the type and give the number of links to be created (1 by default).


TOPOLOGY MANAGEMENT



� In the Source area, select a source Etherne interface (1) (2).

� In the Destination area, select a destination Ethernet interface (1)(2).

� In the name part of the window, enter a serial number for the new link and if necessary a "Long name". By clicking [Default Value ], you will obtain a default number for serial number.

� In the specific parameters area, select the type of two ethernet ports (EP-Line/LAN Support or EVP-Line/LAN Support (used for mutualization)).


Notes: (1) Incompatible interfaces, already reserve d or not valid (grayed in) are not

accessible.

(2) The source and destination interfaces must be ports of Ethernet type : the ethernet links can be created between GFP cards of ADR155C, ADR2500 EXTRA and ADR622 or on cards 4E/FE of ADR155CPE and ADR155C and on the data cards of the ADR10000. It is also possible to use a VNE with card ETH10-100M or card ETH 1Gb

TOPOLOGY MANAGEMENT







� In the Monitoring part(3), if necessary modify the value of monitoring which involves the update in the equipment : All or None .

� In the Gravity Profiles part (3), if necessary modify the mode by ticking or not the case "manual " and if the case "manual" is ticked, modify the value of Gravity Profile with the proposed list.

� Click [Finish ] to validate the new link: the result window is displayed.

Note: (3) the value displayed by default for monit oring, the Gravity Profiles and the parameters of performance are those defined in the preferences of Ethernet Link ( menu Tools/Preferences/Traffic Carrier/Ether net Link. (see § 12.2.11 -)


TOPOLOGY MANAGEMENT


� Click [Close ] to exit.

� If necessary, activate the Ethernet Link (see § 2.7.2 -).

Notes : If you create a link with two network eleme nts belonging to two different sub-

networks, the graphic representation with the "shor tcut" will be used. When the Ethernet Link is created, a graphical lin k with a number (x 100Mb)

(number of Ethernet links) is created between the t wo NEs in the Topology View . The link is animated with the color corresponding to its alarm state. If you place the mouse pointer on the graphical link, the name of link is displayed.

2.7.2 - To activate an Ethernet link

This procedure is used to activate a "reserved" ethernet link. During activation, commands are sent to update monitoring of cards and ports in the two NEs.

� Display the Topology View, then select the ethernet link to be activated.



� In the list, select [Ethernet ] tab, then the link to be activated click right to bring up the pop-up menu.

� Click [Activate ] : a result window is displayed.

TOPOLOGY MANAGEMENT


Figure 2.162 : Window Ethernet Link activation resu lts (1)

Note : An Ethernet link which has just been created is in the "reserved" status. An Ethernet link which is activated is always in th e "activated" status.

� Double-clicking on the result line (or using [Details ]) will bring up a new result window.


� Double-clicking on the result line "Monitor ethernet link " (or using [Details ]), and double-clicking on each result line of the following window "Monitor termination point" will bring up the result of monitoring for card and ethernet port (PPI).


� Click [Close ] to close all the result windows.

Note : If one of two NEs is inaccessible or in sess ion locked, the link is activated and

the NE inaccesible or in session locked will be pot entially misaligned. The monitoring will be realign with an audit on this NE .

2.7.3 - To deactivate an Ethernet link

This procedure is used to deactivate an "activated" ethernet link. During deactivation, commands are sent to update monitoring of cards and ports in the two NEs.

� Display the Topology View (Figure 2.1), then select the ethernet link to be deactivated.

� Cllick right to bring up the pop-up menu, then click [Show Links] : the Show Links window is displayed with the list of links.

TOPOLOGY MANAGEMENT



� In the list, select [Ethernet ] tab, then the link to be deactivated click right to bring up the pop-up menu.

� Click [Deactivate ] : a result window is displayed.

Figure 2.166 : Window Ethernet Link De-activation r esults (1)

Note : An Ethernet link which is deactivated is alw ays in the "reserved" status.


TOPOLOGY MANAGEMENT



� Double-clicking on the result line "De-monitor ethernet link " (or using [Details ]), and double-clicking on each result line of the following window "De-monitor termination point" will bring up the result of demonitoring for card and ethernet port (PPI).



Note : If one of two NEs is inaccessible or in sess ion locked, the link is deactivated and the NE inaccesible or in session locked will be potentially misaligned. The monitoring will be realign with an audit on thi s NE.

2.7.4 - To delete an Ethernet link

Caution : This operation is only possible provided no ethernet services use this link.

� Display the Topology View (Figure 2.1), then select the Ethernet link to be deleted.


� In the list, select [Ethernet ] tab, then the link to be deleted then click right to bring up the pop-up menu.




2.7.5 - To dissociate an Ethernet link

� Display the Topology View (Figure 2.1) then click right on the Ethernet link to be dissociated.

� Click right to bring up the pop-up menu, then click on [Show Links ] : the Show Links window is displayed .

TOPOLOGY MANAGEMENT


� In the list, select [Ethernet ] tab, then the link to be dissociated then click right to bring up the pop-up menu.

� Click [Dissociate ] to dissociate the link: a confirmation message is displayed.

� Click [Yes] to validate the dissociation.


2.7.6 - To display / modify the properties of an Et hernet link

This procedure is used to display/modify the attributes of an Ethernet link (ports used and customized data).

� Display the Topology View (Figure 2.1), then select the Ethernet link to be modified.


� In [Ethernet ] tab, select the link to be modified then click right to bring up the pop-up menu.

� Click [Properties ] to modify the Ethernet link: the Properties Ethernet Link screen is displayed with following tabs : Information, Additional information, Occupation, Al arms, Status History .

� Open the [Information ] tab

Figure 2.169 : Window Ethernet Link Properties / In formation (1)

� If necessary, modify the serial number of the name (Information tab) or the Long name.

� If necessary, modify the type of port (Information tab)

TOPOLOGY MANAGEMENT


Figure 2.170 : Window Ethernet Link Properties / Ad ditional information (2)


Figure 2.171 : Window Ethernet Link Properties / Oc cupation (3)

TOPOLOGY MANAGEMENT


� If necessary, visualize the occupation of the Ethernet link : display of ethernet service using this link with the n° VMAN (Ressource) and the state of activ ation (Occupation tab).

Figure 2.172 : Window Ethernet Link Properties / Al arms (4)

Note: If the traffic is not "OK", the list of alar ms of Ethernet Link is displayed. The value of the "Failure #gravity" displayed corre sponds to the value of the "Gravity Profiles" according to the status of Ether net Link. This value is given in menu "Tools/Preferences/Failure Gravity Configur ation. (see § 12.2.9 -)

� if necessary, modify the value of the monitoring which involves the update in the equipment: All or No (Alarms tab). I

Note: It is not possible to modify the monitoring of EThernet Link to "None" if it is

used by an monitored Ethernet service.

� If necessary, modify the profile of gravity of Ethernet Link: tick or nor the case "Manual " and give a value of the "Gravity Profiles" in the proposed list.


TOPOLOGY MANAGEMENT


Figure 2.173 : Window Ethernet Link Properties /Sta tus history (5)

� Visualize the status history of the Ethernet Link since its creation (Status History Tab) clicking on Status History tab: if the two NEs are misaligned, the history is not given.

Note: Following a stop of the server or change of monitoring of Ethernet Link, the history is not available any more during a few minu tes.

TOPOLOGY MANAGEMENT


2.8 - OPTICAL LINK ADMINISTRATION

2.8.1 - To create a WDM link

This procedure is used to set up a WDM link between two network elements (type FSP2000 or FSP3000): an « inter- nodal » link is an Optical physical connection set up using optical ports on two NEs.




Figure 2.175 : Window Create WDM Link (1)

� Select the type of traffic carrier: "WDM" for Domain, "Links " for Family, and "n Lambda Link " (with n = 1 to 80, n=1/2, n=1/4, n=1/8 ou n=1/10) for the type. Give the number of links to be created (1 by default).

TOPOLOGY MANAGEMENT


Cautions: Links should be created with a lambda throughput corresponding to the

engineering (16 lambda, if the fiber will support 1 6 lambda max for example). IONOS-NMS does not make control on the lambda rate coherence with the engineering. Only external WDM links should be created (respecti ng the engineering by selecting the port where the fiber is connected).



� In the Source area, select a source WDM interface (1) (2) (3) (4).

� In the Destination area, select a destination WDM interface (1) (2) (3) (4).

� In the name part of the window, enter a serial number for the new link and if necessary a "Long name". By clicking [Default ], you will obtain a default number for serial number.


TOPOLOGY MANAGEMENT


Notes: (1) Incompatible interfaces, already reserve d or not valid (greyed in) are not

accessible.

(2) The source and destination interfaces must be ports of WDM type : the WDM links can be created between cards of FSP2000 a nd FSP3000. It is also possible to use a VNE with a card WDM.

Cautions:

(3) FSP3000: the transmission alarms of cards OSFM are synthesised on the ports of cards OSCM or 2OSCM (according to engineer ing). It is possible to create the link between two cards OSCM Whether:

a/ directly by selecting the ports "Network" of c ards OSCM (in this case, alarms located on boards OSCM or 2OSCM will not be propagated on the link – Neither coloration nor traffic status)

or: b/ by selecting the port "Network" on cards OSCM or 2OSCM (according

to engineering). In this case, the alarms located o n boards OSCM or 2OSCM will be propagated correctly on this "symbolic" lin k (coloration and traffic status)

Caution:

(4) for FSP3000, it is mandatory to select West po rt as source and East port as destination of the link. The engineeri ng must also respect this rule (west side of the first FSP cable d with the east side of the second FSP) Since P5.1 reN, it is mandatory to delete and recre ate all the optical link involving FSP3000 created before IONOS-NMS P5. 1 reN in order to respect these rules. (Engineering west/east and link creation)

TOPOLOGY MANAGEMENT







� In the Monitoring part(3), if necessary modify the value of monitoring which involves the update in the equipment : All or None .

� In the Gravity Profiles part (3), if necessary modify the mode by ticking or not the case "manual " and if the case "manual" is ticked, modify the value of Gravity Profile with the proposed list.

� Click [Finish ] to validate the new link: the result window is displayed.

Note: (3) the value displayed by default for monit oring, the Gravity Profiles and the parameters of performance are those defined in the preferences of WDM Link (menu Tools/Preferences/Traffic Carrier/WDM Link).


TOPOLOGY MANAGEMENT



� If necessary, activate the WDM Link (see § 2.8.2 - )

Notes: When the WDM Link is created, a graphical li nk with a number (x λ) (number of Lambda) is created between the two NEs in the Topology View . The link is animated with the color corresponding to its alarm state. If you place the mouse pointer on the graphical link, the name of li nk is displayed.

If you create a link with two network elements bel onging to two different sub-networks, the graphic representation with the "shor tcut" will be used.

2.8.2 - To activate a WDM link

This procedure is used to activate a "reserved" WDM link. During activation, commands are sent to update monitoring of cards and ports in the two NEs.

� Display the Topology View (Figure 2.1), then select the WDM link to be activated.



� In the list, select [WDM] tab, then the link to be activated click right to bring up the pop-up menu.

� Click [Activate ] : a result window is displayed.

TOPOLOGY MANAGEMENT


Figure 2.180 : Window WDM Link activation results ( 1)

Notes : A WDM link which has just been created is i n the "reserved" status.

A WDM link which is activated is always in the "act ivated" status. For FSP3000, the "admin state" is respectively set to 'In service" or "Management" for concerned cards and ports, during the activation of an Optical Links monitored or not.



� Double-clicking on the result line "Monitor WDM link " (or using [Details ]), and double-clicking on each result line of the following window "Monitor termination point " will bring up the result of monitoring for card and port (PPI).



Note : If one of two NEs is inaccessible or in sess ion locked, the link is activated and

the NE inaccesible or in session locked will be pot entially misaligned. The monitoring will be realign with an audit on this NE .

TOPOLOGY MANAGEMENT


2.8.3 - To deactivate a WDM link

This procedure is used to deactivate an "activated" WDM link. During deactivation, commands are sent to update monitoring of ports in the two NEs.

� Display the Topology View (Figure 2.1), then select the WDM link to be deactivated.

� Click right to bring up the pop-up menu, then click [Show Links] : the Show Links window is displayed with the list of links.

� In the list, select [WDM] tab, then the link to be deactivated click right to bring up the pop-up menu.

� Click [Deactivate ] : a result window is displayed.

Figure 2.183 : Window WDM Link deactivation results (1)

Note : A WDM link which is deactivated is always in the "reserved" status.



� Double-clicking on the result line "De-monitor WDM link" (or using [Details ]), and double-clicking on each result line of the following window "De-monitor termination point " will bring up the result of demonitoring for port (PPI).


TOPOLOGY MANAGEMENT



Note : If one of two NEs is inaccessible or in sess ion locked, the link is deactivated

and the NE inaccesible or in session locked will be potentially misaligned.

2.8.4 - To delete a WDM link

Caution : This operation is only possible provided no WDM trails use this link.

� Display the Topology View (Figure 2.1), then select the WDM link to be deleted.


� In the list, select [WDM] tab, then the link to be deleted then click right to bring up the pop-up menu.




2.8.5 - To dissociate a WDM link

� Display the Topology View (Figure 2.1), then click right on the WDM link to be dissociated.

� Click right to bring up the pop-up menu, then click on [Show Links ]: the Show Links window is displayed .

� In the list, select [WDM] tab, then the link to be dissociated then click right to bring up the pop-up menu.

� Click [Dissociate ] to dissociate the link: a confirmation message is displayed.

� Click [Yes] to validate the dissociation.


2.8.6 - To display / modify the properties of a WDM link

This procedure is used to display/modify the attributes of a WDM link (ports used and customized data).

� Display the Topology View (Figure 2.1), then select the WDM link to be modified.


� In [WDM] tab, select the link to be modified then click right to bring up the pop-up menu.

� Click [Properties ] to modify the WDM link: the Properties WDM Link screen is displayed with following tabs: Linear display, Information, Additional information , Occupation, Alarms and Status History .

� Click on tab [Linear display ]

TOPOLOGY MANAGEMENT


Figure 2.186 : Window WDM Link Properties / Linear display (1)

Note: If source or destination ports are belonging to equipment FSP3000, the tool tip gives the direction west to east (see § 2. 8.1 - "To Create a WDM link")

� Click on tab [Information ]

TOPOLOGY MANAGEMENT


Figure 2.187 : Window WDM Link Properties / Informa tion (2)

� If necessary, modify the serial number of the name (Information tab) or the Long name.

Figure 2.188 : Window WDM Link Properties / Additio nal information (3)

TOPOLOGY MANAGEMENT



Figure 2.189 : Window WDM Link Properties / Occupat ion (4)

� If necessary, visualize the occupation of the WDM link : display of WDM trails using this link and the state of activation (Occupation tab).

Figure 2.190 : Window WDM Link Properties / Alarms (5)

TOPOLOGY MANAGEMENT


Note: If the traffic is not "OK", the list of alar ms of WDM Link is displayed.

The value of the "Failure #gravity" displayed corre sponds to the value of the "Gravity Profiles" according to the status of WDM L ink. This value is given in menu "Tools/Preferences/Failure Gravity Configurati on. (see § 12.2.9 -)

� If necessary, modify the value of the monitoring which involves the update in the equipment: All or None (Alarms tab).

Note: It is not possible to modify the monitoring of WDM Link to "None" if it is used

by an monitored WDM Trail.

� If necessary, modify the profile of gravity of WDM Link: tick or nor the case "Manual " and give a value of the "Gravity Profiles" in the proposed list.


Figure 2.191 : Window WDM Link Properties /Status h istory (6)

� Visualize the status history of the WDM Link since its creation clicking on Status History tab: if the two NEs are misaligned, the history is not given.

Note: Following a stop of the server or change of monitoring of WDM Link, the history is not available any more during a few minu tes.

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.).

Note: In some cases, there is no automatic refresh of the NML View also it can be

necessary to do a manually Refresh to update the NM L View window.

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)

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 depe nd on the object processed by the

manager: sub-network, NE, trails, STM-n link, ring, VCGroups, alarms, points of performance (see Appendix : Special functions u pon 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.

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-n etworks 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 objec ts.

� Click [Show result ] to display the results.

Notes : The lists selected can each be displayed i n a tab. Use the [Back] and [Next] buttons (at the top lef t) 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 / Filt er

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

NML VIEW


Figure 3.4 : NML View / Main Filter / Trails / Filt er / 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.

� 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 sele cted celll]. A filter is activated on the cell contents.

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/ d eactivation (Trail/Bearer, VCGroups, Ethernet services, MSP, SNC, Ring), List of the screen "Software management", list of the screen "Show Links" , list s 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 the STM-n links of a sub-network.

� In the result list, select an STM-n link then activate the pop-up menu.

� In this menu, select the function [Set as new input filte r] : the STM-n link appears in the editing chain (Browse ) of the Main Filter.

� Then, select the "Bearers " and "Trails " lists in the Result area: this gives the bearer trails and the trails used by the STM-n link.

3.2.3 - To display a list of SDH trails filtered by customer

This procedure is used to display a list of SDH trails filtered by customer.

� In the Main filter area of the search area, click [Browse ]

� Click on SDH trail customer tab. The list of customers (filled in the field customer name of SDH trails properties) is displayed.

Figure 3.5 : Window – NML view / Browse / SDH trail customer

NML VIEW


� Select a customer in the list and do [Select ]

Note: It is not possible to apply a filter by sele cting a Customer and a Sub-network or a NE.

� In the Result area of the search area, select the object "Trails " to be listed

� Click [Show result ] to display the list of SDH trails whose "customer name" field matches the filter.

3.2.4 - 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.

� Links. The actions associated with this type of object are detailed in the paragraph 2.6 - SDH links administration.

� Ethernet Links . The actions associated with this type of object are detailed in the paragraph 2.7 - Ethernet Link administration.

� WDM Links . The actions associated with this type of object are detailed in the paragraph 2.8 - Optical Link administration.

� Bearers and Trails. The actions associated with this type of object are detailed in the paragraph 4 SDH Trails management.

� VCGroups . The actions associated with this type of object are detailed in the paragraph 5 VCGroups management.

� Ethernet Services . The actions associated with this type of object are detailed in the paragraph 6 Ethernet Point-To-Point Services management and paragraph 7 Ethernet MultiPoint Services.

� WDM Trails . The actions associated wuth this type os object are detailed in the paragraph 8 Optical Trails management.

� Rings . The actions associated with this type of object are detailed in the paragraph 9 Management of MS-SPRing protection.

� Alarms . The actions associated with this type of object are detailed in the paragraph 10 Alarms management.

� Points of Performances . The actions associated with this type of object are detailed in the paragraph 3.2.5 - below.

3.2.5 - Points of performance

The list of the points of performance can be obtained for all the network, by sub-network, for a NE, a STM-n Link, a bearer or a trail given by using the function "Set as new input filter".

3.2.5.1 - To visualize information of a point of co llection

This procedure is used to visualize information of a point of collection.

� Display the NML View window, then select a STM-n Link, a SDH trail or a bearer,

� Click right to bring up the pop-up menu, click on [Set as new input filter ], tick on "SDH perf".

� Click [Show results ]: the list of the points of collection is displayed.

NML VIEW


� Click right to bring up the pop-up menu and click [Properties ]: the properties of the point of collection are displayed window on the right.

Figure 3.6 : Window NML View/Performances/Informati on

� Visualize in the Information tab the information of this point of collection, in particular the name of STM-n Link, Bearer or associated Trail.

Figure 3.7 : Window NML View /Performances/Collecte d counters

NML VIEW


� Visualize in the Collected Counters tab the values of the counters UAS, ES, SES and BBE which were collected over the corresponding period (15mn or 24h) and the periods of unavailability since activation of the collection.

Figure 3.8 : Window NML View /Performances/Temporal Graphic

� Visualize in the Temporal Graphic tab the values of the counters UAS, ES, SES and BBE which were collected over the corresponding period (15mn or 24h) in the form of graph: the errors are represented in red, the not collected periods (lost values, unexpected values, not collected values) are represented in blue.



� Modify the period displayed on the axis of times (X-axis) by using the button [Change ]. The following window is displayed.

NML VIEW


Figure 3.9 : Window Time interval selection

� Use the buttons [Today ], [Last day ], [Last week ], [Last month ] or manually modify the date/hour of beginning and the date/hour of end.

� Click on [Apply ] to validate the update.

� Select the type of counter : UAS, ES, SES or BBE or UAS/ES/SES/BBE.

� Visualize if necessary on the graph periods of unavailability by ticking "Unavailable period". They are represented in gray.

3.2.5.2 - To export the collections of current SDH performances points

A script is provided to start the export of the current performances points. The format used is the same one as that of the historical performances carried out automaticaly by IONOS-NMS.

The script can only be executed from the server IONOS-NMS.

� From the installation folder.(Ionos-NMS or /tools/IONOS-NMS by default), select the bin folder.

� Execute the command:

exportperf.cmd username/password for a server running on PC Windows

or ../exportperf.sh username/password for a server running on SOLARIS (1) (2).

For example /tools/IONOS-NMS/bin/export.sh admin/secret (under Solaris)

The resulting files 15mnCounterLog.txt, 25hCounterLog.txt et UAPLog.txt are created in the folder log/perf in the server installation folder.

For instance, in the repertory IONOS-NMS or /data/IONOS-NMS (by default) :

.\log\perf\15mnCounterLog.txt

.\log\perf\24hCounterLog.txt

.\log\perf\UAPLog.txt

Notes : (1) IONOS-NMS server must be started (2) Use <login> and <password> of a user IONOS-NMS

3.2.5.3 - To export the extremities points of perfo rmances 24h for SDH trails in “text” format

A script is provided to start the export of the 24h extremities points of performances for SDH trails. It is started on Server IONOS-NMS.


� Run the command : (1)(2)(3): exportperf24htrailextremity <login>/<password>

For example: exportperf24htrailextremity admin/secret (with windows )

For example: /tools/IONOS-NMS/bin/exportperf24htrailextremity.sh admin/secret (with solaris)

NML VIEW


The files are stored :

- on PC in the folder \log\perf\yyyy\yyyy-mm\dd of the directory chosen for the installation (c:\Program Files\Ionos-NMS by default).

- on UNIX in the directory /data/IONOS-NMS/log/perf/yyyy/yyyy-mm/dd.

Notes : (1) IONOS-NMS server must be started (2) Use <login> and <password> of a user IONOS-NMS (3) The exported data are those already collected, of the previous day. It is

advisable to await 22h to guarantee the presence of the whole of the data of the day before.

(4)The format used is the same one as that of the “historical” performances

carried out automatically by IONOS-NMS.

SDH TRAILS MANAGEMENT


4. SDH TRAILS MANAGEMENT

4.1 - INTRODUCTION

IONOS-NMS enables end-to-end trail management and management of their protections: this function only concerns the ADR155C, ADR63E1, ADR155CPE, ADR155E, EXT155HA, ADR2500C, ADR2500 EXTRA, ADR622, ADR10000HN and ADR10000 equipment.

Several types of bidirectional trails can be managed: bearer VC4, VC12, VC3, VC4, VC4-4C, VC4-16C and VC4-64C.

� The bearer VC4 trails are formed by a list of connections within STM-n links and are used to carry the VC12 and VC3 end-to-end trails : lower-order trails are thus able to cross higher-order multiplexers.

All the connections belonging to a VC4 bearer trail have the same structure and will interconnect several types of network elements (low rate STM1 multiplexers and high rate STM4-16 multiplexers).

� the VC12 end-to-end trails are formed by a list of TU12 contained in the VC4 carrier trails.

� the VC3 end-to-end trails are formed by a list of TU3 contained in the VC4 bearer trails.

� the VC4 end-to-end trails are formed by a list of VC4 connections contained in the STM1/4/16/64 links.

� the VC4-4C end-to-end trails are formed by a list of VC4-4C connections contained in the STM4/16/64 links.

� The VC4-16C end-to-end trails are formed by a list of VC4-16C connections contained in the STM16/64 links.

� The VC4-64C end-to-end trails are formed by a list of VC4-64C connections contained in the STM64 links.

A trail is routed manually: the user enters all the trail elements and the manager simply controls the feasibility. The manager checks that there is no loop in a trail (network element which can only be crossed once).

Notes : A VC4-4C connection is defined as the conti nuous concatenation of 4 VC4 connections (a freely chosen STM4 link or a free VC 4 connection followed by three VC4 connections in an STM16 link). The VC4 co nnections used are 1 to 4, 5 to 8, 9 to 12 or 13 to 16.

For all the trail types, the Source and Destina tion access points of the

network elements must be defined. The VC4 trails and the VC4 bearers cannot be prote cted by an SNC protection

in the ADR155C P3 type equipment, if version of sof t = P3.x. The SNC protection can be used if version of soft ≥≥≥≥ P4.x

The VC12 trails and the VC4 bearers cannot be prot ected by an SNC

protection in the ADR63E1 type equipment.



4.2 - DESCRIPTION OF "USER" TASKS

4.2.1 - To create a VC4 bearer trail

This procedure is used to define a trail within an STM-n link.

� In the tools bar of the NML View, click left on the New icon: the New window is displayed.


� In this window, select the TRaffic Carrier icon then click [OK] : the Create traffic carrier window is displayed

Figure 4.2 : Window Create Trail/Bearer (1)

� Select the type of traffic carrier: SDH for Domain, Bearers for Family and VC4-Bearer for Type.

� Enter the number of bearers to be created (1 by default)

� then click [Next ] : the Create VC4 Bearer window is displayed with all its resources (1).



Figure 4.3 : Window Create Trail/bearer : VC4 Beare r (2)

� In the Source part of the window, select a Source equipment (2).

� In the Destination part of the window, select (not mandatory) (3) a Destination equipment (2) : the selection is confirmed by a graphic representation of the network elements (ex : AdrSTM4 and NE-104) in the Linear Display part (4).

� If the destination equipment has been selected (3), in the Name part of the window, enter a serial no. for the new bearer. Click [Default ] to obtain a default no. For a multiple creation of bearers, the serial no. is an interval (x-z) or a list of values (x;y;z).

� If necessary, enter a name in the « Long name » field. For a multiple creation, the serial no. will be added to the long name.

� Click [Next ] to confirm the screen: the following screen is displayed.

Notes : (1) Incompatible elements which are already reserved or not valid (grayed in) are not accessible.

(2) Bearer trails interfacing on the equipment: i n this case, only the ADR155C, ADR63E1, ADR155CPE, ADR155E, EXT155HA, ADR2500C, AD R2500 EXTRA, ADR622, ADR10000HN, ADR10000 or the VNE can be used as source and destination.

(3) The destination NE can be selected later. In t his case, the serial no of the

M1400 name cannot be entered. The string of the des tination NE is replaced by "???".



(4) If you want information on the NEs and trails , move the mouse pointer to the icons or to the links in the graphic representa tion.


� Select [All ] or [Extremities ] or [None ] to monitor the alarms of bearer (5)

� Modify the Gravity Profile (5) by ticking the case "Manual " or preserve the default value.

� Modify the mode for the collection of performances and to activate or not the collection of performances or preserve the default values (5).

� Enter:





Note: (5) the default values are those which are d efined in menu Tools/Preferences/Trail.

(5) If monitoring = [extremities], the points of e xtremity NEs are monitored and the points of other NEs are demonitored.




� Select a VC4 connection link (6) (or several for a multiple creation): the selection is confirmed by a graphic representation of the bearer trail (example: trail between equipment Adrstm4 and Rennes-95) in Linear Display part: the equipment crossed by the bearer is shown. A possible MS-SPring or MSP protection may be indicated.

� If you want to modify the equipment or choose another link, click [Previous ] to return to the previous screen.

� Use if required the button [Create Link ] to create the STM-n Link if it were not created as a preliminary (see § 2.6.1 - How to create a STM-n link).

� Use if required the button [Change destination ] to choose the destination NE or to modify the destination NE already selected.




� Select the equipment Destination and enter the serial no. Click [Default ] to obtain a no. by default. Click [OK] to validate the choice of the equipment destination and return to the previous screen.

� Otherwise, click [Next ] to confirm the screen: the following screen is displayed.

� Repeat the operations for each equipment on the main route.

� Once the destination is reached, the [Create main route ] button is displayed.

Notes : (6) Trails already used (grayed in) are not accessible.

(6) for a multiple creation, all the connection li nks must belong to the same STMn Link.

(6) for a multiple creation, use the key "Ctrl" to select/unselect a connection link.

(6)The properties of the selected link can be dis played, by selecting a connection link then clicking on the right button o f the mouse, then on Properties in the pop-up menu.




� Click [Create main rout e] to validate the creation: a result window is displayed with the result for all created bearers.


� Click [Finish ] : the following window is displayed.




Note: By validating creation of the main route, the trail(s) is(are) created in the database.

� Activate the pop-menu to create an SNC protection on each created bearer (see § 4.2.11 - Add a SNC protection to a trail). In the case of a multiple creation, all the bearers will have the same SNC protections (the same containers and the same extremities).

� Click [Map display ] to display the network map.

� Click [Finish ] to finish the operation.

� If necessary, activate the bearer(s) directly (see § 4.2.7 - Activate a trail). In this case, the screen of result is displayed. Double-click on the line of the bearer to obtain the details of activation.

4.2.2 - To create a trail (VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C)

This procedure is used to define a trail within an STM-n or a bearer trail.





� In this window, select the Traffic Carrier icon then click [OK] : the Create Traffic carrier window is displayed with all the trail types.

Figure 4.11 : Window Create Trail/Bearer : VC12 Tra il (1)

� Select the type of traffic carrier: SDH for Domain, Trails for Family and VC12 Trail for type.

� Enter the number of trails to be created (1 by default)

� Then click [Next ] : the Create Trail/Bearer window is displayed with all its resources (1).




� In the Source part of the window, select a Source NE and a PDH or SDH port or several (if multiple creation) (2).

� In the Destination part of the window, select (not mandatory) (3) a Destination NE and a PDH or SDH port or several (if multiple creation) (2) (4) : the selection is confirmed by a graphic representation of the network elements (ex : Adrstm4 and NE-104) in the Linear Display part (5).

� In the Virtual concatenation part, click [Belongs to a virtual concatenated trail] if the trail belongs to a concatenated trail.

� If the destination NE and associated ports have been selected, in the Name part of the window, enter a serial no. for the new trail. By clicking [Default ], you can obtain a default no. For a multiple creation of trails, the serial no. Is an interval (x-z) or a list of values (x;y;z).

� In the « Long name » field, enter a name if necessary. For a multiple creation, the serial no. will be added to the long name.

� Click [Next ] to confirm the screen: the next screen is displayed.


(2) VC3, VC4, VC4-4C, VC4-16C, VC4-64C and VC12 tr ails interface on the PDH and SDH ports whereas the bearers interface on the equipment.

(2)The Properties function in the contextual menu allows the display of the

properties of each NE which can be selected. (2) The Trib1 and Trib2 cards for an EXTRA cannot be used as PDH card.

These cards can be used as protection cards. (2) The Trib1 card for an ADR155E cannot be used a s PDH card. This a card of

protection. (2) The Trib1, 16 and 17 card for an ADR10000HN ca nnot be used as PDH

card. This a card of protection. (3) The destination NE and it (its) port (s) can be selected later. In this case,

the serial no. of the M1400 name cannot be entered. The string of the destination NE is replaced by "???". The icon of de stination NE is identified "Unknown".

(4) It is possible to create a trail on only one N E : in this case the Source NE is

identical to the destination NE. (5) If you want information on the NEs and trails, move the mouse pointer to the icons or links in the graphic representation.




� Select [All ] or [Extremities ] or [None ] to monitor the trail alarms (6).

� If necessary, modify the Gravity Profile by ticking the case "Manual " or preserve the default value (6).

� For VC12/VC3 SDH trails on PDH cards ( ≥5.5 and Adr2500Extra ≥ 3.0.5) , if necessary, modify the Standby Mode or preserve the default value for the source or the destination . The choice is “Normal”, “Standby LOS”, “Standby AIS”

.

Figure 4.14 : Window Create Trail: VC12/VC3 Standby Mode Trail

Normal = no modification on PPI-LOS or PPI-AIS alarms

Standby LOS = Existing PPI-LOS alarm will be inverted after activation of the trail

Standby AIS = Existing PPI-AIS alarm will be inverted after activation of the trail



� Enter :





Note: (6) the default values are those which are d efined in menu Tools/Preferences/Trail. (see § 12.2.5 -) (6) If monitoring = [extremities], the points of ex tremity NEs are monitored and the points of other NEs are demonitored. (6) the capacity of monitoring for LO points is lim ited to 28 points in ADR2500C and 56 points in ADR2500 EXTRA.


� Select a connection link (7) (8) (9) or several (if multiple selection) : the selection is confirmed by a graphic representation of the trail (ex : trail between Adrstm4 and NE-104) in the Linear Display part: all the NEs crossed by the bearer are shown.

� If you want to modify the NEs and select another trail, click [Previous ] to return to the previous screen.

� Use if required the button [Create Bearer ] to create the Bearer (7) if it were not created as a preliminary (see § 4.2.1 - To create a VC4 bearer trail).



� Use if required the button [Change destination ] to choose the destination NE or to modify the destination NE already selected.


� Select the equipment Destination and one or several (multiple creation) PDH or SDH ports and enter the serial no. Click [Default ] to obtain a no. by default. Click [OK] to validate the choices and return to the previous screen.

� Otherwise, click [Next ] to confirm the screen: the next screen is displayed.






� Click [Create main route] to validate the creation: a result window is displayed will the result for all created trails (10).




Notes : (7) The creation of trails VC12 or VC3 is p ossible even if all the bearers were

not created between the Source and it Destination. The creation of the bearer trail can be done during the creation of Trail (but ton Create Bearer).

(8) Trails already used (grayed in) are not access ible.

(9) For the VC12 trails , the resources given from the NE comprise all the bearer trails, the TUG3s, the TUG2s and the TU12s , being understood that a VC4 bearer trail comprises 3 TUG3s, a TUG3 comprises 7 TUG2s a nd a TUG2 comprises 3 TU12s.

(10) For the VC3 trails , the resources given from the NE comprise all the bearer trails, the TUG3s and the TU3s, being understood that a VC4 bearer trail comprises 3 TUG3s, and a TUG3 comprises 1 TU3.

(11) For the VC4 trails , the resources given from the NE comprise all the STM-n links, being understood that an STM-n link comprises n VC4 connections.

(12) For the VC4-4C trails, the resources given f rom the NE comprise all the STM4 links and all the STM16 links, being understoo d that an STM16 link comprises 4 VC4-4C connections : the usable links a re 1 to 4, 5 to 8, 9 to 12 and 13 to 16.

(13)The Properties function in the pop-up menu ena bles you to display the properties of each connection link which can be sel ected. (14) For a multiple creation of trails, all the con nection links must belong to the same container (bearer or STM-n #Link). (15) By validating creation of the main route, the trail(s) is(are) created in the database and is(are) displayed in the list of trail s already created.

� Click [Finish ] : the following screen is displayed.




� Tick the Details box to display the protections of the bearer trails used.


� Activate the pop-up menu [Add protectio n] to create a SNC protection (see § 4.2.11 - Add a SNC protection to a trail). In the case of multiple creation, all the trails will be have the same SNC protections (the same bearers or STM-n Links and the same extremities).


Note: In the case of multiple creation, only one t rail is represented on Linear display.

� If necessary, activate the trail(s) directly (see § 4.2.7 - Activate a trail). In this case, the screen of result is displayed. Double-click on the line of the trail to obtain the details of activation.



4.2.3 - To create a trail with adoption (VC4 bearer , VC12, VC3, VC4, VC4-4C, VC4-16C)

This procedure is used to define a trail within an STM-n or a bearer trail, by adopting the cross-connections already created in the equipment.



� In this window, select the Traffic Carrier icon then click [OK] : the Create Traffic carrier window is displayed.

Figure 4.21 : Window Create Trail/Bearer: VC12 Trai l with adoption (1)

� Select the type of traffic carrier: SDH for Domain, Trails for Family, VC-12 trail for type.

� Enter 1 for the number of trails to be created.

� Then click [Next ] : the Create Trail/Bearer window is displayed with all its resources (1).




� In the Source part of window, select a Source NE and a PDH or SDH port (3)..

� In the Destination part of the window, select a Destination NE (not mandatory) (2) and a PDH or SDH port (3) : the selection is confirmed by a graphic representation of the network elements (ex : NE99) in the Linear Display part (4).


� If the destination NE has been selected, in the Name part of the window, enter a serial no. for the new trail. By clicking [Default ], you can obtain a default no.

� In the « Long name » field, enter a name if necessary.

� Click [Auto XC Audit] to activate the discovery of cross-connections already present in the next equipment (5).




Notes : (1) Incompatible elements which are already reserved or not valid (grayed in)

are not accessible.

(2) The destination NE and it port can be selected later. In this case, the serial no. of the M1400 name cannot be entered. The string of the destination NE is replaced by "???". The icon of destination NE is id entified "Unknown".

(3) VC3, VC4, VC4-4C, VC4-16C, VC4-16C and VC12 tr ails interface on the PDH

and SDH ports whereas the bearers interface on the equipment. (3)The Properties function in the contextual menu allows the display of the

properties of each NE which can be selected. (4) If you want information on the NEs and trails , move the mouse pointer to

the icons or to the links in the graphic representa tion. (5) You can also use the button [Audit XC] instead of [Auto XC Audit] to

activate the discovery of the cross-connections alr eady present in the selected equipment.






� If necessary, modify the mode for the collection of performances and to activate or not the collection of performances or preserve the default values (6).

� Enter :





Note: (6) the default values are those which are d efined in menu Tools/Preferences/Trail. (6) If monitoring = [extremities], the points of ex tremity NEs are monitored and the points of other NEs are demonitored.




� If the connection link is discovered, it is selected in purple: the selection is confirmed by a graphic representation of the trail (ex : trail between NE-99 and Strasbourg – 91 –ADR63E) in the Linear Display part : all the NEs crossed by the bearer are shown. The selection obtained by adoption can be modified.

� Click [Next ] to go to the next screen. The button [Auto XC Audit] being always activated, the discovery of cross-connections is launched in the next NE.


� Click on [Next ] : the destination NE and its PDH or SDH port can be discovered.


� Enter the serial no. Click [Default ] to obtain a no. by default. Click [OK] to validate the choices and return to the previous screen. The button [Create main route ] is displayed.




� Click [Create main rout e] to validate the creation : a result window is displayed with the result for the created trail (7).


Note: (10) By validating creation of the main rout e, the trail is created in the

database and is displayed in the list of trails alr eady created.






� Click on [Map display ] to display the map of network.

� Activate the pop-up menu [Add protection ] to create a SNC protection (see § 4.2.11 - Add a SNC protection to a trail). .





4.2.4 - To create a bearer or trail (VC12, VC3, VC4 , VC4-4C, VC4-16C, VC4-64C) with automatic selection of the route

This procedure is used to define a bearer or a trail within an STM-n or a bearer trail with automatic selection of the route.

� In the tools bar of the NML View, click left on the new icon: the new window is displayed.


� In this window, select the Traffic Carrie r icon then click [OK]: the Create Traffic carrier window is displayed with all the trail types.


� Select the type of traffic carrier: SDH for Domain, Bearer or Trails for Family and the type (VC12 Trail f or example).

� Enter the number of bearer or trail to be created (1 by default).

� Then click [Next ]: the Create Trail/Bearer window is displayed with all its resources (1).




� In the Source part of the window, select a source NE and a PDH or SDH port or several (if multiple creation) (2).

� In the Destination part of the window, select (mandatory for automatic selection of the route) (3) a destination NE and a PDH or SDH port or several (if multiple creation) (2) (4): the selection is confirmed by a graphic representation of the network elements in the linear display part.


� If the destination NE and associated ports have been selected, in the Name part of the window, enter a serial number for the new bearer or trail. By clicking [Default ], you can obtain a default number. For a multiple creation, the serial number is an interval (x-z) or a list of values (w;y;z).

� In the « Long name » field, enter a name if necessary. For a multiple creation, the serial no will be added to the long name.


Notes: (1) Incompatible elements that are already reserved or not valid (greyed) are not accessible.

(2) VC3, VC4, VC4-4C, VC4-16C, VC4-64C and VC12 tr ails interface on the PDH

and SDH ports whereas the bearers interface on the equipment.

(3) The Properties function in the contextual menu allows the display of the properties of each NE that can be selected.

(4) The Trib1 and Trib2 cards for an EXTRA cannot be used as PDH card.

These cards can be used as protection cards.



(5) The Trib1 card for an ADR155E cannot be used a s PDH card. This is a card of protection.

(6) The Trib1, 16 and 17 card for an ADR10000HN ca nnot be used as PDH

card. These are cards of protection.

(7) The destination NE and it (its) port (s) can b e selected later but the automatic selection of the route will not be perfor med. In this case, the serial number of the M1400 name cannot be entered. The str ing of the destination NE is replaced by "???". The icon of destination NE is identified "Unknown".

(8) It is possible to create a trail on only one N E: in this case the Source NE is

identical to the destination NE.

(9) If you want information on the NEs and trails, move the mouse pointer to the icons or links in the graphic representation.





� Enter :







Notes: (10) the default values are those which are defined in menu

ools/Preferences/Trail. (11) If monitoring = [extremities], the points of e xtremity NEs are monitored and the points of other NEs are demonitored. (12) The capacity of monitoring for LO points is li mited to 28 points in ADR2500C and 56 points in ADR2500 EXTRA.


� If a route exist from the current selection to the destination, the container is coloured in green and the first resource available is automatically selected.

Notes: When the automatic selection of the route o ption is activated, IONOS-NMS

computes a route from the current selection to the selected destination. If several routes are discovered, only one of the shortest routes is proposed.

Container coloured in green indicates this route. If you change the current selection, IONOS-NMS com putes the new shortest

route to the destination from the new selection. Caution: Already selected resources are not taken i nto account to compute the end of the route.

The "shortest route" is a route that uses the mini mum number of container to reach the destination. (Number of bearers for trail s VC12 and VC3, number of links STM-n for trail VC4, VC4-4C, VC4-16C, VC4-64C and bearer)

� If no route is found between the current selection to the destination, the following message is displayed, In this case, you may use the button [Create Bearer] for trails VC12 and VC3 or [Create Link] for other trails and bearer to create a new container (see § 4.2.1 -To create a VC4 bearer trail).




� If you want to modify the NEs and select another trail, click [Previous ] to return to the previous screen.

� Use, if required, the button [Change destination ] to modify the destination NE already selected. IONOS-NMS will compute automatically the new shortest route from the current selection to the new destination.

� If you select another container, IONOS-NMS will computes the new shortest route from the new current selection to destination.

� The button [Create shortest route ] can be used if a route has been discovered. In this case, the intermediate screens creation are not displayed.


� Repeat the previous operations for all equipment of the main route.


Figure 4.35 : Window Create Trail/Bearer: VC12 Trai l (6)



� Click [Create main route ] to validate the creation: a result window is displayed with the result for all created trails.


Notes: For a multiple creation of trails, all the c onnection links must belong to the same container (bearer or STM-n #Link).

By validating creation of the main route, the trail (s) is (are) created in the database and is (are) displayed in the list of trai ls already created.

� Click [Finish ] : the following screen is displayed:






� Activate the pop-up menu [Add protection ] to create a SNC protection (see § 4.2.11 - Add a SNC protection to a trail). In the case of multiple creation, all the trails will have the same SNC protections (the same bearers or STM-n Links and the same extremities). If the automatic selection of the shortest route option is activated, the shortest route for the SNC protection will be also computed.


Note: In the case of multiple creation, only one t ra il is represented on linear display.



� Click [Finish ]

Note : The creation of a VC12 trail management (MNGT ports ) takes two VC12 resources into the VC4 for a ADR2500C or ADR2500 EX TRA (and only one for a ADR155C or ADR622), then the second contiguous bus y resource appears available from the trail creation window of IONOS-N MS while it is unavailable in the equipment.

Note: When a SDH trail is created from a data card, the Created traffic carrier wizard suggest to create (or not) a VCGroup.

4.2.5 - To adopt a trail from a NE (VC4 bearer, VC1 2, VC3, VC4, VC4-4C, VC4-16C, VC4-64C)

This procedure is used to adopt a trail within STM-n links or bearers trails from one of NEs crossed by the trail, by adopting the cross-connections already created in the equipment.

� In the explorer or in the Topology View (Figure 2.1), click left to select the network element for which you want to adopt a trail.


� Select the Cross-Connections tab : The cross-connections present in the equipment and which does not correspond to any trail/bearer activated in IONOS-NMS are displayed in red in NE database.



Figure 4.39 : Window Audit Results

� In this window, select the cross-connection(s) corresponding to the trail(s) to adopt and click [Discover path from cross connections ] : the Trail/bearer/protection discovery from NEs window is displayed.

Figure 4.40 : Window Create Trail/Bearer/protection discovery from NEs (1)

� When the discovery by IONOS-NMS of cross-connections in the equipment is finished for the first cross-connection, a message indicates if the first trail were partially or completely discovered.


� Click [Yes] to launch the creation of trail. The screen of choice of the Source NE and its port PDH or SDH (in the case of trail) is displayed.




� In the Source part of this window, the Source NE and its port PDH or SDH (1) are selected purple. The selection cannot be modified.

� In the destination part of this window, the Destination NE and its port PDH or SDH are possibly selected purple (if the discovery is complete).

� All the path discovered is visualized by a graphic representation of the network elements (ex : NE-104 and Adrstm4) in the Linear Display part. (2).

� If the Destination NE and its associated port have been selected (3), in the Name part of the window, enter a serial no. for the new trail. By clicking [Default ], you can obtain a default no.


� Click [Next ] to confirm the screen : the next screen is displayed (4).

Notes : (1) VC3, VC4, VC4-4C, VC4-16C,VC4-64C and V C12 trails interface on the PDH and SDH ports whereas the bearers interface on the equipment.

(1)The Properties function in the contextual menu allows the display of the

properties of each NE which can be selected.



(2) If you want information on the NEs and trails, move the mouse pointer to the icons or links in the graphic representation.

(3) The destination NE and it (its) port (s) can b e selected later. In this case, the serial no. of the M1400 name cannot be entered. The string of the destination NE is replaced by "???". The icon of de stination NE is identified "Unknown". (4) The button "Adopt main route" can be used if th e trail is completely discovered. In this case, the screens of intermedia te creation are not displayed. The values of monitoring, gravity failur e, the mode of collection of performance and the activation of the collection ar e put at the default values (see menu Tools/Preferences/Trail). The field "Loc ation" in Additional Information is automatically filled.


� Select [All ] or or [Extremities ] or [None ] to monitor the trail alarms (5).





� Enter :





Note: (5) the default values are those which are d efined in menu Tools/Preferences/Trail. (6) If monitoring = [extremities], the points of ex tremity NEs are monitored and the points of other NEs are demonitored.




� If the connection link is discovered, it is selected in purple: The selection is confirmed by a graphic representation of the trail (ex : trail between NE-104 and Adrstm4) in the Linear Display part : all the Nes crossed by the bearer are shown. The selection obtained by adoption cannot be modified.



� If the Destination NE and its port PDH or SDH have not been discovered, use the button [Change destination] to select them.

Once the destination is reached, the [Create main route ] button is displayed.

� Click [Create main route ] to validate the creation : a result window is displayed with the result of the created trail. (6)


Notes : (7) By validating creation of the main rout e, the trail is created in the

database.





� Tick the Details box t o display the protections of the bearer trails used.


� Activate the pop-up menu [Add protection ] to create a SNC protection (see § 4.2.11 - Add a SNC protection to a trail).



� The result of the adoption is displayed in the result window.




� Click [Finish ] if all the adoptions are finished.

� The audit of NE is launched again automatically.

4.2.6 - To adopt partially a trail from a NE (VC4 b earer, VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C )

This procedure is used to adopt a part of trail within STM-n links or bearers trails from one of NEs crossed by the trail, by adopting the cross-connections already created in the equipment.




Figure 4.48 : Window Audit Results


Figure 4.49 : Window Trail/Bearer/protection discov ery (partially) from NEs (1)



� When the discovery by IONOS-NMS of cross-connections in the equipment is finished for the first cross-connection, a message indicates if the first trail were partially discovered.


� Click [Yes] to launch the creation of trail.

� All the path discovered is visualized by a graphic representation of network elements (ex : NE105, NE106 and NE-107) in the Linear Display part.




� Click [Next to source ] to select the missing path until the Source NE.

� Click [Change source ] to select the Source NE and its port PDH or SDH (in the case of trail).



� Click [OK] to validate the selection of Source NE.




� Click [Accept source ] to validate the path selected until the Source NE. A confirmation message is displayed to begin the selection of the path until the Destination NE.


� Click [Yes] to continue the selection of trail.




� Select [All ] or [Extremities ] or [No] to monitor the trail alarms.

� If necessary, modify the Gravity Profile by ticking the case "Manual " or preserve the default value.

� If necessary, modify the mode for the collection of performances and to activate or not the collection of performances or preserve the default values.

� Enter :





Note : The values by default are those defined in t he menu Tools/Preferences/Trail. (see § 12.2.5 -)




� If the connection link is discovered, it is selected in purple: The selection is confirmed by a graphic representation of the trail (ex : trail between NE-105 and NE-107) in the Linear Display part : all the NEs crossed by the bearer are shown. The selection obtained by adoption cannot be modified.



� If the Destination NE and its port PDH or SDH have not been discovered, use the button [Change destination ] to select them.

Once the destination is reached, the [Create main route ] button is displayed.

� Click [Create main route ] to validate the creation : a result window is displayed with the result of the created trail.




Notes : By validating creation of the main route, t he trail is created in the database.





� Activate the pop-up menu [Add protection ] to create a SNC protection (see § 4.2.11 - Add a SNC protection to a trail).





� The result of the adoption is displayed in the result window.


� The audit of NE is launched again automatically.

4.2.7 - To activate a trail

This procedure is used to activate a "reserved" (1) or "partially activated" trail. During activation, commands are sent to create connections in all the network elements crossed by the trail.

When the trail is "activated", all the protection paths are also activated.


� In the search window, select Trail : the list of trails is displayed.

� Select the trail(s) to be activated then click right to bring up the pop-up menu:

Figure 4.59 : Window Trail / Activate Trail

� Click [Activate ] : the following activation window is displayed (1) (2) (3).

Notes : (1) A trail which has just been created is in the "reserved" status.

(2) If you activate a trail which uses a bearer t rail which is not activated, the bearer trail will be displayed with the possibility for activating it.

(3) An activated trail goes to the "activated" st atus when all the connections associated to the trail have been created in each c oncerned equipment.

(4) An activated trail remains in the "reserved" s tatus when all the equipment in which connections are to be created are inaccess ible.



� The Trail/Bearer activation results window indicates the status of the activated trail.

Figure 4.60 : Window Trail/Bearer activation result s

� Double-clicking on the trail line will bring up the Details window which shows all of the details in the two tabs, Cross-connections and Monitoring results (4).

Figure 4.61 : Window Trail/Bearer activation result s / Details / Cross-connections

Figure 4.62 : Window Trail/Bearer activation result s / Details / Monitoring results

� Click [Close ] to close the activation window.

Notes : (5) The Details / Cross-connections window displays the list of all the « cross-connections » showing if they have been created or not (in this case, with the cause of the error).

(6) The Details / Monitoring results window lists the points monitored, indicating if they have been updated or not (in thi s case, with the cause of the error).



4.2.8 - To deactivate a trail

This procedure is used to deactivate an "activated" or "partially activated" trail.

When the trail is deactivated, all the protection paths are also activated (1).



� Select the trail(s) to be deactivated then click right to bring up the pop-up menu.

� Click [De-Activate ] : after confirmation, the Trail/Bearer activation results window is displayed indicating the status of the deactivated trail (1) (2) (3).

Notes : (1) It is not possible to deactivate a VC4 bearer trail which carries other activated customer trails.

(2) A deactivated trail goes to the "partially act ivated" status when all the connections associated to the trail have not been d eleted in the concerned equipment.

(3) A deactivated trail goes to the "reserved" sta tus when all the connections associated to the trail have been deleted in each e quipment concerned.

(4) A deactivated trail can remain in the "activat ed" status if all the equipments in which the connections are to be delet ed are inaccessible.

� Double-clicking the trail line brings up the Details window indicating all the information for the trail.

Figure 4.63 : Window Trail/Bearer de-activation res ults / Details

� Click [Close ] to close the window.

Note : After a trail deactivation, the monitoring o f connection points is automatically modified to "No".

4.2.9 - To delete a trail

Caution : This operation is only possible provided the trail is deactivated in the

"reserved" status.



� Select the trail(s) to be deleted then click right to bring up the pop-up menu.

� Click [Delete ] : after confirmation, the trail and its protection paths are deleted from the list.



4.2.10 - To dissociate a trail

This procedure is used to delete, from the manager database, an "activated" or "partially activated" trail while preserving the « cross-connections » in each NE.

� Display the NML View by clicking View > NML View.


� Select the trail to be deleted then click right to bring up the pop-up menu.

� Click [Dissociate ] : after confirmation, the trail is dissociated.

4.2.11 - To add a SNC protection to a trail

This procedure is used to protect a trail within an STM-n link.



� Select the trail for which you want to add a protection then click right to bring up the pop-up menu.

Figure 4.64 : Window NML View / Trail / Add protec tion

� Click [Add protection ] : the Creation protection path window is displayed.



Figure 4.65 : Window Create protection path (1)

� In the Source part of the window, select a Source equipment.

� In the Destination part of the window, select a Destination equipment (not mandatory) (2) : the selection is confirmed by a graphic representation of the network elements (ex : Paris 94 and Rennes-95) in the Linear Display part (3).


Notes : (1) Incompatible elements, already reserved or not valid (grayed in) are not accessible.

(2) The destination NE can be selected later. In this case, the serial no. of the M1400 name cannot be entered. The string of the des tination NE is replaced by "???". The icon of destination NE is identified "Unknown".

(3) If you want more information on the NEs and tra ils, place the mouse pointer on the icons or links in the graphic repres entation.




� In the SNC Parameters part, tick or enter the protection parameters (4) :


b/ Type SNC : choice of SNC protection.

c/ WTR (from 30 to 900 seconds): time while the status of normal trail is correct before the return on this normal trail.


� Click [Next ] to validate the parameters: the next screen is displayed.

Note: (4)The default values are those which are de fined in menu Tools/Preferences/Trail. (see § 12.2.5 -)

(5) If the mode SNC/N is chosen, the monitoring of trail must be "all". (6) For ADR1000, the SNC parameters, Revertive, WT R and Hold Off Time are

no set in the equipment . These parameters must be manually configured from the EMS-ADR and they are available for all SNC Prot ection set in the NE.

(7) Only SNC/I type is supported on ADR10000.




� Select a VC4 connection link or several (if multiple creation) (5) (6): the selection is confirmed by a graphic representation of the bearer trail (example: trail between Paris-94 and Rennes-95) in the Linear Display part.

� If you want to modify the equipment and select another protection trail, click [Previous ] to return to the previous screen.

� If necessary, use the button [Create Bearer ] or [Create Link ] to create a bearer or a STM-n Link if it were not created as a preliminary ( see 4.2.1 - To create a Bearer Trail or 2.6.1 - to create a STM-n Link).

� If necessary, use the button [Change destination ] to select the Destination NE or modify the selection of Destination NE.




� Select the equipment Destination and enter the serial no. Click [Default ] to obtain a no. by default. Click [OK] to validate the choices and return to the previous screen.



Once the destination is reached, the [Create protection path ] button is displayed.

� Click [Create protection path ] to confirm the protection trail creation: A result window is displayed.


� At this moment, the protection(s) is(are) saved in the manager database and can no longer be modified.



Notes : (5) Trails already used (grayed in) are not accessible.

(6) For the VC12 trails , the resources given from the NE comprise all the bearer trails, the TUG3s, the TUG2s and the TU12s, being understood that a VC4 bearer trail comprises 3 TUG3s, a TUG3 comprises 7 TUG2s a nd a TUG2 comprises 3 TU12s.

(7) For the VC3 trails , the resources given from the NE comprise all the bearer trails, the TUG3s and the TU3s, being understood that a VC4 bearer trail comprises 3 TUG3s, and a TUG3 comprises 1 TU3.

(8) For the VC4 trails , the resources given from the NE comprise all the STM-n links, being understood that an STM-n comprises n VC4 connections.

(9) For the VC4-4C trails , the resources given from the NE comprise all the STM4 bearer trails, and all the STM16 links, being understood that an STM16 comprises 4 VC4-4C connections.

(10) in the case of multiple creation, all the con nection links must belong to

the same container (bearer or STM-n Link). (11)The Properties function in the pop-up menu ena bles you to display the

properties of each connection link which can be sel ected.

� Click [Finish ] : the next screen is displayed.


� When the protection is created, it is displayed in the list of protections already created. You can then activate this protection if necessary.



4.2.12 - To add a SNC protection to a trail by usin g adoption.

This procedure is used to add a SNC protection to a trail, by adopting the cross-connections already created in the equipment.



� Select the trail for which you want to add a protection then click right to bring up the pop-up menu.

Figure 4.71 : Window Create Protection with adoptio n (1)

� Click on the button [Add protection ] : the Creation protection path window is displayed.




� In the Source part of the window, select a Source NE.

� In the Destination part of the window, select (not mandatory) (2) a Destination NE : the selection is confirmed by a graphic representation of the network elements (ex : Pau 97 and Unknown) in the Linear Display part.

� Click [Auto XC Audi t] to activate the discovery of cross-connections already present in the next equipment.

� Click [Next ] to confirm the screen : the next screen is displayed.


(2) The destination NE can be selected later. In this case, the serial no. of the M1400 name cannot be entered. The string of the des tination NE is replaced by "???". The icon of destination NE is identified "Unknown". (see Figure 4.72 above)










Note: (3) the default values are those which are d efined in menu Tools/Preferences/Trail. (see § 12.2.5 -)




� If a connection link is discovered, it is selected in purple. the selection is confirmed by a graphic representation of the network elements (ex : Pau 97 and NE-98) in the Linear Display part: all the NEs crossed by the bearer are shown. The selection obtained by adoption can be modified.

� Click [Next ] to go to the next screen. The button [Auto XC Audit ] being always ticked, the discovery of cross-connections is launched in the next NE.


� Click [Next ] : the Destination NE can be discovered if adoption.




� Click [OK] to validate the selection of Destination NE and return to the previous screen. The button [Create protection path] is displayed.




� Click [Create protection path] to validate the creation of protection : A result window is displayed for the created protection.




Notes : By validating creation of the protection ro ute, the protection is created in the database.

� Click [Finish ].




� Activate the pop-up menu [Add protection ] to add another SNC protection.


� If necessary, activate the protection direct. In this case, the result window is displayed. Double-click on the line of the protection to obtain the details of activation.



4.2.13 - To adopt a trail with SNC protection from a NE (VC4 bearer, VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C)

This procedure is used to adopt a trail with SNC protections within STM-n links or bearers trails from one of NEs crossed by the trail, by adopting the cross-connections already created in the equipment.




Figure 4.79 : Window Create Trail/bearer/protection discovery from NEs (1)





� When the discovery by IONOS-NMS of cross-connections in the equipment is finished for the first cross-connection, a message indicates if the first trail were partially or completely discovered.


� Click [Yes] to launch the creation of trail.

� Adopt the main route (see § 4.2.5 - Adopt a trail from a NE). The next screen is displayed.


Notes: Two lines are displayed for each protection (extremities NEs of protection).



� Select one of the lines, then click right to bring up the pop-up menu.

� Click [Adopt ] : the Creation protection path window is displayed.


� In the Source part of the window, the discovered NE is selected in purple. the selection is confirmed by a graphic representation of the network elements (ex : protection between Pau 97 and Unknown) in the Linear Display part. The selection obtained by adoption cannot be modified.

� Click [Next ] to confirm the selection : the next screen is displayed.










Note: (1) the default values are those which are d efined in menu

Tools/Preferences/Trail (see § 12.2.5 -).




� If a connection link is discovered, it is selected in purple. the selection is confirmed by a graphic representation of the network elements (ex : Pau 97 and NE-98) in the Linear Display part: all the NEs crossed by the bearer are shown. The selection obtained by adoption cannot be modified.


� Repeat the operations for each equipment of the protection path.

� Click [Next ] : The Destination NE is discovered. The next screen is displayed.




� Click [OK] to validate the selection of Destination NE and return to the previous screen. The button [Create protection path ] is displayed.




� Click [Create protection path ] to validate the creation : a result window is displayed for the created protection.







� Select possibly another line to create another SNC protection and activate the pop-up menu [Adopt ]. Repeat the operation

� When you have finished, click [Finish ].

� If necessary, activate the trail with its protections. In this case, the result window is displayed. Double-click on the line of the trail to obtain the details of activation.

� The result of adoption is displayed in the next screen.





� The NE audit is launched again automatically.

4.2.14 - To adopt the SNC protection of a trail fro m a NE (VC4 bearer, VC12, VC3, VC4, VC4-4C, VC4-16C, VC4-64C)

This procedure is used to adopt a SNC protection within STM-n links or bearers trails from one of NEs crossed by the protection, by adopting the cross-connections already created in the equipment.

� In the explorer or in the Topology View (Figure 2.1), click left to select the network element for which you want to adopt the protection.


� Select the Cross-Connections tab : The cross-connections present in the equipment and which does not correspond to any trail/bearer activated in IONOS-NMS are displayed in red in NE database (case of connection with protection in NE and without protection in IONOS-NMS).

Figure 4.91 : Window Create Protection discovery fr om NEs (1)



� In this window, select the cross-connection(s) corresponding to the protection to adopt and click [Discover path from cross connections ] : the Trail/bearer/protection discovery from NEs window is displayed.


� When the discovery by IONOS-NMS of cross-connections in the equipment is finished, a message indicates if the protection was partially or completely discovered.


� Click [Yes] to launch the adoption of the SNC protection.




� Select the line, then click right to bring up the pop-up menu.

� Click [Adopt ] : the Creation protection path window is displayed.




� In the Source part of the window, the discovered NE is selected in purple. the selection is confirmed by a graphic representation of the network elements (ex : protection between Pau 97 and Unknown) in the Linear Display part. The selection obtained by adoption cannot be modified.

� Check [Auto XC Audit ] is ticked. If not activate [Auto XC Audit ]

� Click [Next ] to confirm the selection : the next screen is displayed.









� Click [Next] to validate the parameters: the next screen is displayed.

Note: (1) the default values are those which are d efined in menu Tools/Preferences/Trail. (see § 12.2.5 -)




� If a connection link is discovered, it is selected in purple. the selection is confirmed by a graphic representation of the network elements (ex : Pau 97 and NE-98) in the Linear Display part: all the NEs crossed by the bearer are shown. The selection obtained by adoption cannot be modified.


� Repeat the operations for each equipment of the protection path.

� Click [Next ] : The Destination NE is discovered. The next screen is displayed.




� Click [OK] to validate the selection of Destination NE and return to the previous screen. The button [Create protection path] is displayed.




� Click [Create protection path ] to validate : a result window is displayed for the created protection.

Figure 4.100 : Window Create Protection discovery f rom NEs (10)






� Click [Finish ] to terminate the operation.

� If necessary, activate the protection. In this case, the result window is displayed. Double-click on the line of the protection to obtain the details of activation.

� The result of adoption is displayed in the next screen.





� The NE audit is launched again automatically.

4.2.15 - To delete a SNC protection of a trail

This procedure is used to delete an SNC protection of a trail which has already been created: you can only delete the protection provided it is "reserved".


� In the Search window, select Trail : the list of trails is displayed.

� Select the trail for which you want to delete the protection, then click right to bring up the pop-up menu.

� Click [Protection deletion ] : the Deletion Protection Results window is displayed on the right

� Click [Close ] to close the window : the protection path selected is deleted.

Notes : It is also possible to delete one or severa l SNC protection paths, using the

menu [Delete] of pop-up menu on the selected protec tions in tab Protection Path of menu Properties of trail (click right).

The deletion can be activated on a multiple select ion of trail/bearers with SNC protection in state "reserved".

4.2.16 - To activate the SNC protections of a trail

This procedure is used to activate all the "reserved" or "partially activated" protection paths or a trail. During the operation, commands are generated to create protection connections in all the NEs crossed by the protection paths.


� In the search window, select Trail or Bearer : the list of trails is displayed.

� Select the trail for which you want to activate the protection, then click right to bring up the pop-up menu.

� Click [Protection activation] : the Activation Protection Results (1) (2) window is displayed on the right.


Notes : (1) The result window displays the list of all the cross-connections, showing if they have been created or not (in this case, with t he cause of the error).

(2) A trail for which the protection has been act ivated goes to the "activated" or "partially activated" state.

It is also possible to activate one or several SNC protection paths, using the menu [Activate] of pop-up menu on the selected prot ections in tab Protection Path (click right).

The activation can be activated on a multiple sele ction of trail/bearers with protection.

(3) For ADR1000, the SNC parameters, Revertive, WTR and Hold Off Time are no set in the equipment . These parameters must be manually configured from the EMS-ADR and they are available for all SNC Prot ection set in the NE.



4.2.17 - To deactivate the SNC protections of a tra il

This procedure is used to deactivate all the "activated" or "partially activated" protection paths. During the operation, commands are generated to delete the protection connections in all the NEs crossed by the protection paths.



� Select the trail for which you want to activate the protection, then click right to bring up the pop-up menu.

� Click [Protection deactivation ] : the Deactivation Protection Results (1) (2) window is displayed on the right.


Notes : (1) The result window displays the list of all the "cross-connections", showing if they have been deleted or not (in this case, wit h the cause of the error).

(2) A trail for which the protection has been dea ctivated goes to the "partially activated" state.

It is also possible to deactivate one or several S NC protection paths, using the menu [De-activate] of pop-up menu on the select ed protections in tab Protection Path (click right).

The deactivation can be activated on a multiple se lection of trail/bearers with protection.

4.2.18 - To send SNCP protection switchover command s

Caution : These commands can only be sent to an "ac tivated" trail.




Figure 4.103 : Window SNC Switch commands


� Select the trail to which you send a command, then click right to bring up the operations pop-up menu.

� Click [Properties ] : the trail properties are displayed on the right.

� In the right window, select the Protection path tab then, in the list, the trail which is to receive the command.

� At the bottom of the window, click the Switch commands tab: the following commands are displayed: Clear, Forced to working, Forced to protection, Manual to working, Manual to protection, SNC Switch Lockout.

� Select the command which you want to send.

� Click [Send ] to generate the command.

Note : The Switch command is applied to the protect ion path selected.

4.2.19 - To display/modify the properties of a trai l

This procedure is used to visualize / modify the properties of a trail.



� Select the trail which you want to display, then click right to bring up the pop-up menu.


� Select one of the tabs: Linear display, Information, Protection path, Additional information, Alarms, Status history or Performances.

� Click [Refresh ] to update the data or reset the default values.

� Click [Apply ] to apply the modifications.



Figure 4.104 : Window Trail / Properties / Linear d isplay (1)

� In the Linear Display tab, Click [Activation ] in "Animation" area to visualize the state of activation of the trail.

Notes : In the Linear Display window, the trails are represented by a continuous line

for the main trail or by a dotted line for the prot ection trail: the lines are green (when the trail is activated) or orange (when the t rail is "reserved" or "partially activated"). When necessary, an MS-SPRING or MSP pr otection information is displayed.

Color of Link :

- For the path "Working" : always green

- For the path of protection: green if protection SNC is activated, orange if protection SNC is reserved or partially activated.

Color of the name of NE icons:

- In green if cross-connection is activated on it

- In orange if cross-connection is not activated on it.

� In the Linear Display tab, Click [Alarms ] in "Animation" area to visualize the state of alarm of the trail according to the direction (one-way or bidirectional).



Figure 4.105 : Window Trail / Properties / Linear d isplay (2)

Color of the link:

- For the path "Working" and a given direction

� in green if not of alarm or alarm of maximum severity = warning on the output

� in gray if "output" NE is a VNE

� in blue if alarm of inaccessibility on output NE

� in red if alarm of maximum severity = major on output NE

� in yellow if alarm of maximum severity = minor on output NE

- For the path "Working" and the bidirectional mode:


- For the path "Protection" (protection SNC) and a given direction

� in green if not of alarm or alarm of maximum severity = warning on output NE

� in gray if it "output" NE is a VNE

� in gray if the SNC protection is not activated




- For the path "Protection" (protection SNC) and the bidirectional mode:

� colored according to the synthesis of the colors of the two directions according to the command gray, green, yellow, red and blue.



Color of NE icons :

- Color of for a given direction is:

� in green if not of alarm or alarm of maximum severity = #warning

� without color if is not to it a #VNE

� in blue if alarm of inaccessibility

� in red if alarm of maximum severity = major

� in yellow if alarm of maximum severity = minor

- Color of for the bidirectional mode is:

� colored according to the synthesis of the colors of the two directions according to the command without color, green, yellow, red and blue.

Note: all alarms acknowledged or not are taken int o account..

The direction of traffic is not taken into account. The alarms on the port of MSP protection are taken into account only if the MSP is activated on both NEs. For the color of NE, only alarms on the CTP of inpu t of the activated cross-connection which belongs to an activated path.

� Click [Traffic Indic .] (tab Linear display ) to visualize if the traffic passes by the path "Working" or the path of protection according to the direction.

� Select one of NEs or one of Links and activate the pop-up menu (click right). This menu allows to launch the actions on the selected NE or Link, or on the SNC protection.

Figure 4.106 : Window Trail / Properties / Informat ion

Notes : The Information tab displays the details of the trail (Trail or Bearer) on the main path or the protection paths.

The name M1400 (serial no.), the « Long name » an d the «Belongs to a concatenated trail» field can be modified .



Figure 4.107 : Window Trail / Properties / Protecti on path

Note : In the Protection Path tab, you can display and modify the SNC parameters of a protection.

Figure 4.108 : Window Trail / Properties / Addition al information

Note : In the Additional Information tab, you can c ustomize the data: customer name, location and info.



Figure 4.109 : Window Trail / Properties / Alarms

Note: In the Alarms tab, you can activate/deactivat e the monitoring function. You can also modify the "Gravity Profile" (tick on "Man ual" and select a value of "Gravity Profile" in the proposed list).

If you tick on [Extremity port de-monitoring], the monitoring points of extremity ports will be demonitored on the two extr emity NEs.

It is possible of modify the monitoring of a trail /bearer which passes by a STM-16 used in a ring only if the ring is "monitore d". If the traffic is not "OK", the list of the associa ted alarms is displayed.

The value of the "gravity failure" which is displa yed is given by the "Gravity Profile" and the status of trail. This value corres ponds to the table of configuration given in menu "Tools/Preferences/Grav ity Profile".(see § 12.2.9 -)



Figure 4.110 : Window Trail / Properties / Status h istory

Note : In the Status history tab, you can display t he status history of the trail since it was activated: if one of the extremity NEs is misal igned, the history is not always supplied.

Following a stop of the server or change of monito ring of the trail, the history is not available any more during a few minutes.

The status history is calculated from the Fault lo g. If the Fault log is purged, the status history will be not given for the purged events.

Figure 4.111 : Window Trail / Properties / CC



Note : In the CC tab, you can display the descripti on of all cross-connections associated with this trail.

Figure 4.112 : Window Trail / Properties / Occupati on (Bearer)

Note : In Ocupation tab, you can display the occupa tion of all the trails created and activated using this bearer.

� Visualize if necessary the collection of performance associated with the trail (tab Performances ): see § 4.2.20 -.

4.2.20 - Visualize / modify the performances of a t rail

This procedure is used to visualize / modify the collection of the points of performance associated with a trail.





� Click on the Performances tab..

� Select the Performance tab and access to the three sub-tabs : Definition, Temporal Graphic and Collected counters.



Figure 4.113 : Window Trail /Performances/Definitio n/Near Counters

� Visualize in the Definition tab the list of all the points which accept a collection of performance. Two types of counters are defined :

- In the NEAR counters tab : les NEAR counters for the direction Forward (source NE towards

destination NE) and the direction Reverse (destination NE towards source NE)..

- In the FAR counters tab : les FAR counters for the direction Forward (source NE towards destination NE) and the direction Reverse (destination NE towards source NE)..

Notes : (1) the collection of performance is starte d only if: - the trail is monitored - the case "Collected defined counters" is ticked - the mode is not equal to "none".

IONOS collects the values of performance once by ho ur. 4 records of 15mn are read in NE. If a SNC protection exists on the trail, the collec tion of the points associated with this protection is made only if the SNC is act ivated. The number of really collected points is given for the periods of 15mn and the periods of 24h. The collection of performance is launched periodica lly on each equipment according to the values of parameters conconfig.xml on server IONOS-NMS. (see § 1.2.3.6 -) The collected values are saved in database. The number of records is limited by configuration ( file xml see § 1.2.3.6 -) (10000 maximum). When the maximum number is reached, the server expo rt a part of records in a file (format ASCII) and delete the exported records (6000 by default). The exported files are saved in folder "/IONOS-NMS/ log/export". The older exported files are deleted periodically ( if date > 3 months by default).



� If necessary, modify the mode of collection and tick or not the case "Collected counters" (1). The mode of collection makes it possible to select the points automatically. The possible values are:

� none (1)

� extremities 24h: points collected over one period of 24h on both NEs of extremities.

� extremities 24h/15mn: points collected over one period of 24h and 15mn on both NEs of extremities.

� all 24h: points collected over one period of 24h on all NEs.

� all 24h/15mn: points collected over one period of 24h and 15 mn on all NEs

� 24h + extremities 15mn: points collected over one period of 24h on all NEs and one period of 15 mn on both NEs of extremities.

� Click [Apply ] to validate all the modifications when you finished.

Figure 4.114 : Window Trail /Performances/Collected counters

� Visualize in the Collected Counters tab the values of the counters UAS, ES, SES and BBE which were collected on 15mn and on 24h (according to the mode chosen in the Definition tab) and the periods of unavailability since activation of the collection (1)

� Use the button [ Force collection ] to force a collection of the points of performance 15mn and 24h in the equipment (2).

Notes: (2) information associated with a forced co llection will be available later only

a few minutes if the collection is activated for a certain time. They will not be available before half an hour if the collection has been just activated.

(2) [Force Collection] is used to speed up the col lect. The message "Collection has been re-scheduled and will be done in a few minutes" is displayed. Refresh the collected counters in a few minutes. A new collect will be displayed.

(3) by ticking on the small arrows, it is possibl e to display the tabs of performance in full screen or vice versa.



Figure 4.115 : Window Trail /Performances/Temporal Graphic

� Visualize in the temporal Graphic tab the values of the counters UAS, ES, SES and BBE which were collected on 15mn and on 24h in the form of graph: the errors are represented in red, the not collected periods (lost values, unexpected values, not collected values) are represented in blue.



� Modify the period displayed on the axis of times (X-axis) by using the button [Change]. The following window is displayed.

Figure 4.116 : Window Time interval select ion



� Use the buttons [Today ], [Last day ], [Last week ], [Last month ] or to manually modify the date/hour of beginning and the date/hour of end.

� Click [Apply ] to validate the update.

� Select the type of counter : UAS, ES, SES or BBE.

� Select the period "15mn" or "24h".

� Select the mode:

� Outputs :

2 graphs for a Trail/Bearer, in top the graph of the NEAR/MST/Reverse point on output NE and in bottom the graph of the NEAR/MST/Forward point on input NE.

� Inputs and outputs :

4 graphs for a Trail/Bearer, in top two graphs for the points NEAR (Forward and Reverse) for the output NE and in bottom two graphs for the points NEAR (Forward and Reverse) for the input NE.

� 1 free point :

1 graph for the point NEAR selected with the button [Change ]. The points NEAR of protection can also be selected (validate the selection with [Apply ]).

Figure 4.117 : Window Point selection

Note: In the mode "1 free point", it is possible t o display four graphs, one by type of counter, while selecting like type of counter "UAS/ SES/ES/BBE".

� 2 free points :

2 graphs for two points NEAR selected with the button [Change ]. The points NEAR of SNC protections can also be selected.



� 4 free points :

4 graphs for four points NEAR selected with the button [Change ]. The points NEAR of SNC protections can also be selected.

� Visualize, if necessary, on the graph periods of unavailability by ticking "Unavailable period". They are represented in gray.

� Visualize the counter FAR, if necessary, corresponding to the graph (Forward or Reverse). The values are represented on a black line. When the value misses, the line is not represented any more. One period of unavailability colors the line in gray.

Note: The counter FAR is displayed only for two mo des "Outputs" or " Outputs".

4.2.21 - Visualize / modify the performances of a t rail with Near correlation

This procedure is used to visualize / modify the collection of the points of performance associated with a trail, with utilization of near correlation.





� Click on the Performances tab.

� Select the Performance tab and access to the three sub-tabs : Definition, Temporal Graphic and Collected counters.

� If necessary, detach the window "Properties of bearer/trail", using the drawing pin at the top of the right. The window can be displayed in full screen or iconised.

� In the Definition tab, the points NEAR (NEAR Counters Tab) and FAR (FAR Counters Tab) are defined (see § 4.2.20 -). The collection of performance is started, the trail is monitored and activated, the "Collected defined counters" is ticked and the mode is selected. Use the mode "all 24h/15mn".

� Select the points used for the near correlation in Tab NEAR Correlation : two points can be defined for each direction Forward (source NE towards destination NE) and Reverse (destination NE towards source NE).



Figure 4.118 : Window - Trail /Performances/Definit ion/Near Correlation (1)

� Click [Change ] for each point you want selected : the window "Point selection" is displayed..

Note: It is possible to define only the two counte rs Forward or only the two

counters Reverse.

� Select the point and Click [Apply ] to validate the selection.

Figure 4.119 : Window - Trail /Performances/Definit ion/Near Correlation (2)



� When the points of correlation are defined (two points Forward, two points Reverse or two points Forward + two points Reverse), click [Refresh ] to update the values of counters which correspond the point of correlation.

Notes: The definition of performance points used f or near correlation (NEAR Correlation tab) is not saved in database. This sel ection will be lost when the display of trail "Properties" will be closed.

� The selection of two points (Forward or Reverse) allows to define the

corresponding point of near correlation. Its name i s the name of second point + the string "Near correlation" which is added :

Example: First point Forward : Dijon26/2/TRIB 3-4S1.1/STM1- 1AU4-1/TU12-2(lo) Second point Forward : Nice26/1/TRIB 3-4S1/1/STM1- 2/AU4-1/TU12-2 (lo) point of correlation Forward : Nice26/1/TRIB 3-4S1 .1/STM1-2/AU4-1/TU12-2 (lo-

Near correlation). For this point of correlation, the values of count ers UAS/SES/ES/BBE will be

given for periods of 15mn and 24h.

� Visualize in the Collected Counters tab the values of the counters UAS, ES, SES, BBE and the values of Unavailable periods (UAP) which were collected on 15mn and on 24h for this point of correlation.

Notes: The value of Unavailable periods (UAP) are not available for the ADR10000

Figure 4.120 : Window – Trail /Performances/Collect ed counters of Near Correlation point

� Visualize in the temporal Graphic tab for this point of correlation the values of the counters UAS, ES, SES and BBE which were collected on 15mn and on 24h in the form of graph: the errors are represented in red, the not collected periods (lost values, unexpected values, not collected values) are represented in blue. Choose the mode “1 free point” and select the point of correlation with button [Change ].

Note: The description of “Temporal Graphic” Tab is done in previous paragraph.



Figure 4.121 : Window - /Performances/Temporal grap hic of Near Correlation point

Figure 4.122 : Window - /Performances/Temporal Grap hic of Near Correlation point and associated points.



4.2.22 - To create a Tandem Connection

Tandem Connection Monitoring allows carriers to monitor the end-to-end quality of service across network segments. Operator can identify an error generation location in his network.

This procedure is used to create a Tandem Connection on a trail of type VC4 or VC3 or on a VC4 bearer.


� In the search window, select Trail or Bearer : the list of trails/bearers is displayed.

� Select the trail/bearer on which you want to create a Tandem Connection then click right to bring up the pop-up menu.


� Click on the TCM tab.

Figure 4.123 : Window – Trail / Create TCM (1)

� Then Click [Add ] : the “Create TCM” window is displayed.




� In the Source part of the window, select the source NE of TCM.

� In the Destination part of the window, select the destination NE of TCM.

� Click [Add ] to validate the creation : a result window is displayed.


Notes : A TCM which has just been created is in th e “reserved” status.

The trail on which the TCM has been created is in t he “reserved” or “partially activated” (if activated before the creation of TCM ) status. The creation of Tandem connection is possible betwe en two NES of main route of trail. The Nes extremity of SNC protection cannot be selec ted. The Nes included between two Nes extremity of SNC p rotection cannot be selected. The two Nes extremity of bearer cannot be selected. Two Tandem connection cannot cross. The TCM will be created with a monitoring to “all” (value by default).

� Click [Close ] to finish the creation.

� If necessary, activate the Tandem Connection (see § 4.2.23 -).



4.2.23 - To activate a Tandem Connection

This procedure is used to activate a “reserved” Tandem Connection on a trail of type VC4 or VC3 or on a VC4 bearer.



� Select the trail/bearer on which you want to activate a Tandem Connection then click right to bring up the pop-up menu.



� Select the TCM to be activated then click right to bring up the pop-up menu.

Figure 4.126 : Window – Trail /Bearer / Activate TC M

� Click [Activate ] : two windows are displayed : the activation results window and a warning window.



Figure 4.127 : Window – Trail / Bearer / TCM act ivation results

Figure 4.128 : Window – Trail / Bearer /TCM Warning window

Notes : The warning window displays the Tandem con nections to be configurated in

all the Nes of activated TCM. The Tandem Connection must be coneach NE on the giv en CTP (output, input or both) associated to the trail/bearer. A Tandem Connection cannot be activated if the trai l/bearer is not “activated”. A trail/bearer goes to the “activated” status when all the Tandem Connections associated to the trail/bearer have been activated. If you activate a trail/bearer with Tandem connecti ons, the tandem connections will be activated. A warning window wil l be displayed, giving all the Tandem connections to be configurated in all th e Nes.

� Click [Close ] to close the two windows.

4.2.24 - To deactivate a Tandem Connection

This procedure is used to deactivate an “activated” Tandem Connection on a trail of type VC4 or VC3 or on a VC4 bearer.



� Select the trail/bearer on which you want to deactivate a Tandem Connection then click right to bring up the pop-up menu.



� Select the TCM to be deactivated then click right to bring up the pop-up menu.



Figure 4.129 : Window – Trail /Bearer / Deactivate TCM

� Click [Deactivate ] : two windows are displayed : the deactivation results window and a warning window.

Figure 4.130 : Window – Trail / Bearer / TCM dea ctivation results

Figure 4.131 : Window – Trail / Bearer / TCM dea ctivation results



Notes : The warning window displays all the Tandem Connections to be de-configurated in all the Nes of trail deactivated. The Tandem Connection must be de-configurated with HTTP browser in each NE on the given CTP (output, input or both) associa ted to the trail/bearer. A trail/bearer goes to the “partially activated” st atus when one at least Tandem Connections associated to the trail/bearer h as been deactivated. If you deactivate a trail/bearer with Tandem connec tions, the tandem connections will be deactivated. A warning window w ill be displayed, giving all the TCM to be de-configurated in all the Nes.

� Click [Close ] to close the two windows.

4.2.25 - To delete a Tandem Connection

This procedure is used to delete an “reserved” Tandem Connection on a trail of type VC4 or VC3 or on a VC4 bearer.



� Select the trail/bearer on which you want to delete a Tandem Connection then click right to bring up the pop-up menu.



� Select the TCM to be deleted then click right to bring up the pop-up menu.

� Click [Delete ] : the deletion results window is displayed.

Notes : A trail/bearer “partially activated” (with TCM reserved) goes to the “

activated” status when all the Tandem Connections a ssociated to the trail/bearer has been deleted. If you delete a trail/bearer with Tandem connection s, the tandem connections will be deleted.


4.2.26 - To dissociate a Tandem Connection

This procedure is used to dissociate an “activated” Tandem Connection on a trail of type VC4 or VC3 or on a VC4 bearer.



� Select the trail/bearer on which you want to deactivate a Tandem Connection then click right to bring up the pop-up menu.



� Select the TCM to be dissociated then click right to bring up the pop-up menu.

� Click [Dissociate ] : the dissociation results window is displayed.

Notes : If you dissociate a trail/bearer with Tand em connections, the tandem

connections will be dissociated.




4.2.27 - To display / modify the properties of a Ta ndem Connection

This procedure is used to visualize / modify the properties of a Tandem Connection.



� Select the trail/bearer on which you want to display/modify the properties of a Tandem Connection then click right to bring up the pop-up menu.


� Click on the TCM tab : the list of TCM associated to the trail/bearer are displayed with their status (“reserved” or activated”).

Figure 4.132 : Window – Trail / Bearer /TCM

� Modify, if necessary, the monitoring of all the TCM (two values “all” and “extremities”).

� Validate the modification by clicking [Apply ] : A warning window displays the tandem connections to be de-configurated in the intermediate Nes (if modification from “all” to “extremities”) or to be configurated in the intermediate Nes (if modification from “extremities” to “all”) with HTTP browser.

Figure 4.133 : Window – Trail / Bearer / TCM Warnin g Window



4.2.28 - To visualize / modify the performances of a trail with TCM

This procedure is used to visualize / modify the collection of the performance points associated with a trail, with utilization of Tandem Connections .



� Select the trail/bearer with tandem Connection on which you want to display/modify the performances, then click right to bring up the pop-up menu.


� Click on the Performances tab.

� Select the Performance tab and access to the three sub-tabs : Definition , Temporal Graphic and Collected counters .

� If necessary, detach the window “Properties of bearer/trail ”, using the drawing pin at the top of the right. The window can be displayed in full screen or iconised.

� In the Definition tab, the points NEAR (NEAR Counters Tab) are defined for the Tandem Connections of trail/bearer (for example TCM Dijon 26/2- Nice 26/1). The collection of performance is started, the trail is monitored and activated, the Tandem connections are activated and monitored (all or extremities). The “Collected defined counters” is ticked and the TCM mode is selected (Use for example the mode “all 24h/15mn”).

Figure 4.134 : Window – Trail /Performances/Definit ion with TCM

Notes: For this TCM points, the values of counters UAS/SES/ES/BBE will be given for

periods of 15mn and 24h. The associated type is Nea r tcm.

� Visualize in the Collected Counters tab the values of the counters UAS, ES, SES, BBE and the values of Unavailable periods (UAP) which were collected on 15mn and on 24h for this TCM points of type “near tcm ”.



Figure 4.135 : Window – Trail /Performances/Collect ed counters of Near TCM point

� Visualize in the temporal Graphic tab for this TCM points the values of the counters UAS, ES, SES and BBE which were collected on 15mn and on 24h in the form of graph: the errors are represented in red, the not collected periods (lost values, unexpected values, not collected values) are represented in blue. Choose the mode “1 free point” and select the TCM point with button [Change ].

Figure 4.136 : Window – Trail /Performances/TC M selection point

� Select the TCM point and validate with button [Apply ].



Figure 4.137 : Window - /Performances/Temporal grap hic of Near TCM point

4.2.29 - To audit the TCM parameters in a network e lement (NE)

Caution : This operation is only valid for ADR2500 EXTRA.

The NE audit 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 IONOS-NMS manager.



Notes : If there is an inconsistency between the ma nager data and the NE data, the audit line is displayed red: a message at the top l eft 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 it is not aligned.

� Select the General tab to display the general parameters

� Check the capability “Tandem Connection support” = “Yes” in part “capability parameters” of IONOS database and in NE database.



Figure 4.138 : Window – Audit Results / General

Notes : The capability “TCM Connection Support” can be realigned in IONOS by using the button [NE to NMS capability parameters a lignment].

� Select the Cross-Connections tab to display the « cross-connections » activated.

Figure 4.139 : Window - Audit Results / Crossconne ctions



Notes : In tab Crossconnections, the column “TCM” d isplays the type of TCM :

- None : the Tandem Connection is not created in IONO S/NE or created in “reserved” state in IONOS

- A-Included : the Tandem Connection defined on port “Input”

- Z-Included : the Tandem Connection defined on port “Output”

- Both : the Tandem Connection defined on the two por ts “Input” and “Output”.

Caution : The Tandem Connections cannot be reactiva ted in the NE by using the button [Global NMS to NE cross-connections re-activation].

After the reactivation of a cross-connection with Tandem Connection, a TCM warning window is displayed to give the Tandem Conn ection which must be configurated or de-configurated in the NE with HTTP Browser.

4.2.30 - To merge two VC4 bearers

This procedure is used to merge two VC4 bearers. During the operation, commands are sent to the NE in which the bearers are merged (to deactivate the old cross-connections and reactivate the new cross-connection), on the others Nes, if there is a rename of cross-connections associated to the bearer, and on the Nes, used by these bearers and gone through by a ring (modification of the misconnection table).


� In the search window, select Bearer : the list of bearers is displayed.

� Select the bearer which you want to merge, then click right to bring up the pop-up menu.

� Click [Merge ] : the window Merge of VC4 bearers : bearer selection is displayed with the list of bearers which can be merged with the first selected bearer.



Figure 4.140 : Window Merge of VC4 bearers (1)

Note: Two VC4 bearers can be merged if :

- They use the same AU4 in case of MS-SPRing. - They have only a NE together. - All the trails which use the first bearer, use also the second bearer and vice-

versa with the same TU12 or TU3. - The value of “monitoring” should be identical for t he two bearers.

� Select the second bearer and click [Next ] : the next screen is displayed.




For the new bearer which will be created :

� Enter the serial number : click [Default ] to have a value by default.

� Enter the “Long name”.

� If necessary, modify the Gravity Profile by ticking the case “Manual “ or preserve the displayed values.

� If necessary, modify the mode for the collection of performances and to activate or not the collection of performances or preserve the displayed values.

� Enter :




� Click [Next ] to go to the next screen : the list of trails VC12 or VC3 impacted by the merge of two bearers is displayed.




� Click [Next ] : a confirmation window is displayed.


� Click [Yes] to launch the action.

� When the action is finshed, some results windows are displayed :

a/ the list of deleted cross-connections (connections VC12 and VC3) in the NE on which the two bearers are merged and the list of demonitored points.

b/ the cross-cpnnection created in the NE (connection VC4) on which the two bearers are merged and the list of points monitored or demonitored (according to the value of monitoring).

c/ the cross-connections renamed in the other Nes used by the bearer.

d/ the results of misconnection table modification in the Nes used by a MS-SPRING.

Note : Check for the new created bearer the values of Gravity Profile and the values of performance parameters (collect and mode).



4.2.31 - To split a VC4 bearer

This procedure is used to split a VC4 bearer. During the operation, commands are sent to the NE in which the bearer is splitted (to deactivate the old cross-connection and reactivate the new cross-connections), on the others Nes, if there is a rename of cross-connections associated to the bearers, and on the Nes, used by these bearers and gone through by a ring (modification of the misconnection table).


� In the search window, select Bearer : the list of bearers is displayed.

� Select the bearer which you want to merge, then click right to bring up the pop-up menu.

� Click [Split ] : the window Split of VC4 bearers : bearer selection is displayed with the list of Nes (and associated cross-connection) on which the bearer can be splitted.

Figure 4.144 : Window Split of VC4 bearer (1)

Note : A bearer cannot be splitted on : - A NE of main route in a portion of main route prote cted by a SNC

protection path. - An ADR2500C which doesn’t provide the VC12 switch ( version < P3) - An ADR2500C or an ADR2500 EXTRA on which the maximu m number of

TU/LO monitored points will be reached after the sp lit.



� Select the NE and Click [Next ] : the next screen is displayed


For the first bearer which will be created :

� Enter the serial number :click [Default ] to have a value by default.




� Enter :








For the second bearer which will be created :

� Enter the serial number :click [Default ] to have a value by default.




� Enter :




� Click [Next ] to go to the next screen: the list of trails VC12 or VC3 impacted by the split of bearer is displayed.




� Click [Next ] : a confirmation window is displayed.


� Click [Yes] to launch the action.

� When the action is finished, some results windows are displayed :

a/ the deleted cross-connection (connections VC4) in the NE on which the bearer is splitted and the list of demonitored points.

b/ the list of cross-connections created in the NE (connection VC12 and VC3) on which the bearer is splitted and the list of points monitored or demonitored (according to the value of monitoring).

c/ the cross-connections renamed in the other Nes used by the bearer.

d/ the results of misconnection table modification in the Nes used by a MS-SPRING.

Note : Check for the new created bearer the values of Gravity Profile and the values of performance parameters (collect and mode).



4.2.32 - To swap a SNC protection

This procedure is used to swap the roles “working” and “protection” of a SNC protection on a bearer or a trail. This function allows to reorganize the occupation of resources in a network without cut of traffic.


� In the search window, select Trail ou Bearer : the list of trails/bearers is displayed.

� Select the bearer/trail with SNC protection you want to swap, then click right to bring up the pop-up menu..

� Click [Properties ] : The properties of bearer/trail are displayed at the right. This window can be detached.

� Select the tab Protection path.

Figure 4.149 : Window Swap of bearer/trail (1)

� Select the protection path to swap, then click right to bring up the pop-up menu.

� Click [Swap protection ]. A confirmation message is displayed.

� Click [Yes] to launch the action. The window Protection swap results is displayed.




� Double-click on the result line to obtain the details of swap. The new cross-connections created in the extremities Nes are displayed.


� Click [Close ] then [Finish ] to finish. The tab Protection Path is displayed again.

Notes : The trail or the bearer you want to swap mu st be in state « Activated » or «

Reserved ». The function « swap » is not possible on a NE of type EXT155HA. The function « swap » is possible on a NE of type ADR155C if the version of

soft ≥ P4.x If the traffic was before swap on protection path, the traffic will be always

switched on protection path after swap. The function « swap » is not supported on a NE of type ADR155E,

ADR10000HN or ADR10000.

4.2.33 - To invert the direction of a traffic carri er

This procedure is used to invert the direction of a Bearer or a trail SDH. The cross-connections and the name M1400 of the traffic carrier are without cut of traffic.


� In the search window, select Trail ou Bearer : the list of trails/bearers is displayed.

� Select the bearer/trail you want to invert, then click right to bring up the pop-up menu..

� Click [Invert Direction] : The window Invert Trail/Bearer Direction is displayed.



Figure 4.152 : Window Invert Trail/Bearer Direction (1)

� Enter a suffix number for the M1400 name of the modified traffic carrier (4 characters max) Click [Default ] to obtain a default number

� In the “Long name” field, enter a name if necessary. (the “long name” of the inverted traffic carrier is proposed)

� Click [Apply ]. To launch the action..

� A confirmation window is displayed.


� Click [Yes] to launch the action. The results window is displayed.


� Double-click on the result line to obtain the details of the inversion. The new cross-connections renamed in the Nes, are displayed.




� Click [Close ] then [Finish ] to finish.

Notes : The trail or the bearer properties are not modified by the function of inversion

4.2.34 - To supervise in real time the trail status

This procedure is used to supervise in real time the trail status (only for SDH trails). The maximum number of trails supervised in real time can be modified in a file xml (voir § 1.2.3 - Available configurations on Server IONOS-NMS).


� In the search window, select Trails : the list of Trails is displayed.

� Select the Trails then click right to bring up the pop-up menu.

� Click [Enable real time supervision ]: a result window is displayed.

Figure 4.156 : Window Enable Real Time Supervision trail / result


Notes: If the trail is supervised in real time, th e indication “Real time Supervision “ is updated (ticked) in the list of trails in NML View.

The trail status (global status) can be visualis ed in the window “Real Time Supervision” (see § 10.2.13 -Management of current alarms->To display the trails supervised in real time) The export of daily reports of the status of the tr ails supervised in real time present in previous IONOS-NMS versions, is replaced by a new tab “SDH Trails Log” in the screen “Log View” (see § 11 Mana gement of Histories->To display the logs)

Caution: Only the users with a profiles “provider access” set to Yes, have access to this functionality.

4.2.35 - To remove a trail from real time supervisi on

This procedure is used to remove a trail from real time supervision (only for SDH trails).


� In the search window, select Trail : the list of Trails is displayed.

� Select the Trail then click right to bring up the pop-up menu.

� Click [Disable real time supervisio n] : a result window is displayed:



Figure 4.157 : Window Disable Real Time Supervision trail / result


Notes : If the trail is no more supervised in real time, the indication “Real time Supervision “ is updated (not ticked) in the list o f trails in NML View.

The trail status (global status) cannot be visualis ed anymore in the window “Real Time Supervision” (see § 10.2.13 - Managemen t of current alarms->To display the trails supervised in real time).


4.2.36 - Standby Mode management

This procedure is used to modify the Standby Mode (only for VC12/VC3 SDH trails on Adr155c ≥P5.5 and Adr2500Extra ≥3.0.5 ). .


� In the search window, select Trails : the list of Trails is displayed.

� Select the Trails then click right to bring up the pop-up menu.

� Click [Standby mode source ] or [Standby mode destination ] and [Normal/Standby Ais/Standby Los ]. .

Figure 4.158 : Window modification Standby Mode for VC3/VC12 trails



� A result window is displayed

Figure 4.159 : Window result for Standby Mode (VC3 /VC12 trails)


4.2.37 - To Export the configuration of a trail

This procedure is used to export the configuration of a bearer or trail or several bearers or trails in a file xml.


� In the search window, select Bearers or Trails : the list of Bearers or Trails is displayed.

� Select the Bearer(s) or Trails(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) :



The name of file is bearer-yyyy-mm-dd-000n.xml or trail-yyyy-mm-dd-000n.xml

� To obtain a file of format “text”, select the bin folder and run the command :

TrailsToExcel.cmd filename1 filename2 with filename1 : output file and filename2 : file.xml

Notes : This file give for each Bearer or Trail : - M1400 name - Long name - Type - NE source - NE destination - List of links connection of main route - List of links connection of protection route - Monitoring - Gravity profile - Manual profile - For a bearer, List of trails using this bearer - Additional information - Performance parameters - Activation status

VCGROUPS MANAGEMENT


5. VCGROUPS MANAGEMENT

5.1 - INTRODUCTION

IONOS-NMS enables end-to-end VCGroups management. A VCGroup connects two ports (f type VCG) and uses some trails SDH to carry Ethernet traffic.

This function only concerns :

� the GFP boards on ADR155C – version ≥ P4 and on ADR2500 EXTRA ≥ P2.1 ,

� the 4E/FE board on ADR155CPE or ADR155C ≥ P5.2

� the 4E/FE + 1GE board on ADR155C ≥ P5.5

� the GigabitEthernet boards on ADR2500C and ADR2500 EXTRA.

� the UFTQA boards of the ADR 155E

� the UGSD boards of the ADR155e and ADR 10000HN

� the GFP boards on ADR622 ≥ P1.1

� the EISMB_840, EISMB_804, MSCM and DIOM_40 boards of ADR 10000

On GFP card, 8 VCGroups can be created. Each VCGroup can provide 46 VC12 trails or 2 VC3 trails maximum.

On the GigabitEthernet Board of ADR2500, only one VCGroup can be created with 7 VC4 trails maximum. The VC4 trails must be connected right (port 1 with port 1) and have to be created in the order of ports numbering.

The VCGroups are not managed on the ADRIMA card of ADR155C.

On the UFTQA board of ADR155E, 32 VCGroups can be created. 4* 63 trails VC12 or 4*3 trails VC3 can be created selecting the ports VC12 or/and VC3 of the object “SDHMap” of the board.

On the UGSDA board of ADR155E, 2 VCGroups can be created. 4*1 trails VC4, 4* 63 trails VC12 or 4*3 trails VC3 can be created selecting the ports VC4, VC12 or/and VC3 of the object “SDHMap” of the board.

On the UGSD board of ADR10000HN, 2 VCGroups can be created. 2(4*1) trails VC4, 2(4* 63) trails VC12 or 2(4*3) trails VC3 can be created selecting the ports VC4, VC12 or/and VC3 of the two objects “SDHMap” of the board.

The trails starting from the first pool (SDHMap-3) should be used only with the first VCGroup (vcg-5)

The trails starting from the second pool (SDHMap-4) should be used only with the last VCGroup (vcg-6)

On the EISBM_840 and EISMB_804 boards of the ADR10000, 8 VCGroups can be created. It supports granularity VC12/VC3/VC4 with a maximuml capacity of 2,5 Gb/s. It provides 16 * VC4 ports, 48 * VC3 and 252 * VC12 ports.

On the DIOM_40 board of the ADR10000, 4 VCGroups can be created. It supports granularity VC12/VC3/VC4. It provides 16 * VC4 ports, 48 * VC3 and 252 * VC12 ports.

In all the cases,

the ports VC12-1 to 21 and the port VC3-1 of the same pool should not be used at the same time,



the ports VC12 or VC3 of the same pool and the port VC4 should not be used at the same time

VCGROUPS MANAGEMENT


On the MSCM board, 16 VCGroups can be created. It supports granularity VC12/VC3/VC4. It provides 32 * VC4 ports, 96 * VC3 and 252 * VC12 ports.

The port numbering differs from the EMS-ADR and IONOS-NMS. Some interfaces may be assigned as Ethernet or EoS port. See below, the correlation between both.

Port ID

(GUI order)

EMS-ADR

Type of

Interface

Port assignment

IONOS-NMS

1 EoS or ETFE GFP VCG-1 or ETH 10/100-1








9 EoS GFP VCG-9

10 EoS GFP VCG-10

11 EoS GFP VCG-11

12 EoS GFP VCG-12

13 EoS GFP VCG-13

14 EoS GFP VCG-14

15 EoS GFP VCG-15

16 EoS GFP VCG-16

17 OTGBE/OTFE ETH 1G -9








Figure 5.1 : MCSM port numbering and assignment

VCGROUPS MANAGEMENT


5.2 - DESCRIPTION OF “ USER” TASKS

5.2.1 - To create a VCGRoup

Note: When a SDH trail is created from a data card, the Created traffic carrier wizard suggest to create (or not) a VCGroup.

This procedure is used to define a VCGroup.

� In the tools bar of the NML View, click left on the New icon : the New window is displayed.


� In the window, select the Traffic Carrie r icon then click [OK] : the Create Traffic Carrier window is displayed.

Figure 5.3 : Window Create VCGroup (1)

� Select the type of Traffic carrier : Ethernet for Domain, VCGroups for Family, VCGRoup for the type and give the number of VCGroups to be created (1 by default).

VCGROUPS MANAGEMENT


� Click [Next ] to display the following screen : all the list of interfaces is displayed (1).


� In the Source area, select a source VCG interface (2).

� In the Destination area, select a destination VCG interface (2).

� In the name part of the window, enter a serial number for the new VCGroup and if necessary a “Long name”. By clicking [Default Value ], you will obtain a default number for serial number.

� In the Specific parameters area, enter the type of VCG ports : EP-Line/LAN Support or EVP-Line/LAN Support (with mutualization) (3)


Notes: (1) Incompatible interfaces, already reserve d or not valid (grayed in) are not accessible.

(2) The source and destination interfaces must be ports of VCG type : the VCGRoups can be created between GFP cards (ADR155C and ADR2500 EXTRA) or 4E/FE card ≥ P5.2, 4E/FE + 1GE ≥P5.5 between GigabitEthernet cards (ADR2500C, ADR2500 EXTRA and ADR622). It is a lso possible to use a VNE with cards GFP and GigabitEthernet.

(3) The value displayed for the type of VCG ports is the value defined in the VCGRoup Preferences (menu TOOLS/Preferences/Traffic Carrier/VCGRoup see § 12.2.7 -)

VCGROUPS MANAGEMENT







� In the Monitoring part (3), if necessary modify the value of monitoring which involves the update in the equipment : All or None .

� In the Gravity Profiles part (3), if necessary modify the mode by ticking or not the case “manual” and if the case “manual ” is ticked, modify the value of Gravity Profile with the proposed list.

� Click [Finish ] to validate the new VCGroup : the result window is displayed.

Note: (3) the value displayed by default for monit oring, the Gravity Profiles and the parameters of performance are those defined in the preferences of VCGRoup ( menu Tools/Preferences/Traffic Carrier/Vcgroup s ee § 12.2.7 -).


� Click [Close ] to close the result window : the next window is displayed.

VCGROUPS MANAGEMENT



� If necessary, add trails in VCGRoup (see § 5.2.7 - “to add trails in a VCGRoup”.

� Click [Finish ] to validate the creation of VCGroup.

� If necessary, activate the VCGroup (see § 5.2.2 -).

Notes : There is no graphical representation create d for the VCGroup in Topology View.

When creating the VCGroup, no update is done in the Nes.

5.2.1.1 - To create a VCGoup with ADR10000

First it is necessary to configure GeoS ports from the EMS-ADR: Refer to the main document Element Management System for ADR Platforms version 8.1 N 2 53 359 465-A CARD CONFIGURATION AND MANAGEMENT Configuring DIO EIS/EISM GeoS ports and MCS Card Internal for MSCM board. Also VCG settings: I-NNI interface is not supported .

Procedure to create and configure a VCGroup on DIOM/EISMB board using the ADR10000 Proxy from the data card:

� Choose the VCG granularity and the Number of VC’s allocated. The GeoS port must be enabled.

Example: See below the settings of VCG-7 (EoS port 7)

VCGROUPS MANAGEMENT


Figure 5.8 : Window Configuring GEoS ports (1) – A DR10000 In this example, the both VC3 allocated for the VCG-7 are the number 16 and 17 (see below).

Figure 5.9 : Window Configuring GEoS ports (2) – A DR10000

� From the Create traffic carrier wizard of Ionos-NMS, it is mandatory to select the same number of VC: GFP-VC3-16 and GFP-VC3-17

VCGROUPS MANAGEMENT


Figure 5.10 : Window Create GFP trail

� Follow the procedure and activate the VC3 trails

� From the Create traffic carrier wizard of Ionos-NMS, it is mandatory to create the same VCG number 7: VCG-7 (see below)

Figure 5.11 : Window Create VCGroup

VCGROUPS MANAGEMENT


� Then, follow the VCGroup creation using the normal procedure. Procedure to create and configure a VCGroup on MSCM board using the ADR10000 Proxy from the data card:

� Choose the Port Type (L2 EoS NNI) and the Port Bank (A or B)

Note: Granularity for MCSM card on VC-12 is permitt ed with Bank A only.

Example: See below the settings of VCG-12 (EoS port 12)

Figure 5.12 : Window Configuring EoS ports (1) – A DR10000

� Choose the VCG granularity and the Number of VC’s allocated. The EoS port must be enabled

VCGROUPS MANAGEMENT



� Choose the VCG granularity and the Number of VC’s allocated.

� The number of allocated VC3 are displayed in the Topology Tree.

In this example, the both VC3 allocated for the VCG-12 are the number 18 and 19 (see below).


� From the Create traffic carrier wizard of Ionos-NMS, it is mandatory to select the same number of VC on the MSCM board: GFP-VC3-18 and GFP-VC3-19

� Follow the procedure and activate the VC3 trails

� From the Create traffic carrier wizard of Ionos-NMS, it is mandatory to create the same VCG number 12: VCG-12

� Then, follow the VCGroup creation using the normal procedure.

VCGROUPS MANAGEMENT


5.2.2 - To activate a VCGroup

This procedure is used to activate a “reserved” or “partially activated” VCGroup (1). During activation, commands are sent in the two Nes of VCGroup to create the VCGroup, to update the monitoring, to create connections in all the network elements crossed by the trails associated to VCGroup, to allocate the trails in the VCGroup.


� In the search window, select VCGRoups : the list of VCGroups is displayed.

� Select the VCGroup(s) to be activated then click right to bring up the pop-up menu.

� Click [Activate ] : the following activation window is displayed (1) (2) (3) (4) (5).

Figure 5.15 : Window VCGroup activation results

Notes : (1) The status of a VCGroup (“global status activation”) is the synthesis of activation state of VCGroup parameters (“parameters activation” ), of the activation state of trails and of the allocation ac tivation state of trails (allocation activation). (2) a VCGroup which has just been created is in a “ reserved” state. (3) a VCGroup which has just been activated goes to the “activated” status when all the trails of VCGRoup are activated in all the network elements crossed and when all the trails of VCGroup are allo cated in the two equipment extremities of VCGroup.

(4) a VCGroup which has just been activated goes t o the “Partially activated” status when all the trails of VCGroup are not all a ctivated or allocated.

(5) a VCGRoup which has just been activated remain s in the “reserved” or

“partially activated” status if one of Nes is inacc essible or in session locked.

Caution: On ADR10000, the activation of VCG must b e done using the ADR10000 proxy.

� Double-clicking on the VCGroup line or using [Details ] will bring up a new window Activate VCGRoup which shows the detailled results for the parameters activation, the trails activation and the trails allocation.

VCGROUPS MANAGEMENT


Figure 5.16 : Window VCGroup activation results / D etails (1)

� Double-clicking on line « VCGroup parameters activation » or using [Details ] will bring up the details of the monitoring update (to Yes or No) according to the chosen value for the VCGroup (see tab Alarms in Properties of VCGroup).

Note : (6) If the update of monitoring cannot be d one in one of two Nes, the

parameters will be “activated”, but the NE will be misaligned.

� Double-clicking on line « Trail activation » or using [Details ] will bring up the details of the trails activation.

Figure 5.17 : Window VCGRoup activation results / D etails (2)

� Double-clicking line « Trail allocation activation » or using [Details ] will bring up the global result of trails allocation.

Figure 5.18 : Window VCGRoup Trail allocation activ ation results / Details

Note : (7) If one of two extremities Nes is inacces sible or in locked session, the allocation of trails is not done (result of “ Extre mity Nes lock “).

VCGROUPS MANAGEMENT


� Double-clicking line « Allocations activation » or using [Details ], then double-clicking line «A-end trails allocation activation » or « Z-end trails allocation activation » will bring up the result of allocation activation for each trail of VCGroup in each NE.

Figure 5.19 : Window VCGRoup A-end Trails allocatio n activation results / Details

Notes : 46 VC12 trails or 2 VC3 trails maximum can be allocated in a VCGroup on an

GFP card. 7 VC4 trails can be allocated in a VCGRoup on Giga bitEthernet card.

� Click [Close ] to close all the results windows.

5.2.3 - To deactivate a VCGroup

This procedure is used to deactivate a VCGRoup « activated » or « partially activated ».During deactivation, commands are sent in the two Nes of VCGroup to update the monitoring (to “no”) and to deallocate the trails from the VCGroup. The trails are not deactivated.


� In the search window, select VCGroups : the list of VCGroups is displayed.

� Select the VCGroup(s) to be activated then click right to bring up the pop-up menu.

� Click [De-Activate ] : you obtain the VCGroup deactivation results window (1) (2) (3).

Figure 5.20 : Window VCGRoup De-activation results

Notes : (1) a VCGroup which has just b een deactivated goes to the status « partially activated » when the trails associated are dealloca ted in the two Nes. The trails are always activated. If all the trails are deactivated, the VCGRoup goes to the status « reserved ».

(2) a VCGroup which has just been deactivated rema ins « activated » if one of

two Nes is inaccessible or in session locked.

Caution: On ADR10000, the deactivation of VCG must be done using the ADR10000 proxy.

VCGROUPS MANAGEMENT


� Double-clicking on line of VCGRoup or using [Details ] will bring up the De-activate VCGRoup window which shows the result for the trails deallocation and the result for the parameters deactivation.

Figure 5.21 : Window VCGroup de-activation results / Details

� Double-clicking on line « Trail allocation de-activation » or using [Details ] will bring up the following window.

Figure 5.22 : Window VCGRoup Trail allocation de-ac tivation results / Details

Note : (3) If one of two extremities Nes is inacces sible or in locked session, the deallocation of trails is not done (result of “ Ext remity Nes lock “).

� Double-clicking on line « Allocations de-activation » or using [Details ], then double-clicking on line «A-end trails allocation de-activation » or « Z-end trails allocation de-activation » will bring up the result of deallocation for each trail of VCGroup.

VCGROUPS MANAGEMENT


Figure 5.23 : Window VCGroup A-end Trails allocatio n de-activation results / Details

� Double-clicking on line « VCGroup de-activation parameters » or using [Details ] will bring up the result on monitoring update (to No).

Notes : (4) If the monitoring cannot be updated in one of two Nes, the parameters

become “reserved”, but the NE will be misaligned. (5) during the deactivation of VCGroup, the monito ring point of VCGroup is

updated to “No”.


5.2.4 - To delete a VCGroup

Caution : This operation is only possible provided the VCGRoup est dactivated in the «

reserved » or « partially activated» status.


� In the search window, select VCGroups : the list of VCGRoups is displayed.

� Select the VCGRoup(s) to be deleted then click right to bring up the pop-up menu.

� Click [Delete ] : after confirmation, the VCGRoup is deleted from the list: the trails allocated in the VCGroup are automatically deallocated from VCGroup.

Notes : The deletion of VCGroup is only possible if the VCGroup parameters are «

reserved » and if all the trails incorporated in th is VCGRoup have been deactivated for allocation (status of Allocation a ctivation = « reserved »).

After deletion of VCGRoup, the indication “concate nated” is updated for the trails previously allocated in the VCGroup.

VCGROUPS MANAGEMENT


5.2.5 - To dissociate a VCGroup

This procedure is used to delete, from the manager database, an « activated » or « partially activated » VCGroup while preserving the VCGroup and trails allocation in each NE.

� Display NML View by clicking View > NML View .

� In the search window, select VCGRoups : The list of VCGroups is displayed.

� Select the VCGroup to be dissociated then click right to bring up the pop-up menu.

� Click [Dissociate ] : after confirmation, the VCGroup is dissociated.

Note : The dissociation of VCGroup is only possible if the VCGroup parameters are

activated (status = « activated »). The status of a llocation activation of trails can be « reserved » or « partially activated » or « activated »).

After dissociation of VCGRoup, the indication “con catenated” is updated for the trails previously allocated in the VCGroup.

5.2.6 - To display/modify the properties of a VCGRo up

This procedure is used to visualize / modify the properties of a VCGroup.



� Select the VCGroup which you want to display, then click right to bring up the pop-up menu.

� Click [Properties ] (ou [Show Properties ]) : the VCGroup properties are displayed.

� Select one of tabs : Information, Group, Additional information, Occupation, Alarms, Status history.



VCGROUPS MANAGEMENT


Figure 5.24 : Window VCGroup / Properties / linear display

Notes : The linear display tab displays the source and destination NE of the VCGRoup link by a line.

Figure 5.25 : Window VCGroup / Properties / Informa tion

VCGROUPS MANAGEMENT


Notes : The Information tab displays the details of the VCGRoup. The name M1400 (serial no.) and the « Long name » can be modified. The type of VCG ports (EP-Line/LAN Support or EVP- Line/LAN Support) can

be modified.

Figure 5.26 : Window VCGroup / Properties / Additio nal information

Note : In the Additional Information tab, you can c ustomize the data : customer name, location and info.

Figure 5.27 : Window VCGroup / Properties / Group

VCGROUPS MANAGEMENT


Note : in the Group tab, you can read the state of VCGRoup parameters activation (« activated » or « reserved »), the global status of VCGRoup (« reserved », « activated » or « partially activated »), and visual ize the list of allocated trails with activation state and allocation activation sta te for each trail.

The menu [ Add trails to VCGroup ] is used to incorporate one or several trails in a VCGroup (see § 5.2.7 -).

You can select a trail and click right to bring up the pop-up menu. This menu allows to launch the following actions :

� Properties : to open the properties of trail

� Activate/Deactivate : to activate/deactivate the trail

� Protection deletion / Protection activation / Prote ction Deactivation : to activate/deactivate/delete the SNC protection (s).

� Add trails to VCGroup : to add new trails in the VCGroup (see § 5.2.7 -)

� Remove member from VCGroup : to remove a trail from the VCGroup (see § 5.2.8 -)

� Activate/Deactivate allocations : to activate/deactivate the trail allocation in the VCGroup (see § 5.2.9 - et 5.2.10 -)

Figure 5.28 : Window VCGroup / Properties / Alarms

Notes : In the Alarms tab, you can modify the value of monitoring (values = “All” or “None”). You can also modify the “Gravity Profile” of VCGroup (tick on “Manual” and select a value of Gravity Profile in t he proposed list.)

If the traffic is not “OK”, the list of associated alarms is displayed.

The value of the “Failure gravity” which is display ed is given by the “Gravity Profile” and the status of VCGRoup. This value corr esponds to the table of configuration defined in menu “Tools/Preferences/Fa ilure Gravity Configuration. (see § 12.2.9 -)

VCGROUPS MANAGEMENT


Figure 5.29 : Window VCGroup / Properties / Occupat ion

Note : In Occupation Tab, you can display the Ether net service which uses this VCGroup.

Figure 5.30 : Window VCGroup / Properties / Status history

Notes : In the Status history tab, you can display the status history of the VCGRoup since it was activated : if one of the extremities Nes is misaligned, the history is not always supplied.

VCGROUPS MANAGEMENT




5.2.7 - To add a trail in a VCGroup

This procedure is used to add a trail(several trails) in a VCGroup. The VCGroup can be « activated », « reserved » or « partially activated ».

� Display NML View by clicking View > NML View.

� In the search window, select VCGroups : the list of VCGRoups is displayed.

� Select the VCGroup to be modified then click right to bring up the pop-up menu.

� Click [Properties ] : the properties of VCGroup are displayed.

� Select the Group tab.


� Click [Add Trails to VCGroup ] : the Trail incorporation window is displayed with the list of all trails which can be added in the VCGroup.

Figure 5.31 : Window VCGroup / Properties / Group / Trail incorporation

Notes : When a trail is added to a VCGroup, the ind ication « concatenated » is

updated and cannot be modified. This indication can be displayed in the list of trails in NML View. It is also displayed in the pro perties of trail in Information tab.

46 VC12 trails or 2 VC3 trails maximum can be alloc ated in a VCGRoup on GFP card.

VCGROUPS MANAGEMENT


It is not possible to add VC12 trails and VC3 trail s in the same VCGRoup (refused by ADR155C).

Trails starting or ending on a VNE can be added to a VCGRoup if only ports GFP VCx and GFP VCG of the VCGRoup are created on t he same board of the VNE

� Select one or several trails and click [Add ] : a result window is displayed for all selected trails.

Figure 5.32 : Window VCGroup / Properties / Group / Trail incorporation result

� Click [Close ] : the list of added trails is displayed in Group tab of VCGroup.

Notes : A pop_up menu can be launched on the added trails with the possibility to activate/deactivate trails, to remove trails from V CGRoup, to activate/deactivate allocation of trails in the Vcg roup.

The global status of VCGroup can be modified after the addition of trails.

5.2.8 - To remove a trail from a VCGroup

This procedure is used to remove trail(s)s from a VCGroup. This action is only possible for trails with a state of allocation activation « reserved ».



� Select the VCGRoup to be removed then click right to bring up the pop-up menu.



� Select the trail (s) to remove from VCGroup then click right to bring up the pop-up menu.

� Click [Remove member from VCGroup ] : the result window is displayed with the list of trails which have been removed from VCGroup.

Figure 5.33 : Window VCGroup / Properties / Group / Remove member from VCGroup result

VCGROUPS MANAGEMENT


Notes : a trail can be removed from VCGroup if its state of allocation activation is « reserved ».

When a trail is removed from a VCGroup, the indica tion “concatenated” is updated.

� Click [Close ] : the list of trails is updated in Group tab of VCGroup.

Note : The global status of Vcgroup can be modified when trails are removed from VCGroup.

5.2.9 - To activate the allocation of a trail in a VCGroup

This procedure is used to activate the allocation of trail(s) in a VCGroup « activated » or « partially activated » (1). During the activation, commands are sent to allocate trail(s) in the VCGroup in the two network element crossed by the VCGroup.


� In the search window, select VCGRoups : the list of VCGRoups is displayed.




� Select the trail (s) then click right to bring up the pop-up menu.

Figure 5.34 : Window VCGroup / Activate Allocation

VCGROUPS MANAGEMENT


� Click [Activate Allocation ] : you obtain the following result window (1) (2).

Figure 5.35 : Window Trail activation allocation re sults

Notes : (1) The activation of trail allocation is only possible if the main path of trail is activated and VCGroup parameters are activated (sta te « activated »). (2) 46 VC12 trails or 2 VC3 trails maximum can be a llocated in a VCGroup on GFP card.

Caution: On ADR10000, the activation of trail allo cation for VCG must be done using the ADR10000 proxy.

� Double-click on result line or use [Details ] will bring up the details in the Activate allocations window.

Figure 5.36 : Window Trail Activate allocation resu lts / Details

� Double-click on line « Trail allocation activation » or use [Details ] then double-click on line « Allocations activation », then on line «A-end trails allocation activation » or « Z-end trails allocation activation » will bring up the result of allocation for each trail in each NE.

Figure 5.37 : Window A-end Trails allocation activa tion results / Details


VCGROUPS MANAGEMENT


Notes : if one of two extremities Nes is inaccessib le or in locked session, the allocation of trails is not done (result of « Extre mity Nes lock »).

If the allocation of trail is activated, the globa l status of VCGroup can be modified.

5.2.10 - To deactivate the allocation of a trail in a VCGRoup

This procedure is used to deactivate the allocation of trail(s) in a VCGroup « activated » or « partially activated ». During the deactivation of trail allocation, commands are sent to deallocate trail(s) in the VCGroup in the two network elements crossed by the VCGroup.


� In the search window, select VCGroup : the list of VCGroups is displayed.


� Click [Properties ] : The properties of VCGroup are displayed on the right of screen. This window of properties can be detached.


� Select the trail (s) then click right to bring up the pop-up menu.

Figure 5.38 : Window VCGRoup De-activate allocation

� Click [De-activate Allocation ] : the result window of deactivation is displayed (1) (2) .

VCGROUPS MANAGEMENT


Figure 5.39 : Window VCGroup Trail allocation de-ac tivation results / Details

Notes : (1) The deactivation of trail allocation is only possible if the allocation

activation is « activated » ou « partially activate d ».

Caution: On ADR10000, the activation of trail allo cation for VCG must be done using the ADR10000 proxy.

� Double-clicking on result line or use [Details ] will bring up the Trails allocations de-activation window.

Figure 5.40 : Window VCGroup Trail De-activate allo cation results / Details

� Double-clicking on line « Trail allocation de-activation » or use [Details] then double-click on line « Allocations de-activation » then on line «A-end trails allocation de-activation » or « Z-end trails allocation de-activation » will bring up the result of allocation for each trail in two Nes.

Figure 5.41 : Window VCGroup A-end allocation deact ivation results / Details


Notes : If one of two extremities Nes is inaccessib le or in locked session, the deallocation of trails is not done (result of « Ex tremity Nes lock »).

If the trail is deallocated, the global status of VCGroup can be modified.

ETHERNET POINT-TO-POINT SERVICES MANAGEMENT


6. ETHERNET POINT-TO-POINT SERVICES MANAGEMENT

6.1 - INTRODUCTION

IONOS-NMS enables Ethernet Point-To-Point Services management. An Ethernet service connects two ports of type Ethernet 10-100Mb and uses some VCGroups and/or Ethernet Links to carry Ethernet traffic.

This function only concerns the GFP cards on ADR155C – version ≥ P4 and on ADR2500 EXTRA ≥ P2.1, the 4E/FE card on ADR155CPE and ADR155C,the card 4E/FE + 1GE ≥P5.5, the UGSD and UFTQA cards on ADR155E, the UGSD card on ADR10000HN, EISMB_840, EISMB_804, DIOM_40 cards on ADR10000, and MCSM card on ADR10000 ≥ 8.1, GFP150-622 and GFP2500-622 on ADR622 ≥ P1.1 or Ethernet ports on VNE.

Multiservice per customer port concern the GFP2500 card on ADR2500 EXTRA version ≥ P3.0.1, GFP2500-622 card on ADR622 and EISMB and DIOM cards on ADR10000, and MCSM card on ADR10000 ≥ 8.1, .

The Ethernet Services are not managed on the GigabitEthernet card of ADR2500C and ADR2500 EXTRA.


6.2.1 - To create an Ethernet Point-To-Point Servic e

This procedure is used to define an Ethernet Point-To-Point Service.



� In the window, select the Traffic Carrier icon then click [OK] : the Create Traffic Carrier window is displayed.



Figure 6.2 : Window Create Ethernet Point-To-Point Service (1)

� Select the type of traffic carrier : Ethernet for Domain, Services for Family and Ethernet point-to-point service for the type and give the number of Ethernet services to be created (1 by default).

� Click [Next ] to display the following screen : all the list of interfaces is displayed (1).


� In the Source area, select a source Ethernet interface (2).

� In the Destination area, select a destination Ethernet interface (2).

� In the name part of the window, enter a serial number for the new Ethernet service and if necessary a “Long name”. By clicking [Default Value ], you will obtain a default number for serial number.

� Enter the priority. Click on button [allow all classes ] to have access all the values.

� For GFP2500 board (on ADR25000 EXTRA) or EISMB, MCSM, and DIOM boards (on ADR10000), select a classification based on port, C-VLAN (3), User Predefined (4) or Default.



� Select a profile defined by default (3) for quality of service parameters or select the value “Free” and modify the values of parameters Policing type, CIR, PIR, CBS, EBS. Validate each modification with key [Return ]. Note: TrTCM policing type in QoS parameter is not s upported with EISMB and DIOM

cards on ADR10000.


Notes (1): (1) Incompatible interfaces, already reserved or not valid (grayed in) are not accessible.

(2) The source and destination interfaces must be p orts of Ethernet 10-100Mb

or 1 Gb type : the Ethernet services can be created on GFP cards (ADR155C, ADR2500 EXTRA and ADR622), 4E/FE cards (A DR155CPE and ADR155C P5.2), 4E/FE + 1GE cards ≥ P5.5 cards (ADR155c), UGSD cards (ADR155E and ADR10000HN), UFTQA (ADR155E), EISMB, D IOM and MCSM (ADR10000). It is also possible to use a VNE w ith port ETH10-100Mb and 1 Gb .

(3) About the port numbering and assignment of MCSM card of ADR1000, see

Figure 5.1 : MCSM port numbering and assignment (4) Classification based on C-VLAN:

Figure 6.4 : Window C-VLAN classificat ion (3) (5) This range string can contain a max of 8 ranges , should be an integer

included from 2 to 4094, separate by comma. Each it em of the C-VLAN range should be in ascending order and not overlap each other. The C-VLAN range should not be blank.

(6) To finish the “User Predefined” configuration i n the equipment use the

HTTP browser to configure the global settings of sw itch functions. (7) The QOS profiles by default are given in menu “ Tools/Preference/QOS

Profile (see § 12.2.10 -) (8) Only priorities level 0, 2, 4 and 6 are support ed on ADR10000 with EISMB

and DIOM cards.

(9) Also, the classification based on “Port” is not supported on ADR10000 (use “Default”).

(10) The capability to manage the probes of continu ity check OAM-CC for

Ethernet services is not implemented on ADR10000: t he global status displayed in the Alarms tab of the Ethernet service can not be calculated

Caution: Ethernet service with MSTP Protection is n ot supported on ADR10000.



Notes (2): About multiservice per customer po rt use, see below the compatibilities table

PORT DEFAULT C-VLAN User Predefined

PORT No No No No

DEFAULT No No Yes Yes

C-VLAN No Yes Yes according to C-

VLAN compatibility

No

User Predefined No Yes No Yes according to

User Predefined

compatibility






� In the Monitoring part(4), if necessary modify the value of monitoring which involves the update in the equipment : All , Extremities or None .

� In the Gravity Profiles part (4), if necessary modify the mode by ticking or not the case “manual ” and if the case “manual” is ticked, modify the value of Gravity Profile with the proposed list.


Note: (10) the value displayed by default for moni toring, the Gravity Profiles and the parameters of performance are those defined in the preferences of Ethernet Link (menu Tools/Preferences/Traffic Carrier/Ethern et Service ).



In case of Monitoring none and Extremites, the pro bes OAM-CC for continuity check will not be activated.


� Select a link connection (5) : the selection is confirmed by a graphic representation of the ethernet service in the Linear display part.

� If you want to modify the Nes source and destination and modify the link connection, click [Previous ] to return to the previous screen.

� Repeat the operation for each equipment on the route.

� Click [Next ] to display the next scren.

Note: (5) the VCGroups and the Ethernet links alre ady used are not available (in grayed) (5) the VCGroups with a throughput not compatible w ith QOS parameters chosen for created Ethernet service are not availab le (in grayed).

Caution: On GFP2500 board, IONOS-NMS allows the VC G creation with more than 100 Mb/s for the VCG other than VCG#1, #7, #13 and #19 whereas the equipment does not support it.




� In the part VMAN selection, enter a VMAN no (from 2 to 4031, from 4032 to 4094 if MSTP is selected), for the new ethernet service. Click [Auto VMAN ] to obtain a default no.

Caution : MSTP is not available for ADR10000

� Click [Finish ] to validate the new Ethernet service : the result window is displayed.



� If necessary, activate the Ethernet service (see § 6.2.2 -).

Notes : When creating the Ethernet service, no upda te is done in the Nes.



6.2.2 - To Activate an Ethernet Point-To-Point Serv ice

This procedure is used to activate an “reserved” or “partially activated” Ethernet Point-To-Point Service. During activation, commands are sent to update the monitoring and to create bridging points and continuity-check probes in all the network elements crossed by the Ethernet service.


� In the search window, select Ethernet P2P services : the list of Ethernet services is displayed.

� Select the Ethernet service(s) to be activated then click right to bring up the pop-up menu.

� Click [Activate ] and confirm the activation : the following activation window is displayed (1) (2) (3)

Figure 6.9 : Window Ethernet Point-To-Point service activation results

Notes : (1) an Ethernet service which has just been created goes to rhe “reserved” status. (2) an Ethernet service which has just been activat ed goes to the “ activated” status when all the bridging points/continuity-chec k probes have not been created in all the network elements crossed.

(3) an Ethernet service which has just been deacti vated goes to the “Partially activated” if one of Nes is inaccessible or in sess ion locked.

� Double-clicking on the result line or using [Details ] will bring up a new window Activate Ethernet service which shows the detailled results for the activation of different ports (external and internal ports).

Figure 6.10 : Window Ethernet Point-To-Point servic e activation results / Details (1)

� Double-clicking on line « Activate all ethernet internal point-to-points » or using [Details ], then double-clicking on each line (if multiple activation) « Activate internal point-to-point » or using [Details ], will bring up the results on creation of bridging points on internal ports of extremities Nes and middle Nes.

� Double-clicking on line « Activate all services ports » or using [Details ], then double-clicking on each line (if multiple activation) « Activate services port » or using [Details ], will bring up the results on creation of bridging points and monitoring on external ports of extremities Nes.



� Double-clicking line « Update continuity-check probes » or using [Details ] will bring up the result on the creation of continuity-check probes (source and sink) on the two extremities Nes.

Note : If the update of monitoring cannot be done in one of two Nes, the service

Ethernet will be “activated”, but the NE will be mi saligned. The continuity-check frame is sent every 10 second s


6.2.3 - To Deactivate an Ethernet Point-To-Point Se rvice

This procedure is used to deactivate an “activated” or “partially activated” Ethernet Point-To-Point Service. During deactivation, commands are sent to update the monitoring and to delete bridging points and continuity-check probes in all the network elements crossed by the Ethernet service.




� Click [De-activate ] and confirm the deactivation : the following deactivation window is displayed (1) (2) (3) .

Figure 6.11 : Window Ethernet Point-To-Point servic e deactivation results

Notes : (1) an Ethernet service which has just been deactivated goes to the “reserved” status when all the bridging points and continuity-check probes associated to the ethernet service have been delete d in each concerned equipment. (2) an Ethernet service which has just been deactiv ated goes to the “partially activated” status when all the bridging points/cont inuity-check probes have not been deleted in all the network elements crosse d.

(2) an Ethernet service which has just been deacti vated goes to the “Partially activated” if one of Nes is inaccessible or in sess ion locked.

(3) after an ethernet service deactivation, the mo nitoring of ports Erhernet is modified to “none”.

� Double-clicking on the result line or using [Details ] will bring up a new window De-Activate Ethernet service which shows the detailled results for the deactivation of different ports (internal point-to-point ports and service ports).



Figure 6.12 : Window Ethernet Point-To-Point servic e deactivation results / Details (1)

� Double-clicking on line « De-activate all ethernet internal point-to-points » or using [Details ], then double-clicking on each line (if multiple deactivation) «De-activate internal point-to-point » or using [Details ], will bring up the results on deletion of bridging points on internal ports of extremities Nes and middle Nes.

� Double-clicking on line « De-activate all services ports » or using [Details ], then double-clicking on each line (if multiple deactivation) « De-activate services port » or using [Details ], will bring up the results on deletion of bridging points and demonitoring on external ports of extremities Nes.

� Double-clicking line « Update continuity-check probes » or using [Details ] will bring up the result on the deletion of continuity-check probes (source and sink) on the two extremities Nes.

Note : If the update of monitoring cannot be done in one of Nes, the Ethernet service

will be “reserved”.


6.2.4 - To delete an Ethernet Point-To-Point Servic e

Caution : This operation is only possible provided the Ethernet service is deactivated in

the « reserved » status.


� In the search window, select Ethernet P2P services : the list of Ethernet Point-To-Point services is displayed.

� Select the Ethernet service(s) to be deleted then click right to bring up the pop-up menu.

� Click [Delete ] : after confirmation, the Ethernet service is deleted from the list.

6.2.5 - To dissociate an Ethernet Point-To-Point Se rvice

Caution : This operation is only possible provided the Ethernet service is activated in the « activated” or “partially activated » status.

This procedure is used to delete, from the manager database, an « activated » or « partially activated » Ethernet service while preserving the bridging points in each NE.


� In the search window, select Ethernet P2P services : The list of Ethernet services is displayed.

� Select the Ethernet service to be dissociated then click right to bring up the pop-up menu.

� Click [Dissociate ] : after confirmation, the Ethernet service is dissociated.



6.2.6 - To display/modify the properties of an Ethe rnet Point-To-Point Service

This procedure is used to visualize / modify the properties of an Ethernet service.



� Select the Ethernet service which you want to display, then click right to bring up the pop-up menu.

� Click [Properties ] (ou [Show Properties] ) : the Ethernet service properties are displayed.

� Select one of tabs : Linear Display, Information, Route, Additional information, Alarms, Status history.



Figure 6.13 : Window Ethernet Point-To-Point Servic e / Properties / Linear display (1)

� In tab Linear Display, Click [Activation ] in “Animation” area to visualize the state of activation of the ethernet service.

Color of Link :

- always green

Color of name of NE icons :

- in green if the bridging points are activated on it

- in orange if the bridging points are not totally activated on it

� In tab Linear Display , Click [Alarms ] in “Animation” area to visualize the state of alarm of the ethernet service according to the direction (one-way or bidirectional).



Figure 6.14 : Window Ethernet Point-To-Point Servic e / Properties / Linear display (2)

Color of Link :

- For a given direction

� In green if not of alarm or alarm of maximum severity = warning on the output NE

� In gray if “output” NE is a VNE

� In blue if alarm of inaccessibility on output NE

� In red if alarm of maximum severity = major on output NE

� In yellow alarm of maximum severity = minor on output NE

- For the bidirectional mode :

� The synthesis of the colors of the two directions according to the command gray, green, yellow, red and blue.

Color of NE icons :

- The color of NE for a given direction is :


� without color if NE is a VNE



� In yellow alarm of maximum severity = minor

- The color of NE for the bidirectional mode is :

� Colored according to the synthesis of the colors of the two directions according to the command without color, green, yellow, red and blue.

Notes : all alarms acknowledged or not are taken in to account.

The direction of traffic is not taken into account.



Figure 6.15 : Window Ethernet Point-To-Point Servic e / Properties / Information

Notes : The Information tab displays the details of the Ethernet service.

The name M1400 (serial no.) and the « Long name » can be modified.

The N° VMAN can be modified if the ethernet servic e is “reserved”.

The priority can be modified. Click on button [Allo w all classes] to have access all the values.

The QOS parameters can be modified. Another profil by default can be selected or the profil “free” is used to modify the parameters. Each modification of parameter must be validated with ke y “Return”. Les valeurs par défaut des progiles sont celles définies dans l es Préférences (menu Tools/Preferences/QOS Profile)

The type of ethernet service can be modified in “et hernet multipoint service”. The service is converted in ethernet multipoint ser vice. It has two ethernet ports and one internal point-to-point.

Caution :GFP2500 board (ADR2500 EXTRA): To update t he QOS parameters it is necessary to audit the ADR2500EXTRA and to reactiva te the bridging points (NMS to NE) for Ethernet service. (see § 2.5.6 -



Figure 6.16 : Window Ethernet Point-To-Point Servic e / Properties / Additional information


Figure 6.17 : Window Ethernet Point-To-Point Servic e / Properties / Route/ Link connection

Note : In the tab Route/Link connection, you can re ad the state of link connections (VCGroups or Ethernet Links) of Ethernet service ( «reserved », « activated » or « partially activated »).



Figure 6.18 : Window Ethernet Point-To-Point Servic e / Properties / Route/ CrossConnection

Note : In the tab Route/Crossconnection, you can re ad the state of connections or “bridging points” of Ethernet service ( «reserved » , « activated » or « partially activated »).

Figure 6.19 : Window Ethernet Point-To-Point Servic e / Properties / Alarms



Notes : In the Alarms tab, you can modify the value of monitoring (values = “All” , “Extremities” or “None”). You can also modify the “ Gravity Profile” of Ethernet service (tick on “Manual” and select a val ue of Gravity Profile in the proposed list).

If the traffic is not correct, all the alarms assoc iated with ethernet service are displayed.

The value of the “Failure gravity” which is display ed is given by the “Gravity Profile” and the status of ethernet service. This v alue corresponds to the table of configuration defined in menu “Tools/Pref erences/Failure Gravity Configuration.

Figure 6.20 : Window Ethernet Point-To-Point Servic e / Properties / Status history





ETHERNET MULTIPOINT SERVICES MANAGEMENT


7. ETHERNET MULTIPOINT SERVICES MANAGEMENT

7.1 - INTRODUCTION

IONOS-NMS enables Ethernet MultiPoint Services management. An Ethernet MultiPoint Service connects several ports of type Ethernet10-100Mb and uses some VCGroups and/or Ethernet Links to carry Ethernet traffic.

This function only concerns the GFP cards on ADR155C – version ≥ P4 and on l’ADR2500 EXTRA ≥ P2.1 (mutualization) or Ethernet ports on VNE, the EISMB_840, EISMB_804, DIOM_40 boards on ADR10000 and MCSM board on ADR10000 ≥ 8.1, and GFP cards on ADR622.

Multiservice per customer port concern the GFP2500 card on ADR2500 EXTRA version ≥ P3.0.1, EISMB, MSCM and DIOM cards on ADR10000, and MCSM board on ADR10000 ≥ 8.1 and GFP2500-622 card on ADR622.

The Ethernet MultiPoint Services are not managed on the GigabitEthernet card of ADR2500C and ADR2500 EXTRA.


7.2.1 - To create an Ethernet MultiPoint Service

This procedure is used to define an Ethernet MultiPoint Service.



� In the window, select the Traffic Carrie r icon then click [OK] : the Create Traffic Carrier window is displayed.



Figure 7.2 : Window Create Ethernet MultiPoint Serv ice (1)

� Select the type of traffic carrier : Ethernet for Domain, Services for Family and Ethernet multipoint service for the type and give the number of Ethernet serivice to be created (1 by default).

� Click [Next ] to display the following scren.


� Enter the name “Normalized name ” and if necessary a Long name.

� Enter a N° VMAN or click on “undefined”.

� If necessary, modify the value of priority (values available 1, 2 or EP-Line/Lan or click on “allow all classes” to select other values) (1).



� If necessary click “Use MSTP Protection ” (2).


Notes : (1) the value displayed by default for prio rity is the value defined in the preferences of Ethernet Service (menu Tools/Prefere nces/Traffic Carrier/Ethernet Service)

(2) If MSTP is selected, the value of VMAN must be between 4032 et 4094. (3) Only priorities level 0, 2, 4 and 6 are supported o n ADR10000 with EISMB

and DIOM cards.

(4) Also, the classification based on “Port” is not sup ported on ADR10000 (use “Default”).

(5) The capability to manage the probes of continuity c heck OAM-CC for

Ethernet services is not implemented on ADR10000: t he global status displayed in the Alarms tab of the Ethernet service can not be calculated

Caution: Ethernet service with MSTP Protection is n ot supported on ADR10000.


� In the Monitoring part(3), if necessary modify the value of monitoring which involves the update in the equipment : All , Extremities or None .







� Click [Finish ] to validate the new Ethernet service : the result window is displayed.

Note: (3) the value displayed by default for monit oring is these defined in the preferences of Ethernet Service ( menu Tools/Prefer ences/Traffic Carrier/Ethernet Service). In case of Monitoring none and Extremites, the prob es OAM-CC for continuity check will not be activated.


� Click [Close ] to close the result window. The next window is displayed with the possibility to add Ethernet ports (extremity ports) and internal point-to-point services.


� Add if necessary extremity ethernet ports and internal services (see § 7.2.2 - “To add an ethernet port in an Ethernet Multipoint Service and § 7.2.8 - “To add an internal point-to-point service to an Ethernet Multipoint Service”).



� Clic[Finish ] to validate the creation of service.

� Activate, if necessary”, the Ethernet Multipoint Service , if the VMAN, extremity ports and internal services have been provided.

Note : When creating the Ethernet service, no updat e is done in the Nes.

7.2.2 - To add an ethernet port in an Ethernet Mult ipoint Service

This procedure is used to add an Ethernet port in an Ethernet Multipoint Service.


� In the search window, select Ethernet Services : the list of Ethernet MultiPoint Services is displayed.


Figure 7.7 : Window Ethernet MultiPoint Service / A dd Port (1)

� Click [Show Properties ] or [Properties ] : the Ethernet service propeties are displayed.

� Select the Composition tab.




� Click [Add ] in the part “Extremity Ports” : the window Add extremity port is displayed with the list of all interfaces (1).


� Select an Ethernet interface (2).



� For GFP2500 board (on ADR25000 EXTRA and ADR622) or EISMB, DIOM and MSCM boards (on ADR10000), select a classification based on port, C-VLAN (3), User Predefined (4) or Default

� Select a profile defined by default (1) for quality of service parameters or select the value “Free” and modify the values of parameters Policing type, CIR, PIR, CBS, EBS. Validate each modification with key [Return ]. Note: TrTCM policing type in QoS parameter is not s upported with EISMB and DIOM

cards on ADR10000.

� If necessary give a Long name for the selected ethernet port.

Notes: (1) Incompatible interfaces, already reserved or not va lid (grayed in) are not accessible.

(2)The source and destination interfaces must be po rts of Ethernet 10-100Mb

or 1 Gb type : the Ethernet services can be created on GFP cards (ADR155C , ADR2500 EXTRA and ADR622), 4E/FE cards (ADR155CPE a nd ADR155C P5.2), 4E/FE + 1GE ≥ P5.5 (ADR155C), UGSD cards (ADR155E and ADR10000HN ), UFTQA (ADR155E), EISMB, DIOM and MSCM (ADR10000). I t is also possible to use a VNE with port ETH10-100Mb and 1 Gb.

(3) About the port numbering and assignment of MCSM card of ADR1000, see Figure 5.1 : MCSM port numbering and assignment

(4) Only priorities level 0, 2, 4 and 6 are support ed on ADR10000 with EISMB and DIOM cards.

(5)Also, the classification based on “Port” is not supported on ADR10000 (use “Default”).

(6) Classification based on C-VLAN:

Figure 7.10 : Window C-VLAN classifica tion (3) This range string can contain a max of 8 ranges, sh ould be an integer included from 2 to 4094, separate by comma. Each it em of the C-VLAN range should be in ascending order and not overlap each o ther. The C-VLAN range should not be blank. (7) To finish the “User Predefined” configuration i n the equipment use the HTTP browser to configure the global settings of sw itch functions. (8) The QOS profiles by default are given in menu “ Tools/Preference/QOS Profile (see § 12.2.10 -)

Notes (2): About multiservice per customer port use , see below the compatibilities table

PORT DEFAULT C-VLAN User Predefined

PORT No No No No

DEFAULT No No Yes Yes

C-VLAN No Yes Yes according to C-

VLAN compatibility

No

User Predefined No Yes No Yes according to

User Predefined

compatibility



(9)The ethernet interfaces must be ports of Etherne t 10-100Mb on GFP cards (ADR155C, ADR2500 EXTRA and ADR622), EISMB, DIOM an d MSCM on ADR10000. It is also possible to use a VNE with por t ETH10-100Mb.

(10)The QOS profiles by default are given in menu “ Tools/Preference/QOS Profile

� Click [Add ] to validate the creation : the result window is displayed (4).

Figure 7.11 : Window Ethernet MultiPoint Service / Add Port (4)

Note : (11) If the ethernet multipoint service was activated, it goes to the “partially

activated” status when the ethernet port is added.

� If necessary, activate the ethernet port (see § 7.2.3 - “To activate an ethernet port”).

Notes : When creating the Ethernet port, no update is done in the NEs.

A “warning” message is displayed if each added eth ernet port is not connected with another ethernet port via an interna l P2P service.

7.2.3 - To activate an ethernet port in an Ethernet MultiPoint Service

This procedure is used to activate a “reserved” ethernet port which has been added in an ethernet multipoint service. During activation, commands are sent to update the monitoring of ethernet port and to create the bridging point of ethernet port and all the continuity-check probes in the all associated Nes .



� Select the Ethernet service(s) to be modified then click right to bring up the pop-up menu.



� Select the ethernet port to be activated, then click right to bring up the opo-up menu.

� Click [Activate ] : the following activation window is displayed (1) (2).



Figure 7.12 : Window Ethernet port activation resul ts

Notes : (1) an Ethernet port which has just been cr eated is in a “reserved” state.

(2) an Ethernet port which has just been activated goes to the “activated” status when the the bridging point is created in th e Nean all the continuity-checl probes associated with the ethernet port.

� Double-clicking on the result line or using [Details ] will bring up a new window Activate Ethernet service port which shows the detailled results for the activation of port.

Figure 7.13 : Window Ethernet port activation resul ts / Details

� Double-clicking on line « Activate ethernet service por t » or using [Details ], then double-clicking on each line (if multiple activation) « Activate bridging point » and « Monitor termination point » or using [Details ], will bring up the results on creation of bridging point and the update of monitoring.

� Double-clicking on line « Update ethernet service » or using [Details ], will bring up the results on creation of continuity-check probes associated with the ethernet port (in all the Nes of ethernet ports).

Note : If the update of monitoring cannot be done in NE, the Ethernet port will be

“activated”, but the NE will be misaligned.


7.2.4 - To deactivate an ethernet port in an Ethern et MultiPoint Service

This procedure is used to deactivate an “activated” ethernet port of an ethernet multipoint service. During deactivation, commands are sent to update the monitoring of ethernet port and to delete the bridging point and the associated continuity-check probes in all Nes.








� Select the ethernet port to be deactivated, then click right to bring up the pop-up menu.

� Click [Deactivate ] : the following activation window is displayed (1) (2).



Figure 7.14 : Window Ethernet port deactivation res ults

Notes : (1) an Ethernet port which has just been de activated goes to the “reserved” status when the the bridging point and continuity-c heck probes are deleted in all the NE.

� Double-clicking on the result line or using [Details ] will bring up a new window De-activate Ethernet service port which shows the detailled results for the deactivation of port.

Figure 7.15 : Window Ethernet port activation resul ts / Details

� Double-clicking on line « De-activate ethernet service por t » or using [Details ], then double-clicking on each line (if multiple activation) « De-activate bridging point » and « Demonitor termination point » or using [Details ], will bring up the results on deletion of bridging point and the update of monitoring.

Note : If the update of monitoring cannot be done in NE, the Ethernet port will be

“reserved”.

� Double-clicking on line « Update ethernet service » or using [Details ], will bring up the results on deletion of continuity-check probes associated with the ethernet port (in all the Nes of ethernet ports).




7.2.5 - To delete an ethernet port in an Ethernet M ultiPoint Service

Caution : This operation is only possible provided the Ethernet port is deactivated in







� Select the ethernet port to be deleted, then click right to bring up the pop-up menu.

� Click [Delete ] : after confirmation, the ethernet port is deleted from the list.

7.2.6 - To dissociate an ethernet port in an Ethern et MultiPoint Service

Caution : This operation is only possible provided the Ethernet port is activated in the «

activated » status.






� Select the ethernet port to be dissociated, then click right to bring up the pop-up menu.

� Click [Dissociate ] : after confirmation, the ethernet port is deleted from the list.

7.2.7 - To display/modify the properties of an ethe rnet port in an Ethernet MultiPoint Service

This procedure is used to display/modify the properties of an Ethernet port in an Ethernet MultiPoint Service.






� Cllick [Show Properties ] or [Properties ] : the Ethernet service properties are displayed.


� Select the ethernet port to be visualized/modified, then click right to bring up the pop-up menu.

� Click [Properties ] : the Ethernet port properties are displayed.

� Select one of tabs : Information or Alarms



Figure 7.16 : Window Ethernet Port / Properties / I nformation

Notes : The Information tab displays the details of the Ethernet port.

The Long name of ethernet port can be modified.

The QOS parameters can be modified. Another profil by default can be selected or the profil “free” is used to modify the parameters. Each modification of parameter must be validated with ke y “Return”. The profiles by default are defined in the Preferences (menu Too ls/Preferences/QOS profiles.

Caution :GFP2500 board (ADR2500 EXTRA): To update t he QOS parameters it is necessary to audit the ADR2500EXTRA and to reactiva te the bridging points (NMS to NE) for Ethernet service. (see § 2.5.6 -



Figure 7.17 : Window Ethernet Port / Properties / A larms

Note : In Alarms tab, you cannot modify the value o f monitoring. The “Global Status” is not calculated. All the alarms of port are displ ayed.

7.2.8 - To add an internal Point-To-Point in an Eth ernet Multipoint Service

This procedure is used to add an internal point-to-point in an Ethernet MultiPoint Service.






Figure 7.18 : Window Ethernet MultiPoint Service / Add Internal P2P (1)




� Click [Add ] in part “internal point-to-points” : the window Create traffic carrier is displayed with the list of all interfaces (1).




� In the Source area, select a GFP source interface (2).

� In the Destination area, select a GFP destination interface (2).

� In the name part of the window, enter a serial number. By clicking [Default ], you will obtain a default number.

� If necessary, enter a Long name.

� In the Specific parameters part of the window, enter if necessary a “weight”(4) (used only for MSTP) and give the QOS parameters : select a profile defined by default (3) for quality of service parameters or select the value “Free” and modify the values of parameters Policing type, CIR, PIR, CBS, EBS. Validate each modification with key [Return ]. Note: TrTCM policing type in QoS parameter is not s upported with EISMB and DIOM

cards on ADR10000.


Notes: (1)Incompatible interfaces, already reserved or not valid (grayed in) are not accessible.

(2)The interfaces must be GFP cards (ADR155C, ADR25 00 EXTRA, and ADR622), EISMB, DIOM and MSCM on ADR10000. It is al so possible to use a VNE with GFP card.

(3)The QOS profiles by default are given in menu “T ools/Preference/QOS Profile (see § 12.2.10 -) (4) If MSTP is used, a weight is associated to each internal P2P service. This This weight is used to calculate the NE “root”. Put a weight =1 for the main route and a weight superior to 1 for protections ro utes.



(5) MSTP is not supported on ADR10000. Table of correspondance : Weight MSTI Port Path Cost MSTI Bridge Priority 1 20 0 2 400 4096 3 8000 8192 4 160000 12288 5 3200000 16384 6 64000000 20480


� Check the M1400 name and the long name are correct





� Select a connection link (5) : the selection is confirmed by a graphic representation of internal point-to-point in linear display part.

� If you want to modify the interfaces (source and sestination) or choose another link connection, click [Previous ] to return to the previous screen.

� Repeat the operations for each equipment on the route.

Notes : (5) the VCGroups and the Ethernet links alr eady used are not available (in grayed)

(6) the VCGroups with a throughput not compatible w ith QOS parameters chosen for internal point-to-point are not availabl e (in grayed).

� Once the destination is reached, click [Next ] to display the following screen.




� Click [Finish ] to validate the new internal point-to-point : the result window is displayed (6) (7).


Notes : (7) If the ethernet service was “activated” , it goes to the status “partially

activated” when the internal point-to-point is adde d. - The N° VMAN of ethernet service must be available w ith the internal point-to-point.

� If necessary, activate the internal point-to-point (see § 7.2.9 - “To activate an internal point-to-point”).

Note : When creating the internal point-to-point, n o update is done in the Nes.

A “warning” message is displayed if each ethernet port is not connected with another ethernet port via an internal P2P service.

A “warning” message is displayed if a loop is dete cted. In this case, use MSTP.



7.2.9 - To activate an internal point-to-point in a n Ethernet Multipoint Service

This procedure is used to activate a “reserved” or “partially activated” internal point-to-point added in an ethernet multipoint service. During activation, commands are sent to update the bridging points in all NE crossed by the internal point-to-point (extremity Nes and intermediate Nes).


� In the search window, select Ethernet Service s : the list of Ethernet MultiPoint Services is displayed.




� Select the internal point-to-point to be activated, then click right to bring up the pop-up menu.

� Click [Activate ] : the following activation window is displayed (1) (2).

Figure 7.25 : Window Internal point-to-point activa tion results

Notes : (1) an internal point-to-point which has ju st been created is in a “reserved”

status. (2) an internal point-to-point which has just been activated goes to the “activated” status when all the bridging points are created in all the Nes. (3) an internal point-to-point which has just been activated goes to the « partially activated » status when the “bridging poi nt” are not all updated. (NE in time-out or in session locked for example).

� Double-clicking on the result line or using [Details] will bring up a new window Activate Ethernet internal point-to-point which shows the detailled results for the activation of internal point-to-point.

Figure 7.26 : Window Internal point-to-point activa tion results / Details

� Double-clicking on each ligne « Activate ethernet bridging point » or using [Details ], will bring up the results on update of bridging points.

� Click [Close ] to close the result windows.



7.2.10 - To deactivate an internal point-to-point d ’un service ethernet multipoint

This procedure is used to deactivate an “activated or “partially activated” internal point-to-point added in an ethernet multipoint service. During deactivation, commands are sent to update the bridging points in all NE crossed by the internal point-to-point (extremity Nes and intermediate Nes).






� Select the internal point-to-point to be deactivated, then click right to bring up the pop-up menu.

� Click [Deactivate ] : the following activation window is displayed (1) (2).

Figure 7.27 : Window Internal point-to-point deacti vation results

Notes : (1) an internal point-to-point which has ju st been deactivated goes to the

“reserved” status when all the bridging points are deleted in all the Nes.

(2) an internal point-to-point which has just been deactivated goes to the « partially activated » status when the “bridging poi nt” are not all updated. (NE in time-out or in session locked for example).

� Double-clicking on the result line or using [Details ] will bring up a new window De-activate Ethernet internal point-to-point which shows the detailled results for the activation of internal point-to-point.

Figure 7.28 : Window Internal point-to-point deacti vation results / Details



� Double-clicking on each ligne « De-activate ethernet bridging point » or using [Details ], will bring up the results on update of bridging points.

� Click [Close ] to close the result windows.

7.2.11 - To delete an internal point-to-point in an Ethernet MultiPoint Service

Caution : This operation is only possible provided the internal point-to-point is

deactivated in the « reserved » status.






� Select the internal point-to-point to be deleted, then click right to bring up the pop-up menu.

� Click [Delete ] : after confirmation, the internal point-to-point is deleted from the list.

7.2.12 - To dissociate an internal point-to-point i n an Ethernet MultiPoint Service

Caution : This operation is only possible provided the internal point-to-point is in the «

activated » or “partially activated” status.






� Select the internal point-to-point to be dissociated, then click right to bring up the pop-up menu.

� Click [Dissociate ] : after confirmation, the internal point-to-point is deleted from the list.



7.2.13 - To visualize / modify the properties of an internal point-to-point in an Ethernet MultiPoint

This procedure is used to visualize/modify the properties of an internal point-to-point in an Ethernet MultiPoint Service.






� Select the internal point-to-point to be deleted, then click right to bring up the pop-up menu.

� Click [Properties ] : the internal point-to-point properties are displayed.

� Select one of tabs : Linear Display, Information, Route, Alarms.

� Cllick [Refresh ]to update the data or reset the default values.

� Click [Apply ] to apply the modifications.pour appliquer les modifications.

Figure 7.29 : Window Internal point-to-point / Prop erties / Linear display (1)

� In tab Linear Display , Click [Activation ] in “Animation” area to visualize the state of activation of the internal point-to-point.



Color of Link :

- always green


- In green if the bridging points are activated on it

- In orange if the bridging points are not totally activated on it

� In tab Linear Display , Click [Alarms ] in “Animation” to viisualize the state of activation of the internal point-to-point.

Figure 7.30 : Window Internal point-to-point / Prop erties / Linear display (2)

Color of Link :

- For a given direction


� In gray if “output” NE is a VNE





� The synthesis of the colors of the two directions according to the command gray, green, yellow, red and blue.



Color of NE icons :








� Colored according to the synthesis of the colors of the two directions according to the command without color, green, yellow, red and blue.



Figure 7.31 : Window Internal point-to-point / Prop erties / Information



The “Weight” can be modified (used only with MSTP) .

The QOS parameters can be modified. Another profil by default can be selected or the profil “free” is used to modify the parameters. Each modification of parameter must be validated with ke y “Return”. The profiles by default are defined in the Preferences (menu Too ls/Preferences/QOS profiles).



Figure 7.32 : Window Internal point-to-point / Prop erties / Route/ Link connection

Note : in the tab Route/Link connection, you can re ad the state of link connections (VCGroups or Ethernet Links) of internal point-to-p oint ( «reserved », « activated » or « partially activated »).

Figure 7.33 : Window Internal point-to-point / Prop erties / Route/ CrossConnection

Note : in the tab Route/Crossconnection, you can re ad the state of connections or

“bridging points” of internal point-to-point ( «res erved », « activated » or « partially activated »).



Figure 7.34 : Window Internal point-to-point / Prop erties / Alarms

Note : Dans l’onglet Alarms, the value of monitorin g cannot be modified. The “Global Status” is not calculated. All the alarms are displayed.

7.2.14 - To activate an Ethernet MultiPoint Servic e

This procedure is used to activate a “reserved” or “partially activated” Ethernet MultiPoint Service (1). All the Ethernet ports “reserved” of Ethernet MultiPoint Service are activated. All the Internal Point-To-Point “reserved” or “partially activated” of Ethernet MultiPoint Service are activated. During activation, commands are sent to update the monitoring of Ethernet ports, to update the “bridging points” in all the network elements crossed by the Ethernet, to update the continuity-check probes associated with Ethernet ports.


� In the search window, select Ethernet Services : the list of Ethernet services is displayed.


� Click [Activate ] : the following activation window is displayed (1) (2) (3) .

Figure 7.35 : Window Ethernet Service MultiPoint ac tivation results



Notes : (1) an Ethernet service which has just been created is in a “reserved” state. It

cannot be activated, if it has not ethernet port an d internal point-to-point. (2) an Ethernet service which has just been activat ed goes to the “activated” status when all the ethernet ports and all internal point-to-point are activated (update of monitoring of ethernet ports, update of bridging points for ethernet ports and internal point-to-point in all crossed Ne s, update of continuity-check probes for ethernet ports.

(3) an Ethernet service which has just been activa ted goes to the “Partially activated” if one of internal point-to-point or eth ernet port cannot be activated (for example one NE is inaccessible or in session l ocked).

� Double-clicking on the result line or using [Details ], will bring up a new window Activate ethernet service which shows the detailled results for the activation of objects (internal point-to-point, ethernet ports, probes de continuity check).

Figure 7.36 : Window Ethernet service activation re sults / Details

� Double-clicking on the result line « Activate all ethernet internal point-to-points » or using [Details ], then double-clicking on each line (is multiple activation) « Activate ethernet internal point-to-point » or using [Details ], will bring up the detailled results for the updating of bridging points on internal point-to-point for all crossed Nes.

� Double-clicking on the result line « Activate all ethernet services ports » or using [Details ], then double-clicking on each line « Activate ethernet services port s » or using [Details ], will bring up the results for the updating of bridging points and monitoring for ethernet ports.

� Double-clicking on the result line « Update continuity-check probes » or using [Details ], will bring up the results for the creation of continuity-check probes (source et sink) associated with ethernet ports.

Note : If the update of monitoring cannot be done in one of two Nes, the service

Ethernet will be “activated”, but the NE will be mi saligned.

� Click [Close ] to close the results windows.

7.2.15 - To deactivate an Ethernet MultiPoint Serv ice

This procedure is used to deactivate an “activated” or “partially activated” Ethernet MultiPoint Service (1). All the Ethernet ports “activated” of Ethernet MultiPoint Service are deactivated. All the Internal Point-To-Point “activated” or “partially activated” of Ethernet MultiPoint Service are deactivated. During deactivation, commands are sent to update the monitoring of Ethernet ports, to update the “bridging points” in all the network elements crossed by the Ethernet, to delete the continuity-check probes associated with Ethernet ports.






� Click [Deactivate ] : after confirmation the following deactivation window is displayed (1) (2) (3) .

Figure 7.37 : Window Ethernet service deactivation results

Remarques : (1) An Ethernet MultiPoint Service W hich has just been deactivated goes to the “reserved” status when all the ethernet ports a nd internal point-to-points are “reserved” (update of all bridging points in al l crossed Nes, delete of all continuity-check probes)).

(2) An Ethernet MultiPoint Service goes to the « p artially activated » status if

at least one of internal Point-To-Point or one ethe rnet port cannot be deactivate (for example one of NE is inaccessible o r in session locked).

(3) After an ethernet service deactivation, the mon itoring of ports Erhernet is modified to “none”.

� Double-clicking on the result line or using [Details ], will bring up a new window De-activate ethernet service which shows the detailled results for the activation of objects (internal point-to-point, ethernet ports, probes de continuity check).

Figure 7.38 : Window Ethernet service deactivation results / Details

� Double-clicking on the result line « De-activate all ethernet internal point-to-points » or using [Details ], then double-clicking on each line (if multiple activation) « De-activate ethernet internal point-to-poin t » or using [Details ], will bring up the detailled results for the updating of bridging points on internal point-to-point for all crossed Nes.

� Double-clicking on the result line « De-activate all ethernet services ports » or using [Details ], then double-clicking on each line « De-activate ethernet services ports » or using [Details ], then double-clicking on each line « Demonitor termination » vwill bring up the results for the updating of bridging points and monitoring for ethernet ports.



� Double-clicking on the result line « Update continuity-check probes » or using [Details ], will bring up the results for the deletion of continuity-check probes (source et sink) associated with ethernet ports.

Note : If the update of monitoring cannot be done in one of two Nes, the service Ethernet will be “activated”, but the NE will be mi saligned.

� Click [Close ] to close the results windows.

7.2.16 - To delete an Ethernet MultiPoint Service

Caution : This operation is only possible provided the Ethernet service is deactivated in




� Select the Ethernet service(s) to be deleted then click right to bring up the pop-up menu.

� Click [Delete ] : after confirmation, the Ethernet service is deleted from the list. All the ethernet ports and internal point-to-point are deleted.

7.2.17 - To dissociate an Ethernet MultiPoint Servi ce

This procedure is used to delete in the IONOS-NMS database an Ethernet Multipoint Service « activated » or u « partially activated» while preserving the monitoring of ethernet ports, the bridging points associated with bridging points and ethernet ports, the continuity-check probes associated with ethernet ports in each NE.

Caution : This operation is only possible provided the Ethernet service is activated in the « activated or “partially activated » status.



� Select the Ethernet service(s) to be dissociated then click right to bring up the pop-up menu.

� Click [Dissociate ] : after confirmation, the Ethernet service is dissociated from the list. All the ethernet ports and internal point-to-point are dissociated.



7.2.18 - To visualize/modify the properties of an E thernet MultiPoint Service

This procedure is used to visualize/modify the properties of an Ethernet MultiPoint Service.


� In the search window, select Ethernet services : the list of Ethernet services is displayed.

� Select the Ethernet service which you want to display, then click right to bring up the pop-up menu.

� Click [Properties ] (ou [Show Properties ]) : the Ethernet service properties are displayed.

� Select one of tabs : Information, Composition, Additional information, Alarms, Status history.



Figure 7.39 : Window Ethernet Service MultiPoint / Properties / Information


The name and the « Long name » can be modified.

The N° VMAN can be modified if the ethernet servic e is “reserved”.

The priority can be modified. Click on button [all ow all classes] to have access all the values.



Figure 7.40 : Window Ethernet Service MultiPoint / Properties / Composition

Remarques : The Composition tab displays all the et hernet ports and all the internal points-points of ethernet multipoint service.

Figure 7.41 : Window Ethernet ServiceMultiPoint / P roperties / Additional information

Note : In the Additional Information tab, you can c ustomize the data : customer

name, location and info.



Figure 7.42 : Window Ethernet Service MultiPoint / Properties / Alarms

Notes : In the Alarms tab, you can modify the value of monitoring (values = “All” , “Extremities” or “None”). You can also modify the “ Gravity Profile” of Ethernet service (tick on “Manual” and select a val ue of Gravity Profile in the proposed list).

The value of “Failure gravity” is given by the “Gr avity Profile” and the global status (see menu Tools/Preferences/ Gravity Profile ).



Figure 7.43 : Window Ethernet Service MultiPoint / Properties / Status history




OPTICAL TRAILS MANAGEMENT


8. OPTICAL TRAILS MANAGEMENT

8.1 - INTRODUCTION IONOS-NMS enables Optical Trails management. An Optical Trail connects two ports type WDM/ 1λ, WDM/ ½ λ, WDM/ ¼ λ, WDM/ 1/

8 λ,WDM/ 1/10 λ and uses some WDM Links to carry traffic.

This function only concerns the cards on FSP2000, on FSP3000 or WDM ports on VNE.


8.2.1 - To create an Optical Trail

This procedure is used to define an Optical Trail.

� In the tools bar of the NML View, click left on the NEW icon: the New window is displayed.


� In the window, select Traffic carrier icon then click [OK]: the Create Traffic Carrier window is displayed.



Figure 8.2 : Window Create WDM Trail (1)

� Select the type of traffic carrier: WDM for Domain, Trails for Family, 1 lambda trail (or ½ lambda trail or ¼ lambda trail or 1/

8 lambda trail or 1/10 lambda trail ) for the type. Give the number of trails

to be created (1 by default).

� Click [Next ] to display the following screen: all the list of interfaces is displayed (1).


� In the Source area, select a source WDM interface (2).

� In the Destination area, select a destination WDM interface (2).

� In the name part of the window, enter a serial number for the new Trail and if necessary a “Long name”. By clicking [Default Value ], you will obtain a default number for serial number. For a multiple creation of trails, the serial no is an interval (x..z) or a list of values (x;y;z), the serial no will be added to the long name.




Notes: (1) Incompatible interfaces, already reserve d or not valid (greyed in) are not accessible.

(2) The source and destination interfaces must be ports of WDM type : the WDM trails can be created between two FSP2000 or FS P3000 equipment, via WDM links. It is also possible to use a VNE with WD M port.






� In the Monitoring part (3), if necessary, modify the value of monitoring which involves the update in the equipment : All , Extremities or None .

� In the Gravity Profiles part (3), if necessary modify the mode by ticking or not the case “manual ” and if the case “manual” is ticked, modify the value of Gravity Profile with the proposed list.


Note: (3) the value displayed by default for monit oring, the Gravity Profiles and the parameters of performance are those defined in the preferences of WDM Trail (menu Tools/Preferences/Traffic Carrier/Optical Tra il).




� Select a link connection: the selection is confirmed by a graphic representation of the trail in the linear display part.

Notes: IONOS-NMS does not perform any control of co herence with the selection and engineering.

The links connection already used are not availabl e (in greyed) For a multiple creation, all the link connections must belong to the same WDM

link. In case of trails going through FSP3000 PCN cards, it is necessary to respect

for the link creation the direction West to East (s ee §2.8.1 - “To create WDM Link” and § 8.2.6 - “To add a O-SNC protection to a n Optical Trail”) for more details.

If the two extremities of the link connection belon g to the same NE, It is possible to select the direction for the route in o rder to respect engineering (direction is symbolised by the char “=>” and “<=”) . See Figure 8.6




� If you want to modify the Nes source and destination and modify the link connection, click [Previous ] to return to the previous screen.

� Repeat the operations for each equipment on the route.

� When the destination is reached, [Create main route] is displayed.

� Click [Create main route ] to validate the new WDM trail creation: the result window is displayed.


Note: When creating the WDM Trail, no update is don e in the Nes.

� Click [Close ]: the following screen is displayed





� Activate [Add protection] to create a O-SNC protection (see § 8.2.6 - Add a O-SNC protection to an optical trail).


� If necessary, activate the Trail (see § 8.2.2 - “To activate an Optical Trail”).



8.2.2 - To activate an Optical Trail

This procedure is used to activate a “reserved” Optical Trail (1). During activation, commands are sent to update the monitoring in all the network elements crossed by the trail.


� In the search window, select WDM Trails : the list of WDM Trails is displayed.

� Select the Trail(s) to be activated then click right to bring up the pop-up menu.

� Click [Activate ] : the following activation window is displayed (1) (2) (3) (4).

Figure 8.9 : Window WDM Trail activation results

Notes : (1) a WDM Trail which has just been created is in a “reserved” state.

(2) a WDM Trail which has just been activated goes always to the “activated” status.

(3) During activation of WDM Trail, there is no cre ation of cross-connections in Nes. Only the monitoring is updated. (4) For FSP3000, the “admin state” is respectively set to ‘In service” or “Management” for concerned cards and ports, during the activation of an optical Trail monitored or not.

� Double-clicking on the result line or using [Details ] will bring up a new window Activate WDM Trail which shows the detailed results for the activation of trail.

Figure 8.10 : Window WDM Trail activation results / Details (1)

� Double-clicking on line « Monitor WDM Trail » or using [Details ], then double-clicking on each line (if multiple activation) « Monitor Termination point » or using [Details ], will bring up the results on monitoring of trail (card and ports).




� Double-clicking line « Monitor termination point » or using [Details ] will bring up the global result of monitoring on external port on each extremity NE.


Note: If the update of monitoring cannot be done i n one of Nes, the WDM trail will be

“activated”, but the NE will be potentially misalig n.


8.2.3 - To Deactivate an Optical Trail

This procedure is used to deactivate an “activated” WDM trail. During deactivation, commands are sent to update the monitoring in all the network elements crossed by the Trail.



� Select the Trail(s) to be deactivated then click right to bring up the pop-up menu.

� Click [De-activate ] and confirm the deactivation: the following activation window is displayed (1) (2).

Figure 8.13 : Window WDM Trail deactivation results



Notes : (1) a WDM Trail which has just been deactiv ated goes always to the

“reserved” status.

(2) After a WDM Trail deactivation, the monitoring of ports WDM is modified to “none”.

(3) for FSP3000, the “admin state” is set to “Manag ement” for concerned ports, during the deactivation of an optical Trail.

� Double-clicking on the result line or using [Details ] will bring up a new window De-Activate WDM Trail which shows the detailed results for the deactivation of trail.

Figure 8.14 : Window WDM Trail deactivation results / Details (1)

� Double-clicking on line « Demonitor WDM trail » or using [Details ], then double-clicking on each line « Demonitor termination point » or using [Details ], will bring up the results on demonitoring of ports.

Figure 8.15 : Window WDM Trail deactivation results / Details (2)


8.2.4 - To delete an Optical Trail

Caution: This operation is only possible provided t he WDM Trail is deactivated in the «

reserved » status.



� Select the Trail(s) to be deleted then click right to bring up the pop-up menu.

� Click [Delete ] : after confirmation, the WDM Trail is deleted from the list.



8.2.5 - To dissociate an Optical Trail

ATTENTION : This operation is only possible provide d the WDM Trail i s activated in the « activated » status.

This procedure is used to delete, from the manager database, an « activated » WDM Trail while preserving the monitoring in each NE.


� In the search window, select WDM Trails : The list of WDM Trails is displayed.

� Select the Trail(s) to be dissociated then click right to bring up the pop-up menu.

� Click [Dissociate ]: after confirmation, the WDM Trail is dissociated.

8.2.6 - To add a O-SNC protection to an Optical Tra il

This procedure is used to protect an optical trail.



� Select in tab WDM Trails the optical trail for which you want to add a protection then click right to bring up the pop-up menu.

� Click [Properties ] the WDM Trail properties are displayed. Select the tab Protections .

Figure 8.16 : Window NML View / WDM Trail / protect ion



� Click [Add protection ]: the creation protection window is displayed.

Figure 8.17 : Window Create protection O-SNC (1)

� In the Source part of the window, select a Source board.

� In the Destination part of the window, select a Destination board: the selection is confirmed by a graphic representation of the network elements (eq : FSP1 and FSP2) in the Linear Display part.

Notes: (1) Incompatible elements, already reserved or not valid (greyed in) are not

accessible.

For the FSP3000, the direction “West working” or “ East working” is deducted from the topology according to the direction of sel ected links (Links are created from source port west to destination port e ast, see § 2.8.1 - “To create a WDM Link”)





� In the Parameters part, tick the protection parameter (2) :

Revertive: when the box is ticked, the revertive function enables return to the normal trail when ready, taking in account the value of WTR (not configurable).

Note : In case of FSP3000, protections O-SNC can on ly be not revertive


Note: (2) the default values are those which are d efined in menu Tools/Preferences/Traffic Carrier/tab Optical Trail .




� Select a connection link or several (if multiple creation) (3)(4)(5) : the selection is confirmed by a graphic representation of the connection link (example: optical trail between FSP1 and FSP2) in the Linear Display part.

� If you want to modify the equipment and select another protection trail, click [Previous ] to return to the previous screen.

� If necessary, use the button [Change destination] to select the Destination NE or modify the selection of Destination NE.


� At this moment, the protection is saved in the manager database and can no longer be modified.

Notes : (3) Links connections already used (greyed in) are not accessible.

(4) When creating the protection Trail, no update is done in the Nes.

(5) IONOS-NMS does not perform control of coherenc e with the selection and the engineering

� Click [Close ] : the next screen is displayed.




8.2.7 - To delete an O-SNC protection of an Optical trail

This procedure is used to delete an O-SNC protection of an optical trail which has already been created: you can only delete the protection provided if it is “reserved”.


� In the Search window, select Trail : the list of trails is displayed.

� Select in tab WDM Trails the trail for which you want to delete the protection, then click right to bring up the pop-up menu.

� Click [Properties ] the WDM Trail properties are displayed. Select the tab Protections.

� Select the protection you want to delete. Click right to bring up the pop-up menu. Click [Delete ]

� Confirm the action.

� Click [Close ] to close the result window : the protection path selected is deleted.

8.2.8 - To activate the O-SNC protections of an Opt ical trail

This procedure is used to activate all the “reserved” or “partially activated” protection of an optical trail. During the operation, commands are sent to update the monitoring and to activate the function of protection in the extremities NE of the protection.



� Select in tab WDM Trails the trail for which you want to activate the protection, then click right to bring up the pop-up menu.

� Click [Properties ]: the WDM Trail properties are displayed. Select the tab Protections .

� Select the protection you want to activate. Click right to bring up the pop-up menu. Click [Activate ]: the result window is displayed.


Notes: During activation of O-SNC protection, ther e is no creation of cross-connections in Nes. Only the monitoring and the fun ction O-SNC on boards are updated

With FSP2000 or FSP3000, the protection is applied to the board. When a

protection is activated, all the optical trail for which the board are <protection enabled>, are protected in the network element. It is recommend to create and activate an optical protection for these optical tr ails with the same source and destination boards.

The activation can be activated on a multiple selec tion of trail/bearers with protection.

Caution: With IONOS-NMS, remote port A (FSP2000) i s used exclusively for the working direction. Remote port B (FSP2000) is used for the protecting direction.

With IONOS-NMS, Network West port (FSP3000) and Ne twork East port

(FSP3000) can be used for the working or the protec ting direction. This is defined with the selection of the links during the creation of the trails. In this case, the links must be created from source-West to Destination-East respecting the engineering



8.2.9 - To deactivate the O-SNC protections of an O ptical trail

This procedure is used to deactivate all the “activated” or “partially activated” protection of an Optical trail. During the operation, commands are generated to delete the protection connections in all the Nes crossed by the protection paths.



� Select in tab WDM Trails the trail for which you want to deactivate the protection, then click right to bring up the pop-up menu.

� Click [Properties ]: the WDM Trail properties are displayed. Select the tab Protections .

� Select the protection you want to deactivate. Click right to bring up the pop-up menu. Click [Deactivate ]: the result window is displayed.


Notes: During deactivation of O-SNC protection onl y the monitoring and the function O-SNC on boards are updated

With FSP2000 and FSP3000, the protection is applie d to the board. When a

protection is deactivate, the function O-SNC is sti ll activated if other protected optical trail are activated using the same board as extremity of protection.

A trail for which the protection has been deactivat ed goes to the “partially activated” state.

8.2.10 - To send O-SNC protection switchover comman ds

Caution : These commands can only be sent to an “ac tivated” optical trail.



� Select in tab WDM Trails the optical trail for which you want to send a command, then click right to bring up the operations pop-up menu.

� Click [Properties ]: the WDM Trail properties are displayed. In the right window, select the Protections tab then, in the list, the trail which is to receive the command



Figure 8.22 : Window O-SNC Switch commands

� At the bottom of the window, click the Switch command tab: the following commands are displayed: Clear, Swiitch to working, Switch to protection, Lockout protection .

� Select the command which you want to send.

� Click [Send ] to generate the command.

Note : The Switch command is applied to the protect ion path selected.

For a FSP3000, to send the same switch command a s econd time, is refused by the equipment but is without consequence

The commands sent from IONOS-NMS correspond to the following commands executed in the equipment FSP2000 or FSP30 00:

Command executed Command sent from

IONOS-NMS FSP2000 FSP3000 Switch to working Force working Manual working Switch to protection Force protection Manual protection Lockout Force working Lockout protection Clear Auto Clear



8.2.11 - To display / modify the properties of an O ptical Trail

This procedure is used to display / modify the properties of a WDM Trail.



� Select the Trail which you want to display, then click right to bring up the pop-up menu.

� Click [Properties ] (or [Show Properties] ) : the WDM Trail properties are displayed.

� Select one of tabs : Linear Display, Information, Protections, Route, Additional information, Alarms, Status history.



Figure 8.23 : Window WDM Trail / Properties / Linea r display (1)

� In tab Linear Display , Click [Activation ] in “Animation” area to visualise the state of activation of the WDM trail.

Notes : In the Linear Display window, the optical trails are represented by a

continuous line for the main trail or by a dotted l ine for the protection trail: the lines are green (when the trail is activated) or or ange (when the trail is “reserved” or “partially activated”).

The tool tip gives the direction “west to east” of the selected link



Color of Link :

- For the path “Working” : always green

- For the path of protection: green if protection O-SNC is activated.


- in green if the trail is activated.

- In orange if the trail is reserved.

� In tab Linear Display , Click [Alarms ] in “Animation” area to visualise the state of alarm of the WDM trail according to the direction (one-way or bi-directional).

Color of Link :

- For the path “Working” and a given direction


� In grey if “output” NE is a VNE


� In purple if alarm of maximum severity = critical on output NE



- For the path “Working” and the bidirectional mode:

� the synthesis of the colors of the two directions according to the command grey, green, yellow, red, purple and blue.


� The synthesis of the colors of the two directions according to the command grey, green, yellow, red and blue.

- For the path “Protection” (protection SNC) and a given direction

� in green if not of alarm or alarm of maximum severity = warning on output NE

� in gray if it “output” NE is a VNE

� in gray if the O-SNC protection is not activated


� in purple if alarm of maximum severity = critical on output NE



- For the path “Protection” (protection O-SNC) and the bidirectional mode:

� colored according to the synthesis of the colors of the two directions according to the command gray, green, yellow, red, purple and blue.



Color of NE icons :





� In purple if alarm of maximum severity = critical




� Colored according to the synthesis of the colors of the two directions according to the command without color, green, yellow, red, purple and blue.



� Click [Traffic Indic. ] (tab Linear display ) to visualise if the traffic passes by the path “Working” or the path of protection according to the direction.

� Select one of Nes or one of Links and activate the pop-up menu (click right). This menu allows to launch the actions on the selected NE or Link, or on the O-SNC protection.

Figure 8.24 : Window WDM Trail / Properties / Infor mation

Notes : The Information tab displays the details of the WDM Trail.




Figure 8.25 : Window WDM Trail / Properties / Prote ctions

Note : In the Protection Path tab, you can display and modify the O-SNC parameters of a protection.

Figure 8.26 : Window WDM Trail / Properties / Addit ional information




Figure 8.27 : Window WDM Trail / Properties / Route / Link connection

Note : in the tab Route/Link connection, you can re ad the state of link connections (WDM Links) of Trail ( «reserved » or « activated » ).

Figure 8.28 : Window WDM Trail / Properties / Route / CrossConnection



Note : in the tab Route/Crossconnection, you can re ad the state of connections of WDM Trail ( «reserved » or « activated »).

Figure 8.29 : Window WDM Trail / Properties / Alarm s

Notes: In the Alarms tab, you can modify the value of monitoring (values = “All”, “Extremities” or “None”). You can also modify the “ Gravity Profile” of WDM Trail (tick on “Manual” and select a value of Gravi ty Profile in the proposed list).

Figure 8.30 : Window WDM Trail / Properties / Statu s history



Notes: In the Status history tab, you can display t he status history of the trail since it was activated: if one of the extremity Nes is misal igned, the history is not always supplied.

Following a stop of the server or change of monitor ing of the trail, the history is not available any more during a few minutes.

The status history is calculated from the Fault log . If the Fault log is purged, the status history will be not given for the purged events.

MS-SPRING PROTECTION MANAGEMENT


9. MS-SPRING PROTECTION MANAGEMENT

9.1 - INTRODUCTION

The MS-SPRing protection management functions are used to create an STM16 MS-SPRing protection in a ring of ADR2500C multiplexers, ADR2500 EXTRA multiplexers or ADR10000HN or to create an STM64 in a ring of ADR10000HN. In the ring, channels 1 to 8 (STM16 protection) or 1 to 32 (STM64 protection) are used for data transport and channels 9 to 16 (STM16 protection) or 33 to 64 (STM64 protection) for protection data transport.

In the event of a link or node rupture, the two nodes adjacent to the link or to the node loop the transport channels in the protection channels.

9.2 - DESCRIPTION OF « USER » TASKS

9.2.1 - To create a ring

This procedure is used to create an MS-SPRing protection ring.



� In this window, select the Ring icon then click [OK] : the Create Ring window is displayed with its resources.



Figure 9.2 : Window Create Ring : Select First NE

� In the “Name“ field, enter a name (60 characters max.) for the ring.

� In this window, select the first network element (1) (2).

� Click [Next ] to validate the creation of the first NE: all the conditions are automatically validated by the manager before the next screen is displayed.

Notes : (1) An NE is not valid: . if it is not an ADR2500C, ADR 2500 EXTRA or ADR1 0000HN multiplexer or a

VNE with STM16 interfaces for protection STM16. . if it already contains an MS-SPRing protection f or ADR2500C or ADR2500

EXTRA multiplexeur. . if there are “cross-connections” between the int erfaces of lines 1 and 2

(SNCP protection, non-direct connections) . if the interfaces of lines 1 and/or 2 have an MS P protection. (2) The network elements which are not valid are grayed in the window.



Figure 9.3 : Window Create Ring : Select STMLink

� In this window, select the STM16 or STM64 link leading out from the first NE (3) (4).

� Click [Next ] to validate the selection: the selection is confirmed by the graphic representation of the ring at the bottom of the screen.

� Select a new STM16 link starting from the second NE.

� Repeat the two last operations for each NE in the ring up to the first NE (the number of Nes in the ring remains 3 ≤ n ≤ 16).

Notes : (3) An STM16 or STM64 link is not valid: if it is already used in a previous selection. If it belongs to another ring. If it does not belong to the interfaces of lines 1 and 2 for ADR2500C or

ADR2500 EXTRA (STM16). If the Destination NE is invalid for creation of t he ring. The relative interface that can support MS-SPRing for ADR10000HN are :

“1,16”, “2,3”, “4,5”, “6,7”, “10,11”, “12,13” and “ 14,15” (4) The STM16 links which are not valid are grayed in the window.

� When the first NE is reached, all the Nes (16 max.) belonging to the ring are selected: the following window is displayed.



Figure 9.4 : Window Create Ring : Select Properties

� If necessary, modify the default parameters (5) of the MS-SPRing protection: WTR (6), Multiple Ring Switch Handling (7).

� Click [Next ] to go to the next screen to enter the customized data for the ring.

Notes : (5) The structure of the channels is given according to the VC4 bearers and VC4 trails going through the ring. This structure c an be modified : a channel “Working” can always be modified to “NUT”. The asso ciated channel (from 9 to 16 for a ring STM16 or 33 to 64 for a ring STM64 ) is automatically “NUT”. A channel “NUT” can be modified to “Working” only if the associated channel (from 9 to 16 for a ring STM16 or 33 to 64 for a ri ng STM64) is free (no VC4 bearer and no VC4 trail) and if the bearers/trails created on the modified channel respect the MS-Spring rules (not switched A U4 and not SNC).

(5) The default parameters can be modified with men u Tools/Preferences/Ring

(6) WTR is the waiting time (30 to 900 s.) defined to accept the validity of a

channel after it has failed.

- If the ring operates in Multiple Ring Switch Handli ng : this means that the AU4 traffic which cannot be protected is replaced by the SIA signal. In Sing le Ring Switch Handling, only the single failures are managed by the ring.



Figure 9.5 : Window Create Ring : Select Additional Information

� Select [Yes] or [No] for the monitoring of ring (8).

� Enter:



c/ any necessary additional information in the « Info » field (200 characters max.).

� Click [Create Ring ] to validate the ring creation (8) : the MS-SPRing protection « reserved » is then saved in the manager database.

To visualize the created ring see § 9.2.6 -

Caution : (8) The default value for monitoring can be modified with menu

Tools/Preferences/Ring (8) Monitoring is relative to protected channel onl y. (8) A ring can be created in state “monitored” only if all STM-16 (STM64) links of ring are “monitored”. If one of Links is not “mo nitored”, a pop-up window is displayed with the possibility to monitor the Li nk. (8) a ring can be created in state “no-monitored” o nly if all the bearers/trails going through the ring are “no-monitored”. (9) When an MS-SPRing protection ring is created, a ll the AU4s ( 9 to 16 for ring STM16 and 33 to 64 for ring STM64) are unavail able for creation of trails, except channels used in “NUT”.

ADR10000HN does not support “NUT” configuration



9.2.2 - To activate a ring

This procedure is used to activate the “reserved” (1) or “partially activated” MS-SPRing ring. During the operation, commands are generated to all the Nes crossed by the ring to configure and activate the ring.


� In the search window, select Rings : the list of rings is displayed.

� Select the ring to be activated then click right to bring up the pop-up menu.

Figure 9.6 : Window Trail / Activate Ring

� Click [Activate ] : the Activation result window is displayed (1) (2) (3) (4) (5) (6).

Notes: (1) An MS-SPRing ring which has just been cr eated is in a “reserved” status.

(2) An MS-SPRing ring activated goes to the “acti vated” status when all the parameters associated to the protection have been c onfigured in each equipment of the ring.

(3) An MS-SPRing ring activated goes to the “parti ally activated” status when all the parameters associated to the protection hav e not been configured in the equipment of the ring.

(4) If during activation, a ring is crossed by a VC 4, VC4-4C or VC4-16C (ring STM64 only) trail already activated, the manager up dates the “misconnection” tables of the Nes of the ring crossed by the trail if the used channel = “Working” (in Multiple Ring Switch Handling mode).

(5) If one of the Nes is inaccessible, the commands will not be generated to the next NE: the status of the ring will then be “r eserved” or “partially activated”.

(6) if the ring is “activated”, the loops on the eq uipment are displayed on NE icons in Topology View. The switching indication s preads on icons of associated sub-networks.



Figure 9.7 : Window Activation results / Ring

� Double-clicking on the ring line brings up the Details window with all the details in the MS-SPRING results tab (7).

Figure 9.8 : Window Activation results / Ring / De tails

� Click on MS-SPRing Monitoring results Tab to have the list of monitored points.



Figure 9.9 : Window Activation results / Ring / Det ails monitoring


� Click [Finish ] to close the activation window.

Notes : (7) The results window displays the list of all the Nes, showing if they have been activated or not (in this case, with the cause of the error). The results window give the list of monitored points (monitorin g of AU/HO points for AU4 “Protection”+ monitoring of ring for each NE).



9.2.3 - To deactivate a ring

This procedure is used to deactivate the “activated” or “partially activated” MS-SPRing ring. During the operation, commands are generated to all the Nes crossed by the ring to deconfigure and deactivate the ring.



� Select the ring to be activated then click right to bring up the pop-up menu.

� Click [De-Activate] : a confirmation message is displayed.

� Click [Yes] to confirm : the window Deactivation results is displayed (1) (2) (3).

Figure 9.10 : Window Deactivation results / Ring

� Double-clicking on the ring line brings up the Details window showing all the details in the MS-SPRING results tab (4).

Figure 9.11 : Window Deactivation results / Ring / Details

� Click on MS-SPRing Monitoring results tab to have the list of points which are “no-monitored” (4).



Figure 9.12 : Window DeActivation results / Ring / Details monitoring


� Click [Finish ] to close the activation window.

Notes : (1) An MS-SPRing ring deactivated goes to t he “reserved” status when all the parameters associated to the protection have been d eleted in each equipment of the ring.

(2) An MS-SPRing ring deactivated goes to the “par tially activated” status when all the parameters associated to the protectio n have not been deleted in the ring equipment.

(3) If one of the Nes is inaccessible, the comman ds are generated to the next NE: the ring status then becomes “partially activat ed”.



(4) The results window displays the list of all th e Nes, showing if they have been deactivated or not (in this case, with the cau se of the error). The results window give the list of points “no-monitored” (moni toring of AU/HO points for AU4 n°9 to 16 (ring STM16) or n°33 to 64 (ring STM6 4) “Protection” for each NE).

9.2.4 - To delete a ring

Caution : This operation is only possible provided the MS-SPRing is deactivated

(“reserved” status)



� Select the ring to be deleted then click right to bring up the pop-up menu.


� Click on [Yes] to confirm the deletion : the ring is deleted from the list.

9.2.5 - To dissociate a ring

This task is used to delete, from the manager database, an “activated” or “partially activated” MS-SPRing ring while preserving the modifications in each NE of the ring.



� Select the ring to be dissociated then click right to bring up the pop-up menu.

� Click [Dissociate ] : a confirmation message is displayed.

� Confirm the dissociation : the ring is dissociated.

9.2.6 - To display and modify the properties of a r ing

This task is used to display and modify the properties of an MS-SPRing protection ring.



� Select the ring to be displayed then click right to bring up the pop-up menu.

� Click [Properties] : the right window is displayed with 5 tabs: Linear display, Properties, Additional information, Details, Alarms.

� Click on Linear Display Tab.

� Click on [Activation ] (Linear display tab) in “Animation” to display the activation state of ring.



Figure 9.13 : Window MS-SPRing Properties / Linear Display (1)

Link color :

- If the ring is “activated”, all the links are green.

- If the ring is “reserved” or “partially activated”, all the links are orange.

Color of NE name :

- In green if the ring is “activated” in the NE.

- In orange if the ring is “reserved” or “partially activated” in the NE.

� If the ring is “activated”, Click [Alarms ] (Linear display tab) in “Animation” to display the alarm state of ring,



Figure 9.14 : Window MS-SPRing Properties / Linear Display (2)

The link is colored :

� In green if no alarm or alarm of maximum severity = warning.

� In gray if the two Nes are VNE.

� In blue if inaccessibility alarm.

� In red if alarm of maximum severity = major.


The NE is colored :

� In green if no alarm or alarm of maximum severity = warning.

� Without color if the NE is VNE.

� In blue if inaccessibility alarm.

� In red if alarm of maximum severity = major.


Click on [Switch Indic. ] (Linear display tab) to display the switches.

Notes : The animation takes in account all the alar ms, acknowledged or not

acknowledged, but not the traffic direction. The ring must be “activated”.

� Click on [Map display ], the map of ring is displayed.

� Select one of Nes or one of STM-16 links and activate the pop-up menu. This menu allows to launch the actions on the selected NE or the selected Link.



Figure 9.15 : Window MS-SPRing Map Display

� Click on Properties tab to display the ring properties.

Figure 9.16 : Window Ring / Properties / Properties



� Modify possibly the channels structure

� Modify possibly the WTR value and the et “Multiple Switch Ring Failure” mode.

Notes : The structure of channels can be modified : a channel “Working” can always be modified to “NUT”. The associated channel (from 9 to 16) is automatically “NUT”. A channel “NUT” can be modified to “Working” only if the associated channel (from 9 to 16 for ring STM16 or 33 to 64 fo r ring STM64) is free (no VC4 bearer and no VC4 trail) and if the bearers/tra ils created on the modified channel respect the MS-Spring rules (not switched A U4 and not SNC). The structure of the channels is static.

The fiber failure management mode (Multiple Ring S witch Handling) can be modified if the ring is “reserved”.

WTR is the waiting time (30 to 900 s.) defined to accept the validity of a channel following failure of the channel.

� Click on Additional Information tab to display the customer data.

Figure 9.17 : Window MS-SPRing / Properties / Addit ional information

Note : In the Additional information tab, you can m odify the customer name, location and info data.

� Cliquer sur [Apply ] to validate the modifications

� Click on Details tab to display the states of ring in each NE.



Figure 9.18 : Window MS-SPRing / Properties / Detai ls

� Click on Alarms tab to display the ring alarms.

Figure 9.19 : Window MS-SPRing / Properties / Alarm s



9.2.7 - To send switchover commands

Caution : These commands can only be sent to an “ac tivated” ring.

� Display the NML View by clicking on View > NML View .


� Select the ring to which you want to send a command then click right to bring up the pop-up menu.

� Click [Properties ] : the properties of the trail are displayed in the right.

� In the right window, select the Details tab then, in the list, the equipment to receive the command.

Figure 9.20 : Window MS-SPRing / Properties / Detai ls / Switch commands

� At the bottom of the window, click the Switch commands on tab.

� Select the side where the command will be generated: West or East (in the ring).

� Select one of the commands which you want to send: Clear, Forced switch or Manual switch.

� Click [Send ] to send the command.

Notes : The Status on West and Status on East items (West and East of NE) are updated.

In the Linear display tab, you can display the lo ops on the equipment, and in Topology View on NE icons.

The “NE direction” field indicates if the East and West directions are identical or not in the equipment (displayed in HTTP browser) .

ALARMS MANAGEMENT


10. ALARMS MANAGEMENT

10.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 OFF.

� alarm not acknowledged: alarm ON.

� alarm acknowledged : alarm ACK.

� Alarm disappeared : alarm OFF.

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.

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 pfysic al Nes.

ALARMS MANAGEMENT


10.2 - MANAGEMENT OF CURRENT ALARMS

10.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 10.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.

� 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.

ALARMS MANAGEMENT


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 10.2 : Window Topology View / Fault View / P op-up menu

Notes : (1) At the bottom of the main menu to the r ight, you can immediately check the number of current alarms by 4 numbers: polling alarms (blue), major alarms (red), minor alarms (yellow) and other alarm s (blue or gray).

(1) The current alarms table can be detached (to u se 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 a lways visible). (2) To sort on another parameter, click on the para meter in the parameters bar of the log: once selected, choose the appropriate m arker (▲ 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 fun ctions : . [Filter selection] to add a filter on the conte nts 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

10.2.2 - To acknowledge a current alarm

This procedure is used to acknowledge an alarm.

ALARMS MANAGEMENT


� In the alarms table, select an alarm.


� 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 co lor 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.

10.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 Ctr l key.

(2) This operation contributes to changing the col or 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.

10.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).

ALARMS MANAGEMENT


Figure 10.3 : Window Topology View / Fault View / L ist 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 si ze of displayed columns.

(3) Use “visible columns” to choose the columns dis played 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 o f 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 mad e for each user when the IONOS-NMS client will be closed.

ALARMS MANAGEMENT


Note : To display the status of alarm for SDH and W DM links, bearers, and SDH and WDM trails, use “visible columns” to add the “Statu s “ column and use “Row coloration” to color according to the severity of t he Status.

This function is available by default for a user w ith the administrator rights.

10.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 .

10.2.6 - To display the properties of a current ala rm

This procedure is used to display the properties of an alarm.



� In this menu, select [Properties ] : the Alarm Properties / Information window is displayed.

Figure 10.4 : Window Alarms properties / Informatio n

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 to ols bar to display the properties of

an alarm.

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 selec ted in the list of alarms of the NML View (Alarms tab).

10.2.7 - To display the alarms unacknowledged clear ed 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 10.5 : Window Unacknowledged cleared and new Alarms

ALARMS MANAGEMENT


� Click, if necessary, [Clear New Alarms ] to clear all the alarms of this list.


� To deactivate the function, uncheck [Show Cleared Alarms list ] in the window.

Notes : (1) If the function is activated, the windo w 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

10.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 10.6 : Window Unacknowledged cleared and new Alarms

� Click, if necessary, [Clear New Alarms ] to clear all the alarms of this list.

ALARMS MANAGEMENT



� To deactivate the function, un-check [Show New Alarms list ] in the window.

Notes : (1) If the function is activated, the windo w 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

10.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 § 1.2.3.27 - To configure the alarm multi-criteria filtering.

Then, it’s 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, it’s 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.

ALARMS MANAGEMENT


Figure 10.7 : Window Topology View /Fault View / Li st 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:

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.

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

10.2.10 - To activate the send of mails on alarms m odification

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

ALARMS MANAGEMENT


1 Inaccessible alarm raised on P1198383 Alarm Status : Unack alarms : 26 Major, 10 Minor, 81 Warning All alarms : 26 Major, 10 Minor, 81 Warning Activity Summary : Raised : 1 Inaccessible, 1 Major Cleared : 2 Inaccessible, 1 Critical, 1 Major Acknowledged : Unacknowledged : Activity Equipment Location Event type Status Ack Begin date Raised and cleared 155c104/104 BOARD SLOT B defective Major no 03/12/04 14:37:36 Cleared 63e99/99 Synchro NE Data failure (Configuration Number) Critical no 03/12/04 14:37:16 Raised and cleared 63e99/99 Polling Inaccessible no 03/12/04 14:38:44 Cleared Nice26/1 Polling Inaccessible no 03/12/04 14:37:28

10.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

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 Equipment Location Event type Status Ack Begin date Raised SLF-N-62.122 Polling Inaccessible no 03/12/08 10:39:47

10.2.12 - To propagate current alarms on the trails

This procedure is used to supervise the consequences of an alarm on the trails, the VC4 bearer trails, the STM-n links, the VCGroups, the Ethernet Links, the Ethernet Services, the WDM Links, the WDM Trails of the network.



� In this menu, select [Properties ] : the Alarms Properties / Information window is displayed.

� Click on [Propagation ] : the Propagation Alarms /Propagation window is displayed with several tabs (1) (2) (3) (4) (5).

Figure 10.8 : Window Alarm properties / Propagation

� Select the STM-n tab to view the status of the STM-n links affected (2).

� Select the Bearers tab to view the status of the bearer trails affected (2).

� Select the Trails tab to view the status of the trails affected (2).

� Select the VCGRoups tab to view the status of the VCGroups affected (2)

� Select the Ethernet Link tab to view the status of the Ethernet Links affected (2)

ALARMS MANAGEMENT


� Select the Ethernet P2P Service to view the status of the Ethernet Point-To-Point service affected (2)

� Select the Ethernet Servic e to view the status of the Ethernet MultiPoint services affected (2)

� Select the WDM Link to view the status of the WDM Links affected (2)

� Select the WDM Trail to view the status of the WDM Trails affected (2)


Notes : (1) You can obtain the Propagation Alarms on Trails window directly by double-clicking on an alarm in the Fault View list.

(2) Depending on the status of the links, trails a nd VCGroups, the line is displayed:

. green: traffic normal . yellow: downgraded traffic . red: traffic cut off . blue: trail status undetermined (extremity node s inaccessible) . gray (no input signal).

(3) The Propagation menu can also be obtained in the pop-up menu of an alarm selected in the list of alarms in the NML View (Alarms tab).

4) If the collection of performance is activated on the link or on the trail, the number of collected points is indicated in the colu mns “P 24h “ and P 15mn”.

(5) The “Failure gravity” is displayed according to the selected profile (columns “Manual” and “Gravity Profile”) and trail status (c olumn “status”).

10.2.13 - To display the trails supervised in real time.

You can display the SDH trails supervised in real time at the bottom of the main view window, tab SDH Trails. This function is defined for any users.

� Click in tab SDH Trails : The trails supervised in real time whose status is different from ‘traffic OK’, are “logged” and updated (1) (2) (3).

Figure 10.9 : Window Topology View / SDH trails (1)

Notes : (1) The table “Real Time Supervision” is re freshed each 5 seconds. (2) The menus [Filter] and [Save as] are available in pop-up menu. (3) The number of trails supervised in real time a nd the refresh frequency are

defined in a file xml (see § 0)

ALARMS MANAGEMENT


Figure 10.10 : Window Topology View / SDH trails (2 )

� Select a trail and click [Disable real time supervision ] to cancel the supervision in real time for this trail and for the “logged” user. The trail is deleted from the list.

� Select a line and click [Acknowledge ] to acknowledge a trail : The “Ack” field is checked (1)(2).

� Select a line and click [Unacknowledge ] to unacknowlege a trail : The “Ack” field is un-checked (1)(2).

Notes : (1) You can use the Acknowledge function in the tools bar to directly

acknowledge or unacknowledge several lines selected using the Ctrl keys. (2) The user name and date of acknowledgement are updated in

corresponding columns.


10.2.14 - To activate the Standby trail management.

In order to decrease the quantity of alarms, this procedure is used to invert the type of PPI-LOS or PPI-AIS alarms for VC12/VC3 SDH trails on PDH cards (Adr155c ≥P5.5 and Adr2500Extra ≥3.0.5) This function is defined for any users.

� This procedure can be done manually from the NML view or with a scheduled task once a day (§ 1.2.3.24 -To configure the scheduled task for Standby trail).

� .To see the “mode” of a SDH trail (source and destination) from the NML view (tab Trail SDH), add the columns “Source mode” and “Destination mode” (§ 3.2.1 -To display / filter a list of objects)

Figure 10.11 : Window Topology View / SDH trails

� When the scheduled task is finished, an export file is generated. This file contains the list of the trails with a source “state” or destination “state” which is not “Normal”.

The filename is StandbyTrails-yyyy-mm-dd.txt. It can be found in the directory chosen during the installation (by default ….\Ionos-NMS\log\export\yyyy\yyyy-mm\dd on Windows /data/Ionos-NMS/log/export/yyyy/yyyy-mm/dd on Solaris

HISTORIES MANAGEMENT


11. 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 b e configured from 200 to

10000 by clicking on button [View Size]

(3) Use the tools bar to access the following funct ions:

� [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 fun ctions:

. [Filter selection ] to add a filter on the cont ents of a selected cell.

. [Enable filters] to activate/deactivate the filt ers.

. [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.



a/ By selecting the Event Log , the following screen is displayed (3).

Figure 11.1 : Window Log View / Event Log

b/ By selecting the Fault Log, the following screen is displayed (3).

Figure 11.2 : Window Log View / Fault Log



Notes : The parameters are the same as for the cur rent alarms log (see § 10.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 leve l 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 11.3 : Window Log View / Server Log

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

Figure 11.4 : Window Log View / Database Log



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 11.5 : Window Log View / SDH Trails Log

PREFERENCES MANAGEMENT


12. PREFERENCES MANAGEMENT

12.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.

12.2 - PREFERENCES

12.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 12.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 accoun t only on one new launching of the Application Client (after closing of IONOS-NMS Clie nt).



12.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 12.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 ic ons as model.



12.2.3 - To change the default properties of the Ne s

This procedure is used to modify the default values of NE parameters.


� In this screen, select the Nes tab.

Figure 12.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




12.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 12.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



� Use [Browse ] to select a new file.

� Use [Clear ] to delete the configuration of selected line.


Notes : The configuration sounds is defined for ea ch 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 > warnin g)

12.2.5 - To change the default properties of trails

This procedure is used to modify the default values of parameters for Bearers and Trails..


� In this screen, select the Trails tab.

Figure 12.5 : Window Preferences / Trail

� In the Default monitoring area, select the default monitoring: [All ], [None ] or [Extremities ].

� In the Performance area , give the parameters by default : to activate or not the collection of performance by ticking the case “collect defined counters”) and select the mode of collection.

a/ none : no collection of performance;

b/ extremities 24h : collect performance over the periods of 24h on the points of extremities Nes of the bearer/trail;



c/ extremities 24h/15mn : collect performance over the periods of 24h and 15mn on the points of extremities Nes of the bearer/trail;

d/ all 24h : collect performance over the periods of 24h on all the points of the bearer/trail;

e/ all 24h + extremities 15mn : collect performance over the periods of 24h on all the points of the trail and the periods of 15mn on the points of extremities Nes of the bearer/trail;

f/ all 24h/15mn : collect performance over the periods 24h and 25mn for all the points of the bearer/trail.

� In the Default gravity configuration area, to modify if required the “gravity failure” profile for each type of trail (1). The values which can be selected are those defined in the Failure Gravity default Profile tab.(see § 12.2.9 -)

� In the Default value protection path parameters area, tick or enter the default parameters for the protection:

a/ Revertive: ticked, enables return to normal trail when ready. The activation time is defined by WTR (30 to 900 s.) ;

b/ WTR (in seconds) : revertive function activation time ;

c/ Hold Off Time (in 1/10 s.) : protection activation time after appearance of an alarm ;

d/ Type SNC (SNC/I or SNC/N)


Note : (1) the modification will be applied to all the trails/bearers already created of

which Gravity Profile is in automatic mode (case “m anual” not ticked in Properties/Alarms tab of bearer/trail).

12.2.6 - To change the default properties of STM-n Links

This procedure is used to modify the default values of parameters for STM-n Links.


� In this screen, select the STM-n Link tab.



Figure 12.6 : Window Preferences / STMnLink

� In the Default monitoring area, select the default monitoring: [All ] or [None ]

� In the Performance area, give the parameters by default : to activate or not the collection of performance by ticking the case “collect defined counters”) and select the mode of collection.

a/ none : no collection of performance;

b/ extremities 24h (idem all 24h) : collect performance over the periods of 24h on all the points of the STM-n Link;

c/ extremities 24h/15mn (idem all 24h/1(mn and all 24h + extremities 15mn): collect performance over the periods of 24h and 15mn on all the points of the STM-n Link;

� In the Default gravity configuration area, to modify if required the “gravity failure” profile for each type of STM-n Link (1). The values which can be selected are those defined in the Failure Gravity default Profile tab. (see § 12.2.9 -)

� In the Default RS Path Trace Configuration area, to modify if required the “RS Path Trace” default configuration.

� In the bottom area, tick or enter the default parameters for the MSP protection:

a/ Revertive: ticked, enables return to normal trail when ready. The activation time is defined by WTR (30 to 900 s.) ;


c/ Hold Off Time (in 1/10 s.) : protection activation time after appearance of an alarm ;



d/ SF/SD Priority : Low or High G783 ;



Note : (1) the modification will be applied to all the STM-n Links already created of which Gravity Profile is in automatic mode (case “m anual” not ticked in Properties/Alarms tab of STM-n Link).

12.2.7 - To change the default properties of VCGrou ps

This procedure is used to modify the default values of parameters for VCGroups.


� In this screen, select the Traffic Carrier tab, then VCGroups tab.

Figure 12.7 : Window Preferences / VCGroups

� In the Default monitoring area, select the default monitoring: [All ] or [None ]

� In the Default gravity configuration, to modify if required the “gravity failure ” profile for each type of VCGroup (1). The values which can be selected are those defined in the Failure Gravity default Profile tab. (see § 12.2.9 -)



� In the Specific parameters area, to modify if required the default type of ethernet ports : EP-Line/LAN Support or EVP-Line/LAN Support (used for mutualization).


Note : (1) the modification will be applied to all the VCGroups already created of which Gravity Profile is in automatic mode (case “m anual” not ticked in Properties/Alarms tab of VCGroup).

12.2.8 - To change the default properties of MS-SPR ings

This procedure is used to modify the default values for the Rings.


� In this screen, select the Ring tab.

Figure 12.8 : Window Preferences / Ring

� In Default monitoring area, select the default monitoring : [Yes] or [No].

� In Default values MSSPRING parameters area, tick or enter the default values for parameters of protection :

a/ Multiple Ring Switch Handling ;





12.2.9 - To change the default properties of “gravi ty failure” profiles

This procedure is used to modify the values of “failure gravity” for each defined profile according to the status of Trail/Bearer/STM-n Link (1).


� In this screen, select the Gravity profiles tab.

Figure 12.9 : Window Preferences / Gravity profiles

� For each profile defined by default : “Low importance”, “Medium importance”, “High importance” and “Very high importance” and for each status ( “cut”, “degraded”, “no input”, “unavailable”), if necessary modify the label and the level. For the label, select one of the possible values in the proposed list “very low”, “low”, medium”, “high, “very high” or “ “ (no value). For the level, give a number between 1 and 100. The level can not be indicated.

� If necessary, add a new profile with button [Add ].

� If necessary, select a profile and click on [Remove ] to delete a profile (2).


Note : (1) The “failure gravity” gives for each tr ail, STM-n Link, Ethernet Link,

VCGroup in alarm status (“cut”, “degraded”, “no i nput” or “unavailable”) a severity which can be used on the alarm propagation (see §10 )to sort the trails, the STM-n Links, the VCGroups, the Ethernet Links.

(2) A profile used by a STM-n Link, a Bearer, a Tra il, a VCGroup, an Ethernet Link cannot be removed (the case “Used” is ticked).



12.2.10 - To change the default properties of QOS p rofiles

This procedure is used to modify the profiles by default of QOS parameters used for Ethernet Services.


� In this screen, select the QOS profile tab.

Figure 12.10 : Window Preferences / QOS profiles

� For ach profile defined by default, if necessary modify the label.

� If necessary, add a new profile with button [Add ].

� If necessary, select a profile and click on [Remove ] to delete a profile (2).




12.2.11 - To change the default properties of Ether net Links

This procedure is used to modify the default values of parameters for Ethernet Links.


� In this screen, select the Traffic Carrier tab, then Ethernet Link tab.

Figure 12.11 : Window Preferences / Ethernet Links

� In the Default monitoring area, select the default monitoring: [All ] or [None ].

� In the Default gravity configuration , to modify if required the “gravity failure ” profile for each type of Ethernet Link (1). The values which can be selected are those defined in the Failure Gravity default Profile tab. (see § 12.2.9 -)

� In the Specific parameters area, to modify if required the default type of ethernet ports : EP-Line/LAN Support or EVP-Line/LAN Support (used for mutualization.


Note : (1) the modification will be applied to all the Ethernet Links already created of which Gravity Profile is in automatic mode (case “m anual” not ticked in Properties/Alarms tab of Ethernet Link).



12.2.12 - To change the default properties of Ether net Services

This procedure is used to modify the default values of parameters for Ethernet Services.


� In this screen, select the Traffic Carrier tab, then Ethernet Service tab.

Figure 12.12 : Window Preferences / Ethernet Servic es

� In the Default monitoring area, select the default monitoring: [All], [Extremities ] or [None ].

� In the Default gravity configuration , to modify if required the “gravity failure” profile for an ethernet service (1). The values which can be selected are those defined in the Failure Gravity default Profile tab. (see § 12.2.9 -)

� In the Traffic priority area, to modify if required the default priority for the ethernet point-to-point service and for ethernet multipoint service.

� In QOS Profile area, select the profile by default. The values which can be selected are those defined in the QOS Profile tab. (see § 12.2.10 -)




12.2.13 - To change the default properties of Optic al Links

This procedure is used to modify the default values of parameters for Optical Links.


� In this screen, select the Traffic Carrier tab , then Optical Link tab.

Figure 12.13 : Window Preferences / WDM Links

� In the Default monitoring area, select the default monitoring: [All ] or [None ].

� In the Default gravity configuration , to modify if required the “gravity failure ” profile for each type of Optical Link (1). The values which can be selected are those defined in the Failure Gravity default Profile tab. (see § 12.2.9 -)


Note : (1) the modification will be applied to all the WDM Links already created of which Gravity Profile is in automatic mode (case “m anual” not ticked in Properties/Alarms tab of WDM Link).



12.2.14 - To change the default properties of Optic al Trails

This procedure is used to modify the default values of parameters for Optical Trails.


� In this screen, select the Traffic Carrier tab, then Optical Trail tab.

Figure 12.14 : Window Preferences / WDM Trails

� In the Default monitoring area, select the default monitoring: [All ], [Extremities ] or [None ].

� In the Default gravity configuration , to modify if required the “gravity failure ” profile for each type of Optical Trail (1). The values which can be selected are those defined in the Failure Gravity default Profile tab. (see § 12.2.9 -)


Note : (1) the modification will be applied to all the WDM Trails already created of

which Gravity Profile is in automatic mode (case “m anual” not ticked in Properties/Alarms tab of WDM Trail).

USERS MANAGEMENT


13. USERS MANAGEMENT

13.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.

13.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 13.1 : Window Admin View / Research tree

USERS MANAGEMENT


Figure 13.2 : Window Admin View / Users

Figure 13.3 : Window Admin View / Groups

USERS MANAGEMENT


Figure 13.4 : Window Admin View / Profiles

13.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 13.5 : Window Profile creation (1)

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.).

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 on ly visualize all the

network with animation of his domain (see Figure 13.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 13.8 : Window Topology View / Profile provid er access

Note: Three profiles are created by default: - Admin: with all the rights

- Operator: with all the rights except the administra tion - Observer: with rights in reading only.

13.2.2 - To create a group

This procedure is used to create a group of users.

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 [Group ] : the Group creation window (1) is displayed.

USERS MANAGEMENT


Figure 13.9 : Window Group creation (1)

Enter the group name in the « Group nam e » field.

Enter the group description in the « Group description » field.

In the « Profile nam e » 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 (wit h all the sub-networks contained in it).

A user in a group can only display the trails bel onging 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.

USERS MANAGEMENT


13.2.3 - To create a user

This procedure is used to create a user.

Caution : LDAP users must be defined in the LDAP Di rectory Service before to defined in IONOS-NMS

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 [User ] : the User creation window (1) is displayed.

Figure 13.11 : Window User creation (1) Figure 13.1 2 : Window LDAP User creation (1)

Caution : If the connection to a LDAP server is ena bled (see § 1.2.3.25 -), the check box LDAP user is ticked. The user should be defined in the L DAP 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 ena bled (see § 1.2.3.25 -), the LDAP user should

be created using the Name of the user defined in th e 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.

Figure 13.13 : Window User creation (2)

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 ena bled (see § 1.2.3.25 -), the password could be

not changed.


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.

13.2.4 - To display/modify the properties of a prof ile

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.

USERS MANAGEMENT


Figure 13.15 : Window Admin View / Profiles / Defin ition

If necessary, modify the profile name and the profile description (Definition tab).

Figure 13.16 : Window Admin View / Profiles / Autho rization

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.

USERS MANAGEMENT


13.2.5 - To display/modify the properties of a grou p

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.

USERS MANAGEMENT


Figure 13.17 : Window Admin View / Groups / Defini tion

If necessary, modify the group name, the profile and the domain (Definition tab).

Figure 13.18 : Window Admin View / Groups / Additio nal information

If necessary, modify the customized data (Additional information tab).

Click [Apply ] to validate the data changes.

USERS MANAGEMENT


13.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 13.19 : Window Admin View / Users / Definiti on

If necessary, modify the user name in the « User name field except for Ldap user .

Figure 13.20 : Window Admin View / Ldap Users / Def inition

USERS MANAGEMENT


Figure 13.21 : Window Admin View / Users / Password

If necessary, modify the password in the « Password » field except for Ldap user (Password tab).

Figure 13.22 : Window Admin View / Users / Addition al information

If necessary, modify the additional data (Additional information tab).

Click [Apply ] to validate the changes.

USERS MANAGEMENT


13.2.7 - To copy a profile



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

In the menu’s 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.


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.

13.2.8 - To copy a group



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

In the menu’s bar, click Edit > Copy/Paste : the following Group creation window is displayed.


In the « Group nam e » field, enter a new name for the group.

Select a new profile and a new domain if necessary.


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.

13.2.9 - To copy a user

Display the Admin View by clicking View > Admin View.


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.

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.


USERS MANAGEMENT


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.).

Click [Finish ] when you have finished : the new user appears in the list of users.

13.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.

Click [Yes] to validate the deletion.

13.2.11 - To delete a group



In the list, select the group which you want to delete.



13.2.12 - To delete a user



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



13.2.13 - To lock a user



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

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 d efault users can not be locked

A user locked can not open a session

13.2.14 - To unlock a user



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

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

IONOS SERVERS FEDERATOR


14. IONOS SERVERS FEDERATOR

14.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 EM S-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.

14.2 - DESCRIPTION OF IONOS SERVERS FEDERATOR

14.2.1 - The map of Federator

Figure 14.1 : Window Ionos Federator



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).

14.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 14.2 : Window Ionos Federator / Alarms



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.

14.2.3 - To filter current alarms of a server by cr iteria

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 14.3 : Window Ionos Federator / Alarms / Lis t

� 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) .



Figure 14.4 : Window Ionos Federaor / List configur ation

� 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 dis played in the list.



14.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.

14.2.5 - To open a IONOS-NMS Client on a server wit h 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 14.5 : Window Ionos Federator / Login on Cli ent

� 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.



14.2.6 - To force the connection of a server not co nnected

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 ).

14.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 ].

14.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 m anually 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

14.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 map, click right the server IONOS-NMS .

� In the pop-up menu, select [Stop Server ].

Note : In case of ADR10000 management, you have to stop ma nually 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

14.2.10 - To backup the database of a server

This procedure is used to backup the database of a server which is not stopped.




� 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 Iono s-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.

14.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 ].

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, 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.

14.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 map, click right the server IONOS-NMS.

� In the pop-up menu, select [Change 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).


14.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.

14.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 EMS-ADR.

Backup 1+1 is based on :



- 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.


Also, if the ssh protocol is used, it can be necess ary to configure the username and password of the SFTP server on the EMS-ADR serv er. (see § 1.2.3.30 - To configure ssh protocol with EMS-ADR (ADR10000).

14.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 t he IP address of EMS-ADR and the path of backup in EMS-ADR: /sdh_home/em s/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-A DR.

Each server “main” is described in the file “Federator.xm l” (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”.



� 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 a ddress of backup server. The IP

address of main server is removed from the table. T his update is not done for equipment of type ADR155C P2.6, and for all equipme nt inaccessible or in session locked.

Notes : In the following drawing the word FTP can be replaced by SFTP according your configuration



Server 1

EasyLauncher

NMSServer

Oracle

FTPserver

Server n

EasyLauncher

NMSServer

Oracle

FTPserver

Backup Server (alive or stopped)

EasyLauncher

NMSServer(stopped)

Oraclecontentnot used

FTPserver

...

Server 1

EasyLauncher

NMSServer

Oracle

FTPserver

Server i (alive or stopped)

EasyLauncher

NMSServer(stopped)

Oraclecontentnot used

FTPserver

Backup Server

EasyLauncher

NMSServer

Oracledatabaseserver i

FTPserver

...

Main server use

Backup server use

Client PC

Federator

Client PC

Federator

Server origin (alive or stopped)

EasyLauncher

NMSServer

Oracle

FTPserver

Server destination

EasyLauncher

NMSServer(stopped)

Oracleemptydatabase

FTPserver

Changing server main <->backup

Client PC

Federator

...

APPENDIX – SPECIAL FUNCTIONS UPON OBJECTS



Object Functions Menus

Sub-network

Copy Cut Delete Paste Properties Read / Write Rename

Edit

New Sub-Network Creation

Network element (NE)

Copy Cut Delete Paste Rename

Edit

New NE Creation 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

Action

Software Management NE Discovering

Tools

Links SDH

Delete Rename Properties Read / Write

Edit

Switch MSP Edit / Properties New STM-n Link Creation Activate MSP Add MSP De-Activate MSP Delete MSP Dissociate MSP NE extraction NE insertion Export XML Show Links RS Path trace configuration

Action

Links Ethernet

Delete Properties Read / Write

Edit




New Ethernet Link Creation Activate De-Activate Dissociate Show Links

Action

Links WDM

Delete Properties Read

Edit

New WDM Link Creation Activate De-Activate Dissociate Show Links

Action

Trails SDH


Edit

Switch SNC Edit / Properties New Trail Creation Activate De-Activate Dissociate Split / Merge Protection activation Protection de-activation Export XML Enable Real Time

Supervision Disable Real Time

Supervision

Action

VCGRoup

Delete Properties Read/Write

Edit

New VCGroup Creation Activate De-Activate Dissociate

Action

Ethernet Services

Delete Properties Read /Write

Edit

New Ethernet Service Creation Activate De-Activate Dissociate

Action

Trails WDM

Delete

Properties Read /Write Edit

New WDM Trail Creation Activate

De-Activate

Dissociate Action




MS-Spring


Edit

Switch MS-SPRing Edit / Properties New Ring Creation Activate De-Activate Dissociate

Action

Alarms

Properties Read Edit Propagation Edit/Properties Clear Acknowledge Export Unacknowledge

Tool-bar

Performances

Properties Read Edit

Users

Change password File

Applications

Forced backup File

Administration

User New user Creation Copy / Paste Delete Properties

Edit

Groups New groups Creation Copy / Paste Delete Properties

Edit

Profiles New profiles Creation Copy/Paste Delete Edit Properties

Preferences

Preferences Tools

Note : Whatever the object (Sub-network, NE, STM-Li nk, etc.), the Tools menu presents the same functions : preferences and soft ware management.

APPENDIX – USER PROFILE RIGHTS



User admin operator observer

System functions

Change password True True True Forced Backup True True False Preferences True True False Exit True True True

Sub-network functions

Cut True True False Copy True True False Paste True True False New Sub-network True True False Delete True True False Rename True True False Properties Read True True True Properties Write True True False

NE functions

Cut True True False Copy True True False Paste True True False New NE True True False Delete True True False Rename True True False Properties Read True True True Properties Write True True False Audit True True True Audit/Inventory NE to NMS aligns True True False Audit/NMS to NE parameters reapplication True True False Audit/NMS to NE reactivation True True False Equipment View / Read True True True Equipment View / Write True True False SNMP View / Read True True True SNMP View / Write True False False Force Polling True True True NE extraction True True False NE database backup True True False NE database restoration True False False Export XML True True True Software management True True False

Links SDH functions

New Link True True False Delete True True False Rename True True False Properties Read True True True Properties Write True True False NE insertion True True False Add MSP True True False Delete MSP True True False Dissociate MSP True True False Activate MSP True True False




Deactivate MSP True True False Switch command on MSP True True False Export XML True True True RS Path trace configuration True True False Show status NML view True False False

Links Ethernet functions

New Ethernet Link True True False Delete True True False Properties Read True True True Properties Write True True False Dissociate True True False Activate True True False De-activate True True False Links WDM functions

New WDM Link True True False Delete True True False Properties Read True True True Properties Write True True False Dissociate True True False Activate True True False De-activate True True False Show status NML view True False False Trails SDH functions

New Trail True True False Delete True True False Properties Read True True True Properties Write True True False Dissociate True True False Activate True True False DeActivate True True False Split / Merge True True False Protection Activation True True False Protection Deactivation True True False Switch command on SNC protection True True False Export XML True True True Visualize Real Time supervision True True False Enable Real Time supervision True True False Disable Real Time Supervision True True False Show status NML view True False False VCGroups functions

New VCGroup True True False Delete True True False Properties Read True True True Properties Write True True False Activate True True False DeActivate True True False Dissociate True True False Ethernet Services functions

New Ethernet Service True True False Delete True True False Properties Read True True True Properties Write True True False Activate True True False




De-Activate True True False Dissociate True True False

Trails WDM functions

New WDM Trail True True False Delete True True False Properties Read True True True Properties Write True True False Activate True True False DeActivate True True False Dissociate True True False Show status NML view True False False

MS-SPRING functions

New Ring True True False Delete True True False Properties Read True True True Properties Write True True False Activate True True False DeActivate True True False Dissociate True True False Switch command on Ring True True False

Alarms functions

Clear True True False Properties Read True True True Acknowledge True True False Unacknowledge True True False Propagation True True True Export True True True

Admin View functions

Admin View / Read True False False

Admin View / Write True False False

Log View functions

Event Log / Read True True True

Event Log / Purge True True False

Fault Log / Read True True True

Fault Log /Purge True True False

Server Log / Read True False False

Server Log / Purge True False False

Database Log /Read True False False

Database Log /Purge True False False

SDH trails Log / Read True True False

SDH trails Log / Purge True True False

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



� 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.



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.



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.



� 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.



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.



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



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.



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.

APPENDIX – Example of split/merge scenario


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

� Update the Ionos-NMS/config/oracle_ext_assembly.xml file: 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 :

� Update the Ionos-NMS/config/oracle_ext_assembly.xml file: Replace NMSSERVER by NMSSERVER_AP

� Perform an import of database: From the Ionos-NMS/bin folder run the command: > 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

� Update the Ionos-NMS/config/oracle_ext_assembly.xml file: Replace NMSSERVER_MERGE by NMSSERVER

� Perform an import of database: From the Ionos-NMS/bin folder run the command: > 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 configura tion


APPENDIX – Example of SNMP trap generator configura tion

See Below, an example of generation.xml file:

<generation> <netype> <Type value="ADR155C"/>  <Type value="ADR2500Extra"/> </netype> <distant> <IpAddress value="10.0.0.1/163"/> <IpAddress value="10.0.0.2/164"/> </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 nedatebegin="2009-10-01 05:00:00" nedateend="2009-12-31 09:00:00"/>

<filter nedatebegin="2010-01-02 05:00:00" nedateend="2010-03-31 09:00:00"/> <filter nmsdatebegin="2009-10-01 05:00:00" nmsdateend="2010-03-31 09:00:00"/> </filter-alarm> <filter-event> <filter nename="Paris"/> <filter nename="Lyon"/> <filter eventtype="Login"/> <filter location="" match="begin"/> <filter location="SESSION" match="exact"/> <filter nmsdatebegin="2009-12-31 05:00:00" nmsdateend="2010-03-31 09:00:00"/> </filter-event> </generation> Interpretation of the different filtering criterias: <generation> <netype> <Type value="ADR155C"/>  <Type value="ADR2500Extra"/> </netype> <distant> <IpAddress value="10.0.0.1/163"/> <IpAddress value="10.0.0.2/164"/> </distant> <filter-alarm> <filter nename="Dijon"/> OR

<filter nename="Paris"/> AND

<filter status="critical"/> OR

APPENDIX – Example of getTrailLongNames script usag e


APPENDIX – Example of getTrailLongNames script usag e

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 name[1]=My Trail Long Name 2 name[2]=My Trail Long Name 3 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 TrailLongName : end : nb = 1 : delay = 302 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 no trail for this alarm Searching for trails (1) : 741a9a4c1 name[0]=My Trail Long Name 4 Searching for trails (2) : 741a9a4c7 no trail for this alarm Searching for trails (3) : 741a9a4c8 no trail for this alarm .... TrailLongName : end : nb = 1 : delay = 1287 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 us er name’ result.

S

AG

EM

CO

M S

AS

H

eadquarters : 250, route de l’Em

pereur 92500 R

ueil-Malm

aison – France

ww

w.sagem

com.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_nms user guide 253153959-05

Documents

key ctrl pressed

indow trailbearerprotection

corba interface

ethernet multipoint

indow create

indow ne extraction

network background

indow ne insertion