03 ft93123en05gla0 netviewer introduction doc

NetViewer Introduction

FT93123EN05GLA0 2011 Nokia Siemens Networks

1

Content

1 Product Position 3

2 Network Elements Portfolio 4

3 Network Scenarios 11

3.1 SDH Networks 11

3.2 Microwave SDH Ring 12

3.3 Microwave and Fiber Optic SDH Ring 13

3.4 Mixed Ring 14

3.5 Microwave Networks 15

4 NetViewer Configurations 16

4.1 Entry Configuration 17

4.2 Single Server Configuration 19

4.3 Multi Server Configuration 20

5 Warm Standby Server - Single Server 23

6 Weight associated to the equipment 25

7 Remote Launch 27

8 Web Interface 29

8.1 Web Access 30




2



3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Product Position

The NetViewer system represents the Element Management Layer of the Nokia

Siemens Networks

The product positioning and main functionalities are depicted in Fig. 1 NetViewer Product Positioning

Fig. 1 NetViewer Product Positioning



4

2 Network Elements Portfolio

The Network Elements controlled by NetViewer are mainly the NSN Microwave radio

NetViewer

Q1 Agent

Q1 Equipments

SRT 1F

SDH Trunk

FlexiMetro

SDH

TDMoP 4xE1

TDMoP 16xE

DF

DF Blade

DynaSwitchFE

FlexiNT22

FlexiLT22

Connection Master

SRAL XD

FlexiHybrid

FIU19E

FTFA

FTFB

PDH

FlexiPacket Radio

FlexiPacket MultiRadio

FlexiPacket Hub 1200

FlexiPacket Hub 2200

FlexiPacket Hub 800

FlexiPacket FirstMile 200

FlexiPacket eBand

Ethernet

Microwave portfolio Narrowband/Multiservice portfolio

Fig. 2 NetViewer Portfolio

Considering the communication protocol towards TMN, the following groups of

radio are identified:

radio equipment with OSI stack

radio equipment with IP stack

radio equipment with other proprietary stacks



5

2.1.1 Radio equipment with OSI stack

The standard OSI protocol via DCC (Data Communication Channels) - overhead bytes of the SDH signal - is normally supported by the SDH radios, for example SRT 1C, RT 1F. Anyway, the more recent SDH equipment don't implement OSI protocol: IP based protocols are used instead (e.g. FlexiMetro).

2.1.2 Radio Equipment with IP stack

The IP protocol is supported by the major part of the former-Siemens microwave equipments, for example SRA L, SRA Series 3, SRAL XD, FlexiMetro. The protocol stack for these radio devices is usually TCP over IP: so they require a TCP/IP DCN for the connection to TMNS. Thanks to Dual-Q adapter equipment (a device able to tunnell/detunell IP messages over OSI ), it's possible to avoid the necessity to create two different DCNs when SDH (typically OSI based) and IP radio equipments are simultaneously present,: in such a way only SDH DCN is implemented in the network Fig. 3 OSI-DCN and Payload Transport Network. shows an example of a network with a DualQ-Adapter equipment

Fig. 3 OSI-DCN and Payload Transport Network



6

Another family of equipments, typically the ones with SNMP communication protocol,

has a UDP/IP stack, instead of TCP/IP; for example:

SRT 1F microwave radio equipment

Narrowband equipment (TDMoP)

Multiservice equipment (DF family)

FIU19E/FTFA radio equipment

FlexiHybrid SDH radio equipment

DualQ-Adapter Enhanced.

2.1.3 Radio Equipment with proprietary stack

Q1 is the protocol supported by some former-Nokia network elements. NetViewer supervises them by mean of the software product called "Q1-Agent", which publishes a NE3S (SNMPv2c over UDP plus XML over FTP) interface towards the EMS. NetViewer does not connect directly Q1 network elements, see Fig. 4 Scenario with Q1 NEs managed by NetViewer Q1 NEs can be microwave radio devices or other types of equipment supporting data transport.

TIP Only for some Q1 NE the direct connection to NetViewer through SNMP interface is possible; for example:

FIU19E microwave NEs

FTFA microwave radio NEs.



7

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fig. 4 Scenario with Q1 NEs managed by NetViewer



8

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. The supported remote pollers are:

DCN Adapter (DCN-A)

AXC.

DCN-A unit has (up to) 3 buses for connecting NEs and AXC has 1 bus for this purpose. Q1 protocol is used for communication between the remote pollers and NEs.

Fig. 5 Communication interfaces between Q1 Agent and Q1 NEs



9

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DCN Adapter

135 mm240 mm

22 mm

DCN Adapter rack shelf for 6 units

LEDs DC

Bus 0 Bus 1 Bus 2LMI LAN

DCN Adapter

Fig. 6 DCN Adapter Example



10

Here below all the Node Types currently supported by NetViewer are listed:

ACL2 ACL4 ACM2 ACM2V2 ACM2V5 ACM2_V5.1 ACM4

ACM4_V2 Ala-asema Branching Unit CO140 CO2 CO2-8 CO34 CO8-34 DB 2B DB 2B-CD DB 2B-LB DB 2B-LP DB 2BP DB 2T DF140 DF2-8 DF34 DFE1000 DL2E DL2E IREM

DL2E IREM 260V DL2EREP DM140 DM2 DM2+ DM34 DM8

DMF DMF 16x2 DMR DMR13-18CE DMR18-38CE DMR2000

DMR7000 DN2 DNT128 DNT128 -sp DNT1M DNT2M

DNT2M 1p DNT2M mp DNT2M sp DR13 DR15 DR1500E

FC E1T1 FC RRI FXC E1 Asymm FXC E1T1 Symm FXC HDSL

FXC RRI Hopper 19 Hopper FC RRI Hopper IFUE Hopper RRIC

ILT128 ILT1M Nokia DNT2M Nokia DNT2M -mp Nokia DNT2M -sp

Nokia MetroHub SubStation TMS Adaptor ACL2i dc ACL2ti pf

DNT2Mi sp DNT2Mi mp ACL2i pf DSL2i DNT2Mi-fp530

DNT2Mi-fp G.704 DNT2Mi DNT2M-G mp DNT2M-G sp

ACL8i 75 ohm modem 1 ACL8i 75 ohm modem 2 ACL8i 75 ohm modem 3 ACL8i 75 ohm modem 4 ACL2i FlexiHub 2U Connection Master

TIP Possible Node Types not included in the previous list are supported by NetViewer as

Node Type Unknown



11

3 Network Scenarios

This paragraph gives an overview of the network scenarios, which are managed by the NetViewer Elements Management System [EMS]. The scenarios described here are not assaultive

3.1 SDH Networks

NetViewer is able to reach and manage microwave equipment in SDH networks. Considering older SDH equipment, this is done thanks to an OSI stack integrated in Net- Viewer . More recent equipment, anyway, are managed via IP stack.

Fig. 7 NetViewer and Microwave Equipment in SDH Network



12

3.2 Microwave SDH Ring

SDH microwave ring can be used for the distribution of 2 Mbit/s signal via SRA L

Fig. 8 Microwave SDH Ring



13

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.3 Microwave and Fiber Optic SDH Ring

Metropolitan networks often require 2 Mbit/s microwave distributions: this is achieved by SRA L

Fig. 9 Microwave distributes 2Mbs Signals



14

3.4 Mixed Ring

It can occur that STM ring cannot be closed with fiber optic equipment for geographical reasons, so microwave equipment can be used

Fig. 10 Microwave and Fiber Optic Equipment in the same Ring



15

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.5 Microwave Networks

In this scenario, NetViewer is able to manage the microwave radio network

elements.

Fig. 11 Microwave Networks



16

4 NetViewer Configurations

NetViewer is a very flexible management system, allowing the expansion of the management network according to the network growth. For small networks (up to 100 NEs) a simple Notebook PC can be enough; for very wide networks, the Multi Server configuration with several PCs can be very useful. In the following paragraphs the allowed network configurations are described.

Nokia Siemens Networks

2500** NEs* 20 Clients

Single Server

server

Multiple Server

main server

slave serversclients

clients

* Network Element equivalent

** at NetViewer 10.2 C5

10.000 max NEs* 30 max clients 10 max slave servers

Fig. 12General Configuration Overview



17

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Entry Configuration

The Entry one is the minimum configuration for small networks: the subcomponents Server and Client are installed on a single PC

Only one access is available and it is considered as a start up configuration. The migration to a higher configuration can be done using the PC as Client PC and adding the Server PC.

NV Entry Notebook

Q1 Network

Q1 Agent

NV Entry Notebook

MWR & NB/MS

Network

Entry Notebook Managed NEs: up to 100 Client and Server in the

same Notebook No additional software

modules All-in-one configuration:

Q1 Agent + NetViewer + Node Manager(s) on same HW

Fig. 13 Entry Configuration with Notebook Example



18

NV Entry

Q1 Network

Q1 Agent

MWR & NB/MS

Network

NV Entry Entry

Managed NEs: up to 200 Client and Server in the same

Notebook

No additional software modules

All-in-one configurationQ1 Agent + NetViewer + Node Manager(s) on same HW

Fig. 14 Entry configuration Example

TIP The system Database is Microsoft Access.



19

4.2 Single Server Configuration

For medium networks the Server and Client subcomponents are installed on different PCs To support a distributed operation of the network, several NetViewer Clients can operate simultaneously. Concurrent access to network resources is handled by the Server:

only one operator at a time may obtain write access to a certain network element

concurrent access, to NE data, is any way possible in read-only mode.

