TM 87 10049 - RevA - OTS v5 00 01

Opti-Trace OTS
Shelf Management Software

Version 5.00.01
Installation and Configuration Guide
TM 87-10049 Rev. A
OTS Software Installation and Configuration Guide
Copyright © 2006 Aurora Networks. All rights reserved.
All rights reserved. No part of this document may be reproduced, stored in a retrieval system, or transmitted, in any form or
by any means, electronic, mechanical, photographic, magnetic, or otherwise, without the prior written permission of Aurora
Networks.
Aurora Networks makes no representations, express or implied, with respect to this documentation or any of the software it
may describe, including (with no limitation) any implied warranties of utility, merchantability or fitness for any particular
purpose. All such warranties are expressly disclaimed. Neither Aurora Networks nor its distributors or dealers shall be liable
for any indirect, incidental or consequential damages under any circumstances.
(The exclusion of implied warranties may not apply in all cases under some statutes, and thus the above exclusion may not
apply.)
Specifications are subject to change without notice. Every attempt has been made to make this manual complete, accurate,
and up-to-date. Readers are cautioned, however, that Aurora Networks reserves the right to make changes without notice and
shall not be responsible for any damages, including indirect, incidental or consequential damages, caused by reliance on the
material presented, including, but not limited to, omissions, typographical, arithmetical, or listing errors in the material.
Revision Date ECO

Rev A Initial release. 10/03/06 1090
Visit www.aurora.com for the latest documentation release information.

Aurora Networks, Inc.
2803 Mission College Blvd.
Santa Clara, CA 95054
Phone 408.235.7000
Fax 408.845.9045
www.aurora.com
i-ii TM 87-10049 Rev. A

Table of Contents
Preface .......................................................................................................... Preface-i
Intended Audience ....................................................................................... Preface-i
How to Use this Guide ................................................................................. Preface-i
Conventions ................................................................................................. Preface-ii
Related Documentation ............................................................................... Preface-iii
Product Support ........................................................................................... Preface-iii
Comments and Feedback ............................................................................ Preface-iii
Chapter 1 Introduction to Opti-Trace OTS Shelf Management Software ......... 1-1
1.1 What is Opti-Trace OTS Shelf Management Software?................................... 1-1

1.2 Major Management Functions and Features.................................................... 1-2
Chapter 2 Installing OTS ...................................................................................... 2-1
2.1 Software Package Contents ............................................................................. 2-1

2.2 System Requirements ...................................................................................... 2-1
2.3 PC Network Requirements ............................................................................... 2-2
2.4 Example Modules ............................................................................................. 2-2
2.5 Install Recommendations ................................................................................. 2-2
2.6 Required Module Software Version Updates ................................................... 2-3
2.7 Updating Existing OTS Software ...................................................................... 2-3
2.8 Installing the Software Using the CD................................................................ 2-3
2.9 Downloading the Software Using the Web ....................................................... 2-3
2.10 Uninstalling the Software................................................................................ 2-8
2.10.1 Files Removed during Uninstall................................................................... 2-8
2.10.2 Effect on DLL Files during Uninstall ............................................................ 2-9
2.10.3 Potential Failure to Update MIB Files .......................................................... 2-9
Chapter 3 Overview of OTS Graphical User Interface ....................................... 3-1
3.1 Getting Started ................................................................................................. 3-1

3.2 Navigational Tools and GUI Components ........................................................ 3-3
3.3 Main Window .................................................................................................... 3-3
3.4 Main Menu and Submenus............................................................................... 3-4
3.5 Modules and Alarms Toolbar............................................................................ 3-6
3.6 Standard Editing Toolbar.................................................................................. 3-7
3.7 Main Window Icons and Definition ................................................................... 3-8
3.8 Trap Manager Bar ............................................................................................ 3-9
Chapter 4 Introducing the Interface Tabs ........................................................... 4-1
4.1 Accessing Detailed Module Information Via Tabs ............................................ 4-1

4.1.1 Refresh Button............................................................................................... 4-2
4.2 Status Tab ........................................................................................................ 4-2
4.3 Alarms Tab ....................................................................................................... 4-3
TM 87-10049 Rev. A iii

4.3.1 Controlling Alarms..........................................................................................4-7
4.3.2 Color-Coded Alarm Definitions ......................................................................4-7
4.4 User Setup Tab.................................................................................................4-8
4.4.1 Entering Values in Editable Fields .................................................................4-9
4.5 Module Info Tab ................................................................................................4-10
4.6 Module Specific Tabs........................................................................................4-11
Chapter 5 Basic OTS Operations .........................................................................5-1
5.1 Summary Objectives.........................................................................................5-1

5.2 Connecting to a Chassis ...................................................................................5-2
5.2.1 Access Levels and Default Passwords ..........................................................5-3
5.3 Saving Chassis Configuration to a File .............................................................5-3
5.4 Opening a Module.............................................................................................5-6
5.5 Updating Cache ................................................................................................5-7
5.6 Clearing Shelf History .......................................................................................5-8
5.7 Polling Chassis Devices....................................................................................5-8
5.8 Saving SNMP Operations to a Log File ............................................................5-10
5.9 Naming Devices for Easy Management............................................................5-12
5.10 Setting Up Trap Host List................................................................................5-14
5.10.1 Standard Trap Configuration........................................................................5-15
5.11 Setting Shelf Alarm Trap Replay and Transceiver Alarm Summary ...............5-15
5.12 Viewing Traps .................................................................................................5-18
5.12.1 Configuring Alerts and Sounds for Incoming Traps .....................................5-20
5.12.2 Deleting Traps from the Trap View Window ................................................5-23
5.12.3 Saving Traps to a File ..................................................................................5-24
5.13 Viewing/Saving Trap Logs to File ...................................................................5-24
5.13.1 Clearing Trap Log History ............................................................................5-26
5.14 Configuring OTS Email for Trap Alarms .........................................................5-27
5.14.1 Adding a Recipient’s Email Address ............................................................5-28
5.14.2 Deleting a Recipient.....................................................................................5-29
5.14.3 Editing a Recipient .......................................................................................5-29
5.14.4 Configuring the Email Server .......................................................................5-29
5.14.5 Viewing Email Statistics and Sending Test Email........................................5-30
5.15 Configuring CX/NI Modules for Email .............................................................5-31
5.16 Updating Software on CX/NI Modules ............................................................5-31
Chapter 6 Configuring CX3001 Communications Module .................................6-1
6.1 Summary Objectives.........................................................................................6-1

6.2 CX3001 Communications Module Description .................................................6-1
6.3 Prerequisite Hardware and Software Installation Requirements ......................6-3
6.4 CX3001 Status Tab...........................................................................................6-3
6.4.1 CX3001 Status Attributes...............................................................................6-4
6.5 CX3001 Alarms Tab..........................................................................................6-5
6.5.1 RF Alarm, Backup Power Alarm, and Clear Alarm History Configuration......6-6
iv TM 87-10049 Rev. A
6.5.2 CX3001 Alarm Attributes ............................................................................... 6-8
6.6 CX3001 User Setup Tab .................................................................................. 6-9
6.6.1 Setting System Time ..................................................................................... 6-10
6.6.2 CX3001 User Setup Attributes ...................................................................... 6-11
6.7 CX3001 Module Info Tab.................................................................................. 6-11
6.7.1 Module Info Attributes.................................................................................... 6-12
6.8 Performing Software Upgrades on CX3001 ..................................................... 6-12
Chapter 7 Additional Chassis Module Examples ............................................... 7-1
7.1 DR3002 Digital Receiver .................................................................................. 7-2

7.2 FA3524S Optical Amplifier ............................................................................... 7-11
Appendix A Color-coded Icons and Definitions ................................................... A-1
A.1 Generic System Icons ...................................................................................... A-1
A.2 Device Icons..................................................................................................... A-2
Appendix B Error Messages .................................................................................. B-1
B.1 Error Messages................................................................................................ B-1
Appendix C Resource mib File .............................................................................. C-1
C.1 System3000.mib File ....................................................................................... C-1
TM 87-10049 Rev. A v
This page intentionally left blank.
vi TM 87-10049 Rev. A
List of Tables
Table 2-1 System Requirements ................................................................................... 2-1
Table 2-2 Example Modules and Models ...................................................................... 2-2
Table 3-1 Menu/Submenu Commands and Descriptions.............................................. 3-5
Table 3-2 Modules/Alarms Icon Definitions .................................................................. 3-7
Table 3-3 Main Window Icons and Definition ................................................................ 3-8
Table 3-4 Trap Manager Bar Icons ............................................................................... 3-9
Table 4-1 Alarms LEDs for Active Alarm and History States......................................... 4-7
Table 6-1 CX3001 Communications Module Status Attributes and Definition .............. 6-4
Table 6-2 Service Affecting and Non-Service Affecting Alarms .................................... 6-8
Table 6-3 CX3001 Communications Module User Setup Attributes and Definition....... 6-11
Table 6-4 CX3001 Communications Module Info Attributes and Definition .................. 6-12
Table A-1 Generic System Icons and Definitions .......................................................... A-1
Table A-2 OTS Color-coded Icons and Definitions ........................................................ A-2
Table B-1 System Error Messages: Cause/Corrective Action ....................................... B-1
TM 87-10049 Rev. A vii

viii TM 87-10049 Rev. A

Preface
This preface provides important information that you should know prior to using the Opti-Trace OTS
application. Topics include the following:
• Intended Audience
• How to Use This Guide
• Conventions
• Related Documentation
• Product Support
• Comments and Feedback
Intended Audience
This guide is intended for qualified network administrators and operators who are responsible for network status
and alarm monitoring using the Opti-Trace OTS Shelf Management application
How to Use this Guide
The following is a summary of each chapter in this guide.
Chapter Summary
Chapter Summary
Chapter 1 Introduction to Opti-Trace OTS Shelf Introduces the users to the OTS application by
Management Software describing major features and functions
Chapter 2 Installing OTS Shows step-by-step CD and web installation

procedures
Chapter 3 Overview of OTS Graphical User Provides a brief description of the GUI tools and
Interface functions with associated GUI icons
Chapter 4 Introducing the Interface Tabs Defines and illustrates the four major interface tabs:
Status, Alarms, User Setup and Module Info that are
used to access crucial module information
Chapter 5 Basic OTS Operations Provides the most common operations that a
network administrator and/or operator uses to
monitor the installed modules in a shelf.
Chapter 6 Configuring CX3001 Communications Describes how to configure the CX3001

Module Communications Module using its associated tabs
TM 87-10049 Rev. A Preface-i

Chapter Summary (Continued)
Chapter Summary
Chapter 7 Additional Chassis Module Examples Illustrates through examples, additional modules
and their associated tabbed screens for the DR3002
Digital Receiver Module and FA3524S Fiber
Amplifier
Appendix A Color-coded Icons and Definitions Lists and defines, in tabular form the OTS color-
coded icons
Appendix B Error Messages Lists and defines, in tabular form the OTS system
error messages and popup windows
Appendix C Resource mib File Provides as an example a partial listing of the

system3000.mib file
Conventions
The following symbols represent the conventions used in this guide.
Symbol Description
WARNING! This symbol is used to identify
conditions or actions that could seriously injure
personnel, for example, an electrical shock hazard.
CAUTION! This symbol is used to identify situations

that present minor hazards that can interfere with or
threaten equipment or system performance.
This symbol identifies important points in the text.
Preface-ii TM 87-10049 Rev. A

Related Documentation
Refer to Aurora Network’s website at www.aurora.com for the latest product information and documentation
updates. The website includes a special customer support area (password required) for Aurora customers.
The following lists both the software and hardware guides that are associated with this guide.
Related Documentation TM Number

Opti-Trace EMS Element Management Software Installation and 87-10048
Configuration Guide
Opti-Trace CMS Craft Management Software Installation and Configuration 87-10050

