NMS/10 SR C5.

0
Nokia Network Management System/10

Product Overview

C33820.20 B0

C33820002SE_A0 © Nokia Networks Oy 1 (50)

 Product Overview

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This document is intended for the
use of Nokia Networks’ customers only for the purposes of the agreement under which the
document is submitted, and no part of it may be reproduced or transmitted in any form or
means without the prior written permission of Nokia Networks. The document has been
prepared to be used by professional and properly trained personnel, and the customer
assumes full responsibility when using it. Nokia Networks welcomes customer comments as
part of the process of continuous development and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or
performance of the mentioned hardware or software products cannot be considered binding
but shall be defined in the agreement made between Nokia Networks and the customer.
However, Nokia 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
Networks will, if necessary, explain issues which may not be covered by the document.
Nokia Networks’ liability for any errors in the document is limited to the documentary
correction of errors. Nokia Networks WILL NOT BE RESPONSIBLE IN ANY EVENT FOR
ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR
CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this
document or the information in it.
This document and the product it describes are considered protected by copyright according
to the applicable laws.
NOKIA logo is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective
companies, and they are mentioned for identification purposes only.
Copyright © Nokia Networks Oy 2000. All rights reserved.

2 (50) © Nokia Networks Oy C33820002SE_A0

 Contents

Contents

1 About this document............................................................................6

2 Introduction to NMS/10 ........................................................................8

2.1 System Release overview.......................................................................8
2.2 NMS/10 system concept.........................................................................9
2.3 NMS/10 System Frame ........................................................................10
2.4 Agents ..................................................................................................10
2.5 Mediators..............................................................................................11
2.6 Node managers ....................................................................................11
2.7 GCS and NMS/10 Command Scripting .................................................12

3 Features ..............................................................................................13
3.1 General features...................................................................................13
3.2 Remote access.....................................................................................14
3.2.1 Remote access to NMS/10 System Frame ...........................................14
3.2.2 Remote access to node managers .......................................................15
3.3 Performance management ...................................................................15
3.4 SNMP interface ....................................................................................16
3.4.1 Downward interface..............................................................................16
3.4.2 Upward interface ..................................................................................16
3.5 NMS/10 Command Scripting (RCM) macros ........................................17
3.6 Q1 network test ....................................................................................17
3.7 Security ................................................................................................17
3.7.1 Windows NT security ............................................................................18
3.7.2 Security in the System Frame...............................................................18
3.7.3 Agent security.......................................................................................18
3.7.4 NMS/10 MF and node manager security...............................................18

4 Applications........................................................................................19
4.1 NMS/10 in mobile networks ..................................................................20
4.2 Integration with third-party management systems.................................21
4.3 Stand-alone applications ......................................................................22
4.4 Managing nodes ...................................................................................23
4.4.1 Managing Synfonet nodes ....................................................................23
4.4.2 Managing Q1-managed nodes .............................................................24
4.4.3 Managing SDH radios...........................................................................26

5 NMS/10 System Frame user interface ...............................................28

5.1 Introduction...........................................................................................28
5.2 Network maps ......................................................................................29
5.2.1 Maps ....................................................................................................29
5.2.2 Submaps ..............................................................................................29
5.2.3 Symbols................................................................................................29
5.3 Alarms and events................................................................................31
5.4 Running node managers ......................................................................32

C33820002SE_A0 © Nokia Networks Oy 3 (50)

 Product Overview

5.4.1 Synfonet node managers......................................................................32

5.4.2 Q1 node managers ...............................................................................33
5.4.3 SDH radio equipment node managers ..................................................33

6 NMS/10 SR products ..........................................................................34

6.1 Sales items...........................................................................................34
6.1.1 Media....................................................................................................34
6.1.2 Software licences .................................................................................35
6.1.3 Printed documentation..........................................................................35
6.2 Product codes.......................................................................................35
6.2.1 CD-R Media..........................................................................................35
6.2.2 HP OpenView NNM products and licences...........................................36
6.2.3 NMS/10 System Frame licences...........................................................36
6.2.4 NMS/10 Q3 Agent licences...................................................................36
6.2.5 NMS/10 SDH Radio Agent licences......................................................37
6.2.6 NMS/10 MF ..........................................................................................37
6.2.7 MF Manager licences ...........................................................................38
6.3 Document product codes ......................................................................38
6.4 Compatibility information.......................................................................39
6.4.1 Supported Synfonet node types............................................................39
6.4.2 Supported Nokia SDH radios................................................................39
6.4.3 Supported Q1 network element management systems.........................39
6.4.4 Supported node managers ...................................................................40

7 System requirements .........................................................................41

7.1 General.................................................................................................41
7.2 Product-specific requirements ..............................................................42
7.2.1 NMS/10 System Frame PC...................................................................42
7.2.2 NMS/10 Remote Station .......................................................................42
7.2.3 NMS/10 Remote Console .....................................................................43
7.2.4 NMS/10 Q3 Agent ................................................................................43
7.2.5 NMS/10 SDH Radio Agent....................................................................43
7.2.6 NERA NEW-NMS .................................................................................43
7.2.7 NMS/10 MF C2.0 ..................................................................................43
7.3 Integration with network-level Nokia NMS.............................................44
7.4 Network connection and alarm monitoring ............................................44
7.4.1 Q3 managed nodes (Synfonet) .............................................................44
7.4.2 NMS/10 MF ..........................................................................................44
7.4.3 SDH radios ...........................................................................................44

4 (50) © Nokia Networks Oy C33820002SE_A0

 Summary of changes

Summary of changes

Document number Date Comment

C33820002SE_00 14 Apr 2000 Valid for programs:
P31159.01, 02, 03 release A
P31159.51, 52, 53 release A
C33820002SE_A0 7 Jun 2000 Valid for programs:
P31159.01, 02, 03 release A
P31159.51, 52, 53 release A

C33820002SE_A0 © Nokia Networks Oy 5 (50)

 Product Overview

1 About this document

This document describes the general features of NMS/10 and is intended for
anyone who wishes to get an overview of the functions and operation of the
NMS/10 network management application.
This Product Overview covers the following topics:
• Introduction to NMS/10 (Chapter 2)
• Features (Chapter 3)
• Applications (Chapter 4)
• NMS/10 System Frame user interface (Chapter 5)
• NMS/10 SR products (Chapter 6)
• System requirements (Chapter 7)
• Glossary.
Note that the windows shown in this document are examples; the exact contents
will depend on the installed agents and node managers, managed network and
its status.

6 (50) © Nokia Networks Oy C33820002SE_A0

 About this document

References
For further information, refer to the following operating manuals:
• NMS/10 System Release User Manual
• NMS/10 Q3 Agent User Manual
• NMS/10 SDH Radio Agent User Manual
• NMS/10 MF Operating Manual
• MF Manager User’s Manual
• User manuals of the various Nokia node managers
• Microsoft Windows NT Workstation documentation
• Microsoft Windows NT Server, Terminal Server Edition documentation
• HP OpenView Network Node Manager for Windows NT (HP OpenView
NNM) user documentation
• User documentation of the PCs.

C33820002SE_A0 © Nokia Networks Oy 7 (50)

 Product Overview

