NEW Manual Radio Nera

User Manual
NEW-NMS R8
Nera Element vieWer
B1091
Rev. L
Section I
: Basics
Section II
: Software Setup
Section III
: Using NEW
Section IV
: Fault Management
Section V
: Configuration Management
Section VI
: Performance Management
Section VII
: Security Management
Section VIII
: Database
Section IX
: Appendices
This page is intentionally left blank.

2
B1091 Rev. L
List of Revisions
Rev.
Date
What is changed
99-01-27
New Section VII; SNMP
99-06-14
Section VI, Chapter 2.4; Map tutorial added (2.4.2)

Section XII, new Chapter 6.0; RF Statistics.
00-11-27
Section III: New Chapter 5.0 Equipment Compability.

Chapter 2.0 Hardware Requirements updated.
Section IV: 1.0 Software Installation changed. New
subchapters: 1.2 Client/Server and 1.3 Database.
Section VII: SNMP. The content of this Section has
been totally changed.
Section XI, Modem Port described in Chapter 1.1.
Section XII: Some new bitmaps, removed all "CityLink
only" contents.
Section XIII: Some new bitmaps, removed all "CityLink
only" contents
Section XIV: Alarmlists for NL18x, NL24x & NL29x
included. Alarmlist for CityLink updated. Modem
installation & configuration included.
01-04-23
Section XI: Chapter 1.0; changed bitmap and description

Subchapter 1.1.3; New bitmaps and description.
Subchapter 1.3: Additional text regarding CompactLink.
New subchapter: 1.4 Subnetworks Dialog.
New Chapter: 3.0 SNMP Settings.
Section XIV: New Appendix E; CompactLink Alarms
New Appendix C; Configuration of CompactLink
01-08-23
Section XI: Chapter 1.3; Description changed.

Chapter 3.0 totally revised.
Section XII: Chapter 3.2; changed bitmap and
description.
Section XIV: Appendix B; NL29x alarm list changed
Appendix B; New "NEClock" bitmap
New Appendix C; Totally revised with many new
subchapters
B1091 Rev. L
Rev.
Date
What is changed
01-09-11
Section IV: Chapter 1.3.1.3 and 1.3.2 changed.
03-01-17
Major restructuring of the manual
Not used
04-06-30
Changes in Section I & II due to new version of NEW-NMS.
05-04-07
Section II: Fig. II-14 changed

As from NEW-NMS R8A00, MS Access is no longer
supported. This leads to changes in Section II and VIII.
05-11-09
Section I: Chapter 3.1; Change in Hardware

Requirements
Section II: Chapters 1.0, 2.1.2, 3.2, 3,3 and 3.4.2.1
changed
Section VIII: References to MS Access removed.
B1091 Rev. L
Table of Contents
SECTION I, Basics ............................................... 11
1.0
Introduction ..................................................................
1.1
General ............................................................
1.2
Key Features ...................................................
1.3
Versions ...........................................................
1.3.1
NEW-NMS .......................................................
1.3.2
NEW-Configurator ...........................................
13
13
14
14
14
15
2.0
Nera Management Networks ......................................

2.1
Network Element (NE) .....................................
2.2
Section ............................................................
2.3
Nera Management Network .............................
2.4
Nera Element vieW ..........................................
2.4.1
Communication Principals ................................
15
15
15
16
16
16
3.0
Hardware Overview ....................................................

3.1
Hardware Requirements ..................................
3.2
Hardware Program Key ...................................
3.3
Network Element Connections .........................
3.4
Equipment Compatibility...................................
17
18
18
19
20
4.0
Database Requirements ............................................. 20

4.1
Database Hardware Requirements Factors ..... 20
4.2
Database Hardware Requirements .................. 21
SECTION II, Software Setup................................. 23

1.0
Software Installation ................................................... 25
2.0
Database ......................................................................
2.1
Create NEW-NMS Database ...........................
2.1.1
MS SQL Server ...............................................
2.1.2
Oracle .............................................................
B1091 Rev. L
26
26
26
27
5
2.2
2.2.1
2.2.2
3.0
Data Link Properties ........................................ 28

Connection Tab (MS SQL Server) .................. 29
Connection Tab (Oracle) ................................. 31
Client/Server ...............................................................
3.1
Client/Server Access Configuration ................
3.2
Client/Server Requirements ............................
3.3
User Administration .........................................
3.4
DCOM Configuration .......................................
3.4.1
Windows 2000 DCOM Configuration ..............
3.4.2
Windows XP/Windows 2003 Server DCOM
Configuration ...................................................
3.5
Server Login ....................................................
3.6
Client Login ......................................................
33
33
34
34
35
35
39
46
46
SECTION III, Using NEW..................................... 47

1.0
Getting Started ........................................................... 49

1.1
Logon .............................................................. 49
1.2
Discovering Network Elements ....................... 49
2.0
Program Environment ................................................ 51

2.1
Menus .............................................................. 51
2.2
Toolbar ............................................................ 52
2.3
Explorer View .................................................. 54
2.4
The Map View (Only available in NEW-NMS) .... 56
2.4.1
Map Management (Only available in NEW-NMS) 58
2.4.2
Tutorial ............................................................ 59
2.5
Alarm View ...................................................... 63
2.6
Logs ................................................................ 63
2.7
Context Sensitive Help .................................... 64
B1091 Rev. L
SECTION IV, Fault Management ....................... 65

1.0
General ........................................................................ 67
2.0
Information Acquisition .............................................. 67

2.1
Polling .............................................................. 67
2.2
Event Notification ............................................. 67
3.0
Alarms ........................................................................... 68
3.1
Severity Levels ................................................ 68
3.1.1
Changing the Alarm Severity Colors and Sounds68
3.2
Alarm Editing ................................................... 70
4.0
Visual Alarm Notification ............................................ 72

4.1
Alarms on a Tree Node/Leaf in the Explorer View72
4.2
Alarms on a Node Symbol in the Map View ..... 73
4.3
Viewing the Current Alarms ............................. 74
5.0
Logging Fault Events .................................................

5.1
Fault Log Manager ...........................................
5.2
The Fault Log View ..........................................
5.2.1
Select Visible Columns ...................................
5.3
Filtering ............................................................
75
75
76
80
81
SECTION V, Configuration Management ......... 83

1.0
B1091 Rev. L
Communication ...........................................................
1.1
Change Communication Media Settings .........
1.1.1
Serial Port ........................................................
1.1.2
Modem Port .....................................................
1.1.2.1 Modem Configuration ......................................
1.1.2.2 Modem Call Sequence ....................................
1.1.3
TCP/IP Port Settings .......................................
1.2
Element Communication Map .........................
1.3
Auto Discover ..................................................
1.4
Subnetworks Dialog ........................................
85
86
87
88
90
92
94
96
97
98
7
2.0
Network Element Configuration ................................ 99
3.0
SNMP Settings ............................................................ 101
SECTION VI, Performance Management ......... 105

1.0
General ........................................................................ 107
2.0
RF Statistics View ....................................................... 108
3.0
Logging Performance Events ...................................

3.1
Performance Log Manager ..............................
3.2
Viewing the Performance Log .........................
3.2.1
3.3
Performance Log Discriminator ......................
3.4
Filtering ............................................................
110
110
112
114
115
116
SECTION VII, Security Management ................ 119

1.0
General ........................................................................ 121
2.0
User Levels and Privileges ....................................... 121
3.0
Logon ........................................................................... 122

3.1
Logging into NEW-NMS,
Server and Stand-alone Versions .................... 122
3.2
Logging into NEW-NMS, Client Version ........... 124
4.0
User Administration ....................................................

4.1
Adding Users ...................................................
4.2
Editing Users ...................................................
4.3
Deleting Users .................................................
4.4
Changing Password ........................................
125
125
127
129
130
B1091 Rev. L
5.0
Logging Security Events ...........................................

5.1
Security Log Manager ......................................
5.2
Viewing the Security Log .................................
5.2.1
5.3
Filtering ............................................................
131
131
133
135
136
SECTION VIII, Database ..................................... 139

1.0
NEW-NMS Database Introduction .............................

1.1
General ............................................................
1.2
Supported Database Engines .........................
1.3
Database Size .................................................
1.4
When a Log is Full ...........................................
1.4.1
Wrap ...............................................................
1.4.2
Halt ..................................................................
1.5
Create Your Own Reports ...............................
141
141
141
142
143
144
144
145
2.0
Database Configuration .............................................

2.1
Configuration of NEW-NMS Database Systems
2.1.1
Configuring an SQL Server Database .............
2..2
Oracle Configuration/Maintenance Issues .......
2.3
Use NTFS File System ....................................
148
148
148
150
150
3.0
Backup and Restore of NEW-NMS Systems ............

3.1
General Backup and Restore Issues ..............
3.1.1
Why backup? ..................................................
3.1.2
Backup Interval ................................................
3.1.3
Backup Equipment ..........................................
3.1.4
Tape Rotation ..................................................
3.1.5
Backup Software .............................................
3.2
Restore of a NEW-NMS Database ..................
3.2.1
Backup and Restore of NEW-NMS Files .........
3.3
Backup and Restore of an MSDE Database ...
3.3.1
Backing up an MSDE Database ......................
3.3.2
Restoring an MSDE Database ........................
151
151
151
152
152
152
152
153
153
154
154
154
B1091 Rev. L
3.4
3.4.1
3.4.2
3.4.3
3.5
Backup and Restore of an SQL Server Database .

Backing up an SQL Server Database .............
Scheduled Backups ........................................
Restoring a SQL Server Database .................
Backup and Restore of an Oracle Database ..
155
155
156
156
157
SECTION IX, Appendices .................................. 159

Appendix A - Modem Installation and Configuration ............. 161
Appendix B - Configuration of NL29x, NL24x & NL18x ......... 165
Appendix C - Configuration of CompactLink ......................... 178
Appendix D- Configuration of CityLink, InterLink and Netlink 206
Appendix E - Abbreviations ..................................................... 207
10
B1091 Rev. L
Basics
SECTION I
Basics
B1091 Rev. L
11
NEW NMS
This page is intentionally left blank

12
B1091 Rev. L
Basics
1.0
1.1
Introduction
General
NEW-NMS is an abbriviation for NERA Element vieW-Network Management System and is a tool for performing network management functions
on a NERA Management Networks (NMN). The network management
functions NEW-NMS provides are configuration of the network elements
and monitoring of the network elements alarm and performance status.
NEW-NMS is an integral part of NERA network management and benefits
from the built-in management facilities of the NERA network elements.
NEW-NMS is a fully compliant 32-bits Windows application running on
PC with a minimum of Windows NT 4.0 operating system. If you have used
other Windows applications, the NEW-NMS graphical user interface will
be familiar to you. NEW-NMS has a graphical user interface and follows
a plug & play philosophy.
NEW-NMS communicates with the NMN via a serial port connection,
modem or via a TCP/IP connection to one or more Network Elements in the
NMN.
NEW-NMS provides different facilities to users depending on their user
privileges. Five different user levels gives an administrator possibilities to
limit the actions to be performed by the users.
NEW-NMS offers full range management of NERA network elements.
NEW-NMS has the ability to perform configuration-, fault-, performance- and security-management.
NEW-NMS is the user interface to all NERA transmission products. The
key issue for NEW-NMS is to present NERA management networks in the
simplest possible manner. The software has network auto-discovery and
uses the configuration data in the network elements to automatically build
a representation of the network. The various elements and their attributes
may be accessed using the intuitively graphical presentation of the element and its components. NEW-NMS has a continuously updated display
of network status and network events are reported from the elements using
notifications. NEW-NMS has extensive database and context sensitive
help facilities that enables the user to analyze and report network events.
NEW-NMS can act as a mediation device to higher order management
network systems in various ways. It has a Simple Network Management
Protocol (SNMP) interface that allows communication with management
platforms based on the Internet standards. It also has limited support for
Northbound "TMF CORBA".
B1091 Rev. L
13
NEW NMS
1.2
Key Features
NEW-NMS is designed to perform network management functions
NEW-NMS may be used for controlling one Network Element or
manage an entire network
Graphical user interface
Plug & play with network auto-discovery
Continuously updated display of network status
Data from various network elements displayed simultaneously
Full range management
Configuration
Fault
Performance
Security
Client/Server solution for enterprise wide access
Supports multi-vendor RDBMS (relation database management systems)
Extensive database and help facilities
Mediation device (SNMP, CORBA) for higher level management
systems
1.3
Versions
The NEW program is available in several versions and can either be used
as an element configuration manager (NEW-Configurator) or a network
manager (NEW-NMS).
A hardware key, connected to the PC parallel port, holds the license
information for the customer and differs between the element configurator
and the network manager. To upgrade your license, contact NERA and you
will receive information for upgrading your hardware key.
1.3.1
NEW-NMS
When a licensed hardware key is connected to the PC parallel port (when
the program is started), the program will behave as NEW-NMS with the
restrictions the customer license gives. NEW-NMS is a network manager
offering a full range of network management facilities.
The Standalone version lets the user start a NEW-NMS session and
monitor the connected network.
The Server version lets the user start a NEW-NMS session and monitor
the connected network. In addition, a license dependent number of concurrent client sessions are allowed to connect to the server. The clients will
then be able to monitor and configure the connected network in the same
way that it is done on the standalone version.
14
B1091 Rev. L
Basics
The Client version lets the user start a NEW-NMS session by starting the
client, connect and log-in on a remote NEW-NMS server via LAN (TCP/
IP).
1.3.2
NEW-Configurator
When the hardware key not is connected, the program will behave as NEWConfigurator. This is a program for network element configuration. NEWConfigurator only allows the user to monitor, and configurate, two network
elements at the same time. NEW-Configurator also have certain other
limitations in the functionality compared with NEW-NMS. There are no
logging facilities or map facilities.
2.0
2.1
Nera Management Networks

Network Element (NE)
A network is a collection of radios and/or optical line equipment. A radio or
an optical line equipment is the basic building block of the network and is
called the Network Element (NE). With an NE, it is possible to do fault-,
performance- and configuration-management. The fault management consists of alarm surveillance and testing. The equipment are of three types
termed as Terminal, Add/Drop repeater and Repeater.
2.2
Section
A Section is a combination of equipment that forms a switching section.
It is a relay with Terminals (add/drop repeaters) at both end and none or
more Repeaters in between. In a Section it is possible to perform protection switching functions. A Section transports data traffic. Sections may
be connected to form a larger network. A Section has also a Data
Communication Channel (DCC) to provide logical and management operations between the NEs. See Figure I-1.
Data Communication Channel (DCC)
Traffic
Terminal
Repeater
Repeater
Terminal
Figure I-1 Section

B1091 Rev. L
15
NEW NMS
2.3
Nera Management Network

Each NE in the network has the capability of gating network management
information through a Network Interface (NI). By connecting NIs in
different sections, it is possible to build a management network for one or
more networks.
All the NE functions for a particular NE are available to any other NE in
the management network, consequently network management may be
performed from any NE. In a management network the NE will have a
unique address consisting of a section and an element address. Enquiries
about an NE are routed in the management network using the DCC and NIs.
Figure I-2 shows a typical Nera Management Network.
Data Communication Channel (DCC)
Traffic
Network Interface (NI)
Terminal
Terminal
NI
Repeater
Terminal
NI
NI
NI
NI
Repeater
Terminal
Terminal
NI
Terminal
Figure I-2 Network Interface
2.4
Nera Element vieW

The Network Element vieW (NEW) is capable of issuing network management operations on the individual NEs and the complete Nera Management Network. NEW may be connected to any NEs in the management
network. The protocols used are Q1 (which is Nera proprietary) or SNMP.
2.4.1
Communication Principals
NEW communicates with the individual NEs in a question and answer
fashion. NEW sends a question in a message to the connected NE. The
message contains the address of the requested NE. This message is routed
through the address of the requested NE, and the answer is returned in a
message generated by the requested NE. If an answer is not received within
a predefined time(user definable) or is garbled, NEW will retransmit the
question message. If an NE ceases to answer, this will be notified by NEW.
16
B1091 Rev. L
Basics
3.0
Hardware Overview
NEW needs a minimum of additional hardware to be operational. This
Chapter describes required hardware and how to connect it.
MODEM
MODEM
Figure I-3 Network Element (NE) - PC connection
B1091 Rev. L
17
NEW NMS
3.1
Hardware Requirements
Standalone
Server
Client
Configurator
Win XP Prof. SP2

Win XP Prof. SP2
Win XP Prof. SP2
Win XP Prof. SP2
Win Server 2003 SP1 Win Server 2003 SP1 Win Server 2003 SP1
English
English
English
English
Operating system
CPU Speed
Win 2000 Prof. SP4 Win 2000 Prof. SP4 Win 2000 Prof. SP4 Win 2000 Prof. SP4
Win 2000 Server SP4 Win 2000 Server SP4 Win 2000 Server SP4
English
English
English
English
1 GHz
500 MHz
300 MHz
Memory <= 100 NEs 128 MB
700 MHz
256 MB
128 MB
128 MB
Memory > 100 NEs
256 MB
512 MB
128 MB
N/A
Disk size
2 GB
2 GB
1.5 GB
1.5 GB
Disk file system
NFTS
NTFS
Optional
Optional
Network protocol
Optional
TCP/IP
TCP/IP
Optional
Comm. Ports
1+
1+
1+
Minimum system requirements
Additional required hardware:

A VGA-compatible or better graphical color display; 17" monitor or
larger is recommended.
A CD-ROM drive for software installation.
A mouse, trackball or equivalent pointing device
Hardware program key (enabled by Nera)
A hardware program key has to be plugged into the parallel port to run
the NEW-NMS program. The hardware key is described in chapter
3.2.
Communication hardware:
Depending on which communication media to use for connection
between PC and NE: (The communication hardware is described in
chapter 3.3)
Serial communication: RS-232 cable.
TCP/IP commnication: TCP/IP cables
Modem communication: Multitech Multimodem ZDX telephone
modems (local and remote)
3.2
Hardware Program Key

The hardware program key is needed to run NEW-NMS. If no correct
licensed and activated hardware key is plugged into the parallel port NEW
will start as NEW-Configurator with the limitations this gives. The
hardware key comes in two different versions; parallel port hardware key
and USB port hardware key. See Figures I-4 and I-5.
18
B1091 Rev. L
Basics
The hardware key holds the license information for the customer. The license
information can be read in the About dialog box in the Help menu of the
program. The key is programmed by Nera. If an extension of the present
license agreement is wanted, please contact Nera and you will receive
information for upgrading your hardware key.
If the hardware key is removed during a NEW-NMS session, the program will
terminate within 60 seconds.
Figure I-4 NEW-NMS parallel port hardware key
Figure I-5 NEW-NMS USB port hardware key

Driver for the hardware key is installed during the regular NEW-NMS
installation.
3.3
Network Element Connections

To connect NEW to a Network Element/Nera Management Network, a
physical connection must be applied. NEW can connect to NE/NMN with
either a serial connection (RS-232), a modem connection or a TCP/IP
connection. These connections must be available through the operating
system. When a serial connection is used, the plug on the NE/NMN side of
the connecting cable differs depending on the actual NE type. For complete
documentation, including pin diagrams please see the NE specific manuals.
B1091 Rev. L
19
NEW NMS
3.4
Equipment Compatibility
Equipment
SW code
SW version
SDH - CityLink
SWCityLink-IDU-BOOT / SWCityLink-IDU-APP
R1A and later
SDH - InterLink
SDH - NL29x
SW-CL2IDU-BOOT / SW-CL2IDU-APP
R1A and later
SW-2KCN231-APP
R1A00 and
later
SW2KZ198A-29x-301/SW2KZ198A-29x-302
SW2KZ198B-29x-APP
PDH - NL18x-A
4.0
4.1
R14A and later

R1A and later
SWKCN178B-18x-10
R2A and later
PDH - NL24x
SWKCN178B-24x-10
R5A and later
PDH - CompactLink
435-01249
1.0 and later
PMP - NetLink GFSK
N/A
2.6 and later
N/A
N/A
Selected routers/switches
1
NL29x with 2KZ198B type supervisory unit

Auto-discovery only.
Database Requirements
Database Hardware Requirements Factors
Requirements of the hardware on which the NEW-NMS database system
is running is mostly dependent on factors concerning database logging and
queries, namely:
How much data are logged by the configuration per time unit.
How much historical data are required for statistics.
What is the query load for the database server.
In order to estimate the hardware requirements, it is important to estimate
the amount of data logged by the system. To a large extent this can be
configured by the user.
There are several options for historical data. At user option, NEW-NMS
can wrap the logged data such that older records are deleted from the
database to stop the database from growing indefinitely. Alternatively, the
database can be swapped manually and taken offline for archival, or one can
choose to scale hardware such that data can be stored online for the
foreseeable future.
If the log is wrapped, the system should not log more than 50000 records
per 24 hours when wrap threshold has been reached.
20
B1091 Rev. L
Basics
If your database is going to contain much more than 1000000 records per log,
NERA recommends that the database be moved to a separate computer to
unload the NEW-NMS server machine.
If historical data have any value, wrapping the database should be avoided.
The data should also be secured in some way or the other. The conventional
way of securing data is by utilising a tape backup system. Nera recommends a weekly/monthly full backup of the database.
The query load is mainly dependent on how many users there are of the
system. As a general rule, a NEW-NMS client/server system with 5+
concurrent clients should have the database on a separate computer.
4.2
Database Hardware Requirements

Hardware requirements with respect to amount of historical data.
Description
Recommended
Disk system
RAM
CPU
Other
DB system
B1091 Rev. L
Max entries pr log

< 100000
MSDE
500MB free
128MB
350MHz
Max entries pr log

< 500000
MSDE / MS-SQL / Oracle
2GB free
256MB
500MHz
Max entries pr log

< 5000000
MS-SQL / Oracle
2+ disks, total >

20 GB
512MB
1GHz
Separate DB server,
Fast Ethernet
Client/Server
5+ clients
MS-SQL / Oracle
2 GB free
512 MB
1 GHz
Separate DB server,
Fast Ethernet
21
NEW NMS

22
B1091 Rev. L
Software Setup
SECTION II
Software Setup
B1091 Rev. L
23
NEW NMS