NV Server

Operational Cent

res

remotely located

NV Client 1NV Client 2

NV Client 3

NV Client 20

Q1 Network

Q1 Agent

MWR & NB/MS

Network

OR

Fig. 15 Single Server Configuration Example

TIP In order to know the maximum numbers of NEs managed by a single server see chapter :6



20

4.3 Multi Server Configuration

NetViewer can be configured with several Servers to scale the network management.

In the Multi Server configuration a Server, called Main-Server, has the role of MasterServer; the other ones, called Sub-Servers, are the Slave Servers. Each Server is functionally independent and it manages the communication with its NEs. The difference between Main-Server and Sub-Servers concerns the network view: the map managed by the Main-Server contains the Sub-Servers. In other words, the Main-Server sees all the NEs managed by the Sub-Servers; on the contrary, a Sub-Server sees only its own NEs.

In a Multi Server configuration it is not allowed:

having nested Sub-Servers: there is only one level of Sub-Servers

having multiple representation of the same NE, in the network, also if they are in different servers: the violation of this rule can cause system malfunction.

Q1 Network 1

MWR & NB/MS

Network 2

NV Master

NV Client(s)

Q1 Agent 1

NV Serve 2

Q1 Agent or NV server 10

Fig. 16 Multi Server Configuration Example

TIP

In order to know the maximum numbers of NEs managed by a multi server see chapter :6

WARNING In Multi Server Configuration from the SVR 10.x , the Main Server doesnt manage any Network Elements but only Sub Server



21

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.3.1 Subserver Types

The versions of NetViewer prior to the V9.5 managed only the native Sub-Server type: the native type is simply another installation of the NetViewer Server. Starting from Net- Viewer V9.5, other types are supported.

The native Sub-Servers share with the Main- Server the behavior and the interfaces, so they can be managed with the same graphical interfaces, both for run-time supervision (via GUI Client) and for off-line network design (via NetBuilder tool). The newer Sub-Server types are products different from Net- Viewer, and each of them provides its user management interface. Due to this reason, the NetViewer GUI can connect directly the native Sub-Servers, but not the other Sub- Servers; the supervision of the NEs in a non-native Sub-Server map can be done, by the operator, via a NetViewer GUI connected to the Main-Server, as depicted in Fig. 17Different Types of Subserver

Fig. 17Different Types of Subserver



22

Each "additional" Sub-Server type has its proper configuration tool, where the native one is supported by NetBuilder

The Q1 Sub-Server is configured via a WEB browser connected to the HTTP Server implemented by the Q1 Sub-Server itself.

Fig. 18 Native and Q1 Subserver Configuration Way



23

5 Warm Standby Server - Single Server

This configuration may be used if the customer wants to have the system working even if the Server PC fails (e.g. because of a serious hardware failure, a fire in the management centre, ...). The concept of the Standby solution is the protection of the whole Server system. The Standby Server is a second Server machine, which can be situated on local Fig. 19 Local NetViewer Warm Standby Configuration or on remote site Fig. 20 Remote NetViewer Warm Standby Configuration. Both the Active and Standby Server have identical hardware and software configuration.

Fig. 19 Local NetViewer Warm Standby Configuration



24

Fig. 20 Remote NetViewer Warm Standby Configuration

NetViewer Clustering Architecture of Microsoft Windows is the base of NetViewer Warm Standby system. The Clustering Architecture presents to the network of Net- Viewer Clients a redundant group of hosts that act as a single logical Server (that is they share a single "virtual" IP address). If the host currently "active" failed, another host would quickly takeover the Server's responsibilities allowing the Clients to continue submitting requests to the Server without knowing anything about the physical Server's switch. During the normal system run all Database transactions on the Active Server are automatically replicated to the Standby Server. In case of a breakdown of the Active NetViewer Server the network control is automatically assumed by the Standby Server and only a short period off loss of supervision may occur

In case of remote localization of NetViewer Standby PC, it is required to connect the LAN by a dedicated link: the same has to be done for the network connection. In the Fig. 20 Remote NetViewer Warm Standby Configuration, two couples of routers are drawn for underlining the dedicated links concept: really only a couple of routers can be used, but it can be useful to split the link load in the router in two parts



25

6 Weight associated to the equipment

In order to determine the total number of elements that can be managed by a NetViewer native Sub-Server/NetViewer Single Server, also the weight associated to each type of element must be considered.

In the following table are reported the main NetViewer configuration, with the max number of NE that can be manage.

Configurations Max NE equivalents Other limitations

Entry/Entry Notebook Configuration

200 NEeq Max 200 SDH trunk 1

Max 200 SDH trunk 2

Max 200 SPS 155

Single Server/ Sub Server

2500 NEeq Max 250 SDH trunk 1

Max 200 SDH trunk 2

Max 250 SPS 155

Main Server

(Multi server configuration)

10000 NEeq

(NO direct NE managed)

Q1 Sub Server 3600 NEs -

Q1 Sub Server in Entry 200 NEs -

WARNING Take care that NEeq = Network Element Equivalent is referred to the SRAL (XD) equipment. and the value is 1



26

Different Type of NEs have different weights

MW NE = SRA L, SRAL XD

NEeq = 1

MW NE = FTFA, FTFB, FIU19E

NEeq = 1

SRT 1, SRT 1C, SRA, SPS 155, SRT 1S NEeq = 1

SPS E, SRA S3, FlexiMetro

NEeq = 1

FlexiHybrid

NEeq = 2

SRT 1F

NEeq = 2

FlexiPacket Radio, FlexiPacket MultiRadio

NEeq = 1

FlexiPacket Hub 1200, FlexiPacket Hub 2200,

NEeq = 2

FlexiPacket FirstMile 200, FlexiPacket HUB 800/800H

NEeq = 1

DualQ Adapter

NEeq = 1

DF1/4, DF1/4 Blade, DF CX, TDMoP 4xE1, TDMoP 16xE1

NEeq = 1

SNMP Based Device

NEeq = 1

Legacy Nokia Q1 MWR supported through Q1 Agent

NEeq = 1

Legacy Nokia Q1 NB/MS supported through Q1 Agent

NEeq = 1

SUMMARY Example. 100 Flexi Packet Radio + 100 Flexi Packet 1200 = 300 NEs

In a Multiserver configuration the max number of NEeq is 10000, that means 5000 Flexi Packet Hub (1200/2200)



27

7 Remote Launch

NetViewer is tested and certified to be compatible with the remote launch of the GUI client, via Citrix XenApp. This framework allows having, at a terminal, the display of a program running on a different PC; it is possible, in other words, to operate on the graphical interface of a program not installed and running locally.

Fig. 21 Single Server with Citrix Environment



28

Fig. 22 GUI Remote Launch provides a deeper look in the architecture supporting the remote launch of NetViewer GUI

Fig. 22 GUI Remote Launch



29

8 Web Interface

The main function of NetViewer HTTP Server is to provide an Internet/Intranet access towards NetViewer Serve

This feature allows monitoring the status of the radio network managed by NetViewer from every PC/Palmtop connected in Internet/Intranet with the Server PC by means of a Microsoft Internet Explorer type browser. By means of WEB Client, the operator can execute read-only operations. In detail, it is possible, according to query to the Database and to the NetViewer Server engine, to manage from the browser the following functions:

Network Alarm List

NE Alarm List

Network History Report

NE History Report

Network Performance Report

NE Performance Report

Network Inventory Report

NE Inventory Report


Fig. 23 Access via Intra/Internet from Browser towards NetViewer Server



30

8.1 Web Access

From the Browser type the server IP address follow by \NetViewer

The Web browser login page appears:

User Name : administrator

Pss: sysmanager


Fig. 24 Web Access



31

The Web Client User Interface appears:

The WEB Client is a HTTP interface that allows monitoring the status of the radio network and of the NEs directly from a browser. The displaying on browser of the network map foresees a series of HTML pages opened in cascade starting from the main root page of the Server network map (Root Map page) up to reach the status page of the single NEs.


Fig. 25 Web Client Interface



32

On each HTML page, except for the login page, a tool bar is present, that provides the following buttons:

Back: it is the command to come back to the previous page (it corresponds to the backward command of the browser)

RootMap: it opens the main root page of the network map

Network Alarm List: it opens the page that lists all the alarms currently activated over the whole radio network

History: it opens the query page of the Network History Report

Performance: it opens the query page of the network Performance Report

Inventory: it opens the query page of the Network Inventory Report

Options: it opens the setting page of the report displaying parameters

Tools: it opens the window of the reports available via Reporting Services

Downloads: it opens the window for the download via HTTP of the Client components and updates

NetViewer Introduction1 Product Position2 Network Elements Portfolio2.1.1 Radio equipment with OSI stack2.1.2 Radio Equipment with IP stack2.1.3 Radio Equipment with proprietary stack

3 Network Scenarios3.1 SDH Networks3.2 Microwave SDH Ring3.3 Microwave and Fiber Optic SDH Ring3.4 Mixed Ring3.5 Microwave Networks

4 NetViewer Configurations4.1 Entry Configuration4.2 Single Server Configuration4.3 Multi Server Configuration4.3.1 Subserver Types

5 Warm Standby Server - Single Server6 Weight associated to the equipment7 Remote Launch8 Web Interface8.1 Web Access

03 ft93123en05gla0 netviewer introduction doc

Documents

osi stack radio equipment

ip stack radio equipment

netviewer portfolio

sdh networks

nokia siemens networks

microwave networks

netviewer system

netviewer configurations