2 Introduction to NMS/10
This chapter introduces NMS/10, describes the main functions of the system
and its key components, and explains how they work together. It covers the
following topics:
• System Release overview (section 2.1)
• NMS/10 system concept (section 2.2)
• NMS/10 System Frame (section 2.3)
• Agents (section 2.4)
• Mediators (section 2.5)
• Node managers (section 2.5)
• GCS and NMS/10 Command Scripting (section 2.7).

2.1 System Release overview

Nokia Network Management System/10 (NMS/10) products are part of the
Nokia NMS family, which provides management for a network composed of
Nokia’s telecommunications products. NMS/10 is an element-level
management system, and can be used either for small transmission networks, or
as part of the management solution for larger networks.
The primary function of NMS/10 is to collect alarms and performance data from
the network devices that are managed by the NMS/10 agents and to present the
alarm information to network operations staff. PM data can be post-processed
using external tools.
Interfaces to integrate Nokia NMS/10 with other Nokia NMS products and to
third party network management systems are included with the System Release.
Configuration management of network elements is undertaken by using node
managers.

8 (50) © Nokia Networks Oy C33820002SE_A0

 Introduction to NMS/10

2.2 NMS/10 system concept

The NMS/10 system concept combines several products to provide a network
overview and detailed equipment configuration.
NMS/10 System Release consists of a core program, the System Frame,
together with separate agents, mediators and node managers. Agents collect
alarms and performance data from various network elements. Node managers
configure the network elements. NMS/10 manages objects that represent:
• Synfonet nodes and areas
• Q1-managed nodes (PDH/Primary Rate Equipment nodes, buses and
stations, and Nokia Q1-managed equipment, for example, FIU 19,
MetroHopper, FlexiHopper, MetroHub)
• SDH radios (Nokia PowerHopper, NERA CityLink, NERA NL29x),
NERA Element vieWer - Network Management Systems (NEW-NMS)
and sections.

NMS/10
Windows NT Workstation

Windows NT TSE
Q1-managed nodes
Q3 Agent

Q1 management bus LAN/WAN

connection
V.11 connection

LAN/WAN connection Q3 network

NMS/10 MF C2.0
(with MF Agent)

Figure 1. A simplified NMS/10 configuration

NMS/10 System Frame provides a network-level user interface and database

system management. This supports a selection of separate agents and node
managers, as required by the configuration of the network. By combining
different programs with NMS/10 System Frame, it is possible to create an
integrated network management system for a range of different networks.

C33820002SE_A0 © Nokia Networks Oy 9 (50)

 Product Overview

2.3 NMS/10 System Frame

NMS/10 System Frame provides the management system platform. NMS/10
System Frame runs on top of Hewlett-Packard’s OpenView Network Node
Manager for Windows NT product. HP OpenView NNM has been extended by
Nokia to provide a generic user interface for networks consisting of Nokia's
network elements.
The extension provided by Nokia is what is known as ‘NMS/10 System Frame’.
However, when referring to the management system, ‘NMS/10 System Frame’
is generally intended to encompass both parts.

2.4 Agents
An agent is a software program that collects alarms and performance data from
nodes on the network. Alarm information is stored for in the 'run-time' memory
of the computer on which the agent is running, and the destination management
systems are notified via SNMP. Performance data is saved to disk files on the
agent computer and it can be separately retrieved via FTP. This kind of an agent
can also be called a proxy agent.
Agents for nodes of various types mediate between these nodes and a network
management system to provide an open interface. Agents can therefore also be
used in multi-vendor cases, where integration with other management systems
is needed.
Agents can be configured using an agent configuration tool.

Agent configuration tool

An agent is configured by an agent configuration tool that allows you to
undertake some or all of the following:
• Configure the Simple Network Management Protocol (SNMP); the agent
uses SNMP to communicate with the management system
• Determine the nodes that will be managed by a particular agent
• Configure the destinations to which the agent’s alarm data is sent
• Configure security controls
• Configure node termination points for performance management
• Configure the locations from which a user can view or modify an agent’s
configuration via SNMP.

10 (50) © Nokia Networks Oy C33820002SE_A0

 Introduction to NMS/10

2.5 Mediators

NMS/10 Mediation Function (NMS/10 MF)

NMS/10 MF is used for collecting Q1 alarms and other messages from Nokia’s
Q1-managed nodes and mediating between these equipment and a supervising
management system, such as NMS/10 System Frame. NMS/10 MF C2.0 can
also be used as an MF Agent.
NMS/10 MF is also designed to be used as a replacement for Nokia’s TMS4
Transmission Management System as it emulates the TMS4 interface for a
supervising network management system.
NMS/10 MF is a robust and fault-tolerant subsystem that does not require daily
supervision or maintenance after it has been initially installed and configured. A
watchdog timer in the MF workstation provides automatic recovery from
possible software failures. Thus, NMS/10 MF can also be located onto remote
network sites.
The main new features offered by NMS/10 MF C2.0 are: Q1 network test, fault
management information transport via an SNMP interface, and support for the
enhanced Nokia Q1 protocol.

2.6 Node managers

Node managers are used to configure nodes. They are available for the different
types of Synfonet node, Q1-managed node, and SDH radio.
Node managers are independent programs. The System Frame integrates node
managers by making them available for launch. This can be done by, for
example, double-clicking a node symbol on a submap.
Node managers can be placed on the same, local computer (except for NMS/10
MF and NEW-NMS) as the agents and the System Frame, or they can reside on
a remote computer, possibly devoid of other NMS/10 programs.
The only requirement on the remote computers is that they must run the
Windows NT Server 4.0, Terminal Server Edition (Windows NT TSE), and the
NMS/10 System Frame computer must run the Windows NT TSE Client
software. This is so that the user input from the local computer can be received
and used by the remote computer, and so that the display output from the
remote computer reflects back to the local computer.

C33820002SE_A0 © Nokia Networks Oy 11 (50)

 Product Overview

2.7 GCS and NMS/10 Command Scripting

General Communication Service (GCS) communication stack and NMS/10
Command Scripting (RCM) utility are included in the NMS/10 SR C5.0 CD-R
Media to provide additional functionality and facilities.

General Communication Service

General Communication Service is a communication stack that is used by node
managers to communicate with Nokia’s Q1-managed nodes. The Nokia
Connection Tool, which is part of General Communication Service, allows you
to define Q1 connections that are saved to the node manager database. These
connections are required to enable, for example, a node manager to connect to a
node.

NMS/10 Command Scripting

The NMS/10 Command Scripting utility provides a mechanism to execute
macros, or scripts, written in the Visual Basic for Scripting Language. The
scripts can be executed manually or scheduled. A script normally accesses Q1-
managed nodes, that is, sends commands. This could be, for example, to
retrieve performance data. To access Q1-managed nodes, the General
Communication Service R4.1 communication stack is required. A web-based
interface is required for configuring and using RCM.

12 (50) © Nokia Networks Oy C33820002SE_A0

 Features

3 Features
NMS/10 System Release has many advanced features in addition to all the
essential network management system features described in Chapter 2. This
chapter describes these features in detail, covering the following topics:
• General features (section 3.1)
• Remote access (section 3.2)
• Performance management (section 3.3)
• SNMP interface (section 3.4)
• NMS/10 Command Scripting macros (section 3.5)
• Q1 network test (section 3.6)
• Security (section 3.7).

3.1 General features

