ROSA NMS Configuration Manual

4014778 Rev H
ROSA NMS
Network Management System
User's Guide
Version 4.1
For Your Safety
For Your Safety
Explanation of Warning and Caution Icons

Avoid personal injury and product damage! Do not proceed beyond any symbol
until you fully understand the indicated conditions.
The following warning and caution icons alert you to important information about
the safe operation of this product:
You may find this symbol in the document that accompanies this product.
This symbol indicates important operating or maintenance instructions.
You may find this symbol affixed to the product. This symbol indicates a
live terminal where a dangerous voltage may be present; the tip of the flash
points to the terminal device.
protective ground terminal.
chassis terminal (normally used for equipotential bonding).
You may find this symbol affixed to the product. This symbol warns of a
potentially hot surface.
You may find this symbol affixed to the product and in this document.
This symbol indicates an infrared laser that transmits intensity-modulated
light and emits invisible laser radiation or an LED that transmits
intensity-modulated light.
Important
Please read this entire guide. If this guide provides installation or operation
instructions, give particular attention to all safety statements included in this guide.
4014778 Rev H iii

Safe Operations
Notices
Trademark Acknowledgments
Cisco, Cisco Systems, the Cisco logo, the Cisco Systems logo, ROSA, Copernicus,
Si-Server, and SciCare are registered trademarks or trademarks of Cisco Systems,
Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document are the property of their respective
owners.
Publication Disclaimer
Cisco Systems, Inc., assumes no responsibility for errors or omissions that may
appear in this publication. We reserve the right to change this publication at any
time without notice. This document is not to be construed as conferring by
implication, estoppel, or otherwise any license or right under any copyright or
patent, whether or not the use of any information in this document employs an
invention claimed in any existing or later issued patent.
Copyright
2009 Cisco Systems, Inc. All rights reserved.
Information in this publication is subject to change without notice. No part of this
publication may be reproduced or transmitted in any form, by photocopy,
microfilm, xerography, or any other means, or incorporated into any information
retrieval system, electronic or mechanical, for any purpose, without the express
permission of Cisco Systems, Inc.
4014778 Rev H v
Contents
Contents
Safe Operations xvii
Preface xix
Chapter 1 Introducing ROSA NMS 1

About the ROSA Network Management System................................................................ 2
Introduction ................................................................................................................. 2
Features and Benefits ................................................................................................. 3
ROSA NMS Software Versions ................................................................................. 3
System Requirements ................................................................................................. 4
General Add-On Components for ROSA NMS................................................................... 5
ROSA NMS Notification Task................................................................................... 5
ROSA Advanced Configuration ............................................................................... 5
ROSA NMS Automation and Redundancy Tasks ................................................. 5
ROSA NMS Performance and Trending ................................................................. 6
Third Party Equipment Integration Tools ............................................................... 8
ROSA NMS Headend Applications ......................................................................... 9
ROSA NMS iLynx Backbone Model ...................................................................... 10
ROSA NMS HFC Network Monitoring................................................................. 11
Contribution .............................................................................................................. 12
Chapter 2 Installing the ROSA NMS Software 13

Introduction ............................................................................................................................ 14
To Install the ROSA/Copernicus Software........................................................................ 15
Chapter 3 Using the ROSA NMS User Interface 23

About ROSA NMS User Interface ....................................................................................... 24
ROSA NMS User Interface Window ................................................................................... 25
About the Title Bar.................................................................................................... 25
About the Standard Windows Buttons on the Title Bar...................................... 25
About the ROSA Control Icon and ROSA Control Menu................................... 26
About the ROSA NMS User Interface Menu Bar ................................................. 26
About the ROSA NMS Status Bar........................................................................... 27
Using Shortcut Keys ................................................................................................. 28
Tool Bars..................................................................................................................... 30
About the Color Palette............................................................................................ 34
Opening the Legend of the Icons used by the ROSA NMS System .................. 35
4014778 Rev H vii

Contents
About the Server Explorer .................................................................................................... 36

Introduction ............................................................................................................... 36
Manipulating the Server Explorer Box .................................................................. 37
Browsing Through an Explorer Tree ..................................................................... 38
Searching into the Server Explorer Tree ................................................................ 39
About the Icons Used in an Explorer Tree ............................................................ 40
Changing View Options ....................................................................................................... 44
Introduction ............................................................................................................... 44
To Set the View Options .......................................................................................... 45
Chapter 4 Getting Started 47

Starting a ROSA NMS Single User System for the First Time......................................... 48
Starting a ROSA NMS Client system for the First Time................................................... 52
Starting a ROSA NMS Device Configuration Shell System for the First Time ............. 55
Chapter 5 Licensing 59
Introduction ............................................................................................................................ 60
About ROSA NMS Licenses .................................................................................... 60
License Errors ............................................................................................................ 60
Obtaining a New License File ................................................................................. 61
Checking the Host ID of a Server ........................................................................... 62
Installing a License File ......................................................................................................... 63
Chapter 6 Working with Drivers 65

Introduction ............................................................................................................................ 66
Installing Drivers ................................................................................................................... 68
Introduction ............................................................................................................... 68
To Install Drivers ...................................................................................................... 69
Getting Drivers from a Copernicus Server or SI-Server................................................... 71
Viewing Driver Details ......................................................................................................... 73
Introduction ............................................................................................................... 73
Checking the Details of a Driver............................................................................. 74
Making a Task Instance......................................................................................................... 75
Uninstalling Drivers .............................................................................................................. 77
Assigning Serial Port Drivers to Serial Ports ..................................................................... 79
Chapter 7 Working with Resources 81

Handling Units....................................................................................................................... 82
Introduction ............................................................................................................... 82
Opening the User Interface of a Unit ..................................................................... 83
GUI Updating Behavior ........................................................................................... 85
About the Local and Remote Control of Units ..................................................... 87
Working with Unit Folders ..................................................................................... 88
viii 4014778 Rev H

Contents
Working with Unit Groups ..................................................................................... 91

Working with Demo Units ...................................................................................... 99
Changing the Management Mode........................................................................ 100
Removing Units ...................................................................................................... 103
Exporting Unit Details ........................................................................................... 104
Unit Settings ......................................................................................................................... 106
Introduction ............................................................................................................. 106
Changing Unit Settings via Resource Settings Dialog....................................... 106
Changing Unit Settings via the Edit Unit dialog................................................ 108
Configuring Unit Input/Output Ports ............................................................................. 110
Introduction ............................................................................................................. 110
Listing the Currently Defined Input/Output Ports........................................... 110
Adding Input/Output Ports ................................................................................. 113
Removing Input/Output Ports............................................................................. 114
Printing the List of Input/Output Ports .............................................................. 115
Using Notes .......................................................................................................................... 116
Introduction ............................................................................................................. 116
Creating Notes......................................................................................................... 117
Opening Notes ........................................................................................................ 118
Editing a Note.......................................................................................................... 119
Changing the Title of a Note ................................................................................. 119
Deleting Notes......................................................................................................... 120
Displaying Unit Information in the Server Explorer or Group Explorer Tree............ 121
Introduction ............................................................................................................. 121
To Display Unit Information in the Server Explorer or Group Explorer
Tree ........................................................................................................................ 121
Chapter 8 Working with Servers 123

Introduction .......................................................................................................................... 124
About the Client/Server Architecture ................................................................. 124
Adding and Removing Servers.......................................................................................... 125
Introduction ............................................................................................................. 125
Adding a Server to the ROSA NMS System ....................................................... 125
Removing a Server from the Server Explorer ..................................................... 127
Connecting and Disconnecting Servers ............................................................................ 128
Introduction ............................................................................................................. 128
Connecting a Server to the ROSA NMS System................................................. 128
Disconnecting a Server from the ROSA NMS System....................................... 130
Checking the Currently Connected Clients to a Server..................................... 130
Setting the Auto Connect Parameters .................................................................. 131
Stopping, Rebooting and Starting a Server ...................................................................... 133
Introduction ............................................................................................................. 133
Stopping the Server Software of the ROSA NMS System or Server................ 135
Rebooting the ROSA NMS System or Server...................................................... 135
Defining a Master Server .................................................................................................... 137
Introduction ............................................................................................................. 137
4014778 Rev H ix
Contents
To Define a Master Server ..................................................................................... 137

Manipulating the Global Inventory .................................................................................. 138
Introduction ............................................................................................................. 138
Copying the Server Inventories of a ROSA NMS System to the Master
Server..................................................................................................................... 138
Copying Server Inventories from a Master Server to a ROSA NMS
System ................................................................................................................... 140
Updating Server Inventories on the Master Server............................................ 141
Updating Server Inventories on the ROSA NMS System ................................. 142
Removing Server Inventories from the Master Server ...................................... 144
Sending Messages ................................................................................................................ 145
Introduction ............................................................................................................. 145
To Send Messages Between ROSA NMS Systems ............................................. 145
Defining a Default Client ....................................................................................... 146
Synchronizing Date and Time............................................................................................ 148
Introduction ............................................................................................................. 148
To Synchronize Date and Time............................................................................. 148
To Adjust the Time and Date Manually .............................................................. 149
Changing Server Settings.................................................................................................... 150
Changing the Server Identification Settings ....................................................... 150
Changing the Computer Name............................................................................. 151
Changing the Administrative User Password .................................................... 153
Changing the Network Settings............................................................................ 154
Viewing Trace Files ............................................................................................................. 155
Introduction ............................................................................................................. 155
Enabling or Disabling Tracing for a Particular Server....................................... 156
Viewing Trace Files ................................................................................................ 156
Filtering Trace Files ................................................................................................ 157
Copying Traces to a File......................................................................................... 158
Printing Traces ........................................................................................................ 159
Checking Server Availability ............................................................................................. 161
Introduction ............................................................................................................. 161
Setting the Server Availability Checking Preferences ....................................... 161
Using Active or Passive FTP .............................................................................................. 163
Introduction ............................................................................................................. 163
Setting Active or Passive FTP................................................................................ 163
Chapter 9 Working with Services and Channels 165

Using TV Services ................................................................................................................ 166
Introduction ............................................................................................................. 166
Adding TV Services ................................................................................................ 166
Editing a TV Service ............................................................................................... 168
Assigning Priorities to TV Services ...................................................................... 168
Removing TV Services ........................................................................................... 170
Working with Folders ............................................................................................ 170
Printing a List of TV Services ................................................................................ 172
x 4014778 Rev H
Contents
Configuring the Filter............................................................................................. 173

Using Analog TV Channels ................................................................................................ 175
Introduction ............................................................................................................. 175
Adding Analog TV Channels................................................................................ 175
Editing an Analog TV Channel............................................................................. 177
Loading Channels from Modulators.................................................................... 178
Storing Channels into Monitoring Devices ......................................................... 178
Printing a List of Analog TV Channels................................................................ 179
Removing Analog TV Channels ........................................................................... 180
Using Analog Satellite Channels ....................................................................................... 183
Introduction ............................................................................................................. 183
Adding Analog Satellite Channels ....................................................................... 183
Editing Analog Satellite Channels........................................................................ 186
Storing Analog Satellite Channels to Satellite Receivers................................... 187
Printing a List of Analog Satellite Channels ....................................................... 188
Removing Analog Satellite Channels................................................................... 189
Chapter 10 Working with Attributes and Locations 193

Using Attributes................................................................................................................... 194
Introduction ............................................................................................................. 194
Adding Attributes................................................................................................... 194
Editing Attributes ................................................................................................... 195
Removing Attributes .............................................................................................. 196
Using Locations.................................................................................................................... 197
Introduction ............................................................................................................. 197
Adding a Location .................................................................................................. 197
Assigning Attributes to a Location....................................................................... 198
Changing an Attribute value................................................................................. 199
Removing Attributes from a Location ................................................................. 200
Renaming a Location.............................................................................................. 200
Removing a Location.............................................................................................. 201
Chapter 11 Working with Messages 203

Introducing ........................................................................................................................... 204
ROSA NMS Message Database............................................................................. 204
Message Viewer ...................................................................................................... 204
Message Notification .............................................................................................. 204
Messages in the Status Bar..................................................................................... 205
Message Types ........................................................................................................ 205
Message Severity..................................................................................................... 206
Pending and Non-Pending Messages .................................................................. 206
Acknowledging Messages ..................................................................................... 206
4014778 Rev H xi
Contents
Viewing Messages ............................................................................................................... 207

Introduction ............................................................................................................. 207
Working with the Message Viewer ...................................................................... 207
Viewing Messages .................................................................................................. 209
Viewing Additional Message Information.......................................................... 211
Changing the Message Viewer Layout ................................................................ 212
Viewing the Message Details ................................................................................ 214
Using Message Filters............................................................................................. 215
Basic Message Operations .................................................................................................. 223
Acknowledging Messages ..................................................................................... 223
Working with Message Attachments................................................................... 225
Resetting Pending Messages ................................................................................. 226
Deleting Non-Pending Messages ......................................................................... 228
Printing Messages................................................................................................... 229
Copying Messages to the Clipboard .................................................................... 230
Exporting Messages................................................................................................ 231
Logging Manual Created Messages .................................................................................. 232
Introduction ............................................................................................................. 232
To Log Manual Created Messages ....................................................................... 232
Changing Message Rules .................................................................................................... 234
Introduction ............................................................................................................. 234
Adding Message Rule Scripts ............................................................................... 234
Enabling or Disabling Message Rules.................................................................. 235
Configuring the Message Options..................................................................................... 237
Configuring Message Notification ....................................................................... 237
Hiding or Displaying the Hidden Messages....................................................... 238
Configuring the Repetitive Alarm Suppression Feature................................... 238
Configuring the Link to External Web Server Feature ...................................... 239
Switching On or Off Backup Active Message Logging ..................................... 240
Working with the Listening Console ................................................................................ 241
Introduction ............................................................................................................. 241
Setting a Server in Listening Mode ...................................................................... 242
Opening the Listening Console ............................................................................ 242
Selecting the Message Category in the Listening Console................................ 242
Changing the Layout of the Listening Console Window.................................. 243
Setting Up the Message Filter for the Listening Console Window.................. 244
Removing Messages from the Listening Console .............................................. 247
Alarm Correlation Domains............................................................................................... 248
Introduction ............................................................................................................. 248
License key............................................................................................................... 248
HFC Alarm Correlation ......................................................................................... 248
Adding the Alarm Correlation Domains Scripts................................................ 249
Editing the Configuration File .............................................................................. 249
Viewing Alarm Correlation Domains.................................................................. 250
Using the HFC Alarm Correlation ....................................................................... 251
Maintaining the Message Database................................................................................... 254
Viewing Message Statistics.................................................................................... 254
xii 4014778 Rev H

Contents
Cleaning the Message Database ........................................................................... 255

Using Message Maintenance Rules ...................................................................... 257
Chapter 12 Working with Maps 261

About Maps .......................................................................................................................... 262
Introduction ............................................................................................................. 262
Headend and Network Structure Maps .............................................................. 262
Network Monitoring Topology Maps ................................................................. 263
Task Configuration Maps ...................................................................................... 264
Map Modes ........................................................................................................................... 265
Introduction ............................................................................................................. 265
Changing the Map Mode ....................................................................................... 265
Setting the Map Options ..................................................................................................... 266
Introduction ............................................................................................................. 266
To Set the Map Options ......................................................................................... 266
Resource Bitmaps................................................................................................................. 268
Introduction ............................................................................................................. 268
Installing User-Defined Bitmaps .......................................................................... 268
Changing the Bitmap of a Resource ..................................................................... 270
Uninstalling Bitmaps.............................................................................................. 270
Map Operations ................................................................................................................... 272
Creating Maps ......................................................................................................... 272
Opening and Closing Maps................................................................................... 274
Renaming a Map ..................................................................................................... 274
Saving Maps ............................................................................................................ 275
Importing Maps ...................................................................................................... 275
Deleting Maps ......................................................................................................... 276
Manipulating the Map Windows ......................................................................... 277
Changing the Map Settings ................................................................................... 280
Printing Maps .......................................................................................................... 283
Synchronizing Maps............................................................................................... 285
Repairing Maps ....................................................................................................... 291
Using Map Objects............................................................................................................... 292
Using Resources ...................................................................................................... 292
Adding Objects Using the Drawing Tools .......................................................... 296
Using Bitmap Illustrations..................................................................................... 306
Embedding OLE Objects........................................................................................ 309
Using Map Links..................................................................................................... 315
Manipulating Map Objects ................................................................................................. 321
Selecting Objects ..................................................................................................... 321
Copying and Pasting Objects ................................................................................ 321
Removing Objects ................................................................................................... 322
Resizing Objects ...................................................................................................... 322
Moving Objects ....................................................................................................... 323
Aligning Objects...................................................................................................... 323
Changing the Object Drawing Order................................................................... 323
4014778 Rev H xiii

Contents
Grouping and Ungrouping Objects ..................................................................... 324

Selecting Default Map Object Properties............................................................. 324
Ordering Map Objects............................................................................................ 324
Using Performance Bars...................................................................................................... 326
Introduction ............................................................................................................. 326
Adding a Performance Bar to Devices................................................................. 326
Updating a Performance Bar................................................................................. 329
Chapter 13 Working with Relations 331

Introduction .......................................................................................................................... 332
Using Relations in Maps ..................................................................................................... 333
Adding Relations .................................................................................................... 333
Checking the Properties of a Relation.................................................................. 334
Removing a Relation from a Map......................................................................... 335
Using the Relation Dialog................................................................................................... 336
About the Relation Dialog ..................................................................................... 336
Adding Relations .................................................................................................... 337
Removing Relations Using the Relations Dialog ............................................... 338
Printing Relations ................................................................................................... 339
Chapter 14 Performance Monitoring 343

Introduction .......................................................................................................................... 344
Opening Reporting Component ........................................................................................ 346
Generating Demo Quality Data ......................................................................................... 347
Introduction ............................................................................................................. 347
To Generate Demo Quality Data .......................................................................... 347
Adding Availability Data ................................................................................................... 349
Introduction ............................................................................................................. 349
To Add Availability Data ...................................................................................... 349
Deleting Quality Data ......................................................................................................... 351
Chapter 15 ROSA NMS System Security 353

Using Security Group.......................................................................................................... 354
Creating a New Security Group ........................................................................... 354
Changing User Group Properties ......................................................................... 357
Removing a Security Group .................................................................................. 359
Security Actions Overview.................................................................................... 360
ROSA NMS Users ................................................................................................................ 362
Creating Users ......................................................................................................... 362
Changing User Properties ..................................................................................... 363
Removing Users ...................................................................................................... 365
Changing Active User ............................................................................................ 365
Changing a User Password ................................................................................... 366
xiv 4014778 Rev H

Contents
Exporting and Importing Security Settings ..................................................................... 368

Introduction ............................................................................................................. 368
Exporting all Security Settings.............................................................................. 368
Exporting the Security Settings of a User or a Security Group ........................ 369
Importing Security Settings................................................................................... 371
Map Security......................................................................................................................... 373
Introduction ............................................................................................................. 373
Adding a User to a Map......................................................................................... 373
Changing Map Permissions .................................................................................. 375
Removing Users from a Map ................................................................................ 376
Setting the Minimum Password Length........................................................................... 377
Chapter 16 ROSA High Availability Solution 379

Introduction .......................................................................................................................... 380
General ..................................................................................................................... 380
Features .................................................................................................................... 380
Installing the High Availability Control Software .......................................................... 383
Introduction ............................................................................................................. 383
Preparing the Server............................................................................................... 384
Configuring the Network Settings ....................................................................... 389
Additional Checks and Configurations............................................................... 396
Licensing .................................................................................................................. 398
Installing the High Availability Control Software ............................................. 402
Configuring the High Availability Control Software ..................................................... 429
Prerequisites ............................................................................................................ 429
To Configure the High Availability Control Software ...................................... 429
General Remarks.................................................................................................................. 441
ROSA NMS SNMP Agent Task ............................................................................ 441
Email Notification of Neverfail Alerts ................................................................. 441
Recovering from a Failover ................................................................................... 441
Known Issue - Ping Targets reset after Power Outage on both Servers ......... 441
Appendix A Customer Information 443

Product Support................................................................................................................... 444
Appendix B Additional Configuration 447

Starting Messenger Service................................................................................................. 448
Introduction ............................................................................................................. 448
To Start the Messenger Service ............................................................................. 448
Changing Administrative Password................................................................................. 451
Introduction ............................................................................................................. 451
Changing the Administrative Password ............................................................. 451
Internet Protocol Security ................................................................................................... 456
Introduction ............................................................................................................. 456
4014778 Rev H xv
Contents
To Configure IPsec on a Computer Running Windows XP or

Windows 2000 Server.......................................................................................... 456
To Configure IPsec on a Computer Running Windows Vista.......................... 478
Appendix C Upgrading the ROSA NMS Software 493

Introduction .......................................................................................................................... 494
Installing a ROSA/Copernicus Software Package on a ROSA NMS system.............. 495
Locking and Unlocking the ROSA NMS System ............................................................ 496
Introduction ............................................................................................................. 496
Locking a ROSA NMS System .............................................................................. 496
Unlocking a Locked ROSA NMS System ............................................................ 497
Upgrading Client Software via a Copernicus Server or SI-Server................................ 499
Introduction ............................................................................................................. 499
Installing a Higher Master Software Version on a Copernicus Server or
SI-Server ................................................................................................................ 500
Upgrading the Client Software of a ROSA NMS Client or ROSA NMS
Single User System .............................................................................................. 501
Appendix D Connecting Units to a ROSA NMS System 503

RS232 to RS232 Connection ................................................................................................ 504
RS232 to RS485 Connection ................................................................................................ 505
Glossary 507
Index 515
xvi 4014778 Rev H

Safe Operations
Safe Operations
The software described in this guide is used to monitor and / or manage Cisco
equipment. Certain safety precautions should be observed when operating
equipment of this nature.
For product specific safety requirements refer to the appropriate section of the
documentation accompanying your product.
4014778 Rev H xvii

Preface
Preface
About this Guide
Introduction
This guide provides the information to install, operate, and configure the ROSA
Network Management System (NMS) software.
Purpose
After reading this guide, you will be able to install, setup and use the ROSA NMS
software to manage your application.
Audience
This manual is written for system administrators and operators who want to install,
set up and operate ROSA NMS.
Document Version
This is the fourteenth release of this user's guide.
Related Publications
The technical publications listed below provide further helpful information for the
ROSA NMS system. Refer to these publications as you read this User's Guide.
Hardware
Copernicus MKIII Element Manager - User Manual, part number 6985110
Copernicus MKIV - User's Guide, part number 4005590
Copernicus MKIV System G4 - User's Guide, part number 4010960
Copernicus MKIV System G4p - User's Guide, part number 4015065
Copernicus MKV - User's Guide, part number 4020599
Continuum DVP SI-Server - User's Guide, part number: 4005692
Continuum DVP SI-Server System G4 - User's Guide, part number 4011330
Continuum DVP SI-Server System G4p - User's Guide, part number 4015240
Continuum DVB SI-Server MKV - User's Guide, part number 4022319
Download Spooler, part number: 4007112
4014778 Rev H xix

Preface
Component Drivers
Digital Headend Probe - User's Guide, part number: 4003349
EPG Editor - User's Guide, part number: 6985058
Group-wise Equipment Manager - User's Guide, part number: 4002572
Headend Model - User's Guide, part number: 6985047
Ingress Reporting - User Manual, part number: 6985016
Macro Component - User's Guide, part number: 6984990
Prisma GbE Network Model - User's Guide, part number: 4004439
Reporting - User's Guide, part number: 6984891
Schedule Database - User's Guide, part number: 6984874
SDH Backbone Model - User's Guide, part number: 6984276
Server Backup - User's Guide, part number: 6984272
Service Availability Reporting - User's Guide, part number: 4003351
Setting Management Component - User's Guide, part number 4013127
SNMP Profile Manager - User's Guide, part number: 6984863
UDD/UDD PM - User's Guide, part number: 6984844
Video Monitoring - User Manual, part number: 6984837
Device Drivers
Atlas - User Manual, part number: 6985081
Atlas MkII DVB-T Receiver - User's Guide, part number: 6984288
Continuum DVP D9600 Web Browser User Interface - User's Guide, part number
4003323
D9224 Satellite Receiver - User's Guide, part number: 4005742
FSM 860 - User Manual, part number: 6985051
Generic Network Element - User Manual, part number: 6985048
iLynx Optical Backbone - User's Guide, part number: 6985035
iLynx Optical Backbone 1U - User's Guide, part number: 4001637
Indus DVB Descrambler - User's Guide, part number: 6987948
I/O Box - User Manual, part number: 6985044
LM 860 - User Manual, part number: 6985002
xx 4014778 Rev H
Preface
Maddox Router, part number: 6985050

Neon Rx Telecom Network Adapter - User's Guide, part number: 4008312
Neon Tx Telecom Network Adapter - User's Guide, part number: 4008313
Orion - User Manual, part number: 6984913
Pegasus Transport Stream Re-multiplexer - User's Guide, part number: 6985137
Pegasus XT Transport Stream Re-multiplexer - User's Guide, part number: 6985128
Puson TV Modulator - User's Guide, part number: 6984904
Quantum QAM IF Modulator - User's Guide, part number: 6984902
Quantum RF QAM Modulator - User's Guide, part number: 6984901
Quasar MkII - User Manual, part number: 6984897
Redus MkII Source Selector - User's Guide, part number:6984283
Sierra Router, part number: 6985050
Sirius IF/RF Upconverter - User's Guide, part number: 6984866
Spectra QAM Demodulator - User's Guide, part number: 6984858
Stratos, part number: 6985050
Tektronix VM10X - User Manual, part number: 6984285
Titan IRD - User Manual, part number: 6984850
Titan MkII Digital Satellite Receiver - User's Guide, part number: 6984849
Protocol Drivers
Apollo MkII - User's Guide, part number: 4001750
BTS Router Protocol, part number: 6985050
CCU Protocol - User Manual, part number: 6985071
Elenova/Drake - User Manual, part number: 6984290
Equipment Dialup Protocol - User Manual, part number: 6985055
ICMP Protocol Driver - User's Guide, part number: 6984459
IIOP Protocol Driver - User's Guide, part number: 6985041
Iris iNed Protocol - User Manual, part number: 6985008
Iris Router Protocol, part number: 6985050
RCDS Protocol Driver - User's Guide, part number: 6984895
SNMP Protocol Driver - User's Guide, part number: 6984859
4014778 Rev H xxi

Preface
Trilithic Protocol - User Manual, part number: 6984848

Task Drivers
Autoleveling - User's Guide, part number: 6984080
Digital Headend Backup - User's Guide, part number: 6985066
Dish Backup - User's Guide, part number: 6985065
EPG Scheduler - User's Guide, part number: 6985057
Notification Task - User's Guide, part number: 6984914
Performance Data Compression - User Manual, part number: 6984908
Performance Logging - User's Guide, part number: 6984862
Receiver Modulator Backup - User's Guide, part number: 6984893
SI Correlator - User's Guide, part number: 4006551
SI Distributor - User's Guide, part number: 6984868 15
SI Editor - User's Guide, part number: 6985061
SI Import Agent - User's Guide, part number: 4006552
SNMP Agent - User's Guide, part number: 6984864
UPS Battery Monitoring - User Manual, part number: 6984275
Video Analysis Task - User Manual, part number: 6984838
xxii 4014778 Rev H

1 Chapter 1
Introducing ROSA NMS
Introduction
This chapter gives more information about Cisco's ROSA Network
Management System and the ROSA NMS extensions.
In This Chapter
About the ROSA Network Management System............................... 2
General Add-On Components for ROSA NMS.................................. 5
4014778 Rev H 1
Chapter 1 Introducing ROSA NMS
About the ROSA Network Management System

Introduction
Cisco's ROSA Network Management System (NMS) manages and monitors
equipment and services in entire fiber optic digital transport networks, analog
transport networks, broadcast, contribution applications, the headend, all hub sites,
all the way out to the last amplifier in the outside plant.
The ROSA NMS systems open software architecture covers nearly all aspects of
service management, network management and element management for a network.
In its basic framework, ROSA NMS can handle alarm logging, do performance data
logging, performs interconnection modeling and configuration data storage.
By adding any of several readily available, off-the-shelf ROSA NMS extensions, the
ROSA NMS system can be fine-tuned to application specific requirements. These
ROSA NMS extensions are:
ROSA NMS Notification Task
ROSA NMS Group-wise Equipment Manager
ROSA NMS Digital Headend Backup Task
ROSA NMS Analog Headend Backup Task
ROSA NMS Reporting
ROSA NMS Performance Logging Task
ROSA NMS Performance Data Compression Task
ROSA NMS Service Availability Reporting
ROSA NMS Macro Component
ROSA NMS UDD Profile Manager
ROSA NMS SNMP Profile Manager
ROSA NMS DVB SI-Editor
ROSA NMS Multi-Encoder Manager
ROSA NMS iLynx Backbone Model
ROSA NMS HFC Alarm Correlation
ROSA NMS UPS Battery Maintenance Task
Ingress Monitoring Component
ROSA NMS ATM Service Management
2 4014778 Rev H
About the ROSA Network Management System
More information concerning these ROSA NMS extensions can be found in topic
ROSA NMS General Add-On Components further in this chapter.
Features and Benefits

The features and benefits of the ROSA NMS software are:
Multiple views on status of your network (interconnection, layout, geographical,
)
Alarm correlation
Graphical and textual performance and availability (SLA) reporting tools
Predefined automation tasks, customizable by means of scripting
Common look and feel
Highly flexible and scalable system
Easy integration of third party equipment
ROSA NMS Software Versions

The ROSA NMS software is available in three versions, providing low cost entry and
practically unlimited growth potential, due to its client-server architecture.
ROSA NMS Client/Server
This version unleashes the full power of the ROSA NMS system by running all
core functionality on a Copernicus server or SI-Server. ROSA NMS clients give
an accurate view on the status of each site managed by the servers. And since
the processing load is distributed, system growth is virtually unlimited.
ROSA NMS Single User
The single user version provides full management system functionality for a
single computer. The server software and the ROSA NMS client run on the
same computer.
ROSA NMS Device Configuration Shell
This basic version offers access to device drivers, allowing you to configure your
devices in a user-friendly way.
4014778 Rev H 3
System Requirements
The computer that is used to run the ROSA NMS Client, ROSA NMS Single User, or
ROSA NMS DCS software must meet or exceed the following minimum hardware
and software requirements:
Item Requirements
Minimum Recommended
Processor 600 MHz Pentium III or 1 GHz Pentium III or compatible or
compatible or higher higher
Memory Minimum 192 MB 512 MB RAM
Free Hard disk 1 GB 10 GB
space
Operating System Windows 2000, Windows Server 2003, Windows XP, or Windows
Vista
Web browser Internet Explorer version 5 or later.
Serial ports One or more Serial Ports (RS-232 and/or RS-485) if serial
communication is needed
Ethernet Adapter Required
4 4014778 Rev H
General Add-On Components for ROSA NMS

ROSA NMS Notification Task
Notification Task
The Notification Task allows ROSA to send alarm notifications to maintenance
engineers via pager, SMS and e-mail. This task is highly configurable; different
rules and schedules can be defined for each scenario and service technician.
Pager, email and SMS
Creation of user groups (resource/application) and schedules
Fine-grained customization
ROSA Advanced Configuration

Group-wise Equipment Manager
The Group-wise Equipment Manager is a reporting and configuration tool:
parameters can be set or read for a group of equipment and it also allows you to
copy the configuration of a device and apply it to one or more network elements
supporting the same parameters, regardless of its vendor. Group reports can be
exported to any Windows application as well as to HTML format.
Highly customized and efficient configuration of groups of equipment
Get a snapshot of the settings and status of a group devices
Easy to set and restore configurations (backup and restore)
Efficient tabular editing and printing
ROSA NMS Automation and Redundancy Tasks

Digital Headend Backup Task
The Digital Headend Backup Task provides device or transport stream redundancy
in a digital headend. This task analyzes the headend topology and divides it into a
number of sections related to certain functionality. Depending on the number of
predefined alarm triggers, an alarm correlation is performed for the different alarms
over a predefined observation interval. Based on the diagnosis, a number of
backup actions are performed on the devices. Afterwards, a post evaluation of the
system is done to search for remaining alarms.
Support for receivers, decoders, scramblers, descramblers, encoders,
(re)multiplexers, transraters, upconverters, fiber optic transport, modulators...
4014778 Rev H 5
Triggered by device alarm, I/O contact closure or channel alarm

Supports different router configurations
Analog Headend Backup Task

The Analog Headend Backup Task provides automatic backup for outgoing analog
TV channels in case of a receiver, modulator or up-converter failure. The task has
two parts: a receiver backup and a modulator/up-converter backup. Both parts
work independently, but if required, they can exchange information. The task uses
equipment alarms from our Line Monitoring device LM 860 and the ROSA NMS
interconnection database to reroute signals to the available backup equipment.
Support for receivers, decoders, modulators and up-converters
Triggered by device alarm, I/O contact closure or channel alarm
ROSA NMS Performance and Trending

Reporting Component
The Reporting Component is part of the basic ROSA NMS package and makes it
possible to quickly analyze your network performance and service availability to
drive preventive maintenance actions by focusing on the weakest part of the
network. Graphic and text reports can be specifically customized to fit your needs
for identifying pro-active maintenance opportunities, lowering costs and downtime.
Graphical reports are available for comparing the quality of different services,
comparing performance at different network locations and for plotting performance
evolution over time. Comparisons can begin with a general query, involving
multiple sites and services, and be refined to pinpoint the problem by narrowing the
selection and range of data.
The ROSA NMS reporting system not only focuses on historical data, but can also
produce graphs that display the most up-to-date performance measurements.
Two types of reports: comparison and trending
Graphical and textual reports
Find the weakest spot of your network
Proactive performance management tools
Prove your service availability
6 4014778 Rev H
Performance Logging Task

The Performance Logging Task adds performance-logging capabilities to any SNMP
managed device and with help of proxy MIBs and plug in scripts also to devices
without SNMP support. Performance analysis, trending capabilities and quality of
service data are stored in the Copernicus Quality of Service (QoS) database. The
Performance Logging Task records the minimum, maximum and average of the
different samples based on a pre-set logging time interval and stores the calculated
results in the database, keeping the amount of data limited while not losing
exceptional samples. The data that is logged can be viewed with the Reporting
Component to generate any kind of report, such as comparison and evolution
reports.
Log performance data at user-defined intervals
Highly customizable (define equipment groups and select SNMP parameters)
One database record contains multiple samples (min, max and average values)
Performance Data Compression Task

The Performance Data Compression Task provides automated database
maintenance and compresses logged data in the Copernicus Quality of Service (QoS)
database. The task combines older measurement records into new summary
records that still contain the maximum, minimum and average measured values.
The compression behavior of the task can be programmed in simple rules and will
only combine records that have been measured for the same network element and
parameter. The Performance Data Compression Task can be configured to leave all
recent records untouched, while compressing the older records. It is also possible
to define rules that delete older records instead of compressing them.
Combines many measurement records without loosing minimum and maximum
Programming in simple compression or deletion rules
Service Availability Reporting Component

The Service Availability Reporting Component enables you to visualize the
availability of digital services in your headend and distribution network. This
component translates the device status information and alarm messages into service
availability data, which is logged in the Copernicus Quality of Service (QoS) database.
When creating a report a wizard helps to specify the time frame and the services of
which availability data is displayed. Automated database maintenance of
availability data in the QoS database can be done with the Performance Data
Compression Task.
Generates reports of the service availability in a headend and distribution
network
Wizard to help creation of graphical and textual reports
Reports show availability in percentage or outage in errored seconds
4014778 Rev H 7
ROSA NMS Macro Component

The Macro Component allows you to manipulate and execute a predefined set of
macros on a number of resources. A macro can range from a single action on a
device to a full script that interacts with several devices. Macros can have a wide
set of parameters such as numbers, strings, devices or other resources. With the
Scheduler tool, you can determine when a macro is executed. The Scheduler
supports single shot and recurring macro schedules: a single shot macro is executed
only once at a specified date and time, a recurring macro schedule follows a
schedule that is defined with help of the ROSA NMS Schedule Database
Component.
Execute predefined set of macros
Support of single shot and recurring macro schedules
Third Party Equipment Integration Tools

UDD Profile Manager
The Universal Device Driver (UDD) Profile Manager design tool manages any
equipment with I/O contacts, without software development. It is possible to
create your own configuration menus and to define the graphical bitmap of all the
devices and their status in the ROSA NMS network maps. Additionally, you can
define the input conditions at which the driver must generate alarms or change the
device bitmap. Once you complete the driver definition it can be reused for many
applications.
Manage any equipment with I/O contacts
Guarantees freedom of equipment choice for a future save solution
High-level view on status and control information
Configurable scaling and grouping of I/O
Graphical representation of the device state on the ROSA NMS topological maps
Very well suited for small remote sites connected with IP
SNMP Profile Manager

The SNMP Profile Manager is a design tool that lets you integrate any brand of
network equipment at lowest cost, without software development. Its unique
concept makes it possible to integrate the devices in minutes instead of months. A
profile is created with simple mouse clicks in the graphical driven user interface and
an SNMP driver is generated that can be installed in ROSA NMS. For certain Cisco
equipment off the shelf profiles are available, which can be customized to your needs.
To integrate third party equipment, use the MIB files of the third party vendor to
create your profile.
8 4014778 Rev H
Highly reliable integration; no software development involved

Customize your view on the equipment and its alarm traps at any time
Drag-and-drop graphical user interface creation
Automatic SNMP trap to ROSA NMS message mapping with help of a wizard
Animated representation on the ROSA NMS topological maps
ROSA NMS Headend Applications

Modulator Auto-leveling Task
The Auto-leveling Task aligns the RF levels for all outgoing RF channels of a
headend by using RF level measurements data from our Line Monitoring device LM
860. The task knows the target RF levels for each type of service and will
automatically adjust the RF output level for each channel. The task will perform the
autoleveling function periodically based on a programmable interval. This task can
align both analog and digital carriers.
Automatic alignment of the RF levels
Analog and digital carriers
ROSA NMS DVB SI-Editor

The DVB SI Editor serves as a user-friendly offline-editing tool for creating and
editing DVB PSI and SI tables. All main PSI/SI tables and descriptors (PAT, PMT,
NIT, SDT, BAT, CAT, AIT and EIT P/F) are supported. The DVB SI-Editor
automatically recognizes the different tables and descriptors, ensuring correct format
and CRC. Tables are stored to disk in a DVB standardized binary format ready to
be inserted in a transport stream. The DVB SI Editor creates, saves and forwards
the new PSI/SI tables to different Continuum DVP D9600 Series or Digital Content
Manager (DCM) devices connected to the LAN network.
Creating and editing of DVB PSI and SI tables
Adding of private descriptors
Multi-Encoder Manager
The ROSA Multi-Encoder Manager (MEM) is designed for the management of
multiple encoding programs within a digital headend or playout. The MEM allows
easy allocation of program priorities and calculation of bit rate budgets to maximize
the effectiveness of your system. The simple, but powerful, user interface makes it
is easy to make setting changes that maximize the use of your bandwidth resources.
Calculate transport stream bit rate budgets for complete control over bandwidth
allocation of individual channels
Maximize the use of your bandwidth resources
4014778 Rev H 9
Fine tune statistical multiplexing for all services

Easy and effective PID management
Automatic pre-filtering option
Video Analysis Task

The Video Analysis Task monitors the analog TV services, generates alarms if video
parameters exceed their thresholds, and logs the video quality of the services over a
longer period. The task can be configured to perfectly suit your baseband video
measuring requirements, which allows detecting and solving problems before you
notice a degradation of the service. The logging results can be viewed with the
ROSA NMS Reporting Component.
Monitor analog TV services
Generate alarms if video parameters exceed their thresholds
Log service video quality

The iLynx Backbone Model is a powerful software component offering centralized
management of all connections in an iLynx backbone without need for individual
element interaction. Intuitive graphical user interfaces help you to easily define
your network topology, signal paths and protection paths. Comprehensive
overview screens give you an idea of the free/occupied network bandwidth and the
impact of network failures on services. The iLynx Backbone alarm correlation limits
the number of alarms to a minimum and reports the root cause for quick
intervention and problem solving. Redundancy backup of iLynx tributaries and the
connected equipment is supported in ROSA NMS Digital Headend Backup.
Easy configuration and centralized management of the connections of your
iLynx backbone
Overview of free/occupied bandwidth of each network segment
Instant view of alarm conditions
Alarm correlation and root cause analysis
10 4014778 Rev H
ROSA NMS HFC Network Monitoring

HFC Alarm Correlation
HFC Alarm correlation limits the number of alarms while pinpointing the root cause
at the same time. This topological alarm correlation module will match each
incoming alarm with the network topology model and highlight the alarms
(probable) root cause/location in the alarm log viewers and the ROSA NMS
topological maps. The correlation is executed by means of scripts on the
Copernicus network management server, based on the alarm correlation rules that
can be customized to the operators network.
Limiting the number of alarms extensively
Pinpointing the root cause alarm
Correlation of alarms into service availability
Customizable rules by means of scripts
UPS Battery Maintenance Task

The UPS Battery Maintenance Task measures the Uninterruptible Power Supply
(UPS) batteries discharge at scheduled times and shows the status in an overview.
Batteries and UPS systems are the most vulnerable elements in todays HFC
networks: to assure good operation maintenance is a requirement. The UPS Battery
Maintenance Task can do this maintenance automatically and reports the battery
status to the ROSA NMS. The task is able to work with all power supply systems
that are monitored by means of a UPS monitoring transponder.
Instant status report on the batteries
Long term evaluation of batteries
No network availability risk in case of real power failure
Comprehensive reports
Ingress Monitoring Component

The Ingress Monitoring Component is a high-level software component for
monitoring and analyzing the return path noise over time. The Ingress Monitoring
Component monitors noise real-time, which is very useful in case of
troubleshooting. It also reports alarms to indicate the place where a quick
intervention is needed. Alarm thresholds are programmable and different rules can
be defined to report only the most relevant alarm messages. Evaluation of the noise
over time makes trend analysis possible to react proactively. Based on the logging
of the observations for all return paths, a prediction can be made of the time at
which new investments in the network become mandatory to maintain the desired
quality targets.
4014778 Rev H 11
Comparing different branches helps to find the weakest spot of your network and to
focus maintenance efforts. Intuitive spectrum reports provide quick overview of
minimum, maximum, average and impulsiveness of the ingress noise.
Real time views and alarm logging
Intelligent alarm generation and filtering
Comprehensive noise spectrum visualization
Best/worst performing branch
Long-term noise analysis
Actual measurement, Min/Max/Hold views and histogram views
Contribution
ATM Service Management
The ATM Service Management Component is a service layer in ROSA NMS that
takes the complexity out of setting up and managing multiple ASI connections
across an ATM network. Prior operators handling contribution or primary
distribution networks had to call up a GUI for each involved ATM adaptor every
time a new connection had to be established, changed or torn down. Now, with the
ATM Service Management Component, this is all easily managed from one intuitive
GUI, lowering the risk of making mistakes.
Manage complex networks with multiple connections between multiple ATM
adaptors
Easy to use GUI (Graphical user interface) with ASM
Supports Alcor ATM adaptors and ASI services, supports PVC and SVC
connections
Supports point-to-point and point-to-multipoint connections
12 4014778 Rev H
2 Chapter 2
Installing the ROSA NMS
Software
Introduction
This chapter describes how to prepare the computer before starting the
ROSA NMS software installation process and the procedure to install
the ROSA NMS software.
In This Chapter
Introduction ........................................................................................... 14
To Install the ROSA/Copernicus Software....................................... 15
4014778 Rev H 13
Chapter 2 Installing the ROSA NMS Software
Introduction
The ROSA/Copernicus installation CD-Roms contains the three available versions of
the ROSA NMS software:
ROSA NMS Client
ROSA NMS Single User
ROSA NMS Device Configuration Shell
Only the ordered version can be installed, the version must match the received
license file.
Note: The ROSA NMS software running on a Windows 2000, Windows XP,
Windows Server 2003, or Windows Vista requires additional software components.
Before starting the installation process of ROSA NMS, these software components
should be installed. The procedure to install these components as well as the
procedure to ROSA NMS can be found in the readme.htm file on disk 1 of the
ROSA/Copernicus installation CD-roms.
14 4014778 Rev H
To Install the ROSA/Copernicus Software

The following procedure explains how to install the ROSA/Copernicus installation
software.
Notes:
The installation process can also be aborted by pressing the Cancel command
button on the InstallShield Wizard dialog.
When ROSA NMS software is installed on a laptop, the laptop must be removed
from its docking station.
1 Insert the ROSA/Copernicus installation CD-Rom labeled with disk 1 in the
CD-Rom drive of the computer.
Result: If Autoplay is enabled, the readme.htm file displays.
2 Follow the procedures described in this readme.htm file and click on the ROSA
setup link to start the Setup.exe.
Or
Browse to one of the following locations on the CD-Rom depending on the
ordered version and run Setup.exe.
ROSA NMS Client installation: Setup \ ROSA
ROSA NMS Single User installation: Setup \ ROSA_SU
ROSA NMS Device Configuration Shell installation: Setup \ ROSA_DCS
Result: The Installshield Wizard is started.
3 Click on the Next > command button.
4014778 Rev H 15
Result: The License Agreement step in the InstallShield Wizard is displayed.
4 Read the license agreement carefully.

5 Press the Yes command button if you accept the terms of this agreement,
otherwise press the No command button.
Result: The Choose Destination Location step in the InstallShield Wizard
dialog is displayed.
Note: By default, the ROSA NMS software is installed in the following folder on
the hard disk:
16 4014778 Rev H
ROSA NMS Client installation: \ Program Files \ Scientific-Atlanta \ ROSA

or \ Program Files \ Cisco \ ROSA
ROSA NMS Single User installation: \ Program Files \ Scientific-Atlanta \
ROSASingleUser or \ Program Files \ Cisco \ ROSASingleUser
ROSA NMS Device Configuration Shell installation: \ Program Files \
Scientific-Atlanta \ ROSADevConfShell or \ Program Files \ Cisco \
ROSADevConfShell
6 Click on the Browse command button to choose another destination folder to
install ROSA NMS.
7 Click on the Next > command button when ready.
Result: The Setup Type step in the InstallShield Wizard is displayed.
8 Select the Setup Type.

Typical: recommended setup type
Compact: installs only the minimum required components. The Help files
are not installed.
Custom: allows you to choose the components you want to install.
Result: The Select Components step in the InstallShield Wizard is displayed
when the Custom setup type is selected.
4014778 Rev H 17
Notes:
Depending on the ROSA NMS version, the number of components that can
be cleared or set is different.
It is recommended to leave all components selected.
Note: The BarcoNet DayTime Service can be used to synchronize the time of
devices like Phoenix, Pegasus... with the ROSA NMS system.
Result: The Select Program Folder step in the InstallShield Wizard is displayed.
18 4014778 Rev H
A new program folder is proposed and the existing folders are listed. The name
of the proposed new program folder can be changed or an existing folder can be
chosen.
11 Click on the Next command button.
Result: The Administrative User Account step in the InstallShield Wizard is
displayed.
Note: During a ROSA NMS Client software installation both the Administrative
User Account step and the SQL Server System Administrator step in the
InstallShield Wizard are omitted.
12 In the User Name box, enter the user name of an account with administrator
privileges for the computer. The Copernicus server software will run as this
account.
Note:
Using a local account (non-domain) is recommended.
On computers running Windows XP or Windows Server 2003 accounts with
empty passwords are not allowed.
13 In the Password and Confirm Password box, enter the password for the account.
Result: The SQL Server System Administrator step in the InstallShield Wizard
is displayed.
4014778 Rev H 19
15 In the Password box, enter the SQL Server System Administrator password. By
default, this password is empty or set to the initial ROSA NMS Administrator
password which can be found on the paper in the sleeve of the
ROSA/Copernicus installation CD-Roms.
Note: When the ROSA System is working with an existing database system, the
administrator password for this database system must be entered.
Result: After completing the ROSA NMS software installation, the computer
must be rebooted.
20 4014778 Rev H
17 Point to the Yes, I want to restart my computer now. selection button if the
computer must be rebooted directly or the No, I will restart my computer later.
selection button if the reboot action must be postponed.
18 Click on the Finish command button.
4014778 Rev H 21
3 Chapter 3
Using the ROSA NMS User
Interface
Introduction
This chapter describes the work environment and the user interface
components that will be encountered by using the ROSA NMS User
Interface.
In This Chapter
About ROSA NMS User Interface ...................................................... 24
ROSA NMS User Interface Window .................................................. 25
About the Server Explorer................................................................... 36
Changing View Options ...................................................................... 44
4014778 Rev H 23
Chapter 3 Using the ROSA NMS User Interface
About ROSA NMS User Interface

The User Interface of the ROSA NMS system is provided with several components.
The illustration below shows the main components of the ROSA NMS user interface.
The main components of the ROSA NMS User Interface are:

Title bar
Menu bar
Server Tools and Map Tools toolbars
Server Explorer box with Server Explorer tree
Map Explorer box with Map Explorer tree
Status bar
Work space with Maps
These components are described further in this chapter.
24 4014778 Rev H
ROSA NMS User Interface Window

About the Title Bar
The Title bar of the ROSA NMS User Interface reflects the ROSA control icon, the
name of the application, and the standard Microsoft buttons. When maps are
opened, the name of the active map appears in the Title bar between [ ] brackets.
The following illustration shows the Title Bar of the ROSA NMS User Interface with
open Maps.
Note: Floating toolbars, maps, the floating Server Explorer, the floating Map
Explorer, and the Color Palette are also provided with a Title bar.
Double-clicking on the Title bar toggles between the maximized and the restore size
of the ROSA NMS User Interface.
About the Standard Windows Buttons on the Title Bar

The standard Windows buttons, which can be used to resize or close the ROSA NMS
User Interface, are located on the right hand side of the Title bar. The following
picture shows the buttons on a maximized user interface and on a resized user
interface.
The table below describes the buttons that can be found on a Title bar.
Button Name Description

Minimize Minimizes the User Interface
Maximize Maximizes the User Interface to the available work space
Restore Returns the User Interface to its last non-minimized and

non maximized position and size
Exit Closes the User Interface
Note: The Server Tools, Map Tools toolbar, and Color Palette are only provided with
the Exit button.
4014778 Rev H 25
About the ROSA Control Icon and ROSA Control Menu

The ROSA Control icon, which can be found at the left hand side of the Title bar,
provides access to the Control menu of the ROSA NMS User Interface. By
right-clicking on the ROSA Control icon, the ROSA NMS User Interface Control
menu displays. The commands in this Control menu can be used to re-position, to
resize, and to close the ROSA NMS User Interface.
The following picture shows the ROSA NMS User Interface Control menu.
Note: Double-clicking on the ROSA Control icon will close the ROSA NMS User
Interface.
About the ROSA NMS User Interface Menu Bar

The Menu bar of the ROSA NMS User Interface represents the menu headings of the
application. The following picture depicts the Menu bar of the ROSA NMS User
Interface.
When the Editing/Operational map mode of the ROSA NMS User Interface is set to
Editing, the Menu bar of the User Interface is enlarged with three menus. The
following picture show an enlarged Menu bar.
26 4014778 Rev H
Each menu contains a list of menu items. Some of these menu items carry out
commands immediately, others display a dialog, and others set or clear parameters.
If a menu item is followed by '...', a dialog will be displayed after pointing to.
Selected An arrow indicates an
Menu available sub menu
Grayed menu items

are not available in
the current context
Clicking an menu item will cause

the command to be carried out or
the dialog to be opened
Menu items that can

be set or cleared
About the ROSA NMS Status Bar

The Status bar of the ROSA NMS User Interface, located along the bottom of the user
interface, gives the user the following information:
The current messages
The severity level of the pending message with the highest severity
The current user of the server
The current server
The zoom percentage of the map
The Status bar of the ROSA NMS User Interface is also provided with a number of
buttons. The table below describes these buttons.

Left arrow Scrolls through the current messages (down)
Right arrow Scrolls through the current messages (up)
Message Opens the Message Information box of the current message
4014778 Rev H 27
The following picture depicts the Status bar of the ROSA NMS User Interface.
Right arrow
button
Left arrow Message
button button
Current Pending Current Current Map zoom

message status user server percentage
The ROSA NMS User Interface allows hiding and displaying the Status bar. In the
View menu tick Status Bar to display the Status bar or clear Status Bar to hide the
Status bar.
Using Shortcut Keys

Particular tools and actions can be selected by using shortcut keys. Most shortcuts
keys involve the [Alt], [Ctrl], or [Shift] key in combination with another key. Some
shortcuts are activated by a Function key, such as pressing <F1> to display online
help, or pressing <F3> to choose the find next resource command. These shortcut
keys are listed in the menus and tooltips.
The following table lists the shortcut key, which are always applicable.
Shortcut Key Function

[Ctrl] + [B] Configuration screen bitmaps
[Ctrl] + [D] Configuration screen drivers
28 4014778 Rev H

[Ctrl] + [E] Open/Close server explorer
[Ctrl] + [F] Find resource
[Ctrl] + [L] Open device locations
[Ctrl] + [M] Open/Close map explorer
[Ctrl] + [Q] Graphical quality statistics
[Ctrl] + [R] Configuration relations
[ESC] Cancel Edit
[F1] Help
[Shift] + [F1] Context help
[F3] Find next resource
[F4] Terminate Copernicus server
[F5] Refresh
The following table lists the shortcut key, which are only applicable when the map
mode is set to Editing.

[Ctrl] + [I] Import file
[Ctrl] + [S] Save file
[Ctrl] + [F4] Close file
[Ctrl] + [P] Print file
[Ctrl] + [A] Select all
[Ctrl] + [X] Cut selected objects
[Ctrl] + [C] Copy selected objects
[Ctrl] + [V] Paste selected objects
[DEL] Delete selected objects
[+] Move Object forward
[Ctrl] + [+] Move Object to the front
[-] Move object backwards
[Ctrl] + [-] Move object to the back
[Ctrl] + [Alt] + [T] Align the top of the selected objects
[Ctrl] + [Alt] + [B] Align the bottom of the selected objects
[Ctrl] + [Alt] + [L] Align the left of the selected objects
[Ctrl] + [Alt] + [R] Align the right of the selected objects
4014778 Rev H 29

[Ctrl] + [Alt] + [S] Make same size both
[Ctrl] + [Alt] + [H] Make same size horizontal
[Ctrl] + [Alt] + [V] Make same size vertical
[Alt] + [Enter] Open object properties
[Ctrl] + [T] Open/Close tool palette
[Ctrl] + [G] Object group
[ESC] Cancel / Select tool
[A Arc tool
[E Ellipse tool
[G Show grid
[I Bitmap tool
[L Line tool
[M Map tool
[N Roundrect tool
[Ctrl] + [O] Color palette
[P Polygon tool
[R Rectangle tool
[S Enable/Disable snap to grid
[T Text tool
[Z Switch between zoom and select tool
Tool Bars
Introduction
The User Interface of the ROSA NMS system is provided with two toolbars: the
Server Tools toolbar and the Map Tools toolbar.
The Server Tools toolbar is default visible. This toolbar can be hidden by pressing
the Exit button in the Title bar if the toolbar is floating or by clearing the Toolbar
menu item in the View menu. The toolbar can be made visible by ticking the
Toolbar menu item in the View menu.
30 4014778 Rev H
The Map Tools toolbar becomes visible if the Editing/Operational map mode is set to
editing. When the toolbar is floating, the toolbar can be closed by pressing the exit
button in the Title bar of the toolbar. The toolbar can be made visible again by
changing the Editing/Operational map mode to Operational and back to editing.
Toolbars can be attached to one of the edges of the ROSA NMS User Interface
workspace (called docked toolbar) or can be undocked and moved anywhere on the
workspace of the ROSA NMS User Interface (called floating toolbar). The picture
below shows a floating toolbar and a docked toolbar.
Making a toolbar floating: A docked toolbar can be made floating by dragging

and dropping the toolbar in the workspace of the ROSA NMS User Interface.
Making a toolbar docked: A floating toolbar can be made docked by moving a
floating toolbar to the edge of the workspace of the ROSA NMS User Interface.
Moving a Docked Toolbar to another Edge of the Workspace: A docked toolbar
can be moved to another edge of the workspace by dragging and dropping the
toolbar to the other edge.
Resizing a floating Toolbar: The size of a floating toolbar can be changed by
moving the pointer over an edge of the toolbar until it change to a
double-headed arrow and dragging the edge.
4014778 Rev H 31
About the Server Tools Toolbar

The Server Tools toolbar gives quick access to commonly used commands on the
ROSA NMS User Interface.
The table below describes the buttons on the Server Tools toolbar.

Units Opens the Units dialog
Find Opens the Search dialog
Refresh Explorer Refreshes the Server Explorer tree
Resource Drivers Opens the Installed Drivers dialog
Bitmaps Opens the Installed Bitmaps dialog
Serial Ports Opens the Server Serial Port Configuration dialog
Relations Opens the Relations dialog
Locations Opens the Locations dialog
Attributes Opens the Attributes dialog
View Messages Opens the Message Viewer box with the messages
using Default Filter specified in the message filter
All Messages Opens the Message Viewer box with all messages
Not Acknowledged Opens the Message Viewer box with the messages that are
Messages not yet acknowledged
Pending Messages Opens the Message Viewer box with the pending
messages
Graphical Quality Opens the Reporting component
Statistics
Selection Tool Activates the selection tool
Zoom Tool Activates the zoom tool
Parent Map Displays the parent map of the selected map
Toggle Editing Toggles between Editing map mode and Operational map
Mode mode
32 4014778 Rev H

Toggle Legend Opens and closes the Legend dialog
Help Opens the online help
About the Map Tools Toolbar

When the ROSA NMS system is set in map Editing mode, the Map Tools toolbar is
displayed. This toolbar gives quick access to commonly used commands for editing
maps.
The following table describes the buttons on the Map Tools toolbar.

Save Map Saves the current map
Print Prints the current map
Cut Cuts the selected objects and store them in the clipboard
Copy Copies the selected objects to the clipboard
Paste Pastes the content of the clipboard in the map
Line Tool Draws straight lines
Rectangle Tool Draws squares and rectangles
RoundRect Tool Draws squares and rectangles with rounded corners
Ellipse Tool Draws circles and ellipses
Polygon Tool Draws polygons and freehand curves
Arc Tool Draws arcs
Bezier Tool Draws fluent curves
Text Tool Adds text to the map
Relations Tool Draws relations between server resources
Bitmap Tool Imports bitmap images into a map
Map Tool Creates links to new or existing maps
4014778 Rev H 33

Grid Toggle Displays or hides the grid lines
Toggle Snapping Enables or disables snapping to the grid points
Color Palette Displays or hides the Color Palette
About the Color Palette

Introduction
In maps, the Color Palette can be used to change the color of lines, shapes, objects,
and text. The following picture shows the Color Palette.
The Color Palette has three areas:

The largest area is the Spectrum area.
The bottom left area is the Preview area. When the mouse is moved over the
spectrum area, the color indicated by the mouse is shown in the Preview area.
The bottom right area is the Pick area. When you click in the Spectrum area, the
corresponding color appears in the Pick area. This area preserves this color until
another color is selected.
The Color Palette can be used to perform the following actions:
Adjust the color of an object in a map: select it and then click on the desired color
in the Spectrum area.
Copy the color of an object in a map to the Pick area: select the object and then
click the Preview area.
For more information concerning maps, please refer to topic Working with Maps on
page 261.
34 4014778 Rev H
Handling the Color Palette

Displaying the Color Palette: The Color Palette can be made visible by ticking
the Color Palette menu item in the View menu or by clicking on the Color Palette
button in the Map Tools toolbar.
Note: The Color Palette is only applicable when the Map mode is set to Editing.
Hiding the Color Palette: The Color Palette can be made invisible by clearing the
Color Palette menu item in the View menu, by pressing the Exit button in the
Title Bar of the Color Palette, or by clicking on the Color Palette button in the Map
Tools toolbar.
Making the Color Palette floating: A docked Color Palette can be made floating
by dragging and dropping the Color Palette in the workspace of the ROSA NMS
User Interface.
Making a Color palette docked: A floating Color Palette can be made docked by
moving a floating palette to the edge of the workspace of the ROSA NMS User
Interface.
Moving a Docked Color Palette to another Edge of the Workspace: A docked
Color Palette can be moved to another edge of the workspace by dragging and
dropping the palette to the other edge.
Opening the Legend of the Icons used by the ROSA NMS System
The following procedure explains how to open the legend dialog of the ROSA NMS
system.
1 In the View menu of the ROSA NMS user interface, tick the Legend menu item.
2 Result: The Legend dialog is displayed.
4014778 Rev H 35
About the Server Explorer

Introduction
The resources of the ROSA NMS system are expressed using trees: the Server
Explorer tree and the Group Explorer tree.
The following picture depicts a Server Explorer and a Group Explorer tree of a
ROSA NMS Single User system.
In the Server Explorer tree, which can be found on the Global tab of the Server
Explorer box, the resources are categorized in different groups, these groups are:
Serial ports
Protocol drivers
Units
Tasks
Channels
Services
Additional Components
Configurations
Reports
When groups of devices are defined, these groups can be accessed using the Group
Explorer tree on the Groups tab of the Server Explorer box.
36 4014778 Rev H
Manipulating the Server Explorer Box

The Server Explorer and the Groups Explorer of the ROSA NMS system are
accommodated into a separate box, called Server Explorer box. This box is default
docked, meaning the box is attached to one of the edges of the workspace of the
Making a docked Server Explorer box floating: A docked box can be made
floating by dragging and dropping the box into the workspace of the ROSA NMS
User Interface.
Making a floating Server Explorer box docked: A floating box can be made
docked by moving the floating box to one of the edges of the workspace of the
Moving a docked Server Explorer box: A docked box can be attached to another
edge of the workspace of the ROSA NMS User Interface by dragging and
dropping the box to the other edge.
Moving a floating Server Explorer box: A floating box can be moved by
dragging the box over the screen.
Note: To prevent docking the floating box, Allow Docking can be switched off.
Therefore right-click in the box and clear the Allow Docking menu item in the
short-cut menu.
Resizing a docked Server Explorer box: A docked box can be resized by moving
the pointer over the edge of the box nearest the workspace of the ROSA NMS
User Interface until the pointer changes to a double-headed arrow, and dragging
this edge.
Resizing a floating Server Explorer box: A floating box can be resized by
moving the pointer over an edge of the box unit the pointer changes to a
double-headed arrow, and dragging this edge.
Hiding the Server Explorer box: The Server Explorer box can be hidden by:
- clearing Server Explorer in the View menu,
- pressing and holding down the <Ctrl> key and pressing the <E> key,
- right-clicking in the Server Explorer box and selecting Hide in the short-cut
menu,
- clicking on the Exit button in the Title bar of the floating Server Explorer box.
Viewing a hidden Server Explorer box: A hidden Server Explorer box can be
made visible by:
- ticking Server Explorer in the View menu,
- pressing and holding down the <Ctrl> key and pressing the <E> key.
4014778 Rev H 37
Browsing Through an Explorer Tree

You can browse through the Server Explorer or Group explorer tree by collapsing
or expanding branches. A branch that can be expanded is indicated by a + sign and
an expanded branch is indicated by a - sign. Point to the + sign to expand a branch
and the - sign to collapse a branch.
38 4014778 Rev H
Searching into the Server Explorer Tree

The Server Explorer tree is provided with a search function that can be used to
locate a unit, folder, tasks... in the tree. The following procedure describes how to
use this search function.
1 In the Server Explorer of the ROSA NMS system, right-click on the server on
which the search function must be done.
2 Select Find Resource...
Result: The Search dialog is displayed.
Tip: The Search dialog can also be opened by using the [Ctrl] + [F] shortcut keys.
3 Tick the Find any item in global explorer check box if an item must be located
different from a unit.
4 In the Name box, enter the name or a part of the name of the item that must be
located.
5 In the Additional Info box, type additional information of the item. This box is
only applicable when the Find any item in global explorer check box is not set.
6 Tick the Case Sensitive check box if the search action must be done case
sensitive.
7 Click Find Next to start search.
Result: If an item matches the search criteria, the item will be highlighted in the
Server Explorer tree. For locating the next matching item in the Server
Explorer tree, click Find Next again.
8 Click Close to stop searching for resources.
The Maps tree is provided with a search function that can be used to locate a map.
The following procedure describes how to use this search function.
1 In the Server Explorer of the ROSA NMS system, right-click on the server on
which the search function must be done.
2 Select Find Resource.
Result: The Search dialog is displayed.
4014778 Rev H 39
Tip: The Search dialog can also be opened by using the [Ctrl] + [F] shortcut keys.
3 Select the Find a Map tab.
Result: The following dialog is displayed.
4 In the Name box, enter the name or a part of the name of the map that must be
located.
5 Tick the Case Sensitive check box if the search action must be done case
sensitive.
6 Click Find Next to start the search.
Result: If an item matches the search criteria, the item will be highlighted in the
Maps tree. For locating the next matching item in the Maps tree, click Find
Next again.
7 Click Close to stop searching for maps.
About the Icons Used in an Explorer Tree

Introduction
The icons used in the Server Explorer or Group Explorer tree can be categorized in
three groups:
The Server related icons
The Unit related icons
The Resource related icons
Server Related Icons

The table below describes the icons showing the connection status of a server
Icon Description
a disconnected server
a connected server
40 4014778 Rev H
Icon Description
a master server
a unreachable server
a server in listening mode
The following table describes the server icons showing the highest severity of the
pending messages.
Icon Description
a server of which the highest severity of the pending messages is
(white screen)
Information.
(blue screen)
Warning.
(yellow screen)
Minor.
(red screen)
Major.
(pink screen)
Critical or Indeterminate.
added to a server icon and indicates that a message is not yet
acknowledged.
Notes:
Server icons can be combined. For example the following icon indicates a
master server containing pending messages (with highest severity: Major), which
are not yet acknowledged.
The color representing the alarm severity level is adjustable. The colors shown
in the table are the default colors used by the ROSA NMS system. The
procedure to change these colors can be found in topic Changing View Options on
page 44.
Unit Related Icons

The table below describes the unit icons showing the operational state of a unit.
Icon Description
(gray unit) an active unit
a new unit
4014778 Rev H 41
Icon Description
(green unit) a unit in maintenance state
(deep purple a unit excluded from monitoring

unit)
an inactive unit
a unit that has one or more notes
The table below describes the unit icons indicating the highest severity of the
pending alarms.
Icon Description
(gray unit) a unit without pending messages.
(white unit) a unit of which the highest severity of the pending alarms is
Information.
(blue unit) a unit of which the highest severity of the pending alarms is Warning.
(yellow unit) a unit of which the highest severity of the pending alarms is Minor.
(red unit) a unit of which the highest severity of the pending alarms is Major.
(pink unit) a unit of which the highest severity of the pending alarms is Critical
or Indeterminate.
is added to a unit icon and indicates that a message is not yet
acknowledged.
Notes:
Unit icons can be combined. For example the following icon indicates an active
unit containing pending alarms (with highest severity: Major), which are not yet
acknowledged.
The color representing the alarm severity level is adjustable. The colors shown
in the table are the default colors used by the ROSA NMS system. The
page 44.
Resource Related Icons

The table below describes the icons of the resources used in the Server Explorer tree.
Icon Description
represents a serial port or the serial ports group
42 4014778 Rev H
Icon Description
represents a task and tasks group
represents an analog TV channel
represents a satellite channel
represents a digital channel
represents an analog TV service
represents a protocol driver or the protocol drivers group
represents a component or the components group
represents a configuration or the configuration group
represents a report
represents a group of units
4014778 Rev H 43
Changing View Options

Introduction
In the ROSA NMS system the severity of an alarm is indicated using colors and
is used:
- For the icons in the Server Explorer, Group Explorer, and Map Explorer tree
- In the Message Viewer and Listening Console
- In the Status Bar (pending status pane)
- In the maps (dropped units and gates)
- In the Legend dialog
- For the status icon in the upper right corner of the driver GUIs
The unit used for levels in graphs, RF level settings in a region attribute and so
on is default set to dBmV. The unit can also be set to dBV.
When a resource is in alarm state, the icon indicating the resource in the Server
Explorer, Group Explorer, Map Explorer tree, or map and the Pending Status
field in the Status Bar can blink. Therefore the animation settings must be
adapted.
The user can determine if the icons in the explorer trees and maps will blink if
there is an alarm or will blink only if there is a pending alarm and one or more
unacknowledged messages.
The ROSA NMS system allows printing particular list. The height of the fonts
used in these printouts can be adapted.
The colors used to indicate a backup unit, a unit in maintenance, and a unit taken
over by backup can also be adapted.
44 4014778 Rev H
Changing View Options
The indication of the presence of notes for a resource can be propagated to the
server level in the Server Explorer tree, see picture below.
To Set the View Options

Perform the following steps to change the view options of the user interface.
1 In the ROSA NMS user interface, click on the View menu and point to
Options....
Result: The View Options dialog is displayed.
2 In the Alarms Colors box, select the desired colors in the alarm severity drop
down boxes.
4014778 Rev H 45
3 In the Default Unit drop down box, select dBmV or dBV.

4 In the Animation On Pending Message box, set or clear the Explorer, Map, and
Status bar check boxes.
5 In the Animation On Pending Message drop down box, select the desired
animation: Always, Not Acknowledged Messages., Pending Warnings or Higher,
Pending Minors or Higher, Pending Majors or Higher, or Pending Criticals.
6 In the Font Height box, define the height of the font that must be used in the
printed documents.
7 In the Status Colors drop down boxes, select the colors that must be used to
indicate the status of a unit and background color of map link icons.
8 In the Indicators Propagation box, tick the Propagate 'Notes Present' indicator
on resources check box to switch on the notes present propagation feature.
9 Press the Apply command button to confirm or the Reload command button to
abort the operation.
46 4014778 Rev H
4 Chapter 4
Getting Started
Introduction
This chapter gives information concerning the first start up of a
ROSA NMS Single User, ROSA NMS Device Configuration Shell, or
NMS ROSA Client system.
In This Chapter
Starting a ROSA NMS Single User System for the First Time........ 48
Starting a ROSA NMS Client system for the First Time.................. 52
Starting a ROSA NMS Device Configuration Shell System for
the First Time......................................................................................... 55
4014778 Rev H 47
Chapter 4 Getting Started
Starting a ROSA NMS Single User System for the First Time
Connecting Devices
Devices can be connected to a ROSA NMS Single User system via a RS232 serial
communication port, a RS485 serial communication port, or via an Ethernet
connection. A description about connecting a device to a ROSA NMS Single
User system via RS232 or RS485 can be found in appendix Connecting Units to a
ROSA NMS System on page 503.
A device provided with an Ethernet port can participate into the LAN to which
the ROSA NMS Single User system belongs or a one-to-one connection between
the device and the ROSA NMS Single User system can be established using a
crossed network cable. More information concerning the Ethernet connection
can be found in the guide that is shipped with the device.
Starting Up the ROSA NMS Single User Software for the First Time
The following procedure explains how to start up the ROSA NMS Single User
software for the first time.
a In the Windows Taskbar, click on Start, point to Programs or All Programs,
click on ROSA Single User, and point to ROSA Single User 3.0.
Result: The ROSA NMS Single User software is started and the ROSA Login
Note: Do not change the User ID Administrator.

b In the Password box, enter the default ROSA NMS Administrator password
for the Local Server. This password can be found on the paper in the sleeve
of the ROSA NMS/Copernicus installation CD-Roms.
Note: The Local Server is the server part of the ROSA NMS Single User
software that runs locally on the computer.
c Click on the OK command button.
48 4014778 Rev H
Result: A message box appears indicating that the default ROSA NMS
Administrator password must be changed.
d Press the OK command button to close the message box.

Result: The Change Current User Password dialog is displayed.
e In the Old Password box, enter the default ROSA NMS Administrator
password.
f In the New Password box and the Confirm box, enter a new ROSA NMS
Administrative password.
g Press the OK command button to confirm or the Cancel command button to
Result: After pressing the OK command button, a message box appears
indicating that the ROSA NMS Administrative password for the Local Server
is successfully changed.
h Press the OK command button to close the message box.

Result: The connection making process with the local server is started.
4014778 Rev H 49
Installing the License File

Without the installation of a valid license file the ROSA NMS Single User can not
run. After installing the ROSA NMS Single User system a license file must be
requested and installed. More information concerning obtaining a license file
and the procedure to install a license file can be found in chapter Licensing on
page 59.
Connecting to a Copernicus Server or SI-Server
Before the ROSA NMS Single User system can be used to control Copernicus
servers or SI-Servers, a LAN or WAN connection must be available between the
ROSA NMS Single User system and the servers. A one-to-one connection
between the ROSA NMS Single User system and a server can be established
using a crossed network cable.
If the ROSA NMS Single User system and the Copernicus server(s) or
SI-Server(s) are a part of a LAN or WAN network, the TCP/IP settings of the
server(s) must be changed according to the network they are placed in. As long
as a server is not known by the ROSA NMS Single User system, the TCP/IP
settings of the server must be changed locally on the server itself. The
procedure to change the TCP/IP settings locally on a server can be found in the
User's Guide shipped with the server.
Note: When a Copernicus server or SI-Server is accessed by a ROSA NMS system
for the first time, a message box appears indicating that the default administrator
password of the server must be changed. More information about changing the
administrator password of a server can be found in topic Changing the
Administrative User Password on page 153.
Installing Drivers
Before additional functionality can be added to the ROSA NMS Single User
system, drivers must be installed. More information concerning drivers and the
procedure to install drivers into the ROSA NMS Single User system can be found
in chapter Working with Drivers on page 65.
Detecting and Mapping Units
To establish communication between the ROSA NMS Single User system or
Copernicus server and units, the units must be identified and mapped using a
Protocol Driver. Since the ROSA NMS software supports several
communication protocols, different Protocol Drivers are foreseen. For more
information concerning these Protocol Drivers and the procedures to use these
drivers, please refer to the user's guide of the corresponding Protocol Driver.
You can find a list with available Protocol Driver User's Guides in the Preface of
this User's Guide.
Note: The ROSA NMS Single User system allows adding demo units, which can
be used to create unit folders, groups, and maps before units are actually
connected to the ROSA NMS Single User system or Copernicus server. More
information concerning demo units can be found in topic Working with Demo
Units on page 99.
50 4014778 Rev H
Creating Folders and Groups

To put units together based on type and location, folders can be created under
the units node in the Server Explorer tree of the ROSA NMS Single User system.
This feature allows making a hierarchical structure in the units node. For more
information concerning folders, please refer to topic Working with Unit Folders on
page 88.
When a large number of similar devices must be set up and controlled, these
devices can be grouped. A group of similar devices has a common user
interface and settings made on such user interface are stored to the complete
group population. More information about groups can be found in topic
Working with Unit Groups on page 91.
Creating Maps and Relations
To have a graphical representation of devices in headends, network structures,
and/or network regions, maps can be imported or created and populated with
devices. Maps can also be created containing interconnections between
monitoring equipment and network equipment. Particular ROSA NMS task
requires the knowledge of the device interconnections. Such interconnections
can be added by creating relations. The easiest way to create relations is to
draw them in a map. More information concerning maps can be found in topic
Working with Maps on page 261 and about relations in topic Working with
Relations on page 331.
Configuring Tasks and Components
When additional functionality is added to the ROSA NMS Single User system by
installing Task Drivers and/or Component Drivers, instances for the task(s) must
be created and the Task(s) and/or Components must be configured.
Information about making task instances can be found in topic Making a Task
Instance on page 75. Information concerning the task(s) and/or component(s) is
described in the corresponding Driver User's Guide. A list with User's Guides
for the Task and Component Drivers is available in the Preface of this User's
Guide.
Configuring Devices
Information concerning the user interface that is used to configure units can be
found in the Driver User's Guide of the corresponding unit. The procedure to
open the user interface is described in topic Opening the User Interface of a Unit on
page 83.
Viewing Messages
Messages received by the ROSA NMS Single User system or server are stored
into the ROSA NMS Message Database of the system. The ROSA NMS Single
User system provides a number of functions to handle the messages in the ROSA
NMS Message Database. More information concerning messages can be found
in chapter Working with Messages on page 203.
4014778 Rev H 51
Starting a ROSA NMS Client system for the First Time

Starting Up the ROSA NMS Client Software for the First Time
The following procedure explains how to start up the ROSA NMS Client
software for the first time.
click on ROSA, and point to ROSA 3.0.
Result: The ROSA NMS Client software is started and a message box appears
indicating that no servers are available to connect with.
b Press the OK command button to close the message box.

Connecting to a Copernicus Server or SI-Server
Before the ROSA NMS Client system can be used to control Copernicus servers
or SI-Servers, a LAN or WAN connection must be available between the ROSA
NMS Client system and the servers. A one-to-one connection between the
ROSA NMS Client system and a server can be established using a crossed
network cable.
If the ROSA NMS Client system and the Copernicus server(s) or SI-Server(s) are
a part of a LAN or WAN network, the TCP/IP settings of the server(s) must be
changed according to the network they are placed in. As long as a server is not
known by the ROSA NMS Client system, the TCP/IP settings of the server must
be changed locally on the server itself. The procedure to change the TCP/IP
settings locally on a server can be found in the User's Guide shipped with the
server.
Note: When a Copernicus server or SI-Server is accessed by a ROSA NMS system
for the first time, a message box appears indicating that the default administrator
password of the server must be changed. More information about changing the
administrator password of a server can be found in topic Changing the
Administrative User Password on page 153.
For more information concerning Copernicus server(s) and or SI-Servers, please
refer to topic Working with Servers on page 123.
Installing Drivers
Before additional functionality can be added to the server, drivers must be
installed. More information concerning drivers and the procedure to install
drivers into the server can be found in chapter Working with Drivers on page 65.
52 4014778 Rev H
Starting a ROSA NMS Client system for the First Time

To establish communication between the Copernicus server and units, the units
must be identified and mapped using Protocol driver(s). Since the ROSA NMS
software supports several communication protocols, different Protocol Drivers
are foreseen. For more information concerning these Protocol Drivers and the
procedures to use these drivers, please refer to the user's guide of the
corresponding Protocol Driver. You can find a list with available Protocol
Driver User's Guides in the Preface of this User's Guide.
Note: The ROSA NMS Client system allows adding demo units, which can be
used to create unit folders, groups, and maps before units are actually connected
to the Copernicus server. More information concerning demo units can be
found in topic Working with Demo Units on page 99.
Creating Folders and Groups
To put units together based on type and location, folders can be created under
the units node in the Server Explorer tree of the ROSA NMS Client system.
This feature allows making a hierarchical structure in the units node. For more
information concerning folders, please refer to topic Working with Unit Folders on
page 88.
Creating Maps and Relations
To have a graphical representation of devices in headends, network structures,
and/or network regions, maps can be imported or created and populated with
devices. Maps can also be created containing interconnections between
monitoring equipment and network equipment. Particular ROSA NMS tasks
require the knowledge about the device connections by creating relations. The
easiest way to create relations is to draw them in a map. More information
concerning maps can be found in topic Working with Maps on page 261 and about
relations in topic Working with Relations on page 331.
Configuring Tasks and Components
When additional functionality is added to the server by installing Task Drivers
and/or Component Drivers, instances for the task(s) must be created and the
task(s) and/or component(s) must be configured. Information about making
task instances can be found in topic Making a Task Instance on page 75.
Information concerning the task(s) and/or component(s) is described in the
corresponding driver User's Guide. A list with User's Guides for the Task and
Component Drivers is available in the Preface of this User's Guide.
4014778 Rev H 53
Configuring Devices
page 83.
Viewing Messages
Messages received by the server are stored into the ROSA NMS Message
Database of the server. The ROSA NMS Client system provides a number of
functions to manipulate the messages in the ROSA NMS Message Database.
More information concerning messages can be found in chapter Working with
Messages on page 203.
54 4014778 Rev H
Starting a ROSA NMS Device Configuration Shell System for the First Time
Starting a ROSA NMS Device Configuration Shell System

for the First Time
Connecting Devices
Devices can be connected to a ROSA NMS Device Configuration Shell system via
a RS232 serial communication port, a RS485 serial communication port, or via an
Ethernet connection. A description about connecting a device to a ROSA NMS
Device Configuration Shell system via RS232 or RS485 can be found in appendix
Connecting Units to a ROSA NMS System on page 503.
A device provided with an Ethernet port can participate into the LAN to which
the ROSA NMS Device Configuration Shell system belongs or a one-to-one
connection between the device and the ROSA NMS Device Configuration Shell
system can be established using a crossed network cable. More information
concerning the Ethernet connection can be found in the guide that is shipped
with the device.
Starting Up the ROSA NMS Device Configuration Shell Software for the First
Time
click on ROSA Device Configuration Shell, and point to ROSA Device
Configuration Shell 3.0.
Result: The ROSA NMS Device Configuration Shell software is started and
the ROSA Login dialog is displayed.
Note: Do not change the User ID Administrator.

b In the Password box, enter the default ROSA NMS Administrator password
for the Local Server that can be found on the paper in the sleeve of the ROSA
NMS/Copernicus installation CD-Roms.
Note: The Local Server is the server software part of the ROSA NMS Device
Configuration Shell software that runs locally on the computer.
c Click on the OK command button.
4014778 Rev H 55
Result: A message box appears indicating that the default ROSA NMS
Administrator password must be changed.
d Press the OK command button to close the message box.

e In the Old Password box, enter the default ROSA NMS Administrator
password.
f In the New Password box and the Confirm box, enter a new ROSA NMS
Administrative password.
g Press the OK command button to confirm or the Cancel command button to
Result: After pressing the OK command button, a message box appears
indicating that a ROSA NMS Administrative password is successfully
changed.
h Press the OK command button to close the message box.

Result: The connection making process with the local server is started.
56 4014778 Rev H
Starting a ROSA NMS Device Configuration Shell System for the First Time
Installing Drivers
Before additional functionality can be added to the ROSA NMS Device
Configuration Shell system, drivers must be installed. More information
concerning drivers and the procedure to install drivers into the ROSA NMS
Device Configuration Shell system can be found in chapter Working with Drivers
on page 65.
Note: Particular drivers require a valid license in the license file. More
information about obtaining a license file and the procedure to install a license
file can be found in chapter Licensing on page 59.
To establish communication between the ROSA NMS Device Configuration Shell
system and units, the units must be identified and mapped using Protocol
driver(s). Since the ROSA NMS software supports several communication
protocols, different Protocol Drivers are foreseen. For more information
concerning these Protocol Drivers and the procedures to use these drivers, please
refer to the user's guide of the corresponding Protocol Driver. You can find a
list with available Protocol Driver User's Guides in the Preface of this User's
Guide.
Note: The ROSA NMS Device Configuration Shell system allows adding demo
units, which can be used to create unit groups before units are actually connected
to the ROSA NMS Device Configuration Shell system. More information
concerning demo units can be found in topic Working with Demo Units on page
99.
Creating Groups
Configuring Devices
page 83.
4014778 Rev H 57
5 Chapter 5
Licensing
Introduction
This chapter gives more information concerning the ROSA NMS
licenses. This chapter also outlines the procedure to install licenses.
In This Chapter
Introduction ........................................................................................... 60
Installing a License File ........................................................................ 63
4014778 Rev H 59
Chapter 5 Licensing
Introduction
About ROSA NMS Licenses
The ROSA/Copernicus software is partially license based; meaning licenses are
required to use particular ROSA/Copernicus functionalities. Without a valid
license a Copernicus Server, SI Server, ROSA NMS Single User system, and ROSA
NMS Device Configuration Shell system can not run. Most of the ROSA NMS
drivers for the ROSA/Copernicus software require a license to use them. The
licenses are combined in a single file, named License.dat.
ROSA NMS Device Configuration Shell System
After installing a ROSA NMS Device Configuration Shell system, a license file for
the ROSA NMS system and for the free drivers must be installed. This license
file can be found on the ROSA/Copernicus installation CD-Rom labeled with
Disk 1.
ROSA NMS Single User System
After installing a ROSA NMS Single User System, a License file must be
requested. More information concerning obtaining a license file can be found in
sub topic Obtaining a New License File further in this topic.
ROSA NMS Client System
A ROSA NMS Client system needs no license file.
Copernicus server and SI-Server
When a Copernicus server or SI-Server leaves our assembly line, the license file
with the ordered licenses is already installed.
When additional functionalities are needed for a ROSA NMS Device Configuration
Shell system, ROSA NMS Single User system, Copernicus server, or SI-Server, a new
license file is required containing the existing licenses and the licenses for the new
functionalities.
License Errors
When additional functionality is added to a ROSA NMS system without license for
this functionality, the driver status of this functionality in the Installed Drivers
dialog will be License Error. As long as the license for this functionality is not
available in the installed license file, this functionality can not be used.
60 4014778 Rev H
Introduction
The following picture depicts an Installed Drivers dialog with drivers in License
Error state.
As long as the license file is not installed on a ROSA NMS Single User system, the
local server of the system can not be connected. The following message box is
displayed when a local server connection is performed on a ROSA NMS Single User
system without installed license file.
Obtaining a New License File

To obtain a new license file, please contact our Customer Service department; phone
numbers, fax numbers, and/or e-mail addresses of the assistance centers can be
found in appendix Customer Information.
Provide the Host ID of the Local Server, Copernicus Server, or SI-Server because this
number is required to create a new license file. The procedure to check the Host ID
of a server can be found in topic Checking the Host ID of a Server on page 62.
The Customer Service department will send you as soon as possible the new license
file. The procedure to install a license file can be found in topic Installing a License
File on page 63.
4014778 Rev H 61
Chapter 5 Licensing
Checking the Host ID of a Server

The following procedure explains how to check the host ID of a server.
1 In the Server Explorer of the ROSA NMS system, select the server of which the
Host ID is required.
2 In the Server menu, select License and point to Get Host ID....
Result: The Server HostID message box is displayed containing the Host ID of
the selected server.
3 Close the message box by pressing the OK command button.
62 4014778 Rev H
Installing a License File
Installing a License File

The following procedure explains how to install a license file on a server.
1 In the Server Explorer of the ROSA NMS system, select the server on which a
new license file must be installed.
2 In the Server menu, select License and point to Install license file....
Result: The Install License File dialog is displayed.
3 In the Path to License File to Install box, enter the complete path of the license
file or click on the Browse command button and in the Open Dialog, browse to
the license file.
Note: The license file with the licenses for a ROSA NMS Device Configuration
Shell system and free drivers can be found on ROSA/Copernicus installation
CD-Rom labeled with Disk 1 (path = /DCS License).
4 Click on the Install command button to install the license file on the selected
server or press the Close command button to abort the operation.
Result: The following message box displays after a successful license installation.
5 Click on the OK command button.

Result: A message box is displayed asking a reboot of the system.
6 Press the OK command button and reboot the server as described in topic
Stopping, Rebooting and Starting a Server on page 133.
4014778 Rev H 63
Chapter 5 Licensing
64 4014778 Rev H
6 Chapter 6
Working with Drivers
Introduction
This chapter gives more information about ROSA NMS drivers.
In This Chapter
Introduction ........................................................................................... 66
Installing Drivers .................................................................................. 68
Getting Drivers from a Copernicus Server or SI-Server.................. 71
Viewing Driver Details ........................................................................ 73
Making a Task Instance........................................................................ 75
Uninstalling Drivers ............................................................................. 77
Assigning Serial Port Drivers to Serial Ports .................................... 79
4014778 Rev H 65
Chapter 6 Working with Drivers
Introduction
The following ROSA NMS driver types exist:
Protocol Drivers
Protocol drivers are drivers that allow communication with devices that use a
specific protocol. Some of these drivers, like the RCDS Protocol driver, are used
as Serial Port drivers. Other Protocol drivers are not linked to a serial port. For
example, the Apollo Protocol Driver allows the server to communicate with
RCDS-compatible devices connected to an Apollo TCP/IP interface or a ROSA
Element Manager. The Apollo or the ROSA Element Manager is connected to
the server via a TCP/IP network. Another example is the SNMP Protocol
Driver that allows monitoring devices via SNMP.
Serial Port Drivers
Without a serial port communication driver, you cannot use the serial port(s) on
your computer for communication with the equipment. For more information
about configuring the serial ports, please refer to topic Assigning Serial Port
Drivers to Serial Ports on page 79. The RCDS Protocol Driver is the proprietary
serial port communication driver to be used for communication with all
equipment that uses the RCDS protocol. Other port drivers implement
non-RCDS compatible serial protocols and are used to connect non-RCDS
compatible devices to the serial ports, for example an Iris router or a Philips BTS
router.
RCDS Drivers
You have to install an RCDS driver for each type of RCDS compatible device you
want to control. Each RCDS device driver has a user interface to control the
device using ROSA NMS. The driver also processes the messages coming from
the device.
Device Drivers
These drivers are used to control non-RCDS compatible devices via for instance
the SNMP or IIOP protocol.
Task Drivers
All tasks are installed using a task driver. After installation a task driver, a task
instance must be created. For more information about creating task instances,
please refer to topic Making a Task Instance on page 75.
Service Drivers
Three Service drivers can be installed without additional driver license keys: the
Analog TV Service, Analog TV Channel, and Satellite Channel Service Drivers.
66 4014778 Rev H
Introduction
Component Drivers
ROSA NMS plug-ins are installed using a component driver. Additional
functionality then becomes available in ROSA NMS. Examples are the
Scheduler component and the UDD Profile Manager component.
4014778 Rev H 67
Installing Drivers
Introduction
Before attempting driver installations, please read the following notes carefully.
Drivers with a lower product version cannot be installed.
To upgrade a driver, simply install the newer driver. The old driver will be
replaced automatically. Do NOT uninstall the old driver first!
Downgrading drivers within the same product version is not possible unless you
uninstall the drivers first. Uninstalling a driver results in the loss of all
configurations because all resources using the driver are removed from the
Server Explorer tree.
If you install drivers that require a server software version higher than the
current installed version, the server software will be upgraded automatically.
Once drivers are installed in the ROSA NMS system, the status of the installed
drivers is displayed in the Installed drivers dialog. Normally the status is OK; the
following table shows all driver states that indicate an error.
Driver Status Reason / Solution
Not Registered Each driver is included in the registry. If not, the installation failed. Try
re-installing the driver.
Not Present The driver is not found on the location specified in the registry. Possibly, the
driver file has been deleted. Try re-installing the driver.
Incorrect Version The version of the driver does not correspond to the server software version.
The first two numbers of these version numbers should be identical. This can
occur when the driver was not upgraded during upgrading ROSA NMS.
Object Creation The driver object could not be created. This can be an error or problem in the
Failed driver.
License Error Your current License file does not include the License key for the driver.
Unstable Error in the driver, causing driver instability.
Removal Pending The driver was uninstalled but the server has not been restarted yet. After
restarting the server, this driver is removed from the Drivers list.
68 4014778 Rev H
Installing Drivers
To Install Drivers
The following procedure explains how to install one or more driver.
1 In the Server Explorer of the ROSA NMS system, select the server for which a
driver should be installed.
2 In the Config menu, point to Drivers....
Result: The Installed Drivers dialog is displayed.
3 Click on the Install command button.

Result: The Open dialog is displayed.
4 Browse to the folder containing the driver files. These drivers can be found on
the ROSA NMS installation CD-Rom or on the following location:
ROSA NMS Single User system: in the folder ... \ Program Files
\Scientific-Atlanta \ ROSASingleUser \ Copernicus \ Drivers \ or ...\ Program
Files \ Cisco \ ROSASingleUser \ Copernicus \ Drivers \
4014778 Rev H 69
ROSA NMS Client system: on the hard disk of the Copernicus server or
SI-Server in the shared folder ...\ Copernicus \ Drivers \
ROSA NMS Device Configuration Shell system: in the folder ...\ Program
Files \ Scientific-Atlanta \ ROSADCS \ Copernicus \ Drivers \ or ...\ Program
Files \ Cisco \ ROSADCS \ Copernicus \ Drivers \
Notes:
If the ...\ Copernicus \ Drivers \ folder on the hard disk of the server is no
longer shared, the driver files can be downloaded to the hard disk of the
ROSA NMS system. The procedure to download the driver files from the
hard disk of a server can be found in topic Getting Drivers from a Copernicus
Server or SI-Server on page 71.
When drivers are downloaded from our FTP server, browse to the location
where these files are stored.
5 Select the driver(s) that should be installed. To select consecutive drivers, point
to the first driver, press and hold down the [SHIFT] key, and then click on the
last driver. To select drivers that are not consecutive, press and hold down the
[CTRL] key and point to each driver.
6 Click on the Open command button.
Result: After successful installation, the name of the driver(s) is (are) added to
the list box on the Installed Drivers dialog.
Note: In the list box on the Installed Drivers dialog, each installed driver is
accompanied with driver type, driver version, version of the required core, the
name of the company providing the driver, and the driver status.
7 Click on the Close command button to close the Installed Drivers dialog.
Note: When drivers cannot be installed due to errors, the Driver Installation
Failed dialog is displayed with an overview of the driver installation files that
caused errors.
8 Click on the Details command button to view the error details or the Close
command button to close the dialog.
70 4014778 Rev H
Getting Drivers from a Copernicus Server or SI-Server
Getting Drivers from a Copernicus Server or SI-Server

A ROSA NMS Single User or ROSA NMS Client system is able to download the
driver files from a Copernicus Server or SI-Server. The downloaded driver files are
stored into the ...\ Drivers directory of the ROSA NMS system. Driver files that
already exist in this directory are overwritten.
The following procedure explains how to download all driver files from a
Copernicus server or SI-Server.
1 In the Server Explorer tree of the ROSA NMS system, select the server from
which driver files must be downloaded.
Result: The Installed Drivers dialog of the selected server is displayed.
3 Click on the Get Drivers from Server command button.

Result: A confirmation box is displayed.
4 Point to the Yes command button to confirm or the No command button to abort
the download operation.
4014778 Rev H 71
Result: After pressing the Yes command button, a progress indicator is

displayed.
Note: The driver downloading process can always be stopped by pressing the
Stop command button.
Once the driver files are successfully copied from the server, a message box
appears.
5 Press the OK command button to close the message box.

6 On the Installed Drivers dialog, press the Close command button to close the
dialog.
72 4014778 Rev H
Viewing Driver Details
Viewing Driver Details

Introduction
The Driver Details dialog of a driver provides the following information:
Filename: the file name of the driver DLL file
Company Name: the name of the company that created the driver
Driver Type: the type of the driver.
Status: the current driver status. More information concerning the driver status
can be found in topic Introduction on page 68.
File Version: the version of the driver DLL
Required Core: the lowest version of the server software core that is required to
use all functionality of the driver
Multiple Instances: if selected, multiple instances can be created using the same
driver. This is always the case for device drivers, and occasionally also for task
drivers.
Groups: if selected, resources using the driver can be grouped. For details
about unit groups, please refer to topic Working with Unit Groups on page 91.
Object Type ID: internal number that uniquely identifies the driver
4014778 Rev H 73
The following picture shows a Driver Details dialog for a Model D9032 Encoder.
The lower part of the Driver Detail dialog shows the components of the drivers
accompanied with details.
Checking the Details of a Driver

The procedure below describes how to check the details of a driver.
1 In the Server Explorer tree of the ROSA NMS system, select the server
containing the driver of which details must be checked.
Result: The Installed Drivers dialog of the selected server is displayed.
3 Select the driver of which the details must be checked and point to the Details
command button.
Result: The Driver Details for <driver name> dialog of the selected driver is
displayed.
4 The Driver Details for <driver name> dialog can be closed by pressing the OK
command button.
74 4014778 Rev H
Making a Task Instance
Making a Task Instance

Once a task driver is installed, the task cannot be used as long as no task instance is
created. The following procedure explains how to make a task instance.
1 In the Server Explorer or Group Explorer tree of the ROSA NMS system, select
the server for which a task instance must be created.
3 In the list box, select the task driver for which a task instance must be created
and point to the Make Task command button.
Result: The Make Task dialog is displayed.
4 In the Task Name box, enter a name for the task.

5 Press the OK command button to confirm or the Cancel command button to
Note: For some of the task, multiple task instances can be created. Repeat this
procedure but give for each instance another name. These tasks can then run
simultaneously and independently.
6 Close the Installed Drivers dialog by pressing the Close command button.
4014778 Rev H 75
Result: The new task instances appear under the Task node in the Server
Explorer tree.
76 4014778 Rev H
Uninstalling Drivers
Uninstalling Drivers
The following procedure explains how to uninstall drivers.
1 In the Server Explorer of the ROSA NMS system, select the server for which
drivers should be uninstalled.
3 In the Installed Drivers list box, select the drivers that must be uninstalled. To
select consecutive drivers in the list box, point to the first driver, press and hold
down the [SHIFT] key, and point to the last driver. To select non-consecutive
drivers, press and hold down the [CTRL] key, and click on each driver.
4 Press the Uninstall command button.
5 Click on the Yes command button to uninstall the selected drivers or the No
command button to abort the operation.
4014778 Rev H 77
Note:
Removing a driver will automatically remove all resources using that driver
from the Server Explorer, Group Explorer and from all maps.
Depending on the removed driver, the server from which the driver is
uninstalled may be rebooted. For more information concerning rebooting a
server can be found in topic Stopping, Rebooting and Starting a Server on page 133.
78 4014778 Rev H
Assigning Serial Port Drivers to Serial Ports
Assigning Serial Port Drivers to Serial Ports

By default, all RS-232 and RS-485 serial ports on the computer running the server
part of the ROSA NMS system software are disabled. The serial port to which units
are connected must be provided with a serial port driver.
1 In the Server Explorer tree of the ROSA NMS system, select the server for which
serial ports must be provided with serial port drivers.
2 In the Server menu, point to Serial Ports....
Result: The Server Serial Port Configuration dialog is displayed.
3 Double-click on the serial port that must be provided with a serial port driver.
Result: The Server Serial Port dialog is displayed.
4 In the Usage selection box, point to the Driver Type selection button.
5 In the Driver Type drop down box, select the driver.
6 Press the OK command button to confirm.
Result: The Server Serial Port is closed.
4014778 Rev H 79
7 On the Server Serial Port Configuration dialog, press the OK command button
to confirm or the Cancel command button to abort the operation.
Note: In the Server Explorer tree of the ROSA NMS system, the status of the serial
ports is indicated by the following icons.
Icon Description
The serial port is functioning properly.
The serial port is malfunctioning.
80 4014778 Rev H
7 Chapter 7
Working with Resources
Introduction
This chapter describes how to work with resources in ROSA NMS.
0
In This Chapter
Handling Units...................................................................................... 82
Unit Settings ........................................................................................ 106
Configuring Unit Input/Output Ports ............................................ 110
Using Notes ......................................................................................... 116
Displaying Unit Information in the Server Explorer or Group
Explorer Tree ....................................................................................... 121
4014778 Rev H 81
Chapter 7 Working with Resources
Handling Units
Introduction
New units are units that are detected by the serial ports or protocol drivers of a
Copernicus server, SI-Server, or ROSA NMS system. As long as new units are not
mapped into the ROSA NMS system by giving a name and location, the system
doesn't control these units. They are displayed in the Server Explorer tree as
question marked icons in front of the serial port or protocol driver by which they are
detected.
Once units are mapped into the ROSA NMS system, the system adds them to the
The following picture shows a Server Explorer tree with mapped units and units
that are not yet mapped.
Note: More information about scanning and detecting units on a serial port or on the
network and how to map these units to ROSA NMS resources can be found in the
User's Guide of the Protocol driver.
82 4014778 Rev H
Handling Units
Opening the User Interface of a Unit

In the ROSA NMS system, the user interface of a unit can be opened in different
ways:
Double-click on the unit under the Units node in the Server Explorer tree or
right-click on the unit and click on Properties in the short-cut menu.
When a unit belongs to a group, right-click on the unit under its group node in
the Group Explorer tree and click on Properties in the short-cut menu.
For more information about groups, please refer to Working With Unit Groups on
page 91.
4014778 Rev H 83
Right-click on a message from the unit in the Message Viewer and then click on
Log on to Resource in the short-cut menu.
More information concerning messages can be found in chapter Working with

Messages on page 203
Right-click on the unit in a map and point to Properties in the short-cut menu.
For more information concerning maps, please refer to chapter Working with
Maps on page 261.
Note: The user interface of a unit can only be opened via a map if the map mode
is set to Operational.
84 4014778 Rev H
Handling Units
GUI Updating Behavior

Introduction
The Graphical User Interface (GUI) of a driver is available on the server as well as on
the ROSA NMS system. By default, the ROSA NMS system checks the version of
the GUI on the server when opening a driver GUI. If the version of the GUI on the
ROSA NMS system is lower, the server version is copied to the ROSA NMS system.
When a driver is updated via one ROSA NMS system, other ROSA NMS systems
will automatically open the updated version.
When the driver versions are equal, the ROSA NMS system can do a Cyclic
Redundancy Check (CRC) on both files, to make sure that they are really identical.
If the CRCs are different, the file is copied from the server, assuming that this is the
most recent version.
Downgrading a GUI is also possible, when the driver on the server is lower than that
on the client.
Changing the GUI Updating Behavior

Perform the following steps to change the GUI updating behavior.
1 In the File menu of the ROSA NMS user interface, click on Preferences....
Result: The Preferences dialog is displayed.
2 Point to the GUI Updates tab.
Result: The GUI Updates tab is displayed.
The GUI updating behavior depends on the combination of settings on the GUI
Updates tab.
4014778 Rev H 85
File version and CRC checking, no forced downgrade (default setting)
After opening the GUI of a resource, the ROSA NMS system checks if it has
the most recent version. If its version is older than the servers version, it is
overwritten. If both versions are equal, the ROSA NMS system performs a
CRC on both files.
Only file version checking
When opening a GUI of a resource, the ROSA NMS checks if it has the most
recent version. If its version is older than the one on the server, it is
overwritten by that on the server. If the versions on the ROSA NMS system
and on the server are equal, no CRC is performed and the ROSA NMS
system GUI version is opened.
No file version check
The ROSA NMS system GUI version is always opened, regardless of the
server GUI version.
File version checking and forced downgrade
86 4014778 Rev H
Handling Units
Also if the server GUI version is older, the ROSA NMS system version is
overwritten. This can be interesting when two servers are running different
versions of a driver. It avoids using a newer GUI when connected to a
server that has an older driver installed that does not support new
functionality.
CRC checking can be enabled if desired.
3 Click on the OK command button to activate the GUI updating settings or the
Cancel command button to abort the operation.
About the Local and Remote Control of Units

Introduction
Units that are controlled by a ROSA NMS system are in remote control mode. Units
that are controlled via front panel are in local control mode. Units allow switching
between remote and local control mode by unlocking the front panel and sending a
local control request to the ROSA NMS system. For more information concerning
the control mode of a unit, please refer to the User's Guide that is shipped with the
device.
The ROSA NMS system allows switching from remote control mode to local control
mode and vice verso.
Switching from Remote Control to Local Control Mode

The following procedure explains how to switch from remote control mode to local
control mode via the ROSA NMS system.
1 In the Server Explorer or Group Explorer tree of the ROSA NMS system,
right-click on the unit that should be set to local control mode and point to Local
Control in the short-cut menu.
Result: The unit is switched from remote control to local control mode and a red
bar is displayed across the icon of the unit.
Switching from Local Control to Remote Control Mode

The following procedure explains how to switch a unit from local control mode to
remote control mode via the ROSA NMS system.
right-click on the unit that should be set to remote control mode and point to
Remote Control in the short-cut menu.
Result: The unit is switched from local control to remote control mode and the
red bar across the unit is removed.
4014778 Rev H 87
Working with Unit Folders

Introduction
Under the Units node in the Server Explorer tree of a server, unit folders can be
created. Folders can be useful to put units together based on type or location, for
example to keep modulators and receivers together in separate folders.
In a folder, units are sorted alphabetically as in the Server Explorer tree itself. The
color of the folder icon represents the highest severity of the devices it contains.
This allows easy top-down alarm tracking. The messages of the units within a
particular folder can be displayed.
Creating a New Folder

The following procedure explains how to create a new folder.
new folder should be created.
2 Right-click on the Units node and point to New folder... in the short-cut menu.
Result: The New Folder dialog is displayed.
3 In the Name box, enter a name for the new folder.

4 Click on the Create command button to confirm or the Cancel command button
to abort the operation.
Result: After pressing the Create command button the new folder displays
under the Units node in the Server Explorer tree.
Creating Nested Folders

Perform the following steps to create a folder in a folder (nested folders).
1 In the Server Explorer of the ROSA NMS system, right-click on the folder in
which a new folder must be created and select New Folder... in the short-cut
menu.
88 4014778 Rev H
Handling Units

3 Press the Create command button to confirm or the Cancel command button to
Result: After pressing the Create command button, the new folder is added to
the selected folder. Units can be moved to this folder as described in topic
Moving Units to a Folder on page 89.
Tip: Nested folders can also be created by dragging and dropping a folder into
another folder. Moving a nested folder to another folder or to the units node can be
done by such drag and drop action.
Moving Units to a Folder

The following procedure explains how to move units to a folder.
1 In the Server Explorer of the ROSA NMS system, select the folder to which units
must be moved.
2 Right-click on the folder and point to Move Units ... in the short-cut menu.
Result: The Move unit(s) to folder... dialog is displayed.
3 In the Move unit(s) to folder... dialog, select the unit(s) that must be moved to
the folder. To select consecutive units in the list, click on the first unit, press and
hold down the [SHIFT] key, and then click on the last unit. To select units that
are not consecutive, press and hold down the [CTRL] key, and point to each unit.
4 Click on the ADD command button to confirm or the Cancel command button to
Result: After pressing the ADD command button, the unit(s) is (are) moved to
the selected folder.
Note: Units can also be moved to a folder using a drag and drop action.
4014778 Rev H 89
Moving Units Back to the Units Node

The following procedure explains how to move a unit back to the Units node.
1 In the Server Explorer of the ROSA NMS system, right-click on the Units node
and select Move Units... in the short-cut menu.
Result: The Move unit(s) to folder... dialog is displayed.
2 In the Move unit(s) to folder... dialog, select the unit(s) that must be moved back
to the Units node. To select consecutive units in the list, click on the first unit,
press and hold down the [SHIFT] key, and then click on the last unit. To select
units that are not consecutive, press and hold down the [CTRL] key, and point to
each unit.
3 Click on the ADD command button to confirm or the Cancel command button to
Result: After pressing the ADD command button the unit(s) is (are) moved to
the Units node.
Note: Units can also be moved from a folder to the Units node using a drag and
drop action.
Renaming a Folder
Perform the following steps to rename a folder.
1 In the Server Explorer of the ROSA NMS system, right-click on the folder that
must be renamed and select Rename... in the short-cut menu.
Result: The Rename Folder dialog is displayed.
2 In the Name box, enter the new name for the selected folder.
90 4014778 Rev H
Handling Units
3 Press the Rename command button to rename the folder or the Cancel command
button to abort the operation.
Removing a Folder
The following procedure explains how to remove a folder.
must be deleted and select Remove in the short-cut menu.
2 Press the Yes command button to remove the folder or the No command button
Result: After pressing the Yes command button, the folder is removed and the
units member of this folder are moved to the Units node or to the folder the
removed folder was part of (nested folders).
Working with Unit Groups

Introduction
When a large number of similar devices, such as Netsense End of Line Monitors,
Sirius Up-converters, or ADVM Broadcast monitors, must be set up and controlled,
these devices can be grouped. This approach allows to quickly configuring similar
devices with same settings. A group of similar devices has a common user interface
and the settings made on such an interface are stored to all devices in the group.
4014778 Rev H 91
The following picture shows a common user interface of an ADVM Broadcast

monitor group.
Note: Not all drivers support grouping. To check if grouping is supported by a

driver, check the driver details. For more information about driver details, please
refer to topic Viewing Driver Details on page 73.
Displaying the Group Explorer

To allow easy access to a group of devices, groups are displayed in the Group
Explorer tree of the ROSA NMS system.
The following procedure explains how to display the Group Explorer tree.
1 In the Server Explorer box, point to the Groups tab.
92 4014778 Rev H
Handling Units
Result: The Group Explorer tree is displayed.
Creating a New Group

When drivers are installed on the ROSA NMS system that support groups, a group
can be created. The following procedure explains how to create a group.
1 In the Group Explorer of the ROSA NMS system, right-click on the Groups node
of the server on which a new group should be created and point to New Group...
in the short-cut menu.
Result: The New Group dialog is displayed.
Note: As long as no driver is installed that supports groups, no group can be

created. In this case the following message box appears.
2 In the Name box, enter a name for the new group.

3 In the Driver drop down box, select the driver of the units that must be grouped.
4014778 Rev H 93
Notes:
The Driver drop down box only contains the installed drivers that support
groups.
A group can only be populated with units of the selected driver.
4 Press the OK command button to create the group or the Cancel command
Result: After pressing the OK command button, the new group is added to the
Groups node of the selected server.
Adding Units to a Group

The following procedure describes how to add units to a group.
on which units should be added and point to Modify... in the short-cut menu.
Result: The Modify Group dialog is displayed.
Note: The Units you can add... list box is populated with the units that can be
added to this group. These are the units that use the driver specified during the
group creation process, see topic Creating a New Group on page 93. The Units in
group... list box contains the units belonging to this group.
2 In the Units you can add... list box, select the unit(s) that should be added to this
group. To select consecutive units, click on the first unit, press and hold down
the [SHIFT] key, and then click on the last unit. To select units that are not
consecutive, press and hold down the [CTRL] key, and point to each unit.
Note: If the Units you can add... list is too long, the list can be filtered. The
following steps explain how to filter the Units you can add... list.
Click on the Filter... command button below the Units you can add... list box.
94 4014778 Rev H
Handling Units
Result: The Specify filter... dialog.
In the Specify a filter using wildcards [*,?] box, enter a string to filter the list.
Wildcard characters are allowed. Use the asterisk character (*) as a
substitute for zero or more characters and the question mark (?) as a
substitute for a single character in the unit name.
Press the OK command button to confirm or the Cancel command button to
Note: When a filter is active, a blinking exclamation mark and the filter
definition are displayed below the Units you can add... list box.
3 After selecting the units in the Units you can add... list box, click on the >>
command button.
Result: The units are moved to the Units in group... list box.
4 Press the OK command button to add the units to the group or the Cancel
Result: After pressing the OK command button, the units are added to the
Group Explorer tree.
4014778 Rev H 95
Removing Units from a Group

The procedure below describes how to remove units from a group.
from which units should be removed and point to Modify... in the short-cut
menu.
Result: The Modify Group dialog is displayed.
2 In the Units in group... list box, select the unit(s) that should be removed from
this group. To select consecutive units, click on the first unit, press and hold
down the [SHIFT] key, and then click on the last unit. To select units that are
not consecutive, press and hold down the [CTRL] key, and point to each unit.
Note: If the Units in group... list is too long, the list can be filtered. The
following steps explain how to filter the Units in group... list.
Click on the Filter... command button below the Units in group... list box.
Result: The Specify filter... dialog.
In the Specify a filter using wildcards [*,?] box, enter a string to filter the list.
Wildcard characters are allowed. Use the asterisk character (*) as a
substitute for zero or more characters and the question mark (?) as a
substitute for a single character in the unit name.
96 4014778 Rev H
Handling Units
Note: When a filter is active, a blinking exclamation mark and the filter
definition are displayed below the Units in group... list box.
3 After selecting the units in the Units in group... list box, click on the <<
command button.
Result: The units are removed from the Units in group... list box and added to
the Units you can add... list box.
4 Press the OK command button to remove the units from the group or the Cancel
Opening a Common User Interface

The following procedure explains how to open a common user interface for all
devices in a group.
1 In the Group Explorer of the ROSA NMS system, right-click on the Group for
which the common user interface should be opened and point to Properties in
the short-cut menu.
Result: The common user interface is opened.
Note: The common user interface of a group is similar to the user interface of a
single device of this group. For more information concerning a common user
interface, please refer to the User's Guide of the corresponding driver.
4014778 Rev H 97
Renaming a Group
The following steps explain how to rename a group.
1 In the Group Explorer of the ROSA NMS system, right-click on the Group that
should be renamed and point to Rename... in the short-cut menu.
Result: The Rename Group dialog is displayed.
2 In the Name box, enter a new name for the group.

3 Press the OK command button to rename the group or the Reload command
Removing a Group
Perform the following steps to remove a group from the Group Explorer tree.
1 In the Group Explorer of the ROSA NMS system, right-click on the Group that
should be removed and point to Remove in the short-cut menu.
2 Press the Yes command button to remove the selected group or the No
Result: The group will be removed from the Group Explorer tree after pressing
the Yes command button.
Note: Only the group will be removed, not the units member of the group.
98 4014778 Rev H
Handling Units
Working with Demo Units

Introduction
The ROSA NMS system allows adding units that do not represent real devices. The
ROSA NMS system marks such units as demo units. This feature can be used to
create unit folders, groups, and maps before the units are actually connected to the
ROSA NMS system and acts as a placeholder for real units. When the units are
connected to the ROSA NMS system, they can be mapped to the demo units, which
become fully ROSA NMS-controlled units.
Adding Demo Units

The following procedure explains how to add demo units to a ROSA NMS system.
demo units should be added.
2 Point to Units... in the Config menu.
Result: The Units dialog is displayed.
3 Click on the Add... command button.

Result: The Add Unit dialog is displayed.
4 In the Device Driver drop down box, select the driver for the demo unit that
should be added.
4014778 Rev H 99
Note: The Device Driver drop down box only contains the installed drivers.
5 In the Name box, enter a name for the demo unit.
6 Click on the ... command button beside the Location box.
Result: The Locations dialog is displayed.
7 Browse to the location and press the Select command button.

Result: The Location dialog is closed and the name of the selected location is
indicated in the Location box on the Add Unit dialog.
For more information about locations, please refer to topic Using Locations on
page 197.
8 Press the Add command button to confirm and the Close command button to
close the Add Unit dialog.
Result: The demo unit is added to the list on the Units dialog.
Note: A demo unit is indicated by Demo Unit in the Additional Info column.
Changing the Management Mode

Introduction
For instance for reconfiguration purposes, it can be useful to set the management
mode of a device in maintenance. Messages created by a unit in maintenance will
be logged but the indication and propagation in the Server Explorer tree and maps
are stopped.
The management mode for SNMP devices can also be set to Exclude for Monitoring.
Devices in this mode will not longer be polled by the ROSA NMS and messages will
not longer be logged.
100 4014778 Rev H

Handling Units
Changing the Management Mode of a Unit to Maintenance

The following procedure describes how to set the management mode of a unit to
maintenance.
1 In the Server Explorer tree, Group Explorer tree or map, right-click on the unit
for which the management mode must be set to maintenance, point to
Management Mode and select Unit in Maintenance in the short-cut menu.
Result: The management mode of the device is changed to Unit in Maintenance.

The following pictures show a unit in maintenance.
Unit in tree
Unit in Map
Tip: The color representing a unit in maintenance can be changed. The procedure
to change this color can be found in topic Changing View Options on page 44.
4014778 Rev H 101

Changing to Exclude from Monitoring

The following procedure describes how to set the management mode of a unit to
Exclude from Monitoring.
for which the management mode must be set to Exclude from Monitoring, point to
Management Mode and select Exclude from Monitoring in the short-cut menu.
Result: The management mode of the device is changed to Exclude from

Monitoring.
The following pictures show a unit in Exclude from Monitoring.
Unit in tree
Unit in Map
Tip: The color representing a unit in Exclude from Monitoring can be changed. The
procedure to change this color can be found in topic Changing View Options on page
44.
102 4014778 Rev H

Handling Units
Removing Units
Introduction
Units can be removed from a ROSA NMS system on two different ways: using the
Server Explorer tree and via the Units dialog.
Notes:
When a unit is removed from the ROSA NMS system but still connected, the unit
is detected as a new unit.
If a unit has relations to or from other units, these relations will be removed after
removing the unit from the ROSA NMS system. The task that used this unit
and its relations should be re-initialized.
Removing Units via the Units Dialog

The following steps explain how to remove units from the ROSA NMS system via
the Units dialog.
1 In the Server Explorer tree, select the server from which units must be removed.
3 In the Units list box, select the unit(s) that must be removed. To select
consecutive units, point to the first unit, press and hold down the [SHIFT] key,
and point to the last unit. To select units that are not consecutive, press and
hold down the [CTRL] key, and select each unit.
4 Press the Remove command button.
Result: The selected units are removed.
4014778 Rev H 103

Removing Units via the Server Explorer Tree

The following procedure describes how to remove units from the ROSA NMS
system via the Server Explorer tree.
1 In the Server Explorer tree of the ROSA NMS system, right-click on the unit that
must be removed and point to Remove in the short-cut menu.
2 Press the Yes command button to remove the selected unit or the No command
Result: The unit is removed.
Exporting Unit Details

Introduction
The ROSA NMS system allows exporting details of units. These details can then be
used in other applications. The following picture shows unit details pasted in
Notepad.
Note: Each unit is another paragraph and the unit details are separated by a tab.
104 4014778 Rev H

Handling Units
Exporting Unit Details

The following steps describe how to export details of units.
unit details must be exported.
3 In the Units list box, select the unit(s) for which details must be exported. To
select consecutive units, point to the first unit, press and hold down the [SHIFT]
key, and point to the last unit. To select units that are not consecutive, press and
hold down the [CTRL] key, and click on each unit.
4 Right-click on the list box and point to Copy to Clipboard in the short-cut menu.
Result: The details are copied to the clipboard.

5 Open the application and paste the details into the application.
4014778 Rev H 105

Unit Settings
Introduction
The list below shows the unit settings that can be changed:
Name: the name that is used to identify the unit in the Server Explorer tree,
Group Explorer tree, and maps.
Location: the location assigned to a unit. This can be useful when performance
graphs compared by locations are created.
Bitmap: the bitmap assigned to a unit. This bitmap represents the unit in a
map. This parameter can not be changed via the Edit Unit dialog.
The settings of units can be changed via the Resource Settings dialog or via the Edit
Unit dialog of the ROSA NMS system.
Changing Unit Settings via Resource Settings Dialog

The following steps explain how to change the settings of a unit via the Resource
Settings dialog.
of which settings must be changed and point to Settings... in the short-cut menu.
Result: The Resource Settings dialog of the selected unit is displayed.
2 In the Name box, enter a new name for the unit.

106 4014778 Rev H

Unit Settings
Result: The Location dialog is displayed.
4 Browse to the desired location and press the Select command button.
Result: The name of the location appears in the Location box on the Unit
Settings dialog.
5 In the Bitmap drop down box, select the bitmap that must be assigned to the
unit.
6 Press the OK command button to adapt the unit settings or the Cancel command
4014778 Rev H 107

Changing Unit Settings via the Edit Unit dialog

Perform the following steps to change unit settings via the Edit Unit dialog.
the server of which unit settings must be changed.
3 In the Units list box, select the unit of which setting should be changed and press
the Edit... command button.
Result: The Edit Unit dialog is displayed.
4 In the Name box, enter a new name for the unit.

108 4014778 Rev H

Unit Settings
6 Browse to the desired location and press the Select command button.
Result: The name of the location appears in the Location box on the Unit
Settings dialog.
7 Press the Update command button to confirm or the Close command button to
8 Press the Close command button to close the Units dialog.
4014778 Rev H 109

Configuring Unit Input/Output Ports

Introduction
The Input/Output (I/O) ports on units are used to interconnect different units via
relations. Before making a relation between units, input or output pins for these
units may be defined. For some devices, I/O ports are automatically assigned
according to the device type and the installed options.
I/O ports can be Driver-defined, User-defined or Unknown:
Driver-defined ports were created automatically during the driver installation
process and depend on the actual configuration of the unit to which they belong.
User-defined ports are created manually afterwards, see topic Adding I/O Ports
on page 113.
Unknown ports were created in earlier ROSA NMS versions and can be either
Driver-defined or User-defined.
Listing the Currently Defined Input/Output Ports

Introduction
The Input/Output ports of a particular device or all currently defined Input/Output
ports can be checked using the Input/Output Ports dialog of the ROSA NMS system.
The picture below shows an Input/Output Ports dialog with the I/O ports of an
ADVM.
110 4014778 Rev H

In the Input/Output Ports dialog, each port is accompanied with the following
information:
Port Name: name of the port as mentioned in the Server Explorer or Group
Explorer tree.
Port Nr: number of the port
Parent Name: name of the device to which the port belongs
Parent Location: name of the Copernicus server or ROSA NMS Single User
System to which the device is connected
Input ?: represents if the ports is an input port or not
Type: port type, driver-defined or User-defined
Checking the I/O Ports of a Device

The following procedure describes how to display the I/O ports of a device.
1 In the Server Explorer or Group Explorer tree, right-click on the device for
which I/O ports should be displayed and point to I/O Ports... in the short-cut
menu.
Result: The Input/Output Ports dialog with the I/O ports of the selected device
is displayed.
The dialog can be closed by pressing the Close command button.
Checking All Currently Defined I/O Ports

The following procedure describes how to display all currently defined I/O ports.
1 In the Server Explorer or Group Explorer tree, select the server for which
currently defined I/O ports should be displayed.
2 In the Config menu, point to I/O Ports....
Result: The Input/Output Ports dialog with all currently connected I/O ports is
displayed.
The dialog can be closed by pressing the Close command button.
Filtering the Input/Output Ports Dialog

The following procedure explains how to set up a filter for the Input/Output Ports
dialog.
1 In the Server Explorer or Group Explorer tree, select the server for which
currently defined I/O ports should be displayed.
Result: The Input/Output Ports dialog is displayed.
3 Click on the Filter command button in the upper right corner of the dialog.
4014778 Rev H 111

Result: The Filter dialog is displayed.
4 In the On/Off box, set the Filter ON check box.

5 In the Columns list box, select one or more filters to build the filter. To select
consecutive columns, point to the first column, press and hold down the [SHIFT]
key, and point to the last column. To select non-consecutive columns, press and
hold down the [CTRL] key, and point to each column.
6 Click on the And selection button or the Or selection button to select an AND or
OR combination of the selected columns.
7 In the for column drop down box, select one of the columns.
8 In the Methods selection box, select the filter method.
None: no filtering on the selected column
equals/differs: first select equals or differs in the drop down box, then select
one or more values
Between values: select two values
9 Repeat step 7 and 8 for each column selected in the Columns list box.
Note: As long as the OK button is not pressed, the previous filter can be restored
by pressing the Restore previous... command button.
112 4014778 Rev H

Adding Input/Output Ports

For some units, the I/O ports must be added manually. The following steps explain
how to add an I/O port.
1 In the Server Explorer or Group Explorer tree, select the server containing the
device for which an I/O port should be added.
3 Click on the Add command button.
Result: The Add I/O Port dialog is displayed.
4 In the Parent Device drop down box, select the unit for which an I/O port
should be added.
5 In the Port Name box, enter a name for the port. The name will automatically
be enlarged with type (I or O) and port number.
6 In the Port Type selection box, point to the Input or Output selection button.
7 In the Port Number selection box, select one of the following selection buttons:
Single: to create a single port
Range: to create a range of ports of the same type at once
To create a single port, enter the port number. To create a range of ports, enter
the beginning and ending port number.
8 Click on the Add command button to add the port(s) or the Cancel command
button to abort the operation and to close the dialog.
4014778 Rev H 113

Removing Input/Output Ports

Perform the following steps to remove unknown or unused User-defined I/O ports.
1 In the Server Explorer or Group Explorer tree, select the server for which an I/O
port should be removed.
3 Select the I/O port(s) that should be removed. To select consecutive ports, click
on the first port, press and hold down the [SHIFT] key, and point to the last port.
To select non-consecutive ports, press and hold down the [CTRL] key, and point
to each port.
4 Click on the Remove command button.
Notes:
It is not allowed to remove Driver-defined I/O ports. When you try to
remove such a port, the following warning message box is displayed.
If the selection contains Unknown ports, the following warning message box
is displayed.
Click on the Yes command button to remove the Unknown type I/O port or
click on the No command button to close the warning message box without
removing the selected ports.
5 When the I/O port removal action is finished, close the dialog by pressing the
Close command button.
114 4014778 Rev H

Printing the List of Input/Output Ports

The following procedure explains how to print a list of I/O ports.
1 In the Server Explorer or Group Explorer tree, select the server for which a list
with I/O ports should be printed.
3 In the list box on the Input/Output Ports dialog, select the input/output ports
that must be printed. To select consecutive ports, click on the first port, press
and hold down the [SHIFT] key, and point to the last port. To select
non-consecutive ports, press and hold down the [CTRL] key, and point to each
port.
4 Press the Print command button.
Result: The Print dialog is displayed.
5 Select a printer in the Name drop down box.

6 In the Print range selection box, select the Selection selection button to print the
selected ports or the All selection button to print all ports.
7 In the Number of Copies box, specify the number of copies.
8 Click on the OK command button to confirm or the Cancel command button to
Note: The font size can be defined in the View Option dialog. More information
concerning this dialog can be found in topic Changing View Options on page 44.
4014778 Rev H 115

Using Notes
Introduction
For some reason it can be necessary to keep particular information about a resource
to this resource. Therefore notes can be created and attached to a resource. These
notes can then be consulted and/or edited. Notes can be attached to units, tasks,
serial ports...
In the Server Explorer tree, Group Explorer tree, and maps, resources with one or
more notes are indicated by a little yellow square at the bottom right corner of the
icon or bitmap.
Note:
Resource notes can only be opened when the server that controls the resources is
connected. When a server is disconnected, the notes of the resources belonging
to this server will be closed.
The indication of the presence of notes can be propagated to the server level in
the Server Explorer tree, see picture below. The procedure to switch on this
notes present propagation feature can be found in topic Changing View Options
on page 44.
Only the author of a note and the members of the ROSA NMS administrator
group can edit or delete that note.
116 4014778 Rev H

Using Notes
Creating Notes
Perform the following procedure to create a note and to attach this note to a unit.
1 In the Server Explorer tree, Group Explorer tree, or a map, right-click on the unit
for which a note should be attached, select Notes in the short-cut menu, and
point to Create New.
Result: The Please specify a title for the note dialog is displayed.
Note: When a note of a resource is already opened, a new note can be created for
this resource by right-clicking on the note and pointing to Create New in the
short-cut menu.
2 In the Title box, enter a title for the note.
Result: An empty note is displayed.
Note: The creation date of the note is displayed in the bottom left corner of the
note and the author in the bottom right corner.
4 Enter the content of the note.
5 Store the note by closing the note.
A note can be closed by pointing to the Windows Exit button in the Title bar of
the note or by right-clicking on the note and pointing to Close in the short-cut
menu. When multiple notes of a particular resource are opened, these notes can
be closed by right-clicking on one of these notes and pointing to Close All in the
short-cut menu.
Note: A note can be attached to a particular server via a unit in the Server Explorer
tree of this server.
4014778 Rev H 117

Opening Notes
The following procedure describes how to open notes.
1 In the Server Explorer tree, Group Explorer tree, or a map,
right-click on the single resource for which notes should be opened, select
Notes in the short-cut menu and point to Manage
or
right-click on a node containing multiple resources for which notes should be
opened and point to Manage Notes... in the short-cut menu.
Result: The Notes for <unit name> dialog is displayed.
Note: When notes are added while the Notes for <unit name> dialog is
displayed, the dialog can be refreshed by pointing to the Refresh command
button.
Tips:
Selecting a note in the Notes for <unit name> dialog shows the note content
in the bottom box of the dialog.
The notes in the Notes for <unit name> dialog can be filtered by entering a
key word in the Only show Notes Containing box and pressing the Filter
command button.
118 4014778 Rev H

Using Notes
2 In the list box, select the note(s) that should be opened. To select consecutive
notes, select the first note, press and hold down the [SHIFT] key, and point to the
last note. To select notes that are not consecutive, press and hold down he
[CTRL] key, and select each note.
3 Press the Show command button.
Result: The selected notes are opened.
Notes:
The Notes for <unit name> dialog can be closed by pressing the Exit command
button.
All files of a particular unit can be opened by right-clicking on the unit, selecting
Notes in the short-cut menu and pointing to Show All.
A note can be closed by pointing to the Windows Exit button in the Title bar of
the note or by right-clicking on the note and pointing to Close in the short-cut
menu. When multiple notes of a particular resource are opened, these notes can
be closed by right-clicking on one of these notes and pointing to Close All in the
short-cut menu.
Editing a Note
When a note is opened and you are either the author of the note or a member of the
ROSA NMS administrator group, you can edit the note content in the note dialog.
The changes are saved by closing the note. The date and time in the note will be
updated.
Changing the Title of a Note

The following procedure explains how to change the title of a note.
Note: The title of a note can only be changed by the author of the note or by a
member of the ROSA NMS administrator group.
of which the title of a note should be changed, select Notes in the short-cut menu
and point to Manage.
2 In the list box, select the note of which the title must be changed, and point to the
Show command button.
Result: The note is opened.
3 Right-click on the note and point to Edit Title in the short-cut menu.
4014778 Rev H 119

Result: The Please specify a title for the note dialog is displayed.
4 In the Title box, enter the new name for the note.
6 Close the note.
7 Press the Exit command button to close the Notes for <unit name> dialog.
Deleting Notes
The following procedure explains how to delete a note.
Note: A note can only be deleted by the author of the note or by a member of the
ROSA NMS administrator group.
of which notes should be deleted, select Notes in the short-cut menu and point to
Manage.
2 In the list box, select the note(s) that must be deleted and point to the Delete
command button. To select consecutive notes in the list box, press the first note,
hold down the [SHIFT] key and point to the last note. To select notes that are
not consecutive, press the [CTRL] key and point to each note.
3 Click on the Yes command button to delete the notes or the No command button
4 Press the Exit command button to close the Notes for <unit name> dialog.
Note: A note can also be deleted by right-clicking on the note and pointing to Delete
120 4014778 Rev H

Displaying Unit Information in the Server Explorer or Group Explorer Tree
Displaying Unit Information in the Server Explorer or Group

Explorer Tree
Introduction
In the Server Explorer or Group Explorer tree, information can be added to units.
This information is:
Resource ID: the unique identifier that the ROSA NMS system assigns to each
resource
Additional Information: the embedded software version, device address, the
COM port the device is connected to and so on, depending on the information
the ROSA NMS system has about the resource.
The following picture shows a Server Explorer tree of which resources are
accompanied with Resource ID.
To Display Unit Information in the Server Explorer or Group Explorer Tree

Perform the following steps to customize the information accompanied a unit in the
Server Explorer or Group Explorer tree.
right-click on the Units node of which the units should be accompanied with
information and point to Display Options... in the short-cut menu.
Result: The ROSA Unit Options dialog is displayed.
4014778 Rev H 121

2 In the Show box, set the Resource ID check box to display the ID or clear the
check box to hide the ID.
3 Set the Additional Information check box to display the additional information
or clear the check to hide the information.
122 4014778 Rev H

8 Chapter 8
Working with Servers
Introduction
This chapter describes how to handle servers into ROSA NMS
In This Chapter
Introduction ......................................................................................... 124
Adding and Removing Servers......................................................... 125
Connecting and Disconnecting Servers ........................................... 128
Stopping, Rebooting and Starting a Server ..................................... 133
Defining a Master Server ................................................................... 137
Manipulating the Global Inventory ................................................. 138
Sending Messages............................................................................... 145
Synchronizing Date and Time .......................................................... 148
Changing Server Settings................................................................... 150
Viewing Trace Files ............................................................................ 155
Checking Server Availability ............................................................ 161
Using Active or Passive FTP ............................................................. 163
4014778 Rev H 123

Chapter 8 Working with Servers
Introduction
About the Client/Server Architecture
The ROSA/Copernicus system has a client-server architecture with ROSA NMS as
the client part and the Copernicus the server part. Depending on the ROSA NMS
Copernicus version, the ROSA/Copernicus client/server architecture differs:
ROSA NMS Client/Server: the ROSA NMS client software part of the ROSA
NMS Client/Server system is installed on a remote PC and the Copernicus
server software part on a Copernicus server or SI-Server. The remote computer
running the ROSA NMS client software (ROSA NMS Client System) can be
connected to several Copernicus Servers or SI-Servers and a Copernicus server or
SI-Server can be connected to several ROSA NMS Client Systems.
ROSA NMS Single User: the ROSA NMS client software part as well as the
Copernicus server software part is installed on the same computer. The
computer running ROSA NMS Single User software (ROSA NMS Single User
system) can be connected to its own server (called Local Server) or to several
Copernicus servers or SI-Servers.
ROSA NMS Device Configuration Shell: the ROSA NMS client software part as
well as the Copernicus server software part is installed on the same computer.
The computer running the ROSA NMS Device Configuration Shell software
(ROSA NMS Device Configuration Shell System) can only be connected to its
own server.
124 4014778 Rev H

Adding and Removing Servers

Introduction
A ROSA NMS Single User and ROSA NMS Client system can be connected to
external servers, like Copernicus servers or SI-Servers. Before a ROSA NMS system
can be connected to an external server, the server must be added to the Server
Explorer tree of the ROSA NMS system. Once an external server is added to the
Server Explorer tree, the ROSA NMS system should be connected to the external
server. The procedure to connect a ROSA NMS system to an external server can be
found in topic Connecting and Disconnecting a Server further in this chapter.
Note: Since a ROSA NMS Device Configuration Shell system cannot be connected to
external servers, the sub topics in this topic can be omitted for users of such ROSA
NMS system.
Adding a Server to the ROSA NMS System

Before a server can be controlled by a ROSA NMS Client or ROSA NMS Single User
system, the server should be added to the system. The following procedure
explains how to add a server to the ROSA NMS system.
right-click on the Global Inventory node and point to New Server in the
short-cut menu.
Result: The Server Settings dialog is displayed.
2 In the Server Name box, enter a name for the server. This name is used to label
the server in the ROSA NMS system.
3 In the Computer Name box, type the computer name or the IP address of the
server.
4014778 Rev H 125

The computer name identifies the server on the network. The default computer
name for a Copernicus server is COP00000 and for a SI-Server is SIS00000.
When the computer name of the server is changed, use this changed name.
Notes:
Both the Server Name as well as the Computer Name are case-sensitive.
When an IP Address is used to identify the server on the network. The
octets of the IP address must be separated by dots.
Note: After pressing the OK command button the following message box
displays for a while.
Result: The server is added to the Server Explorer and Group Explorer tree of
the ROSA NMS system.
Notes:
Once a server is added to the ROSA NMS system, the server should be connected
to the system. The procedure to connect a server to the ROSA NMS system can
be found in topic Connecting a Server to the ROSA NMS System on page 128.
When the server is not displayed in the tree, check the IP connectivity by using
for instance a Ping action.
The computer name of a server can always be changed by a ROSA system that is
connected to the server. The procedure to change the computer name can be
found in topic Changing the Computer Name on page 151. The network settings
of this server must be updated manually for all other connected ROSA NMS
systems. When the computer name of a server is changed on the server itself,
the server settings must also be updated manually for all connected ROSA NMS
systems. The procedure to update servers settings can be found in topic
Changing the Network Settings on page 154.
126 4014778 Rev H

Removing a Server from the Server Explorer

A server can be removed from the Server Explorer and Group Explorer tree only
when the server is disconnected. The procedure to disconnect a server can be found
in sub topic Disconnecting a Server from the ROSA NMS System on page 130.
The following procedure explains how to remove a server from the Server Explorer
and Group Explorer tree.
right-click on the server that should be removed and point to Remove in the
short-cut menu.
Note: The Remove menu item in the short-cut menu is not applicable if the
server is still connected.
2 Press the Yes command button to remove the server or the No command button
4014778 Rev H 127

Connecting and Disconnecting Servers

Introduction
Once external servers are added to the Server Explorer or Group Explorer tree of a
ROSA NMS Single User system or ROSA NMS Client system, the ROSA NMS
system should be connected to the external servers before the system can manage
these external servers or the devices connected to these servers.
The Local Server of the ROSA NMS Single User system as well as the Local Server
of the ROSA NMS Device Configuration Shell system should also be connected
before devices can be managed.
Connecting a Server to the ROSA NMS System

The following steps explain how to connect a server to the ROSA NMS system.
right-click on the server that should be connected and point to Connect in the
short-cut menu.
Result: The connection-making-process with the server is started.
Notes:
As long as the license file of a ROSA NMS Single User or ROSA NMS Device
Configuration Shell system is not installed, the connection-making-process to
the Local Server of the ROSA NMS system will not be started. In this case
the following message is displayed.
The procedure to install the license file can be found in topic Installing a
License File on page 63.
The connection-making-process of the ROSA NMS system with a server can
take some time. During this time the following message is displayed.
As long as this message is displayed, the connection-making-process can be

aborted by pressing the Cancel command button. Point to the Cancel All
command button to stop the connection-making-process to all servers.
128 4014778 Rev H

Result: When the connection is made, the ROSA Login dialog is displayed.
2 Enter your user identification in the User ID box and the corresponding
password in the Password box.
Note: Both parameters are case-sensitive.
Result: Once the connection is made with the server and logged on with valid
login parameters, the red bar across the server icon in the Server Explorer or
Group Explorer tree is removed.
Notes:
When other servers are connected to the ROSA NMS system of which the
login parameters match the login parameters of the server that should be
connected, the login parameters don't have to be re-entered. In this case the
ROSA Login dialog is not displayed.
When a Copernicus server or SI-Server is connected to a ROSA NMS system
for the first time, the default login parameters must be used. The following
table shows the default login parameters for the Copernicus server and the
SI-Server.
Server User Identification Password

Copernicus server Administrator copadmin
SI-Server Administrator sisadmin
As soon as the ROSA NMS system is connected to the server, a dialog is
displayed asking to change the login parameters of the server.
Notes:
When one or more servers are not yet connected, right-clicking on a server in the
Server Explorer tree and pointing to Connect All in the short-cut menu starts a
process to connect all servers. When no Copernicus server is connected yet, the
ROSA Login dialog is displayed asking the logon information for the first
server. For the remaining Copernicus servers, the same logon information will
4014778 Rev H 129

be used. If the login information is incorrect for a server, the ROSA Login
dialog will be displayed again.
When a ROSA NMS Client or ROSA NMS Single User system is connected to a
Copernicus server or SI-Server running a master ROSA NMS software with
higher version, a dialog is displayed asking a ROSA NMS software upgrade.
For more information concerning software upgrading, please refer to topic
Upgrading Client Software via a Copernicus Server or SI-Server on page 499.
Disconnecting a Server from the ROSA NMS System

The following procedure describes how to disconnect a server from the ROSA NMS
system.
right-click on the server that should be disconnected and point to Disconnect in
the short-cut menu.
Result: The server is disconnected from the ROSA NMS system.
Notes:
The ROSA NMS system can be disconnected from all connected servers in
one action by selecting Disconnect All in the short-cut menu that appears
after right-clicking on a connected server in the Server Explorer or Group
Explorer tree.
A server disconnected from the ROSA NMS system is indicated by a
red-crossed server icon (Copernicus server in the picture below).
Checking the Currently Connected Clients to a Server

Since multiple ROSA NMS client systems and/or ROSA NMS Single User systems
can be connected to a Copernicus server or SI-Server simultaneously, it can be useful
to check the currently connected ROSA NMS systems to a particular server. The
following steps explain how to check the currently connected ROSA NMS systems to
a server.
1 In the Server Explorer or Group Explorer of the ROSA NMS system, right-click
on the server and point to Currently Connected Clients in the short-cut menu.
130 4014778 Rev H

Result: The Clients currently connected to server dialog is displayed.
The following information is available:

Location: represents the computer name of the currently connected ROSA
NMS systems.
Login Name: represents the login name of the currently connected ROSA
NMS systems.
Module: represents the modules running on the connected ROSA NMS
systems:
ROSA NMS itself
the ROSA NMS drivers
the user interfaces of the resources
Last Resource: represents the last resource accessed by the ROSA NMS
system.
2 Click on the Refresh command button to update the dialog or the OK command
button to close the dialog.
Setting the Auto Connect Parameters

Setting the Server Auto Connect Parameters
At startup, ROSA NMS system is able to connect automatically with those servers
that were connected the last time that ROSA NMS was shutdown. This feature can
be enabled on the Auto Connect tab of the Preferences dialog.
Setting the Auto Connect Parameters

Perform the following steps to set the Auto Connect parameters.
1 In the File menu on the ROSA NMS system, click on Preferences.
2 Click on the Auto Connect tab.
4014778 Rev H 131

Result: The Auto Connect tab is displayed.
3 In the Auto Connect settings selection box, point to one of the following
selection buttons.
Yes: server auto connect enabled
No: server auto connect disabled
Ask me when Starting Up: the ROSA NMS system asks to confirm before
auto connecting to servers. Click on Yes to confirm.
4 Click on OK command button to confirm or the Cancel command button to
132 4014778 Rev H

Stopping, Rebooting and Starting a Server

Introduction
The server software of a ROSA NMS Single User system, ROSA NMS Device
Configuration Shell system, Copernicus Server, or SI-Server can be stopped. This
can be useful to stop managing a particular application. When the server software
of a Copernicus server or SI-Server is stopped, all connected ROSA NMS systems
receive a diagnostic message indicating that the server will be stopped. The
following picture depicts such a message.
Once the server software is stopped, this can be restarted by reconnecting to the
server. The procedure to connect to a server can be found in topic Connecting a
Server to the ROSA NMS System on page 128.
When a ROSA NMS Client system or ROSA NMS Single User system connects to a
Copernicus server or SI-Server of which the server software is stopped, the server
software will be restarted and all ROSA NMS systems connected to the server
receives a diagnostic message indicating that the server software is restarted. The
following picture depicts such a message.
4014778 Rev H 133

For some purposes, for instance after a driver installation, it can be necessary to
reboot the ROSA NMS system, Copernicus server, or SI-Server. When a Copernicus
server or SI-Server reboots, all connected ROSA NMS systems receive a diagnostic
message. The following picture depicts such a message.
After rebooting the server, the server software starts automatically. The ROSA
NMS systems that were connected to the server before the rebooting action, will be
informed by a message. The following picture shows such a message.
When a Copernicus server or SI-Server is stopped or rebooted by means of a ROSA

NMS system, the connected ROSA NMS systems will disconnect automatically. If
this server or one of its resources is selected in the Server Explorer tree, the user ID
of the current user in the status bar is displayed between <> brackets.
134 4014778 Rev H

As soon as the server is running again after a server reboot action, all ROSA NMS
systems will be reconnected automatically and the brackets around the user ID
disappear.
Notes:
Since the message sending functionality of the ROSA/Copernicus software uses
the Messenger service of the Windows operating system, this service should be
started up. By default, this service is disabled on computers running Windows
XP Service Pack 2. The procedure to enable this service can be found in topic
Starting Messenger Service on page 448.
To reduce the number of diagnostic messages, a server can sent its diagnostic
messages to only one ROSA NMS system, called Default Client. Therefore the
Default Client must be defined. The procedure to define the Default Client for a
particular server can be found in topic Defining a Default Client on page 146.
Stopping the Server Software of the ROSA NMS System or Server

The following procedure explains how to stop the server software of a ROSA NMS
Single User system, ROSA NMS Device Configuration Shell system, Copernicus
Server, or SI-Server.
1 On the Server Explorer or Group Explorer tree of the ROSA NMS system, select
the server for which the server software must be stopped.
2 In the Server menu, click on Manage and point to Stop Server Software...
3 Click on the Yes command button to confirm or the No command button to abort
the operation.
Result: After pressing the Yes command button, a message box appears
indicating the server is stopped.
4 Press the OK command button to close this message box.
Rebooting the ROSA NMS System or Server

The following steps explain how to reboot a server.
the server that should be rebooted.
2 In the Server menu, select Manage and point to Restart Server Software....
4014778 Rev H 135

3 Press the Yes command button to confirm or the No command button to abort
the reboot operation.
Result: After pressing the Yes command button, the server start rebooting and a
message box appears.
4 Press the OK command button to close this message box.
136 4014778 Rev H

Defining a Master Server
Defining a Master Server

Introduction
In an application with several client computers and servers, it can be useful to have
the same Server Explorer tree and maps on all client computers and servers. To
achieve this, a master server should be defined. Once a master server is defined in
the application, a synchronization action can be performed between the master
server and the client computers or servers.
For more information concerning maps and synchronizing maps, please refer to
topic Working with Maps on page 261. For more information about synchronizing
Server Explorers, please refer to Synchronizing Date and Time on page 148.
Note: Since a ROSA NMS DCS system cannot be connected to external servers, the
sub topics in this topic can be omitted by ROSA NMS DCS users.
To Define a Master Server

The following procedure explains how to define a master server.
the server that should be the master server.
2 In the Server menu, point to Master.
Result: The selected server becomes master server.
Note:
A server can also be set to master server by right-clicking on the server in the
Server Explorer or Group Explorer tree and pointing to Master in the short-cut
menu.
A master server is indicated by small blue star on the server icon in the Server
Explorer tree.
4014778 Rev H 137

Manipulating the Global Inventory

Introduction
Since the Global Inventory of a server made on a ROSA NMS client or ROSA NMS
Single User system is stored locally on the ROSA NMS system, it is a big job to create
similar Global Inventories on different ROSA NMS client or ROSA NMS Single User
systems. To facilitate this, a Global Inventory synchronization can be executed
between two ROSA NMS systems connected to the same master server. Such
synchronization action is performed in two steps:
Copying the Server Inventories of the ROSA NMS system to the master server.
Copying the Server Inventories stored on the master server to the ROSA NMS
system.
Copying the Server Inventories of a ROSA NMS System to the Master Server
The following steps explain how to copy the Global Inventory of a ROSA NMS
system to the master server.
1 In the Server Explorer or Group Explorer tree of the ROSA NMS system
containing the correct server inventories, right-click on the Global Inventory or
Group Inventory node, and point to Synchronize with Master... in the short-cut
menu.
Result: The Inventory Synchronization dialog is displayed.
138 4014778 Rev H

Note: The Current Local Inventory list box is provided with the inventories of
all servers added to the Server Explorer or Group Explorer tree of the ROSA
NMS system. When this step is perform on a ROSA NMS Single User system,
the server inventory of the local server of the ROSA NMS Single User system is
also displayed in the Current Local Inventory list box.
2 In the Current Local Inventory list box, select one or more server inventories.
To select consecutive server inventories, click on the first server inventory, press
and hold down the [SHIFT] key, and then click on the last server inventory. To
select server inventories that are not consecutive, press and hold down the
[CRTL] key, and point to each server inventory.
3 Press the Copy to Master command button.
Result: The selected server(s) is (are) added to the Current Master Inventory list
box. The Will Be column in both the Current Local Inventory list box and the
Current Master Inventory list box displays the action that will be performed
after pressing the Synchronize command button.
Note: To undo copying of one or more server inventories to the master server,
select them in the Current Local Inventory or Current Master Inventory list box
and press the corresponding Undo command button.
4 Press the Synchronize command button to confirm or the Cancel command
button to abort the synchronization action.
Result: After a successful synchronization action the following message box is
displayed.
5 Click on the OK command button to close the message box.
4014778 Rev H 139

Copying Server Inventories from a Master Server to a ROSA NMS System

Perform the following steps to copy server inventories from a master server to a
ROSA NMS System.
1 In the Server Explorer or Group Explorer tree of the ROSA NMS system that
requires the server inventories, right-click on the Global Inventory or Group
Inventory node, and point to Synchronize with Master... in the short-cut menu.
Note: The server inventories stored on the master server or shown in the Current
Master Inventory list box.
2 In the Current Master Inventory list box, select one or more server inventories.
To select consecutive server inventories, click on the first server inventory, press
and hold down the [SHIFT] key, and then click on the last server inventory. To
select server inventories that are not consecutive, press and hold down the
[CRTL] key, and point to each server inventory.
3 Press the Copy to Client command button.
140 4014778 Rev H

Result: The selected server(s) is (are) added to the Current Local Inventory list
box. The Will Be column in both the Current Local Inventory list box and the
Current Master Inventory list box displays the action that will be performed
Note: To undo copying of one or more server inventories from the master server,
select them in the Current Local Inventory or Current Master Inventory list box
Result: After a successful synchronization action the following message box is
displayed.
Updating Server Inventories on the Master Server

The following procedure describes how to update server inventories on the master
server when server inventories on the ROSA NMS system are changed.
1 In the Server Explorer or Group Explorer tree of the ROSA NMS system of
which server inventories are changed, right-click on the Global Inventory or
Group Inventory node, and point to Synchronize with Master... in the short-cut
menu.
4014778 Rev H 141

2 In the Current Local Inventory list box, select the server inventories that should
be updated. To select consecutive server inventories, click on the first server
inventory, press and hold down the [SHIFT] key, and then click on the last server
inventory. To select server inventories that are not consecutive, press and hold
down the [CRTL] key, and point to each server inventory.
3 Click on the Copy to Master command button.
Result: The server inventories on the master server will be overwritten by the
selected server inventories on the ROSA NMS system after pressing the
Synchronize command button.
Note:
The action that will be performed after pressing the Synchronize command
button is indicated in the Will Be column of the of the Current Master
Inventory and Current Local Inventory list box.
To undo updating one or more server inventories on the master server, select
them in the Current Master Inventory and Current Local Inventory list box
Result: After a successful synchronization action a message box is displayed.
5 Click on the OK command button to close this message box.
Updating Server Inventories on the ROSA NMS System

Perform the following steps to update server inventories on a ROSA NMS system.
1 In the Server Explorer or Group Explorer tree of the ROSA NMS system of
which server inventories should be updated, right-click on the Global Inventory
or Group Inventory node, and point to Synchronize with Master... in the
short-cut menu.
142 4014778 Rev H


2 In the Current Master Inventory list box, select the server inventories that must
be updated. To select consecutive server inventories, click on the first server
3 Press the Copy to Client command button.
Result: The server inventories on the ROSA NMS system will be overwritten by
the selected server inventories on the master server after pressing the
Synchronize command button.
Note:
Inventory and Current Local Inventory list box.
To undo updating one or more server inventories on the ROSA NMS system,
select them in the Current Master Inventory and Current Local Inventory
list box and press the corresponding Undo command button.
4014778 Rev H 143

Removing Server Inventories from the Master Server

The following steps explain how to remove server inventories from the master
server.
right-click on the Global Inventory or Group Inventory node, and point to
Synchronize with Master... in the short-cut.
2 In the Current Master Inventory list box, select the server inventories that must
be removed. To select consecutive server inventories, click on the first server
Result: The selected server inventories on the master server will be removed
Note:
Inventory list box.
To undo removing one or more server inventories on the master server, select
them in the Current Master Inventory list box and press the corresponding
Undo command button.
144 4014778 Rev H

Sending Messages
Sending Messages
Introduction
When ROSA NMS systems are connected to the same Copernicus server or
SI-Server, messages can be sent between these ROSA NMS systems. The following
picture shows an example of a message.
Note: Since the message sending functionality of the ROSA/Copernicus software

use the Messenger service of the Windows operating system, this service should be
started up. By default, this service is disabled on computers running Windows XP
Service Pack 2. The procedure to enable this service can be found in topic Starting
Messenger Service on page 448.
By default diagnostic messages generated by a server, like the messages indicating a
server reboot, are sent to all ROSA NMS systems connected to this server. The
ROSA NMS system allows sending diagnostic messages to one ROSA NMS system,
called Default Client.
To Send Messages Between ROSA NMS Systems

The following procedure explains how to send messages between two ROSA NMS
system, which are connected to the same server.
1 In the Server menu, point to Currently Connected Clients.
4014778 Rev H 145

Result: The Clients currently connected to server dialog is displayed.
2 Select the ROSA NMS system to which a message should be sent and point to the
Send Message command button.
Result: The Message to <computer name> dialog is displayed.
3 Enter the message in this dialog.

Note: The content of this dialog can be cleared by pressing the Clear command
button.
4 Press the Send command button to send this message or the Cancel command
5 After sending the message, the Clients currently connected to server dialog can
be closed by pressing the OK command button.
Defining a Default Client

Diagnostic messages generated by a server to indicate for instance a server reboot,
are sent to each connected ROSA NMS system. To reduce the number of messages,
the diagnostic messages can be sent to only one ROSA NMS system, the default
client. The following procedure explains how to define the default client.
1 In the Server Explorer or Group Explorer tree, select the server for which a
default client should be defined.
2 In the Server menu, point to Options....
146 4014778 Rev H

Sending Messages
Result: The Server Options dialog is displayed.
3 In the Send to Computer box, enter the computer name of the ROSA NMS
system to which the diagnostic messages must be sent.
4014778 Rev H 147

Synchronizing Date and Time

Introduction
The time and date of a Copernicus server or SI-Server leaving our assembly line is
set to the Central European Time (CET). When a server is installed in another time
zone, the date and time can be adjusted by changing the date and time manually or
by synchronizing the date and time with a ROSA NMS system. Synchronizing the
date and time of several ROSA NMS systems can also be synchronized with a server.
To Synchronize Date and Time

The following procedure explains how to synchronize the date and time of a server
with a ROSA NMS system or vice versa.
Notes:
Since the server and client software of a ROSA NMS Single User and ROSA NMS
DCS system runs on the same computer and uses the same data and time, it is
pointless to synchronize the ROSA NMS system with its own local server or vice
versa.
Since the ROSA NMS DCS system cannot be connected to an external server, this
sub topic can be omitted by ROSA NMS DCS users.
the server that must be synchronized or that must be used to synchronize the
ROSA NMS system.
2 In the Server menu, point to Date/Time...
Result: The Synchronization dialog is displayed.
3 Click on the Sync Client command button to synchronize the ROSA NMS
system with the server or the Sync Server command button to synchronize the
server with the ROSA NMS system.
4 Click on the Close command button to close the dialog.
148 4014778 Rev H

Synchronizing Date and Time
To Adjust the Time and Date Manually

Perform the following steps to adjust the date and time of a ROSA NMS system,
Copernicus server, or SI-Server manually.
the server for which the date and time must be changed.
2 In the Server menu, point to Date/Time...
Result: The Synchronization dialog is displayed.
3 Click on the Set... command button.
Result: The Set Server Date/Time dialog is displayed.
4 In Time box, select the value that must be changed and point to the up or down
command button to change the value.
5 In the Date box, adapt the date values. The date can also be changed using the
Date Picker. Therefore point to the down arrow button.
6 Click on the Set command button to confirm and close the Set Server Date/Time
dialog by pressing the Close command button.
7 Close the Synchronization dialog by pressing the Close command button.
4014778 Rev H 149

Changing Server Settings

Changing the Server Identification Settings
Perform the following steps to change the identification settings of a server.
Note: Since the server and client software of a ROSA NMS Single User or ROSA
NMS DCS system runs on the same computer, changing the computer name of the
Local Server will change the name of the computer on which the ROSA NMS
software runs.
right-click on the server for which the server identification settings must be
changed and point to Disconnect in the short-cut menu.
2 Right-click on the server for which identification settings must be changed and
point to Settings in the short-cut menu.
Result: The Server Settings dialog is displayed.
3 In the Server Name box, enter a name for the server. This name is used to
identify the server in the ROSA NMS system, for example in the Server Explorer
tree.
4 In the Computer Name box, enter the computer name or IP Address of the
server.
Notes:
This name must match the computer name of the server, otherwise the ROSA
NMS system is not able to connect to the server.
If an IP address is entered, the octets of the IP address must be separated by
dots.
When the name of the server is changed using the procedure described in
topic Changing the Computer Name on page 151, the new computer name is
automatically filled in.
150 4014778 Rev H

Note: After changing the server identification settings, the server can be
re-connected to the ROSA NMS system.
Changing the Computer Name

When a Copernicus server or SI-Server leaves our assembly line, the computer name
of a Copernicus server is set to COP00000 and the computer name of a SI-Server to
SIS00000. The computer name of a server can be changed on the server itself before
this server is added to a ROSA NMS system or via the ROSA NMS system.
The following procedure explains how to change the computer name of a
Copernicus server or SI-Server via the ROSA NMS system.
the server for which the server name should be changed.
2 In the Server menu, point to Computer Name....
Result: The Server Computer Name dialog is displayed.
3 In the New Computer Name box, enter a new name.

Note: The computer name of a Copernicus server or SI-Server is limited to 15
characters and can not contain spaces or any of the following characters: , ? \ = +
"><*:;|
Result: After pressing the OK command button, a message box is displayed
indicating that the server must be rebooted.
5 Press the Yes command button to reboot the server or the NO command button
to postpone the server reboot.
4014778 Rev H 151

Since the server settings in the Server Explorer tree and also in the maps are
updated automatically after pressing the Yes command button, it is
recommended to reboot the server directly after renaming the server. When the
server reboot is postponed by clicking on the No command button, the server
settings in the Server Explorer tree of all connected ROSA NMS systems and in
the maps must be changed manually after a manual server reboot. The
procedure to perform a server reboot manually can be found in topic Stopping,
Rebooting and Starting a Server on page 133.
Notes:
When the computer name of a Copernicus MKII, MKIII, or SI-Server is changed,
the gamscm.ini file must be updated. For more information, please refer to the
publications shipped with the server.
Since the Copernicus MKIV, MKIV System G4, Continuum DVP SI-Server, and
Continuum DVP SI-Server System G4 don't use the gamscm.ini file, no updates
are required.
When a user interface of a unit is opened via a map, the computer name is used
to connect to the server the unit is managed by. If the computer name of a
server is changed via the ROSA NMS user interface, the maps on the ROSA NMS
Client system that is used to change the computer name are updated
automatically. On all other ROSA NMS client systems that have a copy of these
maps, the computer name has to be changed manually. More information
concerning maps can be found in chapter Working with Maps on page 261.
Set the ROSA NMS map system to Editing mode. The procedure to change
the map mode can be found in topic Map Modes on page 265.
In the Maps menu, point to Diagnostics and click on the Change Computer
Name....
Result: The Change Computer Name dialog is displayed.
Enter the old computer name in the Old box and the new computer name in
the New box.
Point to the Update command button to confirm or the Cancel command
152 4014778 Rev H

Changing the Administrative User Password

Introduction
Each Copernicus server or SI-Server leaving our assembly line is configured with a
default administrative user password:
Copernicus server: copadmin
SI-Server: sisadmin
For security reasons, it is strongly recommended to change this administrative user
password.
Note: This administrative user password is a password for the Windows account,
not a ROSA NMS system password.
WARNING:
If the computer of the ROSA NMS Single User system or ROSA NMS Device
Configuration Shell system runs Windows 2000, Windows Server 2003 or
Windows XP, the administrative password has to be changed via the ROSA NMS
user interface using the following procedure. When the password is changed
without using the ROSA NMS user interface, particular services and the DCOM
administrator password must be changed manually. The procedure to change
these passwords can be found in topic Changing Administrative Password on
page 451.
To Change the Administrative User Settings

The following procedure explains how to change the administrative user password.
the server for which the administrative user settings should be changed.
2 In the Server menu, point to Administrative User Password....
Result: The Server Administrative User dialog is displayed.
3 In the Old Password box, enter the current password.

4 In the New Password and Confirm box, enter the new password for the
administrative user.
5 Press the OK command button to activate or the Cancel command button to
4014778 Rev H 153

Changing the Network Settings

The following procedure explains how to change the network settings of a server.
the server for which the server settings must be changed.
2 In the Server menu, point to Network Settings....
Result: The Server Network Settings dialog is displayed.
Note: If the server participates in a network using the Dynamic Host

Configuration Protocol (DHCP), the octets of the IP Address and Subnet Mask
will be zero. In this case the network settings of the server cannot be changed.
3 In the IP Address box, enter the new IP address for the server. The octets of the
IP address must be separated by dots.
Note: Ethernet interfaces with conflicting IP Address may cause serious network
problems. Contact your network administrator for correct IP settings.
4 In the Subnet Mask box, enter the mask that determines the subnet to which the
IP address belongs. The octets of the Subnet Mask must be separated by dots.
5 In the Default Gateway box, enter the default gateway IP address. The octets of
the default gateway IP address must be separated using dots.
The new network settings are activated after rebooting the server. The procedure to
reboot a server can be found in topic Stopping, Rebooting and Starting a Server on page
133.
154 4014778 Rev H

Viewing Trace Files
Viewing Trace Files

Introduction
A Copernicus server, SI-Server, and ROSA NMS Single User system can trace a
number of actions and stores this information in log files. To generate traces in
trace files the tracing feature on the server must be enabled. The procedure to
enable the tracing feature can be found in topic Enabling or Disabling Tracing for a
Particular Server on page 156.
The trace files generated by a particular server or ROSA NMS Single User system
can be displayed using the Trace dialog of ROSA NMS. The following picture
shows a CopTrace dialog.
Most of the traces logged by a server are stored into the Coptrace log file but traces
of particular resources are stored in separate trace files. The presence of a trace file
depends on the presence of the corresponding resource.
Each time the server is rebooted, a new Coptrace file is created and the old Coptrace
file stored. Up to 5 old Coptrace files are kept on the server.
4014778 Rev H 155

Traces of a particular trace file can also be printed or exported to another

application. The following picture shows traces pasted in Microsoft Excel.
Enabling or Disabling Tracing for a Particular Server

The following procedure explains how to enable or disable the tracing feature of a
particular server.
the server for which the tracing feature must be enabled or disabled.
2 In the Server menu tick the Trace menu item to enable the tracing feature or
clear the menu item to disable the feature.
Viewing Trace Files

Perform the following steps to display a trace file of a particular server.
the server for which traces must be checked.
2 In the View menu, tick the Trace Log menu item.
Result: The Trace dialog containing the traces of the Coptrace file of the selected
server is displayed.
156 4014778 Rev H

Viewing Trace Files
Notes:
To display the traces of other trace files, right-click on the list box of the Trace
dialog and point to the desired trace file.
To reduce the number of displayed traces, the traces can be filtered. For
information about filtering traces, please refer to topic Filtering Trace Files on
page 157.
The server continues adding traces to a trace file. When traces of a trace file
are displayed, the Trace dialog is not automatically updated. Press the
Refresh command button to update the Trace dialog.
3 In the View menu, clear the Trace Log menu item to close the Trace dialog or
click on the Exit button in the title bar of the dialog.
Filtering Trace Files

The following steps explain how to filter the trace files displayed in the Coptrace
dialog.
1 Right-click on the list box of the Coptrace dialog and point to Display Options...
4014778 Rev H 157

Result: The Display Options dialog is displayed.
2 For each filter item, specify:

Include: The filter item is taken into account during the filter operation.
Exclude: The filter item is skipped during the filter operation.
Use the drop down box in front of each item to make the selection.
3 In the ThreadID box, enter the identification number of the thread that must be
used to filter the traces.
4 In the Module box, enter the name of the module that must be used to filter the
traces.
5 In the Info box, type a string that is a part of the trace information that must be
used to filter the traces.
Notes:
The ThreadID, Module, and Info boxes are note case sensitive.
The ThreadID, Module, and Info boxes allow using wild cards. Use the
asterisk character (*) as a substitute for zero or more characters and the
question mark as a substitute for a single character.
For multiple filters, use ; without extra spaces before and after.
6 Point to the OK command button to apply the filter or the Cancel command
Results: After pressing the OK command button, only the traces complying the
filter are displayed.
Copying Traces to a File

The following procedure explains how to copy traces logged into a log file.
1 In the Server Explorer or Group Explorer tree in the ROSA NMS system, select
the server for which traces must be copied.
2 In the View menu, tick the Trace Log.
158 4014778 Rev H

Viewing Trace Files
Result: The Coptrace dialog with the traces of the selected server is displayed.
3 Right-click on the list box in the Coptrace dialog and point to the trace file of
which traces must be copied.
Result: The traces of the selected trace file appear in the Coptrace dialog.
Notes:
page 157.
When only a number of traces should be copied, select these traces in the list
box. To select consecutive traces in the list box, point to the first trace, press
and hold down the [SHIFT] key, and point to the last trace. To select non
consecutive traces, press and hold down the [CTRL] key, and click on each
trace.
4 Right-click on the list box and point to Copy to Clipboard in the short-cut menu.
Result: The traces are copied to the Windows Clipboard.
5 Open the application to which the traces should be pasted.
6 Paste the content of the clipboard in the application.
7 In the View menu of the Trace dialog, clear the Trace Log menu item to close the
Trace dialog or click on the Exit button in the title bar of the dialog.
Printing Traces
The following procedure explains how to print traces logged into a log file.
1 In the Server Explorer or Group Explorer tree in the ROSA NMS system, select
the server for which traces should be printed.
2 In the View menu, point to Trace Log.
Result: The Coptrace dialog with the traces of the selected server is displayed.
3 Right-click on the list box in the Coptrace dialog and point to the trace file of
which traces must be printed.
Result: The traces of the selected trace file appear in the Coptrace dialog.
Notes:
page 157.
When only a number of traces should be printed, select these traces in the list
box. To select consecutive traces in the list box, point to the first trace, press
and hold down the [SHIFT] key, and point to the last trace. To select non
consecutive traces, press and hold down the [CTRL] key, and click on each
trace.
4 Right-click on the list box and point to Print in the short-cut menu.
4014778 Rev H 159


selected traces or the All selection button to print all displayed traces.
Note: The font size can be defined in the View Option dialog. More
information concerning this dialog can be found in topic Changing View Options
on page 44.
9 In the View menu, clear the Trace Log menu item to close the Trace dialog or
click on the Exit button in the title bar of the dialog.
160 4014778 Rev H

Checking Server Availability
Checking Server Availability

Introduction
The ROSA NMS system has the option to check the availability of servers to which
the ROSA NMS system is connected to and listening to. By default both checks are
disabled. If the checks are enabled, the ROSA NMS system generates an alarm
when a server becomes unreachable.
Setting the Server Availability Checking Preferences

Perform the following steps to set the server availability checking preferences.
1 In the File menu of the ROSA NMS user interface, click on Preferences....
2 Point to the Server Availability tab.
Result: The Server Availability tab is displayed.
3 In the When Connected with a Server box, the following settings can be made.
Set the Enabled check box to let the ROSA NMS system check if the
connected servers are reachable.
In the Frequency box, enter the check frequency (in seconds).
In the Timeout box, enter the time-out period (in seconds).
A server can be unreachable during that period before a Server not reachable
alarm is generated.
4 In the When Server is in Listening Mode box, adapt the following settings.
Set the Enabled check box to let the ROSA NMS system check if the
connected servers, which operates in listening mode, are reachable.
4014778 Rev H 161

In the Frequency box, enter the check frequency (in minutes).

Do not make this frequency too high to avoid unnecessary high number of
connections.
In the Timeout box, enter the time-out period (in seconds).
A server can be unreachable during that period before a Server not reachable
alarm is generated.
5 Click on the OK command button to confirm or the Reload command button to
162 4014778 Rev H

Using Active or Passive FTP
Using Active or Passive FTP

Introduction
For certain purposes the ROSA NMS Client system communicates with the server
using the File Transfer Protocol (FTP). Therefore ROSA NMS uses Active FTP by
default. In firewall environments it can be useful to use Passive FTP.
Setting Active or Passive FTP

The following procedure describes how to set Active or Passive FTP.
1 In the ROSA NMS user interface, point to Preferences in the File menu.
2 Click on the Advanced tab.
Result: The Advanced tab page is displayed.
3 In the Settings box, set the Use Passive FTP (for firewall compatibility) check
box to use Passive FTP or clear this check box to use Active PFT.
4 Press the OK command button to confirm or Cancel command button to abort
the operation.
4014778 Rev H 163

9 Chapter 9
Working with Services and
Channels
Introduction
This chapter describes how to create and to manipulate TV Services,
TV Channels, and Analog Satellite Channels which are required to
configure particular ROSA NMS tasks.
Notes:
ROSA NMS Device Configuration Shell doesn't support TV
Services, TV Channels, and Analog Satellite Channels.
Working with the Digital Cable RF Channels, Digital Satellite
Channels, Digital Terrestrial Channels, and Digital Baseband
Channels is described in the Headend Model Component Driver
for ROSA NMS - User's Guide.
In This Chapter
Using TV Services ............................................................................... 166
Using Analog TV Channels............................................................... 175
Using Analog Satellite Channels ...................................................... 183
4014778 Rev H 165

Chapter 9 Working with Services and Channels
Using TV Services
Introduction
TV Services define the incoming analog programs processed in a headend. TV
Services are required to configure tasks like the Receiver-Modulator Backup Task.
TV Services can be dragged into a map for convenient creation of relations. For
details about creating relations, please refer to Working with Relations on page 331.
Note: Before TV Services can be added to a ROSA NMS system, the TV Service
driver (Analog TV Service Service.rsd) must be installed. For more information
about installing drivers, please refer to topic Installing Drivers on page 68.
Adding TV Services
Perform the following steps to add a TV Service to the ROSA NMS system.
the server for which TV Services must be added.
2 In the Config menu, point to Services and select TV Services.
Result: The TV Services dialog is displayed.
Tip: The TV Services dialog can also be opened by right-clicking on the TV

Services node in the Server Explorer tree and pointing to Properties in the
short-cut menu.
3 Press the Add... command button.
166 4014778 Rev H

Using TV Services
Result: The Add TV Service dialog is displayed.
4 In the Name box, enter the service name.

5 Point to the ... command button at the right hand side of the Location box.
6 In the Locations list box, select a location and press the Select command button.
Result: The Location dialog closes and the location is added to the Locations box
on the Add TV Service dialog.
7 Continue adding services and click on the Close command button when
finished.
Result: The services appear in the list and under the TV Services node in the
4014778 Rev H 167

Editing a TV Service
The following procedure explains how to edit a TV Service.
1 In the Server Explorer tree of the ROSA NMS system, right-click on the TV
Service node and point to Properties in the short-cut menu.
2 In the list box, select the TV Service that must be adapted and point to the Edit...
command button.
Tip: When there are a lot of services in the list box, it can be difficult to find a
particular service. Therefore a filter can be configured to reduce the number of
services in the list box. More information concerning the filter can be found in
topic Configuring the Filter on page 173.
Result: The Edit TV Service dialog is displayed.
3 Change the name of the service in the Name box.

4 Change the location in the Location dialog after pressing the ... command button.
5 Press the Update command button to confirm and the Close command button to
close the dialog.
Assigning Priorities to TV Services

Assigning priorities to the TV Services allows the Backup tasks to backup the high
priority services in favor of low priority services if a limited number of backup
modulators or receivers is available.
Perform the following steps to define the service priorities.
the server for which priorities must be assigned to TV Services.
2 In the Config menu, click on Services and select Priorities.
168 4014778 Rev H

Using TV Services
Result: The Service Priorities dialog is displayed.
3 Double-click on the service or just select it and start typing the priority number.
Result: The Set Priority dialog is displayed.
4 In the Priority box, enter the priority for this service.

Priority 0 means that the service will not be backed up when it fails. 1 is the
highest priority, 100 the lowest priority. If the system only provides backup for
one service, and another service fails too, only the highest priority service will be
backed up.
5 Click on the OK command button to set the priority or the Cancel command
Result: After pressing the OK command button, the service priority is changed.
A tick mark and Yes in the Backup column indicates that backup for this service
is enabled.

4014778 Rev H 169

Removing TV Services
Perform the following procedure to remove a TV Service.
WARNING:
The TV Service(s) is (are) removed immediately, including all relations between
the service(s) and devices. Tasks using a service will no longer function
correctly after removing the service.
2 In the list box, select the TV Service(s) that must be removed. To select
consecutive services in the list box, point to the first service, press and hold down
the [SHIFT] key, and point to the last service. To select non-consecutive
services, press and hold down the [CTRL] key, and click on each service.
Result: The selected services are removed from the list.
Tip: A service can also be removed by right-clicking on the service in the Server
Explorer tree and pointing to Remove in the short-cut menu.
Working with Folders

Introduction
Under the TV Services node in the Server Explorer tree of a server, unit folders can
be created. Folders can be useful to put units together based on type or location, for
example to keep modulators and receivers together in separate folders. In a folder,
units are sorted alphabetically as in the Server Explorer tree itself.
Creating a New Folder

The following procedure explains how to create a new folder.
new folder should be created.
2 Right-click on the TV Services node and point to New folder... in the short-cut
menu.
170 4014778 Rev H

Using TV Services
4 Click on the Create command button to confirm or the Cancel command button
Result: After pressing the Create command button the new folder displays
under the TV Services node in the Server Explorer tree. Units can be moved to
this folder as described in topic Moving TV Services to a Folder on page 171.
Creating Nested Folders

Perform the following steps to create a folder in a folder (nested folders).
1 In the Server Explorer of the ROSA NMS system, right-click on the folder in
which a new folder must be created and select New Folder... in the short-cut
menu.

3 Press the Create command button to confirm or the Cancel command button to
Result: After pressing the Create command button, the new folder is added to
the selected folder. Units can be moved to this folder as described in topic
Moving TV Services to a Folder on page 171.
Tip: Nested folders can also be created by dragging and dropping a folder into
another folder. Moving a nested folder to another folder or to the units node can be
done by such drag and drop action.
Moving TV Services to a Folder

The following procedure explains how to move TV services to a folder.
1 In the Server Explorer of the ROSA NMS system, browse to the TV service that
must be moved.
2 Drag and drop this TV service to the destination folder.
4014778 Rev H 171

Renaming a Folder
Perform the following steps to rename a folder.
must be renamed and select Rename... in the short-cut menu.
Result: The Rename Folder dialog is displayed.
2 In the Name box, enter the new name for the selected folder.
3 Press the Rename command button to rename the folder or the Cancel command
Removing a Folder
The following procedure describes how to remove a folder.
must be deleted and select Remove in the short-cut menu.
Result: The following confirmation box is displayed.
2 Press the Yes command button to remove the folder or the No command button
Result: After pressing the Yes command button, the folder is removed and the
services member of this folder are moved to the TV Services node or to the
folder the removed folder was part of (nested folders).
Printing a List of TV Services

The following procedure explains how to print a list with TV Services.
the server for which TV Services must be printed.
2 In the Config menu, point to Services and select the TV Services menu item.
172 4014778 Rev H

Using TV Services
3 In the list box of the TV Services dialog, select the service(s) that must be
printed. To select consecutive services in the list box, click on the first service,
press and hold down the [SHIFT] key, and click on the last service. To select
non-consecutive services, press and hold down the [CTRL] key, and point to
each service.
Tip: When there are a lot of services in the list box, it can be difficult to find a
particular service. Therefore a filter can be configured to reduce the number of
services in the list box. More information concerning the filter can be found in

selected services or the All selection button to print all services.
on page 44.
Configuring the Filter

When there are too many services in the list box of the TV Services dialog, a filter
can be configured to filter these services. The following procedure explains how to
configure the services filter for the TV Services dialog.
4014778 Rev H 173

2 Press the Filter command button in the upper right corner of the dialog.
3 In the 1) On/Off box, tick the Filtering ON check box.

4 In the 2) Columns list box, select one or more filters to build the filter. To select
7 In the 4) Methods selection box, select the filter method.
one or more values
8 Repeat step 6 and 7 for each column selected in the 2) Columns list box.
Note: As long as the OK button is not pressed, the previous filter can be restored by
pressing the Restore previous... command button.
174 4014778 Rev H

Using Analog TV Channels

Introduction
Analog TV Channels are required to configure tasks like the Receiver-Modulator
Backup Task and the Auto-Leveling Task. The Analog TV Channels are linked to
modulators and measuring devices via relations. For more details about relations,
please refer to chapter Working with Relations on page 331.
Note: Before Analog TV Channels can be added, the Analog TV Channel driver
(Analog TV Channel Service.rsd) must be installed. For more information about
installing drivers, please refer to topic Installing Drivers on page 68.
Adding Analog TV Channels

Perform the following steps to add an Analog TV Channel to the ROSA NMS
system.
1 In the Server Explorer tree of the ROSA NMS system, expand the Channels
node.
2 Right-click on Analog TV Channels and point to Properties in the short-cut
menu.
Result: The Analog TV Channels dialog is displayed.
Tip: The Analog TV Channels dialog can also be opened by pointing to

Channels in the Config menu and clicking on the Analog TV... menu item.
3 Click on the Add command button to define a new channel.
4014778 Rev H 175

Result: The Add Analog TV Channel dialog is displayed.
4 In the ChannelID box, type the channel identification name.

5 In the Frequency box, type the channel frequency expressed in MHz.
6 Click on the command button next to the Location box.
7 Double-click on a location in the Location tree or select it and then click on the
OK command button.
Result: The name of the selected location is displayed in the Locations box.
8 In the Transmission Standard drop down box, select BG, DK, I, MN, or L.
9 In the Color System drop down box, select NTSC, PAL, or SECAM.
10 In the Audio System drop down box, select MONO, STEREO, NICAM, BTSC,
DUAL, or BTSC+SAP.
11 In the Scrambling Type drop down box, select None, SA, GI, Zenith, Videocipher,
Digicipher, or B-Mac.
176 4014778 Rev H

Specifying a Scrambling Type is required for mixed scrambled and

non-scrambled backup situations. This information will be used to turn on the
backup scrambler if a scrambled service requires backup.
12 In the RF Level Correction box, enter a positive or a negative value in dB.
By default, the RF Level Correction is set to 0 dB, but for each channel, an offset
to the RF level can be added specified by the Region RF Level and Region Tilt
attributes that belongs to the selected location for this channel. The resulting RF
level is the target level used by the Autolevelling Task.
14 Continue adding channels and then click on the Close command button.
Result: The added channels appear in the list and are displayed in the Analog
TV Channels node in the Server Explorer tree.
Editing an Analog TV Channel

The following procedure describes how to adapt parameters of an Analog TV
Channel.
1 In the Server Explorer tree of the ROSA NMS system, expand the Channels
node.
2 Right-click on Analog TV Channels and point to Properties in the short-cut
menu.
3 In list box, select the channel that should be adapted and point to the Edit...
command button.
Tip: When there are a lot of channels in the list box, it can be difficult to find a
particular channel. Therefore a filter can be configured to reduce the number of
channels in the list box. More information concerning the filter can be found in
4014778 Rev H 177

Result: The Edit Channel dialog of the selected channel is displayed.
4 Modify the channel parameters and click on the Update command button.
Result: The Update command button becomes an Add command button to add
new channels. The dialog can be closed by clicking on the Close command
button.
Loading Channels from Modulators

The following procedure describes how to retrieve channel information from
non-agile Pulsar modulators connected to the server.
1 In the Server Explorer tree of the ROSA NMS system, right-click on the Analog
TV Channels node and point to Properties in the short-cut menu.
2 Press the Load from Modulators... command button.
Result: The frequency and transmission standard is retrieved from the
modulators and stored into new channels. These new channels can be edited to
add additional channel information. For more information about editing
channels, please refer to topic Editing an Analog TV Channel on page 177.
Storing Channels into Monitoring Devices

Storing channels into monitoring devices like the FSM 860 or the LM 860 is an easy
way of providing these devices with the frequencies they need to measure the
channels automatically.
The following procedure explains how to store channels into monitoring devices.
178 4014778 Rev H

2 In the list box of the Analog TV Channels dialog, select the channel(s) that must
be stored. To select consecutive channels in the list box, click on the first
channel, press and hold down the [SHIFT] key, and click on the last channel. To
select non-consecutive channels, press and hold down the [CTRL] key, and point
to each channel.
3 Press the Store to Monitoring Devices command button.
Result: The Store selected channels to monitoring device(s) dialog is displayed.
4 In the Monitoring devices list, select the devices in which the selected channels
must be stored.
5 In the Start on preset nr. box, type a preset number.
6 Click on the Store... command button to confirm or the Cancel command button
Printing a List of Analog TV Channels

The following procedure explains how to print a list with Analog TV Channels.
2 In the list box of the Analog TV Channels dialog, select the channel(s) that must
be printed. To select consecutive channels in the list box, click on the first
to each channel.
4014778 Rev H 179



selected channels or the All selection button to print all channels.
on page 44.
Removing Analog TV Channels

Perform the following procedure to remove an Analog TV Channel.
WARNING:
The Analog TV Channel(s) is (are) removed immediately, including all relations
between the channel(s) and devices. Tasks using a channel will no longer
function correctly after removing the channel.
2 In the list box, select the Analog TV Channel(s) that must be removed. To select
consecutive channels in the list box, point to the first channel, press and hold
down the [SHIFT] key, and point to the last channel. To select non-consecutive
channels, press and hold down the [CTRL] key, and click on each channel.
180 4014778 Rev H

Result: The selected channels are removed from the list.
Note: A channel can also be removed by right-clicking on the channel in the Server

When there are too many channels in the list box of the Analog TV Channels dialog,
a filter can be configured to filter these channels. The following procedure explains
how to configure the channels filter for the Analog TV Channels dialog.

4014778 Rev H 181

one or more values
182 4014778 Rev H

Using Analog Satellite Channels

Introduction
Tasks like the Dish Backup task and the Receiver Backup task require satellite
channel information to configure a backup dish or to tune a backup satellite receiver
to replace defective devices. This information is stored in the Analog Satellite
Channels.
Note: Before Analog Satellite Channels can be added, the Analog Satellite Channel
driver (Satellite Channel Service.rsd) must be installed. For more information about
installing drivers, please refer to topic Installing Drivers on page 68.
Adding Analog Satellite Channels

Before Analog Satellite Channels can be added to a ROSA NMS system, satellite data
must be defined. The following procedure describes how to add satellite data.
the server for which Analog Satellite Services must be added.
2 In the Config menu, click on Units.
4014778 Rev H 183

Result: The Add Unit dialog is displayed.
4 In the Name box, type the name of the satellite.

5 Click on the command button next to the Location box.
6 Double-click on a location in the Location tree or select it and then click on the
OK command button.
Result: The name of the selected location is displayed in the Locations box.
7 In the Device Driver drop down box, select 'Satellite'.
8 Add all required satellites, and then click on the Close command button.
Perform the following steps to add Analog Satellite Channels.
1 In the Config menu, point to Channels and then click on the Analog Satellite...
menu item.
184 4014778 Rev H

Result: The Analog Satellite Channels dialog is displayed.
Tip: The Analog Satellite Channels dialog can also be opened by pointing to
Channels in the Config menu and clicking on the Analog Satellite... menu item.
2 Press the Add command button.
Result: The Add Analog Satellite Channel dialog is displayed.
3 Specify the following parameters: Name, Transponder, Extension, Frequency,

Bandwidth, Location, Satellite, Polarity, Video De-emphasis, Video
Modulation, and Scrambling Type.
4014778 Rev H 185


5 Right-click on the Audio Subcarriers list box and then click on Add in the
short-cut menu to add one ore more audio subcarriers to this satellite channel.
Result: The Add Audio Subcarrier dialog is displayed.
6 Specify the following parameters: Name, Frequency, and Audio De-emphasis.

8 Repeat steps 6 and 7 for each subcarrier you want to add.
9 Click on the Close command button when all subcarriers are added.
Result: The subcarriers are stored in the channel, and the channel itself is added
to the list. The Add Analog Satellite Channel dialog is emptied. Now other
channels can be added.
10 Click on the Close command button in the Add Satellite Channels dialog when
all channels are added.
Editing Analog Satellite Channels

The following procedure describes how to edit an Analog Satellite Channel.
the server for which an Analog Satellite channels must be changed.
menu item.
3 In the list box, select the channel that should be changed and point to the Edit...
command button.
186 4014778 Rev H

Result: The Edit Analog Satellite Channel is displayed.
4 Modify the channel parameters and click on the Update command button.
Result: The Update command button becomes an Add command button to add
new channels. The dialog can be closed by clicking on the Close command
button.
Storing Analog Satellite Channels to Satellite Receivers

Once Analog Satellite Channels are created, these channels can be stored to the
presets in SAT 200 Satellite Receivers as follows.
the server for which Analog Satellite channels must be stored to satellite
receivers.
menu item.
3 In the list box, select the channels that should be stored. To select consecutive
channels in the list box, point to the first channel, press and hold down the
[SHIFT] key, and point to the last channel. To select non-consecutive channels,
press and hold down the [CTRL] key, and click on each channel.
4 Press the Store To Sat Receivers command button.
4014778 Rev H 187

Result: The Store selected channels to sat receiver(s) dialog is displayed.
5 In the Receivers list box, select the receivers to which the channels must be
stored.
Note: Before storing channels to a satellite receiver, the old channel list in the
receiver can be cleaned by pressing the Clean command button.
6 Press the Store command button.
Result: After successfully storing the channels, a message box is displayed.
7 Press the OK command button to close the message box and the Cancel
command button to close the Store selected channels to sat receiver(s) dialog.
Printing a List of Analog Satellite Channels

The following procedure explains how to print a list with satellite channels.
Satellite Channels node and point to Properties in the short-cut menu.
2 In the list box of the Analog Satellite Channels dialog, select the channel(s) that
must be printed. To select consecutive channels in the list box, click on the first
to each channel.
satellite channels in the list box. More information concerning the filter can be
found in topic Configuring the Filter on page 190.
188 4014778 Rev H


selected channels or the All selection button to print all channels.
Note: The font size can be defined in the View Option dialog. More information
concerning this dialog can be found in topic Changing View Options on page 44.
Removing Analog Satellite Channels

Perform the following procedure to remove an Analog Satellite Channel.
WARNING:
The Analog Satellite Channel(s) is (are) removed immediately, including all
relations between the channel(s) and devices. Tasks using a channel will no
longer function correctly after removing the channel.
2 In the list box, select the Analog Satellite Channel(s) that must be removed. To
select consecutive channels in the list box, point to the first channel, press and
hold down the [SHIFT] key, and point to the last channel. To select
non-consecutive channels, press and hold down the [CTRL] key, and click on
each channel.
4014778 Rev H 189

Result: The selected channels are removed from the list.
Note: A channel can also be removed by right-clicking on the channel in the Server

When there are too many channels in the list box of the Analog Satellite Channels
dialog, a filter can be configured to filter these channels. The following procedure
explains how to configure the channels filter for the Analog Satellite Channels
dialog.

190 4014778 Rev H

one or more values
4014778 Rev H 191

10 Chapter 10
Working with Attributes and
Locations
Introduction
This chapter describes how to use attributes and locations.
In This Chapter
Using Attributes.................................................................................. 194
Using Locations................................................................................... 197
4014778 Rev H 193

Chapter 10 Working with Attributes and Locations
Using Attributes
Introduction
Numerical as well as alphanumerical attributes can be created and assigned to
locations. A value can be given to an attributed assigned to a location. For more
information concerning locations and assigning attributes to locations, please refer to
topic Using Locations on page 197.
Example: When locations represent headends, attributes can be created for the
number of subscribers for those headends. The attributes can be assigned to each of
the headend locations and the value of the attributes can be filled in with the number
of subscribes.
Note: The attribute described above is an example of a user-defined attribute. The
ROSA NMS system itself can add attributes as well. These are system-defined
attributes and depend on the installed drivers. For example, when installing the
Autolevelling Task, four additional attributes become available: Region RF Level,
Region Tilt, Digital RF Level and Digital Tilt. These attributes can be assigned to
each location that contains monitoring devices controlled by the Autolevelling Task.
Adding Attributes
The following procedure explains how to add a user-defined attribute.
the server for which an attribute should be added.
2 In the Server menu, point to Attributes... or click on the Attributes button in the
Server Tools tool bar.
Result: The Attributes dialog is displayed.
194 4014778 Rev H

Using Attributes
Tip: The Attributes dialog can also be opened by clicking on the Attributes
Properties... command button on the Attributes of: <selected location name>
dialog. More information concerning this dialog can be found in topic Changing
an Attribute value on page 199.
3 Click on the Add... command button.
Result: The New Attribute command button is displayed.
4 In the Name box, enter a name for the attribute.

5 In the Description box, enter a description for the attribute.
6 Tick the Numeric check box if the attribute will contain a numeric value.
Result: After pressing the OK command button, the new created attribute
appears in the list box of the Attributes dialog.
8 The Attributes dialog can be closed by pressing the Close command button.
Editing Attributes
Perform the following steps to edit an attribute.
the server for which an attribute should be changed.
2 In the Server menu, point to Attributes....
3 In the list box, select the attribute that must be changed and point to the Edit...
command button.
Result: The Edit Attribute dialog is displayed.
4014778 Rev H 195

4 Adapt the name, description, or numeric setting of the attribute.

Note: An attribute assigned to a location cannot be changed.
Removing Attributes
The following procedure explains how to remove an attribute.
the server for which an attribute should be changed.
2 In the Server menu, point to Attributes....
3 In the list box, select the attribute that must be removed and point to the Remove
command button.
Result: The attribute is removed from the list.
Note: An attribute assigned to a location cannot be removed.
196 4014778 Rev H

Using Locations
Using Locations
Introduction
New units added to the ROSA NMS system can be assigned to a location.
Assigning units to locations is useful when performance graphs compared by
location should be created. The ROSA NMS system also allows creating
hierarchical locations, meaning locations populated with sub locations.
To attach additional information to a location, attributes can be assigned. Attributes
are also required when using the Autolevelling Task that uses the Region RF level
and Region Tilt information stored in the attributes. For more information about
creating attributes, please refer to topic Using Attributes on page 194.
Each server has one default location that cannot be removed. The name of this
location is Copernicus At Copernicus computer name in case of a Copernicus server and
SI-Server At SI-Server computer name in case of a SI-Server.
Adding a Location
The following procedure describes how to add a location to a ROSA NMS system.
the server for which a new location must be added.
2 In the Server menu, point to Locations....
4014778 Rev H 197

Tip: The Locations dialog can also be opened by clicking on the Locations
button in the Server Tools tool bar.
3 Select the Locations root to create a new top-level location or select a location to
create a sub location under the selected location and point to the Add command
button.
Result: The Add Location dialog is displayed.
Note: The Parent Location box shows the location under which the new location
will be created. If the new location is added under the Locations root, the
parent location is <None>.
4 In the Name box, enter the name for the new location.
Result: After pressing the OK command button the new location is added to the
Locations tree.
6 The Locations dialog can be closed by pressing the Close command button.
Assigning Attributes to a Location

Perform the following steps to assign attributes to a location.
the server for which a location must be assigned with attributes.
3 In the Locations tree, select the location and point to the Attributes... command
button.
198 4014778 Rev H

Using Locations
Result: The Attributes of: <selected location name> dialog displays.
4 In the Available Attributes list box, select an attribute and point to the <--
command button.
Result: The New Value for Attribute dialog is displayed.
Tip: The New Value for Attribute dialog can also be opened by double-clicking
on the attribute.
Note: In case of system-defined attributes, different dialogs can be displayed.
For details, please refer to the user's guide of the corresponding driver.
5 In the Enter a value for the attribute box, enter a value.
7 Both the Locations and the Attributes of: <selected location name> dialog can
be closed by pressing the Close command buttons.
Changing an Attribute value

Perform the following steps to change the value of an attribute.
the server for which a value of an attribute assigned to location must be changed.
4014778 Rev H 199

button.
4 Select the attribute in the left hand list box and point to the Edit command
button.
Result: The Edit Value of Attribute dialog is displayed.
Tip: The Edit Value of Attribute dialog can also be opened by double-clicking
on the attribute.
5 Enter the new value and point to the OK command button to confirm or the
6 Both the Locations and the Attributes of: <selected location name> dialog can
be closed by pressing the Close command buttons.
Removing Attributes from a Location

The following procedure explains how to remove an attribute from a location.
the server for which attributes should be removed from locations.
button.
4 Select the attribute in the left hand list box and point to the Remove command
button.
5 Point to the Close command button to close the Attributes of: <selected location
name> dialog.
Renaming a Location
The following steps explain how to change the name of a location.
the server for which a location must be renamed.
200 4014778 Rev H

Using Locations
3 Point to the Edit... command button.

Result: The Edit Location dialog is displayed.
4 In the Name box, enter a new name for the location.

Removing a Location
Perform the following steps to remove a location from the Locations tree.
the server for which a location must be removed.
3 In the Locations tree, select the location that must be removed and point to the
Remove command button.
Note: A location can only be removed if no resources are linked to the location.
When a location is removed to which a resource is linked, the following message
box is displayed.
To change the location of a resource, please refer to topic Unit Settings on page
106.
4014778 Rev H 201

11 Chapter 11
Working with Messages
Introduction
This chapter provides more information concerning message handling
using a ROSA NMS system.
Note: A ROSA NMS Device Configuration Shell system does not
support messages.
In This Chapter
Introducing .......................................................................................... 204
Viewing Messages .............................................................................. 207
Basic Message Operations ................................................................. 223
Logging Manual Created Messages ................................................. 232
Changing Message Rules................................................................... 234
Configuring the Message Options.................................................... 237
Working with the Listening Console ............................................... 241
Alarm Correlation Domains.............................................................. 248
Maintaining the Message Database.................................................. 254
4014778 Rev H 203

Chapter 11 Working with Messages
Introducing
ROSA NMS Message Database
Messages received by a Copernicus server, SI-Server, or ROSA NMS Single User
system are stored in the ROSA NMS Message Database of the system. The ROSA
NMS system is provided with a number of functions to facilitate the maintenance of
this database. These maintenance functions are described in topic Maintaining the
Message Database on page 254.
Message Viewer
The messages in the ROSA NMS Message Databases can be visualized using the
Message Viewer of the ROSA NMS system. The Message Viewer window can be
opened for a single resource, a group of resources, a folder with resources, all
resources connected to a server...
The following picture shows a Message Viewer window.
For more information concerning the Message Viewer, please refer to topic Viewing
Message Notification
Incoming messages can be reported using a New Message Received pop-up and/or
a sound. This feature can be enabled and disabled via the Message Options dialog
and is default enabled. For more information concerning the Message Options
dialog, please refer to topic Configuring the Message Options on page 237.
204 4014778 Rev H

Introducing
The following picture illustrates the New Message Received pop-up.
The New Message Received pop-up also represents the severity level of the receive
message.
Note: Pressing the OK command button on the New Message Received pop-up
closes the pop-up.
Messages in the Status Bar

The Status bar at the bottom of the ROSA NMS user interface displays the most
resent message and the status of the pending message with the highest severity.
Right arrow
button
Left arrow Message
button button
Current Pending Current Current Map zoom

message status user server percentage
The Left Arrow button and the Right Arrow button can be used to scroll through the
messages. The Message button can be used to open the Message Information
dialog containing additional information about the selected message.
Message Types
Messages in the ROSA NMS Message Database are categorized using the following
groups:
Communication: A typical communication message is a measurement report.
Quality: the message relates to the quality of a service, for example a RF level
alarm.
Processing: the message relates to the processing of a signal, for example an
input loss alarm.
Equipment: the message relates to the condition of a device, for example a
device temperature alarm.
4014778 Rev H 205

Environmental: the message relates to environmental parameters, for example

the User pressed key message.
Indeterminate: no type is specified for the message.
Message Severity
Not all messages that the ROSA NMS system receives indicate severe problems.
Some messages are only informational or provide measurement data from
monitoring equipment. Not all alarms are equally severe. Following levels are
possible:
Indeterminate: no severity level was assigned to the message.
Information: measurement report messages are information messages.
Warning: a warning message indicates a possible problem.
Minor: generated for example when a signal level exceeds a minor threshold.
Major: generated for example when a signal level exceeds a major threshold, or
when it drops away completely, or when a device fails.
Critical: highest severity, for example when a server becomes unreachable
Cleared: generated when the cause of an alarm, for example an input loss, is no
longer there. A Cleared message resets a previously generated pending message.
Pending and Non-Pending Messages

When a message is pending, it means that the reason the message was generated still
exists. For example, as long as the video signal on the input of a modulator does
not return, the Video Loss on Input message of that modulator remains pending.
When the input signal is restored, the modulator sends a cleared message that
renders the previous message non-pending.
Pending messages indicated by the letter u in the icon may have to be cleared
manually, see also Resetting Pending Messages on page 226. Other messages are
generated but never become pending, for example measurement report messages are
non-pending information level communication type messages.
Acknowledging Messages
Acknowledging messages allows you to keep track of messages you already
handled. In large systems, it can reduce the number of messages displayed in the
Message Viewer window. The procedure to acknowledge messages can be found
in topic Acknowledging Messages on page 223.
206 4014778 Rev H

Viewing Messages
Viewing Messages
Introduction
Various resources such as units and tasks generate messages. These messages can
be checked by opening one or more Message Viewer windows. Messages can be
shown for a server, all resources of a server, a unit folder, a unit group, or a single
resource.
Working with the Message Viewer

About the Message Viewer Window
The Message Viewer window of the ROSA NMS system is provided with several
components. The illustration below shows these components.
The components of the Message Viewer window are:

Message Viewer toolbar
Message list
Details pane
4014778 Rev H 207

Note: The Details pane of the Message Viewer window is default hidden. The
procedure to make this pane visible is described in topic Viewing the Message Details
on page 214.
About the Message Viewer Icons

The table below describes the icons used on the Message Viewer window.
Icon Description
Pending message that must be reset by a ROSA NMS operator
(white) Pending message with Information severity
(blue) Pending message with Warning severity
(yellow) Pending message with Minor severity
(red) Pending message with Major severity
(pink) Pending message with Critical or Indeterminate severity
Message with attachment
Message that is acknowledged
Detail of a message
Note: The color corresponding the alarm severity level is adjustable. The colors
shown in the table are the default colors used by the ROSA NMS system. The
page 44.
About the Message Viewer Toolbar

The Message Viewer window is provided with a toolbar, called Message Viewer
toolbar, that gives quick access to commonly used commands on the window. The
table below describes the buttons on this toolbar.

Acknowledge Acknowledges the selected message(s)
Message
Acknowledge with Acknowledges the selected message and add an
Attachment attachment to this message
View Attachment Opens the attachment of the selected message
Reset Pending Resets pending level of the selected message(s)
Delete Non Pending Deletes the selected non-pending messages
Acknowledge All Acknowledges all messages in the Message Explorer

Messages window
Reset All Pending Resets all pending messages in the Message Explorer
window
208 4014778 Rev H

Viewing Messages

Delete All Non Deletes all non-pending messages in the Message Explorer
Pending window
Logon To Resource Logs on to the resource to which the message belongs
Toggle Detail Toggles between displaying and hiding he Detail pane of

the Message Viewer window
The toolbar on the Message Viewer window can be made visible and hidden. The
following steps explain how to hide or display the Message Viewer toolbar.
1 Right-click on the Message Viewer window and set Toolbar in the short cut
menu to display the toolbar or clear Toolbar to hide the toolbar.
Viewing Messages
The following procedure explains how to open the Message Viewer for specific
resources.
right-click on the resource(s) of which messages should be checked.
To view messages...
for all resources of the server, right-click on the server in the Server Explorer
or Group Explorer tree.
Note: Do not right-click on the Copernicus server or SI-Server node itself.
for a single resource, right-click on the resource in the Server Explorer or
Group Explorer tree.
4014778 Rev H 209

for all units in a folder, right-click on the folder in the Server Explorer tree.
for all units in a group, right-click on the group in the Group Explorer tree.
related to the server itself, right-click on the Copernicus server or SI-Server
resource under Units in the Server Explorer tree.
2 In the short-cut menu, select one of the following message categories:
Or point to the View Messages using default filter, All Messages, Not Acknowledged
Messages, or Pending Messages in the Servers Tools tool bar.
Default Filter: displays only those messages that are specified in the message
filter. For more information concerning filter settings, please refer to
Configuring the Message Filter on page 215.
All Messages: displays all messages
Not Acknowledged: displays only those messages that are not yet
acknowledged
Pending: displays only the messages that are still pending
Result: The Messages Viewer dialog containing the messages of the selected
resource(s) is displayed.
Note: Once the Message Viewer window is opened, the message category can be
changed by right-clicking the window, pointing to Show in the short-cut menu
and selecting the desired category.
The following information is available on the Message Viewer.
Generation Time: the date and time the message was generated by the resource.
This time comes from the internal device clock, if available.
Msg Info: the message text
210 4014778 Rev H

Viewing Messages
Count: when the same message is detected more than once within a certain time
interval and the Suppress Repetitive Alarms rule is enabled, the message is logged
only once but with a count > 1. This interval, called Repetitive Alarm
Suppression interval, can be set in the Message Options dialog. More
information concerning the Message Options dialog can be found in topic
Configuring the Message Options on page 237 and about the Suppress Repetitive
Alarms rule in topic Changing Message Rules on page 234.
Source Name: the name of the resource that produced the message.
Msg Type: the type of message.
Msg Level: the message severity level
Msg Subject: the message subject (for example the program an RF message was
produced for).
Registration Time: the date and time the message was stored in the message
database by the server.
Ack Source: the name of the resource that acknowledged the message.
Ack Time: the acknowledge date and time, shown only when the message is
acknowledged.
Source Location: the location of the resource that produced the message.
Source Type: The type of the resource that produced the message.
Note: Not all information is displayed by default. For more details concerning
hiding or displaying information, please refer to topic Changing the Message Viewer
Layout on page 212.
Viewing Additional Message Information

Additional information about a message can be viewed on the Message Information
dialog. The procedure below describes how to open the Message Information
dialog for a particular message.
right-click on the resource of which additional message information must be
checked and point to Default Filter, All Messages, Not Acknowledged, or
Pending in the short-cut menu.
Result: The Message Viewer is displayed with the messages of the selected
resource.
2 In the Message Viewer window, double-click on the message of which
additional information should be checked.
4014778 Rev H 211

Result: The Message Information dialog with the additional information of the
selected message is displayed.
Notes:
The Message Dialog is default volatile, meaning the dialog disappears as
soon as you click somewhere else on the screen. To keep the dialog
displayed (non-volatile), click on the pushpin command button in the upper
left corner of the dialog. The dialog remains displayed and changes when a
new message is received, or when another message is selected in the
Message Viewer dialog.
The Message Dialog can also be opened by pressing the information

command button on the Status bar at the bottom of the ROSA NMS GUI.
When the Message Information dialog is non-volatile, you can scroll
through the messages by pressing the arrow buttons, which are also located
on the Status bar.
Changing the Message Viewer Layout

Perform the following steps to change the layout of the Message Viewer window.
right-click on a resource and point to Default Filter, All Messages, Not
Acknowledged, or Pending in the short-cut menu.
Result: The Message Viewer window is displayed.
2 Right-click in the Message Viewer window and point to Layout... in the
short-cut menu.
212 4014778 Rev H

Viewing Messages
Result: The Message Viewer Layout dialog is displayed.
3 To hide parameter(s), select the parameter(s) in the Visible (in this order) list
box. To select consecutive parameters, select the first parameter, press and hold
down the [SHIFT] key, and press the last parameter. To select parameters that
are not consecutive, press and hold down the [CTRL] key, and point to each
parameter.
After selecting the parameter(s), point to the Hide > command button.
Result: The selected parameter(s) is (are) moved to the Hidden list box.
Note: A parameter can also be hidden by double-clicking on the parameter in the
Visible (in this order) list box.
4 To make parameter(s) visible, select the parameter(s) in the Hidden list box. To
select consecutive parameters, select the first parameter, press and hold down
the [SHIFT] key, and press the last parameter. To select parameters that are not
consecutive, press and hold down the [CTRL] key, and point to each parameter.
After selecting the parameter(s), point to the Show < command button.
Result: The selected parameter(s) is (are) moved to the Visible (in this order) list
box. The parameter(s) is (are) added at the bottom of the list box, meaning this
(these) parameters will be displayed as the right most column(s) in the Message
Viewer window.
Note: A parameter can also be made visible by double-clicking on the parameter
in the Hidden list box.
4014778 Rev H 213

5 To change the column order of the parameters, select the parameter(s) and point
to the Shift Up or Shift Down command button. Consecutive parameters can be
selected by pointing the first parameter, pressing and holding down the [SHIFT]
key, pointing to the last parameter, and pressing the corresponding command
button.
6 In the Options box, set or clear the following check boxes:
Show Toolbar: select this check box if you always want to display the
Message Viewer Toolbar, see also About the Message Viewer Toolbar.
Show Details: select this check box if you always want to display the Details
pane.
Auto Popup Attachment: when selected, the Message Attachment dialog
displays when selecting a message with an attachment, see also Working with
Message Attachments on page 225.
Jump to incoming message: the Message Viewer is constantly updated.
Select this check box if you want to jump to an incoming message
automatically.
Colour Full Line: if this option is selected, an additional visual indication is
added. The complete line of the pending message is colored.
7 Point to the Make Default command button to make this layout the default
layout. This layout is applied to all Message Viewer windows that will be
opened.
Viewing the Message Details

Some messages provide additional information that does not fit into the normal
Message Viewer window. To view these message details, the Message Viewer
details pane must be displayed. Perform the following steps to display the
Message Viewer details pane.
right-click on the resource of which messages must be displayed and point to
Default Filter, All Messages, Not Acknowledged, or Pending in the short-cut
menu.
2 Right-click on the Message Viewer window and set Detail in the short-cut
menu.
214 4014778 Rev H

Viewing Messages
Result: The detail pane of the Message Viewer window is displayed.
Selecting the message in the Message Viewer window displays the message
details in the details pane.
Notes:
The details pane of the Message Viewer window can be resized by pressing
and holding down the [SHIFT] key and dragging the bottom of the window.
The details pane of the Message Viewer window can be hidden by clearing
Detail item in the short-cut menu after right-clicking on the Message Viewer
window.
Using Message Filters

Introduction
When a ROSA NMS system has to manage a lot of devices, the number of messages
logged by the ROSA NMS system can be huge. To facilitate message processing,
the messages can be filtered by using message filtering. The following topic
describes how to use the message filtering of ROSA NMS.
When multiple message filters are required, predefined message filters can be
configured. These filters can then be selected when needed. The procedures to use
predefined message filters can be found in topic Using Predefined Message Filters on
page 218.
Important: Predefined message filters can only be added, modified, or removed if
you have the rights to do this. By default, these actions can only be done when you
are logged on with an account belonging to the Administrator security group. The
procedure to modify these rights can be found in chapter ROSA NMS System Security
on page 353.
4014778 Rev H 215

Filtering Messages
The following procedure explains how to filter messages.
right-click on a resource and point to Default Filter, All Messages, Not
Result: The Message Viewer window containing the messages of the selected
resource is displayed.
2 Right-click in the Message Viewer window and point to Filter... in the short-cut
menu.
Result: The Message Filter dialog is displayed.
3 In the Type box, set or clear the message type check boxes.
4 In the Level box, set or clear the severity level check boxes.
5 In the Pending selection box, select one of the following selection buttons:
Show All: the pending as well as the not pending message will be displayed.
Show Pending: only the pending messages will be displayed.
Show not Pending: only the not pending messages will be displayed.
6 In the Acknowledged selection box, select one of the following selection buttons:
Show All: the messages that are acknowledged as well as the messages that
are not yet acknowledged are displayed.
Show Acknowledged: only the messages, which are acknowledged, are
displayed.
216 4014778 Rev H

Viewing Messages
Show not Ack: Only the messages, which are not yet acknowledged, are
displayed.
Note: The procedure to acknowledge a message can be found in topic
Acknowledging Messages on page 223.
7 Select the No date/time filtering, Last, or Range selection button.
- No date/time filtering: no time filtering will be performed.
- Last: only the messages within a particular time window will be displayed.
Select the unit of time (seconds, minutes, hours, days, months, years) in the
Last drop down box and duration in the Last box.
- Range: only the messages between two dates will be displayed.
In the From and To box, select the time and date.
8 In the Show box under the Message Info box, enter the string that the message
info must contain to display the message.
9 In the Don't Show box under the Message Info box, enter the string that the
message info must contain to hide the message.
10 In the Show box under the Message Subject box, enter the string that the
message subject must contain to display the message.
11 In the Don't Show box under the Message Subject box, enter the string that the
message subject must contain to hide the message.
Note: In the Show and Don't Show boxes wildcard characters are allowed. Use
the asterisk character (*) as a substitute for zero or more characters and the
question mark as a substitute for a single character in the message info.
Tips:
Click on the Make Default command button to make the filter the default
filter.
Result: After pressing the Make Default command button, the following
message box is displayed.
Point to the OK command button to close this message box.

Result: Each time the Message Viewer is opened via default filter, this filter
definition will be used.
Click on the Save... command button to make the filter a predefined filter.
4014778 Rev H 217

Result: After pressing the Save... command button, the Save as Predefined
Message Filter dialog displays.
Enter a name in the Filter Name box and press the OK command button.
Using Predefined Message Filters

Introduction
For filtering messages logged by the ROSA NMS system, predefines message filters
can be configured. The following topics describe how to add, to edit, to select, and
to remove predefined filters.
Adding Predefined Filters

The following steps explain how to add predefined message filters.
the server for which pre-defined message filters must be configured.
2 In the Messages menu, point to Predefined Message Filters...
218 4014778 Rev H

Viewing Messages
Result: The Predefined Message Filters Dialog is displayed.

4 In the Name box, enter a name for the new predefined message filter.
5 Modify the other message filter parameters as described in topic Filtering
6 Once modified, click on the OK command button to confirm and to close the
Message Filter dialog.
Result: The new filter is added to the Existing Filters list box on the Predefined
Message Filters dialog.
4014778 Rev H 219

Editing Predefined Filters

The following procedure describes how to change a predefined filter.
the server for which pre-defined message filter settings must be changed.
Result: The Predefined Message Filters dialog is displayed.
3 In the Existing Filters list box, select the filter that must be changed and click on
the Edit... command button.
Result: The Message Filter dialog for the selected predefined filter is displayed.
4 Modify the message filter parameters as described in topic Filtering Messages on
page 216.
5 Once modified, click on the OK command button to confirm and to close the
Message Filter dialog.
6 Press the Close command button to close the Predefined Message Filters dialog.
Selecting a Predefined Message Filter

The following steps explain how to select a predefined filter.
right-click on a resources and point to Default Filter, All Messages, Not
2 Right-click in the Message Viewer window and point to Filter... in the short-cut
menu.
220 4014778 Rev H

Viewing Messages
3 Press the Select... command button.

Result: The Select Predefined Message Filter dialog is displayed.
4 In the Existing Filters list box, select the predefined message filter and point to
the OK command button.
Result: The Message Filter dialog showing the settings of the selected
predefined message filter is displayed.
cancel the operation.
4014778 Rev H 221

Removing Predefined Message Filters

Perform the following procedure to remove predefined message filters.
the server for which pre-defined message filters must be removed.
Result: The Predefined Message Filters Dialog is displayed.
3 In the Existing Filters list box, select the predefined filter(s) that must be
removed.
Tip: To select consecutive filters in the list box, point to the first filter, press and
hold down the [SHIFT] key, and point to the last filter. To select
non-consecutive filters, press and hold down the [CTRL] key, and click on each
filter.
222 4014778 Rev H

Basic Message Operations

Acknowledging Messages
Acknowledging Particular Messages
The following procedure explains how to acknowledge particular messages.
1 In the Server Explorer or Group Explorer tree, right-click on the resources of
which messages must be acknowledged and point to Default Filter, All
Messages, Not Acknowledged, or Pending in the short-cut menu.
Result: The Message Viewer window with the messages of the selected
2 In the Message Viewer window, select the messages that should be
acknowledged. To select consecutive messages, click on the first message, press
and hold down the [SHIFT] key, and click on the last message. To select
messages that are not consecutive, press and hold down the [CTRL] key, and
select each message.
3 Right-click on one of the selected messages and point to Acknowledge in the
short-cut menu.
Result: The messages are acknowledged and indicated by a check mark.
Note: When the Message Viewer window was opened via Not Acknowledged
in the sort-cut menu, the messages will be removed from the Message Viewer
window after acknowledging.
Acknowledging All Messages

The following procedure explains how to acknowledge all messages.
1 In the Server Explorer or Group Explorer tree, right-click on the resources of
which all messages must be acknowledged and point to Default Filter, All
Result: The Message Viewer window with the messages of the selected
2 Right-click on one of the messages and point to Acknowledge All... in the
short-cut menu.
4014778 Rev H 223

the operation.
Result: After pressing the Yes command button, all messages are acknowledged
and indicated by a check mark.
Note: When the Message Viewer window was opened via Not Acknowledged
in the sort-cut menu, the messages will be removed from the Message Viewer
window after acknowledging.
Acknowledging a Message and Adding an Attachment

The following procedure explains how to add a message attachment during the
message acknowledging process.
1 In the Server Explorer or Group Explorer tree, right-click on the resource of
which a message must be acknowledged with message attachment and point to
menu.
Result: The Message Viewer window with the messages of the selected resource
is displayed.
2 Right-click on the message that must be acknowledged with message attachment
and point to Ack with Attachment in the short-cut menu.
Result: The Message Attachment dialog is displayed.
3 Enter the attachment content and press the Update command button to confirm
or the Delete command button to abort the operation.
Result: The message is acknowledged.
Note: More information concerning message attachments can be found in topic
Working with Message Attachments on page 225.
224 4014778 Rev H

Working with Message Attachments

Introduction
The purpose of message attachments is to add additional information to particular
messages. When the Auto Popup Attachment feature is enabled in the Message
Viewer Layout dialog, the attachment is automatically opened after selecting a
message with attachment in the Message Viewer window. Fore more information
concerning the Message Viewer Layout dialog, please refer to topic Changing the
Message Viewer Layout on page 212.
In the Message Viewer window, a messages provided with an attachment is
indicated by a small green triangle, see picture below.
Adding an Attachment to a Message

The following procedure explains how to add an attachment to a message.
which a message must be provided with an attachment and point to Default
Filter, All Messages, Not Acknowledged, or Pending in the short-cut menu.
is displayed.
2 Right-click on the message to which an attachment must be added and point to
Attachment in the short-cut menu.
Result: The Message Attachment dialog is displayed.
Note: If the text is long and does not in the dialog, then continue typing, the text
will scroll in the text box.
3 Enter the attachment content and press the Update command button to confirm
or the Delete the operation.
Result: After pressing the Update command button, the attachment is added to
the message.
4014778 Rev H 225

Opening an Attachment
When the Auto Popup Attachment feature is disabled the attachment of a message
will not be opened automatically after selecting the message in the Message Viewer
window. The following procedure explains how to open an attachment if the Auto
Popup Attachment feature is disabled.
which an attachment must be opened and point to Default Filter, All Messages,
Not Acknowledged, or Pending in the short-cut menu.
is displayed.
2 In the Server Explorer window, right-click on the message of which an
attachment should be opened and point to Attachment in the short-cut menu.
Result: The attachment is displayed.
Deleting a Message Attachment

Perform the following steps to remove an attachment from a message.
which an attachment must be removed and point to Default Filter, All
Messages, or Not Acknowledged in the short-cut menu.
is displayed.
2 Select the message of which the attachment should be removed.
Result: The attachment is displayed when the Auto Popup Attachment feature is
enabled.
3 Press the Delete command button to delete the attachment.
Resetting Pending Messages

Introduction
Some pending messages are not reset automatically. Such messages should be reset
by a user. In the Message Viewer window, a pending message that must be reset
manually is indicated by an icon, see illustration below.
The ROSA NMS system allows reset individual pending messages or all messages.
226 4014778 Rev H

Resetting Particular Pending Messages

The following procedure explains how to reset particular pending messages.
which a pending message must be reset and point to Default Filter, All
is displayed.
2 In the Message Viewer window, select the pending messages that must be reset.
To select consecutive pending messages, point to the first message, press and
hold down the [SHIFT] key, and point to the last message. To select
non-consecutive pending messages, press and hold down the [CTRL] key, and
point to each pending message.
3 Right-click on a selected message and click on Reset Pending in the short-cut
menu or point to the Reset Pending button.
Result: The messages are reset.
Note: When the Message Viewer window was opened using Pending in the
short-cut menu, the messages will be removed from the Message Viewer
window.
Resetting All Pending Messages

The following procedure explains how to reset all pending messages.
which all pending messages must be reset and point to Default Filter, All
is displayed.
2 In the Message Viewer window, right-click on a pending message that must be
reset and click on Reset All Pending... in the short-cut menu or point to the Reset
All Pending button.
the operation.
Note: When the Message Viewer window was opened using Pending in the
short-cut menu, all messages will be removed from the Message Viewer
window.
4014778 Rev H 227

Deleting Non-Pending Messages

Introduction
To enhance the organization of the messages in the Message Viewer window, the
non pending messages can be removed. The ROSA NMS system allows removing
particular non-pending messages or all non-pending messages.
Note: Pending messages cannot be removed. When a pending message should be
removed, the message must be reset. The procedure to reset pending messages can
be found in topic Resetting Pending Messages on page 226.
To Delete Particular Non-Pending Messages

The following procedure describes how to delete particular non-pending messages.
which non-pending messages must be removed and point to Default Filter, All
Messages, or Not Acknowledged in the short-cut menu.
is displayed.
2 In the Message Viewer window, select the non-pending messages that should be
removed. To select consecutive non-pending messages, press the first message,
press and hold down the [SHIFT] key, and press the last message. To select
non-consecutive non-pending messages, press and hold down the [CTRL] key,
and point to each message.
3 Right-click on a selected non-pending message and point to Delete
Non-Pending in the short-cut menu or point to the Delete Non Pending button.
Result: The selected messages are removed.
To Delete all Non-Pending Messages

Perform the following procedure to remove all non-pending messages.
which all non-pending messages must be removed and point to Default Filter,
All Messages, or Not Acknowledged in the short-cut menu..
is displayed.
2 In the Message Explorer window, right-click on a non-pending message and
point to Delete All Non-Pending... in the short-cut menu or click on the Delete
All Non Pending button.
228 4014778 Rev H

the operation.
Result: After pressing the Yes command button, the non-pending messages are
removed from the Message Viewer window.
Note: During the message-deleting-process, a progress indicator may be
displayed.
Printing Messages
The following steps explain how to print messages.
right-click on the resource of which messages must be printed and point to
menu.
Result: The Message Viewer window is displayed with the messages of the
selected resource.
2 In the Message Viewer window, select the messages that must be printed. To
select consecutive messages, click on the first message, press and hold down the
[SHIFT] key, and press the last message. To select non-consecutive messages,
press and hold down the [CTRL] key, and point to each message.
3 Right-click on a selected message and point to Print in the short-cut menu.
4014778 Rev H 229

Result: The Print dialog is opened.

selected messages or the All selection button to print all messages.
on page 44.
Copying Messages to the Clipboard

The following steps explain how to copy messages to the clipboard.
right-click on the resource of which messages must be copied to your clipboard
and point to Default Filter, All Messages, Not Acknowledged, or Pending in
the short-cut menu.
selected resource.
2 In the Message Viewer window, select the messages that must be copied. To
3 Right-click on a selected message and point to Copy to clipboard in the short-cut
menu.
Result: The messages are copied to the clipboard of your computer.
230 4014778 Rev H

Exporting Messages
It can be useful to export particular messages to other application. The picture
below shows message exported to Microsoft Excel.
The following procedure explains how to export messages from the ROSA NMS
system.
right-click on the resource of which messages must be exported and point to
menu.
selected resource.
2 In the Message Viewer window, select the messages that must be exported. To
3 Right-click on a selected message and point to Copy to Clipboard in the
short-cut menu.
4 Open the application to which the messages should be exported.
5 Paste the content of the clipboard in the application.
4014778 Rev H 231

Logging Manual Created Messages

Introduction
The ROSA NMS system allows logging manual created messages for resources.
The ROSA NMS systems, which are connected to the Copernicus Server, SI-Server or
ROSA NMS Single User system to which the resource is connected, are able to view
the manual created message in the Message Viewer window.
This feature can be useful for maintenance purposes to inform other ROSA NMS
operators about the maintenance status of units. Units under maintenance
normally generate several alarm messages. By using the Log New Message feature,
other ROSA NMS operators can be alerted that units are under maintenance.
This feature can be restricted to certain resources and/or ROSA NMS operators by
setting the security action Message - Log New Message. More information about this
security action can be found in topic Security Actions Overview on page 360.
To Log Manual Created Messages

The following steps explain how to log manual created messages.
1 In the Server Explorer or Group Explorer tree, right-click on the resource for
which a message must be created and point to Log New Message... in the
short-cut menu.
Note: The Log New Message... menu item might be grayed and not applicable
depending on the configuration of the security action Message - Log New Message.
Result: The Log New Message dialog is displayed.
2 In the Subject box, enter the subject for this message.

3 In the Info box, enter the information for this message.
4 In the Severity drop down box, select the severity for this message.
5 In the Type drop down box, select the message type.
6 Click on the Log Message command button to confirm or the Cancel command
232 4014778 Rev H

Logging Manual Created Messages
Result: The manual created message appears in the Message Viewer

window(s) of the connected ROSA NMS system(s).
Note: Manual created messages can be handled as other messages.
4014778 Rev H 233

Changing Message Rules

Introduction
Message rules define what the server must do with new incoming messages. The
server may log messages into the database, neglect messages, adapt messages before
logging...
Message rules can be added to the ROSA NMS system by creating new scripts and
saving them to the correct location on the Copernicus Server, SI-Server or ROSA
NMS Single User system. Helpful information about creating scripts can be found
in the Msg_Info.htm file on the following location:
ROSA NMS Singe User system: ...\ Program Files \ Scientific-Atlanta \
ROSASingleUser \ Copernicus \ CoreConfig \ MessagePreProcessing \ Scripts or ...\
Program Files \ Cisco \ ROSASingleUser \ Copernicus \ CoreConfig \
MessagePreProcessing \ Scripts
ROSA NMS Client Server system: ...\ Program Files \ Scientific-Atlanta \
Copernicus \ CoreConfig \ MessagePreProcessing \ Scripts or ...\ Program Files \
Cisco \ Copernicus \ CoreConfig \ MessagePreProcessing \ Scripts on the
Copernicus server or SI-Server
Adding Message Rule Scripts

The following procedure explains how to add message rule scripts to the ROSA
NMS system.
1 Open the folder where the new messages rule scripts are located.
2 Copy the message rule scripts to the following location:
ROSASingleUser \ Copernicus \ CoreConfig \ MessagePreProcessing \ Scripts or
...\ Program Files \ Cisco\ ROSASingleUser \ Copernicus \ CoreConfig \
MessagePreProcessing \ Scripts
Copernicus \ CoreConfig \ MessagePreProcessing \ Scripts or ...\ Program Files \
Cisco \ Copernicus \ CoreConfig \ MessagePreProcessing \ Scripts on the
Copernicus server or SI-Server
the server on which message rule scripts are added and point to Rules... in the
Message menu.
234 4014778 Rev H

Changing Message Rules
Result: The Message Rules dialog is displayed.
4 Click on the Reload Rules command button.

Result: The scripts are added to the Message Rules dialog.
Enabling or Disabling Message Rules

Perform the following steps to enable or disable message rules and to change the
priority.
the server of which message rule(s) must be enabled or disabled and point to
Rules... in the Message menu.
Result: The Message Rules dialog is displayed.
4014778 Rev H 235

Note: When message rule scripts are added during the time the Message Rules
dialog is opened, pressing the Reload Rules command button updates the
dialog.
2 In the list box of the Message Rules dialog, select the message rule(s) that should
be enabled or disabled. To select consecutive message rules in the list box, click
on the first rule, press and hold down the [SHIFT] key, and click on the last rule.
To select non-consecutive rules, press and hold down the [CTRL] key, and point
to each rule.
3 Click on the Enable command button to enable the selected message rules or the
Disable command button to disable the rules.
Note: In the list box of the Message Rules dialog, a message rule that is enabled
is indicated by a check mark and a rule that is disabled by a red cross.
4 Change the priority level of the message rules by selecting and moving up or
down message rules using the Move Up or Move Down command button.
5 Press the OK command button to confirm and to close the dialog, the Apply
command button to confirm without closing the dialog, or the Cancel command
236 4014778 Rev H

Configuring the Message Options

Configuring Message Notification
When the ROSA NMS system receives a message from a Copernicus server,
SI-Server, or a device that is directly connected to the system (ROSA NMS Single
User system), the operator of the ROSA NMS system can be informed using a
pop-up dialog or a sound, or by moving the ROSA NMS user interface to the
foreground. A pop-up can also be displayed when a server, to which the ROSA
NMS system is connected, becomes unreachable.
The following procedure explains how to configure the message notification.
1 Point to the Message menu and select Options....
Result: The Message Options dialog is displayed.
2 In the Popup Dialog box, set the Enable check box to enable the message pop-up
function or clear the Enable check box to disable this function.
3 In the Include Levels list box, select the message severity level(s) for which a
pop-up is displayed.
4014778 Rev H 237

4 Set the Server Unreachable check box if a pop-up must be displayed when a
server becomes unreachable.
Note: This feature only functions when the Enabled check box under the When
Connected with a Server box on the Server Availability tab of the Preferences
dialog is set. For more information about the Preferences dialog, please refer to
topic Checking Server Availability on page 161.
5 In the Sound box, make similar settings for the message sound as described for
the message pop-up function in step 2, 3, and 4.
Additional, the Repeat every x s check box can be set to repeat the sound and the
repetition interval can be entered in the every x s box.
6 In the Put ROSA in foreground box, set the Enabled check box if the ROSA
NMS user interface should be moved to the foreground when a message is
received.
Note: The ROSA NMS user interface will not be moved to the foreground when
it is minimized.
Hiding or Displaying the Hidden Messages

To avoid overloading the Message Viewer window, particular messages are hidden
by the ROSA NMS system, these hidden messages can be displayed on the Message
Viewer window by enabling the show hidden message function.
The following steps explain how to hide or display the hidden messages on the
Message Viewer dialog.
2 In the Hidden messages box, set the Show them check box to display the hidden
messages or clear the check box to hide the hidden messages.
Configuring the Repetitive Alarm Suppression Feature

The Repetitive Alarm Suppression feature of ROSA NMS avoids that identical
messages generated within a specified time interval are listened as different
messages in the Message Viewer window. When this feature is enabled, the count
field in the Message Viewer window indicates how many times the message
occurred.
238 4014778 Rev H

Notes:
This feature cannot be enabled if the version of the server software is lower then
or equal to 3.0.17.
The Repetitive Alarm Suppression feature can only be used if the Suppress All
Repetitive Alarms rule is enabled. For more information concerning enabling
the Suppress All Repetitive Alarms rule, please refer to topic Changing Message
Rules on page 234.
Perform the following procedure to configure the Repetitive Alarm Suppression
feature.
1 In the Server Explorer or Group Explorer tree, select the server on which the
Repetitive Alarm Suppression feature must be configured.
3 In the Repetitive Alarm Suppression box, select the unit of time for the interval
in the Default Interval drop down box and the interval duration in the Default
Interval box.
Configuring the Link to External Web Server Feature

The Link to External Web Server feature of the ROSA NMS system allows setting up
a help database on a web server. When a message is received, pressing a certain
menu item (created during configuring of the feature) in the short-cut menu of the
Message Viewer window sends an http request to a web server page and passes all
message parameters of the selected message. The web server returns information
related to the specific message back to the web browser.
The following picture shows two menu items in the short-cut menu of the Message
Receiver window that are created for the Link to External Web Server feature.
For each server two menu items with corresponding web server addresses can be
created.
4014778 Rev H 239

The following procedure describes how to configure the Link to External Web Server
feature.
1 In the Server Explorer or Group Explorer tree, select the server on which link(s)
to external web server(s) must be created.
3 In the Link to External Web Server box, set the Enabled check box.
4 In the Menu Name box, enter the name for the menu item in the short-cut menu.
5 In the Server Page box, enter the URL of the web browser page. The string
http:// can be omitted.
6 Perform step 3 up to 5 to configure the second link if necessary.
Switching On or Off Backup Active Message Logging

The Backup Active Message Logging option logs a Backup Active message with critical
severity into the ROSA EM driver for a device that becomes inactive after a
main-to-backup transition. This alarm will be cleared when the device becomes
active again. The following steps describe how to switch on or off the Backup Active
Message Logging option.
1 In the Server Explorer or Group Explorer tree, select the server for which the
Backup Active Message Logging option must be switched on or off.
3 In the Backup Active Message Logging box, tick the Enabled check box to
switch on or clear this check box to switched off the option.
240 4014778 Rev H

Working with the Listening Console

Introduction
The ROSA NMS system is provided with a Listening Console that displays the
messages received from servers to which the ROSA NMS system listens. Servers in
listening mode only make connection to the ROSA NMS system when they have
messages to send. These messages can then be viewed without making a
connection from the ROSA NMS system to the server.
This feature can be useful if the connection between the Copernicus server or
SI-Server and the ROSA NMS system is build up using switched telephone lines and
access routers. Instead of having a permanent connection with the server, the
ROSA NMS system now listens to the server. A connection is set up only when the
server has messages to report. As soon as the server has sent the messages, the
connection will automatically be closed again to keep the communication costs low.
Note: This feature is started as soon as the server is disconnected from the Server
Explorer tree of the ROSA NMS system. More information concerning
disconnecting a server from a ROSA NMS system can be found in topic
Disconnecting a Server from the ROSA NMS System on page 130.
The messages received from a Copernicus server or SI-Server in listening mode are
categorized in the Listening Console. The Listening Console window displays the
same information as the Message Viewer window but has an additional column
(called Server) showing from which server the message is coming. This information
is useful when the ROSA NMS system listens to different servers. For information
concerning the other information on the Listening Console window, please refer to
topic Viewing Messages on page 207.
The following picture illustrates a Listening Console window.
4014778 Rev H 241

Setting a Server in Listening Mode

The following procedure explains how to set a Copernicus server or SI-Server in
listening mode.
the server to which the ROSA NMS system must listen.
2 In the Server menu, tick Listen to set the server in listening mode or clear Listen
to disable the listening mode.
Note: The ROSA NMS system starts listening as soon as the server is
disconnected from the Server Explorer tree. A disconnected server in listening
mode is indicated by a green horn.
Opening the Listening Console

The following procedure explains how to open the Listening Console window.
1 Point to Listening Console in the Message menu of the ROSA NMS system.
Result: The Listening Console window is displayed.
Note: Opening the Listening Console window does not set up a connection with the
servers in listening mode.
Selecting the Message Category in the Listening Console

The following procedure explains how to change the message category of the
Listening Console window.
242 4014778 Rev H

2 Right-click on the Listening Console window and point to one of the following
categories:
Default Filter: to apply the default message filter. For details about filter
setup, see Setting Up the Message Filter for the Listening Console Window on
page 244.
All Messages: to display all messages.
Not Acknowledged: to display only the non-acknowledged messages.
Pending: to display only the pending messages.
Result: The messages of the corresponding category are displayed.
Changing the Layout of the Listening Console Window

Perform the following steps to change the layout of the Listening Console window.
2 Right-click on the Listening Console window and point to Layout... in the
short-cut menu.
Result: The Listening Console Layout dialog is displayed.
3 To hide parameter(s), select the parameter(s) in the Visible (in this order) list
box. To select consecutive parameters, select the first parameter, press and hold
down the [SHIFT] key, and press the last parameter. To select parameters that
are not consecutive, press and hold down the [CTRL] key, and point to each
parameter.
After selecting the parameter(s), point to the Hide >> command button.
Result: The selected parameter(s) is (are) moved to the Hidden list box.
4014778 Rev H 243

Note: A parameter can also be hidden by double clicking on the parameter in the
Visible (in this order) list box.
4 To show parameter, select the parameter(s) in the Hidden list box. To select
consecutive parameters, select the first parameter, press and hold down the
[SHIFT] key, and press the last parameter. To select parameters that are not
consecutive, press and hold down the [CTRL] key, and point to each parameter.
After selecting the parameter(s), point to the << Show command button.
Result: The selected parameter(s) is (are) moved to the Visible (in this order) list
box. The parameter(s) is (are) added at the bottom of the list box, meaning this
(these) parameters will be displayed as the right most column(s) in the Listening
Console window.
Note: A parameter can also be made visible by double clicking on the parameter
in the Hidden list box.
5 To change the column order of the parameters, select the parameter(s) and point
to the Shift Up or Shift Down command button. Consecutive parameters can
be moved at once by selecting the first parameter, pressing and holding down
the [SHIFT] key, pointing to the last parameter, and pressing the corresponding
command button.
6 In Options box, set or clear the following check box:
Jump to incoming message: the Listening Console window is constantly
updated. Select this check box if you want to jump to an incoming message
automatically.
7 Point to the Make Default command button to make this layout the default
layout.
Setting Up the Message Filter for the Listening Console Window

If there are too many messages displayed in the Listening Console window, these
messages can be filtered. The following procedure describes how to configure the
Message Filter for the Listening Console window.
2 Right-click on the Listening Console window and point to Filter... in the
short-cut menu.
244 4014778 Rev H

Result: The Message Filter dialog for the Listening Console window is
displayed.
3 In the Type box, set or clear the message type check boxes.
4 In the Level box, set or clear the severity level check boxes.
5 In the Pending selection box, select on of the following selection buttons:
Show All: the pending as well as the not pending message will be displayed
Show Pending: only the pending messages will be displayed
Show not Pending: only the not pending messages will be displayed
6 In the Acknowledged selection box, select one of the following selection buttons:
Show All: the messages that are acknowledged as well as the messages that
are not yet acknowledged are displayed.
Show Acknowledged: only the messages, which are acknowledged, are
displayed.
Show not Ack: only the messages, which are not yet acknowledged, are
displayed.
Note: The procedure to acknowledge a message can be found in topic
Acknowledging Messages on page 223.
4014778 Rev H 245

7 Select the No date/time filtering, Last, or Range selection button.

No date/time filtering: no time filtering will be performed.
Last: only the messages within a particular time window will be displayed
on the Listening Console window.
Select the unit of time (seconds, minutes, hours, days, months, years) in the
Last drop down box and duration in the Last box.
Range: only the messages between two dates will be displayed on the
Listening Console window.
In the From and To box, select the time and date.
8 In the Show box under the Message Info box, enter the string that the message
info must contain to display the message.
9 In the Don't Show box under the Message Info box, enter the string that the
message info must contain to hide the message.
10 In the Show box under the Message Subject box, enter the string that the
message subject must contain to display the message.
11 In the Don't Show box under the Message Subject box, enter the string that the
message subject must contain to hide the message.
Note: In the Show and Don't Show boxes wildcard characters are allowed. Use
the asterisk character (*) as a substitute for zero or more characters and the
question mark as a substitute for a single character in the message info.
12 In the Show Server list box, select the server(s) of which messages must be
displayed in the Listening Console window. To select consecutive servers,
point to the first server, press and hold down the [SHIFT] key, and point to the
last server. To select non-consecutive servers, press and hold down the [CTRL]
key and point to each server.
13 Click on the Make Default command button to make the new filter the default
filter.
Result: After pressing the Make Default command button, the following
message box is displayed.
Point to the OK command button to close this message box.

Note: Each time the Message Viewer is opened via default filter, this filter
definition will be used.
246 4014778 Rev H

Removing Messages from the Listening Console

To Remove Particular Messages
Perform the following steps to remove messages from the Listening Console
window.
2 Select the message(s) that should be removed. To select consecutive messages,
click on the first message, press and hold down the [SHIFT] key, and point to the
last message. To select non-consecutive messages, press and hold down the
[CTRL] key, and point to each message.
3 Right-click on a selected message and point to Remove Entry in the short cut
menu.
Result: The selected message(s) is (are) removed from the Listening Console
window.
Note: The hidden message by using a particular filter or by selecting a particular
message category will not be removed from the Listening Console.
To Remove all Messages

The following procedure explains how to remove all messages from the Listening
Console window.
2 Right-click on the Listening Console window and point to Clear All Entries in
the short-cut menu.
Result: All messages are removed from the Listening Console window.
Note: The hidden message by using a particular filter or by selecting a particular
message category will not be removed from the Listening Console.
4014778 Rev H 247

Alarm Correlation Domains

Introduction
The Alarm Correlation Domains is an additional ROSA NMS feature to correlate
different network topologies. The correlation is script-based and the appropriate
scripts files should be added in the right folder. Each Alarm Correlation Domain
needs a corresponding script, which is delivered by Cisco.
License key
The Alarm Correlation Domains feature requires separate license keys that allow the
ROSA NMS system to run the scripts. The following correlation domains are
currently supported by the ROSA NMS system.
HFC-HMS Alarm Correlation domain - ALARMCORR_HFC
iLynx Alarms Correlation domain - ALARMCORR_iLYNX
... (more correlation domains will be available in the near future)
HFC Alarm Correlation

The HFC alarm correlation mechanism is able to correlate Unit not responding
messages of transponders in a HFC-HMS network. Correlation means that if all
active devices (transponders are active devices, splitters are passive devices) in a
certain branch of the HFC network become not responding, these devices should not
log a visible Unit not responding message but instead a correlated Link problem
message for that branch. This message is logged on the top node of that topology.
The link between the lowest responding unit in the tree and the highest not
responding unit in the not responding branch becomes colored. This allows
locating broken links in a very fast way. The Unit not responding message of a
correlated active device is invisible.
The picture below shows an example.
248 4014778 Rev H

Adding the Alarm Correlation Domains Scripts

The following procedure explains how to add the HFC Alarm Correlation Domain
scripts to the ROSA NMS system. This procedure can also be used to add scripts of
other alarm correlation domains.
1 Insert the ROSA/Copernicus installation CD-Rom labelled with Disk 1 in the
CD-Rom drive of the ROSA NMS system.
2 Open the folder ...\ AlarmCorrelation \ HFC.
3 Copy the HFC Alarm Correlation domain scrips to the following location:
ROSASingleUser \ Copernicus \ CoreConfig \ AlarmCorrelation \ Scripts or ...\
AlarmCorrelation \ Scripts
Copernicus \ CoreConfig \ AlarmCorrelation \ Scripts or ...\ Program Files \
Cisco \ Copernicus \ CoreConfig \ AlarmCorrelation \ Scripts on the Copernicus
server or SI-Server
4 Stop and restart the server as described in topic Stopping, Rebooting and Starting a
Server on page 133.
Result: The HFC Alarm Correlation domain is added.
Editing the Configuration File

The HFC.atl configuration file can be set up according to the requirements of the
HFC network. The following parameters of the HFC.atl file can be changed:
ObjectTypeIDTopNode: this device OID number tells the script which device is
on top of the HFC network tree topology. This OID value corresponds with the
SNMP profile of the top node (for example Phoenix1 with OID 55003).
TopNodeTxPinName: not used
ObjectTypeIDActiveUnits: this is the range of OID numbers containing all
active devices (for example SNMP devices...). You are allowed to define
multiple ranges.
ObjectTypeIDPassiveUnits: this is the range of OID numbers containing all
passive devices (for example splitters) that must be modeled using GNE profiles.
DebounceTime (Default: 10000 ms): when active devices in the network become
not responding, a time delay must be entered before the downstream alarm
messages become visible. The debounce time is necessary to avoid messages
due to brief interruptions of active devices.
Note: The HFC.atl configuration file can be opened with any text editor. Do not
forget to save the configuration file and re-initialize the script for a properly
functioning alarm correlation.
4014778 Rev H 249

The following picture shows an example of an HFC.atl configuration file.
Note: In a correlated HFC network many unit not responding messages are logged,
but hidden for the viewer. To make sure the Non-pending and not visible messages
are not overwhelming database, the Delete all non-pending can be enabled, not visible
messages rule can be enabled. A schedule for this rule can also be defined.
Viewing Alarm Correlation Domains

Perform the following procedure to view the Alarm Correlation Domains.
1 In the Server Explorer tree of the ROSA NMS system, select the server of which
the Alarm Correlation Domains should be checked.
2 Click on the Message menu and point to Alarm Correlation Domains.
250 4014778 Rev H

Result: The Alarm Correlation Domains dialog is displayed.
Notes:
The different domains can be checked in which alarm correlation will take
place.
Scripts that might have changed can be reloaded by pressing the Reinitialize
command button.
3 Press the OK command button to close the dialog.
Using the HFC Alarm Correlation

This section shows you how to use HFC alarm correlation. You need to draw a
HFC network topology in a map. It is allowed to draw multiple topologies. These
will be correlated separately.
Note: The Alarm Correlation is only working when your topology has relations
mapped between pins of the devices, not between the devices themselves.
The network topology must have a consistent tree structure. The correlation can
not function properly in case of network loops, multiple parents... In this case, the
HFC alarm correlation mechanism will detect an inconsistent topology and an error
message with more detailed information is logged under the server resource.
The following error messages can appear.
%resourcename% is not allowed for HFC (OID out of range)
%resourcename% has multiple parents
%resourcename% has a father and is a top node: not allowed
Configuration file is missing or has a bad syntax
4014778 Rev H 251

The status of the topology is also indicated in the status field of the Alarm
Correlation Domains dialog.
Note: As long as the topology is inconsistent, no correlation is performed.

The following map shows an HFC-HMS network with a consistent topology.
Note: Each time the topology in the map is changed (edit, add, delete) the script
should be re-initialized.
In case a link is down (for example cable cut...) the alarm correlation detects the
lowest responding unit in the tree and the highest not responding unit in the not
responding branch.
252 4014778 Rev H

The map indicates the broken link and a message describing the problem is logged
into the database. A detailed message description of the network problem is
available in the top node device.
4014778 Rev H 253

Maintaining the Message Database

Viewing Message Statistics
The following steps explain how to view the statistic information about the messages
in the database of a particular server.
1 In the Server Explorer tree or Group Explorer tree, select the server of which
statistic information about the messages in the database should be checked.
2 In the Message menu, point to Maintenance and select Statistics.
Result: The Message Statistics dialog is displayed.
The message figures are categorized using the message type filter and given for
the messages generated in the last 24 hours. The Item column in the list box
indicates the category and the Count column the number of messages.
Note: The message statistics can be updated by pressing the Refresh command
button.
3 The time period can be changed by adapting the Date and Time box in the From
box.
4 The message figures can be categorized using the Resource filter, therefore point
to the Resource selection button in the Show selection box.
Note: After changing the date, time or filter the Refresh command button should
be pressed.
5 The details of a message category can be checked by selecting the message
category and clicking on the Details >> command button.
6 To print one of the lists, in the Options menu on the Message Statistics dialog
click on Print and point to List 1 to print the left hand list box or to List 2 to print
the right hand list box.
7 Press the Close command button to close the Message Statistics dialog.
254 4014778 Rev H

Cleaning the Message Database

Perform the following steps to clean the message database of a server.
1 In the Server Explorer tree or Group Explorer tree, select the server of which the
message database should be cleaned.
2 In the Message menu, click on Maintenance and point to Delete....
Result: The Message database maintenance dialog is displayed showing the
messages statistics.
3 Click on the Delete command button.

Result: The Delete Messages dialog is displayed.
4 In the Locations list box, select the location for which the message database
should be cleaned. To select consecutive locations in the list box, click on the
first location, press and hold down the [SHIFT] key, and click on the last
location. To selective non-consecutive locations, press and hold down the
[CTRL] key, and point to each location.
4014778 Rev H 255

Note: When not all locations in the Locations list box are selected, all messages
can be selected by pressing the All command button. When all locations are
selected, this command button is changed to None and can be used to deselect
all locations in the Locations list box.
5 In the Resources list box, select the resources for which the message database
should be cleaned. To select consecutive resources in the list box, click on the
first resource, press and hold down the [SHIFT] key, and click on the last
resource. To selective non-consecutive resources, press and hold down the
[CTRL] key, and point to each resource.
Note: When not all resources in the Resources list box are selected, all messages
can be selected by pressing the All command button. When all resources are
selected, this command button is changed to None and can be used to deselect
all resources in the Resources list box.
6 In the Level box, set the severity check boxes for the messages that should be
cleaned and clear the check boxes for the messages that cannot be removed.
7 In the Type box, set the type check boxes for the messages that should be cleaned
and clear the check boxes for the messages that cannot be removed.
8 To remove all message between two dates, enter the time in the Time box and
the date in the Date box in both the From and To box.
9 To remove all messages from a particular time ago till now, select the unit of
time (seconds, minutes, hours, days, months, or years) in the Last drop down
box and the time in the Last box.
10 Press the Delete command button to delete the messages or the Cancel
Result: After pressing the Delete command button, a message box appears
displaying the number of messages that are removed.
11 Press the OK command button.

Result: Both the message box and the Delete Messages dialog are closed and the
statistics shown in the Message database maintenance dialog are updated.
12 Point to the Close command button to close the Message database maintenance
dialog.
256 4014778 Rev H

Using Message Maintenance Rules

Introduction
Database clean up actions can be defined using message maintenance rules. These
rules define which messages that should be deleted depending on the message
content or generation time and the time the messages must be deleted.
Message maintenance rules can be added to the ROSA NMS system by creating new
scripts and saving them to the correct location on the Copernicus Server, SI-Server or
ROSA NMS Single User system. Helpful information about creating scripts can be
found in the Mnt_Info.htm file on the following location:
ROSASingleUser \ Copernicus \ CoreConfig \ Maintenance \ Scripts or ...\ Program
Files \ Cisco \ ROSASingleUser \ Copernicus \ CoreConfig \ Maintenance \ Scripts
Copernicus \ CoreConfig \ Maintenance \ Scripts or ...\ Program Files \ Cisco \
Copernicus \ CoreConfig \ Maintenance \ Scripts on the Copernicus server or
SI-Server.
Adding Message Maintenance Rule Scripts

The following procedure explains how to add message maintenance rule scripts to
1 Open the folder where the new message maintenance rule scripts are located.
2 Copy the message maintenance rule scripts to the following location:
ROSASingleUser \ Copernicus \ CoreConfig \ Maintenance \ Scripts or ...\
Maintenance \ Scripts
Copernicus \ CoreConfig \ Maintenance \ Scripts or ...\ Program Files \ Cisco \
Copernicus \ CoreConfig \ Maintenance \ Scripts on the Copernicus server or
SI-Server
the server on which message maintenance rule scripts are added and in the
Message menu, point to Maintenance and click on Rules....
4 Press the Reload Rules command button.
Result: The new added message maintenance rule appears in the list box of the
Message Maintenance Rules dialog.
4014778 Rev H 257

Enabling or Disabling a Message Maintenance Rule

Perform the following procedure to enable or disable a message maintenance rule.
the server of which message maintenance rule(s) should be enabled or disabled.
2 In the Message menu, select Maintenance and point to Rules....
Result: The Message Maintenance Rules dialog is displayed.
Note: When message maintenance rule scripts are added, pressing the Reload
Rules command button updates the dialog.
3 In the list box of the Message Maintenance Rules dialog, select the rule(s) that
must be enabled or disabled. To select consecutive message maintenance rules
in the list box, click on the first rule, press and hold down the [SHIFT] key, and
point on the last rule. To select non-consecutive rules, press and hold down the
[CTRL] key, and point to each rule.
4 Click on the Enable command button to enable the selected message
maintenance rules or the Disable command button to disable the rules.
Note: In the list box of the Message Maintenance Rules dialog, a message
maintenance rule that is enabled is indicated by a check mark and a rule that is
disabled by a red cross.
Note: When Alarm Correlation functionality of ROSA NMS is used, it is
recommended to enable the message maintenance rule Delete all non pending, not
visible messages.
258 4014778 Rev H

Configuring the Message Maintenance Rule Details

The following procedure explains how to change maintenance rule settings.
the server of which Message Maintenance Rule Settings should be changed.
2 In the Message menu, select Maintenance and point to Rules....
Result: The Message Maintenance Rules dialog is displayed.
3 In the list box of the Message Maintenance Rules dialog, select the message
maintenance rule and point to the Edit command button.
Result: The Message Maintenance Rule Details dialog of the selected rule is
displayed.
Note: The Message Maintenance Rule Details dialog of a rule can also be
opened by double-clicking on the rule.
4 In the Application Window box, select the unit of time (seconds, minutes, hours,
days, months, years) in the Messages Older than drop down box and interval
duration in the Messages Older than box.
5 In the Start Time box, enter the time the maintenance message rule should be
activated.
6 In the Recurrence selection box, select the Daily or Weekly selection button.
7 When Weekly is selected in the Recurrence selection box, set or clear the check
box(es) of the day(s) when the maintenance message rule should be activated.
4014778 Rev H 259

12 Chapter 12
Working with Maps
Introduction
This chapter describes how to create and how to use maps into the
ROSA NMS system.
Note: Since the ROSA Device Configuration Shell (DCS) does not
support Maps, this chapter can be omitted by ROSA DCS users.
In This Chapter
About Maps ......................................................................................... 262
Map Modes .......................................................................................... 265
Setting the Map Options .................................................................... 266
Resource Bitmaps................................................................................ 268
Map Operations .................................................................................. 272
Using Map Objects.............................................................................. 292
Manipulating Map Objects ................................................................ 321
Using Performance Bars..................................................................... 326
4014778 Rev H 261

Chapter 12 Working with Maps
About Maps
Introduction
Maps can be used for many purposes. The most important are:
to document the geographical or logical headend structure
to create the topology for network monitoring
to configure various ROSA NMS tasks, using relations
Note: There is no difference between these types of maps in how to create them or
how the ROSA NMS system handles them.
Headend and Network Structure Maps

In headend and network structure maps, bitmaps of the network regions can be
imported and then be populated by headends and/or network devices as they are
located geographically. The ROSA NMS drawing tools can then be used to draw
racks in which the devices are accommodated. The following picture shows a
headend map.
262 4014778 Rev H

About Maps
By using map links, hierarchical maps can easily be created, starting with a region
map, including links to the headend maps and then add links to for example task
configuration maps for tasks running in the headend.
Network Monitoring Topology Maps

In this type of maps, the network monitoring equipment is not necessarily placed in
the map as it is located geographically. Instead, the map contains the
interconnections between the monitoring equipment and other network equipment
such as splitters, taps and so on.
Creating this network topology in a map allows ROSA NMS to correlate

measurements from the monitoring equipment and to determine the network branch
that is most likely malfunctioning.
4014778 Rev H 263

Task Configuration Maps

Tasks such as the Receiver-Modulator Backup Task, which require knowledge about
device connections, scan the relations in the database for valid connections. The
easiest way to create relations is to draw them in a map. The different ROSA NMS
Task user manuals contain instructions about which relations they require.
264 4014778 Rev H

Map Modes
Map Modes
Introduction
The ROSA NMS user interface can work in two different map modes:
Operational mode
Editing mode
The Operational map mode prevents accidentally changing map content and map
hierarchy. When the content of a map should be changed or when maps should be
added, removed, or linked, the map mode must be changed to Editing.
Notes:
In both modes, the resource bitmaps in the maps are updated to represent the
latest status.
A user interface of a resource can be opened in both modes.
Note: If your map permissions do not allow map editing, you cannot enter Editing
mode. For details, please refer to topic Map Security on page 373.
Changing the Map Mode

The following procedure describes how to change the map mode.
1 In the Maps menu, tick Allow Editing to set the mode to Editing or clear Allow
Editing to set the mode to Operational.
When the mode is set to Editing, the menu bar is enlarged with three menus and
the Map Tools toolbar and Colors palette are displayed by default.
Tip: The ROSA NMS user interface allows toggling between Operational and Editing
mode or vice versa by pointing to the Toggle Editing Mode button on the Server
Tools toolbar.
4014778 Rev H 265

Setting the Map Options

Introduction
The behavior of the ROSA NMS system during opening a map and deleting a
relation from a map together with default map component layout settings can be
changed on the Map Options dialog.
To Set the Map Options

The following procedure explains how to set the map options.
1 In the Maps menu of the ROSA NMS user interface, point to Options....
Result: The Maps Options dialog is displayed.
2 In the When opening a map box, set or clear the following check boxes.
Cache map components: when this option is enabled (check box is set), the
active components in the maps are automatically reloaded from the server to
the ROSA NMS system while opening the map. This option is default
enabled since the ROSA NMS system allows automatic map component
updating if a newer driver version is installed. Disable this option to open
the maps faster.
Automatic zoom map: when this option is set, the map is displayed
completely after opening.
266 4014778 Rev H

Setting the Map Options
Show relations: when this check box is set, the relations are shown on the
map.
3 In the When deleting a relation in a map box, click on one of the following
selection buttons.
Delete only the visual representation: when this option is selected, the
relations line can be deleted without deleting the actual relation in the
database. This can be useful when many relations are making the map
unclear.
Delete it also in the database: when this option is selected, deleting a
relation in a map also deletes the relation in the database.
Ask me what I want at that moment: when this option is selected, a dialog is
displayed asking if the relation must be removed from the database when a
relation is deleted.
Note: When a resource is deleted from a map that has relations starting from it or
coming to it, the visual representations of the involved relations are also deleted,
but the relations itself are not deleted from the database. The Apply this also to
relations that are indirectly deleted from a map option allows the following
choices.
The option is not set: the involved relations are deleted visually but not in the
database.
The option is set and the Delete it also in the database selection button is
selected: the involved relations are deleted visually and from the database.
The option is set and the Ask me what I want at that moment selection
button is selected: the ROSA NMS system asks what to do with the involved
relations at the moment of deletion.
4 In the Default Map Component Layout box, specify the default representation
of a map component.
Object Type Name: shows the type of the map component.
Icons: the Not Acknowledged Message and Not Responding icons appear in the
upper right corner and the Note icon in the lower right corner of the bitmap.
Unit Name: shows the map component name as it appears in the Server
Explorer or Group Explorer tree.
Alarm Coloring: The alarm severity level is indicated with a colored border
around the bitmap.
Note: Only the default layout is specified. The layout of each component can
individually be changed afterwards.
4014778 Rev H 267

Resource Bitmaps
Introduction
By default, resources are displayed in a map using the bitmap delivered with the
driver. This default bitmap can be replaced by a self-made bitmap. The following
list gives tips to create new bitmaps.
Create bitmaps in 256 colors using the System Palette.
There is no size limit for the bitmaps, but 40 by 40 pixels usually will be
sufficient. Units with larger bitmaps will not be convenient anymore to place in
a map.
Do not reuse the names of default bitmaps. The default bitmaps are stored on
the following location:
ROSA NMS Single User system: in the folder ...\ Program Files \
Scientific-Atlanta \ ROSASingleUser \ Copernicus \ Bitmaps or ...\ Program
Files \ Cisco \ ROSASingleUser \ Copernicus \ Bitmaps
ROSA NMS Client/Server system: in the folder ...\ Program Files \
Scientific-Atlanta \ Copernicus \ Bitmaps or ...\ Program Files \ Cisco \
Copernicus \ Bitmaps on the Copernicus server or SI-Server.
A bitmap may contain up to 80 sub bitmaps.
Example: MyBitmap[80].bmp
Installing User-Defined Bitmaps

The following procedure explains how to install a self-made bitmap.
the server for which a self-made bitmap should be installed.
2 In the Config menu, point to Bitmaps....
268 4014778 Rev H

Resource Bitmaps
Result: The Installed Bitmaps dialog is displayed.
Note: The Installed Bitmaps dialog can also be opened by clicking on the
Bitmaps button in the Server Tools toolbar.
3 Press the Install... command button.
Result: The Open Dialog is displayed.
4 Browse to the folder containing the self-made bitmap.

5 Select the bitmap and press the Open command button to install the bitmap or
the Cancel command button to abort the operation.
Result: After pressing the Open command button, the bitmap is copied to the ...\
Bitmaps folder on the Copernicus server, SI-Server, or ROSA NMS Single User
system. The bitmap appears in the list box of the Installed Bitmaps dialog.
4014778 Rev H 269

Changing the Bitmap of a Resource

Perform the following steps to change a bitmap of a resource.
right-click on the resource for which the bitmap must be changed and point to
Settings in the short-cut menu.
Result: The Resource Settings dialog is displayed.
2 In the Bitmap drop down box, select the new bitmap for the resource.
Uninstalling Bitmaps
The ROSA NMS system allows uninstalling user-defined bitmaps. When a
user-defined bitmap is removed that is used by a resource, the resource will use its
default bitmap again. Perform the following procedure to remove one or more
user-defined bitmaps.
the server for which self-made bitmap should be uninstalled.
2 In the Config menu, point to Bitmaps....
270 4014778 Rev H

Resource Bitmaps
Result: The Installed Bitmaps dialog is displayed.
3 In the list box of the Installed Bitmaps dialog, select the user-defined bitmap
that must be uninstalled.
4 Press the Uninstall command button.
5 Repeat step 3 and 4 for all user-defined bitmaps that should be removed.
Note: A default bitmap cannot be uninstalled. If you try to uninstall such a
bitmap, the following warning message box is displayed.
Click on the OK command button to close the warning message box.

6 Press the Close command button to close the Installed Bitmaps dialog.
4014778 Rev H 271

Map Operations
Creating Maps
Introduction
Maps can be structured hierarchically, with the highest level map representing for
instance a network region. The sub maps of this map could be individual
headends, each containing different maps, such as maps for alarm tracking and
maps for task configuration. By linking these maps in a hierarchical structure,
alarms can easily be tracked from the top level map down to the map containing the
resource that generated the alarm. This is possible because the links to the sub
maps are colored using the color of the highest level alarm of any resource in the sub
map and its own sub maps.
Creating a Map
Perform the following steps to create a map.
1 In the Map Explorer tree of the ROSA NMS system, right-click on the Maps root
node and point to New/Link in the short-cut menu.
Result: The New/Link Map dialog is displayed.
2 In the Map Name box, enter a name for the new map.
Result: After pressing the OK command button, the new map is added to the
Map Explorer tree.
Creating a Sub Map

The following procedure explains how to create a sub map.
1 In the Map Explorer tree of the ROSA NMS system, right-click on the map or sub
map for which a sub map should be created and click on New/Link in the
short-cut menu.
2 In the Map Name box, enter a name of the new sub map.
272 4014778 Rev H

Map Operations

Result: After pressing the OK command button, the new sub map is added
under the higher-level map node and a map link is placed in the higher-level
map.
Turning an Existing Map to a Sub Map of Another Map

The following steps explain how to turn an existing map into a sub map of another
map.
1 In the Maps Explorer tree of the ROSA NMS system, right-click on the
higher-level map and point to New/Link in the short-cut menu.
2 Click on the Link command button.

Result: The list with maps available for linking is displayed.
3 In the list box, select the map that should be added as a sub map.
4014778 Rev H 273

Result: The map is added as a sub map under the higher-level map node and a
map link to this sub map is added in the higher-level map
Opening and Closing Maps

A map can be opened by right-clicking on the map in the Map Explorer tree and
pointing to Open in the short-cut menu.
A map can be closed as follows:
Clicking on Close in the File menu to close the current map
Clicking on Close All in the Window menu to close all map windows at once.
When a map is closed, the ROSA NMS system stores its view window position, size,
and zoom factor. When the map is opened again, the stored settings are applied to
its view window.
Renaming a Map
Perform the following procedure to rename a map.
1 In the Map Explorer tree of the ROSA NMS system, right-click on the map that
must be renamed and point to Rename in the short-cut menu.
Result: The Rename Map dialog is displayed.
2 In the New box, enter the new name for the map.
Note: The name must be unique.
274 4014778 Rev H

Map Operations
Notes:
When a map already exists with the same name, the following message box
will be displayed after pressing the OK command button.
During the map renaming process, all links to this map will automatically be
renamed.
Saving Maps
Introduction
When server resources are added to or removed from a map or the hierarchy of a
map is changed, the corresponding map will be saved automatically to keep it
consistent with the internal map hierarchy kept by the ROSA NMS system. When
other objects in a map are changed, the map should be saved to make these changes
permanent.
To Save a Particular Map

A particular map can be saved in one of the following ways:
In the Maps menu, point to Save.
In the Map Explorer tree, right-click on the corresponding map and point to
Save.
Click on the Save button in the Map Tools toolbar.
To Save All Maps

All maps can be saved in one of the following ways:
In the Maps menu, point to Save All.
Switch to operational mode.
Importing Maps
The following procedure explains how to import an existing map to the Map
Explorer of the ROSA NMS system.
1 In the Server Explorer or Map Explorer tree of the ROSA NMS system, select the
server for which maps must be imported.
4014778 Rev H 275

2 Click on Import... in the Maps menu.

3 Browse to the folder that contains the maps that should be imported.
4 Point to the map (extension: .Map) and click on the Open command button.
Result: The map is added to the root of the Map Explorer tree.
Deleting Maps
To Delete a Particular Map
Perform the following steps to delete a map.
1 In the Map Explorer tree of the ROSA NMS system, right-click on the map that
must be deleted and point to Delete or Delete link in the short-cut menu.
Note:
Deleting a map that refers more than once in the Map Explorer tree is only
deleted on the position the map is selected. When a map is a sub map of
multiple maps, it's only deleted from the map in which the sub map is
selected. If the selected map has only one reference in the Map Explorer
tree, a confirmation is displayed.
the operation.
276 4014778 Rev H

Map Operations
Notes:
When the selected map is a sub map, the map will be moved to the root if the No
command button is pressed.
When a map is deleted permanently, the resources and their relations are not
removed from the database.
To Delete All Maps

The following steps explain how to delete all maps.
1 In the Map Explorer tree of the ROSA NMS system, right-click on the Maps root
and point to Delete All in the short-cut menu.
the operation.
Result: With the exception of the resources and their relations, all map objects
will be removed after pressing the Yes command button.
Manipulating the Map Windows

Zooming In and Out on Maps
To zoom in to see some areas of a map close up or to zoom out to see the entire map,
the ROSA NMS system is provided with the following zoom commands:
Zoom 100%: set the zoom factor to 100%
Zoom Map: zoom to make the whole map visible in the current window
Zoom Full: zoom to fit all map objects exactly into the current window
These zoom commands are available in the Windows menu and in the short-cut
menu after right-clicking on a map.
Notes:
Zooming is limited to a value between 20% and 500%.
The current zoom factor is displayed in the status bar of the user interface.
The ROSA NMS user interface is also provided with a zoom tool. Perform the
following steps to zoom in or out using this zoom tool.
4014778 Rev H 277

1 In Editing mode, click on Zoom in the Draw menu or click on the Zoom Tool
button in the Server Tools tool bar.
In Operational mode, click on the Zoom Tool button in the Server Tools tool bar.
2 To zoom in, left-click and drag to select a part of the map.
3 To zoom out, right-click and drag to select a part of the map.
Splitting Map Views

To simultaneously view different parts of a map that are too far apart to fit in a
single view, splitter bars can be used. The splitter bars are located at the left hand
side of the horizontal scroll bar and above the vertical scroll bar of the map window.
Drag them to split the view.
278 4014778 Rev H

Map Operations
Using the splitter bars, maximum four parts of a map can be displayed in the same
window.
Note: The split map view is not stored when the map window is closed.
Opening a New Window

The ROSA NMS system allows opening multiple windows with the same map. To
open a new window, select the map window and click on New Window in the
Window menu. To display different parts of a map, both views can be positioned,
scrolled, and zoomed independently.
Arranging Map Icons

Minimized map views can automatically be arranged and stacked at the bottom of
the workspace of the ROSA NMS user interface by clicking on Arrange Icons in the
Window menu.
Arranging Map Windows

When several maps are opened, the windows can be arranged in the workspace of
the ROSA NMS user interface. Click on Cascade in the Windows menu to stack
and to align the windows from the upper left corner to the lower right corner of the
workspace. Press on Tile in the Windows menu to align the windows in rows.
4014778 Rev H 279

Changing the Map Settings

Introduction
The map properties like size, grid and background can be changed on the Map
Properties dialog.
Before map properties can be changed, the ROSA NMS system must be set to Editing
mode. The procedure to set the ROSA NMS system to Editing mode is described in
topic Map Modes on page 265.
Setting the Map Size

The size of a map can be set to a predefined size or to a custom made size. The
predefined sizes are: Letter Portrait, Letter Landscape, A4 Portrait, A4 Landscape,
A3 Portrait, and A3 Landscape (default size). The maximum custom made format
of a map is 1524 x 1524 mm (60 x 60 inch).
Note: Change the map size before adding objects to a map. If the size of a map,
which is populated with objects, is changed, some object might become invisible
because they are outside the map area.
The following procedure explains how to change the size of a map.
1 Double-click on the map background.
2 Result: The Map Properties dialog is displayed.
3 Point to the Size selection button to use a predefined size or the Custom
selection button to use another size.
When the Size selection box is selected, point to the desired predefined size
in the Size drop down box.
When the Custom selection box is selected, point to the desired unit in the
Custom drop down box and enter the size (width and high) in the Custom
boxes.
4 Press the Apply command button to activate the new settings.
Tip: The Map Properties dialog can be closed by clicking on the exit button in the
title bar.
280 4014778 Rev H

Map Operations
Setting the Drawing Grid

Using the drawing grid facilitates the positioning of objects and resources in a map.
In a map the grid is drawn using dashed lines. The middle of the map is indicated
by a vertical and horizontal line with longer dashes. The snap to grid behavior
positions and align objects exactly. When snap to grid is enabled, objects are pulled
to the grid points. Snapping can be used to align objects or to make drawing
straight horizontal and vertical lines easier. When objects in a map must be
positioned freely, it is advisable to switch off snap to grid. The following procedure
explains how to setup the drawing grid for a map.
Result: The Map Properties dialog is displayed.
2 Select the Grid tab.
Result: The Grid tab is displayed.
3 In the Snap grid drop down box, select the desired unit, inch or mm.
4 In the Snap boxes, enter the snap grid dimensions. Using a fine snap grid align
objects more precisely.
5 Set the Show grid every x snap points check box to display the grid lines in the
map or clear the check box to hide the grid lines. If a grid line is needed every
snap point, set x to 1.
Note: You can toggle between hiding and displaying the grid lines by pressing
the Toggle Grid button on the Map Tools toolbar.
6 Set the Snap to grid check box to enable snapping or clear the check box to
disable snapping.
Note: You can toggle between enabling and disabling snapping by pressing the
Toggle Snapping button on the Map Tools toolbar.
7 Press the Apply command button to activate the new grid and snap settings.
title bar.
4014778 Rev H 281

Setting the Map and Grid Colors

Perform the following steps to change the map background color and grid color.
Result: The Map Properties dialog is displayed.
2 Point to the Color tab.
Result: The Color tab is displayed.
3 In the Page drop down box, select a predefined color for the map background.
4 In the Grid drop down box, select a predefined color for the grid lines.
Tip: The Color dialog to define custom colors for the map background and grid
can be displayed by pressing the corresponding Custom command button.
Define the desired color and press the OK command button.

title bar.
282 4014778 Rev H

Map Operations
Printing Maps
Setting Up the Printer
Before maps can be printed, the printer setup can be changed. Perform the
following steps to change the printer setup.
1 In the File menu of the ROSA NMS system, click on Print Setup....
Result: The standard Windows Print Setup dialog is displayed.
2 Change the printer, its properties, and the paper settings as required.
For best results, set the page size and orientation identical to the map size and
orientation. These map settings can be checked on the Map Properties dialog.
For more information concerning the Map Properties dialog, please refer to topic
Setting the Map Size on page 280.
3 Press the OK command button to activate the new printer settings or the Cancel
Displaying a Print Preview

Before printing a map, a print preview can be displayed to see how the map will be
printed. The following steps explain how to display a print preview of a map.
1 Select the map for which a print preview must be displayed.
2 In the File menu, click on Print Preview.
4014778 Rev H 283

Result: A print preview is displayed showing how the map will be printed.
3 Click on the Zoom In or Zoom Out command button to change the

magnification level of the print preview.
4 When the map size exceeds the paper size of the printer, the map will be printed
on several pages. Click on the Next Page or Prev Page command button to
scroll through these pages. Two pages of such a map can be displayed on one
screen by pressing the Two Page command button.
5 Press the Print command button to open the Print dialog or the Close command
button to close the print preview and to return to the ROSA NMS user interface.
Printing a Map
Perform the following steps to print a map.
1 Select the map that should be printed out.
2 In the File menu, click on Print....
284 4014778 Rev H

Map Operations
3 In the Name drop down box, select the printer that should be used to print the
map.
4 Click on the Properties command button to change the settings of the selected
printer and return to the Printer dialog.
5 Press the OK command button to print the map or the Cancel command button
Synchronizing Maps
Introduction
Maps created by a ROSA NMS Single User system or ROSA NMS Client system are
stored on the computer the ROSA NMS system is running. To share these maps
between ROSA NMS systems, the maps can be copied from the ROSA NMS system
to the master server. Each ROSA NMS system connected to this master server can
receive these maps.
Fore more information concerning the master server, please refer to topic Defining a
Master Server on page 137.
Copying Maps
The following procedure explains how to copy maps from a client to the master
server or vice versa.
1 In the Map Explorer tree of the ROSA NMS system, right-click on the Maps node
and point to Synchronize with Master... in the short-cut menu.
4014778 Rev H 285

Result: The Map Synchronization dialog is displayed.
Tip: The Map Synchronizing dialog can also be opened by pointing to

Synchronize with Master... menu item in the Maps menu.
2 In the Client Maps or Master Maps tree, select the maps that must be copied.
Tips: To select consecutive maps in the tree, point to the first map, press and
hold down the [SHIFT] key, and point to the last map. To select
non-consecutive maps, press and hold down the [CTRL] key, and click on each
map.
3 Press the < command button (to copy from the client to the master) or >
command button (to copy from the master to the client).
Result: The selected maps appear in the destination tree with a green icon and in
the source tree with blue C.
286 4014778 Rev H

Map Operations
Notes:
When a map is selected containing children and the maps (main map and the
children) are not yet available on the destination, the complete map hierarchy
will be copied.
When one of the selected maps already exists on the destination, the Resolve
map conflict dialog is displayed.
In the What do you want? selection box, point to:

the Overwrite the Master map selection button to overwrite the map on
the master server.
the Merge the client and the master map selection button to merge both
maps.
Note: When several maps exist on the destination, the Resolve map conflict
dialog will display for each map. Pressing the OK for All button will
execute the selected function on each existing map.
When a map is selected containing children and the map hierarchy (main
map and children) is not completely available on the destination, the missing
maps will be added to the destination after an overwrite or merge action.
4014778 Rev H 287

On the destination a linked map is indicated by a blue icon. The map will be
linked from the map on the destination, not from the source.
A copy of a map hierarchy from a source to a destination can never remove

maps from the destination. In our example below, the maps on the Master
were synchronized with the maps on the client. After removing the
Headend A link from headend 1 on the client, the corresponding link on the
Master will be moved to the top level after copying the Region 1 map from
the client to the Master.
4 Click on the Synchronize command button.

Result: The maps are copied from the source to the destination.
During the map synchronization process, a progress indicator is displayed
indication the status of the process.
Tip: The Map Synchronization dialog can be closed by pressing the Close command
button.
288 4014778 Rev H

Map Operations
Updating Maps
When maps are changed on a ROSA NMS system, the maps can be updated. The
following procedure describes how to update maps.
2 In the source tree (the Client Maps tree if maps of the Master must be
synchronized with maps of the client or the Master Maps tree if maps of the
client must be synchronized with maps of the Master), select the maps that must
be synchronized.
Tips: To select consecutive maps in the tree, point to the first map, press and
hold down the [SHIFT] key, and point to the last map. To select
non-consecutive maps, press and hold down the [CTRL] key, and click on each
map.
Result: The Resolve map conflict dialog is displayed.
3 In the What do you want? selection box, point to the Overwrite the master map
or Overwrite client map selection button.
4 Press the OK for All command button.
Result: The maps appear in the destination tree with a red cross and a green O
on the map icon to indicate that the maps will be overwritten. In the source
tree, a blue C appears on the map icons.
Result: The maps are updated on the master server.
4014778 Rev H 289

During the map updating process, a progress indicator is displayed indication

the status of the process.
Tip: The dialog can be closed by pressing the Close command button.
Removing Maps from the Master Server

Perform the following procedure to remove maps from the Master server.
Tip: The Map Synchronizing dialog can also be opened by pointing to
Synchronize with Master... menu item in the Maps menu.
2 In the Master Maps tree, select the maps that must be removed.
Tips:
To select consecutive maps in the tree, point to the first map, press and hold
down the [SHIFT] key, and point to the last map. To select non-consecutive
maps, press and hold down the [CTRL] key, and click on each map.
When a map contains children and the children are not selected, only the
selected map will be removed.
Note: Children maps can not be removed without removing the main map.
Result: The maps are removed from the master server.
290 4014778 Rev H

Map Operations
During the map updating process, a progress indicator is displayed indication

the status of the process.
Tip: The dialog can be closed by pressing the Close command button.
Repairing Maps
When the map hierarchy on a ROSA NMS system was corrupted due to a crash of
the ROSA NMS system, maps with their content can be recovered but the map
hierarchy will be lost. Links between maps are removed and all maps are placed
under the map root.
The following procedure explains how to repair maps.
1 Click on Repair Maps in the Maps menu.
2 Click on the Yes command button to start the map repair process or the No
4014778 Rev H 291

Using Map Objects

Using Resources
Introduction
Adding resources to a map can be useful for task configuration by connecting the
resources via relations. The ROSA NMS system also represents the current state of
a resource in a map by changing the appearance of the resource. Since the border
color of the resource icon changes depending on the severity level of the alarm,
maps can also be useful for alarm tracking.
Note: Resources are units, tasks, services, channels and most of the items in the
Server Explorer tree of the ROSA NMS system.
The following table gives a description of each icon appearance.
Appearance Title
The resource is active, functions normally, and all messages are
acknowledged.
The resource type above the icon and the resource name below the
icon are grayed when the server to which the resource belongs is
disconnected.
A cyan colored dot in the upper right corner of the icon indicates a
resource for which the messages are not yet acknowledged.
A red cross in the upper right corner of the icon indicates a demo
unit, a not responding unit, or a unit in local control mode.
A yellow colored square in the lower right corner of the icon

represents a resource provided with a note.
A colored icon border indicates a resource in alarm state. The color

of the border represents the severity of the alarm with the highest
severity.
292 4014778 Rev H

Using Map Objects
Combinations of above appearances are also possible. The following icon

represents a not responding resource in alarm state with one or more
unacknowledged messages and one or more notes.
A tool tip with resource information appears if you pause the cursor on the resource
icon.
Adding Resources to a Map

Introduction
Resources can be added to a map by executing a drag and drop action from the
Server Explorer tree or Group Explorer tree to the map. Units can also be added by
executing a drag and drop action from the Unit dialog to the map. A map can be
populated with resources from different servers.
Note: Maps can only be populated with resources when the ROSA NMS system is
set to Editing mode.
Dragging and Dropping Resources from the Server Explorer or Group Explorer Tree to a Map
The following procedure explains how to drag and drop resources from the Server
Explorer or Group Explorer tree to a map.
1 In the Server Explorer or Group Explorer tree, select the resources that must be
added to a map. To select consecutive resources in the tree, point to the first
resource, press and hold down the [SHIFT] key, and point to the last resource.
To select non-consecutive resources, press and hold down the [CTRL] key, and
click on each resource.
4014778 Rev H 293

2 Drag and drop the selected resources to the map.
Dragging and Dropping Units from the Units Dialog

The following steps explain how to drag and drop units from the Units dialog to a
map.
1 In the Server Explorer or Group Explorer tree, select the server from which units
must be added to a map.
3 In the list box of the Units dialog, select the unit(s) that must be added to the
map. To select consecutive units in the list box, point to the first unit, press and
hold down the [SHIFT] key, and point to the last unit. To select
non-consecutive units, press and hold down the [CTRL] key, and click on each
unit.
4 Drag and drop the units to the map.
294 4014778 Rev H

Using Map Objects
Removing Resources from a Map

The following procedure explains how to remove resources from a map.
1 In the map, select the resources that must be removed from the map. To select
multiple resources, press and hold down the [SHIFT] key and point to each
resource.
2 In the Edit menu, point to Delete.
Result: The resources are removed from the map.
Note: Resources on a map can also be removed by selecting the resources and
pressing the Delete key or right-clicking on a selected resource and pointing to
Delete in the short-cut menu.
Finding the Maps in which a Resource is placed

Perform the following steps to find the map(s) in which a particular resource is
placed.
1 In the Server Explorer or Group Explorer tree, right-click on the resource that
must be located in maps and point to Find in Maps in the short-cut menu.
Result: When the resource is present in one map, the corresponding map will be
opened. When the resource is present in more than one map, the Find resource
in maps dialog is displayed.
2 Select the map and press the Open command button to open the map or the
Changing the Component Layout of Resources

Perform the following steps to change the component layout of a resource.
1 In the map, select the resource(s) for which the component layout should be
changed. To select multiple resources in a map, press and hold down the
[CTRL] key, and point to each resource.
2 Right-click on a selected resource and point to Component Layout... in the
short-cut menu.
4014778 Rev H 295

Result: The Map Component Layout dialog is displayed.
3 Set or clear the appropriate check boxes to indicate the items that must be
displayed in the map.
Note: If on ore more check boxes in the dialog is grayed, the selected resources
have different settings for these items. When such a check box is changed, the
item will change for all selected resources.
Adding Objects Using the Drawing Tools

Introduction
The ROSA NMS system is provided with a number of drawing tools to embellish
maps with shapes. These drawing tools are:
Line tool
Rectangle tool
Round rectangle tool
Ellipse tool
Polygon tool
Arc tool
Bezier tool
Before shapes can be added to a map, the map mode of the ROSA NMS system must
be set to Editing. Once shapes are added to a map, the properties of these shapes
can be adapted. When multiple shapes must be drawn with similar properties,
draw a shape and change the properties of this shape to the desired properties.
Objects drawn now will use these adapted properties. More information
concerning draw properties can be found in Changing the Line or Fill Properties of a
Shape on page 300.
296 4014778 Rev H

Using Map Objects
To Draw Object using the Drawing Tools

Drawing a Line
The following steps explain how to draw a line on a map.
1 Activate the line tool by clicking on Line in the Draw menu. The line tool can
also be activated by pointing to the Line Tool button in the Map Tools toolbar.
Result: The line tool is active. An active line tool is indicated by a pressed Line
Tool button in the Map Tools toolbar.
2 Move the cursor where the line must start and press and hold down the mouse
button.
3 Drag the cursor to the end point and release the mouse button.
Drawing a Rectangle
Perform the following steps to draw a rectangle on a map.
1 Activate the rectangle tool by clicking on Rectangle in the Draw menu. The
rectangle tool can also be activated by pointing to the Rectangle Tool button in the
Map Tools toolbar.
Result: The rectangle tool is active. An active rectangle tool is indicated by a
pressed Rectangle Tool button in the Map Tools toolbar.
2 Move the cursor where a corner of the rectangle must be positioned and press
and hold down the mouse button.
3 Drag the cursor to position the opposite corner of the rectangle and release the
mouse button.
Drawing a Polygon
The following steps explain how to draw a polygon on a map.
1 Activate the polygon tool by clicking on Polygon in the Draw menu. The
polygon tool can also be activated by clicking on the Polygon Tool button in the
Map Tools toolbar.
Result: The polygon tool is active. An active polygon tool is indicated by a
pressed Polygon Tool button in the Map Tools toolbar.
2 Click on the map where the first corner of the polygon must be positioned.
3 Point to the map to define each side of the polygon.
4 Double-click on the map to define the last corner of the polygon or point to the
first created point of the polygon.
Note: A point of a polygon can be moved by dragging the point handle.
4014778 Rev H 297

Drawing a Rectangle with Rounded Corners

The following procedure explains how to draw a rectangle with rounded corners on
a map.
1 Activate the round rectangle tool by clicking on Round Rectangle in the Draw
menu. The round rectangle tool can also be activated by pointing to the
RoundRect Tool button in the Map Tools toolbar.
Result: The rectangle tool is active. An active rectangle tool is indicated by a
pressed RoundRect Tool button in the Map Tools toolbar.
2 Move the cursor where a corner of the rectangle with rounded corners must be
positioned and press and hold down the mouse button.
3 Drag the cursor to position the opposite corner of the rectangle and release the
mouse button.
Note: When a rectangle with rounded corners is selected in a map, nine handles
appear. The corner radius can be adapted by dragging the inner handle.
Drawing an Ellipse
Perform the following steps to draw an ellipse on a map.
1 Activate the ellipse tool by clicking on Ellipse in the Draw menu. The ellipse
tool can also be activated by clicking on the Ellipse Tool button in the Map Tools
toolbar.
Result: The ellipse tool is active. An active ellipse tool is indicated by a pressed
Ellipse Tool button in the Map Tools toolbar.
2 Move the cursor where a corner of the bounding box of the ellipse must be
positioned and press and hold down the mouse button.
3 Drag the cursor to position the opposite corner of the bounding box of the ellipse
and release the button.
Drawing a Freeform Shape

The following steps explain how to draw a freeform shape on a map.
1 Activate the polygon tool by clicking on Polygon in the Draw menu. The
polygon tool can also be activated by clicking on the Polygon Tool button in the
Map Tools toolbar.
Result: The polygon tool is active. An active polygon tool is indicated by a
pressed Polygon Tool button in the Map Tools toolbar.
2 Move the cursor where the first point of the freeform shape must be positioned
and press and hold down the mouse button.
3 Drag to draw the contour of the freeform shape.
4 Double-click on the map to define the last point of the freeform shape.
298 4014778 Rev H

Using Map Objects
Drawing an Arc
Perform the following steps to draw an arc on a map.
1 Activate the arc tool by clicking on Arc in the Draw menu. The arc tool can also
be activated by clicking on the Arc Tool button in the Map Tools toolbar.
Result: The arc tool is active. An active arc tool is indicated by a pressed Arc
2 Point to the position of the first corner of the bounding box of the ellipse.
3 Point to the position of the opposite corner of the bounding box of the ellipse.
4 Click on the ellipse to define the starting point of the arc.
5 Click on the ellipse to define the ending point of the arc.
Drawing a Bzier Curve

The following procedure explains how to draw a bezier curve on a map.
1 Activate the bezier tool by clicking on Bezier in the Draw menu. The bezier tool
can also be activated by clicking on the Bezier Tool button in the Map Tools
toolbar.
Result: The bezier tool is active. An active bezier tool is indicated by a pressed
Bezier Tool button in the Map Tools toolbar.
2 Click three times to define the three first points of the bezier curve.
Note: You can drag to draw a continuous line.
3 Keep clicking to continuous the bezier curve or double-click on the map to draw
the last point.
Inserting a New OLE Object

An embedded OLE object can be created as a new object. The following steps
explain how to insert a new OLE object.
1 Open a map and set the ROSA NMS system to Editing mode.
2 In the Edit menu, click on Insert New Object....
4014778 Rev H 299

Result: The Insert Object dialog is displayed.
3 In the Object Type list, select the object type that must be created.
4 Set the Display As Icon check box to show the file icon or clear the check box to
show the file content.
Result: After pressing the OK command button, the selected program is started.
Changing the Line or Fill Properties of a Shape

To Change the Line Properties of a Shape
The following procedure explains how to change the line properties of a shape.
1 Select the shape of which the line properties must be changed and point to
Properties... in the Draw menu.
Result: The properties dialog of the selected shape is displayed.
2 In the Width box, select the line weight using the up or down arrow keys in the
box.
3 In the Style drop down box, select the desired style for the line.
Note: The Style drop down box is only applicable for a line.
4 In the Color drop down box, select a predefined color.
300 4014778 Rev H

Using Map Objects
Note: The Color dialog to define custom colors can be displayed by pressing the
Custom command button.

5 Set the Hide check box to hide the line of the shape or clear the check box to
make the line visible.
6 Close the properties dialog by clicking on the exit button in the title bar.
To Change the Fill Properties of a Shape

The following procedure explains how to change the fill properties of a shape.
1 Select the shape of which the fill properties must be changed and point to
Properties... in the Draw menu.
Result: The properties dialog of the selected shape is displayed.
2 Select the Fill tab.
Result: The Fill tab is displayed.
3 In the Style drop down box, select the pattern that should be used to fill the
shape.
4014778 Rev H 301


Adding Text to a Map

To Add Text to a Map
The following procedure describes how to add text to a map.
Note: Before shapes can be added to maps, the map mode of the ROSA NMS system
must be set to Editing.
1 Activate the Text tool by clicking on Text in the Draw menu. The text tool can
also be activated by pointing to the Text Tool button in the Map Tools toolbar.
Result: The text tool is active. An active text tool is indicated by a pressed Text
2 Click on the map where the text box must be positioned.
Result: The Draw Text dialog is displayed.
3 Enter the text in the Text box and press the OK command button.
Result: The text box containing the entered text is added to the map.
302 4014778 Rev H

Using Map Objects
Notes:
If a text box is selected, 8 handles appears around the box. These handles can be
used to resize the text box.
When a text box is resized to a size in which the text can not longer be displayed,
the font size of this text will automatically be changed to a smaller value.
Changing Text
Perform the following steps to change a text in a text box.
1 In the map, select the text box.
2 Point to Properties... in the Object menu.
Result: The Text Properties dialog is displayed.
3 Select the Text tab.
Result: The Text tab is displayed.
4 In the Text box, adapt the text.

Changing Text Properties
To Change the Properties of the Text Box

The following procedure explains how to change the line and fill properties of the
text box.
1 In the map, select the text box of which text box properties should be changed.
3 Select the Line tab.
Result: The Line tab is displayed.
4014778 Rev H 303

4 In the Width box, select the line weight for the text box border using the up or
down arrow keys in the box.
5 In the Color drop down box, select a predefined color for the text box border.

6 Set the Hide check box to hide the text box border or clear the check box to make
the line visible.
7 Select the Fill tab.
Result: The Fill tab is displayed.
8 In the Style drop down box, select the pattern that should be used to fill the text
box.
9 In the Color drop down box, select a predefined color that should be used to fill
the text box.
304 4014778 Rev H

Using Map Objects
To Change the Font

The following procedure describes how to change the font, font style, size, effect,
and script of a text in a text box.
1 In the map, select the text box of which the font should be changed.
4 Click on the Choose command button.

Result: The Font dialog is displayed.
5 In the Font list box, select the font type.

6 In the Font style list box, select the font style.
7 In the Size list box, select the font size.
8 In the Effects box, tick the Strikeout check box to strike through the text and tick
the Underline check box to underline the text.
9 Select the color for the text in the Color drop down box.
Note: The text color can also be changed on the Text tab of the Text Properties
dialog.
4014778 Rev H 305

10 In the Script drop down box, select the font subset.

Note: Not all font types have multiple font subsets.
11 Press the OK command button to confirm the changes or the Cancel command
To Change the Text Alignment

The following steps describe how to change the text alignment in a text box.
1 In the map, select the text box for which the text alignment should be changed.
3 Select the Align tab.
Result: The Align tab is displayed.
4 In the Horizontal drop down box, select the horizontal alignment for the text in
the text box.
5 In the Vertical drop down box, select the vertical alignment for the text in the
text box.
Using Bitmap Illustrations

Introduction
The ROSA NMS system allows importing bitmap pictures to embellishing maps.
Only bitmap type pictures (extension: .bmp) can be imported.
To Add Bitmap Pictures to a Map

The following procedure explains how to add a bitmap picture to a map.
1 Open the map and set the ROSA NMS system to Editing mode.
2 In the Draw menu, point to Bitmap or point to the Bitmap button on the Map
Tools toolbar.
3 Click on the map to indicate the upper left corner of the bitmap illustration.
306 4014778 Rev H

Using Map Objects
4 Browse to the folder containing the bitmap file that should be imported on the
map.
5 Select the bitmap file and click on the Open command button to confirm or the
Result: The bitmap picture is copied on the map. The original bitmap file can be
deleted without deleting the picture in the map.
Resizing a Bitmap Picture

A bitmap picture can be resized using its handles or the picture can be given the
same size as another picture.
Resizing a Bitmap Picture using the Image Properties Dialog

The following procedure explains how to resize a bitmap picture using the Image
Properties dialog.
2 Right-click on the bitmap picture and point to Properties... in the short-cut menu.
Result: The Image Properties dialog is displayed.
3 Point to the Custom selection button.

4 In the Custom boxes, specify the horizontal and vertical dimension in pixels.
4014778 Rev H 307

5 To keep the original aspect ration of the bitmap picture, set the Maintain aspect
ratio check box. When the Maintain aspect ratio check box is set, only the
horizontal or vertical dimension should be entered.
6 Press the Apply command button.
Note: Press the Exit button in the title bar to close the dialog.
Resetting the Size of a Bitmap Picture to its Original Size

Perform the following steps to reset the size of a bitmap picture to its original size.
2 Right-click on the bitmap picture and point to Properties... in the short-cut menu.
Result: The Image Properties dialog is displayed.
3 Point to the Original Size selection button and press the Apply command
button.
Note: Press the Exit button in the title bar to close the dialog.
308 4014778 Rev H

Using Map Objects
Embedding OLE Objects

Introduction
The ROSA NMS system acts as an OLE container application. ROSA NMS maps
can thus be populated with OLE objects. Once an OLE object is added to a map, the
object can be opened with the corresponding application by double-clicking on the
object.
The following picture shows a chart of a Microsoft Excel document into a ROSA
NMS map.
Embedding an OLE Object

OLE object can be added to a map in different ways.
Embedding OLE Objects from a File

The following procedure explains how to embed an OLE object from an OLE server
application.
2 In the OLE server application, select the object and point to the Copy button.
3 In the ROSA NMS system, right-click on the background of the map and point to
Paste in the short-cut menu.
Tip: The selected object can also be embedded using a drag and drop action.
4014778 Rev H 309

Embedding an OLE Object by Importing a File

New objects can be embedded by importing a file. The following steps explain how
to insert an OLE object.
1 Open a map and set the ROSA NMS system to Editing mode.
2 In the Edit menu, click on Insert New Object....
Result: The Insert Object dialog is displayed.
3 Point to the Create from File selection button.
4 In the File box, type the file path or click on the Browse command button to
locate the file.
5 Set the Link check box to keep the document embedded in the ROSA NMS
system up-to-date with the original.
Note: The link properties can always be changed afterwards.
6 Set the Display As Icon check box to show the file icon or clear the check box to
show the file content.
7 Click the OK command button to insert the object or the Cancel command
Tip: An OLE object can also be inserted by dragging the file from the Windows
Explorer and dropping them into a map.
310 4014778 Rev H

Using Map Objects
Editing OLE Objects

Once an OLE object is embedded into a ROSA NMS map, this object can be edited
without leaving the ROSA NMS system by loading the OLE server application in
background or in foreground.
When the OLE server application is opened in background, both the toolbars and
menu bar of the ROSA NMS user interface are replaced by the menu and toolbars of
the OLE server application.
The following procedure explains how to edit an OLE object with the OLE server
application in background.
1 In the map, select the embedded OLE object.
2 In the Edit menu, point to the OLE object menu item and click on Edit.
Result: The OLE server application is opened in background.

The following procedure explains how to edit an OLE object with the OLE server
application in foreground.
1 In the map, select the embedded OLE object.
4014778 Rev H 311

2 In the Edit menu, point to the OLE object menu item and click on Open.
Result: The OLE object is opened using the corresponding application.
Editing the Linked OLE Object

Opening a Linked OLE Object via the Links dialog
The following procedure explains how to open a linked OLE object using the Links
dialog.
2 In the Edit menu, point to Links....
Result: The Links dialog is displayed.
3 In the Links list box, select the link that must be opened and press the Open
Source command button.
Result: The linked OLE object is opened using the corresponding application.
Tip: The Links dialog can be closed by pressing the Exit button in the title bar.
312 4014778 Rev H

Using Map Objects
Changing the Source File of an Linked OLE Object

The following procedure explains how to change the source file of a linked OLE
object.
3 In the Links list box, select the link for the linked OLE object for which the
source file should be changed and point to the Change Source... command
button.
Result: The Change Source dialog is displayed.
4 In the Change Source dialog, browse to the location of the desired source file.
5 Select the new source file and point to the OK command button to confirm or the
Tip: The Change Source dialog can be closed by pressing the Exit button in the title
bar.
Breaking the Link of Linked OLE Objects

The following procedure explains how to break the link of one or more linked OLE
objects.
4014778 Rev H 313


3 In the Links list box, select the link(s) that must be broken. To select
consecutive links in the list box, point to the first link, press and hold down the
[SHIFT] key, and point to the last link. To select non-consecutive links, press
and hold down the [CTRL] key, and click on each link.
4 Press the Break Link command button.
the operation.
Note: The Change Source dialog can be closed by pressing the Cancel command
button.
Changing the Update Settings of Linked OLE Objects

Each time a map is opened, the linked OLE objects on the map are updated
automatically. This feature can be switched off by setting the update mode to
manual. For each linked OLE object, the update mode is indicated in the Update
column.
The following steps explain how to change the update mode for linked OLE objects.
3 In the Links list box, select the link(s) for which the update mode must be
changed. To select consecutive links in the list box, point to the first link, press
and hold down the [SHIFT] key, and point to the last link. To select
non-consecutive links, press and hold down the [CTRL] key, and click on each
link.
4 Point to the Automatic or to the Manual selection button to set the update mode
to automatic or to manual.
Tip: The Change Source dialog can be closed by pressing the Cancel command
button.
Performs a Linked OLE Object Update Manually

When the update setting of linked OLE object is set to manually, the OLE object can
be updated manually. Perform the following steps to update a linked OLE object
manually.
314 4014778 Rev H

Using Map Objects
3 In the Links list box, select the link(s) that must be updated. To select
consecutive links in the list box, point to the first link, press and hold down the
[SHIFT] key, and point to the last link. To select non-consecutive links, press
and hold down the [CTRL] key, and click on each link.
4 Press the Update Now command button.
Note: The Change Source dialog can be closed by pressing the Cancel command
button.
Using Map Links

Introduction
Via map links, it is easily to navigate the maps when the ROSA NMS system is in
Operational mode. By double-clicking on a map link, or right-clicking on the map
link and then pointing to Open map in the short-cut menu, the corresponding map
is displayed.
Map links are also useful to track alarms. The color of the map link represents the
highest alarm level of all resources in the linked map and in all its sub maps.
The Message Viewer dialog containing the messages of all resources in maps and
sub maps can be opened by right-clicking on the corresponding map link and
selecting the desired message category in the short-cut menu. More information
concerning messages can be found in chapter Working with Messages on page 203.
Adding a Map Link

Adding a link to a new or an existing map can be done in two ways.
In the Map Explorer tree. For more information, please refer to topic Creating a
Sub Map on page 272.
By placing a new map link directly in an existing map, as described in the
following procedure.
Perform the following steps to add a link to a new or an existing map.
1 Set the ROSA NMS system to Editing mode.
2 In the Draw menu, point to Map Link or click on the Map Tool button in the
Map Tools toolbar.
3 Click on the map where the map link must be created.
4014778 Rev H 315

Result: The New/Link Map dialog is displayed
4 In the Map Name box, enter the name of the map and press the OK command
button to confirm or the Cancel command button to about the operation.
After entering a name of a non-existing map and clicking on the OK
command button, a sub map with this name is created and a link to this sub
map is added in the current map.
After entering a name of an existing map and clicking on the OK command
button, a confirmation box is displayed.
Press the Yes command button to confirm or the No command button to

Tip: Instead of entering the name of an existing map in the Map Name box, a list
with existing maps can be displayed by pressing the Link command button. Since
only non-circular links are allowed, not all maps are displayed. Circular links
would make alarm tracking impossible.
316 4014778 Rev H

Using Map Objects
In the displayed Map Name List box, point to the map that must be linked and press
the OK command button to confirm or the Cancel command button to abort the
operation.
Changing the Map Link Appearance

The symbol, line color, text and font properties of a map link icon can be adapted.
Note: Since the fill color of the icon is determined by the alarm status of the
resources in the linked map and the sub maps of this map, the fill color cannot be
changed.
Perform the following steps to change the symbol, line color, and font of a map link
icon.
2 Select the map link and point to Properties... in the Object menu or right-click on
the map link and click on Properties in the short-cut menu.
Result: The Map Link Properties dialog is displayed.
3 Select the Symbol tab.
Result: The Symbol page is displayed.
4 In the Symbol drop down box, select the desired map link symbol.
6 In the Width box, select the line weight using the up or down arrow keys in the
box.
4014778 Rev H 317

Tip: The Color dialog that allows defining custom colors can be displayed by
pressing the Custom command button.

8 Set the Hide check box to hide the line of the border or clear the check box to
make the line visible.
9 Select the Text tab.
Result: The Text tab is displayed.
10 In the Text box, type the text that must be displayed as text indicator for the map
object.
318 4014778 Rev H

Using Map Objects
Tip: The Color dialog that allows defining custom colors can be displayed by
pressing the Custom command button.

12 Select the Font tab.
Result: The Font tab is displayed.
13 Press the Choose command button.
4014778 Rev H 319

Result: The Font dialog is displayed.
14 In the Font list box, select the font type.

15 In the Font style list box, select the font style.
16 In the Size list box, select the font size.
17 In the Effects box, tick the Strikeout check box to strike through the text and tick
the Underline check box to underline the text.
18 Select the color for the text in the Color drop down box.
19 In the Script drop down box, select the font subset.
Note: Not all font types have multiple font subsets.
Deleting a Map Link

Perform the following steps to delete a map link.
2 Select the map link and point to Delete in the Edit menu or right-click on the
map link and click on Delete in the short-cut menu.
Result: The map link is removed from the map.
Tip: A map link can also be removed by selecting the map link and pressing the
<Delete> key.
320 4014778 Rev H

Manipulating Map Objects

Selecting Objects
To activate the selection tool, click on Select in the Draw menu or click on the
Selection Tool button in the Server Tools toolbar, then objects can be selected in
different ways:
To select a single object: click on the object.
To add objects to a selection: press and hold down the [SHIFT] key and click on
the additional object.
To select more than one object at once: drag the pointer to draw a selection
rectangle around the objects that should be selected. All objects included
completely in the selection rectangle are selected.
To select all objects at once: click on Select All in the Edit menu.
Copying and Pasting Objects

Perform the following steps to duplicate an object in a map.
1 In the map, select the object that must be duplicated.
2 Do one of the following actions:
Press and hold down the [CTRL] key while you drag the object to where you
want to copy in the map.
In the Map Tools toolbar, point to respectively the Copy and Paste button.
In the Edit menu, point to respectively Copy and Paste.
Note: During a copy and paste action the Windows Clipboard is used. Only three
types of objects can be copied to and paste from the Clipboard.
ROSA NMS drawing objects: lines, rectangles, ellipses, polygons
Bitmaps: device-independent bitmaps from other applications, such as Paint,
can be copied and pasted into ROSA NMS map documents.
OLE components: ROSA NMS is an OLE container, which means that OLE
server components like Microsoft Excel charts can be copied and pasted into
ROSA NMS maps.
4014778 Rev H 321

Removing Objects
The following steps explain how to remove an object.
1 In the map, select the object(s) that must be removed. To select multiple objects,
select the first object, press and hold down the [SHIFT] key, and point to each
object.
2 Do one of the following actions:
Press the Delete key.
In the Map Tools toolbar, point to the Cut button. The object is moved to
Windows Clipboard. The object can still be pasted in the same map or in
another map.
In the Edit menu, point to Delete.
In the Edit menu, point to Cut. The object is moved to Windows Clipboard.
The object can still be pasted in the same map or in another map.
Resizing Objects
To change the size of an object, drag the handles that appear when the object is
selected.
Perform the following procedure to give two or more objects the same size.
1 In a map, select the object of which the size must be used to resize other objects.
2 Press and hold down the [SHIFT] key and point to each object that must be
resized.
3 Right-click on a selected object, point to Make Same Size in the short-cut menu,
and click on one of the following menu items: Horizontal, Vertical, or Both.
Perform the following procedure to resize object to their original object size.
1 In the map, select the object(s) that must be resized to their original object size.
To select multiple objects, select the first object, press and hold down the [SHIFT]
key, and point to each object.
2 Right-click on a selected object and point to Default Drop Size in the short-cut
menu.
Note: Resizing to their original object size using the Make Same Size command can
only be done for resources (units, tasks...).
322 4014778 Rev H

Moving Objects
The following procedure explains how to move objects in a map.
1 In the map, select the object(s) that must be moved. To select multiple objects,
select the first object, press and hold down the [SHIFT] key, and point to each
object.
2 Drag one of the selected objects to its new position.
Note: Do not drag a selected object using its object handles.
Aligning Objects
Two or more objects can be aligned horizontally or vertically without using the grid.
The following procedure explains how to align multiple objects.
1 In a map, select the object that must be used to align other objects.
2 Press and hold down the [SHIFT] key, and point to each object that must be
aligned.
3 Right-click on a selected object, point to Align in the short cut menu, and click on
one of the following menu items: left, right, top, or bottom.
Changing the Object Drawing Order

The object drawing order determines which objects are drawn in front of or behind
other objects. The initial order is determined by the drawing order. An object
drawn more recently than another object is always in front of the other object.
Perform the following steps to change the drawing order.

1 In a map, right-click on the object, point to Arrange in the short-cut menu, and
click on one of the following menu items.
Forward One: bring the object one position forward in the drawing order
Back One: put the object one position backward in the drawing order
To Front: bring the object to the front of the drawing order. The object will
be drawn in front of any other object, overlapping it
To Back: put the object to the back of the drawing order. Every other object
is drawn in front of it.
4014778 Rev H 323

Grouping and Ungrouping Objects

To manipulate multiple drawing objects as one single object, these objects can be
grouped.
Notes:
Only drawing objects can be grouped and not for example resources.
A group containing other groups can also be created.
The following procedure explains how to group drawing objects.
1 In a map, select the drawing objects that must be grouped. To select multiple
drawing objects in a map, click on the first drawing object, press and hold down
the [SHIFT] key, and point to each other drawing object.
2 In the Object menu, point to Group or right-click on a selected drawing and
click on Group in the short-cut menu.
Result: The selected objects are grouped.
The following procedure explains how to break up a group into its original drawing
objects.
1 In a map, select the group that must be ungrouped.
2 In the Object menu, point to Ungroup or right-click on the group and point to
Ungroup in the short-cut menu.
Result: The selected group is broken up in drawing objects.
Selecting Default Map Object Properties

To select a map object's properties as default map object properties, right-click the
map object and select Set as Default in the short-cut menu.
Ordering Map Objects

Multiple map objects can be sorted numerically or alphabetically in ascending or
descending order.
The following procedure explains how to order multiple map objects.
1 In a map, select the map objects that must be ordered.
2 Right-click on the selected map objects and select Order in the short-cut menu.
324 4014778 Rev H

Result: The Ordering dialog is displayed.
3 In the Sort Algorithm box, tick the Numerical check box to order the map
objects numerically or tick the Alphabetical check box to sort alphabetically.
4 In the Order box, tick the Ascending check box to sort the map objects in
ascending order or Descending check box to sort in descending order.
4014778 Rev H 325

Using Performance Bars

Introduction
Performance bars allow displaying static performance data coming from monitoring
devices, like the FSM 860 Headend Supervisor and LM 850 Network Supervisor, in
maps. These performance bars show the minimum, the maximum, and the average
measured value for a defined performance parameter over a defined period.
Note: A performance bar can be set for any device but the location to which the
device belongs determines what will be used to calculate the bar values.
Adding a Performance Bar to Devices

Perform the following steps to add a performance bar to a device.
Note: To create a performance bar to a device in a map, the ROSA NMS system must
be set to Operational mode. The procedure to set the ROSA NMS system to
Operational mode is described in topic Map Modes on page 265.
1 Right-click on the device to which a performance bar must be added and point to
Performance in the short-cut menu.
Result: The Performance dialog is displayed.
2 In the Parameter drop down box, select a parameter to display in the

performance bar.
326 4014778 Rev H

Note: Select only parameters and items that make sense for the selected device.
The ROSA NMS system does not check if the selected parameters and items are
relevant for the particular device.
For example: if you have selected a Pulsar TV Modulator, you can select the
Vision Carrier level parameter (measured by an FSM 860 or and LM 860) and
also the channel (item) that corresponds to this modulator.
If you have selected a FSM 860 or a LM 860 device, you could select one of the
parameters it is measuring and also the channel (items) it measures on.
3 In the Items list box, select the item(s) from which the performance data must
come. To select consecutive items in the list box, point to the first item, press
and hold down the [SHIFT] key, and point to the last item. To select
non-consecutive items, press and hold down the [CTRL] key, and click on each
item.
When multiple items are selected, the minimum, average, and maximum values
are derived from the combined data.
4 Select a time range in one of the following ways:
- Define a time window by selecting the unit of time (seconds, minutes, hours,
days, months, years) in the Last drop down box and a duration in the Last
box.
- Define a time window between two dates by selecting the time and date in
the From and To box.
5 In the Color1 and Color2 drop down boxes, select a color for the parts of the bar
above and below the average.
6 Press the Compute command button to confirm or the Cancel command button
Notes:
- If the logging database doesn't contain the requested data for the location the
device belongs to, the following message box is displayed.
Press the OK command button and try again by selecting other parameters.
4014778 Rev H 327

- If data is available, the following message box is displayed after pressing the
Compute command box and computing the bar values.

Result: The performance bar is displayed next to the device.
Notes:
- The performance bar will not be updated automatically when new date
becomes available.
- When the mouse pointer is paused over the performance bar, information
about the bar is displayed.
- For FSM 860 devices monitoring the same items but in a different location,
performance bars can be created for both devices at the same time. The
advantage of this approach is that the bars show differences more clearly that
when the bars are created separately.
Therefore both FSM 860 units must be placed in the same map and the
Performance dialog should be opened when both units are selected. After
specifying the data in the dialog and pressing the Compute command
button, the performance bars appears next to the devices.
328 4014778 Rev H

In the example above, parts of the performance bar next to MyFSM2 are white.
That is because both bars use the same minimum and maximum values, and in this
case, those obtained by MyFSM are used. This shows that MyFSM measured a
lower minimum carrier level on one or more of the measured carriers.
Updating a Performance Bar

The following steps explain how to update a performance bar.
Note: To update a performance bar of a device in a map, the ROSA NMS system
must be set to Operational mode. The procedure to set the ROSA NMS system to
Operational mode is described in topic Map Modes on page 265.
1 Right-click on the device for which the performance bar should be updated and
point to Performance in the short-cut menu.
Result: The Performance dialog is displayed.
2 Click on the Compute command button.
Result: After computing the data, the following message box is displayed.

Result: The performance bar beside the device is updated.
4014778 Rev H 329

13 Chapter 13
Working with Relations
Introduction
This chapter provides information about creating an interconnection
model of services, devices, and channels using the relation feature of
In This Chapter
Introduction ......................................................................................... 332
Using Relations in Maps .................................................................... 333
Using the Relation Dialog.................................................................. 336
4014778 Rev H 331

Chapter 13 Working with Relations
Introduction
In the ROSA NMS system, an interconnection model of the services, devices and
channels in the headend can be created. ROSA NMS tasks like the Digital Headend
Backup task and the Video Analysis task require this model for correct operation.
An interconnection model is built up using relations.
Relations are not necessarily the physical interconnections between the devices.
Some relations are physical relations, like a video output on a receiver connected to a
modulator input. Other relations are so-called logical relations because they do not
represent a physical connection between devices. For example, a relation between
an Analog TV Service and a video input on a router is a logical relation, because only
the router has physical connections.
The easiest way to create a relation between two devices is to draw the relation on a
map. Information concerning relations on maps can be found in topic Using
Relations in Maps on page 333. A second way to create relations is using the
Relation dialog of ROSA NMS. More information concerning the Relation dialog
can be found in topic Using the Relation Dialog on page 336.
332 4014778 Rev H

Using Relations in Maps

Adding Relations
The following steps explain how to add relations in a map.
Notes:
Before relations can be added to a map, the relevant resources should already be
added to the map. For more information concerning maps, please refer to
chapter Working with Maps on page 261.
To create relations on maps, the ROSA NMS Map system must be set to Editing
mode. The procedure to set the ROSA NMS Map system to Editing mode is
described in topic Map Modes on page 265.
1 Activate the relation tool by pointing to Relation in the Draw menu. The
relation tool can also be activated by pointing to the Relation Tool button in the
Map Tools toolbar.
Note: Relations can not be made by using the Line tool.
2 Click on the first resource bitmap of the relation and then on the second resource
bitmap.
Notes:
Make sure to draw the relation in the correct direction! The User's Guides of
the tasks that require relations provide a description of the relations they
need to function correctly.
When the relation between two resources cannot be drawn as a straight line,
corner points can be created by clicking between the resources.
Don't click on the bitmap of any other resource than the one for the relations
end point. Once a relation is added between two devices, the corner points
can be moved to another position but additional corner points cannot be
added.
4014778 Rev H 333

Result: When the resource is selected that has to become the end point of the
relation, the Add Relation dialog is displayed.
3 In the Resources boxes, select the resource ports for the relation that must be
created.
When the relation already exists in the relations database, the relation can be
selected in the Or choose an existing relation list box at the bottom of the dialog.
There can be multiple existing relations in the list, so be careful to select the
relation with the correct ports.
Note: Most relations are created from an output of a start point device to an
input of an end point device, therefore only the output ports are displayed in the
Resource drop down box under the From box and only the input ports in the
Resource drop down box under the To box. When a relation must be created
from an input to an output port, all ports can be made visible in the Resource
drop down boxes by setting the Show all pins check box.
4 Press the Add command button to add the relation or the Cancel command
Checking the Properties of a Relation

The following procedure explains how to check the properties of a relation.
1 Select the relation representation line between the devices.
334 4014778 Rev H

Result: The Relation Properties dialog is displayed.
The Relation Properties dialog of a relation can also be opened by right-clicking

on the relation representation line and pointing to Properties... in the short-cut
menu.
The following information is displayed.
Type: represents the relation type, Physical or Logical relation
From: the port of the start point device of the relation
To: the port of the end point device of the relation
Note: On the Look tab of the Relation Properties dialog the weight of the relation
representation line on the map can be changed.
Removing a Relation from a Map

When many relations are making the map unclear, relation lines can be deleted from
a map without deleting the actual relations in the database. The tasks requiring the
relation will still function. A relation can also be deleted completely; in the map as
well as in the database. What happens when deleting a relation in a map depends
on the Map Options settings, for more information concerning the map options,
please refer to topic Setting the Map Options on page 266.
Perform the following steps to delete relations in a map.
1 Select the relation that must be removed and point to Delete in the Edit menu.
2 Click on the Yes command button to remove the relation from the map and
database, point to the No command button to remove the relation representation
line from the map, or the Cancel command button to abort the operation.
4014778 Rev H 335

Using the Relation Dialog

About the Relation Dialog
All relations between devices of a particular server are displayed on the Relation
dialog of the ROSA NMS system. The Relation dialog allows adding, deleting, and
printing relations. The following picture shows a Relation dialog.
In the Relation dialog each relations is accompanied with the following information:
From Resource: the name of the start point resource. This column is also
provided with an icon indicating the relation type. The table below describes
the relation icons.
From Location: the location of the start point resource
From Pin Name: the name of the start point port
To Pin Name: the name of the end point port
To Resource: the name of the end point resource
To Location: the location of the end point resource
Icon Relation Type

Physical relation
Logical relation
336 4014778 Rev H

The Relations dialog is provided with a filter that can be used to reduce the number
of relations displayed in the list box. In the upper right corner of the Relations
dialog, a counter is foreseen to indicate the number of relations displayed in the list
box.
Adding Relations
The following procedure explains how to add a relation using the Relation dialog.
the server for which a relation must be added between resources.
2 Click on Relations... in the Config menu.
Result: The Relations dialog is displayed.

Result: The Add Relations dialog is displayed.
4 Complete the following parameters in the From box for the start point resource
of the relation.
In the Driver drop down box, select the driver.
In the Instance drop down box, select the instance. The Instance drop down
box contains the instances using the selected driver.
4014778 Rev H 337

In the Resource drop down box, select the resource port.

5 Complete the following parameters in the To box for the end point resource of
the relation.
In the Driver drop down box, select the driver.
In the Instance drop down box, select the instance. The Instance drop down
box contains the instances using the selected driver.
In the Resource drop down box, select the resource port.
Notes:
The relation between the start point resource end the end point resource
should be made in the correct sense.
Most relations are created from an output of a device to an input of a device,
therefore only the output ports are displayed in the Resource drop down box
under the From box and only the input ports in the Resource drop down box
under the To box. When a relation must be created from an input to an
output port, all ports can be made visible in the Resource drop down boxes
by setting the Show all pins check box.
7 Continue adding relations and click on the Close command button when
finished.
Result: The added relations appear in the Relations dialog, but they are not
added in a map.
Removing Relations Using the Relations Dialog

Perform the following steps to remove one or more relations using the Relations
dialog.
the server for which relations must be removed.
338 4014778 Rev H

3 In the list box of the Relations dialog, select the relation(s) that must be removed.
To select consecutive relations in the list box, click on the first relation, press and
hold down the [SHIFT] key, and click on the last relation. To select
non-consecutive relations, press and hold down the [CTRL] key, and point to
each relation.
Note: When there are a lot of relations in the list box, it can be difficult to find a
particular relation. Therefore a filter can be configured to reduce the number of
relations in the list box. More information concerning the filter can be found in
4 Press the Remove command button to remove the selected relations.
Note: The dialog can be closed by pressing the Close command button.
Printing Relations
The following procedure explains how to print a list with relations.
the server for which relations must be printed.
3 In the list box of the Relations dialog, select the relation(s) that must be printed.
To select consecutive relations in the list box, click on the first relation, press and
hold down the [SHIFT] key, and click on the last relation. To select
non-consecutive relations, press and hold down the [CTRL] key, and point to
each relation.
4014778 Rev H 339

Note: When there are a lot of relations in the list box, it can be difficult to find a
particular relation. Therefore a filter can be configured to reduce the number of
relations in the list box. More information concerning the filter can be found in

selected relations or the All selection button to print all relations.
on page 44.

When there are too many relations in the list box of the Relations dialog, a filter can
be configured to filter these relations. The following procedure explains how to
configure the relation filter for the Relations dialog.
the server for which relations in the Relations dialog must be filtered.
340 4014778 Rev H


one or more values
Note: As long as the OK button is not pressed, the previous filter can be restored
by pressing the Restore previous... command button.
4014778 Rev H 341

14 Chapter 14
Performance Monitoring
Introduction
This chapter describes how to generate demo quality data for
performance monitoring, how to add availability data and how to
delete data from the performance database of the ROSA NMS system.
In This Chapter
Introduction ......................................................................................... 344
Opening Reporting Component ....................................................... 346
Generating Demo Quality Data ........................................................ 347
Adding Availability Data .................................................................. 349
Deleting Quality Data ........................................................................ 351
4014778 Rev H 343

Chapter 14 Performance Monitoring
Introduction
The monitoring equipment in a heading and network can periodically log a wide
variety of performance measurements in the performance database of the ROSA
NMS system. Using this data, graphs and text reports can be created to analyze the
system performance and drive preventive maintenance actions by focusing on the
weakest part of the network.
Graphs can also be created showing a long-term overview of all services, as well as
detailed graphs of the last measurements on a particular service. This approach
makes it easy to detect problems before customers notice them and to pinpoint
problems in large systems.
Availability graphs and text reports are based on alarm messages generated by the
measuring equipment or by individual devices. The difference with periodic data is
that an alarm message is generated and logged instantaneously, while periodic data
is measured over an interval. Availability graphs shows exactly when something
went wrong or became good again. Quality graphs are more or less detailed
depending on the measurement interval.
The ROSA NMS Single user as well as the ROSA NMS Client is default provided
with the Reporting Component that can be used to create these graphs and reports.
The following picture shows a graphs created by this component.
344 4014778 Rev H

Introduction
Detailed information concerning this performance monitoring can be found in the

Reporting Users Guide - Component Driver for ROSA NMS.
The procedures in this chapter describes how to generate demo quality data that can
be used for practicing the Reporting Component, how to add availability data and
how to delete data from the performance database.
4014778 Rev H 345

Opening Reporting Component

The following procedure explains how to open the user interface of the Reporting
Component.
the server for which graphs or reports must be created.
2 Point to Graphs... in the Performance menu.
Result: The user interface of the Reporting Component is displayed.
Detailed information concerning the Reporting Component can be found in the

Reporting Users Guide - Component Driver for ROSA NMS.
346 4014778 Rev H

Generating Demo Quality Data
Generating Demo Quality Data

Introduction
The ROSA NMS system allows making quality graphs and report without having
any real quality data. Therefore demo quality data can be generated for the vision
carrier and vision carrier availability parameters. The ROSA NMS system is able to
generate four new locations, Paris, New York, Rome and Sydney. Performance
samples for fourteen different programs over the last week are added to the
performance database. For the vision carrier, there will be a quality drop in one
location for one program. The vision carrier will also be unavailable for one
program in one location.
To Generate Demo Quality Data

Perform the following procedure to generate demo data.
the server for which demo data must be generated.
2 In the Performance menu, point to Generate Demo Data....
Result: The Generate Quality Demo Data dialog is displayed.
3 Press the Generate command button.

Notes:
4014778 Rev H 347

During the data generating process a progress indicator is displayed.
The data generation process can always be stopped by pressing the Stop
command button.
When the demo data is created successfully, the following dialog is
displayed.

5 Close the Generate Quality Demo Data dialog by pressing the Close command
button.
348 4014778 Rev H

Adding Availability Data
Adding Availability Data

Introduction
When an availability graph or report must be created, the ROSA NMS system
requires the knowledge of the initial state or condition of the following data:
The measured parameter
The nominal level
The minor and major upper alarm limits
The minor and major lower alarm limits
The condition at that time.
If there is no availability data before the selected starting date and time, the initial
state of the parameter must be defined.
To Add Availability Data

Perform the following steps to enter the initial availability data.
1 In the Performance menu of the ROSA NMS system, click on Availability
Data....
Result: The Add Availability Data dialog is displayed.
2 In the Parameter drop down box, select an availability parameter.
4014778 Rev H 349

Note: The Parameter drop down lists the parameters for which data is present in
the ROSA NMS database.
3 In the Locations list box, select the locations.
Tips:
To select multiple consecutive locations in the list box, click on the first
location, press and hold down the [SHIFT] key, and point to the last location.
To select non-consecutive locations, press and hold down the [CTRL] key,
and point to each location.
All locations can be selected by pressing the All command button.
4 In the Items list box, select one or more items.
Tips:
To select multiple consecutive items in the list box, click on the first item,
press and hold down the [SHIFT] key, and point to the last item. To select
non-consecutive items, press and hold down the [CTRL] key, and point to
each item.
All items can be selected by pressing the All command button.
A new item can be created by entering a name in the Name box on the New
Item dialog that appears after pressing the New command button.
Once the name is entered, pressing the Add command button creates a new
item.
5 In the Limits box, enter the nominal level and the minor and major limits for the
initial state.
If the ROSA NMS system finds existing values for these parameters in the quality
database, the ROSA NMS system will suggest these values as the limits.
Note: Not all limits are available for all parameters.
6 In the Condition selection box, select the initial alarm state.
7 In the Date/Time box, set the initial state date and time.
8 Click on the Add command button to confirm or the Close command button to
350 4014778 Rev H

Deleting Quality Data
Deleting Quality Data

The following procedure explains how to delete quality data from the performance
database.
the server for which data must be removed from the database.
2 In the Performance menu, point to Remove Data....
Result: The Delete Quality Data dialog is displayed.
3 In the Parameter drop down box, select the parameter for which data must be
removed.
4 In the Locations list box, select the location(s) for which data must be removed.
Tips:
To select multiple consecutive locations in the list box, point to the first
location, press and hold down the [SHIFT] key, and point to the last location.
To select non-consecutive locations, press and hold down the [CTRL] key,
and click on each location.
All locations can be selected by pressing the All command button.
5 In the Items list box, select the item(s) for which data must be removed.
Tips:
To select multiple consecutive items in the list box, point to the first item,
press and hold down the [SHIFT] key, and point to the last item. To select
non-consecutive items, press and hold down the [CTRL] key, and click on
each item.
4014778 Rev H 351

All items can be selected by pressing the All command button.

6 Set the From and To date and times for the data that must be removed.
7 Point to the Delete command button.
352 4014778 Rev H

15 Chapter 15
ROSA NMS System Security
Introduction
The ROSA/Copernicus software features an enhanced and expanded
security management system based on users and users groups
available for each individual server. A user can have the same rights
on different servers or can have different rights.
In This Chapter
Using Security Group......................................................................... 354
ROSA NMS Users ............................................................................... 362
Exporting and Importing Security Settings .................................... 368
Map Security........................................................................................ 373
Setting the Minimum Password Length.......................................... 377
4014778 Rev H 353

Chapter 15 ROSA NMS System Security
Using Security Group

Creating a New Security Group
The following procedure explains how to create a new security group.
new security group must be created.
Note: The ROSA NMS system should be connected to the server for which a new
security group must be created.
2 In the Security menu, point to Groups...
Result: The Security Groups dialog is displayed.
3 Press the New command button.
354 4014778 Rev H

Result: The New Security Group dialog is displayed.
4 In the Name box, enter the name for the new security group.
5 In the Description box, enter a small description for the new security group.
6 In the Security Actions list box, select an action and click on the Allow
command button.
By default, all security actions are disallowed for a new security group.
Members of a security group are only allowed to do the actions for which the
Allowed column in the Security Actions list box shows Yes.
Notes:
The allowed status of a security action can also be changed by
double-clicking on the security action row in the Security Actions list box.
Security actions indicated by a green key in the Security Actions list box can
be linked to specific resources.
7 For an action with a green key, point to the More detailed... command button.
For an action with a yellow key, proceed with step 11.
4014778 Rev H 355

Result: The Security Group Properties dialog displays the list of resources for
which the action can be allowed or disallowed. The corresponding action is
indicated in the Properties box.
8 In the Allowed for selection box, point to All resource except... selection button
or to the No resource except... selection button.
9 Select the resources in the Other resources list box and point to the << command
button to add resources or select the resources in the ...these resources list box
and point to the >> command button to remove resources from the ...these
resources list box.
Notes:
By moving resources to the ...these resources list box, the action on these
resources are allowed or disallowed depending on the selection in the
Allowed for selection box (All resource except... selection button or No
resource except... selection button).
In both the Other resources list box and the ...these resources list box,
multiple resources can be selected. To select consecutive resources, click on
the first resource, press and hold down the [SHIFT] key, and then click on the
last resource. To select resources that are not consecutive, press and hold
down the [CRTL] key, and point to each resource.
356 4014778 Rev H

More information concerning the security actions can be found in sub topic
Security Actions Overview further in this topic.
When the server has many resources on different locations, the resources in
both list boxes can be filtered on location basis. To filter the resources on a
particular location, tick the Filter on location basis check box and select the
corresponding location in the list box below the check box.
10 Click on the OK command button to confirm the operation or the Cancel
Result: the Security Group Properties dialog is closed.
11 After allowing and disallowing security actions, click on the OK command
button to create the new group or the Cancel command button to abort the
operation.
Result: The new group is added to the Security Groups dialog.
12 Press the Close command button to close the Security Groups dialog.
Changing User Group Properties

Perform the following steps to change the properties of a user group.
security group must be changed.
Note: The ROSA NMS system should be connected to the server for which a
security group must be changed.
3 Select the security group of which properties must be changed and point to the
Properties... command button.
4014778 Rev H 357

Result: The Security Group Properties dialog with the properties of the selected
security group is displayed.
Note:
The Security Group Properties dialog can also be opened by double-clicking
on the security group in question.
On the Security Group Properties dialog, the properties of another security
group can be chosen by selecting the security group in the Security Group
drop down box.
4 The name or description of the security group can be changed in the Properties
box.
Note: It is not allowed to change the name of the Administrators security group.
5 In the Security Actions list box, allow or disallow a security action by selecting
the action and pointing to the Allow or Disallow command button.
6 For security actions indicated by a green key, open the Security Group
Properties dialog by pointing to the More detailed... command button.
Add resources to the ...these resources list box by selecting resources in the
Other resources list box and pointing to the << command button.
Remove resources from the ..these resources list box by selecting resources
and pointing to the >> command button.
358 4014778 Rev H


7 On the Security Group Properties dialog, press the OK command button to
confirm or the Cancel command button to abort the operation.
Removing a Security Group

The following procedure explains how to remove a security group.
1 In the Server Explorer of the ROSA NMS system, select the server of which a
security group must be deleted.
Note: The ROSA NMS system should be connected to the server for which a
security group must be deleted.
3 Select the security group that must be removed and point to the Remove
command button.
the operation.
Note:
After a security group removal action, the users member of the group are not
removed.
4014778 Rev H 359

It is not allowed to remove the pre-defined administrator security group. After

removing the pre-defined operators or technicians security group, these security
groups will automatically be added again when the server is restarted.
Security Actions Overview

The following table gives an overview of the standard security actions in ROSA
NMS. When installing drivers, additional actions may become available.
Class Action If enabled, you can...

Server Explorer Configuration Set a server to Master in the Explorer
Work with unit folders
Full View Expand the server node in the Explorer
Messages Viewer Layout Change the Message Viewer Layout
Options Change the Message Options
Viewing/enabling message rules
View View messages in the Message Viewers
View messages in the ROSA NMS Status bar
Acknowledge Acknowledge messages
Edit Attachment Add and edit message attachments
Delete Delete messages
Reset Pending Reset pending messages
Log New Message Manually log messages for a ROSA NMS resource
Configure Adding, modifying, or removing predefined message filters
Predefined Message
Filters
Protocol Drivers Adapt Scan Ranges Add, edit and remove scan ranges for the installed protocol
drivers
Map New Units Map ROSA NMS resources to new units for the installed
protocol drivers
Quality View Create performance graphs and reports
Manage Save and remove graphs
Remove data, generate demo-data and add availability data
Resource Logging in Open the user interface of a resource
General Apply settings to resources by clicking on the Apply button
configuration on the GUI
Start and stop tasks
Limited To do limited configuration on certain type of resources, for
Configuration example ROSA EM devices.
Message Change the message configuration on the Message tab of a
configuration resource GUI
Scheduler State Stop and start the scheduler of resources that have scheduler
functionality
360 4014778 Rev H

Class Action If enabled, you can...

Measure Action Do manual measurements using measurement devices such
as the LM 860 or FSM 860
Manage Control Set a unit to local or remote control
Advanced Reset all device addresses from the CCU GUI
Operations Activate the test mode page on the CCU GUI
Activate the pilot generator on the Netsense II GUI
RF Configuration Make changes on the RF settings pages of certain GUIs
IF Configuration Make changes on the IF settings pages of certain GUIs
Server Configuration Change the computer name of a server
Change the network settings
Change the administrative user password
Change the server options
Reinitialize alarm correlation domains (button in the dialog)
Service Model Create relations and change service priorities.
Configuration
Set Time Set or synchronize the server date and time
State Management Stop and reboot servers
Serial Port Settings Configure the serial ports of a server
Device Model Make tasks
Configuration Add, edit and remove units
Configure unit I/O ports
Change unit settings in the Server Explorer
Create unit groups
Add, edit and remove locations
Modules installation Install and uninstall bitmaps
Install drivers
Install a license file
Install new software on a server via ROSA NMS
Synchronizing Maps Synchronize maps (to synchronize the master maps, the
action Updating Master Maps must be allowed, to synchronize
the local maps, you must have edit rights on the individual
maps)
Inventory Synchronize the global inventory in the Server Explorer
Updating Master Update the inventory on the master
Inventory
Updating Master Update the maps on the master
Maps
Note: The security actions of the class Synchronizing must be disabled or enabled on
the master server.
4014778 Rev H 361

ROSA NMS Users

Creating Users
The following procedure explains how to create a new user.
1 In the Server Explorer of the ROSA NMS system, select the server of which a
new user must be created.
Note: The ROSA NMS system should be connected to the server for which a new
user must be created.
2 In the Security menu, point to Users...
Result: The Users dialog is displayed.
3 Click on the New... command button.

Result: The New User dialog is displayed.
362 4014778 Rev H

ROSA NMS Users
4 In the User ID box, enter the user ID for the new user.
Note: The user has to enter this user ID during the connection making process to
a server.
5 In the Full Name box, enter the full name of the user.
6 In the Password and Confirm box, enter a password for this user.
Note: During the connection making process, this password should be entered.
7 Assign the user to one or more security groups by selecting the group(s) in the
Other Groups list box and clicking on the << command button.
Result: The security group(s) is (are) added to the Member of Groups list box.
Note:
To select consecutive security groups, click on the first group, press and hold
down the [SHIFT] key, and then click on the last group. To select security
groups that are not consecutive, press and hold down the [CRTL] key, and
click on each group.
Security groups can be removed from the Member of Groups list box by
selecting the groups in the Member of Groups list and pointing to the >>
command button.
Result: The New User dialog is closed.
Note: When no security groups are assigned to a user, the following message box
appears.
Press the Yes command button to confirm or the No command button to return
to the User Properties dialog.
A user that is not assigned to a security group has no rights.
9 Press the Close command button to close the Users dialog.
Changing User Properties

The following steps explain how to change the properties of a user.
1 In the Server Explorer of the ROSA NMS system, select the server for which user
properties must be changed.
Note: The ROSA NMS system should be connected to the server.
4014778 Rev H 363


3 In the Users list box, select the user of which properties must be changed and
press the Properties command button.
Result: The User Properties dialog is displayed.
4 Change the user ID in the User ID box.

Note: The user ID of the pre-defined Administrator user cannot be changed.
5 Enter a new password in the Password and Confirm box.
6 Assign the user to a security group by selecting the group in the Other Groups
list box and pointing to the << command button or remove the user from a
security group by selecting the group in the Member of Groups list box and
clicking on the >> command button.
Note: The Administrators group cannot be removed from the pre-defined
Administrator user.
Note: When no security groups are assigned to a user, the following message box
appears.
Press the Yes command button to confirm or the No command button to return
to the User Properties dialog.
364 4014778 Rev H

ROSA NMS Users
A user that is not assigned to a security group has no rights.

8 Click on the OK command button to close the Users dialog.
Removing Users
Perform the following steps to remove a user.
1 In the Server Explorer of the ROSA NMS system, select the server of which users
must be removed.
Note: The ROSA NMS system should be connected to the server.
3 In the Users list box, select the user(s) that should be removed. To select
consecutive users, click on the first user, press and hold down the [SHIFT] key,
and then click on the last user. To select users that are not consecutive, press
and hold down the [CTRL] key, and click on each user.
4 Point to the Remove command button.
Result: The user(s) is (are) removed.
Note: The pre-defined Administrator user cannot be removed.
5 Press the Close command button to close the Users dialog.
Changing Active User

Perform the following steps to change the active user of a server.
the active user should be changed.
2 In the Security menu, point to Change User....
4014778 Rev H 365

Result: The Change active user dialog is displayed.
3 In the User ID box, enter the user ID of the user.

4 In the Password box, type the password of the user.
Note: When wrong user ID parameters are entered, the following message box is
displayed after pressing the OK command button.
Changing a User Password

The following procedure describes how to change the password of a user.
Note: You can only change the password of a user if you are logged on to a server
with this user.
the password of the active user should be changed.
2 In the Security menu, point to Change Password....
366 4014778 Rev H

ROSA NMS Users
Note: The user ID of the active user is displayed in the User ID box.
3 If you are connected to multiple servers with this user ID, tick the Change my
password on all connected servers check box to change the password of this
user ID on all connected servers.
4 In the Old Password box, enter the current password.
5 In the New Password and Confirm box, enter the new password
Result: A message box appears when the password is changed successfully.
4014778 Rev H 367

Exporting and Importing Security Settings

Introduction
When multiple systems used by the same person must be configured, the security
can be defined on one system and copied to the other systems. First the security
settings must be exported from the configured system to a file. Then the file with
security settings must be imported by the other systems.
Important: Exporting users should not be used to copy users between existing
groups on different systems. Not only the user is exported, but also the settings of
the users group. When importing this user, the group settings are overwritten.
This may cause undesired changes in security settings for actions that are allowed or
disallowed for specific resources. New users have to be created on each system
individually, unless they belong to a new group. Then you can export and import
that group.
Note: Only members of the Administrators security group can export and import
security settings.
The following security settings can be exported or imported.
Users (with the group they belong to and the settings of the group)
Groups (with all settings, but without users)
Security options (minimum password length)
Note: Security groups may have security actions that are allowed or disallowed for
specific resources. These resources are not always available on other systems on
which the security settings should be imported. Then, detailed settings are changed
as follows:
Actions allowed for all resources except those specific become allowed for all
resources.
Actions allowed for no resources except those specified become disallowed for
all resources.
Then they can be allowed or disallowed for the specific resources in the other
systems.
Exporting all Security Settings

The following procedure explains how to export all security settings of a server.
1 In the Server Explorer of the ROSA NMS system, select the server of which
security settings must be exported.
2 In the Security menu, point to Export Settings....
368 4014778 Rev H

Result: The Export Security Settings dialog is displayed.
3 Click on the Export All command button.

Result: The Save As dialog is displayed.
4 Browse to the folder where the security settings file must be stored.
5 In the file name box, enter a name.
6 Click on the Save command button to confirm or the Cancel command button to
7 Close the Export Security Settings dialog by pressing the Close command
button.
Exporting the Security Settings of a User or a Security Group

The procedure below describes how to export the security settings of a user or the
security settings of a security group.
2 In the Security menu, point to Export Settings....
4014778 Rev H 369

Result: The Export Security Settings dialog is displayed.
3 To export users, select one or more users in the Users list box. To select
consecutive users, click on the first user, press and hold down the [SHIFT] key,
and then click on the last user. To select users that are not consecutive, press
and hold down the [CTRL] key, and point to each user.
Notes:
When a user is selected, the security group to which the user belongs is
automatically selected in the Groups list box because exporting a user
without its security group is not allowed. When the security group does not
exist on the system the security settings should be imported, the security
group is automatically created after importing the security settings. If the
security already exists, the user is added to the security group and the
settings of the security group are overwritten with those of the imported
security group.
The users not belonging to a security group are not listed.
4 To export security groups, select one or more groups in the Groups list box. To
select consecutive security groups, click on the first group, press and hold down
the [SHIFT] key, and then click on the last group. To select security groups that
are not consecutive, press and hold down the [CTRL] key, and click on each
group.
Note: Only the settings of the security group will be exported, not the users
belonging to this group. To export the settings of a security group with its
users, select some or all of the users in the Users list box. The security group(s)
to which the users belong will be selected automatically.
370 4014778 Rev H

5 To export the security options along with the users and security groups, tick the
Export Security Options check box.
Note: The only security option is the minimum password length, see Setting the
Minimum Password Length further in this chapter.
6 Click on the Export command button.
Result: The Save As dialog is displayed.
7 Browse to the folder where the security settings file must be stored.
8 In the file name box, enter a name.
9 Click on the Save command button to confirm or the Cancel command button to
10 Close the Export Security Settings dialog by pressing the Close command
button.
Importing Security Settings

Perform the following procedure to import security settings.
1 In the Server Explorer tree of the ROSA NMS system, select the server on which
security settings must be imported.
2 In the Security menu, point to Import Settings ....
3 Click on the Yes command button to allow overwriting the security settings of
existing users or security groups or the No command button to abort the
operation.
4014778 Rev H 371

Result: After pressing the Yes command button, the open dialog is displayed.
Note: Only the security settings of the existing users and security groups
matching the security settings in the imported file will be overwritten.
4 Browse to the folder containing the security settings that should be imported
(*.sec).
5 Select the file and point to the Open command button.
During the importing process the following message is displayed.
372 4014778 Rev H

Map Security
Map Security
Introduction
To secure the maps stored on a ROSA NMS Single User system or ROSA NMS Client
system, permission can be given to users to view maps, to edit maps, to view the
permissions, and to edit those permissions. For each created maps, specific
permission can be set.
Maps are not linked to a specific server and users from different servers can have
access to these maps. Therefore both the name of the server and the user are stored
in the maps on the ROSA NMS system. Members of Administrator security groups
always have all permission on maps.
When a new map is created, it has an imaginary user called Everyone. These
permissions are only used when the ROSA NMS system is not connected to a server
or when the current user is not found in the permission list on the map.
Notes:
By default the Everyone user has all permissions. To reduce the risk of
unwanted map changes, the permissions of the Everyone user can be changed or
the user can be removed. After removing the Everyone user, this user can
always be added again later if required.
More detailed information concerning maps can be found in Chapter Working
with Maps on page 261.
Adding a User to a Map

The following procedure explains how to add a user to a map.
1 In the Map Explorer of the ROSA NMS system, right-click on the map and point
to Permissions... in the short-cut menu.
4014778 Rev H 373

Result: The Permission for map <map name> dialog is displayed.
2 Point to the Add Users command button.

3 In the Users list box, select the user and click on the Add command button to
confirm or the Cancel command to abort the operation.
4 Point to the OK command button to close the Permission for map <map name>
dialog.
374 4014778 Rev H

Map Security
Changing Map Permissions

Perform the following procedure to change the permissions of users.
2 Tick the Replace permissions on all current sub maps check box to change the
permissions on all sub maps of the current map as well.
3 Select the user of which permissions must be changed and point to the Edit
Permissions command button.
Result: The Permission for user <user name> is displayed.
4 Set or clear the check boxes of the following permissions:

View Map: when the View Map check box is cleared, all other check boxes
will be cleared with the exception of the View Permission check box.
4014778 Rev H 375

Edit Map: when the Edit Map selection box is set, the View Map selection
box is set automatically. When the View Map check box is cleared, the Edit
Permission check box will also be cleared.
View Permission: when the View Permission check box is cleared, the Edit
Permission check box clears automatically.
Edit Permission: when the Edit Permission check box is set, all other check
boxes will be set automatically.
Removing Users from a Map

Perform the following procedure to remove a user from a map.
2 Select the user(s) that should be removed from the map and point to the Remove
Users command button.
the operation.
376 4014778 Rev H

Setting the Minimum Password Length
Setting the Minimum Password Length

The Minimum password length parameter determines the least number of
characters that the password may contain. The procedure below describes how to
change this parameter.
2 In the Security menu, point to Options....
Result: The Security Options dialog is displayed.
3 In the Minimum password length box, enter the least number of characters that
the password may contain.
4014778 Rev H 377

16 Chapter 16
ROSA High Availability
Solution
Introduction
This chapter covers ROSA High Availability Solution combined with
ROSA NMS.
In This Chapter
Introduction ......................................................................................... 380
Installing the High Availability Control Software ......................... 383
Configuring the High Availability Control Software.................... 429
General Remarks................................................................................. 441
4014778 Rev H 379

Chapter 16 ROSA High Availability Solution
Introduction
General
ROSA's High Availability Solution is a solution that provides ROSA NMS and ROSA
VSM to operate in a warm redundant setup. This allows the operator to minimize
its downtime due to power failover support as well as operation advantages on
switchover from Primary Server to Secondary and back. Mostly, the Primary Server
is the Active Server and the Secondary Server is the Passive Server.
Features
Redundancy Support
Warm redundancy operation of the ROSA NMS server application limits systems
downtime.
Automatic or manual failover that protects critical applications and allows
controlled recovery.
Server protection protects the complete ROSA NMS server by failing over from
Primary to Secondary.
Network protection allows protecting the ROSA NMS server from losing its
network connection to the managed devices and ROSA NMS clients.
Application protection ensures that the critical ROSA NMS applications are
monitored. In case of application error, the High Availability control software
will failover to the Secondary ROSA NMS Server.
Data protection replicates all data from the Active Primary ROSA NMS Server to
the Passive Secondary ROSA NMS server. During operation, delta data is
copied.
Server Protection
Failover protection of server crash and operating system crash.
Protected by heartbeat connection between the Primary and Secondary ROSA
NMS Servers.
The Secondary server detects that the Primary server is no longer responding.
Typically caused when the Primary server has crashed or its network connection
is lost.
The system screen can be used to view status, check progress on failover and
copy processes taking place.
380 4014778 Rev H

Introduction
Network Protection
Network protection protects from public network connectivity issues. Detection
of network availability performed by reaching target in the public management
network.
Timeout of failure results in notification to the High Availability control
software.
The system switches autonomously from Primary to Secondary Server
depending on the configuration of the solution.
Application Protection
Application protection by monitoring of services and user defined applications.
Standard applications protected as selected by Cisco are ROSA NMS core server
applications and several other applications that require to be operative for
failure-less operation of the NMS packages
Protection of the ROSA NMS core activity
Cisco provides pre-configuration to protect the function critical applications for
failover.
Depending on the configuration of the solution, the system switches
autonomously from Primary to Secondary server or the operator can invoke a
switchover manually.
Continuous Data Replication

Continuous data replication from Primary server to Secondary Server protects
user and system data.
User data like logging information and application files are kept in sync between
Primary and Secondary Server. This allows for applications as backup tasks,
alarm logging, scheduling to stay in sync.
System data like registry, application critical data and system logging are
synchronized between Primary and Secondary server.
Only delta data is transferred to keep performance and bandwidth under
control.
Deployment
Collocated solution interfaces with the management IP router/switch via the
internal NIC interfaces, present on the ROSA NMS server.
Single IP interface address allows for smooth support of the managed devices.
All devices under management of the ROSA High Available Solution have a
common management server address.
Hearthbeat link between Primary and Secondary server can be realized through
4014778 Rev H 381

a crossover cable Ethernet cable or over the management IP router/switch.

High Availability pack contains 2 extra Network Interface Cards (NIC) and
software enabling a High Availability solution for each ROSA NMS installation.
382 4014778 Rev H

Installing the High Availability Control Software

Introduction
General
This topic explains how to install and to configure High Availability control software
on a ROSA Server pair.
Remark:
Make sure the Computer Name is set correctly before installing the High
Availability control software. Changing the Computer Name after installing
this control software is very difficult and time consuming.
Do not access network resources unless explicitly asked for. During this
installation/configuration, these resources could become unavailable.
The servers must be configured using the console. Do not use Remote Desktop.
Requirements
Hardware Requirements
- 2 x ROSA Server
- 2 x HP NC110T PCI Express Gigabit Server Adapter
Note: The servers must be identical.
Software Requirements
- Windows Server 2003 SP2
- ROSA NMS 4.0
Other Requirements
- ROSA NMS 4.0 installation software
- Neverfail SCOPE 4.3.4 installation software
- Neverfail 5.4.2 installation software
- HP SmartStart 8.0 CD (required for HP NC110T installation)
- ROSA license file (can only be requested from Cisco Services if both HostIDs
are known, see further in this procedure)
- Neverfail license key (can only be requested from Cisco Services after the
Neverfail SCOPE file has been generated)
4014778 Rev H 383

Preparing the Server

Software Requirements
Software Requirements Primary Server
Windows Server 2003 SP2 must be installed
Server must be member of a Workgroup (no domain)
Software Requirements Secondary Server
The Secondary Server must be identically configured as the Primary Server:
- The version of the operating system and Service Pack must match the
Primary Server.
- The operating system must be installed to the same driver letter and
directory as on the Primary Server.
- System Date / Time and Time Zone must be consistent with Primary Server.
- Server must be member of a Workgroup (no domain).
Computer name must be different from that of the Primary Server.
Additional applications, including the protected applications (MS SQL server
and Copernicus) must NOT be installed.
Remark:
The easiest way to get the Secondary Server configured is to completely reinstall it
using the Windows Server 2003 R2 Installation for ROSA Servers DVD.
Installing the HP NC110T NIC into the Server

The following procedure describes how to install a HP NC110T NIC card into the
server. This action must be done for the Primary server as well as for the Secondary
server
1 Shut down the server.
2 Install the NIC card in slot 2 of the server as described in the publications
shipped with the card and the server.
3 Start the server and logon to it using the Administrator account.
384 4014778 Rev H

Result: The Found New Hardware Wizard will be displayed.
4 Click on the Cancel command button to close the wizard.

5 Insert the HP SmartStart 8.0 CD in the DVD-ROM drive.
Result: The HP SmartStart window is displayed.
6 Click on the Agree command button.
4014778 Rev H 385

Result: The following window is displayed.
7 Point to the Software tab.

8 Click on the Install Proliant Support Pack link.
386 4014778 Rev H

9 Point to the Express Installation of the PSP for Windows link.

4014778 Rev H 387

It will take a few minutes for this setup to complete.

10 Remove the HP SmartStart 8.0 CD from the DVD-ROM drive.
11 Now, reboot the server.
ROSA NMS 4.x Installation

On the Primary server, the ROSA NMS Server 4.x software must already be
installed. The path to the license file referred to by the value name
ROSADAEMON_LICENSE_FILE under the HKEY_LOCAL_MACHINE \
SOFTWARE \ FLEXlm License Manager key must be correct, for instance C:\ Program
Files \ Cisco \ Copernicus \ License \ license.dat. The following procedure describes
how to check and to modify if required by using the Registry Editor.
1 Clicking on Start in the Taskbar and pointing to Run...
Result: The Run dialog is displayed.
2 In the Open box, enter regedit and click on the OK button.
Result: The Registry Editor dialog is displayed.
3 In the Registry Editor tree, browse to the HKEY_LOCAL_MACHINE \
SOFTWARE \ FLEXlm License Manager key and click on this key.
Result: The corresponding key is displayed.
4 The license file reference can be changed by double clicking on the key name or
right-clicking on the key and pointing to Modify in the short-cut menu and
modifying the Value data.
Press the OK command button to confirm.

5 Close the Registry Editor dialog by clicking on Exit in the File menu.
388 4014778 Rev H

Configuring the Network Settings

Introduction
The procedures described in following sub topics must be done for the Primary
Server as well as for the Secondary Server. The static IP addresses of both servers
must be different.
Changing the Name of the Local Area Connections

When a server leaves our assembly line and after installing the HP NC110T NIC, the
network configuration of the server is as follows.
Local Area Connection: static IP Address
Local Area Connection 2: DHCP enabled
Local Area Connection 3 was added by installing the HP NC110T NIC.
Before the server can participate into ROSA's High Availability Solution, these Local
Area Connections must be renamed:
Local Area Connection (HP NC373i Multifunction Gigabit Server Adapter): Public
Local Area Connection 2 (HP NC373i Multifunction Gigabit Server Adapter):
Neverfail Channel
Local Area Connection 3 (HP NC110T PCIe Gigabit Server Adapter): Management
Important: The Local Area Connection (HP NC373i Multifunction Gigabit Server
Adapter) with physical address (MAC) matching the HostID used in the ROSA
license file has to be renamed to Public.
The HostID used in the ROSA license file can be found in the HostID.txt file.
This file can be found on the server at the following location:

C:\ Program Files \ Cisco \ Copernicus \ License or
C:\ Program Files \ Scientific-Atlanta \ Copernicus \ License
4014778 Rev H 389

The physical address of all network connections can be determined by using the
ipconfig /all instruction in a cmd box.
The settings of the network connections are displayed after pressing the [Enter]
key.
For new installations and when ROSA license files are not yet available, rename the
network connections as follows:
Local Area Connection: Public
Local Area Connection 2: Neverfail Channel
Local Area Connection 3: Management
The following procedure describes how to rename the Local Area Connections of a
server.
1 Start the server and logon to it using the Administrator account.
2 In the taskbar, click on Start, Settings, and Network Connections.
390 4014778 Rev H

Result: The Network Connections window is displayed.
3 Right-click on the Local Area Connection icon and point to Rename in the
short-cut menu.
4 Enter the appropriate name for the connection.
5 Repeat step 3 and 4 for all Local Area Connections.
6 Change the network connection parameters as describes in following topic.
Changing the Network Connection Parameters

Once the name of the network connections are modified, particular network
connection parameters must be changed. The following overview lists these
parameters.
Public network connection
- Only following network components can be used:
Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
HP Network Configuration Utility
NWLink NetBIOS
NWLink IPX/SPX/NetBIOS Compatible Transport Protocol
Internet Protocol (TCP/IP)
4014778 Rev H 391

- Static IP address
- Correct Subnet Mask
- Correct Default Gateway address
- Correct Preferred and Alternate (if applicable) DNS Server address
- Correct Primary and Secondary (if applicable) WINS Server address
- Enable NetBIOS over TCP/IP.
Neverfail Channel Network Connection
- Only following network components can be used:
NWLink NetBIOS
- Static IP address (in a different subnet than the Public network connection)
- Correct Subnet Mask
- No Default Gateway address
- No DNS Server address
- No WINS Server address
- Enable NetBIOS over TCP/IP
Management Network Connection
Only following network components can be used:
NWLink NetBIOS
Static IP address
Correct Network Mask
Correct Gateway address
No DNS Server address
No WINS Server address
Disable NetBIOS over TCP/IP
392 4014778 Rev H

The following procedure describes how to change the network connection

parameters. This procedure must be done for the Public, the Neverfail Channel,
and the Management Network Connection.
1 In the Network Connections window, right-click on the Local Area Connection
icon and point to Properties in the short-cut menu.
Result: The Properties dialog of the selected network connection is displayed.
2 In the This connection uses the following items list box on the General tab, tick
the check boxes of the network components that can be used and clear the check
boxes of the other components.
3 In the This connection uses the following items list box, select Internet Protocol
(TCP/IP) and click on the Properties command button.
4014778 Rev H 393

Result: The Internet Protocol (TCP/IP) Properties dialog is displayed.
4 Point to Use the following IP address selection button and complete the
following parameters with appropriate values: IP address, Subnet mask,
Default gateway, Preferred DNS server, and Alternate DNS server.
5 After completing the settings, click on the Advanced... command button.
Result: The Advanced TCP/IP Settings dialog is displayed.
6 Click on the WINS tab.
394 4014778 Rev H

Result: The WINS tab page is displayed.
7 In the NetBIOS settings selection box, point to the correct setting.

8 Click on the OK command button to confirm and to close the Advanced TCP/IP
Settings dialog and to return to the Internet Protocol (TCP/IP) Properties
dialog.
9 Click on the OK command button to confirm and to close the Internet Protocol
(TCP/IP) Properties dialog.
10 Click on the OK command button to confirm and to close the Properties dialog.
11 After completing the network parameters for all network connections, check the
network connection order as describes in following topic.
Checking the Network Connection Order

The following list gives the order of the network connections:
Public
Neverfail Channel
Management
This order can be checked and modified if needed as described in the following
procedure.
4014778 Rev H 395

1 In the Advanced menu of the Network Connections dialog, choose Advanced

Settings.
Result: The Advanced Settings dialog is displayed.
2 In the Connections box in the Adapters and Bindings window, check if the
connection order is correct. If not, modify the order by selecting a connection
and pressing the up or down arrow key beside the Connections box.
3 Click on the OK command button to confirm and to close the dialog.
4 Reboot the server if the previous action did not request you to do so.
Additional Checks and Configurations

Application Verification
For the Primary server and in case of an existing installation, connect a ROSA 4.x
client to the server to verify if the installation was successful. More information
about connecting a ROSA client to the server can be found in topic Adding and
Removing Servers on page 125.
396 4014778 Rev H

Event Log Check

For both the Primary and Secondary server, verify that there are no unexplainable
errors in the System and Application Event Log. These logs can be checked with the
Event Viewer.
The event viewer can be opened by selecting Start, All Programs, Accessories,
Administrative Tools, and Event Viewer in the Taskbar.
HostID for ROSA License

For the Primary server and in case of a new installation, disconnect all NICs and run
the following command in a cmd box (to be found in the C:\ Program Files \ Cisco \
Copernicus \ License folder): lmutil lmhostid
For the Secondary server:
Copy the file lmutil.exe (to be found in the C:\ Program Files \ Cisco \ Copernicus \
License or C:\ Program Files \ Scientific-Atlanta \ Copernicus \ License folder) from
the Primary server to the root of the C drive on the Secondary server.
Disconnect all NICs and run the following command in a cmd box: lmutil
lmhostid
Windows Backup Folder

For the Secondary Server, create the folder C:\ _BackupPrimaryServer. It will be
used for storing the Windows backup file of the Primary server.
4014778 Rev H 397

Licensing
Introduction
The HostIDs required to obtain ROSA license file, have been determined in previous
topic. In order to obtain a license for the High Availability control software (called
Neverfail license), a SCOPE data file must be sent together with these HostIDs to
Cisco Services (saemea-support@cisco.com). This file is generated by the SCOPE
Data Collector Service and contains the required information for the generation of
the Neverfail license.
Prerequisites
On both Primary and Secondary server, connect the Public NIC to the network.
Connect the Neverfail Channel of both servers using a crossover cable.
The SCOPE Data Collector Service setup software is available on the ROSA NMS
4.1 (and higher) DVD.
SCOPE Data Collector Service Installation

The following steps describe how to install the SCOPE Data Collector Service.
1 On the Primary Server, open the Neverfail setup folder (for example Setup \
Neverfail \ Z-S-Sw-SCOPE-Data-Collector-Service-V5.0.8-x86 on the ROSA NMS4.x
DVD) and start SCOPE Data Collector Service.msi.
Result: The Neverfail SCOPE Data Collector Service - InstallShield Wizard is
displayed.
398 4014778 Rev H


4014778 Rev H 399


6 In the Local IP addresses list box under Local Configuration, select the IP
address of the Neverfail Channel of the Primary Server.
7 In the Secondary's IP address box under Remote Configuration, enter the IP
Address of the Neverfail Channel of the Secondary Server and click on the Next
command button.
400 4014778 Rev H

8 Click on the Install command button.

Result: After a few seconds, the following window is displayed.
9 Now, the service is installed. Within 15 minutes, the first SCOPE data file will
be available.
4014778 Rev H 401

Neverfail License Request

In the C:\ Neverfail \ Scope \ Data \ Candidate For Upload folder, you will find a .cab
file. Send it to saemea-support@cisco.com in order to generate the Neverfail license
key.

Prerequisites
Before starting the installation, the Neverfail license key must be available.
Make sure the Computer Name is set correctly. If not, change it now.
On both Primary and Secondary server, verify that the Public NIC is connected
to the network.
Verify that the Neverfail Channel of both servers are connected using a crossover
cable.
The setup of the High Availability control software (called Neverfail) is available
on the ROSA NMS 4.x DVD.
To Install the High Availability Control Software on the Primary Server

The following procedure describes how to install the Neverfail software on the
Primary server.
1 If the Copernicus software is running, stop it now by stopping the Copernicus
Manager Service.
2 In the Neverfail setup folder (for example Setup \ Neverfail \ V5-4-2024-X86 on
the ROSA NMS 4.x DVD), start setup.exe.
Result: The Neverfail Heartbeat Setup dialog is displayed.
402 4014778 Rev H

3 In the Setup Type selection box, point to the Install Neverfail Heartbeat
selection button and click on the Next command button.
4014778 Rev H 403

4 In the Physical Hardware Identity selection box, point to the Primary selection
button and click on the Next command button.
5 Point to the I accept terms of the License Agreement selection button and click
on the Next command button.
6 Enter the Neverfail license key and click on the OK command button.
404 4014778 Rev H


4014778 Rev H 405

8 Under Installation Paths, enter C:\ Neverfail in the To box and click on the Next
command button.
9 Under Network Adapters, tick the Neverfail Channel check box and click on the
Next command button.
10 Enter the IP Address of the Neverfail Channel in the IP Address On Secondary

box and click on the OK command button.
406 4014778 Rev H

11 Accept the Default Channel Port and click on the Next command button.
4014778 Rev H 407

12 Under Network Adapters, tick the Public check box and click on the Next
command button.
13 Select the Public IP address and click on the OK command button.

14 Point to the LAN: Configure Primary and Secondary servers with the same
Public IP address(es) selection button and click the Next command button.
408 4014778 Rev H

15 Accept the Default Client Connection Port and click on the Next command button.
4014778 Rev H 409

Remark: The Low Bandwidth Module can also be listed. Since only LAN
installations are supported, clear its check box so it does not get installed.
17 Browse to the folder (for instance Setup \ Neverfail \ Z-Sw-A12-SQLServer.201.5.2

on the ROSA NMS 4.x DVD) containing the SqlServerNFPlugin.dll file and click
on the OK command button.

410 4014778 Rev H

19 Verify that the Installation Summary is correct and click on the Next command
button. Pre-Install Checks will be completed.
4014778 Rev H 411

20 Verify that the Pre-install Check completed successfully and click on the Next
command button. Installation will start.
21 Verify that the installation completed successfully and click on the Next
command button.
22 Map the drive letter Z to the C drive of the Secondary Server (\\ 192.168.1.2 \
C$) and click the Finish command button.
412 4014778 Rev H

23 For Backup File Folder, specify Z:\ _BackupPrimaryServer and tick the Include
protected data in backup set check box
4014778 Rev H 413

25 Click on the Proceed command button. Windows backup will start.

Result: The Backup Progress window is displayed.
414 4014778 Rev H

Result: When backup is complete, the following window will be displayed.

27 Verify that the Windows backup completed successfully and click on the Next
command button.
4014778 Rev H 415

28 Verify that the Packet Filter Installation completed successfully. Click on the
416 4014778 Rev H

29 Click on the Finish command button. The installation of the Primary Server is
now complete.
To Install the High Availability Control Software on the Secondary Server

The following steps explain how to install the Neverfail software on the Secondary
server.
1 In the Neverfail setup folder, start setup.exe.
Result: The Neverfail Heartbeat Setup dialog is displayed.
2 Under Setup Type, point to the Install Neverfail Heartbeat selection button and
click on the Next command button.
4014778 Rev H 417

3 Under Physical Hardware Identity, point to the Secondary selection button and
click on the Next command button.
418 4014778 Rev H

4 Under Identify Microsoft Windows Backup Folder, enter C:\

_BackupPrimaryServer in the Backup File Folder box and click on the Next
command button.
5 Verify that the Pre-install Checks completed successfully. Click on the Next
command button.
4014778 Rev H 419

6 Verify that the installation completed successfully. Click on the Next command
button.
420 4014778 Rev H

7 Verify that the Packet Filter Installation completed successfully. Click on the
8 Under Network Adapters, tick the Neverfail Channel check box but do NOT
click on the Next command button yet.
9 First, open the Internet Protocol (TCP/IP) Properties dialog of the Public
network and change its IP Address to the Public IP address.
4014778 Rev H 421

10 Now, click on the Next command button.

422 4014778 Rev H

11 Under Network Adapters, tick the Public check box and click on the Next
command button.

Result: The Backup Utility dialog is displayed.
13 Click on the Restore Wizard command button.

4014778 Rev H 423


15 Click on the Browse command button.

Result: The Open Backup File dialog is displayed.
424 4014778 Rev H

16 Enter C:\ _BackupPrimaryServer \ NF.bkf in the Open box and click on the OK
command button.
Result: The Restore Wizard dialog is displayed.
17 In the Items to Restore box, tick the C and System State check box and click on
the Next command button.
4014778 Rev H 425

18 Click on the Finish command button.


426 4014778 Rev H

Result: When the restore is complete, the following window will be displayed.
20 Click on the Close command button.

21 Click on the Yes command button to restart the server.
4014778 Rev H 427

22 When restart is complete, logon to the server again. Additional reboots could be
required if New Hardware is detected. If so, first use the Neverfail application in
the System Tray to shutdown Neverfail Heartbeat but leave Protected Applications
running.
Neverfail Post Installation

Reboot the Primary Server.
It is very likely that the HP Insight Foundation Agents application will crash on
both servers. To solve this, disable Performance Monitor in the HP Management
Agents Applet (Control Panel) on Primary and Secondary server.
428 4014778 Rev H

Configuring the High Availability Control Software

Prerequisites
Before starting the Neverfail configuration, a ROSA license file with High
Availability support is required. The HostIDs of both servers are in HA.xml,
located in the License subdirectory of the Copernicus installation folder.
Copy the ROSA license file to the License subdirectory of the Copernicus
installation folder. Then, start the Copernicus Manager Service. This service
should be running now.
On both Primary and Secondary Server, add a second IP Address to the Public
NIC (for example 11.0.0.1/8 for Primary and 11.0.0.2/8 for Secondary). This can
be done in the IP Settings tab of the Advanced TCP/IP Settings.
These extra IP Addresses are needed for Neverfail Split-Brain configuration (see
further).
To Configure the High Availability Control Software

The following steps describe how to configure the Neverfail software.
1 Logon to the Primary Server.
2 Start the Neverfail Manage Server application.
Result: The Neverfail Heartbeat Login dialog is displayed.
3 Click on the Servers... command button.
4014778 Rev H 429

Result: The Server Pairs dialog is displayed.
4 Click on the + Add Pair command button.

Result: The Add Server Pair dialog is displayed.
5 In the HostName / IP Address box, specify the Hostname (localhost is also

allowed) or IP address of the server to manage. The Port Number parameter
does not need to be changed. Click on the OK command button.
6 Click on the Close command button.
430 4014778 Rev H

Tip: Neverfail uses Windows security.

7 In the Password box, enter the Administrator's password.
8 Tick the check box of the server and click on the Open command button.
4014778 Rev H 431

9 Select the Configuration tab.

432 4014778 Rev H

10 Tick the Do not stop protected applications check box and point to the Apply
command button.
11 Click on the Application command button, then select the Services tab.

Result: The Add Service dialog is displayed.
4014778 Rev H 433

13 Configure MSSQL$SQLROSA as shown above. Only for MSSQL$SQLROSA

and COPMANSVC (see further), select Switchover in the On Third Failure drop
down box. For the other services, select Recover Service in the On Third Failure
drop down box. Now click on the OK command button to confirm.
14 Also add the following services:
CQMGHOST
CPQNICMGMT
CQMGSERV
CQMGSTOR
SNMP
BARCONETDAYTIME
COPMANSVC
Important: Make sure the ordering for the User Defined services is the same as
shown above.
15 Click on the Communication command button, then choose the Configuration
tab.
434 4014778 Rev H

16 Configure the Communication as shown above. The address to ping on both

servers is the Public IP address. Click on the Apply command button.
17 Choose the Split-Brain Avoidance Configuration tab.
4014778 Rev H 435

18 Configure the Split-Brain Avoidance as shown above (specify the IP Addresses

you created when starting the Neverfail configuration). Click on the Apply
command button.
19 Click on the Data command button, then choose the Configuration tab.
436 4014778 Rev H

20 Click on the Add Inclusion Filter... command button.

Result: The Add Inclusion Filter dialog is displayed.
21 Enter C:\ POGRAM FILES \ CISCO \ COPERNICUS \ ** in the Pattern box and
click on the OK command button to confirm.
22 Click on the Add Exclusion Filter... command button.
Result: The Add Exclusion Filter dialog is displayed.
23 Enter C:\ POGRAM FILES \ CISCO \ COPERNICUS \ SERVICE \

COPHELPER.EXE in the Pattern box and click on the OK command button to
confirm.
24 Click on the Add Exclusion Filter... command button.
4014778 Rev H 437

Result: The Add Exclusion Filter dialog is displayed
25 Enter C:\ POGRAM FILES \ CISCO \ COPERNICUS \ LICENSE \

HOSTID_HA.TXT in the Pattern box and click on the OK command button to
confirm.
26 Some registry keys also have to be replicated. To accomplish this, run

AddRegKeysToSynch.bat (available in the Setup \ Neverfail folder on the ROSA
NMS 4.X DVD).
27 For the changes to take effect, both servers must be restarted. First, Neverfail
must be shutdown.
So, in the Neverfail Heartbeat Management Client, click on the System
command button, then choose the Status & Control tab.
438 4014778 Rev H

Result: The Status & Control tab page is displayed.
28 Click on the Shutdown command button.

Result: The Shutdown Neverfail Heartbeat dialog is displayed.
29 Point to the Shutdown Heartbeat but leave protected applications running...

selection button and click on the OK command button to confirm.
30 Reboot the Primary server. While the Primary server is booting, reboot the
Secondary server.
31 On the Primary server, shutdown Neverfail Heartbeat but leave Protected
Applications running. Use the Neverfail application in the System Tray.
32 Run a repair Copernicus setup on the Primary server and let setup restart the
server.
33 Start Neverfail Heartbeat on the Secondary server. Use the Neverfail
application in the System Tray.
4014778 Rev H 439

34 On the Primary server, open the Neverfail Heatbeat Management Client and
click the Switchover command button. You will get the following dialog:
Result: The Switchover Confirmation box is displayed.
35 Click the Yes command button to confirm

Result: The following dialog is displayed after a while.
36 Now, click the Shutdown command button and choose to leave the Protected
Applications running.
37 Run a repair Copernicus setup on the Secondary Server and let setup restart the
server.
38 Start Neverfail Heartbeat on the Primary Server. Use the Neverfail application
in the System Tray.
39 Perform another switchover so the Primary Server gets active again.
440 4014778 Rev H

General Remarks
General Remarks
ROSA NMS SNMP Agent Task
The SNMP Agent Task must not be set to Automatic Start since SNMP is controlled
by the Neverfail software.
Email Notification of Neverfail Alerts

It is best to configure the Neverfail Email Notification so alerts can be sent to one or
more recipients.
Recovering from a Failover

Procedure
Solve incident (HDD, power, virus, communication...) that caused the failover.
Reboot failed server.
Start Neverfail Heartbeat on failed server (not automatically started to prevent
accidentally overwriting protected data).
Allow Neverfail to fully synchronize.
Perform a manual switchover.
Known Issue - Ping Targets reset after Power Outage on both Servers
Problem
After a power outage on both servers, the targets that are pinged from the
Primary and Secondary server to check the Public Network Connection are reset
to their defaults: the Default Gateway and the primary DNS Server. If these
targets were defined otherwise, this could result in a required failover not taking
place.
Solution
A fix will be made available by Neverfail.
Workaround
If a power outage has occurred, check if the Ping Targets are still configured
correctly. Otherwise, reconfigure them.
4014778 Rev H 441

A
Appendix A
Appx auto letter
Customer Information
Introduction
This chapter contains information on obtaining product support.
In This Appendix
Product Support.................................................................................. 444
4014778 Rev H 443

Appendix A
Customer Information
Product Support
Obtaining Support
IF... Then...
you have general questions about this contact your distributor or sales agent for
product product information or refer to product data
sheets on www.Cisco.com.
you have technical questions about this call the nearest Technical Support center or
product Cisco office.
you have customer service questions or call the nearest Customer Service center or Cisco
need a return material authorization office.
(RMA) number
Support Telephone Numbers

This table lists the Technical Support and Customer Service numbers for your area.
Region Centers Telephone and Fax Numbers
North America Cisco Services For Technical Support, call:
Atlanta, Toll-free: 1-800-722-2009
Georgia Local: 678-277-1120 (Press 2 at the prompt)
United States For Customer Service, call:
Toll-free: 1-800-722-2009
Local: 678-277-1120 (Press 3 at the prompt)
Fax: 770-236-5477
Email: customer-service@cisco.com
Europe, Belgium For Technical Support, call:
Middle East, Telephone: 32-56-445-197 or 32-56-445-155
Africa Fax: 32-56-445-061
For Customer Service, call:
Telephone: 32-56-445-444
Fax: 32-56-445-051
Email: service-elc@cisco.com
Japan Japan Telephone: 81-3-5908-2153 or +81-3-5908-2154
Fax: 81-3-5908-2155
Korea Korea Telephone: 82-2-3429-8800
Fax: 82-2-3452-9748
Email: songk@cisco.com
China (mainland) China Telephone: 86-21-2401-4433
Fax: 86-21-2401-4455
Email: xishan@cisco.com
All other Asia Pacific Hong Kong Telephone: 852-2588-4746
countries & Australia Fax: 852-2588-3139
Email: saapac-support@cisco.com
444 4014778 Rev H

Product Support
Region Centers Telephone and Fax Numbers

Brazil Brazil Telephone: 11-55-08-9999
Fax: 11-55-08-9998
Email: fattinl@cisco.com or ecavalhe@cisco.com
Mexico, Mexico For Technical Support, call:
Central America, Telephone: 52-3515152599
Caribbean Fax: 52-3515152599
Telephone: 52-55-50-81-8425
Fax: 52-55-52-61-0893
Email: sa-latam-cs@cisco.com
All other Argentina For Technical Support, call:
Latin America countries Telephone: 54-23-20-403340 ext 109
Fax: 54-23-20-403340 ext 103
Telephone: 770-236-5662
Fax: 770-236-5888
Email: keillov@cisco.com
4014778 Rev H 445

B
Appendix B
Appx auto letter
Additional Configuration
Introduction
This appendix contains the procedure to start the Messenger Service
on a computer running Windows XP Service Pack 2 and how to
change the administrative passwords for the SNMP Service,
Copernicus Manager service, and Copernicus server software DCOM
configuration.
In This Appendix
Starting Messenger Service................................................................ 448
Changing Administrative Password................................................ 451
Internet Protocol Security .................................................................. 456
4014778 Rev H 447

Appendix B
Starting Messenger Service

Introduction
The sending messages functionality of the ROSA NMS/Copernicus software uses
the Messenger service of the Windows operating system. By default, the Messenger
service on computers running Windows XP Service Pack 2 is disabled. The
following topic describes how to enable this service.
To Start the Messenger Service

The following procedure explains how to start the Messenger Service on a computer
running Windows XP Service Pack 2.
1 In the Taskbar of Windows XP, click on Start and point to Control Panel in the
Start Menu.
Result: The Control Panel page is displayed.
2 Double-click on Administrative Tools.
448 4014778 Rev H

Starting Messenger Service
Result: The Administrative Tools page is displayed.
3 Double-click on Services.
Result: The Services dialog is displayed.
4 Double-click on the Messenger service.
4014778 Rev H 449

Appendix B
Result: The Messenger Properties dialog is displayed.
5 In the Startup type drop down box, select one of the following settings:
Manual: the Messenger Service must be started by the user each time the
computer starts.
Automatically: the Messenger Service starts automatically when the computer
starts.
7 Close both the Services page and Administrative Tools page.
450 4014778 Rev H

Changing Administrative Password

Introduction
When the password of the administrator account must be changed (on which the
server software part of a ROSA Single User or DCS system is running), it is
recommended to do this using the ROSA user interface. The procedure to change
the administrative password using the ROSA user interface is described in topic
Changing the Administrative User Password on page 153.
When the administrative password is changed without using the ROSA user
interface, the administrative passwords for Copernicus Manager service, the SNMP
service, and Copernicus server software DCOM configuration must be changed
manually.
Note: The SNMP service is used by ROSA's SNMP Agent task and is only present
when the Simple Network Management Protocol is installed in the Windows
operating system.
Changing the Administrative Password

The following procedure describes how to change the administrative password for
the Copernicus Manager service, the SNMP service, and Copernicus server software
DCOM configuration.
1 In the Windows Taskbar, click on Start and point to Run.
Result: The Run dialog is displayed.
2 In the Open drop down box, type DCOMCNFG and point to the OK command
button.
4014778 Rev H 451

Appendix B
Result: The Component Services dialog is displayed.
3 In the Console Root tree, browse to the DCOM Config.
Result: The DCOM Config objects are displayed.

4 Right-click on the Barco.Copernicus.Container object and point to Properties in
the short-cut menu.
Result: The Barco.Copernicus.Container Properties dialog is displayed.
5 Point to the Identity tab.
452 4014778 Rev H

Result: The Identity tab is displayed.
6 Enter the new administrative password in the Password and Confirm password
box.
7 Press the OK command button to confirm.
Result: The administrative password for the Copernicus server software DCOM
configuration is adapted.
8 In the Console Root tree, double-click on Services (local).
Result: The Local Services are displayed.
9 Right-click on the Copernicus Manager service and point to Properties in the
short-cut menu.
Result: The Copernicus Manager Properties dialog is displayed.
10 Point to the Log On tab.
4014778 Rev H 453

Appendix B
Result: The Log On tab is displayed.
box.
12 Click on the OK command button to confirm.
Result: The administrative password for the Copernicus Manager service is
changed.
13 Right-click on the SNMP Service and point to Properties in the short-cut menu.
Result: The SNMP Service Properties dialog is displayed.
14 Point to the Log On tab.
454 4014778 Rev H

Result: The Log On tab is displayed.
box.
16 Click on the OK command button to confirm
Result: The administrative password for the SNMP service is changed.
17 Close the Component Services dialog.
4014778 Rev H 455

Appendix B
Internet Protocol Security

Introduction
IP security (IPsec) ensures secure communication between two peers by providing
authentication and encryption mechanisms for network traffic. IPsec can use
several different encryption and authentication mechanisms to accommodate
various implementations and security needs. To ensure that two peers use the
same protocols when communicating with each other, a policy is set up that defines
a set of security parameters and encryption algorithms that can be configured in
each of both peers.
Notes:
The protocols and encryption algorithms that can be used depend on the
operating system of the computer running the ROSA NMS software.
When the communication between the ROSA NMS server and a device
monitored by this server must be secured, use protocols and encryption
algorithms which are supported by both peers.
The procedures in this topic describe the IP Security configuration for a computer
running Windows XP Professional or Windows 2003 Server and for a computer
running Windows Vista. The protocols and encryption algorithms used in this
topic are 3DES encryption, MD5/SHA-1 hashing, and Diffie-Hellman group 2.
To Configure IPsec on a Computer Running Windows XP or Windows 2000

Server
Windows XP or Windows 2003 Server can be configured to use IPsec using the
Microsoft Management Console (MMC). The MMC is a generic management
console that can manage many different Windows components.
IPsec configuration in Windows consists of four main tasks:
Access the IPsec management console.
Create IP address lists to identify computers.
Create Filter actions to define encryption parameters.
Create Policies that put IP address lists and filter actions together.
Each of these tasks is described below.
Note: You must be an Administrator user to perform these tasks.
456 4014778 Rev H

Accessing the IPsec Management Console

The following steps explain how to open the IPsec management console.
Launching MMC
The following steps explain how to open the MMC main screen.
1 From the Windows desktop, click on the Start button in the System Tray, and
then choose Run from the Start menu.
Result: The Run dialog box appears.
2 Enter mmc in the Open drop down box, and then click on the OK command
button.
Result: The MMC main screen appears as shown below.
Adding the Appropriate Snap-In

In order for MMC to manage the IPsec component, you must add the appropriate
IPsec snap-in as follows:
1 From the File menu, choose Add/Remove Snap-in.
4014778 Rev H 457

Appendix B
Result: The Add/Remove Snap-in dialog appears as shown below.
458 4014778 Rev H

Result: The Add Standalone Snap-in dialog appears as shown below.
3 In the Available Standalone Snap-ins box, choose IP Security Policy Management

and then click on the Add command button.
4014778 Rev H 459

Appendix B
Result: The Select Computer or Domain dialog appears as shown below.
4 Confirm that the Local computer selection button is selected, and then click on
the Finish command button.
5 Click on the Close command button to close the Add Standalone Snap-in dialog
and to return to the Add/Remove Snap-in dialog.
6 Confirm that IP Security Policies on Local Computer now appears in the
Standalone tab of this dialog.
7 Click on the OK command button to return to the management console.
460 4014778 Rev H

Result: The screen should now appear as shown below.
Note: If Console Root is highlighted in the left pane, click on IP Security

Policies on Local Computer to display the options shown in the right pane
above.
Tip: The IP Security Policies on Local Computer settings can also be accessed via
Control Panel / Administrative Tools / Local Security Policy.
Creating a New IP List

Complete the following steps to create a new IP list.
1 In the left pane of the Management Console, right-click on the IP Security Policies
on Local Computer item and choose Manage IP filter lists and filter actions from
the short-cut menu.
4014778 Rev H 461

Appendix B
Result: The Manage IP filter lists and filter Actions dialog appears as shown
below.
2 Click on the Add command button to open the IP Filter List dialog.
Result: The IP Filter List dialog is displayed. Note that the default name New
IP Filter List appears in the Name box.
462 4014778 Rev H

3 In the Name box, replace the default name with a new list name that is
meaningful to you (Headend IPs in the example below).
4 Confirm that the Use Add Wizard check box is checked, and then click on the
Add command button to start the IP Filter List wizard.
5 Complete the steps of the wizard as follows:
a IP Filter Description and Mirrored property (Windows 2003 Server only):
This specifies a filter in each direction. Tick the Mirrored. Match packets
with the exact opposite source and destination addresses check box.
b IP Traffic Source. This identifies the source of IP traffic for this list.
Choose My IP Address from the drop down box, and then click on the Next
command box.
c IP Traffic Destination. This identifies the destination of the IP traffic for
this list. Choose A specific IP Address from the drop down box, then enter
the IP address of the destination device, and then click on the Next command
button.
d IP Protocol Type. This identifies what protocols are valid for this list.
Choose Any from the drop down box, and then click on the Next command
button.
e Click on the Finish command button.
4014778 Rev H 463

Appendix B
For a computer running Windows 2003 Server, the IP Filter Properties dialog
is displayed.
Click on the OK command button to close the IP Filter Properties dialog.

Result: The IP Filter List dialog should now appear as shown below.
464 4014778 Rev H

6 Click on the OK command button to return to the Manage IP filter lists and
filter actions dialog.
7 Confirm that the new IP list now appears in the IP Filter Lists box.
Creating a New Filter Action

Complete the following steps to create a new filter action.
1 Click on the Manage Filter Actions tab to show current filter actions and to add
a new entry for the ROSA NMS.
Result: The tab opens as shown below.
2 Click on the Add command button to start the Filter Action wizard.
3 At the wizard welcome screen, click on the Next > command button.
4 Complete the steps of the wizard as follows:
a Filter Action Name. Replace the default name New Filter Action with a
meaningful name for the new action (for instance Headend IPsec Filter), and
then click on the Next > command button.
b Filter Action General Options. Select the Negotiate Security selection
button, and then click on the Next > command button.
c Communicating with computers that do not support IPsec. Choose Do not
communicate with computers that do not support IPsec, and then click on
the Next > command button.
4014778 Rev H 465

Appendix B
d IP Traffic Security. Select the Custom selection button, and then click on
the Settings command button.
Result: The Custom Security Method Settings dialog appears as shown
below.
e Tick the Data integrity and encryption (ESP) check box and then select MD5
and 3DES from the Integrity algorithm and Encryption algorithm drop
down boxes, respectively.
f Click on the OK command button to save your selections and return to the
Filter Action wizard IP Traffic Security wizard page.
g Click on the Next command button to proceed to the final page of the Filter
Action wizard.
h Click on the Finish command button.
466 4014778 Rev H

Result: The new filter action should now appear in the Filter Actions box as
shown below.
5 Double-click on the filter action you just created to open the Headend IPsec
Filter Properties dialog.
6 On the Security Methods tab, confirm that the Session key perfect forward
secrecy check box is checked and the other boxes are cleared, as shown in the
picture below.
4014778 Rev H 467

Appendix B
7 When finished, click on the OK command button to close the Headend IPsec
filter Properties dialog and return to the Manage IP filter lists and filter actions
dialog.
468 4014778 Rev H

8 Click on the Close command button to close this dialog and return to the MMC
dialog.
To Create a New IPsec Policy

Complete the following steps to create a new IPsec policy.
4014778 Rev H 469

Appendix B
1 Right-click on the right pane of the MMC, and then point to Create IP Security
Policy... in the short-cut menu to open the IP Security Policy wizard.
2 At the wizard welcome screen, click on the Next > command button to continue,
and then complete the steps of the wizard as follows:
a IP Security Policy Name. In the Name box, replace the default policy name
with a name that is more meaningful to you (for instance Headend Policy),
and then click on the Next > command button.
470 4014778 Rev H

b Requests for Secure Communication. Confirm that the Activate the

default response rule check box is not checked, and then click on the Next >
command button.
c On the final page of the wizard, confirm that the Edit Properties check box is
checked, and then click on the Finish command button.
Result: The Headend Policy Properties dialog appears as shown below.
3 Select the General tab and click on the Advanced command button.
Result: The Key Exchange Settings dialog is displayed.
4014778 Rev H 471

Appendix B
4 Point to the Methods... command button.

Result: The Key Exchange Security Methods dialog is displayed.
5 In the Security method preference order list box, select a security method with
3DES encryption and move it to the top of the list by clicking on the Move up
button.
Note: When the desired method is not available, an existing method can be
modified by clicking on the Edit... button or a new method can be created by
clicking on the Add... button.
Select the desired Integrity algorithm, Encryption Algorithm (3DES), and

Diffie-Hellman group (Medium (2)) in the corresponding drop down boxes
and press the OK command button to close the dialog.
6 Click on the OK command button to close the Key Exchange Security Methods
dialog and to return to the Key Exchange Settings dialog.
472 4014778 Rev H

7 Click on the OK command button to close the Key Exchange Settings dialog and
to return to the Headend Policy Properties dialog.
8 Clear the Use Add Wizard check box and then click on the Add command
button.
Result: The New Rule Properties dialog appears as shown below.
9 On the IP Filter List tab, select the Headend IPs selection button.
10 On the Filter Action tab, select the Headend IPsec Filter selection button.
11 On the Authentication Methods tab, click on the Add command button.
4014778 Rev H 473

Appendix B
Result: The New Authentication Method Properties dialog appears as shown

below.
12 Select the Use this string (preshared key) selection button, and then enter
alphanumeric string (between 1 and 200 characters).
Note: Be sure to make a note of this string, as it must exactly match the
preshared key entered in the destination device.
13 Click on the OK command button to save the preshared key entry and return to
the New Rule Properties dialog.
474 4014778 Rev H

Result: The preshared key is added to the Authentication method preference

order box.
14 Select the existing Kerberos entry, and then click on the Remove command button
to delete this entry from the list.
15 In the confirmation dialog, click on the Yes command button to accept the
changes.
16 Click on the OK command button to close the New Rule Properties dialog.
4014778 Rev H 475

Appendix B
Result: The Edit Rule Properties dialog should now display only the newly
entered rule.
17 Close the dialog to return to the MMC. Confirm that the new policy now
appears on the right pane.
18 Right-click on the new policy, and then choose Assign in the short-cut menu to
activate the policy.
If all of the above steps were performed correctly and the destination device is also
configured properly, the computer will now require IPsec to talk to the destination
device.
Note: If you have difficulty communicating with the destination device after
completing this procedure, ask your system administrator for assistance.
To Unassign IPsec
To disable IPsec on a computer running Windows XP or Windows 2003 Server, you
must unassign the IPsec policy as follows:
1 Open the Management Console as described in topic Accessing the IPsec
Management Console on page 457.
2 In the right hand pane of the Management Console, right-click on the IPsec
policy and point to Un-assign in the short-cut menu.
476 4014778 Rev H

For Further Information

Additional information on configuring IPsec for Windows XP Professional and
Windows 2003 Server is available on the following web page:
http://www.microsoft.com/downloads/details.aspx?familyid=a774012a-ac25-4a1d-
8851-b7a09e3f1dc9&displaylang=en
4014778 Rev H 477

Appendix B
To Configure IPsec on a Computer Running Windows Vista

IPsec configuration in Windows Vista consists of two main tasks:
Setting up the IPsec connection
Changing the IPsec connection defaults
Note: You must be an Administrator user to perform these tasks.
Setting Up the IPsec Connection

The following procedure explains how to set up an IPsec connection for Windows
Vista.
1 From the Windows desktop, click on the Start button in the System Tray, and
then choose Control Panel.
Result: The Control Panel dialog is displayed.
2 In the left hand pane of the Control Panel dialog, point to Classic View.
3 In the right hand pane of the Control Panel dialog, double-click on
Administrative Tools.
Result: The Control Panel - Administrative Tools dialog is displayed.
4 Double-click on Windows Firewall with Advanced Security.
Result: The User Account Control might appear.
5 Click on the Continue command button.

Result: The Windows Firewall with Advanced Security dialog is displayed.
478 4014778 Rev H

6 Select Connection Security Rules in the left hand pane of the dialog.
7 Right-click in the Connection Security Rules pane and point to New Rule... in
the short-cut menu.
Result: The New Connection Security Rule Wizard - Rule Type dialog is
displayed.
4014778 Rev H 479

Appendix B
8 Select the Server-to-server selection button and click on the Next > command
button.
480 4014778 Rev H

Result: The New Connection Security Rule Wizard - Endpoints dialog is

displayed.
9 Under Which computers are in Endpoint 1?, select the These IP addresses
selection button and click on the Add... command button.
Result: The IP Address dialog for Endpoint 1 appears.
4014778 Rev H 481

Appendix B
10 Select the This IP address or subnet selection button.

11 Enter the IP address of this computer in the corresponding box and press the OK
button to close the IP Address dialog and to return to the New Connection
Security Rule Wizard - Endpoints dialog.
12 Under Which computers are in Endpoint 2?, select the These IP addresses
selection button and click on the Add... command button.
Result: The IP Address dialog for Endpoint 2 appears.
13 Select the This IP address or subnet selection button.
14 Enter the IP address of the destination device in the corresponding box and press
the OK command button to close the IP Address dialog and to return to the New
Connection Security Rule Wizard - Endpoints dialog.
Result: The New Connection Security Rule Wizard - Requirements dialog is
displayed.
16 Select the Required authentication for inbound and outbound connections

selection button and click on the Next > command button.
482 4014778 Rev H

Result: The New Connection Security Rule Wizard - Authentication Method

17 Select the Preshared Key selection button.

18 In the Key box, enter the preshared key and press the Next > command button.
4014778 Rev H 483

Appendix B
Result: The New Connection Security Rule Wizard - Profile dialog is displayed.
19 Leave all check boxes ticked and press the Next > command button.
484 4014778 Rev H

Result: The New Connection Security Rule Wizard - Name dialog is displayed.
20 In the Name box, enter a name for the IPsec connection (Headend IPs in the
example).
21 Click on the Finish button to close the wizard and to return to the Windows
Firewall with Advanced Security dialog.
Changing IPsec Connection Defaults

Perform the following steps to change the IPsec connection defaults.
1 In the left hand pane of the Windows Firewall with Advanced Security dialog,
right-click on Windows Firewall with Advanced Security on Local Computer
and point to Properties in the short-cut menu.
Result: The Windows Firewall with Advanced Security on Local Computer
2 Click on the IPsec Settings tab
4014778 Rev H 485

Appendix B
Result: The IPsec Settings tab page is displayed.
3 Press the Customize... command button.
486 4014778 Rev H

Result: The Customize IPsec Settings dialog appears.
4 In the Key exchange (Main Mode) selection box, select the Advanced selection
button and point to the corresponding Customize... command button.
4014778 Rev H 487

Appendix B
Result: The Customize Advanced Key Exchange Settings dialog is displayed.
5 In the Key exchange algorithm selection box, select the desired algorithm for key
exchange (Diffie-Hellman Group 2).
6 In the Security methods box, press the Add command button.
488 4014778 Rev H

Result: The Security Method dialog appears.
a In the Encryption algorithm selection box, select the desired encryption

algorithm for key exchange (3DES).
b In the Integrity algorithm selection box, select the desired integrity algorithm
(MD5).
c Press the OK command button to close the Security Method dialog and to
return to the Customize Advanced Key Exchange Settings dialog.
Result: The selected key exchange method is added to the Security methods list
box.
Note: In the Security methods box, at least one method must match a key
exchange method of the destination device.
7 Click on the OK command button to close the Customize Advanced Key
Exchange Settings dialog and to return to the Customize IPsec Settings dialog.
8 In the Data protection (Quick Mode) selection box, select the Advanced
selection button and press the corresponding Customize... command button.
4014778 Rev H 489

Appendix B
Result: The Customize Data Protection Settings dialog is displayed.
9 In the Data integrity and encryption box, point to the Add... command button.
490 4014778 Rev H

Result: The Integrity and Encryption Algorithms dialog is displayed.
a In the Protocol selection box, select the desired protocol for data protection
(ESP).
b In the Encryption algorithm selection box, select the desired encryption
algorithm for data protection (3DES).
c In the Integrity algorithm selection box, select the desired integrity algorithm
(MD5)
d In the Key lifetime (in minutes) box, enter or choose the time a key will be
used for data integrity before a new key will be generated. A lifetime can be
chosen in the range from 5 minutes up to 2,879 minutes.
e In the Key lifetime (in KB) box, enter or choose the amount of data that will
be sent with a key before a new key will be generated. A lifetime can be
chosen in the range from 20,480 KB up to 2,147,483,647 KB.
f Press the OK button to close the Integrity and Encryption Algorithms dialog
and to return to the Customize Advanced Key Exchange Settings dialog.
Result: The selected data protection method is added to the Data integrity and
encryption algorithms box.
Note: In the Data integrity and encryption algorithms box, at least one method
must match a data protection method of the destination device.
4014778 Rev H 491

Appendix B
10 Press the OK command button to close Customize Data Protection Settings

dialog and to return to the Customize IPsec Settings dialog.
11 Press the OK command button to close the Customize IPsec Settings dialog and
to return to the Windows Firewall with Advanced Security on Local Computer
dialog.
12 Close the Windows Firewall with Advanced Security dialog.
Enabling or Disabling IPsec

Enabling or disabling IPsec on a computer running Windows Vista can be done as
follows:
1 Open the Windows Firewall with Advanced Security dialog as described in
topic Settings Up the IPsec Connection on page 478.
2 In the left hand pane of the dialog, point to Windows Firewall with Advanced
Security on Local Computer.
3 In the Windows Firewall with Advanced Security on Local Computer pane,
right-click on the IPsec entry and select Enable Rule or Disable Rule in the
short-cut menu.
492 4014778 Rev H

C
Appendix C
Appx auto letter
Upgrading the ROSA NMS

Software
Introduction
This appendix outlines the procedures to upgrade the ROSA NMS
system software.
In This Appendix
Introduction ......................................................................................... 494
Installing a ROSA/Copernicus Software Package on a ROSA
NMS system......................................................................................... 495
Locking and Unlocking the ROSA NMS System ........................... 496
Upgrading Client Software via a Copernicus Server or
SI-Server ............................................................................................... 499
4014778 Rev H 493

Appendix C
Upgrading the ROSA NMS Software
Introduction
To upgrade your ROSA NMS system, different upgrade procedures are foreseen.
The ROSA NMS software can be upgraded by running again the setup as described
in topic Installing the ROSA NMS Software but using ROSA/Copernicus Installation
CD-Roms with higher ROSA/Copernicus software version.
The ROSA NMS software can also be upgraded by means of software packages
received via E-mail or downloaded from our FTP server. The procedure to upgrade
a ROSA NMS system using a software package is describes in topic Installing a
Software Package on a ROSA NMS system on page 495.
The ROSA NMS Client software part of the ROSA NMS system can also be
upgraded via a Copernicus server or SI-Server. For more information, please refer
to topic Upgrading Client Software via a Copernicus Server or SI-Server on page 499.
494 4014778 Rev H

Installing a ROSA/Copernicus Software Package on a ROSA NMS system
Installing a ROSA/Copernicus Software Package on a

ROSA NMS system
Note: Software packages are delivered in a compressed format. Before upgrading
the ROSA NMS software, the package must be uncompressed.
The following procedure explains how to install a software package.
1 In the ROSA NMS user interface, point to Manage in the Server menu and click
on the Install new ROSA/Copernicus software... menu item.
2 Browse to the directory containing the uncompressed software package.

3 Point to the .RCI file and click on the Open command button.
Result: The Software Upgrading Process is started.
Note: During the upgrading process a message box might appear asking a reboot
of the computer.
Press the OK command button and reboot the computer as described in topic
Stopping, Rebooting and Starting a Server on page 133.
4014778 Rev H 495

Appendix C
Locking and Unlocking the ROSA NMS System

Introduction
When a user wants to leave a ROSA NMS system without quitting the ROSA NMS
software, the ROSA NMS system can be locked to prevent anybody from changing
settings while the user is absent. The following sub topics describe the procedures
to lock and to unlock a ROSA NMS system.
Locking a ROSA NMS System

The following procedure explains how to lock a ROSA NMS system.
1 In the Security menu, point to Lock ROSA.
Result: A Information dialog is displayed.
496 4014778 Rev H

Locking and Unlocking the ROSA NMS System
Note: By locking a ROSA NMS system, the user interfaces of all resources that are
currently opened by this ROSA NMS system are also locked. The actual displayed
user interfaces are indicated by locked in the title bar and a padlock in the user
interface.
Unlocking a Locked ROSA NMS System

Perform the following steps to unlock a locked ROSA NMS system.
1 On the Information dialog, point to the Unlock command button.
Result: The Unlock ROSA dialog is displayed.
2 Select the user ID in the User ID drop down box.

Note: Only the user who locked the ROSA NMS system and a user that is
member of the administrators group can unlock a locked ROSA NMS system.
4014778 Rev H 497

Appendix C
3 In the Password box, enter the password corresponding with the selected user
ID.
498 4014778 Rev H

Upgrading Client Software via a Copernicus Server or SI-Server
Upgrading Client Software via a Copernicus Server or

SI-Server
Introduction
Each Copernicus server and SI-Server has an installation version of the ROSA NMS
Client software part on its hard disk, called Master ROSA NMS software. When a
connection is established between a ROSA NMS Client and a server of which the
version of the Master ROSA NMS software is higher than the version of the ROSA
NMS system, a ROSA NMS Client upgrade is asked using following dialog.
If the current version of the ROSA NMS Client software is incompatible with the
version of the software on the server, no connection can be made without upgrading
of the ROSA NMS Client software. In this case the following dialog appears.
The ROSA NMS Client software will be upgraded automatically after pressing the
Yes command button.
4014778 Rev H 499

Appendix C
Notes:
The client part of the ROSA NMS Singe User software can also be upgraded by
connecting to a server with higher master ROSA NMS software version. In this
case the server part of the ROSA NMS Single User software will not be
upgraded. It is advised to upgrade the ROSA NMS Single User system by
re-installing the software from a CD-Rom with higher ROSA NMS Single User
software version.
The automatic upgrade feature is an easy way to upgrade multiple ROSA NMS
Client systems. After upgrading the software on the server, including the
master ROSA NMS version, each ROSA NMS Client system can be upgraded by
connecting to the server.
Installing a Higher Master Software Version on a Copernicus Server or SI-Server

Software packages are delivered in a compressed format. Before upgrading the
Master ROSA NMS software, the package must be uncompressed on the hard disk of
the ROSA NMS system that is used to upgrade the Master ROSA NMS software.
Perform the following steps to install a higher Master ROSA NMS software version
on a server.
connect to the server for which the Master ROSA NMS software must be
upgraded.
2 Select this server and point to Manage in the Server menu and click on the
Install new ROSA/Copernicus software... menu item.
3 Browse to the directory containing the uncompressed software package.

4 Point to the .RCI file and click on the Open command button.
Result: The Software Upgrading Process is started.
500 4014778 Rev H

Upgrading Client Software via a Copernicus Server or SI-Server
Upgrading the Client Software of a ROSA NMS Client or ROSA NMS Single User
System
The following procedure describes how to upgrade the client software of a ROSA
NMS Client or ROSA NMS Single User system using a Copernicus server or
SI-Server.
1 Connect the ROSA NMS system to a server with a higher Master ROSA NMS
software version.
Result: The ROSA upgrade preferred dialog or the ROSA upgrade needed
2 Press the Yes command button to start the upgrade process.

Result: The following warning dialog is displayed.
Please read this warning and backup the items when necessary.
the upgrading process.
4014778 Rev H 501

D
Appendix D
Appx auto letter
Connecting Units to a ROSA

NMS System
Introduction
This chapter describes how to connect devices to a ROSA NMS Single
User system or to a ROSA NMS Device Configuration Shell system
using a RS232 to RS232 connection or RS485 to RS232 connection.
In This Appendix
RS232 to RS232 Connection ............................................................... 504
RS232 to RS485 Connection ............................................................... 505
4014778 Rev H 503

Appendix D
Connecting Units to a ROSA NMS System
RS232 to RS232 Connection

Particular units are equipped with a RS232 communication port. Use a
crossed-cable (null modem cable) to connect the RS232 port of the device to the
ROSA NMS system. The following tables show how to wire the null modem cable.
DB9 DB9
Signal Pin Pin Signal
RX 2 3 TX
TX 3 2 RX
GND 5 5 GND
DB9 DB25
RX 2 2 TX
TX 3 3 RX
GND 5 7 GND
504 4014778 Rev H


Some devices are provided with a RS485 communication port. Use a RS232/RS485
adapter to connect devices with a RS485 communication port to a ROSA NMS Single
User system or ROSA NMS DCS system. The following table shows how the
output wiring of he RS232/RS485 adapter.
Output Wiring Adapter DB9 on Unit

TX+ - 5 RX+
TX- - 3 RX-
RX+ - 4 TX+
RX- - 2 TX-
GND - 7 GND
4014778 Rev H 505

Glossary
Glossary
ASI
asynchronous serial interface. Allows the intermittent transfer of data one bit at
a time rather than in a steady stream.
AIT
application information table.
ATM
asynchronous transfer mode. A network technology based on transferring data
cells of a fixed size. The small, constant cell size allows ATM devices to
transmit video, audio, and computer data over the same network without one,
single type of data dominating the line. A transmission and switching
technology that encapsulates traffic into 53-byte frames (or cells), with
sophisticated signaling and quality of service mechanisms that have been found
to be complex and non-scalable to the degree necessary for the Internet.
BAT
bouquet association table.
BTS
base transceiver station.
BTSC
Broadcast Television Systems Committee. An EIA committee created to
develop a standard for Multi-channel Television Sound (MTS) broadcasting.
The standard adopted was developed by Zenith Electronics Corporation
(transmission parameters) and dbx, Inc. (noise reduction system).
CAT
conditional access table.
SET
central European time.
4014778 Rev H 507

Glossary
SET
central European time.
COM
communication.
CRC
cyclic redundancy code.
CTRL
control.
DCOM
distributed component object model.
DCS
device configuration shell.
DLL
dynamic link library.
DVB
A standard developed by the Digital Video Broadcasting (DVB) Group, which is
a European organization that has authored many specifications for satellite and
cable broadcasting of digital signals. Part of the DVB work has been focused
specifically on conditional access.
DVP
digital video platform.
EIT
event information table.
EPG
electronic program guide.
FTP
file transfer protocol. Allows users to transfer text and binary files to and from
a personal computer, list directories on the foreign host, delete and rename files
on the foreign host, and perform wildcard transfers between hosts.
508 4014778 Rev H

Glossary
GbE or GigE
gigabit Ethernet. A LAN transmission standard that provides a data rate of 1
billion bits per second. Gigabit Ethernet is defined in the IEEE 802.3z standard.
Gigabit Ethernet is carried primarily on optical fiber.
GNE
gateway network element.
GUI
graphical user interface. A program interface that takes advantage of a
computer graphics capabilities to make the program visually easier to use.
HFC
hybrid fiber/coaxial. A network that uses a combination of fiber optics and
coaxial cable to transport signals from one place to another. A broadband
network using standard cable television transmission components, such as
optical transmitters and receivers, coaxial cable, amplifiers, and power supplies.
The broadband output stream is transmitted as an optical signal, over the
high-speed, fiber optic transmission lines to local service areas where it is split,
converted to electrical RF signals, and distributed to set-tops over coaxial cable.
HTML
hypertext mark-up language. A language used to create documents on the
World Wide Web.
HTTP
hypertext transport protocol. A communication protocol used to request and
transmit files over the Internet and other networks.
I/O
input/output.
ICMP
Internet control message protocol.
ID
identifier.
IIOP
Internet inter-ORB protocol. A protocol developed to implement CORBA
solutions over the web. It enables browsers and servers to exchange integers,
4014778 Rev H 509

Glossary
arrays, and more complex objects. It is a protocol for communication between

an application programming interface (API) and an external client.
IP
Internet protocol. A standard that was originally developed by the United
States Department of Defense to support the internetworking of dissimilar
computers across a network. IP is perhaps the most important of the protocols
on which the Internet is based. It is the standard that describes software that
keeps track of the internetwork addresses for different nodes, routes, and
outgoing/incoming messages on a network. Some examples of IP applications
include email, chat, and Web browsers.
IP address
Internet protocol address. A 32-bit sequence of numbers used for routing IP
data. Each IP address identifies a specific component on a specific network.
The address contains a network address identifier and a host identifier.
IRD
integrated receiver/descrambler. A device that receives satellite signals and
that also decodes encrypted or scrambled signals.
LAN
local area network. A communications link between two or more points within
a small geographical area, such as between buildings. Typically permits data
rates up to 100 Mbps. Smaller than a metropolitan area network (MAN) or a
wide area network (WAN).
MEM
multi-encoder manager.
MIB
management information base. SNMP collects management information from
devices on the network and records the information in a management
information base. The MIB information includes device features, data
throughput statistics, traffic overloads, and errors.
MSDE
Microsoft SQL desktop edition.
NICAM
near-instantaneous companded audio multiplex. A format for digital sound on
analog television transmissions.
510 4014778 Rev H

Glossary
NIT
network information table.
NMS
network management system. A software system designed specifically to
monitor a network and to facilitate troubleshooting.
NTSC
National Television Standards Committee. A committee that determines video
signal standards for television displays in the United States, Canada, Mexico,
and Japan, as well as other Latin American and Asian countries. The NTSC
standard calls for fixed-resolution, interlaced displays that are updated 30 times
per second with a resolution of 525 lines.
OID
object identifier.
OLE
object linking and embedding.
PAL
phase alternate line.
PAT
program association table.
PC
personal computer.
PID
packet identifier or program identifier.
PMT
program map table. Identifies and indicates the locations of the streams that
make up each service, and the location of the Program Clock Reference fields for
a service.
PSI
program specific information.
4014778 Rev H 511

Glossary
PVC
permanent virtual circuit. Data path that someone creates manually and that
continues to exist on a DBDS until someone manually removes it.
QoS
quality of service. The level of service provided in terms of delay, throughput,
reliability and cost. QoS is the concept that transmission rates, error rates, and
other characteristics can be measured, improved, and to some extent, guaranteed
in advance.
RCDS
remote control and diagnostics system.
RF
radio frequency. The frequency in the portion of the electromagnetic spectrum
that is above the audio frequencies and below the infrared frequencies, used in
radio transmission systems.
RMA
return material authorization. A form used to return products.
ROSA
RCDS open system architecture.
RX
receive or receiver.
SDH
synchronous digital hierarchy. The optical transmission standard used by most
countries outside North America and very equivalent to SONET. SDH (or
STM-1) frames are made up of 270 bytes of 8 bits each by 9 rows.
SDT
service description table.
SECAM
squentiel couleur avec mmoire. (French color TV standard.)
SI
system or service information. Tuning information sent from the DNCS to
DHCTs which provides the information that DHCTs need to be able to tune to a
512 4014778 Rev H

Glossary
particular service.
SLA
service level agreement. A contract between a network service provider and a
customer that specifies, usually in measurable terms, what services the network
service provider will furnish.
SMS
short message service. (Cellular phone text messaging.)
SNMP
simple network management protocol. A protocol that governs network
management and the monitoring of network devices and their functions.
SQL
structured query language.
SU
single-user.
SVC
switched virtual circuit.
SVGA
super video graphics adapter. (800 by 600 pixels, 1.33:1 aspect ratio.)
TCP/IP
transmission control protocol/Internet protocol. Two interrelated protocols that
are part of the Internet protocol suite. TCP operates on the OSI transport layer
and breaks data into packets. IP operates on the OSI network layer and routes
the packets. While IP takes care of handling the actual delivery of the data, TCP
takes care of keeping track of the individual units of data (called packets) that a
message is divided into for efficient routing through the Internet.
TV
television.
TX
transmit or transmitter.
4014778 Rev H 513

Glossary
UDD
universal device driver.
UPS
un-interruptible power supply.
WAN
wide area network. A WAN consists of two or more LANs. The largest WAN
in existence is the Internet. A data communications network that serves users
across a wide-ranging geographic area and often uses transmission devices
provided by common carriers. Frame Relay, SMDS, and X.25 are examples of
WANs.
XT
extended.
514 4014778 Rev H

Index
Index
Additional Info parameter 39
3 Additional Information parameter 121
3DES 465 Additional message information 211
Adjusting Date and Time 149
A Administrative password 451
A specific IP Address parameter 461 Administrative user password 153
Ack Source parameter 209 Advanced tab page 163
Ack Time parameter 209 Alarm Color parameter 45
Acknowledged parameter 216 Alarm Coloring parameter 266
Acknowledging messages 204, 223 Alarm Correlation Domain Scripts 249
Activate the default response rule parameter Alarm correlation domains 248
469 Alarm Correlation Domains dialog 250
Active FTP 163 Aligning map objects 323
Active user 365 All Messages button 32
Add Analog Satellite Channel dialog 183 Analog Headend Backup Task 6
Add Analog TV Channel dialog 175 Analog Satellite Channels 183
Add Analog TV Service dialog 166 Analog Satellite Channels dialog 183
Add Audio Subcarrier dialog 183 Analog TV Channels 175
Add Availability Data dialog 349 Analog TV Channels dialog 175
Add I/O Port dialog 113 Analog TV Services 166
Add relation dialog 333 Analog TV Services dialog 166
Add Standalone Snap-in dialog 457 Animate parameter 45
Add Unit dialog 99, 183 Arc object 299
Add/Remove Snap-in dialog 457 Arc Tool button 33
Adding a server 125 Ask me what I want at that moment parameter
Adding analog satellite channels 183 266
Adding analog TV channels 175 Assigning attributes 198
Adding analog TV services 166 Assigning priorities to analog TV services 168
Adding attributes 194 Assigning serial port drivers 79
Adding bitmap illustrations 306 ATM Service Management 12
Adding Input/Output ports 113 Attributes 194
Adding locations 197 Attributes button 32
Adding map links 315 Attributes dialog 194
Adding message attachments 225 Attributes of dialog 198
Adding message rules scripts 234 Audio Subcarrier parameter 183, 186
Adding performance bars 326 Audio System parameter 175, 177
Adding predefined message filters 218 Authentication method preference order
Adding relations 333, 337 parameter 469
Adding resources to maps 293 Authentication Methods tab 469
Adding text object 302 Auto Connect Parameters 131
Adding units to groups 94 Automatic zoom map parameter 266
Adding users to maps 373 Availability data 349
4014778 Rev H 515

Index
Available Standalone Snap-ins list 457 Communicating with computers that do not
support IPsec page 465
B Communication parameter 216
Backup active message logging 240 Company Name parameter 73
Backup Active Message Logging parameter Component driver User's Guides xix
240 Component drivers 66
Bandwidth parameter 183, 186 Component layout of resources 295
Benefits 3 Computer Name parameter 125, 150, 154
Bzier curve object 299 Configuration file 249
Bezier Tool button 33 Connecting to a server 128
Bitmap illustrations 306 Connecting units 503
Bitmap parameter 106 Connection Security Rules parameter 478
Bitmap Tool button 33 Control button 26
Bitmaps button 32 Control menu 26
Copy button 33
C Copying map objects 321
Cache map components parameter 266 Copying maps 285
Change Computer Name dialog 151 Copying Messages to the Clipboard 230
Change Current User Password dialog 48, 55, Copying Server Inventories 138, 140
366 Copying traces to a file 158
Change Source dialog 313 Count parameter 209
Changing a title of a note 119 CRC Checking when File Version Equal
Changing active user dialog 365 parameter 85
Changing Administrative User Password 153 Creating maps 272
Changing attribute values 199 Creating nested folders 88
Changing computer name 151 Creating new group 93
Changing GUI update behavior 85 Creating New Security Groups 354
Changing map mode 265 Creating notes 117
Changing map object drawing order 323 Creating unit folders 88
Changing map options 266 Creating Users 362
Changing Network Settings 154 Critical parameter 216
Changing resource bitmaps 270 Currently connected clients 130
Changing server settings 150 Currently defined I/O ports 110
Changing text object 303 Custom parameter 465
Changing Unit Settings 106, 108 Custom Security Method Settings dialog 465
Changing view options 45 Customize Advanced Key Exchange Settings
ChannelID parameter 175, 177 dialog 485
Channels 165 Customize Data Protection Settings dialog 485
Checking I/O ports 111 Customize IPsec Settings dialog 485
Cleaning message database 255 Cut button 33
Cleared perameter 216
D
Client/Server Architecture 124
Clients currently conneted to server dialog 130, Data integrity and encryption (ESP) parameter
145 465
Closing maps 274 Data integrity and encryption list 485
Color dialog 300, 301, 317 Data protection (Quick Mode) parameter 485
Color Palette 34 Date and Time 148
Color Palette button 33 Date parameter 216
Color System parameter 175, 177 DebounceTime parameter 249
Common User Interface 97 Default client 146
Default Gateway parameter 154
516 4014778 Rev H

Index
Default Unit parameter 45 Editing an analog TV channel 177

Defining Default Client 146 Editing analog satellite channels 186
Delete it also in the database parameter 266 Editing analog TV services 168
Delete Messages dialog 255 Editing Attributes 195
Delete only the visual representation parameter Editing map mode 265
266 Editing OLE objects 311
Delete Quality Data dialog 351 Ellipse object 298
Deleting map links 320 Ellipse Tool button 33
Deleting maps 276 Embedding OLE objects 309
Deleting message attachments 226 Enabling IPsec 492
Deleting non-pending messages 228 Enabling message maintenance rules 258
Deleting notes 120 Enabling message rules 235
Deleting quality data 349 Enabling tracing 156
Demo quality data 347 Encryption algorithm parameter 465, 485
Demo units 99 Environmental parameter 216
Description parameter 194, 195 Equipment parameter 216
Device Driver parameter 99 Exclude from Monitoring mode 100
Device driver User's Guides xix Existing Filters list 220, 222
Device drivers 66 Export Security Settings dialog 368, 369
Digital Headend Backup Task 5 Exporting messages 231
Disabling IPsec 492 Exporting security settings 368, 369
Disabling message maintenance rules 258 Exporting unit details 104
Disabling message rules 235 Extension parameter 183, 186
Disabling tracing 156
Disconnecting a server 130
F
Display Options dialog 157 Features 3
Displaying Server Explorer box 37 File Name parameter 73
Displaying unit information 121 File Version Checking parameter 85
Do not communicate with computers that do not File Version parameter 73
support IPsec parameter 465 Fill properties 301
Docked Server Explorer box 37 Filter Action General Options page 465
Don't Show parameter 216 Filter Action Name page 465
Draw Text dialog 302 Filter Action tab 469
Drawing tools 296 Filter dialog 110, 173, 181, 190, 340
Driver details 73 Filter Name parameter 216
Driver Details dialog 73 Filtering analog satellite channels 190
Driver installation 68 Filtering analog TV channels 181
Driver parameter 93, 98 Filtering input/output ports dialog 111
Driver Type parameter 73 Filtering messages 216
Drivers, uninstalling 77 Filtering relations 340
Filtering trace files 157
E
Find a Resource button 32
Edit Analog Satellite Channel dialog 186 Find a Resource dialog 39
Edit Analog TV Service dialog 168 Find any item in global explorer parameter 39
Edit Attribute dialog 195 Find resource in maps dialog 295
Edit Location dialog 200 Finding resources in maps 295
Edit Properties parameter 469 Floating Server Explorer box 37
Edit Rule Properties dialog 469 Folders 88
Edit Unit 108 Font dialog 317
Edit Value of Attribute dialog 199 Font Height parameter 45
Editing a note 119
4014778 Rev H 517

Index
Force Downgrade when Server File Version is Indeterminate parameter 216

Lower parameter 85 Indicators propagation 45
Freeform shape object 298 Info parameter 157
Frequency parameter 175, 177, 183, 186 Information dialog 496
From parameter 216 Information parameter 216
FTP mode 163 Ingress Monitoring Component 11
Input parameter 110
G Input/output ports 110
General tab 469 Input/Output Ports dialog 110, 114
Generate Quality Demo Data dialog 347 Insert Object dialog 309
Generation Time parameter 209 Installation
Get Drivers From Server 71 Drivers 68
Getting drivers 71 Installed Bitmaps dialog 270
Getting Started Installed Drivers dialog 60, 69, 71, 75, 77
ROSA Client system 52 Installed License File dialog 63
ROSA Device Configuration Shell system Installing license file 63
55 Integrity algorithm parameter 465, 485
ROSA Single User system 48 Integrity and Encryption Algorithms dialog 485
Give the map another name parameter 285 Internet Protocol security 456
Global Inventory 138 Inventory Synchronization dialog 138, 140,
Graghical Quality Statistics button 32 141, 142, 144
Grid color 282 IP Address dialog 478
Grid Toggle button 33 IP Address parameter 154
Group Explorer IP Filter Description and Mirrored property page
Displaying 92 461
Grouping map objects 324 IP Filter List dialog 461
Groups 91 IP Filter List tab 469
Groups parameter 73 IP Filter Properties dialog 461
Group-wise Equipment Manager 5 IP Protocol Type page 461
GUI Update Behavior 85 IP Security Policy Name page 469
IP Traffic Destination page 461
H IP Traffic Security page 465
Handling Units 82 IP Traffic Source page 461
Hardware Use's Guides xix IPsec 456
Headend IPs parameter 469 IPsec management console 457
Headend IPSec Filter parameter 469 IPsec Settings tab 485
Headend IPsec Filter Properties dialog 465
K
Headend Maps 262
Headend Policy Properties dialog 469 Key exchange (Main Mode) parameter 485
Help button 32 Key exchange algorithm parameter 485
HFC Alarm Correlation 11, 248 Key Exchange Security Methods dialog 469
Hidden messages 238 Key Exchange Settings dialog 469
Hiding Server Explorer box 37 Key lifetime (in KB) parameter 485
Host ID 62 Key lifetime (in minutes) parameter 485
Key parameter 478
I
L
Icons parameter 266
iLynx Backbone Model 10 Last parameter 216
Image Properties dialog 307 Last Resource parameter 130
Importing maps 275 Layout Listening Console Window 243
Importing security settings 368, 371 Legend 35
518 4014778 Rev H

Index
Legend dialog 35 Map settings 280

Level parameter 216 Map size 280
License errors 60 Map Synchronization dialog 285, 289
License file Map Tool button 33
Installing 63 Map Tools tool bar 33
Obtaining 61 Map views 278
Line object 297 Maps 262
Line properties 300 Master Server 137
Line Tool button 33 Maximize user interface 25
Link to External Web Server 239 MD5 465
Link to External Web Server parameter 239 Menu bar 26
Links dialog 313 Menu Name parameter 239
Listening console 241 Merge the client and the master map parameter
Listening Console Layout dialog 243 285
Listening console message filter 244 Message Attachment dialog 224, 225
Listening Console window 242 Message attachments 224, 225
Listening mode 242 Message categories 242
Loading channels 178 Message Database 204, 254
Local computer parameter 457 Message database maintenance dialog 255
Local control units 87 Message details 214
Location dialog 106, 166, 175, 183, 197 Message Filter dialog 216, 218, 220, 244
Location parameter 99, 106, 130, 166, 168, Message Info parameters 216
175, 177, 183, 186 Message Information dialog 211
Locations 197 Message maintenance rule details 259
Locations button 32 Message maintenance rule scripts 257
Locking ROSA system 496 Message maintenance rules 257
Log new Messgae dialog 232 Message Maintenance Rules dialog 258
Logging manual created messages 232 Message notification 204, 237
Login Name parameter 130 Message Options dialog 237, 238, 239, 240
Message rules 234
M Message Rules dialog 234, 235
Maintenance mode 100 Message severity 204
Make Task dialog 75 Message statistics 254
Making task instance 75 Message Statistics dialog 254
Manage Filter Actions tab 465 Message Subject parameters 216
Manage IP filter lists and filter Actions dialog Message to dialog 145
461 Message types 204
Management mode 100 Message viewer 204, 207
Map color 282 Message Viewer dialog 204, 209
Map Component Layout dialog 295 Message viewer icons 208
Map grid 280 Message Viewer layout 212
Map Link Properties dialog 317 Message Viewer toolbar 208
Map links 315 Messages 203
Map linl appearance 317 Messenger service 448
Map modes 265 Minimize user interface 25
Map objects 292 Minimum password length parameter 377
Map options 266 Minor parameter 216
Map Options dialog 266 Mirrored. Match packets with the exact opposite
Map permission 375 source and destination addresses parameter
Map Properties dialog 280, 281, 282 461
Map security 373 MMC main screen 457
4014778 Rev H 519

Index
Modify group dialog 94, 96 Notes 116

Modulator Auto-leveling Task 9 Notes for dialog 118, 119, 120
Module parameter 130, 157 Notification Task 5
Move unit(s) to folder dialog 89, 90 Numeric parameter 194, 195
Moving map objects 323
Moving unit folders 89, 90
O
Msg Info parameter 209 Object Type ID parameter 73
Msg Level parameter 209 Object type Name parameter 266
Msg Subject parameter 209 ObjectTypeIDActiveUnits parameter 249
Msg Type parameter 209 ObjectTypeIDPassiveUnits parameter 249
Multi-encoder Manager 9 ObjectTypeIDTopNode parameter 249
Multiple Instances parameter 73 Obtaining license file 61
My IP Address parameter 461 Old Computer Name parameter 151
Old Password 48, 55, 153
N
OLE object 299, 309
Name parameter 39, 88, 90, 93, 98, 99, 106, Opening a note 118
166, 168, 183, 186, 194, 195, 197, 461, 469, Opening common user interface 97
478 Opening listening console 242
Negotiate Security parameter 465 Opening maps 274
Network monitoring topology maps 263 Opening message attachments 226
Network settings 154 Opening user interface units 83
Network structure maps 262 Operational map mode 265
New Attribute dialog 194 Overwrite the master map parameter 285
New Authentication Method Properties dialog
469
P
New Computer Name parameter 151 Parent Device parameter 113
New Connection Security Rule Wizard - Parent Location parameter 110, 197
Authentication Method dialog 478 Parent Map button 32
New Connection Security Rule Wizard - Parent Name parameter 110
Endpoints dialog 478 Passive FTP 163
New Connection Security Rule Wizard - Name Password 48, 55, 128
dialog 478 Paste button 33
New Connection Security Rule Wizard - Profile Pasting map objects 321
dialog 478 Pending messages 204
New Connection Security Rule Wizard - Pending Messages button 32
Requirements dialog 478 Pending parameter 216
New Connection Security Rule Wizard - Rule Performance bars 326
Type dialog 478 Performance Data Compression Task 7
New Folder dialog 88 Performance dialog 326
New Group dialog 93 Performance Logging Task 7
New IP Filter List 461 Performance monitoring 344
New location dialog 197 Permission for map dialog 373, 375, 376
New Password 48, 55, 153 Permission for user dialog 375
New Rule Properties dialog 469 Pinting maps 283
New Security Group dialog 354 Please specify a title for the note dialog 117
New Users dialog 362 Polarity parameter 183, 186
New Value for Attribute 198 Polygon object 297
New/Link Map dialog 272, 315 Polygon Properties dialog 301
No date/time filtering parameter 216 Polygon Tool button 33
Non-pending messages 204 Port Name parameter 110, 113
Not Acknowledged button 32 Port Nr parameter 110, 113
520 4014778 Rev H

Index
Port Type parameter 113 Removing analog satellite channels 189

Predefined message filters 218 Removing analog TV channels 180
Predefined Message Filters dialog 218, 220, Removing attributes 196, 200
222 Removing Input/Output ports 114
Preferences dialog 85, 131, 161 Removing Locations 201
Preshared Key parameter 478 Removing map objects 322
Print button 33 Removing maps 290
Print dialog 115, 159, 172, 179, 188, 229, 284, Removing messages 247
339 Removing relations 335, 338
Print preview 283 Removing resources from maps 295
Print Setup dialog 283 Removing security groups 359
Printing analog satellite channels 188 Removing Server Inventories 144
Printing analog TV channels 179 Removing units 103
Printing analog TV services 172 Removing Units 96
Printing list of I/O ports 115 Removing users 365
Printing messages 229 Removing users from maps 376
Printing relations 339 Rename Folder dialog 90
Printing traces 159 Rename Goup dialog 98
Priority parameter 168 Renaming a group 98
Processing parameter 216 Renaming locations 200
Propagate 'Notes Present' indicator on resources Renaming maps 274
45 Renaming Units folder 90
Protocol driver User's Guides xix Repairing maps 291
Protocol drivers 66 Repetitive alarm suppression 238
Protocol parameter 485 Repetitive Alarm Suppression parameter 238
Reporting Component 6, 346
Q Reporting dialog 346
Quality of Service parameter 216 Requests for Secure Communication page 469
Required authentication for inbound and
R outbound connections parameter 478
Range parameter 216 Required Core parameter 73
RCDS drivers 66 Resetting pending messages 226
Rebooting a server 135 Resizing bitmap illustrations 307
Rectangle object 297 Resizing map objects 322
Rectangle Properties dialog 300 Resizing Server Explorer box 37
Rectangle with rounded corners object 298 Resolve map conflict dialog 285, 289
Refresh Explorer button 32 Resource bitmaps 268
Registration Time parameter 209 Resource Drivers button 32
Related publications xix Resource ID parameter 121
Relation properties 334 Resource map objects 292
Relation Properties dialog 334 Resource related icons 41
Relations 331 Resource Settings dialog 106, 270
Relations button 32 Restore user interface size 25
Relations dialog 336, 337, 338 Rextangle Tool button 33
Relations in maps 333 RF Level Connection parameter 175, 177
Relations Tool button 33 ROSA Headend Applications 9
Remote control units 87 ROSA Login dialog 48, 55, 128
Removing a folder 91 ROSA Macro Component 8
Removing a group 98 ROSA Unit Options dialog 121
Removing a server 127 ROSA Users 362
Removing analmog TV services 170 RoundRect Tool button 33
4014778 Rev H 521

Index
RS232 connection 504 Service drivers 66

RS485 connection 505 Service Priorities dialog 168
Services 165
S Session key perfect forward secrecy parameter
Safe Operations xvii 465
Satellite parameter 183, 186 Set Priority dialog 168
Save as Predefined Message Filter dialog 216 Shortcut Keys 28
Save Map button 33 Show Acknowledged parameter 216
Saving maps 275 Show All parameter 216
Scrambing parameter 175, 177, 183, 186 Show not Ack parameter 216
Searching into the Server Explorer tree 39 Show not Pending parameter 216
Security 353 Show parameter 216
Security actions overview 360 Show Pending parameter 216
Security Group Properties dialog 354, 357 Show relations parameter 266
Security Groups dialog 354, 357, 359 SI-Editor 9
Security Method dialog 485 SNMP Profile Manager 8
Security method preference order list 469 Software versions 3
Security methods parameter 485 Source Location parameter 209
Security Methods tab 465 Source Name parameter 209
Security Options dialog 377 Source Type parameter 209
Select Computer or Domain dialog 457 Specify filter dialog 94, 96
Select Predefined Message Filter dialog 220 Standalone tab 457
Selecting map objects 321 Status bar 27
Selecting predefined message filters 220 Status Color parameter 45
Selection Tool button 32 Status parameter 73
Send to Computer parameter 146 Stopping Server Software 135
Sending Messages 145 Stopping, Rebooting, and Starting a server 133
Sending messages between ROSA systems 145 Store selected channels to monitoring device(s)
Serial port drivers 66 dialog 178
Serial Port Icons 79 Store selected channels to sat receiver(s) dialog
Serial Ports button 32 187
Server Administrative User dialog 153 Storing analog satellite channels 187
Server Availability 161 Storing channels 178
Server Computer Name dialog 151 Subnet Mask parameter 154
Server Explorer 36 Synchronisation dialog 148
Browsing through 38 Synchronizing Date and Time 148
Icons 40 Synchronizing maps 285
Moving Server Explorer box 37 System requirements 4
Server HostID dialog 62 System security 353
Server identification settings 150
T
Server Name parameter 125, 150, 151, 154
Server Network Settings dialog 154 Task configuration maps 264
Server Options dialog 146 Task driver User's Guides xix
Server Page parameter 239 Task drivers 66
Server related icons 40 Task Instance 75
Server Serial Port Configuration dialog 79 Task Name parameter 75
Server Serial Port dialog 79 Text alignment 306
Server Settings dialog 125, 150 Text font 305
Server Tools tool bar 32 Text object 302
Servers 123 Text Properties dialog 303
Service Availability Reporting Component 7 Text Tool button 33
522 4014778 Rev H

Index
These IP addresses parameter 478 User Properties dialog 363

Third Party Equipment Integration Tools 8 User-defined bitmaps 268
This IP address or subnet parameter 478 Users 362
ThreadID parameter 157 Users dialog 362, 365, 373
Time parameter 216 Using HFC alarm correlation 251
Title bar 25
Title parameter 117, 119
V
To parameter 216 Video analysis task 10
To Unassign IPSec 476 Video Deemphasis parameter 183, 186
Toggle Editing Mode button 32 Video Modulation parameter 183, 186
Toggle Snapping button 33 View Message using Default Filter button 32
Tool bar 30 View Options dialog 45
Tool bars 30 Viewing alarm correlation domains 250
TopNodeTxPinName parameter 249 Viewing trace files 156
Trace files 155
Transmission Standard parameter 175, 177 W
Transponder parameter 183, 186 Warning parameter 216
Type parameter 110, 216 Which computers are in Endpoint 1? parameters
478
U
Which computers are in Endpoint 2? parameters
UDD Profile Manager 8 478
Ungrouping map objects 324 Windows buttons 25
Uninstall driver(s) confirmation 77 Windows Firewall with Advanced Security
Uninstalling bitmaps 270 dialog 478
Uninstalling Drivers 77 Windows Firewall with Advanced Security on
Unit Folders 88 Local Computer dialog 485
Unit Groups 91
Unit Name parameter 266 Z
Unit related icons 41 Zoom Tool button 32
Unit Settings 106 Zooming in on maps 277
Units dialog 99, 103, 105, 108, 183 Zooming out on maps 277
Units icon 32
Unlock ROSA dialog 497
Unlocking ROSA System 496
Update maps 289
Updating performance bars 329
Updating Server Inventories 141, 142
Upgrading ROSA software 493
UPS Battery Maintenance Task 11
Use Add Wizard parameter 461
Use Passive FTP (for firewall compatibility)
parameter 163
Use this string (preshared key) parameter 469
User Account Control dialog 478
User group properties 357
User ID 48, 55, 128
User Interface 24
User interface units 83
User Name parameter 153
User Password 366
User Properties 363
4014778 Rev H 523

Scientific-Atlanta Europe bvba Luipaardstraat 12 B-8500 Kortrijk, Belgium
www.scientificatlanta.com
This document includes various trademarks of Cisco Systems, Inc.
Please see the Trademarks section of this document for a list of the Cisco Systems, Inc.,
trademarks used in this document.
All other trademarks mentioned in this document are the property of their respective owners.
Product and service availability subject to change without notice.
2009 Scientific-Atlanta Europe bvba. All rights reserved.
November 2009 Printed in Belgium Part Number 4014778 Rev H

ROSA NMS Configuration Manual

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ROSA NMS Configuration Manual

Hochgeladen von

Copyright:

Verfügbare Formate

4014778 Rev H

For Your Safety

Explanation of Warning and Caution Icons

4014778 Rev H iii

Safe Operations xvii

Chapter 1 Introducing ROSA NMS 1

Chapter 2 Installing the ROSA NMS Software 13

Chapter 3 Using the ROSA NMS User Interface 23

4014778 Rev H vii

About the Server Explorer .................................................................................................... 36

Chapter 4 Getting Started 47

Chapter 6 Working with Drivers 65

Chapter 7 Working with Resources 81

viii 4014778 Rev H

Working with Unit Groups ..................................................................................... 91

Chapter 8 Working with Servers 123

To Define a Master Server ..................................................................................... 137

Chapter 9 Working with Services and Channels 165

Configuring the Filter............................................................................................. 173

Chapter 10 Working with Attributes and Locations 193

Chapter 11 Working with Messages 203

Viewing Messages ............................................................................................................... 207

xii 4014778 Rev H

Cleaning the Message Database ........................................................................... 255

Chapter 12 Working with Maps 261

4014778 Rev H xiii

Grouping and Ungrouping Objects ..................................................................... 324

Chapter 13 Working with Relations 331

Chapter 14 Performance Monitoring 343

Chapter 15 ROSA NMS System Security 353

xiv 4014778 Rev H

Exporting and Importing Security Settings ..................................................................... 368

Chapter 16 ROSA High Availability Solution 379

Appendix A Customer Information 443

Appendix B Additional Configuration 447

To Configure IPsec on a Computer Running Windows XP or

Appendix C Upgrading the ROSA NMS Software 493

Appendix D Connecting Units to a ROSA NMS System 503

xvi 4014778 Rev H

4014778 Rev H xvii

4014778 Rev H xix

Maddox Router, part number: 6985050

4014778 Rev H xxi

Trilithic Protocol - User Manual, part number: 6984848

xxii 4014778 Rev H

About the ROSA Network Management System

Features and Benefits

ROSA NMS Software Versions

General Add-On Components for ROSA NMS

ROSA Advanced Configuration

ROSA NMS Automation and Redundancy Tasks

Triggered by device alarm, I/O contact closure or channel alarm

Analog Headend Backup Task

ROSA NMS Performance and Trending

Performance Logging Task

Performance Data Compression Task

Service Availability Reporting Component

ROSA NMS Macro Component

Third Party Equipment Integration Tools

SNMP Profile Manager

Highly reliable integration; no software development involved

ROSA NMS Headend Applications

ROSA NMS DVB SI-Editor

Fine tune statistical multiplexing for all services