Guide
FA3500 Series Optical Amplifiers Installation and Activation Guide 87-10037
DR3000 Digital Receivers Installation and Activation Guide 87-10040
NC4000 Optical Node Installation and Activation Guide 87-10051
CH3000 Chassis Installation and Activation Guide 87-10029
Note: Go to www.aurora.com and select the Customer Support Area (under Technical Support) for the latest
revisions of user documentation. The Customer Support Area requires a password. If you don’t have a
customer password, send email to support@aurora.com to request one.
Product Support
For technical support: phone 888.AURORA6 (888.287.6726) toll free or email support@aurora.com.
For comments or questions about this guide: phone 408-235-7061 or email techpubs@aurora.com.
Comments and Feedback
We have made every effort to ensure that this guide describes the product completely and correctly, and we
encourage your feedback—your comments and corrections are welcome. You may submit comments using the
Technical Manual Comment Form provided at the back of this guide, by mail or fax, or by sending email directly
to techpubs@aurora.com.
TM 87-10049 Rev. A Preface-iii

Preface-iv TM 87-10049 Rev. A

Chapter 1 Introduction to Opti-Trace OTS Shelf
Management Software
This chapter provides a brief description of the Opti-Trace OTS Shelf Management Software application. It
specifically covers the following major topics:
• What is Opti-Trace OTS Shelf Management Software
• Major Management Functions and Features
This guide applies to Version 5.00.01 of the Optic-Trace OTS Shelf Management Software application.
1.1 What is Opti-Trace OTS Shelf Management Software?
The Opti-Trace OTS Shelf Management (OTS) with system3000.mib v1.33, is a Microsoft® Windows-based
application.
Aurora Networks OTS program is a Graphical User Interface (GUI) application that can be loaded on a PC
running Windows 2000/XP® operating system.
This application monitors and controls applicable Aurora Networks plug-in modules installed in any CH3000
chassis, using SNMP protocol over your network. The following graphic depicts a CH3000 chassis with an
installed CX3001 Communications Module connected to an operator’s PC.
&;W\SLFDOO\UHVLGHVLQ
VORWRIWKH&+FKDVVLV

TM 87-10049 Rev. A 1-1

OTS Software Installation and Configuration Guide
Once installed, the OTS can be used to monitor and control network elements installed in the CH3000 Chassis
(or shelf). The OTS communicates with the hardware layer (via 10BaseT and RJ45 interface) using the SNMP
agent residing in an Aurora Networks CX3001 Communications Module.
The OTS complements monitoring of Aurora Networks’ optical transmission platforms and associated network
elements through higher-level management systems. It allows for quick configuration via SNMP and supports
diagnostic functions in the event that alarm conditions are detected in any of the monitored platforms.
Being an SNMP-based application, OTS allows you to monitor and control all active modules on the shelf in an
IP-based network. Similar to Aurora Networks’ Craft Management System (CMS), OTS provides access to
selective alarm and configuration information from external broadcast transmitters and fiber nodes.
1.2 Major Management Functions and Features

The OTS software application:
• Presents consolidated display of module alarm status in the shelf
• Controls and provides status monitoring of CH3000 network elements and status monitoring of NC4000
series nodes
• Provides SNMP-based management
• Manages multiple CH3000 Chassis and nodes (requires unique IP address for each chassis)
• Allows users to set up trap receiver lists on any active shelf
• Receives traps from the device and display
• Retrieves trap history from the shelf
• Provides user-friendly labeling feature associated with module model and serial number (Device Labels)
1-2 TM 87-10049 Rev. A

Chapter 2 Installing OTS
This chapter describes how to install the OTS software by using the CD or by using the web and covers the
following major topics:
• Software Package Contents
• System Requirements
• PC Network Requirements
• Sample Minimum Installed Modules
• Install Recommendations
• Version Compatibility between Management and MIB
• DLL and Other System Support Files Used by OTS
• Required Module Software Version Updates
• Updating Existing OTS Software
• Installing the Software Using the CD
• Downloading the Software Using the Web
• Uninstalling the Software
2.1 Software Package Contents

If you purchase the OTS rather than downloading and installing the software via Aurora Networks website, you
receive two installation CDs:
• OTS CD
• EMS CD (Element Management Software)
This guide covers specifically the OTS application. For details concerning the EMS application,
see the “EMS Installation and Configuration Guide” (TM 87-10048).
2.2 System Requirements

The following table lists the OTS system requirements.
Table 2-1 System Requirements
OTS
Windows 2000/XP®
IBM PC compatible
256 MB RAM (minimum)
CD-ROM drive
SVGA (16-bit color enabled)
Mouse
Network connection
File Size: ~2.31Mb
TM 87-10049 Rev. A 2-1

Opti-Trace OTS Shelf Management Software
2.3 PC Network Requirements

If you are installing the OTS/EMS onto a PC, you must make sure that your PC is configured for IP
communications and has the following capability:
• 10BaseT Ethernet connection
• Management access to the managed IP network on which the CX3001 Communications or NI3000 Network
Interface Management Module resides
For a Direct Local Connection from PC to CX3001 Communications Module

In newer PCs that are already equipped with a 10/100BaseT Ethernet Network Interface Card
(NIC), the NIC can be configured for default operation at 100BaseT. If this is the case, and if the
computer is being used for direct communications with a management module via a crossover
CAT5 cable, the NIC must be re-configured for 10BaseT operation or 10/100 Auto-negotiation.
Otherwise, communications with the management module is not possible.
2.4 Example Modules

The following table lists as an example, the modules and their associated models that are illustrated in this guide.
Table 2-2 Example Modules and Models
Modules Models
PS3xxx Power Supply PS3002, PS3048
CX3xxx Communications Module CX3001
AT3xxx Analog Transceiver AT3300 Series
DR3xxx Digital Receiver DR3000 Series
FA 3xxx Fiber Optical Amplifier FA3500 Series
Optical Node Platform NC4000 Series
2.5 Install Recommendations

• Users must have “administrative” privileges on your operating system prior to install.
• Close all programs prior to install.
• If a previously installed version of Opti-Trace OTS, CMS, and/or EMS exist, Aurora Networks
recommends that you remove these programs prior to installing the latest or newer versions.
If you do not uninstall any older versions or were not aware of a previously installed version,
during installation an install dialog window will display prompting to repair or remove the older
version. Always select the “Remove Aurora Opti-Trace” option prior to installing a new
version.
• When presented with a choice by the setup program of performing a “Complete” or “Custom” installation,
for this version, Aurora Networks recommends installing the “Complete” only installation.
• Install the OTS prior to installing the EMS.
• Install new updates for both OTS and EMS.
2-2 TM 87-10049 Rev. A

2.6 Required Module Software Version Updates

Version 5.00.01 of OTS is backward compatible with earlier versions of OTS and can provide status monitoring
of all active devices in the Aurora Networks CH3000 Chassis of which earlier releases were capable. While
v5.00.01 provides additional features not found in earlier releases, these added capabilities require that
embedded software in the CX3001 Communications Module be upgraded to Revision 3.14 or higher.
To determine exactly what version of software you are currently running on the CX3001 module, see
Appendix 6, CX3001 Module Info Tab.
After reviewing Chapter 6, if you are uncertain about the CX30001 Communications Module
upgrading procedures, contact Aurora Technical Support.
2.7 Updating Existing OTS Software

If you are simply updating an older version of the OTS software application, Aurora Networks highly
recommends removing any and all existing versions prior to installing the latest version of OTS.
2.8 Installing the Software Using the CD
Aurora Networks highly recommends that you install the OTS prior to installing the EMS, if you
are installing the EMS.
1. Insert the CD into your CD drive and follow the instructions on the popup screens.
If the installation doesn’t start automatically, execute the Setup.exe file on the CD.
2. Select the Complete setup type.
As an example, the following graphic represents the Opti-Trace Shelf desktop shortcut icon.
For detailed software issues and concerns, see Aurora’s website/application notes at:
http://www.aurora.com/support. Then login using your private customer area login and click
the Opti-Trace Software link.
2.9 Downloading the Software Using the Web

You must first set up an account as a customer to obtain a login name and password in order to access the
password-protected page.
Your login name and password are required at Aurora’s password protective page at the website.
If you do not already have administrative privilege, contact technical support in an email at http://
www.aurora.com/support/index.html to request your user name and password. In turn, Aurora Networks then
will supply you with your username and password. Once you become a private customer, you will have access
rights to download the software.
TM 87-10049 Rev. A 2-3

Although the following instructions focus on downloading the OTS software, the steps are
basically the same for the other two types of management software.
1. Access the Aurora Networks website and select Technical Support, which opens the Overview
page.
2. Click the password-protected customer area link.
The Customer Support Area page displays. You may at this time want to bookmark this page for
future use and read the Customer Support Area page carefully to learn about the following
download requirements:
• Browser Requirements
• About Logging In and Popup Blockers (You MUST disable the popup blocker.)
3. Click the Please log in with your assigned username and password here link.
4. Enter your username and password, as shown. Two sequential windows will display. The first one
requests your username; the second popup window requests your password.
5. Upon entering your username and password, the Thank you screen displays. Click OK.
The Customer Support Area Index page displays.
2-4 TM 87-10049 Rev. A

6. Click the Other Collateral icon, located at the top far- right side of the page to access the software
download link.
The Opti-Trace Software page displays and here is where you can select the hot link to
download the software.
TM 87-10049 Rev. A 2-5

7. Click the here hot link to request your password(s) for installing one or more of the packages (either
before or after downloading the file(s).
As a result the Opti-Trace Software Password Request form page displays.
If you did not previously apply for a password to download the software, you must fill out the
Opti-Trace Software Password Request form as indicated earlier.
8. If you already have a password, click the hot link OTS to download your required software.
Remember to keep track of your download location. The executable installation file that you
download as an example may be titled OTS_v5-00-24_Web-Install_Aurora.exe and should
look similar to the following desktop icon.
9. Double-click the desktop icon or locate the executable file to open the application.
The following window displays, prompting you for your password.
10. Enter the password. Then click OK.
2-6 TM 87-10049 Rev. A

11. Continue to follow the instructions on each page that appear on your screen to complete a
successful installation.
If using Internet Explorer with Microsoft’s new enhanced security features to perform the
download/install, you may see the following windows.
As mentioned earlier in this chapter, if you are not logged in as “administrator” with administrative privileges,
you will see the following popup window. As a result, some of the necessary support files will not be copied onto
your system.
For successful installation on your company’s particular system, you as the user must be logged in as
“administrator”. If your company has special policies regarding the downloading of executable files, contact
your IT department.
TM 87-10049 Rev. A 2-7

The following shows an example of the Opti-Trace Shelf desktop shortcut icon.
2.10 Uninstalling the Software

There are two ways to uninstall any of the Opti-Trace applications.
One method is to use the standard “Add/Remove Programs” function from the Windows Control Panel (and this
is the only method available for uninstalling Opti-Trace applications that have been installed from downloaded
web-based versions.)
For newer versions of OTS (v3.19.34 and later) and CMS (v2.15.34 and later) that were installed from CD-based
media, the original CD can be used to uninstall the application by selecting the “Remove” option from the
installation program's main menu (displayed when the original CD is run and auto-discovers an existing
installation of the program on your system).
Uninstalling OTS using the Windows Control Panel “Add/Remove Programs” function to remove the Aurora
Opti-Trace Shelf application is equivalent to using the “Remove” option provided with the OTS installation CD.
2.10.1 Files Removed during Uninstall
The application (.exe file) and all other files that have not been modified except the MIB and most .dll files are
removed during the uninstall. OTS or EMS uninstall may leave the MIB files because they are shared between
these two programs. (In general, uninstallation will remove the MIB files if they have not been modified.) In
addition, the OTS uninstaller will remove its associated 3rusnmp.dll file.
2-8 TM 87-10049 Rev. A

2.10.2 Effect on DLL Files during Uninstall

Most .dll files that were installed (or updated) in the Windows system directory will not be uninstalled. The
exceptions are two files (dartsnmp2.dll and dartsock.dll, included with OTS for SNMP and Winsock controls)
that will be removed during an OTS uninstall unless they have also been registered by Windows for use with
another application. In addition, the 3rusnmp.dll file included with OTS and installed in the same location as its
.exe file will be removed during an uninstall.
2.10.3 Potential Failure to Update MIB Files
There are three possible cases in which the MIB files may not be updated during installation.
• The MIB may be in use by some other application, for example EMS.
• The file timestamp on the MIB already installed on the system is later than the version included with the
installation program.
• The MIB file already installed on the system might be registered as a shared file (by another application), in
which case the installer is not permitted to replace it.
Except for these three scenarios, the OTS installer should be able to update MIB files.
If the OTS installer is prevented from updating the MIB files, the solution is to manually delete the existing MIB
files from the system and perform a reinstall. (For the web-based version, simply re-run the downloaded
installation program. For the CD-based version, insert the CD and select the “Repair” option from the installation
menu.
TM 87-10049 Rev. A 2-9

2-10 TM 87-10049 Rev. A

Chapter 3 Overview of OTS Graphical User Interface
This chapter explains how to open the OTS application and provides brief description of the main window items
of the GUI such as the main menu/submenus, icons, and bars that display when you open the application.
This chapter specifically covers the following:
• Getting Started
• Navigational Tools and GUI Components
• Main Window
• Main Menu and Submenus
• Modules and Alarms Toolbar
• Standard Editing Toolbar
• Trap Manager Bar
A more detailed description of these menu items and icons are explained in detail later in this chapter and in
additional chapters where most appropriate.
3.1 Getting Started

To open the application, simply go to Start>All Programs>Aurora Opti-Trace>Opti-Trace Shelf.
The OTS by default is placed in the Program Files folder.
Click either the OTS icon if displayed as a desktop icon or locate the Opti-Trace Shelf executable in the Program
Files folder or where locally stored on your PC.
The following graphic is an example of a shortcut Opti-Trace Shelf desktop icon.
Upon opening the GUI for the first time, the OTS application attempts to connect to a module with an IP address
of 127.0.0.1 (default address used by OTS).
As a result, a popup window will display as shown indicating that the connection to the host failed. Remember
and as described in Chapter 1, in order to establish a successful connection to the module/chassis, you must
determine a valid IP address. For a brief overview of the connection process, see the following steps and for a
detailed description, see Section 5.2.
Upon clicking OK, the OTS interface displays with the following banner:
127.0.0.1 - Aurora Opti-Trace Shelf - Connection Failed.
TM 87-10049 Rev. A 3-1

The last IP address entered upon a successful connection prior to closing the application brings
up or uses that IP address when re-opening the OTS.
To make a connection to a an active chassis using a valid IP address:
1. Click the Connection Options icon located on the main window.

The Connection Options... default window displays.
2. In the IP Address field, enter a valid IP address.
You may use the CMS application or the front panel of the power supply to view the currently
assigned IP address of the CX3001 Communications Module.
To learn how to determine a valid IP address and details pertaining to connecting to a chassis, see Section 6.
3-2 TM 87-10049 Rev. A

Installation and Configuration
3.2 Navigational Tools and GUI Components

The OTS GUI is a typical Windows-based application that provides the following navigational and informational
features:
• Hoverable (identifiable) icons and buttons with mouseover (tool tips)
• Dockable and customizable main window toolbars (re-position/separate out bars/panels)
• Resizable table columns
This graphic illustrates the hoverable capabilities of OTS when you mouseover a module icon. This graphic
also shows as an example, that a power supply (PS3002N) resides in Slot 16 and is in normal operating
(green-colored icon) condition.
3.3 Main Window

The following graphic (partially shown) shows a typical view of the OTS main window (default view) upon
making a successful connection. It specifically shows connection to a 32-slot CH3000 chassis with an IP address
of 10.10.110.161.
This graphic shows a preconfigured view of the shelf with all View submenu commands enabled (default) and
with an IP address of 10.10.110.161. Note that the right-most slot is reserved for an external (Ext) module.
Main Menu
Modules/
Alarms Bar
Toolbar
Slot Bar
Status Bar
TM 87-10049 Rev. A 3-3

As stated previously, you can re-arrange the tool bars to your liking. The above graphic is an example of a
customized main window modified by the end user with an IP address of 10.10.110.161. In this case, the user
logged in as an Operator.
When opening/closing the OTS and when accessing a different chassis (different IP address),
your customized main window remains intact.
You can turn off polling at your discretion. Aurora Networks recommends that polling be turned
off when you are performing any management operation.
3.4 Main Menu and Submenus
The following graphics illustrate typical-looking main menu commands and their submenus. See
Section 5 Basic OTS Operations to learn how to use these commands.
The View menu defaults with all its submenus enabled (checked).
The following table lists and defines the main menu and submenu commands.
3-4 TM 87-10049 Rev. A

Table 3-1 Menu/Submenu Commands and Descriptions
Menu Submenu Description

File
Open... (Ctrl+O) Opens the specified module that is listed in the Slot drop down box.
Save Chassis Configuration... Saves the current chassis configuration of the installed modules.
(Ctrl+S) Recommend using a user-friendly file naming convention for future
use/retrieval. Opens the Save Chassis Configuration dialog box. See
Section 5.3.
Exit Exits the program.
View Toolbar When enabled (checked), displays the nine icon bars
(commands) on the main window.
Status Bar Shows the Status Bar at the bottom of the main window.
Slots Displays the Slot drop-down box (1-32 + External) modules and Open
button.
Alarms Displays the summary status of all installed, active modules (color-
coded/slot numbered icons).
Polling Bar Displays the Start Polling button and time interval drop-down box.
Intervals range from 2 sec. to 10 min. for polling cycle.
Update Cache Bar Displays the Update Cache button. See Table 3-3.
Clear Shelf History Bar Displays the Shelf Summary Alarm and the Clear Shelf History button.
See Table 3-3.
Trap Manager Displays the Trap Manager Bar. See Table 3-3.
Front Panel Bar Not implemented at this release.
Options Board...(Ctrl+B) Displays the Board Options dialog box for setting Polling and Board
options. See Appendix 5.7 and Appendix 5.8.
Connection...(Ctrl+E) Displays the Connection Options dialog box for setting IP Address and
Security and Timeouts (mS) parameters. See Appendix 5.2.
General...(Ctrl+G) Displays a General Options dialog box for setting the time in secs. for
Shelf Alarm Trap Replay and Maximum Log Entries. Log entries range
form 8-100. See Appendix 5.14 for details on how to configure for
General Options.
Host List...(Ctrl+H) Displays the Trap Receiver List dialog box for setting up and receiving
traps. See Table 3-3. See Appendix 5.12.
CX/NI Email Prior to using this feature, you must have an installed CX/NI module.
Configuration...(Ctrl+M) This feature allows you to add/delete/modify email recipients to
receive emails pertaining to traps, such as Major, Minor, Info, and
Normal. Not implemented in this release.
Alerts and Sounds...(Ctrl+L) Allows you to configure the system to receive alerts and sounds for
receiving traps. See Appendix 5.15.
Abort Aborts the current SNMP operation.
TM 87-10049 Rev. A 3-5

Table 3-1 Menu/Submenu Commands and Descriptions (Continued)
Menu Submenu Description

Tools Software Update Tool... Updates the firmware using the controller file (ControllerVersion.txt).
See Section 6.8 to learn how to update new firmware for the CX3001
Communications Module and the NI3000 Network Interface Module.
OTS Email Configuration... Displays the OTS Email Configuration dialog box to setup email
recipients to receive emails pertaining to traps. See Appendix 5.14.
Help About Opti-Trace Shelf... Displays the About Opti-Trace Shelf window for version and copyright
information.
About Device... Displays the About Device window, listing pertinent information
associated with the active chassis, such as IP address, system up
time, model serial number and slot number of NI/CX, device system
MIB version, and OTS system MIB version. See Appendix C.
3.5 Modules and Alarms Toolbar

One of the primary purposes of OTS is to provide indications of the module’s alarm summary state.
Simply observing the color-coded module icons on the main window indicates the current alarm condition (or no
alarm when green).
The Modules and Alarms Toolbar displays up to 32 modules plus an external module in a chassis. Color-coded
icons identify the state (health) of each module (see Table 3-2 for colored icon definitions) and provides the
following module information:
• Slot numbers (1-32)
• Module Name (either graphically or textual)
• Module State (indicated through color, for example red in Slot 5 indicates that the NI3000 network
interface module has an alarm condition.)
From the Modules and Alarms Toolbar, you can open a module by clicking the module icon.
Not all of Aurora Networks’ modules are presented in this graphic.
3-6 TM 87-10049 Rev. A

Table 3-2 Modules/Alarms Icon Definitions
Modules/
Alarms Definition
Icons
Grey - Indicates that the slot is either not populated or that a passive (unknown) module such as an
optical splitter resides in this slot.
Red - Indicates that a module at one time in the past did reside in the specified slot. The tabbed
windows associated with this particular module will still display and present the Status, Alarms, User
Setup, and Module Info data of the former module. This also indicates that the operator did not select
the Clear Shelf History button after removing the installed module from the chassis.
Green - Indicates that the module has no active alarms.
Red - Indicates active, major alarm on the module, service affecting.
Yellow - Indicates active minor alarm on the module, non-service affecting.
Blue - Indicates no active alarms. This particular module had an alarm at one time. Does not change
color until you select the Clear History button.
N - Indicates a new module has been detected by OTS, but OTS cannot monitor/control this particular
module at this time.
3.6 Standard Editing Toolbar

The Standard Editing Toolbar consists of the typical Window’s-based icons/commands.
See the following table for definitions of all the main window icons.
TM 87-10049 Rev. A 3-7

3.7 Main Window Icons and Definition

The following table lists and defines the main window icons.
Table 3-3 Main Window Icons and Definition
Icon Symbol Icon Name Definition

Cut, Copy, Paste Not implemented at this release.
About Displays the version number and copyright

information related to current software.
Connection Options Connects to user-entered IP address for a

specified chassis.
Abort Aborts the current SNMP communication. For

example, if while connecting to an IP address,
you determine that you entered an incorrect
address, simply click the Abort button.
Folder and Slot Selection Opens the management information window for
Drop-down Box the device of the selected slot.
Polling Allows you to start/stop polling for active

devices in the chassis. Polling intervals range
from 2 sec. - 10 min.
Update Cache Updates the most recent information for the

specified module (maintained on the CX3001)
See Section 5.5.
Shelf Summary Alarm Displays on the main window and shows in

either green for normal state, red for major
alarm state, yellow for minor alarm state, or
blue for alarm history state. This is a
display-only icon.
Clear Shelf History Clears the entire shelf/chassis of all history

alarms for all the active modules installed in the
shelf.
Front Panel Display Not implemented at this release.
Because the above listed icons/buttons are rollovers, their function is displayed in the Status bar.
3-8 TM 87-10049 Rev. A

3.8 Trap Manager Bar

The Trap Manager bar allows you to view/configure the following elements. See Section 5 for details on how to
use these graphical icon/commands function.
• Host List
• Trap View
• Trap Log
• Device Labels
Table 3-4 Trap Manager Bar Icons
Icons Definition
Host List Displays the Trap Receiver List window for setting up the Host Name and IP address and for enabling
types of SNMP traps. For details on how to use Host List, see Section 5.12.
Trap View Displays the Trap View window........For details on how to use Trap View, see Section 5.12.
Trap Log Displays the Trap Log window which includes the trap sequence number, severity, date/time and trap
description. For details on how to use Trap Log, see Section 5.13 (refresh, clear history, save to file).
Device Labels Displays the Device Labels Configuration window for creating user-friendly labeling scheme for active
modules. For details on how to use Device Labels, see Section 5.9.
TM 87-10049 Rev. A 3-9

This page left intentionally blank.
3-10 TM 87-10049 Rev. A

Chapter 4 Introducing the Interface Tabs
This chapter provides a brief description of the four basic graphical user interface tabs that are common to most
modules installed in a chassis.
Clicking a module icon (Modules and Alarms Toolbar) causes a separate popup (or “child”) window to appear,
and displays bank of tabs. The Status window is the default tab (window) and these tabs work just like a typical
Window’s based GUI whereby a user can select each tab to access different types of module information to
monitor and configure any of the actively installed modules.
This chapter demonstrates how to use the four standard GUI tabs to access critical module information, namely
the:
• Status Tab (default window)
• Alarms Tab
• User Setup Tab
• Module Info Tab
The number and types of tabs are dependent upon the type of module; for example, the NI3000
Network Interface Module contains a fifth tab (the Ethernet Tab) and the DR3002 Digital
Receiver also contains a fifth tab (the RF Control Tab).
As examples, this chapter uses the CX3001 Communications Module and the DR3002 Digital
Receiver to demonstrate the use of tabs.
See Section 7 Additional Chassis Module Examples for examples of tabs and screens associated with other
modules that may be installed in the CH3000 Chassis. Chapter 7 specifically highlights the DR30002 Digital
receiver and the FA3524S Fiber Amplifier.
For details concerning the information presented on the Status, Alarms, User Setup, and Module Information
tabs for particular types of modules, see the associated hardware technical manual and application note.
4.1 Accessing Detailed Module Information Via Tabs

Common to all tabs is module identity. At the top of every tabbed screen, the following module identification and
buttons display:
• Slot number where the module resides (e.g., Slot 32)
• Model number (e.g., CX3001)
• Refresh button
• Close button
• Alarms Summary (ALARMS), if applicable and color-coded representing alarm type
TM 87-10049 Rev. A 4-1

If you see a red, yellow, or blue ALARMS heading at the top of any tabbed screen, click the
module’s Alarms tab to see alarm details associated with this particular module.
4.1.1 Refresh Button

You must select the Refresh button every time you make a configuration change to a module. However, prior to
being able to make a configuration change, you must first have an established IP connection. To learn how to
establish an IP connection, see Section 6.3 Prerequisite Hardware and Software Installation
Requirements.
4.2 Status Tab

Although the Status Tab provides similar types of information (such as temperature and fan speed) across all
modules, the specific types of information will differ depending on module type. Because the Status Tab is the
default, we will begin with this tab.
The following graphics depict the Status screens view when opening a module window, for the CX3001
Communications Module and DR3002 Digital Receiver.
4-2 TM 87-10049 Rev. A

4.3 Alarms Tab

The Alarms tab typically presents and defines common alarm attributes through its user-friendly color-coded
alarm LEDs, checkboxes, and in some cases textual screen reports. At this screen, the operator can monitor and
control/set alarm attributes associated with each module type. Note that alarm attributes differ from module to
module depending on the type of active modules installed in the chassis.
The four most common alarm attributes, as shown in the following screen, include Severity: Major/Minor,
Enable/Disable Alarm, Alarm (Active) and History.
TM 87-10049 Rev. A 4-3

All MAJOR alarms are service affecting. All MINOR alarms are non-service affecting.
4-4 TM 87-10049 Rev. A

The following screen is an example of a textual alarm report for the CX3001 which lists in tabular form the
severity level (MAJOR) and (MINOR) alarms for this module.
You can also use OTS to configure your system to receive notifications (audible sounds and/or emails) when a
trap event occurs.
After opening a module, simply click the Alarms Tab.
The following graphics depict the Alarms screens for two representative modules (a CX3001 Communications
Module and a DR3002 Digital Receiver).
TM 87-10049 Rev. A 4-5

One of the most important aspects of this graphic is alarm information for Receiver 1 and Receiver 2.
4-6 TM 87-10049 Rev. A

4.3.1 Controlling Alarms

The operator can basically control alarms for a specific module using the three GUI controls:
• Clear Alarm History button (clears alarm history for the specific group of alarms)
• Clear All Alarm History button (clears all alarm history for the module)
• Enable/Disable alarm attribute checkboxes
For all three of the above-mentioned alarm controls, the user must have Operator privileges.
4.3.2 Color-Coded Alarm Definitions

The following table defines the meaning of LED colors for both Alarm (active) and History states. The History
category indicates that the unit had experienced a Major/Minor alarm some time in the past. A red LED for
History means that a Major/Minor alarm history occurred in the past at some point but was never cleared (Clear
History button was not selected).
Table 4-1 Alarms LEDs for Active Alarm and History States
Active Alarm
Alarm LED Colors & History Alarm Definition
States
Green No Alarm or No Indicates no active alarm and indicates no history.
Alarm History
Red Active Alarm or Indicates either an active alarm or history present.

Alarm History
Gray Masked Alarm User disabled alarm reporting. The alarm is masked.
TM 87-10049 Rev. A 4-7

4.4 User Setup Tab

The User Setup window allows you to configure attributes specific to each module.
The following graphics depict the User Setup screens for two representative modules (a CX3001
Communications Module and a DR3002 Digital Receiver).
4-8 TM 87-10049 Rev. A

4.4.1 Entering Values in Editable Fields

When entering a negative value, the minus sign (-) must be entered as the last character.
After entering/editing each data field, you must select the Accept button to apply the new changes to a module.
(OTS validates all user inputs in the editable fields.)
The following popup window is common to all modules and displays whenever the user enters an invalid value
in a editable field. This particular example warns the operator that he/she entered an invalid value and indicates
the acceptable value range (-9 and 9).
TM 87-10049 Rev. A 4-9

If you enter an invalid value, the system does not re-display the original value. Simply select the Refresh button
to display your original values.
You must have Operator privileges to make configuration changes.
4.5 Module Info Tab

After opening a module, simply click the Module Info Tab, as shown in the following screen.
The following graphics depict the Module Info screens representative for two modules (a CX3001
Communications Module and a DR3002 Digital Receiver Module).
4-10 TM 87-10049 Rev. A

The Module Info window typically contains the following general module information:
• Serial Number
• Model
• Manufacturing Date
• Revision
• Software Version
• Loader Software Version (if applicable)
• FPGA Version (if applicable)
4.6 Module Specific Tabs

In addition to the basic common tabs applicable to most modules, there are other types of tabs pertaining to status
and control, for example the NI3000 Network Interface Module has a unique Ethernet tab and the Digital
Receiver Modules have a special RF Control tab. The RF Control tab is illustrated in Chapter 7.
TM 87-10049 Rev. A 4-11

4-12 TM 87-10049 Rev. A

Chapter 5 Basic OTS Operations
This chapter provides the basic operations that can be performed using the OTS application.
5.1 Summary Objectives

In this chapter you will learn how to specifically use the major features and functions of the OTS application,
such as:
• Connect to a Chassis • Set Up Trap Host List
• Save Chassis Configuration • Set Shelf Alarm Trap Replay & Transceiver
Alarm Summary
• Open a Module • View/Configure/Delete/Save Traps
• Update Cache • View/Save Trap Logs to File
• Clear Shelf History • Configure OTS Email for Trap Alarms
• Poll Chassis Devices • Configure CX/NI Modules for Email
• Save SNMP Operations to Log File • Update Software on CX/NI Modules
• Name Devices for Easy Management
TM 87-10049 Rev. A 5-1

5.2 Connecting to a Chassis

Prior to connecting to a chassis by entering valid IP address and password, you must first have an actively
installed CX3001Communications Module or an NI3000 Interface Module and use the Craft Management
Software (CMS) application to set up an IP address and change the default password. Refer to the “Opti-Trace
CMS Craft Management Software Installation and Configuration Guide” (TM 87-100050) for instructions on
how to set up a valid IP address and change the default password before accessing the OTS. Also, see Section
6.3 Prerequisite Hardware and Software Installation Requirements for details.
There are two ways to connect to a chassis:
• by clicking the Connections Options icon
• by selecting Options>Connection... from main menu
Simply click the Connection Options icon located on the main window.
As an example, the Connection Options... default window displays, as shown.
The Connection Options window is divided into three major groups:

• Management Access (IP Address of CX3001 Communications Module)
• Security (Access Level and Password--SNMP Community String)
• Timeouts (Time out and Retries)
To connect to a chassis:
1. Enter a valid IP address (determined using CMS).
2. Enter a valid password (determined using CMS).
3. Set up the connection timeouts and retries.
4. Select Connect.
The OTS does not validate IP addresses.
5-2 TM 87-10049 Rev. A

5.2.1 Access Levels and Default Passwords

There are two different access levels and default passwords: Viewer (read only) and Operator (read/write). For
viewer, use “public” as the default password. For operator, use “private” as the default password. (These
passwords can be changed using CMS.)
With operator status, you can configure the chassis and its modules. In contrast, with viewer status you can only
view/monitor the chassis devices.
When you connect to a chassis, the status bar at the bottom of the screen immediately displays your access level
and chassis IP address.
5.3 Saving Chassis Configuration to a File

After you configure module parameters for individual, groups, or all modules in the system, you can save your
entire chassis configuration to a file and as a result, restore a known working configuration for future reference.
1. Simply select the File>Save Chassis Configuration... from the main menu, as shown.
2. Select the desired slots (1-32) or select the Select All button from the Slot selection box and then
select the type of configuration from the Save Configuration box that you want to save.
You can select individual slots, one by one and then apply their own unique type of configuration or select
several slots or the entire 32 slots, plus the external module, and then apply the type of configuration for saving.
Once you have selected your slots and the type of configuration for the slots, you can save your unique
chassis configuration to a file (.csv).
TM 87-10049 Rev. A 5-3

3. In the File field, either type in the filename for the file to be saved or click the Browse button to go
to the directory/folder/filename of your choice. Then click Save.
The chassis configuration file is saved as a .csv (comma separated value).
4. Check the Update Cache checkbox to enable cache updating.
This procedure begins by polling Slot 1 and continues updating the remaining actively installed
modules in the chassis and guarantees that your screens will display the most current module data.
It is highly recommended that you name your .csv file with a user-friendly name for future
reference. Because the .csv file is compatible with Microsoft Excel, this file can be opened using
Excel.
The following printout depicts an example of a saved comma-separated .csv file.
5-4 TM 87-10049 Rev. A

OTS Save Chassis Configuration Header:,5/16/2006 9:55, ,
OTS Version:,5.00.01, ,
IP Address:,10.10.110.151, ,
sysUp Time:,278 days 00h:00m:15s.85th, ,
Model Serial Number:,NI3000.53A5663, ,
Slot Number:,8, ,
Device sytem3000 mid Ver.:,1.33, ,
OTS system3000 mib Ver.:,1.33, ,
Slot: 1, Model No: Not Present, Summary Alarm:, None

Slot: 2, Model No: PS3002D,Summary Alarm:, None
Status,,,
Main Supply Status,,,

DC Voltage [V]:,12.3,Module Temperature [°C],
Power [W],37.5,Minimum:,28
Current [A]:,3.08,Maximum:,29
Backup Voltage:, Present, ,
Fan Speed:, Low , ,
Alarms,,,
Service Affecting Alarms,,,

,Alarm, History,
DC Voltage:, No ,No ,
Non Service Affecting Alarms,,,
,Alarm, History
Fan:, No, No
Module Temperature:, No ,No
Output Power High:, No ,No
User Setup, ,
Module Info, ,
Serial Number:, PS3002.53A5715,

Model:, PS3002D,
Manufacturing Date:, 03-12-05,
Revision:, D. ,
Software Version:,1.42,
Loader Software Version:,11.11,
Others,,,
Slot: 3, Model No: Not Present, Summary Alarm:, None
TM 87-10049 Rev. A 5-5

5.4 Opening a Module

There are four ways to open a module so that you can monitor detailed information and configure specific
module parameters:
• Click a module in the Modules and Alarms toolbar.
• Select a slot number from the Slot drop-down list box (1-32 plus Ext.) and then click the Open button.
• Select a slot number from Slot drop-down list box and then select File>Open from main menu.
• Enter the slot number in the Slot drop-down list box and then click the Folder icon from the main window.
The following window shows a detailed view of the Status of a Power Supply in Slot 16. Note the Status
(default), Alarms, and Module Info tabs associated with this particular module.
If a module is not present in the slot that you have chosen, the following screen displays when you click the U
(black icon). The U indicates that the specified slot is vacant, in this case, slot 1.
5-6 TM 87-10049 Rev. A

The following icon and screen depict a module that is not supported. This popup message indicates that your
current version of OTS does not support this specific module. The following screen depicts that the AT3553A
module in slot 11 is not supported.
5.5 Updating Cache

Selecting the Update Cache button from the main window directs the management module (for example
CX3001 Communications Module) to refresh the contents of its cache for the selected active module, that is, all
information for that specific module is updated. Aurora Networks recommends using the Update Cache button
to make sure that the Status window displays the most current data of individual modules, otherwise data
currently cached in the management module can be 10 minutes old, depending on chassis configuration.
To update cache per individual modules, simply open the specified module and click the Update Cache button,
located on the main window.
TM 87-10049 Rev. A 5-7

The following graphic shows the Updating Cache... window and its progress bar, updating cache on Slot 4.
5.6 Clearing Shelf History

The OTS software allows you to clear the entire shelf history.
Simply click the Clear Shelf History button, located on the main window to clear history for each and every
active module installed.
5.7 Polling Chassis Devices

The system allows you to poll the installed devices and update alarm summary and discovery of any newly
installed modules.
After opening the OTS, initial software polling starts and then completes once chassis inventory has been
discovered by the software. The OTS then updates the module and alarms toolbar and external devices as well,
and displays any modules that are in an alarm state.
There are two ways to perform polling on a chassis device/module:

1. Click the Start Polling button, located on the main window or select the Options>Board from the
main menu.
5-8 TM 87-10049 Rev. A

2. Select the polling interval (2 secs. - 10 min.).
3. Enable the Turn ON Polling checkbox. Then click OK.
4. To stop polling, click the Stop Polling button (As soon as you stop polling, the Stop Polling button
immediately changes to a Start Polling button and vice versa.)
The following graphic illustrates that the OTS is in the process of polling the devices in the chassis and is
currently polling Slot 5, as indicated at the bottom of the screen. Note how the main window polling button
changes to a gray, Stop Polling button.
TM 87-10049 Rev. A 5-9

Because the polling cycle consumes significant application resources while interrogating all active
modules, this operation can prevent access to other menu commands. Therefore, turn polling OFF
after the first cycle completes to allow access to other commands.
5.8 Saving SNMP Operations to a Log File

The Board Options feature is really an SNMP feature that allows you to capture/save all of your SNMP device
transactions to a specified log file.
To save device information to a specified log file,
1. Click Options>Board from the main menu.
The Polling Tab displays as the default.
5-10 TM 87-10049 Rev. A

2. Select the Board tab.
3. Select the Write to Log File check box.
4. If you want to save your files to another location, select the File Locator button, and the Open
window displays, as shown.
Saving a new log file to an existing file overwrites the existing file and should only be used for
debugging purposes. The application will not warn you by displaying a popup message if you
decide to do so.
If you are continuously writing to a log file, you are using system resources (disk space).
TM 87-10049 Rev. A 5-11

5.9 Naming Devices for Easy Management

You can apply user-friendly names to your devices to aid in managing the chassis and to print the Device Label
Configuration window as a list for the types/names of all the installed modules for viewing via the Device
Labels button. Instructions also display at the bottom of the Device Label Configuration screen on how to
provide user-friendly names to your devices. Your labeled device names are stored in a file or in a management
module.
To name your devices, do the following:
1. Simply click the Device Labels icon, located on the main window, as shown.
2. In the Label1 and/or Label2 fields, enter a user-friendly name (seven alpha-numeric characters),
then fill in the Description field (32 alpha-numeric characters).
Select the Reload button to restore previously saved labels.
3. Upon entering the user-defined fields, click the Set button for every selected slot.
5-12 TM 87-10049 Rev. A

4. Repeat step 2 as needed.
5. When you are satisfied with all your labeling for the required slots, select the Save>Refresh
button.
You must select the Save button to save and/or view the new device labeling information for future
reference.
Selecting the Save button, saves your modifications to the configuration file.
This file is stored in the flash card of the CX3001 and NI3000. The saved configuration restores
automatically after reboot.
TM 87-10049 Rev. A 5-13

5.10 Setting Up Trap Host List

In order to set up a trap host list, do the following:
1. Click the Host List icon, which displays on the main window to display the Trap
Receiver List screen, as shown.
Note the IP address (10.10.110.161) listed in the upper left corner of the screen. This IP address represents the IP
address for the active management module, residing in slot 32. In this case, it is a CX3001 Communications
Module.
The Trap Receiver List window is divided into three major groups:
• Device Info (IP Address of the specified device, Device Name and Slot number)
• Trap Receiver Setup (add/delete a device)
• Generic Trap Setup (Enable SNMP Cold Start Trap and Enable SNMP Authentication Failure Trap)
In this example, the operator set up three workstations/PCs to receive traps: Station#1, 10.10.101.54; Station#2,
10. 10.100.44; and Station#3, 10. 10.100.33. This host table represents a table of recipients for traps on the
standard UDP port 162.
After setting up the host lists, any trap will cause an SNMP compliant text message to be sent to every host listed.
2. To add a workstation/PC to receive traps, simply enter a user-friendly Host Name and IP Address,
then click Add Host>Refresh button.
3. Click the Set>Refresh button.
4. Repeat steps 2 to 3 to add multiple hosts.

5-14 TM 87-10049 Rev. A
5. To delete one host, select a host from the host list, click the Delete Host(s) button. To delete
multiple hosts, select (highlight) the hosts then press the Ctrl key).The following popup window
displays.
5.10.1 Standard Trap Configuration

Simply check the Enable SNMP Cold Start Trap box to enable SNMP cold start traps (for each CX) and/or the
Enable SNMP Authentication Failure Trap box (example, incorrect password used to access OTS).
The Generic Trap Setup is unchecked as the default.
5.11 Setting Shelf Alarm Trap Replay and Transceiver Alarm Summary
The shelf General Options command is typically used for diagnostic purposes.
1. Simply select Options>General from the main menu. The General Options window displays, as
shown.
The General Options feature allows you to configure:
TM 87-10049 Rev. A 5-15

• Trap History maximum entries

• Shelf Alarm Trap Replay in seconds
• Shelf Alarm Replay (enable/disable)
• Transceiver Alarm Summary in the Receiver
To disable continuous trap reporting, uncheck the Shelf Alarm Trap Replay checkbox.
In relationship to the Note in the above screen, see the graphic at the end of this section which shows an example
of the receiver’s (DR3002) Alarms tab with special attention to the Transceiver Summary group.
As indicated on the screen, for newer software versions, use the receiver’s Alarms tab. See Section 7.3 DR3002
Alarms Tab.
5-16 TM 87-10049 Rev. A

TM 87-10049 Rev. A 5-17

5.12 Viewing Traps

As the default, the Trap View button originally displays as a black button.
However, this button changes colors and state when the following conditions occur:
• Blinking red indicates a new trap arrived since the user last opened the Trap View window.
• Steady red indicates that the user has viewed all the received traps in the Trap View window.
• Steady black indicates that no traps are present in the Trap View window.
The Trap View button remains red (steady state) until you perform a Clear All or Delete. After performing a
Clear All or Delete, the Trap View button turns back to black (steady state).
The OTS provides several different trap notification methods besides a blinking red Trap View button. You can
also configure your workstation/PC to receive trap alert messages and/or sounds. See the following section,
Section 5.12.1 Configuring Alerts and Sounds for Incoming Traps for details on how to set up your system
to receive trap notifications.
If you want continuous shelf summary trap replay, select Options>General menu.
Only one running application can receive traps on any particular PC. See the following screen.
5-18 TM 87-10049 Rev. A