NMS/10 System Frame provides an easy-to-use graphical user interface for the
following network management tasks:
• Create network maps to show the real-time alarm status of nodes
operating in a network. The maps are displayed graphically, and can be
arranged into hierarchies
• Obtain and display alarm and event information from nodes
− Sort and filter the alarm information
− View alarm history for a user-specified time period
− Save alarm information to the database for later analysing and
reporting
− Export alarm information to email and a serial port in ASCII
format (into a serial printer or to another system) for archiving or
further processing

C33820002SE_A0 © Nokia Networks Oy 13 (50)

 Product Overview

• Add agents and node managers to the System Frame

• Print lists of new, cleared, or acknowledged alarms and events
• Run node manager applications for network nodes to modify their role in
the network.

3.2 Remote access

Remote use is a common requirement with operators that do not have 24-hour
activity in their network management centre but rely on qualified operators to
sort out any emergency situations outside working hours remotely from their
home or from another management centre. When the network management
system can be accessed remotely, specialist personnel is not needed at the
network management centre 24 hours a day, as emergencies can be handled by
another centre.

3.2.1 Remote access to NMS/10 System Frame

NMS/10 System Release C5.0 is based on client-server architecture. There are

three main remote access methods available from a client workstation:
• NMS/10 Remote Station
• NMS/10 Remote Console
• web browser.

NMS/10 Remote Station

When NMS/10 System Frame is run on a remote terminal with HP OpenView
NNM Remote Console, the client setup is called the NMS/10 Remote Station.
The following functionality is available remotely:
• viewing the network submaps
• viewing current alarms and the event log
• handling (cancelling, acknowledging) current alarms
• launching node managers (requires a Windows TSE Client).
Using NMS/10 System Frame remotely and locally can be done at the same
time. Also, several simultaneous remote stations are possible. However, using
several remote stations may decrease the performance of the system.
One NMS/10 System Frame licence is required for each remote station, but the
HP OpenView NNM licence for the server PC covers also the remote user
interfaces.

14 (50) © Nokia Networks Oy C33820002SE_A0

 Features

NMS/10 Remote Console

When only the HP OpenView NNM Remote Console is run on a remote
terminal, current alarms can be monitored via the HP OpenView NNM event
browser over this interface.

Web browser
Another method to access NMS/10 System Frame remotely is to use a web
browser. There are two ways of doing this:
• A web browser can be used to access the NMS/10 System Frame PC: all
the NMS/10 functionality is not available, but for example current alarms
can be monitored via the HP OpenView NNM event browser over this
interface.
• A web browser can be used to access agents directly to display the
current alarm view.

3.2.2 Remote access to node managers

NMS/10 System Release C5.0 is a distributed system. Remote access can be

used for starting up and displaying the remotely running node manager onto the
screen of the PC, which NMS/10 System Frame is running on. Although the
node managers were installed in a remote PC, it is still possible to start node
manager applications directly from the NMS/10 System Frame user interface by
double-clicking the network element symbols.
If node managers are not run on the same computer as the NMS/10 System
Frame software, the remote computers must run the Windows NT Server 4.0,
Terminal Server Edition (Windows NT TSE), and the NMS/10 System Frame
computer must run the Windows NT TSE Client software.

3.3 Performance management

In previous releases of NMS/10 System Release, performance data recorded by
network elements could be collected from Q1-managed nodes. In NMS/10 SR
C5.0, performance data can also be collected from Synfonet nodes. Performance
data can be used for the following purposes:
• Maintenance monitoring aims at keeping the network as flawless as
possible. With error performance monitoring, it is possible to identify the
degrading systems before they fail and affect the network services. The
most important counters for maintenance purposes are those in the
regenerator and multiplexer sections.
• With routine monitoring, it is possible to produce hourly, daily, weekly,
and monthly summaries of the performance helping to discover faulty

C33820002SE_A0 © Nokia Networks Oy 15 (50)

 Product Overview

equipment in time. With monitoring on demand, performance data can be

requested on an essentially real-time basis from the node. This allows the
verification of corrections of errors, installation, or acceptance testing.
• Monitoring the quality of the services provided for the customer. Through
performance monitoring, it is possible to produce reports on the trends of
the quality of service both for operator’s internal use and for customers. It
is also possible to verify that the performance criteria agreed with the
customer are met.
The NMS/10 user activates the performance data collection on the nodes by
selecting periods and termination points from which performance measurements
are collected. The performance data is then periodically retrieved (polled) from
the node and stored in a text file on the agent PC. The post-processing of the
data can be carried out using any chosen, external tool.

3.4 SNMP interface

As an industry standard interface, SNMP allows the integration of SNMP
managed elements into the Nokia network management product family. Nokia’s
network elements can also be managed using third-party management systems
that support the SNMP interface.

3.4.1 Downward interface

HP OpenView NNM is a network management system widely used for the

management of datacommunication networks consisting of a large number of
workstations, routers, and bridges. NMS/10 System Frame C5.0 is based on HP
OpenView NNM, thus providing a possibility to use one management platform
to manage transmission and datacommunication networks. If HP OpenView
NNM is already in use, NMS/10 System Frame can be integrated to the
existing, familiar network management platform.

3.4.2 Upward interface

In case the operator has an existing management system equipped with an

SNMP interface, events from management systems that cannot produce SNMP
traps need to be converted before they can be handled by the existing system.
Since NMS/10 agents can directly generate SNMP traps, there is no need to
make a protocol conversion to be able to monitor Nokia’s network elements by
third-party management systems.

16 (50) © Nokia Networks Oy C33820002SE_A0

 Features

3.5 NMS/10 Command Scripting (RCM) macros

NMS/10 Command Scripting (RCM) for NMS/10 SR C5.0 provides means to
execute macros, or scripts, written in Microsoft Visual Basic Scripting Edition.
The scripts can be executed manually or scheduled.
Scripts are managed, executed and scheduled through a web interface. A script
normally accesses Nokia Q1-managed network elements, that is, sends menu
commands.
NMS/10 Command Scripting is intended for providing the functionality of
Remote Control and Measurement of Nokia’s TMS4. A tool is provided to
convert the TMS4 RCM definitions (macros and schedules) to NMS/10
Command Scripting scripts and schedules. The RCM definitions can also be
moved between NMS/10 systems.

3.6 Q1 network test

This feature has been added to the NMS/10 MF Agent C2.0 to be able to test Q1
data communications networks (DCN). This feature enables finding DCN
problems that are not normally found. Q1 network test is used for monitoring
the state of the network connections and command-answer tests for the alarm
units in the system. These facilities are used when commissioning the system or
when the alarm units or supervision connections require testing.

3.7 Security
NMS/10 security involves several components:
• The Windows NT computers used (local security is supported)
• NMS/10 System Frame
• Agents
• Mediators (NMS/10 MF)
• Node managers
• Remote control and measurement (with NMS/10 Command Scripting).
Security is necessary to:
• Restrict access to those authorised to have it
• Restrict access to files and data to protect their physical integrity, to avoid
accidental damage or deliberate sabotage.

C33820002SE_A0 © Nokia Networks Oy 17 (50)

 Product Overview

3.7.1 Windows NT security

Generally, security in NMS/10 is based on the use of Windows NT local

security features, which are based on an individual computer. User groups are
employed widely and a basic set of user groups is installed alongside NMS/10
System Frame.
Applications that do not use Windows NT security, such as certain node
managers, can be used freely by any user. To avoid this, file permissions can be
used to stop unauthorised access to the program.