24
B1091 Rev. L
Software Setup
1.0
Software Installation
The NEW program is distributed on one CD.
In order to install and/or run NEW-NMS, the user must be member of the
Administrator group on the (local) machine.
To install the software from the installation CD, please follow this instruction:
1. Place the CD in the CD-drive (D:).
2. Chose run from the Windows start menu.
3. Type D:\Full Installation\setup.exe and press ENTER. Then follow the
instructions on the screen.
4. Choose one of the following options according to your needs:
4.1 Standalone: Normal NEW-NMS installation.
4.2 Server: NEW-NMS will be installed as a server. After installation,
please continue to Chapter 1.2 for configuration of the Server.
4.3. Client: NEW-NMS will be installed as a client, no hardware key is
needed. After installation, please continue to Chapter 1.2 for configuration of the client.
5. Next you will be prompted with Setup Type. The following types are
defined:
5.1. Typical: Normal installation, recommended for most users
5.2. Compact: Minimum installation.
5.3. Custom: Installs the options you specify.
6. When the installation is completed, reboot your machine
7. If applicable, insert the hardware-key into the parallel port before
starting NEW. No hardware key is needed for running NEW-NMS as
Configurator or as Client.
B1091 Rev. L
25
NEW NMS
2.0
2.1
Database
Create NEW-NMS Database
NEW-NMS will not function without a NEW-NMS database. The database
must reside on a database server. The database server may be running on
the local computer or a remote computer accessed via a network.
Note that the two different database systems supported by NEW-NMS are
quite different in nature and different tools are needed to create and maintain
them.
2.1.1
MS SQL Server
If MSDE is installed during the NEW-NMS installation, an MS SQL database
is installed in the MS SQL Server data folder. The path and filename is by
default: Program Files\Microsoft SQL Server\MSSQL\Data\NEW_SQL_R
<xx>.mdf, where <xx> denotes the release version.
If you want to create your own database, do the following:
Before connecting NEW-NMS to MS SQL Server (or the MSDE bundled with
NEW-NMS) you need to create a NEW-NMS database on the server
instance. To create a database, we recommend using the NEW-NMS SQL
Manager tool accessible from the start menu on your desktop:
StartProgramsNEWNEWSQLServerNEW-NMS SQL Manager
Perform the following steps:
Log in to database server with NEW-NMS SQL Manager as system
administrator (sa and no password on a fresh installation)
Create a NEW-NMS Database with a given name
Exit NEW-NMS SQL Manager and log in to NEW-NMS with newnms
and newpasswd
The tool will create NEW-NMS databases by running the NEWDESIGN.SQL
and NEWDATA.SQL script files (in that order) and set up a newnms user
account for you. However, if you purchase MS SQL Server, you may wish
to create the database directly from the scripts and manage your server via
the tools supplied by Microsoft.
For details on operating the NEW-NMS SQL Manager, see the online help.
26
B1091 Rev. L
Software Setup
2.1.2
Oracle
Before you can connect NEW-NMS to Oracle, please have your Oracle
database administrator set up an Oracle account for you. From this account,
run the ORADESIGN.SQL and NEWDATA.SQL scripts (in that order) to
create the necessary tables. (Remember to COMMIT.) Youll find these
script files located in the Oracle directory on the CD.
Further, you have to ensure that Oracle Provider for OLE DB is installed
on all machines where NEW-NMS is to be run. The version of Oracle
Provider for OLE DB must correspond to the Oracle Database release being
used. This driver is not installed by the NEW-NMS installation program, and
it is not included on the CD. The driver is available for download free of charge
from Oracle (http://www.oracle.com). It can be found in the Downloadssection under Technologies, Utilities, and Drivers. It is necessary to
install both the Oracle Provider for OLE DB as well as Client software (Net
Client). These software components are selected during installation of the
Oracle database driver. Only your Oracle database administrator or someone
familiar with Oracle products should run the installation of this driver
software. Reboot the machine when driver installation is completed. Do NOT
use the Microsoft OLE DB Provider for Oracle driver.
B1091 Rev. L
27
NEW NMS
2.2
Data Link Properties

To set up the connection to a NEW-NMS database, select Database in the
login dialog or Datalink on the Tools NMS Database menu.
Figure II-1
Data Link Property Sheet, Provider Tab
Select provider according to the table below and press Next>> to enable
the Connection tab:
Database Vendor
Oracle
MS SQL Server
28
Provider
Oracle Provider for OLE DB (8.1.7.2.0 or later).
Do NOT use the Microsoft OLE DB Provider for
Oracle.
Microsoft OLE DB Provider for SQL Server
B1091 Rev. L
Software Setup
2.2.1
Connection Tab (MS SQL Server)

Use the Connection tab to specify how to connect to a Microsoft SQL
Server database.
Figure II-2
B1091 Rev. L
Data Link Property Sheet, Connection Tab (MS SQL)
29
NEW NMS
1. Enter the the server where the database you want to access is located.
If server name is not filled out, the local server will be used, however,
it will not be available to NEW-NMS clients.
2. Enter information to log on to the server:
Use Windows NT Integrated Security.
Select to use an authentication service to identify yourself. To use this
feature, your OLE DB provider must support an authentication service
and you must have permissions in the data source to use the authentication service.
Use a specific user name and password.
Click to use a supplied user name and password to authenticate your
logon information to the data source. Enter User name and Password
required to connect to the server and remember to tick the Allow
saving password check box.
3. Select the database on the server:
Preferably, enter the database that you want to access.
- or Attach an SQL .mdf database file as a database name.
4. Press Test Connection to ensure that the information you have entered
is correct and that the database is available.
Note! If the connection fails, ensure that the settings are correct. For
example, spelling errors and case sensitivity may be the cause of a
failed connection.
5. Press OK to apply configuration and close dialog.
30
B1091 Rev. L
Software Setup
2.2.2
Connection Tab (Oracle)

Use the Connection tab to specify how to connect to an Oracle database.
Figure II-3
Data Link Property Sheet, Connection Tab (Oracle)
1. Enter the alias for the oracle server in the Data Source field.
2. Enter User name and Password required to connect to the server and
remember to tick the Allow saving password check box.
3. Press Test Connection to ensure that the information you have entered
is correct and the database is available.
Note! If the connection fails, ensure that the settings are correct. For
example, spelling errors and case sensitivity may be the cause of a
failed connection.
4. Open the All tab and enter PLSQLRSet=1 under Extended
Properties (see Figure II-4).
5. Press OK to apply configuration and close dialog.
B1091 Rev. L
31
NEW NMS
Figure II-4
32
Data Link Property Sheet, Extended Properties (Oracle)
B1091 Rev. L
Software Setup
3.0
Client/Server
The server version lets the user start a NEW-NMS session and monitor the
connected network. In addition, a license dependent number of concurrent
clients are allowed to connect to the server. The clients will then, with some
limitations, be able to monitor and configure the connected network in the
same way as done with the standalone version.
In order to utilise the client/server functionality, both servers and clients
have to be properly configured. The required steps are:
1. Create a Domain User Group with the users who will be allowed to run
NEW-NMS.
2. Configure DCOM (Distributed COM) on the NEW-NMS Server machine.
3. Configure DCOM on each NEW-NMS Client machine.
3.1
Client/Server Access Configuration

Insert the NEW-NMS CD into the CD-player, and run the setup.exe
program. During installation, the user can choose to install the following
versions of NEW-NMS
Standalone
Server
Client
The standalone version lets the user start a NEW-NMS session and monitor
the connected network.
The server version lets the user start a NEW-NMS session and monitor the
connected network. In addition, a license dependent number of concurrent
client sessions are allowed to connect to the server. The clients will then
be able to monitor and configure the connected network in the same way
that it is done on the standalone version.
The client version lets the user start a NEW-NMS session by starting the
client, connect and log-in on a remote NEW-NMS server via LAN (TCP/
IP).
B1091 Rev. L
33
NEW NMS
3.2
Client/Server Requirements
In order to connect NEW-NMS clients to a NEW-NMS server, both server
and all client machines must be members of the same Windows Domain.
Administration of Windows Domains as well as Windows Domain Controllers is beyond the scope of this document.
The users logged in on the NEW-NMS Server machine must have local
administrator privileges.
On Windows 2000 Server / Windows Server 2003 the NEW-NMS Server must
run in a local console session and not a Terminal Services client session. This
is a requirement for successful NEW-NMS Client logon.
3.3
User Administration
In order to let users run NEW-NMS as a client or server, their domain user
accounts must be members of a Windows Domain user group, created
especially for that purpose. The connection between a NEW-NMS client and
the server will not function properly unless the users are members of this
domain group.
In order to perform a successful NEW-NMS Client/Server installation and
configuration, the following actions must be taken:
1. On the Windows Domain Controller create a Domain User Group
named NEW-NMS.
2. Add all users to user group NEW-NMS, who shall be allowed to
connect to the NEW-NMS Server when logged in on the Windows
user session on the client machine(s).
3. Add all user(s) to user group NEW-NMS, who shall be allowed to log
in on the Windows user session on the NEW-NMS Server machine.
4. Add all user(s) as described in item no. 3 to local group Administrators on the NEW-NMS Server machine.
Note that a user in this respect is a Windows Domain user on the local
network, not a user as defined by NEW-NMS.
34
B1091 Rev. L
Software Setup
3.4
DCOM Configuration
To enable the Client/Server communication, DCOM must be configured
properly on the sever and client.
3.4.1
Windows 2000 DCOM Configuration
3.4.1.1
Server Setup
The following steps have to be performed on the server machine:
1. Log in with an administrator account.
2. Select Start/Run, and enter dcomcnfg. Press Ok, and the Distributed COM
Configuration Properties sheet is opened.
3. Select the Default Properties tab. Make sure the following options are
set:
Enable Distributed COM on this computer
Default Authentication Level: [Connect]
Default Impersonation Level: [Identify]
Figure II-5
B1091 Rev. L
DCOM Configuration Sheet, Default Properties Tab
35
NEW NMS
4. Select the Applications-tab.
5. Select NEW-NMS in the list, and click the Properties button.
6. In the NEW-NMS Properties sheet, select the General-tab. Set the field
Authentication level to [Default]
Figure II-6
NEW-NMS Property Sheet, General Tab
7. Select the Security-tab, and click the Use custom access

permission button.
36
B1091 Rev. L
Software Setup
Figure II-7
NEW-NMS Property Sheet, Security Tab
8. Select the corresponding Edit button and add the NEW-NMS Domain
User Group (see Client/Server User Administration, and set the Type of
access for this group to Allow Access. (In this example the NEW-NMS
Domain User Group is created in a domain named NERA-BERGEN).
9. Add user SYSTEM (The operating system) on the local machine and set
the Type of access for this user to Allow Access.
Figure II-8
B1091 Rev. L
Registry Value Permissions

37
NEW NMS
10. Click OK and you are returned to the NEW-NMS Properties sheet.
11. In the NEW-NMS Properties sheet, select the Identity tab. Make
sure the field The interactive user is selected.
Figure II-9
NEW-NMS Property Sheet, Identity Tab
12. Click OK in the NEW-NMS Properties sheet.

13. Click OK in the Distributed COM Configuration Properties sheet.
14. Reboot the machine.
3.4.1.2
Client DCOM Configuration

On each client machine, follow the same procedure as with DCOM configuration for the server machine (see Chapter 3.4.1.1).
38
B1091 Rev. L
Software Setup
3.4.2
Windows XP/Windows 2003 Server DCOM

Configuration
In order to enable the Client/Server communication, DCOM must be configured properly on the Server and Client. The procedures outlined here are
valid for both Windows XP and Windows 2003 Server. Note however, that
the screenshots are taken from Windows XP, but the Windows 2003 Server
will have similar windows present.
3.4.2.1
Server DCOM Configuration

The following steps have to be performed on the server machine:
1. Log in with an Administrator account.
2. Select Start/Run, and enter dcomcnfg. Press Ok, and the Component
Services window is opened.
3. Select the tree node Component Services\Computers\My Computer.
Right-click on the node, and select Properties. The My Computer
Properties window should now be opened.
4. Select the Default Properties tab. Make sure the following options are
set:
Enable Distributed COM on this computer
Default Authentication Level: [Connect]
Default Impersonation Level: [Identify]
Figure II-10
B1091 Rev. L
My Computer Property Sheet, Default Properties

39
NEW NMS
5. Select the COM Security tab and press the Edit Limits... button in the
Launch and Activation Permissions group.
Figure II-11
My Computer Properties Sheet, COM Security
Add the NEW-NMS Domain User Group (See Client/Server User Administration), and set the Launch Permission for this group to allow Local
Launch, Local Activation and Remote Activation as shown in Figure II-12.
(In this example the NEW-NMS Domain User Group is created in a domain
named NERA-BERGEN.)
Figure II-12
40
COM Security, Edit Limits, Launch Permission

B1091 Rev. L
Software Setup
6. Select the COM Security tab and press the Edit Default... button in the
Launch and Activation Permissions group.
Figure II-13
My Computer Properties Sheet, COM Security
Add the NEW-NMS Domain User Group (See Client/Server User Administration), and set the Launch Permission for this group to allow Local
Launch, Local Activation and Remote Activation as shown in Figure II-14.
(In this example the NEW-NMS Domain User Group is created in a domain
named NERA-BERGEN.)
Figure II-14
B1091 Rev. L
COM Security, Edit Default, Launch Permission

41
NEW NMS
7. Press OK to close the My Computer Properties sheet.
8. Expand the tree node Component Services\Computers\My
Computer\DCOM Config.
Figure II-15
Component Services, DCOM Config
9. Select and right-click the NEW-NMS icon in the rightmost pane, and select
Properties. The NEW-NMS Properties sheet should now be opened.
10. In the NEW-NMS Properties sheet, select the General tab. Set the field
Authentication level to [Default].
Figure II-16
42
NEW-NMS Properties Sheet, General

B1091 Rev. L
Software Setup
11. Select the Security tab and select the Customize button in the Access
Permissions group
Figure II-17
B1091 Rev. L
NEW-NMS Properties Sheet, Security
43
NEW NMS
12. Select the corresponding Edit button and add the NEW-NMS Domain
User Group (See Client/Server User Administration), and set the Access
Permission for this group to Local Access and Remote Access.
Figure II-18
NEW-NMS Properties, Access Permission 1
13. Add user SYSTEM (The operating system) on the local machine and set
the Access Permission for this user to Local Access and Remote Access.
.
Figure II-19
44
NEW-NMS Properties, Access Permission 2

B1091 Rev. L
Software Setup
14. Click OK and you are returned to the NEW-NMS Properties sheet.
15. In the NEW-NMS Properties sheet, select the Identity tab. Make sure
the field The interactive user is selected.
Figure II-20
NEW-NMS Properties Sheet, Identity
16. Click OK in the NEW-NMS Properties sheet.

17. Close the Component Services window.
18. Reboot the machine.
3.4.2.2
Client DCOM Configuration

On each client machine, follow the same procedure as with DCOM configuration for the server machine (see Chapter 3.4.2.1).
B1091 Rev. L
45
NEW NMS
3.5
Server Login
To log in on the server, enter user name and password. The user database
connection has to be configured. To do this, push the Database button and
follow the steps described in database configuration. The database contains
user information as well as network information.
3.6
Client Login
To log in on a client, enter the user name and password. The server to connect
to has to be chosen. To do this, enter the hostname (or IP address) of the
machine running the server in the Server to connect to field.
46
B1091 Rev. L
Using NEW
SECTION III
Using NEW
B1091 Rev. L
47
NEW NMS

48
B1091 Rev. L
Using NEW
1.0
1.1
Getting Started
Logon
When the NEW program starts, the Logon dialog box is displayed where
the user must enter a user name and password. If not previously selected,
the database connection must also be selected (see section VIII for more
information about the Logon dialog box).
Figure III-1
1.2
The Logon dialog box
Discovering Network Elements

When logged on with the Create a new network option selected, the
program automatically tries to discover the connected network through
the computers serial ports (only the most common serial port settings are
tried).
All discovered network elements are listed in the add elements dialog box.
(see Figure III-2) The user must select the networks elements to be
managed in NEW. The number of network elements cannot exceed the
maximum number of elements given by the user license.
If the program cannot establish contact with all or some of the network
elements that apparently should have been in the discovered list, the
settings in the communication dialog box must be checked. (The Communication dialog box is opened by selecting Communication from the
Configuration menu). After the correct communication configuration is
done, the discover process must be restarted (by selecting Discover from
the File menu).
B1091 Rev. L
49
NEW NMS
Figure III-2
Add elements dialog box
Elements added to the NEW network are automatically displayed in an

Explorer view.
By default, all network elements are polled in order to check their status.
The polling frequency of the network elements can be reconfigured from
the Polling dialog box, which can be opened by selecting Polling from the
Fault menu.
All connected network elements should now be apparent in the explorer
view.
Maps can now be created by using the Map Navigator, and logs can be
defined and/or viewed.
Note!
NEW-NMS' security system has initially one user account:
User ID:
Password:
admin
adminpasswd
It is strongly recommended to change this

password!
50
B1091 Rev. L
Using NEW
2.0
Program Environment
The NEW program is a 32-bits Windows program. If you have used other
Windows applications, the NEW-NMS graphical user interface will be
familiar to you. NEW-NMS has a graphical user interface and follows a plug
& play philosophy.
2.1
Menus
File
The file menu deals with administration of the network

files, printing, logging on/off networks and discovering networks. Network files have the extension .net
and are used by the program to save network
information.
Edit
The edit menu contains standard Windows clipboard functions and functions for editing Map views.
View
The View menu contains functions for viewing
networks.
Configuration The configuration menu deals with configuration of
the network elements and configuration of the
communication media NEW uses for communication
with the elements.
Fault
The Fault menu contains the program's fault management functions.
Performance
The performance menu contains the program's
performance management functions.
Security
The security menu contains the program's security
management functions.
Tools
The tools menu contains functions for database
management, map navigator, key enabler, SQL
manager and options.
Window
The window menu contains functions for arranging
the windows of the program.
Help
The help menu contains functions for help.
B1091 Rev. L
51
NEW NMS
2.2
Toolbar
The toolbar offers shortcut buttons for some of the most used functions.
The toolbar buttons are shown in Table III-1.The toolbar can be toggled on/
off from the View menu.
Icon
52
Function
Description
New
Opens a new, empty network file.
Open
dialog box.
Opens an existing network file via the Open File
Save
Saves the network file.
Cut
Cuts out the selected text or image and puts it

on the clipboard.
Copy
Copies the selected text or image to the clipboard.
Paste
Pastes the contents of the clipboard to the

currently active window.
Print
This command presents a Print dialog box,

where you may specify the range of pages to be
printed, the number of copies, the destination
printer, and other printer setup options.
Help
Displays the NEW-NMS help file
B1091 Rev. L
Using NEW
Toolbar buttons only available with NEW-NMS:
Icon
Function
Description
Select tool
Selects individual and groups of map objects.

Objects can then be dragged, cut, copied and
pasted.
NE tool,
terminal
Inserts an NE symbol into a map view. The symbol

can then be linked to a true network element by
use of its short cut menu (right mouse click).
NE tool,
repeater
Inserts an NE symbol into a map view. The symbol

can then be linked to a true network element by
use of its short cut menu (right mouse click).
Hyperlink
tool
Inserts a map/hyperlink symbol into the map

view. The symbol can then be linked to a
different map view by use of its short cut menu
(right mouse click) and the Map Navigator Link
button.
Connection
tool
Inserts a virtual connection between two map

objects. To connect; select the two map objects
to be connected, then select the Connection tool.
Map
Navigator
shortcut
Opens the Map Navigator in view mode.
Table III-1 NEW Toolbars
B1091 Rev. L
53
NEW NMS
2.3
Explorer View
The Explorer View is opened by selecting Explore Net from the View
Menu.
The Explorer View shows the Network information in a logical manner. Each
NE is divided into two main branches:
Transmission branch:
The sub-branches and leaves under the Transmissions branch concerns the transmission
aspects of the NE
Equipment branch:
The sub-branches and leaves under the Equipment branch concerns the physical equipment
of the NE.
The sub-branches below the Transmission and Equipment branches are NEtype specific.
Figure III-2 Example of Explorer view, CityLink with Electical line
54
B1091 Rev. L
Using NEW
The user navigates in the Explorer View by closing and expanding the
different element branches and leaves. The tree-branches can be closed or
expanded, and different actions can be imposed on them.
To expand/collapse Nodes in the tree:
Expand nodes by pressing the plus sign, or by choosing Expand
from the right-button menu.
Collapse nodes by pressing the minus sign or by choosing Collapse
from the right-button menu..
The elements can be reviewed with respect to configuration, alarms and
performance. A dynamic right-mouse-button pop-up menu is the main tool
for imposing actions on the tree-nodes.
To view the menus on the elements and nodes:
Press the right mouse button on the actual node or leaf.
Status of selections are indicated in the title bar of the Explorer view.
Alarm severities:
The Icons indicate Alarm severity status through use of colors.
Network element icon indicates its most severe status condition.
Section icon propagates the most severe status condition in its
domain.
The Explorer View use the severity colors to indicate alarm severity status.
The alarms are presented in a hierarchical manner. The color of the most
severe alarm are inherited from the leaf where the alarm was identified, to all
branch leaves up to the section symbol. E.g. the section and NE symbols will
always show the alarm color of the most severe alarm identified in the subbranches in the Explorer view.
By pressing the right mouse button on any leaf in the Explorer View and
selecting Current Alarms from the pop-up menu, a Current Alarm List is
opened showing all alarms Hierarchical below the selected leaf.
B1091 Rev. L
55
NEW NMS
2.4
The Map View (Only available in NEW-NMS)

The Map View is opened by selecting Map Navigator from the Tools
Menu. The Map Views can operate in two modes; edit mode or view
mode. The mode is toggled by the Edit- and View-buttons in the Map
Navigator.
In edit mode, the user is allowed to define/organize maps and symbols, while
in view mode, the user is restricted to browsing predefined maps.
The map view shows a geographical view of sub-networks. Initially, when
the view is created by the Map Navigator, all the discovered NEs with
bindings will appear in the map. The map can be modified utilizing the various
map tools. Illustrative background images can be added, and networks can
be broken into submaps, or different views, all to help visualize complex
networks.
Figure III-3
Example of Map view
The NE icons changes their severity colors according to the current most
severe alarm of the NE.
The Map Views contains various graphical objects:
NE symbols: Shows the current status of the NE
Connection symbols: Indicates various types of
connections between NEs.
Hyperlinks to other map views.
OLE objects for illustration purposes.
56
B1091 Rev. L
Using NEW
Map Editing:
1. To edit a map open the Map Navigator from the Tools menu.
2. Select the map in the list and press Edit or press Create to create
a new map (Press edit to set the new map in edit mode).
3. Edit the map using the map toolbar.
Figure III-4 Map Management toolbar (dockable)

Select tool : Selects individual and groups of map objects.
Objects can then be dragged, cut, copied and pasted.
NE tool, terminal and repeater : Inserts an NE symbol
into a map view. The symbol can then be linked to a true
NE by use of its short cut menu ( right mouse click ).
Hyperlink tool : Inserts a map/hyperlink symbol into the
map view. The symbol can then be linked to a different map
view by use of its short cut menu (right mouse click) and the
Map Navigator Link button.
Connection tool : Inserts a virtual connections between
two map objects. To connect; select the two map objects to
be connected, then select the Connection tool.
Map Navigator shortcut: Pops up the Map Navigator in
view mode.
4. When finished editing, select the map in the Map Navigator and
press View. The map will then enter view mode.
Add background images:
Select Insert New Object.. from the Edit Menu and follow the
instructions.
Map Settings:
The Map Settings Dialog Box lets you change the general appearance
of the maps. The Map settings can be opened from the Tools menu and
then selecting Options.
B1091 Rev. L
57
NEW NMS
2.4.1
Map Management (Only available in NEW-NMS)

The main interface to the map views is the Map Navigator. The map
navigator is the map administration tool. It contains a list box on the left hand
side, and various command buttons on the right hand side. The list box
contains a list of all maps defined in the current network. The user can then
select a map with the mouse from this list, and impose various actions on it
with the buttons on the right hand side.
Figure III-5 Map Navigator
Buttons:
Create
Delete
View
Edit
Link
Close
Help
Creates a new empty map

Deletes the selected map
Opens the selected map in view mode.
Opens the selected map in edit mode.
Links the selected hyperlink symbol (selected in an open,
edit mode, map) to the selected map.
Closes the Map Navigator.
Provides Map Navigator help.
To change the name of a map:
1. Doubleclick the map in the Map navigator list with the left mouse button.
2. Type the new name of the map.
3. Click somewhere else in the dialog box.
58
B1091 Rev. L
Using NEW
2.4.2
Tutorial
(Only available in NEW-NMS)
This chapter describes...
...how to load a network into the NEW-NMS.
...how to create maps.
...the default map.
...how to set a map in edit mode.
...how to delete maps.
...how to rename maps.
...how to populate a map with NEs.
...how to attach NE symbols to NEs.
...how to populate a map with map symbols.
...how to link map symbols to maps.
...how to add a backdrop to a map.
When all the tasks are done in sequence, a hierarchy of three maps are
created. Two of the maps will be local area maps, while the third map will
be a network overview map showing the state of all local areas.
Task 1: Load a network into the NEW-NMS
1.Start the NEW-NMS.
2. Log on as admin.
3.On the File Menu, chose open, and open the tutorial.net file. This file
is localized in the NEW-NMS program folder.
4. On the View Menu, chose Explore Net.
Figure III-6
B1091 Rev. L
Explorer View
59
NEW NMS
The Explorer View is now open, showing three radio sections. The radio
sections are blue, indicating that there is no contact with the network
elements. This is correct.
Task 2: Create maps.
1.On the Tools Menu, select Map Navigator.
2.Push the Create button in the Map Navigator dialog 4 times. Map 1,
Map 2, Map 3, and Map 4 are now created.
Task 3: The default map.
Figure III-7 Map View Edit Mode

In the first map created, all NEs are included, and they are given a default
layout. This is the default map. The default map can be used in cases where
one single map is sufficient for the whole network.
1.In the Map Navigator dialog, select Map 1 and push the View button.
A view containing Map 1 pops up. Note that all the NEs in the network
are present, and that they have been given a default layout.
60
B1091 Rev. L
Using NEW
Task 4: Set a map in edit mode.
1.In the Map Navigator dialog, select Map 1 and push the Edit button.
Note that the title of the Map 1 view is appended with - edit mode.
2.Point and left-click at one of the NEs in Map 1. Do not release the
mouse button. Drag the NE a short distance in the map.
3.Release the mouse button. The NE has now moved to a new position.
4.Make sure Map 1 is still selected in the Map Navigator dialog. Push
the View button. The view is now in View mode; note that the view is no
longer appended with - edit mode, and that it is impossible to move any
of the NEs.
Task 5: Delete maps.
1.In the Map Navigator dialog, select Map 1.
2.Push the Delete button.
The default map is now deleted. It was safe to delete it, because it is not
needed in the rest of the tutorial.
Task 6: Map renaming.
All operations in this task will be performed in the Map Navigator dialog.
1.Select Map2.
2.Type the new name of Map 2 on the keyboard. Name this map Bergen.
3.Select Map3.
4.Type the new name of Map 3 on the keyboard. Name this map Kokstad.
5.Select Map4.
6.Type the new name of Map 4 on the keyboard.
Name this map Bergen area.
7.Click somewhere else in the dialog box.
The maps are now renamed.
Task 7: Populate maps with NEs.
1.Open the map Bergen in Edit mode.
To open a map in edit mode, see task 4.
2.Select one of the NE tools on the map toolbar. Any will do.
3.Left-click once inside the Bergen map. A green NE symbol named
<empty> appears inside the view.
4.Repeat steps 2-3 until there are 6 NE symbols named <empty> inside
the view.
5.Open the map Kokstad in Edit mode.
6.In the Kokstad map, repeat steps 2-3 until there are 3 NE symbols named
<empty> inside the view.
The maps Bergen and Kokstad are now populated with empty NE symbols.
B1091 Rev. L
61
NEW NMS
Task 8: Attach NE symbols to NEs.
1.Open the map Bergen in Edit mode. To open a map in edit mode, see task 4.
2.Right-click of of the NE symbols named <empty>, and select Attach to
NE from the context menu. The Map Attachment dialog appears.
3.Chose the NE to connect to the NE symbol, and push the Attach button.
The NE symbol is now attached to the chosen NE.
4.Repeat step 2-3 for all NE symbols in Bergen. Make sure all attached
NEs are from section 1 and 2.
5.Open the map Kokstad in Edit mode.
6.Repeat step 2-3 for all NE symbols in Kokstad. Make sure all attached
NEs are from section 3.
Task 9: Populate a map with map symbols.
1.Open the map Bergen area in Edit mode. To open a map in edit mode,
see task 4.
2.Select the Hyperlink tool on the map toolbar.
3.Left-click once inside the Bergen map. A map symbol named <empty>
appears inside the view.
4.Repeat steps 2-3 until there are 2 map symbols named <empty> inside
the view.
Task 10: Link map symbols to maps.
see task 4.
2.Right-click one of the map symbols named <empty>, and select Link
from the context menu. The Map Navigator.
3.Inside Map Navigator dialog , select the map to link the map symbol to
and push the Link button. The map symbol is now linked to the selected
map.
4.Repeat step 2-3 for the last map symbol in the Bergen area map.
Task 11: Add a backdrop to a map.
see task 4.
2.On the Edit Menu, chose Insert New Object.
3.Push the Create New radio button, and select Bitmap image from the
list.
4.Draw some lines in the bitmap, and click outside the bitmap, but inside
the view. The backdrop is now added.
Note that if Create From File is selected, any files containing OLE aware
objects can be chosen. This spans Windows metafiles, bitmaps, MS Word
documents, etc. thus a wide range of objects can be selected.
62
B1091 Rev. L
Using NEW
2.5
Alarm View
The current alarms of a section, network element or a network element
node, can be viewed by selecting Current Alarms in the right mouse
button pop up menus in the different views. The Current alarms list shows
the alarms reported on at the present time at all the NE nodes. The alarms
are presented hierarchically below the node where the Current Alarms
view was opened from.
Figure III-8
2.6
Example of Current Alarms view
Logs
All kinds off NE and NEW events can be logged and these logs can be
viewed. (Logs are only supported in NEW-NMS). There are three log
managers; a security log manager, a fault log manager and a performance
log manager.
B1091 Rev. L
63
NEW NMS
2.7
Context Sensitive Help

NEW includes a comprehensive context sensitive help system. All dialog
boxes and property sheets have Help buttons which launches help on the
current open box/sheet. All buttons have Whats this ? popup help which
can be launched by either clicking the little question mark in the upper right
corner of the dialog box/property sheet and then clicking the button/item
you want help on, or you can just press the right mouse button on the item.
Figure III-9
Example of Whats this ? help
All alarms in the Current alarms list and in the alarm logs have unique help
which can be launched by selecting the alarm with the mouse, then either
press F1 or press the right mouse button.
Figure III-10
64
Example of Alarm help
B1091 Rev. L
Fault
SECTION IV
Fault Management
B1091 Rev. L
65
NEW NMS

66
B1091 Rev. L
Fault
1.0
General
Fault management is the process of locating and correcting network
problems or faults. Fault management is possibly the most important task
in network management. It consists of identifying the occurrence of a
fault, isolating the cause of the fault and correcting it if possible. The fault
management increases the network reliability by giving the network
operator a tool that quickly detects problems and initiates recovery
procedures. NEW-NMS contains functions for acquisition, presentation
and storage of alarms and events from the network to be managed.
2.0
Information Acquisition
In order to detect faults, information must be gathered from the network.
The state of the network is monitored using two different methods;
polling and event notification.
2.1
Polling
The various network elements should be polled on a regular basis, so that
changes in Network Elements (NE) are detected and network connectivity
is checked. Which NE to poll and the polling rate is user definable.
The Polling dialog box is opened by selecting Polling from the Fault menu.
Figure IV-1
2.2
Polling Dialog Box
Event Notification
In addition to polling, some NEs have the ability to spontaneously report
events. NEW will gather this information in addition to polling. This
feature may decrease the managers response time to network events.
B1091 Rev. L
67
NEW NMS
3.0
3.1
Alarms
Severity Levels
In all views where network information is presented, colors are used for
indicating the alarm severity status of the network elements. To easily
identify the status of the network elements, all alarms are classified
according to their severity. Each alarm severity class has a color. In the
different views, the network elements changes colors according to the
color of their most severe alarm. The alarm classification are described
below.
Severity
Normal
Color
(default)
Green
Description
No alarms or warning have been reported

from the NE.
Warning
Yellow
Indicates the detection of a potential or impending service-affecting fault, before any
significant affects have been felt. Action
should be taken to further diagnose and correct the problem in order to prevent it from
becoming a more serious service-affecting
fault.
Minor alarm Dark yellow Indicates the existence of a non-serviceaffecting fault condition and that corrective
action should be taken in order to prevent a
more serious fault.
Major alarm Orange
Signifies that a service-affecting condition
has occurred and urgent corrective action is
required.
Critical alarm Red
The most severe alarm. It signifies that a
service-affecting condition has occurred and
an immediate corrective action is required.
No contact
Blue
Indicates that no contact is achieved with the
NE. The communication settings should be
checked in order to obtain contact with the
element.
Logged off
Magenta
The NEW user is not logged on to the element.
3.1.1
Changing the Alarm Severity Colors and Sounds

The Alarm Severity Colors & Sounds Dialog lets the user change the
colors and sounds that indicate the severity of acknowledged and unacknowledged fault alarms. The Severity Colors & Sounds configuration
can be opened from the Tools menu and then selecting Options.
68
B1091 Rev. L
Fault
Figure IV-2
The Alarm Severity Colors & Sounds Dialog Box
To change the color of an alarm severity level:
At the row of the severity level you want to change color:

1 Double-click the row. This will pop up a combo-box with possible colors.
2 Select a color from the combo-box.
3 Press OK to save the changes and close the dialog box. Press Cancel to
discard the changes and close the dialog box.
To restore default colors :
1 Press Default.
2 Press OK to save the changes and close the dialog box. Press Cancel to
discard the changes and close the dialog box.
To assign sounds to specific events:
To assign sounds to specific events or change the existing sounds, you can
edit the sound properties by clicking the Define Sounds button. (This is
the same sound properties as in the Control Panel.)
It is possible to assign sounds to the following events:
NEW_SeverityCritical
NEW_SeverityMajor
NEW_SeverityMinor
NEW_SeverityWarning
NEW_SeverityNormal
NEW_LostContact
The sound is triggered by a change in the severity-level on the individual

NE.
B1091 Rev. L
69
NEW NMS
3.2
Alarm Editing
This sheet shows all alarms hierarchically for the selected node and its
subsequent nodes. Alarm Edit can be opened on all the nodes from the
Section level and below in the Explorer view.
The alarm edit lets the user:
Change the name of the alarms
Change the severity level of the alarms
Block unwanted alarms
Set the active mode for the external alarms
Apply changes to individual or multiple alarms
Apply changes to identical alarms
Figure IV-3
Fields:
Alarm Edit Dialog Box
Description:
Node
Alarm ID
Alarm name
Severity
Blocking
The node location of the alarm.

The unique alarm identification number.
The alarm name. Can be edited.
The severity level of the alarm. Can be edited.
Determines whether the alarm is blocked or not.
Can be edited
Checked = blocked Unchecked = not blocked.
Active
Defines whether a logically high or low input level
represents an alarm on external lines. Can be edited.
(external alarms only)
Modification Range Allows changes made to an alarm to be applied to
identical alarms
Changing the Settings:
There are two ways of editing the alarm settings; by double clicking
(incell) or right clicking (context menu) on single or multiple alarms,
respectively.
70
B1091 Rev. L
Fault
1. Incell editing:
Name:
1) Doubleclick on alarm name to be edited.
2) Type in new name.
3) Click outside name cell.
Severity: 1) Doubleclick on severity cell of alarm to be edited.
2) In the appearing combo box, choose wanted severity.
3) Click outside combo box.
Blocking: 1) Toggle the blocking state of an alarm by clicking on the
check box (in the blocking column) for wanted alarm.
Active:
1) Doubleclick on active cell of alarm to be edited.
2) In the appearing combo box, choose wanted active input
level.
3) Click outside combo box.
2. Context menu:
1) Select alarm(s) to be edited.
2) Rightclick within selection.
3) In appearing context menu, choose wanted setting.
4) In appearing dialog box, edit chosen setting and press OK.
5) If multiple alarms have been selected, confirm editing of all alarms by
pressing Yes in appearing message box.
After finishing editing alarm settings, press Set to send the changes to the
network element(s).
Modification Range
This option simplifies changing settings on identical alarms from the
selected node and below. To illustrate the options advantage an example
is given:
The user wants to rename all LOS (Loss Of Signal, alarm Id #1000)
alarms shown in the list box to Loss of Signal. This can be done in two
different ways;
1) rename all LOS alarms individually
2) set the Modification Range to All identical alarm and renaming one of
the alarms. A message box will prompt the user for verification of the
setting.
Buttons:
Name:
Get:
Set:
Close:
Help:
B1091 Rev. L
Press this button

