911-431 02a0120

Operating Manual
NA-NV Connector 1.2

OMN
911-431/02A0120
Issue 1, March 2009
The information in this document is subject to change without notice and describes only the product defined in the introduction of this
documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement
under which the document is submitted, and no part of it 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. However, Nokia Siemens Networks has made all
reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. 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 MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT.
This documentation 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 2009. All rights reserved.
NA-NV Connector 1.2 - OMN

911-431/02A0120 - Issue 1, March 2009
STATUS OF MANUAL
STATUS OF MANUAL
Current:
Previous:
Issue 1, March 2009
This issue describes the installation and the configuration of the NA-NV Connector V1.2
software application.

911-431/02A0120 - Issue 1, March 2009
R-1
LA
PA
STATUS OF MANUAL
R-2

911-431/02A0120 - Issue 1, March 2009
INDEX
INDEX
STATUS OF MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .R.1
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.1
LIST OF ILLUSTRATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I.3
GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

1.1
Purpose and Subject of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1
1.2
1.2.1
1.2.1.1
1.2.1.2
1.2.2
1.2.3
1.2.3.1
1.2.3.2
1.2.3.3
1.2.3.4
1.2.3.5
1.2.3.6
1.2.3.7
Functions of the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

NetAct. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1
Mediation and adaptation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2
NetViewer - NetAct interaction note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2
NetViewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2
NA-NV Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2
Basic Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3
Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3
Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3
EMS GUI Remote launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3
Configuration supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4
Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4
3rd party software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4
1.3
1.3.1
1.3.2
Software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4

NetViewer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5
NA-NV Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5
1.4
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6
1.5
Supply Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6
1.6
Licenses for the use of the software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6
1.7
Related Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6
1.8
List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7
1.9
Network configuration for the remote management of the NetViewer GUI . . . . . . . . . . . . . . 1.8
1.10
System performances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.9
1.11
1.11.1
1.11.2
Firewall configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.9

Firewall between O&M Agent and NetAct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.9
Firewall between Citrix Server and Client PC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.10
SOFTWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

2.1
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1
2.2
2.2.1
2.2.2
2.2.3
Installation of NA-NV Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

Server installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1
Client installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4
Maintenance procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4
2.3
Verification of the installed services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5

911-431/02A0120 - Issue 1, March 2009
I-1
INDEX
2.3.1
2.3.2
EQUIPMENT MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

3.1
3.1.1
I-2
Stop/start of NetViewer services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5

Configuration of O&M Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7
Supported equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

Sra4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1
NETWORK CONFIGURATION TO REMOTIZE THE GUI OF NETVIEWER . . . . . . . 4.1

4.1
Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1
4.2
4.2.1
4.2.1.1
4.2.1.2
4.2.1.3
4.2.2
4.2.2.1
4.2.2.2
4.2.2.3
Remote management of the NetViewer GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3

Citrix Server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3
Publishing of NetViewer on Citrix Presentation Server 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3
Isolation Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6
Configuration of NetViewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9
Configuration of Client PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10
Configuration of Client with application published on Citrix Server . . . . . . . . . . . . . . . . . . . 4.10
Configuration of Client without publishing of the application on Citrix Server . . . . . . . . . . . 4.11
Command line from Client ICA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.12
4.3
4.3.1
4.3.2
4.3.2.1
4.3.2.2
4.3.3
4.3.4
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access to Windows Terminal Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Access to Citrix Presentation Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selection of the users with rights of execution of the applications . . . . . . . . . . . . . . . . . . .
Configuration of ICA protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Login to NetViewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration of the access to DB of NetViewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.13
4.13
4.13
4.13
4.13
4.14
4.14
INSTALL AND CONFIGURE THE PERFORMANCE MANAGEMENT FRAGMENT. A.1

A.1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.1
A.2
Install NA-NV Connector PM fragment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2
A.3
Configuring local FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4
A.4
Enabling Performance Data export service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.6
A.5
A.5.1
A.5.2
Configuring fine grained PM data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8

Global Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.9
Specific Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.10

911-431/02A0120 - Issue 1, March 2009
LIST OF ILLUSTRATIONS
Fig. 1.1
Fig. 1.2
Fig. 2.1
Fig. 2.2
Fig. 2.3
Fig. 2.4
Fig. 2.5
Fig. 2.6
Fig. 2.7
Fig. 2.8
Fig. 2.9
Fig. 2.10
Fig. 2.11
Fig. 2.12
Fig. 4.1
Fig. 4.2
Fig. 4.3
Fig. 4.4
Fig. 4.5
Fig. 4.6
Fig. 4.7
Fig. 4.8
Fig. 4.9
Fig. 4.10
Fig. 4.11
Fig. 4.12
Fig. 4.13
Fig. 4.14
Fig. 4.15
Fig. 4.16
Fig. 4.17
Fig. 4.18
Fig. 4.19
Fig. A.1
Fig. A.2
Fig. A.3
Fig. A.4
Fig. A.5
Fig. A.6
Fig. A.7
Fig. A.8
Fig. A.9
Fig. A.10
Fig. A.11
Fig. A.12
Fig. A.13
Fig. A.14
Fig. A.15
Architectural design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5