3.7.2 Security in the System Frame

NMS/10 System Frame makes use of general Windows NT security, as

established by user groups, user accounts, and access rights and permissions.

3.7.3 Agent security

Three aspects of security are employed by the agents and agent configuration
tools:
• Computer access security:
Agent servers use standard Windows NT security and NMS/10 user
groups to give users specific access rights to different functions according
to the user groups in which they belong.
• Web interface security:
The web-based agent configuration tools use access-control mechanisms
that rely on the web browser/server security arrangements.
• SNMP security:
Access to agents is restricted to specific IP addresses, trap destinations
are controlled by IP addresses, and an agent will reject all SNMP requests
that have an unauthorised community name.
For information on agent-specific security, refer to the User Manual of the
corresponding agent.

3.7.4 NMS/10 MF and node manager security

NMS/10 MF and node manager security is independent of NMS/10 System

Frame. Disabling the security for one does not affect the other.
For information on NMS/10 MF and node manager security, refer to the user
documentation of the corresponding product.

18 (50) © Nokia Networks Oy C33820002SE_A0

 Applications

4 Applications
NMS/10 System Release is the optimal solution to a wide range of different
management needs in various network environments, both with small to
medium sized networks as a stand-alone network management product, and
with larger networks as a sub-network management product in conjunction with
a higher-level management system. This chapter describes the most common of
these applications.
Typical applications that can use NMS/10 System Release include:
• NMS/10 System Release (including NMS/10 System Frame, HP
OpenView NNM, agents and node managers):
− As a stand-alone network management product for small and
medium sized networks
− As a sub-network management product, when used with a higher-
level management system.
− In conjunction with another (non-Nokia) management product.
• NMS/10 agent(s) alone:
− As a stand-alone network management product for very small
networks
− In conjunction with another Nokia management product.
− In conjunction with non-Nokia management product.

C33820002SE_A0 © Nokia Networks Oy 19 (50)

 Product Overview

4.1 NMS/10 in mobile networks

NMS/10 System Release products can be used together with NMS/2000 to
manage the cellular transmission part of mobile networks. The solution consists
of the following modules:
• NMS/10 Q3 Agent
• NMS/10 SDH Radio Agent
• NWI 1.1 software. This component is used by the NMS/2000 BAM/BAR
application for Q1configuration upload
• node managers.
All these components (excluding NEW-NMS) may coexist on a single
workstation. Node managers can be run on the agent PC, and the user interfaces
can be started to remote (NMS/2000) consoles using Windows NT TSE.
NMS/2000 receives SNMP traps directly from NMS/10 agents and store them
to the NMS/2000 database. By using single database, a full integration of
cellular and transmission network management is possible. Alarms from Q1-
managed network elements are received from BSC/BTS, and hence, no separate
mediation devices or agents are needed.

NMS/2000 user interface Agents,

Q1 node
Q3 node
NM UI mgrs, NWI
mgrs,
Alarms 1.1, NERA
Windows
(SNMP traps) NT TSE NEW-NMS,
Windows
NT TSE

Node manager
launch

Q1
alarms
BSC SDH radio

Synfonet
MSC
BTS

Figure 2. An example of using NMS/10 SR C5.0 products in cellular

environment

20 (50) © Nokia Networks Oy C33820002SE_A0

 Applications

4.2 Integration with third-party management systems

Agents can be used as mediators to integrate Nokia network elements to third
party management systems. In this case, any management system with an
SNMP interface can be used. To be able to interpret SNMP traps from Nokia
network elements, the management system must understand the format used by
Nokia agents. For this purpose the description of Nokia MIBs are included in
the NMS/10 SR C5.0 CD-R Media and in the corresponding agent user
manuals. However, some integration work is always required when a third-party
management system is used.
Node managers are usually also needed, although a third-party management
system is used, and in this case the agent PC can be used as a platform to run
the node managers.
In addition to a third-party management system, also Nokia management
systems can be used with same agents in the same network, if needed.

WWW

Q1 Q3

PDH Synfonet

Figure 3. An agent in a multi-vendor and stand-alone environment

C33820002SE_A0 © Nokia Networks Oy 21 (50)

 Product Overview

4.3 Stand-alone applications

In very small networks, agents can be even used as stand-alone management
systems if the agent’s current alarm view via a web interface is sufficient for
management purposes. This may be sufficient in very small networks,
especially when the price of the network management is very significant. If the
size of the network grows, Nokia network management system can be added to
the network afterwards (NMS/10 SR C5.0 or NMS/2000).

Figure 4. Current alarm view using the web interface of NMS/10 Q3

Agent.

22 (50) © Nokia Networks Oy C33820002SE_A0

 Applications

4.4 Managing nodes

This section describes the management of various nodes.

4.4.1 Managing Synfonet nodes

In NMS/10, Synfonet nodes are managed by NMS/10 Q3 Agent, as illustrated

by Figure 5.

Q3 Agent

Figure 5. NMS/10 Q3 Agent and Synfonet nodes

Synfonet equipment provides Synfonet STM–1/4, STM–16 and SAN nodes.

This equipment provides a flexible way to build transmission and access
networks.

C33820002SE_A0 © Nokia Networks Oy 23 (50)

 Product Overview

Synfonet nodes can be accessed by using a gateway node on the LAN/WAN.

There is a limit to the number of nodes that can be accessed through a gateway
node, before the nodes must be separated into further groups, each accessed
through another gateway node. The limit is dependent upon the LAN/WAN
traffic load.

Capacity
One NMS/10 System Frame can contain up to three NMS/10 Q3 Agents. One
NMS/10 Q3 Agent can manage up to 100 Synfonet nodes.
It is recommended that NMS/10 Q3 Agent is installed in a workstation separate
from NMS/10 System Frame if the System Frame is also managing other
agents.

Protocols and communications

Synfonet nodes communicate by using OSI across a LAN/WAN connection.

Further details
For details on the NMS/10 Q3 Agent software, see NMS/10 Q3 Agent User
Manual.

4.4.2 Managing Q1-managed nodes

In NMS/10, Q1 nodes are managed by NMS/10 MF. MF Agent is pre-installed

on a separate, rack-mounted industrial PC known as a NMS/10 MF C2.0 (see
Figure 6).

24 (50) © Nokia Networks Oy C33820002SE_A0

 Applications

NMS/10 MF C2.0
(with MF Agent)

Figure 6. Q1-managed nodes connected to the computer by using an

NMS/10 MF

Capacity
One NMS/10 MF can manage up to 3000 Q1-managed node FEs.
NMS/10 can accommodate up to three fully populated NMS/10 MFs (that is,
with a maximum of 3000 FEs each) to a limit of 5000 Q1-managed NEs.

Note
Usually one Q1-managed node contains one FE, but there are some exceptions,
such as ACM2 and Nokia Q1 managed equipment (Supervisory Substation,
FIU 19, FlexiHopper, MetroHopper, and MetroHub).

Protocols and communications

A V.11 serial connection is required between the Q1-managed nodes and the
NMS/10 MF. IP connectivity is required between the NMS/10 System Frame
PC and NMS/10 MF.
Q1-managed nodes are connected together by using a management bus cable.
Q1 management information can also be carried on an inband management