Press this button to retrieve the current settings from the NE.
Press this button to send the settings to the NE.
Closes the property sheet.
Press this button to get help on the current property sheet page.
For help on an item, click
at the top of the dialog box, then
click the item.
71
NEW NMS
4.0
Visual Alarm Notification

There are four different ways of monitoring alarms in NEW. These methods
are described in the following subchapters.
4.1
Alarms on a Tree Node/Leaf in the Explorer View

The Explorer View is opened by selecting Explore Net from the View Menu.
The Explorer View shows the Network information in a logical manner. Each
NE is divided into two main branches; one Transmission branch and one
Equipment branch. The sub-branches and leaves under the Transmission
branch concerns the transmission aspects of the NE. The sub-branches and
leafs under the Equipment branch concerns the physical equipment of the NE.
Figure IV-4
Explorer View
The Explorer view uses the severity colors to indicate alarm events. The
alarms are presented in a hierarchical manner. The color of the most severe
alarm is inherited from the leaf where the alarm was identified, to all nodes
up to the section symbol. E.g. the section and NE symbols will always show
the alarm color of the most severe alarm identified in the sub-branches in the
Explorer view.
By pressing the right mouse button on any nodes/leaves in the Explorer View
and selecting Current Alarms from the pop-up menu, a Current Alarm
List (ref. Chapter 4.4) is opened showing all alarms Hierarchical below the
selected leaf.
72
B1091 Rev. L
Fault
4.2
Alarms on a Node Symbol in the Map View

The Map View is opened from the Map Navigator. The Map View shows the
Network information in a geographical manner. Each NE are displayed as
an icon. Graphic-files can be added as background images in the view. NE
icons grouped together with bindings forms networks. The NE icons
changes their severity colors according to the current most severe alarm
of the NE.
Figure IV-5 The Map View (with an example of background graphics)

By pressing the right mouse button on an NE icon in the Map View and
selecting Alarms from the pop-up menu, a Current Alarm List (ref.
Chapter 4.3) is opened showing all alarms of the NE.
B1091 Rev. L
73
NEW NMS
4.3
Viewing the Current Alarms

The current alarms of the selected section, element or element sub-node
can be viewed in a list by selecting Current Alarms from the Fault menu or
from the right-button context menu in the Explorer View or Map View.
The Current Alarms list displays the current alarms Hierarchical below
the selected node. This view has a resizeable frame.
Figure IV-6 Example of Current Alarms
Fields
Description
Severity
The severity of the alarm
Alarm Text A short description of the alarm. The alarm description can
be changed by the user.
Node
The name of the node where the alarm occurred
Buttons:
Freeze
74
Freezes the list so that it is not updatable.
B1091 Rev. L
Fault
5.0
5.1
Logging Fault Events

Fault Log Manager
(Only available in NEW-NMS.)
Administration of the fault log is done from the Fault Log Manager, which
can be displayed by selecting Fault Manager in the Tools NMSDatabase Menu. Users can monitor and store fault events through NEWNMSs fault logging features. NEW-NMS collects fault events from the
whole network.
Figure IV-7
Fault Log Manager Dialog Box
Fields:
Description:
Operational state
Log full action
Enable or disable logging of faults to database.

Choose what to do whem the fault log is full.
Wrap: When the log has reached a maximum
treshold, the oldest records exceeding this
treshold, are deleted in an overnight batch-job.
Halt: When the log has reached a maximum
treshold, Operational State is set to disabled.
Max Record Count:
The maximum number of entries in the log
before Log Full Action is taken.
Current Record Count: The current number of records in the fault log.
Alarm threshold:
When this treshold is reached, a message box
warns you that Log Full Action will be taken
soon.
Percentage bar:
Shows the current log size in a visual manner.
The alarm threshold value is shown as a red line.
Buttons:
Log View:
Discriminator:
B1091 Rev. L
View the contents of the fault log.

Choose which fault events to be collected and stored
in the database.
75
NEW NMS
5.2
The Fault Log View

The Fault Log View is a presentation of the fault database in list-form.
Faults are shown as rows in the list. The column headers are the same as
the database field names.This view is sizable. The initial size is the
minimum allowed size. When sizing the window, the fault list is also sized.
The buttons positioned below the list follows the frame when sizing.
The Fault Log View can be opened with the following actions:
Select Log View from the Fault menu.
Select Fault Log from the View menu.
Press the Log View button in the Fault Log Manager dialog.
Figure IV-8
76
The Fault Log View
Fields:
Description:
Log ID
Sec
SU
Node
Alarm Id
Alarm Text
AlarmEvent
Severity
Time NE
Acked
NE Log Id
Time NE (milli)
Node Address
The log identifier of the fault log.

The section number which the NE is related to.
The Supervisory Unit which identifies the NE.
The NE node where the alarm occurred.
TThe unique fault identification number.
The alarm text.
Raised, Cleared or Floating.
The fault severity .
The time the fault occurred in the NE.
Whether the fault has been acknowledged or not.
The identifier of the fault in the NE log.
The millisecond part of Time NE.
The address of the NE.
B1091 Rev. L
Fault
Remote Id
Agent Name
Network
The equipment identifier.

The name of the machine logging the fault.
The network on which the fault occurred.
Buttons:
Columns
Displays the columns dialog box, where the user may

select the visibility of the columns in the list.
Filter
Displays the filter dialog box, where the user may
select, create or redefine a filter that determines the
set of faults listed in the view.
The filter drop list Displays the currently selected filter, and enables
the user to rapidly change filter, without entering the
filter dialog box.
Auto Refresh
When checked, the list is updated with the latest 50
faults at regular intervals.
Unacked only
When checked, only unacknowledged faults are displayed.
Colors
Press the button in order to display all faults with
their defined alarm colors. To remove the colors,
press the button again. You can select to display
colors based on individual severities by pressing the
arrow part of the button, and check the desired
severity. The displayed colors will follow the
ordinary alarm colors, except for the acknowledged
alarm, where the color will be lighter.
Max. lines per
Limits the maximum number of faults displayed on
grid page
a page in the list. Used to reduce database access
time. The list may contain many pages.
Navigation buttons Use the navigation buttons to move the selection in
the fault list. When the selection is moved to the
next/previous page, the next/previous page with data
matching the current filter will be displayed.
Refresh
Query for new faults matching the current filter and
settings.
Acknowledge
Acknowledge the selected fault(s). When one or
more faults are acknowledged, a dialog is displayed,
where a comment can be added. This button will only
be enabled if the selected fault is not acknowledged.
In order to acknowledge faults, the user must be at
least an Active User.
Comment
View or edit the comment for an acknowledged fault,
or a series of acknowledged faults with the same
B1091 Rev. L
77
NEW NMS
Report
Help
comment. If a single fault is selected, this button will