The following screen indicates that port 162 (standard UDP port) is being used by another application and
therefore is unable to receive traps.
The Trap View window provides detailed trap information, such as:
• Severity (MAJOR, MINOR, NORMAL, and INFO)
• Source
• Date and Time
• Description
The following Trap View illustrates traps received from several modules and types of severity levels.
TM 87-10049 Rev. A 5-19

5.12.1 Configuring Alerts and Sounds for Incoming Traps

The OTS allows you to configure your system to generate alerts (popup message boxes) and/or sounds (.wav
files) upon receiving traps of different severity, such as:
• MAJOR
• MINOR
• INFO
1. Simply select Options>Alerts and Sounds... from the main menu. The default Alerts & Sounds
window displays.
5-20 TM 87-10049 Rev. A

2. To enable an alert/sound, check the Enable alert sounds box and then select (highlight) one of the
three choices of traps: MAJOR/MINOR/INFO. You must enable the Enable alert sounds for this
command to take effect.
If you want an alert message an/or sound to notify you when a trap is sent, you must configure each
of the three types of traps (MAJOR/MINOR/INFO) individually.
3. To be alerted by a message (popup window), check the Display a message box.
4. To be alerted by a sound, check the Playing a sound checkbox and then select the Browse button
to select the directory/folder/sound file of your choice.
Upon locating/selecting a sound file, the blank button immediately changes to identify the location of your
selected sound. To easily access your specified sound file or change to a different sound, simply click the file
location button or the Browse button.
5. Click the Apply/OK button.
The following graphic shows that the user selected “When MAJOR Trap comes” to be alerted by
a popup window and a sound file, in this case pop8.wav.
TM 87-10049 Rev. A 5-21

The following screen illustrates that a MAJOR trap has been received (shown as a message box). While traps are
being received, the Trap View button blinks red in color, as shown.
5-22 TM 87-10049 Rev. A

The following screen shows using a popular email application, a sent trap associated with the NI3000 Network
Interface Module. Note information such as the IP address, severity level of the trap, date and time and
description is listed.
5.12.2 Deleting Traps from the Trap View Window

There are several ways to delete traps from the Trap View window. You can delete:
• a single trap in the listing
• several traps listed anywhere in the listing
• a group of traps
• entire trap listing (clears all traps in the window via Clear All command)
To delete a single trap, simply select the trap by highlighting it using the left-mouse click and press the Delete
button or highlight an individual trap and then right-mouse click and select Delete from the drop down menu.
To delete several traps (random number of traps listed throughout the window and in no particular order), simply
select the trap by highlighting it, move to the next trap that you want to delete, press Ctrl, left-mouse click, then
right-mouse click, select Delete from the drop-down menu or press the Delete button.
To delete a group of traps (traps listed together in a group), simply select the first trap listed in the group and
highlight that trap with a left-mouse click, and then move to the trap at the end of the group, press the Shift key
and then do a right-mouse click to highlight the entire group/listing. Select Delete from the drop-down menu or
press the Delete button.
The drop-down menu displays immediately after selecting/highlighting a trap and immediately performing a
right-mouse click.
To clear the entire trap view window, simply select a single trap, then select the Clear All or Delete command
from the drop down menu.
The following graphic specifically depicts a continuous group of selected traps to be deleted.
TM 87-10049 Rev. A 5-23

5.12.3 Saving Traps to a File

As shown in the above screen and in the following screen, to save traps to a file, simply select the specific traps,
group of traps, or the entire listing. Then select from the drop-down menu, the Save To File... command. This
file is saved as a .csv in a comma separated values format.
When you close the OTS application, you will lose all data displayed in the Trap View window.
5.13 Viewing/Saving Trap Logs to File

The Trap Log allows you to view the history trap log on the CX/NI and also save the log to a file. Simply click
the Trap Log icon located on the main window to view a history of traps previously sent.
The CX/NI is capable of collecting a maximum of 100 traps.

See 5.11 Setting Shelf Alarm Trap Replay and Transceiver Alarm Summary and the General Options
screen which is where you configure your system to generate shelf traps and alarm summary.
Trap Log provides detailed alarm information, such as:
• Sequence No.
• Severity (MAJOR, MINOR, NORMAL, INFO)
• Date/Time
• Description
The following graphic shows an example of the Trap Log and specifically shows only MAJOR severity traps
associated with the CX3001 in slot 32 which was exemplified in the previous trap sections and screens.
5-24 TM 87-10049 Rev. A

The log file significantly increases in size. Therefore, creating and using log files is recommended
only for tracking a small number of SNMP transactions to aid in troubleshooting.
At the Trap Log screen you can perform the following:
• Refresh the log history
• Clear the log history
• Save the log(s) to a file
The trap log shows only the history of traps in a single chassis, i.e., 10.10.100.123.
As another example, the following graphic shows the Trap Log. Notice that log #117 shows a red-colored
MAJOR alarm, and log #116 shows a green-colored NORMAL alarm icon, representing normal module
operation, and log #112 shows a blue-colored INFO alarm icon, representing an information-only alarm. Also
note that the logs listed are associated with the CX3001 and the AR3002 modules.
To save the trap log to a file, simply select the Save To File... button. The saved log file will be saved as a .csv
file, in a comma separated values format.
TM 87-10049 Rev. A 5-25

5.13.1 Clearing Trap Log History