C33820002SE_A0 © Nokia Networks Oy 25 (50)

 Product Overview

channel. Each node has a unique address. The bus cable is a V.11 serial
connection that is connected the appropriate interface card in an NMS/10 MF.
An NMS/10 MF supports up to 16 buses. A bus supports up to 200 FEs.

Further details
For details on NMS/10 MF, see the NMS/10 MF Operating Manual.

4.4.3 Managing SDH radios

In NMS/10, SDH radios are managed by NMS/10 SDH Radio Agent, as

illustrated by a simplified diagram in Figure 7.
NMS/10 SDH Radio Agent collects alarms from the SDH radios through NEW-
NMS.
This node type provides a standard optical SDH interface for STM–1 on the line
side, and an air interface on the (RF) radio side. This way, the transmission
expansion for SDH can be realised with minimum rollout time as compared
with fibre installations.

Capacity
SDH radios are managed by NMS/10 SDH Radio Agent through NEW-NMS.
One NMS/10 System Frame can accommodate one SDH Radio Agent, and one
SDH Radio Agent can manage one NEW-NMS including no more than 100
SDH radios.

DCN considerations
A direct V.24/V.28 serial interface or a LAN/WAN connection is required for
gateway SDH radio equipment to communicate with the computer on which the
NEW-NMS runs.

Further details
For details on NMS/10 SDH Radio Agent, see the NMS/10 SDH Radio Agent
User Manual. For details on NEW-NMS, see the NEW-NMS User Manual.

26 (50) © Nokia Networks Oy C33820002SE_A0

 Applications

Q3 Agent

Node managers Node managers

(excluding NEW-NMS) (excluding NEW-NMS)

Figure 7. NMS/10 SDH Radio Agent and SDH radios

C33820002SE_A0 © Nokia Networks Oy 27 (50)

 Product Overview

5 NMS/10 System Frame user interface

This chapter introduces the user interface and main features of NMS/10 System
Frame. It covers the following topics:
• Introduction (section 5.1)
• Network maps (section 5.2)
• Alarms and events (section 5.3)
• Running node managers (section 5.4).

5.1 Introduction
NMS/10 System Frame provides a user interface based on the underlying HP
OpenView NNM functionality, with additions to represent NMS/10 features
and related functions.
The NMS/10 System Frame user interface allows the user to visualise the
telecommunications network and also launch appropriate applications,
depending on the equipment being viewed. In the user interface, the network is
represented as a hierarchy of submaps that show the network status in real time.
Different colours indicate the fault and management states of each node.
Alarms and other events can be viewed in various lists. The main list is for
current alarms, that is, those for which the cause is not yet resolved. In each
case, the user can select the list to show alarms or events from the objects in
which they are interested.

28 (50) © Nokia Networks Oy C33820002SE_A0

 NMS/10 System Frame user interface

5.2 Network maps

5.2.1 Maps

A map is a collection of submaps. When you open a map, the home submap
appears.

5.2.2 Submaps

A submap is a window displayed by HP OpenView NNM that contains

symbols. By the use of explodable symbols, a hierarchy of submaps can be
created. The root submap represents the top of the hierarchy. The home submap
represents the submap that you want to see first when you open a map. By
default, the home submap is the root submap unless you change this. Figure 8
shows a tree structure that represents part of a submap hierarchy within a map.
The shading of the symbols in the diagram is significant in that it indicates fault
state propagation, using the recommended configuration.

5.2.3 Symbols

A symbol is an icon that represents an object, such as a node or an agent. There

are two types of symbol:
• One that is used to represent a submap (explodable)
• One that is used to launch a program (executable).

HP OpenView NNM symbol functions

The appearance of a symbol depends on its type (explodable or executable), the
fault state of the underlying object (if any), and whether or not it has been
selected.
Figure 9 shows the appearance of an explodable symbol, an executable symbol,
a selected symbol, and a copied symbol.
Each symbol has a label, which is a text name that identifies the symbol. The
label text is added when the symbol is created, and does not have to be the same
as the name of the underlying object.
The commands available to you depend on whether or not a symbol is selected
and by the object that the symbol represents. Click a symbol with the right
mouse button to view a menu that presents commands related to the symbol and
the object (that is, the menu is context-sensitive).

C33820002SE_A0 © Nokia Networks Oy 29 (50)

 Product Overview

Figure 8. Part of a submap hierarchy, showing fault state propagation

30 (50) © Nokia Networks Oy C33820002SE_A0

 NMS/10 System Frame user interface

Figure 9. Symbols: explodable, executable, selected, and copied

5.3 Alarms and events

NMS/10 System Frame receives events from objects in the NMS/10 network
that are being managed by agents. HP OpenView NNM and NMS/10 System
Frame also produce events themselves, concerning internal errors.
Some of these events represent alarms. An alarm is a report about a fault
identified in a managed object.
All events are stored by the System Frame. These events include reports of the
change of state of other events, such as alarms.

C33820002SE_A0 © Nokia Networks Oy 31 (50)

 Product Overview

Alarms can be viewed and managed by using the System Frame’s current
alarms list (Figure 10). Events can be viewed and managed by using the System
Frame’s historical events list. Events can also be viewed and managed by using
the HP OpenView NNM Alarms Browser.

Figure 10. A sample NMS/10 Current Alarms dialog box

5.4 Running node managers

The node managers used by NMS/10 are separate applications that can be
launched from NMS/10 System Frame. The purpose of a node manager is to
configure a node.
The different node managers supported by NMS/10 System Frame are listed in
section 6.4.4, 'Supported node managers'.

5.4.1 Synfonet node managers

When the user launches a Synfonet node manager, NMS/10 System Frame
passes the address of the node to the node manager. The node manager then
attempts to connect with the specified node.

32 (50) © Nokia Networks Oy C33820002SE_A0

 NMS/10 System Frame user interface

5.4.2 Q1 node managers

For Q1-managed nodes, the access to the node is routed via NMS/10 MF. When
the user launches a Q1 node manager, NMS/10 System Frame passes the name
of the node via GCS to the node manager. The node manager then attempts to
connect with the specified node.
The node manager receives the access information that it requires from its
database. This information allows it to access NMS/10 MF and to inform them
of the address of the target node.

5.4.3 SDH radio equipment node managers

When the user launches a NERA NEW-NMS, NMS/10 System Frame passes
the address of the node to the node manager. The node manager then attempts to
connect with the specified node.

C33820002SE_A0 © Nokia Networks Oy 33 (50)

 Product Overview

6 NMS/10 SR products
This chapter lists the sales items within NMS/10 SR C5.0, and gives software
version compatibility information. It covers the following topics:
• Sales items (section 6.1)
• Product codes (section 6.2)
• Document product codes (section 6.3)
• Compatibility information (section 6.4).

6.1 Sales items

There are three types of sales item that relate to the NMS/10 SR C5.0 release:
media, software licences, and printed documentation. The media must always
be ordered separately in addition to purchasing the licence(s).

6.1.1 Media

The NMS/10 SR C5.0 CD-R Media contains the following products and
utilities:
• NMS/10 System Frame software
• Recommended patches for HP OpenView NNM 6.1
• NMS/10 Q3 Agent software
• NMS/10 SDH Radio Agent software
• NERA NEW-NMS software
• SNMP for NEW-NMS software
• NMS/10 MF Agent software
• MF Manager software