only be enabled if the fault has a comment attached.
If several faults are selected, the button will be
enabled if all the selected faults have the same be at
least an Active User.
Opens a Fault Report application which generates a
report from the faults matching the current filter.
This action is independent of the Max. lines per
grid page setting.
Displays this help page.
Operations:
How to acknowledge multiple faults at the same time
First you have to make a contiguous or non-contiguous selection of faults.
A contiguous series of selected faults is made by selecting the first fault,
holding down the SHIFT key, and selecting the last fault. Alternatively;
Select the first fault, and then use the following key combinations: SHIFT
+ Up Arrow, SHIFT + Down Arrow, SHIFT + PgUp, and SHIFT + PgDn. In
order to make a non-contiguous selection, first make a contiguous selection, and then add single faults to the selection by holding down the CTRL
key and clicking on individual faults.
How to view the acknowledge comments
There are three ways to view the comment of an acknowledged fault:
Select the fault, and press the Comment button. The Comment dialog
will be shown.
Select the fault, and double-click on the selected fault. The Comment
dialog will be shown.
Hold the mouse cursor above the check mark in the Acked column of
the selected fault. A tool tip with the comment will appear
How to edit the acknowledge comment
First, open the Comment dialog by double-clicking on the selected fault,
or pressing the Comment button. Edit the comment, and press the Ok
button. The comment will now be updated.
Each time a comment is edited, a new comment is stored in the database.
So if the original comment was shared among many acknowledged faults,
the new comment will shared among those faults that were selected when
the comment was edited. The rest of the acknowledged faults who shared
the original comment, will still have the original comment.
78
B1091 Rev. L
Fault
How to adjust the columns in the list
It is possible to change the column sequence in the list. First, select the
column by clicking on the column header button (on the column name).
Then press the left mouse button down on the header button again, and
while the mouse button is still down, move the column to the desired
location, and then release the mouse button. A marker will be displayed in
the list during the move operation, indicating where the column can be
dropped.
The visibility of the columns is set in the Columns dialog (see chapter
5.2.1), which is opened by pressing the Columns button.
The width of a column is adjusted by placing the mouse cursor between to
columns, when the cursor changes, press the left mouse button and drag.
Release the mouse button when the desired width is achieved.
You can group the various values of a column together, by moving the
column into the grouping area above the columns. First, select the column
by clicking on the column header button (on the column name). Then press
the left mouse button down on the column header button again, drag the
column upwards, and release the mouse when you see the column indicator
in the grouping area. The column will then be sorted, and the sort direction
will be indicated by a small image in the column header button. Press the
column button to switch sort direction. Several columns can be added to
the grouping area, and you can change the sequence of the grouped
columns by dragging the column header to the desired location.
To remove a column from the grouping area, drag the column back into the
non-grouped columns.
Persistent view settings
When the view is closed, most of its settings are stored. These settings
include columns settings, filter name, auto refresh, unacked only and
color settings. When the view is opened the next time, the settings will be
applied to the view, even if NEW-NMS has been shut down in the mean
time.
The Max Lines Per Grid Page is not stored, it is always set to the minimum
size when the view is opened, in order to ensure fast display of data.
B1091 Rev. L
79
NEW NMS
5.2.1
Select Visible Columns

The Select Visible Columns dialog box is opened from the various log
views. With this dialog, you can set the visibility of the columns present
in a log view. Visibility is toggled by clicking on the check box next to the
column name. A check mark indicates that the column will be displayed.
Figure IV-9
The Select Visible Coloumns Dialog Box
Tips:
Column order
The column order can also be changed from within

the log view. Left-click and hold on a column and drag
the column to the desired position. Release the mouse.
The column is now moved.
Invisible column An alternative method to make a column invisible is to
set its width to 0 in the log view. This is done by
dragging the right border of the column onto the left
border (or opposite).
80
B1091 Rev. L
Fault
5.3
Filtering
NEW offers a filtering facility for selecting a subset of the records from
a database. The same filtering dialog box (with minor changes) is used for
filtering performance- and security-logs. The same dialog box is used both
for selecting which events to be added to the database and which events to
be displayed in the log view. All the filter categories are working together
to limit the database search criteria; the records must accommodate all the
categories criteria in order to be included in the resulting recordset.
Figure IV-10
Alarm Filter
The different categories are:

1. Nodes:
Specific set of NE nodes to collect information from. The left tree-control
displays all NE nodes, and the right one displays the selected NE nodes.
The buttons for selecting and deselecting nodes:
Add Selected
Adds the selected nodes.
Add Hierarchy
Adds the selected node plus all sub-nodes under
the node (recursive).
Add All
Adds all nodes in the network.
Remove Selected Removes the selected nodes.
Remove Hierarchy Removes the selected node plus all sub-nodes under
Remove All
Removes all nodes in the network.
B1091 Rev. L
81
NEW NMS
2. Severity (fault log):
One or more alarm severity levels can be selected by selecting the
checkbox for each severity you want to include.
The fault filter also have an additional field: Alarms generated by NEW.
If this check-box is checked, alarms generated by NEW will be included
in the filter.
3. Time:
A specific period of time can be selected from a set of edit-boxes (with
spinbuttons). The period of time is specified by a From time and a To
time. If the Use current time as To- time - check box is checked, the
To time will not be included in the query.
Saving/Restoring filters:
The filter may be stored permanently for later use by pressing Save and
giving the filter a name. The filter will be stored in the NEW network file.
Filters may be retrieved from the network file by first selecting the wanted
filter in the Stored filters list, and then press Load. Filters may be deleted
by selecting the filter and pressing the Delete button.
82
B1091 Rev. L
Configuration
SECTION V
Configuration Management
B1091 Rev. L
83
NEW NMS

84
B1091 Rev. L
Configuration
1.0
Communication
NEW-NMS communicates with the network elements through different
communication ports, which can be serial ports, modem ports, TCP/IP or
SNMP. Configuration of the communication ports is done by selecting
Communication from the Configuration menu.
The serial ports registered by the operation system and installed modems
are automatically displayed in the list while TCP/IP and SNMP ports have
to be added manually.
A backup port can be assigned for each port (except for SNMP ports). The
backup port will be used when a message on the main port times out. When
using the backup port, messages are periodically also sent to the main port
in order to detect whether the main port has recovered. If the message
times out when using the backup port, the message gets lost, even if the
backup port has its own backup port. In other words; the message will only
be routed one level through the backup system.
Note that NEW-NMS will try to keep the port in the selected state. This
means that if the port is disconnected by any reason other than the user
pressing the Disconnect button, NEW-NMS will automatically try to
reconnect. NEW-NMS will automatically retry the connection/disconnection attempts using an increasing interval of time (up to maximum 5
minutes retry interval).
Figure V-1
B1091 Rev. L
Communication Media Manager
85
NEW NMS
The port list displays all communication ports available for the network.
Not all ports need to be in use or connected.
Fields:
Port
Status
Protocol
Backup
Subnetwork
Description:
The port address.
Indicates the state of the communication port.
Possible states are : Connected, Connecting...,
Disconnecting... and Disconnected. For modem
ports the call states are also displayed.
The protocol used on the port. Q1 is used on TCP/
IP, serial and modem ports, while SNMP is used
for SNMP on UDP ports.
The backup port, if any. Note that SNMP ports
cannot have backup ports. In order to select
backup port, double-click in the cell.
The subnetwork the port belongs to. In order to
select subnetwork, double-click in the cell.
Buttons:
Add
Opens a dialog where a TCP/IP or SNMP port can be added

to the port list.
Remove
Removes the select port if possible. In order to remove a
port, no NEs must be attached to this port.
Connect
Connects to the selected port.
Disconnect Disconnects the selected port.
Settings
Open a configuration dialog for the selected port.
Element map Opens an element map dialog, where ports can be changed
for individual NEs. Also, the element message timeout
can be set, globally or individually.
Subnetwork Opens a dialog where subnetworks can be created, deleted
or renamed. The default subnetwork can also be set..
1.1
Change Communication Media Settings

