Rosa em - User's Guide - 4005743n

4005743 Rev N
ROSA Element Manager

User's Guide
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.
4005743 Rev N iii

Notices
Notices
Trademark Acknowledgments
Cisco, the Cisco logo, and ROSA are trademarks or registered trademarks of Cisco
and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks
can be found at www.cisco.com/go/trademarks.
Other third party trademarks mentioned are the property of their respective owners.
The use of the word partner does not imply a partnership relationship between
Cisco and any other company. (1009R)
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
2012 Cisco and/or its affiliates.
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.
4005743 Rev N v
Contents
Contents
For Your Safety iii
Notices v
Safety Precautions xv
Preface xvii
Chapter 1 Introduction 1
About the ROSA Element Manager ...................................................................................... 2
Introduction ................................................................................................................. 2
Operation ..................................................................................................................... 3
Client Options ............................................................................................................. 4
Features and Benefits ................................................................................................. 5
Used Terminology ...................................................................................................... 6
Steps to Take ............................................................................................................................. 7
Introduction ................................................................................................................. 7
Installation of the Device ........................................................................................... 7
Setup of the Device ..................................................................................................... 7
Device Functionality ................................................................................................... 7
Integration of the Device............................................................................................ 7
Device Maintenance ................................................................................................... 8
Additional Functionality............................................................................................ 8
Backup Operation ....................................................................................................... 8
Quick Installation Reference ..................................................................................... 8
LED Indicators.......................................................................................................................... 9
Introduction ................................................................................................................. 9
LED Description .......................................................................................................... 9
Product Information .............................................................................................................. 11
Introduction ............................................................................................................... 11
ID Label ...................................................................................................................... 11
Chapter 2 Setup 13
Installing the ROSA EM Configuration Tools ................................................................... 14
Introduction ............................................................................................................... 14
System Requirements ............................................................................................... 15
4005743 Rev N vii

Contents
Installing Windows 2000 Service Pack 3................................................................ 15

Installing Microsoft Internet Explorer ................................................................... 16
To Install the ROSA EM Configuration Tools ...................................................... 16
To Repair the ROSA EM Configuration Tools...................................................... 20
To Uninstall the ROSA EM Configuration Tools ................................................. 22
Changing the FTP Mode .......................................................................................... 24
Network Configuration......................................................................................................... 25
Introduction ............................................................................................................... 25
Configuring IP Settings using the ROSA EM GUI ............................................... 25
Configuring IP Settings using the Craft Interface ................................................ 28
Configuring IP Settings With the Microsoft Windows Based IP
Configuration Tool ................................................................................................ 34
Configuration of Second Network Interface Connector ..................................... 37
Adding Devices and Groups ................................................................................................ 38
Introduction ............................................................................................................... 38
Device List Concept .................................................................................................. 38
Downloading the Device List .................................................................................. 39
Editing the Device List File...................................................................................... 40
Uploading the Device List ....................................................................................... 47
Chapter 3 Configuring the ROSA EM System 49

Using the ROSA EM Device GUI......................................................................................... 50
Introduction ............................................................................................................... 50
Opening the ROSA EM Configuration GUI.......................................................... 50
Changing the View Mode ........................................................................................ 53
Tool Tips..................................................................................................................... 54
Working with ROSA EM Operator Accounts .................................................................... 55
Adding ROSA EM Operator Accounts .................................................................. 55
Viewing the ROSA EM Operator Account List .................................................... 56
Deleting a ROSA EM Operator Account ............................................................... 57
Changing a ROSA EM Operator Password .......................................................... 57
Configuring Client Computer Connection Feature .......................................................... 59
Introduction ............................................................................................................... 59
Defining an IP Address ............................................................................................ 59
To Set the Accept Any Client Option ..................................................................... 60
Viewing the IP Addresses of the Connected Client Computers ........................ 60
Using Log Information .......................................................................................................... 61
Viewing the ROSA EM Device Log Pages ............................................................ 61
Creating and Viewing a Log File ............................................................................ 62
Deleting Log Files ..................................................................................................... 65
Log Date and Time ................................................................................................... 66
Changing the Device Time ................................................................................................... 67
Introduction ............................................................................................................... 67
Changing the Local Time ......................................................................................... 67
Synchronizing the ROSA EM Device with an External Device.......................... 68
Configuring ROSA EM as a Time Server .............................................................. 71
viii 4005743 Rev N

Contents
Managing Services ................................................................................................................. 72

Introduction ............................................................................................................... 72
Setting FTP and Telnet Passwords ......................................................................... 72
Setting SNMP Community Strings......................................................................... 75
Setting an FTP Upload Password on ROSA EM .................................................. 76
Enabling and Disabling Services on ROSA EM .................................................... 78
Viewing Active TCP/UDP Ports on ROSA EM ................................................... 79
Alarm Processing ................................................................................................................... 81
Introduction ............................................................................................................... 81
To Set the ROSA EM Alarm Parameters ............................................................... 82
To Set the Device Alarm Parameters...................................................................... 82
Filtering Toggling Alarms ....................................................................................... 83
Enhanced Redundancy Trigger Logic ................................................................... 85
Working with Devices and Groups ..................................................................................... 91
Introduction ............................................................................................................... 91
Adding Devices ......................................................................................................... 91
Adding Groups ......................................................................................................... 92
Delete a Device or Group......................................................................................... 93
Configuring Device Polling .................................................................................................. 95
Introduction ............................................................................................................... 95
To Configure Device Polling ................................................................................... 96
Switching On or Off the Polling Actions of a Device .......................................... 97
Executing a Polling Action Manually .................................................................... 98
Working with Alarms............................................................................................................ 99
Reporting the Active Alarms................................................................................... 99
Enabling or Disabling the Blink Not Acknowledge Feature .............................. 99
Executing the Acknowledge-All Alarms Feature............................................... 100
Viewing or Changing the Severity Color Code .................................................. 100
Viewing the Hardware and Software Information ......................................................... 102
Introduction ............................................................................................................. 102
Viewing the Hardware and Software Information ............................................ 102
Checking the ROSA EM Device Temperature and Voltage Levels .............................. 104
Introduction ............................................................................................................. 104
To Check the Device Temperature and Voltage Levels .................................... 104
Changing the Device Temperature Unit.............................................................. 105
Sending Traps ....................................................................................................................... 106
Configuring the Trap Traffic ................................................................................. 106
Configuring Trap Buffering................................................................................... 108
Disabling Trap Regeneration for Devices in Maintenance Mode or Off-
Scan Mode............................................................................................................. 112
Resetting the ROSA EM Device Parameters .................................................................... 114
Introduction ............................................................................................................. 114
To Reset the ROSA EM Device Parameters......................................................... 114
Restarting the ROSA EM Device ....................................................................................... 116
Introduction ............................................................................................................. 116
Restarting the ROSA EM Device from a Remote Location ............................... 116
4005743 Rev N ix
Contents
Device Backup Operation ................................................................................................... 118

Introduction ............................................................................................................. 118
To Enable or Disable Device Backup ................................................................... 118
Configuring HFC-Plant-Monitoring ................................................................................. 119
Introduction ............................................................................................................. 119
To Configure HFC-Plant-Monitoring .................................................................. 119
Using Maintenance Mode ................................................................................................... 121
Introduction ............................................................................................................. 121
Switching On or Off the Maintenance Mode ...................................................... 121
Switching On or Off Trap Generation for Devices in Maintenance
Mode ...................................................................................................................... 122
Using the Debug Mode ....................................................................................................... 123
Introduction ............................................................................................................. 123
To Enable or Disable a Debug Mode.................................................................... 123
Configuring Second NIC and Routing ............................................................................. 124
Introduction ............................................................................................................. 124
Second NIC .............................................................................................................. 125
Routing ..................................................................................................................... 126
Topology Example .................................................................................................. 128
Application Example: Prisma DT Automatic Rerouting................................... 128
Configuring NIC Teaming for High Reliability .............................................................. 131
Introduction ............................................................................................................. 131
Configuring NIC Teaming..................................................................................... 131
Performing a Manual NIC Switch Over .............................................................. 132
Configuring IPsec ................................................................................................................ 133
Introducing IP Security .......................................................................................... 133
Setting the Security Level ...................................................................................... 134
Adding or Removing Clients to or from the IPsec Peers List ........................... 135
Adding or Removing a DCM to or from the IPsec Peers List .......................... 136
Bypassing IPsec by using the Craft Interface ...................................................... 136
Chapter 4 Configuring the Input/Output Functionality 139

General .................................................................................................................................. 140
Introduction ............................................................................................................. 140
Viewing Device Properties .................................................................................... 140
Changing the Identification Settings of the I/O Functionality ........................ 141
Viewing the Inputs and Outputs Parameters ..................................................... 142
Configuring the Digital Outputs ....................................................................................... 144
Introduction ............................................................................................................. 144
Configuring a Digital Output................................................................................ 144
Device Alarm Propagation via Digital Outputs ................................................. 146
Configuring the Digital Inputs........................................................................................... 148
Introduction ............................................................................................................. 148
Configuring a Digital Input ................................................................................... 149
Configuring the Analog Inputs .......................................................................................... 152
Introduction ............................................................................................................. 152
x 4005743 Rev N
Contents
To Configure an Analog Input .............................................................................. 154

Configuring the Analog Outputs....................................................................................... 156
Introduction ............................................................................................................. 156
To Configure an Analog Output........................................................................... 156
Configuring the Temperature Probes ............................................................................... 158
Introduction ............................................................................................................. 158
To Identify the Temperature Probe ...................................................................... 159
To Configure the Temperature Probe Parameters ............................................. 160
Virtual Protocol and Proxy Devices .................................................................................. 161
Introduction ............................................................................................................. 161
Device Type Categories ......................................................................................... 161
Configuration .......................................................................................................... 161
Chapter 5 Configuring the Apollo Functionality 167

Introduction .......................................................................................................................... 168
General ..................................................................................................................... 168
Assigning the COM Port to the Apollo Functionality ....................................... 168
Enabling or Disabling Apollo Communication Ports ........................................ 169
Installing the Apollo Drivers into ROSA NMS................................................... 170
Setting Up Remote Sites ...................................................................................................... 172
Adding a Site ........................................................................................................... 172
To Remove a Site ..................................................................................................... 173
To Change Site Properties...................................................................................... 173
To Check Non-Responding Sites .......................................................................... 174
Message Configuration ....................................................................................................... 176
ROSA Element Manager Messages ...................................................................... 176
To Change the Message Settings .......................................................................... 176
Configuring an Apollo Site ................................................................................................. 178
General Information on Site Configuration ........................................................ 178
Setting Scan Ranges ................................................................................................ 179
Mapping New Devices ........................................................................................... 181
Viewing All Site Devices........................................................................................ 186
Additional Settings ................................................................................................. 186
Chapter 6 Integration of ROSA EM 189

Integration of ROSA EM into ROSA NMS ....................................................................... 190
General ..................................................................................................................... 190
Installing ROSA Element Manager Drivers ........................................................ 192
Mapping the ROSA Element Manager Agent .................................................... 194
Using ROSA Element Manager Graphical User Interface ................................ 198
Configuring the Synchronization Action ............................................................ 202
Integration of ROSA EM into TNCS ................................................................................. 207
Prerequisites ............................................................................................................ 207
Integration of ROSA EM into a 3rd Party SNMP Management .................................... 209
SNMP Protocol and Community Strings ............................................................ 209
4005743 Rev N xi
Contents
Getting MIB Information ....................................................................................... 210
Chapter 7 Maintenance 215

Licensing ............................................................................................................................... 216
Introduction ............................................................................................................. 216
Viewing the License Parameters ........................................................................... 216
Obtaining a New License File ............................................................................... 217
Upgrading the License ........................................................................................... 217
Software Upgrading ............................................................................................................ 218
ROSA Element Manager Software ....................................................................... 218
Upgrading the ROSA Element Manager Device Software ............................... 218
Checking the Software Version............................................................................. 220
ROSA EM Applet Message .................................................................................... 220
Working with Device Configuration Files ....................................................................... 222
Introduction ............................................................................................................. 222
Creating a Backup ................................................................................................... 222
Performing a Restore .............................................................................................. 225
Cloning ROSA EM Device Settings ...................................................................... 225
ROSA EM Parameters ......................................................................................................... 227
Persistence................................................................................................................ 227
Downloading and Deleting a Coredump File ................................................................. 229
Downloading a Coredump File ............................................................................ 229
Deleting a Coredump File...................................................................................... 229
Chapter 8 Creating Graphics in ROSA EM 231

Overview of Graphics ......................................................................................................... 232
Introduction ............................................................................................................. 232
Individual Devices .................................................................................................. 233
Group Devices ......................................................................................................... 234
Standard View ......................................................................................................... 234
Directed Views ........................................................................................................ 235
Custom Views ......................................................................................................... 239
Configuring ROSA EM Graphics ...................................................................................... 242
Introduction ............................................................................................................. 242
Configuring ROSA EM to View Headend Graphics ......................................... 242
Configuring ROSA EM to View Group Graphics .............................................. 243
Configuring ROSA EM to View Rack Positions ................................................. 245
Configuring ROSA EM to View Custom Graphics ............................................ 248
Device Graphics Examples ................................................................................................. 250
Introduction ............................................................................................................. 250
Headend and Hubs................................................................................................. 250
Headend Racks........................................................................................................ 251
Hub and Nodes ....................................................................................................... 251
Nodes and Amps .................................................................................................... 253
xii 4005743 Rev N

Contents
Using Graphics in ROSA EM ............................................................................................. 255

Default Behavior ..................................................................................................... 255
Detachment Feature................................................................................................ 255
Chapter 9 Diverse Notification 257

Introduction .......................................................................................................................... 258
Concept..................................................................................................................... 258
Configuring Diverse Notification ...................................................................................... 259
Introduction ............................................................................................................. 259
Step 1 - Insure Option Selected ............................................................................. 259
Step 2 - Configure Email, Paging and SMS ......................................................... 261
Step 3 - Create Member Accounts ........................................................................ 266
Step 4 - Assign Members to Notification Groups............................................... 272
Step 5 - Configure System Wide Notification Rules .......................................... 274
Step 6 - Assign Notify Sets to Devices and Parameters ..................................... 275
Example ................................................................................................................................. 279
Chapter 10 Scripting in ROSA EM 281

Introduction .......................................................................................................................... 282
Installation of Scripts ........................................................................................................... 283
Custom Scripts ..................................................................................................................... 285
Chapter 11 Backup Operation 287

Introducing the Backup Functionality .............................................................................. 288
General ..................................................................................................................... 288
Regular Versus Floating Backup Applications ................................................... 288
Backup Trigger ........................................................................................................ 288
About Scripts ........................................................................................................... 289
Backup Devices ....................................................................................................... 289
Linked Devices ........................................................................................................ 290
Keeping the Device Chain ..................................................................................... 290
Licensing .................................................................................................................. 291
Backup Indication ................................................................................................... 292
Configuring the Backup Parameters ................................................................................. 294
Introduction ............................................................................................................. 294
Configuring the Backup Parameters for Regular Backup Applications ......... 294
Configuring the Backup Parameters for Floating Backup Applications......... 301
Configuring the Input and Output Router Backup Parameters ...................... 306
Determining the Backup Trigger .......................................................................... 307
Testing the Backup Configuration........................................................................ 308
Executing a Backup/Restore Transition Manually ............................................ 310
Checking the Backup/Restore Information ........................................................ 311
4005743 Rev N xiii

Contents
Appendix A Customer Information 315

Product Support ................................................................................................................... 316
Obtaining Support .................................................................................................. 316
Support Telephone Numbers ................................................................................ 316
Appendix B General Information 319

TCP/UDP Port Overview ................................................................................................... 320
TCP/UDP Ports Used by ROSA EM ................................................................................. 321
Backup Scripts ...................................................................................................................... 322
Appendix C Quick Installation Reference 325

Installation Steps .................................................................................................................. 326
More Information.................................................................................................... 326
Scenario 1 ................................................................................................................. 326
Scenario 2 ................................................................................................................. 327
Appendix D Email Function with Plain Authentication 329

Monitoring Information ...................................................................................................... 330
Requirements........................................................................................................... 330
Determine if Email Authentication is Required ................................................. 330
Example 1: Log of a Successful Email Message .................................................. 331
Example 2: Log of an Unsuccessful Email Message .......................................... 331
Example 3: Log of a Successful Email Message using Plain
Authentication...................................................................................................... 333
Appendix E Additional Configuration 335

Internet Protocol Security ................................................................................................... 336
Introduction ............................................................................................................. 336
To Configure IPsec on a Computer Running Windows XP or
Windows 2000 Server .......................................................................................... 336
To Configure IPsec on a Computer Running Windows Vista.......................... 353
Glossary 367
Index 377
xiv 4005743 Rev N

Safety Precautions
Safety Precautions
The software described in this manual 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.
4005743 Rev N xv
Preface
Preface
About This Guide
This guide provides information to configure and operate a ROSA Element
Manager (EM) device. It also shows the purpose of the integrated software and how
to use it in combination with the ROSA Network Management System (NMS).
Audience
This guide is intended for users (operators) and service personnel who are
responsible for the configuration, operation, and service of the ROSA EM.
Required Knowledge
To use this guide, you should be familiar with ROSA software.
Related Publications
The technical publications listed below provide extra system support. Refer to these
publications as you read this guide.
ROSA Network Management System User's Guide, part number 4014778
Copernicus server and software are further described in the User's Guide of your
Copernicus server.
- 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
ROSA Server MKVI - Network Management System User's Guide, part number
4038595
ROSA Element Manager Installation and Operation Guide, part number 4006813
TNCS Administrator Release - Software User's Guide, part number 730201
Digital Content Manager (DCM) Configuration Guide, part number 4011746
4005743 Rev N xvii

1 Chapter 1
Introduction
Introduction
This chapter is an introduction to the ROSA Element Manager (EM)
and shows its features and benefits. It also gives an overview of the
required installation and configuration steps before you can use the
device and guides you through the rest of the chapters.
In This Chapter
About the ROSA Element Manager ..................................................... 2
Steps to Take ............................................................................................ 7
LED Indicators......................................................................................... 9
Product Information ............................................................................. 11
4005743 Rev N 1
Chapter 1 Introduction
About the ROSA Element Manager

Introduction
The ROSA EM system is specifically designed to cost effectively monitor and control
the transmission network in headends, hub sites and HFC outside plants, and
transmitter sites. The device manages the equipment that is co-located on the site
where the ROSA EM device resides, whether this equipment has an SNMP, serial
(RS-232/422/485), or contact closure interface.
The main functions of the ROSA EM system are to:
Monitor the health of the transmission network
Act as an SNMP proxy
Send alarm notifications when a problem occurs
Automatically backup failed devices
Perform local automation tasks
The following illustration depicts a ROSA EM device.
The ROSA EM system supports several hundred Cisco and third-party devices.
Support for new devices is continuously being added to the ROSA EM system,
which can be exported to existing installations with a simple software upgrade.
The ROSA EM system actively polls all of the devices that it manages looking for
problems and in the event a problem is detected, ROSA EM system will send alarm
notifications to the appropriate personnel via SNMP trap, Email, Pager, or SMS.
ROSA EM communicates with the managed devices via their proprietary protocols
or contact closures then translates this information to SNMP, which can be passed to
2 4005743 Rev N
a higher level network management system. When the ROSA EM system is

configured to perform backup protection it will automatically initiate pre-defined
backup schemes that reroutes signals, activates and configures standby devices all
within seconds of a device failure.
The ROSA EM device is a 2 RU high, 19-inch rack-mount embedded platform that
operates without a monitor or keyboard. The operator interfaces with the ROSA EM
device via a simple easy-to-use web browser client. Communication to the ROSA
EM device can be established over any LAN/WAN network that supports Ethernet.
In addition, dial-in and dial-out (for instance ISDN) is supported for cases where
only a switched connection is available.
Operation
The ROSA EM system supports open standards interfaces, which enable cost-
effective integration of equipment into the ROSA EM system, as well as cost-
effective integration of the ROSA EM system into upper-level network managers.
The northbound management interfaces are composed of:
Web browser client interface on the ROSA EM system that allows management
of network devices as well as viewing real-time status and alarms.
The SNMP agent in the ROSA EM system provides a northbound SNMP
interface to higher level network management systems (supports Traps, Gets,
and Sets).
Utilizes FTP to remotely upgrade ROSA EM software as well as the backup and
restoration of ROSA EM configuration data.
4005743 Rev N 3
The southbound management interfaces are designed to communicate with the

managed devices and consist of:
Multiple serial ports (RS-232, RS-485, RS-422)
Digital and analog I/O contact closures interface
Ethernet interfaces (SNMP Manager )
Temperature probes
Network interface card
Client Options
There are four fundamental client options available for the ROSA EM system; a
simple Web browser, TNCS client, ROSA NMS system, and third party network
management systems each designed to meet specific needs of the user. The ROSA
EM system can be configured to do as much or as little as required to meet the needs
of the technicians and engineers charged with managing the broadband network.
Simple web browser: The user will open a web browser window for each ROSA
EM site. This is an ideal application for small systems that have only one or two
sites with ROSA EM installed.
TNCS client: The TNCS client will aggregate all of the ROSA EM sites to
produce a single network view that is easy to understand. In addition, TNCS will
aggregate the alarms, perform multi-site backup schemes, and retain historical
logs for alarms, system executables, and software status for all of the ROSA EM
sites.
4 4005743 Rev N
ROSA NMS: ROSA NMS provides all of the TNCS functionality as well as a
relational database that enables the operator to produce performance and
trending reports on the network, the managed devices, and overall system
performance. ROSA NMS also has several modular advanced tasks that provide
significant added value to system operators, engineers, and managers.
Third-party client: The ROSA EM system is ideally suited to integrate into an
overall third party network management system via SNMP. The northbound
SNMP interface in the ROSA EM system supports Traps, Gets, and Sets allowing
the overall network management system to have control of the managed devices.
Launching the web browser in the ROSA EM system allows the network
management system operator to easily view the details of any managed device
from the operations center.
Features and Benefits

The following list describes the features and benefits of the ROSA EM system.
Cost-effective solution for management of devices in all locations (large headend
to small hubs/OTN)
Manages Cisco and third-party equipment via proprietary protocol, SNMP, or
contact closures.
Translates proprietary protocols to SNMP and passes configuration/alarm
information to network managers.
Highly reliable (no fans, no hard drive) hardware and software solution
Alarm notification with Email, Pager, or SMS
Easy to use, intuitive web browser interface
Provides easy integration with multiple client options web browser, TNCS,
ROSA NMS, third Party network management system.
Open standards based interfaces (SNMP, HTTP, FTP, HMS, DateTime...)
Delivered with software already installed
Software can be upgraded remotely over LAN/WAN
Automatic remote backup and restore to save the entire configuration of the
ROSA EM system
Seamless integration into currently installed TNCS and ROSA NMS systems
Dual temperature probes available as option
2 RU, 19-inch rack-mount chassis
4005743 Rev N 5
Used Terminology
To identify the different hardware and software parts of the ROSA EM concept, you
may find an overview of the used terminology below:
ROSA Element Manager device: the ROSA EM hardware
ROSA Element Manager software: the software running on the ROSA EM
ROSA Element Manager driver: the software installed on the ROSA NMS to check
the state or change the settings of the device
6 4005743 Rev N
Steps to Take
Steps to Take
Introduction
Before you can use the functionality of the ROSA EM system you have to do some
steps, like installing the appropriate drivers, configuring the device... All the
necessary information is described in the following chapters.
Installation of the Device

First check how you want to use the different ports (serial communication ports,
analog input ports, relay ports...) and change the jumpers and/or switches if
necessary. Install the device in a rack and connect the cables to the ROSA EM device.
For more details about installing the ROSA EM device, please refer to the ROSA
Element Manager Installation and Operation Guide.
Setup of the Device

Before you have access to the device you have to setup the correct IP address via a
LAN connection or Craft interface. From now on the ROSA EM system is ready and
can be integrated in your headend configuration. For more details concerning the
setup of the ROSA EM device, please refer to chapter Setup on page 13.
Device Functionality
The ROSA EM system supports a wide range of functionality:
SNMP Proxy
Input/output (I/O) functionality
Apollo functionality
For more details concerning these items, please refer to chapter Configuring the ROSA
EM System on page 49, Configuring the Input/Output Functionality on page 139, and
Configuring the Apollo Functionality on page 167.
Integration of the Device

To manage the ROSA EM system, it can be integrated in ROSA NMS. For details,
please refer to topic Integration of ROSA EM into ROSA NMS on page 190. It can also
be integrated into a 3rd party SNMP management system, which is described in
topic Integration of ROSA EM into 3rd Party SNMP Management on page 209.
4005743 Rev N 7
The ROSA EM system can also be used in a stand-alone configuration. In this case
the management of the device is done with the built-in applet, which is accessible via
Internet Explorer. For more details concerning the applet of the ROSA EM device,
please refer to chapter Configuring the ROSA EM System on page 49.
Device Maintenance
Support for new devices will be added continuously and to keep your ROSA EM
system up to date, the maintenance functionality provides an easy way to upgrade
your software and license keys. It is also possible to backup, to restore or to clone the
ROSA EM device settings. For more details about the upgrade procedures, please
refer to chapter Maintenance on page 215.
Additional Functionality
To get a graphical representation of the monitored devices, please refer to chapter
Configure ROSA EM Graphics on page 242 for information on how to configure a
ROSA EM system.
The ROSA EM system can also notify operators, technicians... with email, paging
and/or SMS when a certain alarm condition occurs. The necessary configuration
steps are further explained in chapter Diverse Notification on page 257.
The ROSA EM system supports an own scripting language and the Python
programming language. More information about script types, syntax, scripting
commands and arguments can be found in chapter Scripting in ROSA EM on page
281.
Backup Operation
The ROSA EM system can be integrated into a backup/restore application. More
information concerning this integration can be found in chapter Backup Operation on
page 287.
Quick Installation Reference

When you are familiar with the hardware and software installation procedures
described in the chapters mentioned above, please refer to appendix Quick
Installation Reference on page 325.
8 4005743 Rev N
LED Indicators
LED Indicators
Introduction
The ROSA EM device is equipped with a number of LEDs indicating the status and
port configuration of the device. The following illustration reflects the LED
indicators on the front panel.
COM1 COM3 COM5 COM6 COM7 COM8 CRAFT

RS232 DTE RS232 DTE
TX TX RS232 DTE RS232 DTE RS232 DTE RS232 DTE TX
RS485 RS485 RS485 RS485
RX RX RX
RCDS RCDS RCDS RCDS
RUN RS485/RS422 RS485/RS422 RS485/RS422 RS485/RS422
POWER ALARM COM2 COM4
FAIL RS232 DTE RS232 DTE
TX TX TX TX TX TX
RX RX RX RX RX RX
LED Description
The following table describes the front panel LED indicators of the ROSA EM device.
LED Indicator Color Description

POWER Green Illuminates when the device is powered.
RUN Green Blinks when the processor runs.
ALARM Red Indicates a pending alarm detected by the ROSA EM device or by a
device connected to and supported by the ROSA EM device.
FAIL Red Indicates a critical error on the ROSA EM device.
COM 1 2 3 4
Green Blinks during TX communication on the port in question.
TX
Green Blinks during RX communication on the port in question.
RX
COM 5 6 7 - 8
Green Illuminates when the communication port in question is configured to
RS 232 DTE
RS232 DTE using jumpers (*).
RS485 RCDS
RS485 RCDS using jumpers (*).
RS485/RS422
RS485/RS422 using jumpers (*).
TX
RX
CRAFT
TX
RX
(*) More information about the jumper setting can be found in the ROSA Element
Manager Installation and Operation Guide.
4005743 Rev N 9
Note: During rebooting of the ROSA EM device, a running light sequence using the
front panel LEDs is started.
10 4005743 Rev N
Product Information
Product Information
Introduction
The ROSA EM can be identified by means of the ID Label that contains the following
information:
Company address
Model number
Serial number
Part number
Nominal supply voltage
Maximum current
The ID label contains information that you might need.
ID Label
The following illustration shows an example of the ROSA EM identification label :
Note: This identification label is an example and may differ from the information on
the label affixed to your unit.
4005743 Rev N 11
2 Chapter 2
Setup
Introduction
This chapter contains information about the setup of the ROSA
Element Manager (EM) system. It is recommended that the entire
setup procedure in this chapter is read before using the ROSA EM
system.
In This Chapter
Installing the ROSA EM Configuration Tools .................................. 14
Network Configuration ....................................................................... 25
Adding Devices and Groups ............................................................... 38
4005743 Rev N 13
Chapter 2 Setup
Installing the ROSA EM Configuration Tools

Introduction
Before the setup of the ROSA EM system can be started, the ROSA EM
Configuration Tools should be installed on each computer that will be used to
manage the ROSA EM system. The ROSA EM Configuration Tools provide the user
with some useful tools to install and maintain a ROSA EM system.
The ROSA EM Configuration Tools contain:
IP Configuration Tool
This tool can be used to configure IP settings of a ROSA EM with software
version older than V04.01.30.
ROSA EM Configuration Toolbox
This toolbox can be used to:
- Download and upload the device list configuration
- Download the device type list
- Download the MIB files
- Download and upload the options configuration
- Download and upload scripts
- Download logs from the device
- Upgrade the license file
- Upgrade the ROSA EM software
- Backup, restore, or copy ROSA EM system settings
- Set SNMP community strings
- Download and delete a coredump file
Support for Embedded GUI
The prerequisites to run the Embedded GUI (also called Java Applet) of the
ROSA EM system.
Notes:
- ROSA EM Configuration Tools are explained in the different chapters of this
guide.
- All ROSA EM Configuration Tools use FTP to transfer data from and to the
ROSA EM device. You need to set an FTP password and enable the FTP
server before you can use the ROSA EM Configuration Tools. Some backup
14 4005743 Rev N
related tools require that the SNMP agent has been enabled. For more
information, please refer to topic Managing Services on page 72.
System Requirements
Make sure that your computer meets the following requirements before installing
the ROSA EM Configuration Tools software on your computer.
Item Required
Processor Pentium II processor or higher
Memory Minimum 128 MB
Operating System Windows 98 or Me
Windows NT 4.0
Windows 2000 with Service Pack 3a (*)
Windows XP
Windows 2003
Windows Vista
Windows 7
Web browser Internet Explorer version 5 or later (*) (**)
Mouse Required
Monitor SVGA color monitor, 17 or larger is recommended
Graphics Adapter Minimum resolution of 800x600 in 16 colors, 1024x768 in 64K colors
or better is recommended
Ethernet Adapter Required
(*) The English version of Service Pack 3 for Windows 2000 and the English version
of Internet Explorer 5.5 SP2 can be installed from the ROSA EM Configuration Tools
CD-Rom. More information concerning the installation procedures for these
products can be found further in this topic.
(**) Internet Explorer 7 is only supported by ROSA EM V03.01.60 or higher.
Note: The ROSA EM Embedded GUI (also called Java Applet) is not restricted to the
Windows operating system with the Internet Explorer web browser. Other web
browsers that are able to run Java Applets can also be used to run the ROSA EM
embedded GUI.
Installing Windows 2000 Service Pack 3

Only if your computer is running Windows 2000 and no Service Pack is installed or
Service Pack 1 is installed, you have to install Service Pack 3. You do not have to
install this on computers running Windows 98, Me, NT4, XP, 2003, or if Service Pack
3 or higher is already installed.
4005743 Rev N 15
Chapter 2 Setup
Perform the following steps to install Windows 2000 Service Pack 3.

1 Insert the ROSA EM Configuration Tools CD-Rom.
Result: If the Autoplay function of your PC is enabled, the Readme.htm file
displays.
2 In the Readme.htm file of the ROSA EM Configuration Tools select the
Installation on Windows 2000 link.
3 Click on the Service Pack setup link.
Result: The Service Pack 3 setup is started.
4 Follow the instructions.
Note: The procedure above is applicable to the English version of Windows 2000. If
you are running another language version of Windows 2000, please have a look at
the Microsoft downloads. Here, you can either order a CD or download the Service
Pack for your language version of Windows 2000.
Installing Microsoft Internet Explorer

If the Microsoft Internet Explorer version installed on your computer is 4.0 or earlier,
you should install a more recent version of Microsoft Internet Explorer.
To Install the ROSA EM Configuration Tools

The installation procedure of the ROSA EM Configuration Tools depends on the
operation system installed on your PC. Perform the following steps to install the
ROSA EM Configuration Tools on a PC.
displays.
Installation On <OS> link, where <OS> corresponds with the operating system
installed on your computer.
3 Click on the Configuration Tools setup link and choose Open to start the
program.
Result: The InstallShield Wizard is started.
16 4005743 Rev N
4 Click on the Next > button.

Result: The Setup Type page of the InstallShield Wizard is displayed.
5 Select the setup type.

- Typical: recommended setup type
- Compact: installs only the minimum required components.
- Custom: allows you to choose the components you want to install.
Result:
- If you selected Typical or Compact setup, continue with step 8.
4005743 Rev N 17
Chapter 2 Setup
- If you selected Custom setup, the following dialog displays.

Note: By default, the ROSA EM Configuration Tools are installed in the .. \
Program Files \ Scientific-Atlanta \ ROSA EM Configuration Tools folder on your
system hard disk.
7 Click on the Browse button to choose another destination folder to install the
ROSA EM Configuration Tools and click on the Next > button when ready.
Result: The Select Components page of the InstallShield Wizard is displayed.
The following ROSA EM Configuration Tools components can be selected or

unselected:
- Program Files: this component includes the main ROSA EM Configuration
Tools application files.
18 4005743 Rev N
- Support for Embedded GUI: this component includes the Java Runtime
Environment (JRE) and Microsoft VM.
- Scientific-Atlanta DayTime Service: this service can be used for
synchronizing with other Cisco devices.
Note: The Support for Embedded GUI component must be installed if you want to
run the embedded GUI (also called applet) of the ROSA EM system.
Result: The Select Destination Folder step of the InstallShield Wizard dialog is
displayed.
A new program folder is proposed and the existing folders are listed. You can
change the name of the proposed new program folder or choose one of the
existing folders.
Note: The existing program folders can be displayed when you click on the
Windows Start button and then point to Programs.
Result: The Setup Status page with progress indicator is displayed.
4005743 Rev N 19
Chapter 2 Setup
10 The setup is now complete, press the Finish button to end the InstallShield
Wizard.
To Repair the ROSA EM Configuration Tools

The following explains how to repair the ROSA EM Configuration Tools installation.
displays.
20 4005743 Rev N

Installation on <OS> link, where <OS> corresponds with the operating system
program.
4 Select Repair and click on the Next > button.

Result: The Setup Status page with progress indicator of the InstallShield Wizard
is displayed.
Note: Click on the Cancel button if you want to interrupt the repair operation.
4005743 Rev N 21
Chapter 2 Setup
Result: When the repair operation is finished, the Maintenance Complete page
of the InstallShield Wizard is displayed.
5 Press the Finish button.
To Uninstall the ROSA EM Configuration Tools

Perform the following steps to uninstall the ROSA EM Configuration Tools.
displays.
Installation on <OS> link, where <OS> corresponds with the operating system
program.
22 4005743 Rev N
4 Select Remove and press the Next > button.

Result: A confirmation box is displayed.
5 Click on the OK button to remove the ROSA EM Configuration Tools or the

Cancel button to abort the operation.
Result: The Setup Status page of the InstallShield Wizard is displayed followed
by the Maintenance Complete page.
4005743 Rev N 23
Chapter 2 Setup
6 Press the Finish button.
Changing the FTP Mode

The ROSA EM Configuration Tools use Active FTP by default to transfer files from
and to the ROSA EM. When certain firewall functionality is present between the
ROSA EM and the client PC running these ROSA EM Configuration Tools, Passive
FTP is sometimes required. The following procedure explains how to switch from
Active FTP to Passive FTP or vice versa.
1 Open Windows Explorer and browse to the ROSA EM Configuration Tools folder
(the location is by default: C: \ Program Files \ Scientific-Atlanta \ ROSA EM
Configuration Tools)
2 Open the file rosaemtools.ini using a text editor (for instance Notepad).
3 Change the passive parameter to 1 for passive FTP or to 0 for active FTP.
4 Save and close this file.
24 4005743 Rev N
Network Configuration
Introduction
The ROSA EM device is equipped with two Network Interface Cards (NICs)
providing both a 10/100Base-T Ethernet port. The following illustration shows both
Ethernet ports at the rear panel of the ROSA EM.
TEMPERATURE
RF1
PROBE 1 PROBE 2 COM 1 ANALOG I/O PORT 1 DIGITAL INPUT PORT 1 DIGITAL INPUT PORT 5 DIGITAL INPUT PORT 9
RF2
VGA COM 2 GALV.ISOL. DI PORT 1 DIGITAL INPUT PORT 2 DIGITAL INPUT PORT 6 RELAYS PORT 1
ETHERNET 1
USB 1,2
KEYB.
COM 3 COM 5 COM 7
DIGITAL INPUT PORT 3 DIGITAL INPUT PORT 7 RELAYS PORT 2

COM 3 COM 5 COM 7
DIGITAL INPUT PORT 4 DIGITAL INPUT PORT 8 RELAYS PORT 3
ETHERNET 2
COM 8 DIGITAL INPUT 4
COM 6 COM 8 1 - 8 AN IN + G A LV .ISO L. D I DIGITAL I/O 1 15 14 RELAYS PORT 7 21 20

COM 4
14 - 21 AN IN - 16 COM 3 NC 2 NO 22 COM 9 NC 8 NO
COM 1-4 COM 5-8 ANALOG I/O 9,10, 22, 23 GND 1 - 12 D + 1 - 12 D + 4 18 17 10 24 23
MOUSE RS232 DTE RS232/422/485 11, 12, 24, 25 AN OUT 14 - 25 D - 14 - 25 GND 19 1-4 6 1-4 5 1-4 25 5-8 12 5-8 11 5-8
Ethernet Port 2
Ethernet Port 1
In order to establish Ethernet communication with the ROSA EM device, the IP

settings of Ethernet Port 1 must be configured. On a ROSA EM with software
version V04.01.30 or higher, you can configure the IP settings using the ROSA EM
GUI or the ROSA EM craft interface.
Note: On a ROSA EM with software version older than V04.1.30 you can use the IP
Configuration Tool or ROSA EM craft interface to configure the IP settings. You
cannot use the ROSA EM GUI to configure the IP settings with these older software
versions.
Configuring IP Settings using the ROSA EM GUI

If your ROSA EM has a software version V04.01.30 or higher and its IP address is
known, for example the default factory set IP address, you can modify the IP settings
of Ethernet Port 1 using the ROSA EM web browser user interface. Therefore, you
need to connect a PC or laptop to Ethernet Port 1 of the ROSA EM using a crossover
Ethernet cable and open the ROSA EM web browser user interface.
Notes:
If the known IP address is an unused IP address within the IP range defined for
your network, you may configure the IP settings directly via the network instead
of using a crossover Ethernet cable. In this case you can open the web browser
user interface from any PC connected to the same subnet as your ROSA EM.
To establish a connection with the ROSA EM, you must configure the IP settings
of the PC to ensure that both network devices are part of the same subnet. For
example, if the ROSA EM has the default factory IP settings (IP address
150.158.230.250 and subnet mask 255.255.254.0), you can set the computer's IP
address to 150.158.230.251 and subnet mask 255.255.254.0.
4005743 Rev N 25
Chapter 2 Setup
The following procedure describes how to configure the IP settings on a Windows

XP system.
1 Open the Control Panel and double-click on Network Connections.
2 Right-click on the Local Area Connection and select Properties.
Result: The LAN Properties dialog is displayed.
3 Select Internet Protocol (TCP/IP) and then click on Properties.
26 4005743 Rev N
Result: The Internet Protocol (TCP/IP) Properties dialog is displayed.
4 Select Use the following IP address and then enter the IP address and subnet
mask.
Note: Leave all other fields blank.
5 Click OK to confirm.
After configuring the computer's LAN settings, you can now access the ROSA EM's
web browser user interface with the known IP address and change the IP settings.
Note: This procedure only applies to a ROSA EM with known IP address. If the IP
address is unknown, use the craft interface to configure the IP settings instead of the
ROSA EM GUI.
The following procedure describes how to change the IP settings of a ROSA EM
using the GUI.
Important: You cannot use the GUI to configure the IP settings of Ethernet Port 1 if
the software version of your ROSA EM is older than V04.0.30.
1 Start a web browser session on the PC.
2 Enter the known IP address in the web browser's address box.
Result: The web browser user interface of the ROSA EM opens.
3 Login with the admin user name.
4 Click on the ROSA EM device (the top node of the device tree) and select the IP
Config tab.
Result: The IP Config tab page is displayed.
4005743 Rev N 27
Chapter 2 Setup
5 Click on the Value field of the IP Address parameter.

Result: The Change Parameter Dialog is displayed.
6 Enter the new IP address and click on the Execute button.
7 Click on the Value field of the Subnet Mask parameter.
8 Enter the new subnet mask and click on the Execute button.
9 Click on the Value field of the Gateway Address parameter.
10 Enter the new subnet mask and click on the Execute button.
11 Click on the Value field of the IPConfig Apply Changes parameter.
12 Click on the Execute button to apply the IP settings.
Configuring IP Settings using the Craft Interface

The Craft Interface on the front panel of the ROSA EM device can be used to
configure the IP settings. To access the craft interface menu, connect a VT100
terminal or computer running a terminal emulation program to the Craft Interface
port. The following illustration shows the physical location of the Craft Interface
port.
ROSA Element Manager
COM1 COM3 COM5 COM6 COM7 COM8 CRAFT
RS232 DTE RS232 DTE
TX TX RS232 DTE RS232 DTE RS232 DTE RS232 DTE TX
RX RX RS485 RCDS RS485 RCDS RS485 RCDS RS485 RCDS RX
RUN RS485/RS422 RS485/RS422 RS485/RS422 RS485/RS422
POWER ALARM COM2 COM4

FAIL
RS232 DTE RS232 DTE
TX TX TX TX TX TX
RX RX RX RX RX RX
Craft
Interface
The following procedure describes how to access the craft interface menu using
Windows Hyperterminal.
1 Connect a desktop PC or laptop to the RS-232 CRAFT connector on the front of
the ROSA EM device using a crossover serial cable (null modem cable).
28 4005743 Rev N
The table below shows how to wire a null modem cable.

Null Modem Cable PC Pin Pin ROSA Element Manager
Ground 5 5 Ground
RX 2 3 TX
TX 3 2 RX
Note: The COM port may not be in use by some other application.
2 On the PC or laptop, start Windows HyperTerminal.
Example: To start this program on a Windows XP system, click on the Windows
Start button, move to All Programs, Accessories, Communications, and finally
click on HyperTerminal.
Result: The Connection Description dialog is displayed.
3 In the Name box, type a name for the new connection and select an icon from the
Icon list. Click on the OK button.
Result: The Connect To dialog is displayed.
4005743 Rev N 29
Chapter 2 Setup
4 In the Connect using list, select the COM port that is connected with the ROSA
EM device and click on the OK button.
Result: The COM<x> Properties dialog is displayed where <x> stands for the
COM port number that you selected.
5 Enter the following port settings:

Bits per second: 38400
Data bits: 8
Parity: None
Stop bits: 1
Flow control: None
And click on the OK button.
Result: The following HyperTerminal window is displayed.
6 In the File menu, click on Properties.
30 4005743 Rev N
Result: The Properties dialog is displayed.
7 Click on the Settings tab.
8 In the Emulation drop down box select VT100 and click on the OK button.
9 Power up the ROSA EM device and on the PC keep the [Enter] key pressed until
the login prompt appears.
Note: It may take a few moments before the ROSA EM device starts.
10 Enter config after the login prompt and press [Enter].
4005743 Rev N 31
Chapter 2 Setup
11 Enter config after the password prompt and press [Enter].

Result: The available commands are displayed.
The following screenshot shows the craft interface menu for a ROSA EM with
software version V04.01.50 or higher.
The Craft Interface supports the following commands:

help: help command
get IP: displays the IP settings of the selected ROSA EM device.
set IP: for changing the IP settings of a ROSA EM device. The broadcast address
is optional.
activate ipsec bypass: to activate the IPSec bypass
deactivate ipsec bypass: to deactivate the IPSec bypass
factory reset: to reset all ROSA EM settings to factory defaults
clean state: reserved for production
exit or quit: to exit
The following keys can be used to enter commands:
Editing keys: cursor left, cursor right, backspace and [CTRL]+[D] (delete)
Start-end keys: [CTRL]+[A] to move to the start of a command and [CTRL]+[E]
to move to the end of a command.
32 4005743 Rev N
Scroll keys: cursor up and cursor down.

Move left/right keys: [ESC]+cursor left/right allows moving one word
left/right.
Delete keys:
[ESC]+[BACKSPACE]
Cursor on first letter: Delete previous word
Cursor in a word or on last letter: Deletes from start of current word to cursor
Cursor on space between words: Deletes previous word
[ESC]+[DELETE]
Cursor on first letter or space between words: Delete next word
Cursor in a word: Deletes from cursor to end of word
Cursor on last letter in a word: Delete from start of the word to the letter
before the cursor.
To change the IP address, subnet mask and gateway address, enter the following
instruction on the command prompt and press [Enter].
The craft interface menu for a ROSA EM with software version older than V04.01.30
is different as shown in the following example.
Scientific-Atlanta IP Configuration Tool.
Running on the device with MAC address 00-20-9d-03-19-47.
Available commands:
help -- show this text.
list -- shows a list of all running Scientific-Atlanta
devices on the local network
select <pattern> -- selects the Scientific-Atlanta device
with <pattern> in its identification text.
get ip -- show the IP settings for the currently selected
device.
set ip <address> <netmask> [ [<broadcast>] <gateway> ] --
change the IP settings for the currently selected device.
activate ipsec bypass -- activates the IPSec bypass.
deactivate ipsec bypass -- deactivates the IPSec bypass.
exit or quit -- leave this program.
Available servers:
00-50-4b-00-02-88: PEGASUS SN5789503 IP 10.11.33.154 nm
255.255.252.0 bc 0.0.0.0 gw 10.11.32.1
00-c0-3a-0c-05-1e: Prisma GbE SN05790374 IP 10.11.35.81 nm
255.255.252.0 bc 10.11.35.255 gw 10.11.32.1
255.255.252.0 bc 10.11.35.255 gw 10.11.32.1
255.255.252.0 bc 10.11.35.255 gw 10.11.32.1
* 00-20-9d-03-19-47: Rosa/EM (unknown) IP 10.11.34.77 nm
255.255.252.0 bc 10.11.35.255 gw 10.11.32.1
4005743 Rev N 33
Chapter 2 Setup
All IP devices running the IP Configuration Server and residing on the same subnet
are displayed. The ROSA EM device that is connected via the Craft interface is
selected and indicated by an *.
Next to the commands listed above, the craft interface supports two additional
commands:
list command: displays a list with all ROSA EM devices connected to the local
network. An asterisk (*) indicates the ROSA EM to which the COM connection is
made.
select command: For selection of a ROSA EM device by MAC address. The
MAC address may be abbreviated to a unique sub string.
Note: The factory reset command is not available
To change the IP address, netmask, broadcast and gateway, enter the following
instruction on the command prompt and press [Enter].
Note: Broadcast and gateway are optional. When only three strings are entered, the
third string represents the gateway address.
Configuring IP Settings With the Microsoft Windows Based IP Configuration Tool

ROSA EM with a software version older than V04.01.30 contains an IP Configuration
Server that automatically starts running after starting up the ROSA EM. The IP
Configuration Client must be installed on a remote PC residing on the same Ethernet
subnet. When the IP Configuration Client starts up, it establishes communication
with IP devices connected to the same Ethernet subnet and shows a list of the
available servers that support the IP Configuration Tool. You can select your ROSA
EM in the list and configure the IP settings of the device.
CAUTION:
Firewall settings may interact with the IP Configuration Tool. If you have
problems to configure your firewall with the correct settings, you may disable
your firewall temporarily while you are running the IP Configuration Tool.
The Microsoft Windows based IP Configuration Tool (IPConfigTool.exe) can be

found on the Configuration Tools CD-ROM (part number 4006138) shipped with the
ROSA EM device.
If one or more ROSA EM devices with known serial number are installed, then you
can follow the following procedure:
34 4005743 Rev N
1 Power on the ROSA EM device(s) and check if the Power LED is on. When the
processor of the ROSA EM device is completely booted, the IP Configuration
Server automatically starts running.
Note: Ensure that all ROSA EM devices are connected to the same Ethernet
subnet.
2 Connect a PC to the same Ethernet subnet.
3 Start the IP Configuration tool on your PC. If the tool was already running, just
press the Reload button.
Result: The tool returns a list of servers that support the protocol with the
following information:
Device type and serial number
MAC Address
IP Address and Subnet Mask
Broadcast Address
Gateway Address
4 Select the device that you want to configure and press the Configure button.
In case of multiple ROSA EM devices use the serial number for identification.
4005743 Rev N 35
Chapter 2 Setup
Result: The Configure dialog is displayed.
5 Enter the IP Address, the Subnet Mask, and the Gateway. Press the OK button
to confirm or the Cancel button to abort the operation.
6 Repeat steps 4 to 5 for each ROSA EM device.
7 Click on the Exit button to leave the IP Configuration Tool.
If multiple ROSA EM devices with unknown IP address are installed, then you can
follow the procedure below for each ROSA EM device that you want to configure.
1 If a network cable is already connected to the ROSA EM device, disconnect it
now.
2 Connect a PC with a crossover Ethernet cable to Ethernet Port 1 of this ROSA EM
device.
3 Start the IP Configuration tool on your PC.
Note: If the tool was already running, stop it and restart it.
Result: The tool now returns the device interface parameters of one ROSA EM
device.
4 Select the device and press the Configure button.
36 4005743 Rev N
Result: The Configure dialog is displayed.
5 Enter the IP Address, the Subnet Mask and the Gateway. Press the OK button
to confirm or the Cancel button to abort the operation.
6 Disconnect the crossover Ethernet cable and connect the ROSA EM device back
to the Ethernet network.
7 Repeat steps 1 to 6 for every ROSA EM device on this Ethernet network.
Configuration of Second Network Interface Connector

Once an IP address has been assigned to the ROSA EM device, you can assign an IP
address to the second NIC with help of the ROSA EM embedded GUI (applet) or
with a TNCS Classic Client. For more information, please refer to the topic
Configuring Second NIC and Routing on page 124.
4005743 Rev N 37
Chapter 2 Setup
Adding Devices and Groups

Introduction
Once the ROSA EM device network settings are configured, the next step is to define
the devices that need to be monitored and to specify the hierarchical structure that
represents your topology. There are two ways to do this:
Via a device list, commonly referred to as a devlist
Via the add/delete feature on the ROSA EM Device GUI
If you are an advanced user and want full control over the configuration, you can
create a device list as explained in the rest of this topic.
If you want a more convenient way to add/delete a few devices or groups, use the
add/delete feature as explained in the topic Adding devices and Groups on page 91.
Device List Concept

The device list provides the ROSA EM device with the device configuration that
represents the hierarchy of the devices, monitored using the ROSA EM system. The
following shows an example of a device list.
Each ROSA EM device contains its own device list, which:

Identifies each piece of equipment connected to the ROSA EM device.
Arranges the equipment in a hierarchy that directly corresponds to the structure
38 4005743 Rev N
of the application managed by the ROSA EM system.

Shows the parent/child relationships between the connected equipment, for
instance which devices are located in which chassis and/or in which equipment
rack.
Placing the devices in groups is the key to consolidating the devices into easy to
understand displays. A group is a logical device used to contain the status of
subordinate (child) devices and facilitate the hierarchical representation of the
network topology. This hierarchical structure, using groups and parent/child
relationships, provides a natural multi-layered representation of the network.
Subordinate devices can be individual equipment components or other groups. For
example, a headend group could contain multiple equipment rack groups that each
contains individual pieces of equipment. When a device is connected to or removed
from the ROSA EM system, the device list should be changed. This topic describes
the procedures to update a device list. The device list can be downloaded from the
ROSA EM device using the ROSA EM Tools Environment. More information
concerning downloading the device list can be found in the next subtopic.
Downloading the Device List

The device list file is stored on the ROSA EM device and can be downloaded to your
computer to make changes or to check the content. The following procedure
explains how to download the device list file to your computer using the ROSA EM
Tools Environment.
1 Click on the Windows Start button, move to Programs, ROSA EM
Configuration Tools, and select ROSA EM Tools Environment.
Result: The ROSA EM Tools Environment window is displayed.
2 Enter the following instructions on the command prompt:
getdevlist X.X.X.X Y
With:
X.X.X.X: the IP address of the ROSA EM device
Y: the target directory. When no directory is entered, you will be prompted to
provide one. Press [Enter] if you want to save the device list file in the
current directory (the directory of the ROSA EM Tools Environment).
3 Enter the FTP password on the command prompt.
Result: The device list file (devlist.txt) is stored and renamed to
X.X.X.X_devlist.txt with X.X.X.X the IP address of the ROSA EM Device.
4005743 Rev N 39
Chapter 2 Setup
Note: The FTP password prompt is only displayed if your ROSA EM has boot
software version V04.00.50 or higher. For more information, please refer to topic
Managing Services on page 72.
4 Type exit to close the ROSA EM Tools Environment window.
Editing the Device List File

Introduction
After downloading the device list file using the ROSA EM Tools Environment, the
device list file is renamed to X.X.X.X_devlist.txt with X.X.X.X the IP address of the
ROSA EM Device. This file can be opened using a text editor such as Notepad.
There are two types of device list entries:
Group device entries
Individual device entries
Group Device Entries

Individual devices are placed in groups. A group is a logical device used to contain
the status of subordinate (child) devices and facilitate the hierarchical representation
of the network topology.
The format for group device entries is:
Group group name Description=group description Graphic=graphic type
Racverpos=rack vertical position Address=xxxx
Following this format in our example, the entry for the Chassis 01 group device in
the R1 equipment rack is:
Group Chassis01 Description=Chassis 1 Graphic=chassis continuum RacVerPos=23
Address=1004
Field Description Value to Use

Group Name Short, unique name Anything you choose. The value
must not include blank spaces.
Group Description of the group name. The Anything that helps you to identify
Description value must be preceded by the group. The value must be
Description=. enclosed in quotes.
40 4005743 Rev N

Graphic Type of graphic to display when the Use one of the following:
Type group is double-clicked in the device
Rack
tree. The value must be preceded by
Graphic=. Chassis type
Group vrack
Star
Cascade
The value must be enclosed in
quotes. If no value is entered,
ROSA EM will use the standard
view.
Rack Vertical For rack mounted devices only; Any number that represents the
Position identifies the position occupied by the chassis location in the rack. If no
chassis within a rack. value is entered, ROSA EM places
Specifically, refers to the number of the chassis in the first empty
rack units from the bottom of the rack location beginning at the bottom of
to the bottom of the chassis. the rack.
Used for graphic purposes so ROSA
EM knows where to display the
chassis within its rack. The value
must be preceded by Racverpos=.
Group Each group should have a unique Any numerical value that is unique
Address address. The value must be preceded to all addresses of the groups on
by Address =. this ROSA EM device. Valid range
is 0 to 65,535.
Individual Device Entries

A device is the actual piece of equipment connected to the ROSA EM Device.
Examples include controllers, modulators, and upconverters. In the device list,
devices are combined into groups to represent the topology of your network. The
format for individual device entries is:
devicetype devicename Port=device communication port Address=physical device address
Sernam=service name
Following this format in our example, the entries for the Chassis01 group device (in
the R1 equipment rack) and the first two pieces of equipment located within it are:
Group Chassis01 Description=Chassis 1 Graphic=chassis continuum RacVerPos=23
Address=1004
9810 Ctr1 Port=Com2 Address=10
9820 Ch2mod Port=Com2 Address=11 SerNam=Channel 2
4005743 Rev N 41
Chapter 2 Setup

Device Type The name of the devtype file the The name of the devices devtype
ROSA EM system should use file. More information about the
when polling this device. devtype file can be found in sub
topic Device Types further in this
topic.
Device Name Descriptive name of the device Anything that helps you identify
device.
Important: This name must be
unique, no longer than 20
characters, and contain no blank
spaces.
Device The port the ROSA EM device uses The port number on the ROSA EM
Communication to communicate with the device. device that the device is attached to.
Port The value must be preceded by For instance COM1
Port=.
Physical Device The devices address. The value The address you assigned to the
Address must be preceded by Address=. device. We distinguish three types
of device addresses:
RCDS comport address (*)
IP Address
SMC address
Service Name The service provided by the Anything that helps you to identify
device. The value must be the function of the device. The
preceded by Sernam=. value must be enclosed between
brackets.
(*) The RCDS comport address entered in the device is represented in hexadecimal.
Since the ROSA EM device only accepts decimal addresses, you have to convert this
hexadecimal address to a decimal value (for instance C3 hex = 195)
Rules for Editing a Device List

Follow these rules when editing a device list.
Use indentation levels for each line in the file in such a way that the parent/child
relationships reflect the actual relationships between your physical devices. This
helps ensure that the correct relationships are also represented in the device tree.
Indent a line by only one space when representing a child device.
Indent no more than 20 levels deep. The ROSA EM system prohibits you from
going beyond 20 levels because hierarchical device names are used in ROSA EM
system logs to identify devices. The more groups a device belongs to (and thus,
the more indentation levels), the longer the hierarchical device name. When
viewing a log, device names over twenty levels deep in the device list will cause
42 4005743 Rev N
log messages to scroll off the screen horizontally.

Identify devices with unique names that are a maximum of 20 characters long
and meaningful to you.
Certain characters should not be used in device names because the ROSA EM
system interprets the meaning of these characters differently.
Do not use any of the following characters: , . = ( ) $ ; / \ * :
Helpful Hints to Update a Device List

Keep the following in mind while editing a device list.
Including the device communication port and device address is required.
Including the following items in the device list is not required, but doing so
makes ROSA EM device startup more efficient:
- Group description
- Group graphic to display
- Rack vertical position of a chassis
- Device service name
- Device address
Device descriptions are optional and can be included in the device list.
Use quotation marks around values that follow an equal sign.
Use terminators such as spaces, commas, and equal signs to promote readability
of the file.
Add blank lines or descriptive comments to help you better understand the file.
Place a semicolon at the beginning of these types of lines so that the ROSA EM
system will not try to interpret them. In our example, we used blank lines to
separate groups for better readability.
Device Types
In the device list file, each individual device is identified by its type, which is
generally the model number or model name of the product. The ROSA EM device
contains several files, one for each device the ROSA EM system supports.
The format of the filenames is device type.txt.
Example: The file 9810.txt is used for the Continuum 9810 Controller.
Each file contains specific programming code that the ROSA EM system uses to
interpret data received from that particular device during polling. It is possible to
create a device type list from the device type.txt files present on the ROSA EM
device using ROSA EM Configuration Tools.
4005743 Rev N 43
Chapter 2 Setup
The following procedure explains how to create a list of device type files using
ROSA EM Configuration Tools and how to store this list on your computer.
getdevtypelist X.X.X.X Y
With:
Y: the target directory. When no directory is entered, you will be prompted
to provide one. Press [Enter] if you want to save the device type list file in
the current directory (the directory of the ROSA EM Tools Environment).
Result: The device type list file is created, saved and named X.X.X.X_devtypes.txt
with X.X.X.X the IP address of the ROSA EM Device.
Notes:
The FTP password prompt is only displayed if your ROSA EM has boot
software version V04.00.50 or higher. For more information, please refer to
topic Managing Services on page 72.
The device type list file can be opened using a text editor such as Notepad.
44 4005743 Rev N
The following illustration shows a device type list file opened by Notepad.
Example
In our device list example earlier in this topic, rack 1 has to be expanded with a
Galaxy Chassis filled up with 3 Redus MKII Source Selector devices and 3 Titan
MKII Satellite Receiver devices. The Redus MKII devices should be identified with
Redus1, Redus2, Redus3, and the Titan MKII devices with Titan1, Titan2, and Titan3.
The Galaxy Chassis should be named GalaxyChassisA. The ROSA EM device use
port COM 6 to manage these devices. The following table represents the RCDS
comport addresses of the devices.
Device Address (hex) Address (Decimal)

Redus1 A1 161
Redus2 A2 162
Redus3 A3 163
Titan1 A4 164
Titan2 A5 165
Titan3 A6 166
Before editing the device list, you have to verify if devices in the device list and on
the same COM port already use the addresses of the Redus MKII and Titan MKII
devices. If not, you can add the entries of the new devices into the device list,
4005743 Rev N 45
Chapter 2 Setup
otherwise you have to change the comport addresses. Since the Galaxy Chassis is
not provided with a communication port, you must give the chassis a unique
address.
The following shows the device list part that should be entered in the device list.
Group GalaxyChassisA Address=2115 Port=None
redusmkii Redus1 address=161 port=com6
titanmkii Titan1 address=164 port=com6
To comply with the actual relationships between the physical devices into the device
list, three blanks have to precede the group device entry and four blanks the
individual device entries.
The following illustration represents the result.
46 4005743 Rev N
Uploading the Device List

After editing the device list, you can upload this file to the ROSA EM device. The
following procedure explains how to upload the device list to a ROSA EM device.
putdevlist X.X.X.X Y
With:
Y: directory and filename
Directory: directory where the device list file is located
Filename: the name of the device list file
Note: The Y parameter is optional. If it is not added to the putdevlist command,
the devlist in the current directory is automatically selected or you will be
prompted to provide one if there is no devlist in the current directory.
Result: The device list file is renamed to devlist.txt and uploaded to the ROSA
EM device.
4 The ROSA EM device is restarted and uses the newly uploaded device list.
Note: Restarting the device will take some time.
4005743 Rev N 47
3 Chapter 3
Configuring the ROSA EM
System
Introduction
This section describes how to configure the ROSA EM Device.
In This Chapter
Using the ROSA EM Device GUI ....................................................... 50
Working with ROSA EM Operator Accounts ................................... 55
Configuring Client Computer Connection Feature ......................... 59
Using Log Information ......................................................................... 61
Changing the Device Time .................................................................. 67
Managing Services ................................................................................ 72
Alarm Processing .................................................................................. 81
Working with Devices and Groups .................................................... 91
Configuring Device Polling ................................................................. 95
Working with Alarms .......................................................................... 99
Viewing the Hardware and Software Information ........................ 102
Checking the ROSA EM Device Temperature and Voltage
Levels .................................................................................................... 104
Sending Traps ...................................................................................... 106
Resetting the ROSA EM Device Parameters ................................... 114
Restarting the ROSA EM Device ...................................................... 116
Device Backup Operation .................................................................. 118
Configuring HFC-Plant-Monitoring ................................................ 119
Using Maintenance Mode .................................................................. 121
Using the Debug Mode ...................................................................... 123
Configuring Second NIC and Routing ............................................ 124
Configuring NIC Teaming for High Reliability ............................. 131
Configuring IPsec ............................................................................... 133
4005743 Rev N 49
Chapter 3 Configuring the ROSA EM System
Using the ROSA EM Device GUI

Introduction
After assigning an IP address and starting up the ROSA EM device, the embedded
GUI of the ROSA EM Device can be opened using a web browser.
WARNING:
The Java Runtime Environment is required to run the ROSA EM Embedded GUI.
For more information, refer to the topic Installing the ROSA EM Configuration Tools
on page 14.
Note: The connection between the ROSA EM device and the computer running the
embedded GUI should be at least 64 Kbps (8 Kbyte/s). When the embedded GUI is
initially launched, the Embedded GUI will load some data from the ROSA EM
device before becoming responding and fully functional. This action can take some
time depending on the available bandwidth.
Opening the ROSA EM Configuration GUI

Perform the following steps to open the ROSA EM Configuration GUI of a device
without set admin password, such as a brand new ROSA EM or a ROSA EM that has
been reset to factory settings.
1 Start your internet browser.
2 Enter the IP address of the ROSA EM device in the address line followed by a
slash (for instance http://10.11.34.77/).
Result: The Set Operator Password dialog for the admin account is displayed.
Note: Each ROSA EM device leaving our assembly line is configured with a
default ROSA EM operator account with a default user name and a blank
password:
User Name: admin
Password:
Note: It is recommended to add one or more new ROSA EM operator accounts
with different privilege level to the system. For more information about adding
50 4005743 Rev N
or deleting ROSA EM Operator Accounts, please refer to topic Working with

ROSA EM Operator Accounts on page 55.
3 Enter a password in the Password box.
For security reasons, the Regular complex password check box is selected by
default. This means that you must choose a complex password that meets the
following requirements:
At least 4 characters long
Characters must be chosen from at least three of the following groups:
Lower case characters
Upper case characters
Numbers and special characters
Password cannot have characters repeated more than three times
consecutively
Password cannot be identical to the operator ID, the reverse operator ID or
easy passwords such as cisco, ocsic or any variant
Notes:
You may unselect the Require complex password check box to choose an
easy password, but keep in mind that this may compromise security.
If you unselect the Require complex password check box and leave the
password blank, you will be prompted to set the password again the next
time you login.
If you unselect the Require complex password check box and click Cancel
on the Set Operator Password dialog, you will be prompted to set the
password again the next time you login.
4 Repeat the password in the Password Repeat box.
5 Click Set Password to confirm the password or Cancel to abort.
Result: The ROSA EM GUI is opened and the ROSA EM device appears as the
top node of the device tree in the browser frame.
Perform the following steps to open the ROSA EM Configuration GUI of a device
with the admin password already set.
1 Start your Internet browser.
4005743 Rev N 51
2 Enter the IP address of the ROSA EM device in the address line followed by a
slash (for instance http://10.11.34.77/)
Result: The Login dialog for the admin account is displayed.
3 In the User Name box, type the name of your ROSA EM account.
4 In the Password box, type the password.
5 Click Login to confirm or Cancel to abort.
Result: The ROSA EM GUI is opened after correct login.
If the user name and /or password entered in the Login dialog is not correct, a login
failure popup window will appear notifying you that the password is incorrect.
Perform the following steps to re-enter the user name and password.
1 After entering an incorrect user name and/or password, the following login
failure popup is displayed:
2 Press the OK button.

Result: The web browser is opened with a blank ROSA EM GUI (no device
appears in the browser frame) and the Login dialog appears again.
Note: If you click on the Cancel button, you can always recall the Login dialog
via the option Login of the Operator menu.
3 Enter the correct user name in the User Name box and the correct password in
the Password box.
Result: The ROSA EM GUI is opened.
52 4005743 Rev N
Changing the View Mode

Introduction
The menu item View Mode can be found on the ROSA EM GUI menu bar and
contains two items, which can be enabled/disabled.
Tabbed Panes
When enabling the Tabbed Panes option, panes will be shown when selecting a device
(single left-click with the mouse or when using arrow keys on the keyboard) from
the browser frame on the left side of the ROSA EM applet.
Note: When Tabbed Panes is disabled, tabbed panes will never be shown.
4005743 Rev N 53
Graphic Displays
When enabling the Graphic Displays option, a graphic display is generated and
shown when selecting a device (single left-click with the mouse or when using arrow
keys on the keyboard) from the browser frame.
Notes:
When Graphic Displays is disabled, a graphic display can still be opened with a
right-click on the device in the browser frame and selecting Graphic Open.
For detailed information on how to configure and use ROSA EM graphics, please
refer to chapter Creating Graphics in ROSA EM on page 231.
Tool Tips
The Device tree of the ROSA EM system GUI is provided with tool tips giving
additional information of the device in the tree. Tool tips are displayed by hovering
your mouse pointer on the branch.
54 4005743 Rev N
Working with ROSA EM Operator Accounts

Adding ROSA EM Operator Accounts
The following steps explain how to add a new ROSA EM operator account.
1 In the menu bar of the GUI, click on the Operator menu and select Add.
Result: The Add Operator dialog is displayed.
2 Enter the user name of the operator in the Operator ID box.

Note: The Operator ID is limited to maximum 12 characters.
3 In the Privilege Level drop down box, select one of the following levels:
Monitor: the operator can view all ROSA EM GUIs but cannot make any
changes.
Change: the operator can make changes to most of the parameters. Adding
or deleting operator accounts and configuring alarms is not allowed.
Configure: the operator can perform all functions within the ROSA EM
system.
4 Enter a complex password in the Password box.
A complex password must fulfill the following requirements:
consecutively
Note: You may unselect the Require complex password check box to choose an
4005743 Rev N 55
5 Enter a password in the Password box; a case sensitive password of maximum

12 characters can be used.
7 Press the Add button to confirm or the Cancel button to abort the operation.
Notes:
A password is mandatory.
When the repeated password doesnt match the first entered password, an error
message is displayed.
When the repeated password matches the first entered password, a confirmation
box is displayed.
Press the OK button to close the confirmation box.
Viewing the ROSA EM Operator Account List

Perform the following steps to view the ROSA EM operator account list.
1 In the browser frame of the GUI, click on the top node of the device tree.
Result: The ROSA EM System GUI is displayed.
2 Click on the Operator tab.
Result: The ROSA EM operator account list is displayed.
56 4005743 Rev N
Deleting a ROSA EM Operator Account

The following steps explain how to delete a ROSA EM operator account.
1 In the menu bar of the ROSA EM GUI, click on the Operator menu and select
Delete.
Result: The Delete Operator dialog is displayed.
2 In the Operator drop down box, select the ROSA EM operator account that
should be deleted.
3 Press the Delete button to confirm or the Cancel button to abort the operation.
Result: After pressing the Delete button, the following message box is displayed.
Press the OK button to close the message box.
Changing a ROSA EM Operator Password

The following steps explain how to change a ROSA EM operator password for an
operator with Configure privileges.
Note: Operators with other privileges must be first deleted and added again to
change the password.
1 In the menu bar of the ROSA EM GUI, click on the Operator and select Change
Password.
Result: The Set Operator Password dialog is displayed.
2 Enter a password in the Password box.
For security reasons, the Require complex password check box is selected by
default. This means that you must choose a complex password that fulfils the
4005743 Rev N 57

consecutively
Notes:
You may unselect the Require complex password check box to choose an
If you unselect the Require complex password check box and leave the
password blank, you will be prompted to set the password again the next
time you login.
4 Click Set Password to confirm the password or Cancel to abort.
58 4005743 Rev N
Configuring Client Computer Connection Feature
Configuring Client Computer Connection Feature

Introduction
Operators can make connections to the ROSA EM system via different client
computers. An operator can configure the ROSA EM Client-Connection feature in
such a way that the ROSA EM system accepts all connections from any client
computer or that the system only accepts connections from those client computers
whose addresses are defined. A maximum of 16 client computer IP addresses can be
defined.
Note: A maximum of twelve applets and eight TNCS client computers can be
connected to a ROSA EM device at the same time.
Defining an IP Address
The following steps explain how to define an IP address.
1 Open the ROSA EM GUI; in the browser frame click on the ROSA EM device (the
top node of the device tree) and select the Client-Connections tab.
Result: The Client-Connections tab page is displayed.
Notes:
User-configurable fields display in bold text.
Read-only fields display in non-bold text.
2 Click on the Value field of a Valid Client IP-Address parameter.
4005743 Rev N 59
Result: The Change Parameter Dialog of the Valid Client IP-Address parameter
in question is displayed.
3 Enter the IP address and press the Execute button to confirm or the Cancel
button to abort the operation.
To Set the Accept Any Client Option

The following explains how to set the Accept Any Client parameter.
Note: This parameter has no influence on the client computer connection feature
when no IP address is defined.
Result: The Client-Connections tab is displayed.
2 Click on the Value field of the Accept Any Client parameter.
Result: The Change Parameter Dialog of the Accept Any Client parameter is
displayed.
3 Select Yes or No and press the Execute button to confirm or the Cancel button to
abort the operation.
Yes: the system accepts all connections from any client computer.
No: the system only accepts connections from the client computers whose IP
address is defined as a valid client IP address.
Viewing the IP Addresses of the Connected Client Computers

The following explains how to check the IP addresses of the connected client
computers.
Result: The Client-Connections tab is displayed with the IP addresses of the
connected client computers at the bottom of the tab.
60 4005743 Rev N
Using Log Information

Viewing the ROSA EM Device Log Pages
The events logged by the ROSA EM device are divided in three categories: the alarm
logs, the system logs, and the software logs. The alarm logs contain the following
information about an alarm status change:
Date and time
Alarm state
Device hierarchical name
Alarm description
Device status.
The system logs contain the following information concerning a ROSA EM
configuration change:
Date and time the command was issued
Type of configuration change
Device location
Command issued
Operator who made the change
System from which the change was made.
The software logs contain the date, time, and activity of a software activity.
Perform the following steps to check a log page.
1 In the menu bar of the ROSA EM GUI, click on the Logs menu and select Alarm
Log, System Log, or Software Log.
Result: The chosen log page is displayed (for instance Alarm Log page).
4005743 Rev N 61
2 To decrease or increase the font size, right-click on the log page and select
Decrease Font Size or Increase Font Size in the short-cut menu.
3 To define the maximum number of log lines that appear on the log page, right-
click on the log page and select Set Maximum Log Lines in the short-cut menu.
Result: The Maximum Log Lines dialog appears.
4 Enter the number of log lines and click on the OK button to confirm or the
Notes:
The log pages only show events that occurred after opening the ROSA EM GUI.
The newly specified maximum number of log lines will be used on the log page
from the moment when a new log occurs.
The specified maximum number of log lines has only effect on the log page
where applied. For each type of log page (Alarm Log, System Log, and
Software Log) a different maximum number of log lines can be set.
The maximum number of log lines has only effect on the log pages, not on the
number of log lines recorded in the ROSA EM log file.
Logs are saved up to 4 x 10 Mb and then shifted through.
Log files are saved to flash automatically every 24 hours.
Creating and Viewing a Log File

All events that occurred since power up can be dumped into a log file. The
following procedure explains how to create a log file.
2 Select the Persistence tab.
62 4005743 Rev N
3 Click on the Value field of the Dump Log Data to File parameter.
4 Select DumpNow and press the Execute button to confirm or the Cancel button to
The log file is saved on the ROSA EM device. There are two ways to download the
log file:
Via FTP
Via ROSA EM Configuration Tools
Important: The FTP server on a ROSA EM with software version V04.01.30 or higher
is default disabled. Set the FTP password and enable the FTP server to download log
files. For more information, please refer to topic Managing Services on page 72.
Via FTP
Follow the next procedure to obtain the log file via FTP.
1 In the menu bar of the ROSA EM GUI, click on the Logs menu and select Alarm
Log, System Log, or Software Log.
Result: The chosen log page is displayed.
2 Right-click on the log page and select Get Log File (via FTP).
Result: A login dialog displays if your ROSA EM has boot software version
V04.00.50 or higher. Older versions do not require a FTP login.
4005743 Rev N 63
3 In the User Name box, type logs.

4 In the Password box, type the FTP password.
5 Click Log On to confirm or Cancel to abort.
Result: An Explorer Window showing the log file is opened after confirmation.
6 Click on the Refresh icon or press function key [F5] to see the latest logs.
Follow the next procedure to obtain the log file via ROSA EM Configuration Tools.
getlogs X.X.X.X Y
With:
Y: the target directory. When no directory is entered, you will be prompted
to provide one. Press [Enter] if you want to save the log files in the current
directory (directory of the ROSA EM Configuration Tools).
Result: The log files are saved to your computer and named X.X.X.X_logN.txt
with X.X.X.X the IP address of the ROSA EM Device and N=1,2,3,4.
64 4005743 Rev N
Notes:
The log file can be opened using a text editor such as NotePad.
Deleting Log Files

The following procedure describes how to delete all log files.
2 Select the Persistence tab.
4005743 Rev N 65
3 Click on the Value field of the Clear All Log Files parameter.
4 Select ClearNow and click the Execute button to confirm or the Cancel button to
Log Date and Time

WARNING:
For the same messages there can be a date and/or time difference between the
logged information on the ROSA EM GUI and the downloaded log file content.
The date and time information is added as follows:

The messages in the alarm logs, system logs and software logs on the ROSA EM
GUI get the date and time of the PC where the ROSA EM GUI applet is running.
The messages in the log files get the date and time of the ROSA EM device itself.
When the PC (running the applet) and the ROSA EM device are not synchronized
there will be a date and/or time difference when messages are logged. For more
information on how to adjust date and time or on how to synchronize the ROSA EM
device with an external device, please read Changing the Device Time on page 67.
66 4005743 Rev N
Changing the Device Time

Introduction
The internal clock of the ROSA EM device can be set manually or can be
synchronized with an external device such as a time server.
Changing the Local Time

The following procedure explains how to change the internal clock of the ROSA EM
device.
2 Select the Time Synchronization tab.
Result: The Time Synchronization tab page is displayed.

3 Click on the Value field of the Set Local Time parameter.
Result: The Change Parameter Dialog of the Set Local Time parameter is
displayed.
4 Enter the time in the Change Parameter Dialog using the following format:
YYYY-MM-DD HH:MM:SS
With:
YYYY: year (for instance 2004)
MM: month (for instance 03)
DD: day (for instance 25)
HH: hours (for instance 04)
MM: minutes (for instance 59)
SS: seconds (for instance 25)
5 Press the Execute button to confirm or the Cancel button to abort the operation.
4005743 Rev N 67
Synchronizing the ROSA EM Device with an External Device

Introduction
At regular time, the ROSA EM device can be synchronized with a time server using
the Daytime protocol or using the Network Time Protocol (NTP). When the ROSA EM
system is properly configured and after power up of the device, the synchronization
cycles are started by executing a time synchronization action. The last successful
synchronization action is displayed on the Time Synchronization tab.
Synchronizing with a Time-Server using the Daytime Protocol

The following procedure explains how to synchronize the ROSA EM device with an
external device using the Daytime protocol.
3 Click on the Value field of the Synchronization Method parameter.
Result: The Change Parameter Dialog of the Synchronization Method
parameter is displayed.
4 Point to DayTime and press the Execute button to confirm or the Cancel button to
5 Click on the Value field of the Timeserver Address parameter.

Result: The Change Parameter Dialog of the Timeserver Address parameter is
displayed.
6 Enter the IP address of the external device in the Change Parameter Dialog.
Note: The octets of the IP address must be separated by dots.
8 Click on the Value field of the Synchronization Interval parameter.
Result: The Change Parameter Dialog of the Synchronization Interval
The synchronization parameter can be set between 60 and 7200 minutes and is
default 1440 minutes by default.
9 Enter the synchronization interval and press the Execute button to confirm or the
68 4005743 Rev N
Synchronizing with a Time-Server using the NTP Protocol

The following procedure explains how to synchronize the ROSA EM device with an
external device using the NTP protocol.
4 Point to NTP and press the Execute button to confirm or the Cancel button to
5 Click on the Value field of the Continent parameter.

Result: The Change Parameter Dialog of the Continent parameter is displayed.
6 Select the continent where the ROSA EM device is located and press the Execute
button to confirm or the Cancel button to abort the operation.
Note: When the timezone and Daylight Saving Time (DTS) should not be taken
into account, the Continent parameter can be set to UTC (Coordinated Universal
Time). Using this option will force the ROSA EM system to use the time
retrieved from the time server as its internal clock. When UTC is selected, the
<x> Timezone becomes not applicable.
7 Click on the Value field of the <x> Timezone parameter.
Note: <x> preceding the Timezone parameter and the values of this parameter
depend on the selection of the Continent parameter.
Result: The Change Parameter Dialog of the <x> Timezone parameter is
displayed.
8 Select the region where the ROSA EM device is situated and press the Execute
button to confirm or the Cancel button to abort the operation.
Note: Selecting the correct region will result in a correct handling of the timezone
and DST.
9 Click on the Value field of the Timeserver Address parameter.
Result: The Change Parameter Dialog of the Timeserver Address parameter is
displayed.
4005743 Rev N 69
10 Enter the IP address of the external device in the Change Parameter Dialog.
12 Click on the Value field of the Synchronization Interval parameter.
Result: The Change Parameter Dialog of the Synchronization Interval
The synchronization parameter can be set between 60 and 7200 minutes and is
default 1440 minutes.
13 Enter the synchronization interval and press the Execute button to confirm or the
Result: When all parameters are filled in correctly; the NTP client of the ROSA EM
system will synchronize every specified interval.
Note: The ROSA EM system also executes a time synchronization when a DST
transition occurs.
Forcing a Time Synchronization

When the time synchronization parameters are properly configured, a time
synchronization with a time server can be forced. The following procedure explains
how to force time synchronization.
2 Click on the Time Synchronization tab.
3 Click on the Value field of the Synchronize Now parameter.
Result: The Change Parameter Dialog of the Synchronize Now parameter is
displayed.
4 Select SynchronizeNow and press the Execute button to confirm or the Cancel
Note: This function has no influence on the running synchronization cycle.
Switching Off Time Synchronization

The following steps explain how to switch off time synchronization.
70 4005743 Rev N
4 Point to Disabled and press the Execute button to confirm or the Cancel button to
Note: Clearing the Timeserver Address parameter also disables the time
synchronization.
Configuring ROSA EM as a Time Server

The ROSA EM is configurable as time server for synchronization of external devices
using the Daytime protocol.
Tip: You may keep all your ROSA EM devices synchronized by configuring one
device as Daytime server for all other devices.
The following procedure explains how to configure a ROSA EM as Daytime time
server.
1 Set the actual time on the Time Synchronization tab.
2 On the Services tab, enable the Daytime Server and execute a soft reset.
3 Use the IP address of this ROSA EM as time server address on the devices that
you want to have synchronized with your ROSA EM time server.
4005743 Rev N 71
Managing Services
Introduction
ROSA EM software version V04.01.30 or higher provide some basic security features
to offer more network security.
The administrator may now separately enable or disable services that are not
essential or unused. All network security experts recommend to disable unused
services to avoid any open port for potential attack. An overview of all active
TCP/UDP ports is available on the ROSA EM GUI. This allows easy identification of
the active services and established connections. This information may help the IT
network responsible to configure network firewalls and other filters accordingly to
ensure optimal network protection against internet threats.
On a ROSA EM, services are disabled by default:
after a device leaves the production line with software version V04.01.30 or later
after a factory reset
after restoring settings stored with a software version older than V04.01.30
On a ROSA EM with boot software V04.00.50 or higher, all services are password
protected. The ROSA EM software version determines whether the password is
fixed or not.
Software version older than V04.01.50: fixed password set to 'rosaem'
Software version V04.01.50 or higher: passwords to be set by the administrator,
services cannot be enabled if no password has been set
Notes:
Services are not password protected on a ROSA EM with boot software version
older than V04.00.50.
All service credentials are removed after a factory reset.
Tip: It is recommended to set a Telnet password and to enable the Telnet server. This
allows a customer services representative to remotely access the unit for
troubleshooting purposes.
Setting FTP and Telnet Passwords

The following procedure explains how to set passwords for FTP and Telnet services
on ROSA EM.
Result: The ROSA EM GUI is displayed.
72 4005743 Rev N
Managing Services
2 Select the Services tab.

Result: The Services tab is displayed.
3 Click on the Value field of the FTP Password to set the FTP password.
Result: The Change Parameter Dialog for the FTP Password is displayed.
4 Enter the FTP password in the FTP Password box.

following requirements.
4005743 Rev N 73

consecutively
easy password such as cisco, ocsic or any variant
5 Repeat the password in the Repeat value box.
6 Click Execute to confirm or Cancel to abort.
7 Click on the Value field of the Telnet Password to set the Telnet password.
Result: The Change Parameter Dialog for the Telnet Password is displayed.
8 Repeat steps 4 to 6 to set the Telnet Password.

Result: The FTP and Telnet Server Status field are displayed now on the Services
tab.
74 4005743 Rev N
Managing Services
Setting SNMP Community Strings

On a ROSA EM, no default SNMP community strings are set. You must set the
community strings before the SNMP agent can be enabled. Note that the read and
write community strings must be different.
The following procedure explains how to set SNMP community strings on ROSA
EM.
Result: The Services tab page is displayed.
3 Click on the Value field of the SNMP Read Community String.

Result: The Change Parameter Dialog for the SNMP Read Community String is
displayed.
4 Type the SNMP Read Community String in the field.

6 Click on the Value field of the SNMP Write Community String.
4005743 Rev N 75
Result: The Change Parameter Dialog for the SNMP Write Community String is
displayed.
7 Type the SNMP Write Community String in the field.

9 To activate the new SNMP Community Strings, click on the Value field of SNMP
Community Apply Changes.
10 Click Execute to apply the new community strings.
Result: The ROSA EM is rebooted and the SNMP Agent Status field is displayed
now on the Services tab.
Setting an FTP Upload Password on ROSA EM

Some devices managed by ROSA may require FTP upload to ROSA EM. A
password, named Storage Password, is required for FTP upload.
The following procedure describes how to set the Storage Password on ROSA EM.
76 4005743 Rev N
Managing Services

3 Click on the Value field of the Storage Password.

Result: The Change Parameter Dialog for the Storage Password is displayed.
4 Enter the Storage password in the Storage Password box.

following requirements.
4005743 Rev N 77

consecutively
Enabling and Disabling Services on ROSA EM

Disabled services on ROSA EM have the following impact on its functionality:
SNMP agent disabled
- ROSA EM cannot be controlled by SNMP managers and ROSA
- No SNMP trap forwarding possible
- Some ROSA EM Configuration Tools such as clone, getbackupdata ... fail
FTP server disabled
- No device management throught ftp possible
- No log file download possible
- All ROSA EM Configuration Tools fail
Telnet server disabled
- No impact on end user functionality
Daytime server disabled
- ROSA EM cannot be used as a time server
TNCS server
- No TNCS functionality available
Notes:
After upgrading to V04.01.30, all services remain enabled until they are disabled
by the user or a factory reset is executed
After downgrading from V04.01.30, the telnet server will retain its status and all
other services will become enabled.
ROSA EM backup configuration settings also contain service status settings.
Services may be enabled or disabled after restoring backup settings. When
restoring backup settings stored with an older software version on a ROSA EM
78 4005743 Rev N
Managing Services
with software version V04.01.30 or higher, all services are disabled.

The following procedure explains how to enable or disable services on ROSA EM.
3 Click on the Value field of the Services.

Result: The Change Parameter Dialog of the service is displayed.
4 Select Enabled to enable the service or Disabled to disable the service.
Notes:
Daytime service changes require a reboot
Disabling the telnet or ftp server requires a reboot
Viewing Active TCP/UDP Ports on ROSA EM

The following procedure explains how to view the active TCP/UDP ports.
1 In the menu bar of the ROSA EM GUI, click on the Reports menu and select
Active TCP/UDP Ports.
4005743 Rev N 79
Result: The Active TCP/UDP Ports dialog is displayed.
The dialog contains the following information:

Program Name: identification name
Local Port: TCP or UDP port number on the ROSA EM
Local Address: IP address of the ROSA EM
Rem Address: IP address of the remote device
Rem Port: TCP or UDP port number of the remote device
Proto: indicates the application layer protocol used for communication
State: indicates the connection state
Description: information about the connection type
2 To reload the port information, right-click the table and click Refresh.
80 4005743 Rev N
Alarm Processing
Alarm Processing
Introduction
The ROSA EM system allows the user to configure particular alarm processing
features. The following parameters of the alarm processing features can be set.
Summary Status: this parameter contains one of the following states:
- Normal: if there are no alarms in the system.
- Alarm (steady): if an alarm has been promoted from any device in the system.
- Alarm (blinking): if there is an unacknowledged system alarm.
Unacknowledged Alarm State: this parameter represents the highest alarm
severity level in the ROSA EM system that is active and not acknowledged.
Acknowledge Severity Level: This parameter represents the minimum alarm
severity that must be acknowledged. Alarms at the specified severity level and
higher flash until cleared or acknowledged. The severity levels that can be
chosen are: Critical, Major (default), and Minor.
Log Severity Level: This parameter contains the minimum alarm severity that is
recorded in the alarms log and system log. Alarms at the specified severity level
and higher are recorded in both logs. The severity levels that can be chosen are:
Critical, Major (default), and Minor. More information concerning logs can be
found in topic Viewing the ROSA EM Device Log Pages on page 61.
Alarm Promotion Threshold: Alarm promotion means the system is configured
so that an alarm occurring in a device at any level in the application is promoted
to the previous level of the hierarchy in the device list, for instance to its parent
device. Therefore, for a group device that contains multiple child devices, any
child device in an alarm state causes the parent group device to also be in the
same alarm state. The severity threshold of alarm promotion can be set. If, for
instance the alarm promotion threshold parameter is set to major, only the
alarms with severity level equal to or higher than major are promoted to the
parent group devices. The severity levels that can be chosen are: Critical, Major,
and Minor (default).
Alarm Report Threshold: This parameter contains the minimum alarm severity
that is included in the alarm report. Alarms at the specified severity level and
higher are included in the report. The severity levels that can be chosen are:
Critical, Major, Minor (default), and Warning.
To reduce the amount of alarms caused by toggling alarms, the Repetitive Alarm
Suppression feature can be used. More information about this feature can be found
in topic Filtering Toggling Alarms on page 83.
4005743 Rev N 81
To Set the ROSA EM Alarm Parameters

Performs the following steps to configure alarm processing.
top node of the device tree) and select the Alarm-Processing tab.
Result: The Alarm-Processing tab page is displayed.
2 Click on the Value field of the alarm processing parameter that should be
changed.
Result: The Change Parameter Dialog of is displayed.
3 Select the severity level in the Change Parameter Dialog of the parameter in
question and press the Execute button.
To Set the Device Alarm Parameters

With the exception of the summary alarms, the settings of the device alarms can be
changed using a shortcut menu. The following steps explain how to change the
severity level using this shortcut menu.
1 Open the ROSA EM System GUI and in the browser frame, browse to the page of
the device in question and click on the Alarms tab.
2 Right-click on the alarm of which the severity level should be changed.
Result: The shortcut menu is displayed.
3 In the shortcut menu, you can select the severity level.
4 Select the Alarm Profile option for more alarm parameters.
Result: The Alarm Profile dialog is opened.
82 4005743 Rev N
Alarm Processing
Note: The Alarm Specification gives information on the device, device type and
alarm.
5 To change the alarm delay, select a time from the Delay list box.
Note: The selected alarm delay is the minimum time when an alarm will occur.
The actual delay time could be longer due to variation in polling times.
6 To change the severity of the alarm, select the severity level from the Severity list
box.
Note: The severities list is the same as shown on the shortcut menu of step 2.
7 When notifications must be sent when the alarm occurs, select the set that refers
to the correct notification group: Notify Set A or Notify Set B.
Note: For information about the configuration and operation of notifications and
notification groups, refer to chapter Diverse Notification on page 257.
8 Click on the Execute button to confirm the selections or click on the Cancel
button to leave without changing the alarm parameters.
Filtering Toggling Alarms

Introduction
The Repetitive Alarm Suppression feature can be used to reduce the number of
alarm traps caused by toggling alarms that are sent to the central management
system.
When an alarm rises and clears a number of times (called Repetitive Alarm
Toggling Count) during a particular time interval (called Repetitive Alarm
Observation Interval) the ROSA EM system considers this alarm as a Toggling alarm
4005743 Rev N 83
and sends a Toggling Started Trap to the management system. Traps for all
following alarms (same type from same device) will be suppressed. When after a
particular time (called Repetitive Alarm Stable Interval) the alarm goes in a stable
status (risen or cleared), the ROSA EM sends a Toggled Stopped trap containing the
number of times the alarm has risen and cleared since the Toggled Start alarm was
sent and the final status of the alarm (risen or cleared).
The illustration below gives a graphical representation of the Repetitive Alarm
Suppression feature (Repetitive Alarm Toggling Count = 3)
Alarm risen
Alarm cleared
Device
Cleared trap
Started trap
Toggling
Toggling
Trap
ROSA EM
Repetitive Alarm Repetitive Alarm

Observation Interval Observation Interval
Note: During the Repetitive Alarm Observation Interval, sending Traps related to
the same alarm can be delayed until the interval is ended or until the Repetitive
Alarm Toggling Count is reached. Traps related to the same alarm arisen during
this interval will be buffered and flushed at the end of this interval if the Repetitive
Alarm Toggling Count is not reached. This feature can be switched on or off by
setting the Repetitive Alarm Observation Window Alarm Suppression parameter
respectively to Yes or to No.
Configuring the Repetitive Alarm Suppression Feature

The following procedure explains how to configure the Repetitive Alarm
Suppression feature.
top node of the device tree) and select the Alarm-Processing tab.
Result: The Alarm-Processing tab page is displayed.
84 4005743 Rev N
Alarm Processing
2 Click on the Value field of the Repetitive Alarm Suppression Enable parameter.
Result: The Change Parameter Dialog of selected parameter is displayed.
3 Select the Enable in the Change Parameter Dialog press the Execute button.
4 Click on the Value field of the Repetitive Alarm Toggling Count parameter.
5 Enter the number of times an alarm has to rise and clear within the Repetitive
Alarm Observation Interval before the Toggling Alarm trap must be sent in the
Change Parameter Dialog press the Execute button.
6 Click on the Value field of the Repetitive Alarm Observation Interval
parameter.
7 Enter a value for the Repetitive Alarm Observation Interval parameter (in
seconds) in the Change Parameter Dialog press the Execute button.
8 Click on the Value field of the Repetitive Alarm Stable Interval parameter.
9 Enter a value for the Repetitive Alarm Stable Interval parameter (in seconds) in
the Change Parameter Dialog press the Execute button.
10 Click on the Value field of the Repetitive Alarm Observation Window Alarm
Suppression parameter.
11 Select Yes or No in the Change Parameter Dialog press the Execute button.
Enhanced Redundancy Trigger Logic

Introduction
ROSA EM's Enhanced Redundancy Trigger Logic (or for short ERTL) feature allows
combining ROSA EM alarms and/or parameter values coming from several devices
into logical expressions that results in triggering one or multiple other alarms
(further called custom alarms).
4005743 Rev N 85
Important:
Parameter values of the ROSA EM Input/Output functionality cannot be used in
the ERTL feature.
The devices supporting custom alarms are the DCM, D9036, and the Signal State
virtual device.
The number of custom alarms for all these devices is limited to 20.
Delayed Custom Alarms are not supported. If a Custom Alarm has its Delay
property set to a value different from 0 seconds, then the logic expression that
defines that alarm reports an error. (The error appears when the State of the logic
expression becomes True).
About the ERTL Virtual Device

ROSA EM's ERTL feature needs the ERTL virtual device (devtype = logic) in its
devlist. The way to add devices to the devlist can be found in topic Working with
Devices and Groups on page 91.
One ERTL virtual device can handle up to 20 logic expressions. If more expressions
are required, multiple ERTL virtual devices must be added to the devlist.
About the Logic Expressions

A logic expression for ERTL is built up using the following fields:
Result = Parameter1 Operator Parameter2
With:
Result
The Result field can either be a custom alarm name or an intermediate variable.
Intermediate variables are useful if multiple logic expressions are required to set
up a custom alarm. If an ERTL expression is given with custom alarm and the
corresponding device supports custom alarms, then the CustomAlarms tab page
will be added to the device interface containing this custom alarm with status
indication, see picture below.
The syntax for the result field is:

group.device.customalarm
with:
- group: the name of the group to which the device belongs to. If the device
doesn't belong to a group, this parameter should be omitted.
- device: the name of the device for which the custom alarm must be created
86 4005743 Rev N
Alarm Processing
- customalarm: the name for the custom alarm

For example: D9036pool1.D9036_A.backuptrigger
Notes:
The group, device (or devtype template), and alarm name must be
separated by a dot. If the result string doesn't contain a dot, the ROSA
EM system assumes that the result is a variable.
The name of a variable must be unique within the ERTL and can be a
sequence of letters, numbers, plus (+), minus (-), and underscore (_).
Parameter 1 & Parameter 2
To build up ERTL expressions, several parameter syntaxes can be used:
- For specifying a parameter
group.device.parametername
with:
parametername: the name of the parameter.
For a parameter name consisting of a single word, use the complete
parameter name.
For a parameter name consisting of multiple words separated by blanks,
use its short name. A short name consists of the first three characters of
each word in the parameter name without blanks. For example the short
name of the Device Operational Failure parameter is devopefai.
Hint: A short name can easily be retrieved by right-clicking on the
corresponding parameter and pointing to Copy Short Name to
Clipboard in the shortcut menu. This short name can then be pasted into
the parameter field of the ERTL expression by using the [Ctrl] + [V] key
combination. If needed, other parts of the parameter can then manually
be added like device, group...
Notes
For a word consisting of one or two characters, use the complete
word.
Parameters consisting of a single word and preceding by an asterisk *
(referring to another parameter) are allowed.
A parameter consisting of multiple words separated by blanks and
referring to another parameter cannot be used as parameter for an
ERTL expression. Copying such parameter into the parameter field of
an expression is not possible and results in an empty field.
device: the name of the device to which the parameter belongs to
group: the name of the group to which the device belongs to
Notes:
The group, device, and parameter name must be separated by a dot.
4005743 Rev N 87
A parameter can be inverted by adding an exclamation mark before the

group.device.parametername.
- For specifying a intermediate variable (see result)
- For specifying a value
- An exclamation mark (!) preceding a parameter inverts the Boolean value of
the parameter.
Important: As soon as the name of an intermediate variable matches a used
value, the corresponding value in the expression becomes intermediate variable.
In for instance the value Normal is used in an expression to compare the status of
a parameter and a new expression is created with the intermediate variable
Normal, the parameter will no longer be compared with the value Normal but
with the intermediate variable Normal.
Operator
The operators that can be used in logic expressions are: AND, OR, EQUALS, and
NOT EQUAL.
For AND and OR operations, normal corresponds with false and alarm with true.
Notes:
When an ERTL expression has to apply to multiple devices with the same
devtype, the devtype template can be used. By using the devtype template
instead of the device name, the expression will be applied to all devices of the
given group that match the devtype. If no group is specified in the expression,
the expression will be applied to all devices. The syntax of a devtype template is
<devtype>, the devtype of the devices surrounded by < and >.
For example: D9036pool1.<D9036>.backuptrigger
This result defines the backuptrigger custom alarm for all D9036 devices that
belong to the D9036pool1 group.
The device names and variables in the ERTL expression are not case sensitive but
the devtype in a template and a value is case sensitive.
The maximum number of characters that can be entered in the result and
parameter fields is limited to 40 characters. This is important when groups and
devices are used with rather long names.
Defining a Logical Expression

A logic expression must be defined in the Logic tab page of the ERTL virtual device
and one ERTL virtual device can handle 20 expressions. The following procedure
describes how to define a logic expression.
1 Open the ROSA EM GUI, in the browser frame browse to the ERTL page, and
click on the Logic tab.
Result: The Logic tab page is displayed.
88 4005743 Rev N
Alarm Processing
2 Click on the Result field in the row of the expression that must be defined.
Result: The Change Parameter Dialog of this parameter appears.
3 Enter the result string in the Change Parameter Dialog and press the Execute
button.
4 Click on the Parameter 1 field in the row of the expression.
5 Enter the parameter 1 string in the Change Parameter Dialog and press the
Execute button.
6 Click on the Operator field in the row of the expression.
7 Select the operator and press the Execute button.
8 Click on the Parameter 2 field in the row of the expression.
9 Enter the parameter 2 string in the Change Parameter Dialog and press the
Execute button.
Next to the Result, Parameter 1 & 2, and Operator fields, a logic expression is
accompanied with following information:
State (read only): this field represents the status of the expression: True, False,
Unsolvable, or Template.
Error Hint (read only): this field gives information about the expression if an
error occurs.
Notes (read write): this field can be used to provided additional information
about the expression (max. 40 characters)
4005743 Rev N 89
Hint: All expressions of the ERTL virtual device can be re-evaluated in a single
action by executing the ReEvaluate All Expressions function. This can be done by
setting the value of the corresponding parameter on the Configuration tab to
Execute.
90 4005743 Rev N
Working with Devices and Groups

Introduction
ROSA EM offers a feature that allows you to add/delete devices and groups via the
device tree of the ROSA EM GUI instead of creating and editing of the device list.
Important: When device or group changes are made via the device tree, the device
list is automatically updated according to the new situation.
Adding Devices
The following steps explain how to add a device to the device tree.
1 In the browser frame of the ROSA EM GUI, right-click on the device or group
immediately above the location where you want to add a new device.
Note: You can also right-click on the top node of the device tree.
Result: The options short-cut menu appears.
2 Select Add Device.
Result: The Add Device dialog is displayed.
3 In the list, select the device you want to add.

Result:
A suggested device name for the device displays in the Name box.
A suggested address displays in the Address box.
A suggested communication port displays in the Port box.
4005743 Rev N 91
Notes:
Some devices will use the Ethernet port instead of a COM port.
Some devices are virtual and dont need a communication port.
When a device has a slot number or an SNMP index point, additional edit
fields are displayed.
The edit box Sub Slot will only be enabled when the selected device supports
a sub slot point, for instance Prisma II Module.
4 If desired, type a different device name in the Name box.
Important: Do not include delimiters such as spaces, commas, periods, and
semicolons in the name.
5 If the device address displayed in the Address box is not correct, type the correct
address in the Address box.
6 In the Port box do one of the following:
If a port number is displayed and you want to use it for the device, proceed
to step 7.
Click on the down arrow on the right of the box and select a communication
port from the list.
Type a new port using the format COM<port number> where <port
number> is replaced with the number of the communication port.
7 If you right-clicked on a device or a group in step 1, the Add Device dialog also
shows an Advanced button.
Click on this button and you can choose a parent for the new device:
The new device is added at the same level as the device or group that you
right-clicked in step 1 or
The new device is added one level deeper and belongs to the device or group
that you right-clicked in step 1.
Example:
8 Click on the OK button to add the new device.

Result: The device tree in the browser frame is updated.
Adding Groups
The following steps explain how to add a group to the device tree.
1 In the browser frame of the ROSA EM GUI, right-click on the device or group
immediately above the location where a new group must be added.
92 4005743 Rev N
Note: You can also right-click on the top node of the device tree.
2 Select Add Group.
Result: The Add Group dialog is displayed.
3 Type the name of the new group in the Name box.

Important: Do not include delimiters such as spaces, commas, periods, and
semicolons in the name.
4 Choose a parent for the new group you want to add:
The new group is added at the same level as the device or group that you
right-clicked in step 1 or
The new group is added one level deeper and belongs to the device or group
that you right-clicked in step 1.
5 Click on the OK button to add the new group.
Result: The device tree in the browser frame is updated.
Delete a Device or Group

The following steps explain how to delete a device or a group from the device tree.
1 In the browser frame of the ROSA EM GUI, right-click on the group or device
you want to delete.
2 Select Delete Device.
Result: The Delete verification dialog is displayed.
3 Click on Yes to delete the device or group, click on the No or Cancel button to
4005743 Rev N 93
Important: Deleting a group also deletes its children. This means that all devices
and groups that display under the group in the device tree will also be deleted.
94 4005743 Rev N
Configuring Device Polling

Introduction
After powering up ROSA EM, it starts poll cycle routines for each individual
communication port. Note that all inputs and outputs of the I/O functionality of the
ROSA EM system are considered as one communication port. Before a poll cycle
routine is started, the ROSA EM system consults the device list to determine the
devices connected to the ports. Each device connected to a port and member of the
device list for the port is polled consecutively. When the last device connected to the
port is polled, the poll cycle is restarted.
The ROSA EM system provides two polling action types: Status Polling and Poll-all
polling. Status polling means that the ROSA EM system asks the device for the
parameters that could change often, like measurements, alarm states... Poll-all polling
means that the ROSA EM system asks the device for all data. The ROSA EM system
normally polls a device using a Status Polling but at regular time (adjustable by
changing the Device Poll-All Count parameter) the system performs a Poll-all
polling action. After a specific number of consecutive unsuccessful Status Polling
actions of a particular device, the ROSA EM system places the device in offline state.
After a specific number of polling cycles, the offline state of the device is canceled.
The following parameters can be changed to configure device polling:
Min Poll Period: this parameter contains the minimum number of milliseconds
the ROSA EM system must wait before polling the same device again. This
feature can be used in applications where only a few devices are connected to a
communication port and the ROSA EM system could poll the same device
quicker than the specified number of milliseconds. The default value of this
parameter is set to 1000 milliseconds and can be set between 0 and 999999
milliseconds. Rosaemio does not take this parameter into account. A fixed
period of 500 ms is used instead.
Device Offline Threshold: contains the number of consecutive unsuccessful
Status Polling actions that should elapse before the ROSA EM system places an
unresponsive device in offline mode. The default value of this parameter is 3
poll cycles and can be set between 0 and 9 poll cycles.
Device Retry Count: contains the number of poll cycles that should elapse before
the ROSA EM system re-polls an offline device. This parameter can be changed
between 0 and 99 poll cycles and is default set to 30 poll cycles.
Device Poll-All Count: contains the number of Status Polling cycles that should
elapse before the ROSA EM system request all data of a device (poll-all cycle).
This feature can be used for devices that normally only send changed data to the
ROSA EM system during polling. Requesting all of a devices data helps ensure
that the ROSA EM system is informed of any minor changes that the device
4005743 Rev N 95
might not normally report. This parameter can be changed between 0 and 999
poll cycles and is default set to 300 poll cycles.
IIOP Call Time Out: specifies the time-out to use for all IIOP communication the
ROSA EM device performs (for instance to D96xx devices). This parameter can
be changed between 10 and 10000 ms and is default set to 3000.
To Configure Device Polling

The following procedure explains how to change the Device Offline Threshold, the
Device Retry Count, the Device Poll-All Count, and the IIOP Call Time Out
parameter.
top node of the device tree) and select the Device Polling tab.
Result: The Device Polling tab page is displayed.
2 Click on the Value field of the Device Offline Threshold parameter.

3 Enter the desired value in the Change Parameter Dialog of the Device Offline
Threshold parameter and press the Execute button.
4 Click on the Value field of the Device Retry Count parameter.
5 Enter the desired value in the Change Parameter Dialog of the Device Retry
Count parameter and press the Execute button.
6 Click on the Value field of the Device Poll-All Count parameter.
7 Enter the desired value in the Change Parameter Dialog of the Device Poll-All
Count parameter and press the Execute button.
8 Click on the Value field of the IIOP Call Time Out parameter.
9 Enter the desired value in the Change Parameter Dialog of the IIOP Call Time
Out parameter and press the Execute button.
Perform the following steps to change the Min Poll Period parameter.
top node of the device tree) and select the System tab.
Result: The System tab is displayed.
2 Click on the Value field of the Min Poll Period parameter.
3 Enter the desired value in the Change Parameter Dialog of the Min Poll Period
parameter and press the Execute button.
96 4005743 Rev N
Switching On or Off the Polling Actions of a Device

The ROSA EM system offers the possibility to switch on or off the polling actions of
a particular device.
Note: When the polling actions of a device is switched on or off, a Trap will be sent
to the SNMP managers to notify them about this change.
This function can be useful during reconfiguring of devices.
the device in question and click on the Properties tab.
Result: The Properties tab page is displayed.
2 Click on the Value field of the M&C-Scan parameter.

Result: The Change Parameter Dialog of the M&C-Scan parameter is displayed.
3 Select On-Scan to enable the input scan function of all inputs or Off-Scan to
disable this function.
Note: Switching on or off the polling action of a device can also be done using the
shortcut menu.
The following explains how to switch on or off the polling actions of a particular
device using the shortcut menu.
the device in question.
2 Right-click on the device in question.
Result: The shortcut menu is displayed.
3 Select On-Scan to enable the polling actions for the device in question or Off-
Scan to disable this function.
4005743 Rev N 97
Executing a Polling Action Manually

The following steps explain how to execute a manual polling action for a particular
device.
the device in question.
2 Right-click on the device in question.
Result: The short-cut menu is displayed.
3 In the short-cut menu, select Retry Device.
98 4005743 Rev N
Working with Alarms
Working with Alarms

Reporting the Active Alarms
The ROSA EM device keeps a report with all active alarms, sorted by severity level,
along with the following alarm information: device hierarchical name, point name,
and point value. This Active Alarm Report can be displayed using the ROSA EM
GUI and is dynamically updated. The Point Value parameter of an alarm is shown
in the color associated with the severity level of the alarm (for instance red for an
alarm with critical severity). For more information concerning the color code, please
refer to topic Viewing or Changing the Severity Color Code on page 100.
The following steps explain how to check the active alarm report.
1 In the menu bar of the ROSA EM GUI, click on the Reports menu and select
Active Alarms.
Result: The Active Alarm Report is displayed.
2 When you double-click on the row of an active alarm, the alarm page of the
device where the active alarm occurs will automatically be displayed.
When you right-click on the row of an active alarm, an option menu appears.
This option menu is further explained in the topic Overview of Graphics on page
232.
Note: In case a tab page contains one or more alarms, the color of the tab will be
the same as the highest alarm severity on that tab page.
Enabling or Disabling the Blink Not Acknowledge Feature

When an alarm is present and not yet acknowledged, the active alarm blinks. This
Blink Not Acknowledge feature is default enabled. The following explains how to
disable this feature.
1 In the menu bar of the ROSA EM GUI, click on the Alarms menu and set the
Blink Not Acknowledged check box.
Result: All active alarms stop blinking.
4005743 Rev N 99
Executing the Acknowledge-All Alarms Feature

For maintenance purposes or during troubleshooting, the ROSA EM device allows
acknowledging all active alarms.
Note: The operator must have a privilege level of Configure to use this feature.
The following steps explain how to execute the Acknowledge All Alarm feature.
1 In the menu bar of the ROSA EM GUI, click on the Alarms menu and select
Acknowledge all.
Result: All active alarms are acknowledged and are no longer blinking. They
remain in alarm status until the cause of the alarm has been cleared.
2 Take the necessary steps to determine the cause of the alarm(s).
Viewing or Changing the Severity Color Code

The severity of alarms is shown using colors. This color code can be checked or
changed using the following procedure.
1 In the menu bar of the ROSA EM GUI, click on the Help menu and select Color
Key.
Result: The Color Key window is displayed.
2 To change an alarm severity color, double click on the colored rectangle next to
the alarm severity.
100 4005743 Rev N

Working with Alarms
Result: A dialog appears where you can choose a new color and see a preview.
The new color will be applied when you click on the OK button.
Note: The new color will also be used on the tab in case the tab page contains an
alarm of the same severity.
4005743 Rev N 101

Viewing the Hardware and Software Information

Introduction
The hardware and software information of the ROSA EM system can be found on
the Properties tab and on the System tab of the ROSA EM System GUI.

Perform the following steps to check the hardware information of the ROSA EM
device.
1 Open the ROSA EM GUI, click on the ROSA EM device (the top node of the
device tree) in the browser frame and select the Properties tab.
The following information is available:

DevType Revision: contains the revision of the system device type file used
by the ROSA EM device.
Product Package: contains the product package of the device.
Software Revision: represents the revision of the software used by the ROSA
EM device.
Boot Software Revision: contains the revision of the boot software.
Apollo Software Revision: contains the revision of the software used by the
Apollo functionality of the ROSA EM device.
Device Serial Number: represents the serial number of the ROSA EM device.
This serial number can also be found on the label affixed to the housing of
the device.
Description: represents the device on which the ROSA EM software runs.
2 Select the System tab.
102 4005743 Rev N

Result: The System tab page is displayed.
The following hardware and software information is available:

ROSA/EM CPU board type: represent the name of the CPU board installed
in the ROSA EM device.
ROSA/EM Altera software version: contains the revision of the software
used by the Altera device on the main board.
ROSA/EM mainboard hardware version: contains the revision of the main
board installed in the ROSA EM device.
ROSA/EM CompactFLASH Model: represent the model of the compact flash
card used by the CPU board.
ROSA/EM CompactFLASH Firmware: contains the version of the firmware
used by the compact flash card.
ROSA/EM COM X port type: represents the configuration of the COM port
in question (with X a number between 5 and 8).
4005743 Rev N 103

Checking the ROSA EM Device Temperature and Voltage

Levels
Introduction
The device temperature of the ROSA EM system, the 3.3 V DC and 12 V DC
generated and used by the ROSA EM device are continuously monitored. The
measuring area of these parameters is divided in 5 zones: the major low, the minor
low, the nominal, the minor high, and the major high zone. When the measured
value of a parameter exceeds a threshold, a related alarm is generated. The
threshold values are relative to the nominal value, that means that the threshold
value must be added to the nominal value to become the absolute threshold value.
Major high alarm zone
Minor high alarm zone

Major High
Threshold
Minor High
Normal zone Threshold
Nominal
Note: The threshold values of the device temperature are adjustable but the
threshold values of the voltage levels are read-only.
To Check the Device Temperature and Voltage Levels

The following steps explain how to check the ROSA EM device temperature and the
voltage levels.
1 Open the ROSA EM GUI and in the browser frame, browse to the rosaemio (io)
page, and click on the Parameters tab.
Result: The Parameters tab page is displayed.
The following information can be checked:

Parameter: a read-only parameter and identifies the measured parameter.
Present Value: a read-only parameter and represents the actual measured
value.
104 4005743 Rev N

Checking the ROSA EM Device Temperature and Voltage Levels
Nominal Value: represents the nominal value of the parameter. Note that
the temperature parameter is read-write and the voltage parameters are read-
only.
Minor-Alarm Low Limit: represents the minor alarm low threshold. Note
that the temperature parameter is read-write and the voltage parameters are
read-only.
Minor-Alarm High Limit: represents the minor alarm high threshold. Note
read-only.
Major-Alarm Low Limit: represents the major alarm low threshold. Note
read-only.
Major-Alarm High Limit: represents the major alarm high threshold. Note
read-only.
Changing the Device Temperature Unit

The following procedure explains how to change the device temperature unit.
page, and click on the Inputs_Outputs tab.
Result: The Inputs_Outputs tab page is displayed.
2 Click on the Value field of the Internal Temperature Unit parameter.

Result: The Change Parameter Dialog of the Internal Temperature Unit
3 Select F (Fahrenheit) or Deg_C (Celsius) and click on the Execute button to
confirm or the Cancel button to abort the operation.
4005743 Rev N 105

Sending Traps
Configuring the Trap Traffic
Introduction
When an alarm arises or a status changes in a ROSA EM device or in a device
connected to and supported by the ROSA EM device, traps can be sent to particular
SNMP managers. ROSA EM systems allow configuring maximum 4 SNMP
managers. Changing the SNMP Trap parameters can optimize the trap traffic. More
information concerning SNMP Trap parameters can be found below in topic
Changing the SNMP Parameters.
If the connection between a ROSA EM device and a SNMP manager system is
established via a semi-permanent connection (for instance ISDN), using trap
buffering can reduce the number of dialups. More information concerning trap
buffering can be found in topic Configuring Trap Buffering on page 108.
Important: The SNMP agent on ROSA EM with software version V04.01.30 or higher
is default disabled. Enable the SNMP agent for sending traps to an SNMP manager.
For more information, please refer to topic Managing Services on page 72.
Changing the SNMP Parameters

The following procedure explains how to change the SNMP settings
top node of the device tree) and select the SNMP tab.
Result: The SNMP tab page is displayed.
2 Click on the Value field of the parameter that should be changed.

3 Enter or select the desired value and press the Execute button to confirm or the
The following parameters can be changed to configure the trap traffic:
106 4005743 Rev N

Sending Traps
SNMP Manager IP Address 1 4: the IP address of the SNMP Manager

system. Maximum 4 SNMP managers can be entered.
SNMP Trap Threshold: This parameter acts as a filter to reduce or to
increase the trap traffic. Alarms at the specified severity level or higher will
be sent; the lower will be blocked. The following settings can be chosen:
None, Minor (default), Major, and Critical. The setting None means all Traps
are blocked.
SNMP Trap Format: Determines the trap format that is used: Limit or Value.
Limit means ROSA EM includes the word High or Low in the trap to
designate that the device exceeded an acceptable high or low parameter limit.
Value means ROSA EM sends the actual value of the out-of-range parameter,
unless the alarmed parameter does not have a reportable value, in which
case, the limit value is sent.
SNMP Trap Max Rate: The maximum trap rate that can be received by a
SNMP manager depends on the used SNMP management software. Before
changing this parameter, please read the documentation shipped with your
SNMP management software. This parameter can be set between 1 and 9999
(default 25).
SNMP Trap Community String: This parameter can be used to provide
authentication, privacy, and authorization services.
Regenerating the Traps of Active Alarms

The ROSA EM system offers the option of sending traps to the SNMP manager
systems for all active alarms. This feature is typically used after a communication
failure with SNMP manager systems. So the manager system can be updated to the
current state of the ROSA EM device. The following procedure describes how to
regenerate traps of the active alarms.
Result: The SNMP tab is displayed.
2 Click on the Value field of the Trap Regen For Active Alarms parameter.
Result: The Change Parameter Dialog of the Trap Regen For Active Alarms
parameter
3 Select regenerate and press the Execute button to confirm or the Cancel button to
Result: The regenerated traps of the active alarms are sent to the SNMP
Manager.
Note: This setting is transient, when the regenerated traps are sent, this
parameter returns to off.
4005743 Rev N 107

Configuring Trap Buffering

Introduction
When a ROSA EM device is used over a semi-permanent network, for instance an
Integrated Services Digital Network (ISDN), each time an alarm or status transition
occurs a connection will be made for sending an SNMP trap. This results in high
dialup costs. To decrease the dialup costs, the ROSA EM system allows buffering
the traps to one of the SNMP managers.
The following illustration shows a ROSA EM device used in an ISDN and a ROSA
EM device used in an Ethernet network.
Master Headend with ROSA NMS
Ethernet
Hub/Switch Headend A
Ethernet
Ethernet Hub/Switch
ISDN
Router
ROSA Element
Manager
ISDN
Headend B
ISDN
Router
Ethernet
Hub/Switch
Ethernet
Ethernet
ROSA Element
Manager
I/O
RCDS
I/O
SMC
108 4005743 Rev N

Sending Traps
When trap buffering is enabled for a particular SNMP manager, traps are bundled
and after a configurable delay sent to the SNMP Manager. This delay is setup with
respect to the severity level of the detected alarm or the status transition.
It is possible to delay minor alarms so that the ROSA EM device informs the SNMP
manager for instance once a day and for major alarms or status transitions for
instance four times a day. For higher severity events it is recommended to use less
delay to notify the SNMP manager earlier than in the case of lower severity events.
If it is time to send a buffered trap, the ROSA EM system will first check whether the
IP link to the SNMP manager is OK by sending ICMP ping packets to the manager.
When the ping action is unsuccessful, this action is retried with an increasing
waiting period between the failing tries. When a ping succeeds the complete bundle
of traps is sent to the SNMP manager.
The purpose of configuring these delay settings is on the one hand to minimize the
number of calls and on the other hand to maximize the communication if necessary.
Note: Traps originating from a device connected to and supported by (member of
the device list with a matching device type) a ROSA EM Device will be decoded to
determine the severity level of the event and classified in the alarm buffer with the
associated times.
WARNING:
If the ROSA EM device is managing other SNMP devices and the ROSA EM
device is used over a semi-permanent network, be sure to add this ROSA EM as a
trap destination for these SNMP devices and to enable Trap Buffering. If you add
the IP address of your SNMP Manager NMS instead of ROSA EM, Trap Buffering
will not work for these devices, resulting in possible high dialup costs.
Configuring Trap Buffering

Note: Before configuring Trap buffering, the trap traffic of the ROSA EM device has
to be configured. More information concerning the configuration of the trap traffic
can be found in topic Configuring the Trap Traffic on page 106. The following
procedure explains how to configure trap buffering.
top node of the device tree) and select the Alarm_Buffering tab.
Result: The Alarm_Buffering tab page is displayed.
4005743 Rev N 109


The following parameters can be changed:
Alarmbuffering Buffered SNMP Devices: this parameter contains the list
with the IP addresses of all devices for which traps will be buffered. These IP
addresses should be separated by spaces. The string all means that the traps
of all connected devices will be buffered and the string None means that no
traps coming from connected devices will be buffered.
Alarmbuffering Trapbuffering for SNMP Manager 1 - 4: Determines the
SNMP manager for which trapbuffering should be enabled.
Remark: Only one SNMP manager can be enabled for Trapbuffering.
Alarmbuffering Redelivery delay: determines the time between a failed
pinging action and a new one. This parameter can be set between 1 and 9999
minutes (default 2 minutes).
Alarmbuffering Max Traps Per Second: the maximum number of Traps per
second that will be transmitted during a trap buffer flushing. This parameter
can be set between 1 and 9999 traps per second (default 5).
Alarmbuffering Maximum Critical Delay: the maximum time between the
moment a critical event occurs and the moment the first attempt will be made
to send out the buffered traps. This parameter can be set between 1 and
999999 minutes (default 1 minute).
Alarmbuffering Maximum Major Delay: the maximum time between the
moment a major event occurs and the moment the first attempt will be made
999999 minutes (default 5 minutes).
110 4005743 Rev N

Sending Traps
Alarmbuffering Maximum Minor Delay: the maximum time between the

moment a minor event occurs and the moment the first attempt will be made
999999 minutes (default 60 minutes).
Alarmbuffering Maximum Notification Delay: the maximum time between
the moment a notification was generated and the moment the first attempt
will be made to send out the buffered traps. This parameter can be set
between 1 and 999999 minutes (default 1 minute).
Sending the Buffered Traps Manually

The ROSA EM device allows the operator to manually send the buffered traps to the
SNMP Manager. Perform the following steps to manually send the buffered traps.
Result: The Alarm_Buffering tab is displayed.
2 Click on the Value field of Alarmbuffering Report Alarms Now parameter.
Result: The Change Parameter Dialog of the Alarmbuffering Report Alarms is
displayed.
3 Select ReportNow and press the Execute button to confirm or the Cancel button to
Result: The buffered Traps are sent to the SNMP Manager.
Note: This setting is transient, when the Trap buffer is flushed, this parameter
returns to Continue.
Viewing the Trap Buffering Figures

The following procedure explains how to check the Trap buffering figures.
Open the ROSA EM GUI; in the browser frame click on the ROSA EM device (the
4005743 Rev N 111

Result: The following parameters can be checked:

Alarmbuffering Buffered Traps: represent the total number of buffered
traps.
Alarmbuffering Critical Traps: represent the number of buffered traps
coming from critical events.
Alarmbuffering Major Traps: contain the number of buffered traps coming
from major events.
Alarmbuffering Minor Traps: contain the number of buffered traps coming
from minor events.
Alarmbuffering Effective Redelivery Delay: contains the time between the
last attempt to send the buffered traps and the last but one.
Alarmbuffering Last Successful Delivery: represent the moment that the
last delivery was successful.
Alarmbuffering Last Delivery Attempt: represent the moment that the last
attempt, to send the buffered traps, was started.
Disabling Trap Regeneration for Devices in Maintenance Mode or Off-Scan Mode

The ROSA EM system offers the option to disable trap regeneration for devices that
are in maintenance mode or devices that are not polled, for example off-scan mode.
The default behavior is to regenerate traps for all devices. To change this behavior,
follow the next procedure.
112 4005743 Rev N

Sending Traps
2 Click on the Value field of the parameter that should be changed:

Trap Regen for Maintenance Mode: This parameter concerns devices in
maintenance mode. For more information on how to set devices in this
mode, please refer to the topic Maintenance Mode further in this section.
Trap Regen for Off Scan Devices: This parameter concerns devices that are
not polled, for instance off-scan mode.
3 Select Enabled or Disabled and press the Execute button to confirm or the Cancel
Result:
Enabled: Trap regeneration is also done for the respective devices.
Disabled: Trap regeneration is not done for the respective devices.
Note: The Trap Regen for Maintenance Mode parameter is not displayed if the
Trap Generation for Maintenance Mode parameter is set to Enabled. More
information about this parameter can also be found in topic Using Maintenance Mode
121.
4005743 Rev N 113

Resetting the ROSA EM Device Parameters

Introduction
The ROSA EM device settings can be reset to the default factory settings.
Two reset modes are available:
Factory reset: resets all settings except for the IP address and disables all services
Reset settings: resets all settings except for the IP address, service credentials,
operator passwords and service settings
To Reset the ROSA EM Device Parameters

The following procedure explains how to reset a ROSA EM device.
3 Click on the Value field of the Factory Reset or Reset Settings parameter.
Result: The Change Parameter Dialog of the Factory Reset parameter displays.
114 4005743 Rev N

Resetting the ROSA EM Device Parameters
4 Enter the Factory Reset Code (see the Factory Reset Code value on the System
tab page) in the Change Parameter Dialog.
Result: After pressing the Execute button, the ROSA EM Device is rebooted
using the default settings.
Note: Rebooting the ROSA EM device may take some time. During rebooting, a
running light is started for a while using the front panel LED indicators of the device
and the messages Waiting To Reconnect, Attempting Connection To Server, and Connect
Attempt Failed, Try number=X appear several times in the status bar of the GUI. After
rebooting, the RUN LED on the front panel of the device starts blinking and the
messages Data Transfer Complete is displayed in the status bar.
4005743 Rev N 115

Restarting the ROSA EM Device

Introduction
A ROSA EM Device can be restarted locally by power cycling the device or remotely
by executing a restart using the ROSA EM GUI.
Restarting the ROSA EM Device from a Remote Location

The following procedure explains how to restart the ROSA EM device from a remote
location.
3 Click on the Value field of the Soft Reset parameter.

Result: The Change Parameter Dialog of the Soft Reset parameter is displayed.
4 Select ResetNow and press the Execute button to confirm or the Cancel button to
Result: After pressing the Execute button, the ROSA EM device starts rebooting.
116 4005743 Rev N

Restarting the ROSA EM Device
Note: Rebooting the ROSA EM device may take some time. While rebooting, a
running light sequence of the front panel LED indicators is started and the messages
Waiting To Reconnect, Attempting Connection To Server, and Connect Attempt Failed, Try
number=X appear several times in the status bar of the GUI. After rebooting, the
RUN LED on the front panel of the device starts flashing and the messages Data
Transfer Complete is displayed in the status bar.
4005743 Rev N 117

Device Backup Operation

Introduction
The ROSA EM system can participate into backup applications. When a main to
backup transition or vice versa is requested (for instance by a failing device) the
ROSA EM is triggered to start a particular backup/restore sequence. Depending on
the nature of the application, different backup/restore scenarios are foreseen.
More information concerning the integration of a ROSA EM device into a
backup/restore application can be found in chapter Backup Operation on page 287.
To Enable or Disable Device Backup

The following procedure explains how to enable or disable the backup functionality
of a ROSA EM device.
2 Select the Device Backup tab.
Result: The Device Backup tab page is displayed.
3 Point to the Value field of the Backup Sub System parameter.

Result: The Change Parameter Dialog of the Backup Sub System parameter is
displayed.
4 Select Enable or Disable and press the Execute button to confirm or the Cancel
118 4005743 Rev N

Configuring HFC-Plant-Monitoring
Configuring HFC-Plant-Monitoring
Introduction
If you have AM Communications transponders in your network, you might have
noticed that the Transmit Frequency and Transponder Output Level parameters in
the transponders Device Details window are blank, even when the ROSA EM
system and the device are successfully communicating. This situation can be
confusing, but it is a normal result of the transponders functioning. You can
configure the HFC-Plant-Monitoring section to automatically fill in these fields if they
are blank. Two parameters can be set to configure the HFC-Plant-Monitoring:
AM Auto Configuration: this option enables or disables the AM Auto
Configuration feature. When this parameter is set to Enabled, the ROSA EM
system automatically fills in the Transponder Output Level parameter in the
transponders Device Details window with the highest output level allowed for
the device the next time it is polled.
Important: If you use more than one reverse path frequency, this field must be
set to Disabled. Select Enabled if you use only one reverse path frequency. This
feature should be enabled before the final balancing of the return system.
Return Frequency: this parameter represents the transponders transmit
frequency to be used in the AM Auto Configuration feature. The next time the
transponder is polled, the ROSA EM system fills in the Transmit Frequency
parameter in the transponders Device Details window, assuming the AM Auto
Configuration parameter is set to Enabled.
The valid range is 0 MHz to 50 MHz.
The Return Frequency field refers to the return path, which is the same as
the transponders transmit path.
The ROSA EM system allows our transponders and AM Communications
transponders to share the same frequency.
To Configure HFC-Plant-Monitoring
The following steps explain how to configure HFC-Plant-Monitoring.
1 Open the ROSA EM GUI.
2 In the browser frame click on the ROSA EM device (the top node of the device
tree) and select the HFC-Plant-Monitoring tab.
Result: The HFC-Plant-Monitoring tab page is displayed.
4005743 Rev N 119

3 Click on the Value field of the AM Auto Configuration parameter.

Result: The Change Parameter Dialog of the AM Auto Configuration
5 Click on the Value field of the Return Frequency parameter.
Result: The Change Parameter Dialog of the Return Frequency parameter is
displayed.
6 Enter a value between 0 and 50 and press the Execute button to confirm or the
Note: This parameter should be set when the AM Auto Configuration parameter is
enabled.
120 4005743 Rev N

Using Maintenance Mode
Using Maintenance Mode

Introduction
The ROSA EM device allows you to switch on or off the alarm declaration and
propagation function of the I/O functionality or for every device in the device tree.
Switching on this function can be used during maintenance activities of devices or
during reconfiguration of devices.
Notes:
When the maintenance mode of a device is switched on or off, a Trap will be sent
to the SNMP managers to notify them about this change.
The alarm trap generation (status changes, alarm changes...) during the time the
device is in maintenance mode is determined by the Trap Generation for
Maintenance Mode parameter. The procedure to change this parameter is
described in topic Switching On or Off Trap Generation for a Device in Maintenance
Mode on page 122.
Switching On or Off the Maintenance Mode

The following procedure explains how to switch on or off the maintenance function.
1 Open the ROSA EM System GUI and in the browser frame browse to the page of
the device for which the maintenance mode must be switched on or off.
2 Click on the Properties tab.
3 Click on the Value field of the Maintenance Mode parameter.
4005743 Rev N 121

Result: The Change Parameter Dialog of the Maintenance Mode parameter is

displayed.
4 Select Maintenance to enable the Maintenance Mode or Normal to disable this
mode.
Switching On or Off Trap Generation for Devices in Maintenance Mode

The following topic explains how to switch on or off alarm trap generation for
devices in maintenance mode.
2 Click on the Value field of the Trap Generation for Maintenance Mode
parameter.
Result: The Change Parameter Dialog for the Trap Generation for Maintenance
Mode parameter is displayed.
3 Select Enable or Disable and click on the Execute button.
122 4005743 Rev N

Using the Debug Mode
Using the Debug Mode

Introduction
WARNING:
The debug modes are for troubleshooting purposes only. Setting a parameter
to something other than Off causes the ROSA EM system to record messages
in logs.
Unless otherwise instructed by our personnel, you should leave all debug
modes in the default setting, i.e. Off.
To Enable or Disable a Debug Mode

Perform the following steps to enable or disable a debug mode.
2 Select the Debug tab.
Result: The Debug tab page is displayed.
3 Click on the Value field of a debug mode parameter.

Result: The Change Parameter Dialog of the debug mode in question is
displayed.
Note: The Hardware Debug Mode is for internal use only.
4 Select the desired setting and press the Execute button to confirm or the Cancel
4005743 Rev N 123

Configuring Second NIC and Routing

Introduction
The ROSA EM device is equipped with two Network Interface Cards (NICs). To see
the number of detected NICs, check the Number Of NICs parameter on the System
tab page of the ROSA EM GUI.
One NIC is used to configure the IP address of the ROSA EM device. The second
NIC can be configured to redirect traffic sent to a specific subnet to another gateway.
Some restrictions apply:
The IP address of the second NIC should not be in the same subnet as the IP
address of the first NIC.
The routing will be applied on the NIC in the same subnet as the specified
gateway.
When 2 NICs are detected, the ROSA EM GUI shows two extra tab pages:
Second NIC: Allows specifying the IP address and subnet of the second NIC.
Routing: Allows specifying the routing of the traffic to the other gateway.
Tip: For High Reliability purposes the second NIC can participates into ROSA EM's
NIC Teaming feature. More information about this feature can be found in topic
Configuring NIC Teaming for High Reliability on page 131.
124 4005743 Rev N

Second NIC
The following second NIC parameters can be viewed and/or changed:
Second NIC Current IP Address: Shows the current IP address on the second
NIC.
Second NIC Current Subnet Mask: Shows the current subnet mask on the
second NIC.
Second NIC IP Address: Used to enter the new IP address of the second NIC.
Second NIC Subnet Mask: Used to enter the new subnet mask of the second
NIC.
Second NIC Apply Changes: Needed to apply the new second NIC settings.
Note: These parameters are only applicable when the Second NIC Usage parameter
is set to Dedicated Subnet (default value).
To change the second NIC settings, follow the steps below.
1 Open the ROSA EM GUI, in the browser frame click on the ROSA EM device (the
top node of the device tree) and select the SecondNIC tab.
Result: The SecondNIC tab page is displayed.
Notes:
The actual second NIC settings are displayed at Second NIC Current IP
Address and Second NIC Current Subnet Mask.
At the first startup of the device all parameter values will be empty.
2 Click on the Value field of the Second NIC IP Address parameter.
Result: The Change Parameter Dialog appears.
3 Enter the new second NIC IP address and click on the Execute button.
4 Click on the Value field of the Second NIC Subnet Mask parameter.
Result: The Change Parameter Dialog appears again.
5 Enter the new second NIC subnet mask and click on the Execute button.
6 Click on the Value field of the Second NIC Apply Changes parameter.
4005743 Rev N 125

7 Select Apply and click on the Execute button.

Result: The new second NIC IP address and subnet mask will be applied
together.
Note: A warning is added to the Software Log when:
An invalid IP address is entered or when the IP address belongs to the same
subnet as the IP address of the first NIC.
An invalid subnet mask is entered.
Routing
The following routing parameters can be viewed and/or changed:
Note: For some parameters an example is given with respect to the Prisma DT
configuration used in next sub topic Example.
Currently Routed Subnet: Shows the currently routed subnet.
Example: The Prisma DT subnet.
Currently Routed Subnet Mask: Shows the subnet mask of the currently routed
subnet.
Example: The subnet mask of the Prisma DT subnet.
Currently Overhead Gateway: Shows the current overhead gateway.
Example: The Prisma DT, which acts as the overhead gateway towards the DT
subnet.
New Routed Subnet: Used to enter the new routed subnet.
New Routed Subnet Mask: Used to enter the new routed subnet mask.
New Overhead Gateway: Used to enter the new overhead gateway.
New Route Apply Changes: Needed to apply the new routing settings.
Follow the next steps to change the routing settings.
top node of the device tree) and select the Routing tab.
Result: The Routing tab page is displayed.
126 4005743 Rev N

Notes:
The actual routing settings are displayed at Currently Routed Subnet,
Currently Routed Subnet Mask and Current Overhead Gateway.
At the first startup of the device all parameter values will be empty.
2 Click on the Value field of the New Routed Subnet parameter.
3 Enter the new routed subnet and click on the Execute button.
4 Click on the Value field of the New Routed Subnet Mask parameter.
5 Enter the new routed subnet mask and click on the Execute button.
6 Click on the Value field of the New Overhead Gateway parameter.
7 Enter the new overload gateway and click on the Execute button.
8 Click on the Value field of the New Route Apply Changes parameter.
9 Select Apply and click on the Execute button.
Result: The new routing settings will be applied together.
Note: When invalid data is entered or when the new overhead gateway is not on the
same subnet as the NIC, a warning is added to the Software Log.
4005743 Rev N 127

Topology Example
NIC 1 NIC 2
IP Address IP Address
200.200.200.254 100.100.100.100
Def Gateway Route Added
IP Address
200.200.200.1 For 100.100.101.*
100.100.101.1
Subnet Mask use 100.100.100.1 IP Address
255.255.255.0 as gateway 100.100.100.1
Subnet Mask
Overhead Gateway Prisma DT
255.255.255.0
ROSA EM Prisma DT
Co-located
DT Overhead Channel
Customer LAN
Subnet: 200.200.200.0 Subnet: 100.100.101.0
Subnet Mask: 255.255.255.0 Subnet Mask: 255.255.255.0 Prisma DT
Prisma DT
ROSA
Client IP Address
100.100.101.2
IP Address
100.100.101.3
IP Address
200.200.200.2
The illustration above shows a setup of a Prisma DT configuration.

NIC 1 is used for the IP configuration of the ROSA EM device.
NIC 2 is defined via the Second NIC tab page of the GUI.
Routing information is defined via the Routing tab page of the GUI and added to
the NIC, which lies in the same subnet as the overhead gateway.
Prisma DT with IP address 100.100.100.1 acts as overhead gateway towards
the 100.100.101.0 subnet.
NIC 2 also uses subnet 100.100.100.0 so routing information is added to NIC
2 and not to NIC 1.
The other Prisma DT equipment uses subnet 100.100.101.0 (DT overhead
channel).
Note: When both NICs use a subnet different from the overhead gateway subnet, no
routing is added.
Application Example: Prisma DT Automatic Rerouting

Introduction
A Prisma DT chassis and its cards are controlled by a CCU, which must be placed in
slot 0 or 1 in the DT chassis. It is possible to have two CCU's in the chassis; one in
slot 0 (designated as CCU0) and one in slot 1 (CCU1). Only one CCU is controlling
the chassis and its cards at a time. Each CCU has its own IP address. Consider the
case where the Prisma DT chassis, which acts as the overhead gateway, in the
topology example above has two CCU's; one at IP 100.100.100.1 and one at
100.100.100.2. The overhead gateway is used to access the Prisma DT subnet
128 4005743 Rev N

100.100.101.0.
ROSA EM has the ability to dynamically switch the route on the applicable NIC on
ROSA EM in case one of the CCU's becomes not responding. If CCU0 is controlling
the chassis, then the route on the applicable NIC (second NIC in the example) must
be For 100.100.101.0 use 100.100.100.1 as gateway. If CCU0 becomes not responding,
ROSA EM will take the decision to alter route into For 100.100.101.0 use 100.100.100.2
as gateway.
Configuration
In order to make this work some preliminary configuration needs to be done as
described in the following steps.
1 Each Prisma DT chassis and its cards must be placed in a separate group in
ROSA EM.
2 Open the Configuration tab page of the CCU, which is controlling the chassis.
3 Click on the Value field of the Designated as Overhead Gateway parameter and
select Yes.
4 Fill in the values for the Prisma DT subnet.
Network Destination is the subnet address of the Prisma DT subnet, which
is to be reached through the overhead gateway.
Network Mask is the subnet mask of this subnet.
Network Interface is the IP address of the CCU, which is to be used to access
the Prisma DT subnet.
Operation
Now, if CCU0 becomes not responding and the CPU Service state of CCU1 is Active,
ROSA EM will automatically copy the values of Network Destination, Network
Mask, and Network Interface and will apply them to CCU1. CCU1 will also
automatically get the value of Yes for the parameter Designated as Overhead
Gateway. The route on the appropriate NIC will also be adapted automatically.
Result: The Prisma DT subnet will still be reachable if CCU0 becomes not
responding, without the need to manually change routes! This also works the other
way around, i.e. CCU1 becomes not responding and CCU0 is responding and its
CPU Service State is Active: CCU0 will take over control and the route will be
changed again.
4005743 Rev N 129

Note: CPU Service State can be found on the Status tab page.
130 4005743 Rev N

Configuring NIC Teaming for High Reliability
Configuring NIC Teaming for High Reliability

Introduction
The NIC Teaming feature can be used for High Reliability purposes. When NIC
Teaming is enabled, both NICs shares the same network parameters like IP address,
subnet mask, gateway..., but only one is active. When a failure (link down) is
detected on the active NIC, the ROSA EM system switches over to the other NIC and
sends a gratuitous ARP notifying the network of this change.
Configuring NIC Teaming

The following procedure explains how to configure ROSA EM's NIC Teaming
feature.
2 Click on the Value field of the Second NIC Usage parameter.
Result: The Change Parameter dialog of the Second NIC Usage parameter is
displayed.
3 Point to Teaming and click on the Execute button to confirm.
Result: The Second NIC tab is populated with the NIC Teaming parameters.
Tip: The Active NIC parameter shows the current active NIC.
4 Click on the Value field of the Switch Over Method parameter.
Result: The Change Parameter dialog of the Switch Over Method parameter is
displayed.
5 Point to one of the following values:
Manual: only an operator can switch over the device from one NIC to
another.
As this switchover cannot be triggered anymore once the management
interface of ROSA EM is disconnected or down, it is important to switch over
before disconnecting the currently active interface.
4005743 Rev N 131

Automatic To Secondary: Besides manual switchover, also automatic

switchover to the secondary NIC is enabled in case a link down is detected
on the primary (active) interface.
Automatic switching back to the first NIC is disabled in this mode; but
manual switchover is possible in both directions.
Automatic Both Ways (Default): Besides manual switchover the automatic
switchover is enabled in both directions. If either active NIC is failing, a
switch over to the other one is executed. If the other NIC would be down
too, then this switchover will occur perpetually, until one of the links is
detected up again.
6 Press the Execute button to confirm.
7 Click on the Value field of the Automatic Switch Over Delay parameter.
Result: The Change Parameter dialog of the Automatic Switch Over Delay
8 Enter the minimum duration a failure must be active before a switch over is
executed. When a link down is detected and the link comes up again within that
time, a switch over will not be executed.
9 Press the Execute button to confirm.
Performing a Manual NIC Switch Over

The following procedure describes how to trigger a manual NIC switch over.
2 Click on the Value field of the Switch Over Command parameter.
Result: The Change Parameter dialog of the Switch Over Command parameter
is displayed.
3 Point to SwitchNow and click on the Execute button.
132 4005743 Rev N

Configuring IPsec
Configuring IPsec
Introducing IP Security
General
IP security (IPsec) ensures secure communication by providing authentication and
encryption mechanisms for network traffic between two peers. This communication
can be:
Between ROSA EM and ROSA NMS
Between ROSA EM and the computer running the web browser user interface of
the ROSA EM.
Between ROSA EM and a Digital Content Manager (DCM) managed by the
ROSA EM
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.
Note: When the communication between two peers must be secured by using IPsec,
IPsec must be configured for both peers. This topic covers the IPsec configuration of
the ROSA EM. The procedures to setup IPsec for a computer running Windows
(Copernicus NMS or computer running the web browser user interface of the ROSA
EM) can be found in topic Internet Protocol Security on page 336. The procedure to
setup IPsec for a DCM can be found in the Digital Content Manager (DCM)
Configuration Guide.
Key Exchange
To establish an IPsec session, the peers need to exchange encryption keys in a secure
way. ROSA EM uses Internet Key Exchange (IKE) for this purpose. IKE is
configured to use preshared keys that can be set by the user. IKE will use 3DES
encryption and MD5/SHA1 hashing.
IPsec Packets
After a key is exchanged, the peers negotiate the structure of the IP packets. IPsec
modifies IP packets between the two peers by adding optional headers and
encrypting the data. Potentially, two headers can be used for this purpose: the
Authentication Header (AH) and the Encapsulated Security Payload Header (ESP).
To meet current requirements, however, ROSA EM uses only ESP; AH is not used.
4005743 Rev N 133

When using ESP, two options ensure data integrity: the encryption algorithm (for
instance 3DES) and the hashing algorithm (for instance MD5). ROSA EM is
configured to accept a number of ESP proposals, that is, a number of combinations
of encryption and hashing algorithms. Any combination of the following encryption
protocols with the MD5 and SHA1 authentication protocol is accepted: AES 256, AES
128, 3DES, and NULL.
Security Levels
ROSA EM allows three security levels:
All IP traffic is allowed, unsecured IP and IPsec.
Only unsecured IP traffic between ROSA EM and its managed devices is
allowed. All other IP communication must be IPsec communication.
All IP communication must be IPsec communication.
These security levels can be configured for both the Management Port and second
NIC.
Setting the Security Level

The following procedure describes how to set the security level for the Management
Port or second NIC.
2 Select the IPSec tab.
Result: The IPSec tab page is displayed.
3 Click on the Value field of the Non-IPSec Traffic Management Port or Non-
IPSec Traffic Second NIC parameter.
Result: The Change Parameter Dialog of the selected parameter is displayed.
134 4005743 Rev N

Configuring IPsec
4 Select one of the following settings:

EnableAll: all IP traffic is allowed, unsecured IP and IPsec.
EnableManaged: only unsecured IP traffic between ROSA EM and its managed
devices is allowed. All other IP communication must be IPsec
communication.
Disabled: all IP communication must be IPsec communication.
Adding or Removing Clients to or from the IPsec Peers List

Perform the following steps to add a Copernicus NMS or computer running the web
browser user interface to the IPsec peers list of a ROSA EM.
2 Select the IPSec tab.
3 Click on the Value field of an IPSec Client IP-Address XX parameter.

4 Enter the IP address of the peer in the Change Parameter Dialog and press the
Execute button.
5 Click on Value field of the corresponding IPSec Pre-Shared Key XX parameter.
6 Enter the pre-shared key for the corresponding IPsec communication in the
Change Parameter Dialog and press the Execute button.
7 Repeat step 3 up to 6 for all clients that must be added to the IPsec peers list.
8 Click on the Value field of the Apply All Client IPSec Settings parameter.
4005743 Rev N 135


9 Select Execute in the Change Parameter Dialog and press the Execute button to
confirm or the Cancel button to abort the operation.
Note: Maximum 30 clients can be added to the IPsec peers list of a ROSA EM.
Adding or Removing a DCM to or from the IPsec Peers List

The following procedure explains how to add a DCM to the IPsec peers list of ROSA
EM.
1 Open the ROSA EM GUI, in the browser frame browse to the DCM that must be
added to ROSA EM's IPsec peers list, and click on the IPSec tab.
2 Click on the Value field of the Pre-Shared parameter.

3 Enter the key in the Change Parameter Dialog of the Pre-Shared parameter and
press the Execute button to confirm.
Notes:
Be sure to make a note of this string, as it must exactly match the preshared key
entered in the corresponding DCM.
Removing a DCM from the IPsec peers list can be done by clearing the Pre-
Shared Key parameter of the corresponding DCM.
Bypassing IPsec by using the Craft Interface

When the ROSA EM becomes inaccessible due to wrong IPsec peer entries in the
IPsec peers list, the IP security can be bypassed by using the Craft Interface on the
front of the ROSA EM. The procedure to start up the Craft Interface is described in
topic Setting IP Address Using the CLI Based IP Configuration Tool Via Craft
Interface.
1 Bypass IPsec by entering the following instruction at the command prompt and
press [Enter].
> activate ipsec bypass
Notes:
A major alarm is generated when IPsec is bypassed.
IPsec bypassing can be deactivated by entering the following instruction at the
136 4005743 Rev N

Configuring IPsec
command prompt and press [Enter].

> deactivate ipsec bypass
Activating the IPsec bypass makes it possible for every client to communicate
with the ROSA EM and not only the configured IPSec clients.
list, get ip and set ip cannot be used when IPsec communication is active on the
ROSA EM.
4005743 Rev N 137

4 Chapter 4
Configuring the Input/Output
Functionality
Introduction
This chapter covers the Input / Output functionality of the ROSA
EM device. This section contains a description about this functionality
and the procedures to configure the different inputs and outputs.
In This Chapter
General ................................................................................................. 140
Configuring the Digital Outputs ...................................................... 144
Configuring the Digital Inputs ......................................................... 148
Configuring the Analog Inputs......................................................... 152
Configuring the Analog Outputs ..................................................... 156
Configuring the Temperature Probes .............................................. 158
Virtual Protocol and Proxy Devices ................................................. 161
4005743 Rev N 139

Chapter 4 Configuring the Input/Output Functionality
General
Introduction
The Input/Output (I/O) functionality of the ROSA Element Manager (EM) system
acts as a separate device within the ROSA EM device. This part of the ROSA EM
device is provided with 24 relays and each relay has three contacts, a normal closed
contact (Nc), a normal open contact (No), and a common contact (Com).
NC NO
COM
The normal closed contact is the contact that is connected with the common contact
in case the unit is not powered. The common contact of each relay can be connected
to GND, +5V, and +12V or can be floated (default) by changing jumpers. Further in
this section, the relay contacts are indicated with Digital Outputs. More information
about this jumper setting can be found in the ROSA Element Manager Installation and
Operation Guide.
Next to these relay contacts the ROSA EM device is equipped with 108 digital input
ports and 12 galvanically isolated digital inputs. The ROSA EM device contains 2
analog outputs. These outputs can be set between 0 and 10 V in steps of 40 mV. The
I/O part of the ROSA EM device is also provided with 8 analog inputs. The voltage
range of each analog input can be set either 15 V or 60 V by changing jumpers. More
information concerning these jumper settings can also be found in the ROSA Element
Manager Installation and Operation Guide. The resolution of an analog input is 250 mV
with 60 V input range and 55 mV with 15 V input range and is rounded up to a
precision of 0.1 V.
The I/O part is also equipped with two temperature probe input connectors, which
can be used in combination with our temperatures probes.
The pinout configuration of the rear panel connectors of the inputs and outputs can
also be found in the ROSA Element Manager Installation and Operation Guide.
Viewing Device Properties

The properties and the status of the I/O part of the ROSA EM device can be found
on the Properties tab of the rosaemio (io) page. The following procedure explains
how to view the device parameters.
1 Open the ROSA EM GUI, in the browser frame browse to the rosaemio (io) page
and click on the Properties tab.
140 4005743 Rev N

General
The following parameters can be checked:

Name: read-only parameter and represents the device type.
Graphic
Symbol
Poll Counter: read-only parameter and represent the number of executed
polling cycles since power up.
Script: name of the script to perform a particular action. More information
about scripts can be found in chapter Scripting in ROSA EM on page 281.
Comm Alarm Threshold: a read-write parameter and contains the number of
times the communication fails before an alarm is generated.
Comm Quality: a read-only parameter that gives an indication of the
communication line quality. For the I/O functionality, this parameter must
always to be 100%.
DevType Revision: read-only parameter and contains the revision of the
device type of the I/O part of the ROSA EM device.
Generic name: read-only parameter and contains the name of the device.
Changing the Identification Settings of the I/O Functionality

To facilitate the identification and location of the I/O functionality of the ROSA EM
device in a network, identification parameters can be entered. The following steps
explain how to set these identification parameters.
page and click on the Properties tab.
4005743 Rev N 141


Result: The Change Parameter Dialog of the parameter in question is displayed.
The following identification parameters can be entered:
Service Name: represents the name of the service associated with this device.
Device Location: represents the location of the device.
Description: this parameter contains a description of the device.
Alias
Viewing the Inputs and Outputs Parameters

The following steps explain how to check the inputs and outputs parameters.
page and click on the Inputs_Outputs tab.
Result: The Inputs_Outputs tab page is displayed.
142 4005743 Rev N

General
The following parameters can be checked.

Number of Galv Isol DI: represents the number of galvanically isolated
digital inputs (12).
Number of Non Galv Isol DI: contains the number of non-galvanically
isolated digital inputs (108).
Number of Digital Outputs: contains the number of digital outputs (relay
contacts, 24).
Number of Analog Inputs: represents the number of analog inputs including
the number of temperature sensor inputs (8 + 2).
Number of Analog Outputs: contains the number of analog outputs (2).
Number of Temp Sensors: contains the number of configured temperature
sensors (0, 1, or 2).
4005743 Rev N 143

Configuring the Digital Outputs

Introduction
The ROSA EM device is equipped with 24 relay contacts (named digital outputs).
The parameters of these digital outputs can be found on the Digital_Outputs tab of
the rosaemio (IO) page. The following lists the digital output parameters:
Parameter: a read-only parameter and contains the type and number of the
output
State: a read-write parameter that contains the state of the digital output. The
representation of this parameter depends on the Low State Name and High
State Name parameter.
Location: a read-only parameter that represents the location of the digital output
on the rear panel of the device.
Name: a read-write parameter useful to facilitate the identification of the digital
input in the application.
Trap On Change: a read-write parameter and switch on or off Trap generation
after a status transition. This feature is only used in combination with the UDD
functionality within ROSA NMS. When the digital output is not used by UDD,
this parameter should be set to no.
Low State Name: a read-write parameter that names the low state of the digital
output, for instance switched off. A name of maximum 20 characters can be given.
High State Name: a read-write parameter that names the high state of the digital
output, for instance switched on. A name of maximum 20 characters can be given.
ROSA EM devices with software version 3.02.20 or higher provides a generic device
script that allows to expose the state of an alarm via one of its digital outputs. More
information concerning this feature can be found in topic Device Alarm Propagation
via Digital Outputs on page 146.
Configuring a Digital Output

The following example describes how to configure a digital output to switch on or
off an additional air-conditioning system in a CATV headend.
Example: Digital output 5 is used to switch on or off an additional air-conditioning
system in the headend.
1 Open the ROSA EM GUI, in the browser frame browse to the rosaemio (io) page,
and click on the Digital_Outputs tab.
Result: The Digital_Outputs tab page is displayed.
144 4005743 Rev N

2 Click on the Name cell of the digital output 5.

3 Enter Additional air-condition system in the Change Parameter Dialog of the
Name parameter and press the Execute button.
4 Click on the Low State Name cell of the digital output 5.
5 Enter Switched off in the Change Parameter Dialog of the Low State Name
6 Click on the High State Name cell of the digital output 5.
7 Enter Switched on in the Change Parameter Dialog of the High State Name
8 Click on the State cell of the digital output 5.
9 In the Change Parameter Dialog of the State parameter, select Switched On and
press the Execute button.
Result: The additional air-conditioning system is switched on.
4005743 Rev N 145

Device Alarm Propagation via Digital Outputs

Introduction
The indication of a device in alarm state can be propagated further by changing the
state of a digital output, meaning the state of a digital output can be modified if a
particular device alarm arises.
Configuring this propagation feature should be done in two steps. First the
alarm2io.py script must be assigned to the device for which the alarm state must be
propagated and secondly the digital output must be renamed using the following
syntax:
A2O_<device name>_<device alarm>
With:
<device name>: the name of the device for which the alarm must be propagated
via a digital output
<device alarm>: the name of corresponding alarm as shown in the Parameter field
on the Alarms tab of the device. Instead of given the full alarm name, the short
name of the alarm can be used. A short name consists of the first three characters
of each word in the parameter name without blanks. For example the short
name of the Link Loss GBE Port 1 parameter is linlosgbepor1.
Hint: For a word consisting of one or two characters, use the complete word.
Notes:
The name of a digital output is limited to 40 characters.
Both device name and device alarm are not case sensitive.
This alarm propagation functionality is available on ROSA EM devices with
software version 3.02.20 or higher.
Assigning the Script to the Device

The following steps explain how to assign the alarm2io.py to a device.
1 Open the ROSA EM GUI and in the browser frame, browse to the page of the
device and click on the Properties tab.
146 4005743 Rev N

2 Point to the Value field of the Script parameter.

3 Enter alarm2io.py in this dialog and press the Execute button.
Result: The script appears in the Value field of the Script parameter.
Renaming the Digital Output for Alarm Propagation

The following procedure describes how to change the name of a digital output for
alarm propagation.
1 Open the ROSA EM GUI and in the browser frame, browse to the rosaemio (IO)
page and click on the Digital_Output tab.
Result: The Digital_Output tab page is displayed.
2 Click on the Name field of the corresponding digital output.
3 Enter the correct name in this dialog and point to the Execute button.
Result: The name appears in the Parameter and Name field.
4 Configure the other digital output parameters as described in topic Configuring a
Digital Output on page 144.
4005743 Rev N 147

Configuring the Digital Inputs

Introduction
The ROSA EM device is provided with 108 digital inputs and 12 galvanically
isolated digital inputs. The configuration parameters of these inputs can be found
on the Digital Input tab of the rosaemio (IO) page. The pinout configuration of the
rear panel connectors of the digital inputs can be found in the ROSA Element
Manager Installation and Operation Guide. The following list shows the digital input
parameters:
Parameter: a read-only parameter that contains the type and number of the
input.
State: a read-only parameter that contains the actual state of the digital input.
The representation of this parameter depends on the Low State Name and High
State Name parameter.
Status: a read-only parameter that represents the severity level that corresponds
with the actual state of the digital input: Normal, Minor, Major, or Critical.
Note: With a right-click on the Status parameter of a digital input, you can select
Alarm Profile and specify the alarm Delay time and the Notifiy Set A or B
parameter for the selected digital input.
Location: a read-only parameter that represents the location of the digital input
148 4005743 Rev N

Alarm State: a read-write parameter that contains the input state to which the
input has to be switched for alarm generation. The representation of this
parameter depends on the Low State Name and High State Name parameter.
Alarm Enable: a read-write parameter that enables or disables the alarm
generation function.
Alarm Severity: a read-write parameter that determines the severity level of the
alarm: Minor, Major, or Critical.
Name: a read-write parameter useful to facilitate the identification of the digital
Trap On Change: a read-write parameter that switches on or off Trap generation
after a status transition. This feature is only used in combination with the UDD
functionality within ROSA NMS. When the digital input is not used by UDD,
this parameter should be set to on.
Debounce Time: a read-write parameter that contains the debounce time for a
digital input. The default debounce time is set to 0 and you can specify a time
from 0 to 10 seconds. This debounce time indicates the time that a digital input
state has to be stable before ROSA EM will accept the new state: it is introduced
to avoid glitches (short state changes due to disturbances).
Note: Any other component of ROSA EM (for instance alarm delay, UDD using a
digital input of ROSA EM, Trap on Change...) will not see the state change until
it is considered stable and accepted by ROSA EM, for example after the
debounce time.
Example: The alarm delay that can be specified for an alarm will start counting
from the moment when a state is considered stable by ROSA EM.
Low State Name: a read-write parameter that names the low state of the digital
input, for instance Open. A name of maximum 20 characters can be given.
High State Name: a read-write parameter that names the high state of the digital
input, for instance Closed. A name of maximum 20 characters can be given.
Configuring a Digital Input

The following example describes how to configure a digital input to guard the access
door of the CATV headend.
Example: Digital input 14 guards the access door of the headend. When the door
opens (the input becomes low), an alarm with major severity has to be generated.
Perform the following steps to configure a digital input as described in the example.
4005743 Rev N 149

and click on the Digital_Inputs tab.
Result: The Digital_Inputs tab page is displayed.
2 Click on the Name cell of digital input 14.

3 Enter Front door in the Change Parameter Dialog of the Name parameter and
4 Click on the Alarm State cell of digital input 14.
5 In the Change Parameter Dialog of the Alarm State parameter, select Low and
Result: An alarm is generated when the input becomes low.
6 Click on the Alarms Enable cell of digital input 14.
7 Select Enabled in the Change Parameter Dialog of the Alarms Enable parameter
and press the Execute button to confirm.
Result: The alarm detection function of digital input 14 is switched on.
8 Click on the Alarm Severity cell of digital input 14.
9 In the Change Parameter Dialog of the Alarm Severity parameter, select Major
Result: The severity level of the generated alarm is major.
10 Click on the Low State Name cell of digital input 14.
11 In the Change Parameter Dialog of the Low State Name parameter, enter closed
12 Click on the High State Name cell of digital input 14.
150 4005743 Rev N

13 In the Change Parameter Dialog of the High State Name parameter, enter open
4005743 Rev N 151

Configuring the Analog Inputs

Introduction
The ROSA EM device is provided with 8 analog inputs. The input voltage range of
each analog input can be set either to 15 V or to 60 V. More information concerning
the input voltage range selection can be found in the ROSA Element Manager
Installation and Operation Guide.
Note: The ROSA EM device is not able to detect which input voltage range is
selected. When the input voltage selection for a particular analog input is changed,
the operator has to inform the ROSA EM System that an input voltage selection
change is done.
To facilitate the read-out of some parameters, ROSA EM allows scaling of the polled
value. Entering a value for scaling and an offset performs this scaling. The unit of
the scaling values can also be changed. The following formula is used:
SV = Scaling * MV + Offset
Where MV is the measured (or polled) value and SV is the scaling value.
The measuring area of an analog input can be divided in 5 zones: the major high
alarm zone, the minor high alarm zone, the normal zone, the minor low alarm zone,
and the major low alarm zone. When the value exceeds a threshold, a related alarm
is generated.
Since values, which vary around a threshold borderline, can cause intermittent
alarms, the alarm zones are foreseen of a hysteresis. The hysteresis is taken in
account when the signal varies from a higher alarm zone towards a lower zone. The
value is considered to belong to a less critical alarm zone when the value varies an
amount (equal to the hysteresis) to the normal zone, counting from the current alarm
zone threshold. The analog input parameters are:
152 4005743 Rev N

input.
Value: a read-only parameter. This parameter is determined by the measured
value and the scaling factor, the unit by the value entered in the unit parameter.
Alarm Status: a read-only parameter and represents the severity level that
corresponds with the actual state of the analog input: Normal, Minor, Major, or
Critical.
Unit: is a read-write parameter and represents the unit of the Value parameter.
This parameter can be used to facilitate the read out of some parameters.
Location/ID: a read-only parameter that represents the location of the analog
input on the rear panel of the device.
Alarm Enable: a read-write parameter that enables or disables the alarm
generation function.
Major Low: a read-write parameter that contains the major low threshold. Note
that the scaling should be taken into account to determine this parameter.
Minor Low: a read-write parameter that contains the minor low threshold. Note
that the scaling should be taken into account to determine this parameter.
Minor High: a read-write parameter that contains the minor high threshold.
Note that the scaling should be taken into account to determine this parameter.
Major High: a read-write parameter that contains the major high threshold.
Note that the scaling should be taken into account to determine this parameter.
Deadband: is a read-write parameter and contains the hysteresis used to
determine alarms. Note that the scaling should be taken into account to
determine this parameter.
Scaling factor: a read-write parameter that determines the scaling.
Offset: a read-write parameter that determines the offset of the measured value.
Range: a read-write parameter and contains the input voltage range of the
analog input.
Name: a read-write parameter useful to facilitate the identification of an analog
after alarm zone transition. This feature is only used in combination with the
UDD functionality within ROSA NMS. When the digital output is not used by
UDD, this parameter should be set to no.
4005743 Rev N 153

To Configure an Analog Input

The following example describes how to configure an analog input to monitor the
temperature of a third party device.
Example: A third party device is provided with an analog output, which generates a
signal in function of the device temperature, 0V corresponds with a temperature of
minus 20 C and 10 V with 80C. This analog signal is connected to analog input 7 of
the ROSA EM device. When the temperature of the device exceeds 55C, a minor
high alarm should be generated and when the temperature exceeds 65C a major
high alarms. When the device temperature becomes to low (5C) a major alarm have
to be generated. To prevent intermittent alarms, a hysteresis of 5C can be used.
and click on the Analog_Inputs tab.
Result: The Analog_Inputs tab page is displayed.
2 Click on the Name cell of analog input 7.

3 Enter Temperature third party device in the Change Parameter Dialog of the Name
parameter and press the Execute button to confirm.
4 Click on the Unit cell of analog input 7.
5 Enter Deg_C in the Change Parameter Dialog of the Unit parameter and press
the Execute button to confirm.
6 Click on the Scaling cell of analog input 7.
7 Enter 10 (1V corresponds with 10C) in the Change Parameter Dialog of the
Scaling parameter and press the Execute button to confirm.
8 Click on the Offset cell of analog input 7.
9 Enter -20 (0V corresponds with 20C) in the Change Parameter Dialog of the
Offset parameter and press the Execute button to confirm.
10 Click on the Range cell of analog input 7.
11 Select 15V in the Change Parameter Dialog of the Range parameter and press
12 Click on the Major Low cell of analog input 7.
13 Enter 5 (5C) in the Change Parameter Dialog of the Major Low parameter and
154 4005743 Rev N

14 Click on the Minor High cell of analog input 7.

15 Enter 55 (55C) in the Change Parameter Dialog of the Minor High parameter
16 Click on the Major High cell of analog input 7.
17 Enter 65 (65C) in the Change Parameter Dialog of the Major High parameter
18 Click on the Deadband cell of analog input 7.
19 Enter 5 (5C hysteresis) in the Change Parameter Dialog of the Deadband
20 Click on the Alarm Enable cell of analog input 7.
21 Select Enabled in the Change Parameter Dialog of the Alarm Enable parameter
Result: Analog input 7 is configured.
4005743 Rev N 155

Configuring the Analog Outputs

Introduction
The ROSA EM device is equipped with two analog outputs. These outputs can be
set between 0 and 10 V in steps of 40 mV. To facilitate the read-out of the value,
ROSA EM allows scaling this value. Entering a scaling factor and an offset performs
this scaling. The unit of the scaling values can also be changed. The following lists
the analog input parameters
input.
Value: a read-write parameter. This parameter is determined by the measured
value and the scaling factor, the unit by the value entered in the unit parameter.
Unit: is a read-write parameter and represent the unit of the Value parameter.
This parameter can be used to facilitate the read out of some parameters.
Location: a read-only parameter that represents the location of the analog input
Scaling: a read-write parameter that determines the scaling.
Offset: a read-write parameter that should be added to the scaling.
Name: a read-write parameter useful to facilitate the identification of an analog
output in the application.
after a value modification. This feature is only used in combination with the
UDD functionality within ROSA NMS. When the digital output is not used by
UDD, this parameter should be set to no.
To Configure an Analog Output

The following example describes how to configure an analog output to set the RF
output level of a third party device.
Example: The level of an output signal of a third party device can be set between 40
and 55 dBmV using an analog input signal. 40 dBmV corresponds with 0 V and 55
dBmV with 10 V. This analog input is connected to the ROSA EM device via analog
output 2.
and click on the Analog_Outputs tab.
Result: The Analog_Outputs tab page is displayed.
156 4005743 Rev N

Configuring the Analog Outputs
2 Click on the Name cell of analog output 2.

3 Enter Output level third party device in the Change Parameter Dialog of the Name
4 Click on the Unit cell of analog output 2.
5 Enter dBmV in the Change Parameter Dialog of the Unit parameter and press
6 Click on the Scaling cell of analog output 2.
7 Enter 1.5 (1.5 dBmV corresponds with 1 V) in the Change Parameter Dialog of
the Scaling parameter and press the Execute button to confirm.
8 Click on the Offset cell of analog output 2.
9 Enter 40 (40 dBmV corresponds with 0V) in the Change Parameter Dialog of the
Offset parameter and press the Execute button to confirm.
10 Click on the Value cell of analog output 2.
11 Enter for example 51 (51 dBmV) in the Change Parameter Dialog of the Value
Result: The analog output is configured.
4005743 Rev N 157

Configuring the Temperature Probes

Introduction
The ROSA EM device is equipped with two temperature probe input connectors,
which can be used in combination with our probes (part number 4005382).
The measuring temperature area can be divided in 5 zones: the major high alarm
zone, the minor high alarm zone, the normal zone, the minor low alarm zone, and
the major low alarm zone. When the temperature exceeds a threshold, a related
alarm is generated.
Since the temperature, which varies around a threshold borderline, can cause
intermittent alarms, the alarm zones are foreseen of a hysteresis. The hysteresis is
taken in account when the temperature varies from a higher alarm zone towards a
lower zone. The temperature is considered to belong to a less critical alarm zone
when the temperature varies an amount (equal to the hysteresis) to the normal zone,
counting from the current alarm zone threshold.
The configuration of a temperature probe can be divided in two steps:
Identifying the temperature probe
Configuring the temperature probe parameters
The procedures to configure the temperature probe are described using the
following example.
Example: The ambient temperature in a room of the headend must be monitored.
When the temperature in the room exceeds 82 Fahrenheit, a minor alarm must be
generated and when the temperature exceeds 89 Fahrenheit, a major alarm. A
minor alarm must be generated when the temperature becomes lower than 41
Fahrenheit, and a major alarm when the temperature becomes lower than 36
Fahrenheit.
158 4005743 Rev N

Configuring the Temperature Probes
To Identify the Temperature Probe

Perform the following procedure to configure a temperature probe.
1 Connect the temperature probe to temperature probe input connector 1 or 2.
and click on the Inputs_Outputs tab.
Result: The Inputs_Outputs tab is displayed.
3 Click on the Value field of the Scan Temperature Sensors parameter.
Result: The Change Parameter Dialog of the Scan Temperature Sensors
4 Select Scan and press the Execute button to confirm or the Cancel button to abort
the operation.
5 Right-click on the value of the Detected Temperature Sensor and in the shortcut
menu, select Copy To Clipboard.
6 Click on the Analog Inputs tab.
Result: The Analog Inputs tab is displayed.
7 Click on the Location/ID cell of a temperature sensor (for instance temperature
sensor 1).
Result: The Change Parameter Dialog of the Location/ID is displayed.
8 Press simultaneously the [Ctrl] key and the [V] key.
Result: The ID of the temperature probe is displayed.
Result: The temperature probe is identified.
4005743 Rev N 159

To Configure the Temperature Probe Parameters

The following steps explain how to configure the temperature probe parameters.
1 Select the Analog_Inputs tab.
Result: The Analog_Inputs tab page is displayed.
2 Select the Name parameter of temperature sensor 1.
3 Enter Room temperature in the Change Parameter Dialog of the Name parameter.
Press the Execute button to confirm the operation.
4 Select the Unit cell of temperature sensor 1.
5 Select F in the Change Parameter Dialog of the Cell parameter and click on the
Execute button to confirm.
6 Select the Major Low cell of temperature sensor 1.
7 Enter 36 in the Change Parameter Dialog of the Major Low parameter and press
8 Click on the Minor Low cell of temperature sensor 1.
9 Enter 41 in the Change Parameter Dialog of the Minor Low parameter and press
10 Click on the Minor High cell of temperature sensor 1.
11 Enter 82 in the Change Parameter Dialog of the Minor High parameter and
12 Click on the Major High cell of temperature sensor 1.
13 Enter 89 in the Change Parameter Dialog of the Major High parameter and
14 Click on the Deadband cell of temperature sensor 1.
15 Enter 1 in the Change Parameter Dialog of the Deadband parameter and press
16 Click on the Alarm Enable cell of temperature sensor 1.
17 Select Enabled in the Change Parameter Dialog of the Alarm Enable parameter
160 4005743 Rev N

Virtual Protocol and Proxy Devices

Introduction
The virtual protocol on ROSA EM allows creating devices that gather their
information not from a physical device but from another ROSA EM device type. In
almost all cases the device from which the virtual devices obtain their data are I/O
devices (ROSA EM I/O, Rymic...). Currently the virtual devices only provide in
support for digital inputs and outputs.
Notes:
For more information about ROSA EM device types and ROSA EM device list in
general, please read topic Adding devices and Groups on page 91.
The alternative for ROSA Network Management System (NMS) is the use of
UDD profiles that are generated with help of the UDD Profile Manager.
Device Type Categories

A number of virtual device types exist on ROSA EM. They can be divided in 2
categories:
Category 1
The first category allows exposing the state of one digital input as the alarm status of
the device. This type of device type (for instance proxy) is handy when monitoring
devices that expose one digital output to report the alarm state.
Example: proxydev, proxydevbu, proxydevbu2
Category 2
The second category allows exposing a consecutive set of digital inputs and outputs.
These are handy when monitoring a device with a digital I/O interface. The digital
inputs and outputs of the device should be connected to consecutive outputs and
inputs of an I/O device that is integrated into ROSA EM. Next the device type has
to be configured to obtain its information.
Example: rymicproxy, proxy
Configuration
Device List
When adding virtual devices to the device list (either by editing the device list or
online with a ROSA or TNCS client) you have to take the following into account:
These devices should always use the virtual port. In most cases, the port is
4005743 Rev N 161

already defined in the device type and can be omitted from the device list.
Each proxy device should have a unique address.
Category 1
The following procedure describes the configuration steps.
1 Open the ROSA EM GUI, in the browser frame click on the category 1 proxy
device and select the Configuration tab.
Result: The Configuration tab page is displayed.
2 Click on the Value field of the Status Source Device parameter.

3 Enter the name of the I/O device from which the status information has to be
queried and click on the Execute button.
4 Click on the Value field of the Status Source Point parameter.
5 Enter the point name or input number that has to be exposed as status for this
device.
Point name: When a non-numeric value is entered, the value is interpreted as
a point-name and the value of this point in the Status Source Device will be
queried upon polling.
Input number: When a numeric value is entered this is interpreted as the input
number that has to be polled.
Example: When using rosaemio as Status Source Device, value 13 would be
interpreted as the first non-galvanic isolated digital input for instance
Digital_Input_13 (default name).
6 Click on the Execute button to confirm the parameter.
7 Click on the Value field of the Alarm State Name(s) parameter.
8 Enter a list of values, which should make this device go into alarm and click on
the Execute button.
Note: The values in this list must be separated with a single space.
Example of Category 1
In rosaemio Digital_Input_14 is used as front door detector: the normal state is high
and no alarm is present.
162 4005743 Rev N

In the virtual proxy device, rosaemio is selected as source device. Digital input 14
will be polled to represent the status of the virtual proxy device and when the state
of the digital input is equal to Low an alarm must be generated.
The Device Status of the virtual proxy device is normal, since the state of the polled
digital input is High.
In rosaemio the state of digital input 14 changes to Low (for instance the front door is
opened) and a major alarm is generated.
The Device Status of the virtual proxy device is also in alarm because the state of the
polled digital input changed to Low.
Note: To change the alarm severity level of the virtual proxy device, right-click on
the Device Status line and a menu will appear: select the desired severity level.
Category 2
The following procedure describes the configuration steps.
1 Open the ROSA EM GUI, in the browser frame click on the category 2 proxy
device and select the Configuration tab.
Result: The Configuration tab page is displayed.
4005743 Rev N 163

2 Click on the Value field of the Source Device parameter.

3 Enter the name of the I/O device from which the status information has to be
queried and click on the Execute button.
4 Click on the Value field of the First Status Point parameter.
5 Enter the first input number that has to be polled and click on the Execute
button.
Example: When using rosaemio as Status Source Device, value 13 would be
interpreted as the first non-galvanic isolated digital input for instance
Digital_Input_13 (default name).
6 Click on the Value field of the Number of Status parameter.
7 Enter the number of consecutive digital inputs to expose via this virtual device,
starting from First Status Point, and click on the Execute button.
Note: If no digital inputs need to be exposed, just enter 0 (default value).
8 Click on the Value field of the First Control Point parameter.
9 Enter the first output number that has to be controlled and click on the Execute
button.
10 Click on the Value field of the Number of Controls parameter.
11 Enter the number of consecutive digital outputs to controlled via this virtual
device, starting from First Control Point, and click on the Execute button.
Note: If no digital outputs need to be controlled, just enter 0 (default value).
12 Click on the Value field of the Alarm State Name(s) parameter.
13 Enter a list of values, which should make this device go into alarm and click on
the Execute button.
Note: The values in this list must be separated with a single space.
164 4005743 Rev N

Example of Category 2
The device operation of this category is very similar to the operation of a category 1
device. The main differences are:
The states of the polled digital inputs are grouped in the Status tab page table.
The states of the controlled digital outputs are grouped in the Controls tab page
table.
4005743 Rev N 165

5 Chapter 5
Configuring the Apollo
Functionality
Introduction
This section covers the Apollo functionality of the ROSA EM system.
In This Chapter
Introduction ......................................................................................... 168
Setting Up Remote Sites ..................................................................... 172
Message Configuration ...................................................................... 176
Configuring an Apollo Site................................................................ 178
4005743 Rev N 167

Chapter 5 Configuring the Apollo Functionality
Introduction
General
The Apollo functionality of the ROSA EM device is a communication organizer
capable of transporting our Remote Control and Diagnostics System (RCDS)
protocol over TCP/IP networks. The Apollo functionality is used in conjunction
with the ROSA Network Management System (NMS).
The Apollo functionality supports all equipment that uses the RCDS serial
communication protocol (RS-232 or RS-485). Up to four COM ports of the ROSA EM
device can be configured to the RS-485 protocol and assigned to the Apollo
functionality and each COM port using the RS-485 protocol can be populated with
31 devices. For more information about how to configure COM ports to the RS-485
protocol, please refer to the ROSA Element Manager Installation and Operation Guide
that is shipped with your device.
Note:
For a ROSA EM device with Apollo software release lower than 1.1.0 and/or
ROSA EM software release lower than 3.1.0, only one COM port configured to
the RS-485 protocol can be assigned to the Apollo functionality.
Since a ROSA EM device isnt able to detect which RS-485 port(s) is(are) used by
the Apollo functionality, the operator must inform the ROSA EM system about
this assignment.
When multiple COM ports of a ROSA EM device are assigned to the Apollo
functionality, the ROSA NMS will handle the ROSA EM device as a single
Apollo site.
WARNING:
The RCDS device address of all devices connected to the ROSA EM

device have to be unique, independent to which port the devices are
connected.
When a port is used for Apollo, only RCDS devices can be connected to
this port.
The ROSA EM device continuously polls all devices connected to this(these) port(s)
to detect alarm conditions. The device also listens for configuration instructions or
status inquiries coming from ROSA NMS and relays these messages to the
appropriate device.
Assigning the COM Port to the Apollo Functionality

The following procedure explains how to assign one or more COM ports to the
Apollo functionality.
168 4005743 Rev N

Introduction
1 Open the ROSA EM GUI; in the browser frame click on the ROSA EM device
(top node of the device tree), and point to the Apollo configuration tab.
Result: The Apollo configuration tab page is displayed.
2 Click on the Value field of the Apollo communication ports parameter.

Result: The Change Parameter Dialog of the Apollo communication port
3 Enter the COM port(s) that should be assigned to the Apollo functionality.
When multiple COM ports must be entered, the COM ports must be separated
with interspacing.
4 Press the Execute button to confirm or the Cancel button to abort.
5 Restart the ROSA EM device as described in topic Restarting the ROSA EM Device
on page 116.
Enabling or Disabling Apollo Communication Ports

Ports assigned to the Apollo functionality can be enabled or disabled. The following
procedure describes how to change the state of an Apollo communication port.
1 Open the ROSA EM GUI, in the browser frame click on the ROSA EM device
(top node of the device tree), and point to the Apollo configuration tab.
Result: The Apollo configuration tab page is displayed.
2 Click on the Value field of the Apollo Com Port State parameter of the port for
which the state must be changed.
Result: The Change Parameter Dialog of the Apollo Com X Port State
Note: The Apollo Com X Port State parameters are only available when the
ports are assigned to the Apollo functionality.
button to abort.
4005743 Rev N 169

Installing the Apollo Drivers into ROSA NMS

Licensing
Before you can use the Apollo Protocol driver and Device Driver, make sure that the
appropriate license key APOLLO is available in your ROSA NMS license file.
Installing the Apollo Drivers

You have to install the Apollo Protocol Driver as well as the Apollo Device Driver. See
the ROSA NMS Users Guide for details about licensing and driver installation.
When you have installed the Apollo Protocol driver, the Apollo Protocol appears
under the node Protocol Drivers in the Server Explorer.
To Open the Apollo Protocol Driver

The Apollo Protocol Driver is opened by right-clicking on the Apollo Protocol under
the Protocol Drivers node in the Server Explorer or by double-clicking on the
Apollo Protocol bitmap in a ROSA map.
170 4005743 Rev N

Introduction
Result: The Apollo Protocol user interface is displayed.
On this user interface, you can add and remove remote sites and change their
properties. The user interface also has a small Communication Watcher dialog,
which displays messages about the site communication status. These messages are
logged in a text file named Report.txt. Double-click on the Communication Watcher
to open the file in Notepad.
4005743 Rev N 171

Setting Up Remote Sites

Adding a Site
Important: The Apollo functionality of a ROSA EM device may only be managed by
one ROSA NMS server (one Protocol Driver). If this is not the case the Apollo
functionality will have unwanted behavior.
For each ROSA EM device connected to the TCP/IP network, you have to create a
site in the Apollo Protocol user interface. The following procedure explains how to
add sites.
1 On the Sites tab, click on the Add button.
Result: The Add Site dialog is displayed.
2 Type a name for the site in the Site Name box. This name will also be the name
of the ROSA EM device in this site.
3 Type the network name or the IP address of the ROSA EM device in the
Network Name box.
4 Click on the button to select a location.
The standard ROSA Locations dialog is displayed. Select a location in the
Location tree and click on the OK button. See your ROSA Users Guide for
details about locations. Units connected to the ROSA EM device will be included
by default in the selected location, but you can change their unit location later in
the Server Explorer.
5 Select the Enabled check boxes to enable checking if the site is responding.
Note: Do not select the Enabled check box under When Site is Responding, if your
network contains semi-permanent connections.
6 In the Check Every drop down, select a time interval.
172 4005743 Rev N

For more details about these settings, see subtopic To Check Non-Responding Sites
on page 174.
7 Click on the OK button to add the new site.
In case of successful initialization, the ROSA EM device is added under the Units
node with the name you gave to the site, and the site details are displayed on the
sites tab in the Apollo Protocol user interface. The Communication Watcher list
box displays Checking site <SiteName> successful.
Note: A new site cannot be defined before the Apollo device driver is installed.
Result: The Add site failed message box displays and the Communication
Watcher list box displays: Please install Apollo device driver first!!!.
8 Click on the OK button to close the message dialog.
To Remove a Site
Perform the following steps to remove a site.
1 Select the site or sites you want to remove in the Sites list box and click on the
Remove button.
Result: A confirmation box displays.
2 Click on the Yes button to confirm or the No button to abort the operation.
To Change Site Properties

The following steps explain how to change the site properties.
1 Select the site in the Sites list box and click on Properties.
Result: The Site Properties dialog is displayed.
4005743 Rev N 173

2 In the Site Name box and the Network Name box, you can change the site name
and the network name.
Note: If the network name is available, the Network Name box displays the real
IP Address. You cannot change the real IP address. You cannot change the
location here but you can via the unit settings in the Server Explorer.
3 Under Check Site Reachable, you can change the site checking settings.
4 Click on the OK button to apply the changes or No to restore the previous
settings.
To Check Non-Responding Sites

When adding a site or when changing site properties, you can define different
checking intervals for responding and not responding sites. Normally, sites become
not responding due to network problems and therefore should not be checked as
frequently as responding sites.
It is advised to disable checking responding sites if the network connection between
the ROSA NMS Server and the ROSA Element Manager contains semi-permanent
sections. Each time a check is made, a connection has to be set up. When checking is
disabled, sites can only become not responding when you try to log on to the ROSA
EM device or to a device connected to the ROSA EM device.
You can force the Apollo Protocol driver to check the not responding sites
immediately as follows.
1 On the Sites tab, click on Check Not-Responding sites
Result: A confirmation box displays.
174 4005743 Rev N

2 Click on the Yes button to start checking the not-responding sites.

Result: The results of these checks are displayed in the Communication Watcher
list box.
4005743 Rev N 175

Message Configuration
ROSA Element Manager Messages
The Apollo Protocol driver itself does not generate messages, but you can configure
the message properties for all ROSA EM devices at the sites in the Sites list.
The three messages that can be generated are:
Configuration Changed messages
Internal Protocol Error messages
Unit not responding messages
The message source and message subject is the site name. This message is generated
when the ROSA EM device in the site is not responding.
To Change the Message Settings

The following procedure describes how to change the message settings.
1 Select the Messages tab.
Result: The Messages tab page displays.
176 4005743 Rev N

Message Configuration
2 Select the Configuration changed message and click on the Properties button or
double-click on the message.
Result: The Message(s) Properties dialog is displayed.
3 Under Severity, select the severity level you want to give to the message.
4 Click on the OK button to apply or the Cancel button to restore the previous
setting.
Note: The only setting you can change is the severity of the Configuration changed
message. You cannot change the properties of the Unit not responding and the
Internal Protocol Error messages: these two messages are always enabled and the
severity is always Major.
4005743 Rev N 177

Configuring an Apollo Site

General Information on Site Configuration
Introduction
Configuring a ROSA EM device in a remote site is similar to the configuration of a
serial port on a ROSA NMS Server. You have to define scan ranges for the devices in
the site and when the ROSA EM device has found the new devices, you have to
assign names and locations and map the devices.
To Open the User Interface of a ROSA Element Manager

You can open the site in the list on the Sites tab of the ROSA EM device in the
remote site as follows.
Double-click on the site in the list on the Sites tab of the Apollo Protocol driver.
For more details about this driver, refer to topic Introduction on page 168.
Right-click on the ROSA Element Manager under the Units node in the Server
Explorer and then click on Properties.
Double-click on the ROSA Element Manager bitmap in a ROSA map.
Result: The ROSA Element Manager user interface is displayed.
178 4005743 Rev N

Setting Scan Ranges

About Device Addresses and Scan Ranges
The ROSA Element Manager cannot detect devices with a remote address equal to
zero. In addition all remote addresses of devices of the same device type should be
different when connected to a serial port of the Apollo functionality. Identical
addresses will cause communication problems, even if they are connected to a
different serial port.
Important: Only create scan ranges for the devices that are actually connected to the
serial ports. If, for example five Pulsar modulators are connected to a serial port,
only include these five addresses in the scan range for the Pulsar device type. Then
the ROSA EM device only has to poll these devices, which improves the polling
speed. If you want to add an additional Pulsar afterwards, add its address to the
scan range as well.
For devices that support automatic address assignment, you do not have to enter a
scan range to detect them. In the Units to Search column on the Scan Ranges tab,
Automatic indicates that these devices receive an address from the ROSA EM device.
See the devices user manual for details about automatic address assignment.
4005743 Rev N 179

To Add Scan Ranges

The following procedure describes how to add scan ranges.
1 Select the Scan Ranges tab.
2 Select a device type and click on the Add button.

Result: The Add Scan Range dialog is displayed.
3 In the From and To boxes, enter the start and end address.
These addresses are in hexadecimal format and have a range of 01h to 7Eh.
Note: To add a single remote address, leave the To box empty.
4 Click on the OK button.
5 To add multiple scan ranges for the same device type, click on the Add button
again.
Note: You cannot add more than 350 addresses in total. If the total number of
addresses exceeds 350, a message is displayed.
180 4005743 Rev N

6 You can now map the newly found devices.

For details about device mapping, see the next sub topic Mapping New Devices.
To Remove Scan Ranges

The following procedure describes how to remove scan ranges.
1 Select a device type and click on the Remove button.
Result: The Remove Scan Range dialog for the device type is displayed.
2 In the From and To boxes, enter the start and end addresses of the range you
want to remove. To remove a single address, only type an address in the From
box and leave the To box empty.
Mapping New Devices

Introduction
Devices with a remote address falling in the added scan range are detected as new
devices. You have to assign names and locations to the devices and then map them.
When a new device is deleted in the remote site, this is displayed in different ways.
In the Server Explorer as a device icon with a red question mark in front of the
ROSA Element Manager icon under the Units node and in front of the Units
node icon.
In the topright corner of the ROSA Element Manager user interface.
4005743 Rev N 181

Assigning Name and Location

The following procedure describes how to assign a name and location to a new
device.
1 Select the New Devices tab.
2 Select a unit in the New Units list box and click on the New Unit button.
Result: The New Device dialog displays.
3 Enter a Name and Location for the new device and click on the OK button.
4 Repeat steps 1 to 3 for each new unit you want to assign.
If all devices are assigned, you can map them all at once.
Changing the Name and Location

To change the settings of a new device, select the device and click on Settings.
Note: The New Unit button becomes the Settings button when you select a device
that is already assigned.
Un-assigning a Device
You can un-assign a device, by selecting it and clicking on the Unassign button.
182 4005743 Rev N

To Filter the List of New Units

If too many new units are displayed, you can define a filter to display only those
units youre interested in. The following procedure describes how to filter the list.
1 Click on the Filter list button.
Result: The Filter dialog displays.
2 Under On/Off, select the Filtering ON check box.

3 Under Columns, select one or more columns to build the filter, then select the
And or Or Combination for these columns.
4 Under Configure filter, select one of the columns.
5 Under Method, select the filter method.
None: No filtering on that column
Equals/Differs: First select equals or differs, then one or more values in the list.
Between value: Select two values
6 Repeat step 4 and 5 for each column you selected in step 3.
7 If you want to restore the previous filter, you can click on Restore Previous
button.
8 Click on the OK button to apply the filter.
Note: The columns used in the filter definition have blue header text.
Mapping Assigned Devices

Once assigned, you can map devices as follows.
1 Click on the Perform MAPPING button.
4005743 Rev N 183

Note: During mapping, a message Mapping action busy appears in the lower
part of the dialog.
2 Mapping devices can take a while. When mapping is completed successfully, a
message is displayed.
Result: A warning message dialog displays.

Result: The mapped devices now appear under the Units node in the Server
Explorer, just like if they were connected directly to a ROSA NMS server.
Re-mapping Existing Devices

Re-mapping is mainly used when defective devices are replaced. With re-mapping,
you can let the spare device take the place of the defective device in ROSA NMS.
You still have to reconfigure most of the settings of the device, but you dont need to
recreate relations and so on.
Suppose that you have disconnected a defective device from the ROSA EM device.
The ROSA EM system still polls to the device, but receives no answer anymore. A
red line across the device in the Server Explorer indicates that it is no longer
responding.
The following procedure describes how to re-map a non-responding device.

1 Connect the spare device to the ROSA EM device.
Note: Take care to set the remote address of the spare device correctly. It does
not need to be identical to that of the defective one, but it must be unique for the
specific device type. It must be within the scan range too; otherwise you have to
adapt the scan range. The unit will appear as new unit.
2 On the New Devices tab, select the new device in the New Units list box.
184 4005743 Rev N

Result: In the Remappable units list box, all inactive (not responding) devices
of the same type as the selected new device are listed. The ROSA EM system
determines which of the inactive devices is most closely resembling the new
device and marks it with a blue pointing hand.
3 In the Remappable units list box, select the device you want to replace with
the new device and click on the Assign button.
Note: If you assigned a wrong unit, click on the Un-assign button and repeat this
step.
4 Repeat steps 1 to 3 for each device you want to remap and click on Perform
MAPPING.
Note: During mapping, a message Mapping action busy appears in the lower
part of the dialog. Mapping devices can take a while. When mapping is
completed successfully, a message is displayed.
Result: The spare devices now take over the place of the defective devices in
ROSA NMS. When a defective device is repaired, you can replace the spare
device in the same way the defective device was replaced.
4005743 Rev N 185

Viewing All Site Devices

To view all devices in a remote site, select the Site Devices tab.
On this tab, all devices in the remote site are listed. This is very useful because:
In the Server Explorer you cannot see whether a device belongs to a site or not.
If a device belongs to a site you can see here to which site it belongs.
Note: In the Site Devices list box, not responding devices are marked with a red line
across their icon.
Additional Settings
Local Control Settings
Some devices can be set to local control when they are remotely controlled and set
back to remote control via the keyboard of the device. You can enable or disable this
for all devices connected to the ROSA Element Manager as follows.
1 Select the Settings tab.
Result: The Settings tab page displays.
186 4005743 Rev N

2 To enable or disable local control, respectively select or clear the Local Control
From Device Keyboard check box.
3 Click on the Apply button.
RCDS Communication Parameters

You can change some parameters of the RCDS communication between the ROSA
Element Manager and the devices connected to it.
1 On the Settings tab, click on the Advanced button.
Result: The Advanced Communication Parameters dialog is displayed.
2 In the Network Delay box, type a value between 0 and 2000 ms.
Note: The value you enter here becomes the Global Network Delay on the Settings
tab. The default network delay is 90 ms. To keep the communication reliable, do
not enter a value lower than 90.
3 In the Command Retry Count box, type a number between 3 and 10.
The default is 3 times. This is the number of times an RCDS command is resent
to the device if the device does not acknowledge the command.
Note: Normally, you should not change these parameters. But in some cases it
may be necessary to change the parameters:
If Commbox Communication Organizers are cascaded after the ROSA EM
system, you might have to increase the network delay.
If the connection contains a cable modem and the communication appears to
be unreliable, try increasing the command retry count.
4 If you want to restore the default settings, click on the Apply Defaults button.
5 Click on the Apply button to apply these settings without closing the dialog or
the OK button to apply them and close the dialog.
4005743 Rev N 187

6 Chapter 6
Integration of ROSA EM
Introduction
This chapter covers the installation of ROSA Element Manager (EM)
devices into a management system.
In This Chapter
Integration of ROSA EM into ROSA NMS ...................................... 190
Integration of ROSA EM into TNCS ................................................ 207
Integration of ROSA EM into a 3rd Party SNMP Management... 209
4005743 Rev N 189

Chapter 6 Integration of ROSA EM
Integration of ROSA EM into ROSA NMS

General
Introduction
A ROSA EM system can be integrated in a central ROSA NMS. The communication
between the ROSA EM device and this central ROSA NMS can be established over a
LAN/WAN network or over a semi-permanent network like an Integrated Services
Digital Network (ISDN). The following illustration shows a LAN/WAN network
combined with a semipermanent network.
Master Headend with ROSA NMS
Ethernet
Hub/Switch Headend A
Ethernet
Ethernet Hub/Switch
ISDN
Router
ROSA Element
Manager
ISDN
Headend B
ISDN
Router
Ethernet
Hub/Switch
Ethernet
Ethernet
ROSA Element
Manager
I/O
RCDS
I/O
SMC
190 4005743 Rev N

Integration Requirements
Before integrating a ROSA EM device in ROSA NMS, the following is required:
An IP address has to be assigned to the ROSA EM device. More information
concerning assigning an IP address to a ROSA EM device can be found in topic
Network Configuration on page 25.
The ROSA EM device should be connected, powered up, and running.
The SNMP Protocol driver and the ROSA EM driver have to be installed.
The drivers of all devices, which should be managed, have to be installed.
Note: More information about the installation procedures can be found in topic
Installing ROSA Element Manager Drivers on page 192.
Integration by Mapping
When the requirements above are fulfilled the ROSA EM Agent should be mapped
to the ROSA EM 2U Device Driver. The procedure to map a ROSA EM Agent to the
ROSA EM 2U Device driver can be found in topic Mapping the ROSA Element
Manager Agent on page 194. After mapping a ROSA EM Agent, the IP address of the
ROSA NMS server is automatically added as a trap destination. More information
concerning trap destinations can be found in topic Sending Traps on page 106.
Synchronization between ROSA EM and ROSA NMS

Additionally a synchronization action is executed. This synchronization action
implies:
A Trap regeneration of all pending alarms arisen in the ROSA EM device or in a
device connected to and supported by the ROSA EM device. These traps are sent
to ROSA NMS and logged by the ROSA NMS system if they are not yet logged.
An inventory synchronization. If a unit is integrated in the Device List of the
ROSA EM device but not yet mapped in ROSA NMS, this unit is automatically
mapped in ROSA NMS.
- When the device is a proxy unit (a proxy unit is a unit which is proxied by
ROSA EM and hence is manageable on the same IP address as the ROSA EM
device) ROSA NMS maps this device either using its installed ROSA EM
profile or using the general proxy unit driver. If ROSA NMS maps the device
using the general proxy unit driver, the Graphical User Interface (GUI) of the
applet is used and shows the parameters of the device.
- An SNMP device (a device with its own SNMP agent and manageable on its
own IP address) is mapped using its dedicated driver, its ROSA EM profile
or the general proxy unit; in this order of preference. If the unit is mapped
on the general proxy unit driver, the SNMP Agent of ROSA EM is used
instead of the SNMP Agent of the device itself. Please refer to the SNMP
Protocol Driver users guide for information on how to map a new agent.
4005743 Rev N 191

If a unit is mapped into ROSA NMS but no longer available in the Device List of
a ROSA EM device, the unit is set to not responding.
After mapping a ROSA EM device, the synchronization action is triggered
periodically. The period between two synchronization actions is adjustable for each
mapped ROSA EM device separately and can be set between 30 minutes and 24
hours in steps of 1 minute.
A synchronization action is executed each time the ROSA NMS server is restarted.
This action can be enabled or disabled for each ROSA EM device separately. If the
synchronization action after a restart is switched off, the first synchronization action
after restarting the server is delayed until the first synchronization action period is
expired. More information about switching on or off the synchronization action
after restarting a ROSA NMS server can be found further in topic Configuring the
Synchronization Action on page 202.
Polling Behavior
When the communication between a ROSA EM device and a ROSA NMS is
established over a semi-permanent network (for instance ISDN) the polling behavior
of the SNMP Protocol driver is different as with a permanent connection (for
instance LAN/WAN network):
With a permanent connection, the SNMP Protocol driver continuously polls the
devices managed by the ROSA EM device.
With a semi-permanent connection, the SNMP Protocol driver doesnt poll the
devices managed by the ROSA EM device to reduce dial-up costs. A status
change of the managed devices is reported with traps sent by the ROSA EM
device and the trap buffering on the ROSA EM device is automatically enabled.
The trap delivery time to ROSA NMS can be programmed short enough to see
the changes in time. Refer to topic Sending Traps on page 106 to see how the
delivery time can be changed.
Please refer to the topic Mapping the ROSA Element Manager Agent on page 194 to see
how the connection type can be specified in the SNMP Protocol driver.
Installing ROSA Element Manager Drivers

Introduction
After assigning an IP address to the ROSA EM device and before integrating the
ROSA EM device in ROSA NMS, the ROSA EM drivers have to be installed into
ROSA NMS. This topic explains how to install the ROSA EM drivers into ROSA
NMS. More information concerning ROSA drivers can be found in the ROSA Users
Guide.
192 4005743 Rev N

Installing ROSA EM Drivers

The following procedure explains how to install the ROSA EM drivers into ROSA
NMS.
1 In the ROSA NMS user interface click on the Resource Drivers icon.
Result: The Installed Drivers dialog is opened.
2 Click on the Install button.

Result: An Open dialog appears.
3 In the Look in box browse to the directory where the ROSA EM driver files are
located.
4 Select all ROSA EM.rsx files and also include the SNMP Protocol.rsx file.
Important:
- To make a selection of multiple files use the [Shift] or [Ctrl] key in
combination with the mouse.
- You can also just select the files you need. In this case make sure that you
include the ROSA EM 2U Device.rsx file in your selection.
Note: The ROSA EM 1U Device.rsx is only necessary if you are using the ROSA
EM functionality of an Apollo MKII device.
4005743 Rev N 193

5 Click on the Open button.

Result: The selected ROSA EM drivers are installed and the Installed Drivers
dialog is updated.
6 Close the Installed Drivers dialog.
Mapping the ROSA Element Manager Agent

Introduction
After installing the ROSA EM drivers into ROSA NMS, the ROSA EM Agent should
be mapped to the ROSA EM Device Driver using the SNMP Protocol driver. For
more information concerning the SNMP Protocol driver, please refer to the SNMP
Protocol Protocol Driver for ROSA 3.0 Users Guide.
Before you map the ROSA EM Agent, you must set the SNMP Agent Status on
ROSA EM to Enabled. For more information, please refer to topic Managing Services
on page 72.
Mapping the ROSA Element Manager Agent

Following steps show you how the ROSA EM Agent is mapped to the ROSA EM
Device driver.
1 In the Server Explorer of ROSA open the Protocol Drivers node and right-click
on SNMP Protocol.
Result: A driver menu appears.
194 4005743 Rev N

2 Select Properties in the short-cut menu.

Result: The SNMP Protocol user interface is opened.
Note: Initially the Scan List will be empty, but in case you already make use of
the SNMP Protocol driver for some agents, they are shown in this list.
3 Click on the Add button to add a new SNMP agent.
Result: The Add agents dialog appears.
4005743 Rev N 195

4 Change the following agent parameters:

- Identify Agent by: select IP-address
- IP Address (range) From: enter the IP address of the ROSA EM device.
- Protocol Version: set the protocol version to SNMPv1.
5 Click on the Advanced button at Advanced Communication Parameters.
Result: The Agent Parameters dialog is displayed.
6 If necessary, change the Timeout and/or Retry Count in the Communication

Parameters area.
7 At Profile Type Information, select Enable Automatic Mapping.
8 In the Community Strings area change the strings as follows:
- In the Read Community box enter the SNMP Read Community string as set
196 4005743 Rev N

on the ROSA EM device.

- In the Write Community box enter the SNMP Write Community string as set
on the ROSA EM device.
9 In the Connection Type drop down box, select the connection type of the
connection between the ROSA EM device and ROSA NMS device.
- If Direct Access is selected, the period between two successive
synchronization actions is set to 30 minutes.
- If ISDN is selected, the period between two successive synchronization
actions is set to 24 hours and Trap buffering is switched on to reduce the dial-
up cost on the semi-permanent connection. More information concerning
Trap buffering can be found in topic Configuring Device Polling on page 95.
Note: Devices managed with a ROSA EM device have the same connection type
as the ROSA EM device itself. When the connection type of the ROSA EM device
is changed, the connection type of these managed devices is updated
automatically.
10 First click on the OK button to close the Agent Parameters dialog and secondly
click on the OK button to close the Add agent dialog.
Result:
- The Scan List (also) shows the last agent you added.
- The Apply button at the bottom of the user interface becomes enabled.
11 Select the agent and click on the Apply button to add the agent.
Result:
- For a moment a red question mark appears in the upper right corner
indicating a new SNMP agent is detected.
- Because Automatic Mapping is enabled (see step 7) the detected SNMP Agent
is automatically added as a new resource.
Note: The automatic mapping works for the ROSA EM 2U Device driver, for the
ROSA EM 1U Device driver refer to the Apollo MKII users guide.
12 Click on the Poll Resources tab of the user interface.
Result: The SNMP Resources list shows that the ROSA EM 2U Device driver
state is Active. The driver can now be used to manage our and 3rd party
equipment.
4005743 Rev N 197

13 Close the SNMP Protocol user interface.
Using ROSA Element Manager Graphical User Interface

Introduction
The previous topics showed how the ROSA EM drivers were installed and how the
ROSA EM Agent was mapped automatically to the ROSA EM Device driver. The
results of these actions are:
The ROSA EM Device resource appears as a unit on ROSA NMS Server Explorer
with the name ROSA EM 2U Device followed by the IP address of the device.
During the mapping action the ROSA EM Device resource performs an
inventory synchronization with the ROSA EM device. Every unit that is
integrated in the Device List of the ROSA EM device but not yet mapped in
ROSA NMS, is mapped automatically in ROSA NMS as explained in the topic
General on page 190.
ROSA EM Device Configuration GUI

The following procedure explains how to open the ROSA EM Configuration GUI.
More information concerning the ROSA EM Configuration GUI can be found in
chapter ROSA EM Functionality on page 49.
1 In the ROSA Server Explorer look for the ROSA EM Device at the Units node.
2 Right-click on the unit and select Properties in the short-cut menu.
198 4005743 Rev N

Result: A dialog called Start User Interface dialog appears.
Note: Two interfaces can be opened:

- With Group & Device Configuration you can start the ROSA EM Device user
interface that allows you to manage equipment (adding or removing devices,
checking the device state...). See the next sub topic Equipment Management
for more information.
- With Applet you can start the configuration user interface of the ROSA EM
Device driver itself. It allows you to view and/or change settings (for
instance alarm settings, system settings...).
3 Select Applet and click on the Start button.
Result: The ROSA EM Applet is opened.
The following procedure shows how to open the user interface of a proxy unit that is
mapped on a General Proxy Unit Driver.
1 In the ROSA Server Explorer look for the proxy unit at the Units node.
2 Right-click on the unit and select Properties from the menu.
Result: The applet with the device specific parameters is opened.
4005743 Rev N 199

Managing the ROSA EM Equipment

Each ROSA EM device is provided with a Device List (Devlist.txt) containing
information concerning the connected and supported equipment. More information
about the ROSA EM Device List can be found in topic Working with Devices and
Groups on page 91.
The following explains how to manipulate the Device List using the Group &
Device Configuration feature integrated in ROSA NMS.
1 Look for the ROSA EM Device at the Units node of the ROSA NMS Server
Explorer.
2 Right-click on the unit and select Properties from the short-cut menu.
Result: A dialog called Start User Interface appears.
3 Select Group & Device Configuration and click on the Start button.
Result: The ROSA EM Device user interface is opened.
200 4005743 Rev N

4 In the ROSA EM Device user interface you can add devices and groups to the
Local node. Right-click on the Local node and select Add Device in the short-cut
menu.
Result: The Add Device at Location Local dialog is opened.
Note: In the Select Device box, the icon of a device is grayed if no ROSA driver
is installed for the device.
5 Enter the following information:
- In the Select Device list, choose a device type.
4005743 Rev N 201

- At Name specify the name of the device.

- At Port select the communication port on which the device is connected.
- At Address specify the device address to access the correct device.
- If necessary specify the slot number at Slot.
Note: Some devices use Ethernet connections and the expected address is an IP
address of the format x.x.x.x where x is a decimal number from 0 to 255.
6 When finished click on the OK button.
Result: The device is added and can be seen on:
- The ROSA EM Device user interface
- The ROSA NMS Server Explorer at the Units node
7 To open the user interface, select the device in the ROSA NMS Server Explorer,
right-click and select Properties in the short-cut menu.
Result: The user interface opens.
Configuring the Synchronization Action

Introduction
When a ROSA EM agent is mapped to a ROSA EM Device Driver, a synchronization
action is executed periodically. Synchronization action involves trap regeneration
and inventory synchronization. After restarting the ROSA NMS server, a
synchronization action is also triggered.
Synchronization Operation
When the synchronization succeeds, the operation behavior is the same for the Direct
Access and ISDN connection types between ROSA EM and ROSA NMS.
When the synchronization fails, the operation behavior is different for both types:
With a Direct Access connection type (for instance LAN/WAN) the
synchronization works as 1 time - hit; in case of failure a new synchronization
will be performed after the period specified in the Synchronization Action
Parameters. No message will be logged.
With an ISDN connection type a shared line may be used and it is possible that
the line is not free at the moment of synchronization. Therefore synchronization
is retried for a maximum of 1 hour and if this fails, a message is generated.
202 4005743 Rev N

Changing the Synchronization Action Parameters

The period between two successive synchronization actions and the synchronization
action after server restarting are both configurable. Perform the following steps to
change the synchronization action parameters.
1 In the ROSA NMS Server Explorer open the Protocol Drives node and right-
click on SNMP Protocol.
3 Click on the Poll Resources tab.
Result: The Poll Resources tab is displayed.
4 In the Poll Resources area, select the ROSA EM Device in question and point the
Synchronize button.
Result: The Synchronize dialog appears.
4005743 Rev N 203

5 In the Synchronization Parameters Area, select or deselect the Disable

Synchronization at startup selection box and enter the time between two
successive synchronization actions in the Synchronize each box.
6 Close successively the Synchronize dialog and the SNMP Protocol user
interface.
Executing a Synchronization Action

After for example a communication loss between the ROSA EM device and the
ROSA NMS server, ROSA NMS allows the operator to manually execute a
synchronization action. The following explains how execute a synchronization
action.
1 In the ROSA NMS Server Explorer open the Protocol Drives node and right-
click on SNMP Protocol.
3 Click on the Poll Resources tab.
Result: The Poll Resources tab is displayed.
204 4005743 Rev N

4 In the Poll Resources area, select the ROSA EM Device in question and point the
Synchronize button.
Result: The Synchronize dialog appears.
5 Press the Synchronize button.

Result: A synchronization action will be performed immediately.
6 Close successively the Synchronize dialog and the SNMP Protocol user
interface.
4005743 Rev N 205

Selective Synchronization
The ROSA EM device offers the option to disable trap regeneration for devices in
maintenance mode or devices that are not polled, for instance off-scan mode. For
more information, please refer to the topic Sending Traps on page 106.
206 4005743 Rev N

Integration of ROSA EM into TNCS
Integration of ROSA EM into TNCS

Prerequisites
Installation
A TNCS version V03.00.00 or higher installed on a PC.
For more information about the installation of TNCS, please refer to TNCS
Administrator Release Software Users Guide.
Both the ROSA EM and the TNCS software version must be equal.
Integration of a ROSA EM with software version V04.01.30 or higher requires
that the TNCS service is enabled.
Integration Procedure
The following procedure explains the steps necessary to integrate ROSA EM into
TNCS.
1 Start TNCS.
2 Log on with an account that has Configure rights as Privilege Level.
3 Open the Details of the Local system.
4 Look for the item Server-Connections and at Server xxx IP Address fill in the IP
address of the ROSA EM device.
4005743 Rev N 207

5 In File select Exit to terminate TNCS.

6 Restart TNCS.
Result: ROSA EM appears as a server node in the tree.
208 4005743 Rev N

Integration of ROSA EM into a 3rd Party SNMP Management
Integration of ROSA EM into a 3rd Party SNMP

Management
SNMP Protocol and Community Strings
SNMP Settings
The following settings are used when implementing ROSA EM in a 3rd Party SNMP
Management System.
Supported protocol version: SNMP v1
Read Community String: parameter set on the ROSA EM device
Write Community String: parameter set on the ROSA EM device
Viewing Community Strings

The following procedure explains how to view the SNMP community strings of the
ROSA EM device via the ROSA EM Configuration Tools.
2 To view the SNMP community strings, enter the following instructions on the
command prompt:
setupcommunities X.X.X.X
With X.X.X.X the IP address of the ROSA EM device.
Result: The current read-community and write-community strings used on the
ROSA EM device are displayed.
4005743 Rev N 209

Changing Community Strings

The following procedure explains how to change the SNMP community strings of
the ROSA EM device via the ROSA EM Configuration Tools.
2 To change the SNMP community strings, enter the following instructions on the
command prompt:
setupcommunities X.X.X.X Y Z
With:
- X.X.X.X: the IP address of the ROSA EM device
- Y: the new read-community string
- Z: the new write-community string
Note that the read and write community strings should be different.
Result: The current read-community and write-community strings are displayed
and the new read-community and write-community strings are set.
Getting MIB Information

Introduction
In order to use the ROSA EM device MIB files by other SNMP Manager software, the
MIB files can be downloaded from the ROSA EM device to the hard disk of your
computer using ROSA EM Configuration Tools or using FTP. The MIB files in the
ROSA EM device are added into a ZIP file.
210 4005743 Rev N

Downloading with ROSA EM Configuration Tools

Perform the following procedure to download the MIB files to your computer.
getmibs X.X.X.X Y
With:
- Y: the target directory. When no directory is entered, you will be prompted
to provide one. Press [Enter] if you want to save the Zip file containing the
MIB files in the current directory (the directory of the ROSA EM
Configuration Tools).
Result: The ZIP file containing the MIB files is downloaded to your computer.
Downloading with FTP

The MIB files can also be downloaded from the ROSA EM device using FTP.
Important: This procedure does not apply to a ROSA EM with boot software version
older than V04.00.50. If your ROSA EM has an older boot software version, please
refer to a previous version of this user's guide.
1 Start the command prompt.
Note: In Windows 2000, the command prompt can be found
via Start, Programs, Accessories, and Command Prompt or
via Start, Run, entering cmd and clicking on the OK button.
ftp X.X.X.X
4005743 Rev N 211

With X.X.X.X the IP address of the ROSA EM device.

3 As User, enter rosa_ro2.
4 As Password, enter the FTP download password.
5 Set the local directory to a directory where you want to save the MIB files.
Example: For the directory \temp enter the command:
lcd c:\temp
6 Set the binary mode with the command:
bin
7 Download the MIB files with the command:
get rosaem-mibs.zip
8 Close the FTP session with the command:
bye
9 Type exit to close the window.
Compiling
The zip packet rosaem-mibs.zip contains the MIB files for all types of devices that
ROSA EM can manage. Some special MIB files need to be compiled first.
MIB File Description

system.mib Properties of the ROSA EM device itself.
This is the first row in the following table:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).scientificatlanta(1429).saTe
rr(1).saTerrTNCS(9).saTNCSrev2(2).satncs(2).saSYSTEM(1).saSYSTEMTable(1)
group.mib Properties of the groups.
Each group is a row in the following table:
iso(1).org(3).dod(6).internet(1).private(4).enteprises(1).scientificatlanta(1429).saTer
r(1).saTerrTNCS(9).saTNCSrev2(2).satncs(2).saGROUP(2).saGROUPTable(1)
212 4005743 Rev N

MIB File Description

tncstrap.mib Used for trap decoding.
Receiving SNMP Traps

Registering
Up to four SNMP managers can be configured for one ROSA EM device. Each
SNMP manager needs to register itself to receive SNMP traps. Therefore some
variables need to be set in the System table: this can be done through SNMP or via
the ROSA EM GUI.
Via SNMP
Set the following variable with the IP address of the SNMP Manager as an octet
string.
Name: saSYSTEMSNMManIPAdd1
Type: OBJECT-TYPE
OID: 1.3.6.1.4.1.1429.1.9.2.2.1.1.1.520
Full path: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).scie

ntificatlanta(1429).saTerr(1).saTerrTNCS(9).saTNCSrev2(2).satnc
s(2).saSYSTEM(1).saSYSTEMTable(1).saSYSTEMEntry(1).saSYSTEMSNMM
anIPAdd1(520)
Module: TNCSSYSTEM
The next three variables (saSYSTEMSNMManIPAdd2, saSYSTEMSNMManIPAdd3

and saSYSTEMSNMManIPAdd4) are also available for SNMP Manager IP
addresses.
Via ROSA EM GUI
This configuration can also be done on the ROSA EM GUI. Look for the SNMP tab
page of the ROSA EM device and enter the data at the SNMP Manager IP address
parameter(s).
4005743 Rev N 213

7 Chapter 7
Maintenance
Introduction
This chapter provides the user with information about licensing,
license upgrading, software upgrading, the backup and restore
procedure and cloning ROSA EM device settings.
In This Chapter
Licensing .............................................................................................. 216
Software Upgrading ........................................................................... 218
Working with Device Configuration Files ...................................... 222
ROSA EM Parameters ........................................................................ 227
Downloading and Deleting a Coredump File ................................ 229
4005743 Rev N 215

Chapter 7 Maintenance
Licensing
Introduction
The license for a ROSA EM device consists of 2 components:
Device-count: The number of devices that a ROSA EM device can monitor.
Application domain: The application domain defines the type of devices a ROSA
EM device can monitor. A ROSA EM device can have several application
domains. Five different types exist: Headend, HUB & HFC, Microtransmitter,
Transmitter sites, and General.
Viewing the License Parameters

Perform the following steps to check the license parameters of a ROSA EM device.
1 Launch your internet browser.
top node of the device tree) and select the License tab.
Result: The License tab page is displayed.
The following license parameters can be checked:

- Device License Count: The number of devices that can be managed.
- Device License Usage Count: The number of devices that is managed.
- Licensed Application Domains: The application domain that the ROSA EM
device can manage.
- Device License Shortage: The number of devices for which no license is
available.
Note: License limit warnings appear when the number of managed devices reaches:
90% of the number of devices that can be managed
100% of the number of devices that can be managed
More information about logging and alarms can be found in topic Using the ROSA
EM Device GUI on page 50.
216 4005743 Rev N

Licensing
Obtaining a New License File

When your ROSA EM device needs more device count than its license file provides
or needs another device domain, the license can be upgraded by installing a new
license file. The license file can be recognized by its extension (.lic).
To obtain a new license file, please contact our Customer Service department.
Telephone numbers, fax numbers, and/or e-mail addresses of our assistance centers
can be found in chapter Customer Information on page 315.
Provide the serial number of the ROSA EM device because this is required to create a
new license file. As soon as possible, your license file will be created and sent to you
by e-mail.
Upgrading the License

The following procedure explains how to upgrade the license via the ROSA EM
Configuration Tools.
putlicense X Y.Y.Y.Y
With:
- X: the name of the ROSA EM license file
- Y.Y.Y.Y: the IP address of the ROSA EM device
Result: The new license file is uploaded to the ROSA EM device.
4005743 Rev N 217

Software Upgrading
ROSA Element Manager Software
The ROSA EM software can be remotely upgraded using ROSA EM Configuration
Tools. The software exists of three parts:
The boot software
The ROSA EM device software
The ROSA EM Apollo Functionality software
Important:
In case an upgrade is needed, contact the customer services department for the
most recent software files. A software file is recognizable by its extension (.rpm).
Only one part of the software can be upgraded at the time, repeat the upgrade
procedure separately for every file.
During a software upgrade, always start with the boot software.
Upgrading the ROSA Element Manager Device Software

The following procedure explains how to upgrade the ROSA EM software using the
ROSA EM Configuration Tools.
update X.rpm Y.Y.Y.Y
With:
- X: the filename of the software upgrade
- Y.Y.Y.Y: the IP address of the ROSA EM device
Notes:
- The processing and upgrade start after the file has been transferred to the
ROSA EM device. During the upgrade of a software part, the ROSA EM
device and connected devices may become inaccessible during a few
minutes. This is a normal situation. The availability of the ROSA EM device
can always be checked with a ping request.
- If the ROSA EM device remains inaccessible after installing a software part,
please re-install the complete software (three parts). If a second attempt is
unsuccessful, please contact a customer service representative.
218 4005743 Rev N

Software Upgrading

Result: The ROSA EM with IP address Y.Y.Y.Y is upgraded.
4 The new software starts up as soon as the software upgrade is successfully
completed resulting in a warm start of the device.
5 Repeat step 2 and 3 for every .rpm upgrade file you received after the previous
.rpm upgrade file was installed successfully.
A ROSA EM software upgrade action can be started by drag and drop the software
upgrade file to the update tool. The following steps explain how to upgrade the
ROSA EM software using the drag and drop method.
1 Open Windows Explorer window and browse to the directory containing the
software upgrade file.
2 Click on the Windows Start button, move to Programs, ROSA EM Configuration
Tools, and select ROSA EM Tools Environment.
3 Type following instruction on the command prompt, but dont press [Enter].
update followed by a single space
4 Drag-and-drop the software upgrade file to the ROSA EM Tools Environment
window.
Result: The path and the name of the file are added at the command prompt.
5 Press the [Enter] key.
Result: The tool asks for the IP address of the ROSA EM device.
6 Enter the IP address and press the [Enter] key.
Result: The ROSA EM with IP address Y.Y.Y.Y is upgraded.
4005743 Rev N 219

8 Repeat steps 3 to 6 for every .rpm upgrade file you received after the previous
.rpm upgrade file was installed successfully.
9 When finished, type exit to close the ROSA EM Tools Environment window.
Checking the Software Version

The following steps explain how to check the software version.
1 Launch your internet browser.
top node of the device tree) and select the Properties tab.
The following license parameters can be checked:

- Software Revision: the version of the ROSA EM embedded software.
- Boot Software Revision: the version of the ROSA EM boot software.
- Apollo Software Revision: the version of the ROSA EM Apollo software.
ROSA EM Applet Message

When the ROSA EM device software has been upgraded and an applet was still
open on this device, the following message will appear on the applet.
220 4005743 Rev N

Software Upgrading
1 Close the Message box.

2 Close the web browser that is running the applet, and open the applet again.
Result: In this way you are sure that you are using the latest applet version.
Note: When you upgrade or downgrade the ROSA EM software a lot, it can occur
that the message reappears every time you open the applet in a web browser. This
can be solved by enabling the page refresh option of your web browser. In case you
are using Internet Explorer, follow the procedure below.
1 Click on the Tools menu item of the Internet Explorer.
2 Select Internet Options.
Result: The Internet Options dialog is displayed.
3 At Temporary Internet files click on the Settings button.
Result: The Settings dialog is displayed.
4 At Check for newer versions of stored pages: point to the Every time you start
Internet Explorer selection button.
5 Click on the OK button of the Settings dialog to apply the new setting and click
on the OK button of the Internet Options dialog to close the dialog.
4005743 Rev N 221

Working with Device Configuration Files

Introduction
ROSA EM allows to create a backup file with the device configuration settings
except for the IP settings. This file can be used to restore device configuration
settings when needed by transferring the backup file to the ROSA EM device.
ROSA EM backup configuration settings contain service status and password
settings. After restoring a backup, the passwords will have changed to those defined
in the backup file. Services may be enabled or disabled after restoring backup
settings. When restoring backup settings stored with an older software version on a
ROSA EM with software version V04.01.30 or higher, all services are disabled.
The ROSA EM cloning feature allows you to copy device settings from a source
ROSA EM to a target device. This feature is extremely useful if you have several
ROSA EM devices that must have identical configuration settings.
Creating a Backup
A backup can be created in two different ways:
Via ROSA EM Device GUI: the backup file is stored on the ROSA EM device and
can be obtained via FTP.
Via ROSA EM Configuration Tools: the backup file is stored in a target directory
on your system.
Via ROSA EM Device GUI
The following procedure explains how to create a backup of the ROSA EM device
settings using the ROSA EM device GUI.
Important: This procedure does not apply to a ROSA EM with boot software version
older than V04.00.50. If your ROSA EM has an older boot software version, please
refer to a previous version of this user's guide.
top node of the device tree) and select the Config_Backup tab.
Result: The Config_Backup tab page is displayed.
2 Click on the Value field of the Backup Configuration Now parameter.
222 4005743 Rev N


3 Select BackupNow and click on the Execute button.
Result: The backup action is triggered and might take up to 15 seconds or more
to complete, based on the amount of data to backup.
4 When the backup action is completed:
- The Last Configuration Backup Status parameter will show the result of the
action (Success or Failed) together with the date and time.
- The backup file is stored on the ROSA EM device.

Note: A backup will generate a new backup file and erase the previous.
5 Launch the Internet Explorer browser and in the Address line of the browser
enter the following instruction:
ftp://X.X.X.X
Where X.X.X.X is the IP address of your ROSA EM device.
Result: The FTP server login dialog is displayed.
6 In the User name box, type bu_ro.

7 In the Password box, type the FTP password.
8 Click Log On to confirm or Cancel to abort.
9 Copy the backup file to a save place and close the Internet Explorer browser.
Notes:
The generated backup file is a zip-file containing all the settings:
rosaem_configbackup.<ROSA EM IP address>.<Time Stamp>.<ID>.zip
Example:
The file itself is not password protected, but the content is: this means it is not
possible to extract any data and the content of the file should never be changed.
4005743 Rev N 223

When the content is changed, this will result in an invalid file.

The file name, <ROSA EM IP Address> and <Time Stamp> may be changed, but
dont change <ID> and extension .zip.
The following procedure explains how to create a backup of the ROSA EM device
settings using the ROSA EM Configuration Tools.
2 Enter the following instructions on the command prompt.
getbackupdata X.X.X.X Y Z
With:
- Y: target directory where the backup file will be stored. When no directory is
entered, you will be prompted to provide one. Press [Enter] if you want to
save the backup file in the current directory (the directory of the ROSA EM
Tools Environment).
- Z: timeout between the SNMP trigger to write the file and to download the
file, expressed in seconds
Notes:
The Y parameter is optional.
This tool requires that the FTP SNMP agent has been enabled.
Result: The backup file is created and stored.
Note: The resulting backup file has exactly the same look and characteristics as the
backup file generated via the ROSA EM device GUI.
224 4005743 Rev N

Performing a Restore
The following procedure explains how to restore the ROSA EM device settings using
the ROSA EM Configuration Tools.
2 Type the following instruction on the command prompt, but dont press [Enter].
restorebackupdata followed by a single space
3 Go to the directory where you saved the backup file and simply drag-and-drop
the backup file into the ROSA EM Tools Environment window.
Result: The path and the name of the backup file are added at the command
prompt.
4 Press the [Enter] key.
Result: The tool asks for the IP address of the ROSA EM device.
5 Enter the IP address.
Result: A connection is established with the ROSA EM device and the backup
file is transferred. When the file is valid it is extracted, the settings are restored
and the device is rebooted.
7 Press the [Enter] key to continue and type exit to close the ROSA EM Tools
Environment window.
Cloning ROSA EM Device Settings

Via the ROSA EM Configuration Tools it is also possible to clone the settings from a
source ROSA EM device to target ROSA EM device in a single operation.
Note: This tool requires that the SNMP agent has been enabled.
4005743 Rev N 225


clone X.X.X.X Y.Y.Y.Y
With:
- X.X.X.X: The IP address of the source ROSA EM device
- Y.Y.Y.Y: The IP address of the target ROSA EM device
3 Enter the FTP password of the source ROSA EM on the command prompt.
4 Enter the FTP password of the target ROSA EM on the command prompt.
Result: The settings of the source ROSA EM are cloned to the target ROSA EM.
Result: The text Specify Source ROSA EM IP Address appears.
5 Press the [Enter] key to continue and type exit to close the window.
The status of the clone operation is available on the Config_Backup tab page:
The source ROSA EM device shows the status of the backup operation and the
date + time at Last Configuration Backup Status.
The target ROSA EM device shows the status of the restore operation and date +
time at Last Configuration Restore Status.
226 4005743 Rev N

ROSA EM Parameters
ROSA EM Parameters
Persistence
Perform the steps below to check the persistence parameters of a ROSA EM device.
top node of the device tree) and select the Persistence tab.
Result: The Persistence tab page is displayed.
2 The parameters in normal letter type are read-only parameters:

- Devices with Changed Instance Data: Shows the number of devices with
changes, which are not saved yet.
- Total Instance File Write Count: When a setting is changed, a devices
changes a setting itself (for instance due to a measurement) or an alarm
change occurs, a write operation to flash memory is performed. This
parameter shows the number of write operations.
- Available Storage: Shows the available memory storage space in KB.
- Available Data Storage: Shows the available data storage (logs, settings,
uploaded files)
The parameters in bold letter type can be used to perform an action:
Save all Device Instance Changes Now: Used to save all device changes. Click
on the Value field of this parameter and select SaveNow.
Dump Log Data to File: Used to generate a log file. Refer to topic Using the
ROSA EM Device GUI on page 50 for more information.
Clear All Log Files: Used to clear all log files. Click on the Value field of this
parameter and select ClearNow.
Available Data Storage Alarm Threshold: Will show an alarm when the
Available Data Storage drops below this configurable threshold.
4005743 Rev N 227

Remove Stale Instance Files: If a new device list is installed, it happens that
instance files of devices used by the previous device list remain. When these
devices are not used in the new device list, the instance files are not necessary
anymore and only consume memory space. To free this unused memory space,
click on the Value field of this parameter and select RemoveNow.
228 4005743 Rev N

Downloading and Deleting a Coredump File
Downloading and Deleting a Coredump File

Downloading a Coredump File
The ROSA EM Configuration Tools contain a tool to download a coredump file
located on the internal ROSA EM flash memory.
Note: This tool is only supported if your ROSA EM has boot software version
V04.00.50 or higher. An error message is displayed if this tool is used to download a
coredump file from a ROSA EM with older boot software version.
The following steps describe how to download a coredump file.
getcoredump X.X.X.X Y
With:
- Y: the target directory where the coredump file will be stored. When no
directory is entered, you will be prompted to provide one. Press [Enter] if
you want to save the coredump file in the current directory (the directory of
the ROSA EM Tools Environment).
3 Enter the FTP password of the ROSA EM on the command prompt.
Result: The coredump file is saved to the specified location.
Notes: A 'No coredump file' message is displayed if there is no coredump file on

the flash memory.
Environment window.
Deleting a Coredump File

The ROSA EM Configuration Tools contain a tool to delete a coredump file located
on the internal ROSA EM flash memory. The following steps describe how to delete
a coredump file.
4005743 Rev N 229

Note: This tool is only supported if your ROSA EM has boot software version
V04.00.50 or higher. An error message is displayed if this tool is used to delete a
coredump file from a ROSA EM with older boot software version.
deletecoredump X.X.X.X
With:
3 Enter the FTP password of the ROSA EM on the command prompt.
Result: The coredump file is deleted.
Note: A 'No coredump found' message is displayed if there is no coredump file

on the flash memory.
Environment window.
230 4005743 Rev N

8 Chapter 8
Creating Graphics in ROSA
EM
Introduction
This chapter explains how to configure the ROSA Element Manager
(EM) to display graphics.
In This Chapter
Overview of Graphics ........................................................................ 232
Configuring ROSA EM Graphics ..................................................... 242
Device Graphics Examples ................................................................ 250
Using Graphics in ROSA EM ............................................................ 255
4005743 Rev N 231

Chapter 8 Creating Graphics in ROSA EM
Overview of Graphics
Introduction
ROSA EM reads the device list file (devlist.txt) to graphically represent your
monitored devices.
Important: Before continuing make sure that the ROSA EM device has a device list.
If the device list doesnt exist, create a device list according to the instructions of the
topic Adding devices and Groups on page 91.
After each device has been identified and grouped in the device list file, the next step
is to set up ROSA EM to display graphics. This section provides an overview of all
the device graphics ROSA EM offers.
The examples and information in this topic are based on the following device list:
232 4005743 Rev N

Individual Devices
When individual devices are graphically represented, they are displayed as a
member of the parent group to which they belong.
While viewing a device graphically, you can right-click on it for more options.
Menu Item Description

Open Displays the devices Details window (if the logged-on users privilege level
is equal to or greater than the Display DetailsPrivilege Level field on the
System tab page of the ROSA EM GUI.
Summary Displays the alarms and status of various device parameters.
Details Displays the devices Details window.
Off-Scan Turns off polling for the device.
On-Scan Turns on polling for the device.
Retry This option overrides the Device Retry Count parameter on the ROSA EM
Device-Polling tab and begins polling immediately.
If the polling is unsuccessful, the device returns to offline mode, and ROSA
EM automatically retries polling after the number of cycles specified in the
Device Offline Threshold parameter on the ROSA EM Device-Polling tab.
4005743 Rev N 233

Group Devices
Group devices can be graphically displayed in the following formats:
Standard view (default)
Directed views
Custom views
Upon right-clicking on a group in the device tree, you have the following options.
Menu Item Description

Open Displays a graphic of the groups child (or children).
Examples:
Right-clicking on a headend graphic displays the racks in the

headend.
Right-clicking on a chassis displays a zoomed-in view of the
chassis, allowing you to see its individual devices.
Summary Displays the summary status of the group, allowing you to see if an alarm has
been promoted from a device that belongs to the group.
Details Displays the properties and summary status of the group.
Off-Scan Turns off polling for the devices in the group and all groups that belong to it.
On-Scan Turns on polling for the devices in the group and all groups that belong to it.
Standard View
The standard view is the simplest graphical form for a group. This view is the
default view for group device types when the Graphic field in the device list or the
groups Device Details window is not populated. Each subgroup and/or device in
the group is represented as a box or as the symbol that is set for the device or group.
234 4005743 Rev N

Directed Views
A directed view is configured with keywords in the groups Graphic field in the
device list or in the groups Device Details window. Several types of directed views
are supported.
Directed View Description

Rack View Displays a rack with the chassis and single-rack mount devices that
are located in it.
Chassis View Displays a chassis with the individual devices that are located in it.
Group of Racks View Displays multiple racks in a row.
Star View Displays higher-end components of the network, such as headends,
hubs and nodes, and shows how they are connected.
Lines that represent attached equipment radiate from the center of
a component in a star-like fashion.
Cascade View Displays nodes, amps, power supplies, and taps horizontally, with
attached components cascading down the screen.
Rack View
Single rack-mount devices and chassis can be displayed in rack view. The rack
view is configured by setting the Graphic field to the keyword value rack.
Note: A second argument can be specified to select the rack height in rack units
(RUs). The default rack height is 7 feet (50 RUs).
4005743 Rev N 235

Example: Setting the Graphic field under R1 to the value rack 40 displays the
device as a 70-in. (40 RU) rack drawing.
Each chassis within the rack is placed in the position specified in the rack
vertical position field. If no position is specified, the chassis is placed in the first
empty location beginning at the bottom of the rack.
Chassis View
Devices that are mounted in a chassis are usually displayed with a chassis view
as a configured group. The Graphic field has the keywords cadminhassis type.
The supported types are as follows: continuum, evertz7700, evertz500,
ensembleAvenue, galaxy, prisma, prisma2, prisma2hd, prismadt, prismaIP,
laserlink, vision1000, system60, Uc4, Stratum, Omnistar, HDRX, GX2,
Homeworx, DV6000, DV6300, SMOA (not typically located in rack), Sirius,
Constellation, dvrps, prisma2hdr2, fuba, wisi, prisma2xd, lumin, rfgw1 and
xdqa.
236 4005743 Rev N

Example: Setting the Graphic field to the value chassis continuum in chassis C1
of rack R1 displays the device as a Continuum chassis drawing.
Group of Racks View

Multiple racks can be displayed as a row or group of racks. A group of racks is
displayed by setting the Graphic field to the keyword value group vrack.
Example: Setting the Graphic field to the value group vrack displays the devices
as a group of racks drawing.
4005743 Rev N 237

Note: Displaying a graphic for a group that has several racks sometimes reduces
the racks to a size that is too small to comfortably view. In this case, you can
break the racks into several groups (so there are fewer racks per group), or you
can create a custom drawing that shows the racks in an overhead view. Refer to
Custom Views later in this section.
Star View
Headend and hub sites typically use the star view graphic to produce an overall
view of the network. A star configuration is displayed by setting the Graphic
field to the keyword value star.
Example: The following graphic is a display of the Graphic field set to the value
star (set in the Details window or via tab panes as preferred).
Note: The first device of the group is put in the center, the rest of the devices is
equally divided over 360 degrees. When there are more than 10 surrounding
devices, these devices are represented as little circles.
Cascade View
Multiple devices can be displayed in a cascade configuration. This is the display
typically used for HFC networks and is configured by setting the Graphic field
to the keyword value cascade.
Example: Setting the Graphic field to the value cascade displays the devices in a
cascade drawing.
238 4005743 Rev N

Custom Views
Instead of viewing your equipment with a standard or directed graphic, you can also
choose to display a custom graphic. As with the other views, a customized view
allows you to see the state of your monitored devices (normal or in alarm).
However, custom views also offer several other advantages.
More realistic device symbols
The ability to show the status of devices that ROSA EM does not monitor, such
as fiber optic cables. This option helps assist in troubleshooting system faults.
Different equipment configurations. Although the flexibility of ROSA EM allows
for several configurations, system overview displays and floor plan displays are
the most common.
Notes:
Before you can view custom graphics, you must install a display file on the
ROSA EM device.
ROSA EM can also run a device script each time it polls a device. If the device is
in alarm or meets certain criteria, ROSA EM takes action described in the script.
Example: If a primary fiber optic path is in alarm, ROSA EM can command a
device to switch to a redundant fiber optic path.
For information on having Cisco create a display file and/or a device script for
you, refer to chapter Customer Information on page 315.
Once you receive the file(s), they can be easily uploaded to the ROSA EM device
with the putscript command that can be found in the ROSA EM Configuration
Tools. For information on how to upload or download scripts and files, please
refer to topic Installation of Scripts on page 283.
Floor Plan
This type of graphic is intended to show a customized floor plan of a headend or
4005743 Rev N 239

hub. Sometimes, a site has so many device racks that a directed view (group
vrack graphic) reduces the racks to a size that is too small to comfortably view
on-screen. In this case, you could use a custom graphic to display an overhead
view of the racks.
Example: A floor plan of a headend or hub might look as the graphic below. In
this example, each row of racks is shown as an aisle.
240 4005743 Rev N

If desired, you could double-click on an aisle to view a group of racks, allowing

you to see which racks belong to the aisle.
4005743 Rev N 241

Configuring ROSA EM Graphics

Introduction
ROSA EM allows you to view graphics at the local PC and group levels. Individual
devices are displayed as members of groups, such as a module that is one of several
within a chassis. The following instructions explain how to configure ROSA EM to
view graphics.
Configuring ROSA EM to View Headend Graphics

Follow the steps below to set up ROSA EM for headend graphics.
1 In the device tree, click on the name of the headend.
Result: The headend tabbed panes are shown on the right.
2 Select the Properties tab.
3 Click on the Value field of the Graphic parameter.

4 In the edit field, type the graphic type you want to display and click on the
Execute button.
Example: To display a group of racks, type group vrack.
242 4005743 Rev N

5 In the device tree, right-click on the name of the headend and click on Graphic
Open.
Result: A graphic of the devices attached to the headend is displayed.
Configuring ROSA EM to View Group Graphics

Follow the steps below to set up ROSA EM for group graphics.
1 In the device tree, click on the group name.
Result: The tabbed panes of the group are shown on the right.
4005743 Rev N 243


Execute button.
Example: To display a rack of 40 rack units (RUs) high, type rack 40.
5 In the device tree, right-click on the group name and click on Graphic Open.
Result: A graphic of the rack and its devices is displayed.
244 4005743 Rev N

Configuring ROSA EM to View Rack Positions

Follow the steps below to configure the vertical rack position of a rack-mounted
chassis or a single device.
1 In the device tree, click on the name of the rack-mounted chassis or single device.
Note: As example the configuration is explained for a rack-mounted chassis.
The configuration for a single device is identical.
Result: The tabbed panes of the chassis are shown on the right.
4005743 Rev N 245


Execute button.
Example: To display a Continuum chassis, type chassis continuum.
5 Click on the Value field of the Rack Vertical Position parameter.

246 4005743 Rev N

6 In the edit field, type the number of rack units (RUs) that should exist from the
bottom of the rack to the bottom of the chassis and click on the Execute button.
Example: The space between the rack and chassis bottom is exactly 17 RUs.
Notes:
- The Rack Vertical Position field is used only when the Graphic field of the
parent group is of the type rack.
- If you do not enter a value, ROSA EM displays the chassis in the first empty
location beginning at the bottom of the rack.
7 In the device tree, right-click on the group name that contains the chassis and
click on Graphic Open.
Result: A graphic of the group and its devices (rack-mounted chassis and single
devices) is displayed.
4005743 Rev N 247

Configuring ROSA EM to View Custom Graphics

Follow the steps below to use custom graphics.
1 In the device tree, click on the group (headend, hub, rack, ) where you want to
use a custom graphic.
Result: The tabbed panes of the group are shown on the right.

4 In the edit field, type file <name> where <name> is the file name of the custom
graphic file and click on the Execute button.
Example: The file hub81_roomA.txt is used as custom graphic file.
Notes:
- If you dont have a custom graphic file and you want to create a display file
for you, refer to Appendix A Customer Information for contact information.
- When you receive a custom graphic file, upload it to the ROSA EM device
with the putscript command, which can be found in the ROSA EM
Configuration Tools.
5 In the device tree, right-click on the device where you added the custom graphic
file and click on Graphic Open.
248 4005743 Rev N

Result: The custom graphic is displayed.
4005743 Rev N 249

Device Graphics Examples

Introduction
The following examples explain how to set up graphics for a system containing a
headend, racks, hubs, nodes and amplifiers.
Headend and Hubs

The device list below has a main headend (group MainHeadend) and three remote
hubs (group A1, group A2, and group A3). All components are placed under a root
(group TheOneAndOnlyRoot).
Note: The headend and hubs are all parents in this example.
Follow the steps below to set up a star graphic for a system containing a headend
and multiple hub sites.
1 In the device tree, click on the name of the root.
4 In the edit field, type star and click on Execute.
5 In the device tree, right-click on the root name and click on Graphic Open.
Result: A graphic displays a star configuration. The headend is placed in the
centre and the hubs are placed around the headend. For an example look at Star
View in the topic Overview of Graphics on page 232.
250 4005743 Rev N

Headend Racks
The device list below has a headend (group MainHeadend) and three racks (groups
R1, R2 and R3).
Notes:
In this example the headend is the parent and the racks are the children.
Rack 1 has several discrete devices and a Continuum chassis, rack 2 has a single
discrete device and rack 3 has no devices or chassis.
Follow the steps below to display the lineup of racks in the headend. For a detailed
procedure, refer to the topic Configure ROSA EM Graphics on page 242.
1 In the device tree, click on the name of the headend.
2 On the Properties tab enter group vrack in the Value field of the Graphic
parameter.
3 On the Properties tab of rack R1, rack R2 and rack R3 set the Value field of the
Graphic parameter to rack or rack xx, with xx being the height of the rack in rack
units (RUs).
4 In the device tree, right-click on the name of the headend and click on Graphic
Open.
Result: A graphic displays a group of racks. For an example look at Group of
Racks View in the topic Overview of Graphics on page 232.
Hub and Nodes

The device list below has a headend (group Headend), a hub (group Hub), and
nodes (group Area1 through group Area7). There are also two racks in the hub
(group R1 and group R2 that are children of group HubRacks).
4005743 Rev N 251

Note: Group Hub is the parent to group HubRacks and group Area1 through Area7.
Follow the steps below to set up a star graphic for a hub with nodes.
1 On the Properties tab of the hub, enter star in the Value field of the Graphic
parameter.
2 In the device tree, right-click on the hub name and click on Graphic Open.
Result: A graphic displays the system as a star. The racks located in the hub are
at the center, while the nodes are placed around the hub.
252 4005743 Rev N

Nodes and Amps

The device list below has a headend (group MainHeadend), a hub (group Hub1),
racks (group Racks), and a node (group A1) with 4 outputs (group province1, group
province2, group province3 and group province4).
1 Group A1 is the parent to a Model 6940 optical node.

2 The Model 6940 optical node has four children.
a Group province1
b Group province2
c Group province3
d Group province4
3 The amplifiers and power supplies in group province1 are placed in cascade.
4 This amplifier also has two children.
a Group city1
b Group city2
5 These lines define cascades a and b.
Follow the steps below to set up a cascade graphic of a node with amplifiers.
1 On the Properties tab of the node A1, enter cascade in the Value field of the
Graphic parameter.
2 In the device tree, right-click on the name of the node and click on Graphic
Open.
4005743 Rev N 253

Result: A graphic displays the node with the amplifiers in cascade.
Note: The indications on the graphic refer to the indications on the device list on the
previous page.
254 4005743 Rev N

Using Graphics in ROSA EM
Using Graphics in ROSA EM

Default Behavior
The ROSA EM applet runs in a web browser window and the graphic displays are
rendered in separate windows. Each opened graphic display creates a new button in
the Taskbar (next to the one of the browser where the applet is running).
Detachment Feature
Sometimes it can be a problem to display the applet browser window and graphic
display(s) at the same time: the graphic display(s) always get(s) behind the browser
window when focusing on the applet (to do some action there like changing a
parameter or opening another graphic display).
To solve this problem the Window menu item in the ROSA EM menu bar contains
the Detachment from browser option.
When enabled, the applet appears in a separate window:

The window only contains the ROSA EM menu bar (no browser menus and
buttons anymore) and has the device tree and tab panes beneath it in two
dialogs.
The window can be used simultaneously with the graphic display(s). The tiling
options in the Window menu can help to arrange the windows.
4005743 Rev N 255


Note: To return to the default behavior, just disable the Detachment from browser
option or on the web browser window click on the text:
The applet is currently detached from the browser. Click here to attach it again.
256 4005743 Rev N

9 Chapter 9
Diverse Notification
Introduction
This chapter explains the concept of Diverse Notification and shows
how to configure the ROSA Element Manager (EM).
In This Chapter
Introduction ......................................................................................... 258
Configuring Diverse Notification ..................................................... 259
Example ................................................................................................ 279
4005743 Rev N 257

Chapter 9 Diverse Notification
Introduction
Concept
The Diverse Notification feature of the ROSA EM system is a way to inform
operators and technicians that an alarm is active on one of the devices managed by
the ROSA EM system. This Alarm Notification can be performed using Email, Pages
(primarily used in US markets), and SMS (Short Message Service, primarily used in
European markets).
When an operator or technician is informed, he can take the appropriate steps to
resolve the alarm situation. When the alarm situation is solved, the operators and
technicians are notified by means of a Cleared Notification.
If the operator or technician determines that the alarm cannot be resolved
immediately, he can acknowledge the alarm. In this case an Acknowledge Notification
will be sent to the operators and technicians.
Since the ROSA EM system is capable to manage a huge number of devices and
some alarm conditions create multiple alarms, Alarm Notification storms can arise.
To prevent Alarm Notification storms, the Diverse Notification feature is provided
with a number of filters:
An Alarm notification is sent only when the severity of the alarm is equal to or
higher than an adjustable severity level (called Notification Severity Level
parameter).
An Alarm notification is sent only when the time the alarm remains active is
higher than a particular adjustable value (called Notification Initial Delay
parameter).
When multiple alarms arise, an Alarm Notification is sent indicating the alarm
with the highest severity.
During a pending alarm situation and not all alarms are acknowledged, the Alarm
Notification can be repeated. The number of times an alarm notification will be
repeated (called Notification Max Sends parameter) and the time between two
consecutive Alarm Notifications (called Notification Repeat Delay parameter) is
adjustable.
When a particular alarm condition arises, not all operators and/or technicians must
be informed. Therefore groups are defined in ROSA EM, which are populated with
Member accounts that define the individuals to be notified and how they are to be
notified.
Each managed device in ROSA EM can specify two of the 16 notification groups to
be sent alarm information when a problem is detected. Each parameter in this
device that can generate an alarm, can be set to one of the two selected groups to
send an alarm notification when that parameter is determined to be in an alarm
condition.
258 4005743 Rev N

Configuring Diverse Notification

Introduction
Most of the effort required to configure ROSA EM for an effective diverse
notification program is performed on the ROSA EM System pages. There are six
steps required to set up ROSA EMs Diverse Notification.
1 Insure that the correct notification options are selected
2 Configure email, paging, and SMS
3 Create member accounts
4 Assign Members to Notification Groups
5 Configure system wide notification rules
6 Assign Notify Sets to devices and parameters
Step 1 - Insure Option Selected

ROSA EM has the capability to send alarm notifications to operators, technicians,
engineers... via pagers, email, and SMS. In ROSA EM the options are set by default
so that email, paging, and SMS are enabled. These options can be checked/changed
with the ROSA EM Configuration Tools by following the next procedure.
getoptions X.X.X.X Y
With:
- Y: the target directory. When no directory is entered, you will be prompted
to provide one. Press [Enter] if you want to save the options file in the
current directory (directory of the ROSA EM Configuration Tools).
4005743 Rev N 259

Result: The options file is saved to your computer and named

X.X.X.X_options.txt with X.X.X.X the IP address of the ROSA EM Device.
Notes:
The log file can be opened using a text editor, for instance Notepad.
4 If you want to change one or more notification settings, do the following:

- Remove the semicolon in front of each of the services that you want to use for
alarm notification. The choices are email, paging and SMS.
- To disable a service insert a semicolon at the beginning of the line of that
notification service.
Note: The email, paging, and SMS option settings are enabled by default.
5 Only when one or more notification settings are changed, enter the following
instructions on the command prompt:
putoptions X.X.X.X Y
With:
- Y: the options file name or the path where the options file is located. When
no directory is entered, you will be prompted to provide one. Press [Enter] if
you want to load the options file in the current directory (directory of the
260 4005743 Rev N

ROSA EM Configuration Tools).

Result: The options file is uploaded to the ROSA EM device with IP address
X.X.X.X, and this device will automatically restart to apply your changes.
ROSA EM - Configuration - Managing Services on page 72.
Step 2 - Configure Email, Paging and SMS

Introduction
The configuration procedure is described separately for each type of service. Note
that the paging service is used on the North American market and the SMS service is
used on the European market.
Configure Email Service

Follow the steps below to configure the email service.
top node of the device tree) and select the Email_Service tab.
Result: The Email_Service tab is displayed.
2 Click on the Value field of the Email Server Authentication parameter.

Result: The Change Parameter Dialog of the Email Server Authentication
This parameter of ROSA EM allows the email function to work with an enhanced
security feature called Plain Authentication that has been added to many email
servers. To determine if plain authentication is required for your email server
use the procedure described in appendix Email Function with Plain
Authentication on page 329.
4005743 Rev N 261

Note: Not all possible email server authentication methods are implemented in
ROSA EM and if the email server uses another authentication method as plain
authentication, ROSA EM will not be able to send emails through that server.
3 If the parameter is changed, click on the Execute button to confirm.
4 Click on the Value field of the Email User ID parameter.
Result: The Change Parameter Dialog of the Email User ID parameter is
displayed.
5 Enter the email user ID that ROSA EM will use to send the email.
Notes:
- If the service provider requires verification of the sending email account, the
email user ID must be a valid account on the sending email server.
- The length of the email user ID is limited to 30 characters.
6 Click on the Execute button to confirm.
7 Click on the Value field of the Email User Password parameter.
Result: The Change Parameter Dialog of the Email User Password parameter is
displayed.
8 Enter the Email User password in the Email User Password box.
consecutively
11 Click on the Value field of the Email Server Name parameter.
Result: The Change Parameter Dialog of the Email Server Name parameter is
displayed.
12 Enter the IP address of the email server that processes the ROSA EM emails.
13 Click on the Execute button to confirm or Cancel to abort.
262 4005743 Rev N

14 Click on the Value field of the Email From Address parameter.

Result: The Change Parameter Dialog of the Email From Address parameter is
displayed.
15 Enter the email from address that has to be displayed in the From field of the
email notification (for instance john.doe@companyname.com).
Notes:
- The length of the email from address is limited to 60 characters.
- If the Email From Address parameter is left blank, the Email User ID will
appear in the From field of the email notification. This results in the user
account followed by @ and the IP address of the smtp server.
- If the Email User ID parameter (see step 6) is also left blank, ROSA EM
automatically inserts the name TNCS@ followed by the IP address of the
smtp server. Note that most smtp servers will not accept this as a user ID.
Configure Paging Service

If you plan to use the paging service, see that you have a PSTN (Public Switched
Telephone Network) modem available. Also keep in mind that the paging service
only works with pagers that support the TAP protocol not all telecom operators
support this protocol. Follow the steps below to configure the paging service.
1 Connect the PSTN modem to one of the ports COM1...COM8.
Note: If you use one of the ports COM5COM8, make sure that it is configured
for RS-232.
top node of the device tree) and select the Paging_Service tab.
Result: The Paging_Service tab is displayed.
3 Click on the Value field of the Pager Port Name parameter.

Result: The Change Parameter Dialog of the Pager Port Name parameter is
displayed.
4 Enter the name of the communication port where the PSTN modem has been
connected to in step 1 of this procedure.
Note: The default communications port is COM2.
4005743 Rev N 263


6 Click on the Value field of the Pager Port Baudrate parameter.
Result: The Change Parameter Dialog of the Pager Port Baudrate parameter is
displayed.
7 Select the communication rate of the paging service.
Note: Contact the paging service provider for the proper setting.
9 Click on the Value field of the Pager Modem Init String parameter.
Result: The Change Parameter Dialog of the Pager Modem Init String
10 Enter the initialization string that ROSA EM will send to the pager modem.
Note: The content of the initialization string depends on the pager modem. The
default setting works for most standard modems, but if it doesnt work properly
refer to the documentation provided with the modem for the correct
initialization string.
12 Click on the Value field of the Pager Modem Dial String parameter.
Result: The Change Parameter Dialog of the Pager Modem Dial String
13 Enter the commands required prior to sending the ATDT command.
Note: Typically this parameter is left blank.
15 Click on the Value field of the Pager Service Max Chars parameter.
Result: The Change Parameter Dialog of the Pager Service Max Chars
16 Enter the maximum number of characters accepted by the paging service.
Notes:
- The default setting of 230 characters works for most pagers.
- The valid range is from 1 to 9999 characters.
18 Click on the Value field of the Numeric Pager Post-dial Delay parameter.
Result: The Change Parameter Dialog of the Numeric Pager Post-dial Delay
19 Enter the delay in seconds between the moment when a connection is made and
the moment when ROSA EM begins with sending the message.
Notes:
- The default delay is 5 seconds.
- The valid range is from 1 to 99 seconds.
264 4005743 Rev N


21 Click on the Value field of the Numeric Paging Message parameter.
Result: The Change Parameter Dialog of the Numeric Paging Message
22 Enter the digits that ROSA EM will use when sending an alarm notification to a
pager.
Notes:
- The number of digits is limited to 10.
- If this parameter is left blank, ROSA EM calculates its own code to send to
the pager. Although the code identifies the device that is in alarm, it might
be less meaningful to you than a number you enter yourself. Also, the
calculated code often begins with a zero, which is prohibited by some pagers.
Example: You might choose to enter the phone number of the site where the
devices are located. This way, the person who receives the paging is able to
easily identify the site that is in alarm.
Configure SMS Service

If you plan to use the SMS service, see that you have a GSM modem available with a
SIM card to send SMS messages (for example Siemens MC35). Follow the steps
below to configure the SMS service.
top node of the device tree) and select the SMS_Service tab.
Result: The SMS_Service tab is displayed.
2 Click on the Value field of the SMS Service Provider Number parameter.
Result: The Change Parameter Dialog of the SMS Service Provider Number
3 Enter the number that ROSA EM dials to access the SMS service provider.
5 Click on the Value field of the SMS Pin Code parameter.
Result: The Change Parameter Dialog of the SMS Pin Code parameter is
displayed.
6 Uncheck the Require complex password check box.
4005743 Rev N 265

7 Enter the PIN (Personal Identification Number) code that ROSA EM sends to the
SMS service provider.
8 Repeat the PIN (Personal Identification Number) code in the Repeat Value box.
9 Click on the Execute button to confirm or Cancel to abort.
Result: The PIN code is recorded, but will be displayed as **** for security
reasons.
10 Click on the Value field of the SMS Port Name parameter.
Result: The Change Parameter Dialog of the SMS Port Name parameter is
displayed.
11 Enter the name of the communication port ROSA EM uses to dial the SMS
service.
Notes:
- Valid communication ports are those with a GSM modem attached.
- The default communications port is COM2.
- If the GSM modem is connected to one of the ports COM5COM8, make
sure that the port is configured for RS-232.
Step 3 - Create Member Accounts

General
Each operator, technician, engineer, manager... that should be notified of an alarm
condition needs to have a Member account. Up to 64 separate Member accounts can
be created in ROSA EM and each account can be notified via email, pager and/or
SMS. To create new or edit existing member accounts, follow the procedure below.
top node of the device tree) and select the Member_Information tab.
Result: The Member_Information tab is displayed.
266 4005743 Rev N

2 Click on the Value field of the Member n Name parameter (with n between 1
and 64) where you want to create a new or edit an existing member account.
Result: The Change Parameter Dialog of the Member n Name parameter is
displayed.
3 Enter or change the member name.
Note: The length of the member name is limited to 12 characters.
5 Click on the Value field of the Member n Notification Type parameter (with n
between 1 and 64) of the same member account as in step 2.
Result: The Change Parameter Dialog of the Member n Notification Type
6 Select one of the following notification types.
Types Description
None No additional entry field will appear at the member account.
Page An additional entry field will appear at the member account, allowing you
to (dis)activate the paging notification.
4005743 Rev N 267

Types Description
Email An additional entry field will appear at the member account, allowing you
to (dis)activate the email notification.
SMS An additional entry field will appear at the member account, allowing you
to (dis)activate the SMS notification.
All-Config Additional entry fields will appear at the member account, allowing to
(dis)activate paging, email and SMS notification.
Notes:
- The additional entry fields only appear after an Execute command.
- Member accounts that will use two of the notification methods to receive
alarm information, should select All-Config and only activate the two
desired methods.
- The activation procedure is explained separately for each method further in
this sub topic.
Activate Paging for a Member Account

Follow the procedure below to activate paging for a member account.
1 Click on the Value field of the Member n Paging Active parameter (with n
between 1 and 64).
Result: The Change Parameter Dialog of the Member n Paging Active

2 Select Yes to activate paging for this member account.
Result: Two additional entry fields appear to configure paging.
268 4005743 Rev N

4 In case of an alphanumeric pager, click on the Value field of the Member n

Pager Access Number parameter (with n between 1 and 64).
Otherwise proceed with step 7.
Result: The Change Parameter Dialog of the Member n Pager Access Number
5 Enter the pager access number.
7 Click on the Value field of the Member n Pager Number parameter (with n
between 1 and 64).
Result: The Change Parameter Dialog of the Member n Pager Number
8 Enter the pager number.
Result: The member account is configured to receive paging notifications of
alarm conditions on ROSA EM.
Follow the procedure below to inactivate paging for a member account.
1 Click on the Value field of the Member n Paging Active parameter (with n
between 1 and 64).
Result: The Change Parameter Dialog of the Member n Paging Active

2 Select No to inactivate paging.
Result: Paging is inactivated for this member account.
Activate Email for a Member Account

Follow the procedure below to activate email for a member account.
1 Click on the Value field of the Member n Email Active parameter (with n
between 1 and 64).
4005743 Rev N 269

Result: The Change Parameter Dialog of the Member n Email Active parameter
is displayed.
2 Select Yes to activate email for this member account.
Result: An additional entry field appears.
4 Click on the Value field of the Member n Email Address parameter (with n
between 1 and 64).
Result: The Change Parameter Dialog of the Member n Email Address
5 Enter the members email address.
Result: The member account is configured to receive email notifications of alarm
conditions on ROSA EM.
Follow the procedure below to inactivate email for a member account.
1 Click on the Value field of the Member n Email Active parameter (with n
between 1 and 64).
Result: The Change Parameter Dialog of the Member n Email Active parameter
is displayed.
2 Select No to inactivate email.
Result: Email is disactived for this member account.
Activate SMS for a Member Account

Follow the procedure below to activate SMS for a member account.
1 Click on the Value field of the Member n SMS Active parameter (with n
between 1 and 64).
270 4005743 Rev N

Result: The Change Parameter Dialog of the Member n SMS Active parameter
is displayed.
2 Select Yes to activate SMS for this member account.
Result: An additional entry field appears.
4 Click on the Value field of the Member n SMS GSM Number parameter (with n
between 1 and 64).
Result: The Change Parameter Dialog of the Member n SMS GSM Number
5 Enter the members GSM phone number.
Result: The member account is configured to receive SMS notifications of alarm
conditions on ROSA EM.
Follow the procedure below to inactivate SMS for a member account.
1 Click on the Value field of the Member n SMS Active parameter (with n
between 1 and 64).
Result: The Change Parameter Dialog of the Member n SMS Active parameter
is displayed.
2 Select No to disactivate SMS.
Result: SMS is disactived for this member account.
Activate Paging, Email and / or SMS for several Member Accounts

Repeat one or more activation procedures for every member account you want to
configure. Member accounts that will use two of the notification methods to receive
alarm information, should select All-Config and only activate the two desired
methods.
4005743 Rev N 271

Example:
Step 4 - Assign Members to Notification Groups

There are two basic steps for the creation of Notification Groups:
1 Give the group a name
2 Identify the members of the group
Follow next procedure to assign members to any of the 16 available Notification
Groups.
top node of the device tree) and select the Notify_Group tab.
Result: The Notify_Group tab is displayed.
272 4005743 Rev N

2 Click on the Value field of the Notify Group n Name parameter (with n between
1 and 16) where you want to create a new or edit an existing Notification Group.
Result: The Change Parameter Dialog of the Notify Group n Name parameter is
displayed.
3 Enter or change the name of the Notification Group.
Note: The length of the group name is limited to 12 characters and should not
contain any spaces.
Example:
5 Click on the Value field of the Notify Group n Members parameter (with n
between 1 and 16) of the same Notification Group as in step 2.
Result: The Change Parameter Dialog of the Notify Group n Members
6 Enter the member name or the associated member number for each member that
needs to be part of this Notification Group.
Notes:
- When you enter a member name, be careful to use exactly the same name as
it is specified on the Member_Information tab page. ROSA EM will not
perform name checking and no warning is given when an invalid name is
entered.
- Separate each name or number with a comma and/or a space.
- The length of the input data is limited to 65 characters.
Example:
8 Repeat steps 2 to 7 for each Notification Group you want to configure.

Example:
4005743 Rev N 273

Step 5 - Configure System Wide Notification Rules

Follow the next procedure to configure system wide notification rules for alarms.
top node of the device tree) and select the Notification_Information tab.
Result: The Notification_Information tab is displayed.
2 Click on the Value field of the Notification Configuration parameter.

Result: The Change Parameter Dialog of the Notification Configuration
3 Select one of the choices.
- None: No alarm notifications will be sent from this ROSA EM server and/or
client.
- Local or System: Only alarm notifications for devices directly managed by this
ROSA EM server will be sent.
5 Click on the Value field of the Notification Initial Delay parameter.
Result: The Change Parameter Dialog of the Notification Initial Delay
6 Set the number of seconds ROSA EM waits before sending an alarm notification.
Notes:
- This feature is useful in reducing or eliminating nuisance alarm notifications,
such as alarms for intermittent communication.
- The valid range is from 0 to 99 seconds, default value is 30.
8 Click on the Value field of the Notification Repeat Delay parameter.
Result: The Change Parameter Dialog of the Notification Repeat Delay
9 Set the number of seconds ROSA EM waits for an alarm to be acknowledged
before resending an alarm notification.
Note: The valid range is from 10 to 999 seconds, default value is 60.
274 4005743 Rev N

11 Click on the Value field of the Notification Max Sends parameter.

Result: The Change Parameter Dialog of the Notification Max Sends parameter
is displayed.
12 Enter the maximum number of times ROSA EM will send an alarm notification
for a given alarm.
14 Click on the Value field of the Notification Max Attempts parameter.
Result: The Change Parameter Dialog of the Notification Max Attempts
15 Enter the maximum number of times ROSA EM will attempt to send an alarm
notification when an email, paging or SMS failure occurs.
17 Click on the Value field of the Notification Severity Level parameter.
Result: The Change Parameter Dialog of the Notification Severity Level
18 Set the minimum alarm severity level that prompts ROSA EM to send an alarm
notification. ROSA EM will send an alarm notification for each alarm that meets
or exceeds the specified severity level.
Note: A selection can be made between Minor, Major and Critical (ordered in
increasing severity level) with Major as default setting.
Step 6 - Assign Notify Sets to Devices and Parameters

ROSA EM can be configured to have two different Notification Groups per
individual device or group device.
Note: For more details, please refer to the topic Introduction on page 258.
The following procedure describes how to configure two different Notification
Groups per individual device.
1 Open the ROSA EM GUI; in the browser frame browse to a device and select the
Properties tab.
Result: The device Properties tab is displayed.
4005743 Rev N 275

2 Click on the Value field of the Notify Set A parameter.

Result: The Change Parameter Dialog of the Notify Set A parameter is
displayed.
3 Enter the name of the Notification Group.
Note: When you enter a name, be careful to use exactly the same name as it is
specified on the Notify_Group system tab page. ROSA EM will not perform
name checking and no warning is given when an invalid name is entered.
5 Click on the Value field of the Notify Set B parameter.
Result: The Change Parameter Dialog of the Notify Set B parameter is
displayed.
6 Enter the name of another Notification Group.
Note: When you enter a name, be careful to use exactly the same name as it is
specified on the Notify_Group system tab page. ROSA EM will not perform
name checking and no warning is given when an invalid name is entered.
Example: Both Notify Set parameters are configured.
276 4005743 Rev N

8 Select the Alarms tab of the device.

Result: The device Alarms tab is displayed.
9 To select a Notify Set for an alarm-able parameter, right-click on the Parameter

or Value field and select Alarm Profile.
Result: The Alarm Profile dialog of the parameter is displayed.
The following illustration shows the alarm profile dialog of the Loss of Video
alarm.
4005743 Rev N 277

10 Under Alarm Parameters, select a Severity level.
Notes:
- Ordering is from lowest (Warning) to highest severity level (Critical).
- Only the severity levels Minor, Major, and Critical generate an alarm that will
trigger a notification operation.
- The selected Severity level should be the same or higher as the Notification
Severity Level defined on Notification_Information tab of ROSA EM.
- Refer to topic Step 5 - Configure System Wide Notification Rules on page 274 for
more information.
11 Under Alarm Parameters, specify the Notify Set that will be notified in case of
an alarm condition.

Result: The members of the Notification Group specified in the selected Notify
Set will receive a notification in case of an alarm condition.
278 4005743 Rev N

Example
Example
In case a device generates an alarm the following events will take place:
A check is done to see if the severity level of the alarm is the same or higher as
the severity level specified on the Notification_Information tab of ROSA EM.
With a correct severity level, Notify Set B will be triggered.
Notify Set B refers to the Notification Group Engineers.
The Notification Group Engineers contains one member called Jason.
4005743 Rev N 279

Member Jason will receive a paging and an email notification of the alarm.
Below are some examples of an email:

Alarm Acknowledged
Alarm Cleared
280 4005743 Rev N

10 Chapter 10
Scripting in ROSA EM
Introduction
This chapter describes what kind of scripting possibilities exist on the
ROSA Element Manager (EM).
In This Chapter
Introduction ......................................................................................... 282
Installation of Scripts .......................................................................... 283
Custom Scripts .................................................................................... 285
4005743 Rev N 281

Chapter 10 Scripting in ROSA EM
Introduction
A ROSA EM script is a text file containing series of commands and can be written
using ROSA EM's own scripting language or the Python Programming Language.
Scripts are used for different applications within ROSA EM:
Device Scripts
Every time a devtype is polled, a script can be executed. One of the settings of a
device in ROSA EM is the parameter Script. Here you can specify the name of
the script to run after each poll-action.
Example: A typical application for such a script might be to set one or more
digital or analog outputs based on the state of an input (I/O automation).
Pre-backup, Backup, and Restore Scripts
ROSA EM provides in backup of failing devices. The general backup mechanism
(state-machine, checking, backup/restore linked devices, retry if needed...) is
part of the ROSA EM core. The actual backup (transfer of the settings,
enable/disable outputs...) is done by a script. If custom backup scenarios are
needed, a custom script can be developed. Pre-backup scripts allow
implementing specific conditions that should be met before backup transitions
can proceed.
Trap Scripts
Trap scripts allow implementing specific actions that need to be done when
receiving traps from the device.
Alarm Correlation Scripts
These scripts allow bundling multiple alarms to a single alarm. To enable the Alarm
Correlation feature, an Alarm Correlation script should be present and the feature
should be switched on. Switching on or off the Alarm Correlation feature can be
done by setting the Alarm Correlation Control parameter on the Alarm-Processing
tab page (ROSA EM device) to On or Off.
When a ROSA EM system leaves our assembly line, the device is already provided
with a number of scripts. Self made scripts or scripts received from our customer
services department need to be uploaded first to the ROSA EM device before they
can be used. Uploading a script to a ROSA EM system can be done using the ROSA
EM Configuration Tools or via any FTP client. More information can be found in
topic Installation of Scripts on page 283. Note that device scripts are of type devscripts,
backup and restore scripts are respectively of type backup and restore.
282 4005743 Rev N

Installation of Scripts
Installation of Scripts
The following steps explain how to upload a script file to a ROSA EM device.
putscript X Y Z.Z.Z.Z
With:
- X: the script file (name and .txt/.py extension)
- Y: the script type (backup, restore, alarmcorrelationscripts, trapscipts,
devscripts or displays)
- Z.Z.Z.Z: the IP address of the ROSA EM device
Result: The script file is uploaded to the ROSA EM device with IP address
Z.Z.Z.Z in the folder specified with script type.
Environment window.
The following steps explain how to view the scripts installed on a ROSA EM device.
getscript X.X.X.X Y Z
With:
- Y: the script type (backup, restore, alarm correlation, devscripts or displays)
- Z: the name of the script (optional)
4005743 Rev N 283

Chapter 10 Scripting in ROSA EM
Result:
- When the name of the script is not defined, the getscript command will
display all the scripts installed on the ROSA EM device with IP address
X.X.X.X that are of the same type as specified in Y.
- When the name of the script is specified, the getscript command downloads
the script from the ROSA EM device with IP address X.X.X.X of which the
type and the name are the same as specified in Y and Z.
Note: For the use of the commands and examples just type putscript or getscript at
the command prompt and press [Enter].
Environment window.
284 4005743 Rev N

Custom Scripts
Custom Scripts
Scripts can be developed on request. For development of custom scripts please
contact our Customer Service. Contact information of our assistance centers can be
found in appendix Customer Information on page 315.
4005743 Rev N 285

11 Chapter 11
Backup Operation
Introduction
This chapter contains the necessary information to integrate the
ROSA Element Manager into a backup application.
In This Chapter
Introducing the Backup Functionality ............................................. 288
Configuring the Backup Parameters ................................................ 294
4005743 Rev N 287

Chapter 11 Backup Operation
Introducing the Backup Functionality

General
The ROSA Element Manager acts as the functional unit within a backup application.
When the ROSA EM device is triggered from for instance a failing device, a
particular backup sequence is started to transfer the functionality of the failing
device to a backup device. The ROSA Element Manager supports two backup
scenarios:
The Regular Backup scenario
The Floating Backup scenario
Regular Versus Floating Backup Applications

About Regular Backup
In a Regular Backup application, the functionality of a failing device can be taken
over by a backup device that is assigned to this failing device. Once the main to
backup transition is executed, the backup system waits until a backup-to-main
trigger is given (device restoration). The ROSA EM system keeps track of which
device is in backup for which other device.
About Floating Backup
In Floating Backup applications the operator defines to which pool of devices
each device belongs to, and whether it is in Active, or Inactive state at startup.
Whenever a main to backup transition is triggered, the backup system can
allocate as backup device any of the Inactive devices belonging to the same pool
as the failing device.
During the main to backup transition the previously active device becomes either
Inactive (=free to be used in another backup transition) or Excluded (=not to be
used; needs operator intervention to revert the device to Inactive). The state it is
set to depends solely on a parameter in the system device.
In a Floating Backup application and after a backup transition, device restoration
is not needed.
Backup Trigger
A backup transition can be triggered by a device alarm of which Backup-on-Alarm is
set (called Failure Backup) or via a manual backup transition request (called
Maintenance Backup). Once the element manager is triggered, the device will go
into backup state when the following conditions are met:
The backup feature of the ROSA EM device is enabled. More information
concerning enabling the backup feature can be found in topic Backup Operation
on page 287.
288 4005743 Rev N

The primary device is backup-capable and configured properly.

The standby device accepts the service transfer.
When the ROSA EM system is triggered to start a backup transition the system
performs a configuration check, looks for a backup device, and updates its internal
administration. When the ROSA EM system determines that the backup transition
can be continued, a number of scripts are executed. These scripts implement the
actual backup action.
A restore transition is similar (regular backup applications only). If the restore mode
is set to Automatic and no alarms of which Backup-on-Alarm is set are active on the
primary device, the ROSA EM system performs a restore transition. If the restore
mode is set to Manual, the operator has to start the restore transition, even if no more
alarms are active.
About Scripts
As described in previous subtopics, the scenarios used by the ROSA EM system to
backup and to restore devices is script driven, meaning particular scripts are
required to perform a transition. In general there are two or three scripts involved
for backup and restore:
One for the backup transition
One for the restore transition (Regular Backup scenario only)
One for checking whether the backup transition can proceed (optionally). This
script (called Pre Backup Check script) allows implementing specific conditions
that should be met before a backup transition can proceed. Such a script is used
for both an automatic backup and a maintenance backup.
For backup applications containing Stellar or Stellar XT MPEG-2 Decoder devices,
Pyxis ATSC MPEG-2 Encoder devices, and Capella Audio Codec devices, additional
scripts are required. These scripts are needed to handle the input- and output
routers.
Scripts can be written using ROSA EM's native scripting language or using the open-
source scripting language PYTHON. For more information concerning scripts,
please refer to chapter Scripting in ROSA EM on page 281.
Backup Devices
A backup device is a device that takes over the functionality of a failing device. The
ROSA EM software uses the following logic to determine the backup device:
For Regular Backup applications, the list of backup devices is always evaluated
in the order as specified. The ROSA EM software will try the device as specified
in Backup device. If for some reason this device cannot be used, the ROSA EM
software will try the device as specified in Backup Device 2, and so on.
4005743 Rev N 289

The ROSA EM system will try to find a backup device that is not yet in use to
backup a failing device. If not available, it will look for the backup device in use
for the failing main device with the lowest priority (Regular Backup scenario
only). If the priority of the failing device in backup state is less than the priority
of the failing device that should be backed up, then the backup device of the
failed device with lower priority will be used. Before starting this backup
transition, a restore transition will be executed on the device with lower priority.
For Floating Backup applications, an inactive device belonging to the
corresponding pool will be used (the order of selection is the same as the order in
the devlist).
When a backup device is not responding due to a communication status alarm or
the backup device is set to Off-Scan or is in Maintenance Mode, the backup
device will be skipped.
When a backup device has an active alarm with backup-on-alarm flag set and the
Check Backup Device Alarmed (Regular Backup) or Check Floating Device Alarmed
(Floating Backup) is enabled, the device will be skipped.
For Regular Backup applications, the ROSA EM system allows defining 10 backup
devices to backup a particular device.
Linked Devices
Linked devices are devices that will be switched into backup as well if the device
specifying them goes into backup. The maximum number of linked devices which
can be specified for a device is 8.
Notes:
Links are hierarchically evaluated, meaning if a device has a number of linked
devices and these linked devices have linked devices as well, the linked devices
of the linked devices will be switched into backup (/restore) as well when the
device is backed up (/restored).
Restoring a linked device restores the main device as well.
For Floating Backup applications, the topology of the chains with linked devices
should be identical. For instance: if the active link contains 2 devices, one being
member of pool1 and another being member of pool2, then the inactive chain
should contain also devices with the same 2 pools being configured.
Keeping the Device Chain

If, in a backup application, series of primary linked devices (further called device
chain) can be backed up by multiple backup device chains (for instance in a M/N
backup application) the ROSA EM system needs to know that a device chain with a
failing device must be backed up by linked devices belonging to the same backup
chain.
290 4005743 Rev N

When the Keep Chain functionality of ROSA EM is disabled, the ROSA EM system
will provide a backup device for each primary device without taken the chains of the
backup devices into account. When in the example below device 2a fails, it can be
possible that device 1a, 2a, and 4a are backed up by devices from backup chain B
and device 3a by a device from backup chain C.
The backup devices that are being activated will be determined by a number of
parameters, like order in the backup list, Checked Backup Device Alarmed
parameter...
When the Keep Chain functionality is enabled and device 2a fails, then the backup
devices are chosen in such a way that all activated backup devices will belong to the
same backup chain of linked devices, in the example below by devices of backup
chain b.
The chain of backup devices that will be chosen depends again on a number of
parameters, the first one being the order of the backup devices as mentioned on the
device that was triggered for backup. But also the fact whether a backup device has
an alarm state might affect the chain choice.
Licensing
The ROSA EM system integrated into backup applications needs specific licenses:
For backup applications with Continuum DVP Encoder Model D9030, D9032,
D9034, D9050, and D9054 devices a Headend or General license is required.
For backup applications with DQA, XDQA, XDQA24, RFGW-1, Stellar or Stellar
XT MPEG-2 Decoder devices, Pyxis ATSC MPEG-2 Encoder devices, or Capella
4005743 Rev N 291

Audio Codec devices a Hub, Headend, or General license is required.

Notes:
A ROSA EM device with Transmitter Site license cannot be integrated into a
backup application.
Whether backup for a certain device is licensed can be seen on the Backup page
of the device. If the Backup Licensed parameter is set to Yes, the ROSA EM can
be integrated into a backup application with such devices. If set to No, a license
upgrade/change of the ROSA EM system is required.
Backup Indication
In the device tree, a backup or restore transition in progress is indicated by the name
of the main device in vignette. A backup transition is indicated by the background
color that fades out from the solid backup color (by default magenta) to white and a
restore transition by background color that fades out from white to the solid backup
color.
Backup transition in progress Restore transition in progress
In a regular backup application the main as well as the backup device is colored with
the backup color (by default magenta) after a backup transition.
In a floating backup application, the activated device has the same appearance as
any other active device once the backup transition is completed. The only way the
inactivated device might differ from an inactive device is the fact that the Floating
Device State parameter could be set to Excluded, where free devices are put in
Inactive. In the device tree, the Floating Device State of a device is indicated using
the following icons:
Icon Description
Device in Active state
292 4005743 Rev N

Icon Description
Device in Inactive state, free to be used as backup device
Device in Excluded state, not to be used as backup device
To provide status updates to SNMP Managers, the following Trap is sent if Floating
Backup or Floating Device State is changed: saTncsFloatingBackupConfigChangeTrap.
4005743 Rev N 293

Configuring the Backup Parameters

Introduction
This topic describes how to configure the backup parameters on the ROSA EM for
Regular Backup and Floating Backup operation.
Note: Specific backup applications are described in separately published application
notes. For more information, please contact your customer service representative.
Configuring the Backup Parameters for Regular Backup Applications

Introduction
This topic outlines the backup related parameters of the ROSA EM system and
devices participating into a Regular Backup application. The following list describes
the backup related parameters of the devices.
Backup State: This parameter can be used to trigger a backup/restore transition
by changing this parameter to Backup or Inactive.
Backup Mode: A backup transition can be triggered by a device (for instance by
an alarm) or via a manual backup transition request. For some purposes (for
instance during configuration) it can be useful to switch off backup transition
triggered by a device alarm. This parameter determines if a backup transition
will be triggered if a device alarm occurs (Automatic) or not (Manual).
Restore Mode: When the backup is no longer required (for instance the device
alarm is cleared) the service can be restored to the primary (main) device. This
restore transition can be done automatically or manually depending on the
setting of this parameter. We recommend against using the automatic restore
mode in regular backup applications.
Backup Priority: When the ROSA EM system has to backup a device, the system
looks for free backup devices. As soon as a free backup device is found, the
backup transition is started. When no free backup devices are found, the system
compares the priorities of the failing devices. If the priority of the failing device
is lower than the priorities of the failed devices in backup state, the failing device
will not be backed up. Otherwise the backup device of the failed device with the
lowest priority is used to backup. The Backup Priority parameter tells ROSA EM
what the device's importance is compared to other devices in the application.
- The valid range of priority numbers is 0 to 99 (0 = disabling the backup
functionality of the device)
- 1 indicates the highest priority, 2 indicates the next highest priority, and so
on.
294 4005743 Rev N

Backup By Reconfiguration: In a backup application, particular devices need a

reconfiguration if a backup situation arises, for instance the Redus MKII Source
Selector device.
Backup Enable: This parameter switches on or off the backup functionality of
the device.
Keep Chain: This parameter enables or disables the keep chain functionality, see
topic Keeping the Device Chain on page 290.
Integrated Backup Script: for future use.
Pre Backup Check Script: The Pre Backup Check Script parameter can be used
to perform additional checks to determine if a backup transition is allowed or
not. A Pre Backup Check Script can allow the backup to continue, abort the
backup and send out a Backup failed trap to the SNMP managers or cancel a
backup cycle because the backup is not needed or must be delayed. In this last
case, no trap is sent out to the SNMP managers. For example, the backup of an
encoder with redundant outputs might be canceled because only one of the IP
outputs is failing. This parameter determines which pre backup check script
must be executed. Leave this parameter empty if no pre backup script must be
executed.
Backup Script: This parameter determines the script that must be executed
during the backup transition. The list with backup scripts can be found in topic
Backup Scripts on page 322.
Restore Script: This parameter determines the script that must be executed
during the restore transition. The list with restore scripts can be found in topic
Backup Scripts on page 322.
Backup Device X: ROSA EMs backup functionality allows multiple backup
device assignments to a primary device. These parameters determine the backup
devices for this device.
Linked To Device X: Certain applications require a backup scenario where 2 or
more devices should be backed up together. Such a backup scenario is often
necessary when multiple devices are linked together and function as one unit.
These parameters determine the devices that must be backed up together with
this device.
Backup Test Mode: This parameter can be used to test the backup application.
More information about testing the backup application can be found in topic
Testing the Backup Application on page 308.
Floating Backup: This parameter determines the backup scenario for the
application and should be disabled for regular backup applications.
Additional Switch Over Delay: This parameter can be used to achieve a
seamless transition during a maintenance backup. This additional delay must be
defined for the backup devices.
4005743 Rev N 295

Note: The Additional Switch Over Delay parameter is only applicable for
Continuum DVP encoder devices.
The following ROSA EM system parameters must be configured when the Regular
Backup scenario is used.
Check Backup Device Alarmed: When this parameter is enabled, then before a
main to backup transition will be started, the ROSA EM system checks if the
backup device has no alarms active for which Backup on Alarm is enabled. If so,
the transition will not be started.
When the Check Backup Device Alarmed parameter is disabled, the ROSA EM
system will start the transition, even when the backup device has one or multiple
active alarms for which Backup on Alarm is enabled.
Configuring the Device Backup Parameters

The following steps explain how to configure the backup related parameters of a
device.
1 Open the ROSA EM GUI and in the device tree, browse to the page of the device
in question and click on the Backup tab.
Result: The Backup tab is displayed.
2 Click on the Value field of the Floating Backup parameter.
Result: The Change Parameter Dialog of the Floating Backup parameter is
displayed.
3 Select Disabled and press the Execute button.
Result: The Backup tab is filled up with parameters for Regular Backup.
296 4005743 Rev N

Note: The picture above shows the Backup tab of an encoder. The Backup tab of
other devices is similar.
4 Click on the Value field of the Backup Enable parameter.
Result: The Change Parameter Dialog of the Backup Enable parameter is
displayed.
5 Select Enabled to switch on the backup functionality of the device and click on the
6 Click on the Value field of the Backup Mode parameter.
4005743 Rev N 297

Result: The Change Parameter Dialog of the Backup Mode parameter is

displayed.
Manual: only a manual backup request will trigger a backup transition.
Automatic: a manual backup request or a device alarm will trigger a backup
transition.
8 Press the Execute button.
9 Click on the Value field of the Restore Mode parameter.
Result: The Change Parameter Dialog of the Restore Mode parameter is
displayed.
Manual: only a manual restore request will trigger a restore transition.
Automatic: a restore transition will be triggered after a manual restore request
or when there are no alarms anymore of which Backup-on-Alarm flag is set.
12 Click on in the Value field of the Backup Priority parameter.
Result: The Change Parameter Dialog of the Backup Priority parameter is
displayed.
13 Enter a priority number and click on the Execute button to confirm.
14 Click on in the Value field of a Backup by Reconfiguration parameter.
Result: The Change Parameter Dialog of the Backup by Reconfiguration
parameter in question is displayed.
15 Select Yes to switch on the Backup by Reconfiguration or No to switch off the
function.
17 Click on in the Value field of a Keep Chain parameter.
Result: The Change Parameter Dialog of the Keep Chain parameter is
displayed.
18 Select Disabled or Enabled for respectively disabling or enabling the Keep Chain
functionality and click on the Execute button to confirm.
19 Click on the Value field of the Pre Backup Check Script parameter.
Result: The Change Parameter Dialog of the Pre Backup Check Script
20 Enter the name of the script that must be executed before performing the backup
transition and press the Execute button to confirm. When no pre backup check
script must be executed, clear this parameter
21 Click on the Value field of the Backup Script parameter.
Result: The Change Parameter Dialog of the Backup Script parameter is
displayed.
298 4005743 Rev N

22 Enter the name of the script that must be executed during the backup transition
23 Click on the Value field of the Restore Script parameter.
Result: The Change Parameter Dialog of the Restore Script parameter is
displayed.
24 Enter the name of the script that must be executed during the restore transition
25 Click on in the Value field of a Backup Device x parameter.
Result: The Change Parameter Dialog of the Backup Device x parameter in
question is displayed.
26 Enter the name of the backup device.
The device name must be unique, meaning there cant be another device
integrated in the ROSA EM system with the same name. If necessary, rename
the device to make it unique. Enter enough characters to ensure that the
name is completely unique.
If multiple devices with the same device name but categorized in different
groups are connected to the ROSA EM device, specify the device by using its
hierarchical name. This hierarchical name is the concatenation of the names
of all groups starting from the top node of the tree up to the device name
(included) separated by dots (for instance group1.group2.device)
27 Click on the Execute button.
28 Repeat steps 24 up to 26 for all backup devices that must be assigned to the
corresponding device.
29 Click on in the Value field of a Linked to Device x parameter.
Result: The Change Parameter Dialog of the Linked to Device x parameter in
30 Enter the name of the device that must be linked.
Notes:
- The device name must be unique, meaning there cant be another device
- If multiple devices with the same device name but categorized in different
(included) separated by dots (for instance group1.group2.device).
- Bi-directional device links are allowed. This means that a configuration can
be made with device A, a linked device of device B and vice versa. When a
backup transition is triggered for one device, the other device will also be
backed up.
4005743 Rev N 299

Tip: The backup configuration can be facilitated by the next and previous
keywords. Previous refers to the device immediately preceding this device and
next refers to the device immediately succeeding this device in the device list or
browser tree.
32 Repeat step 28 up to 30 for all devices that should be linked.
33 Click on the Value field of the Additional Switch Over Delay parameter.
Result: The Change Parameter Dialog of the Additional Switch Over Delay
34 Enter the desired delay value (in milliseconds) to achieve a seamless backup
transition and press the Execute button to confirm.
Note: Repeat this procedure for all devices participating into the backup application.
Tip: During performing this procedure, the Backup Configuration Error Hint
parameter gives additional information about the configuration. More information
about these hints can be found in topic Testing the Backup Configuration on page 308.
Configuring the ROSA EM Backup Parameters

The following steps explain how to configure the backup related parameters of the
ROSA EM which are applicable for all integrated devices.
top node of the device tree) and select the Device Backup tab.
2 Click on the Value field of the Check Backup Device Alarmed parameter.
Result: The Change Parameter Dialog of the Check Backup Device Alarmed
3 Select Enabled or Disabled and press the Execute button.
300 4005743 Rev N

Configuring the Backup Parameters for Floating Backup Applications

Introduction
This topic describes the backup related parameters of the ROSA EM system and
devices participating into a Floating Backup application and the procedures to
configure these parameters. The following list describes the parameters of the
devices.
Backup State: This parameter can be used to trigger a backup transition by
changing this parameter to Backup.
Backup Mode: A backup transition can be triggered by a device (for instance by
an alarm) or via a manual backup transition request. For some purposes (for
instance during configuration) it can be useful to switch off backup transition
triggered by a device alarm. This parameter determines if a backup transition
will be triggered if a device alarm occurs (Automatic) or not (Manual).
Backup By Reconfiguration: Particular devices need a reconfiguration if a
backup situation arises.
Keep Chain: This parameter enables or disables the keep chain functionality, see
topic Keeping the Device Chain on page 290.
Backup Enabled: This parameter switches on or off the backup functionality of
the device.
Integrated Backup Script: for future use
Pre Backup Check Script: A Pre Backup Check Script can be used to perform
additional checks to see if a backup transition is allowed. If a Pre Backup Check
Script is assigned, the script will be executed before trying to perform the backup
transition.
Backup Script: This parameter determines which script must be executed during
the backup transition. The following list gives the scripts supported by ROSA
EM for floating backup.
- bu903x.py: for D9030, D9032, D9034, D9054 and D9022 with router and
switch
- budqa.py: for (x)dqa(24) family.
Linked To Device X: Certain applications require a backup scenario where 2 or
more devices should be backed up together. Such a backup scenario is often
necessary when multiple devices are linked together and function as one unit.
These parameters determine the devices that must be backed up together with
this device.
Backup Test Mode: This parameter can be used to test the backup application.
More information about testing the backup application can be found in topic
Testing the Backup Application.
4005743 Rev N 301

Floating Backup: This parameter determines the backup scenario for the
application and should be Enabled for floating backup.
Floating Device State: reflects the current state of the device (Active, Inactive, or
Excluded). It can be used to configure the initial state of the device.
Floating Pool Name: This parameter determines to which pool the device
belongs to.
Additional Switch Over Delay: This parameter can be used to achieve a
seamless transition during a maintenance backup. This additional delay must be
defined for backup devices.
Note: The Additional Switch Over Delay parameter is only applicable for
Continuum DVP encoder devices.
The following ROSA EM parameters must be configured when the floating backup
scenario is used.
Set Deactivated Floating Backup Devices: This parameter determines the state
(Floating Device State parameter) of the device that is backed up.
- Excluded (default): The state of the device that is inactivated by backup
transition will be set to Excluded. Such device can no longer be used as
backup device in the application as long as the Floating Device State
parameter of the device is not manually changed to Inactive.
- Inactive: The state of the device that is inactivated by backup transition will
be set to Inactive. Such device can then be used to backup another device.
Check Floating Device Alarmed:
Values: Enabled (default), Disabled
When enabled, the ROSA EM system will verify that a backup device has no
alarm with backup on alarm flag set. If the alarm is active, the system will prohibit
backup for this device.
When disabled, backup will continue to the backup device, even if there would
be a signal with checked backup on alarm in alarm status.
Configuring the Device Backup Parameters

The following steps explain how to configure the backup parameters of a device.
1 Open the ROSA EM System GUI and in the device tree, browse to the page of the
device in question and click on the Backup tab.
2 Click on the Value field of the Floating Backup parameter.
Result: The Change Parameter Dialog of the Floating Backup parameter is
displayed.
3 Select Enabled and press the Execute button.
Result: The Backup tab is filled up with parameters for floating backup.
302 4005743 Rev N

4 Click on the Value field of the Backup Enable parameter.

Result: The Change Parameter Dialog of the Backup Enable parameter is
displayed.
5 Select Enabled to switch on the backup functionality of the device and click on the
6 Click on the Value field of the Backup Mode parameter.
Result: The Change Parameter Dialog of the Backup Mode parameter is
displayed.
Manual: only a manual backup request will trigger a backup transition.
Automatic: a manual backup request or a device alarm will trigger a backup
transition.
9 Click on in the Value field of a Keep Chain parameter.
Result: The Change Parameter Dialog of the Keep Chain parameter is
displayed.
10 Select Disabled or Enabled for respectively disabling or enabling the Keep Chain
functionality and click on the Execute button to confirm.
11 Click on the Value field of the Pre Backup Check Script parameter.
4005743 Rev N 303

Result: The Change Parameter Dialog of the Pre Backup Check Script
12 Enter the name of the script that must be executed before performing the backup
transition and press the execute button to confirm. When no pre backup script
must be executed, leave this parameter empty.
13 Click on the Value field of the Backup Script parameter.
Result: The Change Parameter Dialog of the Backup Script parameter is
displayed.
14 Enter the name of the script that must be executed during the backup transition
15 Click on in the Value field of a Linked to Device x parameter.
Result: The Change Parameter Dialog of the Linked to Device x parameter in
16 Enter the name of the device that must be linked.
Notes:
- The device name must be unique, meaning there cant be another device
- If multiple devices with the same device name but categorized in different
(included) separated by dots (for instance group1.group2.device).
- Bi-directional device links are allowed. This means that a configuration can
be made with device A a linked device of device B and vice versa. When a
backup transition is triggered for one device, the other device will also be
backed up.
Tip:
- The backup configuration can be facilitated by the next and previous
keywords. Previous refers to the device immediately preceding this device
and next refers to the device immediately succeeding this device in the
device list or browser tree.
18 Repeat step 13 up to 15 for all devices that should be linked.
19 Click on the Value field of the Floating Device State parameter.
Result: The Change Parameter Dialog of the Floating Device State parameter is
displayed.
20 Select the desired initial state for the device:
304 4005743 Rev N

Active (default): the device can be backed up by an Inactive device of the same
pool.
Inactive: the device can be involved in a backup transaction.
21 Click on the Execute button.
22 Click on the Value field of the Floating Pool Name parameter.
Result: The Change Parameter Dialog of the Floating Pool Name parameter is
displayed.
23 Enter the name of the pool to which the device belongs to. This name is not case
sensitive.
24 Point to the Execute button.
25 Click on the Value field of the Additional Switch Over Delay parameter.
Result: The Change Parameter Dialog of the Additional Switch Over Delay
26 Enter the desired delay value (in milliseconds) to achieve a seamless backup
transition and press the Execute button to confirm.
Note: Repeat this procedure for all devices participating into the backup application.
Tip: During performing this procedure, the Backup Configuration Error Hint
parameter gives additional information about the configuration. More information is
available in topic Testing the Backup Configuration on page 308.
Configuring the ROSA EM Backup Parameters

The following steps explain how to configure the backup parameters of the ROSA
EM.
top node of the device tree) and select the Device Backup tab.
2 Click on the Value field of the Set Deactivated Floating Backup Devices
parameter.
Result: The Change Parameter Dialog of the Set Deactivated Floating Backup
Devices parameter is displayed.
3 Select Inactive or Excluded and press the Execute button.
4 Click on the Value field of the Check Floating Device Alarmed parameter.
4005743 Rev N 305

Result: The Change Parameter Dialog of the Check Floating Device Alarmed
5 Select Enabled or Disabled and press the Execute button.
Configuring the Input and Output Router Backup Parameters

A device might be connected to an input- and/or output router. In case of backup
these routers need to be switched. In order to do this, the ROSA EM device requires
the knowledge of the router names and the input and/or output ports used by the
primary and backup device.
The following procedure explains how to enter the input and output router backup
parameters.
the device in question and click on the Routing tab.
Result: The Routing tab is displayed.
Note: For Stellar, Stellar XT, Pyxis, and Capella devices this knowledge should
be entered on the Backup tab of the device pages.
2 Click on the Value field of one of the following parameters. On the Change
Parameter Dialog of the selected parameter enter a correct value.
Input Router: the name of the input router that is connected to the device
Input Router Video Layers (**): specifies the layer(s) on the input router
routing the video; multiple layers must be separated using a comma or a
space and a layer must be entered using its number (numerical value).
Input Router Audio Layers (**): specifies the layer(s) on the input router
routing the audio; multiple layers must be separated using a comma or a
space and a layer must be entered using its number (numerical value).
Input Router Video Input: the video input port number of the input router.
Input Router Audio Input: the audio input port number of the input router.
Note: Both the Input Router Video Input and Input Router Audio Input
parameter are only displayed when an input router is specified.
306 4005743 Rev N

Input Router Video Output: the video output port number of the input
router to which the device is connected.
Input Router Audio Output: the audio output port number of the input
Input Router Backup Script (*): the name of the script that is used to switch
the input router in case of a backup transition.
Input Router Restore Script (*): the name of the script that is used to switch
the input router in case of a restore transition.
Output Router: the name of the output router that is connected to the device.
Output Router Video Layers (**): the video layer(s) of the output router;
multiple layers must be separated using a comma or a space and a layer must
be entered using its number (numerical value).
Output Router Audio Layers (**): the audio layer(s) of the output router;
multiple layers must be separated using a comma or a space and a layer must
be entered using its number (numerical value).
Output Router Video Input: the video input port number of the output
Output Router Audio Input: the audio input port number of the output
Output Router Backup Script (*): the name of the script that is used to
switch the output router in case of a backup transition.
Output Router Restore Script (*): the name of the script that is used to
switch the output router in case of a restore transition.
3 After entering a value in the Change Parameter Dialog of a parameter, click on
the Execute button to confirm or the Cancel button to abort the operation.
(*) Only for Stellar, Stellar XT, Pyxis, and Capella devices.
(**) Not for Vikinx Routers
Determining the Backup Trigger

Not all alarms that a device can generate should trigger a backup transition. The
operator has freedom to choose which alarm must trigger a backup transition. The
following procedure explains how to select an alarm that has to trigger a backup
transition.
the device in question and click on the Alarm tab.
Result: The Alarm tab is displayed.
2 Right-click on the corresponding alarm and tick the Backup-on-Alarm check box
in the short-cut menu.
4005743 Rev N 307

Note: The Backup-on-Alarm check boxes of particular alarms are by default

checked.
3 Perform step 2 for all alarms that have to trigger a backup transition.
Testing the Backup Configuration

Once the backup application is configured, the Backup Configuration State
parameter on the Backup page of each main and each backup device represents the
correctness of the configuration of the corresponding device. When configuration
errors are given, particular hints to fix the errors are displayed in the Backup
Configuration Error Hint parameter. The following table lists this status
information.
308 4005743 Rev N

Value Description
Incorrect_configuration Backup script doesn't support floating bu: for floating
backup, only backup scripts which are compatible
with the floating backup are supported. This
message appears if the backup script is not
compatible with floating backup.
Failed to find script: script not found
Floating backup device linked to non-floating backup

device: all linked devices should be in the same mode.
This message appears if a device configured for
floating backup is linked to a device configured for
regular backup.
Input/output router not a valid device
Internal error
Linked device is not a valid device
No other device in this pool: a pool needs a population

of at least two devices. This message appears if the
pool has only one member and Backup by
Reconfiguration is disabled.
No pool name for floating backup: every device

participating into a floating backup application must
belong to a pool. This message appears if no pool
name is entered.
No valid backup device specified
No (valid) script was defined for the parameter

<Backup/Restore Script>: This message appears if no
backup/restore script is defined.
Poolname <name> is used more than once in same chain:

in a chain with linked devices, only one device must
be added to a certain pool. This message is displayed
if two devices in the same link chain are member of
the same pool.
Configured OK for backup
Backup_Device Is selected as backup by a main device (Another device is
referring to this device as backup device)
Configured_with_priority_zero Backup priority equals 0: backup is disabled. This message
can occur when a device has been used as a backup.
Not_licensed Backup disabled by devtype (No license for backup)
Backup_system_disabled Backup option not activated
Backup subsystem disabled
Backup disabled
4005743 Rev N 309

Value Description
Configured_for_restore_only Configured for restore only: Only a restore is allowed,
afterwards backup to this device will be disabled.
When the configuration is properly done, the backup configuration can be tested
using the backup test mode. The following steps explain how to enable or disable
this mode.
the device in question and click on the Backup tab.
2 Right-click on the Backup Test Mode parameter and set the Backup-on-Alarm
check box in the short-cut menu.
3 Click on the Value field of the Backup Test Mode parameter.

Result: The Change Parameter Dialog of the Backup Test Mode parameter is
displayed.
4 Select Test to enable the backup test mode or Normal to disable the mode.
5 Click on the Execute button to confirm or the Cancel button to abort the
operation.
Executing a Backup/Restore Transition Manually

For some reasons it can be necessary to trigger a backup/restore transition
manually.
Note: For Floating Backup applications, only a backup transition can be triggered.
The following procedure explains how to trigger a transition.
2 Click on the Value field of the Backup State parameter.
310 4005743 Rev N

Result: The Change Parameter Dialog of the Backup State parameter is

displayed.
3 Select Backup to trigger a backup transition or Inactive to trigger a restore
transition.
4 Click on the Execute button to confirm or the Cancel button to abort the
operation.
Note: It is not possible to trigger a backup/restore transition manually via a backup
device.
Checking the Backup/Restore Information

For monitoring the progress of a backup or restore transition and the result of a
transition, particular information can be checked on the backup tab page of the
device.
Backup State: represents the actual state of the device. Backup state indicates the
device is in backup and the Inactive indicates the device is not in backup.
Backup Reason: indicates the backup transition reason:
- None: no backup transition
- Failure: the device is in backup state, caused by a device alarm/error.
- Maintenance: the device is in backup state, caused by a manual backup
transition request. More information can be found in topic Executing a
Backup/Restore Transition Manually on page 310.
- Linked Failure: this device is in backup state caused by an alarm/error in the
device to which this device is linked.
- Linked Maintenance: this device is in backup state caused by a manual backup
transition request of the device to which this device is linked.
Active Backup Device (Regular backup scenario and for main devices only):
shows the name of the backup device currently used for the active backup.
Backup Completion Status: represents the completion state of a backup or
restore transition:
- Backup_Started: the backup transition is in progress.
- Backup_Completed: the backup transition is completed.
- Restore_Started: the restore transition is in progress.
- Restore_Completed: the restore transition is completed.
- empty field: initial state after adding the device to the tree.
Backup Alarm Status: represents if the last backup or restore transition was
successfully or not.
4005743 Rev N 311

- Normal: the last backup or restore transition was successfully or the backup
alarm is manually cleared.
- Alarm: the last backup or restore transition was not successfully.
Last Main Device: shows the hierarchical name of the main device that the
corresponding device used as backup device. In a floating backup application,
this parameter refers to an inactivated or excluded device.
Last Backup Device: indicates the hierarchical name of the device that was used
as backup by the corresponding device. In a floating backup application, this
parameter refers to the activated device.
Timeout On Completion: determines the time window in which the backup or
restore transition should be executed. This parameter can be set between 20 and
7200 s and its default value is 600 s.
Device is Backup (Regular Backup scenario only): indicates the backup mode of
the device, Yes means that device is configured as backup device.
Device Configuration Status: represents combined information about the
device:
- Main or Backup
- Normal, Floating, Standalone, Incomplete, or Unknown
- Active, Inactive, or Excluded
Device Redundancy Scheme: represents combined information of the
redundancy type to which the device belongs to: Normal or Floating, M:N or 1:1,
Standalone, Unknown.
Backup State Counter: Some devices or backup scenarios require multiple
backup/restore script cycles before a backup/restore transition sequence is
completed. This parameter shows the number of cycles the backup or restore
script has been run. R preceding the counter indicates a restore script cycle and B
a backup script cycle.
In Backup for Device (Regular Backup scenario and for backup devices only):
this parameter represents the name of the device for which this device is the
active backup device. Remark that the device name is only displayed if the state
of this backup device is Active.
The following procedure explains how to check the backup/restore information.
Result: The Backup tab is displayed with the corresponding information.
312 4005743 Rev N

4005743 Rev N 313

A Appx auto letter
Customer Information
Appendix A
Introduction
This appendix contains information on obtaining product support.
In This Appendix
Product Support .................................................................................. 316
4005743 Rev N 315

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
316 4005743 Rev N

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
4005743 Rev N 317

B Appx auto letter
General Information
Appendix B
Introduction
This appendix gives general information about the ROSA Element
Manager.
In This Appendix
TCP/UDP Port Overview.................................................................. 320
TCP/UDP Ports Used by ROSA EM................................................ 321
Backup Scripts ..................................................................................... 322
4005743 Rev N 319

Appendix B
General Information
TCP/UDP Port Overview

The following list gives an overview of the available ports on the ROSA EM device.
Note: For technical information about the ports, please refer to the ROSA Element
Manager Installation and Operation Guide.
Name Number of Ports

Ethernet Ports 2
Serial Ports (RS-232) 4
Configurable Serial Ports (RS-232/RS-485/RS-422) 4
Digital Input Ports 108
Galvanic Isolated Digital Input Ports 12
External Temperature Sensor Ports 2
Relay Output Ports 24
Analog Input Ports 8
Analog Output Ports 2
Craft Interface Port 1
Keyboard and Mouse Ports 2
320 4005743 Rev N

TCP/UDP Ports Used by ROSA EM
TCP/UDP Ports Used by ROSA EM

This topic summarizes the TCP/UDP ports used by the ROSA Element Manager.
Application Port Number

TNCS - ROSA EM TCP port 2000
ROSA EM applet GUI TCP port 2001
HTTP TCP 80
FTP TCP 20, 21
SNMP UDP 161
SNMP-TRAP UDP 162
Apollo TCP 5001, 5002
Telnet TCP 23
DayTime TCP 13
NTP UDP 123
Note: Other ports may be required to manage certain device types that also make
use of network protocols.
4005743 Rev N 321

Appendix B
General Information
Backup Scripts
The following list gives an overview of the scripts used by ROSA EM for backup
purposes.
Scripts for 1:1 device backup with Digital Content Manager (DCM)
Generic DCM 1:1 device backup
- Backup script: budcm.py
- Restore script: redcm.py
DCM 1:1 backup in Statmux configuration
- Backup script: budcm_smx.py
- Restore script: redcm_smx.py
Scripts for backup applications with 984X Receivers
- Backup script: bu984x.py
- Restore script: re984x.py
Scripts for backup applications with D9154 Encoders
- Pre backup check script: prebu9154.py
- Backup script: bu9154.py
- Restore script: re9154.py
Scripts for backup applications with Stellar and Stellar XT devices via RCDS
- Pre backup check script: vikinx_bacchk
- Backup script: stellar_bkp
- Restore script: stellar_res
- Input router backup script: vikinx_inproubacscr
- Input router restore script: vikinx_inprouresscr
- Output router backup script: vikinx_outroubacscr
- Output router restore script: vikinx_outrouresscr
Scripts for backup applications with Capella devices
- Pre backup check script: vikinx_bacchk
- Backup script: capella_bkp
- Restore script: capella_res
322 4005743 Rev N

Backup Scripts
- Input router backup script: vikinx_inproubacscr

- Input router restore script: vikinx_inprouresscr
- Output router backup script: vikinx_outroubacscr
- Output router restore script: vikinx_outrouresscr
Scripts for backup applications with Stellar XT devices via SNMP
- Backup script: bustellarxtsnmp
- Restore script: restellarxtsnmp
Scripts for backup applications with D9030, D9032, D9034, D9050, or D9054
devices
- Backup script: bu903x.py
- Restore script: re903x.py
Scripts for backup applications with (X)DQA(24) devices
Scripts for the (X)DQA(24) Chassis (1:1 backup)
- Backup script: dqachassis_bkp
- Restore script: dqachassis_res
Scripts for the (X)DQA(24) Chassis (M:N backup)
- Backup script: budqa.py
- Restore script: redqa.py
Scripts for the QAM Cards
- Backup script: dqaqam_bkp
- Restore script: dqaqam_res
Scripts for backup applications with Cisco RF Gateway 1 devices
- Pre backup check script: preburfgw1.py.
- Backup script: burfgw1.py
- Restore script: rerfgw1.py
Scripts for backup applications with Modulus Video Encoder (me6000)
- Backup script: bu-mvenc.py
- Restore script: re-mvenc.py
4005743 Rev N 323

C Appx auto letter

Appendix C
Introduction
This appendix gives an overview of the steps to take to install a
ROSA Element Manager (EM).
In This Appendix
Installation Steps ................................................................................. 326
4005743 Rev N 325

Appendix C
Installation Steps
More Information
This Quick Installation Reference gives a summary of the installation procedures
described in the different chapters of this manual. If you are not familiar with these
procedures, please read the entire manual first before continuing.
Scenario 1
If you are installing one or more ROSA EM devices with known IP address, for
example the default factory IP address, you can follow the steps below.
For more detailed information, please also refer to the ROSA Element Manager
1 Set the internal jumpers and/or switches of your ROSA EM to configure the I/O
interfaces according to the needs of your application.
2 Mount the ROSA EM in the rack where it will be used.
3 Install the devices that will be managed by the ROSA EM, and connect these
devices to the correct I/O port.
4 Power on the ROSA EM device, and verify that the Power LED is on.
now, and connect a PC or laptop with a crossover Ethernet cable to the ROSA
EM.
Note: If the known IP address is an unused IP address within the IP range
defined for your network, you may configure the IP settings directly via the
network instead of using a crossover Ethernet cable.
6 Open the ROSA EM web browser user interface using the known IP address.
7 Set the admin Operator ID password. For more information, please refer to Using
the ROSA EM Device GUI on page 50
8 Configure the IP settings of the ROSA EM. For more information, please refer to
Network Configuration on page 25.
9 Disconnect the crossover Ethernet cable, and connect the ROSA EM device back
to the Ethernet network.
10 A ROSA EM with software version V04.01.30 or higher has all services default
disabled for security reasons. Login to the web browser user interface, set all
service passwords and enable the ROSA EM services required for your
application. For more information, see also Managing Services on page 72.
11 Depending on how the ROSA EM device(s) will be used in your application,
refer to the following chapters:
326 4005743 Rev N

Installation Steps
- As stand-alone device: see chapter ROSA EM Functionality on page 49 for

more information.
- Integrated in a management system: see chapter Integration of ROSA EM on
page 189 for more information.
12 Repeat the above steps for each ROSA EM device with known IP address that
you want to install.
Scenario 2
If you are installing one or more ROSA EM devices with unknown IP address, you
can follow the steps below.
For more detailed information, please also refer to the ROSA Element Manager
1 Set the internal jumpers and/or switches of your ROSA EM to configure the I/O
interfaces according to the needs of your application.
2 Mount the ROSA EM in the rack where it will be used.
3 Install the devices that will be managed by the ROSA EM, and connect these
devices to the correct I/O port.
4 Power on the ROSA EM device, and verify that the Power LED is on.
now.
6 Connect a PC or laptop with a crossover serial cable to the craft interface of the
ROSA EM.
7 Configure the IP settings of the ROSA EM using the craft interface. For more
information, please refer to ROSA EM - Setup - Network Config on page 25.
8 Disconnect the crossover serial cable, and connect the ROSA EM device to the
Ethernet network.
9 A ROSA EM with software version V04.01.30 or higher has all services default
disabled for security reasons. Login to the web browser user interface and enable
the ROSA EM services required for your application. For more information, see
also Managing Services on page 72.
10 Depending on how the ROSA EM device(s) will be used in your application,
refer to the following chapters:
- As stand-alone device: see chapter ROSA EM Functionality on page 49 for
more information.
- Integrated in a management system: see chapter Integration of ROSA EM on
page 189 for more information.
11 Repeat the above steps for each ROSA EM device with unknown IP address that
you want to install.
4005743 Rev N 327

D Appx auto letter
Email Function with Plain

Appendix D
Authentication
Introduction
This appendix describes how the ROSA Element Manager (EM) email
function can work with an enhanced security feature that has been
added to many email servers called Plain Authentication.
Important: ROSA EM has not implemented all possible Email Server
Authentication methods and if the email server has implemented any
authentication method other than Plain Authentication, ROSA EM will
not be able to send emails through that server.
This appendix provides ROSA EM administrators with the following
information:
How to determine if email authentication is required for ROSA EM
to send emails
How to set the email server authentication
In This Appendix
Monitoring Information ..................................................................... 330
4005743 Rev N 329

Appendix D
Email Function with Plain Authentication
Monitoring Information
Requirements
ROSA EM Software Revision V02.01.00 or higher
IP connectivity from the ROSA EM device to the email server that allows a
simple ICMP ping message to pass in both directions.
Determine if Email Authentication is Required

Follow the procedure below to determine if ROSA EM can send emails on your
email server.
1 Configure the email service on the ROSA EM device as described in the chapter
Diverse Notification on page 257.
Note: This configuration includes six steps, i.e. check if the email option is
enabled, configure the email service, create member account(s), assign
member(s) to notification group(s), configure system wide notification rules and
finally assign notify sets to devices and parameters.
Important: On the Email_Service tab page of the ROSA EM GUI, leave the value
of the Email Server Authentication parameter to None.
2 On the Debug tab page of the ROSA EM GUI set the value of the Email Debug
Mode parameter to On.
Notes:
- For more information on how to enable a debug mode, please refer to the
topic Using the Debug Mode on page 123.
- If any other debug modes are enabled, disable them while performing this
procedure. It will make reading the email debug messages easier.
3 Create an alarm of which the severity level is the same or higher as the
Notification Severity Level defined on Notification_Information tab of ROSA EM.
Note: There are numerous ways to do this. One method to create an alarm is to
adjust the limits on a monitored device parameter to a value that creates an
alarm.
4 In the menu bar of the ROSA EM GUI, click on the Logs menu and select Software
Log.
Result: This log will record the messages between the ROSA EM device and the
email server.
330 4005743 Rev N

Example 1: Log of a Successful Email Message

When an email message is send successfully, the log will contain information similar
to the last 4 lines in bold of the log example below.
29Oct2003 09:26:27 Sending Email addressed to rosaemuser@mailserver.net - Alarm-Major
ROSAEMDev mod1 "Communication Status" Alarm
29Oct2003 09:26:28 Message Sent: HELO.
29Oct2003 09:26:28 Email Server Response: 250 mta02-srv.mailserver.net.
29Oct2003 09:26:28 Message Sent: MAIL FROM: <rosaemaccount@mailserver.net>.
29Oct2003 09:26:28 Email Server Response: 250 Sender <rosaemaccount@mailserver.net>
Ok.
29Oct2003 09:26:28 Message Sent: RCPT To: <rosaemuser@mailserver.net>.
29Oct2003 09:26:28 Email Server Response: 250 Recipient <rosaemuser@mailserver.net>Ok.
29Oct2003 09:26:28 Message Sent: DATA.
29Oct2003 09:26:28 Email Server Response: 354 Ok Send data ending with <CRLF>.<CRLF>.
29Oct2003 09:26:28 Message Sent: To: rosaemuser@mailserver.net
From: rosaemaccount@mailserver.net
Subject: Alarm-Major ROSAEMDev mod1 "Communication Status" Alarm
Alarm-Major ROSAEMDev mod1 "Communication Status" Alarm
Important: If the log indicates a successful email message, Plain Authentication must
NOT be used. In other words, on the Email_Service tab page leave the value of the
Email Server Authentication parameter to None.
Note:
rosaemuser@mailserver.net: The email address where the alarm information is
being sent to.
rosaemaccount@mailserver.net: The email account being used by the ROSA EM
device.
ROSAEMDev: The system name of the ROSA EM device.
mod1: The name of the module in alarm.
Example 2: Log of an Unsuccessful Email Message

If the email message is unsuccessful, the log will contain a statement similar to
Recipient address rejected: Relaying Denied: see the bold line in the log example below.
ROSAEMDev Mod1 "Communication Status" Alarm
29Oct2003 15:55:14 Message Sent: HELO ROSAEMDev.
29Oct2003 15:55:14 Email Server Response: 250 mta02-srv.mailserver.net.
29Oct2003 15:55:14 Message Sent: MAIL FROM: < rosaemaccount@mailserver.net >.
29Oct2003 15:55:14 Email Server Response: 250 Ok.
29Oct2003 15:55:14 Message Sent: RCPT To: < rosaemaccount@mailserver.net >.
29Oct2003 15:56:00 Email Server Response: 550 < rosaemaccount@mailserver.net >:
Recipient address rejected: Relaying Denied:
29Oct2003 15:56:00 Message Sent: QUIT.
29Oct2003 15:56:00 Email Server Response: 221 Bye
Only when information similar to Relaying Denied is returned, perform the following
procedure to determine if the email server supports Plain Authentication.
1 Open the Command Prompt.
Example: For a system with the operating system Windows 2000, click on the
Windows Start button, move to Programs, move to Accessories and click on
Command Prompt.
4005743 Rev N 331

Appendix D
Email Function with Plain Authentication
Result: The command prompt dialog is opened.

2 Enter the command
telnet <email server address> 25
where <email server address> is replaced with your email server address.
Example: telnet mailserver.net 25
Result: The session should show some text welcoming you to the server.
Example: 220 mailserver.net ESMTP Sendmail 8.12.9/8.11.6; Fri, 8 Aug 2003
16:11:20 -0400 Ready
Note: Some email servers do not return a welcoming text. Just continue with the
next step of this procedure.
3 Enter the command
EHLO <ROSA EM device>
where <ROSA EM device> is replaced with your ROSA EM device name.
Example: EHLO ROSAEMDev
Result: The email server will respond with a list of options it supports.
Example:
250-mailserver.net Hello ROSAEMDev, pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE 5242880
250-DSN
250-ETRN
250-AUTH LOGIN PLAIN
250-DELIVERBY
250-HELP
4 If AUTH LOGIN PLAIN is returned as one of the options (see third line from the
bottom of example in step 3), on the Email_Service tab page of the ROSA EM
GUI set the value of the Email Server Authentication parameter to Plain.
Note: When using Plain Authentication, a valid Email User ID and Email User
Password that are authorized on the email server are required.
Important: If the options do not list AUTH LOGIN PLAIN, then the ROSA EM
device cannot send emails to this server.
332 4005743 Rev N

Example 3: Log of a Successful Email Message using Plain Authentication

The log example below contains the debug information of a successful email
message via an email server using Plain Authentication.

ROSAEMDev Mod1 "Communication Status" Alarm
30Oct2003 14:10:09 Message Sent: EHLO ROSAEMDev.
30Oct2003 14:10:09 Email Server Response: 250-smtp-3. mailserver.net
250-PIPELINING
250-SIZE 3000000
250-VRFY
250-ETRN
250-AUTH LOGIN PLAIN
250 8BITMIME.
30Oct2003 14:10:09 Message Sent: AUTH LOGIN.
30Oct2003 14:10:09 Email Server Response: 334 VXNlcm5hbWU6.
30Oct2003 14:10:09 Message Sent: VE5DU1dBWU5FQGhvdHBvcC5jb20=.
30Oct2003 14:10:09 Email Server Response: 334 UGFzc3dvcmQ6.
30Oct2003 14:10:09 Message Sent: ZG9nNzc3Nw==.
30Oct2003 14:10:10 Email Server Response: 235 Authentication successful.
30Oct2003 14:10:10 Message Sent: MAIL FROM: < rosaemaccount@mailserver.net >.
30Oct2003 14:10:10 Message Sent: RCPT To: < rosaemuser@mailserver.net >.
30Oct2003 14:10:10 Message Sent: DATA.
30Oct2003 14:10:10 Email Server Response: 354 End data with <CR><LF>.<CR><LF>.
30Oct2003 14:10:10 Message Sent: To: rosaemuser@mailserver.net
From: rosaemaccount@mailserver.net
Subject: Alarm-Major ROSAEMDev Mod1 "Communication Status" Alarm
Alarm-Major ROSAEMDev Mod1 "Communication Status" Alarm.
.
30Oct2003 14:10:11 Email Server Response: 250 Ok: queued as 3B1F095D82A.
30Oct2003 14:10:11 Message Sent: QUIT .
30Oct2003 14:10:11 Email Server Response: 221 Bye
4005743 Rev N 333

E Appx auto letter
Additional Configuration
Appendix E
Introduction
This appendix describes the IP Security configuration for a computer
running Windows XP Professional or Windows 2003 Server and for a
computer running Windows Vista.
In This Appendix
Internet Protocol Security .................................................................. 336
4005743 Rev N 335

Appendix E
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.
Note: When the communication between the ROSA EM and peer must be secured by
using IPsec, 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.
Accessing the IPsec Management Console

The following steps explain how to open the IPsec management console.
336 4005743 Rev N

Launching MMC
The following steps explain how to open the MMC main screen.
1 From the Windows desktop, click on Start 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 OK.
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.
Result: The Add/Remove Snap-in dialog appears as shown below.
4005743 Rev N 337

Appendix E
2 Click on Add.
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 Add.
Result: The Select Computer or Domain dialog appears as shown below.
338 4005743 Rev N

4 Confirm that the Local computer selection button is selected, and then click on
Finish.
5 Click on Close 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 OK to return to the management console.
Result: The screen should now appear as shown below.
4005743 Rev N 339

Appendix E
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.
Hint: 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 shortcut menu.
Result: The Manage IP filter lists and filter Actions dialog appears as shown
below.
340 4005743 Rev N

2 Click on Add 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.
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 Add
to start the IP Filter List wizard.
5 Complete the steps of the wizard as follows:
4005743 Rev N 341

Appendix E
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 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 Next.
d IP Protocol Type. This identifies what protocols are valid for this list. Choose
Any from the drop down box, and then click on Next.
e Click on Finish.
For a computer running Windows 2003 Server, the IP Filter Properties dialog
is displayed.
Click on OK to close the IP Filter Properties dialog.

Result: The IP Filter List dialog should now appear as shown below.
342 4005743 Rev N

6 Click on OK 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 EM.
Result: The tab opens as shown below.
4005743 Rev N 343

Appendix E
2 Click on Add to start the Filter Action wizard.

3 At the wizard welcome screen, click on Next >.
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 Next >.
b Filter Action General Options. Select the Negotiate Security selection
button, and then click on Next >.
c Communicating with computers that do not support IPsec. Choose Do not
communicate with computers that do not support IPsec, and then click on
Next >.
d IP Traffic Security. Select the Custom selection button, and then click on
Settings.
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 OK to save your selections and return to the Filter Action wizard IP
Traffic Security wizard page.
g Click on Next to proceed to the final page of the Filter Action wizard.
h Click on Finish.
344 4005743 Rev N

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.
4005743 Rev N 345

Appendix E
7 When finished, click on OK to close the Headend IPsec filter Properties dialog
and return to the Manage IP filter lists and filter actions dialog.
8 Click on Close to close this dialog and return to the MMC dialog.
346 4005743 Rev N

To Create a New IPsec Policy

Complete the following steps to create a new IPsec policy.
1 Right-click on the right pane of the MMC, and then point to Create IP Security
Policy... in the shortcut menu to open the IP Security Policy wizard.
2 At the wizard welcome screen, click on Next > 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 Next >.
4005743 Rev N 347

Appendix E
b Requests for Secure Communication. Confirm that the Activate the default
response rule check box is not checked, and then click on Next >.
c On the final page of the wizard, confirm that the Edit Properties check box is
checked, and then click on Finish.
Result: The Headend Policy Properties dialog appears as shown below.
3 Select the General tab and click on Advanced.

Result: The Key Exchange Settings dialog is displayed.
4 Point to Methods....
348 4005743 Rev N

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 Move up.
Note: When the desired method is not available, an existing method can be
modified by clicking on Edit... or a new method can be created by clicking on
Add....
Select the desired Integrity algorithm, Encryption Algorithm (3DES), and

Diffie-Hellman group (Medium (2)) in the corresponding drop down boxes
and press OK to close the dialog.
6 Click on OK to close the Key Exchange Security Methods dialog and to return
to the Key Exchange Settings dialog.
7 Click on OK 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 Add.
Result: The New Rule Properties dialog appears as shown below.
4005743 Rev N 349

Appendix E
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 Add.
Result: The New Authentication Method Properties dialog appears as shown
below.
350 4005743 Rev N

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 OK to save the preshared key entry and return to the New Rule
Properties dialog.
Result: The preshared key is added to the Authentication method preference
order box.
14 Select the existing Kerberos entry, and then click on Remove to delete this entry
from the list.
15 In the confirmation dialog, click on Yes to accept the changes.
16 Click on OK to close the New Rule Properties dialog.
Result: The Edit Rule Properties dialog should now display only the newly
entered rule.
4005743 Rev N 351

Appendix E
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 shortcut 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 336.
2 In the right hand pane of the Management Console, right-click on the IPsec
policy and point to Un-assign in the shortcut menu.
For Further Information

Additional information on configuring IPsec for Windows XP Professional and
Windows 2003 Server is available on the following web page:
352 4005743 Rev N

http://www.microsoft.com/downloads/details.aspx?familyid=a774012a-ac25-4a1d-
8851-b7a09e3f1dc9&displaylang=en
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 Start 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 Continue.
Result: The Windows Firewall with Advanced Security dialog is displayed.
4005743 Rev N 353

Appendix E
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 shortcut menu.
Result: The New Connection Security Rule Wizard - Rule Type dialog is
displayed.
354 4005743 Rev N

8 Select the Server-to-server selection button and click on Next >.

Result: The New Connection Security Rule Wizard - Endpoints dialog is
displayed.
4005743 Rev N 355

Appendix E
9 Under Which computers are in Endpoint 1?, select the These IP addresses
selection button and click on Add....
Result: The IP Address dialog for Endpoint 1 appears.
10 Select the This IP address or subnet selection button.
356 4005743 Rev N

11 Enter the IP address of this computer in the corresponding box and press OK 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 Add....
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
OK to close the IP Address dialog and to return to the New Connection Security
Rule Wizard - Endpoints dialog.
15 Click on Next >.
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 Next >.
Result: The New Connection Security Rule Wizard - Authentication Method
dialog is displayed.
4005743 Rev N 357

Appendix E
17 Select the Preshared Key selection button.

18 In the Key box, enter the preshared key and press Next >.
Result: The New Connection Security Rule Wizard - Profile dialog is displayed.
358 4005743 Rev N

19 Leave all check boxes ticked and press Next >.

Result: The New Connection Security Rule Wizard - Name dialog is displayed.
4005743 Rev N 359

Appendix E
20 In the Name box, enter a name for the IPsec connection (Headend IPs in the
example).
21 Click on Finish 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 shortcut menu.
Result: The Windows Firewall with Advanced Security on Local Computer
dialog is displayed.
2 Click on the IPsec Settings tab
Result: The IPsec Settings tab page is displayed.
360 4005743 Rev N

3 Press Customize....
4005743 Rev N 361

Appendix E
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... button.
362 4005743 Rev N

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 Add.
4005743 Rev N 363

Appendix E
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 OK 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 OK 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... button.
Result: The Customize Data Protection Settings dialog is displayed.
364 4005743 Rev N

9 In the Data integrity and encryption box, point to Add....

Result: The Integrity and Encryption Algorithms dialog is displayed.
4005743 Rev N 365

Appendix E
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 OK 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.
10 Press OK to close Customize Data Protection Settings dialog and to return to
the Customize IPsec Settings dialog.
11 Press OK 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 353.
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 shortcut
menu.
366 4005743 Rev N

Glossary
ac, AC
alternating current. An electric current that reverses its direction at regularly
recurring intervals.
AES
advanced encryption standard.
AH
authentication header.
AIN
analog input.
AM
amplitude modulation. A transmission technique in which the amplitude of the
carrier varies in accordance with the modulating signal.
AOUT
analog output.
ASI
asynchronous serial interface. Allows the intermittent transfer of data one bit at a
time rather than in a steady stream.
ATSC
Advanced Television Systems Committee of the USA.
AWG
American Wire Gauge. A U.S. standard for wire conductor sizes.
BU
backup.
4005743 Rev N 367

Glossary
CD
compact disc.
CENELEC
Comit Europen de Normalisation ELECtrotechnique. The European
Committee for electro-technical standardization.
CLI
command line interface. A command reference software that allows the user to
interact with the operating system by entering commands and optional
arguments.
Com
common.
COM
communication.
CPU
central processing unit.
CSA
Canadian Standards Association.
CTRL
control.
dc, DC
direct current. An electric current flowing in one direction only and substantially
constant in value.
DCM
digital content manager.
Deg_C
degrees Celsius.
DES
data encryption standard.
368 4005743 Rev N

Glossary
DevList
device list.
DI
digital input.
DQA
dense QAM array.
DTE
data termination equipment.
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.
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.
EM
element manager.
EMC
electromagnetic compatibility. A measure of equipment tolerance to external
electromagnetic fields.
EN
European norm.
ESC
escape.
ESD
electrostatic discharge. Discharge of stored static electricity that can damage
electronic equipment and impair electrical circuitry, resulting in complete or
intermittent failures.
4005743 Rev N 369

Glossary
ESP
encapsulation security payload.
ESP
encapsulation security payload.
ETSI
European Telecommunications Standards Institute.
F
Fahrenheit.
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.
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.
GI
galvanically isolated digital input.
GND
ground. A conducting connection, whether intentional or accidental, by which an
electric circuit or equipment is connected to the earth, or to some conducting
body of relatively large extent that serves in place of the earth.
GSM
global system for mobile communications (cellular phone technology).
GUI
graphical user interface. A program interface that takes advantage of a computer
graphics capabilities to make the program visually easier to use.
HD
high density.
370 4005743 Rev N

Glossary
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.
HMS
hybrid management sublayer. A set of ANSI/SCTE standards specifying an
element management system for hybrid fiber/coaxial networks. The standards
establish key protocols for the communication of status monitoring information
between elements in the network.
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.
IEC
International Electro-technical Commission.
IIOP
Internet inter-ORB protocol. A protocol developed to implement CORBA
solutions over the web. It enables browsers and servers to exchange integers,
arrays, and more complex objects. It is a protocol for communication between an
application programming interface (API) and an external client.
IKE
internet key exchange
IP
Internet protocol. A standard that was originally developed by the United States
4005743 Rev N 371

Glossary
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.
IPsec
internet protocol security.
ISDN
integrated services digital network. An integrated digital network in which the
same time-division switches and digital transmission paths are used to establish
connections for services such as telephone, data, e-mail, and fax.
JRE
Java runtime environment.
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).
LED
light-emitting diode. An electronic device that lights up when electricity passes
through it.
MAC
media access control. The layer in the OSI model above the physical layer. It
defines media access control methods and parameters for access to the physical
media.
MD5
message digest 5 algorithm.
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.
372 4005743 Rev N

Glossary
MMC
Microsoft management console.
MPEG
Motion Picture Experts Group. A joint committee of the International Standards
Organization (ISO) and the International Electrotechnical Commission (EG). This
committee develops and maintains the MPEG specification for a series of
hardware and software standards designed to reduce the storage requirements
of digital video and audio. The common goal of MPEG compression is to convert
the equivalent of about 7.7 MB down to under 150 K, which represents a
compression ratio of approximately 52 to 1. Current standards are MPEG-1,
MPEG-2, and MPEG-4.
NC/Nc
normally closed.
NIC
network interface card.
NMS
network management system. A software system designed specifically to
monitor a network and to facilitate troubleshooting.
NO/No
normally open.
NTP
network time protocol.
OS
operating system.
PC
personal computer.
PCM
pulse code modulation.
PSI
program specific information.
4005743 Rev N 373

Glossary
PSTN
public switched telephone network.
QAM
quadrature amplitude modulation. A phase modulation technique for
representing digital information and transmitting that data with minimal
bandwidth. Both phase and amplitude of carrier waves are altered to represent
the binary code. By manipulating two factors, more discrete digital states are
possible and therefore larger binary schemes can be represented.
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.
RTS
request to send.
RU
rack unit. RU is the measuring unit of vertical space in a standard equipment
rack. One RU equals 1.75" (44.5 mm).
RX
receive or receiver.
SDI
serial digital interface.
SELV
safety extra-low voltage.
374 4005743 Rev N

Glossary
SHA1
secure hash algorithm version 1.0.
SID
service identifier.
SMC
The lowest stratum level in the SONET hierarchy of digital clocks used to time
signals. Stratum level 1 provides the highest level of accuracy and stability,
followed by stratum levels 2, 3E, and 3, and finally SMC. The SMC or level 3
clock may be used as an alternate timing source in the event of a loss of reference
clock or loss of lock.
SMS
short message service. (Cellular phone text messaging.)
SMTP
simple mail transfer protocol. (Internet e-mail.)
SNMP
simple network management protocol. A protocol that governs network
management and the monitoring of network devices and their functions.
SP
splitter. A device that divides power from an input signal to deliver multiple
outputs or combines multiple inputs into one output.
SVGA
super video graphics adapter. (800 by 600 pixels, 1.33:1 aspect ratio.)
TAP
telocator alphanumeric input protocol. A paging protocol used for sending
alphanumeric messages.
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.
4005743 Rev N 375

Glossary
TNCS
Transmission Network Control System. An application that allows status
monitoring and control of all transmission equipment located in headends and
hubs plus optical nodes, power supplies, and amplifiers in the outside plant.
TNCS provides access to and information on the entire network in an easy to
understand, topology driven, graphical user display.
TX
transmit or transmitter.
UDD
universal device driver.
UDP
user datagram protocol. A connectionless protocol, like TCP, that runs on top of
IP networks. Unlike TCP/IP, UDP/IP provides very few error recovery services,
offering instead a direct way to send and receive datagrams over an IP network
without acknowledgements for guaranteed delivery.
UTC
coordinated universal time.
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.
WDT
watchdog time.
XDQA
extra dense QAM array.
XDQA24
extra dense QAM array 24.
376 4005743 Rev N

Index
Agent Parameters dialog 194
3 AH 133
3DES 133, 343 Alarm correlation scripts 282
3DES encryption 133 Alarm Enable parameter 148, 152, 160
ALARM LED 9
A Alarm log 61
A specific IP Address parameter 340 Alarm notification 258
Accept any client option 60 Alarm processing
Accept Any Client parameter 60 Device Alarm Parameters 82
Accessing the IPsec Management Console 337 Introduction 81
Acknowledge All parameter 100 ROSA EM alarm parameters 82
Acknowledge notification 258 Alarm Profile dialog 82
Acknowledge Severity Level parameter 81 Alarm Promotion Threshold parameter 81
Acknowledge-All Alarms feature 100 Alarm Report Threshold parameter 81
Activate the default response rule parameter Alarm Severity parameter 148
347 Alarm Specification 82
Active Alarm Report dialog 99 Alarm State Name(s) parameter 162, 163
Active Backup Device parameter 311 Alarm State parameter 148
Active FTP 24 Alarm Status parameter 152
Add agents dialog 194 Alarm_Buffering tab 109, 111
Add Device at Location Local dialog 200 Alarmbuffering buffered SNMP Devices
Add Devices dialog 91 parameter 109
Add Group dialog 92 Alarmbuffering Buffered Traps parameter 111
Add Operator dialog 55 Alarmbuffering Critical Traps 111
Add Scan Range dialog 180 Alarmbuffering Effective Redelivery Delay
Add Site dialog 172 parameter 111
Add Standalone Snap-in dialog 337 Alarmbuffering Last Delivery Attempt
Add/Remove Snap-in dialog 337 parameter 111
Adding a DCM to the IPsec peers list 136 Alarmbuffering Last Successful Delivery
Adding clients to the IPsec peers list 135 parameter 111
Adding devices 91 Alarmbuffering Major Traps parameter 111
Adding groups 92 Alarmbuffering Max Traps Per Second
Adding operator accounts 55 parameter 109
Adding the snap-in 337 Alarmbuffering Maximum Critical Delay
Additional settings 186 parameter 109
Additional Switch Over Delay parameter 294, Alarmbuffering Maximum Major Delay
301 parameter 109
Address parameter 91, 200 Alarmbuffering Maximum Minor Delay
Administrative Tools 360 parameter 109
Advanced Communication parameters 194 Alarmbuffering Maximum Notification Delay
Advanced Communication Parameters dialog parameter 109
187 Alarmbuffering Minor Traps parameter 111
4005743 Rev N 377

Index
Alarmbuffering Report Alarms Now parameter Backup functionality 288

111 Backup by Reconfiguration 294, 301
Alarmbuffering Trapbuffering for SNMP Backup information 311
Manager X parameters 109 Backup transition 310
Alarmbuffreing Redelivery Delay parameter Licensing 291
109 Linked devices 290
Alarm-Processing tab 82, 84 Restore information 311
Alarms Restore transition 310
Acknowledge-All Alarms feature 100 Scripts 289
Alarm processing 81 Testing 308
Blink Not Ackowledge feature 99 Backup indication 292
Reporting active alarms 99 Backup information 311
Severity Color Code 100 Backup Mode parameter 294, 301
Alarms menu 100 Backup Operation
Alarms tab 82, 307 Enabling/disabling 118
Alias parameter 141 Introduction 118
AM Auto Configuration parameter 119 Backup Priority parameter 294
Analog inputs 152 Backup Reason parameter 311
Analog outputs 156 Backup Script parameter 294, 301
Analog_inputs tab 154 Backup scripts 289
Analog_Outputs tab 156 Backup State Counter parameter 311
Apollo Com Port State parameter 169 Backup State parameter 294, 301, 310, 311
Apollo Com X Port State parameter 169 Backup Sub System parameter 118
Apollo communication ports parameter 168 Backup tab 294, 301, 308, 310
Apollo configuration tab 168, 169 Backup Test Mode parameter 294, 301, 308
Apollo drivers 170 Backup transition 310
Apollo functionality Backup trigger 288
Assigning a COM port 168 Backup-on-Alarm parameter 307, 308
Introduction 168 Benefits 5
Apollo functionality software 218 Blink Not Acknowledge parameter 99
Apollo Protocol user interface 170 Boot software 218
Apollo site Boot Software Revision parameter 102, 220
General Information 178 Buffered Traps
Apollo Software Revision parameter 102, 220 Sending manually 111
Application example 128 Bypassing IPsec 136
Assigning name and location 182
Assigning Notify Sets 275
C
Authentication header 133 Cascade View 235
Authentication Methods tab 347 Cell parameter 160
Automatic Switch Over Delay parameter 131 Change privilege level 55
Available Standalone Snap-ins parameter 337 Changing device time 67
Available Storage parameter 227 Changing FTP Mode 24
Changing IPsec Connection Defaults 366
B
Changing local time 67
Backup by Reconfiguration 294, 301 Changing name and location 182
Backup by Reconfiguration parameter 294, 301 Changing Severity Color code 100
Backup Configuration Now parameter 222 Chassis view 235
Backup Configuration State parameter 308 Check Floating Device Alarmed parameter 301
Backup Device X parameter 294 Checking license parameters 216
Backup devices 289 Checking non-responding sites 174
Backup Enable parameter 294, 301 Choose Minor Alarm Color dialog 100
378 4005743 Rev N

Index
Clear All Log Files parameter 65 Currently Routed Subnet Mask parameter 126
Cleared notification 258 Currently Routed Subnet parameter 126
Client Computer Connection feature Custom graphics 248
Accept any client option 60 Custom parameter 343
Defining IP Address 59 Custom scripts 285
Introduction 59 Custom Security Method Settings dialog 343
Viewing connected client computers 60 Custom views 234, 239
Client options 4 Customize Advanced Key Exchange Settings
Client-Connections tab 59, 60 dialog 366
clone instruction 225 Customize Data Protection Settings dialog 366
Clooning ROSA EM device settings 225 Customize IPsec Settings dialog 366
Color Key window 100
Comm Alarm Threshold parameter 140
D
Comm Quality parameter 140 Data integrity and encryption (ESP) parameter
Command Retry Count parameter 187 343
Communicating with computers that do not Data integrity and encryption algorithms list
support IPsec parameter 343 366
Communication parameters 194 Data integrity and encryption box 366
Communication watcher list 174 Data protection (Quick Mode) parameter 366
Community Strings 194, 209 Date and time logging 66
Compiling MIB information 212 Daylight saving time 69
Config_Backup tab 222, 225 Daytime protocol 68
Configuration 37 Deactivating IPsec 136
Configuration Changed messages 176 Deadband parameter 152, 160
Configuration Error Hint parameter 308 Debounce Time parameter 148
Configuration tab 162, 163 Debug mode 123
Configuration tools 14 Debug tab 123
Configure dialog 34 Delay parameter 82
Configure privilege level 55 Delete verification dialog 93
Configuring device polling 96 Deleting devices 93
Configuring graphics 242 Deleting groups 93
Configuring HFC plant monitoring 119 Deleting log files 65
Configuring NIC Teaming 131 Deleting operator accounts 57
Configuring Trap buffering 109 Description parameter 102, 141
Connection Security Rules pane 360 Detect Temperature Sensor parameter 159
Connection Security Rules parameter 360 Determining backup triggers 307
Connection Type parameter 194 Device alarm parameters 82
Continent parameter 69 Device Backup tab 118, 311
Control Panel - Administrative Tools dialog Device Communication Port parameter 41
360 Device is Backup parameter 311
Control Panel dialog 353 Device License Count parameter 216
Coordinated universal time 69 Device License Shortage parameter 216
Coredump Device License Usage Count parameter 216
Deleting 229 Device list
Downloading 229
Creating a backup 222
Creating a New Filter Action 343
Creating a new IP list 340
Creating a new IPsec policy 347
Creating log files 62
Currently Overhead Gateway parameter 126
4005743 Rev N 379

Index
Concept 38 Diverse Notification

Device types 43 Assigning Notify Sets 275
Downloading 39 Configuring 259
Editing 40 Email service configuration 261
Editing rules 42 Example 279
Group device entries 40 Introduction 258
Helpful hints 43 Member accounts 266
Individual Device Entries 41 Notification rules 274
Uploading 47 Paging service configuration 263
Device Location parameter 141 SMS service configuration 265
Device Name parameter 41 Do not communicate with computers that do not
Device Offline Threshold parameter 95, 96 support IPsec parameter 343
Device parameters Downloading device list 39
Resetting 114 Downloading MIB information 211
Device Poll-All Count parameter 95, 96 DTS 69
Device polling Dump Log Data to File parameter 62, 227
Configuring 96
Executing polling actions manually 98
E
Introduction 95 Edit Properties parameter 347
Switching on or off 97 Edit Rule Properties dialog 347
Device Polling tab 96 Editing device list 40
Device Properties 140 Email From Address parameter 261
Device Retry Count parameter 95, 96 Email Server Authentication parameter 261
Device Serial Number parameter 102 Email Server Name parameter 261
Device software 218 Email service configuration 261
Device Temperature 104 Email User ID parameter 261
Device Type Categories 161 Email User Password parameter 261
Device Type parameter 41 Email_Service tab 261
Device types 43 Enable Automatic Mapping parameter 194
Device voltage levels 104 EnableAll security level 134
Devices EnableManaged security level 134
Adding 38, 91 Enabling Apollo Communication Ports 169
Deleting 93 Enabling backup operation 118
Introduction 91 Enabling Blink Not Acknowledge feature 99
Devices with Changed Instance Data parameter Enabling Debug mode 123
227 Enabling IPsec 366
DevType Revision parameter 102, 140 Encapsulated security payload header 133
Digital inputs 148 Encryption algorithm 133
Digital Outputs 144 Encryption algorithm parameter 343, 366
Digital_Inputs tab 148, 149 ESP 133
Digital_Outputs tab 144 Executing polling actions manually 98
Directed views 234, 235 Executing synchronization action 204
Disable Synchronization at startup parameter
203 F
Disabled security level 134 Factory Reset Code parameter 114
Disabling Apollo Communication Ports 169 Factory Reset parameter 114
Disabling backup operation 118 FAIL LED 9
Disabling Blink Not Acknowledge feature 99 Features 5
Disabling Debug mode 123 Filter Action General Options parameter 343
Disabling IPsec 366 Filter Action Name parameter 343
Disabling time synchronization 70 Filter Action tab 347
380 4005743 Rev N

Index
Filter Action wizard 343 Group graphics 243

Filter dialog 183 group MIB 212
Filter list of new units 183 Group Name parameter 40
Filtering ON parameter 183 Group of racks view 235
Filtering toggling alarms 83 Groups
First Control Point parameter 163 Adding 38, 92
First Status Point parameter 163 Deleting 93
Floating backup 288 Introduction 91
Floating Backup parameter 294, 301
Floating Device State parameter 301
H
Floating Pool Name parameter 301 Hardware information 102
Floor plan 239 Headend and hubs devlist example 250
Forcing time synchronization 70 Headend graphics 242
FTP Headend IPs parameter 347
FTP Mode 24 Headend IPsec Filter parameter 347
FTP password 72 Headend IPsec Filter Properties dialog 343
Headend Policy Properties dialog 347
G
Headend racks devlist example 251
Gateway parameter 25, 34, 37 HFC plant monitoring 119
General tab 347 HFC-Plant-Monitoring tab 119
Generic Name parameter 140 High State Name parameter 144
Get Log File (via FTP) 62 Hub and nodes devlist example 251
getbackupdate instruction 222
getdevlist instruction 39 I
getdevtypelist instruction 43 ID label 11
getlogs instruction 62 Identification settings 141
getoptions parameter 259 Identify Agent by parameter 194
getscript parameter 283 IIOP Call Time Out parameter 95, 96
Graphic Displays view mode 54, 242, 243, 245, IKE 133
248 In backup for Device parameter 311
Graphic parameter 140 Individual Device Entries 41
Graphic Type parameter 40 Individual devices 233
Graphics 231 Input parameters 142
Cascade View 235 Input Router Audio Input parameter 306
Chassis view 235 Input Router Audio Layers parameter 306
Configuring 242 Input Router Audio Output parameter 306
Custom views 234, 239 Input router backup 306
Directed views 234, 235 Input Router Backup Script parameter 306
Example 250 Input Router parameter 306
Floor plan 239 Input Router Restore Script parameter 306
Group devices 234 Input Router Video Input parameter 306
Group of racks view 235 Input Router Video Layers parameter 306
Individual devices 233 Input Router Video Output parameter 306
Rack view 235 Input/Output functionality 140
Standard view 234 Inputs_Outputs tab 105, 142, 159
Star view 235 Installed Drivers dialog 193
Using 255 Installing Apollo drivers 170
Group Address parameter 40 Installing ROSA EM drivers 192
Group Description parameter 40 Installing scripts 283
Group device entries 40 Installing TNCS 207
Group devices 234 InstallShield Wizard 16, 20, 22
4005743 Rev N 381

Index
Integrated Backup Script parameter 294, 301 L

Integration into ROSA NMS 190
Integration into Third Party SNMP Management Label 11
209 Last Configuration Backup Status parameter
Integration into TNCS 207 222
Integration of ROSA EM 189 Last Configuration Restore Status parameter
Integration requirements 191 225
Integrity algorithm parameter 343, 366 Launching MMC 337
Integrity and Encryption Algorithms dialog 366 LED description 9
Internal Protocol Error messages 176 LEDs 9
Internal Temperature Unit parameter 105 License tab 216
Internet Explorer 5.0 Licensed Application Domains parameter 216
Installation 16 Licensing 216, 291
Internet key exchange 133 License parameters 216
Introducing ROSA EM 2 New license file 217
IP Address (range) From parameter 194 Upgrading license file 217
IP Address dialog 366 Linked devices 290
IP Address setting Linked to Device X parameter 294, 301
Using GUI 25 Local Control From Device Keyboard parameter
Using IP Configuration Tool 34 186
IP Config Tool 34 Local control settings 186
IP Filter Description and Mirrored property Location parameter 144, 148, 156
parameter 340 Location/ID parameter 152
IP Filter List dialog 340 Log information 61
IP Filter List tab 347 Log Severity Level parameter 81
IP Filter List wizard 340 Login As dialog 225
IP Filter Lists box 340 Login dialog 50
IP Filter Properties dialog 340 Login Failure 50
IP Protocol Type parameter 340 Look in box 193
IP Security 133 Low State Name parameter 144
IP Security Policies on Local Computer 337 M
IP Security Policy Name parameter 347
IP Security Policy wizard 347 M&C-Scan parameter 97
IP Traffic Destination parameter 340 Maintaining ROSA EM 215
IP Traffic Security parameter 343 Maintenance Complete page 20
IP Traffic Source parameter 340 Maintenance mode 112, 121
IPsec 133 Maintenance Mode parameter 121
IPSec Client IP-Address XX parameter 135 Major High parameter 152, 160
IPSec Pre-Shared Key XX parameter 135 Major Low parameter 152, 160
IPsec Settings tab 366 Major-Alarm High Limit parameter 104
IPSec tab page 134, 135, 136 Major-Alarm Low Limit parameter 104
Manage Filter Actions tab 343
K Manage IP filter lists and filter Actions dialog
340
Key exchange 133
Manage IP filter lists and filter actions parameter
Key exchange (Main Mode) parameter 366
Key exchange algorithm parameter 366 340
Managing ROSA EM equipment 200
Key Exchange Security Methods dialog 347
Mapping assigned devices 183
Key Exchange Settings dialog 347
Mapping into ROSA NMS 191
Key lifetime (in KB) parameter 366
Mapping new devices 181
Key lifetime (in minutes) parameter 366
Key parameter 360 Mapping ROSA Element Manager Agent 194
382 4005743 Rev N

Index
Maximum Log Lines dialog 61 New Connection Security Rule Wizard -

MD5 133, 343 Authentication Method dialog 360
MD5/SHA1 hashing 133 New Connection Security Rule Wizard -
Member accounts 266 Endpoints dialog 360
Activate Email 269 New Connection Security Rule Wizard - Name
Activate Paging 268 dialog 360
Activate SMS 270 New Connection Security Rule Wizard - Profile
Assigning to Notification Groups 272 dialog 360
Member n Email Active parameter 269 New Connection Security Rule Wizard -
Member n Email Address parameter 269 Requirements dialog 360
Member n Name parameter 266 New Connection Security Rule Wizard - Rule
Member n Notification Type parameter 266 Type dialog 360
Member n Pager Access Number parameter New Device dialog 182
268 New Devices tab 182, 184
Member n Pager Number parameter 268 New IP Filter List box 340
Member n Paging Active parameter 268 New Overhead Gateway parameter 126
Member n SMS Active parameter 270 New Route Apply Changes parameter 126
Member n SMS GSM Number parameter 270 New Routed Subnet Mask parameter 126
Member_Information tab 266 New Routed Subnet parameter 126
Message Settings 176 New Rule Properties dialog 347
Message(s) Properties dialog 176 NIC Teaming 131
Messages tab 176 Nodes and amps devlist example 253
MIB information 210 Nominal Value parameter 104
Compiling 212 Non-IPSec Traffic Management Port parameter
Downloading using FTP 211 134
Downloading using ROSA EM Configuration Non-IPSec Traffic Second NIC parameter 134
Tools 211 Notification Configuration parameter 274
SNMP Traps 213 Notification groups 272
Min Poll Period parameter 95, 96 Notification Initial Delay parameter 258, 274
Minor High parameter 152, 160 Notification Max Attempts parameter 274
Minor Low parameter 152, 160 Notification Max Sends parameter 258, 274
Minor-Alarm High Limit parameter 104 Notification Repeat Delay parameter 274
Minor-Alarm Low Limit parameter 104 Notification rules 274
Mirrored. Match packets with the exact opposite Notification Severity Level parameter 258, 274
source and destination addresses parameter Notification_Information tab 274
340 Notify Group n Members parameter 272
MMC main screen 337 Notify Group n Name parameter 272
Monitor privilege level 55 Notify Set A parameter 275
My IP Address parameter 340 Notify Set B parameter 275
Notify_Group tab 272
N NTP 69
Name parameter 91, 92, 140, 144, 148, 152, Number of Analog Inputs parameter 142
156, 160, 200, 340, 347, 360 Number of Analog Outputs 142
Negotiate Security parameter 343 Number of Controls parameter 163
Network Configuration 25 Number of Digital Outputs parameter 142
Network Delay parameter 187 Number of Galv Isol DI parameter 142
Network Name parameter 172, 173 Number of Non Galv Isol DI parameter 142
Network Time Protocol 69 Number of Status parameter 163
New Authentication Method Properties dialog Number of Temp Sensors parameter 142
347 Numeric Pager Post-dial Delay parameter 263
Numeric Paging Message parameter 263
4005743 Rev N 383

Index
O Port overview 319

Port parameter 91, 200
Obtaining license file 217 POWER LED 9
Off-Scan mode 112 Pre backup check script 294
Offset parameter 152, 156 Pre Backup Check Script parameter 294, 301
Open dialog 193 Present Value parameter 104
Opening the Apollo driver 170 Preshared Key parameter 360
Opening user interface 50 Pre-Shared parameter 136
Operation 3 Privilege Level parameter 55
Operator Accounts Product information 11
Adding 55 Product Package parameter 102
Deleting 57 Profile Type Information 194
Viewing 56 Properties tab 97, 102, 121, 140, 141, 220, 242,
Operator ID parameter 55 243, 245, 248, 275
Output parameters 142 Protocol parameter 366
Output Router Audio Input parameter 306 Protocol Version parameter 194
Output Router Audio Layers parameter 306 Proxi Devices 161
Output router backup 306 putdevlist instruction 47
Output Router Backup Script parameter 306 putlicense instruction 217
Output Router parameter 306 putoptions parameter 259
Output Router Restore Script parameter 306 putscript instruction 283
Output Router Video Input parameter 306
Output Router Video Layers parameter 306 Q
P Quick installation reference 325
Pager Modem Dial String parameter 263 R
Pager Modem Init String parameter 263
Rack positions 245
Pager Port Baudrate parameter 263
Rack Vertical Position parameter 40, 245
Pager Port Name parameter 263
Rack view 235
Pager Service Max Chars parameter 263
Range parameter 152
Paging service configuration 263
RCDS communication parameters 187
Paging_Service tab 263
Read Community parameter 194
Parameter 104, 144, 148, 152, 156
Regular backup 288
Parameters tab 104
Remappable units list 184
Passive FTP 24
Re-mapping existing devices 184
Passive parameter 24
Remote Sites
Password parameter
Adding 172
Admin 50
Checking 173
FTP 72
Properties 173
Operator ID 55
Removing 173
Storage 76
Remove scan range dialog 181
Telnet 72
Remove scan ranges 181
Performing a Manual NIC Switch Over 132
Remove Stale Instance Files parameter 227
Performing a Restore 225
Removing a DCM from the IPsec peers list 136
Persistence parameters 227
Removing clients form the IPsec peers list 135
Persistence tab 62, 227
Repetitive Alarm Observation Interval parameter
Physical Device Address parameter 41
83, 84
Plain Authentication 329
Repetitive Alarm Observation Window Alarm
Poll Counter parameter 140
Suppression parameter 83, 84
Poll Resources tab 194, 203, 204
Repetitive Alarm Stable Interval parameter 83,
Polling behavior 192
84
384 4005743 Rev N

Index
Repetitive Alarm Suppression Feature Routing 126

Configuring 84 Routing tab 126, 306
Introduction 83 RPC Port Number parameter 140
Repetitive Alarm Toggling Count parameter RS 232 DTE LED 9
83, 84 RS485 RCDS LED 9
Reporting active alarms 99 RS485/RS422 LED 9
Requests for Secure Communication parameter RUN LED 9
347 RX LED 9
Required authentication for inbound and
outbound connections parameter 360
S
Requirements 15 Save all Device Instance Changes Now
Resetting device parameters 114 parameter 227
Restore information 311 Scaling Factor parameter 152
Restore Mode parameter 294 Scaling parameter 156
Restore Script parameter 294 Scan ranges 179
Restore scripts 282 Scan Ranges tab 180
Restore transition 310 Scan Temperature Sensors parameter 159
restorebackupdata instruction 225 Script parameter 140
Retry Count parameter 194 Scripting
Return Frequency parameter 119 Backup scripts 282
ROSA Element Manager user interface 178 Custom scripts 285
ROSA EM Device scripts 282
Introduction 2 Installation 283
ROSA EM Agent 194 Introduction 282
ROSA EM alarm parameters 82 Restore scripts 282
ROSA EM applet message 220 Second NIC 124
ROSA EM Configuration Tools 14, 225, 259 Second NIC Apply Changes parameter 125
ROSA EM device Second NIC Current IP Address parameter 125
Restarting 116 Second NIC Current Subnet Mask parameter
ROSA EM device backup 222 125
ROSA EM Device Configuration GUI 198 Second NIC IP Address parameter 125
ROSA EM device restore 222 Second NIC Subnet Mask parameter 125
ROSA EM Device user interface 200 SecondNIC tab 125, 131, 132
ROSA EM drivers 192 Security levels 134
ROSA EM Graphical User Interface 198 Security Method dialog 366
ROSA EM Graphics 231 Security method preference order list box 347
ROSA EM Integration 189 Security methods box 366
ROSA EM Tools Environment 43, 62, 209, Security methods list 366
216, 218, 222, 225, 259, 283 Security Methods tab 343
ROSA EM/Altera software version parameter Select Components page 16
102 Select Computer or Domain dialog 337
ROSA NMS integration requirements 191 Select Device list 200
ROSA NMS system 4 Select Device parameter 200
ROSA/EM COM X port type parameter 102 Selective synchronization 206
ROSA/EM CompactFLASH Firmware Server-to-server parameter 360
parameter 102 Service Name parameter 41, 141
ROSA/EM CompactFLASH Model parameter Services 72
102
ROSA/EM CPU board type parameter 102
ROSA/EM mainboard hardware version
parameter 102
4005743 Rev N 385

Index
Active TCP/UDP ports 79 Start User Interface dialog 198, 200

Disabling 78 State parameter 144, 148
Enabling 78 Status parameter 148
Introduction 72 Status Source Point parameter 162
Session key perfect forward secrecy parameter Steps to take 7
343 Subnet Mask parameter 25, 34, 37
Set Deactivated Floating Backup Devices Summary Status parameter 81
parameter 301 Switch Over Command parameter 132
Set Local Time parameter 67 Switch Over Method parameter 131
Set Maximum Log Lines parameter 61 Switching Off Maintenance mode 121, 122
Setting the security level. 135 Switching On Maintenance mode 121, 122
Setting Up an IPsec Connection 353, 360 Switching on or off device polling 97
Settings dialog 220 Symbol parameter 140
Settings tab 186, 187 Synchronization Action parameters 203
Setup Status page 16, 20, 22 Synchronization action withe ROSA NMS 202
Setup Type page 16 Synchronization Interval parameter 68, 69
setupcommunities instruction 209 Synchronization Method parameter 68, 69, 70
Severity Color Code 100 Synchronization parameters 203
Severity parameter 82 Synchronize dialog 203, 204
Site Devices tab 186 Synchronize each parameter 203
Site Name parameter 172, 173 Synchronize Now parameter 70
Site Properties dialog 173 Synchronizing wih ROSA NMS 191
Sites tab 178 System log 61
SMS Pin Code parameter 265 system MIB 212
SMS Port Name parameter 265 System tab 96, 102, 114, 116
SMS service configuration 265
SMS Service Provider Number parameter 265 T
SMS_Service tab 265 Tabbed Panes view mode 53
SNMP Manager IP address parameter 212 TCP/UDP ports 79
SNMP Manager IP Address X parameters 106 Telnet password 72
SNMP parameters 106 Temperature probes
SNMP protocol 209 Configuring 160
SNMP Protocol user interface 194, 203 Identifying 159
SNMP tab 106, 107, 112 Introduction 158
SNMP Trap Community String parameter Temperature unit 105
SNMP Read Community String 75 Terminology 6
SNMP Write Community String 75 Testing backup configuration 308
Trap Community String 106 These IP addresses parameter 360
SNMP Trap Format parameter 106 Third-Party client 4
SNMP Trap Max Rate parameter 106 This IP address or subnet parameter 360
SNMP Trap Threshold parameter 106 Time synchronization 68
Soft Reset parameter 116 Time Synchronization tab 67, 68, 69, 70
Software information 102 Timeout parameter 194
Software log 61 Timeserver Address parameter 68, 69
Software Revision parameter 102, 220 Timezone parameter 69
Software Upgrading 218 TNCS
Software version 220 Installation 207
Source Device parameter 162, 163 Integration 207
Standalone tab 337 TNCS client 4
Standard view 234 tncstrap MIB 212
Star view 235 Toggling alarms 83
386 4005743 Rev N

Index
Topology example 128 Viewing all site devices 186

Total Instance File Write Count parameter 227 Viewing connected client computers 60
Trap buffering Viewing device log pages 61
Configuring 109 Viewing operator accounts 56
Introduction 108 Viewing Severity Color code 100
Trap buffering figures 111 Virtual Protocol Devices 161
Trap Generation for Maintenance Mode
parameter 122
W
Trap On Change parameter 144, 148, 152, 156 Web browser 4
Trap Regen For Active Alarms parameter 107 Windows 2000 SP 3
Trap Regen for Maintenance Mode parameter Installation 15
112 Windows Firewall with Advanced Security
Trap Regen for Off Scan Devices parameter dialog 360
112 Windows Firewall with Advanced Security on
Trap regeneration Local Computer dialog 366
Disabling 112
Trap regeneration active alarms 107
Trap scripts 282
Trap Traffic
Introduction 106
SNMP parameters 106
Traps 106
TX LED 9
U
Unacknowledges Alarm State parameter 81
Unassigning IPsec 352
Unit parameter 152, 156
update instruction 218
Upgrading license 217
Uploading device list 47
Use Add Wizard parameter 340
Use this string (preshared key) parameter 347
User Account Control 360
User Interface
Introduction 50
Opening 50
View modes 53
User Name parameter 50, 217, 225
UTC 69
V
Valid Client IP-Address parameter 59
Value parameter 152, 156
View group graphics 243
View headend graphics 242
View Mode
Graphic displays 54
Introduction 53
Tabbed panes 53
View rack positions 245
4005743 Rev N 387

Cisco Systems International BV Haarlerbergweg 13-19 Amsterdam, The Netherlands
www.Cisco.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.
2012 Cisco and/or its affiliates. All rights reserved.
January 2012 Printed in USA Part Number 4005743 Rev N

Rosa em - User's Guide - 4005743n

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Rosa em - User's Guide - 4005743n

Caricato da

Copyright:

Formati disponibili

4005743 Rev N

ROSA Element Manager

For Your Safety

4005743 Rev N iii

For Your Safety iii

4005743 Rev N vii

Installing Windows 2000 Service Pack 3................................................................ 15

Chapter 3 Configuring the ROSA EM System 49

viii 4005743 Rev N

Managing Services ................................................................................................................. 72

Device Backup Operation ................................................................................................... 118

Chapter 4 Configuring the Input/Output Functionality 139

To Configure an Analog Input .............................................................................. 154

Chapter 5 Configuring the Apollo Functionality 167

Chapter 6 Integration of ROSA EM 189

Getting MIB Information ....................................................................................... 210

Chapter 7 Maintenance 215

Chapter 8 Creating Graphics in ROSA EM 231

xii 4005743 Rev N

Using Graphics in ROSA EM ............................................................................................. 255

Chapter 9 Diverse Notification 257

Chapter 10 Scripting in ROSA EM 281

Chapter 11 Backup Operation 287

4005743 Rev N xiii

Appendix A Customer Information 315

Appendix B General Information 319

Appendix C Quick Installation Reference 325

Appendix D Email Function with Plain Authentication 329

Appendix E Additional Configuration 335

xiv 4005743 Rev N

4005743 Rev N xvii

About the ROSA Element Manager

a higher level network management system. When the ROSA EM system is

The southbound management interfaces are designed to communicate with the

Features and Benefits

Installation of the Device

Setup of the Device

Integration of the Device

Quick Installation Reference

COM1 COM3 COM5 COM6 COM7 COM8 CRAFT

LED Indicator Color Description

Installing the ROSA EM Configuration Tools

Windows 2000 with Service Pack 3a (*)

Installing Windows 2000 Service Pack 3

Perform the following steps to install Windows 2000 Service Pack 3.

Installing Microsoft Internet Explorer

To Install the ROSA EM Configuration Tools

4 Click on the Next > button.

5 Select the setup type.

- If you selected Custom setup, the following dialog displays.

The following ROSA EM Configuration Tools components can be selected or

To Repair the ROSA EM Configuration Tools

2 In the Readme.htm file of the ROSA EM Configuration Tools select the

4 Select Repair and click on the Next > button.

5 Press the Finish button.

To Uninstall the ROSA EM Configuration Tools

4 Select Remove and press the Next > button.

5 Click on the OK button to remove the ROSA EM Configuration Tools or the

6 Press the Finish button.

Changing the FTP Mode

DIGITAL INPUT PORT 3 DIGITAL INPUT PORT 7 RELAYS PORT 2

COM 8 DIGITAL INPUT 4

COM 6 COM 8 1 - 8 AN IN + G A LV .ISO L. D I DIGITAL I/O 1 15 14 RELAYS PORT 7 21 20