34 (50) © Nokia Networks Oy C33820002SE_A0

 NMS/10 SR products

• NWI 1.1 software

• General Communication Service (GCS) software
• NMS/10 Command Scripting (RCM) software
• user documentation
• Adobe Acrobat Reader for reading user documentation.
No permanent licences to use the software are included. However, a trial period
of 30 days is allowed. When the trial period expires, the software can no longer
be used without a permanent licence.

6.1.2 Software licences

A software licence must be obtained for permanent use. The licences can be
ordered either when purchasing the CD-R Media, or after the evaluation of the
software.
There are separate licences for NMS/10 System Frame, and Agent products, as
specified in section 6.2, ’Product codes’.
HP OpenView NNM licensing is based on Hewlett-Packard’s licensing.

6.1.3 Printed documentation

All user documentation is included in the CD-R Media in electronic format.

Paper copies can be ordered separately. Refer to section 6.3, ’Document product
codes’ for the order codes.

6.2 Product codes

6.2.1 CD-R Media

Table 1. Product codes for CD-R Media

Product Product code

NMS/10 SR C5.0 CD-R Media P31755.01

C33820002SE_A0 © Nokia Networks Oy 35 (50)

 Product Overview

6.2.2 HP OpenView NNM products and licences

Table 2. Product codes for HP OpenView NNM

Product Product code

HP OpenView Network Node Manager 250 6.1 (NT) S35500.01
HP OpenView Network Node Manager Enterprise 6.1 (NT) S35500.02

6.2.3 NMS/10 System Frame licences

Table 3. Product codes for NMS/10 System Frame

Product Product code

NMS/10 System Frame C5.0 for 1 system P31159.01
NMS/10 System Frame C5.0 for 5 systems P31159.02
NMS/10 System Frame C5.0 for 10 systems P31159.03
NMS/10 System Frame C5.0 upgrade for 1 system P31159.51
NMS/10 System Frame C5.0 upgrade for 5 systems P31159.52
NMS/10 System Frame C5.0 upgrade for 10 systems P31159.53

6.2.4 NMS/10 Q3 Agent licences

NMS/10 Q3 Agent is required for collecting alarms from Synfonet nodes for
display by NMS/10 System Frame.

Table 4. Product codes for NMS/10 Q3 Agent

Product Product code

NMS/10 Q3 Agent C1.0 for 1 system P31690.01
NMS/10 Q3 Agent C1.0 for 5 systems P31690.02
NMS/10 Q3 Agent C1.0 for 10 systems P31690.03
NMS/10 Q3 Agent C1.0 upgrade for 1 system P31690.51

36 (50) © Nokia Networks Oy C33820002SE_A0

 NMS/10 SR products

Product Product code

NMS/10 Q3 Agent C1.0 upgrade for 5 systems P31690.52
NMS/10 Q3 Agent C1.0 upgrade for 10 systems P31690.53

6.2.5 NMS/10 SDH Radio Agent licences

NMS/10 SDH Radio Agent is required for collecting alarms from SDH radios
for display by NMS/10 System Frame. Note that NERA NEW-NMS is needed
with NMS/10 SDH Radio Agent.

Table 5. Product codes for NMS/10 SDH Radio Agent

Product Product code

NMS/10 SDH Radio Agent C1.0 for 1 system P31756.01
NMS/10 SDH Radio Agent C1.0 for 5 systems P31756.02
NMS/10 SDH Radio Agent C1.0 for 10 systems P31756.03
NMS/10 SDH Radio Agent C1.0 upgrade for 1 system P31756.51
NMS/10 SDH Radio Agent C1.0 upgrade for 5 systems P31756.52
NMS/10 SDH Radio Agent C1.0 upgrade for 10 systems P31756.53

6.2.6 NMS/10 MF

Table 6. Product codes for NMS/10 MF

Product Product code

NMS/10 MF Hardware C1.0 release B T31090.22
(includes one Polling card and two Q1 Interface cards)
NMS/10 MF Hardware upgrade from release A T31090.51
(includes a memory upgrade to 128 MB and a CD-ROM
drive)
NMS/10 MF Agent C2.0 and a licence for 1 MF P31758.01
NMS/10 MF Agent C2.0 upgrade for 1 MF P31758.51

C33820002SE_A0 © Nokia Networks Oy 37 (50)

 Product Overview

6.2.7 MF Manager licences

MF Manager is required for configuring NMS/10 MF C2.0.

Table 7. Product codes for MF Manager

Product Product code

MF Manager C2.5 for 1 system P31757.01
MF Manager C2.5 for 5 systems P31757.02
MF Manager C2.5 for 10 systems P31757.03
MF Manager C2.5 upgrade for 1 system P31757.51
MF Manager C2.5 upgrade for 5 systems P31757.52
MF Manager C2.5 upgrade for 10 systems P31757.53

6.3 Document product codes

Tables 8 to 10 contain the titles of the documents related to NMS/10 and the
product codes that are needed when ordering them. To order the documents,
contact your Nokia sales representative.

Table 8. Documentation for NMS/10 System Frame

Document title Product code

NMS/10 SR C5.0 Product Overview C33820.20
NMS/10 SR C5.0 User Manual C33820.21

Table 9. Documentation for agents

Document title Product code

NMS/10 Q3 Agent C1.0 User Manual C33803.20
NMS/10 SDH Radio Agent C1.0 User Manual C33804.20

Table 10. Other documentation relating to NMS/10

Document title Product code

NMS/10 MF C2.0 Operating Manual C33846.21

38 (50) © Nokia Networks Oy C33820002SE_A0

 NMS/10 SR products

Document title Product code

MF Manager C2.5 User’s Manual C33846.22
NMS/10 MF Agent C2.0, Agent Configuration Tool User C33846.23
Manual
NERA Network Element Workstation R4B User’s Manual T38344.04
GCS R4.1 User Manual C33596.21
RCM C1.0 User Manual C33596.22

In addition to these listed documents, on-line help is provided with each

NMS/10 System Release product, which includes a graphical user interface.

6.4 Compatibility information

This section lists Nokia’s network management products and their releases
compatible with NMS/10 SR C5.0.

6.4.1 Supported Synfonet node types

NMS/10 Q3 Agent C1.0 is compatible with the following Synfonet nodes:

Node Release
Synfonet STM-1/4 C2.21, C3.30, C3.40, C3.50
Synfonet STM-16 C1.0, C1.5, C2.0
Synfonet Access Node (SAN) C1.0, C1.5, C2.0

6.4.2 Supported Nokia SDH radios

NMS/10 SDH Radio Agent C1.0 is compatible with the following SDH radios:
• Nokia PowerHopper
• NERA CityLink
• NERA NL29x.

6.4.3 Supported Q1 network element management systems

• MF Manager C2.5

C33820002SE_A0 © Nokia Networks Oy 39 (50)

 Product Overview

• NMS/10 MF C2.0.

6.4.4 Supported node managers

Table 11. NMS/10 SR C5.0 compatibility with node managers