To change the communication settings for a specific communication port,
open the Communication dialog box from the Configuration menu. Select
the port in the list and press the Settings button. The settings dialog box
will then appear.
86
B1091 Rev. L
Configuration
1.1.1
Serial Port
The Communication Settings Dialog box lets you change the parameters
for a selected serial port.
Figure V-2
Fields:
Serial port configuration dialog box
Description
Baud Rate The number of bits transmitted per second (Default: 115200).
Data Bits The number of bits in a word of data (Default: 8)
Parity
The number of parity bits used for Forward Error Correction
(FEC) (Default: None).
Stop Bits The number of stop bits used to indicate where each word of
data ends (Default: 1).
Flow Ctrl The way to control the rate of transmission of characters or
messages on the link so the receiver always has sufficient
buffer storage recourses (Default: None).
B1091 Rev. L
87
NEW NMS
1.1.2
Modem Port
The Modem Settings dialog box is were the dial string is selected and the
driver for the local modem is configured. Press the Call Destination
Properties button to select the location of the remote modem. Press the
My Location Properties button to select the location of the local modem.
The information from My Location and Call Destination is used to
calculate a resulting dial string (phone number) to be used when connecting the modem port. This dial string is displayed at the bottom of the dialog
box.
Figure V-3
88
Modem port configuration dialog box
B1091 Rev. L
Configuration
My Locations Dialog Box
This dialog box is provided by the operating system (Windows). This is
where you set the properties of your location. This information is used to
calculate the part of the dial string that will get you an outside line
Figure V-4
B1091 Rev. L
My Locations Dialling Property Sheet
89
NEW NMS
Call Destination Dialog Box
This is where you set the properties of the remote modems location. This
information is used to calculate the part of the dial string that will get you
from the outside line to the location of your remote modem. The settings
are stored in the Windows registry under HKEY_LOCAL_MACHINE.
Figure V-5
1.1.2.1
Call Destination Property Sheet
Modem Configuration
The modem driver can be configured from two different user interfaces.
For permanent configuration use the Modems applet in the Control Panel,
select the modem and press the Properties button. For temporary configuration (the settings stay in effect for as long as NEW-NMS is running),
use the Properties button in the Modem Settings dialog in NEW-NMS.
Notice that the Modem Properties property sheet is provided by the
modem vendor and may differ depending of the modems features. All the
configuration changes are made to the modem drivers (not to NEWNMS).
The General tab of the Modem Properties dialog box displays the COM
port to which the modem is attached, the volume setting of the modem
speaker, and the maximum data rates to use with the modem. (The data rates
displayed are those supported by the COM port and the port driver, and
might not correspond to what your modem supports. When selecting the
baud rate, bear in mind that your modem might use compression to achieve
data rates that are not listed for the COM port.
90
B1091 Rev. L
Configuration
The Connection tab of the dialog box has settings for the modem baud
rate, parity method, and number of stop bits. These are the settings that will
be used to transfer data between the two modems once a connection is
made. The Connection tab also has settings to tell the modem to wait for
a dial tone before dialling, and settings for call setup call timer and
inactivity timeout. The advanced button brings up a dialog box containing
advanced connection settings. You can specify whether to use error
control protocols and compression when transferring data and whether to
use hardware or software flow control between the port and the modem.
You can also specify the low-speed modulation type to use with slow
modems (You should generally ignore this unless you are connecting at a
very low speed [1200 or 300 baud]). In the extra settings edit box you can
tell windows to send extra initialization commands to the modem during
the initialization (when the line device is opened). The modem initialization commands usually takes the form of AT command strings, and they
can be used to make the modem execute functions that are not supported
by Windows, especially if the modem is an unusual model or brand that
Windows does not recognize. The Advanced Connection Settings dialog
box also includes a check box for recording a log file, called
MODEMLOG*.TXT (where * is a wildcard), in the Windows home
directory. This is a useful feature for troubleshooting when you are having
trouble making a call.
The Option tab is displayed only from the modem configuration in NEWNMS (Not from the Control Panel). This tab contains additional settings
for dialling. Two of these options controls the display of a terminal screen
for entering modem control commands both before and after dialling.
Like the Extra Settings field in the Advanced Connection Settings dialog
box, the terminal window that is displayed allows you to manually control
the modem both before and after dialing. You typically do this by entering
AT commands in the terminal window, and then pressing F7 to send the
commands to the modem. Another setting on the Options tab is for manual
dialing. Manual dialing is useful when you are unable to dial the number
automatically. When the manual dialing is selected, Windows will prompt
you with a message box that asks you to lift the receiver and dial the number
manually. You dial and then listen to the screeching of the modem on the
other end, which indicates that it is time for the local modem to connect.
You then click the Connect button in the message box, and Windows tells
the local modem to negotiate a connection with the remote modem. You
should hang up the phone while the modems negotiate to avoid introducing
noise onto the line. The last setting in the Options tab is for status control.
Selecting this setting displays the status of the connection in a status
window.
B1091 Rev. L
91
NEW NMS
The settings in the Address and Forwarding tabs are only used when
answering calls, and are not of interest here.
1.1.2.2
Modem Call Sequence

An outbound modem call progresses through various states during its
lifetime. In the beginning, there is no call, so the call is in IDLE state. When
the phone is taken off the hook, the call enters the DIALTONE state,
indicating that a dial tone is present on the line. (If a call never reaches the
DIALTONE state, something is disconnected; either the modem is disconnected from the PC, the phone line is disconnected from the modem,
or the phone company has shut off your phone service!). When the phone
number is being dialed, the call is in the DIALING state. Once the dialing
is complete, but before the modem on the other end starts ringing, the call
is in the PROCEEDING state. When the modem on the other end starts
ringing, the call is in the RINGBACK state. (or if the line is busy, the call
enters the BUSY state.) During the negotiation phase, the state of the call
might be UNKNOWN or it might simply remain in the RINGBACK state.
Finally, if negotiation was successful, the call enters the CONNECTED
state. When a call fails to connect, or when it is disconnected for some
reason it becomes DISCONNECTED. A DISCONNECTED call usually
transitions to the IDLE state almost immediately.
Figure V-6
92
The lifetime of an outbound call.
B1091 Rev. L
Configuration
NEW-NMS displays port state and call state in the Communications
dialog box. Please note that your modem may not support all the states
(EricssonK56DTV supports IDLE, DIALTONE, DIALING, PROCEEDING, CONNECTED, DISCONNECTED and UNKNOWN). Possible status text in the Communication dialog box:
"Disconnected" : The line is closed. The call does not exist.
"Connecting (idle)" : The line has been opened, but the call state is
still IDLE.
"Connecting (disconnected)" : The call state is DISCONNECTED
but NEW-NMS is trying to reconnect.
"Connecting (dialtone)" : The call state is DIALTONE.
"Connecting (dialing)" : The call state is DIALING.
"Connecting (unknown)" : The call state is UNKNOWN.
"Connecting (ringback)" : The call state is RINGBACK.
"Connecting (proceeding)" : The call state is PROCEEDING.
"Connecting (unknown)" : The call state is UNKNOWN.
"Connected" : The call state is CONNECTED but is not displayed.
"Disconnecting (connected)" : The disconnection process has just
started.
"Disconnecting (disconnected)" : The call has been disconnected by
the remote modem.
"Disconnecting (idle)" : The line is still open and the call state is
IDLE. Trying to close the line.
Error conditions:
There are also some error conditions were an error text is displayed after
the port state. The error situations most likely to occur are:
"Connecting (resource unavailable)": Unable to open the line. The
serial port may be in use by another resource, or the modem driver
may be opened exclusively by another resource.
"Connecting (operation failed): The connection or disconnection
operation failed. NEW-NMS will automatically retry the connection /disconnection attempts using an increasing interval of time (up
to maximum 5 minutes retry interval). Please note that when disconnecting the modem port from NEW-NMS, the connection between
NEW-NMS and the local modem is broken. It may still take some
time before the connection between the local and remote modem is
broken (depending on the inactivity timer settings (=50sec?). This
means that a new connection will fail before the modem-modem
connection is reset.
B1091 Rev. L
93
NEW NMS
1.1.3
TCP/IP Port Settings

Communication Port Dialog
This dialog is used for three purposes:
Add a new TCP/IP port (optionally with specific IP port)
Add a new SNMP port.
Edit TCP/IP port settings.
Depending on the use, the dialog will have slightly different behavior.
Adding Communication Ports
The dialog looks like this:
Figure V-7
Fields:
Add Communication Port Dialog Box
Description:
Port type
Check the port type you would like to create. If TCP/IP is

checked, then the Community name is disabled, since that
settings is only relevant for SNMP ports. Check the SNMP
port in order to add a CompactLink or NetLink element, else
check the TCP/IP port.
IP address This is a list of the most recently used IP addresses. A new
IP address may be entered. The IP address must be set in
order to create a port, regardless of the selected port type.
For accessing a CityLink or NL29x element with Ethernetinterface, TCP/IP port 5070 is used. For SNMP elements,
port 161 is used.
SNMP
The community name used when requesting information
community from SNMP elements at the specified address.
94
B1091 Rev. L
Configuration
Assign to
Select the subnetwork you would like to use the port with.
Network elements found at the specified port will be added
to the selected subnetwork. If you have several network
elements with the identical Section and SU address, you
must assign them to different subnetworks. See also Sub
networks dialog.
SubnetworksLaunches the Subnetworks dialog, where subnetworks can
be added, deleted, renamed and set as default.
Editing TCP/IP Port Settings
After the port is created, it is possible to change the settings provided that
it is a TCP/IP port. SNMP port settings cannot be changed after the port
is created. A TCP/IP port can be edited by pressing the Settings button the
Communication dialog, when a TCP/IP port is selected.
It is only possible to change the IP address, port number and subnetwork,
when editing a TCP/IP port.
Specifying a Port Number for a TCP/IP Port
If you want to use a terminal server or an IP-router with RS232 interface
to access NL29x with old SU or PDH elements over TCP/IP, you have to
install NEW-NMS with the optional feature to customize which TCP-port
to use. The TCP/IP port settings dialog will then look like this:
Figure V-8
B1091 Rev. L
Add Communication Port Dialog Box with

Port number field
95
NEW NMS
1.2
Element Communication Map

To This dialog is launched from the Element map button in the Network
communications dialog box. In this dialog, you can:
Select another communication port to use with a network element.
Set individual message timeout values for the network element.
Set a global message timeout value used for all network elements.
Figure V-9
Fields:
NE Communication Media dialog box
Description:
Network element The name of the network element (NE).

Port
The port which NEW-NMS uses to communicate
with the NE. Double-click in the cell in order to
select another port, if desired.
Timeout (ms)
The message timeout used for the NE. Double-click
in the cell in order to set your own timeout value.
Note that when Use global timeout limit is checked,
then these fields are grayed out, and not editable.
Buttons:
Description:
Optimize
Calculates the optimal individual timeout limit for the

selected NEs. Note that this process may take several
minutes if NEW does not have contact with some of the
selected elements. This button is only enabled as long as
Use global timeout limit is unchecked.
Use global
When checked, the global message timeout limit will be
timeout limit used for all NEs, regardless of the individual timeout
limits shown in the list. The message timeout is set in
milliseconds.
96
B1091 Rev. L
Configuration
1.3
Auto Discover
When starting the application or selecting the Discover command from
the File menu, the auto discover function is initiated. What happens is that
NEW sends special broadcast messages to all available serial communication (COM) ports registered in the PCs operating system. This message
is sent using several different baud rates. If any correct answer is received
from an element, the Add Element dialog box is displayed where the user
can add the element to NEW.
For CompactLink elements autodiscovery is only initiated when selecting
the Discover command, see the SNMP Settings for setting up the SNMP
discovery. For manually adding CompactLink elements, select Communication from the Communication menu and press the Add button in the
Communication dialog.
Figure V-10
Add Elements
Buttons:
Add Selected:
Moves the selected elements from the left list to the

right list.
Add All:
Moves all elements from the left list to the right list.
Remove Selected: Moves the selected elements from the right list to the
left list.
Remove All:
Moves all elements from the right list to the left list.
OK:
Adds all elements in the right list to NEW and closes
the dialog box.
Cancel:
Closes the dialog box.
B1091 Rev. L
97
NEW NMS
1.4
Subnetworks Dialog
The Subnetworks dialog lets you create, delete and rename subnetworks. It
is also possible to set the default subnetwork. When a port is added, the
default subnetwork (if not changed) will contain the network elements
found on the port. All communication ports have an associated subnetwork, and all network elements reached on a specific port belongs to the
subnetwork of that port.
All Nera Q1 based NEs (NL18x, NL24x, NL29x, CityLink, NL2000)
within a single subnetwork must have unique SU-addresses (SU, Station).
Elements with overlapping SU-addresses must be allocated to different
subnetworks.
Figure V-11
Subnetworks
Buttons:
Add:
Delete:
Adds a new subnetwork.

Deletes selected subnetwork. It is not possible to delete the
default network or a network that is allocated to a port.
Set Default: Sets selected sub network as default network.
Editing subnetwork names
The name of the subnetwork can be edited by double-clicking on the

desired subnetwork. Also, if F2 is pressed, the selected subnetwork can be
edited.
98
B1091 Rev. L
Configuration
2.0
Network Element Configuration

Configuration of Network Elements is achieved using a set of propertysheets. The property-sheets are modeless, so configuration of several
different modules can be displayed simultaneously.
To open the configuration property sheets:
Select the object you want to view or change either from the Explorer View
or a Map View. Select a Configuration command either from the context
sensitive menu (right mousebutton) or from the Configuration /Edit menu.
The property sheets are divided into two categories by means of functionality:
Configuration Property sheets with Multiple Settings:
The program retrieves the current settings from the NE when the property
sheet is opened. No set-messages is sent to the element and no data is
modified in the programs data structure before the user presses one of the
property sheet buttons:
Figure V-12
Buttons on Configuration property sheets with

multiple settings
Button description:
Set:
Get:
Close:
Help:
Applies the current settings in the Network Element.

Retrieves the current settings of the Network Element.
Closes the property sheet without saving or setting any data
Displays help for the active property-page.
Changing the Settings:
1. Get the current settings from the NE by pressing Get.

The current NE settings are automatically retrieved when the property
sheet is opened.
2.Alter the settings.
3.Press Set to send the changes to the NE.
B1091 Rev. L
99
NEW NMS
Configuration Property sheets with
Single Interactive Settings:
The program retrieves the current NE settings when the property sheet is
opened.
The property sheet has no Get or Set buttons; All functional buttons are
placed in the property pages. A message is sent to the Network Element
immediately when a control is changed or a button is pressed.
Property sheet buttons:
Figure V-13
Buttons on Configuration property sheets with

single interactive settings
Button description:
Close:
Help:
Closes the property-sheet.

Displays help for the active property-page.
All property-pages have an information field at the bottom reflecting the

current status of the data shown in the property-page and the date and time
the property sheet data was retrieved from the network element.
Figure V-14
100
Configuration property sheet information field
B1091 Rev. L
Configuration
3.0
SNMP Settings
The SNMP configuration dialog box lets you configure varioius parameter
used during discovery of SNMP elements. NEW-NMS will use UDP port
162 as default for incomming traps. When the user selcts Discover from
the File menu a search for snmp agents is started. By default a local
broadcast (255.255.255.255) is used for finding SNMP elements on the
local sub net. This local broadcast will not propagate to other sub-nets and
different search-areas can be defined for searching various subnets. Each
entry in the search area table contains a start address, stop address, read
community, and set community. For the range specified a snmp message
will be sent to each ip address in that range. Configuring the SNMP settings
is done by selecting SNMP Settings from the Configuration menu.
It is possible to configure the SNMP settings of each connected element.
This is described in Element SNMP Agent settings.
Figure V-15
B1091 Rev. L
SNMP Settings
101
NEW NMS
Fields:
Description:
Get:
The community string used during discovery of

SNMP elements NOT defined in any search area.
Set:
Default Set community string for elements NOT
defined in any search area.
SNMP:
The UDP port used as destination port for discovery of
SNMP elements.
Trap:
UDP port used by NEW-NMS for receiving Traps.
Start Address: Starting IP address of the range to be searched. Format
of the address must be xxx.xxx.xxx.xxx.
Stop Address Stop IP address of the range to be searched. Stop address
must be equal or greater than start address. Format of the
address must be xxx.xxx.xxx.xxx.
Add an entry to the search area:

1 Press the Add button, an entry is added to the list. By default start
address = 0.0.0.0, stop address = 0.0.0.0, read community =
public, and write community = private.
2 To change the default values dobbel click the entry in question and enter
the wanted value.
3 To save your settings press OK.
Remove an entry from the search area:

1 Select the entry from the list.
2 Press the Remove button.
3 To save your settings press OK.
TroubleShooting
If the Trap is in use by another application NEW-NMS can not bind to the
port and error message will be displayed.
In order for NEW-NMS to receive traps the application using the port must
terminate. Common applications using the port 162 are Microsoft Trap
Service and HP Openview.
102
B1091 Rev. L
Configuration
Buttons:
OK:
Press this button to close the dialog box and save current
settings.
Cancel: Press this button to close the dialog box without saving the
current settings.
Help: Press this button to get help on the current property sheet. For
help on an item, click at the top of the dialog box, then click the
item.
Add:
Press this button to add an entry to the search area list.
Remove:Press this button to remove selected entry from the search area
list.
B1091 Rev. L
103
NEW NMS

104
B1091 Rev. L
Performance
SECTION VI
Performance Management
B1091 Rev. L
105
NEW NMS

106
B1091 Rev. L
Performance
1.0
General
NEW-NMS contains functions for acquisition, presentation and storage
of data related to the performance of the network to be managed.
The amount of performance information and the way it is presented
depends on the network element type.
B1091 Rev. L
107
NEW NMS
2.0
RF Statistics View
Figure VI-1
RF Statistics View
In the graph, the horizontal axis represent the input level in dBm (AGCvoltage for NL18x) and the vertical axis represent cumulative probability.
The cumulative probability is given by number of samples / total number
of samples.
To Open the RF Statistics View for a specific node:
The RF Statistics view can only be opened for nodes with RF input level
Analog values.
The following list shows the nodes for different equipment:
CityLink:
Element\Equipment\ODU\Antenna\Rx
NL 29x:
Element\Equipment\Radio Rack\RCVR
NL 24x:
Element\Equipment\Rack\Transceiver
NL 18x:
Element\Equipment\Rack\Transceiver
108
B1091 Rev. L
Performance
To open the view, select the node containing RF Statistics in the
explorer view and select RF Statistics from the Performance menu or
the Context menu.
To start polling:
In the Polling interval field in the view set the polling interval in
seconds.
Push the Start Polling button to start polling.
The polling will start for this node only. The operation must be repeated for each node RF statistics are to be collected.
If polling is started on several nodes on one element, the polling
interval will be the same for all nodes. To change polling interval, stop
polling, change the polling interval value and restart polling.
The chart will appear after polling is started the first time, but no graph
will appear until fading has occurred.
To copy the chart to the Clipboard:

The chart can be copied to the clipboard if the view has focus and Copy
(Ctrl+C) is selected from the Edit menu. The chart can then be pasted
into a Word document or equal.
To stop polling:
To stop polling, push the Stop Polling button. The collected data will
be resident in the node, and if the polling is restarted the new data will
be added to the old data.
If the network is saved, the data will be saved. The data can be removed
from the node by pushing the Delete Stat Button.
B1091 Rev. L
109
NEW NMS
3.0
3.1
Logging Performance Events

Performance Log Manager
Administration of the Performance log is done from the Performance Log
Manager, which can be displayed by selecting Performance Manager in
the Database menu. Users can monitor and store performance events
through NEW-NMSs performance logging features. NEW-NMS collects performance events from the whole network.
Figure VI-2
110
Performance Log Manager
B1091 Rev. L
Performance
Fields:
Description:
Operational state:
Choose the operational mode of the performance

logging.
Choose what to do when performance log file is
full.
Wrap: Overwrites the oldest record when log file
has reached its maximum size, so that the
log size remains constant.
Halt: Halts logging when log file has reached
its maximum size.
The maximum number of kilobytes in the
performance log. (Editable)
The current number of kilobytes in the
performance log file.
The alarm threshold value. When the size of the
performance log exceeds this value, an alarm is
generated.(Editable)
Shows the current log size in a visual manner.
The alarm threshold value is shown as a red line.
Log Full action:
Max. no of
records required:
Current no. of
records:
Alarm threshold:
Percentage bar:
Buttons:
View:
Discriminator:
B1091 Rev. L
View the contents of the performance log file.

Choose which performance measurement
intervals to be collected and stored in the database.
111
NEW NMS
3.2
Viewing the Performance Log

The Performance Log View is a presentation of the performance database
in list-form. Performance measurements are shown as rows. The column
headers are the same as the database field names. This view is sizable. The
initial size is the minimum allowed size. When sizing the window, the
performance measurement list is also sized. The buttons that are positioned below the list follows the frame when sizing.
The Performance Log View can be opened with the following actions:
Select Log View from the Performance menu.
Select Performance Log from the View menu.
Press the Log View button in the Performance Log Manager
dialog
Figure VI-3 Performance Log View
Fields:
Description:
Log Id
Sec
SU
Node
Type
Source
Interval
SES
The log identifier of the performance measurement.

The supervisory unit which identifies the NE.
The NE node where the measurement was performed.
Type of interface; G.821 or G.826.
B1, B2 or M1 REI.
The measurement interval (15min, day or month)
Severely Errored Seconds - a one-second period with
one Errored Block Overstep (EBO) and/or one Severely
Errored Overstep(SEBO)
Unavailable Seconds
Background Block Error
UAS
BBE
112
B1091 Rev. L
Performance
ES
Status
Time NE
Time PC
Node Address
Agent Name
Network
Errored Second - a one-second period with one or more

Error Blocks (EB).
The status of the performance measurement.
The time the performance data was registered in the NE.
The time the performance data was fetched from the NE.
The address of the NE.
The name of the machine logging the performance
measurement.
The network on which the measurement was performed.
Buttons:
Filter
Displays the filter dialog box, where the user may select,
create or redefine a filter that reduces the amount of data
presented in the view.
Columns
Filter
Displays the filter dialog box, where the user may select,
create or redefine the filter that determines the set of
performance events listed in the view.
The filter
Displays the currently selected filter, and enables the
drop list
user to rapidly change filter, without entering the filter
dialog box.
Auto refresh
performance measurements at regular intervals.
Max. lines per Limits the maximum number of performance measuregrid page
ments displayed on a page in the list. Used to reduce
database access time. The list may contain many pages.
Navigation
Use the navigation buttons to move the selection in the
buttons
performance list. When the selection is moved to the
Refresh
Query for new performance measurements matching
the current filter and settings.
Report
Opens a Performance Report application which generates a report from the performance measurements matching the current filter. This action is independent of the
Max. lines per grid page setting.
Help
B1091 Rev. L
113
NEW NMS
Operations
dropped.
The visibility of the columns is set in the Columns dialog, which is
opened by pressing the Columns button.
When the view is closed, most of are settings is stored. These settings
include columns settings, filter name, and auto refresh. When the view is
opened the next time, the settings will be applied to the view, even if NEWNMS has been shut down in the mean time.
3.2.1

See Section IV Chapter 5.2.
114
B1091 Rev. L
Performance
3.3
Performance Log Discriminator

The Performance Log Discriminator selects which performance measurement intervals to be collected and stored in the database.
Figure VI-4
Performance Log Discriminator
To add performance events to the current performance file:

Check ( ) the categories you want to log for each NE.
B1091 Rev. L
115
NEW NMS
3.4
Filtering
filtering security- and fault-logs. All the filter categories are working
together to limit the database search criteria; the records must accommodate all the categories criteria in order to be included in the resulting
recordset.
Figure VI-5
116
Performance Filter
B1091 Rev. L
Performance
1. Nodes:
Specific set of Network Element nodes to collect information from. The
left tree-control displays all NE nodes, and the right one displays the
selected NE nodes.
The buttons for selecting and deselecting nodes:
Add Selected
Adds the selected nodes.
Add Hierarchy
Adds the selected node plus all sub-nodes under
Add All
Adds all nodes in the network.
Remove Selected Removes the selected nodes.
Remove Hierarchy Removes the selected node plus all sub-nodes
under the node (recursive).
Remove All
Removes all nodes in the network.
2. Interval (performance log):
Select intervals (15min, day and/or month) to be included in the query.
3. Time:
spinbuttons). The period of time is specified by a From time and a To
B1091 Rev. L
117
NEW NMS

118
B1091 Rev. L
Security
SECTION VII
Security Management
B1091 Rev. L
119
NEW NMS

120
B1091 Rev. L
Security
1.0
General
NEW handles security partly by means of security functions in NEW and
partly by access control by the Network Elements and supports the main
security features of ITU-T recommendations X.736, X.740, X.741 and
X.800.
The system controls security by:
User names
User groups with several levels of privileges
Passwords for both user and group
Access control for Mediation device and Network Elements
NEW contains functions for logging operator interactions as well as user
authentication.
The security in NEW is divided into two categories:
Program security:
Protects against unauthorized editing of network files, management of
logs, and other saved network information. In addition it protects
elements that do not have built-in security features, i.e. the NL29x,
NL24x and NL18x series radios.
Element security:
Protects against unauthorized configuration, settings, fault and
performance monitoring on individual elements.
2.0
User Levels and Privileges

NEW has four levels of privileges. A higher order level will have access
to all the lower order functions in addition to those specific to the level.
User level
Privileges
Passive Users Passive users are only able to monitor data. They are not
able to change the network configuration.
Active Users Active users are able to collect data and change some
communication settings, but not commands that can make
unrecoverable configuration changes.
Master Users Master users have access to all NEW commands, except
those attended with user account administration.
Admin Users Admin users have access to all NEW commands. The Admin
user is the administrator and will be responsible for adding,
deleting and managing user accounts and privileges.
B1091 Rev. L
121
NEW NMS
3.0
3.1
Logon
Logging into NEW-NMS,
Server and Stand-alone Versions
This Logon dialog is displayed when starting NEW-NMS Server or StandAlone, and when File-New is invoked from the menu.
Figure VII-1
122
The Logon Dialog Box, Server and Stand-alone Version
Fields:
Description:
Username
The user name you have been given. A NEW-NMS

user with Admin rights must create an user account
for each user allowed into NEW-NMS.
Password
The password you have been given.
Create a new
new network
Check this to create a new empty network when you

log into NEW-NMS
Open an
existing network
Check this to open an existing network into NEWNMS. The networks can be selected from the list
below this button. Select the desired network file
before logging in, or select More Files... in order to
browse for a file not present in the list.
B1091 Rev. L
Security
Buttons:
Log on
Logs you into NEW-NMS. A valid user name, password and

database connection must have been set before you are
allowed to log into NEW-NMS.
Exit
Exits NEW-NMS.
Database Opens a dialog where you can specify your database
connection.
Help
Opens this help page.
Tips:
B1091 Rev. L
Silent logon
It is possible to log into NEW-NMS without

showing the logon dialog. In order to achieve
this, you need to specify the user name and
password as startup parameters to NEW-NMS,
and optionally the network file to open. The
startup parameters are: -Login:user:password
filename. Replace user with your user name,
password with your password, and optionally
filename with the full path to the network file
you would like to open. Note that Silent logon is
only possible when running NEW-NMS as server
or stand-alone.
Ask your system administrator on how to start a
program with startup parameters.
Open network file

without connecting
to elements
In some rare cases, you might want to open a

network file without connecting to the network
elements. This is done by starting NEW-NMS
with the startup parameter -LogonLocally. Note
that Silent logon is only possible when running
NEW-NMS as server or stand-alone.
Ask your system administrator on how to start a
program with startup parameters.
123
NEW NMS
3.2
Logging into NEW-NMS, Client Version

This Logon dialog is displayed when starting NEW-NMS Client, and when
File-New is invoked from the menu.
Figure VII-2
The Logon Dialog Box, Client Version
Fields:
Description:
Username
The user name you have been given. A NEW-NMS user with
Admin rights must create an user account for each user
allowed into NEW-NMS.
The password you have been given.
Select the name of the NEW-NMS server you would like to
connect to, or enter the name of a NEW-NMS server if not
present in the list.
Password
Server
Buttons:
Log on
Exit
Help
124
Logs you into NEW-NMS. A valid user name, password and

server must have been set before you are allowed to log into
NEW-NMS.
Exits NEW-NMS.
Opens this help page.
B1091 Rev. L
Security
4.0
4.1
User Administration
Adding Users
(Requires Admin user privileges)
Adding a user to the network is the process of giving a user user ID,
password and user level on some or all the elements in the network. This
is done from the add user dialog box, which can be displayed by selecting
Add User in the Security menu. To add a user, fill out the fields in the
dialog box, choose user level on the different elements shown in the list
and press Apply or OK.
Figure VII-3
B1091 Rev. L
Add User Dialog Box
125
NEW NMS
Fields:
Description
User ID:
Here you type in the ID which will identify the user

in the Network. The ID must be maximum 8 characters long, and can contain any letter or number.
REMEMBER: The user ID is case-sensitive.
Password:
Here you type in the users default password. The

password has to be between 8 and 12 characters,
and can contain any letter or number. The user
should change his/hers password the first time he/
she logs on to the Network.
REMEMBER: The password is case-sensitive.
Confirm password: Here you type in a confirmation of the users

default password. This MUST be the same as in the
password field, otherwise NEW will NOT add the
user.
REMEMBER: The Confirm password is casesensitive.
Setting the user level:

To set user level; choose one or more elements from the elements list and
push the + and - buttons to increase or decrease the user level. It is possible
to give a user different level on different elements, but it is recommended
that a user has the same level throughout the network.
126
B1091 Rev. L
Security
4.2
Editing Users
Editing a user is the process of editing the password and/or the different
user levels for a chosen user ID. This is done from the Edit User dialog
box, which can be found by selecting Edit user in the Security menu. To
edit a user, choose a user ID from the drop-down list, change the password
and/or the user levels in the dialog box, and press Update or OK.
Figure VII-4
B1091 Rev. L
Edit User Dialog Box
127
NEW NMS
Fields:
Description:
User ID:
Here you choose one of the IDs in the Network.
Password:

password has to be between 8 and 12 characters, and
can contain any letter or number. The user should
change his/hers password the first time he/she logs
on to the Network.
Confirm password: Here you type in a confirmation of the users

default password. This MUST be the same as in the
password field, otherwise NEW will NOT add the
user.
Setting of the user level:

To set user level, you choose one or more elements from the elements list
and push the + and - buttons to in- or decrease the user level. It is possible
to give a user different level on different elements, but it is recommended
that a user has the same level throughout the network.
128
B1091 Rev. L
Security
4.3
Deleting Users
Deleting a user from the Network is the process of removing the user from
some or all the elements in the network. This is done from the Delete User
dialog box, which can be displayed by selecting Delete User in the
Security menu. To delete a user, choose the user ID from the drop-down
list in the dialog box, select the network elements you want to delete the
user from and press Delete.
Figure VII-5
Fields:
Delete User Dialog Box
Description:
User ID: A drop-down list containing all the user IDs in the entire network.
B1091 Rev. L
129
NEW NMS
4.4
Changing Password
Changing your password is done from the Change Password dialog box,
which can be displayed by choosing Change Password from the Security
menu.
To change your password, fill out the fields in the dialog box, and press OK.
Figure VII-6
Change Password Dialog Box
Fields:
Description:
Old Password:
Here you type in your old password. The password

has to be between 8 and 12 characters, and can
contain any letter or number. The user should change
his/hers password the first time he/she logs on to the
Network.
Password:

password has to be between 8 and 12 characters, and
can contain any letter or number. The user should
change his/hers password the first time he/she logs
on to the Network.
Confirm password: Here you type in a confirmation of the users default

password. This MUST be the same as in the password
field, otherwise NEW will NOT add the user.
130
B1091 Rev. L
Security
5.0
5.1
Logging Security Events

Security Log Manager
Administration of the Security log is done from the Security Log
Manager Dialog box, which can be displayed by selecting Security
Manager in the Database menu. An administrator can monitor and store
user activity through NEWs security logging features. NEW collects
security events from the whole network. Security events are user actions.
If security logging is enabled when closing NEW, security logging will
automatically start when starting NEW.
Figure VII-7
B1091 Rev. L
Security Log Manager Dialog Box
131
NEW NMS
Fields:
Description:
Operational state:
Choose the operational mode of the security logging.
Log full action:
Choose what to do when the security log file is full.

Wrap: Overwrites the oldest record when log file
has reached its maximum size so that the
log size remains constant.
Halt: Halts logging when log file has reached its
maximum size
Max. no. of
records required:
The maximum number of records in the security log.

(Editable)
Current no. of
records:
The current number of records in the security log.
Alarm threshold:
The alarm threshold value. When the size of the

security log exceeds this value, an alarm is
generated.(Editable)
Percentage bar:
Shows the current log size in a visual manner. The

alarm threshold value is shown as a red line.
Buttons:
View:
132
View the contents of the security log file.
B1091 Rev. L
Security
5.2
Viewing the Security Log

The Security Log View is a presentation of the security database in listform. Security events are shown as rows. The column headers are the same
as the database field names. This view is sizable. The initial size is the
minimum allowed size. When sizing the window, the event list is also
sized, letting the user view a smaller or larger portion of the list. The
buttons positioned below the list follows the frame when sizing.
The Security Log View can be opened with the following actions:
Select Log View from the Security menu.
Select Security Log from the View menu.
Press the Log View button in the Security Log Manager dialog
Figure VII-8
B1091 Rev. L
Security Log View
133
NEW NMS
Fields:
Description:
Log ID
Sec
SU
NE
NE Log Id
User Id
Operation
Status
Time NE
Millisec NE
Time PC
Time PC Milli
Agent Name
Network
The identifier of the logged security event.

The supervisory unit which identifies the NE.
The element name.
The identifier of the event in the NE log.
The user ID (user name).
The performed event.
The status of the event.
Time stamp (date and time) set by the NE.
The millisecond part of Time NE.
Time stamp (date and time) set by the PC.
The millisecond part of Time PC.
The name of the machine logging the security event.
The network on which the security event occurred.
Buttons:
Filter:
Displays the Filter Dialog box, where the user may

select, create or redefine a filter that reduces the
amount of data presented in the view.
Columns
Filter
Displays the filter dialog box, where the user may
select, create or redefine the filter that determines
the set of security events listed in the view.
The filter drop list Displays the currently selected filter, and enables the
user to rapidly change filter, without entering the
filter dialog box.
Auto refresh
security events at regular intervals.
Max. lines per
Limits the maximum number of security events disgrid page
played on a page in the list. Used to reduce database
access time. The list may contain many pages.
Navigation buttonsUse the navigation buttons to move the selection in
the event list. When the selection is moved to the
Refresh
Query for new security events matching the current
filter and settings.
Help
134
B1091 Rev. L
Security
Operations
dropped.
The visibility of the columns is set in the Columns dialog, which is
opened by pressing the Columns button.
When the view is closed, most of its settings are stored. These settings
include columns settings, filter name, and auto refresh. When the view is
opened the next time, the settings will be applied to the view, even if NEWNMS has been shut down in the mean time.
5.2.1

See Section IV Chapter 5.2.
B1091 Rev. L
135
NEW NMS
5.3
Filtering
filtering performance- and fault-logs.
All the filter categories are working together to limit the database search
criteria; the records has to accommodate all the categories criteria in
order to be included in the resulting recordset.
Figure VII-9
136
Security Filter
B1091 Rev. L
Security
1. NEs:
Specific set of Network Elements to collect information from. The left
tree-control displays all network elements, while the right one displays
the selected NEs.
The buttons used for selection and deselection of nodes:
Add Selected
Adds the selected NEs.
Add All
Adds all NEs in the network.
Remove Selected
Removes the selected NEs.
Remove All
Removes all NEs in the network.
2. Time:
spin buttons). The period of time is specified by a From time and a To
B1091 Rev. L
137
NEW NMS
This page is intentionally left blank.

138
B1091 Rev. L
Database
SECTION VIII
Database
B1091 Rev. L
139
NEW NMS

140
B1091 Rev. L
Database
1.0
1.1
NEW-NMS Database Introduction