Because the Trap Log is maintained on the CX, when clearing the logs, you area actually clearing
the trap logs that are maintained in the CX.
To display the final trap log prior to selecting the Clear History button, do not uncheck the Shelf Alarm Trap
Replay checkbox in the Options>General menu. The following screen is an example of listing the final trap log
of the CX3001 before selecting the Clear History button.
After clearing the trap log, if you wish to view incoming trap logs, simply click the Refresh button and you will
see the latest incoming logs.
To clear all current logs (without displaying the final trap log), simply uncheck the Shelf Alarm Trap Replay
checkbox in the Options>General menu prior to clicking the Clear History button. A progress bar displays
indicating that this process has been initiated and an INFO log displays indicating that the entire trap log was
cleared, as shown.
5-26 TM 87-10049 Rev. A

5.14 Configuring OTS Email for Trap Alarms

The OTS application can be configured to allow a user to send emails associated with traps by using the Enable
e-mail feature. Otherwise, emails will not be sent.
The OTS must first be configured to receive traps (as described in Section 5.10 Setting Up Trap
Host List) prior to sending emails.
To configure OTS to send emails pertaining to traps, simply select Tools>OTS Email Configuration from the
main menu then select the Enable e-mail feature checkbox, as shown.
You can configure each email recipient to receive traps dependent on the following severity levels as listed in the
Trap Selection:
• Major
• Minor
• Info
• Normal
TM 87-10049 Rev. A 5-27

xxxx.xxx.com
The OTS Email Configuration window consists of the following major groups:
• Recipient Email Addresses and To, Cc, and Bcc drop-down list
• Sender Email Configuration
• Trap Selection (Major, Minor, Info, Normal)
• Email Statistics
5.14.1 Adding a Recipient’s Email Address
Under the Recipient Email Addresses group:
1. Enter the recipient’s name and email address in the Recipient Name and Recipient Email Address
box.
2. Check the Enable e-mail to this address checkbox.
At Trap Selection , check the trap types (Major, Minor, Info, Normal) that you would like to
send.
5-28 TM 87-10049 Rev. A

You must configure each recipient’s trap types separately.
3. Click the Add Recipient button. The recipient’s name and email address will display in the
Recipient Email Addresses box.
4. Click OK.
5.14.2 Deleting a Recipient
1. Simply highlight the recipient’s name in the Recipient Email Address box and then select the
Delete Recipient button.
As a result, the following popup displays.
2. Select Yes to remove the specified recipient from the Recipient Email Addresses list.
5.14.3 Editing a Recipient

To edit a recipient, simply highlight the recipient’s name in the Recipient Email Address box and then select the
Edit button.
5.14.4 Configuring the Email Server
See you network administrator to obtain the SMTP address.
Under the Sender Email Configuration group:

1. Enter your SMTP Address, for example name server or IP address.
2. Enter your email address and name.
3. Enter the Subject Field Test (Re:), for example OTS Traps.
4. Check the Enable e-mail feature checkbox. (This is an OTS global command and must be
enabled.)
To stop sending/receiving emails, disable (uncheck) the Enable e-mail feature to this address
checkbox.
TM 87-10049 Rev. A 5-29

5.14.5 Viewing Email Statistics and Sending Test Email

The Email Statistics group consists of several display boxes and buttons.
• Sent Email Count, Failed Email Count, Last Failed Reason boxes
• Clear Counters and Send Test Email (s) buttons
Simply select the Send Test Email to send a test email. The following is an example of a test email sent to the
user’s PC through a popular email application.
22
If sending an email fails, the Email Statistics group displays the following attributes associated with the emails:
• Sent Email Count (the number of emails sent)
• Failed Email Count (the number of failed emails sent)
• Last Failed Reason (contains a text message, such as “Could not connect to SMTP Server.
Error: 10022”.)
A reason why the above message may display is that there is no SMTP server on that device.
The following graphic shows an example of an email sent successfully.
To clear the counters to zero, (reset the Sent Email Count and Failed Email Count), simply select the
Clear Counters button.
5-30 TM 87-10049 Rev. A

5.15 Configuring CX/NI Modules for Email

This feature is not implemented in this release. For another email feature that pertains to traps, see section 5.14
Configuring OTS Email for Trap Alarms for learning how to configure OTS users to receive emails pertaining
to the different levels of traps (Major, Minor, Info, Normal).
5.16 Updating Software on CX/NI Modules

To update the software on the CX3001 and NI Network Interface modules, simply select the Tools>Software
Update Tool... from the main menu.
See Section 6.8 Performing Software Upgrades on CX3001 which provides step-by-step details for
updating the software on a CX/NI module.
TM 87-10049 Rev. A 5-31

This page intentionally left bank.
5-32 TM 87-10049 Rev. A

Chapter 6 Configuring CX3001 Communications Module
6.1 Summary Objectives
This chapter provides information on how to configure the CX3001 Communications Module and specifically
describes the module’s major features and functions, lists the default configuration for the CX3001, and provides
step-by-step instructions for the following major tasks:
• Monitoring CX3001 Communications Module via the Status Tab
• Configuring CX3001Communications Module via Alarms Tab (RF Alarm and Backup Power Alarm)
• Configuring CX3001 Communications Module via Setup Tab
• Monitoring CX3001 Communications Module via Module Info Tab
• Performing Software Upgrades for CX3001Communications Module
6.2 CX3001 Communications Module Description

The CX30001 Communications Module is an management module that enables standard SNMP access to alarm
and configuration information from active chassis modules, including fiber node alarm and status information
caches in digital receivers and from broadcast transmitters via an external serial connection. More specifically,
the CX3001 connects from the module’s faceplate serial RS-232 port to an AT1550 analog broadcast
transmitter’s serial port, located on the rear of the AT1550.
The CX3001 does not require a dedicated physical slot in a CH3000 Chassis. Instead, you can physically
position it at the rear of any installed Aurora Networks PS3002 Power Supply module.
The CX3001 primary functions include:
• Serves as an SNMP proxy agent for all installed modules in the CH3000 shelf, one external AT1550
Broadcast Trasmitter (if present) and Aurora Networks’ nodes via the DR3002 Digital Receiver Modules.
Its two standard RJ-45 connectors support daisy-chaining for up to 8 CX3001 Communication Modules (see
following figure) and connection to a 10Base-T Ethernet network for communications with either Aurora
Networks OTS/EMS/CMS management software or with third-party SNMP network management
platforms, such as Castle Rock SNMPc and HP OpenView. Its built-in SNMP proxy allows control and
monitoring of the CH3000 active modules over any IP-based network but only supports passive monitoring
of the external broadcast transmitter and Aurora Networks nodes. The CX3001 can be configured with up to
8 SNMP hosts as trap destinations and with multiple SNMP communities.
TM 87-10049 Rev. A 6-1

Must remain open. Do not

create a closed loop.
• Monitors any single device external to the chassis that is capable of RS-232 communications and for which
the communications protocol (handshaking, command and message formats) has been determined. The
RS-232 serial interface communications port on the CX3001 provides this type of communication. The only
device that currently supports monitoring through the CX3001’s serial port is the AT1550 analog broadcast
transmitter and the CX3001 can only monitor a single AT1550 transmitter.
• Monitors the chassis mid-plane alarm line that can be driven by any active module when a service-affecting
(MAJOR) alarm occurs.
• Supports Normally Closed (NC), Normally Open (NO), and Common (COM) contacts that can be used to
drive external alarm sensing equipment whenever a chassis alarm is detected through the mid-plane alarm
line.
• Provides a 12V DC backup power interface connector that can be used to connect to an optional external
backup power source to the CH3000 shelf.
6-2 TM 87-10049 Rev. A

6.3 Prerequisite Hardware and Software Installation Requirements

This chapter assumes that you have already performed the prerequisite hardware and software installation and
configuration requirements prior to accessing the CX3001 Communications Module. These hardware and
software installation requirements must be done using the CMS application prior to using the OTS. Therefore, if
you are not familiar with the CMS and how to use this application to connect to a chassis, refer to the CMS
Installation and Configuration Guide TM 87-10050 and the relevant hardware installation and activation guide.
6.4 CX3001 Status Tab

Click the CX3001>Status tab, as shown.
The CX3001 Communications Module maintains an SNMP trap log that is time stamped based on the system
clock time. This module is factory-programmed for GMT time. However, the time is user-configurable, therefore
an operator can set the system time to their local time.
The CX3001 Communications Module Status window is divided into the following four major groups:
• Module Information
• System Up Time
• Input Port
• Output Port
TM 87-10049 Rev. A 6-3

6.4.1 CX3001 Status Attributes

The following table lists and defines the CX3001 Communications Module Status attributes.
Table 6-1 CX3001 Communications Module Status Attributes and Definition
Attributes Definition
Module Info
12V, 5V, 3.3V DC Displays the current measured DC voltage levels.
Input Port and Output Port

IP Address Assigned IP address. Example: 10.10.110.162
Mask Assigned subnet mask. Example: 255.255.0.0
Gateway Assigned gateway address. Example: 10.10.110.1
MAC Addr.[hex] Unique MAC address of this module. Example: 00.07.9B.10.0C.8A
Link Status Can be either Up or Down.
Speed [Mbps] Indicates the optical link speed (10/100 Mbps).
System Up Time Indicates how long the system has been running in days, hours and minutes. Example: 14
days, 1 hour, 4 minutes.
Temperature [oC] Ambient temperature inside the module. Example: 39
Fan Speed Provides fan status. NOTE: The fan can only be replaced by an Aurora Network’s technical
support representative.
Shelf Backup When detected by the CX, indicates if a shelf power supply backup unit is present in this
shelf/chassis. Values are Present or Absent.
Ext 12V on CX Indicates if an external 12V power supply is connected to the CX. Values are Present or Not
Present.
Ext 12V Displays the external power supply voltage reading.
Shelf Alarm Status Indicates that the CX’s shelf alarm status is either Active or Inactive. Active shelf alarm
status is monitored from the Alarms tab when the alarm(s) are enabled.
6-4 TM 87-10049 Rev. A

6.5 CX3001 Alarms Tab

Select the Alarms Tab to view and configure alarm information and settings, as shown. The following screen
depicts the CX residing in slot 32 and showing a MINOR alarm.
The Alarms screen for the CX3001consists of two basic groups:

• Service Affecting Alarms
• Non-Service Affecting Alarms
For a definition of these alarms, see Table 6-2.
TM 87-10049 Rev. A 6-5

6.5.1 RF Alarm, Backup Power Alarm, and Clear Alarm History Configuration
Also at the CX3001 Alarms screen, you can enable/disable the RF Alarm and Backup Power Alarm (backup
power supply).
To enable/disable the RF Alarm and to enable/disable backup power alarm, see Table 6-2.
6-6 TM 87-10049 Rev. A

To clear all alarm history on the specified CX, including the text alarms listed at the bottom of the Alarms screen,
select the Clear Alarms History button.
When you select the Clear Alarm History button, the Updating Cache window appears
indicating that this process takes approximately 15 seconds.
TM 87-10049 Rev. A 6-7

6.5.2 CX3001 Alarm Attributes

The following table lists and defines the Service Affecting (Major) and Non-Service Affecting (Minor) alarms
for the CX3001 Communications Module.
Table 6-2 Service Affecting and Non-Service Affecting Alarms
Service Affecting Alarms (Major)
12V, 5V, 3.3V DC Indicates that the DC supply rail exceeds these DC power readings.
RF Alarm Indicates bit lane configuration on one or more DR clusters is not

according to the pre-defined legacy mode setting.
Backup Power Alarm When enabled and if there are no backup power supply modules
installed with a valid power source, the CX will generate an alarm.
Non-Service Affecting Alarms (Minor)

Module Temperature Alarm Triggers when the module temperature is outside normal range.
Acceptable range is -20o - +65oC.
Fan Alarm Triggers when the fan temperature is outside normal range. Example:
43oC.
6-8 TM 87-10049 Rev. A

6.6 CX3001 User Setup Tab

Simply select the User Setup tab, as shown.
The Input Port IP Configuration and Output Port IP Configuration attributes displayed on the
User Setup screen represent typical IP address information such as IP address, Gateway, and
Mask for this module and can not be changed/set at this screen. You must use the CMS to
change IP addresses.
At the User Setup tab, you can monitor the following:

• Input Port IP Configuration and Output Port IP Configuration (always identical, but can only be configured
via the CMS)
• Other Settings (Shelf Monitoring ON/OFF)
• System Time
• Reboot the CX3001
TM 87-10049 Rev. A 6-9

6.6.1 Setting System Time

The CX3001 Communications Module maintains an SNMP trap log that is time-stamped based on the system
clock time. The unit ships programmed with GMT time. The operator has the option of setting the system time to
local time. There is no automatic time zone or daylight savings time adjustments associated with the CX3001
Communications Module.
To change the system date/time, select/highlight the desired date listed on the calendar. Then select the Set
button. A progress bar immediately displays while the system is being configured to the new date/time.
To display a previous or future month in the drop-down calendar, simply click the left/right arrows, located in the
upper corners of the calendar.
6-10 TM 87-10049 Rev. A

6.6.2 CX3001 User Setup Attributes

The following table lists and defines the User Setup attributes for the CX3001 Communications Module.
Table 6-3 CX3001 Communications Module User Setup Attributes and Definition
Other Settings
Shelf Monitor* Allows you to enable/disable shelf monitoring.
System Time
Set Time When clicked, brings up the popup calendar that you can configure for the current
system date/time, as shown in the above screen.
Reboot Button Reboots the CX3001 Communications Module.
If Shelf Monitoring is set to OFF, you will not be able to monitor the shelf.
6.7 CX3001 Module Info Tab

Click the Module Info tab, as shown.
TM 87-10049 Rev. A 6-11

6.7.1 Module Info Attributes

The CX3001 Communications Module Info attributes are similar to all other modules.
The following table lists and defines the Info attributes for the CX3001 Communications Module.
Table 6-4 CX3001 Communications Module Info Attributes and Definition
Serial Number Factory-assigned serial number. Example: CX3001.52A3209.
Model Module model number. Example: CX3001.
Manufacturing Date Date the module was manufactured. Example: 02-07-05 (mm/dd/yy).
Revision Hardware version on the module. Example: B.
Software Version Software (firmware) version running on the module. Example: 2.95.
Loader Software Version Boot loader version. Example: 2.6.
6.8 Performing Software Upgrades on CX3001

You can perform upgrades on an active CX3001 Communications Module that resides in a chassis. To upgrade
the CX3001, you must first receive the upgrade file which is emailed to you from Aurora Networks upon your
request. This email is packaged as a zip file and contains two files: text and binary. Upon receiving your zipped
Controller File, you must then save it in an appropriate directory for uploading onto the CX3001.
To perform a software upgrade, do the following steps:
1. After unzipping the upgrade file, copy the following required files to a directory on your PC:
• CX_3_14.NXE
• ControllerVersion.txt
2. From the main menu, select Tools>Software Update Tool...
3. Select the Browse... button to access the Controller File where originally stored.
Immediately after locating the Controller file, the Get File Info button becomes activated.
4. Select the Get File Info button (upgrade information).
5. Enter the password and IP address.Then select the Get Info button (target information).
6. Check the version number on the CX to verify the correct version number.
7. Select the Initiate Update button.
The following graphic depicts the CX/NI Software Update Tool screen.
6-12 TM 87-10049 Rev. A

8. After a successful file transfer, select the Reboot Device button. The following popup window
displays.
TM 87-10049 Rev. A 6-13

9. Wait for the reboot to completely finish and then verify that a successful transfer occurred by
viewing the Device Version read-only field, as shown.
If an error occurs while the update is in progress, a Timeout occurred message displays.
The following is an example of the expected output.
Pinging 10.10.110.161 with 32 bytes of data:
Reply from 10.10.110.161: bytes=32 time=1ms TTL=30
Ping statistics for 10.10.110.161:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Contacting 10.10.110.161
SNMP Connection with 10.10.110.161 established.
Getting Device Name and Software Version...
SNMP Get success: Device Name : Headend Shelf 2-161 slot 32 , Version
3.14
Uploading new firmware, This may take several minutes. Please wait.....
************************************************
Transfer successful: 2097152 bytes in 85 seconds, 24672 bytes/s
10. To upgrade additional CXs, enter the new IP address in the Device IP Address box and then select
the Initiate Update button.
6-14 TM 87-10049 Rev. A

Chapter 7 Additional Chassis Module Examples
This chapter provides an overview of additional modules that may be installed in your CH3000 Chassis. In
particular and as examples only, this chapter focuses on the tabbed screens associated with the DR3002 Digital
Receiver and the FA3524S Fiber Optical Amplifier.
The purpose of this chapter is to get you more acquainted with the tabbed screens of other modules because
although most of the modules’ tabbed screens display similar information, there are, however, differences
depending on module types and versions.
Examples only and GUIs for specific module types are subject to change based on software
changes.
The following screens are arranged according to the order of tabs listed on the module screens beginning with the
Status tab and ending with the Module Info tab.
For additional details see the related hardware guides: DR3000 Digital Receivers Installation and Activation
Guide (TM 87-10040) and FA3500 Series Optical Amplifiers Installation and Activation Guide (TM 87-10037).
TM 87-10049 Rev. A 7-1

7.1 DR3002 Digital Receiver

The following screen depicts the DR3002 Status tab.
At this window, you can view status information and access external optical nodes as well. This graphic in
particular illustrates links to the transceiver in external optical nodes, provides summary information and
controls polling.
To access an external node, as called out in this graphic, you select one of the sixteen daisy-chained digital
transceivers located at the bottom of the screen. The following example shows a digital receiver in an alarming
state in position 1 of the daisy chained digital transceivers. Several graphics listed on the following pages
illustrate how an operator can control external optical nodes.
For details concerning external nodes and how you can monitor/control external nodes through a digital receiver,
refer to the appropriate application note.
7-2 TM 87-10049 Rev. A

Click to access an
external optical node
Upon selecting one of the daisy-chained digital transceivers (as shown above), the MFN Properties window
displays. From the MFN Properties (Mini Fiber Node) window, select the Node Properties (Lid) tab, as shown
to access and monitor an external node.
TM 87-10049 Rev. A 7-3

7-4 TM 87-10049 Rev. A

From the Node Properties (Lid) window, click the View button to display the Node Monitor Module Status
window, in this case the NM4002.
Click to access an
external optical node
TM 87-10049 Rev. A 7-5

The digital transceiver must be inserted into slot A and should have a NM4002 module inserted
in the external node.
7-6 TM 87-10049 Rev. A

The following screen depicts the DR3002 Alarms tab.
TM 87-10049 Rev. A 7-7

The following screen depicts the DR3002 User Setup tab.
7-8 TM 87-10049 Rev. A

The following screen depicts the DR3002 RF Control tab.
TM 87-10049 Rev. A 7-9

The following screen depicts the DR3002 Module Info tab.
7-10 TM 87-10049 Rev. A

7.2 FA3524S Optical Amplifier

The following screen depicts the FA3524S Status tab.
TM 87-10049 Rev. A 7-11

The following screen depicts the FA3524S Alarms tab.
7-12 TM 87-10049 Rev. A

The following screen depicts the FA3524S User Setup tab.
TM 87-10049 Rev. A 7-13

The following screen depicts the FA3524S Module Info tab.
7-14 TM 87-10049 Rev. A

Appendix A Color-coded Icons and Definitions
A.1 Generic System Icons
The following table lists and defines generic system icons for OTS.
Table A-1 Generic System Icons and Definitions
Icons Name Definitions

Warning Non-service affective trap event.
OK/INFO Information trap event.
STOP Service-affecting trap event.
Normal Indicates normal operation for the event trap received.
Communications Window Displays communications window.
Loader State Device is in loader state.
Unknown Device A device was previously in this slot but is no longer detected.
Unknown Device No device was detected in this slot.
Unsupported new card This card is not supported.
Shelf Summary Alarm Status Summary of the alarm status of the shelf.
TM 87-10049 Rev. A A-1

A.2 Device Icons

The following table lists the green color-coded device icons that represent active (not alarming) modules
installed in a chassis.
Table A-2 OTS Color-coded Icons and Definitions
Icons Definitions
PS3002 Series AC Power Supply
Digital Transceivers
A/B Alternate Routing Switches
Analog Receivers
1550nm External Broadcast Transmitter
1550nm External Narrowcast Analog Transmitter
Broadcast Transmitter
CX3001 Communications Module
PS3048 Series DC Power Supply
Digital Receivers
Digital Transponders
A-2 TM 87-10049 Rev. A

Table A-2 OTS Color-coded Icons and Definitions (Continued)
Icons Definitions
Ethernet Switches
Optical Switches
EDFAs (Optical Amplifiers)
Media Converter
Network Interface Module
BC/NC Optical Combiner Modules
TM 87-10049 Rev. A A-3

A-4 TM 87-10049 Rev. A

Appendix B Error Messages
This appendix lists in tabular form all system and applicable module error messages.
B.1 Error Messages

The following table lists in alphabetical order the OTS shelf error messages and cause.
Table B-1 System Error Messages: Cause/Corrective Action
System Error Message Cause

Are you sure you want to delete the selected Recipient? The user tried to delete an email recipient.
Busy performing other tasks. Please try again later. The user tried to do an operation while the present task
is in progress.
Cannot add trap receiver. A trap Receiver with the same The user tried to add a host name to the trap receiver
name already exists. list which is already listed.
Cannot add trap receiver. IP Address already exists in the The user tried to add an IP address to the trap receiver
list. list which is already listed.
Cannot close window while Module Status window is open. The user tried to close the present window when the
Module Status window is opened.
Cannot close window while Module Status window is The user tried to close the present window when
Refreshing. Module status is refreshing.
Can’t add recipient. All the fields of Recipient Email Address The user tried to add an email recipient without filling in
should be filled in. all the information fields.
Could not connect to host: xx.xx.xx. Connection to host failed. The possible reason can be
an invalid IP address.
Could not Reload name bindings. SNMP requests failed. Indicates a failed SNMP operation to reload the name
bindings from a saved file.
Could not save the configuration. SNMP requests failed. Indicates a failed SNMP operation while saving the
configuration.
Host Name field cannot contain spaces and cannot be The host name cannot have spaces.
empty. Please enter a valid name.
Invalid Value. Please enter a value between x.y and a.b. The user tried to set a value for a specific parameter
that is out of range or invalid.
Not all of the trap receiver(s) were deleted. Indicates that all the entries selected from the trap
receiver list are not deleted.
Please set the value within the range x-y for Timeout. The user tried to set an invalid timeout while connecting.
Please set the value within the range x-y for Retries. The user tried to set an invalid value for retries.
Please wait for alarms to be enabled/disabled…. Indicates that an alarm enabled/disabled operation as
Note: Updating data may take more than a minute for requested is in progress.
receiver. Please do refresh after a minute.
Please wait for alarm setup to be set Indicates that an alarm setup operation as requested is
Note: These changes may take up to 3 minutes to take into in progress.
effect.
TM 87-10049 Rev. A B-1

Table B-1 System Error Messages: Cause/Corrective Action (Continued)
Module Error Message Cause

Please wait for history to be cleared. The application is in the process of clearing history.
Refreshing Data. Please wait. Indicates the application is in the process of getting the
latest information from the controller.
Update cache on slot XX can take up to 15 seconds. Please Indicates the update cache is in progress. Update cache
wait…. is the operation to get the latest information by the
Note: Updating data may take more than a minute for controller from the specified module in slot XX.
receiver. Please do refresh after a minute.
Valid range for Maximum Log Entries: x-y. The user tried to resize the maximum trap log entries to
a larger value than allowed.
Are you sure you want to Reboot the CX3001 controller? The user tried to reboot the CX3001.
(Applies only to the CX3001)
B-2 TM 87-10049 Rev. A

Appendix C Resource mib File
C.1 System3000.mib File
A Management Information Base (MIB) is a collection of information organized hierarchically. A MIB is
accessed using a network management protocol, usually SNMP. MIBs consist of managed objects identified by
object identifiers.
A MIB object represents any number of characteristics of a managed device. Managed objects consist of one or
more object instances (variables).
An object identifier (or object ID) uniquely identifies a managed object in the MIB hierarchy. The MIB hierarchy
can be seen as a tree with a nameless root, with levels uniquely assigned.
The top-level MIB object IDs belong to different standards organizations, while lower-level object IDs are
allocated by associated organizations.
The following screen depicts the About Device window which lists the OTS system3000.mib version. This
screen is accessible from the main menu under Help.
Aurora Networks defines private branches that include managed objects for Opti-Trace applications in a custom
branch.
Listed below are the three MIB files you will have on your system after downloading OTS:
• mib_ii.mib
• smi.mib
• system3000.mib (Aurora Enterprise MIB)
The most important MIB files is the system3000.mib because the following components rely on the data supplied
by this MIB:
• shelf/chassis
• third party vendors
• latest version number required by customers
When you install OTS from your CD, the latest version of the sys3000.mib also is installed in the same location
as the application.
The following example is a partial listing of the system3000.mib file.
TM 87-10049 Rev. A C-1

system3000.mib
-- Revision: 1.33
-- Date: Mar 11, 2005
-- Aurora Networks, Inc

-- 2803 Mission College Blvd
-- Santa Clara, CA 95054
-- support@aurora.com
-- This module provides definitions for Aurora's enterprise-specific

-- shelf MIB.
-- LICENSOR MAKES NO WARRANTIES WHATSOEVER (EXPRESSED, IMPLIED OR STATUTORY)

-- REGARDING THIS DOCUMENT, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES
-- OF FITNESS FOR A PARTICULAR PURPOSE AND WARRANTIES OF MERCHANTABILITY.
-- Aurora Networks, Inc reserves the right to make changes in

-- specifications and other information contained in this document
-- without prior notice. The reader should consult Aurora Networks
-- to determine whether any such changes have been made.
-- In no event shall Aurora Networks, Inc be liable for any incidental,

-- indirect, special, or consequential damages whatsoever (including
-- but not limited to lost profits) arising out of or related to this
-- document or the information contained in it, even if Aurora Networks
-- Inc has been advised of, knew of or should have known of the
-- possibility of such damages.
-- Aurora grants vendors, end-users, and other interested parties
-- a non-exclusive license to use this document solely in connection
-- with the management of Aurora Networks, Inc products.
-- Copyright (C) 2001-2005, Aurora Networks, Inc. All Rights Reserved.
AURORA-SYSTEM3000-MIB DEFINITIONS ::= BEGIN
IMPORTS
OBJECT-TYPE
FROM RFC-1212
TRAP-TYPE
FROM RFC-1215
enterprises, NetworkAddress, IpAddress, Counter, Gauge, TimeTicks
FROM RFC1155-SMI
C-2 TM 87-10049 Rev. A

DisplayString
FROM RFC1213-MIB
DateAndTime
FROM SNMPv2-TC;
AuroraAlarmType ::=
TM 87-10049 Rev. A C-3

C-4 TM 87-10049 Rev. A

Index
Symbols CX software update example 6-14
CX/NI Email Configuration command 3-5
.csv file extension 5-4
CX3001 attributes
.csv file, example 5-5 Alarms 6-8
Module Info 6-12
Numerics Status 6-4
User Setup 6-11
3rusnmp.dll 2-8
D
A Device Labels command 1-2, 3-9
Abort command 3-5, 3-8 Device Labels icon 5-12
About command 3-8
About Device command 3-6
About Opti-Trace Shelf command 3-6 E
access levels Email Statistics 5-30
operator 5-3 Sent Email Count, Failed Email Count, Last Failed
viewer 5-3 Reason 5-30
access MIB C-1 Enable SNMP Authentication Failure Trap command
active state, alarm 4-7 5-14, 5-15
Alarms command 3-5 Enable SNMP Cold Start Trap command 5-14, 5-15
Alarms tab 4-3 error messages, cause, corrective action B-1
Alerts and Sounds command 3-5 Ethernet Tab 4-11
Exit command 3-5
B
backward compatibility, OTS 2-3 F
Board command 3-5 Failed Email Count, email statistic 5-30
file extension, .csv 5-3
Folder command 3-8
C Front Panel Bar command 3-5
CAT5 cable 2-2
Clear Shelf History Bar command 3-5
Clear Shelf History button 3-8, 5-8 G
Clear Shelf History command 3-8 General Options command 3-5
color-coded icons 3-6 generic system icons A-1
color-coded icons, definitions A-2
Commands
Abort 3-5 H
About Device... 3-6 history state, alarm 4-7
Alarms 3-5 Host List icon, displays Trap Receiver List window 5-
Alerts and Sounds... 3-5 14
Board... 3-5 hoverable icons 3-3
Clear Shelf History 3-5
Connection... 3-5
CX/NI Email Configuration... 3-5 I
Exit 3-5
Front Panel Bar 3-5 invalid values, entering 4-10
General 3-5
Host List... 3-5 L
OTS Email Configuration... 3-6
Save Chassis Configuration... 3-5 Last Failed Reason, email statistic 5-30
Slots 3-5
Software Update Tool... 3-6
Status Bar 3-5 M
Toolbar 3-5 main window, customize 3-4
Trap Manager 3-5 major alarm 4-7
Update Cache Bar 3-5 managed device C-1
connecting to a chassis managed objects C-1
Connections Options icon 5-2
Management Information Base (see MIB) C-1
Options>Connection... command 5-2
Masked alarm 4-7
Connection command 3-5
Connection Options command 3-8 MIB
access C-1
Connections Options icon 5-2 definition C-1
conventions, used in this guide i-ii object identifier C-1
customized main window 3-4 MIB managed device C-1
TM 87-10049 Rev. A Index-i

MIB managed objects C-1 Send Test Email command 5-30

minor alarm 4-7 Sent Email Count, email statistic 5-30
minus sign (-), entering 4-9 service affecting alarms 3-7
Module Info Tab 4-10 Shelf Summary Alarm icon 3-8
module specific tabs Slot numbers 3-6
Ethernet 4-11 Slots command 3-5
RF Control 4-11 software download, via Web 2-3
module, opening 5-6 Software Update Tool command 3-6
Modules and Alarms Toolbar 3-6 Stat Polling button 5-8
Status Bar command 3-5
N Status tab 4-2
support, technical i-iii
naming devices for easy management 5-12 system requirements 2-1
negative value, entering 4-9
NIC
configuration 2-2 T
non-service affecting alarms 3-7 technical support i-iii
Toolbar command 3-5
O Transceiver Summary attributes
Receiver 1 4-6
object identifier, MIB C-1 Receiver 2 4-6
operator privileges 4-7 Trap Log command 3-9
Options>Connection... command 5-2 trap logs
Options>General command, receiving traps 5-15 clearing 5-26
Opti-Trace Software Password Request form 2-6 viewing/saving 5-24
OTS Email Configuration command 3-6, 5-27 Trap Manager command 3-5
Trap View
command 3-9
P Trap View window
password-protected link 2-4 major, minor, normal, info alarms 5-19
passwords traps
private 5-3 deleting via Clear All command 5-23
public 5-3 receiving 5-14
PC configuration 2-2 viewing 5-18
Polling Bar command 3-5
Polling command 3-8 U
popup blockers, disabling 2-4
uninstall Opti-Trace applications 2-8
Uninstalling OTS 2-8
R Unknown module 3-7
Refresh button 4-2 Update Cache
related documents i-iii button 5-7
RF Control tab 4-11 command 3-8
Update Cache Bar command 3-5
S
V
sample module configuration 2-2
Save Chassis Configuration... command 3-5 version, software 1-1
Index-ii TM 87-10049 Rev. A

Technical Manual Comment Form
Tell us about yourself:
Company Address
Name City
Job Title State/Province
e-mail ZIP/Postal Code
Phone Country
Fax
Is the organization of this manual clear? Is the language clear? Is the manual easy to understand? If not, give examples.
Are the illustrations clear? What illustrations are unclear or confusing? List figure numbers.
Are procedures clear and complete? What procedures need improvement? List page and step numbers.
Is the information in this manual relevant to your job?
TM 87-10049 Rev. A
Did you find any incorrect information in this manual? Where? Did you find any incomplete information in this manual? Where?
What do you like most about this manual? What do you like least about this manual?
What changes would you suggest to this manual? What additions would you suggest to this manual?
Additional comments-use additional sheets as necessary.
Thank you! We appreciate your comments. Please complete this form and send it to:
Technical Publications e-mail: techpubs@aurora.com

Aurora Networks, Inc.
2803 Mission College Blvd. or FAX: 408.845.9045
Santa Clara, CA 95054
TM 87-10049 Rev. A

TM 87 10049 - RevA - OTS v5 00 01

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

TM 87 10049 - RevA - OTS v5 00 01

Încărcat de

Drepturi de autor:

Formate disponibile

Opti-Trace OTS

Shelf Management Software

Copyright © 2006 Aurora Networks. All rights reserved.

Revision Date ECO

Visit www.aurora.com for the latest documentation release information.

i-ii TM 87-10049 Rev. A

Chapter 1 Introduction to Opti-Trace OTS Shelf Management Software ......... 1-1

1.1 What is Opti-Trace OTS Shelf Management Software?................................... 1-1

Chapter 2 Installing OTS ...................................................................................... 2-1

2.1 Software Package Contents ............................................................................. 2-1

Chapter 3 Overview of OTS Graphical User Interface ....................................... 3-1

3.1 Getting Started ................................................................................................. 3-1

Chapter 4 Introducing the Interface Tabs ........................................................... 4-1

4.1 Accessing Detailed Module Information Via Tabs ............................................ 4-1

TM 87-10049 Rev. A iii

Chapter 5 Basic OTS Operations .........................................................................5-1

5.1 Summary Objectives.........................................................................................5-1

Chapter 6 Configuring CX3001 Communications Module .................................6-1

6.1 Summary Objectives.........................................................................................6-1

Chapter 7 Additional Chassis Module Examples ............................................... 7-1

7.1 DR3002 Digital Receiver .................................................................................. 7-2

Table 2-2 Example Modules and Models ...................................................................... 2-2

Table 3-1 Menu/Submenu Commands and Descriptions.............................................. 3-5

Table 3-2 Modules/Alarms Icon Definitions .................................................................. 3-7

Table 3-3 Main Window Icons and Definition ................................................................ 3-8

Table 3-4 Trap Manager Bar Icons ............................................................................... 3-9

Table A-1 Generic System Icons and Definitions .......................................................... A-1

Table A-2 OTS Color-coded Icons and Definitions ........................................................ A-2

Table B-1 System Error Messages: Cause/Corrective Action ....................................... B-1

TM 87-10049 Rev. A vii

viii TM 87-10049 Rev. A

Chapter 2 Installing OTS Shows step-by-step CD and web installation

Chapter 6 Configuring CX3001 Communications Describes how to configure the CX3001

TM 87-10049 Rev. A Preface-i

Appendix C Resource mib File Provides as an example a partial listing of the

CAUTION! This symbol is used to identify situations

This symbol identifies important points in the text.

Preface-ii TM 87-10049 Rev. A

Related Documentation TM Number

Opti-Trace CMS Craft Management Software Installation and Configuration 87-10050

FA3500 Series Optical Amplifiers Installation and Activation Guide 87-10037

DR3000 Digital Receivers Installation and Activation Guide 87-10040

NC4000 Optical Node Installation and Activation Guide 87-10051

CH3000 Chassis Installation and Activation Guide 87-10029

TM 87-10049 Rev. A Preface-iii

Preface-iv TM 87-10049 Rev. A

1.1 What is Opti-Trace OTS Shelf Management Software?

TM 87-10049 Rev. A 1-1

1.2 Major Management Functions and Features

1-2 TM 87-10049 Rev. A

2.1 Software Package Contents

2.2 System Requirements

Table 2-1 System Requirements

256 MB RAM (minimum)

SVGA (16-bit color enabled)

File Size: ~2.31Mb

TM 87-10049 Rev. A 2-1

2.3 PC Network Requirements

For a Direct Local Connection from PC to CX3001 Communications Module

2.4 Example Modules

Table 2-2 Example Modules and Models

CX3xxx Communications Module CX3001

AT3xxx Analog Transceiver AT3300 Series