Product Release
ACL2 Manager C3.0
ACM2 Manager C4.0
ACM2 V5 Manager C3.2
DB 2 Manager C4.0
DM 2 Manager C1.0
DMF Manager C2.0
DMR Manager C3.0
DN 2 Manager C5.1 release B
DNT128 Manager C3.0
DNT1M Manager C3.0
DNT2M Manager C3.0
Hopper Manager C3.1
ILT1M Manager C3.0
ILTn64 Manager C3.0
Macro STE C4.1
NERA NEW-NMS R4B00
with SNMP for NERA NEW-NMS R1A02
SAN Manager C2.0
STM-16 Manager C2.0
Synfonet Node Manager C3.60
TruMan C7.0

Additional node managers and their new versions can be validated for this
NMS/10 release later on. Future releases of the above Nokia products will be
supported by later releases of NMS/10.

40 (50) © Nokia Networks Oy C33820002SE_A0

 System requirements

7 System requirements
This chapter describes the requirements of the system in which NMS/10 System
Frame and other NMS/10 System Release products are installed.

7.1 General
This section lists the general requirements for the operating systems and
computers used in the NMS/10 SR system (NMS/10 System Frame PC,
separate agent PC, and remote node manager PC).

Software
• Microsoft Windows NT Workstation version 4.0 with Service Pack 6a (or
later). Only the international Windows NT 4.0 version is supported
For remote management:
Microsoft Windows NT Server 4.0, Terminal Server Edition with Service
Pack 5 (or later) on the remote computer and Windows NT TSE Client on
the NMS/10 System Frame computer for launching node managers
• HP OpenView Network Node Manager 250 version 6.1 for Windows NT,
or HP OpenView Network Node Manager Enterprise version 6.1 for
Windows NT
• Windows NT 4.0 Option Pack
• Microsoft SNMP Service
• Microsoft Data Access Components version 2.1
• Internet Explorer 5 or later.

Hardware
• Personal computer with a Pentium compatible processor
• Minimum of 128 megabytes (MB) of RAM. The following equipment
combinations require at least 256 MB:

C33820002SE_A0 © Nokia Networks Oy 41 (50)

 Product Overview

− Q3 (Synfonet) networks with many different node versions

− Q3 (Synfonet) networks with SDH radios
− PDH networks with Q3 (Synfonet) nodes
− PDH networks with Q3 (Synfonet) nodes and SDH radios
• NTFS-formatted hard disk
• 1 gigabyte (GB) of free hard disk space is recommended
• CD-ROM drive and high-density 3.5" disk drive for software installation
• VGA-compatible or better graphical colour display. A 17" or larger
monitor is recommended
• Mouse or equivalent pointing device with driver software and mouse port
• Printer accessible from Windows NT if the contents of the windows are
to be printed
• Dedicated serial port if alarm information is to be spooled to a printer or
exported to another system
• Connection to an SMTP-compliant server if alarm information is to be
sent via e-mail.

7.2 Product-specific requirements

7.2.1 NMS/10 System Frame PC

• Windows NT Workstation 4.0 supported (Windows NT Server 4.0, TSE

is NOT supported)
• requires HP OpenView NNM for Windows NT
• requires a TSE client when node managers are used from remote
computer.

7.2.2 NMS/10 Remote Station

• Windows NT Workstation 4.0 supported (Windows NT Server 4.0, TSE

is NOT supported)
• requires HP OpenView NNM for Windows NT Remote Console
• requires NMS/10 System Frame C5.0
• requires a TSE client when node managers are used from remote
computer.

42 (50) © Nokia Networks Oy C33820002SE_A0

 System requirements

7.2.3 NMS/10 Remote Console

• Windows NT Workstation 4.0 supported

• requires HP OpenView NNM for Windows NT Remote Console.

7.2.4 NMS/10 Q3 Agent

• Windows NT Workstation 4.0 supported

• Windows NT Server 4.0, TSE supported
• can be installed in the same PC with NMS/10 SDH Radio Agent
• can be installed in the same PC with NMS/10 System Frame only if the
System Frame does not manage other agents.

7.2.5 NMS/10 SDH Radio Agent

• Windows NT Workstation 4.0 supported

• Windows NT Server 4.0, TSE supported
• can be installed in the same PC with NMS/10 Q3 Agent
• can NOT be installed in the same PC with NMS/10 System Frame
• can NOT be installed in the same PC with NERA NEW-NMS.

7.2.6 NERA NEW-NMS

• Windows NT Workstation 4.0 supported

• Windows NT Server 4.0, TSE supported
• can NOT be installed in the same PC with NMS/10 System Frame
• can NOT be installed in the same PC with NMS/10 SDH Radio Agent
• can NOT be installed in the same PC with NMS/10 Q3 Agent.

7.2.7 NMS/10 MF C2.0

• Windows NT Workstation 4.0 supported

• runs on an industrial PC.

C33820002SE_A0 © Nokia Networks Oy 43 (50)

 Product Overview

7.3 Integration with network-level Nokia NMS

If NMS/10 is to be integrated with a network-level Nokia NMS (NMS/2000,
NMS/400, or NMS for IP), Microsoft Windows NT Server 4.0, Terminal Server
Edition and add-in software are required instead of the Windows NT
Workstation 4.0. In this case the system and especially memory requirements
are higher, and depend also on the number of simultaneous client sessions.
Moreover, the needed NMS/10 products depend on the selected network-level
NMS as well as the number of users simultaneously running node manager
applications.

7.4 Network connection and alarm monitoring

This section lists the hardware and software products needed when connecting
the NMS/10 System Frame workstation to the various managed networks.

7.4.1 Q3 managed nodes (Synfonet)

• An NDIS-compliant Ethernet network adapter for communicating with

Synfonet nodes and web browsers.
Also, LAN software is needed to use the Ethernet connection. An NDIS
driver is supplied with all Ethernet network cards.
• An installed and configured TCP/IP stack (provided with the operating
system) for communicating with Q3 managed nodes.

7.4.2 NMS/10 MF

• An installed and configured TCP/IP stack (provided with the operating

system) for communicating with NMS/10 MF.

7.4.3 SDH radios

• NERA NEW-NMS with a licensed HW Key and an SNMP option.

• An installed and configured TCP/IP stack (provided with the operating
system) for communicating with NERA NEW-NMS, and between NERA
NEW-NMS and SDH radio nodes.
For serial port connection:
• A serial port cable connected to the first node.

44 (50) © Nokia Networks Oy C33820002SE_A0

 System requirements

Glossary

Terms

Administrator user In the System Frame, the administrator user performs all installation tasks and,
in addition to all of the tasks of a standard user, creates and manages maps.
Agent In NMS/10, a software program or system that manages the operation of a
particular collection of nodes (and other objects). Alarms generated by these
objects are propagated to the System Frame by agents. Agents can be
configured to control the objects that are to be managed.
Alarm An event, generated by a node (or other object), that represents a fault or other
occurrence that may adversely affect the performance of the network.
Area A logical grouping of Synfonet nodes. Each node is contained within a single,
specific area.
Bus A physical grouping of Q1-managed nodes. Each node is attached to a single,
specific bus.
Child (object) In HP OpenView NNM submaps, any NMS/10 object that is contained within
another object, such as a node within an area, bus, station, or section, and a
section within a NEW-NMS. See also Parent (object).
CityLink A NERA SDH radio product.
Colour In NMS/10, fault states and management states are represented by particular
colours. If an object is managed, it has a fault state and takes the associated
colour. If an object is not managed, it does not have a fault state and takes the
colour for unmanaged.
Computer In this guide, a personal computer running Windows NT Workstation, Windows
NT Workstation (Terminal Server Edition) or Windows NT Server.
Container A logical or physical grouping of objects (nodes and other containers) within an
NMS/10 network. The System Frame records details of all relevant containers:
area, bus and station, NEW-NMS and section. The default explodable symbol
for an agent in HP OpenView NNM, which (when double-clicked) provides a
submap, is not itself a container. See also Parent (object).
Domain A collection of Windows NT computers, and other devices and facilities.
Event Messages from objects in an NMS/10 network that are being managed by
agents. Alarms are events.
Fault state In NMS/10, an object always has a fault state associated with it, even when
there is no fault. An alarm associated with an object is classified by using the
appropriate fault state.
A colour is associated with each of these fault states.
HP OpenView NNM HP OpenView Network Node Manager for Windows NT. A software program,
created and maintained by Hewlett-Packard, that allows the graphical display of
objects and controls their management. See also map and submap.