Example of network configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.9
Installation of NA-NV Connector (1/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2
Services Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5
Window of confirmation of the stop of NetViewer Services Manager . . . . . . . . . . . . . . . . . . . . . . . . 2.6
Window of confirmation of the stop of NetViewer AUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6
NetViewer Advanced Update Pack window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7
Configuration of O&M Agent (1/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9
Example of remote management using Citrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2
Publishing of the GUI of NetViewer (1/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4
Configuration of Isolation Environment (1/7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6
Configuration of the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9
Configuration of ICA protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.14
Configuration of the access to the DB of NetViewer (1/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.15
Installation of NA-NV Connector PM (1/5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2
Configuring local FTP server (1/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4
Enabling Performance Data export service (1/3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.6
Configuring fine grained PM data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8
Performance Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8
Global Configuration panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.9
Specific NE Configuration panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.10

911-431/02A0120 - Issue 1, March 2009
I-3
I-4

911-431/02A0120 - Issue 1, March 2009
1 - GENERAL INFORMATION
1 GENERAL INFORMATION
1.1 Purpose and Subject of the Manual
This Manual provides the information for the installation, the configuration and the use
of the NetAct-NetViewer Connector software application (from now on called NA-NV
Connector).
NA-NV Connector is an optional software package that allows the integration of
NetViewer into NetAct and, then, the management of the supported radio Network
Elements.
The use of Citrix Presentation Server framework allows the remotization of the GUI of
NetViewer on the Client PCs of NetAct (Screen Level Integration).
It is forbidden, unless after written authorization, to divulge the content of this
Manual to third parties. A copy of this Manual can be required, mentioning its
code (present on the frontispiece).
1.2 Functions of the application

1.2.1
NetAct
NetAct is a network and service management framework that addresses the operator's
challenges to handle more network elements, larger networks, greater complexity and
explosive growth in traffic and data expected in future networks.
NetAct can manage both the network and services in a centralised manner, meaning
that the operator can view all network element failures, service quality indicators and
traffic from one single screen.
The ability to collect, integrate and utilise the information about the status and the
performance of all network elements and services is the cornerstone of NetAct. Fluent
alarm handling, reporting capabilities as well as network optimisation functionality
minimise the network downtime and congestion, optimise the network capacity and
create the basis for efficient network operations.
NetAct is a total OSS package including common network functionalities as well as
sophisticated tools for service assurance and optimisation.
Key drivers in the NetAct solution:
One single system for monitoring, measuring and configuring the network and
services
High scalability that meets the growth of network and services and technology
lifecycle requirements
Wide support for customer specific extensions to adapt NetAct to the business
processes and needs of individual organisations.

911-431/02A0120 - Issue 1, March 2009
1-1
1.2.1.1
Mediation and adaptation

The support for network elements is divided between mediation and adaptation
functions. Mediation is responsible for the conversion of the network element interface
to the NetAct internal format. Mediation is in most cases network technology
independent.
Adaptation is responsible for adapting the applications to a certain network domain, e.g.
BSS, RAN, Packet Core etc. Technically, an adaptation configures the user interfaces,
database and mediation.
Adaptation contains typically the following information:
Topology adaptation (new managed objects)
FM adaptation (mediation adaptation and alarm manual pages)
PM adaptation (mediation adaptation and definition of measurement types and

counters)
Adaptation information for other applications
Adaptation of the element manager launch
Application layer includes management applications (monitoring, reporting, optimising

etc) that provide management capabilities grouped together according to the most
relevant operator processes.
1.2.1.2
1.2.2
NetViewer - NetAct interaction note
On NetViewer map close, all the NetAct nodes will be deleted.
On NetViewer element name change, the element with old name will be removed
from NetAct and a new element (with different Distinguish Name) will be added.
On NetViewer element version change, the element with the old date will be
removed from NetAct and the same element (with same Distinguish Name) will be
re-added with new data.
NetViewer
NetViewer Server is the Element Manager of all the radio NE: it collects all the
information coming from the NE such as fault and performance and enables to configure
the radio equipments. To get more information about NetViewer refer to the
NetViewer Technical Customer Documentation.
1.2.3
NA-NV Connector
NetAct-NetViewer Connector implements the Mediation layer to interface
NetViewer towards NetAct.
The main functionalities of the application are:
Basic Configuration Management
Fault Management
Performance Management (optional)
The project NA-NV Connector 1.2 provides also the EMS GUI remote lauch feature.
1-2

911-431/02A0120 - Issue 1, March 2009
This is a separate feature of the same integration, not provided by the Connector module
itself, but provided via Citrix Presentation Server framework.
1.2.3.1
Basic Configuration Management

Topology Upload from NetViewer is supported.
The NetViewer object is created manually, after that all Network Elements are uploaded
from NetViewer.
Also topology events (add/delete NE) are supported.
1.2.3.2
Fault Management
All alarms managed by NetViewer, except the alarms/events with TEST severity, are
forwarded to NetAct and will be managed into NetAct as all the other NetAct alarms.
It is possible to present alarms from a NetAct view containing NetViewer managed
object by right-clicking the object and selecting "Alarm Monitor". Moreover it is
possible, on the icon, to select the "Alarm History" functionality.
It is important underline that NetAct does not present in the Alarm List the alarms with
severity warning, but they will be logged in the Alarm History.
Another topic to underline is the station alarms behaviour that in NetViewer have
the Indeterminate severity. This kind of Severity is not foreseen in NetAct so the station
alarms severity is mapped into the Minor severity in the NetAct system. Moreover
Station Alarms have in NetAct as Specific Problem the value "Station Alarm", but
NetViewer can customise the description string. So in NetAct is visible "Station Alarm x"
while in NetViewer a specific description as "door open" is shown.
1.2.3.3
Performance Management
This optional fragment manage the Network elements performance collection.
For further details see Appendix A.
1.2.3.4
EMS GUI Remote launch

The access from more Client terminals to an application resident on a remote Server PC
is based, in Windows environment, on the Microsoft Windows Terminal Services
service.
The access to the application resident on the remote Server PC is possible also from
non-Windows environments, by using the Citrix Presentation Server framework.
The remote launch of the NetViewer GUI, from a NetAct Client, is made via a command
line.
The focus in the NetViewer GUI is on the complete Network View, without selecting
the particular equipment addressed at NetAct level.
The NetViewer GUI, launched via screen level integration, requires the user to insert the
correct credentials, in order to log-in to the NetViewer Server. These credentials are
defined at NetViewer Server.
The maximum number of NetViewer GUI simultaneously open is 10, in the
foreseen scenario with a single Citrix Server.

911-431/02A0120 - Issue 1, March 2009
1-3
If the same user log-in at another terminal, the previous session (in the previous
terminal) will be closed, and the NetViewer GUI will be displayed at the new
terminal.
1.2.3.5
Configuration supported
This release of the connector supports only the NetViewer Single Server configuration.
The Connector is installed on the same host of NetViewer and manages only the NE's
managed by that NetViewer.
1.2.3.6
Firewall
The following cases are possible:
firewall between NetAct NetViewer Connector and NetAct
firewall between Citrix server and ICA clients
No firewalls are allowed between Citrix server and NetViewer server.
1.2.3.7
3rd party software

For the 3rd Party Software required by NetAct-NetViewer Connector and GUI remote
launch refer to the operating guide of NetViewer.
1.3 Software architecture

NetAct-NetViewer Connector is an additional package of the NetViewer Suite which
provides the specific Adaptation layer in order to accomplish the connection towards
NetAct SW product by means of O&M Agent. A graphic description of the architecture
is given in Fig. 1.1.
NetAct -NetViewer Connector is based of two main SW core components:
NetViewer Interface
used for implementing north bound IF of NetViewer
NA-NV Connector
used to convert NetViewer proprietary model in the correspondent O&M Agent.
Together with the setup of NA-NV Connector, also the O&M Agent component is
installed, providing the NE3S fully compliant north bound interface of the NA-NV
Connector product.
This allow the exchange of requests and informations between NMS and EMS.
1-4

911-431/02A0120 - Issue 1, March 2009
Fig. 1.1
Architectural design
NetAct
NetViewer Suite Host PC

O&M Agent
NA-NV Connector
NA NV Connector
NetViewer Interface
NetViewer Server
Radio NE
1.3.1
Radio NE
Radio NE
NetViewer Interface
The NetViewer Interface module is an interface between the NetViewer server and the
NA-NV Connector. Its main purpose is to collect and manage with specific criteria all the
information coming from NetViewer Server and to send it towards upper layer interfaces.
Its basic operations can be resumed in the following points:
Create a Managed Element structure, which contains the physical and functional
representation of a single Network Element.
Manage the dynamic functional plug-ins.
Manage all the network element event-alarms and send them to the interested
interfaces.
For these purposes, NetViewerInterface loads all the alarm information available
in the NetViewer TVX/TVD/TVF format files and gives an interface for query the alarms
information for a given NE.
NetViewer Interface is a component of the NetViewer Advanced Update Pack
service of NetViewer, and is included in the NA-NV Connector setup.
1.3.2
NA-NV Connector
The NA-NV Connector component has been implemented to provide the mapping
between the NetViewerInterface event/alarms modelization and the O&M Agent
proprietary format (NE3S style).
For this purpose, a set of interfaces has been implemented in order to manage the data
coming from NetViewerInterface and going towards O&M Agent layer. In particular two

911-431/02A0120 - Issue 1, March 2009
1-5
types of java interfaces are instantiated:
ConfigurationManager IF: for managing the NE's configuration.
FaultManager IF: for alarm event handling.
1.4 System requirements

The hardware and software system requirements for a correct installation and utilization
of the NA-NV Connector 1.2 software module into the NetViewer Suite are the same of
NetViewer 9.7.
Refer to the operating guide of NetViewer to get a complete list of the hardware
and software requirements.
1.5 Supply Conditions

NA-NV Connector 1.2 application is an optional module provided only on Customer's
demand. It is provided on dedicated CD-ROM.
1.6 Licenses for the use of the software

NA-NV Connector is a software product of Nokia Siemens Networks S.p.A. protected by
Copyright Nokia Siemens Networks S.p.A. and all the rights are reserved.
Appendix A reports in detail the licenses for the use of NA-NV Connector and of the
software products of Third Parties used and included in the supply.
1.7 Related Manuals

For information about NetAct product, refer to the relevant documentation.
For information about the modalities of use and installation of NetViewer, refer to the
relevant Operating Manual (OMN).
For each radio equipment supported by NetViewer, the following manuals are available:
User Manual (UMN)

Contains the information necessary for the installation, the commissioning and the
maintenance of the radio equipment.
Operating Manual (OMN)

Contains the information for the management of the radio equipment via
NetViewer.
All the Manuals are available on CD-ROM.
1-6

911-431/02A0120 - Issue 1, March 2009
1.8 List of abbreviations

OSS
Open-Source Software
GUI
Graphical User Interface
EMS
Element Management System
SW
Software
IF
Interface
NE3S
Nokia Enhanced SNMP Solution Suite
NMS
Network Management System
NE
Network Element
ICA
Independent Computer Architecture
IP
Internet Protocol
TNMS
Telecommunications Network Management System
DB
Database
SRA
Synchronous Radio Access
OS
Operating System
O&M
Operate and Maintain

911-431/02A0120 - Issue 1, March 2009
1-7
1.9 Network configuration for the remote

management of the NetViewer GUI
The configuration for the remote management of the NetViewer GUI in Citrix
environment foresees:
Citrix Server PC:

Microsoft Windows 2000/2003 Server
Microsoft Windows Terminal Services
NetViewer Client
Microsoft Excel
Citrix Presentation Server 4.0
JVM 1.4.2_08
NetViewer Engine licence for Microsoft Windows Terminal Services
4 Gb RAM (minimum)
NetViewer Server PC:

Microsoft Windows 2000/2003 Server
Microsoft SQL Server 2000 with SP4
NetViewer Server
Client PC:
Operating System: Microsoft Windows, UNIX (Solaris, HP), Linux
Citrix ICA Client (from 7.0)
supported Web Browser.
Fig. 1.2 show an example of network configuration.

It is possible to open at most 10 sessions of NetViewer Client at the same time. If
it is necessary to open other sessions, another Server PC must be used. Anyway,
with NetViewer Server more than 20 sessions of NetViewer Client cannot be
opened at the same time.
When you run Citrix Management Console (CMC) on a Server machine, where an
ATI display driver is present, the Server itself can crash. To solve this problem, it
is necessary that Citrix uses a JVM higher than 1.4.2_05. Then, the installation on
the Server machine of two different JVMs, deriving from two different releases (1.4
for Citrix and 1.3 for NetViewer Client), is necessary.
For more information on the network architecture, refer to the OMN Manual of
NetViewer.
For information on the installation and the configuration of the server
(Presentation Server) and client (ICA Client) components of Citrix, refer to the
OMN Manual: NetViewer Client remotization with Third Parties Software .
1-8

911-431/02A0120 - Issue 1, March 2009
Fig. 1.2
Example of network configuration

Windows Server
Windows Terminal Services
NetViewer Client
Citrix Presentation Server
Windows Server
SQL Server
NetViewer Server
NA-NV Connector 1.1 (Core engine) (**)
DCN
NetViewer
Server PC
Citrix
Server PC
WAN
Router
NE
192.168.24.244 (*)
Router
NE
Firewall
LAN
Operating System
Citrix ICA Client
NA-NV Connector 1.1 (Client) (**)
NetAct Client PC
NetAct PC
Operating System
Citrix ICA Client
NA-NV Connector 1.1 (Client) (**)
NetAct Client PC
(*) IP address of the ethernet card (example)

(**) To be installed with the NA-NV Connector setup
1.10 System performances

Number of managed Network Elements: 2000 (NetViewer Single Server solution)
Event Throughput:
20 events / second are processed real-time.
Event Burst:
burst of 40 events / second is processed in
10 minutes without service interruption.
Event Long Flood:
flood of 20 events / second for 72h period is
processed real-time without service
interruption.
1.11 Firewall configuration

The following cases are possible:
firewall between NA-NV Connector and NetAct
firewall between Citrix Server and ICA Clients
Assumption: no firewall present between Citrix server (and NetViewer GUI) and
NetViewer Server.
1.11.1
Firewall between O&M Agent and NetAct

O&M Agent used ports and NetViewer Suite host IP Address must be configured in the
firewall. Ping functionality is used by adaptation to check management connection
aliveness, so ping should be allowed to pass through firewall.

911-431/02A0120 - Issue 1, March 2009
1-9
1.11.2
Firewall between Citrix Server and Client PC

In case of presence of Firewall between the Server PC of Citrix and Client PC of NetAct,
in order to use the ICA Client service, verify that the following ports are open:
1-10
1494 (TCP protocol) on remote host
1356 (TCP protocol) on local PC.

911-431/02A0120 - Issue 1, March 2009
LA
PA

911-431/02A0120 - Issue 1, March 2009
1-11
1-12

911-431/02A0120 - Issue 1, March 2009
2 - SOFTWARE INSTALLATION
2 SOFTWARE INSTALLATION
2.1 Requirements
NA-NV Connector setup must be executed on the NetViewer Server PC and on the
Client PCs (PCs with Citrix ICA Client).
In the first case the core engine is installed, while in the second case only the client
component is installed.
In both cases, the selection of the installation modality is transparent for the operator.
NA-NV Connector must be installed on each Server PC of NetViewer.
For the procedure and the Hardware/Software requirements relevant to the

installation of NetViewer, refer to the OMN Manual of NetViewer.
For information on the installation and the configuration of software of third
parties necessary for the remotization of the GUI of NetViewer on the Client PCs
of NetAct, refer to the OMN Manual: NetViewer Client remotization with Third
Parties Software.
For information on the installation and the configuration of the NA-NV Connector
Performance Management fragment see Appendix A
2.2 Installation of NA-NV Connector

2.2.1
Server installation procedure

The following set-up must be executed on the NetViewer Server PC, in order to install
the core engine of NA-NV Connector.
It is necessary to stop the NAUP services before installing the NA-NV Connector.
The procedure for the installation of NA-NV Connector is the following one:
Launch the guide of the

"<CD_drive>:\Launch.exe").
If the presence of NetViewer is not detected, an error window is displayed

(Fig. 2.1). Click on OK to close the window and abort the setup.

911-431/02A0120 - Issue 1, March 2009
CD-ROM
of
NA-NV
Connector
(file:
2-1
If NetViewer is present on the machine, the starting Welcome window is displayed

(Fig. 2.2). Click on Next> to continue.
It is always possible, until the end of the setup, to stop the procedure, clicking on
Cancel.
The License Agreement window is displayed. Accept the conditions of the license
for the use of the software. The Next> button becomes active (Fig. 2.3). Click on
Next> to continue or on <Back to return to the previous window.
The Ready to Install the Program window is displayed (Fig. 2.4). Click on Install
to continue the installation or on <Back o return to the previous window.
At the end of the installation, the window of installation complete (Fig. 2.5) is
displayed. Click on Finish to end and exit from the setup.
It is recommended to confirm always, if required in the final window, the restart

of the machine.
2-2
Fig. 2.1
Installation of NA-NV Connector (1/5)
Fig. 2.2

911-431/02A0120 - Issue 1, March 2009
Fig. 2.3
Fig. 2.4
Fig. 2.5

911-431/02A0120 - Issue 1, March 2009
2-3
2.2.2
Client installation procedure

The following set-up must be executed on the Client PC in order to install the
configuration GUI Client for a remote management.
The procedure for the installation of NA-NV Connector is the following one:

CD-ROM
of
NA-NV
Connector
(file:
The starting Welcome window is displayed (Fig. 2.2). Click on Next> to continue.
Cancel.
for the use of the software. The Next> button becomes active (Fig. 2.3). Click on
The Ready to Install the Program window is displayed (Fig. 2.4). Click on Install
At the end of the installation, the window of installation complete (Fig. 2.5) is

of the machine.
2.2.3
Maintenance procedure
The following options for the NA-NV Connector maintenance are available:
Repair: it executes the restore of the already installed components of NA-NV

Connector. This option allows installing again all the already installed components
in case of troubles concerning one or more component programs of NA-NV
Connector or in case of errors during the setup procedure.
Remove: it executes the uninstallation of all the installed components of NA-NV

Connector. This option allows removing completely the NA-NV Connector
application service.
On the Server PC of NetViewer, before executing the maintenance of NA-NV

Connector, it is necessary to stop the NA-NV Connector service acting through
NetBuilder. For the description of this procedure, refer to the OMN Manual of
NetViewer.
The maintenance procedure of NA-NV Connector is the following one:
Run the setup program of NA-NV Connector (file: "<CD_drive>:\Setup.exe").
It is possible to run the NA-NV Connector maintenance also using the typical
adding/removing mode of the application programs in Microsoft Windows
("Add/Remove Programs" command in Control Panel).
2-4

911-431/02A0120 - Issue 1, March 2009
The Welcome window opens allowing selecting the type of maintenance

procedure to execute. Click on Next> to confirm the selection and to continue or
<Back to abort.
At the end of the maintenance procedure, the Maintenance Completed window

opens. Click on Finish to end the procedure and to exit.
It is suggested to confirm always if the system asks, in the final window, for the restart
of the machine.
2.3 Verification of the installed services

NA-NV Connector software application includes two modules:
NetViewer Interface
NA-NV Connector
Both the modules, together with O&M Agent component, are installed, with the setup,
as services of NetViewer AUP and, then, can be managed from the Services
Management window of NetBuilder, which can be opened by the Services command
of Configuration menu.
For information on the use of the tool for the management of the services of
NetBuilder, refer to the Operating Manual of NetViewer.
In the Services Management window (Fig. 2.6) are displayed, in format of table, the
services managed by NetViewer Services. For each service, it is possible:
Fig. 2.6
2.3.1
Execute the command to stop the service (if the service is operating)
Execute the command to start the service (if the service is not operating)
Display the properties of the service (if the service is operating).
Services Management window
Stop/start of NetViewer services

It is possible to command the stop/start of a service selecting the corresponding line in
the Services Management window and then clicking on Stop/Start.

911-431/02A0120 - Issue 1, March 2009
2-5
The stop/start command is available for the following services:
Fig. 2.7
Window of confirmation of the stop of NetViewer Services Manager
Fig. 2.8
NetViewer AUP
The stop command determines the stop both of NetViewer AUP and of the linked
services.
A confirmation for the execution of the stop command is required (Fig. 2.8).
Window of confirmation of the stop of NetViewer AUP
2-6
NetViewer Server
The stop command determines the stop of all NetViewer services and close the
Services Management window.
A confirmation for the execution of the stop command is required (Fig. 2.7).
NetViewer Interface, ESYMAC [Agent] and ESYMACAdapter

To access to the command for the stop/start of the services, in the Services
Management window (Fig. 2.6) select NetViewer AUP and click on Properties.
The NetViewer Advanced Update Pack window opens (Fig. 2.9). Select the
Components tab.
This tab lists the components of NetViewer AUP currently installed. The format
used to list the component is the following:
ComponentName [ver . x.x (Build 00000)] servicestate
ComponentName: points out the name of the component (e.g. NA-NV

Connector);
[ver . x.x (Build 00000)]: univocally points out the installed release
Servicestate: points out the state of the service.

The components installed by default are:
NetviewerInterface: interface between the NetViewer server and the

NA-NV Connector
NA-NV Connector: allows integration between the NetViewer north bound

interface and O&M Agent south bound interface
O&M Agent: provides the NE3S fully compliant north bound interface of the
NA-NV Connector product
Selecting the O&M Agent item or NA-NV Connector item a command panel is
shown:
Stop/Start button: execute the command to stop the NA-NV Connector (if the
service is running) or to star the NA-NV Connector (if the service is not
running).
AutoStart button: execute the command to auto-start the NA-NV Connector

when the System starts up.
The stop command determines the stop of the service as follows:

911-431/02A0120 - Issue 1, March 2009
Fig. 2.9
2.3.2
stopping NetViewer Interface, also NA-NV Connector stops

stopping O&M Agent, also NA-NV Connector stops
stopping NA-NV Connector, the other services continue to run.
NetViewer Advanced Update Pack window
Configuration of O&M Agent

NA-NV Connector does not start automatically, after the first installation, if O&M
Agent interface is not configured.
Before starting NA-NV Connector, it is necessary to configure the O&M Agent interface:
From NetBuilder, by means of the Services command of the Configuration menu,

open the Services Management window (Fig. 2.6).
Select NetViewer AUP and click on Properties. The NetViewer Advanced

Update Pack Properties window opens (Fig. 2.10).
Select the O&M Agent component, click on the button O&M Agent General
Configuration that opens the Global Configuration window (Fig. 2.11).
This window has two sections:
Service state: show the state of O&M Agent Services:
The Configuration Management button, that controls the reporting of

network configuration informations, shows the current service state and can
be Active or Inactive.
The Fault Management button, that controls the reporting of fault events,
shows the current service state and can be Active or Inactive
The Performance Management button, that controls the network

performance reporting, is fixed Inactive; a specific license is required for this
feature.

911-431/02A0120 - Issue 1, March 2009
2-7
General Configuration: this panel report the configuration of some O&M Agent
general parameters (the Apply button confirm the changes):
Community: this string is the community used by the O&M Agent SNMP
operation. The default value is esymac.
O&M Agent port: local port used by ESYMAC (not modified by default). The
value is 9998
Prefix Path: path that identifies the local installation, provided by NetAct; the
set value is PLMN-PLMN
The O&M Agent port may be changed, if it isnt available due to settings of the
host PC (ex.: local firewall).
Click the button O&M Agent Specific Configuration that opens the Specific
Configuration window (Fig. 2.12) (the apply button confirm all configurations).
Configuration settings: this panel shows the settings for Configuration

Managenet
Agent id: identifying code of the Agent, provided by NetAct.
Remote FTP destination: IP address of the Manager that collects the

configuration information (NetAct osscore2).
Remote User: username for the access to the manager side of the FTP
connection (nx2suser with NetAct use).
Remote Pwd: password for the access to the manager side of the FTP
connection.
Remote import dir: path of the destination folder of the configuration

files, starting from the source folder of FTP. Use default.
Remote export dir: path of the destination folder of the query of the
manager, starting from the source folder of FTP. Use default.
Polling Period: time in seconds for the FTP polling.
Fault settings: this panel shows the settings for Fault Management:
Destination address: IP address for destination SNMP (NetAct

osscore2).
Destination port: SNMP port
Local request port: local SNMP port for incoming request.
Performance settings: this feature is disabled a special license is nedded.
Click the button Start in order to start the O&M Agent application.
For more information, refer to the Manual Integrating NetViewer to NectAct

Chapter 4.
2-8

911-431/02A0120 - Issue 1, March 2009
Fig. 2.10
Configuration of O&M Agent (1/3)
Fig. 2.11
Fig. 2.12

911-431/02A0120 - Issue 1, March 2009
2-9
2-10

911-431/02A0120 - Issue 1, March 2009
3 - EQUIPMENT MANAGEMENT
3 EQUIPMENT MANAGEMENT
3.1 Supported equipment
Currently, the SRA 4 4.8/4.10 equipment is supported and is represented in the GUI of
NetAct by a specific icon:
All the other equipment are represented in the GUI of NetAct by an icon of generic NE:
3.1.1
Sra4
The SRA 4 radio system, designed for MAN (Metropolitan Area Network) and WAN
(Wide Area Network) applications, is a broadband wireless point-to-point system.
The SRA 4 radio system has been developed for the transmission of the following
signals:
SDH (STM-1)
SONET (OC-3)
ATM on SDH
ATM on SONET
The system is available in the 5.67 to 40.0 GHz frequency ranges.

The used modulation is 32/64/128 TCM-4D, so, depending on the different signals in
inputs, we can have RF spacings of 27.5 to 56 MHz.
System Types:
Terminal 1+0 without Multiplex Section Termination (MST)
Terminal 1+1, Frequency Diversity, Single Terminal, without MST
Terminal 1+1, Hot Stand-by (HSBY), Single Terminal, without MST
Terminal 1+1, Frequency Diversity, Double Terminal, without MST
Terminal 1+1, Hot Stand-by (HSBY), Double Terminal, without MST
Terminal 2+0 without MST.
1xSTM-1 tributary interfaces:
electrical
optical
Management interfaces:
two Ethernet interfaces (one 10baseT and the other 10/100baseT), reserved
for the connection to NetViewer and/or other TMN supervision centers (e.g.:
EM-OS, Access Integrator) and for the transmission of the supervision
information among the system controllers of the same station

911-431/02A0120 - Issue 1, March 2009
3-1
3 - EQUIPMENT MANAGEMENT
3-2
F interface, reserved for the local connection to LCT

DCC channels, reserved for the transmission via radio of the supervision
information.

911-431/02A0120 - Issue 1, March 2009
4 - NETWORK CONFIGURATION TO REMOTIZE THE GUI OF NETVIEWER
4 NETWORK CONFIGURATION TO
REMOTIZE THE GUI OF NETVIEWER
4.1 Foreword
Scope of this chapter is to define a network configuration suitable to screen level
integration functionality of NetAct - NetViewer Connector, release 1.21.2.
The screen level integration consists in the possibility to have the NetViewer Graphical
User Interface [GUI] at NetAct GUI terminal, where the system user operates.
First integration foresees:
NetViewer Single Server configuration
Only one instance of NetViewer Server
Only one Citrix Presentation Server
Fixed command line
Only one NetViewer GUI per terminal
No NE selection is provided in the NetViewer GUI, at launch; the entire managed

network is displayed.
In the following, we assume that on the network PCs have been installed and configured
the following components:
Citrix Server PC:

Microsoft Windows 2003 Server
Microsoft Windows Terminal Services
NetViewer Client
Citrix Presentation Server 4.0
NetViewer Engine licence for Microsoft Windows Terminal Services
NetViewer Server PC:

Microsoft Windows 2003 Server SP2 or R2 SP2
Microsoft SQL Server 2005 with SP2
NetViewer Server
NA-NV Connector 1.2
O&M Agent
NetAct Client PC:

Operating System: Microsoft Windows, UNIX (Solaris, HP), Linux
Citrix ICA Client (from 7.0)
Fig. 4.1 show an example of network configuration.

911-431/02A0120 - Issue 1, March 2009
4-1
A maximum of 10 remote GUI clients are managed by a single Citrix Server PC.
It's a Citrix Server performance issue, and a Citrix Server host performance issue.
If more NetViewer GUI clients are needed, additional Citrix Server hosts must be
added.
A maximum of 20 NetViewer GUI clients can be connected to a NetViewer Server.
It's a NetViewer Server performance issue.
For more information on the network architecture, refer to the OMN Manual of
NetViewer.
Fig. 4.1
Example of remote management using Citrix

Windows Server
Windows Terminal Services
NetViewer Client
Citrix Presentation Server
Windows Server
SQL Server
NetViewer Server
NA-NV Connector 1.1 (Core engine)
DCN
NetViewer
Server PC
Citrix
Server PC
WAN
Router
NE
Router
NE
Firewall
LAN
Operating System
Citrix ICA Client
NA-NV Connector 1.1 (Client)
NetAct Client PC
NetAct PC
4-2
Operating System
Citrix ICA Client
NA-NV Connector 1.1 (Client)
NetAct Client PC

911-431/02A0120 - Issue 1, March 2009
4.2 Remote management of the NetViewer GUI

The remote management of an application, through Citrix, can be realized in two
different ways:
4.2.1
4.2.1.1
From Citrix Server PC, publishing the applications you wish to make available to
all the users who can connect (even via Web).
From a Client PC by declaring the command line at ICA Client.
Citrix Server configuration

Publishing of NetViewer on Citrix Presentation Server 4.0
For information on the procedures for the installation and configuration of Citrix
Presentation Server on a Server Windows 2003, refer to the Manual "NetViewer
Client Remotization with Third Parties Software".
For the launch of NetViewer GUI with Citrix Presentation Server 4.0, it is necessary to
execute the publishing of the application:
Launch the Presentation Server Console program.
Click on the Action > New > Published Application menu (Fig. 4.2)
The Publish Application window opens (Fig. 4.3) where entering the information
of the published application:
Display name field: give a name to the application
Application description field: type a brief description.

Click on Next.
In the next window (Fig. 4.4) specify:
In the Application Type box, select the radio button corresponding to the
publication type (in case of NetViewer, it is an application):
Command Line field: enter the command line to execute:

<JVM installation path>\javaw.exe" -Xverify:none -Xms256m -Xmx256m
-Xincgc -XX:MaxNewSize=96M - XX:NewSize=96M -Djava.ext.dirs=.;jar;appl
-jar "<NV GUI installation path>\Nvc.jar" /sa <NV server IP address> /norec
If there is the need to pass parameters, without inserting them in the
command line of the published application, the command line published at
Citrix Server will contain also the %* tag, which indicates the position where
to insert the command line parameters passed when launching the ICA client,
with the "-param <...>" option (see. par. 4.2.2.3).
Working Directory field: it is automatically filled.

Click on Next.
In the following window, leave the default setting and click Next.
Specify the size of the window and the quantity of color as in Fig. 4.5. Click on
Next.
In the Specify Client Requirments window, leave the default setting and click on
Next.
In the Specify Application Limits window, leave the default setting and click on
Next.

911-431/02A0120 - Issue 1, March 2009
4-3
In the Configure Access control window, leave the default setting and click on
Next.
In the Specify Servers (Fig. 4.6) window, select the server containing the
application and click on Add. Click on Next.
In the Specify Users (Fig. 4.7) window, select the users with the right to launch the
application.
It is possible to select the users among which present in the Look in field
containing the users configured on the Server of the Farm (e.g.: netviewertest) or
add to the list a valid user through Add List of Names."(e.g.:
NVSERVER1\netviewertest).
Selecting the Allow Anonymous Connections check box, when ICA Client is
launched, an authentication window of the Server will open.
Up to 15 users with Anonymous access class are allowed.
Click on Next.
4-4
In the Specify file type associations window, leave the default settings. Click on
Finish to finish.
Fig. 4.2
Publishing of the GUI of NetViewer (1/6)
Fig. 4.3
Fig. 4.4

911-431/02A0120 - Issue 1, March 2009
Fig. 4.5
Fig. 4.6
Fig. 4.7

911-431/02A0120 - Issue 1, March 2009
4-5
4.2.1.2
Isolation Environment
Isolation Environment, from now on identified by IE, allows isolating an application or
more applications published by Citrix Presentation Server, protects possible resources
shared with the operating system, for example configuration files, database, etc.
avoiding conflicts and incompatibility with the rest of the environment.
IE creates a copy of the system resources which can be modified by the application
published both runtime and during an installation, this ensures not only the correct
operation of the application but avoids also the collision with the rest of the system.
Furthermore, IE implements the mechanism of "Virtual Mapping" consisting in the
mapping of those resources that can be modified in some measure by the published
application itself. The steps to follow are:
Point out the application to isolate.
Make sure that IE is enabled in Server Citrix.
Create the IE.
Configure correctly the properties of IE.
Isolate the published application.
Creation of an Isolation Environment

By default, the selection of IE is enabled when an application is published on the Server
farm. The default settings generally solve the greater part of the troubles that can occur
when an application is executed. Should not be sufficient, or simply if you wish to
optimize the Isolation Configuration, it is sufficient to change the settings.
Here below are pointed out the steps to follow for the creation of the IE:
Fig. 4.8
Launch the Presentation server console
In the left part of the console, select Isolation environment
From the Actions menu, select New > Isolation environment
Configuration of Isolation Environment (1/7)
Fig. 4.9
4-6
Type the name of the new Isolation Environment and then click on OK.
The new IE is put in the list of the IEs available on the server.

911-431/02A0120 - Issue 1, March 2009
Configuration of Isolation Environment

After the creation of a new Isolation Environment and having identified it by a name,
it is necessary to assign an application to the created IE and then to configure it in the
correct way to complete the physical isolation of the program.
Fig. 4.10
Fig. 4.11
Open the properties of the just created IE (in the example of the previous figure
Isolation test).
The window moves to Applications, click on Add button and select the application
you wish to isolate (in the example, NetViewer_8_0_SP2), confirm with OK.
Select the Roots item, where can be specified the directories and, is possible, the
register where the user can modify keys or files inside the virtual folders. Leave the
default settings.
Select the Rules item, where it is specified what will be explicitly isolated or what
can be ignored.
Select Default file system isolate rule and ckick on Modify; the Rule Type
window opens (Fig. 4.12).

911-431/02A0120 - Issue 1, March 2009
4-7
Fig. 4.12
Fig. 4.13
Fig. 4.14
4-8
Leave unchanged the options in Action and Object; click on Next; the Isolate
Files window opens (Fig. 4.13).
Click on Add, in the Choose path window, click on Browse and choose the
folders, objects, files, etc you wish to isolate. Confirm with OK and then click on
Next; the Isolation Type window opens (Fig. 4.14).
Select the Per user radio button and click on Next, and then Finish.
In the tab Security leave the default settings.
Confirm all with OK.

911-431/02A0120 - Issue 1, March 2009
4.2.1.3
Configuration of NetViewer
When publishing the NetViewer application by means of the Isolation Environment
technique, it is necessary to configure the application (on Citrix Presentation Server
side) in the following way:
Fig. 4.15
1.
Launch Presentation server console
2.
Select the published application and make sure that, in the Application Location
list, the characteristics of the application are:
Application Type: Application
Command Line:
"<JVM installation path>\javaw.exe" -Xverify:none -Xms256m -Xmx256m
-Xincgc -XX:MaxNewSize=96M - XX:NewSize=96M -Djava.ext.dirs=.;jar;appl
-jar "<NV GUI installation path>\Nvc.jar" /sa <NV server IP address> /norec
Working Directory:
<directory>:\Program Files\Radio Management\NetViewer
Isolate Application: selected
Configuration of the application
3.
Open the installation folder of NetViewer and control that, in the nvcStart.ini file, the
keys jarParams and mutexmode are the following:
JarParams= /sa <NV server IP address>
MutexMode=0

911-431/02A0120 - Issue 1, March 2009
4-9
4.2.2
4.2.2.1
Configuration of Client PC
Configuration of Client with application published on Citrix Server
The launch of the GUI of NetViewer from command line foresees the creation, on the
NetAct terminal with ICA Client installed, of a file "<file name>.ica" which must contain:
Citrix Server IP address
Citrix Server user identifier
Citrix Server user encrypted password
Other parameters as screen width ad height, colours, etc.
Here follows an example of ".ica" file, used for launching the remote NetViewer GUI.
The interesting parameters are at the end.
[ApplicationServers]
NetViewer 8_0_SP2=
[NetViewer 8_0_ SP2]
Address=NetViewer 8_0_SP2 (1)
DesiredHRES=1024
DesiredVRES=768
DesiredColor=4
TWIMode=On
ClientAudio=On
TransportDriver=TCP/IP
WinStationDriver=ICA 3.0
InitialProgram=#NetViewer 8_0_SP2 (2)
Password=0005e99f138914 (3)
Domain=NVSERVER1 (4)
Username=test (5)
(1)
It specifies the address of the target Citrix server. This can be the DNS name of a
MetaFrame server, the IP address of a MetaFrame server, or the name of a published
application (as in the example). Usually it will be the IP address of the Citrix Server.
(2) Name of the published application, plus "#"
(3)
Encrypted password to Citrix Server
(4)
Citrix Server domain
(5) Citrix Server user ID
Valid credentials must be inserted in the file, in order to connect to the Citrix Server. The
valid credentials are set at Citrix Server, when configuring the system and publishing the
application.
4-10

911-431/02A0120 - Issue 1, March 2009
4.2.2.2
Configuration of Client without publishing of the application on

Citrix Server
In this case, the file ".ica" must transmit to the Server Citrix also the information to launch
the application:
[ApplicationServers]
NetViewer 8_0_SP2=
[NetViewer 8_0_ SP2]
Address=192.40.10.22 (1)
DesiredHRES=1024
DesiredVRES=768
DesiredColor=4
TWIMode=On
ClientAudio=On
TransportDriver=TCP/IP
WinStationDriver=ICA 3.0
WorkDirectory=C:\Program Files\Radio Management\NetViewer (2)
InitialProgram= "<JVM installation path>\javaw.exe" -Xverify:none -Xms256m
-Xmx256m
-Xincgc
-XX:MaxNewSize=96M
XX:NewSize=96M
-Djava.ext.dirs=.;jar;appl -jar "<NV GUI installation path>\Nvc.jar" /sa <NV server IP
address> /norec (3)
Password=0005e99f138914 (4)
Domain=NVSERVER1 (5)
Username=test (6)
(1)
It specifies the IP address of the target Citrix server

VetViewer GUI installation path
(3) It is possible to use some environmental variables, to be defined at Citrix Server
where NV GUI is installed, for example:
JAVA_PATH = <JVM installation path>
NETVIEWER_PATH = "<NV GUI installation path>
GUI_PARAMS = -Xverify:none -Xms256m -Xmx256m -Xincgc -XX:MaxNewSize=96M
-XX:NewSize=96M - Djava.ext.dirs=.;jar;appl
So the command line should be as:
"%JAVA_PATH%\javaw.exe" %GUI_PARAMS% -jar "NETVIEWER_PATH\Nvc.jar"
/sa <NV server IP address> /norec
(4)
Encrypted password to Citrix Server
(5) Citrix Server domain
(6)
Citrix Server user ID
(2)
In case of direct launch of the GUI of NetViewer from Citrix Client, without the
previous publishing of the application on the Server Citrix, the Isolation
Environment functionality (par. 4.2.1.2) is not available.

911-431/02A0120 - Issue 1, March 2009
4-11
4.2.2.3
Command line from Client ICA

The command line to launch the remote NV GUI application is:
<ICA client path>/wfica <file name>.ica (for UNIX Solaris OS)
<ICA client path>/wfica32 <file name>.ica (for Microsoft Windows OS)
If there is the need to pass parameters, without inserting them in the command line of
the published application, the command line published at Citrix Server will contain also
the %* tag, which indicates the position where to insert the command line parameters
passed when launching the ICA client, with the
"-param <...>" option.
When there will be the need to pass parameters, the command line will be:
<ICA client path>/wfica <file name>.ica -param "<parameters passed to NV GUI>"
The following table details the possible parameters.
Tab. 4.1
Possible NV GUI parameters

Parameter
Example
Notes
NV Server IP Address
/sa 192.168.0.1 Optional.

Required if it is not preconfigured at Citrix
Server, inside the published application.
NV Server port
/sp 3686
Optional.
If the default port is used, there is no need
to redefine it; it can anyway be
preconfigured inside the published
application.
User ID
/ln username
Optional.
If not inserted and not predefined in the
published application, user will be
prompted to insert it.
Not foreseen for first integration, user will
insert manually the credentials at
NetViewer GUI.
User password
/lp password
As for "User ID".

Not foreseen for first integration, user will
insert manually the credentials at
NetViewer GUI.
NE name
/ip SouthMilan
Optional. Not useful in first integration.

It will be mandatory when NE selection
functionality will be available at NetViewer.
"ip" means not IP address, it is the NE
map name in NetViewer.
Remote display identifier
TBD
Still TBD
An example is:
<ICA client path>/wfica nvc.ica -param "/sa 192.168.0.1 /ln username /lp password".
4-12

911-431/02A0120 - Issue 1, March 2009
4.3 Security
There are three levels of access to the system for the launch of the GUI of NetViewer:
4.3.1
Access to Windows Terminal Services
Access to Citrix Server Farm
Access to NetViewer Server
Access to Windows Terminal Services

In Windows 2000/2003 Server, the authorizations are configured to define and limit the
credentials to access to Windows Terminal Services.
For information on the configuration of the authentications in Windows 2000/2003
Server, refer to OMN Manual "NetViewer Client remotization with Third Parties
Software".
4.3.2
4.3.2.1
Access to Citrix Presentation Server

Selection of the users with rights of execution of the applications
During the publishing of the GUI of NetViewer, besides the users local to Server Citrix
with rights to execute the remote application, it is necessary to specify the users having
rights to execute the remotized GUI (par. 4.2.1.1).
To avoid the request of Username and Password at the launch of the GUI, the
credentials of the users with access rights can be written in the file ".ica" during
the configuration of the Client ICA (par.4.2.2); these credentials are used for the
automatic access to the published application.
4.3.2.2
Configuration of ICA protocol

From Start -> Programs -> Administrative Tools select Terminal Services
Configuration. In the list of the connections, double click on the ICA-Tcp item and
select "Permissions" panel. For the locally defined users, and for the group or the users
of the domain which will be able to access to the remotized application, it is necessary
to enable the permission corresponding to "User Access" (Fig. 4.16).

911-431/02A0120 - Issue 1, March 2009
4-13
Fig. 4.16
4.3.3
Configuration of ICA protocol
Login to NetViewer
At the opening of the GUI of NetViewer the credentials are required for the access to
NetViewer. These credentials must be manually installed and are defined and managed
in NetViewer server with the NetBuilder tool.
For information on the use of NetBuilder, refer to OMN Manual of NetViewer.
4.3.4
Configuration of the access to DB of NetViewer

Some applications external to NetViewer (Performance Report,History Report and
Inventory Report) must be able to access to the Database of NetViewer. The access to
the DB is made through the IUSR system user. After the installation of NetViewer, it is
necessary that:
1.
In MS SQL Server appears the IUSR user of domain. From Start -> Programs ->
Microsoft SQL Server -> Enterprise Manager. In the "Security" folder, select the
"Logins" item. Control that the user <Domain Name>\IUSR_<Machine Name> is
among the users.
2.
IIS uses the IUSR user of domain as Anonymous Account for the access for the
access to DB. From Control Panel > Administrative Tools select IIS Manager.
By means of the right button of the mouse, select Properties of NetViewer folder.
Select the Directory Security tab. Click on the Edit button in the Authentication
and Access Control box. Verify that the User Name box reports the IUSR user
of domain.
If these users are noy used by SQL Server or by IIS, act as follows:
1.
4-14
From Control Panel > Administrative Tools select IIS Manager. By means of the
right button of the mouse, select Properties of the NetViewer folder.

911-431/02A0120 - Issue 1, March 2009
Fig. 4.17
Configuration of the access to the DB of NetViewer (1/3)
2.
Fig. 4.18
Select the Directory Security tab. Click on Edit button in the Authentication and
Access Control box.
Through the Browse key, select the IUSR user created before. Verify that the
Enable anonymous access e Integrated Windows authentication check boxes
are selected.

911-431/02A0120 - Issue 1, March 2009
4-15
Fig. 4.19
From Start -> Programs -> Microsoft SQL Server -> Enterprise Manager, under the
Security folder, select the Logins item. Clicking the right button of the mouse, select
the item New Login. On the General panel, at item Name, through the Browse button,
select the domain and the IUSR user just defined and, in the Database field, select the
DB of NetViewer. In Database Access panel, select the database (NetViewer), which
the user must access to, and specify the role which this user has on the database (select
public, db_datareader).
4-16

911-431/02A0120 - Issue 1, March 2009
A - INSTALL AND CONFIGURE THE PERFORMANCE MANAGEMENT FRAGMENT
A INSTALL AND CONFIGURE THE

PERFORMANCE MANAGEMENT
FRAGMENT
A.1 Overview
This addendum describes how to configure the Performance Management fragment of
the NE3S O&M Agent north bound interface included into NetViewer.
The contents scope is the limited to the O&M Agent 2.3 included into NA-NV Connector
1.2.
The NA-NV Connector SW includes the following management fragments:
Topology Upload
Fault Management
Performance Management
The default installation setting does not include the Performance Management
activation and it has to be performed after the first installation.
Some configurations can be performed during the run-time in order to align the Agent
side with the Manager setup (i.e.: NE instances that have to transfer PM Data files).
The contents of this addendum apply to the following configuration:
NetViewer 9.7 EU1
NA-NV Connector 1.2
OSS 4.x/5.x

911-431/02A0120 - Issue 1, March 2009
A-1
A.2 Install NA-NV Connector PM fragment

The following set-up must be executed on the NetViewer Server PC, in order to install
the c NA-NV Connector PM fragment.
The procedure for the installation of NA-NV Connector PM fragment is the following one:

CD-ROM
of
NA-NV
Connector
PM
(file:
If the presence of NetViewer is not detected, an error window is displayed

(Fig. A.1). Click on OK to close the window and abort the setup.
If NetViewer is present on the machine, the starting Welcome window is displayed

(Fig. A.2). Click on Next> to continue.
Cancel.
for the use of the software. The Next> button becomes active (Fig. A.3). Click on
The Ready to Install the Program window is displayed (Fig. A.4). Click on Install
At the end of the installation, the window of installation complete (Fig. A.5) is

of the machine.
A-2
Fig. A.1
Installation of NA-NV Connector PM (1/5)
Fig. A.2

911-431/02A0120 - Issue 1, March 2009
Fig. A.3
Fig. A.4
Fig. A.5

911-431/02A0120 - Issue 1, March 2009
A-3
A.3 Configuring local FTP server

In order to allow NetAct the upload of the performance data file from NetViewer PC FTP
server must be enabled and configured as reported in the following steps.
The FTP Server configuration is a mandatory pre-requisite for supporting the PM
Fragment at NE3S O&M Agent interface.
Open the Computer Management window (from My Computer -> Manage)
Fig. A.6
Configuring local FTP server (1/3)
Select FTP Sites and choose Properties (right panel)

Fig. A.7
A-4

911-431/02A0120 - Issue 1, March 2009
Select Home Directory tab and configure the properties as shown in the following
snapshot:
Fig. A.8
The home directory of the NetViewer system must be configured to

%NETVIEWER_ROOT%/ESYMACAdapter/ESYMAC and the Directory listing style
must be set to UNIX

911-431/02A0120 - Issue 1, March 2009
A-5
A.4 Enabling Performance Data export service

The enbling of the Performance Management fragment is possible by selecting from
NetBuilder > Service Management window the list item NetViewer AUP and opening
the relevant Properties window.
Once the NetViewer Advanced Update Pack Properties window is opened then
select O&M_Agent item list.
The right hand options set appears (refer to the next snapshot).
Fig. A.9
Enabling Performance Data export service (1/3)
Select the O&M Agent General Configuration option.

Fig. A.10
The Service state of the Performance Management (left side panel) must be set
Active. If Service State is set to Inactive please proceed pushing the button to activate
the option.
A-6

911-431/02A0120 - Issue 1, March 2009
Authentication, destination directory and other PM fragment specific configurations can

be set by selecting the O&M Agent Specific Configuration option from NetViewer
Advanced Update Pack Properties window (Fig. A.9).
Fig. A.11
The PM Fragment configuration is reported on the right side of the O&M Agent Specific
Configuration window.
The meaning of the specific parameter is reported here below:
Destination address
IP address of the server hosting the manager application (FTP client role) for PM
data.
Destination port
The availability of the PM is notified via SNMP trap. The PM data file name and its
location are embedded in the trap and the manager application has to be informed.
The IP Address is set via Destination Address parameter; the destination port of
the notification is set via Destination Port parameter. Default value is 162. It is fully
configurable and depends on the Manager/Agent agreement.
Time-Out for PM notification (in sec)

O&M Agent notification time-out. Default value is 120 seconds. It is fully
configurable and depends on the Manager/Agent agreement.
Max PM file size (in byte)

Max size of PM data files. Default is 1MB and it is also the maximum size allow by
the current implementation of the NE3S management protocol. Different Size
dimensions are configurable and depend on the Manager/Agent agreement, but it
cannot be set to value greater than 1MB.
Max NE x PM file
Max number of network element for which data are potentially stored in a single
performance file. Default is 100. It is suggested to maintain this value under 100.
The data transferred via PM file may refer to a number of real NEs lesser than the
configured value because the PM data file size is the most important limitation
concerning the file transfer.
File Storing period (in minutes)

O&M Agent file storing period.
Measurement Result Table max count

Default is 10. It is fully configurable and depends on the Manager/Agent
agreement.

911-431/02A0120 - Issue 1, March 2009
A-7
A.5 Configuring fine grained PM data collection

The previous steps guarantee that the functionality is active and the Manager/Agent
connectivity is working.
The NA-NV Connector can be configured in order to collect different performance for
each connected network element.
From NetViewer Advanced Update Pack Properties window choose the NA-NV
Connector line and then push the Configure PM Collection button:
Fig. A.12
Configuring fine grained PM data collection
The Perfomance Management window opens:

Fig. A.13
A-8
Performance Management window

911-431/02A0120 - Issue 1, March 2009
Network Element relevant information is reported for each item in the list:
NetAct Name: it is the NE nickname in the NetAct namespace.
NetViewer Name: it is the NE nickname in NetViewer namespace.
Collection Mode: it reports the type of the configured performance collection.

Possible values are:
Full collection: both 15m and 24h PM data collection is enabled [Default]
Only 15m: 15m PM data collection is enabled.
Only 24h: 24h PM data collection is enabled.
No collection: no PM data collection is enabled.
The specific granularity period collection enabling doesnt ensure real data
collection and transfer because it depends on the NE capability to provide PM
data for the selected granularity period.
On Windows right side two panels are available. They allow the operator to configure
the collection type for a single NE (Specific NE Configuration) or for all the managed
network elements (Global Configuration).
A.5.1
Global Configuration
In order to configure the collection for all the Network Elements is necessary to choose
the collection mode from Global Configuration panel as reported herebelow.
Fig. A.14
Global Configuration panel
Appling the setting via Apply to All button causes the change of the Collection Mode
for every item in the list.

911-431/02A0120 - Issue 1, March 2009
A-9
A.5.2
Specific Configuration
In order to configure the collection for a specific network element is necessary to find the
NE in the list and select the related list item.
In Specific NE Configuration panel the NetAct NE nickname appears and it is possible
to choose and apply the wanted Collection Mode.
Fig. A.15
A-10
Specific NE Configuration panel

911-431/02A0120 - Issue 1, March 2009
PRINTED in ITALY
NA-NV Connector 1.2
911-431/02A0120
NA-NV Connector 1.2
D.45
D.55
Issue 1, March 2009
NA-NV Connector 1.2

911-431/02A0120
Issue 1, March 2009
NA-NV Connector 1.2
911-431/02A0120
D.25
Issue 1, March 2009

911-431/02A0120
Issue 1, March 2009
D.30
NA-NV Connector 1.2
D.20
NA-NV Connector 1.2

911-431/02A0120
Issue 1, March 2009
911-431/02A0120
Issue 1, March 2009

911-431 02a0120

Uploaded by

Document Information

Original Description:

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

911-431 02a0120

Uploaded by

Copyright:

Available Formats

Operating Manual

NA-NV Connector 1.2

NA-NV Connector 1.2 - OMN

Issue 1, March 2009

NA-NV Connector 1.2 - OMN

NA-NV Connector 1.2 - OMN

GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

Purpose and Subject of the Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

Functions of the application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1

Software architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4

System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6

Supply Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6

Licenses for the use of the software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6

Related Manuals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6

List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7

System performances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.9

Firewall configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.9

SOFTWARE INSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

Installation of NA-NV Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1

Verification of the installed services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5

NA-NV Connector 1.2 - OMN

EQUIPMENT MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

Stop/start of NetViewer services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5

Supported equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1

NETWORK CONFIGURATION TO REMOTIZE THE GUI OF NETVIEWER . . . . . . . 4.1

Remote management of the NetViewer GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3

INSTALL AND CONFIGURE THE PERFORMANCE MANAGEMENT FRAGMENT. A.1

Install NA-NV Connector PM fragment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.2

Configuring local FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.4

Enabling Performance Data export service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.6

Configuring fine grained PM data collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A.8

NA-NV Connector 1.2 - OMN

Architectural design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5

NA-NV Connector 1.2 - OMN

NA-NV Connector 1.2 - OMN

1.2 Functions of the application

NA-NV Connector 1.2 - OMN

Mediation and adaptation

Topology adaptation (new managed objects)

FM adaptation (mediation adaptation and alarm manual pages)

PM adaptation (mediation adaptation and definition of measurement types and

Adaptation information for other applications

Adaptation of the element manager launch

Application layer includes management applications (monitoring, reporting, optimising

NetViewer - NetAct interaction note

On NetViewer map close, all the NetAct nodes will be deleted.

Basic Configuration Management

Performance Management (optional)

NA-NV Connector 1.2 - OMN

Basic Configuration Management

EMS GUI Remote launch

NA-NV Connector 1.2 - OMN

firewall between NetAct NetViewer Connector and NetAct

firewall between Citrix server and ICA clients

No firewalls are allowed between Citrix server and NetViewer server.

3rd party software

1.3 Software architecture

NA-NV Connector 1.2 - OMN

NetViewer Suite Host PC

Manage the dynamic functional plug-ins.

NA-NV Connector 1.2 - OMN

types of java interfaces are instantiated: