NV9.7 TPD 080808 1

NetViewer Suite
NetViewer 9.7
Technical Product Description
NV9.7-TPD-080808-1 © Nokia Siemens Networks 1 (75)

Issue 1 Draft 1
NetViewer 9.7
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is not an official
customer document and Nokia Siemens Networks does not take responsibility for any errors
or omissions in this document. This document is intended for the use of Nokia Siemens
Networks customers only for the purposes of the agreement under which the document is
submitted. No part of this documentation may be used, reproduced, modified or transmitted in
any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks
welcomes customer comments as part of the process of continuous development and
improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity
or performance of the mentioned hardware or software products are given “as is” and all
liability arising in connection with such hardware or software products shall be defined
conclusively and finally in a separate agreement between Nokia Siemens Networks and the
customer.
IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS
DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO
SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES
SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA, that might arise from the use of this
document or the information in it.
THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS". EXCEPT AS REQUIRED
BY APPLICABLE MANDATORY LAW, NO WARRANTIES OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-
INFRINGEMENT, ARE MADE IN RELATION TO THE ACCURACY, RELIABILITY OR
CONTENTS OF THIS DOCUMENT. NOKIA SIEMENS NETWORKS RESERVES THE RIGHT
TO REVISE THIS DOCUMENT OR WITHDRAW IT AT ANY TIME WITHOUT PRIOR
NOTICE.
This document and the product it describes are considered protected by copyrights and other
intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2008. All rights reserved.
2 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

Issue 1 Draft 1
Contents
Contents
1 Introduction.......................................................................................... 6
2 System overview .................................................................................. 8

2.1 Flexible SW architecture ........................................................................ 9
2.2 NetViewer Engine .................................................................................. 9
2.2.1 General.................................................................................................. 9
2.2.2 NetViewer Server................................................................................... 9
2.2.3 Data Base manager ............................................................................. 10
2.2.4 NetViewer Client .................................................................................. 10
2.2.5 NetBuilder ............................................................................................ 11
2.2.6 NE Plug-in............................................................................................ 11
2.2.7 Southbound interfaces ......................................................................... 12
2.3 Hardware Architecture ......................................................................... 13
2.3.1 NetViewer Large configuration - Multi-server ....................................... 13
2.3.2 Q1 Agent Integration............................................................................ 14
2.4 Web Interface ...................................................................................... 16
2.5 Element Management Layer within NetViewer ..................................... 16
2.5.1 Node Manager Server.......................................................................... 16
3 System details.................................................................................... 18
3.1 Management Functions........................................................................ 18
3.1.1 Fault Management ............................................................................... 19
3.1.2 Configuration Management .................................................................. 25
3.1.3 Links among the NE’s .......................................................................... 28
3.1.4 Graphical tools ..................................................................................... 29
3.1.5 Service Management ........................................................................... 31
3.1.6 NE Configuration.................................................................................. 37
3.1.7 Security Management .......................................................................... 37
3.1.8 NetViewer - System Functions ............................................................. 48
3.2 System administration NetBuilder ........................................................ 50
3.3 Graphical User Interface (GUI)............................................................. 52
3.3.1 General Features ................................................................................. 52
3.3.2 GUI ...................................................................................................... 52
3.3.3 Status Bar ............................................................................................ 53
3.3.4 FIND .................................................................................................... 54
3.3.5 Browsing to the neighboring NE........................................................... 56
3.3.6 Writing a description............................................................................. 56
3.3.7 Online Help .......................................................................................... 57
3.3.8 Logs & Lists ......................................................................................... 57
3.4 Data base ............................................................................................ 58
3.4.1 Content ................................................................................................ 58
3.4.2 Settings................................................................................................ 59
3.4.3 History Report ...................................................................................... 59
3.5 Export Data from the Database with SSIS............................................ 63
3.6 MS Windows Terminal Services, Citrix Metaframe, support ................. 64

Issue 1 Draft 1
NetViewer 9.7
4 System Technical Specification........................................................ 67

4.1 Managed network elements ................................................................. 67
4.2 Hardware ............................................................................................. 68
4.3 Software............................................................................................... 68
Appendix ............................................................................................................ 70
References ......................................................................................................... 71
Glossary 72
Index 75

Issue 1 Draft 1
Summary of changes
Summary of changes

Issue 1 Draft 1
NetViewer 9.7
1 Introduction
This document presents an overview of NetViewer functionalities of the system version V9.7.
Detailed information about the supported NE types and the features available in each
NetViewer version is found in NetViewer Customer Feature List document. As general
concept, NetViewer implements common features for all the Network Elements (NE), but
some of these features are not developed/available in all the types of NE; so it is really
necessary to merge this document with NetViewer Customer Feature List for avoiding a
misunderstanding of what is the real behavior of a NE under NetViewer itself.
The NetViewer is the Nokia Siemens Networks Management Solution designed for:
• the needs of metropolitan and regional microwave transport networks as well as for long
distances within national or international networks; NetViewer supports Nokia Siemens
Networks PDH and SDH microwave network elements
• new WiMAX technology based on .16d standard in a wide variety of application scenarios.
• Narrowband Access solution
Moreover support:
• Equipment supporting the DCN;
• Mediation devices (both HW and SW) towards other network elements, included no Nokia
Siemens Networks equipments
NetViewer covers the usual management areas for an EMS: Fault, Performance, Configuration and
Security Management on the network elements.
It is based on client-server architecture; the server is always connected to the NEs in order to collect,
and save, the information collected from the network. A relational database is used to make persistent
the data collected by NetViewer and to make them available also to other systems for post-processing
purpose.
The NetViewer operators access the system via NetViewer client that connects to the server and
displays the requested information in graphical screens. More than one NetViewer GUIs could connect
to the same server, so it is possible to have different operators in the same networks at the same time,
typically operating with different responsibilities and tasks.
NetViewer integrates a light Network Management Layer (as outlined in Figure 1-1), providing an
overall view of the managed Network. In this way it’s easy to understand the network status and zoom
down to the network element details.
\

Issue 1 Draft 1
Introduction
Business
Management
Service
Management
Network
Management
Element
NetViewer
Management
Fault Management
Configuration Management
Performance Management
Security Management
Figure 1-1: NetViewer product positioning
NetViewer EMS provides:

• Connectivity to Network Elements, supervision of connection and working status;
• Fault Error Reporting functionality, trap loss recovery, summarization of alarm state;
• Configuration Management for the Network Elements;
• Performance Monitoring collection and report;
• Inventory data collection and report;
• Graphical User Interface for user-friendly management;
• Web access, via HTTP server, to NE management;
• Security Management on Network Elements;
• Report and log functionalities;
• Storing in internal database of main NE parameters;
• Advanced user/sub-domain management;
It works simultaneously with other management systems allowing mixed Microwave and SDH F.O.
equipment networks.
This system can be scaled within wide range to give customized network management solutions.
This product description gives details about the architecture, functionality, configuration and some
scenarios of NetViewer applications.

Issue 1 Draft 1
NetViewer 9.7
2 System overview
NetViewer Suite as shown in figure Figure 2-1 is a managenent system based on Microsoft Windows
system, while the HW is based on standard x86 platform; they are platforms largely used and well
known, moreover the solution is cheaper than other ones, also concerning HW requirements.
The man-machine interface is GUI based: GUI is simpler than command line interface, especially for
not skilled operators.
NetViewer implements a client/server(s) architecture and the server(s) also support the master/slave
configuration: the network element data are processed by the server-side parts of the system and the
user normally access the NE information via graphical user interfaces.
The data are stored in the NetViewer database, that is implemented by Microsoft Access in the
NetViewer Entry configuration, or Microsoft SQL Server in the other ones. Data can be exported using
the export functionalities of these products.
In addition, NetViewer can act as mediation device, to allow higher level NMSs or external repository
systems to access Nokia Siemens Network NEs. These interfaces are simply called Northbound
interfaces
Figure 2-1: System Architecture of NetViewer

Issue 1 Draft 1
System overview
2.1 Flexible SW architecture
NetViewer is endowed with flexible software architecture based on Client-Server solution.

NetViewer is organized in a core software (the Engine, with the common parts and the main features
and the Graphical User Interface (the GUI); the network elements to be managed are plug-in software
modules separated by the Engine.
These plug-in have to be added to the Engine and are released independently from the Engine itself at
different dates. So a new network element can be managed by an installed NetViewer release simply
loading its relevant plug-in.
For increasing functionalities additional packages software are available and can be designed.
Another advantage of this architecture is that it is open to the customer’s needs.
2.2 NetViewer Engine
2.2.1 General
This component is the core part of the system; in fact the engine contains the code implementing the
common functions of the system:
• the connection to the NE,
• the management of the NE information,
• the storage and retrieval of the data to/from the database,
• the Graphical user interfaces,
In the NetViewer Engine component it is possible to identify several subcomponents, even if they are
installed by the same setup package.
2.2.2 NetViewer Server
The NetViewer Server is the main server subcomponent of NetViewer and it is the real core of the
system: it collects the information from an NE via the proper adapter, it processes the information
data, it stores it in the DB via the DB Manager module, and it makes it available for the graphical user
interfaces. NetViewer Server contains all functions needed for the network layer and element layer
management and it implements the logic of the system administration function.
The NetViewer Server can be replicated in a multi-server configuration where a server is configured as
Master and the others work as Slaves servers. In this case each Server (included the Master one for
the NE directly managed by it) is responsible for the connection to the network elements configured
and assigned to it (using a NetViewer terminology, the NE assigned to a server “belongs to its map”),
while the Master Server is also responsible for the collection of the data from the Slave Servers

Issue 1 Draft 1
NetViewer 9.7
regarding the NE managed by them. Each NetViewer Server of such configuration is installed in a
different Server PC.
2.2.2.1 Q1 Agent
Q1 Agent is used as a mediator between Nokia Q1-managed network elements and the NetViewer.
The agent is installed in an own PC workstation and it is managed by NetViewer as a slave server;
there can be one Q1 Agent per workstation. When the network grows, new agents can be added to
the NetViewer system.
Q1 Agent is connected to Q1 management buses through remote pollers. A TCP-based
communication protocol is used for communication between the remote pollers and Q1 Agent.
For more details please refer to the Q1 agent documentation.
2.2.3 Data Base manager
NetViewer DataBase manager is the subcomponent that receives the data from NetViewer Server
(alarms, performance measures, etc) and stores them in the physical DB.
When the pre-configured DB limits are reached, it is possible to archive the excessive data (otherwise
deleted) in other DB instances, in order to have additional repositories for a longer period of time. Also
these extra repositories can be lost, if a periodical backup is not performed, because the DB instances
and size are anyway limited.
It is possible to set the nominal capacity (expressed in record) of the Database as regards to the
performance data. The default value of capacity is 100.000 records, with a max capacity equal to
800.000 records.
Data presence is assured until the first one of the cancellation criteria is met:
• data reach the configured age limit;
• data amount reach the configured limit as entries number;
• data amount reach the maximum DB physical limits.
It is also possible to manually delete the entries, or the desired subset (for example only 24H PM
Entries).
2.2.4 NetViewer Client
NetViewer client implements the Graphical User Interface (GUI) for the network and the network
elements management. All management functions of the NetViewer Server are accessible through this
NetViewer GUI client. The NetViewer Client communicates with the NetViewer Server via a optimsed
application protocol, over TCP/IP.
Up to 20 NetViewer Clients may operate in one NetViewer Server simultaneously: in case of multi
server configuration 10 additional Clients are available, but they have to be associated to the Slave
servers (i.e. the sub-servers).
The window architecture, implemented by the NV GUI client, is called MDI (Multiple Document
Interface). In this graphical interface the consistency of displayed data is guaranteed. For example,

Issue 1 Draft 1
System overview
this means that GUI elements displaying the same information, also within different windows, are
updated at the same time.
The design of the user interface components are based on the standard Windows look-and-feel
providing user friendly pull down menus and drag & drop operation.
When opening the NE via the NetViewer GUI, the NE specific screens appear: these screens are
almost identical to the LCT ones, as this screens are implemented by a specific NE plug-in that is
common to NetViewer and LCT.
2.2.5 NetBuilder
NetBuilder is the graphic tool for the administration of NetViewer system, which allows:
• the creation/modification of NetViewer network maps (see below)
• the management of the services of NetViewer Server
• the user management
The use of NetBuilder is reserved to the users that have the proper privileges.
The most important entries in the NetViewer network maps are:
• the names and the network parameters of NEs that the server has to manage, as for example
the IP address;
• the credential that NetViewer has to use in the log-in procedure towards the NEs;
• their position in the NetViewer graphical map view;
• the structure of the map, in terms of sub-servers and sub-maps. A sub-map is a logical group of
NEs, which for some reason the operator wants to keep separated by the other ones: an
example is the set of NEs in a particular geographical area, or a cloud of a particular type of
NEs inserted in a network supported by different equipment types;
• the links between the NEs.
NetBuilder implements also the Discovery function, which allows executing an automatic search of the
NEs and adding the discovered NEs in a new map (normal Discovery) or in an already existing map
(incremental Discovery); in case of normal Discovery, it is possible to include also the automatic
search of the links between the NEs in the map.
2.2.6 NE Plug-in
The NE plug-in is the NE type specific software component of the NetViewer system . For each NE
type to be managed by NetViewer there must be a corresponding NE Plug-in installed in NetViewer
Server.. Each plug-in is a separate component that can be installed separately in the NetViewer PC.
The NE Plug-in includes mainly the info model (e.g. the name of all the possible alarms) and the GUI
screens of the specific NE. The info model is used by NetViewer Server for the Element Manager (EM)
functionalities, and the screen description is used by NetViewer Client to display in a consistent way
the NE informations. for more details.
The loading of a Plug-in is performed in run-time modality, without the NetViewer restart.

Issue 1 Draft 1
NetViewer 9.7
2.2.7 Southbound interfaces
The Southbound interfaces allow the communication among NetViewer Server and the different
network elements.
NetViewer supports different interfaces and for each interface a managers is developed as
components belonging to the NetViewer Server.
The managers provide interfaces for managing the connections to the network elements, and for
sending and receiving data to / from a network element.
The Managers available in NetViewer are:
TNMP Manager. It is used for the communication with SRA 4 and SRA XD Microwave equipment
families.
OSI Manager. It is used for the communication with SDH network elements using the OSI
communication protocol towards NetViewer. OSI ping is available. This protocol is used only on the
old NE such as SRT1 and SRT 1C: the new SDH equipment is managed by TCP/IP protocol.
SNMP Manager. It is used for the communication with WayMAX (WiMAX .16d Base Station), SRT 1F,
FIU19E, FTFA, FlexiHybrid and the generic SNMP devices (multi vendors router, interfaces etc.), often
utilized for building the DCN (See Figure 5.2).
TL1 Manager. TL1 protocol over TCP/IP is used for managing the SRT 1F NE.
2.2.7.1 Q1 Agent Interface

Q1 Agent support has a northbound interface the NE3S Nokia Siemens Networks protocol based on
SNMP-UDP/IP framework. The NetViewer support this protocol as Master server – Q1 Agent protocol.

Issue 1 Draft 1
System overview
2.3 Hardware Architecture
2.3.1 NetViewer Large configuration - Multi-server
NetViewer NetViewer
Remote WEB
Client Access
Client
WAN Inter- / Intranet
NetViewe NetViewer NetViewer

Client Client Client
LAN
NetViewer NetViewer
NetViewer Q1Slave
Agent Q1 Agent
Slave
Master 1
server 1 n
server n
Server
...
NE NE NE
Figure 2.1: NetViewer Large Configuration - Multi server
NetViewer can be configured with several Servers to scale the network management. The servers
can be NV server or Q1 Agent.
If there is more than one Server used, a Multi-server configuration is built up, as shown in Figure 2-1.
In Multi-server configuration the additional Servers required for the increasing of the network are
configured as Slave ones, while the first as Master one.
Up to 20 NetViewer Clients may simultaneously operate on one NetViewer Multi-server; what is more
up to 10 additional Clients can be operate one for NetViewer Slave servers.

Issue 1 Draft 1
NetViewer 9.7
From each Client is possible to simultaneously open up to 4 GUI sessions each of which connected to
1
a different server .
Multi-servers
2
Master Slaves
Max # of Clients
simultaneously connected
20 10
Table 1: Numbers of Clients simultaneously connected to a NetViewer system
The NetViewer Clients can be connected either by LAN, WAN, ISDN/PSTN, or WEB access.
The EM application (EM) is the GUI for the network element management of a given NE type. The EM
application is located on the NetViewer Server. From NetViewer Client it is started by the operator in
order to zoom into the network element. Configurations on the network element level (e.g. configuring
cards, software management) are done by using the EM application.
An Element Manager can be started via the GUI of the NetViewer Client for some particular NE’s. The
GUI application is identical to the LCT one.
2.3.2 Q1 Agent Integration
Here following the system architecture for Q1 Agent integration.
1
The Multi GUI session can not be applied to the Entry Configuration
2
The numbers of Clients simultaneously connected have to be considered totally for all Servers. Not
applicable with Q1 agent

Issue 1 Draft 1
System overview
Client PC Client PC
NetViewer NetViewer
Type NM Type NM
GUI client GUI client
ICA client ICA client

or Terminal
Server client
Node Type info or Terminal
is available to Server client "sobriquet" (Q1
the GUI address) passed
as parameter
NetViewer Node Manager

Master Server Server
Citrix Pres. Server
or Terminal
Server alone
Node Type passed
as SubClass in
topology upload NM1 NM1 NM2
GCS Topology DB
Q1 Agent Sobriquet Q1 addr.
Sub-Server topology
upload to
GCS DB
Q1
NE NE NE NE
Figure 2-2 – NetViewer – Q1 system architectures

Issue 1 Draft 1
NetViewer 9.7
2.4 Web Interface

NetViewer System is provided with the Web Interface.
The Web interface is for opening NetViewer to the Web world and allowing the access via Internet /
Intranet connection
2.5 Element Management Layer within NetViewer

The Element Management Layer of NetViewer provides a set of functions to support the operational
tasks of the network operator to supervise the single Network Element. These include the visualization
of the Network Element configuration and all the functions needed to the operator for understanding
the status of the network Element and, if need, to perform action on it.
For each Q1 Network element, and for the related Q1 Agent, the specific element manager (called
Node Manager) is available on a Node Manager Server a dedicate PC where are store al the Node
Manager application.
Each Node Manager can be remotely execute form NetViewer GUI and through the Terminal Server
application provided by Node Manager Server display the Node Manager GUI interface on NetViewer
Client
For detailed information on Node Manager server and It configuration together with Q1 Agent please
refer to the dedicated documentation available With Q1 Agent.
Like for the Q1 Agent also for the FIU19E and FTFA that use Node Manager for Equipment
configuration management a Node Manager Server is need.
2.5.1 Node Manager Server
The NetViewer 9.7 is certificated with Node Manager server available on a dedicated PC is
required. To support FTFA and FIU19E a Node Manager server is required.
The Node Manager Server is a dedicated machine on which run the Node Manager application
components necessary to perform configuration management of network elements.
The NetViewer GUI client is able to provide a "context sensitive" launch: if the operator is managing a
specific equipment type, the correct node manager for that node is launched

Issue 1 Draft 1
System overview
For detailed information please refer to the “Node Manager Server Principles” (DN03410658 Issue 7-
0)

Issue 1 Draft 1
NetViewer 9.7
3 System details
3.1 Management Functions
The ITU-T M.3010 standard for TMN networks describes the management functionalities, distributing
them in 4 layers. The layers implemented with some restrictions by NetViewer and Path Manager
(optional) are:
• Element Management Layer: NetViewer manages each network element on an individual basis.
The following collections coming from all the NE’s, as specified in the Customer Feature List, are
available
- fault
- performance
- configuration
• Network Management Layer: NetViewer with Path Manager. Path Manager supports an
abstraction of the functions provided by the network element layer and is responsible for the
management of a network as supported by the element management layer.
The same recommendation fixes for each layer four functional areas Fault, Configuration,
Performance and Security Management. A summary of these functions with some explanatory notes
are reported in the table of Figure 6-1.
Layer Description
Element Management
(NetViewer standalone)
Fault Management Performs the alarm surveillance on the managed Network
Elements.
Configuration Management Allows the manipulation of the changeable parameters (cross-
connections, protection, alarms status, communication
parameters, etc) of the Network Elements.
Performance Management Collects, presents and logs performance data of those Network
Elements which provide NetViewer with the performance data that
have been saved in each NE.

Issue 1 Draft 1
System details
Layer Description
Security Management Controls the access to network elements and the access to the
OS and determines the rights and privileges of the different users
and classes (supervising, maintenance, operation, configuration,
administration).
Figure 3.1: Management areas table
3.1.1 Fault Management
NetViewer collects all the alarms coming from each NE’s of the network and represents them in the
Map: they are automatically stored in the Data Base.
NetViewer performs alarm surveillance on the managed networks, sub-networks and network
elements. It performs automatically alarm detection, e.g. synchronization alarm or AIS, which are
immediately reported by the network elements. The alarm severity is ranked into seven categories: not
on line, indeterminate, test, warning, minor, major, critical.
3.1.1.1 Alarm List

An alarm list displays the current alarm situation of the entire network and its components (sub-
networks, NEs, termination points, etc.). It is activated from the NetViewer menu. The Alarm List can
be displayed in three ways (Figure 3.2, 7.3) and one tab of the Alarm List window reports the External
Alarms (figure 7.4):
• Full tree (tree view of all the NE of the network with/without alarms)
• Active table (tree view of all the NE of the network with alarms)
• Active Tree (alarms in table format)
• Ext. Alarms Table
For every alarm the information, shown in the different views of the alarm list, contains the
following elements:
• A colored ball representing the alarm severity
• Time stamp
• NE name
• Severity
• Probable Cause
• Alarm type
• Specific Problem
• Acknowledged by
• Acknowledgement date
• Acknowledgement Note

Issue 1 Draft 1
NetViewer 9.7
Figure 3.2: the Active Table View of the Network Alarm List
Figure 3.3: the Full Tree view of the Network Alarm List
At the bottom of the alarm list window, the Active Alarms Summary is available too: for each severity
the number of unacknowledged/total alarms is reported (Figure 7.5).

Issue 1 Draft 1
System details
Figure 3.4 Active Alarms Summary
Selecting the Options of the GUI Client (Push-bottom bar or Menu bar) it is available:
• Filter for Alarm List: the acknowledged alarms can be done not visible (Figure 7.6)
• Customize table. The tables generated by the different applications of NetViewer can be
customized in terms of Sort and hide. The order of the columns can be changed and the columns
can be hided (Figure 7.7).
The options available for the Alarm List are reported in the following tables;
Alarm List of the Network
Column Hide/ Mobile Default

Show Show position
Index yes no yes 0
Time stamp yes no yes 1
NE name yes yes yes 2
Severity yes yes yes 3
Alarm description yes yes yes 4
Ack. by yes yes yes 5
Ack Date & Time yes yes yes 6
Alarm List of the single NE

Show Show position
Index no no yes 0
Time stamp no no yes 1
Severity no yes yes 3
Alarm description no yes yes 4
Ack by yes yes yes 5
Alarm List of External Alarms

Show Show position
Index no no yes 0
Time stamp no no yes 1
NE name yes yes yes 2
Severity no yes yes 3
Alarm description no yes yes 4
Ack by yes yes yes 5
The Alarm List of the Single NE can be opened from in NE view GUI frame (Figure 7.8)

Issue 1 Draft 1
NetViewer 9.7
Figure 3.5: Alarm List of Single NE

Issue 1 Draft 1
System details
3.1.1.2 Alarm Acknowledgment

The acknowledgment of an alarm can be performed from:
• The icon of the NE in the Map view and in the Map Tree View
• The row of the NE in the NE Tree View
• The alarm list
In the first case and in the second one, all alarms of the selected NE are acknowledged through the
NE popup menu. So, when this option is chosen, a warning message appears to signal consequences
of this action (figure 7.9).
Figure 3.6: Acknowledgement through NE Tree View, Map View and Map Tree View
In the third case it is possible to acknowledge every single alarm or group of them by its popup menu.
In the alarm list alarms are marked with the “=” symbol; when they are acknowledged, this symbol is
changed with the “√” one.
The information about “who acknowledged” and “when” are available:

• In columns of the active table of Alarm List
• In tool tips that appear on the icons in Full Tree and Active Tree of the Alarm List
Moreover during the acknowledgment procedure is provided the possibility to associate to the alarm(s)
under acknowledgment a textual note that will be saved in the database and showed in the Alarm lists
and history report
The Alarm acknowledgment can be performed also by:

a) the alarm list – multiple acknowledgement. The alarms to be acknowledged together are selected
and then they are acknowledged.
b) the icon of the subnet (view of the Network) - acknowledgement of all the alarms of the subnet
c) the icon of the slave server (view of the Network) - acknowledgement of all the alarms of the slave
server

Issue 1 Draft 1
NetViewer 9.7
The visualization of the Acknowledgment on the NE icon

The NE (or sub-net/subserver) icon label is divided in two parts the right side becomes green
(equivalent to NORMAL severity) when the alarm is acknowledged, the left one, the triangle, always
reports the real severity of the higher alarm present in the NE. Tool tips explain the icon severity and
icon acknowledgment status(Figure 7.11).
Also Slave server and Subnet icons are divided in two parts (Figure 7.12) to report acknowledgment
status.
N o Alarm
Alarm On /
not Acknowledged.
Tool tips Severity: MINOR/ Unack. MINOR
Alarm On /
Acknowledged
Severity: MINOR/ Ack. NORMAL
Figure 3.7: Acknowledgment on NE icon

Issue 1 Draft 1
System details
3.1.1.3 Summarized Network Status
For a very quickly view, the summarization of the whole managed network is represented by a special
icon able to be moved onto the screen: its color reports the relative alarm severity in the same way of
all the other icons, included the acknowledgment status (see Figure 7.16).
The color of a dedicated flag in the same window summarizes the status of all the external alarms of
all NEs (they are used for reporting environment alarms of the site where the equipment are located):
● Green, when there are no alarms
● Red, when at least one alarm is activated
Figure 3.8: Network status icon with summarization of the External Alarms
3.1.2 Configuration Management
The Configuration, via NetBuilder application, allows to create/change the network to be managed by
NetViewer: the so called “Map”.
The map includes all the NE’s, their relative connection proprieties, the structure of the map, the sub-
maps, the servers, the access passwords to the Server, the database of the access passwords.
3.1.2.1 Configuration of the Map

NetBuilder is the network Editor of the creation of the Map.
The features available are:

• To apply the NE icons in the most proper positions on the drawing;
• To apply the Subnetwork icons in the most proper positions on the drawing;
• To assign the corresponding name and/or IP address, that has to be a univocal one, to each NE;
• To import into NetBuilder the radio equipment network drawing, that constitutes the map
background
• To compose the radio equipment network drawing using a common graphical Windows
application (e.g. Paintbrush) supporting the “.bmp”, “.gif” and “.jpg” graphical format
• To set the passwords for the access to the Server and the database of the access passwords to
the NE’s;
• To save the map with the desired name in a “.db” format file.
• To create also some maps with tree structure, which is composed by a main map and one or more
sub-maps in cascade.

Issue 1 Draft 1
NetViewer 9.7
• To drag and Drop NE’s/sub-networks

• To editing a comment to each NE (max 250 characters)
• To import “.map” format
• To Import/Export NE List with “.csv” format to/from the database
• To edit text on the map
• To draw arrows and lines on the map
Network Icons
NetBuilder provides the icons for building the NetViewer Map.

Three types of icons are available
• NE-icon for the network element
• Sub-map for the sub-networks
• Sub-server to be used for Multi-server configuration
The NE/Sub-map/Sub-server icons are not specific to the network element type during the
construction of the Map. The icons take the symbolic view of network elements when NetViewer
Server is connected to the effective NE.
The icon Sub-map, provided by default, can be changed: the new icon is shown only when NetViewer
Server is active.
Icon information
When NetViewer Server is connected to a network element, the NE-icon provides the information:
• upper part of the icon; the type of network element
• lower part of the icon; it includes the alarm severity of the network element and the
acknowledgment status. Both are represented by different colors.
A tool tip of the icon supplies the additional information relative to:
• IP address
• the eventual edited description. The presence of a customized description is marked by a blue
triangle on the right of the icon.
Figure 3.9: Example - SRAL XD Series 3 icon
The severity status is the result of the summarization of NE existing alarms: it is reported the higher
one.
The Default configuration of the Severity/Color is:
• disconnected grey
• normal green

Issue 1 Draft 1
System details
• test cyan
• warning yellow
• minor orange
• major red
• critical magenta
The Administrator can change these color settings in the general preference dialog of the NetViewer
System Administration.
Network Representation
NetViewer is working and the NE/Sub-net is connected: so the type of NE is displayed in the icon,
together with the severity: green means no alarms in the network.
The visualization of the Map tree is in the left upper frame, while the tree Menu of the NE selected is
reported in the left lower one.
Map
Tree view
of the Map
Tree view of
the NE
Figure 3.10: Network representation
Editing the description of a NE
The Description of NE pop-up menu allows the editing of a string of characters (max 256) to be stored
for each NE. It is so possible by the operator to report some comment/note for e.g. regarding the
maintenance process of a network or other (Figure 7.23).
The presence of such Description is marked by a blue triangle in the upper corner of the icon in
NetViewer GUI and the edited file is visualized by a tool tip (Figure 7-24).

Issue 1 Draft 1
NetViewer 9.7
Figure 3.11: NE description editing
3.1.3 Links among the NE’s
The tool, which allows creating the map and inserting NEs, Subnets and Slave servers, can create the
links among the NEs (Figure 7.25).
Figure 3.12: create link among the NEs
In case of link between two NE’s with different sub-map path, the NE belonging to the other map is
shown with a smaller icon.

Issue 1 Draft 1
System details
Figure 3.13: Links crossing sub-maps
3.1.4 Graphical tools
Graphical tool of NetBuilder is available for drawing lines, arrows, notes on the map.
The Menu Add Graphic Objects includes:
- Line
- Text
The combination of lines and texts allow to represent in the map which NE’s are included in the
different stations as reported as reported here following.

Issue 1 Draft 1
NetViewer 9.7
The borders of the stations and their names are drawn and written with the Graphical
tool
Figure 3.14: Map and Graphical tool
Copy, Paste, Delete options are available clicking on right push button of the map.
3.1.4.1 Import/Export List of NE’s
The Export command allows exporting the list of NE’s contained in the currently opened and selected
map, included the NEs of the sub-maps. The NE list is saved in the “.csv” file.
The Import command creates a new map, where the list of NE’s contained in the specified “.csv” file is
imported.
3.1.4.2 Editor with NetViewer Server activated
The configuration Map can be modified while NetViewer Server is running.
3.1.4.3 Map Summary
The Map Summary network application provides information on the structure and the composition of
the network map and on the connection status of NEs and Sub-Servers.

Issue 1 Draft 1
System details
Furthermore, it allows the management of the functionality of contemporary modification of the user
class for the access of Server to all the NEs (“Restricted” or “Normal” operation).
Figure 3.15: Map Summary Window
3.1.5 Service Management
The Services Management window displays, in table format, the Server services managed by
NetViewer Services Manager.
Two services are available:
• NetViewer Server Service
• Database Service
If other modules are installed, the relative services are reported.
For each service, the following information is reported:

• the service name (Name)
• the software version of the service (Version)
• the current status of the service (Status)
• the reason for which a service has problems (Message)

Issue 1 Draft 1
NetViewer 9.7
Figure 3.16: Map Summary Window
NetViewer Server Service Properties:

– the current map field where the system displays the file name of the actually loaded map
– three push-buttons for the map loading/closing commands:
• Open Map
• Close Map
• Reload Map
Figure 3.17: NetViewer Service management
When the Database Properties button is pushed, a window appear.
Figure 3.18: NetViewer Database Management
Through the button “Database Usage”, it is possible to accede to the window “NetViewer Database
Usage”. This service displays the space currently used in the Database for each event category,
expressed as percentage with respect to the relevant nominal capacity.
Figure 3.19: NetViewer Database Usage

Issue 1 Draft 1
System details
Through the button “Database Config”, it is possible to accede to the window “NetViewer DB
Configurato
Figure 3.20: Database Configurator - General
The Database Configuration has a General view for configuring the 3 database sections of NetViewer:
Events, RX Power, Performance.
The configuration has different buttons for managing its main entries:
• General
• Events
• RX power
• Performance
• Other parameters
The General View includes the functions:

• Activation every a chosen time of the DB copy
• Setting of the Warm standby account
• Performance measurements status (enabled/disable of day/quarters G.826, RSPI, RPS, G.784
PM)
For each Database the following settings are available:

• Max data amountDelete automatically after X days
• Delete all
• Delete older than
• Keep only the newest Y events
• Enable event threshold
If the event threshold is enabled, a warning message is generated when the threshold value (xy%) of
the total available space of the Database is exceeded.

Issue 1 Draft 1
NetViewer 9.7
In the Events, it is possible to delete the reporting of the Events “Data Performance Presence” either
PM24h or PM15m relative to each NE. These events are not more useful, because the PM
measurements of the whole network are collected by NetViewer and available in its Database.
Figure 3.21: Database Configurator - Events
The PM’s have to be enabled with the specific selection:

• RPS 15m, 24h
• RSPI 15m. 24h
• G.821, G.826 15m ,24h
• G.784 15m, 24h
G.826 15m PM’s of the whole network meet the limits:

• type of NE: SRAL, SRA S3, SRAL XD, SRA 4
• number of PM’s for SRA L, SRA S3: two measurements to be choose among the 5 available
ones (BBE, SES, ES UAS, OI)

Issue 1 Draft 1
System details
Figure 3.22: Database Configurator - PM parameters
It is possible to operate on the data of scheduled e/o periodic measurements.
Figure 3.23: Database Configurator - RX Power Parameters
It is possible to enable the Collection of:

• Inventory Data
• Configuration Data

Issue 1 Draft 1
NetViewer 9.7
Figure 3.24: Database Configurator - Other Parameters

Issue 1 Draft 1
System details
3.1.6 NE Configuration
Configuration management comprises features to read the current configuration from a network
element and to change it. NetViewer allows the system operator to read and write the configuration
information directly by means of Netviewer or by means of the remote execution of Node Manager
application.
The remote execution of Node Manager can be made from the NE tree view Windows.
3.1.7 Security Management
The Security allows the access to NetViewer only to the authorized Users: each User is defined with
some parameters (login, password) and with specific Permissions.
Users and Permissions are assigned by the Administrator of the System (SysAdmin).
NetViewer 9.7 introduces the User Groups management: each Users of the same group has the same
permissions, which can be modified in accordance with Customer’s needs.
3.1.7.1 Security and Permissions

In NetViewer 9.7 there are three types of Permissions:
- on the objects of the map.

Applicable via NetViewer and NetBuilder Client by the User on each object of the map: map,
sub-map, sub-server, NE.
It is the base of the Sub-domain management. Each part of the network can assigned to different
User: e.g. a
User can have the Permission of Read/Write on a Sub-Network, but in the same time, have the
Permission of
Monitor on anther one.
- on the map.
Applicable via NetViewer Client by the User on each map, when NetViewer is on-line (e.g.
SW download).
It is used for allowing some operations on the maps. Different profiles of Operators can be defined as
required by the different tasks of the management of a network: e.g. a user with the task of SW
download
can be created.
- on the System.
Applicable via NetViewer and NetBuilder Client on NetViewer server.

Issue 1 Draft 1
NetViewer 9.7
They allow the management of the server. It is possible to define User with specific tasks on the
System: e.g.
a User with the profile of add/delete NE from the Map.
The three types of permissions are assigned independently among them, so to create a very flexible
management of the network.
User A has the

Permission to monitor ll
NE’s sub-maps included
in the black circle.
User B has the

Permission to
add/remove NE on all
NE’s, sub-maps
included in the red
circle.
User B has only the

Permission to SW
download on the 2 sub-
maps included in the blue
circle.
Figure 3.25: example of the application of Permission to a network
The User management is performed with two modalities:

- Local User management.
Users management via internal Database, as it was done in the previous releases.
- External User Management.
Users management via an external Active Directory. NetViewer is supplied with the Active Directory
of the Operating System MS 2003 server, but other applications can be used (e.g. Active Directory of
the Customer organization).
3.1.7.2 Local User Management

It is implemented the User Groups management: each Users of the same group has the same
permissions.
The User Groups are four:
- NetViewerAdmins
- NetViewerRWs
- NetViewerROs
- NetViewerMonitors.

Issue 1 Draft 1
System details
It is not possible to create new groups: this task is only via the External Active Directory.
The following Permissions are available as default to each group:
Groups Permissions Permissions Permissions

on the objects of the map on the map on the System
(default) (default) (default)
NetViewerAdmins administrator all Map Open/Close
Services Configuration
Collect Info Configure.
Map Create
NetViewerRWs readwrite - -
NetViewerROs readonly - -
NetViewerMonitors monitor - -
An User created under a User Group heredities the Permissions of the groups itself.
If it is required to change the defaults Permissions to an User, it is possible:
- to assign him each single Permissions required
- to change the permissions of the Groups
The Permissions assigned to each groups can be changed, with the exception of the Permissions on
the objects of the map.
The User Management is done by SysAdmin User (Figure 7.56).
SysAdmin has all the Permissions of the System (Figure 7.57):
- Services: tool for the management of NetViewer services.

- Set External User Manager: for setting the external Active Directory
- User management: for creating the Users
- System Permission Management: for adding/reducing permissions of the system to the groups/users.
- Exclusive Mode management: for logging out the Users from NetViewer. SysAdmin has the priority to
the access of the network either in NV Client either in NetBuilder Client.
SysAdmin can create an User with his permissions with the exception one of Set External User
Manager.
Figure 3.26: User Management window Figure 3.27: SysAdmin- configuration
The creation of a new User is done selecting the belonging groups.

Issue 1 Draft 1
NetViewer 9.7
Figure 3.28: new User creation
3.1.7.3 External User Management

The External User Management allows:
- the Identity management of the Users,
- to create different User Groups, as required by the different requirements of the Customers
The groups imported by the External Active Directory don’t have permissions assigned: they have to
be specified using NetBuilder Client.
The Local User Groups with the relative Permissions can be moved to the External Active Directory,
simply creating a group with the same name.
The rules to be applicable for the creation of the new groups are defined by the Administrator of the
External Active Directory: all the relative information are located where the application is installed.
Figure 3.29: Active Directory - Users List
The creation of new Users and the setting of some password parameters.

Issue 1 Draft 1
System details
Figure 3.30: new Users Figure 3.31: setting of password parameters
3.1.7.4 Add/Move Permissions of the System to Groups/Users
The System Permission is the tool for assigning/removing the Permissions of the System to the
Groups/Users (only via SysAdmin).
The permissions of the System are:

- Map Open\Close: rights to open/close the map loaded into the server for modifying the network
managed by NetViewer.
- Map Reload: right to enable the changes of the network into the NetViewer server. This right is
applicable to the NetBuilder Client.
- NetViewer Start/Stop: rights to start/stop NetViewer services.
- Services Configuration: rights to modify the configurations of NetViewer Services.
- Collect Info Configuration: rights to access to the Debug tool.
- Local User Management: rights to create/modify/delete the local User.
- Map Create: rights to create new maps.
The rights can be assigned separately to each Users and are valid for the selected server and are
subjected to the hierarchy here reported:
System Permission inherited Permissions
Map Map NetViewer NetViewer NetViewer NetViewer NetViewer

Open/close Reload Start/Stop Start/Stop Start/Stop Start/Stop Start/Stop
assign. Map X X X
Permis. Open/close
Map X
Reload
NetViewer X X X X X
Start/Stop
Services X X
Config.
Collect info X X
Config.
Local User X
Maneg.
Map create X
As default the following permissions are assigned to the group NetViewerAdmins:

- Map Open/Close

Issue 1 Draft 1
NetViewer 9.7
- Services Configuration
- Collect Info Configuration
- Map Create
Figure 3.32: the System Permission Management window
Selecting Add/Remove the Permissions can be modified: other Permissions can be assigned/removed
to the Groups/Users created by the User Management.
Figure 3.33: Add Permissions
3.1.7.5 Add/Move Permissions to the Map

The Map Permissions allows to assign/remove the Permissions of the Map to the Groups/Users: it is
applicable to the map reported in the main frame of the window of NetViewer Client, only via
SysAdmin.
The Permissions of the Map are:
- Use SW Download: to enable the network SW Download via the SW Download Manager.
- Change the Access Rights to Network Elements: to modify the User Class of the server
simultaneously on all the NE’s of the network via the Map Summary application.
- Allow NML Operations: to work with the Path Manager.

Issue 1 Draft 1
System details
- Rx Power Collection Settings: to modify the sampling period for detecting the measurements of
the Rx Power Collection
- Map Inventory: to start the application Map Inventory.
As default all the permissions are assigned to the group NetViewerAdmins while all the other Groups
haven’t any permission.
Figure 3.34: Map Permissions Figure 3.35: the Map Permission

window
Selecting Add/Remove the Permissions can be modified: other Permissions can be assigned/removed
to the Groups/Users created by the User Management.
Figure 3.36: Add Permissions

Issue 1 Draft 1
NetViewer 9.7
3.1.7.6 Identity management via external applications

From NetViewer V8.0 the Users identification can be selected between the existing internal application
and an external one. The external application supplied is the Active Directory of Microsoft Windows
2003 server, but other Identity Managers, such as ones of the Customer’s organization, can be directly
connected to NetViewer.
In such a way the features relative to the NetViewer access are aligned to the security standards.
Internal Identity Manager

NetViewer
Access OR
External Identity Manager
of MS Windows 2003 server
OR
External Identity Manager
of the Customer’s
Figure 3.37: Users Identification selection
Follow the main features coming from the Identity Manager of MS Windows server:
- the password lengths
- the password number and types of characters,
- the automatic lock of the account after a defined unsuccessful logon attempts
- not reusability of the most recent expired passwords
- automatic log off after a defined period of inactivity
- password ageing
The selection of the Identity Manager has to be done in NetBuilder, choosing the Configuration of the
Menu Bar.
The IP address of the PC where the External User Manager is installed has to be specified.
Figure 3.38: Setting User Manger Figure 3.39: Setting External User Manager

Issue 1 Draft 1
System details
3.1.7.7 Sub-domain management

The sub-domain management allows to split the network managed by NetViewer in more domains and
to assign each of them to the different Users having different privileges.
The sub-domain management is realized assigning the permissions to each objects of the map:
Map, Sub-map, Sub-server, NE.
The window for assigning/removing the Permissions to the Groups/Users is opened clicking the right
button of the mouse directly on the map, on the icon of the sub-maps/sub-server/NE.
Figure 3.40: Permissions on NE
The permissions are the following:

• User class Admin on NE: permissions of writing, change of the security status and password (via
NV Client)
• User class RW on NE: permissions of writing (via NV Client)
• User class RO on NE: permissions of reading (via NV Client)
• Acknowledgement: permissions of alarm acknowledgment of NE/submap/ slave server alarms (via
NV Client)
• Server Connection: permissions of modifying the connections status among the server and the
Objects of the map;
a) change User among server and NE’s/salve servers (via NV Client)
b) definition of the object properties (via NetBuilder Client)
c) reload map of the slave servers (via NV Client and NetBuilder Client)
d) enable/Disable of NE’s/sub maps/ slave servers (via NV Client and NetBuilder Client)
e) synchronization of the NE’s/sub maps/ slave servers (via NV Client and NetBuilder Client)
f) writing of the description into NE’s/sub maps/ slave servers (NV Client and NetBuilder Client
The permissions are grouped in 4 classes: the permissions of each class cannot be modified.
Permissions on Class Class Class Class Monitor

the object of the map Administrator Readwrite ReadOnly
Admin su NE X - - -
RW su NE X X - -
RO su NE X X X X
Acknowledgement X X X -
Server Connection X - - -
It is possible to assign the following Permissions on the object of the map:

- Administrator

Issue 1 Draft 1
NetViewer 9.7
- ReadWrite
- ReadOnly
- Monitor
Selecting Add/Remove the Permissions can be modified.
Figure 3.41: Permissions on NE
3.1.7.8 Security mechanism
A Security mechanism is present as at Server level as at NE one; the two Security levels are
independent and work on parallel planes. Each user can change its passwords.
The Server Security is always enabled and it is not possible to disable it.
The enabling status of the NE Security can be changed; the disabled Security condition provides for
that level the Admin prerogatives. The Security mechanism to access to the menu commands of the
Net Viewer Server program is activated by means of the “Lock Workstation” function of Windows.
Server Security
The Server Security defines the access prerogatives to the Server.
The Configuration of the Security (passwords for the different user classes) is executed by means of
the NetBuilder tool for the Server configuration; it is reported into the configuration file (map) of the
Server.
The Server Security allows the identification of the users connected and the correct management of
the contemporaneous accesses. It is possible to set/change, by means of the NetBuilder tool, the
passwords of the Server Security.
Single Sign-on
If an Active Directory system is used to manage the users for both NetViewer and Windows OS is
possible to apply the single sign-on functionality where one user name & password allows to access to
both NetViewer GUI and NetViewer Server an.

Issue 1 Draft 1
System details
3.1.7.9 Management of user privilege release
In case of inactivity time period is possible to force the NetViewer GUI logout for the server connected.
The inactivity time period can be configured.
This functionality allow to avoid to live a NetViewer GUI process active if no more need releasing
machine resource.
If a Read/Write section on a NE has bee open by an NetViewer operator and in a time period non
actions have performed the NetViewer provide to declass the connection in to ReadOnly priority. The
Inactivity time period can be configured.
One operator with appropriate privilege can force the logout of other NetViewer operator(s) connected.
This operation can be performed both form NetViewer and NetBuilder.
Network Management Layer within NetViewer
NetViewer with Path Management becomes the Network Management Layer.
The following features are the key features:

• Provide a logical view of the Network;
• Shows the impact of faults on topological links (“link state in NV map”)
• Shows the impact of faults on services;
• Automatic discovery of 2 Mb/s and STM-1 services;
• GUI fully integrated in NVClient.
Refer to the: Technical Product Description of Path Manager.

Issue 1 Draft 1
NetViewer 9.7
3.1.8 NetViewer - System Functions
3.1.8.1 Data Storage Concept and Standby
System Availability
The high demands on data security and system availability of the NetViewer System require an
advanced security concept. Precautions against critical failures in software and hardware components
need to be taken. This concept is based on the following techniques:
• usage of mirror disks
• sage of UPS units
• availability of a warm standby server
• database backup
• Autoarchive function
Mirror Disks
NetViewer database and the entire data disk are replicated in two identical SCSI mirror disks. The
control over the mirror disks and the automatic data synchronization between them are handled by a
SCSI RAID 1 Controller System.
A breakdown of one of the hard disks does not influence the system. The controller is running the
system on the intact disk further on. In the meantime, the defected disk can be replaced by another
disk. After then the controller is re-synchronizing the new disk with the second one.
3.1.8.2 Database Backup
To minimize loss of data, when a system component breaks down, the NetViewer System provides the
possibility of the manual backup of its databases. In case of software failure, the backup-set can be
used to restart the system. If the operator wants or has to recover a previous backup-set he can
provide the manual restoration.
3.1.8.3 Autoarchive Function
The “auto-archive” functionality consists in keeping, in a proper space, all that information which is
periodically deleted from the Database of NetViewer, because the deletion threshold has been
reached or because of the manual deletion of the entries present in the different tables.
Two Database typologies are foreseen for the auto-archives:

• one for PM data
• one for event data
It can be assigned dedicate rules for autoarchive to each database typology.

Issue 1 Draft 1
System details
Moreover it is also possible to configure the max size of Autoarchive Database. As default the size is
200Mbyte; the max size allowed is 10% of disk size.
In particular, all the entries deleted from the following tables of NetViewer are automatically inserted
into another Database to be used in post-processing phase:
– events
– measures_periodical
– measures_scheduled
– pm_switching_values
– pm_entries
– pm_radio_power_values
– pm_standard_values
The “auto-archive” functionality foresees the automatic creation, in sequence, of more archive
Database; a new archive Database is created each time the current archive Database reaches the
maximum set dimension.
However, the storing of max. five archive Databases is foreseen (the five most recent Databases), by
means of the possible automatic deletion from the archive Database on the creation of a new archive
Database.
The “auto-archive” functionality is available only with Database of NetViewer based on Microsoft SQL
Server format (Single Server and Multi Server configuration of NetViewer).
NetViewer Server PC 1
NetViewer
Server
Current
DB
MS SQL Server 2000 Archive

DB 1
Figure 3.42: Archive Database

Issue 1 Draft 1
NetViewer 9.7
3.2 System administration NetBuilder
NetBuilder, the NetViewer System administration, is a defined set of functions applicable to the
management software. Certain aspects of security, design and usability techniques lead to a
separation of the system administration functionality from the NetViewer Server and the NetViewer
Client.
It’s important for a management system to limit the number of users and their privileges, concerning
configuration, monitoring and security functionality to avoid interference in other management
functions.
The NetBuilder application handles all configurations, monitoring and security features related to the
NetViewer System in a secure and easy to use way. This system administration application can only
be accessed by the Administrator SysAdmin. SysAdmin User creates Groups/Users and assignees
Permissions so to avoid the conflicts of competence among them in their administration functions.
NetBuilder (the NetViewer System Administration tool) was redesigned for performing its
functionalities directly from the NetViewer Client PC without the need to access to NetViewer Server
PC.
The application was separated into a Server and a Client part: the server one (NetViewer System
Administration Service) is installed into NetViewer Server PC, while the Client one (NetBuilder) into the
NetViewer Client PC.
It is so possible the creation of NEs, Subnets, Sub-servers and users directly from the NetViewer
Client PC.
The big advantage of the new Client/server structure of NetBuilder is the possibility to do all the tasks
required by NetViewer directly from the NetViewer Client PC without any access to NetViewer Server
PC, that could be located in a different room.
The main administrative tasks, which can be performed directly from the client, are:
NetBuilder Client
Users management
Assign Permissions
Services management
Database configuration
Server management
Map summary
Map creation: add/remove NE, sub-net, sub-server
etc.
NE find function
Radio Link Auto-discovery
NE Auto-discovery
Editing a comment to each NE (max 250
characters)
Import/export lists of NE’s

Issue 1 Draft 1
System details

Issue 1 Draft 1
NetViewer 9.7
3.3 Graphical User Interface (GUI)
This chapter explains the general features of the graphical user interface.
3.3.1 General Features
One of the key features of the user interface design is the standardized display and behavior of visual
elements such as icons and controls. By using a standardized display of visual elements the user is
able to recognize the meaning or behavior of these elements regardless of their occurrence. The
functionality and visualization directly correspond to each other, so that the user is able to intuitively
understand their meanings.
In general the design of the user interface components are based on the Microsoft Style Guide
providing user friendly pull down menus and drag & drop operation. The grey color is used for showing
the no availability of some items on NetViewer Client screen.
3.3.2 GUI
The NetViewer GUI is implemented with Java language.

The GUI is divided in three frames (figure 9.7). In the map frame, the NE’s of the Network and their
links are reported (figure 9.7 A). Another frame shows the tree view of the map for a quick access to
NE’s: Network View (figure 9.7 B). The last frame contains the tree view of a NE, selected from one of
the previous frames: NE View (figure 9.7 C)..

Issue 1 Draft 1
System details
Figure 3.43: NetViewer GUI look
NEs, subservers and subnetworks can be opened in three ways:

♦ through the relevant popup menu
♦ double-clicking onto the icon in the map frame
♦ double-clicking onto the icon in the tree view of the map
To each windows is available the functionality “Always on the top”. Setting this functionality the relate
windows will be always on the top.
This configuration will be Operator dependent.
When a NE is opened, the relative properties and data are shown in the NE tree view.
3.3.3 Status Bar

The Status bar in the bottom of the frame window of NetViewer Client reports information useful for the
network management.
When the mouse is over a NE icon, in addition to the tool tip information, the Status Bar supplies:

Issue 1 Draft 1
NetViewer 9.7
- the user class used by NetViewer for the access to NE if the NE is on line and opened the Security is
enabled.
- the permission of the User about NE, if NE is on-line and not opened.
- the status of NE (off-line o disconnected) if NE is not on-line
- it is reported the message “Another Read Write manager is already logged to this NE”, when anther
User of
NetViewer is already connected to NE with the “Write” permission, or if another Manager (e.g. LCT)
is
connected to NE with “Admin” permission.
The Status Bar is reported in: e.g. NCT User has the permission of Administrator on the selected NE.
Status Bar
Figure 3.44: the Status Bar
3.3.4 FIND
The direct access to the NE is activated automatically clicking onto a row of the following applications:
a) Alarm List
b) History Report
c) Performance Report
d) External alarm table of the alarm list
So the selected NE is shown in the three frame of the NetViewer GUI.

Issue 1 Draft 1
System details
Figure 3.45: Views of the selected NE
In NetViewer GUI also the NE find command is available. It is used to search NEs, sub-networks and
subservers. This function can be activated:
• through the find icon
• through the popup menu in the map view
• through the popup menu in the tree view of the map
Figure 3.46: NE find function
The search options are the name, the address and the protocol (used by the NE towards NetViewer)
of the element to looking for (fig. 9.15). The search result is a list of elements; if an element is selected
with a double click, it is shown in all views: map view, tree view of the map, tree view of the NE.

Issue 1 Draft 1
NetViewer 9.7
Figure 3.47: Search options
3.3.5 Browsing to the neighboring NE
From release 7.0 onwards, it is easy to navigate from a radio NE to its adjacent ones. The feature is
particularly useful in the case of linked NE’s belonging to different maps: with a simple double-click,
the map of the peer NE is opened (through the Jump-To-Peer functionality).
After having activated the NE pop-up menu clicking with the right-hand push-button of the mouse on
the icon of the desired NE and selected Link of NE all the links that terminate on the NE are
displayed in table format as shown in.
Figure 3.48: Search options
A double click on the row of the table selects the NE where the corresponding physical link ends; this
operation closes the window for the displaying of the physical link and the map/sub-map containing
the NE is brought in foreground.
3.3.6 Writing a description
It is possible to edit a row of comments (up to 256 characters) for each NE, Sub-map and server from
NetViewer Client application.
The window for inserting the comment is shown in.

Issue 1 Draft 1
System details
Stm1-1 to be connected within

this week (July 4, 2004)
Figure 3.49: External alarms editing from NetViewer Client
The presence of the inserted comment, detected by a Blue triangle is reported in the tool tip of the
NE, Sub-map, server (Figure 9.19).
Blue triangle
triangle
Cremona 1
Figure 3.50: External alarms editing from NetViewer Client
3.3.7 Online Help
The NetViewer supports context sensitive online help system - with index, hyperlinks.
3.3.8 Logs & Lists
In a TMN environment, many events and actions occur spontaneously. To guarantee a complete
surveillance of the entire network activity, an event logging is supported. NetViewer distinguishes
between system events and operator’s events. Since it's necessary to detect the correlation between
operator’s actions and network state changes both kind of actions are logged.
The following logs are provided:
• History
• Security
The following lists are provided:
• Configuration monitoring
• Active alarm
• Active external alarm
Every log and log can be printed with the command Print to file.

Issue 1 Draft 1
NetViewer 9.7
3.4 Data base