C33820002SE_A0 © Nokia Networks Oy 45 (50)

 Product Overview

Icon A term used in graphical user interfaces (GUIs). An image on a display that
represents an object that has properties or contents, or that can be executed as a
program. For example, Windows icons for folders and programs, and symbols
in HP OpenView NNM.
Loss of connection A state that occurs when one part of the managed network loses communication
with another. For example, between the System Frame and an agent, or between
an agent and a node, or between a bus and a node.
Managed The state of an object when alarms are being collected for it by an agent for the
System Frame. See also unmanaged.
Managed object A node or other device that is known to the System Frame and that is managed.
See also object and unmanaged object.
Management state An object in the System Frame has a management state associated with it: it is
either managed or not managed (unmanaged). A colour is used to represent the
management state. The term fault-management state is synonymous.
Map Provides a graphical representation of a network by displaying the available
objects and their connections as symbols, and by using colour to indicate the
most severe alarm amongst all of the associated nodes and other managed
objects. A map consists of one or more submaps in a hierarchical relationship.
When a map is opened, the home submap is what is seen first.
Network element A node.
Network map See map.
NEW-NMS The NERA Element vieWer — Network Management System is a program that
acts as an agent and node manager for NERA SDH radios and sections. SDH
Radio Agents use NEW-NMSs to manage SDH radios and sections.
NL29x A NERA SDH radio product.
NMS/10 MF A rack-mounted industrial PC, including pre-installed software, that is used to
provide access and communications to and from Q1-managed nodes.
Node manager A program that understands the specific details of a particular type or family of
nodes and supports the configuration and maintenance of these nodes.
Node A managed object that provides transmission services.
NTFS New Technology File System: a protected file system that can be run in
combination with the Microsoft Windows NT operating system. You must use
NTFS to ensure that your files are protected.
Object A node or other object that is known to the System Frame, but is not necessarily
managed by it. See also managed object.
In NMS/10, objects include nodes and containers, that is, buses and stations
(Q1-managed nodes), areas (Synfonet), NEW-NMSs and sections (SDH radios).
OpenView See HP OpenView NNM.
Parent (object) In HP OpenView NNM submaps, an NMS/10 object that contains nodes (that is,
an area, bus, station, or section); also a NEW-NMS that contains sections. Used
in preference to Container. See also Child (object).

46 (50) © Nokia Networks Oy C33820002SE_A0

 System requirements

Program file A file that represents a software program and can thus be executed by a
computer’s operating system.
Propagation The communication of an event up the management hierarchy of a network.
The indication on the symbol of a parent object of the most severe fault state
amongst the objects in a branch of an HP OpenView NNM submap hierarchy.
Q1
Q1-managed node PDH/Primary Rate Equipment nodes, buses and stations, and Nokia Q1-
managed equipment, for example, FIU 19, MetroHopper, FlexiHopper,
MetroHub.
Q3 A standard management protocol for Synfonet nodes.
Q3 Agent A program that manages Synfonet nodes.
Remote node manager computer
A computer, running Windows NT TSE, that allows node managers to be run
remotely.
SDH radio In NMS/10, a node in an SDH radio network.
SDH Radio Agent A program that manages SDH radios and containers (NEW-NMSs and sections).
Section A logical grouping of SDH radios, as used by a NEW-NMS. Each SDH radio is
contained within a single, specific section.
Station A logical grouping of Q1-managed nodes. Each node is contained within a
single, specific station. See also bus.
Station is also used by NERA to indicate an SDH radio.
Submap A map that represents a level of detail in a network hierarchy displayed by the
System Frame. A submap contains symbols that represent either further levels
of detail (that is, further submaps) or nodes.
Symbol In HP OpenView NNM, an icon on a submap that represents an object.
Synfonet Nokia’s family of Synchronous Digital Hierarchy (SDH) transmission
equipment.
Unmanaged The state of an object when alarms are not being collected for it by an agent for
the System Frame. See also managed.
Unmanaged object A node or other device that is known to the System Frame, but that is
unmanaged. See also object and managed object.
Windows NT TSE In this guide, Windows NT Server 4.0, Terminal Server Edition.

C33820002SE_A0 © Nokia Networks Oy 47 (50)

 Product Overview

Abbreviations

AFI Authority and Format Identifier (part of a Q3 protocol NSAP address).

DCN Data Communications Network.
DHCP Dynamic Host Configuration Protocol (an HP OpenView NNM installation
option).
DNS Domain Name Server.
ECC Embedded Control Channel (Synfonet network communications).
FE Functional Entity (part of a Q1-managed node address).
GB Gigabyte.
GCS General Communication Service (utility).
IDI Initial Domain Identifier (part of a Q3 protocol NSAP address).
IP Internet Protocol (see also TCP/IP).
IPX (A Novell NetWare protocol).
ITU-T International Telecommunications Union — Telecommunications
standardisation sector (sic).
LAN Local Area Network.
LOC Loss of connection.
MB Megabyte.
MF Mediation Function (see also NMS/10 MF).
MHz Megahertz.
MIB Management Information Base.
NEW-NMS NERA Element vieWer — Network Management System.
NMS/10 Network Management System/10 (one of Nokia’s family of network
management products).
NMS/10 MF MF used specifically for NMS/10 (using a rack-mounted computer and
appropriate software).
NSAP Network Service Access Point (part of a Q3 protocol address).
NSEL Network Selector (part of a Q3 protocol address).
NTFS New Technology File System.
NWF Network File (used in NMS/10 SR C4.x).
PDH Plesiochronous Digital Hierarchy.
PRE Primary Rate Equipment.
Q1 Nokia’s proprietary management protocol.

48 (50) © Nokia Networks Oy C33820002SE_A0

 System requirements

Q3 Management interface (ITU–T).

RAM Random Access Memory.
RCM Remote Control and Measurement (utility).
RF Radio Frequency.
SAN Synfonet Access Node.
SDH Synchronous Digital Hierarchy.
SMTP Simple Mail Transfer Protocol.
SNMP Simple Network Management Protocol.
SR System Release.
TCP/IP Transmission Control Protocol/Internet Protocol.
TSE Terminal Server Edition (from Windows NT Server 4.0, Terminal Server
Edition).

C33820002SE_A0 © Nokia Networks Oy 49 (50)

 Product Overview

50 (50) © Nokia Networks Oy C33820002SE_A0