Network Management has to bring to the Customers the most
global view of their network. It is becoming a key to successful use of
large telecommunication networks. By ensuring that critical service information
is always available, Network Management Platforms are becoming powerful
tools to evaluate the real time service level offered to the users. They
also have to drive the operators on reductions in operational costs.
IONOS NMS is the Network Management Platform designed
by SAGEM SA to provide Network Element configuration, real time alarm
monitoring, centralised access to all troubleshooting and Network Management
functions for all SAGEM products. SDH products but also DWDM, SHDSL, FMX,
Microwaves and other SAGEM equipment.
It has been designed such as :
• to offer to the customers, carriers and private companies the
best service level with automated supervision
• to provision Services (Ethernet point to point for example, VLAN
• to reduce the required skills of the operator personal by improving
the management of network services
• to follow the next expansion of the customer’s network with
a scalable architecture using truly distributed , client-server technology
• to facilitate the integration into the customer’s own management
platform by integrating open interfaces
The global structure of IONOS NMS is given below :
1.1. PRODUCT OVERVIEW
Ease of use
IONOS NMS is a graphical, end-to-end network
management application for configuring,
monitoring and controlling a SAGEM network infrastructure equipment.
With a comprehensive suite of Network Management tools, the operator can
equipment, network links and services through a very intuitive graphical
user interface : “Drag and drop your organisation on the NMS screen”.
Available on Windows XP and UNIX environment, IONOS NMS
may run on commercial workstations and is fully scalable over a wide range
of platforms with different computing power. Moreover, the client-server
architecture is modular to allow distribution on computernetworks. IONOS
NMS is based on advanced technologies (Object Oriented Conception,Relational
Data Base, Java portability, Web technology, SNMP manager, HTTP servers)
topropose a modular and scalable management platform, with a distributed
hardware andsoftware architecture. This allows optimal cost effective
fit for several sizes of managednetwork.
The relational database-driven architecture warranties the flexibility
and the global performance of the system. The MIB persistency is based
on a Data Base Management
System (ORACLE for instance).
1.2. Data Communication Network
IONOS NMS is connected to the management port of a specific NE : the «
gateway NE », via an Ethernet link, locally or remotely trough an
Inside SDH Networks, management information are carried on DCC bytes into
STM-n frame overhead data or in a dedicated VC-12 in case of heterogeneous
networks. The NE gateway ,and all NE in the network, realise a routing
function (RIP or OSPF).
Inside TDM networks, management information are carried on dedicated bits
of TS0 of the E1 frame or on dedicated bytes.
1.2. MANAGED NETWORKS AND PRODUCTS
IONOS-NMS is an homogenous and efficient solution for
networks integrating numerous
SAGEM products :
• Any SDH network with SAGEM ADR range : FOT 155C, ADR 155 C, ADR
2500C, ADR2500eXtra, ADR155e, ADR155CPE, ADR10000
• SAGEM FSP2000 DWDM products
• Any TDM network with SAGEM FMX multiplexers
• Any MicroWaves network integrating SAGEM Link equipment –
either PDH SAGEM Link F and SDH SAGEM Link A
• SAGEM TV transmitters and transposers
IONOS NMS has been designed to manage all SAGEM equipment.
2. IONOS NMS ARCHITECTURE
2.1. GLOBAL ARCHITECTURE
The general architecture is built on a client-server architecture: the
various clients can be
installed on several physical machines connected to the same server.
The interface between the network element (NE equipment) and IONOS-NMS
SNMP V1 protocol to send the alarm messages and to configure the end-to-end
(« provisioning »).
This interface also uses the HTTP protocol to configure the equipment
(NE integrating an on-card HTTP server).
The management data are stored on the server.
• The interface between the NEs and IONOS NMS is realised trough
SNMP V1 protocol concerning the alarms management and end-to-end configuration
• The interface is also realised trough HTTP protocol for the NE
• Data are stored in a data base on the servers
2.2. SOFTWARE ARCHITECTURE
IONOS-NMS is built on software modules implementing independent functional
developed in JAVA: each block only processes a function subset of the
IONOS-NMS is software environment which supplies:
• an SNMP interface.
• base services on which the main functions of the network elements
based (alarms, logs, etc.)
• a Client application (MCP) based on use of Java Beans and providing
the graphic interface elements (topology, etc.)
The IONOS-NMS platform contains a Network element manager and a Network
2.3. HARDWARE ARCHITECTURE
- Server and Client machines
The Client Applications run on a PC whereas the Server
Application run either on a PC or on a UNIX platform depending on performances
required by the network and reliability
required by the customer.
For small networks, the Client Application can be run on the same PC platform
as the server, in stand-alone mode.
The hardware platform thus remains flexible, open-ended and modular in
terms of hard
disk drive, RAM and computing power in order to grow with the system,
depends on the number of network elements to be managed.
3. IONOS NMS GENERAL FEATURES
3.1. GRAPHIC USER INTERFACE (GUI) FUNCTIONS
Thanks to GUI (Graphic User Interface) the operator may
• Copy & paste, drag & drop with mouse , rename resources
• Call contextual menus associated to resources
• Navigate between synoptic and configuration windows, navigate
between alarms and synoptic window
• Have Network hierarchical views with a “Windows Explorer”
• Move an element (equipment or sub-network) without removing links
with other elements
• Disable or enable an Audio alarm
• See only one line per alarm (start, end, acknowledgement)
• Customise the colours (look and feel and icons)
• Ask for a Screen printing in all windows (print hidden parts of
• Call a Help on line
• Add a Map as background image
• Multi-languages user GUI interface
3.2. SECURITY MANAGEMENT
The Management System provides functions to the operator
in order to manage the security of the Management System itself, as well
as the NEs, exploiting the system mechanisms and the database facilities.
Security management performs the following functions:
- Management of users ( with ID and access password)
- Log for user connection
184.108.40.206 Users Identification and password
Every user has to identify himself ( user ID and password)
before giving him access to any system function. Every log, unlog and
user ID is stored in a user log file.
By default, the following profiles are configured :
• Administrator : all rights on all functions.
• Operator : he may create and remove equipment.
• Observer : he may only consult and acknowledge alarms.
220.127.116.11 Activity Log
Operator activity is stored in a log file with the given
• Activity type
• Activity result (parameter old and new values)
• User ID
• date and time
The log file may be read, filtered and sorted with the stored parameters
by administrator users only.
18.104.22.168 Conflicts resolution between local and centralised
The concurrent access is free in “read mode”.
At the contrary, “write mode” access is given to the first
The other users are given a busy state message.
3.3. ADMINISTRATIVE FUNCTIONS
The following administrative functions are available:
• Backup / restore of management system database (command line)
• Backup / restore of management system database (GUI command)
3.4. USER MANAGEMENT
User administration is performed using the Admin View
This window enables:
???creation of new profiles, new groups and new users.
???operations on the profiles (add, delete, copy/cut, display and modify
???operations on the groups (add, delete, copy/cut, display and modify
???operations on the users (add, delete, copy/cut, display and modify
???listing the network domains and their associated groups.
4. NETWORK MANAGEMENT FEATURES
4.1. CONFIGURATION MANAGEMENT
Configuration Management provides functions to identify, check, get and
set data of the
At network level, Configuration management performs Provisioning, Monitor
and control the status, Data and software management.
Configuration management is realised by choosing a NE on the network map
and doubleclicking its icon. An HTTP session is then realised with the
NE from the HTTP server embedded in the NE. The management windows and
menus are particular for each equipment.
Configuration management performs the following generic functions:
• Definition of the network hierarchy (sub-network concept)
• Configuration of “tributary to tributary” trails
• Management of trail activation state (reserved or activated)
• Configuration of virtual elements in order to manage equipment
from other manufacturers
• NE inventory discovery, NE audit, NE configuration misalignment
automatic detection, NE inventory alignment, NE configuration reactivation,
NE date synchronisation
4.2. FAULT MANAGEMENT
Fault management ensures that the deterioration in operating characteristic
of the NEs caused by one or a set of abnormal conditions is kept to a
minimum. Fault management ensures that the NEs faults are reported on
In order to do this, EM receives reports of alarms from the NEs. In general
terms, EM is able to verify the NE accessibility by a polling mechanism,
to supervise the access network NEs to detect the occurrence of abnormal
condition and to record the existence of an abnormal condition
Fault management performs the following functions:
• Propagation of alarms occurred on a trail
• Management of protection mechanism
• Event correlation on trail
- Alarm re-alignment (from NE)
- Alarm log
- Alarm display
- Alarm real time monitoring
- Coloured alarm animation of icons
- Alarm synthesis window
- Event log
- Logs exportation
- Alarms acknowledge and clearing
22.214.171.124 Events Supervision
Equipment access is controlled periodically with a polling mechanism (configurable
polling interval) to check :
??Equipment de-alignment between the current configuration and the configuration
??Eventual alarms loss.
Any condition change sends a notification and a graphical change on the
126.96.36.199 Alarms Re-align function
This re-align function is automatically realised by polling the NEs status.
So, every time a
connection is cut and established, the system searches for all existing
alarms inside the NE and
update the network status.
188.8.131.52 Log function
The log function receives all alarms and events from supervision
function or directly from the NEs. Filters and thresholds may be set in
the NE before logging such events or alarms regarding the equipment.
184.108.40.206 Display function
The display function manages all kind of screen alarms displays, current
log files and historical log files.
Generally, alarms are depicted with the following parameters :
- Alarm ID ,
- Alarm type ( communication, service quality, environment,…)
- Origin of the failure
- Alarm severity (major, minor, unknown)
- alarm status (acknowledged, cleared,…)
Real Time Current alarms management
The manager monitors all alarms and events coming from all monitored NEs.
The operator may enable or disable this monitoring on any NE. Every incoming
alarm is immediately showed in a scrolling window, called the current
The alarms may be filtered with the following criteria :
- Resource ID
- Domain limitation
- Alarm type
- Origin of the failure
The operator may acknowledge or clear an alarm. This action
is recorded in the operator log file.
Synthetic alarm window
A synthetic alarms window gives to the operator a global view of the alarms
in the network. He knows the number of active alarms.
Topology view animation
Icons depicting the NEs of the network are given a colour regarding their
Conventional colours have been used : green colour means NEs without any
fault (or with a warning fault), yellow colour means a minor alarm and
red colour means major alarm.
This logs contain the complete list of past events, alarms and their characteristics
: arrival time, status change and remove. Alarms may be filtered on the
screen or printed by selecting any parameters combination :
- severity , type
- date and time
- equipment list in a given domain
The results may be shown on the screen, printed or exported
in excel format. The size of the file is configurable, depending on the