As NetViewer monitors a very large network in Multi/Single Server configuration, it uses Microsoft SQL
Server as its internal Database.
The following components are all included in the Standard Edition:
– Sql Sever 2005 Integration Service (SSIS).
– Replication (of snapshots, transactions and merges).
– Full text search
– English Query.
– Tools for the development and the debugging of the stored procedures.
– Tools for the analysis of the performance and the SQL.
– Support of a Client to execute queries or report.
®
The two NetViewer Entry Configurations continue to write the database with MS Access format.
Password protection for SQL server access

The post-elaboration Database is protected by means of a password known only by the network
administrator or by qualified personnel. This allows the access to the Database information only to the
authorized personnel that has the task to execute research on the data stored in it.
Microsoft SQL Server gives the possibility to use the same protection policy of the Microsoft Windows
operating system. In fact, it allows associating the users defined in Microsoft Windows to the
Database, with the same characteristics and, then, possible restrictions.
All the operations can be executed only by the administrator of the Database, who is identified by the
"sa" user.
Back-up
For the backup of the Database, a copy of the ".mdf" and ".ldf" files is generated.
Also the backup functionality proper of the Microsoft SQL Server product can be used, that foresees
also the possibility to schedule the backup itself.
An Autoarchive function is also available and it gives the possibility of saving in a backup database, in
automatic mode, the data lost after a scheduled delete operation.
3.4.1 Content
The following data are stored in the Database:
• Network Events.
• Acknowledged Events.
• Network Configuration.
Other data stored:

• NE’s of the map.
• Operator Log.

Issue 1 Draft 1
System details
For the Events and PM data base tables (one table for each PM type) the max number entries
foreseen is 800000
3.4.2 Settings
Follow the possible settings:
• Configurable limit of data storing, automatic deleting of data after a configurable number of
days, keeping only a configurable number of data.
• Enable/disable PM Data Presence Event.
• Delete all data, delete older data from a configurable data.
• Automatic backup every a configurable time.
• Warning message for approaching Database Capacity Limit.
• Measurement of the percentage of the database filling.
• Configurable Database dimension.
Alarm visualization format:

• Standard.
• On/off alarm correlation.
Event Table:
To optimize the Event table size is available the functionality that avoid to save in the table the event
3
notification related to “ceased alarm” .
This functionality can by enabled/disabled by Operator.
3.4.3 History Report

The History Report of the whole Network is managed by the different filters of the section Search
(Figure 9.28):
• Acknowledged by.
• Network Element.
• Event name.
• Equipment Type.
• Severity.
• Data & time.
The operators “=, <>, LIKE” are applicable to Event name and Network Element.
Two options are selectable for Acknowledged by, Equipment Type, Severity:
• Any or a specific Acknowledged by, Equipment Type, Severity
• Multiple. AND & OR operators are applied to the Queries.
The section Search can be closed for analyzing the results of the queries.
3
When this functionally is enabled the History Report is automatically configured in
ON-OFF Alarma Correlation modality.,

Issue 1 Draft 1
NetViewer 9.7
Figure 3.51: Section Search of the History Report
History Report columns

The History Report supplies the columns:
• event sequence.
• data & time.
• NE name.
• Equipment type.
• Severity.
• Event name.
• Acknowledged by.
• Ack Date &Time.
“Clear Data Time” column is added to the History Report if the “On/Off alarm correlation” was activated
in the Options of the Database configuration.
Tool tip is available by mouse for reading all data of the row without scrolling the window report.

Issue 1 Draft 1
System details
Figure 3.52: History Report and tool tip
History Report of the Single NE

The History Report of the single NE is available too, with the same features of the whole one and
without the filters/columns Equipment Type/name. It activated by the frame NE View.
Figure 3.53: History Report
Options
The Options window allows to set the visualization options of the History Report of the Network and
NE:
• On/Off Alarm Correlation Mode; when the box is selected, the life of the alarms (on/off) are reported
on the same row.
• Events reporting options:
- PM Data Presence Events.
- NE Events.
- NE Configuration Events.
- NetViewer Server Events.

Issue 1 Draft 1
NetViewer 9.7
Figure 3.54: History Report Options
Customize Tables
The tables generated by the History Report (Network and NE) can be customized in terms of Sort
and hide. The order of the columns can be changed and the columns can be hided (Figure 9.32).
Figure 3.55: Customize Tables

Issue 1 Draft 1
System details
Options
The Options window allows to set the visualization options of the History Report of the Network and
NE (Figure 9.35):
Figure 3.56: Performance Report Option
Customize Tables
The tables generated by the Performance Report (Network and NE) can be customized in terms of
Sort and hide. The order of the columns can be changed and the columns can be hided: applicable
to each types of Perfomance Measurements (Figure 9.36).
Figure 3.57: Customize Tables
3.5 Export Data from the Database with SSIS

®
With of SQL Server 2005, Microsoft has delivered a new technology to query a Database and
retrieves data to improve the previews Data Transformation Service (DTS) technology. This new
technology is the Sql Server 2005 Integration Services (SSIS).

Issue 1 Draft 1
NetViewer 9.7
SSIS provides a set of tools that lets to extract, transform, and consolidate data from NetViewer
Database into single or multiple destinations. By using SSIS tools, it is possible to create data
movement solutions tailored to the specialized needs.
These tools are available for creating and executing SSIS packages:
- the Import/Export Wizard is for building relatively simple SSIS packages, and supports data migration
and simple transformations.
- the SSIS Designer graphically implements the SSIS object model, allowing you to create SSIS
packages with a wide range of functionality
It so possible, for example, to access to NetViewer Performance Measurements, select the measures
to be exported, sort them as required by the end application, separate each value with “,” “_” or other
and at last activate the transferring of the data: SSIS includes FTP task, the Execute Package task,
the Dynamic Properties task, and the Message Queue Task.
A SSIS Package is a collection of SSIS Connections towards Data source, SSIS Tasks, SSIS
Transformations and rules of workflow. All these elements are easily build with SSIS Designer tool
(Refer to the technical documentation by Microsoft).
The SSIS Designer interface consists of a work area for building packages, toolbars containing
package elements that you can drag onto the design sheet, and menus containing workflows and
package management commands.
By dragging connections and tasks onto the design sheet, and specifying the order of execution with
workflows, you can easily build powerful SSIS packages using SSIS Designer. The following sections
define tasks, workflows, connections, and transformations, and illustrate the ease of using SSIS
Designer to implement a SSIS solution.
SSIS is activated manually or automatically via Windows Scheduler.
3.6 MS Windows Terminal Services, Citrix Metaframe,

support
NetViewer is compatible with Citrix MetaFrame.
This solution allows:
• the centralized management of Client applications;
• Operator Environment abstracted from Client Application. GUI can be delivered to desktops
running different OS’s.
• Uses a Thin Client to deliver the application to the user
• Very high performance over low bandwidth LAN, RAS, or high latency connections
• Highly controlled and secure Client application environment
• Application agnostic: Incompatible applications can be segregated to different servers within the
farm, however the applications will appear to the operator via a single ICA/Web interface
The architecture is described in the following picture.

Issue 1 Draft 1
System details
Server PC Server PC Users PC

ICA Client
LAN
NetViewer
Application
LAN / WAN / RAS / Firewall

Client
Application
Other
Applications
MS Windows TS
Thin” ICA”
NetViewer Citrix MetaFrame Protocol Users PC
Server Application ICA Client
Application
Application
Other
Applications
Figure 3.58: the architecture
NetViewer Client Application is installed into a Server PC dedicated to MS Windows TS: Citrix
MetaFrame has to be added if it is required. The Users access to this server for managing the GUI of
NetViewer Client.
The screen of the Server can be used for opening more sessions of NetViewer Client Application
as required by some Customers.
Server PC HW requirements and Capability

The main requirements for the Server PC where NetViwer Client PC is installed are the following:
- Processor: 2 x Xeon or equivalent, 3.6 GHz
- RAM: 4 GB
Capability: max 10 NetViewer Client sessions.

If more sessions are required, another Server PC is required.
In any cases, not more that 20 NetViewer Client sessions can work simultaneously with NetViewer
Server Application.
Citrix Presentation Server
NetViewer is also compatible with Citrix Presentation Server.

Citrix Presentation Server is the evolution of Citrix Metaframe, already supported by NetViewer.
The new features available with Citrix Presentation Server 4.0 are:
- Load Balancing
For distributing the load of the applications (NetViewer Client) automatically among the servers of a
Citrix Farm.
- Connection Control
For managing the Users and their connections to Citrix.
- Web Interface
An evolution of the previous Web Interface.
- Bandwidth Control
For controlling the bandwidth of the connections to Citrix Server.
- Encryption of the Citrix Interface
Different types of encryption are available for creating a secure Citrix Interface.

Issue 1 Draft 1
NetViewer 9.7
The feature Isolation Environment, that allows to isolate any applications running in the same Citrix
Presentation Server, avoiding in such a way the possible conflicts, is not applicable to NetViewer 9.7 .
Citrix Server manages one NetViewer Single Server (or Multi server):
Windows 2000/2003 Server
Windows 2000/2003 Server
Figure 3.59: Citrix server and one NetViewer Single server

Issue 1 Draft 1
System Technical Specification
4 System Technical Specification
4.1 Managed network elements
The network elements supported are described in the following table:

4
Equipment Equipment Type and the relative Communication protocol to NetViewer
Family TNMP over TCP/IP OSI over SNMP over TL1 over
TCP/IP UDP/IP TCP/IP
SDH SPS E SRT 1C SRT1F
SRA S3 SRT 1S
SRA 4 SRT 1
SRA 4K SPS 155
SRA 4 ADM SRA
PDH SRA L FTFA
SRAL XD Plug-in FIU19E
SRAL XD
SingleBoard
SRAL XD MinIDU
SRAL XD TwoE1
MicroHop
DualQ-Adapter
Narrowband TDMoP
DF CX
DF 1/4
SNMP Generic Devices
Alarm Converter
WayMAX Base Station
4
Detailed information about supported NE types and features covered by each
corresponding NetViewer version can be found
• NetViewer Plug-in Inventory
• NetViewer Customer Feature List document.

Issue 1 Draft 1
NetViewer 9.7
5
Mediation Devise Q1 Agent
4.2 Hardware
NetViewer is a PC based TMN system developed and designed to run on x86 compatible PC’s on
Microsoft Operating Systems. As an option the system can be enhanced with a redundant standby
server.
HW Platform Configuration NV Server NV Client

Figure 17-1 Figure 17-2
2 x CPU Intel XEON DP 5050, 3.0 GHz X -
CPU Intel Core 2 Duo, E6600 - X
2 GBytes RAM - X
4 GBytes RAM X -
SCSI Hard disk, 15kRPM, 73 GBytes X X
Disk mirroring function X -
3.5” floppy disk drive of 1.4 Mbytes X X
Video card with 8 Mbytes RAM or higher X -
Video card with 128 Mbytes RAM or higher - X
Ethernet ports 3 1
Sound card - X
TFT Color monitor 19” 19”
CD-ROM drive X X
Tape backup unit X
Mouse X X
USB port for dongle X -
All information presented about PC types is valid at the point of time when this document was created.
Due to the rapid changes on the PC market all information given may change by Nokia Siemens
Networks without prior notification.
4.3 Software
The NetViewer software requires the following OEM products:
Server
5
For the detailed list of Q1 Network elements supported by Q1-Agent and managed by
NetViewer please refer to the Q1 Agent product technical description documents

Issue 1 Draft 1
System Technical Specification
MS Windows 2003 Server SP1 (English version)

or MS Windows 2003 Server R2 (English version)
Server with Warm Standby configuration

MS Windows 2003 Server SP1 (English version)
or MS Windows 2003 Server R2 (English version)
Client
Microsoft Windows XP Professional SP2 (English version)
Microsoft Windows Vista Professional SP1 (English version)
Entry Configuration
Microsoft Windows XP Professional SP2 (English version)
According to the NetViewer System configuration the following additional OEM components
are required:
Server/Multiserver configuration:
- Microsoft SQL Server 2005 Standard Edition SP1 (English version)
Entry configuration:
- Microsoft Access (English version)

Issue 1 Draft 1
NetViewer 9.7
Appendix
Not Applicabile

Issue 1 Draft 1
References
References
1.

Issue 1 Draft 1
NetViewer 9.7
Glossary
ACI Access Integrator

AIS Alarm indication Signal
CDM Cross Domain Manager
CMX PDH Cross Connect Multiplexer
CORBA Common Object Request Broker Architecture
CPE Customer Premises Equipment
CSW Context Sensitive Windowing
DCN Data Communication Network
DCOM Distributed Component Object Model
DDE Dynamic Data Exchange
DECT Digital Enhanced Cordless Telecommunication
DWDM Dense Wavelength Division Multiplexing
ECC Embedded Communication Channel
GNE Gateway Network Element, i.e. a NE connected to the DCN
GUI Graphical User Interface
HDLC High level Data Link Control
IF Interface
ISDN BRA ISDN Basic Rate Access
ISDN PRA ISDN Primary Rate Access
ISO International Standardization Organization
ITU International Telecommunication Union
LAN Local Area Network
LCT Local Craft Terminal
LL Leased Line
MTNM Multi Technology Network Management
MTBF Mean Time Between Failures
NE Network Element
OEM Original Equipment Manufacturer
OLE Object Linking and Embedding
OS Operation System
OSI Open System Interchange
OSN Optical Service Node
PABX Private Automatic Branch Exchange

Issue 1 Draft 1
Glossary
PDH Plesiochronous Digital Hierarchy

PMP Point to Multi Point microwave
POTS Plain Old Telephone System, i.e. analogue telephony
RAS Remote Access Server
Qx OSI stack for Microwave equipment
SDF System Data Format
SDH Synchronous Digital Hierarchy
SkyWeb Point to Multi Point Microwave
SMS Short Message Service
SMTP Simple Message Transfer Protocol
SNMP Simple Network Management Protocol
SPS 155/E STM1 Switching Microwave Equipment
SRA Point to Point STM1 Medium Capacity Access Microwave
SRA L Point to Point PDH Low Capacity Access Microwave
SRAL XD Point to Point PDH Low Capacity Access Microwave
SRA Series 3 Point to Point STM1 Medium Capacity Access Microwave
SRA 4 Point to Point STM1 Medium Capacity Access Microwave
SRT 1 Point to Point STM1 High Capacity Trunk Microwave
SRT 1C Point to Point STM1 High Capacity Trunk Microwave
SRT 1S Point to Point Sub-STM1 Medium Capacity Access Microwave
STM Synchronous Transport Module
STM1/4/16 Synchronous Transport Module (155Mbit, 622 Mbit, 2.4GBit)
TCP/IP Transmission Control Protocol/Internet Protocol
TMN Telecommunication Management Network
TNMP Trivial Network Management Protocol for Microwave equipment
TNMS C Telecommunication Network Management System Core
UDP User Datagram Protocol
WAN Wide Area Network
WayMAX SIEMENS WiMAX Equipment
WiMAX Worldwide Interoperability for Microwave Access
XML eXtensible Mark up Language

ACI Access Integrator
AIS Alarm indication Signal
CDM Cross Domain Manager

Issue 1 Draft 1
NetViewer 9.7
CMX PDH Cross Connect Multiplexer

CORBA Common Object Request Broker Architecture
CPE Customer Premises Equipment
CSW Context Sensitive Windowing
DCN Data Communication Network
DCOM Distributed Component Object Model
DDE Dynamic Data Exchange
DECT Digital Enhanced Cordless Telecommunication
DWDM Dense Wavelength Division Multiplexing
ECC Embedded Communication Channel
GNE Gateway Network Element, i.e. a NE connected to the DCN
GUI Graphical User Interface
HDLC High level Data Link Control
IF Interface
ISDN BRA ISDN Basic Rate Access
ISDN PRA ISDN Primary Rate Access
ISO International Standardization Organization
ITU International Telecommunication Union
LAN Local Area Network
LCT Local Craft Terminal
LL Leased Line
MTNM Multi Technology Network Management
MTBF Mean Time Between Failures
NE Network Element
OEM Original Equipment Manufacturer
OLE Object Linking and Embedding

Issue 1 Draft 1
Index
Index
Not Applicable
Error! No index entries found.

Issue 1 Draft 1

NV9.7 TPD 080808 1

Uploaded by

Copyright:

Available Formats

NV9.7 TPD 080808 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NV9.7 TPD 080808 1

Uploaded by

Copyright:

Available Formats

NetViewer Suite

NV9.7-TPD-080808-1 © Nokia Siemens Networks 1 (75)

2 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

2 System overview .................................................................................. 8

NV9.7-TPD-080808-1 © Nokia Siemens Networks 3 (75)

4 System Technical Specification........................................................ 67

4 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

NV9.7-TPD-080808-1 © Nokia Siemens Networks 5 (75)

6 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

Figure 1-1: NetViewer product positioning

NetViewer EMS provides:

NV9.7-TPD-080808-1 © Nokia Siemens Networks 7 (75)

Figure 2-1: System Architecture of NetViewer

8 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

2.1 Flexible SW architecture

NetViewer is endowed with flexible software architecture based on Client-Server solution.

2.2 NetViewer Engine

2.2.2 NetViewer Server

NV9.7-TPD-080808-1 © Nokia Siemens Networks 9 (75)

2.2.3 Data Base manager

2.2.4 NetViewer Client

10 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

NV9.7-TPD-080808-1 © Nokia Siemens Networks 11 (75)

2.2.7 Southbound interfaces

2.2.7.1 Q1 Agent Interface

12 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

2.3 Hardware Architecture

2.3.1 NetViewer Large configuration - Multi-server

WAN Inter- / Intranet

NetViewe NetViewer NetViewer

Figure 2.1: NetViewer Large Configuration - Multi server

NV9.7-TPD-080808-1 © Nokia Siemens Networks 13 (75)

Table 1: Numbers of Clients simultaneously connected to a NetViewer system

2.3.2 Q1 Agent Integration

Here following the system architecture for Q1 Agent integration.

14 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

ICA client ICA client

NetViewer Node Manager

Figure 2-2 – NetViewer – Q1 system architectures

NV9.7-TPD-080808-1 © Nokia Siemens Networks 15 (75)

2.4 Web Interface

2.5 Element Management Layer within NetViewer

2.5.1 Node Manager Server

16 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

NV9.7-TPD-080808-1 © Nokia Siemens Networks 17 (75)

3.1 Management Functions

18 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

Figure 3.1: Management areas table

3.1.1 Fault Management

3.1.1.1 Alarm List

NV9.7-TPD-080808-1 © Nokia Siemens Networks 19 (75)

20 (75) © Nokia Siemens Networks NV9.7-TPD-080808-1

Figure 3.4 Active Alarms Summary

Alarm List of the Network

Column Hide/ Mobile Default

Alarm List of the single NE

Column Hide/ Mobile Default

Alarm List of External Alarms

Column Hide/ Mobile Default