General
NEW-NMS logs incoming events from monitored equipment to a database engine. A database engine is the core process that a database
management system, such as SQL Server or Oracle, uses to store and
maintain data. In general terms, engines typically serve two main purposes:
The first is to store information, and the second is to process requests for
stored information. Requests to retrieve or alter stored data are often called
database queries.
NEW-NMS stores information in a number of tables managed by a
database engine:
the fault log where equipment alarms from the network elements
are stored
the performance log where information about bit errors are
stored at user configured intervals
the security log where configuration changes are tracked.
In addition, a few tables with information related to NEW-NMS configuration are also stored in the database.
Note that data are also logged locally at the elements. In the configuration
dialogs for the element these logs can also be managed. However, the best
way to look at these is as buffers storing data if the element and NEWNMS should temporarily lose contact.
1.2
Supported Database Engines

NEW-NMS interfaces to two types of database engines:
Microsoft SQL Server,

Oracle Server.
Microsoft SQL Server is a client-server database management system.

Unlike file-based databases, a client-server database engine is a standalone application (sqlserver.exe) that manages read-write operations to
the database. Because of this, it can handle many concurrent users and
greater amounts of data (in theory several TB) - in practice only limited by
hardware (disk space and cpu power). Microsoft comes bundled with tools
(Enterprise Manager) to manage backups and perform many other database
maintenance and configuration tasks in a safe manner.
B1091 Rev. L
141
NEW NMS
If you do not have MS-SQL currently installed, but plan to do so at a later
stage, you can use the MSDE replacement, which is bundled with NEWNMS. The NEW-NMS companion, NEW-NMS SQL Manager makes it
possible to set up the database tables and perform a few simple management tasks on the database without resorting to the Microsoft SQL Server
- Enterprise Manager or similar tools. However, it cannot help you with
on-line backups or other advanced maintenance or configuration tasks.
With MSDE the total database capacity is limited to 2GB of data.
Oracle Server is supported by NEW-NMS from version R7A. This is a
high-end system similar to Microsoft SQL Server. Another criteria, which
might be of importance when picking the right database, is of course
availability of personnel with database administration skills. If Oracle
certified personnel is available, there is no reason to use Microsoft SQL
server.
1.3
Database Size
The database size depends on several factors:
How much data are logged by the NEW-NMS per time unit.
How much historical data are required for statistics.
The first item is determined by network size of the network, network
architecture, types of network elements and finally on user configuration.
The most significant user configurable parameters are tresholds at which
alarms are being generated and also performance logging activities. The
second item can be determined by setting wrap limits on the various logs.
In order to estimate the hardware requirements, it is important to estimate
the amount of data logged by the system.
10 000 fault alarms adds about 2MB of data to the database. How many alarms
are produced is determined by how alarm thresholds are set up on your radio
network, network architecture, type of network elements, weather conditions and so on. As an example, a worst case system with very high fading
statistics, NL29x, 1+1 configuration, 19NEs with few multiplexers. (many
regenerators) may produce up to 20000 alarms per 24 hours. Ideally there
should not be any alarms at all, in a real life environment there will always be
a few, though hopefully not as much as in the mentioned example.
However, when it comes to the performance log, it is a different story. If
you set up performance data to be logged every 15 minutes, it will be
logged every 15 minutes regardless. Every 10 000 performance records
add about 2,5MB of data to the database. Now, for example on a NL290 7+1
142
B1091 Rev. L
Database
link, you have 8 data channels in two directions. Logging performance on
100 elements, every 15 minutes when every channel might produce 4 log
records per polling interval, 4 times an hour, 24 hours a day, 365 days a year
amounts to roughly 224 256 000 records or 56GB! Such amounts of data are
hard to handle even for relatively powerful systems. Thus, one should take
caution how the logging activities are configured when estimating hardware
requirements.
If possible, one should always minimize the amount of performance data
logged. Very little information is lost in a daily or monthly logging period.
15 minutes interval should be used only if one is trying to pinpoint
problems in time on specific hops.
1.4
When a Log is Full

First of all, for each of the three event log managers (fault, performance and
security), it is possible to set the maximum number of records to keep in the
corresponding database table/log. Therefore, the statement the log is full
does not mean that the size of the database has reached its physical limit, but
that the number of records in the log has exceeded the given maximum number
of records.
So, why it is desirable to limit the number of records?
To limit the physical size of the database; Some database systems like
MSDE have a database size limit of 2GB. Also, database performance is
likely to decrease with the amount of data present
To limit the amount of historical data; The log views are used to browse
the events, and the more events there are, the more difficult it might be
to find the desired data.
What happens when the log is full? Or more precisely, what happens when
the number of records has exceeded the maximum allowed for a table/log?
NEW-NMS offers two solutions: wrap or halt.
B1091 Rev. L
143
NEW NMS
1.4.1
Wrap
Wrap occurs when all of the following conditions are met:
The number of records in a log exceeds the Maximum number of
records defined in the corresponding log manager
The maintenance time-of-day is reached. The maintenance time varies
for the different log managers, but is always at night time. Each
maintenance task has allocated a one hour time slot to perform its
work.
If not all conditions are met, logging continues as normal.
Wrap is performed by deleting the oldest events, until the number of
records in the log equals the maximum number of records set in the Log
Manager dialog.
1.4.2
Halt
Halt occurs when all of the following conditions are met:
The number of records in a log exceeds the Maximum number of
records defined in the corresponding log manager
The maintenance time-of-day is reached. The maintenance time varies
for the different log managers, but is always at night time.
If not both conditions are met, logging continues as normal.
NEW-NMS halts logging by setting Operational State to Disabled in the
Log Manager. Further events will the not be added to the log. The events
will not be visible in the corresponding log view either. As far as fault
events are concerned, NEW-NMS will still apply the correct alarm color
in the explorer view to the node which generated the event, and it will be
possible to view the local alarms for a specific node.
If halt occurs, you have two choices:
Increase the maximum number of records for the log manager, and set
Operational State to Enabled in the Log Manager.
Switch to a new database, and optionally backup/copy your old database, see Database Maintenance
144
B1091 Rev. L
Database
1.5
Create Your Own Reports

There are many reporting tools for the database engines supported by
NEW-NMS. Even Microsoft Office programs like Access and Excel have
facilities to retrieve up to 65535 rows from a custom database query.
The current database schema is not normalised and should be relatively easy
to understand.
Excel cookbook:
On the main menu, choose Data|Get External Data|Create New Query.
Choose your database engine connection and click OK to launch

Microsoft Query.
Choose your database and the log you want to analyse in the Add Tables
Dialog, press Add and Close
B1091 Rev. L
145
NEW NMS
Choose the fields you want or even create SQL queries. (You can even
join results from the performance log and the faultlog.)
146
B1091 Rev. L
Database
Choose File|Return data to Excel In The Returning Data to Excel dialog
box press OK. Now, back in Excel, you can present graphs on the
information as you please.
B1091 Rev. L
147
NEW NMS
2.0
2.1
Database Configuration
Configuration of NEW-NMS Database Systems
When NEW-NMS is installed, the MSDE database engine is automatically
installed if MS SQL Server or MSDE is not installed on the system.
When running MS SQL Server there are some configuration issues to be
considered.
2.1.1
Configuring an SQL Server Database
2.1.2.1
Memory Considerations
SQL Server is designed to grab as much memory as possible. If SQL Server
is installed on the same PC as NEW-NMS, the two applications will
compete for memory. This may have influence on NEW-NMS performance, and you should adjust max server memory. Use the following
procedure:
Open SQL Enterprise Manager
Select the correct database server in the explorer (Console
Root\Microsoft SQL Servers\SQL Server Group\ <Server>) Right
click on the server and select Properties. A configuration dialog
is displayed.
Select the Memory tab.
Make sure the option Dynamically configure SQL Server
memory is selected.
Set Maximum to 60% of available physical memory.
Press OK.
If you have SQL Server installed on a separate PC, the above procedure is
only necessary if you have other memory intensive applications running
there (which you shouldnt).
On the database server, you should also use Virtual Memory in the
Control Panel to make sure that the amount of virtual memory at least 1.5
times the amount of physical memory available.
148
B1091 Rev. L
Database
2.1.2.2
Fragmentation
During a period of time, the data stored in the database files will no longer
be stored sequentially on the hard drive, but the files will be placed in many
chunks distributed all over the hard drive. This process is called fragmentation, and as fragmentation increases, SQL Server performance will
decrease, since it needs to search more after the desired data. Fragmentation can be prevented by shrinking the database, and fortunately, SQL
server can do this automatically. There are two ways SQL Server can do
this; auto shrink and scheduled shrink. Nera recommends using auto
shrink. Auto shrink is ON by default.
The Auto Shrink setting can be changed using the following procedure:
Select the correct database in the explorer (Console Root\
Microsoft SQL Servers\SQL Server Group\<machine>\
Databases\<database>).
Right click on the database and select Properties. A configuration
dialog is displayed.
Select the Option tab.
Set the Auto Shrink setting to the desired value.
Press OK.
If you would rather have a scheduled shrink, use this procedure:
Select the correct database in the explorer (Console Root\Microsoft
SQL Servers\SQL Server Group\ <Server>\Databases\<database>).
Make sure Auto Shrink is OFF, using the above procedure.
Right click on the database and select All Tasks\Shrink Database.
Check the Shrink the database based on this schedule setting
Press the Change button, and set the desired schedule. Do not
schedule this task to a time between 01.00AM and 05.00AM,
because this period is used for automatic database maintenance
tasks (like wrapping), managed by NEW-NMS.
Press OK.
B1091 Rev. L
149
NEW NMS
2..2
Oracle Configuration/Maintenance Issues

If wrap is enabled, make sure you have a rollback segment large enough
to accomodate the deletion of n records in one transaction, where n is the
maximum number of records logged in 24 hours.
Also, if a log has reached wrap-treshold, you should recreate that table
once a month or so to limit fragmentation and reclaim lost extents.
2.3
Use NTFS File System

The NTFS file system is more tolerant of both software and hardware
failures, and can handle files larger than 2 GB.
NOTE!
Do not use screen savers on database servers.
Dont run a screensaver on the database server, it can unnecessarily use
CPU cycles that should be going to your application. The only exception
to this is the blank screen screensaver, which is OK to use.
150
B1091 Rev. L
Database
3.0 Backup and Restore of NEW-NMS Systems

3.1
General Backup and Restore Issues

This section contains general information on backup, valid for all database
systems supported by NEW-NMS.
The backup and restore procedures described below, are only only
for NEW-NMS databases, not for databases other applications may
use.
These procedures are suggested to keep a minimum level of data security
and may not suffice for more stringent requirements.
3.1.1
Why backup?
Basically, you have to backup your data if you believe that it is expensive
to loose them. The expense is not necessarily directly related to loosing
money due to the system being out of operation, but also the time spent in
order to get the system back into a desired state. But arent PCs safe
nowadays? No, they are not! PCs do crash - due to software and/or
hardware failure. You might be lucky and never experience a fatal crash,
but then again, you might experience one very soon.
The most likely component to crash is the hard drive, which inconveniently,
is the part where all your data are stored.
Suppose that you experience a hard drive crash on the PC where NEWNMS runs, and that the database becomes corrupted. What data have you
actually lost?
All fault, performance and security events.
All discriminator settings.
All user settings

Even if it is pretty fast and easy to get NEW-NMS operative with a new
database again, it will be a time-consuming task to restore all the old
settings, selected to suit your needs. And what about the monthly performance report you are supposed to produce? No, those data are lost, because
the database hadnt been backed up.
B1091 Rev. L
151
NEW NMS
3.1.2
Backup Interval
Basically, we recommend a full copy of the database once a week.
However, if major configuration changes have been made to the database,
for instance with respect to discriminator and user settings, an extra full
copy should be made.
Also, if you have made significant changes to NEW-NMS network files
(extension .net), you should back up this file. This file is changed for
instance when you add network elements, add or edit maps, or add or edit
filters.
3.1.3
Backup Equipment
Nera recommends a tape backup system as described in the NEW-NMS
Technical Specification.
However, on smaller systems using MSDE, the database could simply be
copied to a shared network disk, preferrably one which is being backed up
regularly for other purposes as well. Most networks have such disks, ask
your local network administrator.
3.1.4
Tape Rotation
We suggest that you have two backup tapes, labeled EvenWeek and
OddWeek, and that backup takes place once a week. If the week number
is even, you backup to the tape labeled EvenWeek, otherwise to the tape
labeled OddWeek. After the backup is finished, you remove the tape and
store in a secure place.
The tapes should be replaced by new ones, once a year.
3.1.5
Backup Software
SQL Server and Oracle come bundled with special backup management
tools, which can be used alone or in conjunction with 3rd party tools
capable of handling both single files (e.g. NEW-NMS net files) and
complete databases.
152
B1091 Rev. L
Database
3.2
Restore of a NEW-NMS Database

You probably hope that that the day will never come when you actually need
to use a backup - but you should expect it. If something happens to your
machine, and the database becomes corrupted, you have to restore the
database from the backup media. You will loose all data written to the
corrupted database, from the last backup until the database got corrupted,
but on the positive side, if you have done your backups, the system will be
restored to a state where you should have most of the important data.
It is important to know that the restore process:
Must be planned.
Must be practiced at regular intervals.
Must be verified.
3.2.1
Backup and Restore of NEW-NMS Files

If you have made significant changes to the NEW-NMS network file
(extension .net), do make a backup of this file as well. This file is changed
for instance when you add network elements, add or edit maps, or add or
edit filters.
To backup this file:
Find the name and location of the current NEW-NMS network.
Use Windows Explorer and copy this file to a diskette or a backed
up network drive. Make sure you label the diskette or name the
folder on the network drive in a descriptive manner.
To restore this file:
Use Windows Explorer, and copy the NEW-NMS network file to
the desired location on the local hard drive.
Open the file with NEW-NMS.
B1091 Rev. L
153
NEW NMS
3.3
Backup and Restore of an MSDE Database

An MSDE database has a logical name and is stored on a database server.
The logical name is defined by the user when the database is created with
the NEW-NMS SQL Manager. The user also decides which PC to keep the
database on, this PC will be database server. Physically, the database will
be stored on file on the server, in the folder where MSDE was installed
(default C:\MSSQL7\DATA), with the filename <LogicalName>.mdf.
3.3.1
Backing up an MSDE Database

Use the following procedure to manually backup an MSDE database:
From NEW-NMS, open the datalink dialog using the menu
command Database\Datalink. Note the logical name and the
server of the MSDE database
Close NEW-NMS
Start the NEW-NMS SQL Manager, and log into the correct
server (from 1)
Select the correct database (from 1). Right-click on the database
and select Copy database
Save the database with a new name. (Tip: use todays date in the
name, e.g. NEW_10_02_2002_BK.mdf
Start NEW-NMS again.
Use Windows Explorer and find the fresh copy of the database.
Copy the database file to the backup media.
3.3.2
Restoring an MSDE Database

Use the following procedure to restore an MSDE database (assuming that
NEW-NMS is not running):
Use Windows Explorer to copy the backup version of the database
file (e.g. NEW_10_02_2002_BK.mdf) from the backup media to
the location on the hard drive where MSDE was installed. (default
C:\MSSQL7\Data)
Optional: Rename the database file to something more descriptive.
If a database with the desired name already exists, you have to:
Start NEW-NMS SQL Manager, login to the correct server.
Right click on the database you want to delete, and select
Delete database
Now you can rename the backup version of the database file to the
desired name.
Start NEW-NMS SQL Manager, login to the correct server. Do the
menu command Task\Attach Database A dialog is displayed.
Navigate to the database directory (see 1) and select the correct
database file. Press OK.
154
B1091 Rev. L
Database
Start NEW-NMS, connect to the restored database.
3.4
Backup and Restore of an SQL Server Database

The backup and restore procedures in this section assumes that backups
are kept on tapes, written by SQL Server Enterprise manager. It is, of
course, possible to do backups to a file as well. If you backup to a file, you
should manually copy the backup file to a secure location (a tape or shared,
backed up, network disk).
3.4.1
Backing up an SQL Server Database

Use the following procedure to manually backup an SQL Server database:
Insert the appropriate backup tape (see Tape rotation)
From NEW-NMS, open the datalink dialog using the menu
command Database\Datalink. Note the database name and the
database server of the NEW-NMS database.
In the SQL Server Enterprise Manager, select the NEW-NMS
database in the explorer view (Select the Console Root\Microsoft
SQL Servers\ SQL Server Group\database server\Databases\
database name node in the tree)
From the menu, select Tools\Backup Database
The backup database dialog window is displayed.
Make sure database name is selected in the Database drop down
list.
Enter a name and description of the backup.
Make sure Database - complete is selected.
Set the Backup to: selection to Tape.
Select the appropriate tape device from the list below. If no
appropriate device is defined, you have to add one by pressing the
Add button, and create a new tape device.
Select Overwrite existing media
Select the Options page in the dialog window. Check the Verify
backup upon completion option. This will check that the contents
of the backup really matches the database.
Press OK, and the backup process will start. The backup will most
likely take some time.
After the backup is finished, remove the tape and store in a secure
place.
Press Cancel and the backup dialog window will disappear.
If you would rather backup to file, you have to use a file device instead of
a tape device. The file device is also defined by pressing Add button in the
B1091 Rev. L
155
NEW NMS
database backup dialog. The Backup to: selection has to be set to File.
With these considerations, the above procedure can be used with file
backups as well as tape backups.
3.4.2
Scheduled Backups
If you feel confident in the manual backup procedure, and the backup/
restore procedure has been tested thoroughly, you could try scheduled
backups. In the backup configuration dialog described in Backing up an
SQL Server database, you can define a schedule for the backup task.
Backing up the NEW-NMS database could then be almost completely
automated (you still have to switch tapes though).
If you configure a scheduled backup, you should avoid backing up between
01.00AM and 05.00AM, as NEW-NMS automatically performs other
database maintenance tasks in that timespan.
3.4.3
Restoring a SQL Server Database

In order to restore a backed up NEW-NMS database, use the following
procedure.
Insert the appropriate tape into the tape station.
Start the NEW-NMS SQL Manager application, and log in on the
appropriate database server.
Make a new database with the menu command Task\Database\
New database. Note the database name.
From the SQL Server Enterprise Manager, select the newly created
database in the explorer view (Select the Console Root\Microsoft
SQL Servers\ SQL Server Group\database server\databases\
database name node in the tree)
From the menu, select Tools\Restore Database
The restore database dialog window is displayed.
Set Restore to From device.
Press the Select Device button, and select the tape device. If no
tape devices exist, press the Add button, and add the tape device.
Make sure Restore backup set and Database - complete is
checked.
Select the Options page in the dialog window. Select Force
restore over existing database.
Press the Ok button, and the database is restored.
Press Cancel and the restore dialog window will disappear.
In NEW-NMS, connect to the newly restored database.
Press Cancel and the backup dialog window will disappear.
156
B1091 Rev. L
Database
If you restore from a file, you have to define and select a file device instead
of tape device. With that consideration, the above procedure can be used
with files as well as tapes.
3.5
Backup and Restore of an Oracle Database

Outlining how Oracle databases may be backed up is beyond the scope of
this document. To do this, staff with Oracle database administration skills
are required.
B1091 Rev. L
157
NEW NMS

158
B1091 Rev. L
Appendices
SECTION IX
Appendices
B1091 Rev. L
159
NEW NMS

160
B1091 Rev. L
Appendices
Appendix A - Modem Installation and Configuration

NEW-NMS can communicate with remote radios (NEs) through modems
connected to the PCs serial ports.
NEW-NMS probably works fine with most modems from the different
vendors. But since there are many different models and brands out there
having different specifications and quality, and we cannot test them all, we
decided to guarantee that NEW-NMS supports this high quality modem:
Ericsson K56DTV.
Figure IX-1
Communication with NEs through modems
Local Modem Installation

To install the modem driver, open the Modems applet in the Control
Panel and follow the instructions.
Local Modem Configuration

The local Data Terminal Equipment (DTE) is your PC (NEW-NMS) . The
local modem is configured through the modem driver installed on your
PC. This driver is also used by NEW-NMS to transmit and receive data. The
modem driver can be configured from two different user interfaces. For
permanent configuration use the Modems applet in the Control Panel,
select the modem and press the Properties button. For temporary configuration (the settings stay in effect for as long as NEW-NMS is running),
use the Properties button in the Modem Settings dialog in NEW-NMS.
Notice that the Modem Properties property sheet is provided by the
modem vendor and may differ depending of the modems features. All the
configuration changes are made to the modem drivers (not to NEWNMS). The following sections describes how to configure the Ericsson
K56DTV modem driver. For a thorough description of the Modem
Properties property sheet, see Modem Port (Section V-1.1.2).
General tab:
Select the same baudrate in this page as the baudrate set for the LCT port
on the NE connected to the remote modem. and force the modem to only
connect at this speed. This will prevent modem buffer overflow (=>message loss).
B1091 Rev. L
161
NEW NMS
Connection tab:
Data bits = 8, Parity = None, Stop bits = 1.
Sometimes, especially when not calling from a public line, the modem
may not recognize the dial tone. Then you should uncheck the Wait for
dial tone before dialing check box.
Cancel the call if not connected within 60 sec., is a reasonable value. It
usually takes about 20 to 30 seconds for the remote modem to answer the
call depending on the remote modems configuration (how many rings to
wait before answering).
Disconnect the call if idle more than 1 min. Having this low value will
make the local modem hang up and reconnect if the line is idle.
Use error control: Yes. It is also recommended to check the Force to
connect and Compress data check-boxes. This will make the connection more reliable.
Modulation type: Standard.
Extra settings: Leave this edit box blank.
Record a log file: Why not. Useful when troubleshooting.
Options tab:
Does normally not need these features.
Address tab:
Only used for inbound calls.
Forwarding tab:
Only used for inbound calls.
Remote Modem Configuration

The remote Data Terminal Equipment (DTE) is a Network Element. The
NE does not have a modem driver installed and does not support any
handshaking mechanism. Therefore the modem must be configured to
manage the connection all by itself. The remote modem must be configured using a set of AT commands. To configure your Ericsson K56DTV
follow these instructions:
Use the HyperTerminal application shipped with Windows to configure
the remote modem. Connect to the modem using the serial port that the
modem is connected to. Set the COM port speed equal to the baudrate
of the LCT port on the remote NE (This is very important because this
baudrate will be used as DTE speed when modem is connected to the
NE).
162
B1091 Rev. L
Appendices
Test connection by typing AT<cr>.
Configure the remote modem by typing this AT command sequence:
ATF&D0&K0S0=1S30=5&W0&Y0<cr> , or by typing each command
individually:
- ATF<cr> : Restores the factory default settings.
- AT&D0<cr> : Modem ignores the true state of the DTR signal and
responds as it is always on. The connection must be managed by the
modem itself and not the DTE which in this case is the NE.
- AT&K0<cr> : Flow control disabled. The DTE (NE) does not support
handshaking.
- ATS0=1<cr> : Sets the number of rings before the modem answers.
- ATS30=5<cr> : Sets the length of time that the modem stays online
before disconnecting when no data is sent or received.
- AT&W0<cr> : Saves the current configuration into NVRAM as
profile 0.
- AT&Y0<cr> : Designates profile 0 to be loaded into the active
configuration when the modem is powered up.
Verify the configuration by turning the power off and then on again, and
type AT&V<cr> to display the active configuration.
Connect the modem to the NE. Check that the LCT port of the NE is
configured with the same baudrate as your HyperTerminal connection
was.
Troubleshooting
Call status is "resource unavailable": The serial port that the modem is
using may be in use by another application or by another serial port or
modem port in NEW-NMS. Close the other resources that are using the
same serial port.
Call status is operation failed:
- Reset local modem (turn off and on power).
- If resetting the local modem did not help, check the ModemLog*.txt
file in the Windows directory to see if any errors are reported and the
local modem is correctly initialized.
- Uncheck the Wait for dialtone check-box in the modem driver
configuration. The modem may not recognize the dialtone of your
line.
- Check the remote modem configuration.
- See the Troubleshooting section in your modems user manual.
B1091 Rev. L
163
NEW NMS
- Perform modem loop tests described in your modems user manual.
- Check if your modems default settings for line specifications (dial
character spacing, time modem waits to after off-hook till begins
dialling, etc.) are matching the specifications of your line.
Modem port is connected but no messages seems to be received from
the remote NE:
- Check that the baudrate of the local modem driver is correct. (You
may have disconnect and try some different baudrates).
- Reset local modem (turn off and on power).
- Reset remote modem. (hopefully remote is not too far away).
- Check RS232 cable connection between NE and remote modem.
- Check the baudrate settings of the NEs LCT port.
- Use HyperTerminal with the same serial port speed that your LCT port
has. (The DTE baudrate of the remote modem will be set to the same
baudrate of the last AT commands received). Check the active remote
modem settings by typing AT&V<cr>.
Modem port is connected. Some messages are received from NE, but
there seem to be a lot of timeouts and errored messages:
- The line quality of the modem to modem connection is not good
enough for the baudrates that are specified. You may have to use a
lower baudrate.
- Check that your modems are configured to use an error correction
protocol and compression.
- Disconnect and then reconnect: This may get you a different route
through the telephone network and also a better line quality.
164
B1091 Rev. L
Appendices
Appendix B- Configuration of NL29x, NL24x & NL18x

1.0
Element ID (NL29x, NL24x, NL18x)

The Element Id property sheet shows some main information about the
Network Element like name, type, serial number and different addresses.
The fields with white background can be altered by users with proper user
privileges. The gray fields are non editable.
Figure IX-2
Fields:
Element Id Property Sheet
Description:
Serial Number: The serial number of the NE. (not editable)

NE Type:
The type of NE , e.g. NL18x Repeater (not editable)
Name:
The name of the NE (max. 32 characters)
Section Address: The section address of the NE. (1-254)
NE Address:
The NE address (1-128). Used for identification of
NEs within a section
Buttons:
Get:
Set:
Press this button to send the settings to the NE. Only the name is
changeable, and it will be stored in NEW, not in the NE.
Close: Closes the property sheet.
Help: Press this button to get help on the current property sheet page.
click the item.
B1091 Rev. L
165
NEW NMS
2.0
Channels (NL29x)
The Channels property sheet displays some channel specific configuration parameters.
Figure IX-3
Channels Property Sheet
Fields:
Description:
Channels:
Type:
Termination:
Channel P, 1, . . ., N
Channel type; STM-1 (155Mbit/s) or PDH (140Mbit/s)
Only present for terminal stations.
MS (Multiplexer Section) or RS (Regenerator Section)
Buttons:
Get:
Set:
click the item.
166
B1091 Rev. L
Appendices
3.0
Equipment (NL29x, NL24x, NL18x)

The Equipment property sheet displays some general equipment information. The amount of information displayed depends on the element
type.
Figure IX-4
Equipment Property Sheet
Buttons:
Get:
Set:
For help on an item, click at the top of the dialog box, then click
the item.
B1091 Rev. L
167
NEW NMS
4.0
Manual Switching (NL29x, NL24x, NL18x)

The Manual Switching property sheet lets the user perform protection
switching, and shows the current switching status. For NL29x radios
manual switching can be performed on terminals. For NL24x and NL18x
radios manual switching can be performed on terminals and add/drop
repeaters.
NL29x specific: Manual switching can only be done on terminals. Switching of traffic going from Terminal A to Terminal B within a single section
may be performed as a TX direction request on Terminal A, or as a RX
direction request to Terminal B.
NL24x and NL18x specific: Manual switching can be performed on
terminals and add/drop repeaters. Switching of traffic going from Terminal A to Terminal B within a single section may be performed as a RX
direction request to Terminal B.
Figure IX-5
168
Manual Switching Property Sheet

B1091 Rev. L
Appendices
Fields:
Description:
Channel:
None = restore, 1...N = the channel to be

switched to protection.
The switching mode:
- Errorless: switching will be performed errorless if
possible to align the channel with the protection channel.
- Forced: Protection switching will be performed regardless whether the channels are aligned or not.
- Relay: Switching will always result in a short period with
Loss-Of-Frame in the selected channel (only available on
NL29x radios).
- Low priority: Switching will be acknowledged only if no
other channel requires the protection channel.
- High priority: Any other channel using the protection
channel will be restored.
Displays the current status of the protection system (i.e.
the channel currently using protection, alignment
indicator, and some alarms)
Mode:
Switching
status:
Buttons:
Switch: Sends a switch or restore message to the NE using the selected
channel and mode.
Get:
(The settings are automatically retrieved from the NE when the
property-sheet is opened and if status is changed).
Set:
Is always disabled.
click the item.
B1091 Rev. L
169
NEW NMS
5.0
Switching Configuration (NL29x, NL24x)

The Switching Configuration property sheet displays the settings of the
protection system. The data is displayed using three property pages.
170
Figure IX-6
Switching Configuration Property Sheet, General Tab
Figure IX-7
Switching Configuration Property Sheet, Priority Tab
B1091 Rev. L
Appendices
Figure IX-8
Fields:
Switching Configuration Property Sheet, Alarm Input
Description:
Switch limit: Defines which criteria that should cause automatic

protection switching
Restore limit:Defines which criteria that should cause automatic
protection re-switching
B1091 Rev. L
Standby
channel:
Defines how the protection channel is to be used when no

protection switching is required. (When the protection
channel is available). Essentially this defines the setting
of the XSU in a quiescent system. By setting the
protection channel as standby channel it may be used for
occasional traffic. Dynamic means that the channel last
using protection is used as standby channel.
Alignment
time out:
Defines the maximum time allowed for a switching task to

wait for Aligned indication from the ASF.
Manual
switching
access:
Defines access restrictions on manual switching operations.

This configuration applies to the MASTER only. Thus, a
request for manual switching in TX direction (SLAVE
manual request) will be checked against the switching access
restrictions of the opposite (RX) terminal.
171
NEW NMS
Channel
priority:
Defines priority among the regular radio RX channels.

Higher priority channels will get access to the protection
channel if used by a lower priority channel. Setting the
priority to zero implies that the channel is denied access
to the protection channel. Highest priority in a N+1
system is N. Lowest priority is zero. Several channels
may have equal priority.
Alarm input: Defines the input pattern to be used as input mask for the
hardware alarm interface of the RPS system. There is one
mask for each channel. A checked cell means that the
corresponding alarm is not masked but included.
Buttons:
Get:
Set:
the item.
172
B1091 Rev. L
Appendices
6.0
Power (NL29x;NL24x)
The Power property sheet displays the Automatic Transmitter Power
Controllers settings. For a repeater the ATPC settings in both directions
are shown.
Figure IX-9
Fields:
Power Property Sheet
Description:
Mode MTPC/ATPC: Manual Transmitter Power Control or

Automatic Transmitter Power Control
Attenuation:
The manual attenuation. Only changeable
when MTPC is selected
Reference Level:
The reference level used in ATPC
Buttons:
Get:
Set:
the item.
B1091 Rev. L
173
NEW NMS
7.0
Power (NL29x)
The Power property sheet displays the Automatic Transmitter Power
Controllers settings. For a repeater the ATPC settings in both directions
are shown.
Figure IX-10
Power Property Sheet
Fields:
Description:
ATPC On/Off The ATPC function can be turned off or on

Output effect: Different types of ATPC regulations may be selected:
- Maximum: Uses maximum output power.
- Minimum: Uses minimum output power.
- Automatic: Regulates the output power.
- Freeze output power: Locks the current output power.
Alarm delay: The time in seconds that an alarm condition must last
before it becomes alarm
Buttons:
Get:
Set:
click the item.
174
B1091 Rev. L
Appendices
8.0
NE Clock
The NE Clock sheet lets you synchronize the Network Element Date/Time
with the NEW-NMS / PC Date/Time. (The NE Clock is set to the same
date/time as the PC Clock)
The NE Clock configuration sheet can be opened from the Configuration
context menu of the Element node in the Explorer view. The sheet can
also be invoked by selecting (highlighting) the Element node in the
Explorer view and then selecting Edit NE Clock from the Configuration menu.
Figure IX-11
NE Clock Configuration Sheet
Fields:
Description:
The Elements Clock:

Difference from
NEW-NMS (your PC):
The Date and Time retrieved from the NE.

The difference between the PC clock and the
NE Clock
Buttons:
Get:
Set:
the item.
B1091 Rev. L
175
NEW NMS
9.0
Hot Standby (NL29x, NL24x, NL18x)

The Hot Standby property sheet displays the Hot Standby Controllers
settings. The Hot Standby Controller selects which transmitters in a Hot
Standby system configuration to be transmitting. The transmitters are
operating on the same frequency with the same modulation. One of the
transmitters is connected to the antenna while the other is connected to a
dummy load. Which transmitter to be connected to the antenna is dependent on the output signal quality from each transmitter. The user may also
manually force the switch to lock to one of the transmitters.
Figure IX-12
Fields:
Hot Standby Property Sheet
Description:
Auto/Manual: Auto: Uses the transmitter that has the best output signal quality.
Manual: Forces the switch to lock on one of the transmitters.
Standby Ch.: The channel to be used. (Only applicable if Manual).
Status:
The Hot Standby controllers status.
Buttons:
Get:
Set:
the item.
176
B1091 Rev. L
Appendices
10.0
SW Versions (NL29x, NL24x, NL18x)

The SW Versions property sheet displays the revision codes of the
different software modules in the NE. The software revision codes are
displayed using the format: R[rev. number][rev. code][bug fix number]
(e.g. R6A3).
Figure IX-13
SW Versions Property Sheet
Buttons:
Remote Reset Up:
Remote reset of the microprocessors on SU and

all ACUs in the up direction. Disabled on upper
terminals. NL18x and NL24x only.
Remote Reset Down: Remote reset of the microprocessors on SU and
all ACUs in the down direction. Disabled on lower
terminals. NL18x and NL24x only.
Reset SU:
Reset local SU,
Get:
Press this button to retrieve the current settings
from the NE. (The settings are automatically re
trieved from the NE when the property-sheet is
opened).
Set:
Is always disabled.
Close:
Help:
Press this button to get help on the current
property sheet page. For help on an item, click
at the top of the dialog box, then click the item.
B1091 Rev. L
177
NEW NMS
Appendix C - Configuration of CompactLink

1.0
Element ID (CompactLink)
The Element Id property sheet shows some main information about the
Network Element like name, type, and different addresses.
The fields with white background can be altered by users with proper user
privileges. The gray fields are non-editable.
The Element Id configuration sheet can be opened from the Configuration context menu of the Element node in the Explorer view.
The sheet can also be invoked by selecting (highlighting) the Element
node in the Explorer view and then selecting Edit Element Id from the
Configuration menu.
Figure IX-14
178
Element ID Property Sheet
B1091 Rev. L
Appendices
Fields:
Description
NEType:
Configuration
The type of Network Element. (Not Editable)

Equipment Configuration, i.e. Transmission rate,
redundancy (Not Editable)
The name of the Network Element.
The section address of the Network Element.
The Network Element address. Used to identify
Network Elements within a section.
The physical location of this node (e.g., telephone
closet, 3rd floor).
The textual identification of the contact person for
this managed node, together with information on
how to contact this person.
The IP address of the Network Element.
Name:
Section Address:
NE Address:
Location:
Contact:
IP Address:
To change the settings:

In order for the user to change settings the Set Community name must be
configured as described in Element SNMP settings.
1. First, get the current settings from the Network element by pressing
Get. (The settings are automatically retrieved from the NE when the
property-sheet is opened)
2. Alter the settings you want to change.
3. Press Set to send the changes to the network element.
Buttons:
Get:
Set:
Close:
Help:
B1091 Rev. L
Press this button to get help on the current property sheet. For help
on an item, click at the top of the dialog box, then click the item.
179
NEW NMS
2.0
Element SNMP Settings

The SNMP Agent(s) property sheet shows the current SNMP settings. The
Element SNMP Settings configuration sheet can be opened from the
Configuration context menu of the Element node in the Explorer view.
node in the Explorer view and then selecting Edit SNMP Settings from
the Configuration menu. All information presented in the configuration
sheet is set locally and not retrieved from the element.
NOTE! In order for NEW-NMS to manage the SNMP element the SNMP
Agent settings configured locally must match the settings in the NEWNMS. Please see Configuring SNMP agent.
NEW-NMS is using received traps for keeping an accurate element status.
SNMP Traps are unreliable and no delivery guarantee is given, to overcome this weakness a query for number of traps sent from the SNMP
element must be performed from NEW-NMS at given time intervals. If the
number of traps sent from the element is not equal to the number of traps
received from the element, traps have been lost and alarm synchronization
is needed. However, the trap count kept by the SNMP element is dependent
of how many Managers are configured as trap receivers. This information,
stored in the field No Trap Receiving Managers, is by default set to 1. For
elements configured to send traps to more than one manager, the exact
number of managers must be entered to prevent unnecessary alarm
synchronisation (CompactLink is not using this information).
Figure IX-15
180
Element ID SNMP Settings

B1091 Rev. L
Appendices
Fields:
Description:
IP Address:
The Internet Protocol address of the Network

Element (Not Editable).
Set:
The community string used when setting
information at the element (set request).
Get:
The community string used when requesting
information from element (get/getnext request).
Port:
Element UDP Port for Get/Getnext/Set
No Trap receiving Number of Managers set up to receive traps from
Managers:
this element.
Edit values in the list:

The values of the columns SetCommunity, GetCommunity, port, and No
Trap receiving Mnagers can be modified:
1. Double click cell to be edited.
2. Type new value.
3. Click outside cell.
4. To save your settings press OK.
Buttons:
Set:
Close:
Help:
3.0
Press this button to send the settings to the Network Element.

Press this button to get help on the current property sheet. For
help on an item, click
at the top of the dialog box, then click
the item.
CompactLink SNMP Agent Configuration

In order for NEW-NMS to manage the CompactLink radio the CompactLink SNMP agent must be configured. Please see the CompactLink
handbook for how this is done.
The basic parameters to be set (using the CIT Craft Interface Terminal) is
the following:
Station ID (local and remote)
Local IP address, Subnet Mask, and Default Gateway.
Access rights (community Names for Get and Set operation).
IP addresses of Management stations to receive traps.
B1091 Rev. L
181
NEW NMS
4.0
MIB II - System Info

The System Info property page shows some of the MIB-II System group
attributes. The fields with white background can be altered by users with
proper user privileges. The gray fields are non-editable.
Figure IX-16
System Info Property sheet
The Element Info configuration page can be opened from the Configuration context menu of the Element node in the Explorer view.
node in the Explorer view and then selecting Edit Element Id from the
Configuration menu.
182
B1091 Rev. L
Appendices
Fields:
Description:
Sys Description:
A textual description of the entity. This value should

include the full name and version identification of
the systems hardware type, software operatingsystem, and networking software. It is mandatory
that this only contain printable ASCII characters.
The vendors authoritative identification of the
network management subsystem contained in the
entity. This value is allocated within the SMI
enterprises subtree (1.3.6.1.4.1) and provides an
easy and unambiguous means for determining what
kind of box is being managed.
The name of the Network Element.
The physical location of this node (e.g., telephone
closet, 3rd floor).
The textual identification of the contact person for
this managed node, together with information on
how to contact this person.
The time since the network management portion of
the system was last re-initialized.
Sys OID:
Name:
Location:
Contact:
Sys Uptime:

In order for the user to change settings the Set Community name must be
configured as described in SNMP Agent(s) settings.
1 First, get the current settings from the Network element by pressing
2 Alter the settings you want to change.
3 Press Set to send the changes to the network element.
Buttons:
Get:
Press this button to retrieve the current settings from the

Network Element.
Set:
the item.
B1091 Rev. L
183
NEW NMS
5.0
Versions Page
The SW Versions property sheet displays the revisions of the different SW
modules in the NE. The Versions configuration sheet can be opened from
the Configuration context menu of the Element node in the Explorer
view. The sheet can also be invoked by selecting (highlighting) the
Element node in the Explorer view and then selecting Edit Versions
from the Configuration menu.
Figure IX-17
SW Versions
Fields:
Description
Component:
Revision:
Name of the software

Software revision code.
Buttons:
Get:
Close:
Help:
184
Press this button to retrieve the current settings from

the Network Element.
Press this button to get help on the current property
sheet. For help on an item, click
at the top of the
dialog box, then click the item.
B1091 Rev. L
Appendices
6.0
IP Address Table
The IP address Table Property Sheet displays the entitys IP addressing
information as described in RFC-1213 MIB.
The IP Address configuration sheet can be opened from the Configuration context menu of the Element node in the Explorer view. The sheet
can also be invoked by selecting (highlighting) the Element node in the
Explorer view and then selecting Edit IP Address from the Configuration menu.
Figure IX-18
B1091 Rev. L
IP Address Table
185
NEW NMS
Columns:
Description:
IP Address
The IP address to which this entrys addressing

information pertains.
If Index
The index value which uniquely identifies the interface to which this entry is applicable.
Net Mask
The subnet mask associated with the IP address of
this entry. The value of the mask is an IP address with
all the network bits set to 1 and all the hosts bit set to
0.
Broadcast Address The value of the least-significant bit in the IP broadcast address used for sending datagrams on the (logical) interface associated with the IP address of this
entry. For example, when the Internet standard allones broadcast address is used, the value will be 1.
This value applies both the subnet and network broadcasts addresses used by the entity on this (logical)
interface.
Reasm Max. size The size of the largest IP datagram which this entity
can re-assemble from incoming IP fragmented
datagrams received on this interface.
Buttons:
Get:
Close:
Help:
186

Network Element.
help on an item, click at the top of the dialog box, then click
the item.
B1091 Rev. L
Appendices
7.0
IP Routing Table
The IP Routing Table Property Sheet displays the entitys IP routing
information as described in RFC-1213 MIB. The IP routing table contains
an entry for each route presently known to this entity.
The IP Routing configuration sheet can be opened from the Configuration context menu of the Element node in the Explorer view. The sheet
Explorer view and then selecting Edit IP Routing from the Configuration menu.
By default, columns containing variables metric1-metric5, protocol, age
and info are collapsed.
Figure IX-19
Columns:
IP Routing Table
Description:
Destination The destination IP address of this route. An entry with a

value of 0.0.0.0 is considered a default route. Multiple
routes to a single destination can appear in the table, but
access to such multiple entries is dependent on the tableaccess mechanisms defined by the network management
protocol in use.
If Index
The index value which uniquely identifies the local interface
through which the next hop of this route should be reached.
B1091 Rev. L
187
NEW NMS
Columns:
Description:
Metric 1
(By default, column is collapsed)

The primary routing metric for this route. The semantics of
this metric are determined by the routing-protocol specified in the routes ipRouteProto value. If this metric is not
used, its value should be set to -1.
An alternate routing metric for this route. The semantics of
The IP address of the next hop of this route. (In the case of
a route bound to an interface which is realized via a broadcast media, the value of this field is the agents IP address on
that interface.)
The type of route. The value can be:
other(1), none of the following
invalid(2), an invalidated route
direct(3), route to directly connected (sub-)network
indirect(4) route to a non-local host/network/sub-network
The routing mechanism via which this route was learned.
Inclusion of values for gateway routing protocols is not
intended to imply that hosts should support those protocols.
The number of seconds since this route was last updated or
otherwise determined to be correct. Note that no semantics
of too old can be implied except through knowledge of the
routing protocol by which the route was learned.
Metric 2
Metric 3
Metric 4
Next Hop
Type
Protocol
Age
188
B1091 Rev. L
Appendices
Columns:
Description:
Mask
Indicates the mask to be logical-ANDed with the destination

address before being compared to the value in the ipRouteDest field. For those systems that do not support arbitrary
subnet masks, an agent constructs the value of the ipRouteMask by determining whether the value of the correspondent ipRouteDest field belong to a class-A, B, or C network,
and then using one of:
mask
network
255.0.0.0
class-A
255.255.0.0 class-B
255.255.255.0 class-C
If the value of the ipRouteDest is 0.0.0.0 (a default route),
then the mask value is also 0.0.0.0. It should be noted that
all IP routing subsystems implicitly use this mechanism.
A reference to MIB definitions specific to the particular
routing protocol which is responsible for this route, as
determined by the value specified in the routes ipRouteProto value. If this information is not present, its value
should be set to the OBJECT IDENTIFIER { 0 0 }, which is
a syntatically valid object identifier, and any conformant
implementation of ASN.1 and BER must be able to generate
and recognize this value.
Metric 5
Info
Buttons:
Get:
Close:
Help:
B1091 Rev. L

Network Element.
help on an item, click at the top of the dialog box, then click
the item.
189
NEW NMS
8.0
Trap Table
The Trap configuration property sheet displays the current registered trap
receivers. Trap receiver entries in the list are either static or dynamic.
Static entries are added using the CIT and can not be removed from the list
unless using the CIT. A Manager sending SNMP request to the agent is
automatically added to the trap receiver list as dynamic. An entry having
the property set Dynamic will be removed from the list when Last access
is greater than Time to live.
The Trap Table configuration sheet can be opened from the Configuration context menu of the Element node in the Explorer view. The sheet
Explorer view and then selecting Edit Trap Table from the Configuration menu.
Figure IX-20
190
Trap Table
B1091 Rev. L
Appendices
Fields:
Description:
IP Address: IP address of the trap receiver.

Last Access: The seconds since the last access of the trap receiver. For
dynamic entries, the trap receiver will be removed from the
list when Last Access is larger than Time to Live.
Property: -static, - never removed from trap list.
-dynamic - the entry can be removed by the agent
Time to live The time before an dynamic entry is removed if manager
does not poll the agent.

1 First, get the current settings from the Network Element by pressing
Buttons:
Get:

Network Element.
Set:
the item.
B1091 Rev. L
191
NEW NMS
9.0
Looping
The Looping table property sheet displays the current Loopback test.
The Looping configuration sheet can be opened from the Configuration
context menu of the Equipment node in the Explorer view.
The sheet can also be invoked by selecting (highlighting) the Equipment
node in the Explorer view and then selecting Edit Looping from the
Configuration menu.
Figure IX-21
192
Looping Table
B1091 Rev. L
Appendices
Fields:
Description:
Loopback
Type:
Loopback Test Options:

0 - No Loopback test.
1 - External LIU. Verifies path integrity, per channel, from
a local external source to the Line Interface Unit on the
modem and back to the local external source.
2 - Internal Remote. The local modem uses internally
generated data to propagate across the link, then loops back
at the remote DIU and back to the local modem; to verify per
channel path integrity. (Pass or fail results are reported.)
3 - External Remote. Verifies path integrity, per channel,
from a local external source to the local DIU, propagating
across the link, then loops back at remote DIU and back to
the local external source.
4 - Internal Digital Interface Unit. The local modem uses
internally generated data to verify per channel path integrity
of the local modem, while omitting the transformers and
line interface unit. (Pass or fail results are reported.)
Channel Selection used in Loopback Testing. Must be selected prior to selecting any Loopback Test. Value can be
from 1 to 16 (depending on modem data rate).
Result of Internal Loopback Test. Indicates a Pass or Fail
result when an Internal Loopback Test is run. This result is
blank (Not applicable) if an External Loopback test is
selected.
Channel
Loopback
Result

Buttons:
Get:
Set:
Close:
Help:
B1091 Rev. L
the item.
193
NEW NMS
10.0
Hot Standby
The Hot Standby property sheet displays the current Hot Standby settings.
The Hot Standby configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view.
node in the Explorer view and then selecting Edit Hot Standby from
the Configuration menu.
Figure IX-22
Fields:
Hot Standby Property Sheet
Description:
Rx
Receiver Protection Mode Selection:
Protection 0 - RxSwitchManualA - Manually selects side A for the RF
Switching receive path.
1- RxSwitchManualB - Manually selects side B for the RF
receive path.
2 - RxSwitchAuto - Selection of side for the RF receive
path is determined automatically by IDU.
194
B1091 Rev. L
Appendices
Fields:
Description:
Tx
Transmitter Protection Mode Selection:
Protection 0 - txSwitchManualA - Manually selects side A for the
Switching transmit path.
1 - txSwitchManualB - Manually selects side B for the
transmit path.
2 - txSwitchAutoA - Selection of side A is preferred, but
the IDU can automatically switch transmit paths.
3 - txSwitchAutoB - Selection of side B is preferred, but
the IDU can automatically switch transmit paths.
Rx
Relay
Mode
Receiver Relay Mode Selection:

0 - rxRelayManualA - Manually selects side A for the
received data path.
1 - rxRelayManualB - Manually selects side B for the
received data path.
2 - rxRelayAutoA - Selection of side A is preferred but the
IDU can automatically switch the received data path.
3 - rxRelayAutoB - Selection of side B is preferred but the
IDU can automatically switch the received data path.

Buttons:
Get:
Set:
Close:
Help:
B1091 Rev. L
the item.
195
NEW NMS
11.0
Frequency
The Frequency property sheet displays the current frequency settings. The
fields with white background can be altered by users with proper user
privileges. The gray fields are non-editable.
Please note: Any loopback test must be terminated before changing
frequency.
The Frequency configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view.
node in the Explorer view and then selecting Edit Frequency from the
Configuration menu.
Figure IX-23
Fields:
Frequency Settings Property Sheet
Description:
Tx Frequency max:Maximum Transmitter Frequency Setting. Maximum

allowable value of Tx Frequency in kHz.
Tx Frequency
Current Transmitter Frequency Setting. Value (in
kHz.) must be a multiple of 250kHz.
Tx Frequency min Minimum Transmitter Frequency Setting. Minimum
allowable value of Tx Frequency in kHz.
Rx Frequency max Maximum Receiver Frequency Setting. Maximum
allowable value of Rx Frequency in kHz.
Rx Frequency
Current Receiver Frequency Setting. Value (in kHz.)
must be a multiple of 250 kHz.
Rx Frequency min Minimum Receiver Frequency Setting. Minimum
allowable value of Rx Frequency in kHz.
196
B1091 Rev. L
Appendices
Buttons:
Get:
Set:
Close:
Help:
B1091 Rev. L
the item.
197
NEW NMS
12.0
Transmitter
The Transmitter property sheet displays the current Transmitter output
level. For a Hotstandby system there will also be a ODU B tab.
The Transmitter configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view.
node in the Explorer view and then selecting Edit Transmitter from
Figure IX-24
Transmitter Property Sheet
For Phase IV ODU the dialog will look like this:
Figure IX-25
198
Transmitter Property Sheet, Phase IV ODU

B1091 Rev. L
Appendices
Fields:
Description:
Mute Transmitter Enable/Disable Transmitter Mute Function.

Tx Level:
Transmitter Level, Local Side. Magnitude between a

minimum of 0 and a maximum of 255 units.
For Phase IV ODU Magnitude is in dBm.
Tx Level
Remote Side
Transmitter Level, Remote Side. Magnitude between

a minimum of 0 and a maximum of 255 units.
For Phase IV ODU Magnitude is in dBm.
Limit Tx Level
Maximum Transmitter Output Level.

(Only for Phase IV ODU)
Limit Tx Level
Remote Side
Maximum Transmitter Output Level, remote side.

(Only for Phase IV ODU)
The mapping between transmitter output in units and transmitter output in

dBm can be found in the test record of each CompactLink radio.

Buttons:
Get:
Set:
Close:
Help:
B1091 Rev. L
the item.
199
NEW NMS
13.0
PDH Channels
The PDH Channels property sheet displays the settings and status of the
data channels.
The PDH Channels configuration sheet can be opened from the Configuration context menu of the Equipment node in the Explorer view.
node in the Explorer view and then selecting Edit PDH Channels from
Figure IX-26
200
PDH Channels Configuration Sheet
B1091 Rev. L
Appendices
Fields:
Description
Channel:
Data channel number. (1 - 16 depending on data rate)
Line Encoding:
Line Encoding Method on Channel.

AMI - Disables hardware coding, uses straight
Alternate Mark Inversion coding.
HDB3 - High density bipolar 3 coding, four consecutive zero substitution. (European data rates only.)
B8ZS - Binary eight consecutive zeros substitution.
(North American data rates only.)
Masking:
Mask Alarms on Channel.
Status:
Alarm on channel is on or off.

Buttons:
Get:
Set:
Close:
Help:
B1091 Rev. L
the item.
201
NEW NMS
14.0
NE Alarm Log
The NE Alarm Log property sheet displays the settings and content of the
NE alarm log.
The NE Alarm Log configuration sheet can be opened from the Configuration context menu of the Element node in the Explorer view.
node in the Explorer view and then selecting Edit PDH Channels from
Figure IX-27
NE Alarm Log Configuration Sheet
When pressing View in the NE Alarm Log Manager, a dialog box is

displayed prompting for the number of records to retrieve.
Figure IX-28
202
Number of Records Dialog Box
B1091 Rev. L
Appendices
Fields:
Description
Max entries:
The number of entries the Network element alarm

log can hold.
No. Log entries:
Current number of log entries.
Last Log entry:
The sequence number of the latest (in time) entry in

the alarm log. Sequence number of 0, means there
are no entries in the log.
Buttons:
Get:
Close:
Help:
Press this button to get help on the current property sheet.
at the top of the dialog box,
then click the item.
View:
Press this button to view the NEs Alarm Log.
Delete Log: Press this button for deleting the entire alarm log. All
entries will be removed but not reset the sequence number.
B1091 Rev. L
203
NEW NMS
15.0
Performance Registers
The Performance Register sheet displays the G.821 performance data
arranged in bins. The most recent bin is located in 1, and then holds up to
maximum 16.
The Performance Register configuration sheet can be opened from the
Perfromance context menu of the element node, equipment node,
and ODU node in the Explorer view. The sheet can also be invoked by
selecting (highlighting) the element node, equipment node, and ODU
node in the Explorer view and then selecting Registers from the Performance menu.
Figure IX-29
204
Performance Register Configuration Sheet
B1091 Rev. L
Appendices
Fields:
Description:
Node:
The measurement location
Reg. #:
The register number, bin 1 holds the most recent measurement.
SES:
Severely Errored Seconds - a one-second period with one

Errored Block Overstep (EBO) and/or one Severely
Errored Overstep(SEBO).
UAS:
Unavailable Seconds.
DM:
Degraded Minutes.
ES:
Errored Second - a one-second period with one or more

Error Blocks (EB).
Start Time: The time when the performance measurement started.

Status:
The status of the collected data (Data OK, Data Not OK).
Performance Enables/Disables logging of G.821 data into 15 minutes

Monitor
bins.
Enabled

Buttons:
Get:
Set:
Close:
Help:
B1091 Rev. L
the item.
205
NEW NMS
Appendix D- Configuration of CityLink,

InterLink and Netlink
For configuration of CityLink, please refer to the CityLink User Manual.
For configuration of InterLink, please refer to the InterLink User Manual.
For configuration of NetLink, please refer to the NetLink User Manual.
206
B1091 Rev. L
Appendices
Appendix E - Abbreviations
A/D
AAU
ACU
AIS
AGC
ALC
ALS
Analog
AOU
ASF
ASIC
ATDE
ATM
ATPC
ATT
B1
B2
B3
Baseband
BBE
BBER
BER
B1091 Rev. L
Analog to Digital Converter. A component for converting analog electrical

signals to digtal electrical signals. Opposite: D/A (Digital to Analog Converter)
Auxiliary Alarm Unit
Alarm Collection Unit
Alarm Indication Signal
Automatic Gain Control
Automatic Level Control
Automatic Laser Shutdown
Analog measurements from the NE
Auxiliary Output Unit
Alignment Switch Function
Application Specific Integrated Circuit
Adaptive Time Domain Equalizer
Asynchronous Transfer Mode. All information to be transmitted is first
fragmented into small, fixed-sized frames known as cells.
Automatic Transmitter Power Control. ATPC is available as an option for the
SDH-family. This function effectively reduces the interference probability
in your network. Saturation of the receiver during up-fading conditions is
also avoided by use of ATPC.
Attenuator
Part of STM-1 Section overhead: An 8-bit byte-interleaved parity (BIP-8)
check sum which is monitored and calculated by every regenerator and
multiplexer on an SDH line. This check sum is calculated on the entire
STM-1 frame after scrambling, stored and then loaded into the B1 byte of
the following frame - before scrambling.
Part of STM-1 Section overhead: 3 bytes that carry a 24-bit byte-interleaved
parity(BIP-24) checksum which is calculated and inserted into the B2 bytes
by the multiplexer that transmits an SDH signal. The multiplexer that receives
an SDH signal will likewise calculate the checksum and compare it with the
contents of the B2 bytes.
The term baseband is used for designation of the band of frequencies
representing the original signal as delivered by the source of information
Background Block Error - an errored block, excluding blocks during SES and
unavailable time
Background Block Error Ratio - the ratio of errored blocks to total blocks,
excluding blocks during SES and unavailable time
Bit Error Rate. The number of error bits divided by the total number of bits
207
NEW NMS
BIP-2
A 2-bit interleaved parity-check sum which is monitored and calculated by

the terminating points of the actual path. This check sum is calculated on
the entire VC-n, stored and then loaded into the BIP-2 bits of the following
VC-n.
CA
Controlled Attenuator
CB
Control Board
CEPT
European Conference of Postal and Telecommunications Administration
CityLink
CityLink is a super compact NERA SDH radio-relay transmission equipment for the 18, 23 and 25 GHz frequency bands.
CLK
Clock
CMI
Coded Mark Inversion
Combobox A Combobox is a standard Windows control where you by pressing the
little down-arrow can get listed several eligible alternatives
CPU
Central Processor Unit
C/S
Client/Server
DC
Direct Current
DCC
Data Communication Channel
DIP
Dual In-line Package
DM
Degraded Minutes
DRAM
Dynamic Random Access Memory
DRO
Dielectric Resonator Oscillator
DTMF
Dual Tone Multi-Frequency. Used for signalling in PSTN.
EB
Errored Blocks. A block with one or more errored bits, or bits missing due
to loss of signal.
EBO
Errored Block Overstep
ECL
Emitter Coupled Logic
EMC
Electromagnetic Compatibility
EOW
Engineering Order Wire
EPROM
Erasable Programmable Read-Only Memory
EQL
Equalizer
Error bit rate Number of error bits/total number of bits
ES
Errored Seconds. A one-second period with one or more Errores Blocks
(EB).
ESR
Errored Second Ratio. The ratio of ES to the total seconds in available time
during a measurement interval.
FAT
Factory Acceptance Test
FB
Filter Bank
FEC
Forward Error Correction. Coding scheme used for reducing the bit error
rate
FET
Field Effect Transistor
FIR
Finite Impulse Response Filter. Digital filter.
FM
Frequency Modulation. A modulation technique
GaAs
Gallium Arsenide Substrate used in semiconductors
208
B1091 Rev. L
Appendices
GHz
G.826
HBER
HDB3
I/O
IDU
IF
IP
ITU-R
ITU-T
LBER
LCD
LCT
LD
LED
LIF
LMS
LNA
LO
LOM
LPF
MAC
MC
MGC
MHz
MIB
MIL-STD
MLE
MOD
MSOH
MST
NE
NEW-NMS
NI
NMN
NRZ
NSAP
ODU
OSC
OSI
PABX
PAL
B1091 Rev. L
Giga Hertz = 1000000000 Hz = 1.010^9 Hz

ITU-T Standard: Quality requirement recommendation for SDH networks
High Bit Error Ratio
High Density Bipolar (max. 3 0)
Input/Output
InDoor Unit. The part of the radio equipment that is mounted indoor.
Intermediate Frequency
Internet Protocol
International Telecommunication Union (former CCIR)
International Telecommunication Union (former CCITT)
Low Bit Error Ratio
Liquid Crystal Display
Local Craft Terminal
Level Detector
Light Emitting Diode
Line Interface
Least Mean Square
Low Noise Amplifier. Amplifier used for amplifying received signal
Local Oscillator
Length of Message
Low Pass Filter. Filter which only lets low frequencies through
Media Access Control
Micro Controller
Manual Gain Control
Mega Hertz = 1000000 Hz = 1.010^6 Hz
Management Information Base
Military Standard
Maximum Level Error
Modulator
Multiplexer Section Overhead
Multiplexer Section Termination
Network Element
Nera Element vieW-Network Management System. This program.
Network Interface
Nera Management Networks
Non Return to Zero. Linecode
Network Service Access Point
Out Door Unit. The part of the radio equipment that is mounted outdoor.
Oscillator
Open Systems Interconnection. The name of the protocol suite that is based
on ISO protocols to create an open system interconnection environment.
Private Automatic Branch Exchange
Programmable Array Logic
209
NEW NMS
PC
PJE
PLL
PLO
POH
PRBS
PROM
PROT CH
PSCU
PSK
PSTN
PWM
QPSK
RAM
RCVR
RDDU
RDU
REG CH
REI
RF
RPS
RSOH
RST
RTC
RU
SAT
SAW
SCADA
SDH
SEBO
SES
SESR
SIC
SNMP
SOH
210
Personal Computer.
Pointer Justification Events
Phase Locked Loop
Phase Locked Oscillator
Path Overhead
Pseudo-Random Bit Sequence
Programmable Read-Only Memory
Protection Channel
Protection Switching Control Unit
Phase Shift Keying
Public Switched Telephone Network
Pulse Width Modulation
Quadrature Phase Shift Keying
Random Access Memory
Receiver
Receiver Data Distribution Unit
Receiver Distribution Unit
Regular Channel
Remote Error Indicator
Radio Frequency
Radio Protection Switching
Regenerator Section Overhead
Regenerator Section Termination
Run Time Clock
Relay Unit
Site Acceptance Test
Surface Acoustic Wave
Supervision, Control And Data Acquisition
Synchronous Digital Hierarchy
Severely Errored Block Overstep
Severely Errored Seconds. A one-second period with one Errored Block
Overstep (EBO) and/or one Severely Errored Overstep(SEBO)
Severely Errored Seconds Ratio. The ratio of SES to the total seconds in
available time during a measurement interval
Serial Interface Controller
Simple Network Management Protocol. A communications protocol
used in the monitoring and management of communications devices and
services. SNMP utilizes three basic request primitives: Set, Get, and Get-Next
for configuration and performance information, and one asynchronous
notification: Trap for alarm and status information. (Originally designed for
TCP/IP.) Most popular SNMP software: SunNet Manager, HP OpenView
and IBM NetView / 6000.
Section OverHead. The SOH in an STM-1 frame is formed by the RSOH (3
B1091 Rev. L
Appendices
SORP
SRAM
SRQ
SSB
SSS
STMSU
TCM
TCP/IP
TMN
TTL
UAT
UAS
VC
VCO
VCXO
Viterbi
VLSI
XMTR
XSU
B1091 Rev. L
rows x 9 bytes) and the MSOH (5 rows x 9 bytes). The RSOH is the range
of row 0,1 and 2. The MSOH is the range of row 4 to row 8.
Section Overhead & Radio Processor
Static Random Access Memory
Service Request
Single Side Band
SDH Supervisory System
Synchronous Transport Module Supervisory Unit (Part of Nera equipment). The SU is a unit located in each
Nera radio network element (terminal or repeater) and is the main
controller of the NE. The SU has a serial interface for transferring
management information to the NEW-NMS. The SU is able to collect
management data from other SUs in a Nera Management Network.
Trellis Coded Modulation. In CityLink the 32 TCM scheme is used. TCM
is a combined coding and modulation scheme for improving the reliability
of a digital transmission system. Redundancy is introduced by increasing
the number of constellation-points without increasing the symbolrate or
transmitted power.
Transport Communication Protocol/ Internet Protocol
Telecommunication Management Network
Transistor-Transistor Logic
Unavailable Time
Unavailable Seconds
Virtual Container
Voltage Controlled Oscillator
Voltage Controlled X-tal Oscillator
Viterbi is a decoding scheme optimized to reduce the bit error rate. (FEC)
Very Large Scale Integration
Transmitter
Transmitter Switching Unit
211

NEW Manual Radio Nera

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

NEW Manual Radio Nera

Enviado por

Direitos autorais:

Formatos disponíveis

User Manual

This page is intentionally left blank.

New Section VII; SNMP

Section VI, Chapter 2.4; Map tutorial added (2.4.2)

Section III: New Chapter 5.0 Equipment Compability.

Section XI: Chapter 1.0; changed bitmap and description

Section XI: Chapter 1.3; Description changed.

Section IV: Chapter 1.3.1.3 and 1.3.2 changed.

Major restructuring of the manual

Changes in Section I & II due to new version of NEW-NMS.

Section II: Fig. II-14 changed

Section I: Chapter 3.1; Change in Hardware

Nera Management Networks ......................................

Hardware Overview ....................................................

Database Requirements ............................................. 20

SECTION II, Software Setup................................. 23

Software Installation ................................................... 25

Data Link Properties ........................................ 28

SECTION III, Using NEW..................................... 47

Getting Started ........................................................... 49

Program Environment ................................................ 51

SECTION IV, Fault Management ....................... 65

Information Acquisition .............................................. 67

Visual Alarm Notification ............................................ 72

Logging Fault Events .................................................

SECTION V, Configuration Management ......... 83

Network Element Configuration ................................ 99

SNMP Settings ............................................................ 101

SECTION VI, Performance Management ......... 105

General ........................................................................ 107

RF Statistics View ....................................................... 108

Logging Performance Events ...................................

SECTION VII, Security Management ................ 119

General ........................................................................ 121

User Levels and Privileges ....................................... 121

Logon ........................................................................... 122

User Administration ....................................................

Logging Security Events ...........................................

SECTION VIII, Database ..................................... 139

NEW-NMS Database Introduction .............................

Database Configuration .............................................

Backup and Restore of NEW-NMS Systems ............

Backup and Restore of an SQL Server Database .

SECTION IX, Appendices .................................. 159

This page is intentionally left blank

Nera Management Networks

Figure I-1 Section

Nera Management Network

Figure I-2 Network Interface

Nera Element vieW

Figure I-3 Network Element (NE) - PC connection

Win XP Prof. SP2

Memory <= 100 NEs 128 MB

Memory > 100 NEs

Disk file system

Minimum system requirements

Additional required hardware:

Hardware Program Key

Figure I-4 NEW-NMS parallel port hardware key

Figure I-5 NEW-NMS USB port hardware key

Network Element Connections

R1A and later

R1A and later

R14A and later