Академический Документы
Профессиональный Документы
Культура Документы
6.4.7
Network Management System 5 UniX - B
User manual
MN.00247.E - 001
Volume 1/1
The information contained in this handbook is subject to change without notice.
Property of SIAE MICROELETTRONICA. All rights reserved according to the law and according to the inter-
national regulations. No part of this document may be reproduced or transmitted in any form or by any
means, electronic or mechanical, without written permission from SIAE MICROELETTRONICA.
Unless otherwise specified, reference to a Company, name, data and address produced on the screen dis-
played is purely indicative aiming at illustrating the use of the product.
MS-DOS, MS Windows are trademarks of Microsoft Corporation
HP, HP OpenView NNM and HP-UX are Hewlett Packard Company registered trademarks.
UNIX is a UNIX System Laboratories registered trademark.
Oracle is a Oracle Corporation registered trademark.
Linux term is a trademark registered by Linus Torvalds, the original author of the Linux operating system.
Linux is freely distributed according the GNU General Public License (GPL).
Other products cited here in are constructor registered trademarks.
NMS5UX-B
Contents
GENERAL DESCRIPTION 17
MAPS................................................................................................................................ 21
MENU BAR......................................................................................................................... 28
VIEW AREA........................................................................................................................ 34
Passing from one level to the other in the View area.......................................................... 34
Objects of the View area................................................................................................ 34
Background of the View area.......................................................................................... 34
OBJECTS ........................................................................................................................... 36
Graphic representation of the object: symbol ................................................................... 36
Symbol items: icon ....................................................................................................... 37
Symbol items: name ..................................................................................................... 38
Symbol items: check sign .............................................................................................. 38
Symbol items: notes ..................................................................................................... 39
Symbol characteristics: behavior .................................................................................... 39
Symbol characteristics: colour ........................................................................................ 40
EQUIPMENT WINDOW............................................................................................................ 47
NMS5UX USERS...................................................................................................................... 52
PROCEDURES 71
LOM/LCT ..........................................................................................................................116
Types of LOM/LCT-equipment connection: Monitoring, Configuration ..................................116
Indication of the presence of the LCT user to the NMS5UX user .........................................117
To enable/disable of the LCT-equipment connection in Configuration modality .....................117
REFRESH..........................................................................................................................137
To update the UX Map Manager window..........................................................................137
IMPORT/EXPORT ...............................................................................................................140
To copy the objects of a map/container to a different map/container ..................................140
To copy the objects, previously saved to file, into a map/container.....................................142
To save the objects of a map/container to a file ...............................................................142
To compare the objects of a map/container with the objects of a different map/container......143
To compare the objects, previously saved to file, with the objects of a map/container...........144
EXIT ................................................................................................................................147
ADD ................................................................................................................................149
To create Container objects ..........................................................................................149
To create NE object managed with SNMP protocol ............................................................150
NSAP (Gosip) Address ............................................................................................151
To create virtual NE objects managed with SNMP protocol.................................................152
To create NE objects managed with Legacy protocol .........................................................152
To create virtual NE objects managed with Legacy protocol ...............................................153
To create Generic Symbols (graphic symbols)..................................................................154
To create Link objects (connection) ................................................................................154
To create Label objects (wordings).................................................................................155
To create Container, NE (SNMP), Link and Label objects described in a file ..........................155
DELETE ............................................................................................................................156
To delete an object from the map ..................................................................................156
MODIFY/VIEW...................................................................................................................157
To verify/modify the parameters of a Container object......................................................157
To verify/modify the parameters of a Network Element object ...........................................157
To verify/modify the parameters of a Generic Symbol object .............................................158
To verify/modify the parameters of a Link object .............................................................159
To verify/modify the parameters of a Label object............................................................159
INFORMATION ..................................................................................................................160
To verify the information (marking status of the alarms, of the signalling of LCT presence,
Incorrect Upload and the notes) of a symbol ...................................................................160
To add/modify/delete the informative notes of a NE symbol ..............................................161
FIND................................................................................................................................163
To search a symbol in the map ......................................................................................163
ARRANGE SYMBOLS...........................................................................................................164
To align the symbols ....................................................................................................164
GENERATE INFO FOR WEB..................................................................................................165
To check the database information necessary to the RAN ..................................................165
PERFORMANCE..................................................................................................................... 171
LEGACY-ALARM AVERAGE...................................................................................................219
To display the mean of the alarms per second received by the NMS5UX-B system and
sent by the Legacy equipment.......................................................................................219
COMMAND............................................................................................................................ 241
CONNECT .........................................................................................................................244
To connect one or more equipment ................................................................................244
To connect the equipment of one or more containers........................................................244
DISCONNECT....................................................................................................................246
To disconnect one or more equipment ............................................................................246
To disconnect the equipment of one or more containers....................................................246
SNMP-FORCE NE DISCONNECT............................................................................................248
To force the software disconnection of one or more SNMP equipment .................................248
SNMP-PING ......................................................................................................................249
To executes the Ping of a SNMP equipment .....................................................................249
LEGACY-RESET&CONNECT ..................................................................................................250
To reset and connect one or more Legacy equipment .......................................................250
To reset and connect the Legacy equipment of one or more containers ...............................250
ALARM RE-ALIGNMENT.......................................................................................................252
To re-align the alarms of one or more equipment.............................................................252
To re-align the alarms of the equipment of one or more containers ....................................252
SNMP-CONFIGURATION DOWNLOAD....................................................................................256
To transfer the configuration of a SNMP equipment (virtual or real) to one or more
real SNMP equipment ...................................................................................................256
To transfer the configuration of a SNMP equipment (virtual or real) to one or more
virtual SNMP equipment ...............................................................................................258
NE ALARM HISTORY...........................................................................................................285
NE CURRENT ALARMS ........................................................................................................286
TOOLS.................................................................................................................................. 311
SNMP-NE MONITORING......................................................................................................321
To display the list of the measures .................................................................................321
To assign the parameters to monitor to an equipment (create a measure)...........................322
To display the characteristics of a measure .....................................................................323
To delete a measure ....................................................................................................323
To activate a measure ..................................................................................................323
To deactivate a measure ..............................................................................................323
To display the results of a measure ................................................................................324
To save the results of a measure ...................................................................................324
To display the results of a measure stored into a file ........................................................325
To save the results of a measure stored into a file............................................................325
To delete a file ............................................................................................................325
NE Monitoring functionality ...........................................................................................327
SNMP-RMON .....................................................................................................................337
To verify the statistics of an Ethernet port of a SNMP equipment (RMON statistics) ...............337
To activate an Ethernet port for the count of the RMON statistics .......................................339
To deactivate an Ethernet port from the count of the RMON statistics .................................340
To capture the RMON statistics of an Ethernet port in a specific instant ...............................340
To save the RMON statistics of an Ethernet port captured in a specific instant to file .............341
To display the history of the RMON statistics of an Ethernet port ........................................342
To activate an Ethernet port for the count of the history of the RMON statistics ....................345
To deactivate an Ethernet port from the count of the history of the RMON statistics..............345
To save the history of the RMON statistics of an Ethernet port ...........................................345
To verify the enabling and the criteria for the activation/deactivation of alarms relevant to
a counter (RMON statistics)...........................................................................................346
To enable and define the criteria for the activation/deactivation of an alarm relevant to
a counter (RMON statistics)...........................................................................................346
To disable an alarm relevant to a counter (RMON statistics) ..............................................347
Implementation of the RMON standard in the SNMP equipment managed by NMS5UX-B........348
Ethernet counters (RMON) ............................................................................................351
SNMP-XML EXPORT............................................................................................................353
To save the complete equipment configuration into a XML file............................................353
To display the active cronjobs (XML Export) ....................................................................355
To create a cronjob (XML Export)...................................................................................356
To delete one or more cronjobs (XML Export) ..................................................................356
To display the list of the XML files present in a given directory ...........................................356
To display the list of the Log files relevant to the creation of XML files ................................357
To display the list of HTML files obtained from the conversion of XML files ...........................358
To convert a XML file into a HTML file .............................................................................358
To display the content of a XML, Log or HTML file.............................................................358
To delete one or more XML, Log or HTML files .................................................................360
To send email with one or more XML, Log or HTML in attachment ......................................360
Function XML Export (more information).........................................................................361
OPTIONS.............................................................................................................................. 365
OVERVIEW .......................................................................................................................506
MANAGER .....................................................................................................................507
APPENDICES 508
NMS5UX-B SYSTEM
The NMS5UX-B system (Network Management System 5 Unix-B) has been developed to monitor and man-
age telecommunications equipment.
The user can communicate to the supervision system by means of a graphic window, called UX Map Man-
ager which represents the NMS5UX-B graphical interface at general level (see Fig.1).
The NMS5UX-B system has been developed to be used together with the UNIX operating system and
makes use of all the functionalities of this system.
Monitoring of the equipment connected to the system; dynamic displaying of the detection of an
alarm and recording into the alarm history (resident on the machine disk).
The displaying stored into the alarm history are related among them: the date/time of detection
and clearing of the alarm are indicated in the same record. The alarm history can be saved and re-
covered later.
Management of the alarm Log stored in the controller of the equipment: storing of the Log on the
machine, deletion of the Log from the controller.
Management and change of the severity level coupled to each equipment alarm.
Notification via e-mail of the alarm detection.
Management of the measures of Performance Monitoring (PM) of all the equipment connected to
the system:
Activation/deactivation of the measures also contemporary for more equipment of the same
type.
Check of the result of the measures in graphic format.
Store on disk/tape the results. Then, the data can be restored, displayed and saved (subdi-
vided by month) on a file. The saving operation can be executed for a single measurements
of a single equipment or for a measurement of all the equipment of the same type present
into the map.
Management of the equipment software: immediate or scheduled updating of the software of the
equipment connected to the system, check of the software versions.
Management of the equipment configuration: saving of the equipment configuration to file. Then,
it will be possible to transfer the configuration to any equipment present in the network.
Command Executor: program that executes predefined sequences of SNMP commands. The prede-
fined sequences of SNMP commands are provided at customers request by SIAE MICROELETTRO-
NICA.
List of the application programs (browser, manager, etc.), relevant to the NMS5UX-B system, on
progress at the choice of the command.
Possibility to require for or to force the closing of an application program on progress (browser,
manager, etc.) of the NMS5UX-B system.
List of the users connected with the supervisory system. Possibility to require for or to force the
disconnection procedure (logout) of an user. Possibility to forward messages to a single user or to
all the users connected with the supervisory system.
Management of the LCT user list stored for each single equipment.
Access to the system with 5 different user profiles which determine the available commands and
the functions.
The group of main applications manages the NMS5UX-B graphic interface at general level (UX Map Manager
window - Fig.1) through which the user can represent graphically the network, manage the connection,
check the operating status, the results of the measures of Performance Monitoring, etc. of the equipment.
At this level, the equipment is considered on its whole.
The equipment additional application (called <equipment type> Manager) as the task to provide, to the
NMS5UX-B interface, specific commands and functions with respect to the type of equipment that must be
managed.
Each equipment additional application manages a specific equipment graphic interface (pag.47/pag.48)
through which the user can, besides checking the operating status of the equipment, directly intervene in
its management checking or modifying the configuration parameters and verifying the quality parameters
of the signal. The NMS5UX-B supervision system can be provided with one or more Manager applications
according to the equipment types present in its own network.
The access to the graphic interface at general level takes place at the opening of the UX Map Manager win-
dow, while the access to the graphic interface at equipment level takes place opening the equipment win-
dow relevant to the equipment itself. The opening of an equipment window depends on the opening of the
UX Map Manager window.
The additional application Ring Manager (RM) has the task to provide the NMS5UX-B interface with the
commands and the functions specific for the configuration and the management of the network paths
(Path) among the PDH and SDH telecommunications equipment.
The Ring Manager application is composed by a part integrated in the menus of the graphical interface
NMS5UX-B (menu Ring Manager - pag.431) which allows representing, by means of the Ring objects, the
subnetworks of equipment which implement Path directly in the maps, verifying the functional status of
the NEs/Links/Paths present in the Ring objects and displaying the list of the objects Ring, Path and NE.
At this level, the Ring object is considered as a whole.
From the graphical object Ring, you can access the Ring Manager window (pag.50) which allows represent-
ing and managing the single equipment, Links and Paths present in a Ring object.
The opening of a Ring Manager window depends on the opening of the UX Map Manager window. Moreover
a Ring Manager window can be opened only by an enabled NMS5UX user (see pag.55).
The additional application VLAN Manager (VM) has the task to provide the interface NMS5UX-B commands
and specific functions for the configuration and the network-level management of virtual LAN paths (VLAN
paths) among the radio equipment with Ethernet tributaries.
VLAN Manager application is composed by a part integrated in the menus of the graphical interface
NMS5UX-B (menu VLAN Manager - pag.475) which allows representing, by means of the VLAN MAP ob-
jects, the subnetworks of equipment which implement VLAN paths directly in the maps, verifying the func-
tional status of the NEs present in the VLAN Map objects and displaying the list of the objects VLAN Map
and NE. At this level, the VLAN Map object is considered as a whole.
From the graphical object VLAN Map, you can access the VLAN Manager Map window (pag.51) which allows
representing and managing the single equipment, Links and VLAN paths present in a VLAN Map object.
The opening of a VLAN Manager Map window depends on the opening of the UX Map Manager window.
Moreover a VLAN Manager Map window can be opened only by an enabled NMS5UX user (see pag.55).
The additional application Remote Access NMS5UX (RAN) allows a NMS5UX user controlling and managing
the SNMP equipment connecting, via Internet, to his own NMS5UX-B system through his own PC and using
the installed O.S. and the browser.
The access to the servlet RAN takes place opening the Web page Remote Access NMS5UX, which can be
opened only by an enabled NMS5UX user (see pag.55).
The additional application Geographical Redundancy (GR) allows managing the redundancy of the maps
among the different NMS5UX-B systems in order to keep the supervision/management of the maps of a
malfunctioning system through a different NMS5UX-B or NMS5LX system.
With map redundancy we mean the management, by a NMS5UX-B or NMS5LX system, of all the equipment
associated to that specific map.
The GM application has been designed to work as part of the NMS5UX-B, in fact its interface is integrated
within the TMNMENU window (start menu) of the NMS5UX-B graphic interface.
The additional application P.M. Data Export allows exporting the results of the Performance Monitoring
measures relevant to all the SNMP equipment managed by the NMS5UX-B system.
The data are exported directly from the tables of the NMS5UX-B database to a file in TLFF format. This
operation can be both manually carried out by the user or set and periodic operation.
Moreover the application allows re-importing the data previously saved to file into the Oracle table of PM.
The P.M. Data Export application is not provided with a graphic interface but its implementation is executed
by typing specific commands in the command line of a terminal window.
The additional application Proxy Agent allows dispatching the alarm traps, relevant to all the equipment
managed by ones NMS5UX-B system, to an higher level Central Element Manager.
The Proxy Agent application is, in part, integrated into the NMS5UX-B graphic interface (setting, at level
of single equipment, of the address of the machine, which the Proxy Agent sends the traps coming from
the equipment to) and, in part, integrated in the TMNMENU window (start menu) of the NMS5UX-B graphic
interface (activation, deactivation and management of the Proxy Agent application).
This manual describes the use of the NMS5UX-B graphic interface at general level (UX Map Manager
window).
The use of the equipment graphic interface changes depending on the type of equipment which is referred
to. It is reported in the relevant user manuals.
For the description and use of the additional application:
RM, VM, RAN and GR, refer to relevant documentation.
PM Data Export, refer to the relevant technical specifications.
Proxy Agent, refer to pag.150/pag.152 (setting of the Proxy address of the equipment) and to
the administrator manual (management of the Proxy Agent application).
The NMS5UX-B system allows associating a map to each single NMS5UX user. More user can be associated
to the same map.
At the opening of the UX Map Manager window (Fig.1), the map associated to the user that executed the
operation opens.
The whole equipment network or a portion of it can correspond to a map. In this second case, the user
which the map is associated to, will receive only notifications coming from the equipment contained in his
portion of network.
To manage an equipment it is necessary to create a graphic symbol that represents it. The same symbol
can be created in more maps (creation of more copies of the symbol). In this way, the equipment data are
not duplicated in the database, but all the copies access to the same information.
Then, it is possible to save objects of a map into a file and export/import object of a map to another one.
The NMS5UX-B system release 6.4.7 is able to manage at the same time equipment that use as equipment-
supervisory system communication protocol the following one:
The SNMP standard protocol (Simple Network Management Protocol). Into the manual, such
equipment are called equipment managed with the SNMP protocol (SNMP equipment).
A proprietary protocol. Into the manual, such equipment are called equipment managed by the
Legacy protocol (Legacy equipment).
ALplus node
Set of minimum 2 and maximum 3 equipment ALplus interconnected by Nodal Bus.
ALCplus2 node
Set of minimum 2 and maximum 8 equipment ALCplus2 interconnected by a Nodal Bus (TDM
traffic) and/or by LAN (Ethernet traffic).
FAMxc 5 RU multiplexer
FAMxc 2.5 RU multiplexer
ADM1 multiplexer
EXP63 multiplexer
ADMC multiplexer
CommServerS (CS)
IPBOX
The information contained in this manual refers to the system and the NMS5UX-B graphic interface release
6.4.7.
The release can be checked at the opening of the graphic interface (Login window) or selecting the Help
> About NMS5UX-B (pag.500).
The detail of the hardware and software requirements required by the NMS5UX-B system is reported in the
administrator manual.
The maximum number of equipment that can be contemporarily managed by the NMS5UX-B system de-
pends on the codeword required by the customer.
The maximum number of NMS5UX users that can open the UX Map Manager window (Fig.1), using the
same map or different maps, depends on the codeword required by the customer.
At the start of the NMS5UX-B graphical interface the UX Map Manager window opens. The window is dis-
played in Fig.1. The elements that compose the window are:
First time the UX Map Manager window of a new map opens, the Map and View areas are empty (unless
the system has been previously configured by SIAE MICROELETTRONICA). In this case, before connecting
the equipment, it is necessary to graphically represent the network in their own map (pag.78).
The NMS5UX-B graphic interface has been developed to be used in Unix environment, therefore it respects
the conventions - relevant to the menu arrangement, the window style, the use of the keyboard, of the
mouse and so on - typical of this operating system.
OGGETTI
MAP area STATUS bar NEW OBJECT area VIEW area PLATFORM STATUS bar
Menu:
Map (pag.136). It contains the commands for the management of the map: to update the data,
to resize the symbols, to manage the background, to change/delete the map, to export/import
the elements of a map to/from another one and to save on a file all the symbols (container, NE,
etc.) present into a map.
Edit (pag.148). It contains the commands for the management of the objects: creation, modi-
fication, deletion, search, alignment.
View (pag.167). It contains the commands to hide/show the elements of the UX Map Manager
window.
Performance (pag.171). It contains the commands for the management of the measures of
Performance Monitoring (PM) of the equipment.
Configuration (pag.184). It contains the commands to check the status/operation of an equip-
ment and the configuration of the software/hardware of the equipment.
Locate (pag.220). It contains the commands to display and manage, in table format, the equip-
ment.
Command (pag.241). It contains the commands for the management of the connection be-
tween the equipment and the NMS5UX-B system and for the execution of the download of the
configuration of an equipment to another equipment.
Fault (pag.263). It contains the commands for the management of the equipment alarms and
for the display of the history of the operations executed by the NMS5UX users.
Tools (pag.311). It contains the commands to start the Command Executor application, for the
management of the alarm notification via e-mail, to manage the periodic monitoring of param-
eters, to manage the statistics of the Ethernet tributaries, to manage the Auto Discovery and
XML Export functionality.
Options (pag.365). It contains the commands for the management of the alarm severity, of the
NMS5UX-B/LCT users, of the list of remote equipment and the commands for the updating of
the equipment software.
Misc (pag.422). It contains the commands to save/recover/delete from disk/tape the alarm his-
tory, the results of the PM measures and the system database.
Ring Manager (pag.431). It contains the commands for the management of the Ring objects.
The menu is available only if the Ring Manager application is installed. For the use, refer to the
relevant documentation.
VLAN Manager (pag.475). It contains the commands for the management of the VLAN Map
objects.
The menu is available only if the VLAN Manager application is installed. For the use, refer to the
relevant documentation.
Help (pag.499). It contains the commands to open the on-line manuals of the supervisory sys-
tem and to check the list of the software programs that constitute the NMS5UX-B software pack-
age.
Each item, if selected, opens a cascade menu that lists a series of commands.
Some commands immediately execute the action associated to them, others open further cascade menus
(items followed by ).
When a command is displayed greyed out, instead of white, it means that it is not available.
The deactivation of a command can depend on the type of access to the map (pag.63), on the equipment
type or one's user profile (pag.57)does not foresee the use of the command or, even, to make the com-
mand available it is necessary to execute before another action as, for example, to select a symbol.
This bar points out the window name, which can be configured by the superuser. By default, the name is
<company name - UX Map Manager>.
For description convenience, in this manual the main window of the graphic interface of the NMS5UX-B
system is identified by the wording UX Map Manager.
It aligns two or more objects vertically * Edit > Arrange Symbols > Vertical (pag.164)
It aligns two or more objects horizontally * Edit > Arrange Symbols > Horizontal (pag.164)
It hides/displays the labels of the Link objects View > Show/Hide Link Label (pag.170)
(pag.81)
It hides/displays the Map area (pag.32) View > Show/Hide Map Tree (pag.168)
It hides/displays the platform status bar View > Show/Hide Platform Status (pag.169)
(pag.45)
It creates a new SNMP equipment Edit > Add > Network Element > SNMP Managed
(pag.149)
It displays the list of the equipment Locate > Equipment List Locate (pag.221)
It displays the results of the PM measures for Performance > Performance Monitoring (pag.173)
the selected NE **
It displays the alarm history Fault > Network Alarm History (pag.264)
It displays the list of the alarms active on the Fault > Network Current Alarms (pag.273)
equipment
It executes the Line Test for the selected NE *** Command > Line Test > Network Element
(pag.242)
It connects the selected equipment *** Command > Connect > Network Element
(pag.244)
It disconnects the selected equipment *** Command > Disconnect > Network Element
(pag.246)
It re-aligns the alarms and the configuration for Command > Configuration Upload > Network Ele-
the selected equipment *** ment (pag.254)
It re-aligns the alarms for the selected equip- Command > Alarm Re-alignment > Network Ele-
ment *** ment (pag.252)
It reduces the graphic symbols size in the View Map > Map Properties (pag.138) (20 pixel)
area (Zoom 40%)
It restores the average size of the graphic sym- Map > Map Properties (pag.138) (38 pixel)
bol in the View area (Zoom 70%)
It enlarges the graphic symbols size in the View Map > Map Properties (pag.138) (50 pixel)
area (Zoom 100%)
The Map area is the part of the UX Map Manager window (Fig.1) where the map objects, created by the
user to represent the equipment network, are displayed (except for the Link and Label objects).
The displaying of the map is of tree type, in order to represent also the hierarchical links among the dif-
ferent items.
The Map: test map level (see Fig.2) represents the highest hierarchical level: Map level. It is automatically
created on the creation of the map and its name corresponds to the name assigned by the user to the map.
This level cannot be deleted using the commands present in the UX Map Manager window, it is automati-
cally deleted on the deletion of the map.
The lower levels are represented by containers that can contain more NE (pag.79), Generic Symbol
(pag.81), Link (pag.81), Label (pag.81), Container (pag.79), Ring (pag.81) and VLAN Map (pag.81) ob-
jects. The presence of a Container object automatically creates a hierarchically lower level (child level) with
respect to the current level (parent level) as shown in Fig.2.
The subdivision of the equipment network into containers, and then into levels, allows creating areas where
grouping the equipment and items related by some characteristics, for example geographical or other.
In this way, when a Container object is selected, in the View area (pag.32) only the elements present in
the container will be displayed and not all the network elements.
In fact, the selection of a container (or of an element contained in it) changes the content of the View area.
All the objects present in the same level are listed in the area Map in alphanumeric order.
Each container (except for the Map level) has the + or - symbol, displayed one alternatively to the other
(see Fig.2). Symbol:
+. The elements present in the container are not displayed in the Map area under the container
itself (collapsed list).
-. The elements present in the container are displayed in the Map area under the container itself
(expanded list).
The user (independently from its operating level or access type) can anytime display or hide the Map area
(pag.33).
Map
container
Child level of the
Map container
To pass to the:
Higher level (parent level), with respect to that selected and represented in the View area
(pag.32) press or select the container that represents the wished higher level.
Lower level (child level), with respect to that selected and represented in the View area, select
the container that represents the wished lower level.
To pass to the main window of the map (Map level) press or select the Map: container.
The characteristics of the objects present in the Map area: symbol, check sign, note sign, colour, etc. are
described in the par. Objects (pag.36).
2. Select the View > Show/Hide Map Tree command or press again to display the area again.
The View area is the part of the UX Map Manager window where the objects present in the container, se-
lected in the Map area (pag.32), are displayed.
For example in Fig.1, if the Venice container is selected in the Map area, the NE objects ADM1, AL E/W,
AL-P1 and the possible Link and Label objects (objects that are not displayed in the Map area) will be dis-
played in the View area.
The selected container, once selected the level displayed in the View area, is indicated above the area itself
in the Contents of Map: field.
For example, in Fig.1, the Contents of Map: test map/Venice field points out that the objects represented
in the View area are present in the test map (parent level) and in the Venice container (current level).
To pass to the:
Higher level (parental level), with respect to that represented in the View area, press .
Lower level (child level), with respect to that represented in the View area, double click on the
container that represents the level you wish to access.
The characteristics of the objects present in the View area: symbol, check sign, note sign, colour, etc. are
described in the par. Objects (pag.36).
It is possible to associate a background to each container, in such a way that, on its selection, the back-
ground is displayed in the View area besides the symbols present in the container (pag.139).
The new objects are parked in this area after their creation, waiting for their positioning by the user inside
the View area (pag.34).
An object is the representation, in the graphic interface of the NMS5UX-B system, of a network element.
The NMS5UX user must consider each part of the network as an object. For example, the network on its
whole is an object, the container (sub network, station, sub-station) where the equipment are located is
an object, each single equipment is an object.
An object can be:
Created - see Edit > Add (pag.149), Tools > SNMP-Auto Discovery (pag.328), Ring Manager >
Edit > RM-Add Ring (pag.432) and VLAN Manager > Edit > VM-Add VLAN Map (pag.476) com-
mand.
Deleted - see Edit > Delete (pag.156), Ring Manager > Edit > RM-Delete Ring (pag.433) and
VLAN Manager > Edit > VM-Delete VLAN Map (pag.477) command.
Modified - see Edit > Modify/View (pag.157), Ring Manager > Edit > RM-Modify/View Ring
(pag.434) and VLAN Manager > Edit > VM-Modify/View VLAN Map (pag.478) command.
Moved. To move an object, it is sufficient to select it and, keeping pressed the left mouse but-
ton, bring it to the new position.
In the Map area (pag.32), it is possible to move the objects from a container to the other. In
the View area (pag.34) it is possible to put the object in a new position inside the area (contain-
er). Furthermore, it is possible to select an object in the View area and drag it into a container
of the Map area or vice versa.
All the created objects and the relevant values of the parameters are stored into the database of the
NMS5UX-B system. They will be stored until the user deletes the object.
The NMS5UX-B system has a series of predefined objects, which allow the user drawing his network and
providing to the system all the information necessary for the supervision and the monitoring of each single
equipment.
In details, Container (pag.79), Network Element (NE) (pag.79), Generic Symbol (pag.81), Link (pag.81),
Label (pag.81), Ring (pag.81) and VLAN Map (pag.81) objects.
On the creation/deletion/modification/move of an object:
Container, NE, Generic Symbol, Ring or VLAN Map the object is represented/deleted/changed/
moved both in the Map area and in the View area.
Link or Label, the object is represented/deleted/changed/moved only in the View area.
When an object is created, its graphic representation in the map is the symbol.
More symbols can correspond to an object. In fact, if the same object is created more times, we do not
create a new object but simply a copy of its graphic representation, then a new symbol is created. The
symbol of the same object can be created more times in the same map or in other maps as shown in Fig.3.
In the system database, on the creation of the object, the relevant parameter are stored. On the creation
of the next copies (symbols) of the object, the values of the parameters are not inserted again, but the
values already present in the database are used.
To execute an operation, often it is necessary to select the symbol (or the symbols) which you wish to
operate on. The selected symbol is characterized by a dark grey square. It will remain selected until the
user selects another symbol.
It is possible to select one or more symbols at the same time pressing the left mouse button and drawing
an area containing the interested symbols or keeping pressed the Ctrl key selecting the symbols.
Container 1 Container 1
Information
relevant to
object A in Object A
the database
All the objects of the NMS5UX-B system, except for the Label object, has a its own icon.
Tab.2 points out the symbol and the relevant icons represented in the Map (pag.32) and View (pag.34)
areas.
Icon
Symbol Icon (View area)
(Map area)
Container
-
Map
Container
...
Generic
Symbol
.....
Link
-
Label -
Ring
VLAN Map
ELFO radio ALFO radio SDH N+1 radio FAMxc 5 RU Mult. FAMxc 2.5 RU Mult.
ADM-C Multiplexer ADM-1 Multiplexer EXP63 Multiplexer PMP System COMM. SEVER-S
LEGACY equipment
The name (or label) is the string of characters displayed under the icon (View area - pag.34) or next to the
icon (Map area - pag.32).
All the objects of the NMS5UX-B system has a name defined on the creation of the object. For all the objects
the name can be modified later.
For the Link objects, it is possible to hide the name (see pag.154/pag.159).
For the Ring objects, the name represents the title of the window opened by the double selection of the
relevant symbol.
For the VLAN Map objects, the name represents a part of the title of the window which is opened on the
double selection of the relevant symbol (window title <VLAN Map object name> - VLAN Manager Map).
The check sign is an item that characterizes only the Container and Network Element objects, except for
the virtual Network Elements.
The check sign next to the icon points out that there is at least ONE of the listed condition.
It is possible to check the status of each condition in the Equipment Browser [List/Locate] win-
dow (Fig.36) and Information window (Fig.23).
By default, the symbol points out the status of the condition listed above.
It is possible to modify the list of the conditions associating the presence (or absence) of to
two or to only one of the above mentioned conditions. For example, it is possible to associate to
the check sign only the condition of failed Configuration Upload. The change can be made only
by the Superuser. More information is reported in the administrator manual.
The absence of the check sign points out that:
All the (current or historic) alarms of the equipment have been marked.
LCT has not been connected in Configuration modality from the last time that the NE
equipment window has been opened.
The last operation of Configuration Upload to the equipment has been successfully exe-
cuted.
For the Network Element of ALplus Node type or ALCplus2 Node type objects:
The presence of the check sign points out that at least an NE with is present in the node.
The absence of the check sign points out that no equipment with is present in the node.
The note symbol ( ) is an item that characterizes only the Network Element objects. With details:
The presence of the note symbol points out that there is an informative note written by the user
associated to the symbol.
It is possible to see (modify/delete) the note opening the Information window (Fig.23).
The absence of the note symbol points out that there is no informative note associated to the
symbol.
The behavior represents the action that is executed when a symbol is selected twice in fast sequence in
Map (pag.32) or View (pag.34) area.
Tab.3 displays for each object the relevant behavior.
Container It displays in the View area the objects present in the container (child level)
NE ALplus Node type If connected at least once, the ALplus nodal window opens (pag.48)
NE ALCplus2 Node type If connected at least once, the ALCplus2 nodal window opens (pag.49)
The WEB page opens (via the default browser) available at the address set for the
NE WEB Generic type
specific object.
* For virtual SNMP equipment, the equipment window is opened only if the configuration of a (real or vir-
tual) NE of the same type has been transferred to the considered virtual equipment (see pag.79 and
pag.256).
The colour of the icon identifies the connection status or the alarm status of the symbols contained in it.
Tab.4 displays, for each object, the colours that be assumed by the relevant icon and the description of
the condition represented by them.
Green In the container there is at least one equipment in connected status. No NE has
alarms.
Light blue In the container there is at least one equipment in connected status where at least
one alarm of Warning severity is active.
Yellow In the container there is at least one equipment in connected status where at least
one alarm of Minor severity is active.
Orange In the container there is at least one equipment in connected status where at least
one alarm of Major severity is active.
Red In the container there is at least one equipment in connected status where at least
one alarm of Critical severity is active and/or one NE in unreachable status.
Green The equipment is in connected status (pag.114) and does not present any alarm.
Light blue The equipment is in connected status and at least one alarm of Warning severity is
present.
Yellow The equipment is in connected status and at least one alarm of Minor severity is
present.
Orange The equipment is in connected status and at least one alarm of Major severity is
present.
Red The equipment is in connected status and at least one alarm of Critical severity is
present.
White *** The LCT program in Configuration modality is connected to the equipment.
NE ALplus Node Brown All the equipment in the node are in disconnected status
type*
Green All the equipment in the node are in connected status. No equipment has alarm.
Light blue All the equipment in the node are in connected status. The most serious alarm
present on the equipment of the node is Warning.
Yellow All the equipment in the node are in connected status. The most serious alarm
present on the equipment of the node is Minor.
Orange All the equipment in the node are in connected status. The most serious alarm
present on the equipment of the node is Major.
Red All the equipment in the node are in connected status. The most serious alarm
present on the equipment of the node is Critical.
Or
In the node there is at least one equipment in unreacheable status.
Red with X All the equipment in the node are in unreachable status.
Pink *** In the node there is at least one equipment in maintenance status.
White *** In the node there is at least one equipment which the LCT program in Configuration
modality is connected to.
NE ALCplus2 Node Brown All the equipment in the node are in disconnected status
type*
Green All the equipment in the node are in connected status. No equipment has alarm.
Light blue All the equipment in the node are in connected status. The most serious alarm
present on the equipment of the node is Warning.
Yellow All the equipment in the node are in connected status. The most serious alarm
present on the equipment of the node is Minor.
Orange All the equipment in the node are in connected status. The most serious alarm
present on the equipment of the node is Major.
Red All the equipment in the node are in connected status. The most serious alarm
present on the equipment of the node is Critical.
Or
In the node there is at least one equipment in unreacheable status.
Red with X All the equipment in the node are in unreachable status.
Pink *** In the node there is at least one equipment in maintenance status.
White *** In the node there is at least one equipment which the LCT program in Configuration
modality is connected to.
NE WEB Generic type Brown The colour is fixed and does not point out any status condition.
NE (virtual) Brown The colour is fixed and does not point out any status condition.
Generic Symbol Blue The colour is fixed and does not point out any status condition.
Link Black The colour is fixed and does not point out any status condition.
Label Black The colour is fixed and does not point out any status condition.
Green In the Ring there is at least one equipment in connected status. No NE has alarms.
Light blue In the Ring there is at least one equipment in connected status where at least one
alarm of Warning severity is active.
Yellow In the Ring there is at least one equipment in connected status where at least one
alarm of Minor severity is active.
Orange In the Ring there is at least one equipment in connected status where at least one
alarm of Major severity is active.
Red In the Ring there is at least one equipment in connected status where at least one
alarm of Critical severity is active and/or one NE in unreachable status.
Green In the VLAN Map there is at least one equipment in connected status. No NE has
alarms.
Light blue In the VLAN Map there is at least one equipment in connected status where at least
one alarm of Warning severity is active.
Yellow In the VLAN Map there is at least one equipment in connected status where at least
one alarm of Minor severity is active.
Orange In the VLAN Map there is at least one equipment in connected status where at least
one alarm of Major severity is active.
Red In the VLAN Map there is at least one equipment in connected status where at least
one alarm of Critical severity is active and/or one NE in unreachable status.
* By default the color of the icon always reflects the colour of the (contained) object where the most serious
condition is present.
** By default, the colour of the icon always reflects the colour of the most serious alarm present on the
equipment.
*** This condition is not propagated to the icons of the Containers that contain the NE.
The Map: container (Map level) present in the Map area (pag.32) of the UX Map Manager window is
not provided with the right button function.
Selecting a symbol and pressing the right mouse button, a context menu is displayed where the following
commands are present:
Open. If selected a:
Real NE (connected at least once) opens the equipment window (pag.47).
NE ALplus Node type (connected at least once) opens the ALplus nodal window (pag.48).
NE ALCplus2 Node type (connected at least once) opens the ALCplus2 nodal window
(pag.49).
NE WEB Generic type opens the WEB page (via the default browser) available at the ad-
dress set for the specific object.
Virtual NE opens the equipment window (pag.47).
The heading of the context menu points out the name of the selected symbol.
The user (independently from his operating level or from the type of access to the map) can, in
any moment, display/hide the names of the Link objects (see pag.170).
At the opening of the UX Map Manager window, independently from its previous setting, the
display of the names of the Link objects is active (the wording [Link Label Off] is not present).
The colour of the NMS5UX, PROXY, RING and VLAN box points out the status of the specific process:
Green. The process is active and operates correctly.
Red. The process is inactive or it does not operate correctly.
In this condition, the function implemented by the process will be not execute (for example, the
alarms or the PM are not collected for the process relevant to NMS5UX).
Call one's network administrator in order to re-activate the process.
Gray. The modules for the management of the relevant processes are not installed.
A double click of the left mouse button on a box allows checking the status of the relevant process.
The colour of the boxes Alr History Usage and Transaction Log Usage points out the occupation status of
the records in the relevant tables with respect to the maximum available status.
The maximum available status, considered as number of records which can be stored in each table, and
the occupation thresholds which determinate the status can be set by the Superuser. With reference to the
default values of the thresholds, the meaning assumed by the status colours are the following:
Green. The records present in the specific table occupy less than 70% of the available space.
Blue. The records present in the specific table occupy more than 70% but less than 75% of the
available space.
Yellow. The records present in the specific table occupy more than 75% but less than 80% of
the available space.
Orange. The records present in the specific table occupy more than 80% but less than 90% of
the available space.
Red. The records present in the specific table occupy more than 90% of the available space.
In this condition a message is periodically displayed, warning about the critical situation.
The display of the message and the frequency which it is displayed at can be configured by Su-
peruser. Default: message display active, frequency: 60 seconds.
The user (independently from its operating level or access type) anytime, can display or hide the platform
status bar.
At the opening of the UX Map Manager window, independently from its previous setting, the platform status
bar is NOT displayed.
2. Select the View > Show/Hide Platform Status command or press again to hide the bar again.
The choice of a Network Element object allows accessing to the graphic interface at equipment level, level
represent by the equipment window.
At this level, the user can enter into the equipment to check and modify the configuration parameters, to
execute maintenance and test operations.
Each type of equipment, that can be currently managed by the NMS5UX-B system, is characterized by its
own equipment window.
The detailed description of each single equipment window and of the objects which it contains is reported
in the relevant Equipment user manual (see pag.507).
The management of each single equipment window is made from a specific application, called <equipment
type> Manager. These application are part of the NMS5UX-B system and are provided on request.
The equipment window of a NE can be opened by more users at the same time (see pag.67).
The first user that opens the window can check/modify the configuration parameters (Read-Write access).
The other users can only check the parameters (Read Only access).
What just said is valid only for the Superuser and the users with privileged or advanced profile. The
normal and entry users has always Read Only access to the equipment window, even if they are the first
to open it.
In the equipment window with Read Only access, the alarms will not be dynamically updated, it is neces-
sary to require the updating selecting a proper command.
The equipment window can be opened only if the NE has been connected at least once.
What just said is valid only for the objects that represent real equipment.
For the virtual SNMP NEs, the equipment window can be opened after having transferred, at least once,
the configuration of a (real or virtual) NE of the same type to the considered virtual equipment. Instead,
for the virtual Legacy NEs, the equipment can be always opened (see pag.79).
The selection of a NE object of type WEB Generic does not open the equipment window, because this
object does not represent a real equipment (see pag.80).
The selection of a Network Element object of ALplus Node type allows accessing the graphic interface at
level of ALplus nodal system.
At this level, the user can enter into the node to verify the status and execute operations on the single
equipment constituting the ALplus nodal system as some commands, generally available for the NE objects
in the UX Map Manager window, are present in the nodal window for the node equipment.
Moreover, it is possible to access to the graphic interface of the single equipment only via the nodal win-
dow. In fact, it is not possible to create in the map a NE object of an equipment which is part of a nodal
system. It is automatically created in the database of the NMS5UX-B system when the ALplus Node NE
object is created.
The definition of node (equipment forming the node, relevant IP address, etc.) MUST be carried out at
local level via the SCT/LMT application. For more information, refer to the relevant documentation.
The detailed description of the ALplus nodal window is reported in the user manual ...ALplus Node Manager
(see pag.507).
The selection of a Network Element object of ALCplus2 Node type allows accessing the graphic interface at
level of ALCplus2 nodal system.
At this level, the user can enter into the node to verify the status and execute operations on the single
equipment constituting the ALCplus2 nodal system as some commands, generally available for the NE ob-
jects in the UX Map Manager window, are present in the nodal window for the node equipment.
Moreover, it is possible to access to the graphic interface of the single equipment only via the nodal win-
dow. In fact, it is not possible to create in the map a NE object of an equipment which is part of a nodal
system. It is automatically created in the database of the NMS5UX-B system when the ALCplus2 Node NE
object is created.
The definition of node (equipment forming the node, relevant IP address, etc.) MUST be carried out at
local level via the SCT/LMT application. For more information, refer to the relevant documentation.
The detailed description of the ALCplus2 nodal window is reported in the user manual ...ALCplus2 Node
Manager (see pag.507).
The selection of a Ring object allows accessing to the graphic interface of the Ring Manager application:
Ring Manager window.
This application has been developed to create, configure and manage the paths among SDH and PDH
equipment. A Path is a bidirectional connection between a source node and a destination node and is iden-
tified by an input channel on the source node and an output channel on the destination node.
The Ring Manager application is integrated in the NMS5UX-B system and supports the SNMP equipment
(Network Element) already managed by the supervision system.
The Ring Manager window, relevant to the same Ring object, can be opened by only one user at a time
(see pag.69).
The detailed description of the Ring Manager window and of the objects contained in it is reported in the
relevant user manual (see pag.507).
The selection of a VLAN Map object allows accessing to the graphic interface of the VLAN Manager appli-
cation: VLAN Manager Map window.
This application has been developed to create, configure and manage the virtual LAN paths (VLAN path)
among radio equipment with Ethernet tributaries.
The VLAN Manager application is integrated in the NMS5UX-B system and supports the SNMP equipment
(Network Element) of the ALS (AL, ALC, ALS, ALS-C, ALplus, ALCplus, ALplus2, ALCplus2) and ALFO series
already managed by the supervision system.
The VLAN Manager Map window, relevant to the same VLAN Map object, can be opened by only one user
at a time (see pag.70).
The detailed description of the VLAN Manager window and of the objects contained in it is reported in the
relevant user manual (see pag.507).
The NMS5UX-B graphic interface can be started at the same time on more PCs or terminals connected by
an Ethernet connection.
In this way, the displaying of the information relevant to the equipment network is contemporaneous for
all the terminals and the insertion of the data or the sending of the commands by one user is possible from
all the terminals.
To open a copy of the NMS5UX-B graphic interface, it is necessary to have a NMS5UX user.
The supervision system is provided with a predefined NMS5UX user (see pag.54). In a second moment, it
will be possible to create all the wished NMS5UX users (see pag.374).
The NMS5UX-B system has been developed to be used with the Unix operating system.
For each NMS5UX user you want to create, it is necessary to create a Unix user. There is a specific con-
nection between them: it is possible to associate a single NMS5UX user to a Unix user.
Then, before creating the NMS5UX user, it is necessary to create the relevant Unix user.
The username and the password defined at the creation of the Unix user will be automatically used by the
supervision system during the creation of the NMS5UX user.
It is not necessary to create a Unix user for the Superuser (predefined NMS5UX user provided with the
supervision system - pag.54) because during the installation of the NMS5UX-B system a Unix user with
nms5ux username and password is created, which a NMS5UX user with nms5ux username and password
is associated to.
During the installation of the system, a NMS5UX user is created with the following characteristics:
Username - nms5ux
Password - nms5ux
map - nms5ux
Profile - Superuser
Timeout password - Not expired
Internet - Active (if required by the user the RAN application (see pag.19).
Ring/VLAN - Active (if required by the user the relevant application: Ring Manager/VLAN Man-
ager (see pag.19).
Each NMS5UX user is characterized by an username (pag.55), a password (pag.55), a map (pag.56), a
profile (pag.57), the Internet enabling (pag.58) and the Ring/VLAN enabling (pag.58).
The username and the password allow to the system acknowledge the user as NMS5UX user authorized
to start the graphic interface.
The same NMS5UX user can open more NMS5UX-B graphic interfaces (on different PCs/terminals or on the
same) using the same username and password.
A map is associated to each user. The supervision system, at the start-up of the NMS5UX-B interface, au-
tomatically opens the map associated to the user that executed the operation.
The profile allows starting the NMS5UX-B graphic interface and having determinate commands and func-
tions available.
The Internet enabling allows the use of the RAN application (optional) (see pag.19).
The Ring/VLAN enabling allows the use of the (optional) applications Ring Manager and/or VLAN Manager
(see pag.19).
Username
If for ones system the function of manual Login to the UX Map Manager window is active (pag.61), at
the creation of the NMS5UX user, an username different from that of the relevant Unix user can be defined.
Moreover, in this condition the name of the NMS5UX user can be modified (operation available only for the
Superuser).
Password
If for ones system the function of manual Login to the UX Map Manager window is active (pag.61), at
the creation of the NMS5UX user the user password must be defined.
Then the Superuser can modify its password and the passwords of all other NMS5UX users. If an user
should forget his password, it is necessary to call SIAE MICROELETTRONICA.
The privileged, advanced, normal or entry users can modify their own password. If an user should forget
his password, the Superuser can define a new one.
The expiry of the password is managed by the operating system Unix according to the modes reported in
the relevant documentation.
Only if, for ones system, the function of manual Login to the UX Map Manager window (pag.61) is ac-
tive, the management of the expiry of the password is executed, only for the NMS5UX users, by the
NMS5UX-B system as described here below.
The activation of the periodic password change does not influence the expiry date of the user, which can
be set during the creation of a NMS5UX user. The two functionalities are independent and can coexist at
the same time.
Map
The map corresponds to a network or to the network part graphically represented and managed by the
system. It can be arranged by the user according to his needs.
Each map has its own UX Map Manager (Fig.1).
The NMS5UX-B system can manage more maps at the same time.
The map, where he can operate, is associated to each NMS5UX user.
The access to a map is made via the start of the NMS5UX-B graphic interface: automatically, the system
opens the map associated to the NMS5UX user who required the start of the graphic interface.
It is possible to associate, on the creation of the user, to each NMS5UX user, a map that will constitute the
default map of the user.
The Superuser and the users with privileged profile can open their own default map and, then, change map
choosing among those managed by the system (see pag.145).
The users with advanced, normal and entry profile can open only one's default map.
On the installation of the system, the nms5ux map is created. Then, it will be possible to create a new map
(see pag.374).
More NMS5UX users, who can open and use the map at the same time, can be associated to the same map
(more users can have the same default map).
In this case, only the first user who access to the map will have the Read-Write access, all the other users
will have Read Only access (see pag.63).
What just said is valid only for the Superuser and the users with privileged or advanced profile. The
normal and entry users has always Read Only access to the map, even if they are the first to open it.
The max number of NMS5UX users who can access at the same time to the same map depends on the
codeword required by the customer.
The same NE object can be created in more map and/or more times in the same maps. In this way, on the
creation of the first copy of the object in a map, all the parameters of the object must be set.
On the creation of the successive copies, it will be sufficient to enter the physical or logical address and,
automatically, the system will set the parameter and will associate the status of connection of the twin
object already present in the map.
nms5ux map
During the installation of the system, the nms5ux map is created, associated to the Superuser, named
nms5ux (the name of the Superuser can be modified by the user itself).
This map will result the default map of the nms5ux user but, as all the other maps, it can be opened also
by privileged users and be assigned, as default map, to other users.
Superuser (pag.57)
Privileged (pag.57)
Advanced (pag.57)
Normal (pag.58)
Entry (pag.58)
The availability of the commands of the UX Map Manager window depends on the profile of the NMS5UX
user who opened the map.
Tab.16 point out, for each command, the profile that the NMS5UX user must own to be able to use it.
Superuser
The Superuser can start the NMS5UX-B graphic interface relevant to all the maps managed by the system.
In each map, the Superuser can access both in Read-Write and Read Only modality and can verify/set/
modify all the parameters.
The detail of the operations that the Superuser can execute in the equipment window is reported in the
specific equipment User Manual.
The NMS5UX-B system manages ONLY one Superuser. It is created during the installation of the system.
In a second moment, it will not be possible to delete the user or modify his profile.
Privileged
The privileged user can start the NMS5UX-B graphic interface relevant to all the maps managed by the
system.
In each map, the privileged user can access both in Read-Write and Read Only modality.
The detail of the commands/operations available to the privileged user is reported in Tab.16.
The detail of the operations that the privileged user can execute in the equipment window is reported in
the specific equipment User Manual.
On the installation of the system, there is no privileged user. Then, it is possible to create more privileged
users.
Advanced
The advanced user can start the NMS5UX-B graphic interface relevant to the only map associated to his
NMS5UX user (default map).
The advanced user can access to his map both in Read-Write and Read Only modality.
The detail of the commands/operations available to the advanced user is reported in Tab.16.
The detail of the operations that the advanced user can execute in the equipment window is reported in
the specific equipment User Manual.
On the installation of the system, there is no advanced user. Then, it is possible to create more advanced
users.
The normal user can start the NMS5UX-B graphic interface relevant to the only map associated to his
NMS5UX user (default map).
The normal user can access to his map only in Read Only modality.
The detail of the commands/operations available to the normal user is reported in Tab.16.
The detail of the operations that the normal user can execute in the equipment window is reported in the
specific equipment User Manual.
On the installation of the system, there is no normal user. Then, it is possible to create more normal users.
Entry
The entry user can start the NMS5UX-B graphic interface relevant to the only map associated to his
NMS5UX user (default map).
The entry user can access to his map only in Read Only modality.
In his map, the user can only verify the parameters.
The detail of the operations that the entry user can execute in the equipment window is reported in the
specific equipment User Manual.
On the installation of the system, there is no normal user. Then, it is possible to create more normal users.
Internet
The setting of the Internet option for the NMS5UX Superuser user is defined during the installation of the
system and depends on the presence or not, in the installation packet, of the RAN application.
The setting of the Internet option for the other NMS5UX users is defined during the creation of the relevant
user. After the creation of the user, it is possible to modify the setting of the Internet option of any NMS5UX
user (operation available only to the Superuser).
Ring/VLAN
The setting of the Ring/VLAN option for the NMS5UX Superuser user is defined during the installation of
the system and depends on the presence or not of the Ring Manager and/or VLAN Manager application in
the installation packet.
The application:
Ring Manager, besides the Ring Manager window, is constituted by a part integrated in the men-
us of the NMS5UX-B graphic interface (menu Ring Manager - pag.431).
The use of commands of the Ring Manager menu is not affected by the possible use of the
Ring/VLAN option: any NMS5UX user, independently from his setting of the Ring/VLAN option,
can create, delete, etc. a Ring object.
VLAN Manager, besides the VLAN Manager Map window, is constituted by a part integrated in
the menus of the NMS5UX-B graphic interface (menu VLAN Manager - pag.475).
The use of commands of the VLAN Manager menu is not affected by the possible use of the
Ring/VLAN option: any NMS5UX user, independently from his setting of the Ring/VLAN option,
can create, delete, etc. a VLAN Map object.
During the creation of a NMS5UX user, it is possible to assign a validity of n days to the relevant user (ac-
count) (see pag.374).
At the expiry of this period, when the NMS5UX-B graphic interface is started, the system displays the mes-
sage Your Account is expired. Please contact the system administrator.
The displaying of the message forbids the opening of the UX Map Manager windows.
In order to modify ones user or its validity period, contact the Superuser.
If the message is displayed when the Superuser opens the UX Map Manager window, it is necessary to call
SIAE MICROELETTRONICA.
As rule, the username and the password of the Unix user with which the terminal is started, determine
even the NMS5UX user with which the graphical interface NMS5UX-B is started.
In fact, at his creation the NMS5UX user automatically gets the username and the password of the relevant
Unix user.
This involves the user, in order to access the UX Map Manager window, is asked to enter the username and
the password only at the start-up of the terminal (see pag.72).
The NMS5UX-B system manages the function of manual login to the UX Map Manager window.
This function, is active, allows defining, at the creation of the NMS5UX user, a username and a password
different from those defined for the relevant Unix user.
In this case, the user shall enter, at the start-up of the terminal, the username and the password of the
Unix user and, for the start of the UX Map Manager window, will be asked to enter the username and the
password of the NMS5UX user.
The function can be activated on demand when the supervision system is installed.
The function, if active, allows defining a continue inactivity period which must pass during a NMS5UX-B
session, before the suspension of this session for inactivity.
Before closing the UX Map Manager window (NMS5UX-B session) due to inactivity, the message INACTIV-
ITY CHECK!! If you dont acknowledge this dialog in x min your session will automatically be closed is dis-
played.
If the user confirm his presence pressing OK, the session is not closed.
The continue inactivity period (frequency with which the inactivity message is displayed) and the period
during which the warning message is displayed on the screen (value x pointed out in the message) can be
configured by Superuser. These settings are valid for ALL the NMS5UX users.
The function Inactivity Check (User and RW Map) can be activated on demand when the supervision
system is installed.
The NMS5UX-B graphic interface relevant to the same map can be started on more PCs/terminals at the
same time.
In order to avoid conflicts between the graphic interfaces started on different terminals that use the same
map, it is possible to open the UX Map Manager window (Fig.1) in two different modalities:
Read-Write. The user who accesses the map in this modality can add, delete, move the sym-
bols contained in the map and modify the characteristics of the symbols.
Read Only. The user who accesses the map in this modality can control the status of the map
and of the contained symbols, but he cannot create, delete or move any symbol or execute any
modification on the symbols.
The map can be opened in Read Only modality by all the user.
The access in Read-Write modality for each map is assigned to one user at a time.
This user corresponds to the first authorized NMS5UX user who opens the NMS5UX-B graphic interface
(then the associated map) on any of the PCs/terminals.
The users who will connect in a second moment to the same map will have the access in Read Only mo-
dality.
The access modality is displayed in the lower bar of the UX Map Manager window.
The map can be opened in Read-Write modality only by the Superuser and by the user with
privileged or advanced profile. A normal or entry user, even if he is the first user that access to
the map, will open the map in Read Only modality.
The availability of the commands of the UX Map Manager window depends on the modality of access to
the map. Tab.16 point out, for each command, the access to the map necessary to use it.
All the changes executed by Read-Write user in a map, are NOT dynamically displayed also in the UX Map
Manager window of the users, who have access to the same map, in Read Only modality.
To update the data of a map in Read Only modality, it is necessary to select the Map > Refresh (pag.137)
command.
If the user, with access to the map of Read-Write type, closes his UX Map Manager window, the Read-Write
access becomes available to all the other users (Read Only) that opened the UX Map Manager window rel-
evant to the same map.
The user who wishes to modify his modality from Read Only to Read-Write must select the Map > Refresh
(pag.137) command.
The first users who executes the updating of the map changes his access from Read Only to Read-Write.
The availability of the Read-Write access is not signalled to the Read Only users.
It is possible to require (pag.380) or force (pag.381) the disconnection of one user, whose access is Read-
Write. If the user accept the request, his map is closed and the Read-Write access will be available.
The NMS5UX-B system is provided with the function Inactivity Check - RW Map.
The function, if active, allows defining a continue inactivity period which must pass during a NMS5UX-B
session with Read Write access to the map (see pag.63), before the suspension of this session due to in-
activity.
Before closing the UX Map Manager [Read-Write] window (NMS5UX-B session with access to the RW map)
due to inactivity, the message INACTIVITY CHECK!! If you dont acknowledge this dialog in x min your ses-
sion will automatically be closed is displayed.
If the user confirm his presence pressing OK, the session is not closed.
The continue inactivity period (frequency with which the RW inactivity message is displayed) and the period
during which the RW warning message is displayed on the screen (value x pointed out in the message) can
be configured by Superuser. These settings are valid for ALL the NMS5UX users with Read Write access.
The function Inactivity Check - RW Map can be activated on demand when the supervision system is
installed.
The equipment window can be opened by more user at the same time.
In this window, the Read-Write access modality is acquired by the first user who opens the window itself
(independently if his access to the map is Read-Write or Read Only).
All the users, who open later the same equipment window, will have the access in Read Only modality.
What just said is valid only for the Superuser and the users with privileged or advanced profile. The
normal and entry users has always Read Only access to the equipment window, even if they are the first
to open it.
It is not possible to request or to force the closure of the equipment window in Read-Write modality, but
it is possible to require (pag.383) or force (pag.383) the closure of the relevant Manager application.
The nodal window (ALplus or ALCplus2) can be opened by one user at the same time.
It is not possible to request or to force the closure of the nodal window, but it is possible to require
(pag.383) or force (pag.383) the closure of the relevant Manager application.
The Ring Manager window relevant to the same Ring object can be opened by only one user at a time.
Instead more Ring Manager windows relevant to different Ring objects can be opened at the same time.
It is not possible to request or to force the closure of a Ring Manager window, but it is possible to require
(pag.383) or force (pag.383) the closure of the relevant Manager application.
The Ring Manager window relevant to the same Ring object can be opened by only one user at a time.
Instead more Ring Manager windows relevant to different Ring objects can be opened at the same time.
It is not possible to request or to force the closure of a Ring Manager window, but it is possible to require
(pag.383) or force (pag.383) the closure of the relevant Manager application.
The first time that the NMS5UX-B graphic interface starts, after the installation of the system, refer to the
First start-up of the NMS5UX-B interface procedure (pag.75).
The next times, refer to the Start-up of the NMS5UX-B interface procedure (pag.72).
The start-up of the NMS5UX-B graphic interface corresponds to the opening of the UX Map Manager
window (Fig.1).
It is possible to start more NMS5UX-B interfaces on more machines or on the same machine.
The maximum number of NMS5UX-B graphic interfaces that can be started at the same time depends on
the codeword required by the user.
The following procedure presumes that the NMS5UX-B system has been already installed on the ma-
chine and that the processes necessary for the start-up of the interface. The procedure for the installation
and the start-up of the NMS5UX-B system is reported in the administrator manual.
It is supposed that the Unix user and the corresponding NMS5UX user, which you wish to use for the start-
up of the interface, have been created.
2. Type the name and the password of the Unix user in the relevant box.
If you have two or more Unix users, use the name/password of the Unix user associated to the NMS5UX
user that you wish to use to open the map.
3. Press the confirmation push-button.
If the typed data are correct, one's Unix operating system is started-up.
6. Press Enter.
The TMNMENU window opens (Fig.4).
The Login window opens and then the UX Map Manager window (Fig.1) opens with the default map
associated to its user.
The Superuser and the users with privileged profile can change the map anytime (pag.145).
If the system displays the Your Account is expired. Please contact the system administrator message,
one's account is expired. Contact the Superuser to set a new user or modify the current validity period.
If the function of Manual login to the UX Map Manager window (pag.61) is active, in the Login window
it is necessary to:
a. Type the username of one's NMS5UX user into the Login box.
If you have two or more NMS5UX users, type the username of the NMS5UX user associated to
the Unix user used to start the operating system.
b. Type the password of the NMS5UX user into the Password box.
c. Press OK.
The UX Map Manager window opens with the default map associated to its user.
If the system displays the message:
Incorrect Login, the typed name of the NMS5UX user is incorrect.
Wrong Password, the typed password of the NMS5UX user is incorrect.
Wrong Unix User, the used NMS5UX user is not compatible with the Unix user used for
the start-up of the operating system.
If, after more attempts, the Incorrect Login, Wrong Password or Wrong Unix User message
is displayed for three times consecutively, the Login window is automatically closed. To start the
graphic interface, it is necessary to execute again the procedure of the step 7.
The Your Password is going to expire on <data>. Please change it and Password expired. Please
change it to login message are displayed ONLY if the periodical password change functionality
IS ACTIVE. It consists in requiring to the user to change his own password each N days (for ex-
ample each 6 months).
The functionality can be activated/deactivated by the Superuser, who, if he activates the func-
tionality, sets the interval between a password change and the successive one.
The activation of the periodical password change does not influence the expiry date of the user,
which can be set during the creation of a NMS5UX user. The two functionalities are independent
and can coexist at the same time.
(2) The description and the use of these icons is reported in the administrator manual of the NMS5UX-
B system.
The following procedure supposes that the NMS5UX-B system has been already installed on the ma-
chine and that the processes necessary to the start-up of the interface have been already activated. The
procedure for the installation and the start-up of the NMS5UX-B system is reported in the administrator
manual.
7. Press Enter.
The TMNMENU window opens (Fig.4).
If the function of Manual login to the UX Map Manager window (pag.61) is active, in the Login window
it is necessary to:
The closure of the NMS5UX-B graphical interface corresponds to the closing of the UX Map Manager window
(see pag.147).
The closure of the UX Map Manager window causes the automatic closure of all the possible open win-
dow of NMS5UX-B (Alarm History Browser, Equipment Information, etc.).
The system displays the WARNING!! Forced Logout from Superuser message. The Superuser
user has forced the disconnection of the user from the map (see pag.381).
The user closes the operation system.
After the installation of the NMS5UX-B system, it is necessary to represent the network graphically.
The network configuration can be executed both by SIAE MICROELETTRONICA and by the user. If the net-
work has been configured by SIAE MICROELETTRONICA, pass to the equipment connection (pag.108). In-
stead, if the network must be represented, follow the indication reported below.
The network representation is made using a series of predefined objects (see pag.79).
To create them, some general rules pointed out at pag.82 must be respected.
The pre-defined objects, available to the user for the network graphic representation, are:
Container objects (pag.79)
Network Element (NE) objects (pag.79)
Generic Symbol objects (pag.81)
Link objects (pag.81)
Label objects (pag.81)
Ring objects (pag.81)
VLAN Map objects (pag.81)
Container objects
The Container objects can be compared to the directories in the arrangement of the files on a PC.
These objects are used to identify the real or virtual equipment: Radio SDH, Radio PDH, etc.
Real NE
Real equipment (SNMP or Legacy) means those objects that have the corresponding equipment physically
present in the network.
A real NE is not automatically managed by the NMS5UX-B system when the relevant object is created,
but it is necessary to connect it. The only exception is when the created NE is already present in a map
and it is in connected status; in this case, the NE just after its creation acquires the condition of the same
symbol present in the other map.
Virtual NE
Virtual equipment means those objects that have not the corresponding equipment physically present in
the network.
Depending on the type of protocol used to manage the equipment, the configuration of a virtual NE changes
as pointed out here below.
With NE object of ALplus Node type we do not mean a single equipment but a set of minimum 2 and max-
imum 3 ALplus equipment (nodal matrix) interconnected by Nodal Bus (Node).
These equipment are not managed one by one by the NMS5UX-B system, but are managed as a set rep-
resented by the object of ALplus Node type, which has not a corresponding real object present in the net-
work but works as container for the equipment of the nodal system.
The equipment of a node are not automatically managed by the NMS5UX-B system when the relevant
ALplus Node object is created, but it is necessary to connect them. The only exception is if the created
node is already present in a map in connected status; in this case, the equipment of the node will auto-
matically acquire the condition of the same ALplus Node symbol present in the other map.
With NE object of ALCplus2 Node type we do not mean a single equipment but a set of minimum 2 and
maximum 8 ALCplus2 equipment interconnected by a Nodal Bus (TDM traffic) and/or by LAN (Ethernet traf-
fic). (Node).
These equipment are not managed one by one by the NMS5UX-B system, but are managed as a set rep-
resented by the object of ALCplus2 Node type, which has not a corresponding real object present in the
network but works as container for the equipment of the nodal system.
The equipment of a node are not automatically managed by the NMS5UX-B system when the relevant
ALCplus2 Node object is created, but it is necessary to connect them. The only exception is if the created
node is already present in a map in connected status; in this case, the equipment of the node will auto-
matically acquire the condition of the same ALCplus2 Node symbol present in the other map.
This object is used to identify equipment, not managed by NMS5UX-B, which are provided with a WEB man-
agement interface.
In fact, these objects can be assigned an IP address and a NSAP address (as for the creation of a normal
SNMP NE to manage with the NMS5UX-B system). Selecting them, however, starts the default system
browser with the WEB page, available at the set address, active.
These objects were born in never connected (disconnected) status and their status do not change for the
rest of their life because, differently from other NE objects, the objects of WEB Generic type must not be
connected to start the connection.
In fact, for this type of object, not all the commands available for the NE objects are meaningful, for ex-
ample Connect, Disconnect, Network Alarm History, etc.
These objects are used to graphically represent elements present in the network as, for example: pc, mo-
dem, etc.
The Generic Symbol objects, even if they have a physical match in the network, do not allow managing
the physical element which they are referred to, as they are a simple graphical representation.
Link objects
These objects are used to graphically represent a connection between two objects.
The Link objects, even if they have a physical match in the network, do not allow managing the con-
nections, which they are referred to, as they are a simple graphical representation.
Label objects
These objects are used to type a text string into the map.
Ring objects
These objects are used to identify subnetworks of PDH and SDH equipment, managed by the NMS5UX-B
system, which implement Paths.
The selection of a Ring object allows accessing to the relevant graphic interface represented by the Ring
Manager window (pag.50).
The use of the Ring Manager window is reported in the relevant user manual (see pag.507).
These objects are used to identify subnetworks of radio equipment with Ethernet tributary, managed by
the NMS5UX-B system, which implement virtual LAN paths (VLAN path).
The selection of a VLAN Map object allows accessing to the relevant graphic interface represented by the
VLAN Manager Map window (pag.51).
The use of the VLAN Manager Map window is reported in the relevant user manual (see pag.507).
To avoid contemporaneous operations on the same object, only one user at a time can change the network
configuration in a map. This one has the access to the map in Read-Write modality: Read-Write user.
More users can access to the map at the same time. Only the Read-Write user can modify the network
configuration. The changes made by the Read-Write user are not dynamically displayed by the Read Only
users.
To update the information of a map in Read Only modality, it is necessary to update the UX Map Manager
window selecting the Map > Refresh command.
Besides the general instructions described above, for some objects the rules described here below must
be respected.
NE objects
It is possible to create all the equipment in a network in a single map or to subdivide the network in two
or more parts and to associate two or more maps to these parts.
In this case, at the opening of each map, only the part of network associated to this map will be visible
and manageable.
A NE object is displayed ONLY in the map where it has been created. If you wish that an equipment is
present in two different maps, it is necessary to create the relevant symbol in both the maps.
If the created NE symbol is already present in a map, it will automatically acquire the status of the already
existing object. For example, if the NE-1 symbol in connected status is present in the map A, when the NE-
1 symbol (same IP/Physical address) is created in the map B, the symbol will result connected as it inherits
the status of the twin symbol.
The same NE object can be created in more maps and/or more times in the same map.
It is possible to create new NE objects even if these have not been physically installed in the network, for
example because they are foreseen for a future installation. In this case, it will be possible to open the
relevant equipment window only after the first connection; then, only after the equipment has been phys-
ically installed in the network and has been connected.
It is, instead, possible to create virtual NE objects, that is objects not having a corresponding equipment
present in the network, but which can be configured as a normal NE. Then this configuration can be trans-
ferred to any (real or virtual) equipment compatible with the virtual NE (see pag.79).
The NE objects of WEB Generic type (see pag.80), after their creation, do not require any operation (line
test, connection) to be used.
For the NE objects of ALplus Node type, besides the rules defined for the NE objects, it is necessary to
follow the indications reported here below for their creation:
Before creating an ALplus Node object, it is necessary that the ALplus node* has been already
defined (equipment forming the node, relevant IP address, etc.) locally by means of SCT/LMT
application. For more information, refer to the relevant documentation.
* The ALplus node term indicates the set of minimum 2 and maximum 3 ALplus equipment with
nodal matrix interconnected by Nodal Bus.
For the NE objects of ALCplus2 Node type, besides the rules defined for the NE objects, it is necessary to
follow the indications reported here below for their creation:
Before creating an ALCplus2 Node object, it is necessary that the ALCplus2 node* has been al-
ready defined (equipment forming the node, relevant IP address, etc.) locally by means of SCT/
LMT application. For more information, refer to the relevant documentation.
* The ALCplus2 node term indicates the set of minimum 2 and maximum 8 ALCplus2 equipment
interconnected by a Nodal Bus (TDM traffic) and/or by LAN (Ethernet traffic)
If in the map there are already one or more copies of NE objects relevant to equipment belong-
ing to a node, before creating the relevant node it is necessary to DELETE all the copies of these
objects. This because the management of an equipment belonging to a node is supported by the
NMS5UX-B system only through the relevant nodal window.
After the creation of a node, it is not possible to create NE objects relevant to the equipment
forming the node. Their management is carried out from the nodal window and not directly from
the map yet.
During the creation of the node, the system requires the IP address of the node. This corre-
sponds to the IP address of the main equipment forming the node.
Container objects
The container map windows allow subdividing the network into hierarchical levels in such a way that it is
possible to arrive from a general view to the displaying of the single elements, passing through interme-
diate levels.
In fact the network, made by the objects that the supervision system must manage and control, can be
considered from different points of view.
It can be observed taken as a whole, as distribution of elements in a geographical area (for example sub
networks), or you can decide to study a single object to see its configuration; the user can decide at which
level, and then which detail, to access to the network information. In this way, subdividing the network in
containers, it is possible to easily pass from a general overview to a more and more detailed view.
The user is totally free in the creation of the number and type of levels that better fits to the structure of
one's network.
A Ring object is displayed ONLY in the map where it has been created. If you wish that a Ring is present
in two different maps, it is necessary to create the relevant symbol in both the maps.
If the created Ring symbol is already present in a map, it will automatically acquire the configuration of
the already existing object.
For instance, if in the map A there is the symbol Ring-1, where are configured the equipment NE-A, NE-B
and NE-C and the relevant Paths/Links, when the Ring1 symbol (same physical address) is created in the
map B, the equipment NE-A, NE-B and NE-C and the relevant Paths/Links will result configured in the sym-
bol because the new symbol inherits the configuration of the twin symbol.
The same Ring object can be created in more maps and/or more times in the same map.
The commands for the creation/modification/deletion of the Ring objects are present in the Ring Manager
(pag.431) menu.
The menu is present in the UX Map Manager window only if the Ring Manager application, optional and
provided on demand, is installed.
A VLAN Map object is displayed ONLY in the map where it has been created. If you wish that a VLAN Map
is present in two different maps, it is necessary to create the relevant symbol in both the maps.
If the created VLAN Map symbol is already present in a map, it will automatically acquire the configuration
of the already existing object.
For instance, if in the map A there is the symbol VLAN Map-1, where are configured the equipment NE-A,
NE-B and NE-C and the relevant VLAN paths/Links, when the VLAN Map1 symbol (same physical address)
is created in the map B, the equipment NE-A, NE-B and NE-C and the relevant VLAN paths/Links will result
configured in the symbol because the new symbol inherits the configuration of the twin symbol.
The same VLAN Map object can be created in more maps and/or more times in the same map.
The commands for the creation/modification/deletion of the VLAN Map objects are present in the VLAN
Manager (pag.475) menu.
The menu is present in the UX Map Manager window only if the VLAN Manager application, optional and
provided on demand, is installed.
By means of the commands available in the UX Map Manager window, it is possible to create all pre-defined
objects available in the NMS5UX-B system.
In detail for the creation of the objects:
Container, NE, Generic Symbol, Link and Label use the Edit > Add menu (pag.149).
Ring use the Ring Manager > Edit > RM-Add Ring command (pag.432).
VLAN Map use the VLAN Manager > Edit > VM-Add VLAN Map command (pag.476).
Here below a series of examples of graphic representation of a hypothetic network in one or more maps,
using the commands of Edit menu, is reported.
Let us suppose to have to graphically display a certain Italia network in such a way to be able to execute
its supervisory operations by means of the NMS5UX-B system.
According to the equipment type present into his own network, the user has to refer to the specific exam-
ple:
Network composed by SNMP equipment (pag.85).
Network composed by Legacy equipment (pag.88).
Network composed by Legacy equipment and SNMP equipment one (pag.91).
Into the example described here below, the entire equipment network will be displayed into the same
map and it is assumed that such a map has already been created.
It is possible to subdivide the equipment network into two or more parts and to couple to such parts two
or more maps. In this case at the opening of each map, it will be visible, and it will be possible to manage
it, only the part of the network coupled with the map under examination. An example is pointed out to
pag.95.
The Italia network shown in Fig.5, is composed by Radio SDH, Radio PDH and PMP equipment.
The NMS5UX-B loaded on a Workstation connected to an equipment by means of an Ethernet LAN.
A specific IP address has been locally assigned to each equipment by means of LCT.
Lan
Radio PDH
10.10.10.33
Italia
(map)
Nord Italia
(container) 1
Milano
(container) 3
Sud Italia
Torino (container) 2
(container) 4
Lan
9 5
10
PMP
6 10.10.10.40
Radio SDH
10.10.10.21 Radio PDH
10.10.10.31
11
7
Radio SDH Radio PDH
10.10.10.22 10.10.10.32
Radio PDH
10.10.10.33
In Fig.6, a name identifying a geographic area or a town has been associated to the containers. It is pos-
sible to assign any name to the Container objects, but it is suggested to set a name having a geographic
reference. In this way, it will be possible to determine the position of the equipment just from the name
of the symbol of the container.
An IP address and a logical address, different for each created NE object, have been assigned to each NE
object. ONLY if the equipment are inserted into an OSI network, it will be necessary to set also the NSAP
(Gosip) address of the equipment.
The IP Address and the possible NSAP (Gosip) Address, have to coincide with the IP Address and the NSAP
(Gosip) Address locally set (by means of the LCT program) for the relevant equipment. If the values do
not coincide, it will not be possible to activate the connection with the equipment.
The logical address corresponds to the name of the equipment that is displayed under the relevant icon.
Also in this case, as for the Container objects, it is possible to assign any value. It is suggested to assign
a name that makes easy the acknowledgement of the equipment.
Create the Italia map. The Superuser can create the map with a specific command (pag.374) or during the
creation of a new user privileged or advanced (pag.374).
Open the UX Map Manager window with a user associated to the Italia map (pag.72).
Now proceed in the creation of the objects (pag.149).
In order to create the objects, the map must be in Read-Write modality.
During the operation, follow a determinate order because it is not possible to create an object, for example
NE, if the Container object that must contain it has not been previously created.
The first symbols that must be created are the Container objects: Nord Italia and Sud Italia.
Then open, for example, the Nord Italia container and create the objects present in it, and so on.
In Tab.5, for each object present in Fig.6 and identified by a number, some information is reported that
allows understanding how and where the symbol must be created. In detail, there is the indication of the
type of object that must be created, which values must be assigned to the parameters of the object and
in which container the symbol must be inserted. Furthermore, the order of the objects respects a possible
creation order that assures the creation of the Container objects before the creation of the objects con-
tained in them. The Generic Symbol, Link and Label objects can be added in any container.
In Tab.5 not all the parameters are indicated, but only those whose setting is necessary for the creation
of the object.
Type of object that Container where the ob- Setting of the values of the
Object
must be created ject must be created main parameters
* Main container that represents the map: it is created with the map and automatically acquires its name.
** The user can set any value, different from the displayed one.
*** Set the NSAP (Gosip) Address of the equipment only if it is inserted into a OSI network.
The creation of an object implies the displaying of the relevant symbol on video.
By means of the Container symbol, it is possible to display the detail of the network where the equipment
is contained, for example as shown in Fig.7, for the PMP 40 equipment of the Italia network.
Now the NMS5UX-B system knows all the information that allows managing each single equipment when
it will be connected.
The Italia network shown in Fig.8, is composed by FAM, OLTME and G series Radio type equipment.
The NMS5UX-B system is loaded on a Workstation which, by means of Ethernet LAN, is connected to a
CommServer-S and a IPBOX.
The physical address has been locally assigned by means of LOM, to each equipment. The IP Address has
been locally assigned to the CommServer-S and IPBOX.
The CommServer-S and IPBOX need for defining the connection line that physically couples each single
equipment, managed by means of the Legacy protocol, to the supervisory system.
IP-BOX CommServer-S
RS232
RS485
Equipment
type
Radio FAM Oltme
10 6 21
RS232
Equipment
RS485
local address
Radio
12
Italia
(map)
Nord Italia Sud Italia
(container) 1 (container) 2
Milano
(container) 3
5 9
IP-BOX CommServer-S
143.1.1.1 143.1.1.2
2 2 3 4 5 6 7 8
10
Palermo
(container) 11 Oltme
6 21
12
Radio FAM
Torino
(container) 4
10 6
8 7 14 13
Radio Radio FAM FAM
12 11 8 7
In Fig.9, a name identifying a geographic area or a town has been associated to the containers. It is pos-
sible to assign any name to the Container objects, but it is suggested to set a name having a geographic
reference. In this way, it will be possible to determine the position of the equipment just from the name
of the symbol of the container.
An physical or IP address (NE objects: Comm.Server and IPBOX) and a logical address, different for each
created NE object, have been assigned to each NE object.
The physical/IP address, has to coincide with the address locally set (by means of the LOM/LCT program)
for the relevant equipment. If the values do not coincide, it will not be possible to activate the connection
with the equipment.
The logical address corresponds to the name of the equipment that is displayed under the relevant icon.
Also in this case, as for the Container objects, it is possible to assign any value. It is suggested to assign
a name that makes easy the acknowledgement of the equipment.
To each NE object, during its creation, it is necessary to couple all the information necessary to allow the
equipment reaching. Such information are the IP Address of the Comm. Server-S or of the IPBOX and the
number of the used port.
For the equipment not directly connected to the serial port, it has to be set the IP Address of the Com-
mServer/IPBOX and the number of the port to which it is connected the equipment installed upstream of
the equipment chain to which belongs the equipment itself.
The equipment can be connected to the supervisory system, directly or undirectly by means of EOC or
other dedicated connection lines creating, in such a way, equipment chains.
Create the Italia map. The Superuser can create the map with a specific command (pag.374) or during the
creation of a new user privileged or advanced (pag.374).
Open the UX Map Manager window with a user associated to the Italia map (pag.72).
Now proceed in the creation of the objects (pag.149).
In order to create the objects, the map must be in Read-Write modality.
In Fig.9, all the objects that must be created by the user, in such a way that each equipment of the Italia
network can be managed by NMS5UX-B, are identified by a number (1, 2, etc.) located in the upper right
corner.
In Tab.6, for each object present in Fig.9 and identified by a number, some information is reported that
allows understanding how and where the symbol must be created. In detail, there is the indication of the
type of object that must be created, which values must be assigned to the parameters of the object and
in which container the symbol must be inserted. Furthermore, the order of the objects respects a possible
creation order that assures the creation of the Container objects before the creation of the objects con-
tained in them. The Generic Symbol, Link and Label objects can be added in any container.
In Tab.6 not all the parameters are indicated, but only those whose setting is necessary for the creation
of the object.
Type of object that Container where the ob- Setting of the values of the
Object
must be created ject must be created main parameters
Physical Address: 7
Logical Address: FAM 7 **
Network Element > Lega-
13 Palermo CS/IPBOX IP Address: 143.1.1.2
cy Protocol Managed
CS/IPBOX Port: 2
Type: Fam
Physical Address: 8
Logical Address: FAM 8 **
Network Element > Lega-
14 Palermo CS/IPBOX IP Address: 143.1.1.2
cy Protocol Managed
CS/IPBOX Port: 2
Type: Fam
* Main container that represents the map: it is created with the map and automatically acquires its name.
** The user can set any value, different from the displayed one.
*** Set the NSAP (Gosip) Address of the equipment only if it is inserted into a OSI network.
The creation of an object implies the displaying of the relevant symbol on video.
By means of the Container symbol, it is possible to display the detail of the network where the equipment
is contained, for example as shown in Fig.10, for the Radio 12 equipment of the Italia network.
Now the NMS5UX-B system knows all the information that allows managing each single equipment when
it will be connected.
The Italia network shown in Fig.11, is composed by equipment managed with Legacy protocol (FAM) and
equipment managed with SNMP protocol (Radio SDH).
The NMS5UX-B system is loaded on a Workstation that is connected, by means of Ethernet LAN, to a Com-
mServer-S and to the equipment.
The CommServer-S need for defining the connection line that physically couples each single equipment,
managed by means of the Legacy protocol, to the supervisory system.
CommServer-S
143.1.1.2 IP Address
Lan Lan
2 3 4 5 6 7 8 Serial ports
RS232
RS485
Radio SDH Equipment
10.10.10.20 type
FAM FAM
Radio SDH 6 9
10.10.10.21 Equipment
RS485
local address
Before creating the objects that will allow to the system the management of the equipment, it is necessary
to subdivide the network into containers, objects, etc. Doing this, it is suggested to consider as the equi-
pment is connected and where they are located on the field.
Into the subject example, it is supposed that all the Italia network equipment have been created into the
same map. If the operator wants to subdivide the equipment into more maps, he has to respect the indi-
cation reported to pag.95.
A possible subdivision of the network is shown in Fig.12.
Italia
(map)
Nord Italia Sud Italia
(container) 1 (container) 2
Torino
(container) 3
CommServer-S
143.1.1.2
2 3 4 5 6 7 8
4
Radio SDH 8
10.10.10.20 Palermo
(container) 9 FAM
5
9
10
6
12 11
Radio SDH FAM FAM
10.10.10.22 8 7
In Fig.12, a name identifying a geographic area or a town has been associated to the containers. It is pos-
sible to assign any name to the Container objects, but it is suggested to set a name having a geographic
reference. In this way, it will be possible to determine the position of the equipment just from the name
of the symbol of the container.
To each NE object, the system has assigned a physical address (IP Address for the SNMP equipment and
physical address with the Legacy equipment) and a logic one different for each created NE object. ONLY if
the equipment are inserted into an OSI network, it will be necessary to set also the NSAP (Gosip) address
of the equipment.
To each NE object, during its creation, it is necessary to couple all the information necessary to allow the
equipment reaching. Such information are the IP Address of the Comm. Server-S and the number of the
used port.
For the equipment not directly connected to the serial port, it has to be set the IP Address of the Com-
mServer and the number of the port to which it is connected the equipment installed upstream of the
equipment chain to which belongs the equipment itself.
The equipment can be connected to the supervisory system, directly or undirectly by means of EOC or
other dedicated connection lines creating, in such a way, equipment chains.
Create the Italia map. The Superuser can create the map with a specific command (pag.374) or during the
creation of a new user privileged or advanced (pag.374).
Open the UX Map Manager window with a user associated to the Italia map (pag.72).
Now proceed in the creation of the objects (pag.149).
In order to create the objects, the map must be in Read-Write modality.
During the operation, follow a determinate order because it is not possible to create an object, for example
NE, if the Container object that must contain it has not been previously created.
The first symbols that must be created are the Container objects: Nord Italia and Sud Italia.
Then open, for example, the Nord Italia container and create the objects present in it, and so on.
In Fig.12, all the objects that must be created by the user, in such a way that each equipment of the Italia
network can be managed by NMS5UX-B, are identified by a number (1, 2, etc.) located in the upper right
corner.
In Tab.7, for each object present in Fig.12 and identified by a number, some information is reported that
allows understanding how and where the symbol must be created. In detail, there is the indication of the
type of object that must be created, which values must be assigned to the parameters of the object and
in which container the symbol must be inserted. Furthermore, the order of the objects respects a possible
creation order that assures the creation of the Container objects before the creation of the objects con-
tained in them. The Generic Symbol, Link and Label objects can be added in any container.
In Tab.7 not all the parameters are indicated, but only those whose setting is necessary for the creation
of the object.
Type of object that Container where the ob- Setting of the values of the
Object
must be created ject must be created main parameters
1 Container Italia * Label: Nord Italia
2 Container Italia * Label: Sud Italia
3 Container Nord Italia Label: Torino
IP Address: 10.10.10.20
Network Element > SNMP Logical Address: SDH 20 **
4 Torino
Managed NSAP (Gosip) Address: **
Type: Radio SDH
IP Address: 10.10.10.21
Network Element > SNMP Logical Address: SDH 21 **
5 Torino
Managed NSAP (Gosip) Address: ***
Type: Radio SDH
IP Address: 10.10.10.22
Network Element > SNMP Logical Address: SDH 22 **
6 Torino
Managed NSAP (Gosip) Address: ***
Type: Radio SDH
IP Address: 143.1.1.2
Network Element > SNMP Logical Address: CS **
7 Sud Italia
Managed NSAP (Gosip) Address: ***
Type: Comm. Server
* Main container that represents the map: it is created with the map and automatically acquires its name.
** The user can set any value, different from the displayed one.
*** Set the NSAP (Gosip) Address of the equipment only if it is inserted into a OSI network.
The creation of an object implies the displaying of the relevant symbol on video.
By means of the Container symbol, it is possible to display the detail of the network where the equipment
is contained, for example as shown in Fig.13, for the FAM 9 equipment of the Italia network.
Now the NMS5UX-B system knows all the information that allows managing each single equipment when
it will be connected.
In this example, we suppose that the Italia network (Fig.5) is subdivided and graphically represented in
two map, in such a way that at the opening of the map only the part of network associated to the specific
map will be visible and manageable.
A possible subdivision of the network is shown in Fig.14.
Nord Italia
(map)
Milano
(container) 1
Sud Italia
Torino (map)
(container) 2
Lan
7 3
8 PMP
4 10.10.10.40
Radio SDH
10.10.10.21 Radio PDH
10.10.10.31
9 5
Radio SDH Radio PDH
10.10.10.22 10.10.10.32
Radio PDH
10.10.10.33
In Fig.14, a name identifying a geographical area or town has been associated to the maps and to the con-
tainers. It is possible to assign any name to the maps and to the Container objects, but it is suggested to
set a name that has a geographical reference. In this way, it will be possible to determine the position of
the equipment just from the name of the map and of the container symbol.
An IP address and a logic address, different for each created NE object, have been assigned to each NE.
The IP Address must coincide with the locally set IP Address (via LCT program) for the relevant equipment.
If the values do not coincide, it will not be possible to activate the connection with the equipment.
The logical address corresponds to the name of the equipment that is displayed under the relevant icon.
Also in this case, as for the Container object, it is possible to assign any value. It is suggested to assign a
name that makes easy the acknowledging of the equipment.
2. Open the UX Map Manager window with a user, which the Nord Italia map is associated to (pag.72).
5. Open the UX Map Manager window with an user which the Sud Italia map is associated to.
At the opening of each map, only the part of network associated to the open map will be visible and
manageable.
It is possible to create a NE symbol in two different maps. In this case, it is necessary to create the symbol
in both the map, assigning to it the same characteristics (IP address, type, etc.). At the creation of the
second symbol, given that the object is already present in a map, it will automatically acquire the status
of the already existing twin symbol.
* Main container that represents the map: it is created with the map and automatically acquires its name.
** The user can set any value, different from the displayed one.
The Add Network From File functionality allows automatically adding a group of predefined objects whose
characteristics have been edited in a file (csv format) to a map of the NMS5UX-B system.
The predefined objects, which can be automatically created by the considered functionality, are:
Container objects (pag.79)
Network Element objects (pag.79) managed with the SNMP protocol
Link objects (pag.81)
Label objects (pag.81)
2. To copy the file (.csv) to the server where the NMS5UX-B system is installed (default directory opt/
nms5ux/data/files).
The file must be transferred in ASCII format.
4. To open the file (.csv) by means of the Edit > Add > Network From File command.
Opening the file involves the automatic creation of the objects in the UX Map Manager window.
At the end of the operation, the result of the creation is pointed out for each object.
The use of the Network From File command is pointed out at (pag.155).
At pag.101 an example is reported of complete use of the Add Network From File functionality.
The Add Network From File functionality supports files in csv format with a predefined structure.
The user can create the file in the wished mode, but always respecting:
The format (.csv)
The file structure described at pag.97.
The rules for the compilation of the file, pointed out at pag.99.
At pag.100 the procedure for the creation of the csv file, starting from a model in xls format, is reported.
Tab.9 points out the structure of a row of csv file. The column:
Parameter, displays the fields of the row.
According to the csv format, each field is separated from the next one by the character ";".
Possible values, displays the valid values.
Entering a different value or a value not in compliance with what displayed prevents the creation
of the object.
NE object of type
EL series radio, type 1 or Radio PDH
US series radio, type 2 or Radio SDH
PMP system, type 3 or PMP
CommServerS equipment, type 4 or CS
ADMC multiplexer, type 5 or ADM-C
ALS series radio with AL IDU/ALC IDU, type 7 or Radio PDH-AL
ELFO radio, type 8 or ELFO
ADM1 multiplexer, type 9 or ADM-1
ALS series radio with ALS IDU/ALS-C IDU, type 11 or ALS
ALFO radio, type 12 or ALFO
ALS series radio with AL IDU plus, type 14 or ALplus
SDH N+1 radio, type 15 or SDH N+1
ALS series radio with ALC IDU plus, type 16 or ALCplus
ALS series radio with ALplus2 IDU, type 17 o ALplus2
ALS series radio with ALCplus2 IDU, type 18 o ALCplus2
FAMxc 5RU multiplexer, type 22 or FAMxc
FAMxc 2.5RU multiplexer, type 24 or FAMxc 2.5
IPBOX equipment, type 40 or IP-BOX
EXP63 multiplexer, type 41 or EXP63
ALplus node, type 64 or ALplus Node
ALCplus2 node, type 61 or ALCplus2 Node
Web Generic, type 94 or WEB Generic
IP-ADDRESS If you are creating a NE object, type the IP address (SNMP agent) of the equipment.
If you are creating a Label, Container or Link object, compiling this field is not
meaningful. Type "-"
NSAP If you are creating a NE object into an OSI network, white the NSAP address
(GOSIP) of the equipment.
(Parameter meaningful
only for NE objects insert- For NE objects of ALplus Node or ALCplus2 Node type, write the NSAP address of
ed in an OSI network) the main equipment of the node.
If you are creating a Label, Container, Link or NE object not inserted in an OSI
network, compiling this field is not meaningful. Type -
Path If you are creating a NE, Container or Label object, type the complete path where
(Position of the map where you wish to create the object.
the object must be creat- Use the symbol / to point out the different level.
ed) Example. If you are creating a NE object and you type the path Europe/Italy/Rome,
this means that the equipment must be created in the container Rome, contained
in the container Italy contained, in its turn, in the container Europe.
If you are creating a Link object, compiling this field is not meaningful. Type -
x If you are creating a NE, Container or Label object, type the position X (range 0-
(Position X of the object in 10) the object must take in the View area of the UX Map Manager window.
the View area. If X = 0 and Y = 0, the graphic symbol is created in the New Object area.
An 10x10 hypothetic grid
is taken as reference) If you are creating a Link object, compiling this field is not meaningful. Type -
y If you are creating a NE, Container or Label object, type the position Y (range 0-
(Position Y of the object in 10) the object must take in the View area of the UX Map Manager window.
the View area. If X = 0 and Y = 0, the graphic symbol is created in the New Object area.
An 10x10 hypothetic grid
If you are creating a Link object, compiling this field is not meaningful. Type -
is taken as reference)
Every Container, NE (SNMP), Label or Link object you wish the Add Network From File functionality auto-
matically creates must be inserted in the csv file.
Every object corresponds to a row.
Map parameter
All the objects inserted in a file must have the same value for the Map parameter.
This means that you must insert into a csv file only the objects you wish to create in a specific map.
This map is the map the user shall open (in Read-Write mode) (see step 3 of the procedure described
at pag.97).
If you wish to create the objects of a network which must be represented in more maps, the objects shall
be subdivided according to the belonging map and a csv file shall be created for each map.
Path parameter
The Path parameter represents the position, within the map, where the object must be created.
To point out the containing levels, use the symbol /.
Example. If you are creating a NE object, typing the path:
Europe/Italy/Rome, means that the equipment must be created within the container Rome, con-
tained in the container Italy, in its turn contained in the container Europe.
/, means that the equipment must be created within the main container (level Map - see Fig.2).
If the container name includes the character / the container name must be enclosed between inverted
commas (" ") in the description of the Path.
For example, in the description of a path the container Station A/B must be inserted in the following way
/Europe/Italy/StationA/B
If an object must be created in a container, this container must be already present in the map or must be
defined in the csv file (then created) before the object it must contain.
Example. Suppose to have to create the object NE1 in the container Italy and this container is not already
present in the map. In the csv file, the row defining the container Italy must be placed before the row de-
fining the NE object.
For the creation of a Link object, the parameters Category, Type, Name and Map must be pointed out.
The parameters IP Address and NSAP are not meaningful.
In this case, even the parameters Path, X, Y are not meaningful as the position of a Link object is deter-
mined by the position of the two objects Container and/or NE and/or Label which it must end.
This position is determined by the following rule:
A Link object is created as connection between the two Container/NE/Label objects described
in the two previous rows.
If an object of Link type is present in the two rows before (e.g., in row 8) the row of a Link (e.g., in row
10), the creation of the Link (e.g. in row 10) will not be carried out.
A model file, which can be used as starting point for the creation of the file, is available in the server where
ones NMS5UX-B system.
The model is in xls format and the user must have an application program supporting this format (e.g., MS
Excel) to use it.
1. If ones machine is not provided with an application program supporting the xls format, copy the file
AddNetworkFromFile_TEMPLATE.xls to a PC provided with this application program.
2. Open the AddNetworkFromFile_TEMPLATE.xls file and rename it as you wish.
3. Define every single object you wish insert in the file typing the relevant characteristics in the specified
column of the table named TEMPLATE.
Each row represents an object.
Tab.9 reports, for every column, the list of values you can insert.
Before compiling the file, it is suggested to read the rules pointed out at pag.99.
The rows, whose first character is #, have been inserted only to help the user in the file compilation.
The information present in these rows WILL NOT be considered in the automatic creation of the objects,
then it is not necessary to remove them at the end of the compilation of the file.
The only information used for the automatic creation of the objects are those present in the
TEMPLATE table.
Suppose to wish to graphically represent an hypothetic link ALplus1 - ALplus2 in the map nms5ux using
the Add Network From File functionality.
Before compiling the csv file, it is necessary to define if the link must be placed at the main level in the UX
Map Manager window or if it must be inserted into a container and which auxiliary objects (Link and Label)
you wish to create.
A possible representation of the link is depicted in Fig.15.
Example (Container)
Station A (Container)
ALplus 1
(NE)
ALplus 2
(NE)
Station B (Container)
Fig.15 points out, for every item to insert in the csv file, the object category (between brackets) and the
name.
At this point, the csv file can be created.
At this point, it is necessary to copy the file AddNetworkFromFile_EXAMPLE.csv to the server where the
NMS5UX-B system is installed (directory opt/nms5ux/data/files).
Then open the UX Map Manager window with the map nms5ux in Read-Write mode using a user with profile
Advanced, Privileged or Superuser (pag.72).
Select the Edit > Add > Network From File command and open the opt/nms5ux/data/files/
AddNetworkFromFile_EXAMPLE.csv file.
The Add From File Report...AddNetworkFromFile_EXAMPLE.csv window, shown in Fig.18 opens.
The automatic creation of each objects implies the displaying of the relevant symbol on UX Map Manager
window as shown in Fig.19.
The Auto Discovery functionality allows detecting the SNMP equipment present in the network and not
managed yet by the supervision system.
When a new equipment is detected, NMS5UX-B automatically carries out the following actions:
It inserts the detected equipment into the Auto Discovery table.
It creates the corresponding object in a given map/container (optional operation).
It connects the NE object (optional operation).
Moreover the functionality can detect and notify the user if the type of an object, already managed by
NMS5UX-B, is changed.
The Auto Discovery functionality puts two modalities to detect new equipment present in the network at
users disposal:
Network Scan modality (pag.104)
NE Wake Up modality (pag.106)
In order to work, the two modalities must be configured and activated by the user and can
be active at the same time or one at a time.
The Network Scan modality has the purpose to detect new equipment in the network, not managed by
NMS5UX-B yet, and equipment whose type is changed (equipment described in the DB of the supervision
system, but of a type not corresponding to the real one).
The search is executed by a cyclic scanning of the network, executing a SNMP get on all the IP addresses
belonging to given intervals (configurable by the user).
The equipment captured by the Network Scan and NE Wake Up modalities and the notify of the equip-
ment whose type is changed are inserted in the Auto Discovery table.
The table can be displayed any time by the user opening the Network Element Captured window (Fig.54).
For the new captured equipment, besides the characteristics, the action automatically executed by the sys-
tem on the detection are pointed out.
In order to work, the Network Scan modality must be activated by the user. Before activating it, it is nec-
essary to define the operating parameters of the modality.
Then it will be possible to modify, in any moment, one or more parameters and establish if activating im-
mediately the new configuration or, if the modality is already active, waiting for the expiry of the current
scanning in progress. Moreover, it is possible to save a given setting of the parameters to a file an retrieve
it in a second moment (see pag.333).
The parameters, which must be defined by the user and must be used by the Network Scan modality, are
the following:
IP addresses which must be scanned. One or more ranges of addresses and/or single IP address
can be defined.
Scheduling of execution of the cyclic scanning: once per day or continuous each X (hours:min-
utes) and number of IP addresses which must be scanned at the same time each X (seconds).
Example. Suppose that the cyclic scanning is set to be continuous each 3 hours and that, at each
scanning, 5 equipment must be scanned each 4 seconds. The IP addresses to scan in total count-
ing groups and single addresses are 15.
The scheduling of the cyclic scanning will take place as displayed in the following figure.
Interrogation Interrogation
4s 4s 4s 4s
5 IP Add. 5 IP Add. 5 IP Add. 3h 5 IP Add. 5 IP Add. 5 IP Add.
When the NE is created (automatically or manually by means of command of the Auto Dis-
covery table), if the map where the object must be created (map A) is different from that cur-
rently open (map B), the creation of the NE object will take place in the following way:
If the map A is open in Read-Write modality, the object is created and dynamically dis-
played in the map.
If the map A is open in Read Only modality, the object is created but not displayed. It is
necessary to execute a Refresh command on the map in order to display it.
Container where the NE symbol must be possibly created.
If the container is not present in the set map, on the creation of the NE object, the container
will be automatically created too.
The NE object is not directly created into the container set by the user, but in the following
path:
/ <container set by the user> / <year> / <year/month> / <day/month/year>
Example. Suppose to have set the container Station-A. On June 23th 2009 the equipment AL24
is created (automatically or manually by means of the command of the Auto Discovery table)
and the corresponding symbol will be created in the container:
Station-A / 2009 / 06/2009 / 23/06/2009
The procedure to set the parameters for the execution of the Network Scan modality is reported at
pag.330.
Once the execution parameters have been defined, it is necessary to activate the Network Scan modality.
The modality is automatically activated if at least one IP address or a group of IP addresses has been set
and the configuration has been saved by means of the command Save as Active Conf (Fig.53).
The Network Scan modality remains active until when the user deactivates it removing all the values
present in the areas Range IP Addresses and Specific IP Addresses (Fig.53) and saving the new setting by
means of the command Save as Active Conf.
The procedure to activate and deactivate the Network Scan modality is respectively reported at pag.330
and pag.332.
NE Wake Up modality
The NE Wake Up modality has the purpose to detect new equipment in the network not managed yet by
NMS5UX-B.
In this modality, the supervision system intercepts the Wake Up notifications sent by the equipment and
containing the information necessary to the connection and the management of the equipment itself.
When a Wake Up trap is intercepted, the NMS5UX-B system carries out the following actions:
It disables the sending of Wake Up traps by the equipment (trap switch-off).
If the equipment which sent the trap:
Is NOT managed yet by NMS5UX-B, this inserts it in the list of detected equipment and,
if configured by the user, creates and connects the relevant NE object.
Is already managed by NMS5UX-B but with a type different from that pointed out in the
network for the specific IP Address, a notify of type change is inserted in the Auto Dis-
covery table.
Example. Suppose that an EL series equipment with address 172.22.13.6 is managed by
NMS5UX-B. At a given moment, the EL equipment in the network is replaced by an ALplus
equipment. The address 172.22.13.6 is assigned to the new equipment.
If the user activates the NE Wake Up modality and defines that the address 172.22.13.6
is included in the scanned IP addresses, on the detection of the 172.22.13.6 address a
notify of type change is inserted in the Auto Discovery table.
The Wake Up notification is a SNMP trap sent by the equipment to the supervision system to notify its
presence in the network.
The configuration of the Wake Up trap (activation or not of the trap, IP/NSAP address of the machine which
In order to work, the NE Wake Up modality must be activated by the user. Before activating it, it is nec-
essary to define the operating parameters of the modality.
Then it will be possible to modify, in any moment, one or more parameters and establish if activating im-
mediately the new configuration or, if the modality is already active, waiting for the expiry of the current
scanning in progress.
Moreover, it is possible to save a given setting of the parameters to a file an retrieve it in a second moment
(see pag.333).
The parameters, which must be defined by the user and must be used by the NE Wake Up modality, are
the following:
Action which must be automatically executed on the detection of a new equipment. It is possible
to choose among one of the following equipment:
Insertion in the Auto Discovery table, creation and connection of the relevant NE symbol.
Insertion in the Auto Discovery table and creation of the NE symbol.
In this case, the equipment can be connected in a second moment.
Only insertion into the Auto Discovery table.
In this case, the equipment can be created in a second moment by means of the com-
mand present in the Auto Discovery table (pag.336) or by the command Edit > Add
(pag.150) and connect it.
Map where the NE symbol must be possibly created.
When the NE is created (automatically or manually by means of command of the Auto Dis-
covery table), if the map where the object must be created (map A) is different from that cur-
rently open (map B), the creation of the NE object will take place in the following way:
If the map A is open in Read-Write modality, the object is created and dynamically dis-
played in the map.
If the map A is open in Read Only modality, the object is created but not displayed. It is
necessary to execute a Refresh command on the map in order to display it.
Container where the NE symbol must be possibly created.
If the container is not present in the set map, on the creation of the NE object, the container
will be automatically created too.
The NE object is not directly created into the container set by the user, but in the following
path:
/ <container set by the user> / <year> / <year/month> / <day/month/year>
Example. Suppose to have set the container Station-A. On June 23th 2009 the equipment AL24
is created (automatically or manually by means of the command of the Auto Discovery table)
and the corresponding symbol will be created in the container:
Station-A / 2009 / 06/2009 / 23/06/2009
Fig.20 displays an example.
The procedure to set the parameters for the execution of the NE Wake Up modality is reported at pag.332.
Once the execution parameters have been defined, it is necessary to activate the NE Wake Up modality.
The modality is activated (deactivated) activating (deactivating) the Manage Wake-up trap option and sav-
ing the configuration by means of the command Save as Active Conf (Fig.53).
The procedure to activate and deactivate the NE Wake Up modality is reported respectively at pag.332 and
pag.333.
After having graphically represented the network, it is necessary to activate the connection, then the com-
munication, between the NMS5UX-B system (logic NE objects created by the users) and the peripheral area
(physical equipment).
LEGACY protocol the connection procedure (pag.111) is preceded by the opening of the serial
ports (pag.109) that are physically connected to the equipment themselves.
SNMP protocol execute immediately the connection procedure (pag.111) because it is assumed
that the correct operation of the physical connection between the equipment and the supervi-
sory system is ensured by the TCP/IP network.
The opening of the serial ports is NECESSARY ONLY for the Legacy equipment.
For the SNMP equipment do not execute this operation, but pass immediately to the connection (pag.111).
For the Legacy equipment, before starting the connection procedure, it is necessary to activate the man-
agement processes of the serial ports to which the equipment themselves are physically connected.
This procedure is usually defined to open a serial port.
It is possible to connect the Legacy equipment to the supervision centre by means of the serial ports of
CommServer-S or the serial port (if properly configured) of IPBOX.
According to the hardware elements provided with the system, it will be necessary to open the serial ports
of the CommServer-S (represented by the CSB Port symbols present into the Equipment window of the
CommServer-S) and/or the serial port of the IPBOX (represented by the Comm Server B Port symbol
present into the Equipment window of the IPBOX).
It is not necessary to open all the serial ports present into the network but only the ones connected
with the equipment to be managed.
Before opening the serial ports, it is necessary to activate the connection of the relevant equipment
(Comm. Server-S/IPBOX) and the supervision system.
CommServer-S
1. Connect the equipment using the Command > Communication Server Board > Connect command
(pag.259).
IPBOX
1. Connect the equipment using the Command > Connect > Network Element command (pag.244).
The opening procedure of the serial port involves the management of the polling process relevant to the
equipment group connected to the port under examination. The HDLC polling process and the return of the
alarms/events will be activated at the connection of the equipment.
During the opening of each single port, the user will have to set the values of the T and N parameters that
define respectively the time and the transceiving number of a message before that the system would con-
sider an equipment as an unreachable one. The default values are T=10 and N=2. Then, it is possible to
define the time range between the polling of an equipment and the next one.
Usually the opening procedure of the serial port, if the connection of the relevant Comm. Server or IPBOX
object has been successfully ended, is correctly executed.
If the connection procedure of the Comm. Server or IPBOX has not been successfully executed, check the
following conditions:
The IP Address assigned to the NEs object is equal to the one assigned during the local config-
uration.
The equipment is turned on and correctly connected to the supervisory system.
ONLY if the equipment is inserted into an OSI network, check that the NSAP (Gosip) Address
assigned to the NE object coincides with the NSAP (Gosip) Address assigned during its local con-
figuration.
After having opened a serial port, it is possible to close it (it is deactivated the relevant managing process).
The operation is not accepted if there is also a single NE in connected status connected to the port to
be closed.
Closing the serial port, it will not possible longer to connect the equipment physically connected to the port
itself. Then, the polling process, relevant to the equipment group connected to the port under examination,
is not managed longer. Also the Comm. Server and IPBOX can be always disconnected if any of the serial
ports present into them is in open status.
A port can be automatically closed by the system after a supervisory loop or for an overflow of alarms
on the serial port itself.
The automatic closing procedure is executed independently from the connection status of the equipment
connected to such ports.
At the end of the procedure, the equipment connected to the port under examination will results unreach-
able, with the exception of the ones that were disconnected before the procedure; Such ones do not change
their status.
Supervisory loop. The supervisory network is overplaced to the transmission network enabling the prop-
er interfaces. The transmission network can be configured as a loop, on the contrary the supervisory net-
work does not allow this configuration type.
In a loop configuration, the propagation mode of a message causes the re-typing of the message itself,
after having run into the entire loop, into the same supervisory port from which it has entered. In such a
way, it will reach the most upstream equipment present into the propagation chain of the messages, until
to reach the serial port from which such a message has been forwarded.
Usually, when the supervisory system receives the same message that it has forwarded, it automatically
disables the serial port. In such a way, the message forwarded by the centre continues to run into the loop.
This situation is called supervisory loop.
When the user sends the connection command, the NMS5UX-B system sends a test message to verify the
reach ability of the equipment (Line Test).
At the first connection the system, having no information stored in the database, acquires all the informa-
tion from the NE.
Then, if the equipment is managed with the Legacy protocol, the system will forward the messages relevant
to the configuration only when it is changed a parameter. On the contrary, the alarm status is periodically
get by means of a polling cycle (pag.119).
If the equipment is managed with the SNMP protocol, the equipment itself will spontaneously inform the
supervisory system about possible changes concerning the configuration or the status of the alarms (SNMP
trap). A polling cycle from the supervisory system is kept only to check the reachability status of the equip-
ment.
The connection of an equipment causes the automatic insertion of the equipment itself into the specific
polling cycle.
Only after that an equipment has been connected at least once, it is possible to open the relevant equip-
ment window.
In order to modify the connection status of an equipment or to execute some tests or to re-align the infor-
mation stored in the database, the following commands are available:
The Line Test command checks the real reach ability of the equipment.
The check consists in the request of the NMS5UX-B system to an NE of the value of the chosen parameter:
if the NE answers, the test has successful result, otherwise it fails.
All the NE, independently from their type or connection status, are programmed to answer to the test
message. Furthermore, the sending of the command does not influence the connection or alarm status of
the Network Element.
For the use of the command, refer to the par. Line Test (pag.242).
Connect command
The Connect command activates the connection between the NMS5UX-B system and the remote equip-
ment.
At the end of the procedure, if the result is positive, the system will be able to communicate with the NE,
it will have all the information relevant to the current status of the alarms and to the configuration and will
have sent the network time to the equipment.
It is not possible to connect an equipment in connected status. Furthermore, the connection command
towards an equipment in unreachable status is automatically sent by the system at regular intervals.
For the use of the command, refer to par. Connect (pag.244).
Disconnect command
The Disconnect command deactivates the connection between NMS5UX-B and the remote equipment: the
system stops the management of the present NE.
The disconnection of an equipment does not involve the deletion of the relevant information from the
database; they stay stored, even if the equipment is disconnected; the user can open the relevant equip-
ment window where the last acquired configuration is displayed.
For the use of the command, refer to par. Disconnect (pag.246).
It is suggested to select the command only when you suppose that a misalignment between the alarm
information known by the NMS5UX-B system and the real alarm situation present on NE occurred. In fact
this command does not represent the normal procedure to acquire the operating status of an equipment.
For the use of the command, refer to par. Alarm Re-alignment (pag.252).
The Configuration Upload command re-aligns the information, relevant to the configuration and the
alarms, stored in the database to those really present in the equipment.
The execution mode of the procedure is fundamentally equal to the one used for the execution of the re-
aligning procedure on the alarms (pag.113); the only difference is that the system requires to the equip-
ment the status of the alarms and also the configuration information relevant to all the objects known by
the equipment itself. Also in this case, the information replace the ones recorded into the database.
This operation does not influence the status of connection of the NE.
It is suggested to select the command only when you suppose that a misalignment between the alarm
information known by the NMS5UX-B system and the real configuration and operating status of the NE
occurred. In fact this command does not represent the normal procedure to acquire the information rele-
vant to an equipment.
For the use of the command, refer to par. Configuration Upload (pag.254).
Legacy-Reset&Connect command
The command is forwarded only if it has been selected one or more Legacy equipment.
For the SNMP equipment the forwarding of the command under examination is not available because it
could be equal to the forwarding of the Connect command.
The Legacy-Reset&Connect command removes all the information stored into the database, relevant to
the equipment configuration and then activates the connection between the supervisory system and the
equipment itself.
At the end of the procedure, if it has been successfully executed, the system will be able to communicate
with the NEs as after a normal connection procedure; it will have get all the information relevant to the
configuration and to the functional status of the NEs then the NEs themselves will be automatically inserted
into the polling cycle.
This command has to be selected only in extreme cases, when the user supposes that it is present a
misalignment situation between the alarm information known by the supervisory system and the real sit-
uation present into the NEs. The duration of the reset and connection operation is usually longer than the
one of a normal connection because the entire configuration of the NE is transferred from the peripheral
part to the supervisory centre.
The connection status of an equipment shows to the user if the equipment is managed by NMS5UX-B and,
if managed, its operating status (alarms). The status of an equipment are:
Disconnected (pag.114)
Connected (pag.114)
Unreachable (pag.115)
Maintenance (pag.115)
In the UX Map Manager window, the current status of an equipment is represented by the colour of the
relevant NE symbol. In fact, one or more colours correspond to each status (pag.40).
The colour of the NE symbol influences also the colour of the Container symbols that contain the equipment
in the following way. If a container:
Contains at least one connected NE, the Container object will assume the colour relevant to the
connected status: green (if NE is not alarmed) or light blue/yellow/orange/red (if the NE is
alarmed).
Contains more connected NEs or other Container objects, the colour of the Container object will
be determined by the colour of the NE or Container symbol where the most serious alarm is
present.
The colour of the NE icon in maintenance status does not affect he colour if the Container icons where
it is present the NE. For instance, if into a Container object there is an equipment in connected status (gre-
en colour) and an equipment in maintenance status (pink colour), the Container icon will get the colour
relevant to the connected status (green).
Disconnected status
Initial status of an NE just after its creation; then it is the status reached after a disconnection command.
In this condition, the equipment is not managed by the system: no message is sent or received and no
polling procedure is executed.
Conditions/commands that determine the PASSING FROM ONE STATUS TO THE OTHER
After the sending of the Connect or Legacy-Reset&Connect command:
If the operation is successfully, the equipment passes to connected status.
If the operation fails, the equipment passes in an unreachable status.
Connected status
Status reached after a connection procedure gone well. In this condition, the equipment correctly answers
to the system polling.
During the period when the equipment is connected, the user can send commands and require information.
Only exception to this rule is the presence of LCT in Configuration modality (pag.116).
Condition/commands that determine the PASSING FROM ONE STATUS TO THE OTHER
After:
The user sends the disconnection command, the equipment switches to disconnected status.
A system polling, if the equipment does not send any answer, the status from connected be-
comes unreachable.
If there are more alarms of different severity on the equipment at the same time, the colour of the NE
symbol will represent the most serious alarm.
Unreachable status
This is the status reached when the equipment, thought the automatic repetition of the messages, does
not answer to the polling of NMS5UX-B or sends unknown messages. In this condition, the NE is not man-
aged by the system, which however sends a connection command at regular interval.
Conditions/commands that cause the PASSING FROM ONE STATUS TO ANOTHER ONE
After the user or the NMS5UX-B system has sent the connection command (automatic re-connection):
If the operation is successful, the equipment passes to connected status.
If the operation fails, the equipment remains in unreachable status.
After an user has sent the disconnection command:
If the operation is successful, the equipment passes to disconnected status.
If the operation fails, the equipment remains in unreachable status.
Maintenance status
LOM/LCT term means the software application, developed to manage/control locally the equipment: Local
Operator Manager, Local Craft Terminal, WEB Local Craft Terminal.
The operations that can be executed via LOM/LCT are basically those that can be executed via NMS5UX-B.
More information on the use of the LOM/LCT program is reported in the specific documentation. Here
below only some indications are reported about the relationships between LOM/LCT and NMS5UX-B:
The local user can activate the LOM/LCT-equipment connection in Monitoring modality (the user can only
verify the equipment configuration) or in Configuration modality (the user can both verify and modify the
equipment configuration).
Monitoring, does not influence the acquisition of the alarms or the sending of commands by the
system: the NMS5UX user can open the equipment window and verify/modify the equipment
configuration itself.
Configuration, if the NE is:
Managed with Legacy protocol, it is not possible to change the configuration parameters
or to forward commands: the NMS5UX user can not open the equipment window.
Managed with SNMP protocol, influences the acquisition of the alarms or the sending of
the commands by the system.
The NMS5UX user can open the equipment window (except for the equipment of PMP
type) but it cannot modify the configuration and send commands with the following ex-
ceptions:
Execute the software reset of an equipment (pag.261)
Transfer the configuration of an equipment to another one of the same type
(pag.256)
Updating the equipment software (pag.400)
Forcing the disconnection (logout) of a LCT user (pag.381)
During the period when the connection is active, no modification relevant to the alarms is sig-
nalled to the NMS5UX-B system.
When the local LCT-equipment connection is deactivated, the NMS5UX-B system automatically
re-aligns the configuration (sending of the Configuration Upload command - pag.113) to con-
trol possible changes executed by the local user and to acquire the current alarms.
If the local user has changed the configuration of the remote equipment, the new values are
acquired and replaced to those previously present stored in the database.
The activation and the deactivation of the local connection, both in Monitoring and Configuration modality,
are spontaneously communicated by the equipment to the NMS5UX-B system and signalled to the user:
In the map, a check sign is indicated next to the NE icon ( ) is indicated next to the NE icon.
This information is forwarded also to the Container objects containing the NE.
Furthermore, the activation of the local connection in Configuration modality is signalled to the
user in the map: the NE icon assumes the white colour.
This information is not forwarded by the Container objects that contain the NE symbol. For
example, if a Container object contains a connected NE (green colour) and an equipment which
the LCT program in Configuration modality is connected (white colour), the Container symbol
will assume the colour relevant to the connection status (green).
In the Alarm History Browser window (Fig.39), Current Alarms Browser (Fig.41), Equipment
Browser [List/Locate] (Fig.36), Information (Fig.23).
In the equipment window of the NE.
The description reported here below can be applied only for the SNMP equipment.
The NMS5UX user can enable/disable the LCT user to connect to the equipment in Configuration modality
setting the LCT Config.
Independently from the previous setting, when the equipment is switched off and switched on or reset, the
LCT Config parameter is automatically set to the Enabled value.
The command to set the LCT Config parameter is present in the equipment window. Besides the status of
the LCT Config parameter is displayed in the Equipment Browser [List/Locate] equipment (Fig.36).
Functionality of primary importance of the NMS5UX-B system is the detection, visual signalling and cen-
tralized storing of the alarm/status/event signallings present in the equipment that manages.
The alarm term defines the fault signalling generated by an error or by a bad operation of the NE or of
any element that composes it.
The status and event terms identify the signallings that do not indicate a bad operation but a status
change, a running operation or an operation condition. In detail, the signallings of:
Status, are communicated spontaneously from the NE to the system, as for example:
The activation/deactivation of the LCT-equipment connection.
The start/end of the updating of the software of the equipment.
The activation/deactivation of the manual operations.
The status of active/stand-by of duplicated parts of NE.
Event, are generated by the system itself, as for example the start of an operation of alarm re-
alignment.
In the following of the chapter, the alarm generic term indicates the alarm/status/event signalling.
The acquiring process of the alarms changes according to the type of protocol used by the equipment. With
details for the equipment:
Managed with the Legacy protocol, the acquiring of the alarms is executed by means of a polling
process by the supervisory centre (pag.119), through the serial interfaces of the Comm Server
and/or IPBOX, toward all the equipment in connected status.
Managed with SNMP protocol, the detection and reset signals of an alarm are spontaneously for-
warded to the supervisory centre by the equipment (trap SNMP). A polling process executed by
the supervisory centre is kept only to check the reachability status of the equipment.
The equipment in disconnected or unreachable status are not cyclically subjected to polling. It is possible
to force the acquisition of the alarms of an equipment using the Alarm Re-alignment (pag.252) or Con-
figuration Upload command (pag.254).
Polling
The contents of the subject paragraph refer to the Legacy equipment. For the SNMP equipment
the polling process executes only the checking of the reachability of the equipment themselves, and does
not collect the alarms.
Polling execution
Each CS/IPBOX port autonomously executes the polling process relevant to the local equipment (directly
connected) and to the remote ones (connected in cascade by means of EOC, service channels, etc.). In
such a way, the acquiring times of the alarms are strongly reduced because for a high dimension network
it is not executed a single polling process but as much processes as are the managed and in open status
CS/IPBOX ports.
The polling process is managed by a properly devoted program, loaded into the CommServer for the CS
ports and into the IPBOX for the IPBOX port. Such a programs makes cyclically available the connection
line for each single equipment connected to the same CS/IPBOX port. The equipment involved into the poll-
ing cycle communicates to the supervisory system all the detected changes, if the alarm status has
changed from the last polling time. After having forwarded all the information, the connection line will be-
come available for the next equipment.
The duration of the polling cycle changes according to the number of equipment connected to the CS/IP-
BOX port and to the quantity of the transmitted alarms.
Though every alarm is timestamped (by the remote equipment at the occurrence of such an alarm), the
duration of the polling cycle or the query sequence of the equipment into such a cycle will not affect the
correct displaying of the alarm information for the user.
The polling procedure, executed between CS/IPBOX and equipment, is completely transparent for the user:
it is automatically executed without affecting the operations executed by the NMS5UX user.
But since the connection line between the serial port and the relevant equipment group is a single one, the
forwarding of a command executed by the centre is a priority one with respect to the cyclic polling process.
In fact, when it is forwarded a command (for instance, the change of a parameter), to an equipment A, if
the polling process of an equipment B is on progress, the system waits for the end of the polling operation
on the equipment A. After that it executes the command and then restart again the polling procedure from
the step it has been suspended on the equipment B.
The activation of the local connection between the equipment and the LOM/LCT program does not affect
the automatic acquiring of the alarms for the equipment under examination.
At each change of the status of the alarms on the equipment present in the network, the NMS5UX-B system
informs the user by means of the UX Map Manager window, executing the following operations:
If present in the open map, the NE symbol where the alarm has been detected changes colour
according to the severity associated to the alarm.
If a alarm more serious than the detected one is present on the equipment, the icon does not
change colour, because it is determined by the alarm more serious present on the equipment.
The NE icon reports also the information that a not yet checked alarm is present.
The status of the NE (change of colour and presence of a not yet checked alarm) is signalled
also by the Container symbols that have, inside them, this NE (the colour of the Container icons
changes).
The colour of the Container symbol is determined by the colour of the NE symbol contained in-
side it, where the most serious alarm is present.
If open, in the Alarm History Browser window (Fig.39) the record relevant to the detected alarm
is added.
If open, in the Current Alarm Browser window (Fig.41) the record relevant to the detected alarm
is added.
If open, in the equipment window relevant to the NE, where the alarm has been detected, the
NE symbol is graphically modified.
If the equipment window has Read Only access the alarm is not signalled, as the window is not
dynamically updated. To update the alarms, it is necessary to require a new reading of the table
relevant to the current alarms.
In the Alarm History Browser and Current Alarm Browser window if:
Some filters are active, it is possible that the record is not added as it does not satisfy the set
filtering criteria.
The freezing of the window is activated, the record is not added.
The alarm correlation term means the functionality that puts in relationship, in the alarm history, the ac-
tivation of an alarm with that of its clearing.
In detail, in the Alarm History Browser window (Fig.39) the notification of the activation of the alarm is
displayed by a record where the date/time of activation of the alarm activation is displayed. The clearing
of the same alarm is indicated adding, to the already existing record, the indication of the deactivation
date/time.
After a forced alignment of the alarm status, not all the notifications of the alarms active on the equipment
are recorded, but only the possible new alarms.
Furthermore, after the forced realignment, for the alarms that are not active anymore, the deactivation
date/time will be inserted in the relevant record.
If an equipment is disconnected, all the (detected and detected/cleared) alarms relevant to that equip-
ment are removed by the alarm history.
It is possible to save the alarm history stored in the NMS5UX-B database. In detail, it is possible:
To save all the alarm history to tape and/or to disk present in the database (pag.423).
Then, it will be possible to recover the data (pag.424) and display them in the Old History Brows-
er window (Fig.42).
To save to file the whole alarm history (or a part) present in the database of the system
(pag.267).
To save to file the whole alarm history (or a part) recovered from tape or disk (pag.281).
Each alarm, acknowledged and managed by the NMS5UX-B system, has associated a severity which de-
termines the alarm importance.
The alarm severity is the criterion used by NMS5UX-B to represent graphically the operational status of the
equipment.
When an alarm raises in a connected alarm, the icon that represents the equipment modifies its colour
according to the severity of the active alarm present inside it.
The colour of the Container symbols containing the NE reflects the condition of current alarm.
If more alarms of different severity are present at the same time, the colour of the icon will represent the
most serious alarm; the same occurs for the container icons.
The severity of an alarm is reported also in the Alarm History Browser (Fig.39) and Current Alarm Browser
(Fig.41).
The contents of the subject paragraph can be applied only for the SNMP equipment.
The NMS5UX-B system allows modifying, for each alarm, the severity of network and the local severity.
Network severity means the severity that characterizes the alarm when displayed by the NMS5UX-B sys-
tem. For each alarm, the network severity is COMMON to all the NEs of the same type present in all the
maps. To modify the network severity of an alarm, use the SNMP-Network Severity Code command
(pag.368 - command available only to the Superuser).
Local severity means the severity that characterizes the alarm when stored by the controller of the NE and
displayed by the local management system (LCT); this severity is not used by NMS5UX-B. For the same
alarm, it is possible to define a local severity different from NE to NE. To modify the local severity of an
alarm, use the SNMP-Equipment Severity Code command (pag.370).
Example
Suppose that two types of SDH Radio are connected to the NMS5UX-B system: NE-A and NE-B.
By means of the SNMP-Equipment Severity Code command, it is defined that, locally, the alarm x for
NE-A has severity Major, while for the NE-B has severity Minor.
Instead, using the SNMP-Network Severity Code command, it is defined that the alarm x for all the NEs
of SDH Radio type of Critical severity.
In the NE-A, the detection (or cleared) of the alarm x will be stored in the controller of the NE and seen by
LCT with Major severity, while it will be seen by NMS5UX-B with Critical severity.
Instead, in the NE-B, the detection (or clearing) of the alarm x will be stored in the controller of the NE
and seen by LCT with Minor severity, while it will be seen by NMS5UX-B with Critical severity.
What described below is valid for all the alarms (of all the types of SNMP equipment) with the exception of
the alarms used by the user input.
The severity of the alarms of User Input is defined by means of a specific command present in the equip-
ment window.
This severity constitutes both the network and the local severity.
For example, if the User Input x alarm for an equipment is defined having a Critical severity, on its detec-
tion the alarm will be stored in the controller of the NE, seen by LCT and by NMS5UX-B with Critical sever-
ity.
The setting of the severity is independent for each alarm of User Input, and local to the NE selected for the
operation. This means that the setting must be executed for each single alarm of user Input of each single
NE.
More information on the user inputs and on the command to modify the severity is reported in the equip-
ment manual of the NMS5UX-B.
The contents of the subject paragraph are valid only for the SNMP equipment.
The NMS5UX-B system allows enabling/disabling the alarms and/or the sending of the relevant traps. In
detail, it is possible:
To disable the alarm; in this case the detection (or clearing) of the alarm is not recorded in the
controller of the NE and it is not communicated to the supervision program: as the alarm has
never occurred.
To disable the sending of traps; in this case, the detection (or clearing) of the alarm is recorded
in the controller of the NE, but it is not communicated to the supervision system.
The enabling/disabling of the alarm and of the trap sending is independent for each alarm, and local to
the selected NE for the operation. This means that the setting must be made for each single alarm of each
single NE.
To enable/disable the alarms and the sending of traps of an equipment, use the SNMP-Equipment Se-
verity Code command (pag.370).
It is possible to verify the list of the NEs that have at least one disabled alarm/trap opening the Equipment
Browser [List/Locate] window (Fig.36) and configuring properly the filter.
Sometime there can be that, in an equipment, an alarm is detected and is cleared many times in a brief
period.
The instability that characterizes these alarms, defined fleeting, causes a such number of alarms to satu-
rate the network. In fact, each time the alarm raises/clears, the system records a signalling.
For this cause, before recording an alarm, the stability of the alarm itself is verified.
The criterion used to determine if an alarm is fleeting or not is the following: an alarm is considered fleeting
when NMS5UX-B, during a period of time t, records that the number of activation of the alarm is higher
than the thr_in threshold.
An alarm will not be considered fleeting anymore if, during the successive period of time t, the number of
activation of the alarm is lower than the thr_out threshold.
Example
In the Alarm History Browser window, when an alarm exits from the fleeting status and the last signalling
came to the equipment pointed out the deactivation of the alarm, the management of the signalling alarm
will take place without differences with respect to a normal signalling of cleared alarm: the alarm is corre-
lated to the previous signalling.
Differently, when an alarm exits from the fleeting status and the last signalling came to the equipment
pointed out the activation of the alarm, the management will take place in the following way: first a sig-
nalling of cleared alarm will be forwarded, which will be correlated with the previous signalling of fleeting
alarm, and then a new signalling of active alarm of active alarm will be forwarded: in the Alarm History
Browser window, a record of fleeting alarm will be displayed, followed by a record of active alarm.
The fleeting condition of an alarm is not deleted at the forced realignment of the status of the alarms
(Alarm Re-alignment command - pag.252).
The current alarms and those present in the alarm history can be marked: in the relevant window there is
the indication that the user acknowledged the detection or/and the clearing of the alarm.
For the alarms stored in the alarm history and listed in the Alarm History Browser window (Fig.39) or in
the Old History Browser (Fig.42), it is possible to mark both the detection and the clearing of the alarm
(pag.267).
An alarm:
Detected and marked is identified by the letter S in the Ack column of the Alarm History Browser
or Old History Browser window.
Detected/cleared and marked is identified by the letter C in the Ack column of the Alarm History
Browser or Old History Browser window.
When the list of alarms is filtered or in the windows where the total number of marked alarms, the rules
to define if an alarm is considered marked or not are the following.
In this case, even if the user has marked the detection of the alarm (presence of the letter
S), it is considered as not marked because the user has not marked its clearing.
For the current alarms, listed in the Current Alarms Browser window (Fig.41), there is not the above men-
tioned distinction, because it is possible to mark only the detected alarms (pag.275).
With NE Log (Network Element Log) we mean a file where are recorded the signals of alarm/status (alarms)
stored in the controller of a SNMP equipment.
The Log read by an equipment (NE Log) is stored into the machine disk, available for the next reading by
the user.
The creation of a NE Log can be manually done by the user and/or automatically by the system.
The manual creation of the NE Log of one or more equipment can be done by the user by means of the
command Fault > SNMP-NE History Log (pag.287).
By means of the commands, it is even possible to manage the NE Logs (delete, display the content) and
delete the alarms stored in the controller of a SNMP equipment.
The automatic creation of the NE Logs, if the relevant function is active, consists in the automatic creation
of the NE Log for the SNMP equipment which pass from the unreachable status to the connected status.
The function for the automatic creation of the NE Logs can be activated/deactivated by the system admin-
istrator during the installation of the NMS5UX system itself.
The NE Logs can be displayed only through the Equipment History Log Management Main Window (Fig.43).
The quality of the signal of the telecommunication equipment can be controlled via measures of Perform-
ance Monitoring (PM).
A measure of PM consists in recording, during a set time period (observation period), the values of deter-
minated control parameters (BER, alarm counting, etc).
Threshold limits (that can be modified by the Superuser) have been assigned to these parameters.
The exceeding of threshold limit indicates a more or less serious degradation of the signal. This condition
generates an alarm, which is recorded and managed by the equipment and by the NMS5UX-B system as
any other alarm.
The number and the type of measures of PM and the relevant control parameters are specific for each
type of NE. For their description, refer to the relevant equipment Manuals.
The considered control parameters changes according to the type of equipment and of measures that this
equipment supports. Generally, all the executed measures refer to Recommendations of ITU-T (for exam-
ple G.826, G.821, etc.).
It is possible to activate/deactivate the measures for a single equipment at a time or for more equipment
(of the same type) at the same time.
Furthermore, for each equipment, it is possible to activate/deactivate each single measure independently.
The command to activate/deactivate singly the PM measures is present in the specific equipment window.
The description of the equipment window and the procedure for the activation/deactivation of the PM me-
asures are contained in the equipment Manual relevant to the type of considered NE.
The command to activate/deactivate the measures for more equipment (of the same type) at the same
time is View/Modify PM Status (pag.181).
When a PM measure is activated, the controller of the equipment begins the storing of the values of the
control parameters.
The results of the measures are subdivided in records. Each record contains the values recorded in a spe-
cific time interval (observation period).
If, at the end of the observation period, the measure has not been deactivated, another observation period
begins and so on until the measure is not stopped.
When the system interrogates the equipment, this will send to it the records (daily and primary) that
stored.
The equipment managed by the NMS5UX-B, group the results of the PM measures in observation period of
15 minutes (primary records) and 24 hours (daily record).
The observation periods are not synchronized with the instant when the measure is activated, but refer,
for the primary records, to the quarter (00.00, 00.15, 00.30, etc.) and, for the daily records, to the time
00.00 UTC (Universal Time, Coordinated).
For example, if a measure starts at time 11.40, the first primary record will have, as observation period,
11.40...11.45 (corresponding to the interval 11.30...11.45), while the first daily record will have, as ob-
servation period, 11.40...00.00.
For each type of measure, the equipment keeps in memory the last 16 primary records (corresponding to
the last 4 hours) and the last 2 daily records (corresponding to the last 2 days). The previous records are
overwritten.
If an equipment has PM measures running and it is restarted or switched off, then, when it restarts to it is
switched on, the measures active before the switching off will be automatically restarted.
The (daily and primary) records relevant to the period when the measure has been interrupted will be emp-
ty and, if reached the limit of 16 primary records and 1 daily record, will overwrite the previous ones.
The results of the PM measures are acquired by the NMS5UX-B system by means of a polling process (PM
polling) that is executed at regular interval that can vary from 1 to 4 h. The frequency for the request of
the PM information by the system to the equipment is determined by the function Tx15 minutes. The value
T, by default, is 8 (8x15min=2h), but it can be changed by the Superuser from 4 (4x15min=1h) to 16
(16x15min=5h).
The process of PM polling is managed by a dedicated program which, besides executing the polling, has
the function to determinate which equipment must be polled.
The rules that an equipment must satisfy to be polled are the following:
Equipment type. Not all the equipment managed by the NMS5UX-B system supports the PM func-
tion. This equipment are not considered in the PM polling cycle.
Equipment status. Only the equipment in connected status are polled. The equipment in disconnect-
ed or unreachable status are not polled.
Status of the PM measures. Only the equipment that have at least one measure active in progress
when the PM polling is executed.
After a PM polling, the polled equipment sends the daily and primary records relevant to the measures in
progress.
If the measure is deactivated, when the NMS5UX-B system executes the polling, the equipment sends all
the (primary and daily) records calculated until that moment, except the last one.
For example, if the measure is activated at 9.27 and deactivated at 18.42, the record relevant to the ob-
servation period 9.15...9.30 is transferred to the system in incomplete status, while the record relevant to
the period 18.30...18.45 is not sent.
If the measure is activated and deactivated more times during the same observation period, the record
containing the results of the last executed measure will be sent to the NMS5UX-B system.
For example, if the measure is activated at 9.02 and deactivated at 9.07, then it is re-activated at 9.09,
the record relevant to the observation period 9.00...9.15 will contain the results of the measures relevant
to the period 9.09...9.15, while the results relevant to the period 9.02...9.07 will not be sent.
The PM polling is totally transparent to the user: it is automatically executed without affecting the opera-
tions executed by the NMS5UX user.
Being the only connection line between the system and the equipment, the sending of a command by the
centre is prioritary with respect to the process of cyclic polling.
For example, when a command is sent to an equipment A during the polling of an equipment B, the system
waits for the end of the polling in progress. After this, it executes the command towards the equipment A
and, then, it restarts the polling procedure from the point it has been suspended on the equipment B.
The activation of the local LCT-equipment connection does not affect the automatic acquisition of the re-
sults of the PM measures for the considered equipment.
The NMS5UX user can anytime display the results of the PM measures of a given equipment, subdivided
in daily or primary records of the last 180 days.
To display the daily and primary records, select the equipment in the map and choose the Performance
Monitoring command (pag.173).
It is also possible to display the results of the PM measures, previously saved to disk by means of the Old
Performance Monitoring command (pag.177).
It is possible to save the results of the PM measures stored in the database of the system. In detail, it is
possible:
To save to tape and/or disk all the results of the PM measures relevant to a month present in
the database (pag.426).
Then, it will be possible to recover the data (pag.427) and display them in the Graphic Perform-
ance Monitoring - OLD window (pag.177).
To save on file the results (present into the system database) relevant to a specific measure-
ment for all the selected NEs of the same type (pag.179).
During the saving operations, it is possible to forward the file to a user, via e-mail.
The data are saved in ASCII format, that can be detected by the great part of the text processing
programs and of the electronic sheets.
NMS5UX, point out the commands relevant to the management of the NMS5UX-B system.
Legacy..., point out the commands relevant to the equipment managed with the Legacy proto-
col ONLY.
Such commands are present into the menus only if the modules for the management of the Leg-
acy equipment have been installed.
SNMP..., point out the commands relevant to the equipment managed with the SNMP protocol
only.
The commands with the label that does not point out the Legacy or SNMP wording, are relevant to all the
equipment.
Some commands are optional ones. Therefore, such commands can be absent into the specific menu of its
own NMS5UX-B system.
For each command, the type of access to the system (Read Only, Read-Write) and the user profile (Entry,
Normal,...) necessary to use it are described. The Reading terms indicates that it is possible to verify the
parameters, the Writing term that it is possible to set or modify them.
The Map Properties command modifies the size of the symbols present in the View area (pag.34) of the
UX Map Manager window (equipment, containers, etc.).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
In the View area, the symbols of equipment, containers, etc. assume the new size.
The Submap Properties command associates a background to the container in such a way that, on its
selection in the View area (pag.34), the background is displayed besides the symbols present in the con-
tainer.
1. Select, in the Map area (pag.32), the container which you wish to associated the background to.
3. To add the background, type in the Background Pixmap box, the path/name of the file and press OK.
The system acknowledges, as background, the files in GIF format.
Press Browse to search the wished file in the disk.
The background is displayed in the View area.
4. To remove the background, delete the file specified in the Background Pixmap box and press OK.
The background is removed in the View area.
The Import/Export command imports/exports/compares the objects from a map to another and saves
the objects of a map into a file.
With details it is possible:
To copy the objects of a map/container to a different map/container (pag.140)
To copy the objects, previously saved to a file, into a map/container (pag.142)
To save the objects of a map/container to a file (pag.142)
To compare the objects of a map/container with the objects of a different map/container
(pag.143)
To compare the objects, previously saved to a file, with the objects of a map/container
(pag.144)
Menu
bar (1)
Parameters
to set to
import/export
the objects
(2)
The result of
the operation
is displayed,
according to
the executed
operation, in
this area (3)
Fig.21 notes
(1) Menu:
File > Close. It closes the window.
(2) Option:
Copy data. It copies the objects from a file or map/container to a different file or map/con-
tainer.
Compare data. It compares the objects of a file or map/container to a different map/contain-
er.
From Map/Submap to Map/Submap. It copies/compares the objects present in a map/con-
tainer into a different map/container.
From File to Map/Submap. It copies/compares the objects present into a file to a map/con-
tainer.
From Map/Submap to File. Copies the objects present in a map/container to a file.
Clear and Copy All. It replaces the objects present into a file or map/container with those
present into a different file or map/container.
Copy Only Differences. It compares the objects present in two different files or maps/con-
tainers and copies into the destination map/container only the different objects.
Box:
Source. File or map/container from which the objects are copied (source).
Destination. File or map/container to which the objects are pasted (destination).
7. Press Apply.
The Messages area displays the detail regarding the executed operation. A record is displayed for each
deleted and/or created object.
5. Set the file into which you wish to save the objects:
6. Press Apply.
The Messages area displays the detail regarding the executed operation. A record is displayed for each
saved object.
7. Press Apply.
The Messages area displays the detail regarding the executed operation. A record is displayed for each
compared object.
7. Press Apply.
The Messages area displays the detail regarding the executed operation. A record is displayed for each
compared object.
List of
maps (1)
To delete a map
The Exit command closes the UX Map Manager window and then the NMS5UX-B graphic interface.
2. Press Ok.
The closure of the UX Map Manager window causes the automatic closure of all the possible open
window of NMS5UX-B (Alarm History Browser, Equipment Information, etc.).
Add (pag.149). It creates objects for the graphic representation of the network in the map.
Delete (pag.156). It deletes the objects from the map.
Modify/View (pag.157). It displays and/or modifies the characteristics of the objects.
Information (pag.160). It displays the information of the symbol.
Graphical Symbol Properties (pag.162). It displays the graphic parameters of the symbol.
Find (pag.163). It searches an object of the map.
Arrange Symbols (pag.164). It aligns vertically/horizontally the symbols.
Generate Info for WEB (pag.165). It checks the database information necessary to the RAN
(Remote Access NMS5UX) application.
Set Current Window Geometry For All Containers (pag.166). It sets the size of the con-
tainers windows such as the size of the window where the command is selected.
These commands are used to represent graphically the equipment network in the maps and to provide
to NMS5UX-B the parameters to manage and control each single object.
Before using them, it is suggested to read the Graphic network representation (pag.78) where the modal-
ities to configure correctly and rapidly one's supervision system are described.
The Add command creates objects for the graphic representation of the network in the map.
With details it is possible:
To create Container objects (pag.149)
To create NE objects managed with SNMP protocol (pag.150)
To create virtual NE objects managed with SNMP protocol (pag.152)
To create NE objects managed with Legacy protocol (pag.152)
To create virtual NE objects managed with Legacy protocol (pag.153)
To create Generic Symbol objects (pag.154)
To create Link objects (pag.154)
To create Label objects (pag.155)
To create Container, NE (SNMP), Link and Label objects described in a file (pag.155)
Before creating an object, it is suggested to read the par. Rules for the creation of the objects (pag.82).
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the container.
3. Type the name of the container (alphanumeric string of minimum 1 character and maximum 48 char-
acters) in the Label box.
The name will be displayed under the symbol of the container.
4. In the Type area, select the type of container you wish to create among: Subnetwork, Station, Substa-
tion.
5. In the Comment area, type possible information relevant to the object (max 100 characters).
The setting of this parameter is optional.
6. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The container is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move the
symbol in any point of the View area.
The maximum number of SNMP equipment objects that can be created depends on one's codeword.
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the NE.
2. Select the Edit > Add > Network Element > SNMP Managed command or press .
The Add Equipment window opens.
5. ONLY if the new NE is inserted into a OSI network, activate the Osi Address box and set the NSAP (Gos-
ip) address of the equipment, as pointed out to pag.151.
For the ALplus Node or ALCplus2 Node objects, if the Osi Address box is activated, it is NECESSARY to
set the NSAP address of the main equipment of the node. During the first operation of Line Test or Con-
nect of the system towards the main equipment of the node, the NSAP address of the other equipment
belonging to the node will be automatically detected.
6. In the Type area, select the type of equipment you wish to create (see Tab.2).
7. ONLY if the equipment is managed by Proxy Agent and the Proxy Agent application is installed, activate
the Proxy Address box.
The box aside displays the default address, configured by the system administrator, with which the
equipment is acknowledged by Proxy Agent.
In order to modify the address, type in the box the new address of the machine to which the Proxy
Agent sends the traps coming from the equipment.
For the ALplus Node or ALCplus2 Node objects, if the Proxy Address box is activated, the addresses by
which the equipment belonging to the node are acknowledged by the Proxy Agent are configured.
9. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The NE is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move the symbol
in any point of the View area.
If the created NE symbol is already present in a map, it automatically will acquire the status of the ex-
isting object.
The NSAP Address, according to the GOSIP V2, is composed by two parts: IDP (Initial Domain Part) and
DSP (Domain Specific Part).
Each part is composed by parameters. The values of these parameters, represented by one or more bytes,
can be changed. Each byte is represented by means of two characters that are the exadecimal value of the
two byte nibbles as pointed out into Tab.11.
Byte Changeable
Part Parameter
number by the user
AFI (Authority and Format Identifier) 1 Yes
IDP
IDI (Initial Domain Identifier) 2 Yes
Ver (Version) 1 Yes
Auth (Authority) 3 Yes
Reserved 2 No
DSP Domain (Routing Domain) 2 Yes
Area 2 Yes
System ID (Network Element Identification) 6 Yes
Sel (Selector) 1 No
To change the AFI, IDI, VER, Auth, Domain, Area parameters (default part of the
NSAP Address)
3. To change the Domain parameter, choose the arrow placed on the side of the box and select the desired
value from the list.
To add a value to the list:
a. Press Add.
The Domain Settings window opens.
b. Into the Label box, type a name for the domain under examination.
c. Into the Hex value boxes, type the values of the bytes that represent the domain and press OK.
To remove a value form the list:
4. To change the Area parameter, press the arrow on the side of the box and select the desired value into
the list.
To add or remove a value from the list, execute the procedures pointed out for the Domain parameter.
5. Press OK.
2. Type into the boxes the value of the 6 bytes that compose the System ID and press OK.
Into the text field on the side of the Settings push-button, the system points out the value of the set
System ID.
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the virtual NE.
2. Select the Edit > Add > Network Element > SNMP Managed (Virtual) command.
The Add Equipment window opens.
3. Type, in the Logical Address box, the logical address of the virtual NE (alphanumeric string of max 32
characters).
The logical address will be displayed under the symbol of the NE.
It is not possible to assign the same logical address to two virtual NEs.
4. In the Type area, select the type of virtual equipment you wish to create (see Tab.2).
After the creation of the virtual NE, the value cannot be modified.
6. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The virtual NE is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move the
symbol in any point of the View area.
The maximum number of Legacy NE objects that can be created depends on one's codeword.
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the NE.
2. Select the Edit > Add > Network Element > Legacy Protocol Managed command.
The subject command is available only if the modules for the management of the Legacy equipment
have been installed.
The Add Equipment window opens.
3. Into the Physical Address box, type the physical address comprised between 2 and 60000 (the value 1
is not allowed), to be assigned to the new NE.
After the creation of the NE, the value can not be changed.
Press Auto, to set, as value of the parameter, the first available address. It is possible also to set a
value into the Physical Address field and then to press Auto; in this case, the system will automatically
display the first available address that follows the set value.
The physical address set into this field has to CORRESPOND to the NE address, locally defined. If the
addresses are not the same one, it will not be possible to forward any command to the NE itself.
It is not possible to assign the same address to two different NEs also if they are two different type ones.
If into an map there is already a NE object with the same physical Address set into the field, the system
will automatically point out, into all the other fields of the Add Equipment window, the values assigned
to the same object present into the other map.
4. Into the Logical Address text field, type the logic address (alphanumeric string with maximum 32 char-
acters) to be assigned to the new NE.
The logic address will be displayed under the symbol of the equipment.
It is possible to assign, as logic address, the same value assigned to the Physical Address parameter,
while it is not possible to assign the same logic address to two NEs.
5. Into the CS Ip Address box, type the IP address of the CommServer-S or of the IPBOX to which it is
(or it will be) connected the Legacy equipment.
6. Into the CS Port box, type the number of the port of the CommServer-S or of the IPBOX to which it is
(or it will be) connected the NE.
7. In the Type area, select the type of equipment you wish to create (see Tab.2).
8. ONLY if the equipment is managed by Proxy Agent and the Proxy Agent application is installed, activate
the Proxy Address box.
The box aside displays the default address, configured by the system administrator, with which the
equipment is acknowledged by Proxy Agent.
In order to modify the address, type in the box the new address of the machine to which the Proxy
Agent sends the traps coming from the equipment.
The Proxy Agent manages only G series Radio equipment with Legacy interface.
10.Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The NE is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move the symbol
in any point of the View area.
If the created NE symbol is already present in a map, it automatically will acquire the status of the ex-
isting object.
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the virtual NE.
2. Select the Edit > Add > Network Element > Legacy Protocol Managed (Virtual) command.
The subject command is available only if the modules for the management of the Legacy equipment
have been installed.
The Add Equipment window opens.
3. Type, in the Logical Address box, the logical address of the virtual NE (alphanumeric string of max 32
characters)
The logical address will be displayed under the symbol of the NE.
It is not possible to assign the same logical address to two virtual NEs.
4. In the Type area, select the type of virtual equipment you wish to create (see Tab.2).
After the creation of the virtual NE, the value cannot be modified.
6. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The virtual NE is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move the
symbol in any point of the View area.
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the Generic Symbol.
3. Type, in the Label box, the name of the generic symbol (alphanumeric string of max 40 characters).
The name will be displayed under the generic symbol.
It is possible to assign the same name to more graphic symbols even of different type.
4. In the Group area, select the group where the generic symbol is contained.
5. In the Object area, select the generic symbol you wish to create.
6. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The Generic Symbol is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move
the symbol in any point of the View area.
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the Link.
2. Select the two objects among which you wish to create the connection.
The operation is not executed if selected:
A container and a NE or Generic Symbol
Two containers
A single object
More than two objects
4. Type, in the Label box, the name of the connection (alphanumeric string of max 40 characters).
It is possible to assign the same name to more Links even of different type.
5. Activate the Show Label box if you wish that the name of the connection is displayed in the map.
The display of the names of the Link objects is influenced even by the command View > Show/Hide
Link Label (see pag.170/Tab.12).
6. In the Connection type area, select the type of connection.
8. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The connection line is displayed between the selected objects.
If one of the two object is moved, the line automatically adapted according to the move.
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the wording.
4. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The object is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move the symbol
in any point of the View area.
1. Select the Edit > Add > Network From File command.
The Add Network From File window opens.
3. Press Ok.
The Add From File Report - <path/name of the selected file> window is displayed where, for every cre-
ated object, is pointed out in the column:
Category and Type. Object type.
Name. Logical address (NE) or name of the object.
Message. Self-explanatory message about the result of the object creation.
If the total operation of object creation:
Was successful, the objects described in the file will be present in the UX Map Manager.
Was failed, the message SYNTAX ERROR - operation ABORTED is displayed in the Add From File
Report... window.
1. Into the UX Map Manager window select the object you wish to delete.
Object:
Container. It can be deleted only if it does not contain objects.
Network Element. If present only in one map, can be deleted only if it is in disconnected status
(brown symbol).
If the object is present in more maps, it is possible to delete the symbol even if it is in connected
status, except for the last copy for which the above mentioned rule is valid: it can be deleted
only if in disconnected status.
The virtual NE and NE WEB Generic type can be always deleted.
If the object is managed even by the Ring Manager and/or VLAN Manager application, first it
must be deleted from the Ring Manager and/or VLAN Manager Map window and then it can be
deleted from the map.
Generic Symbol, Link or Label. It can be always deleted.
A connection is automatically deleted even when one of the two symbols, which is connected to,
is removed.
2. Select the Edit > Delete command or press the right mouse button, select Delete (command not
available if a Link object is selected) and confirm.
The object is removed from the map.
The values of some parameters cannot be changed. If it was necessary to modify these parameters, it
is suggested to delete the object and then re-create it assigning the new values to the parameters.
If the same object has been created into two different maps, at the changing of the parameter values of
such an object into a map, the system automatically changes the values of the parameters relevant to the
same object into the other map.
2. Select the Edit > Modify/View > Network Element command or press the right mouse button and
select Modify/View.
The Equipment Properties window opens.
If a following objects is selected:
NE managed with SNMP protocol is displayed in the box/area:
IP Address, the IP address of the NE
Logical Address, the logical address of the NE
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
2. Select the Edit > Modify/View > Generic Symbol command or press the right mouse button and
select Modify/View.
The Generic Symbol Properties window opens.
Box/area:
Label. Generic symbol name.
Group. Group containing the symbol.
Object. Symbol.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
In the UX Map Manager window, the generic symbol assumes the new characteristics.
2. Select the Edit > Modify/View > Label command or press the right mouse button and select Modi-
fy/View.
The Label Properties window opens.
The wording is displayed in the Label box.
3. To modify the parameter, type the new value (alphanumeric string of max 50 characters) in the Label
box.
4. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The label is modified in the UX Map Manager window.
The command is not available for the Generic Symbol, Label or Link objects.
2. Select the Edit > Information command or press the right mouse button and select Information.
The Information window opens, where the symbol characteristics is displayed (Fig.73).
Marking status
of the " alarms",
of the signalling
of "LCT presence"
and "Incorrect
Upload" (1)
Symbol
informative
note (2)
Fig.23 notes
(2) If selected, an NE object, the Note area reports the possible informative notes inserted by the user.
2. Select the Edit > Information command or press the right mouse button and select Information.
The Information window opens (Fig.23).
4. Press OK.
If some notes are present, the symbol , is added next to the equipment symbol.
The Graphical Symbol Properties command displays the graphic parameters assigned by the system to
the symbol.
The Find command searches a symbol in the map using, as criterion, an alphanumeric string that consti-
tutes one part or the whole name, the IP address or notes.
2. Type in the Text to find: box the alphanumeric wording relevant to the NE you wish to find.
It is possible to use the asterisk wild-card character (*). For example, typing in the box the letter:
p, the equipment with name, address or notes equal to p will be searched.
p*, the NEs with name, address or notes starting with p will be searched.
p*o, the NEs with name, address or notes starting with p and ending with o will be searched.
3. Select, in the Search for area, the field where the alphanumeric string must be searched:
Symbol Name. Name of the symbol.
IP Address. IP address of the symbol (parameter valid only for NE objects).
Note. Additional notes for the symbol (parameter valid only for NE objects).
4. Press Find.
In the Search result area, there are as many rows as the objects, present in the map, that satisfy search
conditions.
For each object, the name and the position (map/container/) of the relevant symbol.
5. In order to bring the UX Map Manager window with a a highlighted symbol in foreground, select the
relevant row in the Search result area and, then, press Open or double click on the row itself.
2. To align:
Vertically the symbols, select the Edit > Arrange Symbols > Vertical command or press .
Horizontally the symbols, select the Edit > Arrange Symbols > Horizontal command or press
.
According to the selected command/push-button, the symbols are aligned vertically or horizontally.
The Generate Info for WEB command checks the database information necessary to the RAN. This op-
eration re-alignment the information between the NMS5UX-B and RAN application.
For more information about the RAN application refer to the specific documentation.
The Set Current Window Geometry For All Containers command allows to set the size of the contain-
ers windows such as the size of the window where the command is selected.
2. Select the Edit > Set Current Window Geometry For All Containers command.
When a container is selected, the UX Map Manager window will keep the size set at step 1.
The Show/Hide Map Tree command hides/displays the Map area (pag.32).
2. Select the View > Show/Hide Map Tree command or press again to display the area again.
The Show/Hide Platform Status command hides/displays the platform status bar (pag.45)
2. Select the View > Show/Hide Platform Status command or press again to hide the bar again.
The command Show/Hide Link Label hides/shows the names of the Link objects in the View area of the
UX Map Manager window.
The display status of the names of the Link objects is pointed out by the presence of the wording [Link
Label Off] in the status bar.
In detail, if the wording is:
Present, points out that the names of the Link objects ARE NOT displayed in the View area.
Not present, points out that the names of the Link objects ARE displayed in the View area.
The display of the name of a Link object is influenced even by the setting of the relevant parameter Show
Label.
This parameter is set during the creation of the object (see pag.154). Then, it can be changed in any mo-
ment (see pag.159).
Tab.12 points out the interaction between the setting of the parameter Show Label and the display status
of the names of the Link objects in a map for an hypothetical object Link A.
Object Link A - Display of the names of the Display of the name of the object
parameter Show Label Link objects in the map * Link A in the map
* The wording [Link Label Off] is present in the status bar of the UX Map Manager window.
The Performance Monitoring Read command updates the results of the PM measures of an equipment.
The updating request is sent to the controller of the equipment.
The Performance Monitoring command displays the results of the PM measures of an equipment.
With details it is possible:
To verify the results of the PM measures of an equipment, subdivided in daily records (24 hours)
and, for each record, verifying the values of the control parameters (pag.173).
To verify the results of the PM measures of an equipment, subdivided in primary records (15
minutes) and, for each record, verifying the values of the control parameters (pag.176).
The command is not available for the virtual NE objects and the NE objects of ALplus Node or ALCplus2
Node type (for the equipment of a nodal system, the command is present in the nodal window - pag.48/
pag.49).
3. Set the Date Reference and Day previous boxes to the wished values.
It is possible to set a value within 10 and 180 days.
Remember that it is possible to display at most the daily records relevant to the last 180 days (starting
from the current day). The results of the PM measures are stored in the database of the system (Per-
formance Monitoring table). They are available for a period of 6 months, then they are automatically
removed.
5. Press OK.
The Graphic Performance Monitoring window opens.
7. Select the control parameters, for which you wish to display the results of the PM measures.
All the control parameters of a TP can be displayed in the same graphic. They have been subdivided
according to the measure unit used for their counting: seconds, blocks, dBm, etc.
The Graphic Performance Monitoring window displays the results of the selected control parameters
Fig.24 shows an example.
When a parameter is selected, the name of the relevant TP changes colour: from orange, it becomes
red. While the selected control parameter is characterized by a led on its left side.
When a control parameter is selected, it is possible to select all the parameters that have the same
measure unit present in the same TP or in anyone of the other TPs.
The control parameters that have not the same measure unit of the selected parameter are not avail-
able (wording of grey colour).
In order to display the results of the parameters with measure unit different from the currently selected
one, it is necessary to deselect all the control parameters (Option > Deselect all TPC command) and,
then, select the new parameters.
Characteristics of the selected control Date of the record where the mouse
parameters and relevant to the record is placed and which the characteristics of
where the mouse is placed (5) the control parameters below are refered to
(1) In order:
Type and logical address of the equipment.
Start date and End date.
Type of displayed record (Daily, Primary).
Type of graph (Histogram, Chart, Chart Comp).
(2) Menu:
File > Exit. It closes the window.
Option > Deselect all TPC. It deselects all the selected control parameters.
Option > Thresholds. It displays in the graph a broken line that represents the threshold val-
ue of each selected control parameter.
Each broken line will have the colour that represents the parameter in the graph.
Option > Type image. It modifies the type of graph. In detail:
Histogram, graph with histograms.
Chart, line graph.
Chart Comp., compressed line graph.
TPC. List of the types of measure (TPC - Termination Point Class - wordings in yellow) and
of the measure points (TP - Termination Point - wordings in orange) available for the selected
type of equipment.
Help > Index. It opens the on-line manual.
(3) The window displays the records contained in the set time period. They are displayed from the old-
est to the newest one. Use the scrolling bar to move among the records.
Each control parameter, within the record column, is identified by a colour. The colour legend is
displayed in the Legend and measure.... area
The daily record of the current date will be always incomplete as the daily records are
acquired at 23.59 of each day.
Restarted (black). The record was lost due to a reset of the NE.
When the NE has a software restart and verifies that, for a given measure point, the measure
is active, all the records of that measure point will result in this status.
The field is displayed and it is meaningful only for power control parameters (e.g. RLTS,
RLTM, etc.).
3. To return to the displaying of the primary records, double click on any point of the window.
The Old Performance Monitoring command displays the results of the PM measures of an equipment,
saved and restored from tape or disk.
With details it is possible:
To verify the results of the PM measures of an equipment, subdivided in daily records (24 hours)
present in the Old Performance Monitoring table (pag.177).
To verify the results of the PM measures of an equipment, subdivided in primary records (15
minutes) present in the Old Performance Monitoring table (pag.178).
The command is not available for the virtual NE objects and the NE objects of ALplus Node or ALCplus2
Node type.
In the Old Performance Monitoring table are stored the results of the PM measures saved (see pag.426)
and restored (see pag.427) from tape or disk.
3. Set the Date Reference and Day previous boxes to the wished values.
It is possible to set a value within 10 and 180 days.
Remember that it is possible to display, at most, the daily records relevant to the last 180 days (starting
from the current day).
5. Press OK.
The Graphic Performance Monitoring - OLD window opens.
If, at the opening of the window, the table is empty, it is necessary to restore from the backup file
saved before the list of the wished measures (see pag.427).
They will remain available in the Old Performance Monitoring table and in the Graphic Performance
Monitoring - OLD window, until a different list of measures is not restored.
7. Select the control parameters for which you wish the display the results of the PM measures.
In the same graph not all the control parameters of a TP can be displayed. They have been subdi-
vided according to the measure unit used for their counting: seconds, blocks, dBm, etc.
The Graphic Performance Monitoring - OLD window displays the results of the selected control param-
eters.
The items of the Graphic Performance Monitoring - OLD window and their description are the same
shown in Fig.24.
When a parameter is selected, the name of the relevant TP changes colour: from orange it becomes
red. The selected control parameter is characterized by a led on its left.
When a control parameter is selected, it is possible to select all the parameters that have the same
measure unit present in the same TP or in any of the other TP.
The control parameters that have not the same measure unit of the selected parameter will not be
available (wording in grey colour).
In order to display the results of parameter with measure unit different from the currently selected
one, it is necessary to deselect all the control parameters (Option > Deselect all TPC command)
and, then, select the new parameters.
2. Double click on the record relevant to the day for which you wish to display the primary records.
An addition Graphic Performance Monitoring - OLD window opens.
In this, it is possible to verify the results of the PM measures of all the primary records of the selected
day.
The items of the window and their description are the same shown in Fig.24, the only difference is that,
instead of the daily records, each column will represent a primary record (15 minutes).
3. In order to come back to the displaying of the primary records, double click on any point of the window.
The Export Performance Monitoring command saves on file the results of the PM measures of one or
more equipment of the same type. Then, during the operation, it is possible to forward the file to a user,
via e-mail.
3. Position the pointer into the TPclass area and press the right mouse button.
The system displays the list of the measurements foreseen for the selected type of NE.
7. Set the date (into the Date boxes) and the time (into the Time boxes) respectively for the starting (Start
Date Time box) and for the ending (Stop Date Time box) of the time for which the results of the PM
measurements have to be saved.
The supervisory system has at disposal the results of the PM measurements relevant to the last 180
days (6 months).
8. Type the directory and the file name, for which the operator wants to save the data, into the File Name
box.
The system provides a default directory and name composed by specific information, such as, for in-
stance, the date, the time, the NE logic address.
The format of the provided default name can be changed by the Superuser.
9. ONLY if the user wants to forward the file to another user, it is necessary to set the name of the user
into the Remote Address box.
If the user positions the pointer on the text field and press the right mouse button, the system displays
a pre-defined list of users. Select the desired user.
In this case, the file will be as saved into the pre-defined directory as forwarded to the set user.
The predefined list of users has to be set and later it can be changed by the Superuser.
To be able to forward the file, the system administrator has to configure properly the mail server.
10.Press OK.
The system can display an error message that points out that the number of record present into the
set time is too high. This situation is caused because the system stores into each file a maximum limit
N of records. The limit N can be changed by the Superuser.
The data are saved in ASCII format that can be recognized by a great number of text processing pro-
grams and databases.
The View/Modify P.M. Status command displays the status and allows activating/deactivating the PM
measures of one or more equipment of the same type contemporarily.
With details it is possible:
To verify the operating status of the PM measure points of one or more equipment of the same
type (pag.181)
To activate at the same time one or more PM measures for one or more equipment of the same
type (pag.183)
To deactivate at the same time one or more PM measures for one or more equipment of the
same type (pag.183)
To verify the operating status of the PM measure points of one or more NEs
of the same type
If more NE objects of different type are selected, the PM measures relevant to the first type of se-
lected NE are displayed. For example, if selected in order, one NE of SDH type, one NE of FAM type and
one NE of PDH type, on the selection of the command, the PM measures that characterize the SDH
equipment are displayed.
In this area, it is possible to filter the measure This area (Termination This area points out the
points displayed in the area are the right side Point) points out the measure Menu detail of the executed
(Termination point area) (1) points (2) bar (3) operations and their result
Fig.25 notes
(1) Area:
Equipment. Equipment selected in the map. Select the option:
All Equipment, to display the measure points relevant to all the equipment in the Ter-
mination Point area.
Selected Equipment, to display the measure points relevant only to the selected
equipment in the Termination Point area.
The option is available only after having selected at least one equipment.
Termination Point Class. Types of measures relevant to the type of equipment selected in
the map. Select the option:
All TP Class, to display the measure points relevant to all the types of measure in the
Termination Point area.
Selected TP Class, to display the measure points relevant only to the selected types
of measure in the Termination Point area.
The option is available only after having selected at least one type of measure.
Termination Point Instances. Status of the measure point. Activate the box:
Running Counters to display the active measure point in the Termination Point area.
(2) For each measure point, the following column points out:
Logical Addr., the logical address of the equipment.
TP Class, the name of the type of measure.
TP Instance, name of the measure point.
Status, status of the measure: active (wording: Running), inactive (wording Not running).
(3) Menu:
File > Close. It closes the window.
Action > Start. It activates the PM measures.
Action > Stop. It deactivates the PM measures.
Action > Refresh Info. It updates the information contained in the window.
Help > On Usage. It opens the on-line manual.
Help > About Application. Version of the module that manages the considered functionality.
To activate at the same time one or more PM measures for one or more
equipment of the same type
3. To activate:
All the PM measures of all the NE of the same type selected in the map, select the Action >
Start > All command.
The measures relevant to the measure points present in the Termination Point area select the
Action > Start > Filtered command.
The measures relevant to the measure points selected in the Termination Point area, select the
Action > Start > Selected command.
In the Message area, the result of the operation is displayed.
To deactivate at the same time one or more PM measures for one or more
equipment of the same type
3. To deactivate:
All the PM measures of all the NE of the same type selected in the map, select the Action >
Stop > All command.
The measures relevant to the measure points present in the Termination Point area, select the
Action > Stop > Filtered command.
The measures relevant to the measure points selected in the Termination Point area, select the
Action > Stop > Selected command.
In the area Message, the result of the operation is displayed.
Equipment Info (pag.185). It displays the characteristics and the functional status of the
equipment.
Radio Certificate (pag.187). It records the characteristics of the radio equipment.
Legacy-Hw/Sw Edition Inventory (pag.188). It displays the hardware version and software
version of the Legacy equipment present into the open map.
Legacy-Physical Unit Inventory (pag.191). It displays the units list of the Legacy equipment
present into the open map.
SNMP-Software Inventory (pag.194). It displays the software version and the units list
(where a controller or a FPGA is present) of the SNMP equipment present into the open map.
SNMP-Equipment Port Configuration (pag.200). It displays the settings of the communica-
tion ports of the SNMP equipment present into the open map.
SNMP-NE PPP Interfaces (pag.204). It displays the settings relevant to the PPP communica-
tion ports of an equipment.
SNMP-NE Routing Table (pag.205). It displays the Routing Table and the Default Gateway ad-
dress of an equipment.
SNMP-Hw Inventory (pag.209). It displays the hardware version of the SNMP equipment
present into the open map.
SNMP-NE Backup/Restore (pag.213). It displays the backup files of the SNMP equipment
present into the open map.
Legacy-Alarm Average (pag.219). It displays the mean of the alarms per seconds sent by the
Legacy equipment and received by the NMS5UX-B system.
The Equipment Info command displays the characteristics and the functional status of the equipment.
2. Select the Configuration > Equipment Info command or press the right mouse button and select
Equipment Information.
The Equipment Information window opens, where the characteristics and the functional status of the
equipment are displayed (Fig.26).
Selecting more NE symbols and choosing this command, more Equipment Information window open for
each selected NE.
Characteristics
and funtional
status of
the NE (1)
Fig.26 notes
(1) Option:
Physical Address. Physical address of the NE.
Logical Address. Logical address of the NE.
Type. Type of NE.
Equipment status. Status of the connection between the NE and the supervision system.
Alarm status. Functional status (alarms) of the NE.
If a NE object of ALplus Node or ALCplus2 Node type is selected, the displayed information is
referred in part to the node (Physical Address, Logical Address and Type) and in part to the sum of
the information of the equipment belonging to the node (Equipment status, Alarm status, LCT Pres-
ence, Alarm history and Current alarms).
* The recording data, if modified, can be saved only the Superuser and by the users with privileged and
advanced profiles.
The Radio Certificate command records the characteristics of the radio equipment.
With details is possible:
To verify/modify the data registration (conformity certificate) of a radio (pag.187)
To save to file or print the conformity certificate of a radio (pag.187)
3. To enter a value or modify the existing one, select the relevant box and type the new value.
4. Press Save.
The certificate is saved in the database of the system.
The Legacy-Hw/Sw Edition Inventory command displays the hardware version and software version
of the Legacy equipment present into the open map.
With details it is possible:
To verify the hardware and software version of the objects relevant to the Legacy equipment
present into the open map (pag.188)
To save/print the list of the objects (pag.189)
To filter/order the list of the objects (pag.189)
The command is available only if the modules for the management of the Legacy equipment have been
installed.
To verify the hardware and software version of the objects relevant to the
Legacy equipment present into the open map
Menu
bar (1)
Objects
list (2)
Status
bar (3)
Fig.27 notes
(1) Menu:
File > Print/Save. It prints/saves on a file the information.
File > Close. It closes the window.
View > Set Filter. It filters/orders the objects list.
View > Refresh Info. It refreshes the information present into the window.
Help > On usage. It opens the on-line manual.
(2) Each NE is seen by the supervisory system as an assembly of objects that represent one or more
physical parts of the NE itself. More detailed information concerning the objects that characterize
each single type of NE are reported into the relevant equipment manual.
The information present into the table correspond to the characteristics of the objects at the selec-
tion of the command.
(3) Into the status bar, the system points out the following information:
The number of the displayed records (xx records).
The activation of one or more filters.
The date and the time when it has been opened or refreshed the window.
The Legacy-Physical Unit Inventory command displays the units list of the Legacy equipment present
into the open map.
With details it is possible:
To verify the objects list of the Legacy equipment present into the open map (pag.191)
To save/print the list of the objects (pag.192)
To modify the identification code of the unit (pag.192)
To filter/order the list of the objects (pag.193)
The command is available only if the modules for the management of the Legacy equipment have been
installed.
To verify the objects list of the Legacy equipment present into the open map
Menu
bar (1)
Objects
list (2)
Status
bar (3)
Fig.28 notes
(1) Menu:
File > Print/Save. It prints/saves on a file the information.
File > Close. It closes the window.
Action > Set Unit Code. It changes the identification code of the object.
View > Set Filter. It filters/orders the objects list.
View > Refresh Info. It refreshes the information present into the window.
Help > On usage. It opens the on-line manual.
(2) Each NE is seen by the supervisory system as an assembly of objects that represent one or more
physical parts of the NE itself. More detailed information concerning the objects that characterize
each single type of NE are reported into the relevant equipment manual.
The information present into the table correspond to the characteristics of the objects at the selec-
tion of the command.
(3) Into the status bar, the system points out the following information:
The number of the displayed records (xx records).
The activation of one or more filters.
The date and the time when it has been opened or refreshed the window.
4. Open the Object Type option menu and choose the object.
5. Into the Unit Code box, type the identification code of the object.
If after having changed the code, the user wants to reset the preceding one, it is sufficient to press
Default.
6. Press Ok.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the Physical Unit Inventory window only the records that satisfy the activated
criteria.
Each time that the list is filtered, all the records are considered, both the displayed ones and the hidden
ones.
In the window there are also the Clear (it removes the activation of the filters and displays the com-
plete list), Cancel (it closes the window and does not execute the command) and Help (it opens the
on-line manual) push-buttons.
When the Physical Unit Inventory window closes, the possible activation of the filters is automatically
removed.
* The user with entry profile cannot switch the operating of the memory benches.
The SNMP-Software Inventory command displays the software version and the units list (where a con-
troller or a FPGA is present) of the SNMP equipment (except FAMxc, ELFO and SDH N+1) present into the
open map.
With details it is possible:
To verify the software version of the SNMP equipment present into the open map (pag.194)
To verify the units list (where a controller or a FPGA is present) of the SNMP equipment present
into the open map (pag.196)
To save/print the list of the equipment/units (pag.196)
To open the equipment window (pag.197)
To verify the configuration/functional status of an equipment (pag.197)
To update the equipment software (pag.197)
To switch the operating of the memory benches of an equipment controller (pag.197)
To require the updating of the data to the controller of an equipment (pag.198)
To filter/order the list of the equipment/units (pag.198)
To verify the software version of the SNMP equipment present into the open
map
Menu
bar (1)
The selected
push-button
points out the
type of data
displayed in
the table (2)
Equipment/
units list (3)
Status
bar (4)
(1) Menu:
File > Print/Save. It prints or save to file the information.
File > Close. It closes the window.
Action > Open Equipment. It opens the equipment interface.
Action > Equipment Info. It displays the configuration/operation status of an equipment.
Action > Refresh Info. It updates the information contained in the window.
Action > Software Download. It updates the equipment software.
Action > Read Data From NE. It sends a request for the updating of the information to the
controller of the selected NE.
Action > Bench Switch. It switches the operation of the memory benches of the controller of
the selected NE.
View > Set Filter. It filters the list according to specific criteria.
Help > On Usage. It opens the on-line manual.
(2) The lists (equipment and units) are not displayed contemporarily in the window. They are displayed
one instead of the other, according to the selected option. In detail, if active, the option
NE Software Inventory, the list of the NEs and the detail of the equipment software is dis-
played.
Unit Software Inventory, the list of the units is displayed.
The list points out all the SNMP equipment present in the open map except for FAMxc, ELFO and
SDH N+1.
For the NE objects of ALplus Node or ALCplus2 Node type, the detail of the equipment of the nodal
system is pointed out. This equipment is identified by the logic address:
<node name>.X, where X can assume the value A, B or C (ALplus Node object).
<node name>.Y, where Y can assume a value from 1 to 8 (ALCplus2 Node object).
(3) If active, the NE Software Inventory option, for each equipment, displays in the column:
Logical Address. Logical address of the equipment.
Type. Type of equipment.
Ip Addr. IP address of the equipment.
Status. Status of the connection between the equipment and NMS5UX-B.
Release Bench 1. File name and version of the software present on the memory bench 1.
Bench 1 Status. Operating status of the memory bench 1:
Running. The software of the considered memory bench is running.
Loaded. The software is present on the bench, but is not currently running (standby).
Not loaded. The software is not loaded in the memory bench.
Downloading. The updating of the software of the memory bench is running.
Release Bench 2. File name and version of the software present on the memory bench 2.
Bench 2 Status. Operating status of the memory bench 2. The detail of the wordings is the
same pointed out by the Bench 1 Status parameter.
If active, the Unit Software Inventory option displays in the column, for each unit:
Logical Addr. Logical address of the equipment where the unit is present.
Type. Type of equipment where the unit is present.
Ip Address. IP address of the equipment where the unit is present.
Status. Status of the connection between the equipment, where the unit is present, and
NMS5UX-B.
Unit. Name of the unit.
Element. Name of the element, where the software is loaded, present in the unit: controller,
programmable logic, etc.
Actual Release. Name of the file and version of the software present in the element.
The information present in the table refers to the moment when the command is selected or the
refresh is executed.
To verify the units list (where a controller or a FPGA is present) of the SNMP
equipment present into the open map
The filter is available only when the NE Software Inventory option is active in the Snmp NE
Software Inventory window.
Match Object. Unit and/or element of the unit.
To set the criterion:
Select the unit in the Unit Type list.
It is possible to select only one unit or all the units selecting All Units.
Select the element (controller, programmable logic, etc.) in the Element Type list.
It is possible to set only one element or all the elements of the unit set in the Unit Type
box, selecting All Elements.
The filter is available only when the Unit Software Inventory option in the Snmp NE Software
Inventory window is active.
Match Actual Release. Version of the software present in an element (controller, programmable
logic, etc.).
To set the criteria, select from the list the wished release (the list displays the releases of the
software present in the equipment pointed out in the Snmp NE Software Inventory window). The
selected item is displayed in the box.
The filter is available only when the Unit Software Inventory option in the Snmp NE Software
Inventory window is active.
4. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the Snmp NE Software Inventory window only the records that satisfy the acti-
vated criteria.
Each time that the list is filtered, all the records are considered, both the displayed ones and the hidden
ones.
In the window there are also the Clear (it removes the activation of the filters and displays the com-
plete list) and Cancel (it closes the window and does not execute the operation) push-buttons.
When the Snmp NE Software Inventory window closes, the possible activation of the filters is automat-
ically removed.
The SNMP-Equipment Port Configuration command displays the settings of the communication ports
of the SNMP equipment (except FAMxc and SDH N+1) present into the open map.
With details it is possible:
To verify the settings of the communication ports of the SNMP equipment present into the open
map (pag.200)
To display the settings of the PPP communication ports of an equipment (pag.201)
To display the Routing Table and the Default Gateway of an equipment (pag.202)
To executes the Ping of an equipment (pag.202)
To display the equipment with Logical Address and Station Id different (pag.202)
To modify the Logical Address of an equipment as its Station Id or vice versa (pag.202)
To filter/order the list of the equipment (pag.202)
Menu
bar (1)
Equipment
list (2)
Fig.30 notes
(1) Menu:
File > Exit. It closes the window.
View > Filter. It filters the list according to specific criteria.
View > Show mismatched (Station Id - Logical Address) only. It displays only the equipment
whose equipment identifier (Station Id) is different from the Logical Address.
View > Show all equipment. It displays all the SNMP equipment (except from FAMxc and SDH
N+1) present in the open map.
The list points out all the SNMP equipment in connected or unreacheable status present in the
open map except for FAMxc and SDH N+1.
For the NE objects of ALplus Node or ALCplus2 Node type, the detail of the equipment of the nodal
system is pointed out. This equipment is identified by the logic address:
<node name>.X, where X can assume only the value A, B or C (ALplus Node object).
<node name>.Y, where Y can assume only a value between 1 and 8 (ALCplus2 Node object).
2. Select the View > Show mismatched (Station Id - Logical Address) only command.
The window displays only the equipment whose value in the column Station Id is different from that
present in the column Logical Address.
3. Select the:
Commands > Set Station Id (like Logical Address) command. The value present in the col-
umn Station Id is changed. The new value corresponds to the logical address of the equipment
(Logical Address).
Commands > Set Logical Address (like Station Id) command. The value present in the col-
umn Logical Address is changed. The new value corresponds to the equipment identifier (Station
Id).
4. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the Port Communication Browser window only the records that satisfy the acti-
vated criteria.
Each time that the list is filtered, all the records are considered, both the displayed ones and the hidden
ones.
In the window there are also the Clear (it removes the activation of the filters and displays the com-
plete list) and Cancel (it closes the window and does not execute the operation) push-buttons.
When the Port Communication Browser window closes, the possible activation of the filters is automat-
ically removed.
The SNMP-NE PPP Interfaces command displays the settings relevant to the PPP communication ports
available for an equipment for the input/output of the supervisory signal.
The command is available only if it has been selected a single SNMP equipment except for the ELFO,
SDH N+1, FAMxc, ALFO, ALplus2 Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCplus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
Menu
bar (1)
Equipment
info (2)
PPP
communication
ports (3)
Fig.31 notes
(1) Menu:
File > Exit. It closes the window.
(2) This area lists in order: NE logical address (NE type - NE IP address) - connection status of NE.
(3) The available values change depending on the type of selected equipment. For the detail of all the
available ports for each type of equipment, refer to the equipment documentation.
The window displays the more meaningful characteristics for each communication ports. In details,
the column:
Interface. PPP communication ports name.
IP Address. IP/PPP address of the port.
IP Netmask. Mask for the network address definition.
Mode. Functioning mode of the PPP protocol.
Speed. Transmission rate of the port.
Signal Input. Type of signal in input to the port (e.g. E1, STM-1, etc.).
2Mbit Selector, Slot Selector and 16Kbit Map. Respectively setting of the tributary 2Mb,
timeslot and 16Kbit (channel EOC E1).
The symbol - points out that the value is not meaningful for the considered type of port.
If the equipment is in disconnected status because it has been just created and the first connec-
tion has not been executed yet, the window will result empty because the required information is
not present in the database of the supervision system.
The SNMP-NE Routing Table command displays the static Routing Table and the Default Gateway ad-
dress currently used by an equipment (Routing Table Running and Default Gateway).
With details it is possible:
To display the Routing Table and the Default Gateway of an equipment (pag.205)
To add an element to the Routing Table (pag.206)
To delete an element from the Routing Table (pag.207)
To set or modify the IP address used as Default Gateway (pag.207)
To delete the IP address used as Default Gateway (pag.207)
The command is available only if it has been selected a single SNMP equipment except for the ELFO,
SDH N+1, FAMxc, ALFO, ALplus Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCplus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
For more information about the Routing Table and Default Gateway go to pag.207.
Modality of
Elements of the connection
routing table (direct or indirect)
between the specific port
IP address of (Interface) and the
the destination destination IP network (4)
IP network
or element IP address
of the equipment which
IP NetMask of acts as Gateway
the destination
IP network
Supervision port
or element
of the local equipment
IP address which the equipment
of the equipment acting as Default Gateway
which acts as is connected to (3)
Gateway
(1) Menu:
File > Exit. It closes the window.
Commands > Refresh. It updates the information contained in the window.
Commands > Add New Route. It adds an element to the Routing Table.
Commands > Delete Route. It deletes an element from the Routing Table.
(2) This area points out in order: Logical address of the NE (Type of NE-IP Address of NE) - connection
status of NE.
If the equipment is in disconnected status because it has been just created and the first connec-
tion has not been executed yet, the window will result empty because the required information is
not present in the database of the supervision system.
(3) The available values change depending on the type of selected equipment. Here below are reported
the ports generally present in all the equipment. For the detail of all the ports available for each
type of equipment, refer to the equipment documentation.
Wording:
Lan. Communication port with the LAN network.
Lan/OSI. Communication port that interfaces itself with the router OSI.
Lct. Port for the connection with the PC where resides the SCT/LMT management program
or the browser for the start of WEB LCT.
RS232. Serial port for the connection with other network elements.
Radio. Communication port represented by the radio signal.
2Mb/s. E1 communication port (2Mb/s).
- . Inner port (internal loopback).
(4) Wording:
Direct. The IP network or the element are directly connected to the equipment interface. The
IP network or the element are automatically inserted by the equipment software.
Indirect. The IP network or the element are not directly reachable by the equipment inter-
face. The IP network or the element have been automatically inserted by the OSPF protocol
(dynamic element).
4. Into the Destination box, type the IP Address of the IP network or of the destination element.
For each one of the four available spaces (sub-divided by a dot), insert a number comprised between
0 and 255.
5. Into the NetMask box, type the mask for the destination IP network.
For each one of the four available spaces (sub-divided by a dot), insert a number comprised between
0 and 255.
6. Into the Hop box, type the IP Address of the Gateway equipment for the destination network.
For each one of the four available spaces (sub-divided by a dot), insert a number comprised between
0 and 255.
7. Press Add.
The new element is inserted into the table. The system records the new element into the currently used
Routing Table (Running Routing Table) and into the backup memory of the equipment (Stored Routing
Table).
When all the equipment belong to the same IP network, it is not necessary to define the Routing Table
and the address of the gateway equipment because the network is able to manage its own inner traffic.
The setting of these parameters is necessary when the equipment belong to different networks, then, the
traffic has to be routed again from a network to the other one.
Routing Table
The function of the Routing Table is the one to check the routing of the supervisory messages exchanged
among the elements (PCs, equipment, etc.), that use the TCP/IP protocol, from one network to the other
one.
Each equipment at its initialization (start-up operation) automatically sets the elements of the Routing Ta-
ble that identify the supervisory ports of the equipment (communication ports provided with the equipment
for the input/output of the supervisory signal).
These elements are set according to the IP addresses assigned to each port.
If the user changes the IP address of a supervisory port, the system does not dynamically change it into
the equipment Routing Table. It is necessary to execute a reset of the equipment, because the elements
of the Routing Table are set at the equipment start-up.
If it is necessary, the user can add to these elements (automatically set) some other ones.
The system records each new element (manually set) into the currently used Routing Table (Running Rout-
ing Table) and into the backup memory of the equipment controller (Stored Routing Table); the system
does not record the elements (automatically set) into the backup memory of the controller because they
are newly set at every equipment start-up.
The Running Routing Table is a static one. The system updates such a table, through the elements present
into the Stored Routing Table, at every equipment start-up.
The equipment does not currently use the Stored Routing Table. This table becomes operative on the
equipment restart. In fact, in this case, the system inserts the elements of the Stored Routing Table into
the Routing Table used by the equipment (Running Routing Table). What just said is valid only for the el-
ements whose router equipment (Hop) is associated to an active interface.
The setting of the Stored Routing Table id necessary, for instance, when the user wants to change an ad-
dress of the equipment supervisory ports. In such a case, it is not possible to change the currently used
Routing Table (Running Routing Table). The changes have to be inserted into the Stored Routing Table. At
the next equipment start-up, the system inserts the elements of the Stored Routing Table into the Routing
Table used by the equipment.
The Stored Routing Table can be displayed/modified through the local management program of the equip-
ment (SCT/LMT and/or WEB LCT).
Default Gateway
The system forwards to the equipment with the Default Gateway function the data that have a receiver
unreachable through the routes present into the Routing Table.
The SNMP-HW Inventory command displays the hardware version of the SNMP equipment present into
the open map (Hw Inventory functionality).
With details it is possible:
To display the hardware of the SNMP equipment present in the open map (pag.209)
To save the data to file (pag.211)
To save periodically the data to file (pag.212)
To deactivate the periodic saving of the data to file (pag.212)
The Hw Inventory functionality is optional and available only for the SNMP equipment of type EL, US,
ADM-1, EXP63, ALFO and ALS series (AL, ALC, ALS, ALS-C, ALplus, ALCplus, ALplus2, ALCplus2).
To display the hardware of the SNMP equipment present in the open map
2. Select, in the Equipment Type area, the NE types for which you wish to display the hardware data.
3. Type, in the Max Rows box, the maximum number of records you wish to display.
4. Press Read.
The window displays the hardware data relevant to all the types of NE selected present in the open map.
5. If you wish to display a specific detail of the data, execute one or more of the following settings, ac-
cording to the filter criteria you wish to use:
Logical Address. Logical address of the NE.
To set the criterion, type the logical address of the NE in the text field and press Add.
It is possible to use the asterisk (*) as jolly character only at the end of the alphanumeric string.
The values set in this way are inserted in the list above the text field.
It is possible to delete an item from the list pressing, after having highlighted it, Del.
IP Address. IP address of the NE.
To set the criterion, type the wished IP address.
It is possible to use the asterisk (*) as jolly character only for the final fields (the asterisk cannot
be before a numeric field). For example, the values 172.18.54.* or 172.18.*.* are allowed, whi-
le the value 172.18.*.215 is not allowed.
Pressing IP Clear to delete the IP Address.
Unit Type. Type of unit of the equipment.
The filter is available and meaningful only if the Expansion display modality is selected.
To set the criterion, select the wished units. It is possible to select a maximum of three units.
To select the units, press the Ctrl key and the unit.
Moreover it is possible to define, for each type of equipment, which units must not be used in
the Unit Type in the following way:
Press Not managed unit type.
The FilterUnitType window opens.
In the Select equipment type area, select the type of equipment for which you wish to
hide the units.
In the area below, the detail of the relevant units is displayed.
The highlighted units are already hidden.
6. Press Read.
The hardware data relevant to all the NEs, present in the open map, satisfying the set criteria are dis-
played.
7 Select the option:
Expansion to display the data in expanded format: for each equipment, the hardware charac-
teristics of all the units are displayed.
Compact to display the data in compact format: for each equipment, the hardware characteris-
tics of the controller unit are displayed.
Fig.33 notes
The Max Rows box points out the maximum number of displayed records.
The x of y Rows field points out the number of displayed records (x) with respect to the number of
total records (y) which satisfy the set filter criteria.
To display all the records that satisfy the set criteria, it is necessary to type the total number of
records in the Max Rows box.
(4) Push-button:
Read. It reads the data stored in the database of the NMS5UX-B system and display them
according to the set filter.
Reset Filter. It deletes the filter setting.
Export timer. It periodically saves the displayed data to file.
Export manual. It saves the displayed data to file.
4. Type the name of the filter into the Filter Name box.
5. Type, in the Export periodicity day box, the periodicity in days of the data export and, in the Hour box,
the time when the export is executed.
6 Press Insert.
At the first set time interval, a file will be saved containing the hardware data of the equipment that
satisfy the criteria present in the filter.
The file will be saved in the directory /opt/nms5ux/ExpHwInv, in the format .cvs and .xml, and will ba
named HwInv-filtername-<date_time>.
The files will be saved until when the user does not remove the filter (pag.212).
4 Press Delete.
The filter is removed.
The SNMP-NE Backup/Restore command displays the backup files of the SNMP equipment present into
the open map.
With details it is possible:
To display the backup files of the SNMP equipment present in the open map (pag.213)
To transfer the configuration present in a backup file to an equipment (configuration restore)
(pag.216)
To save the equipment configuration to a file (configuration backup) (pag.216)
To lock/unlock a backup file (pag.216)
The equipment list for which the NE Backup/Restore functionality is configurable. Default: EL, US, ADM-
1, EXP63, ALFO and ALS series (AL, ALC, ALS, ALS-C, ALplus, ALCplus, ALplus2, ALCplus2).
The supervision system periodically saves to disk the configuration of the equipment (backup files). For
more information about the backup and restore modalities go to pag.217.
To display the backup files of the SNMP equipment present in the open map
2. If you wish to display a specific detail of the files, execute one or more of the following basic settings,
according to the filter criteria you wish to use:
Logical Address. Logical address of the NE.
It is possible to set the logical addresses in one of the following ways:
Type the logical address of the NE into the text field and press Add.
Press Tree. A window opens, where are displayed the containers and the equipment
present in the map. Select the wished equipment. The equipment is pointed out in the
text field. Press Add.
The Tree push-button is only available in the page open with the Microsoft Internet Ex-
plorer browser.
It is possible to use the asterisk (*) as jolly character only at the end of the alphanumeric string.
The values set in this way are inserted in the list above the text field.
To delete a record from the list, select the address and press Del.
IP Address. IP address of the NE.
In order to set the criterion, type the wished IP address.
It is possible to use the asterisk (*) as jolly character only for the final fields (the asterisk cannot
precede a field with numbers). For example, the value 172.18.54.* or 172.18.*.* are allowed,
while the value 172.18.*.215 is not allowed.
Pressing IP Clear to delete the IP Address.
File lock. Status of the file. Selecting the option:
All, the list will display all the backup files.
Unlocked, the list will display only the unlocked files.
Locked, the list will display only the locked files.
Eligible, the list will display only the files matching all the following rules:
Last backup file of a NE for which no locked backup file already exists.
The backup file must not contain errors.
To set the criterion select the wished option.
5. Press the Info push-button, relevant to a backup file to display its detail.
The File Property window opens with the following information:
Logical Address. Logic address of the NE.
IP Address. IP address of the NE.
Eq. Type. Type of equipment.
File Name. Name of the backup file. The format of the name of the file is the following: <Equip-
ment ID> <hours minutes seconds> <days months years>_U.bku.
File Date. Date/time of saving of the backup file.
Backup Result. Result of the operation of file saving.
Restore Date. Date/time when the operation of file restore has been executed.
Restore Result. Result of the operation of file restore.
The presence of the symbol - signals that the information is not available.
For the Backup Result and Restore Result the background color:
Green, points out that the operation was successful.
Red, points out that the operation is failed.
(2) The Max Rows box points out the maximum number of displayed files.
The x of y Rows field points out the number of displayed records (x) with respect to the number of
total records (y) which satisfy the set filter criteria.
In order to display all the records satisfying the set criteria, it is necessary to type the total
number of records into the Max Rows box.
(3) Each record identifies a backup file. For each file, is pointed out in the column:
Logical Address. Logical address of the NE.
IP Address. IP address of the NE.
Eq. Type. Type of equipment.
Backup Date. Date/time of creation of the backup file.
Lock. Status of the file: Locked, <empty box> (unlocked).
Backup file name. Name of the backup file. The format of the name of the file is the following:
<Equipment ID> <hour minutes seconds> <days months years>_U.bku.
Operations available. Push-button:
Info. It displays the characteristics of the file. If the color of the box backgrounds:
Green, there are not errors in the backup file.
Red, there are errors in the backup file.
Restore. It transfers the configuration stored in the file to the relevant equipment
present in the map.
Backup. It saves the current equipment configuration to file.
Lock/Unlock. It locks/unlocks the file. The push-buttons are displayed one in alter-
native to the other, depending on the status of the file.
When a push-button is disabled, it means that the relevant function is not available.
(4) Push-button:
Apply Filter. It reads the data stored in the database of the NMS5UX-B system and displays
them according to the set filters.
Switch to Equipment. It displays all the equipment, managed by the NE Backup/Restore
functionality, present in the map. The records with the available Backup push-button cor-
respond to the equipment in connected status, whose configuration can be saved.
Switch to Backup File. It displays the backup files of the equipment, managed by the NE
Backup/Restore functionality, present in the map.
Reload. It re-reads the data stored in the database of the NMS5UX-B system.
Lock All. It locks all file present in the list.
The Switch to Equipment and Switch to Backup File push-buttons are displayed one in alter-
native to the other.
2. Display the backup file you wish to transfer to the equipment (pag.213).
4. Press Confirm.
The operation is scheduled to the process which manages the procedure of periodic file saving.
a. Display the backup file/files of the equipment whose configuration you wish to save (pag.213).
b. Press Backup near the file/files.
Or:
2. Display the backup file you wish to transfer to the equipment (pag.213).
The NE Backup/Restore functionality allows saving to file the complete configuration of an equipment
(Backup operation), displaying the list of the available backup files and transferring the configuration
stored in a file to the relevant equipment (Restore operation).
The list of equipment for which the NE Backup/Restore function is configurable. Default: equipment of
type EL, US, ADM-1, EXP63, ALFO and ALS series (AL, ALC, ALS, ALS-C, ALplus, ALCplus, ALplus2,
ALCplus2).
Backup operation
The saving of the backup files is automatically executed by the supervision system or it can be forced in
any moment (pag.216).
The saving modalities by the supervision system are the following: NMS5UX-B periodically verifies if, for
each equipment, one of the following conditions has occurred:
No backup file is available.
A change (set) has been executed to the equipment configuration.
A connection in Configuration modality has been activated between LCT and the equipment.
The connection between the supervision system and the equipment has been activated or re-
activated.
A new operation has been stored in the Command Log stored in the equipment controller.
For each equipment, which at least one of the above mentioned conditions has occurred for, the system
saves the complete configuration into a file. At the successive check, if at least one of the above mentioned
conditions has occurred again, the complete configuration of the equipment will be saved into a different
file and so on.
With complete configuration of an equipment we mean:
Configuration of the equipment.
Configuration of the communication port (IP Ethernet, PPP RS-232, etc.) of the routing tables
and of the possible OSPF parameters.
List of remote equipment (Remote Element Table).
The periodicity of the control by NMS5UX-B can be configured by the Superuser.
A maximum of N files (N configurable - default=3) for each equipment is saved on the disk of the machine
where the supervision system is installed. The file successive to the maximum number will overwrite the
oldest backup file.
It is possible to lock one or more files in such a way that the system does not overwrite them (pag.216).
These files will not enter in the count of the maximum number of files saved for each managed equipment.
This means they will not be overwritten until the user unlocks them.
For example, suppose that the system saves a maximum of 3 files for each equipment. For the equipment
A, the files A1, A2 and A3 are automatically saved in this order. If the oldest file (A1) is locked, when the
fourth file is generated, this will not overwrite the file A1, but a new file (A4) will be created. If no other
file is locked, when a new file (A5) is generated, this will overwrite the oldest file (A2). In this way, the
locked files + the last three saved files will be always available to the user.
It is possible to lock as many files as you wish. The files will remain locked until the user unlocks them.
Two files with the same content will be available for each backup file in the system disk, one for each for-
matting compatible with the O.S.:
UNIX. The path, where the file is saved, can be configured. The name of the file has the following
format: <Equipment ID> <hour minute second> <day month year>_U.bku.
WINDOWS. The path, where the file is saved, can be configured. The name of the file has the
following format: <Equipment ID> <hour minute second> <day month year>_W.bku.
This file is compatible with the applications SCT, WEB LCT, SCT BKU Builder and is available on
the disk of the machine where ones supervision system is installed.
By means of the RAN (Remote Access NMS5UX) application, it is possible to copy a backup file to a different
machine or external disk by means of a proper push-button present in the NE Backup/Restore page.
The Restore operation (pag.216), transfers to the equipment ONLY the configuration parameters present
in the backup file.
The restore of the communication parameters (IP Address, routing tables, etc.) can be executed only
through the SCT o WEB LCT application. The restore of the Remote Element Table can be configured
through the SNMP-Remote Element Table command (pag.390) or through the SCT/WEB LCT applica-
tion.
The Legacy-Alarm Average command displays the mean of the alarms per second received by the
NMS5UX-B and sent by the Legacy equipment.
The command is available only if the modules for the management of the Legacy equipment have been
installed.
To display the mean of the alarms per second received by the NMS5UX-B sys-
tem and sent by the Legacy equipment
Equipment List Locate (pag.221). It displays the list of the equipment managed by the
NMS5UX-B system.
Proxy Equipment List (pag.239). It displays the list of the equipment managed by the Proxy
Agent and their Proxy address.
* Only the Superuser can verify in which maps is present the symbol of an equipment and can reset and
rewrites the equipment table.
The Command Executor application can be started only by the Superuser or by the user with privileged or
advanced profile.
The recording data of the conformity certificate of a radio equipment, if modified, can be saved only by the
Superuser and by the users with privileged and advanced profiles.
The Equipment List Locate command displays the list of the equipment managed by the NMS5UX-B.
With details it is possible:
To verify/modify the status/severity of the alarms and the status of the trap sending of an equip-
ment (pag.232)
If the profile of the user who has selected the command is:
Superuser, the information is referred to the equipment present in ALL the map managed by
NMS5UX-B.
Entry, Normal, Advanced or Privileged, the information is referred ONLY to the equipment
present in the open map.
At the opening of the Equipment Browser [List/Locate] window, it is possible that a warning window
opens, where it is pointed out that the database contains a number of equipment higher than N.
For this cause, the user is asked if he wishes that the information about the active measures of PM is
made available (operation that can take a lot of time). To press the push-button:
Yes, the Equipment Browser [List/Locate] window opens and, for each NE in the list, it will be
possible to verify the activation status of the PM measures (Perf. column).
No, the Equipment Browser [List/Locate] window opens, but the information relevant to the ac-
tive measures of PM will be not available.
The N limit is, by default, 100. The value can be modified by the Superuser.
Menu
bar (1)
List of
equipment
(2)
Status
bar (3)
Fig.36 notes
(1) Menu:
File > Print/Save. It prints or saves to file the information.
File > Close. It closes the window.
Actions > Open Equipment. It opens the equipment window.
Actions > Equipment Info. It displays the configuration/operation status of an equipment.
Actions > Refresh Info. It updates the information contained in the window.
Actions > Performance Monitoring. It displays the results of the PM measures of an NE.
Actions > Export Performance Monitoring. It saves on file the results of the PM measures.
The information corresponds to the characteristics/operating status of the equipment when the
Equipment Browser [List/Locate] window has been opened or updated.
The presence of the - symbol points out that the information is not available as not meaningful for
the status and/or the type of equipment, which is referred to.
(3) Field:
xx of yy. Number of displayed records (xx) and number of total records (yy). If no filter is
active, the number of displayed records corresponds to the number of total records.
View... Activation of one or more filters.
Date and time when the window has been opened or updated.
The box is not available if in the warning window, displayed at the opening of the Equipment
Browser [List/Locate] window, the No push-button has been pressed.
Match Alarm. Severity level of the alarms of the NE.
To set the criterion, select the option relevant to the wished severity.
Match Alarm Disabled. Enabling status of the alarms/trap sending of the equipment to NMS5UX-B.
To set the criterion, select the option:
Enabled, the NEs that have not alarms or enabled trap sending will be displayed.
Disabled, the NEs that have at least one alarm or one disabled trap sending will be dis-
played.
Match Gosip Address. Parameters that compose the NSAP (Gosip) address of the equipment.
To set the criterion, select the:
Domain box and type, into the relevant boxes, the value of the corresponding 2 bytes,
(Domain parameter - default part of the NSAP Address).
Area box and type, into the relevant boxes, the value of the corresponding 2 bytes (Area
parameter - default part of the NSAP Address).
System ID box and type, into the relevant boxes, the value of the corresponding 6 bytes
(System ID parameter).
Match location. Physical position of the equipment.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the Equipment Browser [List/Locate] window only the records that satisfy the
activated criteria.
Each time the list is filtered, all the records are considered, both the displayed and the hidden ones.
In the window there are also the Clear (it removes the activation of the filters and displays the com-
plete list), Cancel (it closes the window and does not execute the operation) and Help (it opens the
on-line manual) push-buttons.
When the Equipment Browser [List/Locate] window closes, the possible activation of filters is automat-
ically deleted.
To verify the marking status of the alarms, of the signalling of LCT presence
and Incorrect Upload of an equipment
2. To add a prefix:
a. Select one or more equipment which you wish to add the same prefix.
b. Select the Actions > Location > Assign command.
The Location window opens.
c. Type, in the New Location Name box, the prefix you wish to add to the logical address of the
equipment (alphanumeric string of minimum 1 maximum 10 characters).
d. Press Apply.
In the Logical Addr column of the selected equipment, the prefix is added (prefix - logic ad-
dress).
The prefix is furthermore added in all the windows where the <logic address> field is present.
The only exception is the label of the icon that represents the equipment in the map, where the
prefix is not pointed out.
If the equipment was already provided with prefix, the new value replaces the previous one.
3. To remove a prefix:
a. Select one or more equipment which you wish to remove the prefix to.
b. Select the Actions > Location > Remove command.
The prefix is removed from the logic address of the equipment.
The command must be used only in case of a supposed misalignment between the information
present in the equipment table and the equipment represented on video in the maps.
Operation not available for virtual NE objects and virtual NE objects of ALplus Node and ALCplus2 Node
type (for the equipment of a nodal system, the command is present in the nodal window - pag.48/pag.49).
4. Set the Date Reference and Day previous boxes to the wished values.
It is possible to set a value within 10 and 180 days.
Remember that it is possible to display at most the daily records relevant to the last 180 days (starting
from the current day). The results of the PM measures are stored in the database of the system (Per-
formance Monitoring table). They are available for a period of 6 months, then they are automatically
removed.
6. Press OK.
The Graphic Performance Monitoring window opens.
7. Select the TPC menu.
All the types of measure (TPC - Termination Point Class - yellow wordings) and the measure points
(points where the control parameters are really measured) (TP - Termination Point - orange wording)
available for the selected equipment are selected.
The control parameters are contained in the pop-up menu that opens on the side of the measure point.
Generally, more control parameters refer to the same TP.
8. Select the control parameters, for which you wish to display the results of the PM measures.
All the control parameters of a TP can be displayed in the same graphic. They have been subdivided
according to the measure unit used for their counting: seconds, blocks, dBm, etc.
The Graphic Performance Monitoring window displays the results of the selected control parameters
Fig.24 shows an example.
When a parameter is selected, the name of the relevant TP changes colour: from orange, it becomes
red. While the selected control parameter is characterized by a led on its left side.
When a control parameter is selected, it is possible to select all the parameters that have the same
measure unit present in the same TP or in anyone of the other TPs.
The control parameters that have not the same measure unit of the selected parameter are not avail-
able (wording of grey colour).
In order to display the results of the parameters with measure unit different from the currently selected
one, it is necessary to deselect all the control parameters (Option > Deselect all TPC command) and,
then, select the new parameters.
6. Choose one or more measuring points for which the results of the PM measurements have to be saved
on file. It is possible to select more records.
9. Type the directory and the file name, for which the operator wants to save the data, into the File Name
box.
The system provides a default directory and name composed by specific information, such as, for in-
stance, the date, the time, the NE logic address.
The format of the provided default name can be changed by the Superuser.
10.ONLY if the user wants to forward the file to another user, it is necessary to set the name of the user
into the Remote Address box.
If the user positions the pointer on the text field and press the right mouse button, the system displays
a pre-defined list of users. Select the desired user.
In this case, the file will be as saved into the pre-defined directory as forwarded to the set user.
The predefined list of users has to be set and later it can be changed by the Superuser.
To be able to forward the file, the system administrator has to configure properly the mail server.
11.Press OK.
The system displays the Preview window that points out the resuming of the executed setting opera-
tions.
Then, in the lower part of the window, the system points out the total number of records (Total Record
Number box) and the number of records that contain errored data (Records with counters box).
The system can display an error message that points out that the number of record present into the
set time is too high. This situation is caused because the system stores into each file a maximum limit
N of records. The limit N can be changed by the Superuser.
The data are saved in ASCII format that can be recognized by a great number of text processing pro-
grams and databases.
4. To activate:
All the PM measures of all the NE of the same type selected in the map, select the Action >
Start > All command.
The measures relevant to the measure points present in the Termination Point area select the
Action > Start > Filtered command.
The measures relevant to the measure points selected in the Termination Point area, select the
Action > Start > Selected command.
To deactivate:
All the PM measures of all the NE of the same type selected in the map, select the Action >
Stop > All command.
The measures relevant to the measure points present in the Termination Point area, select the
Action > Stop > Filtered command.
The measures relevant to the measure points selected in the Termination Point area, select the
Action > Stop > Selected command.
In the area Message, the result of the operation is displayed.
2. Select the SNMP equipment, except for ELFO, SDH N+1, FAMxc, ALplus Node and ALCplus2 Node.
Selecting two or more records of the same type, it is possible to execute the operation for all the equip-
ment at the same type.
4. In the Selection file DWL box, set the file you wish to use for the updating.
It is possible to type the path and the name of the file or press Select (the Select file for download
window opens) and select the file among the available ones.
If the file you wish to use for the operation is not in the home/ftp directory, it is necessary to copy
it in this directory as the supervision system needs, in order to execute correctly the download opera-
tion, to find the file for the updating in the home/ftp directory.
To press Read to display a brief description that illustrates the content of the selected file.
5. Set the type of download you wish to execute. Select the option:
Forced, to update the software of the equipment controller.
Only different or not present, to update the software of peripheral units (FPGA file and/or oper-
ating code).
6. Activate the Bench switch? box if you wish that, at the end of the download, a switching of the memory
bench is automatically executed in order to use the bench with the updated software.
Before starting the updating of the controller of the NE, it executes a compatibility check be-
tween the software that must be sent and the one present in the controller itself.
The check consists in verifying the technology and the type of NE (pointed out by the first 2 char-
acters of the file name). For some types of NEs, checks are executed also on the 3rd character
of the filename. More information is reported in the equipment user manual relevant to the spe-
cific type of NE.
If the parameters are compatible, the download starts. Otherwise, the updating of the software
will not be executed.
If the operation is successful, opening the RelSw window (Fig.82), in the Release box relevant
to the updated memory bench, the new version of the software is pointed out.
If it is not successful, the Status box relevant to the updated memory bench displays the old
version or the wording not loaded.
Set a date/time of execution for the updating of the software, the Software Download window
is closed.
In the list of the scheduled equipment for the download, a record is added for each NE present
in the Equipment list for download area.
Selecting two or more records of the FAMxc type, it is possible to execute the operation for all the
NEs at the same type.
4. In the File Selection box, set the file you wish to use for the updating.
It is possible to type the path and the name of the file or press Browse (the fileSelection... window
opens) and select the file among the available ones.
If the file you wish to use for the operation is not in the home/tftpdir directory, it is necessary to
copy it in this directory as the supervision system needs, in order to execute correctly the download
operation, to find the file for the updating in the home/tftpdir directory.
5. Set the date/time when you wish to schedule the operation in the Date/Time Scheduled for Download
box.
6. Activate the Switch Bench and Restart box if you wish that, at the end of the download, a switch of the
memory bench and a restart of the equipment are executed.
The setting is valid for all the equipment present in the Equipment List area. If you wish to execute
a different setting for an equipment of the list:
7. If enabled, type the access code of the equipment in the Password box.
If the Superuser has defined the equipment password in the configuration file of the system, it is not
necessary to insert the code to access the equipment. It is sufficient to activate the Password Default
box.
The set password is valid for all the equipment present in the Equipment List area. If an equipment
has a different password, it is necessary to set in the following way:
To verify/modify the status/severity of the alarms and the status of the trap
sending of an equipment
Operation available only if it has been selected a single SNMP equipment in connected status, except
for the ELFO, SDH N+1, FAMxc, ALplus Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCplus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
In the list are not present the alarms of the user inputs, which have a different management of the
severity (see pag.124).
4. To modify the characteristics of an alarms double click on the wished alarm or select the alarm and then
the Action > View/Modify Severity command.
The View/Modify Severity Code window opens, where it is pointed out in the box/area:
Alarm Description. Name of the alarm.
Status. Status of the alarm and of the trap sending by the NE to the system. If active the option:
Enabled, the alarm and the sending of trap is enabled.
Trap Disabled, the sending of trap is disabled.
Alarm Disabled, the alarm is disabled.
Severity. Severity level associated to the alarm.
The label (NMS5UX-B default) points out the default setting associated to that alarm by the su-
pervision system.
If the Alarm Disabled option is selected (Status area) the severity level associated to the alarm can-
not be modified.
6. Press Modify.
The possible modification of the enabling status of alarm/trap sending is pointed out in the Equipment
Severity Code window.
Operation available only if it has been selected a single SNMP equipment in connected status, except
for the ELFO, SDH N+1, FAMxc, ALFO, ALplus Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCplus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
4. The procedures to modify the list of the LCT users are the same pointed out at par.
To add a new LCT user (pag.386)
To modify the characteristics of the LCT users (pag.387)
To delete a LCT user (pag.387)
Operation available only if it has been selected a single SNMP equipment in connected status, except
for the ELFO, SDH N+1, FAMxc, ALplus Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCplus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
The recording data, if modified, can be saved only by the Superuser and by the users with privileged
and advanced profiles.
5. Press Save.
The certificate is saved in the database of the system.
4. Press Execute.
The request will be sent only to the NEs in disconnected or unreachable status.
Another CONNECT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type column. Type of NE.
Status column. Result of the operation:
OK. The operation was successful, the symbol of the NE changes colour: from brown it
becomes green, light blue, yellow, orange or red depending on the severity of the alarms
present on the NE.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
4. Press Execute.
The request will be sent only to the NEs in connected or unreachable status.
Another DISCONNECT command window opens where, for each NE, there is the indication of:
Address field, logic address.
Type field, type of NE.
Status field, result of the operation:
OK, the operation was successful, the symbol of the NE changes colour: from the current
colour, it becomes brown.
FAILED! ...., the operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
4. Press Execute.
The request will be sent only to the NEs in connected status.
Another ALARM RE-ALIGNMENT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type column. Type of NE.
Status column. Result of the operation:
OK. The operation was successful.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
Command available only if the SNMP equipment is selected, except for ELFO, SDH N+1, FAMxc, PMP,
ALplus Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCplus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
4. Depending on the operation you wish to execute, follow (from the step 3) the procedure:
To transfer the configuration of a SNMP equipment (virtual or real) to one or more real SNMP
equipment (pag.256)
To transfer the configuration of a SNMP equipment (virtual or real) to one or more virtual SNMP
equipment (pag.258)
4. Press Execute.
The request will be sent only to the NEs in disconnected or unreachable status.
Another RESET&CONNECT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type column. Type of NE.
Status column. Result of the operation:
OK. The operation was successful.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
3. Select the Commands > Communication Server Board > Connect command.
The CONNECT BOARD command window opens.
Into the Command Scope area, the system points out all the selected CSs for which it will be executed
the operation. One record is devoted to each CS. Such a record orderly points out the following infor-
mation: IP address and name.
To delete one or more CSs from the list, select the equipment and press Remove From List.
4. Press Execute.
The connection request will be forwarded only to the CSs present into the list and in disconnected
status.
Another CONNECT BOARD command window opens where, for each CS, there is the indication of:
CS Board Address column. IP address of the CS.
CS Name column. CS name.
Status column. Result of the operation:
OK. The operation was successful.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation (in the Status field there is the wording Working) is available the Stop push-but-
ton that, when it is pressed, stops the procedure.
The user can print the displayed information pressing Print.
It is not possible to disconnect a CS if it has at least one port in open status. In this case, first close the
port and then disconnect the CS.
3. Select the Commands > Communication Server Board > Disconnect command.
The DISCONNECT BOARD command window opens.
Into the Command Scope area, the system points out all the selected CSs for which it will be executed
the operation. One record is devoted to each CS. Such a record orderly points out the following infor-
mation: IP address and name.
To delete one or more CSs from the list, select the equipment and press Remove From List.
4. Press Execute.
The disconnection request will be forwarded only to the CSs present into the list and in connected
or unreachable status.
Another DISCONNECT BOARD command window opens where, for each CS, there is the indication of:
CS Board Address column. IP address of the CS.
CS Name column. CS name.
Status column. Result of the operation:
OK. The operation was successful.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation (in the Status field there is the wording Working) is available the Stop push-but-
ton that, when it is pressed, stops the procedure. The user can print the displayed information pressing
Print.
Operation available only to the Superuser and to the user with privileged or advanced profile.
2. Select the equipment for which you wish to execute the series of SNMP commands stored on file.
If the message No Command available for the selected equipment is displayed, the supervision sys-
tem is not provided, for the selected equipment type, with files containing the sequences of SNMP com-
mands. SIAE MICROELETTRONICA provides, on demand, files containing specific sequences of SNMP
commands.
The Execute Command window opens.
The Proxy Agent function is an optional one. The function and the subject command are available if
requested by the customer only.
The Proxy Equipment List command displays the list of the equipment managed by the Proxy Agent and
their Proxy address.
With details it is possible:
To display the list of the equipment managed by the Proxy Agent (pag.239)
To verify/modify the Proxy configuration parameters of an equipment (pag.240)
Menu
bar (1)
Equipment
list (2)
Status
bar (3)
Fig.37 notes
(1) Menu:
File > Close. It closes the window.
Actions > Refresh. It refreshes the information present into the window.
Actions > Modify Proxy Parameters. It displays/changes the Proxy configuration parameters
of the selected equipment.
Help > On Usage. It opens the on-line manual.
The information correspond to the characteristics of the equipment at the selection of the command.
For the NE objects of ALplus Node or ALCplus2 Node type, the detail of the equipment of the nodal
system is pointed out. This equipment is identified by the logic address:
<node name>.X, where X can assume the value A, B or C (ALplus Node object).
<node name>.Y, where Y can assume a value between 1 and 8 (ALCplus2 Node object).
(3) Into the status bar, the system points out the following information:
The activation of the filter. With details, if it has been activated:
The Managed by Proxy Agent box, the system displays into the window the equipment
managed by Proxy Agent.
The Not Managed by Proxy Agent box, the system displays into the window the equip-
ment that are not managed by the Proxy Agent.
The Managed by Proxy Agent and Not Managed by Proxy Agent box, the system dis-
plays into the window the all equipment.
The number of the displayed records and the total number of records (xx of yy). If it has not
been activated any filter, the number of the displayed records corresponds to the total
number of records.
4. To modify one or more parameter, type the new value into the relevant boxes.
If a NE of type ALplus Node or ALCPlus2 Node is selected, the addresses used by Proxy Agent to rec-
ognize the equipment belonging to the node are automatically configured.
5. Press Apply.
Line Test (pag.242). It verifies the real reach ability of the equipment.
Connect (pag.244). It activates the connection between NMS5UX-B and equipment.
Disconnect (pag.246). It deactivates the connection between NMS5UX-B and equipment.
SNMP-Force NE Disconnect (pag.248). It forces the software disconnection of the SNMP
equipment.
SNMP-Ping (pag.249). It executes the Ping in order to check the presence and reachability of
the selected SNMP equipment.
Legacy-Reset&Connect (pag.250). It resets the information, stored into the NMS5UX-B data-
base, relevant to the configuration of one o more Legacy equipment and activates the dialogue
between the equipment and the system itself.
Alarm Re-alignment (pag.252). NMS5UX-B acquires the alarm status present on the equip-
ment.
Configuration Upload (pag.254). NMS5UX-B acquires the current configuration of equipment.
SNMP-Configuration Download (pag.256). It transfers the configuration of an SNMP equip-
ment to another SNMP equipment of the same type.
Communication Server Board (pag.259). It activates/deactivates the connection between
the NMS5UX-B and the CommServer-S
SNMP-Reset Equipment Controller (pag.261). It executes the software reset of the SNMP
equipment.
PMP Clear Alarm Table (pag.262). It transfers to the PMP the alarm default table stored in the
NMS5UX-B database.
The Line Test command verifies the real reach ability of the equipment.
With details it is possible:
To execute the Line Test for one or more equipment (pag.242)
To execute the Line Test for the equipment of one or more containers (pag.242)
1. Select the NE or the group of NEs, for which you wish to execute the test.
2. Select the Command > Line Test > Network Element command or press .
The LINE TEST command window opens.
In the Command Scope area, the selected NEs, for which the operation will be execute, are displayed.
Each NE has a dedicated record, which reports in order: logic address and type.
To delete one or more NEs from the list, select the equipment and press Remove From List. To filter
the NEs according to the type, to activate/deactivate the boxes present in the Filter On Type area.
3. Press Execute.
Another LINE TEST command window opens, where for each NE there is the indication of:
Address column. Logic address.
Type field column. Type of NE.
Status column. Result of the test:
OK. The test was successful.
FAILED!... The test is failed; a message explaining the cause of the failure is displayed
among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
To execute the Line Test for the equipment of one or more containers
1. Select the container symbol(s) that contain the NEs for which you wish to execute the test.
2. Select the Command > Line Test > Container command.
The LINE TEST command window opens.
In the Command Scope area, the selected NEs, for which the operation will be execute, are displayed.
Each NE has a dedicated record, which reports in order: logic address and type.
To delete one or more NEs from the list, select the equipment and press Remove From List. To filter
the NEs according to the type, to activate/deactivate the boxes present in the Filter On Type area.
3. Press Execute.
Another LINE TEST command window opens, where for each NE there is the indication of:
The Connect command activates the connection between NMS5UX-B and equipment.
With details it is possible:
To connect one or more equipment (pag.244)
To connect the equipment of one or more containers (pag.244)
1. Select the NE or the group of NEs for which you wish to connect.
2. Select the Command > Connect > Network Element command or press .
The CONNECT command window opens.
In the Command Scope area, the selected NEs, for which the operation will be execute, are displayed.
Each NE has a dedicated record, which reports in order: logic address and type.
To delete one or more NEs from the list, select the equipment and press Remove From List. To filter
the NEs according to the type, to activate/deactivate the boxes present in the Filter On Type area.
3. Press Execute.
The request will be sent only to the NEs in disconnected or unreachable status.
Another CONNECT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type field column. Type of NE.
Status column. Result of the test:
OK. The operation was successful, the symbol of the NE changes colour: from brown it
becomes green, light blue, yellow, orange or red depending on the severity of the alarms
present on the NE.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
1. Select the container symbol(s) that contain the NEs you wish to connect.
2. Select the Command > Connect > Container command.
The CONNECT command window opens.
In the Command Scope area, the selected NEs, for which the operation will be execute, are displayed.
Each NE has a dedicated record, which reports in order: logic address and type.
To delete one or more NEs from the list, select the equipment and press Remove From List. To filter
the NEs according to the type, to activate/deactivate the boxes present in the Filter On Type area.
The Disconnect command deactivates the connection between NMS5UX-B and equipment.
With details it is possible:
To disconnect one or more equipment (pag.246)
To disconnect the equipment of one or more containers (pag.246)
1. Select the NE or the group of NEs for which you wish to disconnect.
2. Select the Command > Disconnect > Network Element command or press .
The DISCONNECT command window opens.
In the Command Scope area, the selected NEs, for which the operation will be execute, are displayed.
Each NE has a dedicated record, which reports in order: logic address and type.
To delete one or more NEs from the list, select the equipment and press Remove From List. To filter
the NEs according to the type, to activate/deactivate the boxes present in the Filter On Type area.
3. Press Execute.
The request will be sent only to the NEs in connected or unreachable status.
Another DISCONNECT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type field column. Type of NE.
Status column. Result of the test:
OK. The operation was successful, the symbol of the NE changes colour: from the current
colour it becomes brown.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
1. Select the container symbol(s) containing the NEs you wish to disconnect.
The SNMP-Force NE Disconnect command forces the software disconnection of the SNMP equipment.
With software disconnection we mean that the NMS5UX-B system set graphically the equipment in discon-
nected status (brown icon), but it does not communicate the operation to the equipment itself.
The use of this command is necessary if the equipment remains graphically blocked in maintenance status
(pink icon).
1. Select the SNMP NE or the group of SNMP NEs for which you wish to disconnect.
2. Select the Command > SNMP-Force NE Disconnect command.
The FORCED DISCONNECT command window opens.
In the Command Scope area, the selected NEs, for which the operation will be execute, are displayed.
Each NE has a dedicated record, which reports in order: logic address and type.
To delete one or more NEs from the list, select the equipment and press Remove From List. To filter
the NEs according to the type, to activate/deactivate the boxes present in the Filter On Type area.
3. Press Execute.
The request will be sent only to the NEs in connected, unreachable or maintenance status.
Another FORCED DISCONNECT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type field column. Type of NE.
Status column. Result of the test:
OK. The operation was successful, the symbol of the NE changes colour: from the current
colour it becomes brown.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
The SNMP-Ping command executes the Ping in order to check the presence and reachability of the select-
ed SNMP equipment.
2. Select the Command > SNMP-Ping command or press the right mouse button and select Ping.
The Ping window opens, where the operation progress and the final statistics (number of sent and re-
ceived packets, percentage of lost packet, etc.) are displayed.
Each Ping command sends the test packet three times.
The Legacy-Reset&Connect command resets the information, stored into the NMS5UX-B database, rel-
evant to the configuration of one o more Legacy equipment and activates the dialogue between the equip-
ment and the system itself.
With details it is possible:
To reset and connect one or more Legacy equipment (pag.250)
To reset and connect the Legacy equipment of one or more containers (pag.250)
1. Select the Legacy equipment that you wish to reset and connect.
3. Press Execute.
The reset and connection request will be forwarded only to the NEs present into the list and in dis-
connected or unreachable status.
Another RESET&CONNECT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type field column. Type of NE.
Status column. Result of the test:
OK. The operation was successful, the symbol of the NE changes colour: from the current
colour it becomes brown.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
1. Select the container symbol(s) containing the Legacy equipment that you wish to reset and connect.
3. Press Execute.
The reset and connection request will be forwarded only to the NEs present into the list and in dis-
connected or unreachable status.
Another RESET&CONNECT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type field column. Type of NE.
Status column. Result of the test:
OK. The operation was successful, the symbol of the NE changes its current colour brown.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
The Alarm Re-alignment command acquires the alarm status present on the equipment.
With details it is possible:
To re-align the alarms of one or more equipment (pag.252)
To re-align the alarms of the equipment of one or more containers (pag.252)
1. Select the NE or the group of NEs for which you wish to re-align the alarms.
2. Select the Command > Alarm Re-alignment > Network Element command or press .
The ALARM RE-ALIGNMENT command window opens.
In the Command Scope area, the selected NEs, for which the operation will be execute, are displayed.
Each NE has a dedicated record, which reports in order: logic address and type.
To delete one or more NEs from the list, select the equipment and press Remove From List. To filter
the NEs according to the type, to activate/deactivate the boxes present in the Filter On Type area.
3. Press Execute.
The request will be sent only to the NEs in connected status.
Another ALARM RE-ALIGNMENT command window opens where, for each NE, there is the indication of:
Address column. Logic address.
Type field column. Type of NE.
Status column. Result of the test:
OK. The operation was successful.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
1. Select the container symbol(s) that contain the NEs for which you wish the re-align the alarms.
3. Press Execute.
1. Select the NE or the group of NEs, which you wish to acquire the configuration.
2. Select the Command > Configuration Upload > Network Element command or press .
The UPLOAD command window opens.
In the Command Scope area, the selected NEs, for which the operation will be execute, are displayed.
Each NE has a dedicated record, which reports in order: logic address and type.
To delete one or more NEs from the list, select the equipment and press Remove From List. To filter
the NEs according to the type, to activate/deactivate the boxes present in the Filter On Type area.
3. Press Execute.
The request will be sent only to the NEs in connected status.
Another UPLOAD command window opens, where for each NE there is the indication of:
Address column. Logic address.
Type field column. Type of NE.
Status column. Result of the test:
OK. The operation was successful.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation, the Stop push-button is available, which stops the procedure, if selected. For
example, if the execution of the operation has been required for ten NEs, the system sends the com-
mand to the first NE, then it will pass to the next one. If, during the execution of the command for the
second NE, the user presses Stop, the system will terminate the operation in progress and then will
terminate the procedure. So, the list will display only the first two NEs.
To print the displayed information press Print.
1. Select the container symbol(s) that contain the NEs, which you wish to acquire the configuration.
3. Press Execute.
The command is available only for the SNMP equipment except for the ELFO, SDH N+1, FAMxc, PMP,
ALplus Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCPlus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
1. Select the SNMP equipment whose type/configuration correspond to the characteristics of the SNMP
equipment wished for the transferring of the configuration.
3. Select, in the Source area, the (real or virtual) NE having the configuration you wish to transfer.
5. Press Parameter Selection to define the configuration parameters you wish to transfer.
The View Download Parameter window opens.
In the area:
Group, the logic groups, which the configuration parameters of the type of the considered equip-
ment are subdivided in, are displayed.
Attributes, the attributes relevant to the selected group in the Group area are displayed.
Each group and parameter is characterized by a check box.
If the box is active, it points out that the group/parameter will be transferred during the download. If
the box is inactive, it points out that the group/parameter will not be transferred during the download.
6. Activate the check boxes relevant to the groups/parameters that you do not wish to transfer.
The activation of one group is prioritary with respect to the setting of the parameters contained in
it. For example, if the group A is activated, when the configuration will be transferred, the values of the
parameters associated to the group A will be transferred, even if the box of the single parameters is
not active.
In order to activate all the check boxes at the same time, press Select all. In order to deactivate all
the check boxes at the same time, press Deselect all.
7. Select, in the Destination area, the NE or the group of NEs to which you wish to transfer the configu-
ration.
8. Select the Command > Download Configuration command and confirm.
In the Messages area, the start and the end of the operation are displayed as messages.
Menu
bar (1)
List of (real
and/or virtual)
NEs, present
in the map, List of (real
with the same and/or virtual
characteristics (3)) NEs, present
(type and values of in the map, with
the configuration the same
parameters) of characteristics
the selected NE, (type and values
from which it is of the configuration
possible to COPY parameters) of the
the configuration selected NE, to
to transfer (2) which it is possible
to TRANSFER
the configuration
(4)
This area
displays,
in form of
messages,
the operations
in progress
Fig.38 notes
(1) Menu:
File > Close. It closes the window.
Command > Download Configuration. It transfer the configuration of a (real or virtual) NE
to one or more real NEs.
Command > Copy Configuration. It transfer the configuration of a (real or virtual) NE to one
or more virtual NEs.
Action > Refresh. It updates the data present in the window.
Help > On Usage. It opens the on-line manual.
Help > About Application. Version of the module that manages the considered functionality.
(2) In the list, it is possible to display real and virtual NEs at the same time.
For the first ones, it is necessary to activate the Real Equipment box, for the second ones the Virtual
Equipment box.
(3) In the list, it is possible to display only real NEs or only virtual NEs.
To display the real ones, it is necessary to select the Real Equipment (download) option, to display
the virtual ones the Virtual Equipment (copy) option.
(4) The list will not contain the (real or virtual) NE selected in the Source area, as the NE, which the
configuration to be transferred from is taken, is automatically excluded by the list of the NEs which
the configuration can be transferred to.
1. Select the SNMP equipment whose type/configuration correspond to the characteristics of the wished
SNMP equipment for the transfer of the configuration.
3. Select, in the Source area, the (real or virtual) NE having the configuration you wish to transfer.
5. Select from the list the NE or the group of NEs, which you wish to transfer to configuration to.
The Communication Server Board command activates/deactivates the connection between the
NMS5UX-B and the CommServer-S.
With details it is possible:
To connect one or more CommServer-S (pag.259)
To disconnect one or more CommServer-S (pag.259)
The command is available only if the modules for the management of the Legacy equipment have been
installed.
2. Select the Command > Communication Server Board > Connect command.
The CONNECT BOARD command window opens.
Into the Command Scope area, the system points out all the selected CSs for which it will be executed
the operation. One record is devoted to each CS. Such a record orderly points out the following infor-
mation: IP address and name.
To delete one or more CSs from the list, select the equipment and press Remove From List.
3. Press Execute.
The connection request will be forwarded only to the CSs present into the list and in disconnected
status.
Another CONNECT BOARD command window opens, where for each CS there is the indication of:
CS Board Address column. IP address of the CS.
CS Name column. CS name.
Status column. Result of the operation:
OK. The operation was successful.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation (in the Status field there is the wording Working) is available the Stop push-but-
ton that, when it is pressed, stops the procedure.
To print the displayed information press Print.
2. Select the Command > Communication Server Board > Disconnect command.
The DISCONNECT BOARD command window opens.
3. Press Execute.
The disconnection request will be forwarded only to the CSs present into the list and in connected
or unreachable status.
Another DISCONNECT BOARD command window opens, where for each CS there is the indication of:
CS Board Address column. IP address of the CS.
CS Name column. CS name.
Status column. Result of the operation:
OK. The operation was successful.
FAILED!... The operation is failed; a message explaining the cause of the failure is dis-
played among brackets.
During the operation (in the Status field there is the wording Working) is available the Stop push-but-
ton that, when it is pressed, stops the procedure.
To print the displayed information press Print.
The SNMP-Reset Equipment Controller command executes the software reset of the equipment.
The operation consists in the re-initialization of all the communication channels (for example, with the su-
pervision system) of the equipment. Its execution causes a temporary disconnection of the equipment from
NMS5UX-B.
The command is available only for the SNMP equipment except for the ELFO, SDH N+1 and FAMxc.
The PMP Clear Alarm Table command transfer to the PMP equipment the default table of the alarms
stored in the NMS5UX-B database.
The files, which contains the tables of the default alarms relevant to each type of NE managed by the
NMS5UX-B, are copied in the database during the installation of the system.
Network Alarm History (pag.264). It displays/manages the alarm history stored in the
NMS5UX-B database, relevant to the equipment of the open map.
Network Current Alarms (pag.273). It displays/manages the alarms active in the equipment
of the open map.
Old Alarm History (pag.279). It displays/manages the alarm history previously saved to file.
NE Alarm History (pag.285). It displays/manages the alarm history of an equipment.
NE Current Alarms (pag.286). It displays/manages the alarms active in an equipment.
SNMP-NE History Log (pag.287). It displays/manages the alarm list stored on the controller
of a SNMP equipment.
SNMP-NE Command Log (pag.291). It displays/manages the list of the operations executed
by the users, stored on the controller of a SNMP equipment.
Alarm Summary (pag.295). It displays/manages the summary of the alarm history stored in
the NMS5UX-B database, relevant to the equipment of the open map.
SNMP-Event Statistics (pag.300). It displays the alarm statistics of all SNMP equipment
present in the network.
Transaction Log (pag.305). It displays/manages the list of the operations executed by the
NMS5UX users, who have modified the configuration of the network, of the supervision system
and of an equipment.
The Network Alarm History command displays/manages the history of the alarm/status/event signall-
ings (alarms) stored in the NMS5UX-B database, relevant to the equipment of the open map.
With details it is possible:
To display the alarm history of the equipment present in the map (pag.264)
To save/print the alarms list (pag.266)
To copy the alarms list to a text editor (pag.267)
To delete the alarms (pag.267)
To mark the alarms (pag.267)
To display the acknowledge information of an alarm (pag.268)
To activate/deactivate the automatic updating of the data (pag.268)
To filter the alarms list (pag.269)
To highlight in the map the symbol of an equipment (pag.270)
To verify the time interval between two different alarms (pag.270)
To verify the configuration/functional status of an equipment (pag.271)
To sort the alarms list (pag.271)
At the opening of the window a filter is applied to the alarms list: only the alarms, whose detection
date is successive to the midnight of the current day, are displayed. Besides, by default, the automatic
updating of the information is inactive.
A warning message could be displayed, informing that the database contains a number of alarms great-
er than N.
For this cause, the window will display only the records, in chronological order from the newest to the
oldest one, until N.
The N limit is not a memory limit, but simply a limit in the displaying of the alarms.
In order to read the alarms successive to N, it is sufficient to delete some records.
The N limit can be modified by the Superuser.
Menu
bar (1)
Alarms
list (2)
Status
bar (3)
Fig.39 notes
(1) Menu:
File > Print/Save. It prints or saves to file the alarms list.
File > Export. It copies into a text editor the alarms list.
File > Close. It closes the window.
Action > Delete. It deletes one or more records from the databases.
Action > Acknowledge. It marks one or more records, in such a way that the system mem-
orizes that the user has seen the alarms.
Action > Freeze Window/Unfreeze Window. The commands are displayed one in alternative
to the other: the first stops the automatic updating of the data, the second one reactivates it.
Action > Re-read Database. It updates the data present in the window.
View > Set Filter. It filters the alarms list.
View > Elapsed Time. It determines the time interval between the recordings of two different
alarms.
View > HighLight Equipment On Map. It highlights in the map the symbol of the NE which
the selected record is referred to.
View > ClearHighlights. It removes the highlighted condition from all the symbols marked
by the HighLight Equipment On Map command.
View > Equipment Info. It displays the characteristics and the operating status of the NE
which the selected record is referred to.
View > Sort Mode. It sorts the alarms list.
Help > On Usage. It opens the on-line manual.
For the NE objects of ALplus Node or ALCplus2 Node type, the detail of the equipment of the nodal
system is pointed out. This equipment is identified by the logic address:
<node name>.X, where X can assume the value A, B or C (ALplus Node object).
<node name>.Y, where Y can assume a value from 1 to 8 (ALCplus2 Node object).
The date/time is set by the element that generated the alarm; in the most cases it is the NE con-
troller.
Operation available only to the Superuser and to the users with privileged or advanced profile.
The operation is not available if the symbol is present in the status bar of the Alarm History Browser
window. To execute the operation, it is necessary first to update the window, selecting the check sign.
Operation available only to the Superuser and to the users with privileged or advanced profile.
The operation is not executed if the symbol is present in the status bar of the Alarm History Browser
window. To execute the operation, it is necessary first to update the window, selecting the check sign.
After a record has been marked, the operation cannot be undone.
2. To mark:
A group of alarms, select the records and the Action > Acknowledge > Selected Alarms
command.
The displayed alarms, select the Action > Acknowledge > Filtered Alarms command. If the
filters are not active, the displayed records correspond to the records stored in the database.
All the alarms of the database, select the Action > Acknowledge > All Alarms command.
It is possible to mark an alarm also by a double click of the mouse button.
The Acknowledged Info window opens.
The User box displays the username of the NMS5UX user who required the marking of the records. The
value of the box is automatically set to the username of the NMS5UX user who opened the map. The
value cannot be changed.
3. Type in the Trouble Identification Code box a code identifying the records (alphanumeric string of max
16 characters); it can be used later as search criterion.
The setting of this parameter is optional.
4. Type in the Comment box some additional information (alphanumeric string of max 500 characters).
The setting of this parameter is optional.
5. Press Ok.
If the selected record refers to an alarm:
2. Select the record which you wish to display the detail of the acknowledge for.
Identification
code (1)
Detailed
information
of the
acknowledge
when the signal
was in status:
Detailed detected
information (2) (3)
of the
acknowledge
when the signal
was in status:
detected and
cleared
(2) (3)
Fig.40 notes
(1) Identification code of the record assigned by the user during the alarm acknowledge.
(2) Option:
User. Username of the NMS5UX user who executed the acknowledgement of the record.
Time. Moment when the record has been acknowledged <day-month-year hour:min-
utes:seconds>.
Comment. Additional information.
(3) If the alarm has been acknowledged the first time when it was in detected-cleared status, the data
present in the SET Ack Info and CLEAR Ack Info areas are the same.
If the alarm has never been acknowledged, all the fields will be empty.
2. To activate the automatic updating of the data, select the Action > Unfreeze Window command or
the symbol .
3. To deactivate again the automatic updating of the data, select the Action > Freeze Window com-
mand or the symbol .
The Freeze Window and Unfreeze Window commands are displayed alternatively.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the Alarm History Browser window only the record that satisfy specific criteria.
Each time that the list is filtered, all the records are considered, both the displayed and the hidden ones.
When the Alarm History Browser window is closed, the possible activation of the filters is automatically
cleared.
In the window, there are the push-buttons:
Save.... It saves the set criteria to a file.
On the choice of the push-button, the Save Filter window opens.
Type the name you wish to assign to the file in the Selection box and press OK.
Load.... It opens the file, where a previously saved specific setting of filters is contained.
On the choice of the push-button, the Load Filter window opens.
Select the wished file in the Files list and press OK.
Delete.... It deletes the file where a previously saved specific setting of filters is contained.
On the choice of the push-button, the Delete Filter window opens.
Select the wished file in the Files list and press OK.
Clear Filters. It clears the activation of all the filters, except for the <Severity>, Match Ac-
knowledged, Match Unacknowledged criteria.
Cancel. It closes the window and does not execute the operation.
Help. It opens the on-line manual.
The path indicated in the Selection box cannot be changed.
5. If you wish that the alarms are sorted also according to their address, activate the box Group by Ad-
dress (second sorting criterion).
6. Press Apply (it executes the sorting and closes the window) or Set (it stores the setting, but does not
execute the sorting and closes the window).
If pressed Apply, the Alarm History Browser window will list the records in the set order.
The information present in the Alarm History Browser window are dynamically updated only if the proce-
dure for the automatic updating is active (pag.268).
At the opening of the Alarm History Browser window, the procedure of automatic updating of the infor-
mation is, by default inactive (the default setting can be modified by the Superuser).
The presence of the symbol in the status bar of the window points out that the displayed information
are misaligned with respect to those stored in the database of NMS5UX-B.
This occurs when:
Two or more NMS5UX users (each one on a different terminal) have opened the Alarm History
Browser window for the same map and, in a window, some records have been marked or delet-
ed, the system does not update all the open windows. This is necessary to avoid that the win-
dows must be continuously refreshed while the users are using them.
One or more records are marked in a Current Alarms Browser window. The record is not auto-
matically marked also in the Alarm History Browser window, if open.
To update the window, it is sufficient to click on the symbol . It is possible to refresh the window also
modifying the order of the displaying of the records (pag.271) or applying a filter (pag.269).
The alarms are stored in the database of NMS5UX-B (Alarm History table).
They remain stored for a certain number of days (which can be configured by the Superuser - by default
90 days), after which they are automatically deleted.
Also, it is possible to configure the maximum number of records in the Alarm History table (value that can
be set by the Superuser) that can be stored.
During the day, all the alarms sent by the equipment are stored in the table (even if their number exceeds
the maximum value of records). At midnight, the number of record is checked; if this exceeds the maxi-
mum set number, the system will delete, only among the raised and cleared signallings, the oldest records.
If the alarm history contains all active and not cleared alarms and their number exceeds the maximum set
value, the system will NOT delete any record.
When the maximum number of record in the table is exceeded, the message Alarm History occupation ex-
ceeded 100% is periodically displayed, warning about the critical situation. The display of the message and
the frequency with which it is displayed can be configured by the Superuser.
The Network Current Alarms command displays/manages the alarm/status/event signallings (alarms)
active in the equipment of the open map.
As help to the description of the command, see par. Modality of updating of the data (pag.278).
At the opening of the window, by default, the automatic updating of the information is inactive.
Menu
bar (1)
Alarms
list (2)
Status
bar (3)
(1) Menu:
File > Print/Save. It prints or save to file the alarm list.
File > Close. It closes the window.
Action > Acknowledge. It marks one or more records, so that the system memorizes that
the user has seen the alarms.
Action > Freeze Window/Unfreeze Window. The commands are displayed alternatively: the
first one stops the automatic updating of the data, the seconds re-activates it.
Action > Re-read Database. It updates the data present in the window.
View > Set Filter. It filters the alarms list.
View > Elapsed Time. It determines the time interval that separates the recording of two
different alarms.
View > HighLight Equipment On Map. It highlights, in the map, the symbol of the NE which
the selected record is referred to.
View > ClearHighlights. It deletes the condition of highlighted from all the symbols marked
by the HighLight Equipment On Map commands.
View > Equipment Info. It displays characteristics and the functional status of the NE which
the selected record is referred to.
Help > On Usage. It opens the on-line manual.
2. To mark:
A group of alarms, select the records and then the Action > Acknowledge > Selected Alarms
command.
The displayed alarms, select the Action > Acknowledge > Filtered Alarms command. If fil-
ters are not active, the displayed records correspond to the records stored in the database.
All the alarms of the database, select the Action > Acknowledge > All Alarms command.
It is also possible to mark an alarm, by means of a double click over it.
2. To activate the automatic updating of the data, select the Action > Unfreeze Window command or
the symbol .
The Freeze Window and Unfreeze Window commands are displayed alternatively.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays, in the Current Alarms Browser window, only the records that satisfy the activated
criteria.
Each time the list is filtered, all the records are displayed, both the displayed and the hidden ones.
When the Current Alarms Browser window is closed, the possible activation of filters is automatically
cancelled.
The information present in the Current Alarms Browser window are dynamically updated only if the proce-
dure of automatic updating is active (pag.268).
At the opening of the Current Alarms Browser window, the procedure of automatic updating is, by de-
fault, inactive (the default setting can be modified by the Superuser).
The Old Alarm History command displays/manages the history of the alarm/status/event signallings
(alarms) previously saved to file.
With details it is possible:
To display the alarm history present in the Old History table (pag.279)
To save/print the alarms list (pag.281)
To copy the alarms list into a text editor (pag.281)
To filter the alarms list (pag.281)
To highlight in the map the symbol of an equipment (pag.283)
To verify the time interval between two different alarms (pag.283)
To sort the alarms list (pag.284)
To display the acknowledge information of an alarm (pag.284)
In the Old History table is stored the alarm history saved by the Alarm History Backup (pag.423)
command and restored by the Alarm History Restore (pag.424) command.
If, at the opening of the window, the table is empty, it is necessary to restore from the backup file
saved before, the list of wished alarms (pag.424).
These alarms will remain available in the Old History table and in the Old History Browser window, until
a different list of alarms is restored.
Menu
bar (1)
Alarms
list (2)
Status
bar (3)
(1) Menu:
File > Print/Save. It prints or save to file the alarms list.
File > Export. It copies in a text editor the alarms list.
File > Close. It closes the window.
Action > Re-read Database. It updates the data present in the window.
View > Set Filter. It filters the alarms list.
View > Elapsed Time. It determinates the time intervals that separates two different alarms.
View > HighLight Equipment On Map. It highlights in the map, the symbol of the NE which
the selected record refers to.
View > ClearHighlights. It removes the condition of highlighted from all the symbols marked
by the HighLight Equipment On Map command.
View > Sort Mode. It sorts the list of records.
Help > On Usage. It opens the on-line manual.
For the NE objects of ALplus Node or ALCplus2 Node type, the detail of the equipment of the nodal
system is pointed out. This equipment is identified by the logic address:
<node name>.X, where X can assume the value A, B or C (ALplus Node object).
<node name>.Y, where Y can assume a value from 1 to 8 (ALCplus2 Node object).
The date/time is set by the element that generated the alarm; in the most cases it is the NE con-
troller.
(3) Field:
xx of yy. Number of displayed records (xx) and number of total records (yy). If filters are
not active, the number of displayed records corresponds to the total records.
Filters:... Activation of one or more filters.
Sort:... Order used to list the alarms.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
5. If you wish that the alarms are sorted also according to their address, activate the box Group by Ad-
dress (second sorting criterion).
6. Press Apply (it executes the sorting and closes the window) or Set (it stores the setting, but does not
execute the sorting and closes the window).
If pressed Apply, the Old History Browser window will list the records in the set order.
The NE Alarm History command displays/manages the history of the alarm/event/status signallings
(alarms) relevant ONLY to the selected equipment.
The choice of the command opens the Alarm History Browser window (Fig.39).
The description of the window and the operations that can be executed are the same reported in the
par. Network Alarm History (pag.264).
Into the Alarm History Browser window to display the alarm relevant to other equipment, deactivate the
Match Address filter.
If a NE object of ALplus Node or ALCplus2 Node type is selected, the Alarm History Browser window displays
the detail of the equipment of the nodal system. This equipment is identified by the logic address:
<node name>.X, where X can assume the value A, B or C (ALplus Node object).
<node name>.Y, where Y can assume a value from 1 to 8 (ALCplus2 Node object).
The NE Current Alarms command displays/manages the alarm/event/status signallings (alarms) active
in the selected equipment.
The choice of the command opens the Current Alarms Browser window (Fig.41).
The description of the window and the operations that can be executed are the same reported in the
par. Network Current Alarms (pag.273).
Into the Current Alarms Browser window to display the alarm relevant to other equipment, deactivate the
Match Address filter.
If a NE object of ALplus Node or ALCplus2 Node type is selected, the Current Alarms Browser window dis-
plays the detail of the equipment of the nodal system. This equipment is identified by the logic address:
<node name>.X, where X can assume the value A, B or C (ALplus Node object).
<node name>.Y, where Y can assume a value from 1 to 8 (ALCplus2 Node object).
The SNMP-NE History Log command displays/manages the alarm list stored on the controller of an
equipment (NE Log).
With details it is possible:
To display the list of the NE Log of a SNMP equipment (pag.287)
To create a NE Log (pag.288)
To create more NE logs at the same time (pag.288)
To display the content of a NE Log (pag.289)
To delete a NE Log (pag.289)
To delete all the NE logs of a SNMP equipment (pag.289)
To delete the alarms stored in the controller of a SNMP equipment (pag.290)
The command is available only for the SNMP equipment except for the ELFO, SDH N+1, FAMxc, PMP.
3. Double click, in the Selected Equipment area, the equipment for which you wish to verify the NE Log.
The area on the right displays the list of the NE Logs (Fig.43).
If the message No files available for equipment ... is displayed, no NE Log is available for the specific
equipment.
Logic address
of the equipment
which the NE logs
present in the area
below are referred to
List of the NE
List of logs, stored
equipment in the disk,
selected in relevant to
the map (1) a single
equipment (2)
(2) Each NE Log is identified by a record, where the date (day-month-year) and the time (hour:min-
utes:seconds) of the file creation are contained.
When a Log is inactive, it means that it has been selected to be displayed.
When the NE Log is removed from the Selected Files List area, the record that represents it is re-
activated.
To create a NE Log
3. Select, in the Selected Equipment area, the equipment for which you wish to create a NE Log.
3. Select, in the Selected Equipment area, the equipment for which you wish to create a NE Log.
3. Double click, in the Selected Equipment area, the equipment for which you wish to verify the NE Log.
In the ...history log files area, the list of the NE Logs relevant to the selected equipment will be pointed
out.
4. Double click on the NE Log for which you wish to verify the content.
The NE Log is displayed in the Selected files list area. The file, in the ...history log files area, is disabled.
5. Repeat the previous step, to insert all the wished NE Logs in the Selected files list area.
To delete a NE Log
3. Double click, in the Selected Equipment area, the equipment for which you wish to delete a NE Log.
In the ...history log files area, the list of the NE Log relevant to the selected equipment will be displayed.
3. Select, in the Selected Equipment area, the equipment for which you wish to delete all the NE Logs.
3. Select, in the Selected Equipment area, the equipment for which you wish to delete the alarms.
4. Select the NE Log command and press the right mouse button.
A pop-up menu opens.
It is possible to delete the alarms stored in the controller of an equipment also during the creation of
a NE Log (pag.288).
The SNMP-NE Command Log command displays/manages the list of the operations executed by the us-
ers, stored on the controller of an equipment (NE Command Log).
With details it is possible:
To display the list of the Command Log of a SNMP equipment (pag.291)
To create a Command Log (pag.292)
To create more Command Logs at the same time (pag.293)
To display the content of a Command Log (pag.293)
To delete a Command Log (pag.294)
To delete all the Command Logs of a SNMP equipment (pag.294)
To delete the list of the operations stored in the controller of a SNMP equipment (pag.294)
The command is available only for the SNMP equipment except for the ELFO, SDH N+1 and FAMxc.
3. Double click, in the Selected Equipment area, the NE for which you wish to verify the Command Log.
The area on the right displays the list of the Command Logs (Fig.44).
If the message No files available for equipment ... is displayed, no Command Log is available for the
specific equipment.
Logic address
of the equipment
which the NE logs
present in the area
below are referred to
List of the NE
List of logs, stored
equipment in the disk,
selected in relevant to
the map (1) a single
equipment (2)
(2) Each Command Log is identified by a record, where the date (day-month-year) and the time
(hour:minutes:seconds) of the file creation are contained.
3. Select, in the Selected Equipment area, the equipment for which you wish to create a Command Log.
3. Double click, in the Selected Equipment area, the NE for which you wish to verify the Command Log.
In the ...history log files area, the list of the Command Logs relevant to the selected equipment will be
pointed out.
4. Double click on the Command Log for which you wish to verify the content.
The Commands Log File Information window is displayed where, for each operation, is pointed out in
the column:
Date/Time. Date and time when it has been executed the operation.
Source Address. IP address of the machine (PC or workstation) from which it has been executed
the operation.
User. Name of the user who has executed the operation.
Object. Object to which the operation refers.
Instance. Name of the equipment instance to which the operation refers.
Value Set. Set value.
The presence of the symbol points out that the information is not available because it is a not signif-
icant one for the type of operation to which it refers.
3. Double click, in the Selected Equipment area, the NE for which you wish to delete a Command Log.
In the ...history log files area, the list of the Command Log relevant to the selected equipment will be
displayed.
4. Select the Command Log and press the right mouse button.
A pop-up menu opens.
3. Select, in the Selected Equipment area, the equipment for which you wish to delete all the Command
Logs.
4. Select the right mouse button.
A pop-up menu opens.
To delete the list of the operations stored in the controller of a SNMP equip-
ment
NE Command Log is a file where the system records the operations executed by the SCT/LMT or NMS5UX
user stored into the controller of the selected equipment.
The Log read from equipment (Command Log) is stored on the disk of the machine and it remains available
for subsequent consultations done by the user.
The list of the Command Log and their contents can be displayed only through the Equipment History Com-
mand Log Management Main window (Fig.44).
The Alarm Summary command displays/manages the summary of the alarm/status/event signallings
(alarms) stored in the NMS5UX-B database, relevant to the equipment of the open map.
To display the summary of the alarm history subdivided for the severity rel-
evant to the equipment present in the map
Activation
status of
the filters
(1) Automatic
updating
of data (2)
Data
Indication of refresh
"Status" time (3)
change (4)
Number of
alarms
subdivided
according
type and
severity (5)
Number of
alarms
detected
but not
cleared yet (8)
Criterion used
Number of
to subdivide
alarms
the alarms (6)
detected
and cleared
Push-buttons (7)
(9)
(1) Label:
Filters: NONE. There are not filters active.
Filters: <applied filters>. There are indicated filters active.
It is possible to insert a description in this area (pag.297).
(3) Interval (in seconds) between an automatic update of the data and the next one
The parameter is meaningful only when the Auto Refresh box is active.
(4) The presence of the asterisk next to the record points out that, from when the Siae Alarm Summary
window has been opened or from the last selection of the Clear Alert push-button, a change oc-
curred: an alarm has been detected or cleared.
(5) It is possible that, in the Siae Alarm Summary window, there are not one or more records relevant
to the type of signallings/severity levels. Their presence is subjected to the activation of filters.
When the box is deactivated, relevant to a type of signalling/severity, the Filtered record appears
in the Siae Alarm Summary window. This record displays the total alarms of the only records
present in the window. For example, if in the window there are only the Critical (Cleared 20 - Active
15) and Major (Cleared 5 - Active 3) records, the Filtered record will indicate the sum of their alarm
(Cleared 25 - Active 18).
In detail, the option:
Cleared (Filtered record), points out the total number of detected/cleared alarms relevant
only to the records present in the window.
Active (Filtered record), points out the total number of detected but not cleared alarms rel-
evant only to the records present in the window.
(6) Record:
Critical. Alarms with Critical severity.
Major. Alarms with Major severity.
Minor. Alarms with Minor severity.
Warning. Alarms with Warning severity.
Status. Status signallings.
Normal. Event signallings.
All. All the signallings (alarms, status, events).
(7) Option:
Cleared (Critical record). Detected/cleared alarms with Critical severity.
Cleared (Major record). Detected/cleared alarms with Major severity.
Cleared (Minor record). Detected/cleared alarms with Minor severity.
Cleared (Warning record). Detected/cleared alarms with Warning severity.
Cleared (Status record). Detected/cleared status signallings.
Cleared (Normal record). Detected/cleared event signallings.
Cleared (All record). Total number of detected/cleared signallings.
(8) Option:
Active (Critical record). Detected alarms with Critical severity.
Active (Major record). Detected alarms with Major severity.
Active (Minor record). Detected alarms with Minor severity.
Active (Warning record). Detected alarms with Warning severity.
Active (Status record). Detected status signallings.
Active (Normal record). Detected event signallings.
Active (All record). Total number of detected signallings.
The push-button is not available when the Auto Refresh box is active.
Clear Alert. It resets the signallings of status change.
Filter. It filters the alarms list.
2. Press Filter.
The Filters Setting window opens.
Select one or more boxes present in the window, according to the criteria you wish to use.
The activation of each box enables the criterion or expands the window displaying a section containing
the following option:
Match Severity. Type of signalling (alarm/status/event) and, for the alarms, their severity (the
colour of the box, if active, reflects the colour associated to the severity of the alarm or the type
of signalling). Activating the box:
Critical (red), the alarms with Critical severity will be displayed.
Major (orange), the alarms with Major severity will be displayed.
Minor (yellow), the alarms with Minor severity will be displayed.
Warning (light blue), the alarms with Warning severity will be displayed.
Status (blue), the status signallings will be displayed.
Normal (green), the event signallings will be displayed.
The deactivation of a box causes the deletion of the relevant record from the Siae Alarm
Summary window and the displaying of the Filtered record (Fig.45).
Occurred After and Occurred Before. Date/time of the alarm.
Activating the box:
Occurred After, the list will display only the records whose recording date is equal or after
that displayed next to the option.
Occurred Before, the list will display only the records whose recording date is equal or
before that displayed next to the option.
To modify the date/time displayed next to the specific option, move the indicator of the scrolling
bar or click on the arrows located on the sides of the bar.
In the box located over the bar, choosing the Coarse Granularity item, it is possible to modify
the date/time by steps of one hour, while choosing the Fine Granularity item by steps of one
second.
Activating contemporary the boxes and setting properly the date/time, it is possible to determi-
nate a time interval.
Match Address. Logic address of the Network Element.
The logic addresses can be set by one of the following ways:
Select the symbol or the symbols of the interested NEs, directly in the map and press
Add From Map.
Type the logic address of the NE in the Source box and press Add.
The values set in this way will be inserted in the area located next to the Match Address box.
It is possible to delete from the list a single item pressing, after having highlighted it, the Re-
move push-button, or all the items contemporarily pressing Remove All.
Match Object. Physical/logic objects that compose the NE.
To set the criterion:
Open the Equipment Type menu and select the type of NE.
Open the Object menu and set the wished object.
It is possible to set only one class of objects at a time or all the classes contemporarily selecting
the All Objects item.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the Siae Alarm Summary window only the record that satisfy the activated cri-
teria.
Each time that the list is filtered, all the records are considered, both the displayed and the hidden ones.
When the Siae Alarm Summary window is closed, the possible activation of the filters is automatically
cleared.
2. To ACTIVATE the automatic refresh of the window, activate the Auto Refresh box.
The data are automatically refresh each N seconds, displayed in the Timeout (sec) box.
To change the parameter, type the new value in the box (numeric value between 30 and 999 seconds).
It is possible to modify the value also when the automatic refresh is active. In this case, at next refresh
after the modification of the timeout, the new value will be acquired as valid.
3. To DEACTIVATE the automatic refresh of the window, deactivate the Auto Refresh box.
The SNMP-Event Statistics command displays the statistics of the alarm/status/event signallings
(alarms) of the SNMP equipment.
With details it is possible:
To display the statistics of the alarms subdivided by time interval (pag.300)
To display the statistics of the alarms subdivided by equipment (pag.302)
To display the statistics of the alarms subdivided by alarms (pag.302)
To delete the alarms (pag.303)
To filter the alarms (pag.303)
The statistics refer to the alarms occurred on all the SNMP equipment present in the network.
Only the 15 minute periods, where alarms are present, are displayed.
Press Up to return to the previous display.
4. Double click on the histogram of a quarter to display the statistics of the alarms of that day/quarter,
subdivided by single equipment.
Each histogram identifies an equipment. For each equipment, the logic address, between brackets, the
equipment type and the number of detected alarms are pointed out.
Press Up to return to the previous display.
5. Double click on the histogram of an equipment to display the detail of the alarms detected by the equip-
ment in the specific day/quarter.
Each histogram identifies an alarm. For each alarm, the description of the alarm and the number of
time that the alarm has been detected in the specific period are pointed out.
The description of the alarm is the same reported in the Message field of the Alarm History Browser
window (Fig.39) and Current Alarms Browser window (Fig.41).
Fig.46 notes
(1) Menu:
File > Close. It closes the window.
Graphics > Network Event Counters. It displays the statistics of the alarms subdivided by
days.
Graphics > Equipment Event Counters. It displays the statistics of the alarms subdivided by
equipment.
Graphics > Event Frequency. It display the statistics of the alarms subdivided by alarms.
Maintenance > Filtered Delete. It deletes the specific group of the alarms stored into the sta-
tistics database.
Maintenance > Delete All. It deletes all alarms stored into the statistics database.
Help > On Usage. It opens the help on-line.
Help > About Application. Version of the module that manages the considered functionality.
(3) Push-button:
Up. It returns to the immediately previous display
Reload. It updates the data present in the window.
Filter. It filters the list of the alarms.
When one or more filter criteria are active, an asterisk is present in the push-button.
3. Double click on the histogram of an equipment to display the statistics of the relevant alarms subdivided
in days.
Each histogram identifies a day. By default, the last 30 days, where alarms are present, are displayed.
The parameters can be configured by the Superuser.
Press Up to return to the previous display.
4. Double click on the histogram of a day to display the statistics of the alarms of that equipment/day
subdivided in periods of 15 minutes.
Each histogram identifies a quarter.
Only the 15 minutes periods, where alarms are present, are displayed.
Press Up to return to the previous display.
5. Double click on the histogram of a quarter to display the detail of the alarms detected by the equipment
in the specific day/quarter.
Each histogram identifies an alarm. For each alarm, the description of the alarm and the number of
times that the alarm has been detected in the specific period are detected.
The description of the alarm is the same reported in the Message field of the Alarm History Browser
window (Fig.39) and Current Alarms Browser window (Fig.41).
Press Up to return to the previous display.
3. Double click on the histogram of an equipment/alarm to display the statistics of the alarm detection
subdivided in days.
Each histogram identifies a day. By default, the last 30 days, where alarms are present, are displayed.
The parameters can be configured by the Superuser.
Press Up to return to the previous display.
4. Double click on the histogram of a day to display the statistic of the detection of the subject alarm/day,
subdivided in periods of 15 minutes.
Each histogram identifies a quarter.
Only the 15 minutes periods, where alarms are present, are displayed.
Press Up to return to the previous display.
This operation allows deleting ONLY the alarms stored in the statistics database and not in the general
database of NMS5UX-B (for this operation, refer to pag.267).
2. Press Filter.
The Filtered Graph Creation window opens.
3. Press the push-button relevant to the statistics which you wish to apply the filters to:
Network Event Counters, statistics of the alarms subdivided by days.
Event Frequency, statistics of the alarms subdivided by alarms.
4. Select one or more of the boxes present in the window, according to the criteria you wish to use to filter
the alarms.
The activation of each box expands the window displaying a section containing the options:
Match Date. Date/time.
From the pop-up menu, select the value:
==, to display the alarms detected at the day/time pointed out by the cursor on the right.
>=, to display the alarms detected in the days after the day/time pointed out by the cur-
sor on the right and in the day/time itself.
<=, to display the alarms detected in the days before the day/time pointed out by the
cursor on the right and in the day/time itself.
<>, to display the alarms detected in the days between the two dates/time pointed out
by the cursor on the right.
To modify the date/time pointed out by the cursor, move the indicator of the scrolling bar or
select the arrows placed next to the bar (the value is moved at steps of a quarter).
Match Source box. Logic address of the equipment.
To set the criterion press Select. Select the wished equipment from the list and press Ok.
The selected equipment is inserted in the area below the Match Source box.
It is possible to delete all the items from the list pressing Reset.
Match Object box. Physical/logical objects that compose the NE.
To set the criterion:
Open the Equipment Type menu and select the type of NE.
Open the Object menu and set the wished object.
It is possible to set only one object class at a time or all the classes at the same time selecting
the All Objects item.
Containing string box. Description of the alarm.
To set the criterion, type the wished string in the text field.
5. Press OK.
For the selected statistics, only the records that satisfy the activated criteria are displayed.
Each time the list is filtered, all the records are considered, both displayed and hidden.
When the type of displayed statistics is changed or the NMS5UX Alarm Statistics window is closed,
the possible activation of the filters is automatically removed.
The Transaction Log command displays/manages the list of the operations executed by the NMS5UX us-
ers, who have modified the configuration of the network, of the supervision system and of an equipment.
With details it is possible:
To display the list of the operations executed by the NMS5UX users (pag.305)
To save/print the list of the operations (pag.306)
To delete the operations (pag.307)
To filter the list of the operations (pag.307)
As help to the description of the command, see par. Recording modality of the operations (pag.308)
If the user profile of the user who selected the command is:
Superuser, the list points out the operations executed by the NMS5UX users of all the existing
maps.
Privileged, Advanced, Normal or Entry the list points out the operations executed by the
NMS5UX users of one's map.
In order to speed up the reading from database and not to display too much old records, at the opening
of the window only the operation executed in the last N days (default N=10 days, configurable by Su-
peruser) are displayed. This does not mean that the oldest records cannot be displayed, but that a filter
is automatically applied.
Menu
bar (1)
List of
operations
(2)
Status
bar (3)
(1) Menu:
File > Print/Save. It prints or saves to file the list of the operations.
File > Close. It closes the window.
Action > Delete Records. It deletes the operations.
Action > Refresh Info. It updates the data present in the window.
View > Set Filter. It filters the list of operations.
Help > On Usage. It opens the on-line manual.
Help > About Application. Version of the module that manages the considered functionality.
(3) Field:
xx of yy. Number of displayed records (xx) and number of total records (yy). If no filter is
active, the number of displayed records corresponds to the number of total records.
View... Activation of one or more filters.
Date and time when the window has been opened or refreshed.
Operation available only to the Superuser and to the users with privileged or advanced profile.
The list of the operations executed by the NMS5UX users records all the operations that have involved any
modification of the network configuration (for example, addition of a NE), of the configuration of the su-
pervision system (for example, addition of a user) or of the configuration of a NE (for example, change of
a parameter).
The detail of the operation is reported in Tab.13.
The operations are stored in the database of NMS5UX-B (Transaction Log table).
They remain stored for a certain number of days (which can be configured by the Superuser - by default
90 days), after which they are automatically deleted.
Also, it is possible to configure the maximum number of records in the Transaction Log table (value that
can be set by the Superuser) that can be stored.
During the day, all the operations are stored in the table (even if their number exceeds the maximum value
of records). At midnight, the number of record is checked; if this exceeds the maximum set number, the
system will delete the oldest records.
When the maximum number of records in the table is exceeded, the message Transaction Log occupation
exceeded 100% is periodically displayed warning about the critical situation. The display of the message
and the frequency with which it is displayed can be configured by the Superuser.
In any moment, it is possible:
To display the occupation status of the table Transaction Log in the platform status bar (see
pag.45).
To manually delete the operations (pag.307). It is suggested to periodically delete and/or store
to file the less meaningful records, so to avoid the saturation of the table.
Alarm Notification via e-mail (pag.312). It displays/manages the operators enabled to the
reception of the alarm notification via e-mail.
SNMP-Command Executor (pag.318). It executes series of SNMP commands stored on file.
SNMP-NE Monitoring (pag.321). It executes, for the SNMP equipment, the periodic monitoring
of parameters.
SNMP-Auto Discovery (pag.328). It manages the Auto Discovery functionality for the detec-
tion of the equipment present in the network and not managed yet by the supervision system;
the automatic creation and the connection of the discovered NE objects.
SNMP-Rmon (pag.337). It displays/manages, for the SNMP equipment, the RMON standard
(groups: Statistics, History and Alarm).
SNMP-XML Export (pag.353). It manages the export of the configuration data of the SNMP
equipment in XML format.
Superuser (pag.312)
Entry, Normal, Advanced, Privileged (pag.316)
The Alarm Notification via e-mail command displays/manages the operators enabled to the reception
of the alarm notification via e-mail.
With detail for the Superuser, it is possible:
To display the list of all the operators enabled to the reception of the alarm notification via e-
mail (pag.312)
To add an operator (pag.313)
To modify the characteristics of the operators (pag.314)
To delete an operator (pag.315)
To activate/deactivate an operator (pag.315)
To acknowledge an operator and re-enable him to receive e-mail (pag.315)
To create a filter relevant to the type of alarms whose detection must be notified to the operator
via e-mail (pag.315)
For more information on the functionality of alarm notification via e-mail go to pag.317.
To display the list of all the operators enabled to the reception of the alarm notifica-
tion via e-mail
Menu
bar (1)
Operators
list (2)
Push-buttons
bar (3)
(1) Menu:
Edit > Exit. It closes the window.
Edit > Filters. It creates a filter relevant to the type of alarms whose detection must be no-
tified to the operator via e-mail.
Edit > Refresh. It updates the information contained in the window.
Operator > Create. It adds an operator.
Operator > Modify. It modifies the characteristics of an operator.
Operator > Delete. It deletes an operator.
Alert > Clear. It acknowledges an operator, in such a way that the system stores the infor-
mation that the operator has read the e-mail and reactivates him to receive e-mail.
Help > Index. It opens the on-line manual.
(3) Push-button:
Exit. It closes the window.
Refresh. It adds the information contained in the window.
Clear Alert. It acknowledges an operator, in such a way that the system stores the infor-
mation that the operator has read the e-mail and reactivates him to receive e-mail.
To add an operator
3. Type, in the Name box, the name you wish to assign to the operator (alphanumeric string of maximum
30 characters).
It is not possible to assign the same name to two different operators. Moreover, after the creation
of the operator, the name cannot be modified.
4. Select the Active box, according to the status you wish to assign to the operator:
Active box ( ). Active operator: he receives the alarm notifications via e-mail.
Inactive box. Inactive operator: he does not receive the alarm notifications via e-mail.
5. Type, in the Password box, the access code relevant to the new operator (alphanumeric string of min-
imum 6 and maximum 21 characters).
For safety reason, an asterisk (*) is displayed for each typed character.
The name/password of the operator will be required by the system to the NMS5UX user with privi-
leged, advanced, normal or entry profile who selects the Alarm Notification via e-mail command.
The correct setting of the parameters will allow these NMS5UX users acknowledging the possible re-
ception of e-mails by the specific operator and re-enable him to the e-mail reception.
7. Set a possible filter relevant to the type of alarm, whose detection must be notified to the operator e-
mail:
a. Press Select Filter.
The Select Filter window opens.
b. Select, in the Files list, the name of the file you wish to retrieve.
The list points out the files present in the predefined directory (pointed out in the Selection box).
Modify the path, if necessary.
c. Press OK.
If you wish to create a new filter, press Filter. The Filter window opens. The modalities of filter creation
are the same described at pag.315 from step 3.
8. Type the e-mail address of the operator in the EMail box.
9. In the Secondary Operator area, set the data for the reception of the e-mail by a second operator if the
main operator does not acknowledge the reception of the mail:
Type, in the Notification delay box, the time interval (expressed in minutes) elapsed which, if
the main operator has not acknowledge the reception of the mail, this one is forwarded also to
the second operator.
Type, in the Email box, the e-mail address of the second operator.
10.Press Ok.
4. Press Ok.
4. Press Ok.
The operator is removed from the list.
To activate/deactivate an operator
4. To ACTIVATE the operator to the reception of the alarm notifications via, activate the Active box ( ).
To DEACTIVATE the operator to the reception of the alarm notifications via, deactivate the Active box.
5. Press Ok.
The new status of the operator is displayed in the Status column.
To create a filter relevant to the type of alarms whose detection must be notified to
the operator via e-mail
3. Type the name of the new filter in the Filter Name box.
6. Press OK.
In the window there are also the push-buttons:
Load.... It opens the file containing a previously saved specific filter setting.
When the push-button is selected, the SelectFilter window opens.
Select the wished file in the Files list and press OK.
Delete.... It delete the file containing a previously saved specific filter setting.
When the push-button is selected, the SelectFilter window opens.
Select the wished file in the Files list and press OK.
The Alarm Notification via e-mail command displays/manages the operators enabled to the reception
of the alarm notification via e-mail.
With detail for the user with entry, normal, advanced and privileged profile, it is possible:
To acknowledge an operator and re-enable him to receive e-mail (pag.317)
For more information on the functionality of alarm notification via e-mail go to pag.317.
The operation can be executed by the NMS5UX user only if this knows the name and the password of
the operator.
2. Type the name of the operator you wish to acknowledge in the Operator field.
3. Type the access code of the operator you wish to acknowledge in the Password field.
4. Press Ok.
If the entered data are not correct, the message Alert has been acknowledged and reactivated is dis-
played, pointing out that the operator has been acknowledged and re-enabled to receive e-mail.
The NMS5UX-B system manages the sending of e-mail after the detection of an alarm of any equipment
present in the network.
The sending of the e-mails is subordinated to the definition of the operators who must receive the e-mails
and to the setting of the sending criteria: enabling for the reception of the e-mails, type of equipment/
alarm, period when the operator is enabled to the reception of the e-mails, etc.
When an operator is enabled, at the first detection of an alarm that corresponds to the sending criteria set
for that operator, he receives an e-mail pointing out:
Equipment type Logical address
Alarm description
No more e-mail will be sent to this operator, even if new alarms raise, until when the operator himself (or
the NMS5UX Superuser) does not communicate to the system to have received the e-mail (acknowledge
of the operation) and re-enables the operator himself to receive new e-mails.
An operator can be created/modified/deleted and acknowledged by the NMS5UX Superuser (see pag.312).
The NMS5UX entry, normal, advanced or privileged user can only, knowing the name and the password of
an operator, acknowledge him in such a way that the system memorizes that the operator has read the e-
mail and re-enables him to receive e-mails (pag.316).
The SNMP-Command Executor command executes series of SNMP commands stored on file.
With details it is possible:
To execute series of SNMP commands stored on file (pag.318)
To display the content of a file of SNMP commands (pag.319)
To display the file of scheduled SNMP commands (pag.320)
If you select an equipment in the map and then the considered command, it is possible that the system
displays the message No Command available for the selected equipment. This means that ones supervi-
sion system, for the type of selected equipment, is not provided with files containing sequences of SNMP
commands. SIAE MICROELETTRONICA provides, on demand, files containing specific sequences of SNMP
commands.
2. If the wished file is not in the directory specified in the Directory box, type the new path in the box or
use the Change Directory push-button.
4. Set the possible parameters, displayed in the and Command File Description area, on the choice of the
file.
The list of parameters changes according to the selected file. Some file do not need the setting of the
parameters.
5. Select the option:
Immediate, if you wish that the sequence of SNMP commands present in the file is immediately
executed.
Scheduled, if you wish that the sequence of SNMP commands present in the file is executed lat-
er.
On the choice of the push-button, the boxes for the setting of the data (Day, Month, Year) and
of the time (Hour, Min), where you wish to execute the sequence of the commands, are dis-
played.
Menu
bar (1)
Path where
files are stored
List of
available
files
Parameters
to set for the
execution of
the SNMP
commands
relevant to
the file selected
in the FILES
area
Operations
executed
during the
execution of
the selected
file (2)
Fig.49 notes
(1) Menu:
File > Close. It closes the window.
Edit > View Command File. It displays the content of a file of SNMP commands.
2. If the wished file is not in the directory specified in the Directory box, type the new path in the box or
use the Change Directory push-button.
3. To delete a file, select the relevant record and then press Delete Command.
The file is deleted from the list
4. To display the progress of the executed operation by a file, select the relevant record and then press
View Detailed Information.
The View File - window opens displaying the list of the displayed operation.
The SNMP-NE Monitoring command allows assigning a set of parameters to monitor periodically to a
SNMP equipment. The SNMP equipment - parameters to monitor is defined measure.
With details it is possible:
To display the list of the measures (pag.321)
To assign the parameters to monitor to an equipment (create a measure) (pag.322)
To display the characteristics of a measure (pag.323)
To delete a measure (pag.323)
To activate a measure (pag.323)
To deactivate a measure (pag.323)
To display the results of a measure (pag.324)
To save the results of a measure (pag.324)
To display the results of a measure stored into a file (pag.325)
To save the results of a measure stored into a file (pag.325)
To delete a file (pag.325)
Menu
bar (1)
List of
the set
measures
(2)
Status
bar (3)
(1) Menu:
File > Load Graphics. It displays, in graph format, the results of a measure saved to file.
File > Load Exported File. It displays, in table format, the results of a measure saved to file.
File > Delete File. It deletes the files where the results of the measures are stored.
File > Close. It closes the window.
Options > Add Measure. It assigns the parameters to monitor to an equipment (creation of
a measure).
Options > Delete Measure. It deletes a measure.
Options > Start Measure. It activates a measure.
Options > Stop Measure. It deactivates a measure.
Options > Measure Properties. It displays the measure properties.
Options > View Graphics. It displays, in graph format, the results of a measure.
Options > View Exported File. It displays, in table format, the results of a measure.
(3) If, before opening the NE Monitoring window, an SNMP equipment has been selected, the logical
address of the selected equipment is displayed in the status bar of the window.
If the check-box is active, the window will list only the measures relevant to the selected equipment.
If the check-box is inactive, the window will list all the measures defined by the user.
1. It is possible to set the SNMP equipment which you wish to assign the parameters to monitor to, se-
lecting it in the UX Map Manager window.
Otherwise, it will be possible to set the equipment during the procedure of measure creation.
4. Set the equipment, which you wish to assign the parameters to monitor to, in one of the following ways:
Select the NE Logical Address option and type the logical address of the wished NE in the box
below.
Select the NE IP-Address option and type the IP address of the wished NE in the box below.
If, at step 1, a specific NE has been selected in the box, the IP address of this equipment is automati-
cally pointed out.
5. Type, in the Timeout box, the time interval, expressed in seconds, between a reading of the value of
each parameter and the next one.
The user can select predefined groups of parameters. The SIAE MICROELETTRONICA provides, on
demand, files with specific groups of parameters.
7. Press Ok.
The measure is added to the list.
To delete a measure
To activate a measure
To deactivate a measure
3. Select the measure for which you wish to display the results.
1. To display:
Only the measures relevant to a given SNMP equipment, select the wished equipment in the UX
Map Manager window.
All the measures relevant to all the SNMP equipment, starts the procedure from step 2.
3. Select the measure for which you wish to save the results.
4. Press OK.
5. If at step 2 has been selected the command:
File > Load Graphics.
The <parameters group name> - <NE logical address> window opens. Fig.51 shows an example.
File > Load Exported File.
The Preview:... window opens. Fig.52 shows an example.
4. Press OK.
8. Press OK.
To delete a file
4. Press OK.
The file is deleted from the disk of the machine.
Menu
bar (1)
Display of
the result
in graphic
format (2)
Monitored
parameter
Parameter
value
Parameters
present in the
specific
group of
measures (3)
Fig.51 notes
(1) Menu:
File > Save as. It saves the results of the measure to a file which the user can assign the
wished name and path to.
File > Close. It closes the window.
View > Zoom Minutes > ... It displays the results subdivided by intervals of 5, 15 or 30 minutes.
View > Zoom Hours > ... It displays the results subdivided by intervals of 1, 3, 6 or 12 hours.
View > Zoom Days > ... It displays the results subdivided by intervals of 1, 2, 5, 15 or 30 days.
View > Zoom 100%. It displays the results subdivided by the time interval stored in the file
until the selection of the command.
Into the View menu the asterisk next to a value points out the current setting.
(2) For each parameter selected in the area below, a graph is displayed.
Menu
bar (1)
Display of
the result in
table format
Date/time when
the parameter
value has
been recorded
Monitored
parameters
present in the
specific group
of measures
Fig.52 notes
(1) Menu:
File > Save as. It saves the results of the measure to a file which the user can assign the
wished name and path to.
File > Close. It closes the window.
NE Monitoring functionality
The NE Monitoring functionality allows assigning to an SNMP equipment a group of parameters to monitor.
The SNMP equipment - parameters to monitor is defined measure.
For a single equipment, it is possible to define more measures.
The user can assign to an equipment only PREDEFINED groups of parameters. SIAE MICROELETTRO-
NICA provides, on demand, files with specific groups of parameters.
After having created the measure (pag.322), it is necessary to start it (activation of the monitoring of the
parameters - pag.323). Periodically, the system will read the parameters and will record the results until
when the measure is not interrupted (pag.323).
At the start of a measure, a file is automatically created where are recorded the results of the measure
itself. At next start, a new file will be automatically created.
The system stores the file in a predefined directory (default /opt/nms5ux/tools/nms5NeMonitoring/data)
and assigns a name formed by the following parameters <name of the parameters group>-<NE logical
address>-<yearmonthday>_<hourminuteseconds>.csv.
For each measure, a maximum of N files are kept in memory (default N=10, configurable by Superuser).
The system allows, moreover, the contemporary start of N files (default N=10, configurable by Superuser).
The results of the measures can be displayed in graphic or table format (pag.324/pag.325).
Moreover, it is possible to save the results of the measures to a file which the user can assign the wished
name and path (pag.324/pag.325).
The command SNMP-Auto Discovery allows managing the Auto Discovery functionality for the detection
of the equipment present in the network and not managed yet by the supervision system, the automatic
creation and connection of the discovered NE objects.
With details it is possible:
To verify the status and the configuration of Auto Discovery (Network Scan and/or NE Wake Up
modality) (pag.328)
To set the execution parameters and activate the Network Scan modality (pag.330)
To deactivate the Network Scan modality (pag.332)
To set the execution parameters and activate the NE Wake Up modality (pag.332)
To deactivate the NE Wake Up modality (pag.333)
To display the list of the equipment detected by Auto Discovery (Auto Discovery table) (pag.333)
To search an equipment in the Auto Discovery table (pag.335)
To delete one or more equipment from the Auto Discovery table (pag.335)
To create manually the object of an equipment present in the Auto Discovery table (pag.336)
For more info about the Auto Discovery functionality ago to pag.104.
To verify the status and the configuration of Auto Discovery (Network Scan
and/or NE Wake Up modality)
Menu bar
(1)
Activation
status of
NE Wake Up
mode (2)
Activation status
and configuration
parameters of
Network Scan
mode (3)
Configuration
parameters
of the Network
Scan and NE
Wake Up modes
(4)
Immediate
apply status
of the new
configuration
(5) Push-buttons
(6)
Fig.53 notes
(1) Menu:
File > Close. It close the window.
Manager > Scan Configuration. It displays the Scan Configuration window.
Command not meaningful for the considered window.
Manager > Network Element Captured. It displays the Network Element Captured window.
Help > On Usage. It opens the on-line manual.
Help > About Application. Version of the module that manages the considered functionality.
(3) Parameter/area:
Range IP Addresses and Specific IP Addresses. Respectively groups of IP addresses and sin-
gle IP addresses cyclically scanned by the Network Scan modality.
The presence or not of values in the two areas causes even the activation or not of the Net-
work Scan modality. In detail, the Network Scan modality is:
Active, when at least one value is present in the Range IP Addresses or Specific IP
Addresses areas
(4) Parameter:
Action When Found. Type of action NMS5UX-B must execute at the detection of a new equip-
ment:
Manage. The system automatically inserts the equipment in the Auto Discovery table,
creates the relevant NE symbol in the map and connects it.
Create Only. The system automatically inserts the equipment in the Auto Discovery
table and creates the relevant NE symbol in the map.
Log Only. The system automatically inserts the equipment in the Auto Discovery ta-
ble.
Selected Map. Map where the equipment symbol must possibly be created.
Selected Container. Name of the container where you wish to create the possible NE object.
Remember that the NE object is not created directly in the container but in the path <con-
tainer set by the user> / <year> / <year/month> / <day/month/year when the object is
created>
Fig.20 shows an example.
(6) Push-button:
Save as Active Conf. Saves the current setting of the execution parameters of Auto Dis-
covery as new active configuration.
Save As. Saves the current setting of the execution parameters of Auto Discovery to a file.
Load Active Conf. Updates the data present in the window loading those stored as current
configuration.
Load. Opens the file containing a specific setting of the execution parameters of Auto Dis-
covery previously saved.
To set the execution parameters and activate the Network Scan modality
a. Type, in the First IP and Last IP boxes, the IP addresses determining the range of values which
will be scanned each cycle.
a. Type the IP address which will be scanned each cycle into the IP box.
The value is displayed in the Specific IP Addresses area.
b. Press Add.
c. Repeat the steps a. and b. to insert more IP addresses.
It is possible to delete, from the Specific IP Addresses area, a single item pressing the Delete push-
button after having selected the item, or all the items at the same time pressing Delete All.
It is possible to set the scanning takes place once at a day in the following way:
a. Set the value One Time At Day in the Scan Repetition box.
b. Set the hours:minutes, within 24 hours, when you wish the Auto Discovery scanning takes place
in the Start Time box.
It is possible to set the scanning takes place continuously in the following way:
5. Type the number of IP addresses (numeric value between 1 and 100) you wish to scan at the same
time in the IP Managed Simultaneously.
6. Type the interval (expressed in seconds) between the simultaneous scanning of a group of IP addresses
and the next one in the Timeout Between Simultaneous IP box.
7. Set, in the Action When Found box, the type of action NMS5UX-B must execute at the detection of a
new equipment:
Manage. The system automatically inserts the equipment in the Auto Discovery table, creates
the relevant NE symbol in the map and connects it.
Create Only. The system automatically inserts the equipment in the Auto Discovery table and
creates the relevant NE symbol in the map.
Log Only. The system automatically inserts the equipment in the Auto Discovery table.
8. Set, in the Selected Map box, the map where the equipment symbol must be possibly created:
a. Press ...
The Select a Map window opens.
b. Select the map from the list.
c. Press Ok.
9. Type, in the Selected Container box, the name of the container where you wish to create the possible
NE object.
If the container is not present in the set map, when the NE object is created, even the container will
be automatically created.
Remember that the NE object is not created directly in the container but in the path <container set by
the user> / <year> / <year/month> / <day/month/year when the object is created>
Fig.20 shows an example.
10.If you wish the Network Scan modality is activated:
Immediately, activate the Apply Configuration Immediately option and press Save as Active
Conf.
At the end of the scanning process in progress, press Save as Active Conf.
The parameters Action When Found, Selected Map and Selected Container are in common with the
NE Wake UP modality. A change to them affects even the execution of this modality.
4. Set, in the Action When Found box, the type of action NMS5UX-B must execute at the detection of a
new equipment:
Manage. The system automatically inserts the equipment in the Auto Discovery table, creates
the relevant NE symbol in the map and connects it.
Create Only. The system automatically inserts the equipment in the Auto Discovery table and
creates the relevant NE symbol in the map.
Log Only. The system automatically inserts the equipment in the Auto Discovery table.
5. Set, in the Selected Map box, the map where the equipment symbol must be possibly created:
a. Press ...
The Select a Map window opens.
b. Select the map from the list.
c. Press Ok.
6. Type, in the Selected Container box, the name of the container where you wish to create the possible
NE object.
If the container is not present in the set map, when the NE object is created, even the container will
be automatically created.
Remember that the NE object is not created directly in the container but in the path <container set by
the user> / <year> / <year/month> / <day/month/year when the object is created>
Fig.20 shows an example.
The parameters Action When Found, Selected Map and Selected Container are in common with the Net-
work Scan modality. A change to them affects even the execution of this modality.
5. Set the path and type, in the Selection box, the name of the file (with .cfg extension) where you wish
to save the Auto Discovery configuration.
6. Press Ok.
3. Press Load.
The filesb_popup window opens.
4. Select the file (with .cfg extension) where the wished Auto Discovery configuration is stored.
5. Press Ok.
In the Scan Configuration window, the configuration stored in the file is displayed.
To display the list of the equipment detected by Auto Discovery (Auto Dis-
covery table)
Menu bar
(1)
Characteristics
of the selected
equipment (3)
Fig.54 notes
(1) Menu:
File > Close. It close the window.
Manager > Scan Configuration. It displays the Scan Configuration window.
Manager > Network Element Captured. It displays the Network Element Captured window.
Command not meaningful for the considered window.
Help > On Usage. It opens the on-line manual.
Help > About Application. Version of the module that manages the considered functionality.
The update of the Auto Discovery table is dynamic. This means that the detection of a new equip-
ment is immediately pointed out in the window, if this is open.
(3) If an equipment, for which the action of creation/connection of the symbol (column Action, value
Create or Create and Connect) has been executed, the system points out in the filed:
NSAP. NSAP address (GOSIP) of the equipment.
Value available and meaningful only for equipment inserted in an OSI network.
Create Date. Date/time when the corresponding NE object has been created.
Connection Date. Date/time when the corresponding NE object has been connected.
Value available and meaningful only for created and connected NE objects (column Action,
value Create and Connect).
Map. Map where the corresponding NE object has been created.
Path. Path (containers) where the corresponding NE object has been created.
(4) Push-button:
Find. Searches one or more equipment in the list.
Reload. Updates the data present in the window.
Delete. Deletes the selected equipment.
Create. Creates the NE object of an equipment for which no action has been executed yet
(column Action, value Done).
3. Type, in the text field next to the Find push-button, an alphanumeric string (case sensitive) corre-
sponding to the value or to part of the value present in the ID, IP Address, Customer ID, Type, Action
or Status column relevant to the equipment you wish to search.
4. Press Find.
The list highlights the first line matching the set searching criterion.
If the list contains more equipment matching the search criterion, the Find push-button is replaced by
the Next push-button.
4. Press Delete.
The equipment are removed from the list.
Operation available only for equipment detected by Auto Discovery for which no action has been exe-
cuted yet (column Action, value Done - see Fig.54).
3. Select the equipment for which you wish to create the relevant NE object.
4. Press Create.
During the operation, the Status column points out the wording In progress.
At the end of the operation, the Action column points out the wording Create.
The NE object is created in the following path:
<map set by the user*> / <container set by the user*> / <year> / <year/month> / <day/
month/year when the object is created>
The SNMP-Rmon command manages, for the SNMP equipment, the RMON standard (groups: Statistics,
History and Alarm).
With details it is possible:
Statistics group
To verify the statistics of an Ethernet port of a SNMP equipment (RMON statistics) (pag.337)
To activate an Ethernet port for the count of the RMON statistics (pag.339)
To deactivate an Ethernet port from the count of the RMON statistics (pag.340)
To capture the RMON statistics of an Ethernet port in a specific instant (pag.340)
To save the RMON statistics of an Ethernet port captured in a specific instant to file (pag.341)
History group
To display the history of the RMON statistics of an Ethernet port (pag.342)
To activate an Ethernet port for the count of the history of the RMON statistics (pag.345)
To deactivate an Ethernet port from the count of the history of the RMON statistics (pag.345)
To save the history of the RMON statistics of an Ethernet port (pag.345)
Alarms group
To verify the enabling and the criteria for the activation/deactivation of alarms relevant to a
counter (RMON statistics) (pag.346)
To enable and define the criteria for the activation/deactivation of an alarm relevant to a counter
(RMON statistics) (pag.346)
To disable an alarm relevant to a counter (RMON statistics) (pag.347)
The operations are available only for SNMP equipment in connected status (which LCT/WEB LCT is NOT
connected to in Configuration modality) where the equipment software supports the RMON standard.
For more info on the implementation of the RMON standard in the SNMP equipment managed by
NMS5UX-B go to pag.348.
2. In the Network Elements area, select the equipment that manages the wished Ethernet ports.
The Interface Definition... area defines the ports currently active for the count of the RMON statistics.
If the wished port is not active, it can be activated (see pag.339)
3. In the Interface Definition... area, select the port which you wish to verify the counters for.
For each counter, the relevant value is reported in the Value column.
The description of the counters changes according to the type of selected equipment (see pag.351).
In order to refresh the data press Refresh or activate the Auto Refresh box (the data are automatically
update every second).
Menu
bar (1)
List of
SNMP NEs
(2)
LAN ports
of the selected
equipment
currently
active for
the count of
the RMON
statistics (3)
Alarms enabled
for the
selected port
(4)
Values of the
counters
relevant
to the selected
LAN port
(5)
Data
refresh
mode (6)
Fig.55 notes
(1) Menu:
File > Close. It closes the window.
Help > About Application. It opens the manual.
(2) For each equipment, the relevant logic address is pointed out.
It is possible to insert one or more equipment selecting the relevant symbols in the map and press-
ing Add From Map or to delete all the equipment in the list pressing Clear All.
For the NE objects of ALplus Node and ALCplus2 Node type in the list, the detail of the equipment
of the nodal system is pointed out. This equipment is identified by the logic address:
<node name>.X, where X can assume the value A, B or C (ALplus Node object).
(3) The number/type of Ethernet ports changes depending on the equipment type.
For each port, is pointed out in the column:
Index. Value identifying univocally the port in the table of the RMON statistics of the data-
base.
Interface. Name of the Ethernet port.
Owner. User who has activated the port. User means the user used for the connection to the
equipment, then nms5ux user.
(5) For each counter, the relevant value is pointed out in the Value column. The wording n/a points out
that the value is not available.
The description of the counter changes depending on the type of selected equipment (see pag.351).
(6) In order to refresh the data press Refresh or activate the Auto Refresh box (the data are automat-
ically update every second).
2. In the Network Elements area, select the equipment that manages the wished Ethernet ports.
The Interface Definition... area defines the ports currently active for the count of the RMON statistics.
3. In the Interface Definition... area press the right mouse button and select Add.
The Nms5ux Statistics Enable window opens.
4. Select the Ethernet port you wish to activate in the Interface box.
5. Press Add.
The port is added to the Interface Definition... area.
If the selected port is already active, the message Unable to Perform Operation. Selected Port Already
Used is displayed.
The port will remain active until the user will deactivate it (see pag.340).
2. In the Network Elements area, select the equipment that manages the wished Ethernet ports.
The Interface Definition... area defines the ports currently active for the count of the RMON statistics.
3. In the Interface Definition... area, select the port you wish to activate.
6. Set, in the Interval (1-60min) box, the time interval (number between 1 and 60 minutes) at the end
of which the values of the counters must be displayed in the Captured Statistics window.
7. Press Start.
The status of the capture operation changes from Ready to Running.
To stop the operation press Stop.
Once elapsed the set time interval, the status of the capture operation changes from Running to Com-
plete and the Captured Statistics window displays the values of the counters in the instant when the
time interval is elapsed.
Equipment
logical adddress
Ethernet
port
Status of
the captured
operation (1)
Counters
values
(2)
Fig.56 notes
(1) Wording:
Ready. Operation not in progress.
Running. Operation in progress.
Complete. Capture operation complete.
Aborted. Operation stopped by the user.
(2) The description of the counters changes depending on the type of selected NE (see pag.351).
1. Capture the RMON statistics of an Ethernet port in a specific instant (see pag.340).
3. Set the path and type, in the Selection box, the name of the file (with extension .txt) where you wish
to save the information.
4. Press Ok.
The file is saved in text format and can be opened by any text editor.
2. In the Addresses area, select the equipment that manages the wished Ethernet ports.
The area below defines the ports currently active for the count of the history of the RMON statistics.
If the wished port is not active, it can be activated (see pag.345)
3. Select the port, press the right mouse button and select Graph.
The graph of the statistics history is displayed.
By default, the starting display mode is the following:
Packets box. Counters displayed in the graph: Packets. The graph displays the counters whose
measure unit is the packet: Packets, Multicasts, Broadcasts, CRC Errors, Undersize, Oversize,
Fragments, Collision, Jabber, Drop Events.
To hide a counter, deactivate the relevant box in the Graph Summary area. To display it again
in the graph, re-activate the relevant box.
Each counter is identified by a color corresponding to the color of the relevant bar (or line) in
the graph.
To modify the counters represented in the graph set, in the Packets box, the Utilization option
(percentile estimate of the real bandwidth used) or Octets (total number of octets).
The description of the counters change depending on the type of selected equipment (see
pag.351).
Grap Type box. Type of graph: Histogram. Each bar within the observation period has a color
corresponding to the color of the relevant counter pointed out in the Graph Summary area.
To modify the type of graph set, in the Graph Type box, the Line option: the values are repre-
sented by lines; even in this case, the color of the lines represents the counter which the line
itself refers to.
Data type box. Value of the represented counter: Mean of the values sampled within the time
interval represented on abscissa axis (Average option).
To modify the parameter set, in the Graph Type box, the Measured option (value represented
on the abscissa axis at the last sampling of the time interval) or Maximum (maximum value,
represented on the abscissa axis, sampled within the pointed out time interval).
Abscissa axis. Time interval: Days (date format month/day/year). The graph displays the last
30 days. If the port is enabled by less than 30 days, only the available days are displayed. The
parameter can be configured by the Superuser.
A double click on the area representing one day in the graph displays the statistics of the
counters of the selected day, subdivided in 1-hour period. Pressing the central mouse button,
you return to the previous view.
A double click on the area representing one hour in the graph displays the statistics of the
counters of the selected day/hour, subdivided in 1-minute period. Pressing the central mouse
button, you return to the previous view.
The display of the message No data available points out that no information is available for the
selected time interval.
Ordinate axis. Measure unit of the counter: number of packets.
The measure unit changes depending on the type of parameters represented in the graph (see
setting of the Packets box in figure).
List of the
SNMP NEs
(4)
Values of the
counters
relevant
to the selected
LAN port
(5)
LAN ports,
of the current
equipment,
currently active
for the count of
the history
of the
RMON
statistics (6)
Fig.57 notes
(1) Menu:
File > Close. It closes the window.
Help > About Application. It opens the manual.
(2) The first box points out the counters represented in the graph:
Packets. The graph displays the values of the following parameters (if enabled in the Graph
Summary area): Packets, Multicasts, Broadcasts, CRC Errors, Undersize, Oversize, Frag-
ments, Collision, Jabber, Drop Events.
Utilization. The graph displays the value of the Utilization parameter only.
Octets. The graph displays the value of the Octets parameter only.
The Graph Type box points out the type of graph:
Histogram. Histogram graph.
Line. Line graph.
The Data type box points out the value of the displayed counter:
Measured. Value, at the last sampling instant of the time interval, represented on the ab-
scissa axis.
(3) The graph can be represented by histograms or by lines (setting of the Graph Type parameter).
The graph does not represent all the counters at the same time. They have been subdivided de-
pending on their own measure unit (setting of the Packets parameter).
To hide a counter, deactivate the relevant box in the Graph Summary area. To display it again in
the graph, re-activate the relevant box.
Each counter is identified by a color corresponding to the color of the relevant bar (or line) in the
graph.
At the first display of the data relevant to a window, the last 30 last days are represented. If the
port is enabled from less than 30 days, only the available days are displayed. The parameter can
be configured by the Superuser.
A double click on the area representing one day in the graph displays the statistics of the counters
of the selected day, subdivided in 1-hour period. Pressing the central mouse button, you return to
the previous view.
A double click on the area representing one hour in the graph displays the statistics of the counters
of the selected day/hour, subdivided in 1-minute period. Pressing the central mouse button, you
return to the previous view.
It is possible to display, into a dynamic window, the detail of the counters relevant to the time in-
terval where the pointer is placed, keeping pressed the right mouse button.
(6) The number/type of Ethernet ports changes depending on the equipment type.
For each port, is pointed out in the column:
Index. Value identifying univocally the port in the table of the history of the RMON statistics
of the database.
Port. Name of the Ethernet port.
Interval. Sampling interval used to collect the data of the statistics history. Value set to 60
seconds.
Samples. Total number of samples to collect. The equipment stores these data in a rotation
buffer, where the new information in input overwrites the old one. Value set to 240 sam-
plings, which allow storing 4 hours in the equipment.
Owner. User who has activated the port. User means the user used for the connection to the
equipment, then nms5ux user.
Status. Status of the entry in the table of the history of the RMON statistics of the database.
2. In the Addresses area, select the equipment that manages the wished Ethernet ports.
The area below defines the ports currently active for the count of the history of the RMON statistics.
3. In the area where the ports are listed, press the right mouse button and select Add Rmon.
The New Control Entry window opens.
4. Select, in the Port box, the Ethernet port you wish to activate.
The remnant parameters present in the window cannot be modified. For their description, refer to
Fig.57.
5. Press Apply.
The port is added to the list.
The port will remain active until the user will not deactivate it (see pag.345).
To deactivate an Ethernet port from the count of the history of the RMON sta-
tistics
2. In the Addresses area, select the equipment that manages the wished Ethernet ports.
The area below defines the ports currently active for the count of the history of the RMON statistics.
1. Select the Tools > SNMP-Rmon > NMS5UX History View command.
The Rmon History View window opens (Fig.57).
3. Press .
The SelectExportFile window opens.
5. Press Ok.
The files are saved in text format and can be opened using any text editor.
The data displayed in the window are saved to file.
2. In the Network Elements area, select the equipment which manages the wished Ethernet ports.
In the Interface Definition... area, the ports currently active for the count of the RMON statistics are
displayed.
If the wished port is not active, it is possible to activate it (see pag.339)
3. In the Interface Definition... area, select the wished port.
In the Alarm Definition... area, the alarms currently enabled for the selected port are displayed. Fig.55
shows an example.
More alarms can be defined for the same counter. Each alarm will be identified by a different value of
Index (Fig.55).
2. In the Network Elements area, select the equipment which manages the wished Ethernet ports.
In the Interface Definition... area, the ports currently active for the count of the RMON statistics are
displayed.
If the wished port is not active, it is possible to activate it (see pag.339)
3. In the Interface Definition... area, select the wished port.
7. Set, in the Measure Type box, the mode to compare the counter value with the threshold:
Absolute Value. The value reported in the last sampling instant of the selected counter will be
directly compared with the set (rising and falling) thresholds.
Delta Value. The value compared with the set (rising and falling) threshold will be the difference
between the counter value at the beginning of the interval and the value at the end of the in-
terval.
8. Set, in the Startup box, the alarm activation mode used for the first comparison between the counter
value and the thresholds set after that the alarm has been enabled by the user: Rising, Falling and Ris-
ing or Falling.
The description of the values available for this parameter and its interaction with the parameters Alarm
Rising Threshold and Alarm Falling Threshold is reported at pag.349.
9. Set, in the Alarm Interval (minutes) box, the interval (in minutes) after which the data are compared
with the thresholds.
10.Set, in the Alarm Rising Threshold box, the rising threshold used for the comparison of the counter val-
ues with the selected counter: when the value of the compared counter is greater than or equal to this
threshold and the value of the previous comparison is lower, an alarm is generated.
For the first comparison, after that the alarm has been enabled by the user, the alarm activation is
affected by the setting of the Startup parameter. The description of the interaction among the param-
eters Startup, Alarm Rising Threshold and Alarm Falling Threshold is reported at pag.349.
11.Set, in the Alarm Falling Threshold box, the lower threshold used for the comparison of the values of
the selected counter: when the value of the compared counter is lower than or equal to this threshold
and the value of the previous comparison is greater, an alarm is generated.
For the first comparison, after that the alarm has been enabled by the user, the alarm activation is
affected by the setting of the Startup parameter. The description of the interaction among the param-
eters Startup, Alarm Rising Threshold and Alarm Falling Threshold is reported at pag.349.
12.Press Ok.
The alarm is added to the Alarm Definition... area.
The Alarm Statistics Creation window remains open. To close it, press Cancel.
The alarm will remain enabled until when it is not deactivated by the user (see pag.347).
2. In the Network Elements area, select the equipment which manages the wished Ethernet ports.
In the Interface Definition... area, the ports currently active for the count of the RMON statistics are
displayed.
4. In the Alarm Definition... area, select the alarm you wish to disable.
RMON Standard
RMON (Remote Monitoring) is a standard whose function is providing a set of services of statistics count,
monitoring and alarm report with reference to the activity of a LAN network.
These services can be accessed through the SNMP protocol and defined in terms of MIB (Management In-
formation Base) group described in the document RFC2819 - Remote Network Monitoring Management In-
formation Base, which must be read for any further detail.
The RMON standard is based on two components: an agent (RMON probe) and a client (remote manage-
ment station).
The agent saves the data within its own RMON tables present on the network devices (equipment, routers,
etc.). The RMON probes can see only the traffic flowing through themselves and therefore are located on
each (internal/external) port of the Ethernet switch of the device to monitor.
The remote management station communicates with the RMON agent using the SNMP protocol to obtain
and correlate the RMON data. Generally, the station is equipped with an interface (graphic or textual) which
allows the display and the analysis of the collected RMON data.
The Rmon functionality available in NMS5UX-B allows monitoring the status of the Ethernet interface
present on the SNMP equipment in compliance with the RMON standard.
With reference to what depicted in the previous paragraph, the Rmon functionality acts as client which,
through the commands present in the NMS5UX-B graphic interface, allows the analysis and the manage-
ment of the data collected by the probes present on each (internal/external) port of the Ethernet switch of
the SNMP equipment.
The probes collect the statistic data, which are stored in the RMON table of the equipment. In any moment,
it is possible to activate (and deactivate) an Ethernet port for the storing of these data by NMS5UX-B.
Currently, the SNMP equipment managed by the NMS5UX-B system implement the following RMON MIB
groups and, as a consequence, the Rmon functionality offers, through the graphic interface, the following
functionality:
Statistics measured by the RMON probes for each monitored Ethernet port (RMON MIB group:
Statistics).
History of the statistics for each monitored Ethernet port (RMON MIB group: History).
Management of the alarms associated to the counters of the RMON statistics (RMON MIB group:
Alarm).
The Rmon functionality can display to the user some statistic information (counters), which allows evalu-
ating the traffic development in input and in output for each single port of the Ethernet switch of the equip-
ment (see pag.337).
To display the counters of a port, it is necessary to activate the port (see pag.339). This port will remain
active until when the user does not deactivate it (see pag.340).
Moreover it is possible to capture the values of the counters at the end of a time interval set by the user
(see pag.340) and then to save them to file (see pag.341).
The description of the counters changes depending on the type of selected equipment (see pag.351).
The update of the data can be carried out automatically (activating the Auto Refresh option) or manually
(pressing the Refresh push-button).
The Rmon functionality can present the time development (history) of the statistics relevant to the
counters in input/output at level of single port of the Ethernet switch of the equipment (see pag.342).
At equipment level, the statistics history stores the value of the counters of the Ethernet counter each 60
seconds (sampling interval). The equipment stores these data into a rotation buffer where, when full, the
new information overwrites the old ones (value set to 240 samples which allow storing 4 hours in the equip-
ment).
In order to store in the NMS5UX-B database and display the statistics history of a port, it is necessary to
activate the port (see pag.345). This port will remain active until when the user does not deactivate it (see
pag.345).
At the activation of the port, the supervision system starts storing the data relevant to the statistics and
makes them available to the user, in form of graph (histogram or line), subdivided by single Ethernet port
of each single equipment.
For each port, it is possible to display, at the same, time, the counters having the same measure unit
(packets: Packets, Multicasts, Broadcasts, CRC Errors, Undersize, Oversize, Fragments, Collision, Jabber,
Drop Events; Octets: Octets; Usage percentage: Utilization).
The user can choose the type of value of the represented counter: Average (mean of the values sampled
within a time interval), Measured (value at the last sampling of a time interval) or Maximum (maximum
value sample within a time interval).
The values of the counters are represented grouped by time intervals (minutes, hour, days). In the graph,
the last 30 days from the activation of the port can be displayed.
The description of the counters changes depending on the type of selected equipment (see pag.351).
When a port is active, the data are displayed in the relevant window (Fig.57) only when the selected
equipment is in connected status and the local management program is not connected in Configuration
modality to the equipment.
By means of the Rmon functionality, one or more alarms can be associated to each counter, of each single
port of the Ethernet switch of a SNMP equipment.
The activation of the alarm is caused by the exceeding of a (rising or falling) threshold of absolute values
or at relative differences.
In detail, at the definition of the alarm by the user (see pag.346), statistic samples of the counters are
periodically collected from the RMON probe.
These samples are compared with some previously set thresholds. If the monitored counter exceeds a
threshold, an alarm is generated and pointed out in the current alarm table and in the alarm history of
NMS5UX-B.
The description of the alarm in the list of the current alarms and in the alarm history is RMON Alarm <in-
dex>, where <index> is the value which univocally points out the alarm in the RMON alarm table of the
database (Fig.55).
In order to limit the generation of alarms, an hysteresis mechanisms is implemented which generates an
alarm each time a threshold is exceeded in the proper direction and does not generate other alarms until
when the opposite threshold is exceeded as described in Fig.58.
Rising
Threshold Trend of the
counter
Falling value
Threshold in time
Sampling Time
interval (1)
Fig.58 notes
(1) The sampling intervals are not synchronized with the instant when the alarm is defined by the user,
but refer to the time of the solar day (00.00, 01.00, 02.00, etc).
For example, if an alarm is defined at 11.40 and the sampling interval defined by the user is 30
minutes, the first usable sampling interval of the counter will be 12.00...12.30.
(2) At the expiry of a sampling interval, depending on the type of mode set by the user for the com-
parison with the thresholds, as value of the counter is taken:
The value assumed by the counter at the end of the sampling interval (comparison method
Absolute).
The difference between the value of the counter at the end of the sampling interval and the
value of the counter at the beginning of the sampling interval (comparison method Delta).
For the SNMP equipment managed by NMS5UX-B, when the user enables an alarm, the system starts the
activities to monitor the sampled value with respect to the thresholds. The result of this activity will be,
possibly, the activation or the deactivation of the associated alarm according to the following modalities.
If the threshold AlarmRisingThreshold is set to a value greater than the threshold AlarmFallingThreshold),
the alarm is activated if the sampled value is greater than or equal to the threshold AlarmRisingThreshold.
The alarm is deactivated when the sampled value becomes lower than or equal to the threshold AlarmFal-
lingThreshold.
For the first comparison at the end of the first usable sampling interval, after that the alarm has been en-
abled by the user, the activation of the alarm is affected by the setting of the Startup parameter. In detail,
if the parameter Startup is set to the value:
Rising or Rising or Falling and the value of the compared value is greater than or equal to the
Rising threshold, the alarm is generated.
Falling and the value of the compared value is greater than or equal to the Rising threshold, the
alarm is not generated.
What just described is valid only for the first comparison after the enabling of the alarm. For the next com-
parison, the rule described above applies.
Example. Suppose that, for a given alarm, we have set the parameter AlarmRisingThreshold=100 and the
parameter AlarmFallingThreshold=50. If the Startup parameter has the value:
Rising. At the expiry of the first usable sampling interval, the sampled value is 120: the alarm
is immediately activated.
Falling. At the expiry of the first usable sampling interval, the sampled value is 120: the alarm
is not activated.
At the end of the next interval, the constraint has not meaning anymore; therefore, if in that
moment the value is greater than the threshold Rising yet, the alarm is immediately generated.
Rising or Falling. At the expiry of the first usable sampling interval, the sampled value is 120:
the alarm is immediately activated.
What just said is valid only for the first comparison after the enabling of the alarm. For the next compari-
sons, the general rule described above applies.
Example. Suppose that, for an alarm, we have set the parameter AlarmRisingThreshold=150 and the pa-
rameter AlarmFallingThreshold=200. If the parameter Startup has value:
Rising. At the expiry of the first usable sampling interval, the sampled value is 120: the alarm
is immediately activated.
Falling. At the end of the first usable sampling interval, the sampled value is 120: the alarm is
not activated.
At the end of the expiry of the next interval, the constraint has not meaning anymore; therefore,
if in that moment the value is lower than the threshold Rising yet, the alarm is immediately gen-
erated.
Rising or Falling. At the end of the expiry of the first usable sampling interval, the sampled value
is 120: the alarm is immediately activated.
Keeping in mind what described in this chapter, consider however that the operating logic of the alarms
on the SNMP equipment managed by NMS5UX-B foresees that the alarms (SNMP traps) are generated only
on the alarm transitions, that is from Off to On and, then, from On to Off, and that the initial status of the
alarms is however Off.
Therefore, the exceeding of a threshold AlarmFallingThreshold will have, as consequence, the generation
of an alarm only if the event takes place after a transition on the corresponding threshold AlarmRisingTh-
reshold or the combination of the values of the thresholds is such that the exceeding of the threshold
AlarmFallingThreshold corresponds to the activation of the alarm.
The description of the counters changes according to the type of selected equipment.
This description is the same reported for the counters of the packets/bytes in input/output from an Ether-
net port (LAN Statistics) contained in the user manual of the Manager application relevant to each single
equipment type.
The only difference is the name of the counter which, in some cases, change from the RMON counters with
respect to the LAN Statistics counters.
Tab.14 reports the correspondence of the names for the Ethernet RMON counters - Statistics counters.
Tab.15 reports the correspondence of the names for the Ethernet RMON counters - History counters.
The counter Utilization is meaningful only as RMON (History) counter and has the following description:
the best estimate of the mean physical layer network utilization on this interface during this sampling in-
terval, in hundredths of a percent.
The command SNMP-XML Export manages the export of the configuration data of SNMP equipment in
XML format (function XML Export).
In detail, it is possible:
Periodical saving of data (definition of cronjobs which automatically creates the XML files)
To display the active cronjobs (pag.355)
To create a cronjob (pag.356)
To delete one or more cronjob (pag.356)
Management of XML, Log and HTML files
To display the list of the XML files present in a given directory (pag.356)
To display the list of the Log files relevant to the creation of XML files (pag.357)
To display the list of the HTML files obtained from the conversion of the XML files (pag.358)
To convert a XML file to a HTML file (pag.358)
To display the content of a XML, Log or HTML file (pag.358)
To delete one or more XML, Log or HTML files (pag.360)
To send email with attached one or more XML, Log or HTML files (pag.360)
The function XML Export is optional and available only for SNMP equipment of type ALFO and series ALS
(AL, ALC, ALS, ALS-C, ALplus, ALCplus, ALplus2, ALCplus2).
1. Select the command Tools > SNMP-XML Export > SNMP-XML Export Mgmt.
The XML Configuration Data Export window is displayed.
3. Define the equipment which the saving of the configuration is required for:
All the SNMP equipment (which support the function XML Export) managed by NMS5UX-B, select
the command Action > Export > All Network.
The equipment selected in the window XML Configuration Data Export:
Select the equipment.
A maximum of 100 equipment can be selected.
Select the command Action > Export > Selected NE.
A group of equipment:
Select the command View > Set Filter.
The Selected Filter window is displayed.
Select the boxes relevant to the criteria you wish to use to display a specific group of NEs
in the XML Configuration Data Export window:
4. Type, in the Selection box, the name of the xml file where the data must be exported.
The system suggests, as path, the default directory. Change the path, if necessary.
5. Press Ok.
The XML file saves the complete configuration only of the equipment in connected status.
In the file, this equipment is listed in alphabetical order with respect to the equipment type and, within
the equipment type, with respect to the logical address of the NE.
Menu
bar (1)
Equipment
list (2)
Status
bar (3)
Fig.59 notes
(1) Menu:
File > Close. It closes the window.
Action > Load Equipment. It displays all the SNMP equipment supporting the function XML
Export.
Action > Export > All Network. It saves into a single file (in XML format) the complete con-
figuration of all the SNMP equipment in connected status, managed by the system and sup-
porting the function XML Export.
Action > Export > Selected NE. It saves into a single file (in XML format) the complete con-
figuration of all the SNMP equipment in connected status, selected from a list.
Action > Export > Filtered. It saves into a single file (in XML format) the complete configu-
ration of all the equipment in connected status, present in the filtered list.
Action > Schedule Backup. It displays the currently active cronjobs.
View > Set Filter. It filters the list according to specific criteria.
Help > About Application. Version of the module for the management of the considered func-
tion.
1. Select the command Tools > SNMP-XML Export > SNMP-XML Export Mgmt.
The XML Configuration Data Export window is displayed.
Menu
bar (1)
Crojob
list (2)
Fig.60 notes
(1) Menu:
Actions > Add > Daily. It creates a cronjob with daily frequency.
Actions > Add > Weekly. It creates a cronjob with weekly frequency.
Actions > Add > Monthly. It creates a cronjob with monthly frequency.
Actions > Delete. It deletes one or more cronjobs.
Actions > Quit. It closes the window.
1. Select the command Tools > SNMP-XML Export > SNMP-XML Export Mgmt.
The XML Configuration Data Export window is displayed.
4. Set, in the Time (hh:mm) box, the hour when you wish the cronjob is executed using the following
format hour (0-23) : minute (0-59).
5. Set, in the Export type box, the saving type you wish to execute:
Full Backup. At each saving, the system generates a single XML file which contains the complete
configuration of all the SNMP equipment (supporting the function XML Export) which, at the mo-
ment of the saving, is in connected status (see pag.362).
Differential Backup. A XML file is generated for each SNMP equipment (supporting the function
XML Export) which, at the moment of the saving, is in connected status (see pag.363).
Incremental Backup. A single XML file is generated with all the SNMP equipment (supporting the
function XML Export) which, at the moment of the saving, is in connected status (see pag.363).
6. The Export Directory box points out the default directory for the saving of the file.
To modify the path, type the new value or press (the Directory Selection window is opened) and
select the new directory.
7. Press OK.
The cronjob is inserted within a list.
More information about the cronjobs and the files created automatically are reported at pag.361.
1. Select the command Tools > SNMP-XML Export > SNMP-XML Export Mgmt.
The XML Configuration Data Export window is displayed.
1. Select the command Tools > SNMP-XML Export > SNMP-XML File Mgmt.
The NMS5UX Data Export File Manager window is displayed.
4. Press OK.
The NMS5UX Data Export File Manager window is renamed into XML Files where are currently displayed
all the files with extension xml present in the selected directory and into the relevant subdirectories, if
present.
Fig.61 reports an example.
Menu
bar (1)
Files
list (2)
Fig.61 notes
(1) Menu:
File > List Log Files. It displays the list of the Log files relevant to the creation of XML files.
File > List XML Files. It displays the list of the XML files present in a given directory.
File > List HTML Files. It displays the list of the HTML files obtained from the conversion of
XML files.
File > Open... It displays the content of a file (.log, .xml or .html).
File > Open. It displays the content of the selected file.
File > Delete. It deletes the selected files.
File > Convert to HTML. It converts the selected XML file to a HTML file.
File > Send email. It sends an email with the selected files in attachment.
File > Close. It closes the window.
Help > About Application. Version of the module for the management of the considered func-
tion.
To display the list of the Log files relevant to the creation of XML files
1. Select the command Tools > SNMP-XML Export > SNMP-XML File Mgmt.
The NMS5UX Data Export File Manager window is displayed.
1. Select the command Tools > SNMP-XML Export > SNMP-XML File Mgmt.
The NMS5UX Data Export File Manager window is displayed.
4. Press OK.
The NMS5UX Data Export File Manager window is renamed into HTML Files where are displayed all the
files with html extension present in the selected directory and in the relevant subdirectories, if present.
The description of the HTML Files window is the same reported in Fig.61 except for the command File
> Convert to HTML which is not meaningful and available in the considered context.
1. Select the command Tools > SNMP-XML Export > XML File Mgmt.
The NMS5UX Data Export File Manager window is displayed.
7. Set, in the Stylesheet File box, the path/name of the file you wish to use as style sheet for the conver-
sion (file XSL - eXtensible Stylesheet Language).
It is possible to type the path and the name of the file or press (the Directory Selection window is
opened) and select the file among those available.
8. The Export Directory box points out the default directory for the saving of the converted files.
To change the path, type the new value or press (the Directory Selection window is opened) and
select the new directory.
9. Press Convert!.
For each XML file, a html file is created in the set directory with the same name of the source file. For
example, the file ALplus2_205.xml is converted into the file ALplus2_205.html.
1. Select the command Tools > SNMP-XML Export > SNMP-XML File Mgmt.
The NMS5UX Data Export File Manager window is displayed.
1. Select the command Tools > SNMP-XML Export > SNMP-XML File Mgmt.
The NMS5UX Data Export File Manager window is displayed.
In order to send the files, it is necessary that the system administrator has properly configured the mail
server.
1. Select the command Tools > SNMP-XML Export > SNMP-XML File Mgmt.
8. Set the modality to send the files activating/deactivating the options Use tarball file and/or Use gzip
Compression according to what pointed out here below.
Inactive Inactive A mail is sent for each file present in the area File(s) to Send. Each
file keeps its original format (.log, .xml or .html)
Active Inactive A single mail is sent with attached a file of type tarball (.tar) which
contains all the files present in the area File(s) to Send
Inactive Active A mail is sent for each file present in the area File(s) to Send. Each
file is compressed with method gzip (.gz)
Active Active A single mail is sent with attached a file of type tarball compressed
with method gzip (.gz)
9. Press Send.
The function XML Export allows saving the complete configuration of the SNMP equipment managed by
NMS5UX-B into a file in XML (eXtensible Markup Language) format.
In the XML file is saved the complete equipment configuration which consists in the following data:
Logical address
IP address (LAN and PPP ports) and Routing Table
Equipment configuration:
General parameters: radio protection, IDU type, etc.
Radio parameters.
Switch Ethernet parameters.
The saving of the equipment data into a XML file can be manually executed by the user (creation of a single
XML file) or automatically by the system (creation of periodical XML files through the definition of cronjobs).
Manual saving
Automatic saving
The function XML Export manages the periodic saving in XML format of the configuration of all the SNMP
equipment managed by the NMS5UX-B system and which support the function XML Export.
The periodic saving is managed and automatically executed by the supervision system.
The only operation required to the user is to define the modality used to execute the periodic saving
through the creation of a cronjob.
Cronjob
The cronjobs are commands executed by a crontab, that is a system command which allows scheduling
the operations to repeat in time.
For the function XML Export, the parameters for the creation of a cronjob are:
Daily. The user must define the time within the 24 hours when the cronjob must be ex-
ecuted.
For example, if the value 23:45 is set as time, the cronjob will be executed everyday at
23:45.
Weekly. The user must define the day of the week (monday, tuesday, etc) and the time
when the cronjob must be executed.
For example, if the value Sun is set for the day and 4:22 is set for the time, the cronjob
will be executed every sunday at 4:22.
Monthly. The user must define the day of the month (1, 2, etc) and the time when the
cronjob must be executed.
For example, if the value 1 is set for the day and 4:42 is set for the time, the cronjob will
be executed every sunday at 4:42 of the first day of every month.
Type of saving you wish to execute:
Full Backup. At each saving a single XML file is generated containing the complete con-
figuration of all the equipment.
For the XML containing the data of more equipment, the data will be listed in the file in alpha-
betical order with respect to the equipment type and, within the equipment type, with respect
to the logical address of the NE.
* In files of type Differential Backup and Incremental Backup, the differences will be highlighted
by the Status field which, depending on the type of executed change, will assume the value:
Modified. Change of configuration
Not present. Deletion of a NE
Present. Addition of a NE
Once the cronjob is defined, it will start saving the files. To stop the operation, it is necessary to delete the
cronjob.
All the XML files automatically generated by cronjobs are saved in the directory set by the user for the
relevant cronjob. Default: /opt/nms5ux/tools/nmsConfigDataExport/Backup.
The file is automatically assigned a name which, depending on the type of saving set for the relevant cron-
job, has the following format:
Type Full Backup. The name FullBackup.xml is assigned to every generated file.
Type Differential Backup. The name format is: NMS5_<hostname>_<ID NE>.xml
Type Incremental Backup.
For the first generated file, after the creation of the relevant cronjob, the name format is:
NMS5_<hostname>_Full_<date>_<time>.xml
For the files generated later, after the detection of changes in the equipment configuration, the
name format is: NMS5_<hostname>_Incr_<date>_<time>.xml
where <hostname> points out the name of the server where NMS5UX-B is running.
<date> and <time> correspond to the moment when the XML file has been saved and are pointed out in
the following format: YYMMDD_HHMM (for example 20100509_1310 means 9 may 2010 time 13:10).
When a XML file is created (manually or automatically), the relevant log file is automatically created where
are stored the actions executed by the user or by the cronjob.
The function XML Export is provided with a series of commands for the management of XML files which
allow to:
The Legacy-Network Alarm Hysteresis command displays/sets the hysteresis parameters that charac-
terizes the ringing alarms of the Legacy equipment.
With details it is possible:
To display the value of the hysteresis parameters of the fleeting alarms (pag.366)
To modify the hysteresis parameters of the fleeting alarms (pag.367)
The command is available only if the modules for the management of the Legacy equipment have been
installed.
The hysteresis parameters are common for all the Legacy equipment (network global parameters).
Such parameters are periodically forwarded from the central part toward the peripheral one through a
broadcast message.
Observation
time
expressed
by means
of minutes
Number of
transitions
during the
t time
range
3. Press Apply (it implements the new settings and it does not close the window) or Close (it closes the
window and does not execute the operation).
The Help push-button opens the on-line manual.
The SNMP-Network Severity Code command displays/manages the network severity level associated
to the alarms of a SNMP equipment type.
With details it is possible:
To verify the network severity of the alarms relevant to a specific SNMP equipment type
(pag.368)
To modify the network severity of the alarms relevant to a specific SNMP equipment type
(pag.369)
Menu
bar (1)
Type of NEs
managed by
NMS5UX-B
system
Alarms that
characterize
the type of
selected NE
(2)
(1) Menu:
File > Close. It closes the window.
Action > Apply Changes. It confirms the modification to the level of alarm severity.
Help > On Usage. It opens the on-line manual.
The modification of the severity level associated to an alarm is COMMON to all the NEs of the same type.
4. Select the Severity box and choose the new severity level from the list.
The value of the Category, Trap ID and Event Name parameters cannot be modified.
Pressing Default, the current setting is restored.
5. Press OK.
The new severity level is pointed out in the New column of the Siae Events Manager window.
The SNMP-Equipment Severity Code command displays/manages the alarm status, the sending status
of the traps and the local severity level of the alarms of a SNMP equipment.
With details it is possible:
To verify the alarms characteristics (status, sending status of the trap, local severity) of a SNMP
equipment (pag.370)
To enable/disable the alarms and to send of the traps and/or to modify the local severity of the
alarms of a SNMP equipment (pag.371)
To filter the alarms list (pag.372)
The command is available only if a single SNMP equipment in connected status has been selected, ex-
cept for the ELFO, SDH N+1, FAMxc, ALplus Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCplus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
To verify the alarms characteristics (status, sending status of the trap, local
severity) of a SNMP equipment
The alarms of the user inputs, which have a different severity management (see pag.124), are not
present in the list.
Menu
bar (1)
The selected
push-button
points out the
criteria used
to list the
alarms (2)
List of
alarms (3)
Status
bar (4)
(1) Menu:
File > Exit. It closes the window.
Action > View/Modify Severity. It displays and modifies the enabling status of alarm/trap
sending and/or the severity level associated to the selected alarm.
Action > Refresh Info. It updates the information contained in the window.
View > Filter. It filters the list according to specific criteria.
Help > On Usage. It opens the on-line manual.
Help > About Application. Version of the module that manages the considered functionality.
(2) Option:
Description, sorts the list according to the name of the alarm.
Object, sorts the list according to the object which the alarm is associated to.
Status, sorts the list according to the status of the alarms and of the traps.
The information present in the window corresponds to the status of the alarm in the moment when
the command or the refresh is executed.
(4) Field:
xx of yy. Number of displayed records (xx) and number of total records (yy). If they are not
active filters, the number of displayed records corresponds to the total number of records.
Customer Id. Logic address of the selected NE.
Date and time when the window has been opened or updated.
To enable/disable the alarms and to send of the traps and/or to modify the
local severity of the alarms of a SNMP equipment
3. Double click on the wished alarm or select the alarm and then the Action > View/Modify Severity
command.
The View/Modify Severity Code window opens, where it is pointed out in the box/area:
Alarm Description. Name of the alarm.
Status. Status of the alarm and of the trap sending by the NE to the system. If active the option:
Enabled, the alarm and the sending of trap is enabled.
Trap Disabled, the sending of trap is disabled.
Alarm Disabled, the alarm is disabled.
Severity. Severity level associated to the alarm.
The label (NMS5UX-B default) points out the default setting associated to that alarm by the su-
pervision system.
4. To modify the enabling status of alarm/trap sending and/or the severity level, select the push-button
relevant to the wished value respectively in the Status and/or Severity area.
5. Press Modify.
The possible modification of the enabling status of alarm/trap sending is pointed out in the Equipment
Severity Code window.
4. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the Equipment Severity Code window only the records that satisfy the activated
criteria.
Each time the list is filtered, all the records are considered, both the displayed and the hidden ones.
In the window, there are also the Clear (it clears the activation of the filters and displays the activation
of the filters and displays the complete list), Cancel (it closes the window and does not execute the
operation) and Help (it opens the on-line manual) push-button.
When the Equipment Severity Code window is closed, the possible activation of the filters is auto-
matically cleared.
Superuser (pag.373)
Entry, Normal, Advanced, Privileged (pag.377)
Only if, for ones system, the function Manual login to the UX Map Manager window (pag.61) is active,
use the procedure depicted at pag.376 for the creation of a NMS5UX user.
To display the list of the NMS5UX users present in all the existing maps
Menu
bar (1)
List of
users
(2)
Fig.68 notes
(1) Menu:
Edit > Exit. It closes the window.
Edit > Create Map. It creates a new map.
Users > Create. It creates a new NMS5UX user.
3. Type in the Map Name box the name of the new map (alphanumeric string of minimum 1 and maximum
20 characters).
4. Press OK.
3. Select, in the Operation System Users list, the Unix user whom you wish to associate the new NMS5UX
user.
For each Unix user, it is possible to associate only one NMS5UX user.
The list displays only the Unix users whom no NMS5UX user has been associated yet.
4. The name of the selected Unix user is automatically set in the Login box.
The value cannot be modified.
5. From the Level list, select the push-button relevant to the profile you wish to associate to the new user.
The Superuser option is not available, as it is not possible to create a second user with this profile.
7. Define an expiry date for the NMS5UX user (account) in the Expiration data boxes.
A default date is automatically displayed; it is possible to modify it typing the day (Day box), the month
(Month box) and the year (Year box) or it is possible not to associate any date activating the Life time
check box.
The default setting can be modified by the Superuser.
8. Select from the Map list, the map which you wish to associate the user to.
All the available maps are listed.
The name of the selected map is displayed in the Map associate box.
If the user you are creating has Advanced or Privileged profile, it is possible to create a new map. To
execute the operation, it is sufficient to type in the Map associate text field the name of the map (al-
phanumeric string of minimum 1 and maximum 20 characters)
9. Press OK.
The user is added to the list of the User Management window.
The limit of users who can be created is determined by one's codeword.
5. Press OK.
3. Select, in the Operation System Users list, the Unix user whom you wish to associate the new NMS5UX
user.
For each Unix user, it is possible to associate only one NMS5UX user.
The list displays only the Unix users whom no NMS5UX user has been associated yet.
4. Type, in the Login box, the name of the new user.
The name of the Unix user, selected in the previous step, is automatically displayed; it is possible to
modify it typing in the box an alphanumeric string of minimum 1 and maximum 20 characters.
5. From the Level list, select the push-button relevant to the profile you wish to associate to the new user.
The Superuser option is not available, as it is not possible to create a second user with this profile.
7. Define an expiry date for the NMS5UX user (account) in the Expiration data boxes.
A default date is automatically displayed; it is possible to modify it typing the day (Day box), the month
(Month box) and the year (Year box) or it is possible not to associate any date activating the Life time
check box.
The default setting can be modified by the Superuser.
8. In the Write box (Password area) type the access code you wish to assign to the new user (alphanu-
meric string of minimum 6 and maximum 21 characters).
10.Select from the Map list, the map which you wish to associate the user to.
All the available maps are listed.
The name of the selected map is displayed in the Map associate box.
If the user you are creating has Advanced or Privileged profile, it is possible to create a new map. To
execute the operation, it is sufficient to type in the Map associate text field the name of the map (al-
phanumeric string of minimum 1 and maximum 20 characters)
11.Press OK.
The user is added to the list of the User Management window.
The limit of users who can be created is determined by one's codeword.
With details for the user with entry, normal, advanced and privileged profile it is possible:
To display the characteristics of the user who opened the map (pag.377)
The following operation is available only if for ones system the function of Manual login to the UX Map
Manager window (pag.61) is active.
In this condition, the password can be changed because the password of the Unix user is not automatically
assigned to the NMS5UX user.
To modify the password associated to ones NMS5UX users (pag.378)
Menu
bar (1)
User
characteristics
(2)
Fig.69 notes
(1) Menu:
Edit > Exit. It closes the window.
Users > Modify. It modifies the password of the NMS5UX user.
Help > Index. It opens the on-line manual.
(2) Column:
Name. Username of the NMS5UX user.
Level. Profile of the NMS5UX user: Privileged, Advanced, Normal, Entry (pag.57)
Map name. Name of the map.
User. Unix user whom the NMS5UX user is associated to.
Expiration time. Expiry date/time of the NMS5UX user (account).
The Not expired label points out that no expiry date is associated to the user.
Int. Enabling of the user to use the RAN (Remote Access NMS5UX) application. In detail, if
the symbol * (asterisk) is:
Present, the user is enabled.
Absent, the user is not enabled.
Ring/VLAN. Enabling of the user to open the Ring Manager window (pag.50) and/or VLAN
Manager Map window (pag.51). In detail, if the symbol * (asterisk) is:
Operation available only if for ones system the function Manual login to the UX Map Manager window
(pag.61) is active.
4. In the Write box (Password area) type the new access code (alphanumeric string of minimum 6 and
maximum 21 characters).
6. Press OK.
* The Entry, Normal, Advanced or Privileged user cannot force the user logout or the application closure.
The NMS5UX Logged Users command displays the list of the NMS5UX users connected to the supervision
system and the list of active application (browser, manager, etc.).
With details it is possible:
To display the list of the NMS5UX users who have a map open (pag.379)
To require the disconnection (logout) of a NMS5UX user (pag.380)
To force the disconnection (logout) of a NMS5UX user (pag.381)
To send a message to one or all the NMS5UX users (pag.381)
To filter the NMS5UX users list (pag.381)
To display the list of the active NMS5UX-B application (pag.382)
To require the closure of a NMS5UX-B application (pag.383)
To force the closure of a NMS5UX-B application (pag.383)
To filter the NMS5UX-B applications list (pag.383)
To display the list of the NMS5UX users who have a map open
Menu
bar (1)
The selected
option points
out the type
of the data
displayed in
the table (2)
List of the
users (3)
Number of
displayed records
with respect to
the total number
Fig.70 notes
(1) Menu:
File > Close. It closes the window.
Action > Request Logout. It requires the disconnection of the selected user.
Action > Force Logout. It forces the disconnection of the selected user in Running status.
(2) The list (users and applications) are not displayed contemporarily in the window. They are displayed
alternatively according to the selected option:
View Logged Users. In the windows there is the users list.
View Running Application. In the windows there is the applications list.
6. Type the message in the available text area (alphanumeric string of maximum 150 characters).
4. Press OK (executes the command and closes the window) or Apply (executes the command and does
not close the window).
The system displays in the Nms5ux: Logged Users window only the records that satisfy the activated
criteria.
Each time the list is filtered, all the records are considered, both the displayed and the hidden ones.
Menu
bar (1)
The selected
option points
out the type
of the data
displayed in
the table (2)
List of the
application (3)
Number of
displayed records
with respect to
the total number
Fig.71 notes
(1) Menu:
File > Close. It closes the window.
Action > Request Logout. Not available/meaningful when the application list is selected.
Action > Force Logout. Not available/meaningful when the application list is selected.
Action > Send Message. Not available/meaningful when the application list is selected.
Action > Request Exit. It requires the closure of the selected application.
Action > Forced Exit. It forces the closure of the selected application.
Action > Refresh Info. It updates the information displayed in the window.
View > Set Filter. It filters the list according to specific criteria.
Help > On Usage. It opens the on-line manual.
(2) The list (users and applications) are not displayed contemporarily in the window. They are displayed
alternatively according to the selected option:
View Logged Users. In the windows there is the users list.
View Running Application. In the windows there is the applications list.
4. Press OK (executes the command and closes the window) or Apply (executes the command and does
not close the window).
The system displays in the Nms5ux: Logged Users window only the records that satisfy the activated
criteria.
Each time the list is filtered, all the records are considered, both the displayed and the hidden ones.
In the window there are also the Clear (it clears the activation of the filters and displays the complete
list) and Cancel (it closes the window and does not executes the operation) push-buttons.
When the Nms5ux: Logged Users window is closed, the possible activation of filters is automatically
cleared.
The SNMP-LCT Equipment Users command manages/displays the LCT users list of a SNMP equipment.
With details it is possible:
To display the LCT users list of a SNMP equipment (pag.385)
To add a new LCT user (pag.386)
To modify the characteristics of the LCT users (pag.387)
To delete a LCT user (pag.387)
The command is available only if it has been selected a single SNMP equipment in connected status,
except for the ELFO, SDH N+1, FAMxc, ALFO, ALplus Node and ALCplus2 Node.
For NE objects of ALplus Node or ALCplus2 Node type, the command is present in the nodal window
(pag.48/pag.49).
List of LCT
users (1)
Push-buttons
bar (2)
Type and
logical
address
of the
selected NE
Fig.72 notes
(1) For each user, it is reported in the column:
User Name. Name of the LCT user.
Profile. Profile of the LCT user:
Read only. This user can check the parameters but it can not forward commands or
execute changing to the equipment configuration.
Read and Write. This user can check the parameters and execute maintenance oper-
ations (MAN OP).
The System and NMS5UX users are not pointed out into the LCT User Manager window.
Timeout. Status of the Timeout option. Wording:
No timeout. The option is disabled: the user is not automatically disconnected after a
given period of time.
<number>. The option is enabled: the user, if the program does not execute opera-
tion, is disconnected after the indicated period of time.
(2) Push-button:
Add User. It adds a LCT user.
Modify User. It modifies the characteristics of the selected LCT user.
Remove User. It deletes a LCT user.
Refresh. It updates the information contained in the window.
Close. It closes the window.
It is possible to define in each list a maximum of 4 users for each profile (totally maximum 12 users).
4. Type in the User box the name of the user (alphanumeric string of minimum 1 and maximum 8 char-
acters).
It is not possible to assign the same name to two different users present in the same list. Further-
more, the name of the user, once assigned, cannot be modified later.
5. Type in the Password box the access code of the user (alphanumeric string of minimum 1 and maximum
8 characters).
6. Type again in the Confirm Password box the access code of the user.
8. In the Profile area, select the option relevant to the profile you wish to assign to the user:
Read only. This user can check the parameters but it can not forward commands or execute
changing to the equipment configuration.
Read and Write. This user can check the parameters and execute maintenance operations (MAN
OP).
Station Operator. This user can as check the parameters as send commands or execute changes
to the equipment configuration except for the following operations: modifying the remote equip-
ment list, the user list, aligning the date/time of the equipment, force the login and the logout
of an user and all those operations available only to the System user (or NMS5UX).
9. Press Add.
6. Press Modify.
The users list is a list of users that can be connected and ask for the login to the equipment.
If a user is not present into the users list memorized into the controller on an equipment, such an user will
not be able to connect and/or to execute the login of that equipment.
With the exception of the System and NMS5UX users, all the other users of the users list relevant to an
equipment have to be set by the NMS5UX-B system (see pag.386), the SCT/LMT or WEB LCT applications.
Each equipment (managed by the WEB LCT or SCT/LMT), is equipped with two predefined users:
SYSTEM. User of the WEB LCT or SCT/LMT application with the following features:
User name > System (unchangeable parameter).
Timeout* > No Timeout (changeable parameter).
Profile > System (unchangeable parameter)
Password > Siaemicr (default) (changeable parameter)
The System user is single one for every equipment and he can not be deleted.
NMS5UX. User of the NMS5UX-B system, with the following features:
User name > NMS5UX (unchangeable parameter).
Timeout* > No Timeout (changeable parameter).
Profile > System (unchangeable parameter)
Password > Predefined (changeable parameter)
The NMS5UX user can not be deleted.
The password and the timeout of the predefined users can be changed only with the local management
programs (SCT/LMT, WEB LCT).
* Timeout. Time period when, if the program does not execute operations, its connection is automatically
stopped. The program manages a polling process to verify the presence of the LCT-equipment connection.
If the equipment does not answer to the polling for the set period (timeout), the user is disconnected and,
as consequence, also the equipment is disconnected.
The SNMP-LCT Logged Users command displays the list of the users (LCT and NMS5UX) connected to a
SNMP equipment.
With details it is possible:
To display the list of the users (LCT and NMS5UX) connected to a SNMP equipment (pag.388)
To force the disconnection (logout) of one user (pag.389)
The command is available only if it has been selected a single SNMP equipment in connected status,
except for the ELFO, SDH N+1, FAMxc, ALplus Node and ALCplus2 Node.
For the NEs of ALplus Node and ALCplus2 Node type, the command is present in the nodal window (pag.48/
pag.49).
For more info about the users (LCT and NMS5UX) go to pag.389
To display the list of the users (LCT and NMS5UX) connected to a SNMP
equipment
Menu
bar (1)
List of LCT
users (2)
Fig.73 notes
The information present in the table corresponds to the characteristics of the users connected to
the equipment when the command is selected or the refresh is executed.
(2) Menu:
File > Exit. It closes the window.
Action > Refresh Info. It updates the information contained in the window.
Action > Force Logout. It forces the disconnection of the selected user.
Help > On Usage. It opens the on-line manual.
Help > About Application. Version of the module that manages the considered functionality.
If the logout of a NMS5UX user is forced, the supervision system provides to automatically restore the
connection of the user.
It is possible to force the disconnection of an user even by means of the commands present in the equip-
ment window.
LCT user
User connected to the equipment via the SCT/LMT or WEB LCT management program.
NMS5UX user
User connected to the equipment via NMS5UX-B system (see pag.52).
All the NMS5UX users who connect to an equipment, independently from their username/profile by which
are known by the supervision system, are seen by the equipment controller as users with username
NMS5UX and profile System.
The SNMP-Remote Element Table command manages/displays the remote equipment list of an SNMP
equipment.
With details it is possible:
To display the remote equipment list of a SNMP equipment (pag.390)
To add a station to the remote equipment list (pag.391)
To rename a station of the remote equipment list (pag.392)
To delete a station from the remote equipment list (pag.392)
To add an equipment to the remote equipment list (pag.392)
To add more equipment at the same type to the remote equipment list (pag.394)
To modify the characteristics of an equipment of the remote equipment list (pag.395)
To delete an equipment from the remote equipment list (pag.396)
To move an equipment within the remote equipment list (pag.396)
To save to a file the remote equipment list (pag.397)
To restore from file the remote equipment list (pag.397)
The command is available only if it has been selected a single SNMP equipment in connected status,
except for the ELFO, SDH N+1, FAMxc, ALplus Node and ALCplus2 Node.
For the NEs of ALplus Node or ALCplus2 Node type, the command is present in the nodal window (pag.48/
pag.49).
The ALFO equipment automatically generates the remote equipment list inserting all the equipment be-
longing to the same radio link. Then, for this equipment, the remote equipment list can be displayed but
not modified.
Menu
bar (1)
Station (2)
Equipment
belonging
to the
station (3)
(1) Menu:
File > Load from file. It restores the remote equipment list from file.
File > Save to file. It saves the remote equipment list to file.
File > Close. It closes the window.
Edit > Add > Station. It adds a station.
Edit > Add > Single Element. It adds an equipment.
Edit > Add > Multiple Element. It adds more equipment at the same time.
Edit > Remove > Station. It deletes the station.
Edit > Remove > Element. It deletes an equipment.
Edit > Modify > Station. It modifies the name of the station.
Edit > Modify > Element. It modifies the characteristics of an equipment.
Edit > Exchange > Before. It moves an equipment over the previous one.
Edit > Exchange > After. It moves an equipment under the next one.
Edit > Move to station. It moves an equipment from a station to another one.
Help > About Application. Version of the module that manages the considered functionality.
(2) For each station, the Station/... column reports the name of the station.
No particular meaning is given to the station; it is simply introduced to help the user in the locali-
zation of the equipment.
4. Type, in the text field, the name you wish to assign to the station (alphanumeric string of minimum 1
and maximum 11 characters).
It is not possible to assign the same name to two different stations. Moreover, a number or a blank
cannot be used as first character of the name.
5. Press Ok.
The new station is added at the bottom of the list of already existing station.
5. Type, in the text field, the new name (alphanumeric string of minimum 1 and maximum 11 characters).
It is not possible to assign the same name to two different stations. Moreover, a number or a blank
cannot be used as first character of the name.
6. Press Ok.
The name of the station is modified.
7. Press Apply and then confirm.
The list is stored in the controller of the equipment
The deletion of the station causes also the deletion of all the equipment associated to it.
4. Select the Edit > Remove > Station command and confirm.
The station is deleted.
3. Select the station which you wish to associate the equipment to.
An equipment can be associated only to a single station.
It is not possible to create in the same list (even if in different stations) two equipment with the
same IP Address.
6. In the Element Type area, select the option relevant to the type of element you wish to insert:
Managed by SCT. Equipment managed by the SCT/LMT or WEB LCT program.
Remote link. Equipment managed by the SCT/LMT or WEB LCT program that constitutes the
equipment placed on the other end of the radio connection with respect to the local equipment
(equipment which the user has required the connection to).
Element Manager/Remote Node. This option has a several meanings according to the type of
equipment you wish to insert:
ALplus equipment (Nodal Matrix) belonging to a remote ALplus node.
In this case, it will not be necessary to insert in the remote equipment list all the element
of the remote node but, inserting only one element and identifying it with the Remote
Node type, the connection with all the elements of the remote node will be activated at
the connection with the considered equipment. An example is reported to pag.398.
ALCplus2 equipment belonging to a remote ALCplus2 node.
In this case, it will not be necessary to insert in the remote equipment list all the element
of the remote node but, inserting only one element and identifying it with the Remote
Node type, the connection with all the elements of the remote node will be activated at
the connection with the considered equipment. An example is reported to pag.399.
All the types of equipment, except for the above mentioned one.
Element Manager of the equipment (IP address of the machine where the NMS5UX-B sys-
tem resides).
Not Managed. Element not managed by the SCT/LMT or WEB LCT program. This option can be
used to insert into the remote equipment list some information as for instance the coupling be-
tween the IP address and the NSAP (Gosip) one of an equipment inserted into an OSI network.
7. Only if the equipment is inserted into an OSI network, set the NSAP (Gosip) address executing the fol-
lowing procedure:
a. Activate the Gosip Address box.
b. To change the part of System ID of the NSAP (Gosip) Address, press Settings.
The Settings window opens.
c. Type into the boxes the value of the 6 bytes that compose System ID
d. Press OK
e. To change the default part of the NSAP (Gosip) Address, press Setup Default.
The Gosip Default Option window opens.
f. To change the AFI, IDI, Ver, Auth, Reserved parameters, type, into the relevant boxes, the value
of the corresponding byte/s.
g. To change the Domain parameter, choose the arrow placed on the side of the box and select the
desired value from the list.
To add a value to the list:
Press Add.
The Domain Settings window opens.
Into the Label box, type a name for the domain under examination.
Into the Hex value boxes, type the values of the bytes that represent the domain.
Press OK.
To remove a value from the list:
Select the value to be removed.
Press Remove.
h. To change the Area parameter, choose the arrow placed on the side of the box and select the
desired value from the list.
To add or to remove a value from the list, execute the same procedures already pointed out for
the Domain parameter.
8. Press OK.
Under the selected station, a record named Equipment <progressive number> is displayed, with the
characteristics of the new equipment.
9. Press Apply and then confirm.
The list is stored in the controller of the equipment.
To add more equipment at the same time to the remote equipment list
3. Select the station which you wish to associate the equipment to.
An equipment can be associated only to a single station.
4. Select the Edit > Add > Multiple Element command.
The Add Multiple Element window opens.
The Apply to station field displays the station which the new equipment will be associated to.
Under the field, all the equipment managed by NMS5UX-B are listed. For each equipment, the IP ad-
dress and the logic address are listed in the order.
The list can be filtered:
a. Selecting the Filter push-button
The Load Equipment window opens.
b. Select one or more boxes, according to the criteria you wish to use.
The activation of each box expands the window displaying a section containing the options:
Match Logical Address box. Logic address of the NE.
To set the criteria, type the address of the NE in the text field.
Match IP Address box. IP address of the NE.
To set the criteria, type the IP Address of the NE in the text field.
Match connection status box. Status of the connection between the NE and NMS5UX-B.
To set the criterion, select the push-button relevant to the wished status.
Match equipment type box. Equipment type.
To set the criterion, select the push-button relevant to the type of wished equipment.
c. Press OK (executes the command and closes the window) or Apply (executes the command and
does not close the window).
The table displays only the records that satisfy the activated criteria.
In the window there are also the Clear (it clears the activation of the filters and displays the
complete list) and Cancel (it closes the window and does not executes the operation) push-but-
tons.
5. Select the equipment you wish to add to the remote equipment list.
6. In the Element Type area, select the option relevant to the type of elements you wish to insert:
Managed by SCT. Equipment managed by the SCT/LMT or WEB LCT program.
Remote link. Equipment managed by the SCT/LMT or WEB LCT program that constitutes the
equipment placed on the other end of the radio connection with respect to the local equipment
(equipment which the user has required the connection to).
Element Manager/Remote Node. This option has a several meanings according to the type of
equipment you wish to insert:
ALplus equipment (Nodal Matrix) belonging to a remote ALplus node.
In this case, it will not be necessary to insert in the remote equipment list all the element
of the remote node but, inserting only one element and identifying it with the Remote
Node type, the connection with all the elements of the remote node will be activated at
the connection with the considered equipment. An example is reported to pag.398.
ALCplus2 equipment belonging to a remote ALCplus2 node.
7. Press OK (executes the command and closes the window) or Apply (executes the command and does
not close the window).
Under the selected station, a record named Equipment <progressive number> is displayed, for each
new equipment.
5. To modify the IP address, type the new value in the IP Address box.
It is not possible to assign to the equipment an IP Address already present in the list.
6. To change the element type, select the desired option into the Element Type area:
Managed by SCT. Equipment managed by the SCT/LMT or WEB LCT program.
Remote link. Equipment managed by the SCT/LMT or WEB LCT program that constitutes the
equipment placed on the other end of the radio connection with respect to the local equipment
(equipment which the user has required the connection to).
Element Manager/Remote Node. This option has a several meanings according to the type of
equipment you wish to insert:
ALplus equipment (Nodal Matrix) belonging to a remote ALplus node.
In this case, it will not be necessary to insert in the remote equipment list all the element
of the remote node but, inserting only one element and identifying it with the Remote
Node type, the connection with all the elements of the remote node will be activated at
the connection with the considered equipment. An example is reported to pag.398.
ALCplus2 equipment belonging to a remote ALCplus2 node.
In this case, it will not be necessary to insert in the remote equipment list all the element
of the remote node but, inserting only one element and identifying it with the Remote
Node type, the connection with all the elements of the remote node will be activated at
the connection with the considered equipment. An example is reported to pag.399.
All the types of equipment, except for the above mentioned one.
Element Manager of the equipment (IP address of the machine where the NMS5UX-B sys-
tem resides).
Not Managed. Element not managed by the SCT/LMT or WEB LCT program. This option can be
used to insert into the remote equipment list some information as for instance the coupling be-
tween the IP address and the NSAP (Gosip) one of an equipment inserted into an OSI network.
4. Select the Edit > Remove > Element command and confirm.
The equipment is deleted.
5. Press Apply and then confirm.
The list is stored in the controller of the equipment
5. Type the name of the file in the proper box (with extension .rel) and set the path where you wish to
save the file.
6. Press OK.
4. Select the file (with extension .rel) where the wished remote equipment list is stored.
5. Press OK.
In the Remote Element Table window, the remote equipment list is displayed.
Each equipment has a remote equipment list stored in its own controller.
With remote equipment list we mean a list containing all the network remote equipment which you wish
to connect to.
When the user requires the connection to any equipment present in the network (local equipment), the
local management program:
SCT/LMT reads, at the connection of this equipment, its remote equipment list and automatically
sends the connection command to all the equipment present in the list.
WEB LCT reads, at the connection of this equipment, its remote equipment list and automatically
sends the connection command to the equipment of type Remote Link, present in the remote
equipment list of the local equipment.
For a better vision of the equipment during the setting of the list, it is possible to subdivide the equipment
into stations. The station does not have any particular meaning; it has been simply introduced to help the
user during the localization of the equipment.
Into each remote equipment list, it is possible to create a maximum of 100 equipment and 30 station.
Besides the remote equipment to be connected, the user can insert into the remote equipment list also the
following information:
IP address of the machine where the NMS5UX-B system resides.
Coupling between IP address and NSAP (Gosip) one of an equipment inserted into an OSI net-
work.
Suppose to have a network made by two ALplus nodes both of them composed by 3 ALplus equipment
(Nodal Matrix) as depicted in Fig.75.
Fig.75 - Definition of a remote ALplus node in the remote equipment list (example 1)
Equipment 1 Equipment 4
172.18.10.1 172.18.10.4
By means of the SCT application the ALplus nodes have been defined: assignment of the station, name of
the node, IP addresses and subset (A, B, C) ad depicted in Fig.76.
To do this, it is sufficient to activate the login with an equipment of the ALplus node and, by means of
the SCT application, to \define the characteristics of the equipment composing the node. The program will
automatically configure the characteristics of the ALplus node even in the other two equipment (station,
Equipment ID, Remote Element Table).
Fig.76 - Definition of a remote ALplus node in the remote equipment list (example 2)
Equipment 1 Equipment 4
Station Name: Milan Station Name: Rome
Node Name: Milan Node Name: Rome
IP: 172.18.10.1 IP: 172.18.10.4
Equip ID: Milan.A Equip ID: Rome.A
Now, suppose you wish to manage locally, by means of SCT, all the network equipment connecting to
Equipment 1. To do this, the remote equipment list of the Equipment 1 must be configured in the following
way:
2. Create under the station Milan an equipment of the node Milan, for example Equipment 2 assigning to
it as Element Type > Managed by SCT (pag.392).
3. Create under the station Rome an equipment of the node Rome, for example Equipment 4 assigning to
it as Element Type > Element Managed/Remote Node.
At the activation of the connection with Equipment 1, the program will automatically activate the connec-
tion with:
Equipment 1, Equipment 2 and Equipment 3 in Connected/Login modality.
Equipment 4, Equipment 5 and Equipment 6 in Connected/Monitor modality.
Suppose to have a network made by two ALCplus2 nodes both of them composed by 3 ALCplus2 equipment
as depicted in Fig.77.
Fig.77 - Definition of a remote ALCplus2 node in the remote equipment list (example 1)
Equipment 1 Equipment 4
172.18.10.1 172.18.10.4
By means of the SCT application the ALCplus2 nodes have been defined: assignment of the station, name
of the node, IP addresses and subset (1, 2, 3) ad depicted in Fig.77.
To do this, it is sufficient to activate the login with an equipment of the ALCplus2 node and, by means
of the SCT application, to define the characteristics of the equipment composing the node. The program
will automatically configure the characteristics of the ALCplus2 node even in the other two equipment (sta-
tion, Equipment ID, Remote Element Table, etc.).
Fig.78 - Definition of a remote ALCplus2 node in the remote equipment list (example 2)
Equipment 1 Equipment 4
Station Name: Milan Station Name: Rome
Node Name: Milan Node Name: Rome
IP: 172.18.10.1 IP: 172.18.10.4
Equip ID: Milan.1 Equip ID: Rome.1
Now, suppose you wish to manage locally, by means of SCT, all the network equipment connecting to
Equipment 1. To do this, the remote equipment list of the Equipment 1 must be configured in the following
way:
2. Create under the station Milan an equipment of the node Milan, for example Equipment 2 assigning to
it as Element Type > Managed by SCT (pag.392).
3. Create under the station Rome an equipment of the node Rome, for example Equipment 4 assigning to
it as Element Type > Element Managed/Remote Node.
At the activation of the connection with Equipment 1, the program will automatically activate the connec-
tion with:
Equipment 1, Equipment 2 and Equipment 3 in Connected/Login modality.
Equipment 4, Equipment 5 and Equipment 6 in Connected/Monitor modality.
The SNMP-NE Sw/Fw Download command updates the software of one or more SNMP equipment.
With detail it is possible:
To update the equipment software (pag.400)
To update the WEB LCT application (pag.402)
The command is available only if it has been selected one or more SNMP equipment of the same type,
except for the ELFO, SDH N+1 and FAMxc.
4. Set the type of download you wish to execute. Select the option:
Forced, to update the software of the equipment controller.
Only different or not present, to update the software of peripheral units (FPGA file and/or oper-
ating code).
5. Activate the Bench switch? box if you wish that, at the end of the download, a switching of the memory
bench is automatically executed in order to use the bench with the updated software.
6. Set the execution modality of the download. If you wish that the updating is:
Immediately executed, activate the Immediate Download box.
Before starting the updating of the controller of the NE, it executes a compatibility check be-
tween the software that must be sent and the one present in the controller itself.
Parameters to
set for the
updating of
the equipment
software
NEs selected
in the map
for which the
updating of
the equipment
software
with be
Push-buttons
executed (2)
bar (1)
Fig.79 notes
(1) Push-button:
Start Dwl. It starts the software updating.
Cancel. It closes the window.
Scheduling. It displays the list of the NEs scheduled for the updating of the software
(Fig.80).
Help. It opens the on-line manual
Double click on one NE: the RelSw window (Fig.82) opens, where the version of the software
present in the memory benches of the NE is displayed.
For the NE objects of ALplus Node or ALCplus2 Node type, the detail of the equipment of the nodal
system is pointed out. This equipment is identified by the logic address:
<node name>.X, where X can assume the value A, B or C (ALplus Node object).
<node name>.Y, where Y can assume a value between 1 and 8 (ALCplus2 Node object).
The operation will be successful and is meaningful only if one or more equipment, supporting the WEB
LCT application, is selected.
3. In the Selection file DWL box, set the file you wish to use for the updating.
It is possible to type the path and the name of the file or press Select (the Select file for download
window opens) and select the file among the available ones.
If the file you wish to use for the operation is not in the home/ftp directory, it is necessary to copy
it in this directory as the supervision system needs, in order to execute correctly the download opera-
tion, to find the file for the updating in the home/ftp directory.
To press Read to display a brief description that illustrates the content of the selected file.
5. Set the execution modality of the download. If you wish that the updating is:
Immediately executed, activate the Immediate Download box.
With equipment software we mean the set of all the software necessary for the management of the whole
NE (software of the main controller and software of the peripheral units).
The equipment software is present in the main controller that have two memory benches (bench), one
working and the other in stand-by.
It is possible to update the software of only one memory bench at a time. The NMS5UX-B automatically
updates the software of the memory bench not on progress or not present.
The updating of the software can be immediately executed (only if a single NE is selected) or can be sched-
uled for a given date/time (suggested option).
In the first case, the operation is executed in real time. In the second case, it is scheduled and the system
will execute the updating at the date/time scheduled by the user.
In both cases, the execution of the download for each selected NE is subjected to the following conditions:
The NE must be in connected status.
The local management program in Configuration modality must not be connected to the NE.
No other operation must be running.
If the updating of the software is immediately executed and the NE is not in one of the above mentioned
conditions, the operation is not executed.
Even if the updating is scheduled and in the moment (date/time) when it was schedule the NE is not in one
of the above mentioned conditions, the operation is not executed, but in this case the system, at regular
intervals, will verify the condition of the NE until:
The NE is in the correct condition and then the download is executed.
The NE is removed from the list of NEs scheduled for the download.
The files, for the software updating, are identified by the extension .dwl and by a name composed by 8
characters. In details:
1 character identifies the technology (S=SDH, P=PDH, M=PMP/IPBOX, K=CommServer).
2 character identifies the type of equipment (R=Radio, M=Multiplex, ComS=CommServer).
3 ... 6 character identify the product number.
7, 8 character identify the most meaningful digits of the version.
The WEB LCT application allows an user connecting to an equipment via his own machine (pc, workstation,
etc.) using the operating system and the Web browser at his disposal.
The update of WEB LCT, as for the equipment software, can be executed immediately or scheduled for a
given date/time.
The update modality is the same described for the equipment software.
The files, for the WEB LCT updating, are identified by the extension .dwl.
The SNMP-Scheduled Sw Dwl Status command displays the list of the SNMP equipment scheduled for
the software updating.
WIth details it is possible:
To display the list of the SNMP equipment scheduled for the software updating (pag.404)
To delete one or more equipment from the list (pag.405)
To stop the updating of the software (pag.406)
To save the list of the scheduled equipment (pag.406)
To re-execute the software update (pag.406).
To switch the memory bench (pag.407).
To filter/sort the list of the scheduled equipment (pag.408).
For more information about the update of the equipment software go to pag.403.
To display the list of the SNMP equipment scheduled for the software updat-
ing
Fig.80 notes
(1) Menu:
File > Deleted All. It deletes all the NEs present in the list except for those for which the
updating of the software is in progress.
File > Deleted Select. It deletes the selected NEs except for those for which the updating of
the software is in progress.
File > Deleted Completed. It deletes the NEs for which the download procedure has been
already executed.
File > Export. It saves the list of the scheduled equipment.
File > Abort. It stops the procedure for the updating of the software.
2. Select the equipment for which the updating of the software is in progress (Status field - Downloading
wording).
3. Type, in the File box, the path and the name of the file where you wish to save the data.
When the window is opened, the default path (/opt/nms5ux/data/export/<application name>) and a
name with the following format are proposed:
ExpSwDwl_<day>-<month>-<year>_<hour>-<minutes>.csv
Where date and time refers to the moment when the Export window has been opened, for example
ExpSwDwl_22-4-2010_11-30.csv.
4. Press OK.
2. Select the equipment for which the operation of software update is failed (field Status - wording Inter-
rupted).
4. Set the date (day, month, year) and the time (hour, minute) when you wish to re-execute the software
update.
5. Press Ok.
In the Scheduling Download window, the selected records pass to status Waiting.
2. Select the equipment for which you wish to execute the switching of the memory benches.
The operation will be successful only for the equipment for which the software updating has been cor-
rectly executed (field Status - wording Completed).
Fig.81 notes
4. Press OK.
The system displays in the Scheduling Download window only the records that satisfy the activated cri-
teria.
Each time the list is filtered, all the records are considered, both the displayed and the hidden ones.
When the Scheduling Download window closes, the possible activation of filters is automatically delet-
ed.
The SNMP-NE Sw/Fw Release command displays the software version of a SNMP equipment.
With details it is possible:
To display the software version of a SNMP equipment (pag.409)
To update the software of a SNMP equipment (pag.410)
To switch the operation of the memory benches of a SNMP equipment controller (pag.411)
To delete the software present in the memory bench in standby of a SNMP equipment (pag.411)
The command is available only if it has been selected a SNMP equipment in connected status, except
for the ELFO, SDH N+1, FAMxc, ALplus Node and ALCplus2 Node.
For the NEs of ALplus Node or ALCplus2 Node type, the command is present in the nodal window (pag.48/
pag.49).
For more information about the update of the equipment software go to pag.403.
Logic address,
IP address and
type of
selected NE
Name of the
file and version
of the software
of equipment
present
respectively on
the memory
benches 1 and 2
Operating status
of the memory
benches 1
and 2 (1)
(1) Label:
running. The software of the considered memory bench is running.
loaded. The software is present in the bench but, at the moment, is not running (standby).
not loaded. The software of the memory bench is not present.
downloading. The updating of the software of the memory bench is in progress.
(2) The list of the parts that constitute the software changes depending of the type of selected equip-
ment. For each code or FPGA file, it is displayed in the column:
Unit. Name of the card or of the part of NE where the controller (code) or the programmable
device (FPGA file) is present.
Element. Name of the software. It generally points out the type of component:
FW_boot. Boot code. This part of code cannot be updated, in fact it has not memory
benches.
FW_appl. Application code.
conf_... or fpga... Configuration file of the programmable devices.
Actual release. Version of the code or FPGA file present in the controller (main or of periph-
eral unit).
Release bench 1 and Release bench 2. Version of the software present respectively in the
memory bench 1 and 2 of the main controller.
The system automatically updates the software of the not running or not present memory bench (Status
box- loaded or not loaded wording).
The operation cannot be executed when the updating of the software is already in progress (Status box -
downloading wording).
3. Press Download.
The Software Download window opens.
4. In the Selection file DWL box, set the file you wish to use for the updating.
It is possible to type the path and the filename or press Select (the Select file for download window
opens) and select the file among the available ones.
If the file you wish to use for the operation is not in the home/ftp directory, it is necessary to copy
it in this directory as the supervision system needs, in order to execute correctly the download opera-
tion, to find the file for the updating in the home/ftp directory.
To display a brief description that illustrates the content of the selected file, press Read.
5. Set the type of download that you wish to execute. Select the option:
Forced, to update the software of the equipment controller.
Only different or not present, to update the software of peripheral units (FPGA file and/or appli-
cation code).
6. Activate the Bench switch? box if you wish that, at the end of the download, a switching of the memory
bench is automatically executed in order to use the bench with the updated software.
7. Set the execution modality of the download. If you wish that the updating is:
Immediately executed, activate the Immediate Download box.
Scheduled to be executed in a second moment, set the date/time in the Scheduling data time
for Download area.
Before starting the updating of the controller of the NE, it executes a compatibility check be-
tween the software that must be sent and the one present in the controller itself.
The check consists in verifying the technology and the type of NE (pointed out by the first 2 char-
acters of the file name). For some types of NEs, checks are executed also on the 3rd character
of the filename. More information is reported in the equipment user manual relevant to the spe-
cific type of NE.
If the parameters are compatible, the download starts. Otherwise, the updating of the software
will not be executed.
If the operation is successful, opening the RelSw window (Fig.82), in the Release box relevant
to the updated memory bench, the new version of the software is pointed out.
If it is not successful, the Status box relevant to the updated memory bench displays the old
version or the wording not loaded.
Set a date/time of execution for the updating of the software, the Software Download window
is closed.
In the list of the scheduled equipment for the download, a record is added for each NE present
in the Equipment list for download area.
It is not possible to switch the memory bench when the updating of the software is in progress and
when the software is not present in a bench.
It is not possible to delete the software present in the memory bench when the updating of the software
is in progress.
The FAMxc-NE Sw/Fw Download command updates the software of one or more FAMxc.
For more information about the update of the FAMxc equipment software go to pag.413.
If the file you wish to use for the operation is not in the home/tftpdir directory, it is necessary to
copy it in this directory as the supervision system needs, in order to execute correctly the download
operation, to find the file for the updating in the home/tftpdir directory.
4. Set the date and time when you wish to schedule the operation in the Date/Time Scheduled for Down-
load box.
5. Activate the Switch Bench and Restart box if you wish that, at the end of download, the memory bench
is switched and the equipment is restarted automatically.
The setting applies to all the equipment present in the Equipment List area. If you wish to carry out
a different setting for an equipment in the list:
a. Select the equipment.
b. Select the Action > Bench Info command.
The Equipment Bench Releases window opens (Fig.85).
c. Activate/deactivate the Switch Bench and Restart box as you wish.
d. Press Ok
The wording Modified is pointed out in the record of the selected NE (area Equipment List).
During the execution of the operation for the considered equipment, the setting of the parameter
Switch Bench and Restart of the Insert will not be considered, but the setting of the same parameter
in the Equipment Bench Releases window will be considered.
6. If enabled, type the access code of the equipment in the Password box.
If the Superuser has set the access code of the equipment in the configuration file of the system, in
order to access the equipment it is not necessary to insert the code. It is sufficient to activate the Pass-
word Default box.
The set password applies for all the equipment present in the Equipment List area. If an equipment
has a different password, it is necessary to set it in the following way:
a. Select the equipment.
b. Select the Action > Bench Info command.
The Equipment Bench Releases window opens (Fig.85).
c. Type the access code of the equipment in the Password box.
d. Press Ok
The wording Modified is pointed out in the record of the selected NE (area Equipment List).
During the execution of the operation for the considered equipment, the setting of the password in the
Insert will not be considered, but that set in the Equipment Bench Releases window will be considered.
7. Press OK.
The Software Download window is closed.
In the list of the scheduled NE for the download, a record is added for each NE present in the Equipment
List.
Parameters
to set for the
updating of
the equipment
software
NEs selected
in the map
for which the
updating of
the equipment
software with
be executed
(1)
Fig.83 notes
With equipment software we mean the set of all the software necessary for the management of the whole
NE.
The equipment software is present in the main controller that have two memory benches (bench), one
working and the other in stand-by.
Each bench can house a version (also different) of equipment software.
It is possible to update the equipment software of only one memory bench at a time. The NMS5UX-B au-
tomatically updates the software of the memory bench not on progress or not present.
The update of the equipment software can be only scheduled and will be the system to carry out the update
on the date/time scheduled by the user.
The execution of the download for each selected NE is subjected to the following conditions:
The NE must be in connected status.
The local management program must not be connected to the NE.
No other operation must be running.
If, in the moment (date/time) when the operation was schedule, the NE is not in one of the above men-
tioned conditions, the operation is not executed, but in this case the system, at regular intervals, will verify
the condition of the NE until:
The NE is in the correct condition and then the download is executed.
The NE is removed from the list of NEs scheduled for the download.
The FAMxc-Scheduled Sw Dwl Status command displays the list of the FAMxc scheduled for the soft-
ware updating.
With details it is possible:
To display the list of the FAMxc scheduled for the software updating (pag.414)
To delete one or more equipment from the list (pag.415)
For more information about the update of the equipment software go to pag.413.
To display the list of the FAMxc scheduled for the software updating
Fig.84 notes
(1) Menu:
File > Close. It closes the window.
Command > Delete Completed. It deletes the NEs for which the download procedure has
been already executed.
Command > Delete Selected. It deletes the selected NEs except for those for which the up-
dating of the software is in progress.
Options > Refresh. It refreshes the information present into the window.
Option > View Error. It displays the characteristics of the scheduled NE. In order:
Logic address of the NE (Equipment).
IP address of the server (Ip Server).
Name of the file used for the download (File).
Result of the operation (Error).
2. To delete:
The NEs for which the download procedure has been already executed (Status field - Completed
wording), select the File > Deleted Completed command.
The selected NEs except for those whose software updating is in progress (Status field - Down-
loading wording), select the equipment and then the File > Deleted Select command.
The equipment is removed from the list.
The FAMxc-NE Sw/Fw Release command displays the software version of a FAMxc.
With details it is possible:
To display the software version of a FAMxc (pag.416)
To switch the operation of the memory benches and to restart a FAMxc (pag.417)
The command is available only if it has been selected a FAMxc in connected status.
For more information about the update of the equipment software of the FAMxc go to pag.413.
Logic address
of the selected
equipment
Version of the
software
present
respectively
on the memory
bench 1 and 2
Memory
bench
currently
in use
Memory
bench
which
will be used
at next boot
4. Select the bench you wish to use at the restart of the equipment (option Bench1 or Bench2 - parameter
Restart Bench Selection).
At the end of the operation, the selected bench will be pointed out in the Netx Boot On Bench box.
5. Type in the Password box, if enabled, the access code of the equipment.
If the Superuser has se the access code of the equipment in the configuration file of the system, it is
not necessary to insert the code to access the equipment. It is sufficient to activate the Password De-
fault box.
6. Press Restart.
The equipment is restarted and the Equipment Bench Releases window is closed.
The Legacy-NE Sw/Fw Download command updates the software of one or more Legacy equipment.
The command is available only if it has been selected one or more Legacy equipment of the same type.
For more information about the update of the equipment software go to pag.419.
3. In the File Selection box, set the file you wish to use for the updating.
It is possible to type the path and the name of the file or press Select (the File Select window opens)
and select the file among the available ones.
4. Set the execution modality of the download. If you wish that the updating is:
Immediately executed, activate the Immediate Download box.
Before executing the update operation, the NE controller executes a compatibility check between
the software that has to be forwarded and the one present into the controller itself. The check consists
of checking the technology and the NE type.
Only if the parameters result compatible ones, it is possible to execute the software update (do not
execute the remaining part of the procedure).
If the parameters result compatible ones, the system displays a confirmation window that points out
the physical address, the logic address and the NE type for which it is on progress the software update.
Parameters
to set for the
updating of the
equipment
software
NEs selected
in the map for
which the
updating of
the equipment
software with
be executed
Push-buttons (2)
bar (1)
Fig.86 notes
(1) Push-button:
Start Dwl. It starts the updating of the software.
Cancel. It closes the window.
Scheduling. It displays the list of the NEs scheduled for the updating of the sw (Fig.87).
With equipment software we mean the set of all the software necessary for the management of the whole
NE (software of the main controller and software of the peripheral units).
The updating of the software can be immediately executed (only if a single NE is selected) or can be sched-
uled for a given date/time (suggested option).
In the first case, the operation is executed in real time. In the second case, it is scheduled and the system
will execute the updating at the date/time scheduled by the user.
In both cases, the execution of the download for each selected NE is subjected to the following conditions:
The NE must be in connected status.
The local management program in Configuration modality must not be connected to the NE.
No other operation must be running.
If the updating of the software is immediately executed and the NE is not in one of the above mentioned
conditions, the operation is not executed.
Even if the updating is scheduled and in the moment (date/time) when it was schedule the NE is not in one
of the above mentioned conditions, the operation is not executed, but in this case the system, at regular
intervals, will verify the condition of the NE until:
The NE is in the correct condition and then the download is executed.
The NE is removed from the list of NEs scheduled for the download.
The Legacy-Scheduled Sw Dwl Status command displays the list of the Legacy equipment scheduled
for the software updating.
With details it is possible:
To display the list of the Legacy equipment scheduled for the software updating (pag.420)
To delete one or more equipment from the list (pag.421)
To stop the updating of the software (pag.421)
The command is available only if the modules for the management of the Legacy equipment have been
installed.
For more information about the update of the equipment software go to pag.419.
To display the list of the Legacy equipment scheduled for the software up-
dating
Menu
bar (1)
List of the
NEs sheduled
for the
updating
of equipment
software (2)
Fig.87 notes
(1) Menu:
File > Close. It closes the window.
Options > Remove. It deletes the selected NE with the exception of the one for which the
software update is on progress (Downloading wording into the Status field).
Options > View Download Info. It displays the details of the information relevant to the up-
date of the selected software.
The choice of the command opens the Swdl Information window that points out the following
information:
Logical Address. Logical address of the equipment.
Equipment Type. Equipment type.
Physical Address. Physical address of the equipment.
Selected File. Path and file name used for the update.
Selected Card. Card of the equipment involved into the operation.
Software Release. Release of the software.
Scheduled Time. Date/time relevant to the update programming of the software.
The command is available only if it has been selected an equipment for which the system
is executing the update of the software (Downloading wording into the Status field).
Help > On usage. It opens the on-line manual.
In this case, it is advisable to execute or to program newly the update of the sw.
Check Eq. Status. The status control of the equipment is on progress (operation ex-
ecuted before the download).
Aborted. The update of the software has been interrupted.
The system can point out into the Status column the status of the operation and also a self-
explaining message.
The presence of the symbol - points out that the information is not available because it is
not a significant one for the current status of the operation.
2. Select the equipment you wish to delete from the list, except those for which the software update is
running (Status field - Downloading wording).
Alarm History Backup (pag.423). It saves to disk and/or tape the alarm history stored in the
Alarm History table.
Alarm History Restore (pag.424). It restores the alarm history previously saved to disk/tape
and copies it into the Old History table.
Alarm History Delete Backup (pag.425). It deletes the alarm history saved on disk.
Performance Monitoring Backup (pag.426). It saves to disk and/or tape the results of the
PM measures stored in the Performance Monitoring table.
Performance Monitoring Restore (pag.427). It restores the results of the PM measures pre-
viously saved to disk/tape and copies it into the Old Performance Monitoring table.
Performance Monitoring Delete (pag.428). It deletes the results of the PM measures saved
to disk.
NMS5UX Global Database Backup (pag.429). It saves to disk and/or tape the information
contained in the NMS5UX-B database.
NMS5UX Global Database Restore (pag.430). It restores the information contained in the
system database and previously saved to disk/tape.
The Alarm History Backup command saves to disk and/or tape the history of the alarm/status/event sig-
nallings (alarms) stored in the Alarm History table relevant to the equipment present in all the maps.
2 Activate the:
Backup To Tape box, if the user wants to save the contents of the Alarm History table on tape
(DAT tape).
Backup To Disk box, if the user wants to save the table on the machine disk (workstation or
server).
If the user activates both the boxes, the system saves the data as on disk as on tape.
The wording [/dev/rmt/Om], placed on the side if the box, points out that the contents of
the table will be overwritten on the possible data already present on the DAT. This setting can
not be changed.
Backup To Disk box, type, into the text field, the name of the file where the user wants to save
the contents of the table.
Press Browser to select the name of an already existing file (in this case, the content of the file
will be overwritten by the new data).
The File name field points out the predefined path where the file is saved. The setting cannot be
modified.
4. Press OK.
The content of the table is saved to a file on the disk and/or tape.
Then, to display the content of the file, it will be necessary to restore it (pag.424) and open the Old
History Browser window (pag.279).
To display the content of the Alarm History table open the Alarm History Browser window (pag.264).
The Alarm History Restore command restores the history of the alarm/status/event signallings (alarms)
previously saved to disk/tape and copies it into the Old History table.
2. Select, in the Files list, the name of the file you wish to restore.
The list shows the files present in the predefined directory (displayed in the Selection box). It is the
same used by the system to automatically save the files during the backup procedure.
3. Press OK.
If the operation is successful, a confirmation window opens.
The restored data will overwrite those present in the Old History table. Its contents can be displayed
into the Old History Browser window (pag.279).
The Alarm History Delete Backup command deletes the backup files, relevant to the signallings of
alarm/status/event, saved by the Alarm History Backup command to the disk of the machine.
2. Select, in the Files list, the name of the file you wish to delete.
The list shows the files present in the predefined directory (displayed in the Selection box). It is the
same where the system automatically saves the files during the backup procedure.
Even if it is possible to set a different directory, the system allows deleting files only in the prede-
fined directory.
3. Press OK.
If the operation is successful, a confirmation message opens.
The Performance Monitoring Backup command saves to disk and/or tape the results of the PM meas-
ures stored in the Performance Monitoring table relevant to the equipment present in all maps.
2. In the Selected Month menu, select the month you wish to save.
The last 6 months mapped in the database are available in the list.
3 Activate the:
Backup To Tape box, if the user wants to save the contents of the Performance Monitoring table
on tape (DAT tape).
Backup To Disk box, if the user wants to save the table on the disk of the workstation or server.
If the user activates both the boxes, the system saves the data as on disk as on tape.
The wording [/dev/rmt/Om], placed on the side if the box, points out that the contents of
the table will be overwritten on the possible data already present on the DAT. This setting can
not be changed.
Backup To Disk box, type, into the text field, the name of the file where the user wants to save
the contents of the table.
Press Browser to select the name of an already existing file (in this case the contents of the file
will be overwritten with the new data).
Into the File name field, the system points out the pre-defined path where the system saves the
file. This setting can not be changed.
5. Activate the Delete Table box if you wish that the content of the Performance Monitoring table after the
saving to file is automatically deleted.
6. Press OK.
If the operation is successful, a confirmation window opens and the content of the table is saved to a
file of the disk and/or tape.
Then, in order to display the content of the file, it will be necessary to restore it (pag.427) and open
the Graphic Performance Monitoring - OLD window (pag.177).
To display the content of the Performance Monitoring table open the Graphic Performance Monitoring
window (pag.173).
The Performance Monitoring Restore command restores the results of the PM measures previously
saved to disk/tape and copies it into the Old Performance Monitoring table.
2. Select, in the Files list, the name of the file you wish to restore.
The list shows the files present in the predefined directory (displayed in the Selection box). It is the
same where the system automatically saves the files during the backup procedure.
3. Press OK.
If the operation is successful, a confirmation window opens.
The restored data will overwrite those present in the Old Performance Monitoring table. Its contents
can be displayed into the Graphical Performance Monitoring - OLD window (pag.177).
The Performance Monitoring Delete command deletes the backup files, relevant to the PM measures,
saved by the Performance Monitoring Backup command on the disk of the machine.
2. Select, in the Files list, the name of the file you wish to delete.
The list displays the file present in the predefined directory (displayed in the Selection box). It is the
same where the system automatically saves the files during the backup procedure.
Even if it is possible to set a different directory, the system allows deleting the files only in the pre-
defined directory.
3. Press OK.
If the operation is successful, a confirmation message opens.
The NMS5UX Global Database Backup command saves to disk and/or tape the information contained
in the NMS5UX-B database where the data relevant to all the maps and all the existing equipment are
stored.
2 Activate the:
Backup To Disk box, if the user wants to save the database on the machine disk (workstation or
server).
On the side of the box, it is pointed out the pre-defined path where the system saves the file.
This setting can not be changed.
Backup To Tape box, if the user wants to save the contents of the database on the DAT tape.
The wording [/dev/rmt/Om], placed on the side if the box, points out that the contents of
the database will be overwritten on the possible data already present on the DAT. This setting
can not be changed.
If the user activates both the boxes, the system saves the data as on disk as on tape.
3 If the user has activated the Backup To Tape box, insert the tape into the DAT drive of the machine.
4. Press OK.
Then, it will be possible to restore the information saved executing the procedure of restore of the da-
tabase (pag.430).
The NMS5UX Global Database Restore command restores the information contained in the system da-
tabase and previously saved to disk/tape.
The restore of the data cannot be executed if the NMS5UX-B system is running.
The Ring Manager menu is available only if the Ring Manager application have been installed. For the
use of the Ring Manager application refer to the specific documentation.
The RM-Add Ring, RM-Delete Ring and RM-Modify/View Ring commands are used to represent
graphically the Ring objects in the maps and to provide to NMS5UX-B system the parameters to manage
and control them.
Before using them, it is suggested to read the Graphic network representation (pag.78) where the modal-
ities to configure correctly and rapidly one's supervision system are described.
The Ring objects are used to identify subnetworks of PDH and SDH equipment which implement Paths. For
an easy description, in this manual the wording Ring will be used to point out these subnetworks, while the
Ring objects will be simply defined Ring objects.
Edit > RM-Add Ring (pag.432). It creates Ring objects for the graphic representation of the
network in the map.
Edit > RM-Delete Ring (pag.433). It deletes a Ring symbol from the map.
Edit > RM-Modify/View Ring (pag.434). It displays/modifies the characteristics of a Ring ob-
ject.
Fault > RM-Network Alarm History (pag.435). It displays/manages the alarm history of the
equipment present in the Rings managed by the supervision system.
Fault > RM-Network Current Alarm (pag.443). It displays/manages the alarms active in the
equipment present in the Rings managed by the supervision system.
Fault > RM-Network Alarm Summary (pag.449). It displays/manages the summary of the
alarm history of the equipment present in the Rings managed by the supervision system.
Fault > RM-Element Alarm History (pag.454). It displays/manages the alarm history of the
equipment present in the specific Ring.
Fault > RM-Element Current Alarm (pag.455). It displays/manages the alarms active in the
equipment present in the specific Ring.
Fault > RM-Element Alarm Summary (pag.456). It displays/manages the summary of the
alarm history of the equipment present in the specific Ring.
Locate > RM-Ring Browser (pag.457). It displays the list of the Rings managed by the super-
vision system.
Locate > RM-Path Browser (pag.459). It displays the list of the Path present in the Rings of
the current map.
Locate > RM-Equipment Browser (pag.472). It displays the list of the equipment present in
the Rings of the current map.
The RM-Add Ring command creates Ring objects for the graphic representation of the network in the map.
Before creating an object, it is suggested to read the par. Rules for the creation of the objects (pag.82).
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the Ring.
2. Select the Ring Manager > Edit > RM-Add Ring command.
The Add Ring window opens.
3. Type the name of the Ring (alphanumeric string of minimum 1 character and maximum 32 characters)
in the Label box.
The name will be displayed under the object symbol and will constitute the name of the window that is
opened at the double selection of the symbol.
4. In the Comment area, type possible information relevant to the object (max 100 characters).
The setting of this parameter is optional.
5. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The Ring is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move the symbol
in any point of the View area.
If the created Ring symbol is already present in a map, it automatically will acquire the status and the
characteristics of the existing object.
The RM-Delete Ring command deletes a Ring symbol from the map.
If a Ring object is present only in one map, can be deleted only if it does not contain objects (equipment,
Link, Path, etc.)
If the same Ring object is present in more maps, it is possible to delete the symbol even if it contains ob-
jects, except for the last copy for which the above mentioned rule is valid: it can be deleted only if empty.
1. Into the UX Map Manager window select the Ring object you wish to delete.
2. Select the Ring Manager > Edit > RM-Delete Ring command or press the right mouse button, select
Delete and confirm.
The object is removed from the map.
It is not possible to assign the same name to two different Ring objects.
If the same Ring object has been created into two different maps, at the changing of the parameter values
of such a Ring object into a map, the system automatically changes the values of the parameters relevant
to the same object into the other map.
1. Into the UX Map Manager window select the wished Ring object.
2. Select the Ring Manager > Edit > RM-Modify/View Ring command or press the right mouse button
and select Modify/View.
The Ring Properties window opens.
Box/area:
Label. Ring name.
Type. Ring symbol.
Comment. Additional information.
It is possible to change the Label and Comment parameters. The setting mode of the parameters is the
same one pointed out to pag.432.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
In the UX Map Manager window, the Ring assumes the new characteristics.
The RM-Network Alarm History command displays/manages the history of the alarm/status/event sig-
nallings (alarms) stored in the Ring Manager database, of the equipment present in the Rings managed by
the supervision system.
With details it is possible:
To display the alarm history of the equipment present in the Rings managed by the supervision
system (pag.435)
To save the alarms list (pag.437)
To delete the alarms (pag.437)
To mark the alarms (pag.438)
To realign the alarm table of Ring Manager to that of NMS5UX-B (pag.438).
To activate/deactivate the automatic updating of the data (pag.438)
To filter the alarms list (pag.439)
To sort the alarms list (pag.440)
To display the acknowledge information of an alarm (pag.441)
To display the alarm history of the equipment present in the Rings managed
by the supervision system
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens, where the alarm history stored in the Ring Manager database,
of the equipment present in the Rings managed by the sNMS5UX-B is displayed (Fig.88).
At the opening of the window a filter is applied to the alarms list: only the alarms, whose detection
date is successive to the midnight of the current day, are displayed. Besides, by default, the automatic
updating of the information is inactive.
A warning message could be displayed, informing that the database contains a number of alarms great-
er than 5000.
For this cause, the window will display only the records, in chronological order from the newest to the
oldest one, until 5000.
The 5000 limit is not a memory limit, but simply a limit in the displaying of the alarms.
In order to read the alarms successive to 5000, it is sufficient to delete some records or modify the
filters.
Menu
bar (1)
Alarms
list (2)
Status
bar (3)
Fig.88 notes
(1) Menu:
File > Save. It saves to text file the alarms list.
File > Close. It closes the window.
Actions > Delete. It deletes one or more records from the list and database.
Actions > Acknowledge. It marks one or more records, in such a way that the system mem-
orizes that the user has seen the alarms.
Actions > Refresh. It updates the data present in the window.
Actions > Alarm Synchronization. It re-aligns the alarms table between NMS5UX-B and Ring
Manager.
View > Filter. It filters the alarms list.
View > Sort Criteria. It sorts the list of records.
View > Acknowledge Information. It displays the acknowledge information of the alarms.
(2) For each alarm, it is displayed in the column:
Severity. Type of signalling: alarm, status and event and if the signalling has been detected
or is cleared; for the alarms also the severity is displayed.
The parameter is represented by a coloured box and by a wording, in detail:
Background colour Wording Description
Green Normal Detected event signalling
Blue Status Detected status signalling
Light blue Warning Detected alarm with Warning severity
Yellow Minor Detected alarm with Minor severity
Orange Major Detected alarm with Major severity
Red Critical Detected alarm with Critical severity
No background Normal Cleared event signalling
No background Status Cleared status signalling
No background Warning Cleared alarm with Warning severity
No background Minor Cleared alarm with Minor severity
No background Major Cleared alarm with Major severity
No background Critical Cleared alarm with Critical severity
Ack. Marking status of the record. If the field is empty, the alarm has not been marked. If
the X character is present the record has been marked.
Each alarm can be acknowledged twice: the first time when the alarm is detected. When the
alarm clears, the character X is removed from the record and the user can acknowledge it
the second time.
In any moment, it is possible to display the acknowledge information of an alarm moving to
the record and pressing the right mouse button. A pop-up window is displayed with the detail
of the acknowledge. The content of the window is the same described at pag.441.
For the NE objects of ALplus Node type, the detail of the equipment of the nodal system is pointed
out. This equipment is identified by the logic address <node name>.A, <node name>.B, <node
name>.C.
The date/time is set by the element that generated the alarm; in the most cases it is the NE con-
troller.
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens (Fig.88).
2. To save to a file:
A group of alarms, select the records and then the File > Save > Selected command.
The displayed alarms, select the File > Save > Filtered command. If no filter is active, the
displayed records correspond to the records stored in the database.
The Save File window opens.
3. Type, in the Selection box, the path and the name of the file where the information must be saved.
4. Press Ok.
The files are saved in text format and can be opened using any text editor.
Operation available only to the Superuser and to the users with privileged or advanced profile.
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens (Fig.88).
2. To delete from the list and from the database of supervision system:
A group of alarms, select the records and then the Actions > Delete > Selected Alarms com-
mand.
The displayed alarms, select the Actions > Delete > Filtered Alarms command. If the filters
are not active, the displayed records correspond to the records stored in the database.
All the alarms of the database, select the Actions > Delete > All Alarms command.
The records are deleted.
Operation available only to the Superuser and to the users with privileged or advanced profile.
After a record has been marked, the operation cannot be undone.
Each alarm can be acknowledged twice: the first time when the alarm is detected. When the alarm clears,
the character X is removed from the record and the user can acknowledge it the second time. In this second
case (if already set during the first acknowledge), the value of the Trouble Identification Code parameter
cannot be modified.
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens (Fig.88).
2. To mark:
A group of alarms, select the records and then the Actions > Acknowledge > Selected
Alarms command.
The displayed alarms, select the Actions > Acknowledge > Filtered Alarms command. If the
filters are not active, the displayed records correspond to the records stored in the database.
All the alarms of the database, select the Actions > Acknowledge > All Alarms command.
The Acknowledge Alarm window opens.
The User box displays the username of the NMS5UX user who required the marking of the records. The
value of the box is automatically set to the username of the NMS5UX user who opened the map. The
value cannot be changed.
3. Type in the Trouble Identification Code box a code identifying the records (alphanumeric string of max
15 characters); it can be used later as search criterion.
The setting of this parameter is optional.
4. Type in the Comment box some additional information (alphanumeric string of max 500 characters).
The setting of this parameter is optional.
5. Press Ok.
The record will be marked with the letter X.
If more records are selected for the operation, the setting of the Trouble Identification Code and Com-
ment parameters are for all the records.
If one or more detected and cleared alarms are selected, the setting of the Trouble Identification Code
and Comment parameters applies both for the set event (SET) and for the clear event (CLEAR).
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens (Fig.88).
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens (Fig.88).
At the opening of the window, by default, the automatic updating of the information is inactive.
3. To deactivate again the automatic updating of the data, select the symbol.
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens (Fig.88).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the RM - Alarm History window only the record that satisfy specific criteria.
Each time that the list is filtered, all the records are considered, both the displayed and the hidden ones.
When the RM - Alarm History window is closed, the possible activation of the filters is automatically
cleared.
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens (Fig.88).
5. If you wish that the alarms are sorted also according to their address, activate the Group Equipment
box (second sorting criterion).
6. Press OK (it executes the sorting and closes the window) or Apply (it executes the sorting and does
not close the window).
The RM - Alarm History window will list the records in the set order.
1. Select the Ring Manager > Fault > RM-Network Alarm History command.
The RM - Alarm History window opens (Fig.88).
2. Select the record which you wish to display the detail of the acknowledge for.
Identification
Code
(1)
Detailed
Detailed information
information of the
of the acknowledge
acknowledge when the signal
when the signal was in status:
was in status: detected and
detected cleared
(2) (3) (2) (3)
Fig.89 notes
(1) Identification code of the record assigned by the user during the alarm acknowledge.
(2) Option:
User. Username of the NMS5UX user who executed the acknowledgement of the record.
Time. Moment when the record has been acknowledged <day-month-year hours:min-
utes:seconds>.
Comment. Additional information.
(3) If the alarm has been acknowledged the first time when it was in detected-cleared status, the data
present in the SET:... and CLEAR:... areas are the same.
The information present in the RM - Alarm History window are dynamically updated only if the procedure
for the automatic updating is active (pag.438).
At the opening of the RM - Alarm History window, the procedure of automatic updating of the informa-
tion is, by default inactive (the default setting can be modified by the Superuser).
The setting of the filters or the criteria used to sort the records in a RM - Alarm History window does not
influence the displaying of the information in the other open RM - Alarm History windows or in the RM -
Current Alarms window.
The alarms are stored in the database managed by Ring Manager application (database of Ring Manager).
The application stores to disk all the alarms up to a limit N (configurable by Superuser - default 50000).
When this limit is reached, the system automatically removes the oldest X alarms (X configurable by Su-
peruser - default 1000).
During this period, it is possible to manually delete the alarms (pag.437). It is suggested to periodically
delete and/or store to file the less meaningful records, so to avoid the saturation of the database.
As help to the description of the command, see par. Modality of the updating of data (pag.448)
To display the alarms active in the equipment present in the Rings managed
by the supervision system
1. Select the Ring Manager > Fault > RM-Network Current Alarm command.
The RM - Current Alarms window opens, where the list of the alarms active in the equipment present
in the Rings managed by the supervision system is displayed (Fig.90).
At the opening of the window, by default, the automatic updating of the information is inactive.
Menu
bar (1)
Alarms
list (2)
Status
bar (3)
Fig.90 notes
(1) Menu:
File > Save. It saves to text file the alarms list.
File > Close. It closes the window.
For the NE objects of ALplus Node type, the detail of the equipment of the nodal system is pointed
out. This equipment is identified by the logic address <node name>.A, <node name>.B, <node
name>.C.
1. Select the Ring Manager > Fault > RM-Network Current Alarm command.
The RM - Current Alarms window opens (Fig.90).
2. To save to file:
A group of alarms, select the records and then the File > Save > Selected command.
The displayed alarms, select the File > Save > Filtered command. If filters are not active, the
displayed records corresponds to the records stored in the database.
The Save File window opens.
3. Type, in the Selection box, the path and the name of the file where the information must be saved.
4. Press Ok.
The files are saved in text format and can be opened using any text editor.
1. Select the Ring Manager > Fault > RM-Network Current Alarm command.
The RM - Current Alarms window opens (Fig.90).
2. To mark:
A group of alarms, select the records and then the Actions > Acknowledge > Selected
Alarms command.
The displayed alarms, select the Actions > Acknowledge > Filtered Alarms command. If fil-
ters are not active, the displayed records correspond to the records stored in the database.
All the alarms of the database, select the Actions > Acknowledge > All Alarms command.
The Acknowledge Alarm window opens.
The User box displays the username of the NMS5UX user who required the marking of the records. The
value of the box is automatically set to the username of the NMS5UX user who opened the map. The
value cannot be changed.
3. Type in the Trouble Identification Code box a code identifying the records (alphanumeric string of max
15 characters); it can be used later as search criterion.
The setting of this parameter is optional.
4. Type in the Comment box some additional information (alphanumeric string of max 500 characters).
The setting of this parameter is optional.
5. Press Ok.
The record will be marked with the letter X.
If more records are selected for the operation, the settings of the Trouble Identification Code and Com-
ment parameters applies for all the records.
1. Select the Ring Manager > Fault > RM-Network Current Alarm command.
The RM - Current Alarms window opens (Fig.90).
2. Select the Actions > Alarm Synchronization command.
The information present in the database of Ring Manager and relevant to the alarms are realigned to
that present in the database of NMS5UX-B.
1. Select the Ring Manager > Fault > RM-Network Current Alarm command.
The RM - Current Alarms window opens (Fig.90).
At the opening of the window, by default, the automatic updating of the information is inactive.
3. To deactivate again the automatic updating of the data, select the symbol.
1. Select the Ring Manager > Fault > RM-Network Current Alarm command.
The RM - Current Alarms window opens (Fig.90).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the RM - Current Alarms window only the record that satisfy specific criteria.
Each time that the list is filtered, all the records are considered, both the displayed and the hidden ones.
When the RM - Current Alarm window is closed, the possible activation of the filters is automatically
cleared.
In the window, there are the push-buttons:
Save.... It saves the set criteria to a file.
On the choice of the push-button, the Save Filter window opens.
Type the name you wish to assign to the file in the Selection box and press OK.
Load.... It opens the file, where a previously saved specific setting of filters is contained.
On the choice of the push-button, the Load Filter window opens.
Select the wished file in the Files list and press OK.
Delete....It deletes the file where a previously saved specific setting of filters is contained.
On the choice of the push-button, the Delete Filter window opens.
Select the wished file in the Files list and press OK.
Clear. It clears the activation of all the filters.
Cancel. It closes the window and does not execute the operation.
1. Select the Ring Manager > Fault > RM-Network Current Alarm command.
The RM - Current Alarms window opens (Fig.90).
5. If you wish that the alarms are sorted also according to their address, activate the Group Equipment
box (second sorting criterion).
6. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The RM - Current Alarms window will list the records in the set order.
1. Select the Ring Manager > Fault > RM-Network Current Alarm command.
The RM - Current Alarms window opens (Fig.90).
2. Select the record which you wish to display the detail of the acknowledge for.
Identification
Code
(1)
Fig.91 notes
(1) Identification code of the record assigned by the user during the alarm acknowledge.
(2) Option:
User. Username of the NMS5UX user who executed the acknowledgement of the record.
Time. Moment when the record has been acknowledged <day-month-year hour:minute:sec-
ond>.
Comment. Additional information.
The information present in the RM - Current Alarm window are dynamically updated only if the procedure
for the automatic updating is active (pag.445).
At the opening of the RM - Current Alarm window, the procedure of automatic updating of the informa-
tion is, by default inactive (the default setting can be modified by the Superuser).
The RM-Network Alarm Summary display/manage the summary of the alarm history of the equipment
present in the Rings managed by the supervision system.
With details it is possible:
To display the summary of the alarm history subdivided for the severity relevant to the equip-
ment present in the Rings (pag.449)
To filter the alarm list (pag.450)
To open the file, where a previously saved specific setting of filters is contained (pag.452)
To save the set filters to a file (pag.452)
To delete the file where a previously saved specific setting of filters is contained (pag.453)
To display the alarms stored in the alarm history (pag.453)
To reset the indication of status change (pag.453)
To modify the title of the RM - Alarm Summary window (pag.453)
To display the summary of the alarm history subdivided for the severity rel-
evant to the equipment present in the Rings
1. Select the Ring Manager > Fault > RM-Network Alarm Summary command.
The RM - Alarm Summary window opens, where the summary of the alarm history subdivided for the
severity relevant to the equipment present in the Rings is displayed (Fig.92).
At the opening of the window a filter is applied to the alarms list: only the alarms, whose detection
date is successive to the midnight of the current day, are displayed.
In the window the information updating is dynamic.
Title Number of
bar (1) alarms
Menu detected but
bar (2) not cleared
yet (6)
Indication
Number of
of "status
alarms
change (3)
detected
and cleared
(7)
Number of
alarms
subdivided
according
type and
severity (4)
Criterion
used to
subdivide Status
the alarms bar (8)
(5)
(1) By default, the window title is RM - Alarm Summary. It can be changed as you wish (see pag.453).
(2) Menu:
File > Load. It opens the file, where a previously saved specific setting of filters is contained.
File > Save. It saves the set filters to a file.
File > Delete. It deletes the file where a previously saved specific setting of filters is con-
tained
File > Close. It closes the window.
Options > Window Title. It changes the title of the window.
Options > Clear Flag. It resets the indication of status change.
View > Filter. It filters the alarms list.
(3) The presence of the flag next to the record points out that, from when the RM - Alarm Summary
window has been opened or from the last selection of the Options > Clear Flag command, a
change occurred: an alarm has been detected or cleared.
(4) It is possible that, in the RM - Alarm Summary window, there are not one or more records relevant
to the type of signallings/severity levels. Their presence is subjected to the activation of filters.
(5) Record:
Critical. Alarms with Critical severity.
Major. Alarms with Major severity.
Minor. Alarms with Minor severity.
Warning. Alarms with Warning severity.
Status. Status signallings.
Normal. Event signallings.
Total. All the signallings (alarms, status, events).
(6) Option:
Active (Critical record). Detected alarms with Critical severity.
Active (Major record). Detected alarms with Major severity.
Active (Minor record). Detected alarms with Minor severity.
Active (Warning record). Detected alarms with Warning severity.
Active (Status record). Detected status signallings.
Active (Normal record). Detected event signallings.
Active (Total record). Total number of detected signallings.
(7) Option:
Cleared (Critical record). Detected/cleared alarms with Critical severity.
Cleared (Major record). Detected/cleared alarms with Major severity.
Cleared (Minor record). Detected/cleared alarms with Minor severity.
Cleared (Warning record). Detected/cleared alarms with Warning severity.
Cleared (Status record). Detected/cleared status signallings.
Cleared (Normal record). Detected/cleared event signallings.
Cleared (Total record). Total number of detected/cleared signallings.
(8) xx of yy filed. Number of displayed records (xx) and number of total record (yy). If no filter is active,
the number of displayed records corresponds to the number of total records.
1. Select the Ring Manager > Fault > RM-Network Alarm Summary command.
The RM - Alarm Summary window opens (Fig.92).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the RM - Alarm Summary window only the record that satisfy specific criteria.
Each time that the list is filtered, all the records are considered, both the displayed and the hidden ones.
When the RM - Alarm Summary window is closed, the possible activation of the filters is automatically
cleared.
In the window, there are the push-buttons:
Save.... It saves the set criteria to a file.
On the choice of the push-button, the Save Filter window opens.
Type the name you wish to assign to the file in the Selection box and press OK.
Load.... It opens the file, where a previously saved specific setting of filters is contained.
On the choice of the push-button, the Load Filter window opens.
Select the wished file in the Files list and press OK.
Delete....It deletes the file where a previously saved specific setting of filters is contained.
On the choice of the push-button, the Delete Filter window opens.
Select the wished file in the Files list and press OK.
Clear. It clears the activation of all the filters.
Cancel. It closes the window and does not execute the operation.
To open the file, where a previously saved specific setting of filters is con-
tained (RM-Network Alarm Summary)
1. Select the Ring Manager > Fault > RM-Network Alarm Summary command.
The RM - Alarm Summary window opens (Fig.92).
2. Select the File > Load command.
The Load Filter window opens.
1. Select the Ring Manager > Fault > RM-Network Alarm Summary command.
The RM - Alarm Summary window opens (Fig.92).
2. Select the File > Save command.
The Save Filter window opens.
3. Type the name you wish to assign to the file in the Selection box.
4. Press OK.
The filter currently applied to the window and the window title are saved to the file.
1. Select the Ring Manager > Fault > RM-Network Alarm Summary command.
The RM - Alarm Summary window opens (Fig.92).
4. Press OK.
The file is removed from the disk.
To display the alarms stored in the alarm history (RM-Network Alarm Sum-
mary)
1. Select the Ring Manager > Fault > RM-Network Alarm Summary command.
The RM - Alarm Summary window opens (Fig.92).
2. Select the option relevant to the type/severity of signalling, for which you wish to display the relevant
list stored in the alarm history.
The RM - Alarm History window opens (Fig.88), where only the alarms of the selected type and severity,
whose detection date is successive to the midnight of the current day, are displayed.
For example, if the Active option (Minor record) is selected, the RM - Alarm History window opens, with
displayed only the active alarms with Minor severity whose detection date is successive to the midnight
of the current day. To display the remaining of the alarms, it is sufficient to change the filter.
1. Select the Ring Manager > Fault > RM-Network Alarm Summary command.
The RM - Alarm Summary window opens (Fig.92).
1. Select the Ring Manager > Fault > RM-Network Alarm Summary command.
The RM - Alarm Summary window opens (Fig.92).
3. Type, in the text field, the new title for the RM - Alarm Summary window.
4. Press OK.
The window immediately gets the new title.
The RM-Element Alarm History command displays/manages the history of the alarm/status/event sig-
nallings (alarms) stored in the Ring Manager database, relevant the equipment present ONLY to the se-
lected Ring.
The choice of the command opens the <Ring name> Alarm History window.
The description of the window and the operations that can be executed are the same reported in the
par. RM-Network Alarm History (pag.435).
The RM-Element Alarm History command is available only if it has been selected a single Ring in the UX
Map Manager window.
The choice of the command opens the <Ring name> Current Alarm window.
The description of the window and the operations that can be executed are the same reported in the
par. RM-Network Current Alarm (pag.443).
The RM-Element Current Alarm command is available only if it has been selected a single Ring in the
UX Map Manager window.
The RM-Element Alarm Summary displays/manages the summary of the alarm history of the equipment
present ONLY to the selected Ring.
The description of the window and the operations that can be executed are the same reported in the
par. RM-Network Alarm Summary (pag.449).
The RM-Element Alarm Summary command is available only if it has been selected a single Ring in the
UX Map Manager window.
The RM-Ring Browser displays the list of the Rings managed by the NMS5UX-B.
1. Select the Ring Manager > Locate > RM-Ring Browser command.
The Ring Browser window opens, where the list of the Rings managed by the supervision system
NMS5UX-B is displayed (Fig.93).
Menu
bar (1)
Ring
list (2)
Status
bar (3)
Fig.93 notes
(1) Menu:
File > Refresh. It updates the data present in the window.
File > Close. It closes the window.
Options > Find ring. It searches and highlights in the map the symbol of a Ring
Options > Open ring. It opens the Ring Manager window.
(2) For each Ring the name corresponding to the name of the relevant Ring symbol in the map is point-
ed out.
The list of the Rings is in alphabetical order.
(3) The Ring number option points out the total number of Rings.
1. Select the Ring Manager > Locate > RM-Ring Browser command.
The Ring Browser window opens (Fig.93).
1. Select the Ring Manager > Locate > RM-Ring Browser command.
The Ring Browser window opens (Fig.93).
* The user with Entry profile cannot modify/save the information relevant to a Path and modify the Path
configuration (single or protected).
The user with Entry or Normal profile cannot delete the Paths, add the protection to a Path and activate/
deactivate the management of a Path.
The RM-Path Browser display the list of the Path present in the Rings of the current map.
With details it is possible:
To display the list of the Path present in the Rings of the current map (pag.459)
To save the list of the Path (pag.461)
To delete one or more Paths (pag.461)
To delete the protection of a Path (pag.462)
To add the protection to a Path (pag.462)
To activate the management of a Path (pag.462)
To deactivate the management of a Path (pag.463)
To switch the names of the Paths associated in a protection (pag.463)
To display the alarms active in the equipment implementing a Path (pag.463)
To display the history of the alarms relevant to the equipment implementing a Path (pag.463)
To display/modify/save the information relevant to a Path (pag.463)
To display/modify the configuration of a Path (pag.465)
To display/modify the configuration of a Path protected (pag.468)
To search and highlight a Path in the Ring Manager window in which it is contained (pag.470)
To search and highlight in the map, the Ring symbol in which it is present a Path (pag.470)
To filter/sort the list of the Path (pag.470)
The Path terms indicates a bidirectional route between a source node and a destination node and is
identified by an input channel on the source node and an output channel on the destination node. For more
information refer to the Ring Manager documentation.
To display the list of the Path present in the Rings of the current map
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens, where the he list of the Path present in the Rings of the current
map is displayed (Fig.94).
Menu
bar (1)
Summarizing
bar of the
status (2)
Path list
(3)
Status
bar (4)
(1) Menu:
File > Save. It saves the list of the Path
File > Refresh. It updates the data present in the window.
File > Close. It closes the window.
Edit > Select All. It selects all the displayed Paths.
Edit > Delete Path. It deletes one or more Path from the list and database.
Edit > Delete Path Protection. It delete from the list and database, the protection of one or
more Paths.
Edit > Add Path Protection. It adds the protection to a Path.
Edit > Path on line. It activates the management of a Path.
Edit > Path off line. It deactivates the management of a Path.
Edit > Naming Switch A/B -> B/A. It switches the names of the Paths associated in a pro-
tection.
Fault > Current Alarm. It displays the alarms active in the equipment implementing a Path
and related to the Path.
Fault > Alarm History. It displays the history of the alarms relevant to the equipment imple-
menting a Path and related to a Path.
Options > Path: Information. It displays/modifies/saves the information relevant to a Path
Options > Path: Configuration Parameters. It displays/modifies the configuration of a Path.
Options > Path: Protection Parameters. It displays/modifies the configuration of a Path pro-
tected.
Options > Path: Highlight. It searches and highlights a Path in the Ring Manager window in
which it is contained.
Options > Ring: Highlight. It searches and highlights in the map window, the Ring symbol in
which it is present a Path.
View > Filter. It filters/sorts the list of the Path
(2) The name of each status a Path can assume (except for the status Disabled which is grouped to-
gether with the status Warning) is next to a box pointing out the number of Paths present in the list
with the specific status.
For each box, if the displayed number is 0, the box is grey. When the number is different from 0,
the background of the box assumes the color associated to the status.
For the description of the different statuses and relevant colours, see note (3).
The selection of a box allows filtering the list of Path using, as criterion, the selected status. When
the filter activated, the bar displays the Clear Severity Filter push-button. Selecting it, you can
remove the filter and display all the Paths in the list.
Path Name. Path name assigned by the user to the path during its creation or modification.
The user can assign to the Path the wished name or name the Path, according to Recc. ITU-
T M.1400, with the following format <logic address of source NE (max 12 characters)> -
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. To save to file:
A group of Paths, select the records and then the File > Save > Selected command.
The displayed Paths, select the File > Save > Filtered command. If no filter is active, the dis-
played records correspond to the records stored in the database.
The Save File window opens.
3. Type, in the Selection box, the path and the name of the file where the information must be saved.
4. Press Ok.
The files are saved in text format and can be opened using any text editor.
Operation available only to the Superuser and to the users with privileged or advanced profile.
It is not possible to delete:
A Path in Not Actuated status. Force the Path in Off line status or wait for the successful reali-
zation of the Path and then delete the Path.
A managed Path (On line), if the system has detected a condition of Configuration Mismatch.
First remove the mismatch condition (refer to Ring Manager manual) and then delete the Path.
A Path with at least one of the NEs implementing the Path in status disconnected, unreachable,
maintenance, connected with LCT present in Configuration modality or if a NMS5UX user has
opened the relevant equipment graphic interface (Equipment window). Force the Path in Off line
status or wait for all the equipment implementing the Path are in connected status and then de-
lete the Path.
The deletion of an unmanaged Path (Off line) involves the removal of the Path only from the DB of Ring
Manager, while the deletion of a managed Path (On line) involves the removal of the Path from the DB and
the removal of the relevant cross-connections from the equipment implementing the considered Path.
If a protected Path is selected, this operation deletes the whole Path (paths A and B).
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
Operation available only to the Superuser and to the users with privileged or advanced profile.
It is not possible to delete:
A route (A/B) of a Path in Not Actuated status. Force the Path in Off line status or wait for the
successful realization of the Path and then delete the protection.
A route (A/B) of a managed Path (On line) if the system has detected a condition of Configura-
tion Mismatch. First remove the mismatch condition (refer to Ring Manager documentation) and
then delete the protection.
A route (A/B) of a Path, if at least one of the NEs implementing the connection A or B is in status
disconnected, unreachable, maintenance, connected with LCT present in Configuration modality
or if a NMS5UX user has opened the relevant equipment graphic interface (Equipment window).
Force the Path in Off line status or wait for all the equipment implementing the route (A/B) are
in connected status and then delete the protection.
The deletion of a protection of an unmanaged Path (Off line) involves the removal of the Path only from
the database of Ring Manager, while the deletion of the protection of a managed Path (On line) involves
the removal of the protection from the DB and the removal of the relevant cross-connections from the
equipment implementing the considered protection.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
Operation available only to the Superuser and to the users with privileged or advanced profile.
The operation executed on a managed Path (On line) involves the creation of the protection in the database
of Ring Manager and the creation of the relevant cross-connections for the equipment implementing the
considered protection.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the Path you wish to protect (Protection option - Not protected value).
3. Select the Edit > Add Path Protection command and confirm.
If the operation is successful, the value Protected is displayed in the record of the considered Path (op-
tion Protection). If the operation fails, an error message is displayed.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the Path not managed (Path Status option - Off line value).
Operation available only to the Superuser and to the users with privileged or advanced profile.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the Path managed (Path Status option - Not Actuated, Failure, Incomplete, Degraded, Warning,
Disabled or Running value).
3. Select the Edit > Path off line command and confirm.
At the end of the operation, the Path is not managed by the system anymore (option Path Status -
value Off line).
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the protected Path (Protection option - Protected value) whose names of the two paths (A/B)
you wish to switch.
3. Select the Edit > Naming Switch A/B -> B/A command.
The path named A is renamed as B and vice versa.
To display the new situation, it is necessary to open the Ring Manager window containing the consid-
ered Path.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the Path(s) for which you wish to display the current alarms in the relevant equipment.
3. Select the Fault > Current Alarm command.
The RM - Current Alarm window opens (Fig.90) with Match Path filter active.
The description of the window and the operations that can be executed are reported to pag.443.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the Path(s) for which you wish to display the alarm history in the relevant equipment.
Operation available only to the Superuser and to the users with privileged, advanced or normal profile.
1. Select the Ring Manager > Locate > RM-Path Browser command.
To display the alarm history relevant to the equipment implementing the Path
Menu
bar (1)
Name of
the Path
(2)
Source and
destination
equipment
(3)
Type of
Path (4)
Description
of the Path
(5)
(1) Menu:
File > Save Path Information. It saves the characteristics of the Path.
File > Close. It closes the window.
Fault > Current Alarm. It displays the alarms active in the equipment implementing the Path.
Fault > Alarm History. It displays the history of the alarms relevant to the equipment imple-
menting the Path.
(2) Path name assigned by the user to the path during its creation or modification.
The user can assign the wished name to the Path or name the Path, according to the Recc. ITU-T
M.1400, using the following format <source NE logic address (max 12 characters)> - <destination
NE logic address (max 12 characters) <connection type>s<connection progressive number (max 2
characters)>.
(3) Option:
Source. Logical address of the source equipment of the Path and relevant input channel.
Destination. Logical address of the destination NE of the Path and relevant output channel.
The options are read only.
(5) Each record present in the list represents an equipment implementing the Path. For protected paths
in the list, the equipment implementing the PATH-A and the PATH-B are displayed.
For each equipment, it is displayed in the column:
Status. Status of creation of the cross-connection between input channel and output channel
on the equipment:
Actuated. Connection actuated.
Not Actuated. Connection not actuated yet.
Off line. Connection not managed (Path in Off line status).
Equipment. Logical address of the equipment.
In Channel. Input channel of the Path on the equipment.
Out Channel. Output channel of the Path on the equipment.
Message. This field displays, for the not actuated connections (option Status - value Not Ac-
tuated) the cause of the missed actuation:
Not Connected. Equipment in disconnected status.
Maintenance Status. Equipment in maintenance status.
Unreachable. Equipment in unreachable status
LCT in Configuration Mode. Equipment in connected status which the LCT program in
Configuration modality is connected to.
NMS5UX in Configuration Mode. Equipment for which the NMS5UX user has opened
the relevant equipment graphic interface (Equipment window).
Operation available only to the Superuser and to the users with privileged, advanced or normal profile.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the wished Path.
a. Into the Tributary Enable box, set the use of the tributary:
Disable. The tributary is not active (tributary not used). In this case, the alarms are inhi-
bited and LOS alarm becomes active if, with tributary disabled, the signal is however con-
nected.
Enable. The tributary is active (tributary used). In this case, the controller does not in-
hibit the alarms.
Disable No Inv. The tributary is not active (tributary not used). In this case, the alarms
are inhibited and LOS alarm is NOT given if, with tributary disabled, the signal is however
connected.
b. Press Apply.
At the end a message is displayed with the result of the operation.
a. Into the Trace Expected box, set the specification which the received Signal Label value is re-
ferred to.
b. Into the Trace Sent box, set the specification which the transmitted Signal Label value is referred
to.
c. Press Apply.
At the end a message is displayed with the result of the operation.
Menu
bar (1)
Characteristics Characteristics
of the Path of Path
source destination
equipment equipment (2)
(2)
Configuration
Configuration
parameters of
parameters
the tributary
of the tributary
channel
channel of
of output
input to
from the Path
the Path
destination
source
equipment
equipment (3)
(3)
Push-buttons
bar (4)
Fig.96 notes
(1) Menu:
File > Close. It closes the window.
(2) Option:
Source NE/Destination NE. Respectively source equipment/destination equipment of the
Path.
Channel. Tributary channel used.
NE Name. Logic address of the equipment.
NE Type. Equipment type.
The Virtual... label points out the virtual NE objects (Ring Manager).
IP Address. IP address.
The Virtual... label points out the virtual NE objects (NMS5UX-B).
IDU Type. IDU type (for example 2RU, etc.)
Configuration. Configuration type (for example Drop Insert, Terminal, etc.)
Capacity. Equipment capacity.
IDU Nb. Number of equipment constituting the node (only for NEs of ALplus Node type).
The list of displayed options depends on the equipment type.
J2 Path Trace
Trace Type. Path Trace status:
Disable. The control of the Path Trace is disabled.
Enable. The control of the Path Trace is enabled.
Trace Sent. Transmitted string of control characters
Trace Expected. The string of characters to be controlled in reception.
Signal Label
Trace Expected. Specification, which the received Signal Label value is referred to.
Trace Sent. Specification which the transmitted Signal Label value is referred to.
(4) Push-button:
Apply. It executes the changes made to the configuration parameters.
Refresh. It updates the data present in the window.
Cancel. It closes the window.
Operation available only to the Superuser and to the users with privileged, advanced or normal profile.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the Path protected (Protection option - Protected value).
To modify the management of the switching between the Path A and Path B
Operation of maintenance (MAN. OP).
a. In the Forced Switch box relevant to the wished equipment (source/destination), set:
Auto. The switching is automatically managed according to the presence of the alarms.
Force PATH-A. The equipment is forced to use the Path A for the service.
Force PATH-B. The equipment is forced to use the Path B for the service.
Menu
bar (1)
Logic
address
Logic address of the
of the source destination
NE NE
Push-buttons
bar (4)
Fig.97 notes
(1) Menu:
File > Close. It closes the window.
(2) Remember that the Path is a BIDIRECTIONAL route. In figure, for explanation clearness, we con-
sider an hypothetical route entering in the input channel of the source equipment and exiting from
the output channel of the destination equipment.
(3) The status of the switch is pointed out when the NE is connected to the management system.
(4) Push-button:
Apply. It applies the changes made to the configuration parameters.
Refresh. It updates the data present in the window.
(5) Value:
Not Revertive, without the presence of alarms (that cause the switching), the equipment
does not use a Path in a preferential manner with respect to the other one.
Revertive PATH-A, without the presence of alarms (that cause the switching), the equipment
use the Path A.
Revertive PATH-B, without the presence of alarms (that cause the switching), the equipment
use the Path-B.
(6) Value:
Auto. The switching is automatically managed according to the presence of the alarms.
Force PATH-A. The equipment is forced to use the Path A for the service.
Force PATH-B. The equipment is forced to use the Path B for the service.
To search and highlight a Path in the Ring Manager window in which it is con-
tained
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
To search and highlight in the map window, the Ring symbol in which it is
present a Path
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
2. Select the Path.
1. Select the Ring Manager > Locate > RM-Path Browser command.
The RM - Path Browser window opens (Fig.94).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the RM - Path Browser window only the record that satisfy specific criteria.
Each time that the list is filtered, all the records are considered, both the displayed and the hidden ones.
In the window there are also the Clear (it removes the activation of the filters and displays the com-
plete list) and Cancel (it closes the window and does not execute the operation) push-buttons.
When the RM - Path Browser window is closed, the possible activation of the filters is automatically
cleared.
The RM-Equipment Browser command displays the list of the equipment present in the Rings of the cur-
rent map.
With details it is possible:
To display the list of the equipment present in the Rings of the current map (pag.472)
To filter the equipment list (pag.473)
To search and highlight the equipment symbol in the relevant Ring Manager window (pag.474)
To display the list of the equipment present in the Rings of the current map
1. Select the Ring Manager > Locate > RM-Equipment Browser command.
The RM - Equipment Browser window opens where the list of the equipment present in the Rings of the
current map is displayed (Fig.98).
Menu
bar (1)
Equipment
list (2)
Status
bar (3)
Fig.98 notes
(1) Menu:
File > Refresh. It updates the data present in the window.
File > Close. It closes the window.
Options > Find equipment. It search and highlight the equipment symbol in the relevant Ring
Manager window.
View > Filter. It updates the information contained in the window.
The information corresponds to the characteristics/operating status of the equipment when the RM
- Equipment Browser window has been opened or updated.
The presence of the - symbol points out that the information is not available as not meaningful for
the status and/or the type of equipment, which is referred to.
A double click on an equipment record opens the Ring Manager window containing the equipment.
The equipment is highlighted in the Ring Manager window.
(3) Field:
xx of yy. Number of displayed records (xx) and number of total records (yy). If no filter is
active, the number of displayed records corresponds to the number of total records.
Filter. Activation of one or more filters.
Date and time when the window has been opened or updated.
1. Select the Ring Manager > Locate > RM-Equipment Browser command.
The RM - Equipment Browser window opens(Fig.98).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the RM - Equipment Browser window only the records that satisfy the activated
criteria.
Each time the list is filtered, all the records are considered, both the displayed and the hidden ones.
In the window there are also the Clear (it removes the activation of the filters and displays the com-
plete list) and Cancel (it closes the window and does not execute the operation) push-buttons.
When the RM - Equipment Browser window closes, the possible activation of filters is automatically de-
leted.
1. Select the Ring Manager > Locate > RM-Equipment Browser command.
The RM - Equipment Browser window opens (Fig.98).
The VLAN Manager menu is available only if the VLAN Manager application have been installed. For
the use of the VLAN Manager application refer to the specific documentation.
The VM-Add VLAN Map, VM-Delete VLAN Map and VM-Modify/View VLAN Map commands are used
to represent graphically the VLAN Map objects in the maps and to provide to NMS5UX-B system the pa-
rameters to manage and control them.
Before using them, it is suggested to read the Graphic network representation (pag.78) where the modal-
ities to configure correctly and rapidly one's supervision system are described.
The VLAN Map objects are used to identify subnetworks of radio equipment with Lan Ethernet tributaries
which implement virtual LAN paths (VLAN path).
Edit > VM-Add VLAN Map (pag.476). It creates VLAN Map objects for the graphic represen-
tation of the network in the map.
Edit > VM-Delete VLAN Map (pag.477). It deletes a VLAN Map symbol from the map.
Edit > VM-Modify/View VLAN Map (pag.478). It displays/modifies the characteristics of a
VLAN Map object.
Fault > VM-Network Alarm History (pag.479). It displays/manages the alarm history of the
equipment present in the VLAN Maps managed by the supervision system.
Fault > VM-Network Current Alarm (pag.486). It displays/manages the alarms active in the
equipment present in the VLAN Maps managed by the supervision system.
Fault > VM-Element Alarm History (pag.492). It displays/manages the alarm history of the
equipment present in the specific VLAN Map.
Fault > VM-Element Current Alarm (pag.493). It displays/manages the alarms active in the
equipment present in the specific VLAN Map.
Locate > VM-VLAN Map Browser (pag.494). It displays the list of the VLAN Maps managed
by the supervision system.
Locate > VM-Equipment Browser (pag.496). It displays the list of the equipment present in
the VLAN Maps of the current map.
The VM-Add VLAN Map command creates VLAN Map objects for the graphic representation of the network
in the map.
Before creating an object, it is suggested to read the par. Rules for the creation of the objects (pag.82).
1. In the UX Map Manager window, move to the point of the map (container or main window) where you
wish to create the VLAN Map.
2. Select the VLAN Manager > Edit > VM-Add VLAN Map command.
The Add VLAN Manager Map window opens.
3. Type the name of the VLAN Map (alphanumeric string of minimum 1 character and maximum 32 char-
acters) in the Label box.
The name will be displayed under the object symbol and will constitute the name of the window that is
opened at the double selection of the symbol.
4. In the Comment area, type possible information relevant to the object (max 100 characters).
The setting of this parameter is optional.
5. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The VLAN Map is displayed in the New Object Area of the UX Map Manager window (Fig.1). Move the
symbol in any point of the View area.
If the created VLAN Map symbol is already present in a map, it automatically will acquire the status and
the characteristics of the existing object.
The VM-Delete VLAN Map command deletes a VLAN Map symbol from the map.
If a VLAN Map object is present only in one map, can be deleted only if it does not contain objects
(equipment, Link, Vlan path, etc.)
If the same VLAN Map object is present in more maps, it is possible to delete the symbol even if it contains
objects, except for the last copy for which the above mentioned rule is valid: it can be deleted only if empty.
1. Into the UX Map Manager window select the VLAN Map object you wish to delete.
2. Select the VLAN Manager > Edit > VM-Delete VLAN Map command or press the right mouse button,
select Delete and confirm.
The object is removed from the map.
The VM-Modify/View VLAN Map command displays/modifies the characteristics of a VLAN Map object.
It is not possible to assign the same name to two different VLAN Map objects.
If the same VLAN Map object has been created into two different maps, at the changing of the parameter
values of such a VLAN Map object into a map, the system automatically changes the values of the param-
eters relevant to the same object into the other map.
1. Into the UX Map Manager window select the wished VLAN Map object.
2. Select the VLAN Manager > Edit > VM-Modify/View VLAN Map command or press the right mouse
button and select Modify/View.
The VLAN Manager Properties window opens.
Box/area:
Label. VLAN Map name.
Type. VLAN Map symbol.
Comment. Additional information.
It is possible to change the Label and Comment parameters. The setting mode of the parameters is the
same one pointed out to pag.476.
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
In the UX Map Manager window, the VLAN Map assumes the new characteristics.
The VM-Network Alarm History command displays/manages the history of the alarm/status/event sig-
nallings (alarms) stored in the VLAN Manager database, of the equipment present in the VLAN Maps man-
aged by the supervision system.
With details it is possible:
To display the alarm history of the equipment present in the VLAN Maps managed by the super-
vision system (pag.479)
To save the alarms list (pag.481)
To delete the alarms (pag.481)
To mark the alarms (pag.481)
To realign the alarm table of VLAN Manager to that of NMS5UX-B (pag.482).
To activate/deactivate the automatic updating of the data (pag.482)
To filter the alarms list (pag.482)
To sort the alarms list (pag.484)
To display the acknowledge information of an alarm (pag.484)
To display the alarm history of the equipment present in the VLAN Maps
managed by the supervision system
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens, where the alarm history stored in the VLAN Manager database,
of the equipment present in the VLAN Maps managed by the sNMS5UX-B is displayed (Fig.99).
At the opening of the window a filter is applied to the alarms list: only the alarms, whose detection
date is successive to the midnight of the current day, are displayed. Besides, by default, the automatic
updating of the information is inactive.
A warning message could be displayed, informing that the database contains a number of alarms great-
er than 5000.
For this cause, the window will display only the records, in chronological order from the newest to the
oldest one, until 5000.
The 5000 limit is not a memory limit, but simply a limit in the displaying of the alarms.
In order to read the alarms successive to 5000, it is sufficient to delete some records or modify the
filters.
Menu
bar (1)
Alarms
list (2)
Status
bar (3)
Fig.99 notes
(1) Menu:
File > Save. It saves to text file the alarms list.
File > Close. It closes the window.
Actions > Delete. It deletes one or more records from the list and database.
Actions > Acknowledge. It marks one or more records, in such a way that the system mem-
orizes that the user has seen the alarms.
Actions > Refresh. It updates the data present in the window.
Actions > Alarm Synchronization. It re-aligns the alarms table between NMS5UX-B and VLAN
Manager.
View > Filter. It filters the alarms list.
View > Sort Criteria. It sorts the list of records.
View > Acknowledge Information. It displays the acknowledge information of the alarms.
(2) For each alarm, it is displayed in the column:
Severity. Type of signalling: alarm, status and event and if the signalling has been detected
or is cleared; for the alarms also the severity is displayed.
The parameter is represented by a coloured box and by a wording, in detail:
Background colour Wording Description
Green Normal Detected event signalling
Blue Status Detected status signalling
Light blue Warning Detected alarm with Warning severity
Yellow Minor Detected alarm with Minor severity
Orange Major Detected alarm with Major severity
Red Critical Detected alarm with Critical severity
No background Normal Cleared event signalling
No background Status Cleared status signalling
No background Warning Cleared alarm with Warning severity
No background Minor Cleared alarm with Minor severity
No background Major Cleared alarm with Major severity
No background Critical Cleared alarm with Critical severity
Ack. Marking status of the record. If the field is empty, the alarm has not been marked. If
the X character is present the record has been marked.
Each alarm can be acknowledged twice: the first time when the alarm is detected. When the
alarm clears, the character X is removed from the record and the user can acknowledge it
the second time.
In any moment, it is possible to display the acknowledge information of an alarm moving to
the record and pressing the right mouse button. A pop-up window is displayed with the detail
of the acknowledge. The content of the window is the same described at pag.484.
SET Date/Time. Date and time of the alarm detection.
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens (Fig.99).
2. To save to a file:
A group of alarms, select the records and then the File > Save > Selected command.
The displayed alarms, select the File > Save > Filtered command. If no filter is active, the
displayed records correspond to the records stored in the database.
The Save File window opens.
3. Type, in the Selection box, the path and the name of the file where the information must be saved.
4. Press Ok.
The files are saved in text format and can be opened using any text editor.
Operation available only to the Superuser and to the users with privileged or advanced profile.
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens (Fig.99).
2. To delete from the list and from the database of supervision system:
A group of alarms, select the records and the Actions > Delete > Selected Alarms command.
The displayed alarms, select the Actions > Delete > Filtered Alarms command. If the filters
are not active, the displayed records correspond to the records stored in the database.
All the alarms of the database, select the Actions > Delete > All Alarms command.
The records are deleted.
Operation available only to the Superuser and to the users with privileged or advanced profile.
After a record has been marked, the operation cannot be undone.
Each alarm can be acknowledged twice: the first time when the alarm is detected. When the alarm clears,
the character X is removed from the record and the user can acknowledge it the second time. In this second
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens (Fig.99).
2. To mark:
A group of alarms, select the records and then the Actions > Acknowledge > Selected
Alarms command.
The displayed alarms, select the Actions > Acknowledge > Filtered Alarms command. If the
filters are not active, the displayed records correspond to the records stored in the database.
All the alarms of the database, select the Actions > Acknowledge > All Alarms command.
The Acknowledge Alarm window opens.
The User box displays the username of the NMS5UX user who required the marking of the records. The
value of the box is automatically set to the username of the NMS5UX user who opened the map. The
value cannot be changed.
3. Type in the Trouble Identification Code box a code identifying the records (alphanumeric string of max
15 characters); it can be used later as search criterion.
The setting of this parameter is optional.
4. Type in the Comment box some additional information (alphanumeric string of max 500 characters).
The setting of this parameter is optional.
5. Press Ok.
The record will be marked with the letter X.
If more records are selected for the operation, the setting of the Trouble Identification Code and Com-
ment parameters are for all the records.
If one or more detected and cleared alarms are selected, the setting of the Trouble Identification Code
and Comment parameters applies both for the set event (SET) and for the clear event (CLEAR).
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens (Fig.99).
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens (Fig.99).
At the opening of the window, by default, the automatic updating of the information is inactive.
3. To deactivate again the automatic updating of the data, select the symbol.
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens (Fig.99).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the VM - Alarm History window only the record that satisfy specific criteria.
Each time that the list is filtered, all the records are considered, both the displayed and the hidden ones.
When the VM - Alarm History window is closed, the possible activation of the filters is automatically
cleared.
In the window, there are the push-buttons:
Save.... It saves the set criteria to a file.
On the choice of the push-button, the Save Filter window opens.
Type the name you wish to assign to the file in the Selection box and press OK.
Load.... It opens the file, where a previously saved specific setting of filters is contained.
On the choice of the push-button, the Load Filter window opens.
Select the wished file in the Files list and press OK.
Delete....It deletes the file where a previously saved specific setting of filters is contained.
On the choice of the push-button, the Delete Filter window opens.
Select the wished file in the Files list and press OK.
Clear. It clears the activation of all the filters.
Cancel. It closes the window and does not execute the operation.
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens (Fig.99).
6. Press OK (it executes the sorting and closes the window) or Apply (it executes the sorting and does
not close the window).
The VM - Alarm History window will list the records in the set order.
1. Select the VLAN Manager > Fault > VM-Network Alarm History command.
The VM - Alarm History window opens (Fig.99).
2. Select the record which you wish to display the detail of the acknowledge for.
Identification
Code
(1)
Detailed
Detailed information
information of the
of the acknowledge
acknowledge when the signal
when the signal was in status:
was in status: detected and
detected cleared
(2) (3) (2) (3)
Fig.100 notes
(1) Identification code of the record assigned by the user during the alarm acknowledge.
(2) Option:
User. Username of the NMS5UX user who executed the acknowledgement of the record.
Time. Moment when the record has been acknowledged <day-month-year hour:min-
utes:seconds>.
Comment. Additional information.
(3) If the alarm has been acknowledged the first time when it was in detected-cleared status, the data
present in the SET:... and CLEAR:... areas are the same.
The information present in the VM - Alarm History window are dynamically updated only if the procedure
for the automatic updating is active (pag.482).
At the opening of the VM - Alarm History window, the procedure of automatic updating of the informa-
tion is, by default inactive (the default setting can be modified by the Superuser).
The setting of the filters or the criteria used to sort the records in a VM - Alarm History window does not
influence the displaying of the information in the other open VM - Alarm History windows or in the VM -
Current Alarms window.
The alarms are stored in the database managed by VLAN Manager application (database of VLAN Manager).
The application stores to disk all the alarms up to a limit N (configurable by Superuser - default 50000).
When this limit is reached, the system automatically removes the oldest X alarms (X configurable by Su-
peruser - default 1000).
During this period, it is possible to manually delete the alarms (pag.481). It is suggested to periodically
delete and/or store to file the less meaningful records, so to avoid the saturation of the database.
As help to the description of the command, see par. Modality of the updating of data (pag.491)
To display the alarms active in the equipment present in the VLAN Maps
managed by the supervision system
1. Select the VLAN Manager > Fault > VM-Network Current Alarm command.
The VM - Current Alarms window opens, where the list of the alarms active in the equipment present
in the VLAN Maps managed by the supervision system is displayed (Fig.101).
At the opening of the window, by default, the automatic updating of the information is inactive.
Menu
bar (1)
Alarms
list (2)
Status
bar (3)
Fig.101 notes
(1) Menu:
File > Save. It saves to text file the alarms list.
File > Close. It closes the window.
1. Select the VLAN Manager > Fault > VM-Network Current Alarm command.
The VM - Current Alarms window opens (Fig.101).
2. To save to file:
A group of alarms, select the records and then the File > Save > Selected command.
The displayed alarms, select the File > Save > Filtered command. If filters are not active, the
displayed records corresponds to the records stored in the database.
The Save File window opens.
3. Type, in the Selection box, the path and the name of the file where the information must be saved.
4. Press Ok.
The files are saved in text format and can be opened using any text editor.
1. Select the VLAN Manager > Fault > VM-Network Current Alarm command.
The VM - Current Alarms window opens (Fig.101).
2. To mark:
A group of alarms, select the records and then the Actions > Acknowledge > Selected
Alarms command.
The displayed alarms, select the Actions > Acknowledge > Filtered Alarms command. If fil-
ters are not active, the displayed records correspond to the records stored in the database.
All the alarms of the database, select the Actions > Acknowledge > All Alarms command.
The Acknowledge Alarm window opens.
The User box displays the username of the NMS5UX user who required the marking of the records. The
value of the box is automatically set to the username of the NMS5UX user who opened the map. The
value cannot be changed.
3. Type in the Trouble Identification Code box a code identifying the records (alphanumeric string of max
15 characters); it can be used later as search criterion.
The setting of this parameter is optional.
4. Type in the Comment box some additional information (alphanumeric string of max 500 characters).
The setting of this parameter is optional.
5. Press Ok.
The record will be marked with the letter X.
If more records are selected for the operation, the settings of the Trouble Identification Code and Com-
ment parameters applies for all the records.
1. Select the VLAN Manager > Fault > VM-Network Current Alarm command.
The VM - Current Alarms window opens (Fig.101).
2. Select the Actions > Alarm Synchronization command.
The information present in the database of VLAN Manager and relevant to the alarms are realigned to
that present in the database of NMS5UX-B.
1. Select the VLAN Manager > Fault > VM-Network Current Alarm command.
The VM - Current Alarms window opens (Fig.101).
At the opening of the window, by default, the automatic updating of the information is inactive.
3. To deactivate again the automatic updating of the data, select the symbol.
1. Select the VLAN Manager > Fault > VM-Network Current Alarm command.
The VM - Current Alarms window opens (Fig.101).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the VM - Current Alarms window only the record that satisfy specific criteria.
Each time that the list is filtered, all the records are considered, both the displayed and the hidden ones.
When the VM - Current Alarm window is closed, the possible activation of the filters is automatically
cleared.
1. Select the VLAN Manager > Fault > VM-Network Current Alarm command.
The VM - Current Alarms window opens (Fig.101).
5. If you wish that the alarms are sorted also according to their address, activate the Group Equipment
box (second sorting criterion).
6. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The VM - Current Alarms window will list the records in the set order.
1. Select the VLAN Manager > Fault > VM-Network Current Alarm command.
The VM - Current Alarms window opens (Fig.101).
2. Select the record which you wish to display the detail of the acknowledge for.
Identification
Code
(1)
Fig.102 notes
(1) Identification code of the record assigned by the user during the alarm acknowledge.
(2) Option:
User. Username of the NMS5UX user who executed the acknowledgement of the record.
Time. Moment when the record has been acknowledged <day-month-year hour:min-
utes:seconds>.
Comment. Additional information.
The information present in the VM - Current Alarm window are dynamically updated only if the procedure
for the automatic updating is active (pag.488).
At the opening of the VM - Current Alarm window, the procedure of automatic updating of the informa-
tion is, by default inactive (the default setting can be modified by the Superuser).
The VM-Element Alarm History command displays/manages the history of the alarm/status/event sig-
nallings (alarms) stored in the VLAN Manager database, relevant the equipment present ONLY to the se-
lected VLAN Map.
The choice of the command opens the <VLAN Map name> Alarm History window.
The description of the window and the operations that can be executed are the same reported in the
par. VM-Network Alarm History (pag.479).
The VM-Element Alarm History command is available only if it has been selected a single VLAN Map in
the UX Map Manager window.
The choice of the command opens the <VLAN Map name> Current Alarm window.
The description of the window and the operations that can be executed are the same reported in the
par. VM-Network Current Alarm (pag.486).
The VM-Element Current Alarm command is available only if it has been selected a single VLAN Map in
the UX Map Manager window.
The VM-VLAN Map Browser displays the list of the VLAN Maps managed by the NMS5UX-B.
1. Select the VLAN Manager > Locate > VM-VLAN Map Browser command.
The VLAN Map Browser window opens, where the list of the VLAN Maps managed by the supervision
system NMS5UX-B is displayed (Fig.103).
Menu
bar (1)
VLAN Map
list (2)
Status
bar (3)
Fig.103 notes
(1) Menu:
File > Refresh. It updates the data present in the window.
File > Close. It closes the window.
Options > Find VLAN Map. It searches and highlights in the map the symbol of a VLAN Map
Options > Open VLAN Map. It opens the VLAN Manager Map window.
(2) For each VLAN Map the name corresponding to the name of the relevant VLAN Map symbol in the
map is pointed out.
The list of the VLAN Map is in alphabetical order.
(3) Field:
VLAN Map Nb: xx of yy. Number of displayed records (xx) and number of total records (yy).
If no filter is active, the number of displayed records corresponds to the number of total
records.
Filter. Box for the activation of the filter (see pag.495).
1. Select the VLAN Manager > Locate > VM-VLAN Map Browser command.
The VLAN Map Browser window opens (Fig.103).
1. Select the VLAN Manager > Locate > VM-VLAN Map Browser command.
The VLAN Map Browser window opens (Fig.103).
1. Select the VLAN Manager > Locate > VM-VLAN Map Browser command.
The VLAN Map Browser window opens (Fig.103).
2. Type the letters/numbers present in the name of the wished VLAN Map objects in the text box (status
bar).
3. Press Filter.
The VLAN Map Browser window displayed only the VLAN Map whose name contains the set letters/num-
bers.
The VM-Equipment Browser command displays the list of the equipment present in the VLAN Maps of
the current map.
With details it is possible:
To display the list of the equipment present in the VLAN Maps of the current map (pag.496)
To filter the equipment list (pag.497)
To search and highlight the equipment symbol in the relevant VLAN Manager Map window
(pag.498)
To display the list of the equipment present in the VLAN Maps of the current
map
1. Select the VLAN Manager > Locate > VM-Equipment Browser command.
The VM - Equipment Browser window opens where the list of the equipment present in the VLAN Maps
of the current map is displayed (Fig.104).
Menu
bar (1)
Equipment
list (2)
Status
bar (3)
Fig.104 notes
(1) Menu:
File > Refresh. It updates the data present in the window.
File > Close. It closes the window.
Options > Find equipment. It search and highlight the equipment symbol in the relevant
VLAN Manager Map window.
View > Filter. It updates the information contained in the window.
The information corresponds to the characteristics/operating status of the equipment when the VM
- Equipment Browser window has been opened or updated.
The presence of the - symbol points out that the information is not available as not meaningful for
the status and/or the type of equipment, which is referred to.
A double click on an equipment record opens the VLAN Manager Map window containing the equip-
ment.
(3) Field:
xx of yy. Number of displayed records (xx) and number of total records (yy). If no filter is
active, the number of displayed records corresponds to the number of total records.
Filter. Activation of one or more filters.
Date and time when the window has been opened or updated.
1. Select the VLAN Manager > Locate > VM-Equipment Browser command.
The VM - Equipment Browser window opens(Fig.104).
3. Press OK (it executes the command and closes the window) or Apply (it executes the command and
does not close the window).
The system displays in the VM - Equipment Browser window only the records that satisfy the activated
criteria.
Each time the list is filtered, all the records are considered, both the displayed and the hidden ones.
In the window there are also the Clear (it removes the activation of the filters and displays the com-
plete list) and Cancel (it closes the window and does not execute the operation) push-buttons.
When the VM - Equipment Browser window closes, the possible activation of filters is automatically de-
leted.
1. Select the VLAN Manager > Locate > VM-Equipment Browser command.
The VM - Equipment Browser window opens (Fig.104).
About NMS5UX-B (pag.500). It displays the version of the NMS5UX-B system present on one's
machine.
License Information (pag.501). It displays the details of the codewords relevant to its own
supervisory system.
Display Legend (pag.502). It displays the legend of the colours which the objects present in
the UX Map Manager window can assume.
NMS5UX Software Module (pag.503). It displays the list of the programs that constitute the
NMS5UX-B software package.
System Administrator (pag.505). It opens the NMS5UX-B system administrator manual.
Overview (pag.506). It opens the NMS5UX-B user manual.
Manager (pag.507). It opens the equipment user manual.
The About NMS5UX-B command displays the version of the NMS5UX-B system present on one's machine.
The License Information command displays the details of the codewords relevant to its own supervisory
system.
To display the detail of the codewords relevant to its own supervisory sys-
tem
The Display Legend command displays the legend of the colours which the objects present in the UX Map
Manager window can assume.
To display the legend of the colours which the objects can assume
The NMS5UX Software Module command displays the list of the programs that constitute the NMS5UX-
B software package.
With details it is possible:
To verify the list of the programs that constitute the NMS5UX-B software package (pag.503)
To print the programs list (pag.504).
To end possible processes, relevant only to the Legacy equipment that have remained appended
(pag.504)
To verify the list of the programs that constitute the NMS5UX-B software
package
Menu
bar (1)
Programs
list (2)
Fig.105 notes
(1) Menu:
File > Print. It prints the content of the widow on the default printer.
File > Exit. It closes the window.
Command > Check legacy processes. It allows ending possible processes, relevant only to
the Legacy equipment that have remained appended.
(2) Column:
Program. Program name.
Version. Program version.
Dimension. Program dimensions expressed through byte.
Date. Issuing date of the program.
Path. Program path on the server/workstation.
To end possible processes, relevant only to the Legacy equipment that have
remained appended
The System Administrator command opens the NMS5UX-B system administrator manual.
The <equipment type> Manager command opens the user manual relevant to the specific equipment
type.
In the Help menu, only the manuals of the equipment managed by one's NMS5UX-B will be available.
Tab.16 points out the menus and the commands present in the UX Map Manager window (Fig.1).
For each command, the access to the map and the user profile necessary for the availability of the com-
mand in the window, are reported. In detail
The list of the menus/commands in table is the DEFAULT one present at the installation of the NMS5UX-
B system. The list can be configured by the Superuser. For more information refer to NMS5UX Administra-
tor Manual.
Some commands are optional ones. Then, such commands can be absent into the specific menu of its own
NMS5UX-B system.
Container RW SPA
SNMP Managed
RW SPA
(Virtual)
Network
Element Legacy Protocol
RW SPA
Managed 2
Add
Legacy Protocol
2 RW SPA
Managed (Virtual)
Link RW SPA
Label RW SPA
Delete RW SPA
Edit Network Element RO 3 RW 4 NE 3 SPA 4
3 4 3 4
Container RO RW NE SPA
Modify/View Generic Symbol 3 4 3 4
RO RW NE SPA
3 4 3 4
Link RO RW NE SPA
3 4 3 4
Label RO RW NE SPA
Information RO/RW SPANE
13 The privileged, advanced, normal and entry users can only modify one's password.
14 The Action > Force Logout and Action > Forced Exit commands are available only to Superuser.
15 The Action > Force Logout command is not available to the normal and entry user.
16 The activation of the Delete Table box is available only to Superuser.
17 Menu present only if installed the modules for the management of the Ring Manager application.
18 Menu present only if installed the modules for the management of the VLAN Manager application.
19 The Path: Information, Path: Configuration Parameters and Path: Protection Parameters
commands are not available to entry users.
The Delete Path, Delete Path Protection, Add Path Protection, Path on line and Path off line are
not available to normal and entry users.
12
Alarm Notification via e-mail RO/RW SPANE
14
NMS5UX Logged Users RO/RW SPANE
10
RM-Network Alarm History RO/RW SPANE
RM-Network Current Alarm RO/RW SPANE
A
Acknowledge an operator and re-enable him to receive e-mail (entry, normal, advanced,
privileged user) (Alarm Notification via e-mail) ...........................................................................317
Acknowledge an operator and re-enable him to receive e-mail (Superuser) (Alarm Notification
via e-mail) ............................................................................................................................315
Acquire the configuration of one or more equipment ........................................................... 236, 254
Acquire the configuration of the equipment of one or more containers ...........................................254
Activate a measure (SNMP-NE Monitoring) .................................................................................323
Activate an Ethernet port for the count of the history of the RMON statistics ...................................345
Activate an Ethernet port for the count of the RMON statistics ......................................................339
Activate at the same time one or more PM measures for one or more equipment of the same type ....183
Activate the management of a Path ..........................................................................................462
Activate/deactivate an operator (Alarm Notification via e-mail) .....................................................315
Activate/deactivate one or more PM measures at the same time ...................................................230
Activate/deactivate the automatic updating of the data (Network Alarm History) .............................268
Activate/deactivate the automatic updating of the data (Network Current Alarms) ..........................275
Activate/deactivate the automatic updating of the data (RM-Network Alarm History) .......................438
Activate/deactivate the automatic updating of the data (RM-Network Current Alarm) ......................445
Activate/deactivate the automatic updating of the data (VM-Network Alarm History) .......................482
Activate/deactivate the automatic updating of the data (VM-Network Current Alarm) ......................488
Activate/deactivate the tributary (Path Browser) .........................................................................466
Activate/deactivate the tributary loops (Path Browser) ................................................................466
Add a new LCT user ................................................................................................................386
Add a NMS5UX user ................................................................................................................374
Add a NMS5UX user (manual login to UX Map Manager window - active) ........................................376
Add a station to the remote equipment list ................................................................................391
Add an equipment to the remote equipment list .........................................................................392
Add an operator (Alarm Notification via e-mail) ..........................................................................313
Add more equipment at the same time to the remote equipment list .............................................394
Add the protection to a Path ....................................................................................................462
Add/modify/delete the informative notes of a NE symbol .............................................................161
Add/remove a prefix to the logical address of an equipment .........................................................227
Align the symbols ...................................................................................................................164
Assign the parameters to monitor to an equipment (create a measure) (SNMP-NE Monitoring) .........322
Associate/remove the background to a container ........................................................................139
B
Backup the alarm history .........................................................................................................423
C
Capture the RMON statistics of an Ethernet port in a specific instant ..............................................340
Change the name of the Path (Path Browser) .............................................................................464
Check the database information necessary to the RAN .................................................................165
Close the open map and opening another one ............................................................................145
Close the UX Map Manager window ...........................................................................................147
Compare the objects of a map/container with the objects of a different map/container ....................143
D
Deactivate a measure (SNMP-NE Monitoring) .............................................................................323
Deactivate an Ethernet port from the count of the history of the RMON statistics ............................345
Deactivate an Ethernet port from the count of the RMON statistics ................................................340
Deactivate at the same time one or more PM measures for one or more equipment of the same type 183
Deactivate the management of a Path .......................................................................................463
Deactivate the NE Wake Up modality ........................................................................................333
Deactivate the Network Scan modality ......................................................................................332
Deactivate the periodic saving of the data to file (SNMP-HW Inventory) .........................................212
Default Gateway (NE SNMP)
Delete ..............................................................................................................................207
Display .................................................................................................................... 202, 205
Set, modify ......................................................................................................................207
Delete a Command Log (SNMP equipment) ................................................................................294
Delete a file (SNMP-NE Monitoring) ...........................................................................................325
Delete a LCT user ...................................................................................................................387
Delete a map .........................................................................................................................146
Delete a measure (SNMP-NE Monitoring) ...................................................................................323
Delete a NE Log (SNMP equipment) ..........................................................................................289
Delete a NMS5UX user ............................................................................................................375
Delete a Ring object from the map ...........................................................................................433
Delete a station from the remote equipment list .........................................................................392
Delete a VLAN Map object from the map ....................................................................................477
Delete all the Command Logs of a SNMP equipment ....................................................................294
Delete all the NE Logs of a SNMP equipment ..............................................................................289
Delete an equipment from the remote equipment list ..................................................................396
Delete an object ...................................................................................................................... 36
E
Enable and define the criteria for the activation/deactivation of an alarm relevant to a counter
(RMON statistics) ...................................................................................................................346
Enable/disable the alarms and to send of the traps and/or to modify the local severity
of the alarms of a SNMP equipment ..........................................................................................371
End possible processes, relevant only to the Legacy equipment that have remained appended ..........504
Execute series of SNMP commands stored on file ........................................................................318
Execute the Line Test for one or more equipment .......................................................................242
Execute the Line Test for the equipment of one or more containers ...............................................242
Execute the Ping of a SNMP equipment ............................................................................. 202, 249
F
Filter the alarms (SNMP-Event Statistics) ...................................................................................303
Filter the alarms list (Alarm Summary) ......................................................................................297
Filter the alarms list (Network Alarm History) .............................................................................269
Filter the alarms list (Network Current Alarms) ...........................................................................276
Filter the alarms list (Old Alarm History) ....................................................................................281
Filter the alarms list (RM-Network Alarm History) .......................................................................439
Filter the alarms list (RM-Network Alarm Summary) ....................................................................450
Filter the alarms list (RM-Network Current Alarm) .......................................................................445
Filter the alarms list (SNMP-Equipment Severity Code) ................................................................372
Filter the alarms list (VM-Network Alarm History) .......................................................................482
Filter the alarms list (VM-Network Current Alarm) .......................................................................488
Filter the equipment list (RM-Equipment Browser) ......................................................................473
Filter the equipment list (VM-Equipment Browser) ......................................................................497
Filter the list of operation (Transaction Log) ...............................................................................307
Filter the list of the VLAN Map ..................................................................................................495
Filter the NMS5UX users list (NMS5UX Logged Users) ..................................................................381
Filter the NMS5UX-B applications list (NMS5UX Logged Users) ......................................................383
Filter/order the list of the equipment/units (SNMP-Equipment Port Configuration) ...........................202
Filter/order the list of the equipment/units (SNMP-Software Inventory) .........................................198
Filter/order the list of the objects (Legacy-Hw/Sw Edition Inventory) .............................................189
Filter/order the list of the objects (Legacy-Physical Unit Inventory) ...............................................193
Filter/sort the list of equipment (Equipment List Locate) ..............................................................225
Filter/sort the list of the Path ...................................................................................................470
Filter/sort the list of the scheduled equipment (SNMP-Scheduled Sw Dwl Status) ............................408
Force the closure of an NMS5UX-B application ............................................................................383
Force the disconnection (logout) of a LCT user ...........................................................................389
Force the disconnection (logout) of a NMS5UX user .....................................................................381
Force the software disconnection of one or more SNMP equipment ................................................248
H
Highlight in the map the symbol of an equipment (Network Alarm History) ....................................270
Highlight in the map the symbol of an equipment (Network Current Alarms) ..................................277
Highlight in the map the symbol of an equipment (Old Alarm History) ...........................................283
L
Lock/unlock a backup file ........................................................................................................216
M
Mark the alarms (Network Alarm History) ..................................................................................267
Mark the alarms (Network Current Alarms) ................................................................................275
Mark the alarms (RM-Network Alarm History) .............................................................................438
Mark the alarms (RM-Network Current Alarm) ............................................................................445
Mark the alarms (VM-Network Alarm History) .............................................................................481
Mark the alarms (VM-Network Current Alarm) ............................................................................488
Modality of recording of the alarms ...........................................................................................272
Modality of recording of the alarms (RM-Alarm History window) ....................................................442
Modality of recording of the alarms (VM-Alarm History window) ....................................................485
Modality of the updating of data (RM-Alarm History window) ........................................................442
N
Network severity of the alarms relevant to a specific SNMP equipment type
Modify .............................................................................................................................369
Verify ..............................................................................................................................368
O
Open the equipment window ............................................................................................ 197, 226
Open the file, where a previously saved specific setting of filters is contained (RM-Network
Alarm Summary) ....................................................................................................................452
Open the Ring Manager window ...............................................................................................458
Open the VLAN Manager Map window ........................................................................................495
P
PPP communication ports (NE SNMP)
Display .................................................................................................................... 201, 204
Print the list of programs (NMS5UX Software module) .................................................................504
R
Realign the alarm table of Ring Manager to that of NMS5UX-B (RM-Network Alarm History) .............438
Realign the alarm table of Ring Manager to that of NMS5UX-B (RM-Network Current Alarm) .............445
Realign the alarm table of VLAN Manager to that of NMS5UX-B (VM-Network Alarm History) ............482
Realign the alarm table of VLAN Manager to that of NMS5UX-B (VM-Network Current Alarm) ............488
Re-align the alarms of one or more equipment ................................................................... 235, 252
Re-align the alarms of the equipment of one or more containers ...................................................252
Re-execute the software update (SNMP-Scheduled Sw Dwl Status) ...............................................406
Rename a station of the remote equipment list ...........................................................................392
Require the closure of an NMS5UX-B application .........................................................................383
Require the disconnection (logout) of a NMS5UX user .................................................................380
Require the updating of the data to the controller of an equipment ...............................................198
Reset and connect one or more Legacy equipment ....................................................... 202, 237, 250
S
Save a given Auto Discovery configuration to file ........................................................................333
Save on file the characteristics of the Path (Path Browser) ...........................................................464
Save on file the results of the PM measures of one or more equipment of the same type .......... 179, 229
Save periodically the data to file (SNMP-HW Inventory) ...............................................................212
Save the alarms list (RM-Network Alarm History) ........................................................................437
Save the alarms list (RM-Network Current Alarm) .......................................................................444
Save the alarms list (VM-Network Alarm History) ........................................................................481
Save the alarms list (VM-Network Current Alarm) .......................................................................487
Save the data to file (SNMP-HW Inventory) ...............................................................................211
Save the database (backup) ....................................................................................................429
Save the equipment configuration to a file (configuration backup) .................................................216
Save the history of the RMON statistics of an Ethernet port ..........................................................345
Save the list of the Path ..........................................................................................................461
Save the list of the scheduled equipment (SNMP-Scheduled Sw Dwl Status) ...................................406
Save the objects of a map/container to a file .............................................................................142
Save the PM measures (backup) ..............................................................................................426
Save the results of a measure (SNMP-NE Monitoring) ..................................................................324
Save the results of a measure stored into a file (SNMP-NE Monitoring) ..........................................325
Save the RMON statistics of an Ethernet port captured in a specific instant to file ............................341
Save the set filters to a file (RM-Network Alarm Summary) ..........................................................452
Save to a file the remote equipment list ....................................................................................397
Save to file or print the conformity certificate of a radio ...............................................................187
Save/print the alarms list (Network Alarm History) .....................................................................266
Save/print the alarms list (Network Current Alarms) ...................................................................275
Save/print the alarms list (Old Alarm History) ............................................................................281
Save/print the list of equipment (Equipment List Locate) .............................................................224
Save/print the list of operations (Transaction Log) ......................................................................306
Save/print the list of the equipment/units (SNMP-Software Inventory) ..........................................196
Save/print the list of the objects (Legacy-Hw/Sw Edition Inventory) ..............................................189
Save/print the list of the objects (Legacy-Physical Unit Inventory) ................................................192
Search a symbol in the map ....................................................................................................163
Search an equipment in the Auto Discovery table .......................................................................335
Search and highlight a Path in the Ring Manager window in which it is contained ............................470
Search and highlight in the map the symbol of a Ring .................................................................458
Search and highlight in the map the symbol of a VLAN Map .........................................................495
Search and highlight the equipment symbol in the relevant Ring Manager window ..........................474
Search and highlight the equipment symbol in the relevant VLAN Manager Map window ...................498
Send a message to one or all the NMS5UX users ........................................................................381
Set the automatic updating of the data (Alarm Summary) ...........................................................299
Set the execution parameters and activate the NE Wake Up modality ............................................332
T
Transfer the configuration of a SNMP equipment (virtual or real) to one or more real SNMP
equipment .............................................................................................................................256
Transfer the configuration of a SNMP equipment (virtual or real) to one or more virtual SNMP
equipment .............................................................................................................................258
Transfer the configuration of an equipment to another equipment of the same type ........................236
Transfer the configuration present into a backup file to an equipment (configuration restore) ...........216
Transfer to the PMP the default table of the alarms .....................................................................262
U
Update the equipment software (FAMxc) ........................................................................... 231, 412
Update the equipment software (Legacy) ...................................................................................418
Update the equipment software (SNMP) .............................................................. 197, 230, 400, 410
Update the results of the PM measures of an equipment ..............................................................172
Update the UX Map Manager window ........................................................................................137
Update the WEB LCT application ...............................................................................................402
V
Verify in which map the symbol of an equipment is present ..........................................................227
Verify the alarms characteristics (status, sending status of the trap, local severity) of a SNMP
equipment .............................................................................................................................370
Verify the characteristics and the functional status of an equipment ..............................................185
Verify the configuration/functional status of an equipment ............................................ 197, 271, 278
Verify the configuration/operating status of an equipment ...........................................................226
Verify the enabling and the criteria for the activation/deactivation of alarms relevant to
a counter (RMON statistics) .....................................................................................................346
Verify the graphic parameters assigned by the system to the symbol ............................................162
Verify the hardware and software version of the objects relevant to the Legacy equipment
present into the open map .......................................................................................................188
Verify the information (marking status of the alarms, of the signalling of LCT presence,
Incorrect Upload and the notes) of a symbol ..............................................................................160
Verify the LCT/NMS5UX users connected to an equipment ...........................................................233
Verify the list of the programs that constitute the NMS5UX-B software package ..............................503
Verify the marking status of the alarms, of the signalling of LCT presence and Incorrect Upload
of an equipment .....................................................................................................................226
Verify the objects list of the Legacy equipment present into the open map .....................................191
Verify the operating status of the PM measure points of one or more NEs of the same type ..............181
Verify the reach ability of the equipment (Line Test) ...................................................................234
X
XML
Convert a XML file into a HTML file .......................................................................................358
Create a cronjob ...............................................................................................................356
Delete one or more cronjob ................................................................................................356
Delete one or more XML, Log or HTML files ...........................................................................360
Display the active cronjobs .................................................................................................355
Display the content of a XML, Log or HTML file ......................................................................358
Display the list of HTML files obtained from the conversion of XML files .....................................358
Display the list of the Log files relevant to the creation of XML files ..........................................357
Display the list of the XML files present in a given directory .....................................................356
Save the complete equipment configuration into a file ............................................................353
To send email with one or more XML, Log or HTML files in attachment ......................................360
For more information, refer to the section relevant to the technical support on the Internet site of the com-
pany manufacturing the product.