Provision 6.4.3 UserManual

ProVision 6.4.
3
®
User Guide
614-330055-001
ProVision User Guide
Version 6.4.3
ProVision 6.4.3 User Guide
614-330055-001 Rev 024 July 2009

This manual incorporates features and functions provided with ProVision, version 6.4.3.
Copyright © 2009 by Harris Stratex Networks, Inc.

All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a
retrieval system, or translated into any language or computer language, in any form or by any means,
electronic, magnetic, optical, chemical, manual or otherwise, without the prior written permission of
Harris Stratex Networks Inc. To request permission, contact techpubs@hstx.com.
Warranty
Harris Stratex Networks makes no representation or warranties with respect to the contents hereof and
specifically disclaims any implied warranties or merchantability or fitness for any particular purpose.
Further, Harris Stratex Networks reserves the right to revise this publication and to make changes from
time to time in the content hereof without obligation of Harris Stratex Networks to notify any person of
such revision or changes.
Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons and/or damage
to the equipment:
1. Installation and Service Personnel: Installation and service must be carried out by authorized
personnel who have the technical training and experience necessary to be aware of any hazardous
operations during installation and service, and of measures to avoid any danger to themselves, to
any other personnel, and to the equipment.
2. Access to the Equipment: Access to the equipment in use must be restricted to service personnel
only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety sections of this
manual. Local safety regulations must be used if mandatory. Safety instructions in this document
should be used in addition to the local safety regulations. In the case of conflict between safety
instructions stated in this manual and those indicated in local regulations, mandatory local norms
will prevail. Should local regulations not be mandatory, then the safety norms in Volume 1 will
prevail.
4. Service Personnel Skill: Service personnel must have received adequate technical training on
telecommunications and in particular on the equipment this manual refers to.
Trademarks
All trademarks are the property of their respective owners.
ii Harris Stratex Networks

Contact Information
Sales and Sales Support:
For sales information, contact one of the Harris Stratex Networks headquarters, or find your regional
sales office at http://www.harrisstratex.com/contact.
Corporate Headquarters International Headquarters

North Carolina, USA Singapore
Harris Stratex Networks, Inc. Harris Stratex Networks (S) Pte. Ltd.
Research Triangle Park 17, Changi Business Park Central 1
637 Davis Drive Honeywell Building, #04-01
Morrisville, North Carolina 27560 Singapore 486073
United States
Phone: + 1 919-767-3230 Phone: +65 6496 0900
Fax: + 1 919-767-3233 Fax: + 65 6496 0999
Toll Free for Sales Inquiries: Sales Inquiries:
+ 1 888-HSTX-NOW (888-478-9669) +1-321-674-4252
Customer Service:
For customer service, contact one of the regional Technical Help Desks listed below.
Americas Technical Help EMEA Technical Help Desk Asia Pacific Technical Help
Desk Desk
Harris Stratex Networks Harris Stratex Networks Harris Stratex Networks

120 Rose Orchard Way 4 Bell Drive Bldg 10, Unit B
San Jose, CA 95134 Hamilton International Philexcel Industrial Park
U.S.A. Technology Park Clark Special Economic Zone
Blantyre, Glasgow, Scotland Clark Field, Pampanga
G72 0FB Philippines
United Kingdom
Phone:+1 408 944 3565 Phone:+44 1698 714 073 Phone:+63 45 599 5192
Toll-free in US: Fax: +44 1698 717 204 Fax: +63 45 599 5196
+1 800 227 8332
Fax: +1 408 944 1159
TAC.AM@hstx.com TAC.EMEA@hstx.com TAC.ACPAC@hstx.com
Or you can contact your local Harris Stratex Networks office. Contact information is available on our
website at: www.harrisstratex.com/support/contact-support.asp
614-330055-001 July 2009 iii

WARNING
Making adjustments and/or modifications to this equipment that are not in
accordance with the provisions of this instruction manual or other
supplementary documentation may result in personal injury or damage to
the equipment, and may void the equipment warranty.
AVERTISSEMENT
Tout réglage ou modification faits à cet équipement hors du cadre édicté
par ce guide d’utilisation ou par toute autre documentation supplémentaire
pourraient causer des blessures ou endommager l’équipement et peut
entraîner l’annulation de sa garantie.
WARNUNG
Die an diesen Geräten gemachte Einstellungen und/oder Änderungen,
welche nicht gemäß dieser Bedienungsanleitung, oder gemäß anderen
zusätzlichen Anleitungen, ausgeführt werden, können Verletzungen oder
Materialschäden zur Folge haben und eventuell die Garantie ungültig
machen.
ATENCIÓN
Llevar a cabo ajustamientos y/o modificaciones a este equipo, sin seguir
las instrucciones provistas por este manual u otro documento adicional,
podría resultar en lesiones a su persona o daños al equipo, y anular la
garantía de este último.
iv Harris Stratex Networks

Contents
WELCOME TO PROVISION
What You Need To Know To Use ProVision........................................................ 1-2
Additional Documentation .............................................................................. 1-2
Documentation Organization .......................................................................... 1-3
Documentation Conventions and Terminology ................................................... 1-4
CHAPTER 1, MAKING PROVISION WORK FOR YOU

The Goals of ProVision ................................................................................... 1-1
How ProVision Works..................................................................................... 1-2
Getting the Most Value from ProVision ............................................................. 1-3
CHAPTER 2, NAVIGATING PROVISION

Getting Started ............................................................................................ 2-2
Getting Started Procedures ........................................................................ 2-2
Starting a User Session ......................................................................... 2-2
Exiting a User Session ........................................................................... 2-5
Changing Your Password ........................................................................ 2-6
Entering Your Contact Details ................................................................. 2-7
Viewing Your ProVision License Details..................................................... 2-8
Viewing Customer Support Contact Details ............................................... 2-9
Viewing ProVision’s Version Number ...................................................... 2-10
Using the Online Help .......................................................................... 2-11
The ProVision User Interface ........................................................................ 2-13
Customizing the User Interface ................................................................. 2-14
Menu Bar............................................................................................... 2-15
Main Tool Bar ......................................................................................... 2-21
Right-Click Menus ....................................................................................... 2-22
Tree View Tabs: Physical, Logical, Circuits ...................................................... 2-24
Physical Viewer....................................................................................... 2-24
Logical Tree Viewer ................................................................................. 2-29
Circuits Tree Viewer ................................................................................ 2-29
Map Viewer ................................................................................................ 2-31
Physical Map View................................................................................... 2-32
Flat Map View......................................................................................... 2-33
Map Tools .............................................................................................. 2-34
Map Backgrounds ................................................................................... 2-36
Detailed Device Views ................................................................................. 2-37
Submaps ............................................................................................... 2-38
Equipment Views .................................................................................... 2-39
Interface Views ...................................................................................... 2-46
Event Browser ............................................................................................ 2-47
The Task Manager Screen ............................................................................ 2-49
Using Search to Search All ProVision Data ...................................................... 2-50
Searching the Tree Viewers .......................................................................... 2-53
Icons Information and Usage........................................................................ 2-55
614-330055-001 July 2009 1

Viewing Radio Icon Anatomy .................................................................... 2-55
Event Severity Color Coding ..................................................................... 2-57
Device States ......................................................................................... 2-58
Radio Tasks ........................................................................................... 2-59
CHAPTER 3, DEPLOYING AND MANAGING DEVICES

About Deploying and Managing Devices ........................................................... 3-2
The Process for Deploying and Managing Devices .......................................... 3-4
Device Deployment By Type ....................................................................... 3-5
Deploying Devices ........................................................................................ 3-6
Adding, Editing, and Deleting Device Containers ........................................... 3-7
Adding a Container ............................................................................... 3-7
Renaming a Container ........................................................................... 3-9
Deleting a Container ............................................................................. 3-9
Standard SNMP Device Deployment........................................................... 3-11
Eclipse Devices and Nodes Deployment...................................................... 3-15
TRuepoint Device Deployment .................................................................. 3-18
TRuepoint 6500 Device Deployment .......................................................... 3-22
Constellation Device Deployment .............................................................. 3-25
CAU (Control Alarm Unit) Deployment ....................................................... 3-27
Generic Device Deployment...................................................................... 3-29
WiMAX Device Deployment ...................................................................... 3-31
EfficientSite Manager Deployment ............................................................. 3-33
TNet Device Deployment.......................................................................... 3-34
DXR 200 and DXR SMA Device Deployment ................................................ 3-39
Network Auto-Discovery for Eclipse and WiMAX BS Devices .......................... 3-42
Troubleshooting Device Deployment .......................................................... 3-46
Changing a Device’s Container.................................................................. 3-47
Moving Containers and Devices in the Map Viewer....................................... 3-48
Renaming a Device ................................................................................. 3-49
Deleting a Device.................................................................................... 3-50
Managing Devices ....................................................................................... 3-51
Managing a Device.................................................................................. 3-51
Verifying ProVision is Receiving Device Events ............................................ 3-52
Unmanaging a Device.............................................................................. 3-54
Manually Discovering TRuepoint 6500 Configuration .................................... 3-55
Manually Discovering DXR 700 Radios ....................................................... 3-56
Managing SMA and DXR Devices ............................................................... 3-57
RF Linking Procedures ............................................................................. 3-59
Creating an RF Link from the Tree Viewer .............................................. 3-60
Creating an RF Link from the Find Function ............................................ 3-61
Creating an Eclipse RF Link .................................................................. 3-62
Verifying an Eclipse or TRuepoint RF Link ............................................... 3-64
Deleting an RF Link ............................................................................. 3-65
Miscellaneous Device Procedures .................................................................. 3-66
Viewing Configuration for Devices ............................................................. 3-66
Configuration Profiles for Bulk Configuration ............................................... 3-72
Create and Execute a New Configuration Profile ...................................... 3-72
Configuration Profile Settings for Bulk Configuration ................................ 3-75
Delete a Configuration Profile ............................................................... 3-79
2 Harris Stratex Networks

Viewing/Changing Network IP Addresses.................................................... 3-80

Viewing/Changing TNet Proxy Configurations .............................................. 3-81
Using the TNet Proxy Viewer .................................................................... 3-83
Circuit Management .................................................................................... 3-84
About Circuits and Circuit Tracing.............................................................. 3-84
Initiating and Viewing a Circuit Trace......................................................... 3-85
Circuit Features ...................................................................................... 3-87
Display a Single Circuit ............................................................................ 3-90
Circuit Logical Containers......................................................................... 3-91
Logical Containers Tab......................................................................... 3-91
Creating a Logical Container ................................................................. 3-92
Circuit Provisioning: Creating Circuits Between Devices ................................ 3-93
Using Circuit Provisioning to Create Circuits............................................ 3-93
Commissioning and Decommissioning Circuits......................................... 3-97
Additional Circuit Functions ...................................................................... 3-98
Open Submap .................................................................................... 3-99
Event Browser .................................................................................... 3-99
Circuit Diagnostics .............................................................................. 3-99
Adding Circuit Bundles to Logical Containers..........................................3-100
Configure Circuit Bundles ....................................................................3-102
Cable Connections for Eclipse IDU-IDU Circuits ......................................3-104
Retrace a Circuit ................................................................................3-105
Renaming Circuits ..............................................................................3-106
Circuit Problem Icons .........................................................................3-107
Check and Synchronize Circuit Names ..................................................3-108
Delete a Circuit..................................................................................3-109
Loading/Activating New Eclipse Software and Licenses ....................................3-110
About Loading Eclipse Software Via ProVision ............................................3-110
Eclipse Software Loading Examples ..........................................................3-111
Stage 1: Eclipse Software Load Procedure .................................................3-113
Stage 2: Eclipse Software Activation Procedure ..........................................3-118
Eclipse Node Licenses .............................................................................3-121
Eclipse and StarMAX Configuration Backup Export ......................................3-124
CHAPTER 4, MANAGING EVENTS

Event Management Processes..................................................................... 4-2
Managing Event Processes in ProVision .................................................... 4-2
Suggested Steps for Managing Events ..................................................... 4-3
Event Management Interdependencies..................................................... 4-3
Setting Up Scoreboard Groups ................................................................ 4-4
Customizing Event Browsers................................................................... 4-4
Event Management Procedures ....................................................................... 4-5
Network Events ........................................................................................ 4-5
Network Event States ............................................................................ 4-6
Viewing Network Events......................................................................... 4-7
Viewing an Event’s Properties ................................................................. 4-8
Acknowledging a Network Event ........................................................... 4-10
Unacknowledging a Network Event ........................................................ 4-12
Managing Event Notification Pop-Ups and Audio Alarms............................ 4-13
Manually Clearing a Network Event........................................................ 4-14
614-330055-001 July 2009 3

Manually Resynchronize Alarms ............................................................ 4-15
Configure TRuepoint 6400 Alarm Resynchronization................................. 4-16
Customizing Event Names or Severity Levels .......................................... 4-18
Sleep Status for a Device ..................................................................... 4-20
Event Browsers ...................................................................................... 4-22
Saving an Event Browser View.............................................................. 4-24
Viewing a Saved Event Browser ............................................................ 4-25
Customizing an Event Browser.............................................................. 4-26
Changing Event Browser Options .......................................................... 4-29
Deleting an Event Browser ................................................................... 4-33
Saving Event Browser Contents ............................................................ 4-34
Printing Event Browser Contents ........................................................... 4-35
Event Log Pre-Filtering ............................................................................ 4-36
Viewing Event Log Pre-Filtering............................................................. 4-39
Adding An Event Log Pre-Filter at the Root Level ..................................... 4-40
Adding an Event Pre-filter at an Object Level .......................................... 4-43
Adding an Event Pre-Filter Via an Event Browser ..................................... 4-44
Modifying An Event Log Pre-Filter.......................................................... 4-45
Deleting An Event Log Pre-Filter............................................................ 4-47
Security Log........................................................................................... 4-49
Event Notification ................................................................................... 4-51
Set the Server Notification Preferences .................................................. 4-52
Add or Edit Event Notification Rules....................................................... 4-53
Delete an Event Notification Rule .......................................................... 4-56
Configuring the Notification Rule ........................................................... 4-57
Set Up an Email Event Notification ........................................................ 4-60
Set Up a Pop-Up Message Notification ................................................... 4-63
Set Up an Audio Alarm Notification ........................................................ 4-65
Set Up Script Execution on Event Notification ......................................... 4-66
Logical Containers................................................................................... 4-69
Adding a Device to a Logical Container .................................................. 4-70
Removing a Device from a Logical Container........................................... 4-72
Renaming a Logical Container............................................................... 4-73
Deleting a Logical Container ................................................................. 4-74
Logical Links .......................................................................................... 4-75
Adding a Logical Link........................................................................... 4-76
Renaming a Logical Link ...................................................................... 4-76
Deleting a Logical Link......................................................................... 4-77
Scoreboard Group Scenarios ........................................................................ 4-78
About Scoreboard Group Scenarios ........................................................... 4-78
Viewing a Scoreboard Group ................................................................ 4-80
Creating a Scoreboard Group ............................................................... 4-81
Editing a Scoreboard Group.................................................................. 4-83
Deleting a Scoreboard Group................................................................ 4-83
Adding a Scoreboard ........................................................................... 4-84
Editing a Scoreboard ........................................................................... 4-87
Deleting a Scoreboard ......................................................................... 4-88
Opening an Event Browser from a Scoreboard ........................................ 4-88

CHAPTER 5, SYSTEM DIAGNOSTICS AND REPORTS

Using System Diagnostics .............................................................................. 5-2
About ProVision and Craft Tools ...................................................................... 5-4
Diagnostic and Performance Trends Analysis Procedures .................................... 5-5
Circuit Diagnostics Feature ......................................................................... 5-5
Circuit Trace for Circuit Diagnostics ......................................................... 5-6
Circuit Diagnostic Window ...................................................................... 5-7
Setting Up a Circuit Diagnostic Test....................................................... 5-10
Circuit Diagnostic Options .................................................................... 5-13
Data Collection ....................................................................................... 5-14
Daily Performance Data Collection ......................................................... 5-15
Enabling 15-minute Performance Data Collection..................................... 5-17
Changing Device Data Collection Status ................................................. 5-18
Ethernet Performance Data Collection ........................................................ 5-20
Enabling 15-Minute Ethernet Data Collection .......................................... 5-20
Viewing Ethernet Performance .............................................................. 5-21
Ethernet Bandwidth Utilization .............................................................. 5-28
Performance Features.............................................................................. 5-33
Performance History ............................................................................ 5-33
Performance Trends ............................................................................ 5-38
Performance Thresholds....................................................................... 5-42
WiMAX WSN ASN-GW Controller and Base Station Management .................... 5-46
WiMAX Subscriber Station Connectivity ...................................................... 5-48
Craft Tools and Diagnostic Controls ............................................................... 5-50
Launching a Craft Tool............................................................................. 5-52
LE3000 or Memotec Craft Tool Installation ................................................. 5-54
WMT Craft Tool ...................................................................................... 5-55
TNet Web Craft Tool and Diagnostics ......................................................... 5-58
TNet Diagnostics................................................................................. 5-62
TNet Diagnostics - Protection Tab.......................................................... 5-64
TNet Diagnostics - G.821 Performance Tab ............................................. 5-66
TNet Diagnostics - CB 149 Performance Tab ........................................... 5-68
TNet Diagnostics - RSSI Tab................................................................. 5-70
XP4 Craft Tool and Diagnostics ................................................................. 5-72
Activating and Deactivating an XP4 Tributary Loopback ............................ 5-73
Activating and Deactivating an XP4 Local Loopback ................................. 5-78
Viewing/Changing XP4 Protection Settings.............................................. 5-81
Resetting an XP4 Radio Device.............................................................. 5-84
Diagnostic Controls for Selected Devices .................................................... 5-85
Constellation Diagnostic Controls .......................................................... 5-85
CAU Diagnostic Controls ...................................................................... 5-90
DART Diagnostics Controls ................................................................... 5-91
DVA Diagnostic Controls ...................................................................... 5-95
MegaStar Diagnostic Controls ............................................................... 5-96
EfficientSite Manager System ....................................................................... 5-98
Device and Network Reports........................................................................5-101
Inventory Reports ..................................................................................5-101
View the Inventory Reports .................................................................5-102
Save an Inventory Report for a Single Device ........................................5-104
Save an Inventory Report for Multiple Devices .......................................5-105
614-330055-001 July 2009 5

Eclipse Fault Report ...............................................................................5-107
Eclipse Capacity Report ..........................................................................5-108
View / Save / Delete Server Reports.....................................................5-111
Network Health Reports ..........................................................................5-112
Run and View Network Health Reports ..................................................5-114
GLOSSARY
INDEX

Welcome to ProVision
Welcome to ProVision. ProVision is a management tool for monitoring the elements in

a wireless radio network. ProVision has an easy to use interface and tools that enable
you to view events from network devices. This means that you can identify problem
areas in your network, and determine how to solve these problems.
The purpose of the User Guide documentation is to provide you with the technical
information you require to use ProVision. This includes:
• Using ProVision to create and maintain network maps
• Monitoring and managing device status, performance, and event reporting
• Configuring Harris Stratex Networks devices
• Configuring and managing third party devices
• Generating supporting reports and graphs
This documentation is for all ProVision users, including:

Role Role Description
NOC Operators Monitor the radio network for errors and performance. Follow
predefined procedures when faults are detected. May have
little or no radio expertise.
NOC Engineers Configure the radio settings and performs software and
configuration changes. Radio domain experts.
NOC Fault Finders Diagnose and isolate faults in the network down to the unit/
event level. Issue trouble tickets to field engineers where
necessary.
If you are working with ProVision in a different role, for example, as a ProVision
administrator, refer to the Additional Documentation on page -2.
This section includes the following topics:

• What You Need To Know To Use ProVision
• Additional Documentation
• Documentation Organization
• Documentation Conventions and Terminology
614-330055-001 July 2009 1

What You Need To Know To Use ProVision
To use ProVision effectively, we recommend that you have the following knowledge and
skills:
• General familiarity with Harris Stratex Networks devices and device concepts
Experience working in a ProVision environment is also helpful.

Working knowledge of ProVision is demonstrated by completing ProVision training
courses:
• ProVision User Training
• ProVision System Administrator Training
Next Topic
Additional Documentation
Additional Documentation
The ProVision Installation and Administration Guide (P/N 614-330053-001) contains

additional information to help users understand, install, and use ProVision. Its
audience is advanced users, such as system administrators.
It provides system administrators with the following instructions:
• Task-oriented assistance in planning for, installing, and configuring ProVision
hardware and software components.
• ProVision database backup and restore procedures
• How to provide Harris Stratex Networks with the information Harris Stratex
requires to analyze and respond to ProVision software problems.
It is included in the online help.
The online help also includes information about equipment alarms that may be
accessed through Portal for Eclipse radios, and for other radios, such as Altium, XP, or
TRuepoint.
Next Topic
Documentation Organization

Documentation Organization
This manual is organized into the following chapters and appendices:

Making ProVision Work For You
This is an overview of the ways in which ProVision can help your business, including:
• Achieving maximum system availability
• Reducing cost of running the network
• Managing your network proactively rather than reactively
Navigating ProVision
This section describes how to navigate the ProVision software front end. It introduces
the ProVision user interface and the main interface components. It also describes the
network search facility and navigating context-sensitive pop-up menus and functions.
Deploying and Managing Devices

This section describes how to deploy, link, and manage radios in ProVision. This
includes circuit management and circuit provisioning.
Managing Events
This section describes event management tools for events generated by the radios and
by the system. This includes:
• Individual event history and probable cause identification.
• Services that enable you to group together network devices that share a common
purpose.
• Customizable Event Browsers with event filtering and browser options that you can
save and reuse.
• Prefiltering events at input which reduces the number of events in the system.
• Scoreboard groups, providing an at-a-glance overview of a network.
System Diagnostics and Reports

This section describes system diagnostics, including:
• Enabling performance data collection.
• Launching the individual radio craft tools.
• Using Diagnostics.
• Using Reports.
Next Topic
Documentation Conventions and Terminology
614-330055-001 July 2009 3

Documentation Conventions and
Terminology
Graphic Cues
The following icons function as graphical cues used to characterize particular types of
associated supporting information.
A caution item identifies important information pertaining to

actions that may cause damage to equipment, loss of data, or
corruption of files.
A warning item identifies a serious physical danger or major possible

problem.
A note item identifies additional information about a procedure or

function.
Font Changes
Bold font is used for the names of on-screen elements such as; fields, buttons, and
drop-down selection lists, keywords, commands and for keys on the keyboard.
Courier font is used to indicate commands that the user needs to type in.
Italic font is used to emphasize words and phrases, to introduce new terms, and for
the titles of printed publications.
Common Terminology
• Click or Select: Point the mouse pointer at the item you want to select, then quickly
press and release the left mouse button.
• Right-Click: Point the mouse pointer at the item you want to select, then quickly press
and release the right mouse button.

Chapter 1. Making ProVision
Work For You
The topics covered in this section are:
• The Goals of ProVision on page 1-1
• How ProVision Works on page 1-2
• Getting the Most Value from ProVision on page 1-3
The Goals of ProVision
ProVision can help your business to manage its radio network in many ways:
• Achieving maximum system availability.
• Reducing network operating costs.
• Managing your network proactively rather than reactively.
How does ProVision do this? ProVision informs the user of events and device failures
in a managed wireless radio network. By identifying events and failures for users, this
reduces the time between a fault occurring and the fault being repaired. It may even
allow a repair to be done before a link fails completely.
ProVision also obtains and stores data about the network devices, including:
• Information entered when the device was installed and commissioned into service
• Performance data
• Events from the device
ProVision can be used to reconfigure the devices in the network.
ProVision is used to assist in performing the following functions:
• Network planning
• Installation
• Commissioning
• Event monitoring
• Device / network performance
• Fault diagnostics
• Device reconfigurations
• Inventory management
Next Topic:
How ProVision Works on page 1-2
614-330055-001 July 2009 1-1

Chapter 1. Making ProVision Work For You
How ProVision Works
This figure shows how ProVision interfaces with the radio network:
Figure 1-1. How ProVision Works
The ProVision server communicates with the network devices, and stores the events/
responses in a database.
The ProVision client provides the user interface, and displays on screen the events and
data the user has requested.
The ProVision server and ProVision client software can be installed on a single
computer, or separately.
ProVision can have multiple clients.
Next Topic
Getting the Most Value from ProVision on page 1-3
1-2 Harris Stratex Networks

Getting the Most Value from ProVision
Using ProVision adds value proactively by finding problems before they affect traffic.
ProVision has features that increase its value in several ways.
Turning Data Into Information

ProVision enables you to streamline the number of alarms by:
1. Reducing the number of alarms entering the system using pre-filters, “filtering at
input”.
2. Reducing the volume of alarms being displayed on screen using filters, “filtering at
display”.
In addition, you can create views and Scoreboard groups to meet your monitoring
needs. Scoreboards allow you to group devices together in views that provide the
information you require. This provides a convenient way to review the status of these
devices. At a glance, you can highlight the important areas of the business, for example;
the network backbone, golden cells, and high capacity links, with:
• Easy differentiation between real radio problems vs. informational data
• Alarm status for the entire link
• Reducing the amount of data that is not of value by putting the radio in sleep mode
• Notes and messaging which makes information available to all who need it
Fault reports scan the network elements and present the radios with the highest
number of alarms, or the highest severity alarms.
Managing Data Over Time

Equipment status values such as RSL, temperature and voltages, and G.826 are only
meaningful if you can compare them to a previous, similar value. ProVision can track
these values over time and set thresholds when the values move outside specified
ranges.
Having the history of an alarm can add great value. ProVision lets you view all the
alarms from a single radio and sort the alarms by type, enabling you to determine what
is really happening. This is more significant than viewing one alarm out of context.
With ProVision, you can pre-deploy radios and store data about them without
Managing them. Radios start forwarding events to ProVision when their status is
changed to Managed.
Using Performance Analysis

ProVision can collect and save huge amounts of performance data from the radios. This
data is normally over-written in the radios. The data can be used to find patterns before
traffic is affected, and to diagnose problems if a radio fails.
ProVision can keep the daily data for all radios for a predefined time. This data can be
used to spot long term trends in radio performance, identify problem sites or radios.
Radios that are identified as critical or causing problems can also be monitored more
intensely using 15-minute data collection, which can be used to find problems that are
occurring now. This data can also be kept in the ProVision database indefinitely.
614-330055-001 July 2009 1-3

Chapter 1. Making ProVision Work For You
Performance data can provide information in many ways. If a radio is having

performance trouble, checking the performance data from nearby links or co-sited
links can help to identify if the problem is due to non-equipment problems such as rain
fade, local interference, site power problems, or other reasons. ProVision can be used
to display performance data from a number of radios at the same time to assist with
this, or for a single radio over time.
Real value can be gained from ProVision when a radio has failed. Looking at historical
performance data and events from a failed radio can help determine; what end of the
link has failed and what type of failure it may be. The data stored in ProVision for the
failed radio is available even when communication to the link has been lost.

Chapter 2. Navigating ProVision
This section describes the ProVision user interface and how to start using ProVision,
including:
• Getting Started on page 2-2
• The ProVision User Interface on page 2-13
• Right-Click Menus on page 2-22
• Icons Information and Usage on page 2-55
This section assumes that ProVision has been installed, and the devices
are deployed and being managed from ProVision.
614-330055-001 July 2009 2-1

Getting Started
This section includes the following topics:

• Starting a User Session on page 2-2
• Exiting a User Session on page 2-5
• Changing Your Password on page 2-6
• Entering Your Contact Details on page 2-7
• Viewing Your ProVision License Details on page 2-8
• Viewing Customer Support Contact Details on page 2-9
• Viewing ProVision’s Version Number on page 2-10
• Using the Online Help on page 2-11
Getting Started Procedures

Please be sure to review all the Getting Started procedures before you begin.
Starting a User Session
Introduction
The ProVision Client Software on your PC enables you to start and run a ProVision user
session.
ProVision allows multiple simultaneous user sessions. Changes made by one user are
immediately reflected in the ProVision database. However, no two users can change the
same data at the same time, because when changes are being made to an object, the
system locks that object.
After you enter your login details and these details are verified, your PC connects to the
ProVision server. The ProVision User Interface displays, with the latest details, alarms
and events about the network and its performance. Your user name, and the name of
the ProVision server to which you are connected, are displayed at the bottom of the
User Interface window.
Set your display resolution to a minimum of 1024 x 768. This ensures

that all the components in the ProVision windows are visible on your
display.

Procedure
To start a user session:
1. From the desktop, double-click the ProVision Client shortcut.
2. The ProVision Login window displays.
3. Type your user name and password in the fields provided. For example:
User: LeslieSmith
Password: password
4. Enter the name of your ProVision Server and select Login. The ProVision Loading
window displays.
5. When ProVision is loaded, the ProVision Loading window closes, and the
ProVision User Interface displays.
614-330055-001 July 2009 2-3

Exceptions
If you type in an unknown user name or password, the following error message
displays.
Select OK and retype your user name and password.
After three failed attempts, the Login dialog box closes and
access to ProVision is denied. At this point you must contact your
Network Administrator.
If you type an incorrect server name, or the server is not available, the following error
message displays.
Select OK and retype the server name.

If the error message displays again, contact your Network Administrator.
Related Topics:
• Exiting a User Session on page 2-5
• Changing Your Password on page 2-6

Exiting a User Session
Introduction
ProVision user sessions continue to run until you exit the session or shut down your
workstation.
Procedure
To exit a user session:
1. Select the X in the upper right corner of the user interface window. A message
displays prompting you to confirm your exit request.
2. To close your ProVision user session, select Yes.
Related Topics:
Starting a User Session on page 2-2
614-330055-001 July 2009 2-5

Changing Your Password
Introduction
Each user requires a user name and password to log into ProVision.The system
administrator sets up your first user password. You can change your password at any
time.
ProVision passwords must have between 6 and 32 alphanumeric characters. Passwords
are case sensitive.
If you type an invalid password in any of the password boxes, an error

message displays. To close the message box and try again, select OK.
Procedure
1. Select Administration > Change User Details. The Change User Details window
displays for your user name.
2. Select Change Password. The Change Password dialog box displays.
3. In the Old Password field, type your old password.

4. In the New Password field, type your new password.
5. Re-type your new password in the Confirm New Password field. Select OK.
6. To accept your password changes on the Change User Details window, select OK.
7. Use your new password the next time you log in to ProVision.

Related Topics:
• Entering Your Contact Details on page 2-7
Entering Your Contact Details
Introduction
ProVision provides a location to store your contact details. You can enter new contact
details and change existing details, such as an address and phone number.
Procedure
To change your contact details:
1. Select Administration > Change User Details. The Change User Details window, with
your user name, displays.
2. Select in the Contact Details frame and type in your details.

3. To accept your changes and close the window, select OK.
Related Topic:
Changing Your Password on page 2-6
614-330055-001 July 2009 2-7

Viewing Your ProVision License Details
Introduction
The ProVision license details can be viewed at any time.
There are two types of license, an evaluation license that expires 60 days after
installation and a permanent license that has no expiry date.
Procedure
To view your ProVision license details:
1. Select Help > License Details.
The License Detail window displays, for example:
2. To close the window, select OK.
Related Topics:

Viewing Customer Support Contact Details
Introduction
If you need to contact Harris Stratex Networks Customer Support, the contact
information is available from the ProVision Help menu.
Procedure
To see the contact information for Harris Stratex Networks Customer Support:
1. Select Help > Customer Support.
The Customer Support Information window displays.
2. To view the contact details of your region’s Harris Stratex Networks Customer
Support center, select the appropriate tab.
Related Topics:
614-330055-001 July 2009 2-9

Viewing ProVision’s Version Number
Introduction
In certain situations, you need to know the version number of your ProVision software;
for example, when deciding whether to upgrade or reporting a fault.
Procedure
To view the version number for your installation of ProVision:
1. Select Help > About ProVision. The About ProVision window displays.
Related Topics:

Using the Online Help
Introduction
The online help module you receive with ProVision provides complete documentation
of ProVision, including:
• User Guide
• Installation and Administration Guide
• Alarms
• ProVision Terms of Use
• Harris Stratex Technical Support Information
The online help displays using the default Web browser on the PC. The online help user
interface is shown below:
Figure 2-1. ProVision Online Help
Each topic in the online help has its location listed at the top of the page. This helps you
to identify related topic areas.
614-330055-001 July 2009 2-11

If you prefer to have printed versions of the documentation, print them from the PDF
provided on the ProVision Installation CD (P/N 614-500502-002). You can also print
individual help pages from the Web Browser view.
Procedure
The ProVision online help displays in your default HTML browser. The
ProVision help is included with the ProVision software. You do not need a
link to the Internet to use the ProVision help and its features.
To access the online help:

1. From the menu bar, select Help > Help Topics.
The ProVision online help window displays.
2. To navigate the online help, use the tabs at the top of the left navigation panel:
• Contents - Enables you to view the information headings organized by subject.
Expand the top-level headings to view the subtopics.
• Index - The index is used to find important terms and display the related topic.
• Search - Enables you to search for any character string in the help set.
3. The search results list all the topics that contain the search string, with a % rank
showing how well the topic matches the search. All occurrences of the search string
are highlighted in the help topic.
Related Topics:
• The ProVision User Interface on page 2-13

The ProVision User Interface
From the main ProVision interface, you can perform all the required functions to
manage network responsibilities, quickly and effectively.
Figure 2-2. Main User Interface
The functions of the main user interface are described in the following sections:
• Customizing the User Interface on page 2-14
• Menu Bar on page 2-15
• Main Tool Bar on page 2-21
• Tree View Tabs: Physical, Logical, Circuits on page 2-24
• Map Viewer on page 2-31
• Event Browser on page 2-47
• Using Search to Search All ProVision Data on page 2-50
• Searching the Tree Viewers on page 2-53
614-330055-001 July 2009 2-13

Customizing the User Interface

This table lists the ways you can customize the user interface.
Table 2-1. Customizing the Main User Interface
Required Result Action
Main User Interface
To minimize, maximize, or Select the required button from the buttons

close the interface window located in the upper right corner.
To resize the interface window Click and drag any of the outside edges of the
interface window.
Physical Viewer
To resize the Physical Viewer Click and drag the vertical split bar.
To hide the Physical Viewer Select the X the Physical Viewer toolbar.
To show the Physical Viewer In the Window menu, select Physical.
Map Viewer
To resize the Map Viewer panel Click and drag the vertical split bar.
To hide the Map Viewer Select the X on the Map toolbar.
To show the Map Viewer In the Window menu, select Map.
To add a background Select Map Properties on the Map toolbar to

add a JPG background for the map.
Event Browser
To resize the Event Browser Click and drag the horizontal split bar.
To hide the Event Browser Select Hide.
To show the Event Browser In the Window menu, select Events.
To change displayed Event In the Event Browser toolbar, select Browser

values Options to edit browser options.
Related Topics:
• Menu Bar on page 2-15

Menu Bar
The menu bar contains menu items and pull-down options used to access common,
non-device specific functions such as:
• Event Browsers
• Security Management
• Reporting and Data Collection
• Scheduling configuration operations
• Help System
The menu bar items displayed on the main user interface may vary
depending on your user access profile.
The figure below shows the ProVision menu bar with all the menu options displayed.
The table below contains descriptions of the menu items and associated pull-down
options available from the menu bar.
The ProVision menu system includes context-sensitive right-click menus. Access the
right-click menus by right-clicking on an object within the Map Viewer or Physical
Viewer. The right-click menus provide device specific functionality. For more
information, see Right-Click Menus on page 2-22.
Table 2-2. Menu Bar Items And Pull-Down Options
Menu Item Function
Menu Bar
File > Topology Import

Enables you to import a network topology in XML file
format. The Tree and Map Viewers are automatically
populated with objects, that is, containers and devices.
Typically used when migrating a previous version of
ProVision to ProVision.
For information on importing a network topology see the
ProVision Installation and Administration Guide, Migrating
Topology.
614-330055-001 July 2009 2-15

Menu Item Function
Topology Export
Enables you to export network objects and hierarchy to an
XML file. The network topology can be exported as a
backup, for support diagnostic purposes, for 3rd party
north bound integration and for future migrating to a later
version of ProVision.
For information on exporting a network topology see
ProVision Installation and Administration Guide, Migrating
Topology.
Task Manager
Enables you to review the status of a current task being run
by ProVision.
Exit
Enables you to close your ProVision user session. See
Exiting a User Session on page 2-5.
Search > Search

Enables you to find specific objects. The search process is
done on the data held in ProVision, not on the devices in the
network. See Using Search to Search All ProVision Data on
page 2-50.
Tip: You can also select the search icon on the tool bar.
Search in Tree
Enables you to find specific objects in the Physical Viewer.
Again, the search process is done on the data held in
ProVision, not on the devices in the network. See Searching
the Tree Viewers on page 2-53.
Fault > Events Browser> Security Log

View the ProVision Security Log.
Events Browser > New Events Browser
Enables you to see saved Event Browser views, select the
view you want to open, or create a new Events Browser.
Tip: You can also use the add Event Browser View icon, and the
drop-down arrow to display saved Event Browser views.
Scoreboard Groups > New Scoreboard Groups

Enables you to view saved Scoreboard groups, and select a
Scoreboard group to open, or add a new Scoreboard group.
Tip: You can also use the add Scoreboard group icon, and the
drop-down arrow to display saved Scoreboard groups.
For more information on Scoreboard Groups, see

Scoreboard Group Scenarios on page 4-78.

Menu Item Function
Event Pre-Filter
Enables you to view, add, and remove pre-filter events.
Events that match the pre-filter events are blocked before
reaching the system. Filtering events at input reduces the
number of events being fully processed and increases
performance.
For more information on the Event Pre-filters, see Event
Notification on page 4-51.
Event Notifications
Enables you to set up ProVision to notify you via email,
audio, or pop-ups whenever selected events occur within
the network. You can also instruct ProVision to run a shell
script for a batch file whenever selected events occur.
For more information see Event Notification on page 4-51.
Notifications Preferences
Enables you to set up the IP address of your mail server and
other required settings for E-mail notification.
For more information see Set the Server Notification
Preferences on page 4-52.
Configuration > IP Address
Enables you to view and change IP information assigned to
devices on the network. The following information is
available:
• IP Address
• Read Community
• Write Community
Eclipse License
Enables you to load licenses to individual Eclipse radios, to
provide a capacity greater than the default factory setting
of 10xE1 or 16xDS1.
For more information, see Eclipse Node Licenses on
page 3-121.
Configuration Profiles
Enables you to apply settings to multiple radios.
For more information, see Configuration Profiles for Bulk
Configuration on page 3-72.
Software Loading
Lists the container and current software version of each
Eclipse radio in the network. For more information, see
Loading/Activating New Eclipse Software and Licenses on
page 3-110.
614-330055-001 July 2009 2-17

Menu Item Function
Software Loading Preferences

Enables you to update the software of the Eclipse radios.
The functions include:
• Software Register
• Server
For more information, see Loading/Activating New Eclipse
Software and Licenses on page 3-110.
Network Auto-Discovery
Set up specific devices to be auto-discovered.
Global Circuit Trace
Enables you to run a global circuit trace.
Reports Help Desk

Creates a report for you to send to the Help Desk when you
need support.
Network Health
Enables you to run a Network Health Report.
Fuel Usage
Enables you to run a Fuel Usage report for an Energy
Management location.
Inventory
Enables you to run an Inventory report for a selected radio.
Capacity
Enables you to run a Capacity report for a selected radio.
Server Reports
Enables you to view generated Server reports.
Performance Data Collection

Enables you to view and change performance data
collection criteria, daily and/or every 15 minutes, for each
radio in the network. By default, when a radio is deployed,
data collection is set to daily. For more information, see
Data Collection on page 5-14.
Thresholds
Set data collection thresholds for devices in the network.
Ethernet Bandwidth
View Ethernet Bandwidth use for Eclipse devices.

Menu Item Function
Administration ProVision User Accounts

This is an administrative function. It enables you to create,
delete, and view all user accounts. For more information
see ProVision Installation and Administration Guide, Access
Control.
Change User Details
Enables you to change your contact details and password.
For more information see Entering Your Contact Details on
page 2-7.
Database Purge
Enables you to set the purge criteria and the time of day
that the purge process occurs. For more information see
the ProVision Installation and Administration Guide, Access
Control.
Database Backup > Manual Backup

Database Backup > Scheduled Backup
Enables you to enter a backup description and to indicate
what the system includes in the backup. See ProVision
Installation and Administration Guide, Database
Management.
Server Redundancy
Enable backup server redundancy. See ProVision
Installation and Administration Guide, Standby Server
Management.
Device Security Accounts
This is an administrative function. For radio types that have
user name and password security such as the XP4 radio,
this function enables you to enter these details into
ProVision. See ProVision Installation and Administration
Guide, Access Control.
Generic Device Management
This is an administrative function. For generic devices
entered by the user, this function enables you to enter the
device configuration details into ProVision. See ProVision
Installation and Administration Guide, Generic Device
Management.
Email Server Configuration
In this screen, you note the IP address of your email server,
used when ProVision sends an email message about an
event. See Set the Server Notification Preferences on
page 4-52.
Client Multicast Settings
Enables client multicast updates.
614-330055-001 July 2009 2-19

Menu Item Function
Help > Help Topics

Enables you to access the ProVision User Guide online.
License Details
Displays your ProVision license details.
Customer Support
This window has tabs for the three Customer Support
centers and their contact details.
About ProVision
Displays the version of ProVision that is installed.
Related Topics:

Main Tool Bar

The main Tool Bar and its buttons are a fast way to access frequently used ProVision
functions. The main Tool Bar is shown below. The Physical Viewer, Map Viewer, Event
Browser, and other screen areas have their own tool bars.
Table 2-3. Tool Bar Icons
Icon Name Definition
Tool Bar:
Search Enables you to rapidly find specific objects.

See The ProVision User Interface on page 2-13.
Task Manager Lists all tasks, completed or otherwise, that have

been executed in ProVision. Pop-up windows
provided additional information and functions
when executing tasks. See Loading/Activating
New Eclipse Software and Licenses on page 3-110.
Server Reports Saves and retrieves reports from a single radio or
from multiple radios.
For more information see View / Save / Delete
Server Reports on page 5-111.
Global Circuit Runs a global circuit trace on all circuits in the
Trace system. See Initiating and Viewing a Circuit Trace
on page 3-85.
Event Browser Enables you to open a new Event Browser and

select saved Event Browser views. See Event
Browser on page 2-47.
Scoreboard Enables you to add a new Scoreboard group and
Groups view saved Scoreboard groups. See Scoreboard
Group Scenarios on page 4-78.
Related Topics:
614-330055-001 July 2009 2-21

Right-Click Menus
ProVision right-click menus provide access to the options available for the selected
object, for example a region, an Eclipse radio, or an event. You can access right-click
menus from the objects displayed in Physical Viewer, Map Viewer, and from events
listed in the Event Browser. The options presented in a given right-click menu depend
on the context of the object selected.
To display a right-click menu:
1. Place the cursor over the object or event entry.
2. Right-click using the right-click button on the mouse.
In the ProVision screen, a right-click menu displays. The menu contains the
function options that are available with the selected object or event.
3. Drag the cursor to the desired menu option and left-click to select.
The window or dialog box displays.
Right-click menus are available for:

• All items in the Physical Viewer and Map Viewers, including:
• Containers
• Root levels
• NBI options
• Devices
• Device components
• Links
• Logical links
• All items in the Logical Container and Circuit Viewers, including:
• Logical containers
• Circuit bundles
• Circuits
• Events

Radio Right-Click Menus

Different radio types have different right-click menu options, based on the available
functions for the radio.An example of a radio right-click menu is shown below.
Note that items that are active for a radio are checked. In the example above, the radio
is Managed and is having 15-minute Radio Performance Data recorded.
When a link is established between two radios, the right-click menu includes two
additional options:
• Remote([radio] LINKn) - Displays the options for the remote radio that the selected
radio is connected; where “radio” is the name of the remote radio and “n” is the
remote radio’s slot number where the remote link hardware is installed.
• Link - Displays the options for the link that connects the selected radio and the
remote radio.
614-330055-001 July 2009 2-23

Tree View Tabs: Physical, Logical, Circuits
There are three tabs that provide tree views of ProVision devices:
• Physical - Displays the complete “tree view” of the entire network.
• Logical - Displays logical containers.
• Circuits - Displays circuits.
Figure 2-3. Physical Viewer Frames
The topics covered in this section include:

• Physical Viewer on page 2-24
• Logical Tree Viewer on page 2-29
Physical Viewer
In the Physical View option, the entire radio network is represented as a tree of
containers and devices. Each container (for example, a region) is represented as a
parent, with all the devices positioned underneath, as its children.
A container is a collection of related objects arranged in a hierarchical

relationship. Objects can have parents and children.

Figure 2-4. Tree Viewer - Physical Viewer
You can reparent objects within the Physical pane. For more information see DXR 200
and DXR SMA Device Deployment on page 3-39.
Within the Physical pane, the regions, sites, racks, and devices are listed in alphabetical
order.
Context-sensitive right-click menus are supported within this view. For more
information, see Right-Click Menus on page 2-22.
Navigating the Physical Viewer

Select the + next to a parent object (container or Eclipse radio) to expand the tree for
that object.
Select the - next to a parent object to contract the tree for that object.
Double-clicking an object with the left mouse button expands or contracts the hierarchy
tree for that object.
Single-clicking an object with the left mouse button:
• Highlights the selected object in the Physical Viewer and
• Displays the map for the object in the Map Viewer.
Single-clicking an object with the right mouse button:
• Displays a right-click menu listing the options for that object and
• Opens the map for the object in the Map Viewer.
Physical Frame Object Icons

Within the Physical frame, containers and devices are represented by icons. The table
below lists the containers that can be used in ProVision.
Table 2-4. Containers used in ProVision
Container Icon Notes
ProVision Manager The ProVision Manager generates ProVision

related events, for example trial license
expiry messages, and provides access to the
security log, license and customer support
details.
614-330055-001 July 2009 2-25

Container Icon Notes
Root The Root and ProVision Manager icons are

automatically displayed in the Physical
Viewer.
Region A region is a grouping of devices and/or sites

that is typically geographically based.
Site A site is a location where a device or devices

are stored.
Rack A rack represents a physical storage unit in

which a number of devices can be stored. At
a large site, there may be several physical
racks installed.
The table below lists the Harris Stratex Networks SNMP devices that can be deployed
in ProVision.
Table 2-5. Harris Stratex SNMP Devices
Device Icon
ADR 155C: Harris Stratex ADR
ADR 2500: SAGEM ADR, an add-on to the Altium.
, , and Altium, Altium MX, and Altium MX 2+0
Aurora
Constellation
Control Alarm Unit
DART and DART (remote management)

and
DVA and DVM, DVM-XT

and
and DXR 100 and DXR100 (protected)
DXR 700 and DXR 700 (protected): DXR 700 radios are
and
“discovered”/visible in the ProVision when the
connected DXR SMA is deployed.

Device Icon
and Eclipse INU Node and Eclipse INUe Node

The INU has an NCC, 1 fan and 4 slots for plug-ins.
The INUe has an NCC, 2 fans and 10 slots for
plug-ins.
An Eclipse Node can have the following components:
• NCC
• Fan
• RAC (standard and RAC 4X)
• ODU
• DAC
• NPC
• Links (standard, protected, and ring protected)
These components are displayed in the Physical
Viewer using the following icons:
Eclipse IDU Terminal: the Eclipse Terminal has a fixed

layout; ancillary parts are displayed as plug-ins.
LE3000 and WL1000

and
and MegaStar 1+1 and MegaStar M+N
Memotec CX-U
MicroStar I, I Protected, II, and II
TRuepoint 6400, TRuepoint 5000, TRuepoint 4040, and

TRuepoint 4000
and TRuepoint 6500 and TRuepoint 6500 double terminal
Velox
WiMAX Devices: 6100 BS, 6400 BS blade, SmartCore

ASN-GW, WSN ASN-GW Controller, Subscriber Station
XP4 (remote management) 16xE1/E3/DS3 and XP4

and
16xE1/E3/DS3 (remote management, protected)
XP4 16xE1/E3/DS3 and XP4 16xE1/E3/DS3

and (protected)
614-330055-001 July 2009 2-27

Device Icon
XP4 2/4/8x (remote management) and XP4 2/4/8x

and (remote management, protected)
XP4 2/4/8x and XP4 2/4/8x (protected)

and
Table 2-6. TNet Device Icons
Device Icon
Classic II
and LC Series and LC Series (protected)
M Fiber
M Series and M Series (protected)

and
and Quantum and Quantum (protected)
Spectrum I
and Spectrum II and Spectrum II (protected
TNet Proxy
W Series and W Series (protected)

and
Table 2-7. Generic SNMP Device Icons
Device Icon
The Generic SNMP device icons represents SNMP enabled,

non-Harris Stratex Networks devices. You can manage
these devices and ProVision also presence polls them.
From left to right, these devices are:
• Generic
• Multiplexer
• Router
• Switch
• Microwave Radio
• Power Supply
• Alarm Unit
• Base Station
Instructions for adding containers and deploying devices are described in Deploying
Devices on page 3-6.
Related Topics:

Logical Tree Viewer

The Logical tree viewer displays the logical containers created in ProVision, and the
devices and circuits grouped under each logical container. This tree view supports
severity propagation, with the logical container taking on the highest severity of its
devices.
Configure your required logical containers. Then, add devices to them. You might, for
example, create a logical container to include all backbone radios or all the radios
within the Central Business District. For more information see Logical Containers on
page 4-69.
Figure 2-5. Physical Viewer - Logical Containers Tab
By default, the Logical Containers tab is not populated at installation.
Circuits Tree Viewer

The Circuits tab lists circuit bundles within the network that are made up of one or
more Eclipse radios. Circuits with non-Eclipse radios do not appear in the Circuits tab.
Like the Logical Container tab, this tree view supports severity propagation, with the
circuit bundle taking on the highest severity of its devices.
After a Circuit Trace command is executed, ProVision lists all Eclipse radio circuits. For
more information, see Circuit Management on page 3-84.
614-330055-001 July 2009 2-29

Figure 2-6. Physical Viewer - Circuits Tab
By default, the Circuits tab is not populated at installation.
Related Topics:

Map Viewer
The Map Viewer provides two different views of the network:

• Physical Map View on page 2-32
• Flat Map View on page 2-33
The following object types are supported in the Map Viewer;

• Region
• Site
• Rack
• Device objects
• RF links
• Service links.
Right-click an object in the Map Viewer to see the right-click menu, which lists the
options available for that object.
Additional information on the Map Viewer is in the following sections:

• Map Tools on page 2-34
• Map Backgrounds on page 2-36
• Submaps on page 2-38
614-330055-001 July 2009 2-31

Physical Map View

The Physical Map View shows an overview of the network. This view displays only the
first level of children under the parent object selected. To open this view, click on the
Physical Map icon on the Map Toolbar:
Figure 2-7. Map View
When an Eclipse Node is selected in the Physical Viewer, its chassis and components
are displayed in the Map view.
The map help, map properties, zoom and padlock functions are described
in Map Tools on page 2-34.
Related Topics:
• Flat Map View on page 2-33

Flat Map View

In the Flat Map view, only the network devices and links are displayed. This view
enables you to change from a traditional hierarchal view showing regions, sites, and
devices, to an all network object view. To open this view, click on the Flat Map icon in
the Map Toolbar:
This view is particularly helpful when managing events, because you can see the
severity information for both ends of the links, for many radios.
Flat map views can be displayed for any container (root, region, site, and service)
within the Physical Viewer. For example, a flat map view selected at the root container
displays all the network devices. A flat map view selected for a region or site displays all
the network elements grouped under the container selected.
This alternative view is very useful for a use who wants to maintain the logical structure
of regions/sites and view the status of all network elements at a glance.
Figure 2-8. Flat Map View
Related Topics:
• Map Tools on page 2-34
614-330055-001 July 2009 2-33

Map Tools
These are the functions in the ProVision Map toolbar.
Map Tool Icon Use
Physical Click this to view the Physical Map view.

Map
Flat Map Click this to view the Flat Map view.
Navigate Use these arrows to navigate to different maps in the

Up, Back, or network.
Forwards
Zoom to Fit The Zoom to Fit Screen tool enables you to zoom in and
Screen see all of your devices on the Map View at one time. This
is particularly useful for large networks. To return to the
standard view, click the Zoom to Fit tool again.
Enable/ The map zoom tool enables you to zoom in/out of the
Disable Map Map Viewer. The map zoom tool functions are:
Zooming
• Single-click the zoom icon to enable the map zoom
tool.
• Left-click the zoom icon to zoom in on the map and
objects displays in the Map Viewer.
• Right-click the zoom icon to zoom out.
• Single-click the zoom icon a second time to disable the
map zoom tool.
Print The map print tool enables you to print the contents of
the map viewer.
• Fit To Page prints the entire map view on a single page.
• Visible Area prints only the area displayed on the map
view.
• Page Setup allows you to set up the print criteria for
your printer.
Locked and By default the map padlock is locked. This means that
Unlocked objects cannot be moved in the Map Viewer.
To move objects around in the Map Viewer, select the
padlock icon. The icon changes to an unlocked padlock.
Select the unlocked padlock, and the icon changes back
to the locked state. The objects in the Map Viewer revert
back to the default, locked state.
For additional information see Moving Containers and
Devices in the Map Viewer on page 3-48.
Object The map object filter tool enables you to search for and
Filter select specific map items.

Map Tool Icon Use
Properties The map properties tool enables you to add and change
map backgrounds. For more information, see Map
Backgrounds on page 2-36.
Help The map help provides a description of the various links,

device states and event management tasks that are
displayed within the Map Viewer.
To display the map help, hold the cursor over the help
button. The following pop-up window defines the various
links and icons on the Map Viewer.
Related Topics:
• Map Backgrounds on page 2-36
614-330055-001 July 2009 2-35

Map Backgrounds
Introduction
You can add a background image for any object located in the Physical pane. When an
object is selected, in the Physical pane, the imported image displays in the Map Viewer.
Icons can then be placed on top of the background image. Typically, a background
image is a geographical map, a floor plan, or some form of schematic.
Use your favorite search engine to find websites that provide maps for countries,
regions, and cities that you can download and use in ProVision.
ProVision supports the following image formats for map backgrounds:
• jpg
• gif (GIF87 and GIF89a)
The map viewer window size is 4096 X 3072 pixels. Use image editing
software, such as PhotoShop, to size the map image to this size.
Procedure
1. Within the Physical Viewer, select the object to which you want to apply the map
image.
2. Select the Map Properties icon on the Map Viewer.
The Map Properties window displays.
3. Select the checkbox to enable Background Image selection.

4. Select the button. The Map Selection window displays.
5. Browse to the location of the stored map files.
6. Select the required map file and select Open.
7. To apply the selected map, select OK.
To remove a map background image:

1. Within the Physical Viewer, select the object that you want to remove.

2. Select the Map Properties icon on the Map Viewer.

The Map Properties window displays.
3. To remove the background image, deselect the Background Image checkbox.
4. To accept the change, select OK.
The Map Viewer displays with a blank background.
Related Topics:
Detailed Device Views
In ProVision, you can view detailed information about each managed device. All device
have at least one detailed view option: several have two or three.
To identify the device views available for a device, right-click it. Device view options are
listed in the right-click menu.
The following are the detailed device view types:
• Submap View - A view displaying managed elements of a device. See Submaps on
page 2-38.
• Equipment View - A real-time view of a device, based on the physical
configuration of the device. See Equipment Views on page 2-39.
• Interface View - A view displaying a device’s IF interfaces. See Interface Views on
page 2-46.
614-330055-001 July 2009 2-37

Submaps
Introduction
A submap is a separate floating window showing the elements within the selected
object or device. This figure shows an example of a submap window. Submaps are fully
functional maps with their own menu and tool bar.
A submap can be opened for a container, device, RF link, Eclipse element (for example,
DAC, LINK) or Memotec element in either the Physical Viewer or Map Viewer.
Figure 2-9. Eclipse Submap View
Figure 2-10. Memotec Submap View
Use submaps to:

• Have several submaps open at any one time; these can be maximized or minimized
as required.
• Perform specific operations on a submap using its menu and tool bar.
• Increase the Physical Viewer size by minimizing the Map Viewer and displaying
submaps.
Procedure
To open a submap:
1. Right-click the container or device (within the Physical Viewer, or Map Viewer, or
submap).

2. From the right-click menu displayed, select Open Device.

3. Or, in the Physical Viewer, open a device and select a sub-device from the Physical
Viewer.
A separate submap window displays.
If the device’s right-click menu says Open Submap, the view that displays
is similar to the Flat Map option. These devices usually have more
detailed Equipment Views on page 2-39.
Related Topics:
• Detailed Device Views on page 2-37
• Equipment Views on page 2-39
• Interface Views on page 2-46
Equipment Views
Introduction
For certain types of radio, users can access both the standard submap view and an
Equipment View. An Equipment View shows the layout and status of all radio
components, exactly as they are installed.
Equipment Views are available for the following radio types:
• ADR 155c
• ADR 2500
• Constellation
• MegaStar M:N and 1+1
• TRuepoint 4040 and 5000
• TRuepoint 6400
• TRuepoint 6500
• StarMAX 6100 and 6400
• WiMax ASN-GW Home Agent
Procedure
To open an equipment view:
1. Right-click the device within the Physical Viewer or Map Viewer.
2. From the right-click menu displayed, select Open Equipment View. Or, for a
StarMAX 6100, 6400, or SmartChorus ASN-GW Base Station, select Open Device.
3. A separate Equipment View window displays. ProVision communicates with the
device to get the most current data for the equipment view. This may take a
moment.
614-330055-001 July 2009 2-39

4. To rediscover plug-ins in the Equipment View, click the Refresh button .

5. To view the Event Browser for this item, click the Event Browser button .
Equipment View Examples

In the Equipment Views, the color of each plug-in device changes based on new events.
ProVision updates the event status automatically.
ADR 155c
The ADR 155c displays with this equipment view.
ADR equipment views are only available for ADR155c or 2500 if the ADR
firmware is later than P2.6.
ADR 2500
The ADR 2500 displays with this equipment view.

Constellation
The radio below is a Constellation terminal.
The radio below is a Constellation repeater, set up for two links.
614-330055-001 July 2009 2-41

MegaStar M:N and 1+1

This radio displays at two levels in the equipment view; the shelf and the specific
equipment layout. Double-click on a device on the shelf to drill down and view the
specific equipment layout. In the example below, by drilling down into the SPU shelf,
we see that the alarm is from the CTI.
TRuepoint 4040 and 5000
TRuepoint 4040 and 5000 radios display with the same type of equipment view:

TRuepoint 6400
TRuepoint 6500
614-330055-001 July 2009 2-43

StarMAX 6100 and 6400

Both StarMAX 6100 (one blade) and StarMAX 6400 (up to 4 blades) present the same
Equipment View. For StarMAX 6400, the tooltip indicates whether the device blade is
a Master or Slave.
WiMax ASN-GW Home Agent

SmartChorus WiMax ASN-GW Base Station
Related Topics:
Detailed Device Views on page 2-37
Equipment Views on page 2-39
Interface Views on page 2-46
614-330055-001 July 2009 2-45

Interface Views
For certain types of radio, users can access an Interface View. An Interface View shows
the IF interfaces for the radio.
Interface Views are available for the following radio types:
• LE3000
• WL1000
• Generic Devices
• StarMAX 6100 and 64000
• StarMAX Subscriber Stations
• WiMAX ASN-GW/Home Agent
The color of the interface shows the interface status:
• Green = Connected
• Red = Disconnected
• Gray = Disabled
Figure 2-11. Interface View
Procedure
To open an interface view:
1. Right-click the device within the Physical Viewer or Map Viewer.
2. From the right-click menu displayed, select Open Interface Viewer.
3. A separate Interface View window displays. ProVision communicates with the
device to get the most current data for the equipment view. This may take a
moment.
4. To rediscover plug-ins in the Interface View, click the Refresh button .
5. To view the Event Browser for this item, click the Event Browser button .
Related Topics:
Detailed Device Views on page 2-37
Submaps on page 2-38
Equipment Views on page 2-39

Event Browser
The main Event Browser displays at the bottom of the main user interface, presents a
scrolling list of events captured by ProVision.
From the main Event Browser, you can perform many functions, such as acknowledge
and clear events, view event history and probable cause, and add an event to
pre-filtering. For details see Event Management Procedures on page 4-5.
By default, unacknowledged active events are listed in chronological order, with the
most recent events displayed at the top of the list. A maximum of 1000 events can be
displayed in the main Event Browser.
Figure 2-12. Main Event Browser
# Value
1 Severity
2 Status
3 Acknowledged/Unacknowledged
4 Note
5 Status Bar
6 Notification Dialog Boxes
7 Event Severity Counts
Status Bar
The status bar provides the following information:
• The number of active notification dialog boxes. For more information see Set the
Server Notification Preferences on page 4-52.
• The ProVision server to which you are connected.
• The user currently logged on.
614-330055-001 July 2009 2-47

• The event severity counts, color-coded representations of the total number of events
of each severity type.
To view only the events of a particular severity, for example major

events, in a separate Event Browser window, select the color-coded event
severity count.
Event Browser Menu

The right-click menu has additional functions for the main Event Browser.
• Event Filters opens the Filters window and allows you to tell ProVision which event
you want to filter. For more information see Event Log Pre-Filtering on page 4-36.
• Browser Options opens the Browser Options window. From here, you can customize
the details, fields, and sorting options in the Event Browser view. For more
information see Changing Event Browser Options on page 4-29.
• Save Settings saves the current Event Browser settings.
• Maximize/Hide allows you to display and hide the Event Browser view.
Customizing the Main Event Browser

In the main Event Browser, you can change how the information displays.
• To move a column, click and drag the column title bar to the required position.
• Select the required column title to change the order in which events are displayed.
Select the same column title a second time reverses the sort order for the column.
For more information, see Customizing Event Browsers on page 4-4.
Next Topic:
Using Search to Search All ProVision Data on page 2-50

The Task Manager Screen
The Task Manager screen shows the status of tasks in progress. You are often prompted
to open the Task Manager when you start a task or report that may take some time to
run.
ProVision can run multiple tasks simultaneously. If multiple tasks are running, the
Task Manager will show these tasks.
While ProVision can run multiple tasks simultaneously, it will not run
multiple versions of the same task. For example, only one Inventory
Report can be generated at a time.
614-330055-001 July 2009 2-49

Using Search to Search All ProVision Data
Introduction
ProVision’s main search function enables you to find specific data in the ProVision
system. The Search function searches all ProVision data to locate the data you specify,
from an IP address for a specific radio to all radios in a particular state.
Procedure
1. Either: select Edit > Search... from the menu to open the Search window. Or, from
the tool bar, select the Search icon.
The Search window displays.
2. The Search window lists the criteria that you can enter to narrow your search:
• Name
• Physical Container
• IP Address
• Object Type - Note that you can search for one object type or, by selecting check
boxes in the menu, you can search for multiple object types.
• Object State

• Devices with Pre-Filter Enabled

• Devices with Performance thresholds Enabled
• Devices with ethernet or standard data collection every 15 minutes or daily
After you have entered all your search criteria, click Search Now.
3. The results display at the bottom of the Search window. You can select a column
title, Object or Object Container, to sort the results in either ascending or
descending order.
4. You can right-click an object or a container in the search results screen to view
associated right-click menus. See the Search Result Examples below for a sample
of this.
5. To clear the results, or to enter data for another search, click New Search.
6. To close the Search window, select Close.
Search Result Examples

The figure below shows a search result for a specific IP Address. 10.16.150.52 is the IP
address of an Eclipse INU. The Eclipse radio, its components, and related links are
displayed as a result of the search. Note that the last item has been right-clicked and
displays a menu with available functions.
614-330055-001 July 2009 2-51

.The next figure shows an example of a search result, for Eclipse radios with 15-minute
radio data collection enabled. This search criteria is useful when the system is running
slowly, and you suspect there might be too many radios with this mode of data
collection enabled.
Related Topics:
Next Topic:
Searching the Tree Viewers on page 2-53

Searching the Tree Viewers
Introduction
ProVision’s Find search function enables you to find specific data in any of the
ProVision tree views: Physical, Logical, or Circuits. This allows you to find and view an
item quickly.
Select Find from the Tree Viewer toolbar to open the Search Tree window. This will
appear at the bottom of the TreeViewer.
This Find function uses “wildcard” searches. With a wildcard search, you use an
asterisk (*) or question mark (?) to tell the function how you want to search for your
numbers or text. Using the up and down icons, you can then go through the Tree View
and find the items that include part or all of the numbers or text.
For example, if we want to find items with an IP address of 10.16.10.52, there are four
ways to enter that IP address for a wildcard search:
• 10.16.10.52* = An asterisk after the value; finds all items that begin with this value.
• *10.16.10.52 = An asterisk in front of the value; finds all items that end with this
value.
• *10.16.10.52* = An asterisk before and after the value; finds all items that contain
this value.
• 10.*.52 = An asterisk within a value; finds all items that begin and end with the noted
values.
614-330055-001 July 2009 2-53

Procedure
To search any Tree View for a specific item:
1. Select Find from the Tree Viewer toolbar, or highlight the Tree Viewer and press
Ctrl+F3 on the keyboard.
The Tree Search field displays below the Viewer.
2. Type the search criteria. Use the Wildcard search convention.

3. To start the search, either press the Enter key, or click the Up and Down icons in
the Tree Search.
The Tree Search function will go up or down the Tree View and highlight each item
that matches your search. Continue until you find the item you want.
4. To close the Tree Search, select the red X. The Tree Search closes and is not seen in
the display.
Related Topics:
• Using Search to Search All ProVision Data on page 2-50
Next Topic:
Icons Information and Usage on page 2-55

Icons Information and Usage
Both the Physical Viewer and the Map Viewer show the current status of each network
element, with icons representing the highest severity event that has been detected for
the device. Color and other graphic cues show the status of the objects/network
elements. This alerts you to changes in device status.
To identify potential problems, ProVision propagates the alarm state of objects
upwards through each object, and its parent objects change color as well. A parent
object’s color reflects the most severe alarm on any of its children.
This section covers the following topics:
• Viewing Radio Icon Anatomy on page 2-55
• Event Severity Color Coding on page 2-57
• Device States on page 2-58
• Radio Tasks on page 2-59
Viewing Radio Icon Anatomy

Physical Viewer Display of Radio Icon Anatomy
The figure below shows an example of a Eclipse Terminal icon displayed in the Physical
Viewer’s physical pane. From the device icon, you can identify the name of the device,
the type of device, if the device is functioning normally by the color of the event severity
icon, and if any tasks are being performed on the device, for example, pre-filtering.
# Value
Physical Viewer - Labeled Radio Icon
1 This item is Closed in the tree structure; sub-radios and

devices are not displaying.
2 If an event is present, the color here indicates the event

severity. Mouse over this to view the event type.
3 Radio icon.
4 Task.
5 Radio name.
614-330055-001 July 2009 2-55

Map Viewer for Radio Icon Anatomy
The figure below shows an example of an XP4 radio icon displayed in the Map Viewer.
Each radio icon shown in the Map Viewer, or a submap, displays information about the
network element the icon represents. The information includes the radio’s name, state,
and event information.
# Value
Map Viewer - Labelled Radio Icon
1 If an event is present, the color here indicates the event

severity. Mouse over this to view the event type.
2 Radio icon.
3 Radio state and task.
4 Radio name.
• Radio Name - Identifies the specific radio (network element) represented by this
icon.
• Radio State or Task - The current state of the radio. For more information, see Device
States on page 2-58
• Event Severity Colors - Indicates the most severe active event in effect for the device.
Related Topics:
• Event Severity Color Coding on page 2-57
Event Severity Color Coding

Each event has a severity level. The level indicates whether the event is a routine action,
a warning of impending problems, or a signal of catastrophic events within a device.
This table defines the six levels of event severity and the associated color code.
Table 2-8. Event Color Codes
Severity Level Color Code
Critical Red
Major Orange
Minor Yellow
Warning Cyan
Normal Green
Informational White
Related Topics:
614-330055-001 July 2009 2-57

Device States
A device state defines the conditions in which a device exists. State representation is
based on Telecom standards that include:
• OSI state dictionary (based on the OSI SMF 10164-2 standard)
• Event state dictionary to display the set of events
A radio can only be in one state, but can have a number of tasks applied to the events it
is generating. When a radio has more than one task, a + sign displays on the state
indicator. When the cursor is moved over a radio icon, pop-up text displays
information about the radio, such as its state and tasks.
Object Pop-up Details

When you move the mouse over an object in the Physical Viewer, pop-up details for the
object are displayed. The INU radio shown below is in an active state, has 5-min data
collection and pre-filtering enabled, is Managed, and has two warnings.
When you mouse-over a container object the number of its children displays in the
pop-up.
This table lists the various states for devices, and how these states are indicated in the
user interface.
Table 2-9. Device States
Device Icon Other Indicators

State
Radio With Pop-up Text
Unmanaged - Event severity is blue. The pop-up text displays State:

Unmanaged.
Managed - Event severity can be any of the colors - green, cyan,

yellow, orange, or red. The pop-up text displays State:
Managed.
For more information on managing a device, see Managing
a Device on page 3-51.
Connecting ProVision is attempting to connect to the device across the
network using the device’s IP address. There has been no
communication from the device since being managed. The
pop-up text displays State: Connecting.
Device Icon Other Indicators

State
Asleep The radio is asleep. The pop-up text displays State: Asleep.
For information on putting a radio to sleep, see Sleep Status
for a Device on page 4-20.
Errored The managed radio is not responding to polling from
ProVision. The pop-up text displays State: Errored.
“+” icon If a “+” icon appears in the bottom left corner of a task icon,
this indicates that more than one radio task and/or device
state is associated with that radio. The pop-up text displays
the additional tasks/states.
Related Topics:
Radio Tasks
A task represents additional ProVision activity on events. This can be for one radio or
a set of radios. For example, pre-filtering events stops the events that meet the
pre-filter criteria before they can get into the system. Typically, a task is only active for
a radio that is Managed. When a task is being performed on a radio or radios, the radio
displays with the task icon, for example, pre-filtering.
Table 2-10. Radio Tasks
Radio Task Icon
Pre-filtered For more information about pre-filtering events,

see Event Log Pre-Filtering on page 4-36.
15-minute data ProVision uses the data from the radio to create
collection performance trends graphs. See Data Collection on
page 5-14 for more information.
Performance Performance thresholds feature allows you to
Thresholds associate an alarm or group of alarms with
unexpected performance results. See Performance
Thresholds on page 5-42 for more information.
“+” icon If a “+” icon appears in the bottom left corner of a
task icon, this indicates that more than one radio
task and/or device state is associated with that
radio. The pop-up text displays the additional
tasks/states.
Related Topics:
614-330055-001 July 2009 2-59

Chapter 3. Deploying and
Managing Devices
You can deploy and manage devices in a network using ProVision.
Deploying a device provides ProVision with details about a real device in the network.
Managing a device activates ProVision to communicate with the device and show the
device status.
A device is any SNMP enabled object that ProVision can communicate with, for
example, a Harris Stratex Networks (HSX) radio, a DXR SMA or a non-HSX radio.
This section is written for the NOC operator. It is assumed that ProVision is already
installed and managing the network. It describes the workflow and procedures to
deploy, link, and manage devices in ProVision.
• About Deploying and Managing Devices on page 3-2
• Deploying Devices on page 3-6
• Managing Devices on page 3-51
• Miscellaneous Device Procedures on page 3-66
• Circuit Management on page 3-84
• Loading/Activating New Eclipse Software and Licenses on page 3-110
614-330055-001 July 2009 3-1

Chapter 3. Deploying and Managing Devices
About Deploying and Managing Devices
For a radio network, the majority of devices in the network are already physically
installed, commissioned, deployed, and managed in ProVision. When new towers/sites
are installed, the NOC operator/engineer deploys and manages the new devices in
ProVision.
When a device is installed and successfully commissioned, you can manage the device
with ProVision. ProVision polls the device and receives events from the device.
Deploying a device provides ProVision with data about that device in the network. The
deployed device displays as a graphical icon on the ProVision user interface. Until a
new device is deployed and managed in ProVision, ProVision does not recognize the
device, or receive traps generated by a device.
To successfully deploy devices, you need the following information: installation
locations, radio types, and IP addresses.
To enable you to group devices by location, ProVision includes the following
containers:
Region Site Rack
When setting up the network in ProVision you can choose to use any or none of the
container objects. If the network is already set up and you are deploying new devices,
then follow the existing pattern.
A high level container can have additional containers and devices. For
example, a region may consist of several sites and devices
Deployment Guidelines
When deploying HSX devices, you must create your site hierarchy before deploying any
devices. Once you have deployed a device, you can change the site hierarchy placement
of the device at any time.
Naming Standards
You and your company choose the naming standards to apply to your ProVision
network. Set the naming standards as early as possible to make the implementation
easier. Note, that with the proper authority, you can rename most ProVision objects at
any time.
As an example of how your devices and links might be named:
If you have three sites (A, B, and C), that have two connecting links (one between A and
B, and one between B and C) you could have Eclipse device names of:
• Eclipse A-1 10.14.135.1
• Eclipse B-1 10.14.135.3
• Eclipse C-1 10.14.135.5

Device Deployment and Management Workflow

The process below shows how deploying and Managing devices fits into the total
ProVision management process.
1. Install ProVision.
2. Is this installation an upgrade?
• If Yes, after you install the upgrade, import the saved topology.
• If No, proceed to the next step.
3. In ProVision, deploy and manage devices.
4. Use ProVision to manage events.
5. Use ProVision to run system diagnostics.
6. During deployment, management, and system diagnostics, ProVision uses
performance trend analysis of G.826 and RSL/RSSI.
Next Topic:
The Process for Deploying and Managing Devices
614-330055-001 July 2009 3-3

The Process for Deploying and Managing Devices

Prerequisites
To deploy and manage devices, you must have all of the following information:
• A comprehensive network element inventory
• List of all the sites, each radio name and its type
• Know any radio specific details
• Determine IP address assignments
• Determine device specific configuration requirements
Dependencies
ProVision requires the correct IP address for the devices on the network. This is
required so that ProVision can poll and receive events from the radios.
Deploying Radios
This is the recommended process for deploying HSX radios in an existing network.
1. Add a new Container, if required.
2. Deploy the new Radios.
3. If required (for example, for new TRuepoint radios) update their
4. configuration.
5. Manage the new radios.
6. Create links.
7. Verify the new links.
8. Verify that ProVision is receiving events from the radios.
9. Check that the radios, and their links, are all configured correctly.
Pre-Deploying Radios
When you are pre-deploying radios in ProVision, in advance of rolling out the network
you can use the following process. The main difference between this and the standard
Deploying Radios process is that you create and verify links before you Manage the
radios.
1. Add a new Container, if required.
2. Deploy the new Radios.
3. Create links.
4. Verify the new links.
5. Manage the new radios.
6. Verify that ProVision is receiving events from the radios.
7. Check that the radios, and their links, are all configured correctly.

This process is not applicable to the DXR 700 and Eclipse Node radios. A DXR 700 is
auto-discovered when the DXR SMA to which it is connected is managed in ProVision,
and therefore the radio is managed before you can create the link. The Eclipse Node
uses plug-ins, which means its configuration is auto-discovered when the radio is
managed in ProVision. Only then can you create a link or links.
Device Deployment By Type

Table 3-1. Device Deployment Instructions by Device Type
CAU CAU (Control Alarm Unit) Deployment on page 3-27

Constellation Constellation Device Deployment on page 3-25
DXR 200 DXR 200 and DXR SMA Device Deployment on page 3-39
DXR SMA DXR 200 and DXR SMA Device Deployment on page 3-39
Eclipse Eclipse Devices and Nodes Deployment on page 3-15
EfficientSite EfficientSite Manager Deployment on page 3-33
Manager
Generic Generic Device Deployment on page 3-29

TNet TNet Device Deployment on page 3-34
TRuepoint 4000 TRuepoint Device Deployment on page 3-18
TRuepoint 6500 TRuepoint 6500 Device Deployment on page 3-22
WiMAX WiMAX Device Deployment on page 3-31
All Other Standard SNMP Device Deployment on page 3-11
Devices
Includes ADR 155c, ADR 2500, Altium, Aurora, Dart, DVA,
DVM, DVM-XT, DXR 100, LE3000, all MegaStar, Memotec
CX-U, all MicroStar, SAGEM-LINK, Spectrum II SNMP, Velox,
Radwin WL1000, XP4
Next Topic:
Deploying Devices
614-330055-001 July 2009 3-5

Deploying Devices
When you deploy a device, you are providing details about a real device to ProVision.
You can manage the device at the same time or leave the device to be managed at a later
date.
This section covers the following deploying procedures:

• Adding, Editing, and Deleting Device Containers on page 3-7
• Standard SNMP Device Deployment on page 3-11
• includes legacy, MicroStar, MegaStar, DVA
• Eclipse Devices and Nodes Deployment on page 3-15
• TRuepoint Device Deployment on page 3-18
• TRuepoint 6500 Device Deployment on page 3-22
• Constellation Device Deployment on page 3-25
• CAU (Control Alarm Unit) Deployment on page 3-27
• Generic Device Deployment on page 3-29
• WiMAX Device Deployment on page 3-31
• TNet Device Deployment on page 3-34
• DXR 200 and DXR SMA Device Deployment on page 3-39
• Troubleshooting Device Deployment on page 3-46
• Changing a Device’s Container on page 3-47
• Moving Containers and Devices in the Map Viewer on page 3-48
• Renaming a Device on page 3-49
• Deleting a Device on page 3-50
When a device is deployed but not Managed in ProVision, the device does
not generate alarm traps, is not polled for status, and the event state
color is blue, which signifies an unmanaged status.

Adding, Editing, and Deleting Device Containers

A container represents an object that serves as a grouping entity for devices in
ProVision. Other containers are added to a parent container, and devices are deployed
from their container.
This section describes the following Container functions:
• Adding a Container on page 3-7
• Renaming a Container on page 3-9
• Deleting a Container on page 3-9
Adding a Container
The following procedure describes how to add a container. There are three types of
container available. They are as follows:
• Region - Use as a container for Sites.
• Site - Use as a container for radios and/or Racks.
• Rack - Use as a container for Radios.
Procedure
1. In the Tree Viewer or the Map Viewer, right-click on a root icon or an existing
container, for example, the network or a region icon.
2. In the right-click menu, select Deploy Object.
The Deployment window displays.
Click on Containers. The Containers Family window displays.
614-330055-001 July 2009 3-7

3. Select the required Container icon, for example, Site. The Deploying <container>
window displays.
4. In the Name field, type the name for the container.

5. Ensure that the Parent name displayed is correct; the container is placed under the
parent listed.
6. Click Deploy.
The Tree Viewer and the Map Viewer’s Hierarchical layer are updated and display
the new containment icon.
The Deploying <container> results window displays, confirming that the
container has been deployed.
7. Select Close.
The container can be reassigned to another parent.
Related Topics:

Renaming a Container
By default, the network root container is not named. You can give it a name using
the Rename function. You can also change the name of any container that is incorrect
or misspelled.
Procedure
1. Right-click the container to be changed. In the right-click menu, select Rename.
The Rename Object window displays.
2. Make the required changes to the container’s name.

3. To save the changes, select OK.
Related Topics:
Deleting a Container
You can delete a container from the Tree Viewer or the Map Viewer’s Hierarchical
layer. When a container is deleted, the Tree and Map Viewers are refreshed and the
container is no longer displayed.
Before deleting a container, ensure there are no managed radios

or links associated with the container.
If you delete a container that contains radios this has no effect on the
actual radios or the communications traffic they are carrying.
614-330055-001 July 2009 3-9

Procedure
1. Right-click the container icon. In the right-click menu, select Delete.
The Delete Objects window displays.
2. To delete the selected object(s), select Yes.
Related Topics:

Standard SNMP Device Deployment

Introduction
A Harris Stratex or third-party SNMP device has an IP address, can be accessed via IP
networks, and uses the Simple Network Management Protocol to communicate with
ProVision.
When you deploy a device you are providing details about a real device to ProVision.
You can manage the device at the same time or leave the device to be managed at a later
date.
When a device is deployed but not managed in ProVision, the device does
not generate alarm traps, and is not polled for status. The event state
color displays as blue, which signifies an unmanaged status.
This section describes how to deploy standard SNMP devices. To help you deploy
specific device types, see also Device Deployment By Type on page 3-5.
Prerequisites
• MicroStar - For each MicroStar device you are deploying in ProVision, you must
find that device in WebCIT and set up ProVision’s IP address as the manager of that
device. This setting is found in WebCIT via the Provisioning screen, in Network
Setting 2, as the value SNMP Manager #1. See the WebCIT Operator manual for
further details.
• MegaStar - For each MegaStar device you are deploying in ProVision, you must find
that device in FarScan and set up ProVision’s IP address s the manager of that device.
See the FarScan Operator manual for further details.
• Community Strings -Many devices require read and write community strings. The
community string (which is a name or combination of characters) is part of the
device’s configuration information. When ProVision wants to communicate with the
device, it authenticates using the community string. There are typically two
community strings linked with a device, one for reading values and one for writing
(setting) values. These are normally set to “Public” or “Private”, but can be set to
other values as a form of security.
614-330055-001 July 2009 3-11

Procedure
1. Within the Tree Viewer, right-click an existing container and select Deploy Object.
The Deployment window displays, showing all the container and device options.
2. Select the icon for the required device type. The Deployment screen for that device
type displays, showing available devices.
If you cannot immediately find the icon for the device type, try Other
Microwave. Select the required device icon.
3. The Deploying <device name> window displays. Enter the values for the new
device, as described for specific device types listed in the table below.
For all new devices, check to see that the Parent is correct. The device is
placed under the parent listed.
4. Select Deploy.
The Deploying <device name> results window displays.
5. To close the Deploying <device name> window, select Close.
6. Select the required device icon.
8. Select Deploy.

Table 3-2. Device Deployment Details for Standard SNMP Devices
Device Deployment Window Steps
Single Devices: Aurora, DVA, DVM, DVM-XT, ADR, Altium,

Dart, Velox, XP4, Spectrum II SNMP, DXR 100. Memotec
CX-U, LE3000, Radwin WL3000
1. n the Name field, type a descriptive name for the

radio.The radio is labeled with this name in the User
Interface.
2. Enter the radio’s IP address.
3. The Read Community and Write Community strings
have the default values. Only change them if the
radio setting has been changed.
The Read and Write Community strings must match
the strings entered into the radio.
4. To have ProVision start managing the radio, select
the Manage checkbox.
Protected Radios: DXR 100, XP4, SAGEM-LINK
1. In the Name field, type a descriptive name for the

radio. The radio is labeled with this name in the User
Interface.
2. Enter the A radio’s IP address.
3. Enter the B radio’s IP address.
4. The Read Community and Write Community strings
have the default values. Only change them if the
radio setting has been changed.
Multiplexes: ADR 155C, ADR 2500

MicroStar device. It is labeled with this name in the
User Interface.
2. Enter the IP address.
3. The Read Community string has the default value.
Only change it if the radio setting has been changed.
4. To have ProVision start managing this radio, select
614-330055-001 July 2009 3-13

MicroStar I, II, III

MicroStar device. It is labeled with this name in the
User Interface.
MegaStar M:N

Megastar device. It is labeled with this name in the
User Interface.
MegaStar 1+1

Megastar device. It is labeled with this name in the
User Interface.

Eclipse Devices and Nodes Deployment

Introduction
Deploying Eclipse devices and nodes is simple, and similar to Standard SNMP Device
Deployment on page 3-11.
When you are deploying Eclipse nodes, you must select the option to Perform Class
Checking on Deployment. If this is not selected, the Eclipse object is deployed without
checking its radio class, and the object may be incorrect. If it is wrong, you will see an
Invalid Deployment event in the Event Browser.
This indicates that the device needs to be deleted and redeployed as the correct radio
class.
To deploy an Eclipse Edge device, deploy it as an Eclipse INU.
In addition, Administrator-level users can auto-discover and deploy

Eclipse devices with Network Auto-Discovery. See Network Auto-Discovery
for Eclipse and WiMAX BS Devices on page 3-42.
Procedure
1. Identify the IP addresses for the Eclipse devices.
2. In the Tree Viewer, right-click an existing container and select Deploy Object. The
Deployment window displays. Select the Eclipse icon. The Eclipse device options
are displayed.
614-330055-001 July 2009 3-15

3. Select the Eclipse device that you require. Enter the values for it as follows:
Eclipse Node or Terminal (INU / INUe / IDU)
1. Ensure the correct parent displays; the device is

placed under the listed parent.
Interface.
3. Enter the radio’s IP address.
5. Select the checkbox for Perform Class Checking on
Deployment. This checks that the radio class matches
the device deployment window data. If the device
deployment data does not match the actual radio
class, an error message displays:
Click OK. Then, click Back and select the correct device
type.
Protected Eclipse Node

Interface.
Note: In the Name field, note whether the radio is an IDU
ES or an IDU GE.
3. Enter the A radio’s IP address.
4. Enter the B radio’s IP address.
6. When an Eclipse Node is deployed within ProVision, the Eclipse INU icon displays
in the Tree Viewer, and the basic INU chassis displays in the Map Viewer.
7. When an Eclipse Node is managed, ProVision queries the radio to determine its
component layout, and populates the chassis with the results.

Figure 3-1. Eclipse Node that is deployed but not managed
When an Eclipse device is fully deployed, ProVision captures all of its IP

addresses. This provides support for redundant NMS connections.
Related Topics:
• Generic Device Deployment on page 3-29
• Managing a Device on page 3-51
• Verifying ProVision is Receiving Device Events on page 3-52
• Network Auto-Discovery for Eclipse and WiMAX BS Devices on page 3-42
614-330055-001 July 2009 3-17

TRuepoint Device Deployment

Introduction
To deploy a TRuepoint device in ProVision, it must be deployed, then configured using
the Configuration Profiles function. TRuepoint devices must communicate with a
ProVision trap and a ProVision SNMP manager to send data to ProVision.
The procedure below is an overview of the required process. It describes how to deploy
the following TRuepoint devices: 6400, 5000, 2+0, 4040, 4040/2, and 4000. See also
TRuepoint 6500 Device Deployment on page 3-22.
Read Standard SNMP Device Deployment on page 3-11 and Configuration Profile
Settings for Bulk Configuration on page 3-75 for full details.
For TRuepoint 4040 v2 and 5000 devices with V2 controllers, an

additional ProVision function enables you to apply SNMPv3 privacy/
encryption. To do this using the algorithm types of TDES, AES128, or, for
US customers only, AES192 and AES256, your ProVision system
requires:
* A specific ProVision feature license.
* A Java cryptography extension (JCE unlimited strength jurisdiction
policy file/s) from Sun Microsystems.
Contact your Harris Stratex representative to obtain this license and this
extension.
Prerequisite
To do this, you need access to both ProVision and WebCIT, the TRuepoint craft tool,
for the TRuepoint devices.
For each TRuepoint device you are deploying in ProVision, you must find that device in
WebCIT and set up ProVision’s IP address as the manager of that device. This is
required to manage a TRuepoint device from ProVision. See the Procedure below for
specific instructions.
Procedure
1. Identify and record the IP address of your installation of ProVision. See
Determining the Server’s IP Address in the Installation and Administration
Manual for complete instructions.
2. Identify all the TRuepoint devices you want to deploy in ProVision.
3. Log into WebCIT. For each TRuepoint device noted in step 2:
• Go to the Provisioning screen, in Network Setting 2.
• Set the value SNMP Manager to the ProVision IP address identified in step 1. See
the WebCIT Operator manual for further details.
• Save the changes.
4. Once steps 2 and 3 are completed for each TRuepoint device, log into ProVision.
5. Identify the IP addresses for connecting TRuepoint devices to ProVision via a

ProVision trap and a ProVision SNMP manager.

Deployment window displays. Select the TRuepoint icon. The TRuepoint device
options are displayed.
7. Select the TRuepoint device that you require. Enter the values for it as follows:
TRuepoint 4000, 4040, and 6400

• Ensure the correct parent displays; the device
is placed under the parent listed.
• In the Name field, type a descriptive name for
the TRuepoint device. It is labeled with this
name in the User Interface.
• Enter the IP address.
• The Read Community string has the default
value. Only change it if the radio setting has
been changed.
• The Read and Write Community strings must
match the strings entered into the radio.
• To have ProVision start managing this radio,
select the Manage checkbox.
• Select Deploy. The Deploying TRuepoint

results window displays.
Click Close. The radio is now deployed.
TRuepoint 4040 v2, 5000, and 5000 2+0
Click Next.
• Select the SNMP Version. If you select Version

v2c, the Read and Write Community options
display.
• The Read and Write Community strings must
614-330055-001 July 2009 3-19

• If you select Version v3 for the SNMP version,

further options display.
• If required, check the box to Use Inherited
Security Account from the parent container.
• Enter a Username. This is associated with the

two passwords below.
• Authentication: This selects the algorithm used
for this device’s data. Select a Type, and enter
a Password and a Confirmation for the password.
• Privacy: This selects the encryption algorithm
used for this device’s data. Select a Type,
enter a Password and a Confirmation for the
password.
Note: The Authentication and Privacy types are
determined by your organization’s network policy.
An Authentication of MD5 and a Privacy of AES128
is a common “strong security” combination.
Note: To change or view SNMPv3 credentials on a
TRuepoint radio, see the TRuepoint 5000/4040
Operator’s Interface Manual, IMN-903003-E07.
There are two ways to change these credentials.
One is using WebCIT, logging in as the
administrator user and setting the authentication
and privacy passwords. The other way is using
third-party SNMP tools, such as MGSoft and
NetSNMP.
Click Deploy. The TRuepoint radio is now deployed.
8. For 4040, 5000, and 6400 radios, there is an extra step. After you have deployed
all the required radios, select them in the Tree Viewer. In the menu bar, go to the
Configuration menu and select Configuration Profile.
9. In the Configuration Profiles screen, select the TRuepoint 6400/5000/4000/4040
Managers option for the TRuepoint radio type. Enable the option and enter the
SNMP manager IP address; this is the ProVision IP address identified in Step 1.
10. Select the TRuepoint 6400/5000/4000/4040Trap Destination option for the TRuepoint
radio type you have deployed. Enable the option and enter the trap destination IP

address; this is the same as the SNMP manager IP address in step 9.
11. Save and apply the Configuration Profile settings, as documented in Configuration
Profile Settings for Bulk Configuration on page 3-75.
12. The TRuepoint devices are now fully deployed and managed from ProVision.
TRuepoint 6400 requires an additional procedure to enable its alarm

resynchronization; see Configure TRuepoint 6400 Alarm Resynchronization on
page 4-16.
When a TRuepoint device is fully deployed, ProVision captures all of its IP

addresses. This provides support for redundant NMS connections, as
shown in this diagram below:
Related Topics:
• Configuration Profile Settings for Bulk Configuration on page 3-75
• Configure TRuepoint 6400 Alarm Resynchronization on page 4-16
614-330055-001 July 2009 3-21

TRuepoint 6500 Device Deployment

Introduction
You can deploy and manage TRuepoint 6500 devices in ProVision. In ProVision,
TRuepoint 6500 devices differ from other TRuepoint devices. They have a unique
Performance History display; their event collection is trap-based; and their alarms are
synchronized automatically after state changes. More information is included
throughout this documentation, particularly for Managing SMA and DXR Devices on
page 3-57.
There are two types of TRuepoint 6500 devices:
Type Definition Tree Viewer Display
Standard Standard TRuepoint

6500 radio.
Double This type includes 2

Terminal supervisory terminal
units.
The procedure below is an overview of the required process. It describes how to deploy
TRuepoint 6500 and TRuepoint 6500 double terminal devices. For more information,
read Standard SNMP Device Deployment on page 3-11.
Prerequisite
For each TRuepoint device you are deploying in ProVision, you must find that device in
WebCIT and set up ProVision’s IP address as the manager of that device. This is
required to manage a TRuepoint device from ProVision. This setting is found in
WebCIT via the Provisioning screen, in Network Setting 2, as the value SNMP Manager
#1. See the WebCIT Operator manual for further details.

Procedure
1. Identify the IP addresses for connecting TRuepoint devices to ProVision via a
ProVision trap and a ProVision SNMP manager.
Deployment window displays. Select the TRuepoint icon. The TRuepoint device
options are displayed.
3. Select the TRuepoint 6500 device that you require, Standard or Double Terminal.
Enter the values for it as follows:
TRuePoint 6500

been changed.
The Read and Write Community strings must
• Select Deploy. The Deploying TRuepoint results
window displays.
• Click Close. The TRuepoint radio is now
deployed.
614-330055-001 July 2009 3-23

TRuepoint 6500 Double Terminal

been changed.
• For each of the two terminals, enter the IP
addresses.
• Select Deploy. The Deploying TRuepoint results
window displays.
Click Close. The TRuepoint radio is now deployed.
4. After you have deployed the TRuepoint 6500 radio, ProVision immediately
discovers the device configuration and presents the discovered plug-ins. This is
done automatically, as a background task. The terminals display in the Tree Viewer,
with the discovered plug-ins displaying as child objects in the Tree Viewer.
5. The TRuepoint devices are now fully deployed and managed from ProVision.
Related Topics:
• TRuepoint Device Deployment on page 3-18
• Manually Discovering TRuepoint 6500 Configuration on page 3-55

Constellation Device Deployment

Introduction
Constellation devices are deployed using the standard Deployment procedure in
ProVision. After they are deployed, a Constellation discovery agent identifies the
radios, and notes their type. There are two types of Constellation radio:
Type Definition Tree Viewer Display
Terminals Terminals have one link. They can

be protected or unprotected.
Protected link =
Unprotected link =
Repeaters Repeaters have two links. They

can have both links protected,
both links unprotected, or they can
have one link protected and one
link unprotected.
The procedure below is an overview of the Constellation deployment process. Read

Standard SNMP Device Deployment on page 3-11 for full details.
Constellation for FarScan is deployed in ProVision with limited

functionality. It does not have the following:
* Performance data collection (resulting in no performance thresholds or
trends recorded)
* Network Health Report
* Full functionality for the Inventory Report, Diagnostic Controls, and
Configuration Viewer
Performance data collection for Constellation is only supported for the
following variants: 3DS3, 4DS3, and 155mbit.
Prerequisite
For each Constellation device you are deploying in ProVision, you must find that device
in FarScan and set up ProVision’s IP address as the manager of that device. This is
required to manage a Constellation device from ProVision. See the FarScan User
manual for further details.
Procedure
1. Identify the IP addresses for the Constellation radios.
Deployment window displays. Select the Other Microwave icon. The Constellation
614-330055-001 July 2009 3-25

device option is displayed.
3. Select the Constellation option. The Deploying Constellation screen displays. Enter
the values for a Constellation radio, as follows:.
1. Ensure the correct parent displays; the

device is placed under the parent listed.
2. In the Name field, type a descriptive name
for the Constellation device. It is labeled
with this name in the User Interface.
4. The Read Community string has the default
value. Only change it if the radio setting
has been changed.
The Read and Write Community strings
must match the strings entered into the
radio.
5. To have ProVision start managing this
radio, select the Manage checkbox.
6. After you have deployed all the required Constellation devices, the Constellation
discovery agent automatically identifies the devices. Click on the devices in the Tree
Viewer. The devices should display with their links and their protected/
unprotected status.
7. The Constellation devices are now fully deployed and managed from ProVision.
When a Constellation device is fully deployed, ProVision captures all of its

IP addresses. This provides support for redundant NMS connections.
Related Topics:
• CAU (Control Alarm Unit) Deployment on page 3-27

CAU (Control Alarm Unit) Deployment

Introduction
A Control Alarm Unit (CAU) is a site management unit providing alarm/status inputs
for monitoring devices. It can provide remote command outputs for controlling
devices. The communication ports on the CAU carry controls and inputs to the
connected devices. The CAU is normally used with TRuepoint and MicroStar radios, to
connect them to transmission equipment that is not directly compatible with HSX
standards.
The CAU is configured and installed using instructions in the CAU -

Control Alarm Unit Instruction Manual, P/N IMN-099945-E06, provided
with the CAU.
Prerequisite
For each CAU you are deploying in ProVision, you must find that device in FarScan and
set up ProVision’s IP address as the manager of that device. This is required to manage
a CAU from ProVision. See the FarScan Operator manual for further details.
Procedure
1. Identify the IP addresses for connecting the CAUs.
Deployment window displays. Select the Other Microwave icon. The Other
Microwave device options are displayed.
3. Select the CAU device option.
4. The Deploying CAU screen displays. Enter the values for a CAU, as follows:.
1. Ensure the correct parent displays; the

device is placed under the parent listed.
2. In the Name field, type a descriptive name
for the CAU device. It is labeled with this
4. The Read Community string has the default
value. Only change it if the radio setting
has been changed. The Read and Write
Community strings must match the strings
entered into the radio.
5. To have ProVision start managing this
radio, select the Manage checkbox.
6. The CAU and its status can now be viewed from ProVision.
614-330055-001 July 2009 3-27

Related Topics:
Configuration Profiles for Bulk Configuration on page 3-72

Generic Device Deployment

Generic devices can be SNMP or IP based, non-HSX devices. This allows you to deploy
required devices, either as SNMP or IP devices, provided they are SNMP/IP compliant.
ProVision also presence polls them, using either an SNMP or an ICMP ping.
The generic devices are categorized in ProVision as:
• Generic Devices
• Multiplexer
• Router
• Switch
• Microwave Radio
• Power Supply
• Alarm Unit
• Base Station
To create a generic device, you enter both standard deployment details

and a Support Package name. The Support Package name helps
ProVision to manage types of devices. Similar or related devices can be
grouped in the same Support Package.
If a Generic Device is an IP device, its support is limited at this time to

being presence polled.
When you deploy a generic device, you, or an advanced-level user, must

also set up the generic device event collection. This function requires an
additional ProVision module license. This is documented in the
Installation and Administration Guide. If you are working with an
advanced-level user to deploy generic devices, please provide them
with all the device details: name, type, IP address, and Browser and
Telnet port settings.
You can customize event names for CAU events. For more information,
see the ProVision Installation and Administration Guide.
614-330055-001 July 2009 3-29

Procedure
Device Deployment Windows Steps
1. Select the Generic Device Type that best describes

the device. Then, click Next.
2. Enter the values for the device in this screen, as

follows:
• Ensure the correct parent displays; the device is
• Press the Tab key and type in the device’s IP
address.
• The Browser and Telnet Port settings are the
default, only change these if required.
• Select the Communications type for the device,
SNMP or IP.
• To have ProVision start managing the device,
3. Click Next.
Note: For steps 4 through 6, the Generic Device module

license is required.
4. For an SNMP Device only, assign the Read
Community and Write Community strings, and the
SNMP Version. The Read Community string has the
default value. Only change it if the radio setting has
been changed. The Read Community strings must
5. Assign a Support Package name to the new device.
Select a Support Package from the Package
drop-down menu, or enter a Support Package
name in the New Package Name field.
Note: If you enter a new Support Package name, it is
saved and available for other generic devices in the
Package drop-down menu.
Warning: If you select an existing Support Package, it needs to
match the device Communication type, SNMP or IP.
6. Click Deploy. The new device is deployed.
Related Topics:

WiMAX Device Deployment

Introduction
ProVision supports the following WiMAX devices:
Type Definition
StarMAX 6100 BS StarMAX 6100 WiMAX base station.
StarMAX 6400 BS StarMAX 6400 WiMAX base station blade; each 6400
blade contains up to 4 blades, and each blade has its own IP
address and is managed as a separate device.
WiChorus SmartCore WiChorus SmartCore ASN-GW and Home Agent device.

ASN-GW
WSC ASN-GW WSC ASN-GW Controller, linking multiple base stations.

Controller
WiMAX Subscriber WiMAX Subscriber Stations. Only VIP subscriber stations

should be deployed as objects.
WiMAX devices are deployed using the standard Deployment procedure in ProVision.
After they are deployed, for StarMAX 6100 and 6400, you can test the connectivity of
the related subscriber stations.
In addition, Administrator-level users can auto-discover and deploy

StarMAX base stations with Network Auto-Discovery. See Network
Auto-Discovery for Eclipse and WiMAX BS Devices on page 3-42.
About Deploying Subscriber Stations

When you are deploying subscriber stations into ProVision, we recommend that you
only deploy VIP subscriber stations (i.e., those providing services to a company). This
is because a network can have many WiMAX subscriber stations in a network, and each
device deployed in ProVision contributes a loading on the ProVision server.
All subscriber stations are provided with a level of management through the associated
base station objects (see WiMAX Subscriber Station Connectivity on page 5-48).
Deployment provides the following additional management for VIP subscriber
stations:
• Visibility of the devices in the standard network map and tree views
• Presence polling and associated ‘loss of comms’ event reporting
• User standard operations such as Search to identify deployed devices
The procedure below is an overview of the WiMAX deployment process. See Standard
SNMP Device Deployment on page 3-11 for full details.
Procedure
1. Identify the IP addresses for the WiMAX devices.
614-330055-001 July 2009 3-31

2. For any Subscriber stations, identify the MAC addresses.

Deployment window displays. Select the WiMAX icon. The WiMAX options are
displayed.
4. Select the required WiMAX option. The Deploying screen displays. Enter the values
for the WiMAX device as follows:.
StarMAX 6100, StarMAX 6400, SmartCore

ASN-GW/Home Agent, WSC ASN-GW
Controller
1. Ensure the correct parent displays; the device
2. In the Name field, type a name for the device.
It is labeled with this name in the User
Interface.
4. To have ProVision start managing this device,
WiMAX Subscriber
1. Ensure the correct parent displays; the device
2. In the Name field, type a name for the device.
It is labeled with this name in the User
Interface.
4. Enter the MAC address.
5. To have ProVision start managing this device,
6. Click on the devices in the Tree Viewer. The devices should display with their links
and their protected/unprotected status.
7. The WiMAX devices are now fully deployed and managed from ProVision.
Related Topics:
• Equipment Views on page 2-39
• WiMAX Subscriber Station Connectivity on page 5-48
• Network Auto-Discovery for Eclipse and WiMAX BS Devices on page 3-42

EfficientSite Manager Deployment

The Harris Stratex EfficientSite Manager is an intelligent controller based system. It
reduces the energy costs associated with operating telecommunications sites. The
EfficientSite Manager is supported by ProVision through a rich set of Fault,
Configuration, and Performance management features.
EfficientSite Manager devices are deployed in ProVision using the following procedure:
Procedure
1. Identify the IP addresses for the EfficientSite Manager.
Deployment window displays. Select the Energy icon. The Energy options are
displayed.
3. Select the EfficientSite Manager. Enter the values for it as follows:
Efficient Site Manager

device. It is labeled with this name in the User
Interface.
3. Enter the device’s IP address.
4. To have ProVision link to the site manager, select the
Manage checkbox.
5. Click Next.
6. Ignore the SNMP options; accept the defaults and

click Deploy.
7. When an EfficientSite Manager is deployed within ProVision, the device displays in

the Tree Viewer, and can be opened and viewed.
8. For information on the EfficientSite Manager screen, see the EfficientSite Manager
System on page 5-98.
614-330055-001 July 2009 3-33

TNet Device Deployment

Introduction
TNet devices communicate with a TNet Proxy using TNet protocol over TNet cabling.
The TNet Proxy communicates with ProVision using SNMP over ethernet. Due to
performance issues it is recommended that no more than 500 TNet devices are
allocated to a single TNet Proxy. ProVision supports up to 3000 TNet devices.
When an event occurs on a TNet device, an SNMP event is sent by the TNet Proxy to
ProVision.
Within ProVision, TNet devices are typically deployed under the location (region, site
or rack) at which they are physically deployed. This is not necessarily the same location
at which the TNet Proxy is deployed, as shown in the following screen.
You can view Proxy, subnets, and TNet device configurations via the Proxy
Configuration Manager. See Viewing/Changing TNet Proxy Configurations on
page 3-81.
About TNet Proxies

A TNet Proxy is a dedicated Windows NT Server connected to the ProVision server over
a LAN. The TNet Proxies communicate with ProVision using SNMP.
TNet Proxies communicate with managed TNet devices through a serial interface,
either directly or through a terminal server. A TNet Proxy converts SNMP requests
from ProVision to the TNet protocol to communicate with the TNet devices.
This is an overview of how ProVision interacts with the TNet Proxies and the TNet
devices.

Figure 3-2. ProVision and a TNet Network
Procedure
You must deploy the TNet Proxy before you deploy a TNet device,
because part of the device deployment process involves selecting
a TNet Proxy.
1. Within the Tree Viewer, right-click an existing container, for example, the network
icon and select Deploy Object. The Deployment window displays.
614-330055-001 July 2009 3-35

2. Select the TNet icon. The TNet devices are displayed.
3. Select the required device icon.

5. Select Deploy.
TNet Deployment Troubleshooting

The table below lists the TNet device deployment/management problems that can
occur between ProVision and the TNet Proxy, and the suggested solutions.
Table 3-3. ProVision and TNet Proxy - Device Deployment Discrepancies
Deployment Solution
Discrepancy
Radio deployed in See Manually Deploying a TNet Device into the

ProVision but not Proxy on page 3-38.
deployed in the Proxy.
Wrong radio type in 1. Delete the radio from ProVision.

either ProVision or the This also deletes the radio from the Proxy. See
Proxy. Deleting a Device on page 3-50
2. Deploy and manage the radio in ProVision.
The radio is automatically deployed into the
Proxy.
Radio deployed in the 1. Deploy and manage the radio in ProVision.

Proxy but not deployed 2. Delete the radio from ProVision.
in ProVision, and the
This also deletes the radio from the Proxy.
radio is not required.

Table 3-4. Device Deployment Details for TNet Devices
TNet Proxy
Note: ProVision can manage up to ten TNet Proxies. Each
proxy can support up to 16 radio subnets (0 to 15).
TNet Proxy. The TNet Proxy is labeled with this
3. Press the Tab key and type in the TNet Proxy’s IP
address.
5. Enter the total number of Subnets for this proxy.
6. To have ProVision start managing the TNet Proxy,
All Other TNet Devices

radio. The device is labeled with this name in the
User Interface.
3. Press the Tab key and type in the subnet number
(Subnet #). The valid range is 0 - 15.
Note: For all TNet radios other than Spectrum II the valid
radio address range is 0 - 223. For Spectrum II
radios the valid radio address range is 256 - 1279.
4. Press the Tab key and type in the radio address.
5. To have ProVision start managing the TNet device,
6. Select Next. The Proxy List displays.
614-330055-001 July 2009 3-37

7. Select a TNet Proxy from the list displayed.

8. Select Deploy.
9. The Deploying <device name> results window
displays.
10.To close the Deploying <device name> window,
select Close.
Manually Deploying a TNet Device into the Proxy

When a TNet device is deployed and managed in ProVision, the radio data including
the radio subnet, address and type is written to the TNet Proxy. In certain
circumstances data is not written to the Proxy, for example, when you are deploying a
TNet device and communications are lost between ProVision and the Proxy. As a result,
the TNet device displays in ProVision in the connecting state because the device
details were not written to the Proxy database.
You can confirm whether or not the TNet device details have been written to the Proxy,
via the Proxy Viewer. See Using the TNet Proxy Viewer on page 3-83 for more
information. If the TNet device is not listed in the Proxy database, you can manually
deploy the TNet device into the Proxy.
To manually deploy a TNet device into the Proxy:
1. Right-click the TNet device. In the right-click menu, select Deploy into Proxy.
2. The TNet device details stored in ProVision, are written into the Proxy database.
Related Topics:

DXR 200 and DXR SMA Device Deployment

DXR 200 is a legacy device. To view information about DXR 200 in ProVision, they
must be managed with an SMA. DXR 200 devices communicate through an SMA
Proxy. When an event occurs on a DXR device:
• The DXR device communicates with the SMA.
• Then, the SMA sends an SNMP event to ProVision over ethernet.
DXR 200 devices must be communicating with their SMA to send data to ProVision. If
the DXR cannot connect to an SMA, ProVision will not receive data from the DXR.
Up to 4 DXR devices can be directly connected to one SMA. However, a DXR can be
connected to a network of up to 255 other DXRs.
You can view SMA device configurations via the Configuration Manager and the
Management Viewer.
Because DXR 200 is a legacy device, limited information is available through
ProVision. The available ProVision functions for DXR 200 devices are: Presence
Polling, Event Collection, and Configuration Viewer. Configuration Viewer is especially
useful for the DXR slot configuration.
The DXR SMA provides the network communications for the DXR 700 radios. When
you deploy a DXR SMA you also have the option to discover the connected DXR
terminals.
The figure below shows a DXR SMA deployed in ProVision. This example is not yet
Managed, and its DXR 700 terminals are not discovered.
A DXR SMA can have a maximum of four DXR 700s connected.
Figure 3-3. DXR SMA radio deployed in ProVision, but not Managed
Procedure
You must deploy the SMA before you deploy a DXR device,
because part of the device deployment process involves selecting
an SMA.
To deploy an SMA device, and link it to DXR 200 devices, do the following:
614-330055-001 July 2009 3-39

Deployment window displays.
2. Select the DXR icon. The DXR device options are displayed.
3. Select the DXR SMA device icon.
The Deploying DXR SMA window displays.
• Check the Parent field. Ensure the correct

parent displays in this field. The device is
the radio.The radio displays with this name.
• Press the Tab key and type in the radio’s IP
address.
• To have the SMA discover its DXR terminals,
select Discover DXR Terminals.
• To have ProVision start managing the radio,
• Click Next. Then, on the window that displays,
select Deploy. The Deploying SMA results
window displays.
• Select Close.
4. After you have created the SMA, you are ready to set up the DXR 200 devices.
5. In the Tree Viewer, go to the container that includes the SMA. Right-click it and
select Deploy Object.
6. The Deployment window displays. Again, click on the DXR icon. In the DXR Family

screen, and select DXR 200.

The Deploying DXR 200 window displays.

the radio.The radio is labeled with this name in
the User Interface.
• Press the Tab key and type in the radio’s
Network Port, which will be one of the values A
through D on the SMA.
• Enter the Terminal Number of the DXR terminal.
• To have ProVision start managing the radio,
• Click Next. Select Deploy. The Deploying DXR
200 results window displays.
• Select Close.
• The Proxy List displays. Select the DXR SMA

that will be the proxy for this DXR 200.
7. Select Deploy. The Deploying DXR 200 results window displays.

8. Click Close. The DXR 200 is now deployed.
Related Topics:
• Manually Discovering DXR 700 Radios on page 3-56
• Managing SMA and DXR Devices on page 3-57
614-330055-001 July 2009 3-41

Network Auto-Discovery for Eclipse and WiMAX BS

Devices
Introduction
Network Auto-Discovery is a ProVision task that polls a range of IP addresses for
Eclipse or WiMAX base station (BS) devices. When you run Network Auto-Discovery,
you tell ProVision which IP address ranges to search. ProVision polls the IP addresses
and captures any discovered devices in containers in ProVision. This is a fast way to
deploy Eclipse and WiMAX base station devices, especially when applying ProVision to
an existing network.
Note that:
• Discovered devices are named with the class name of the device and the
device-specific IP address.
• Users can edit the device data of all discovered devices.
• ProVision only deploys the discovered objects into the specified Container. If a
Container specified for auto-discovery does not exist, ProVision will create it.
• You can review the auto-deployment results and note any errors.
Procedure
1. Log into ProVision as an NOC Engineer or Administrator.
2. In the Configuration menu, select Network Auto-Discovery. The Network
Auto-Discovery screen displays.
3. To enable Network Auto-Discovery, you need to enter an IP address range. You

must enter at least one IP address range; you can enter multiple ones. ProVision
will search for all Eclipse or StarMAX devices in the IP address ranges. To do this:

• Click Add. The Add IP Range fields display. Enter values for:
IP Address Range - Enter the start and end of the IP address range.
Read Community - Enter public or private.
Container Name - Enter a unique Container name. All the discovered devices for
this IP address range will be deployed in this container, just below the PV/Root
level in the Physical Tree view.
If required, check the Manage on Deployment check box. The discovered devices
will be deployed in a Managed state.
• Click Add IP Range.
4. The IP Address range is added to the Discovery Ranges list.
5. Repeat steps 3 and 4 as required for each IP address range. To remove an IP range,
select it and click Remove. To change an entered IP address range, select it and click
Edit. The IP range displays for editing:
6. To run the network Auto-Discovery, click Start Task.

7. The Task Manager displays the network Auto-Discovery in progress.
ProVision will run the auto-discovery on up to 5 IP address ranges at one

time. All remaining ranges will be queued and run as tasks.
8. When the network Auto-Discovery is complete:
614-330055-001 July 2009 3-43

• The new Container is created, and holds any discovered devices.

• The results and errors of the network Auto-Discovery process can be viewed by
right-clicking on each IP address range in the Task Manager. See below for more
information.
Network Auto-Discovery Results and Error Messages

You can view the results and errors of the network auto-discovery process. There are
four main result messages:
• Object at address <####> successfully deployed - An object was found and deployed.
• Object not detected at address <####>- Nothing at this IP address is responding to the
SNMP request; no object was found or deployed.
• Object detected at address <####> but unable to find matching class - An object was
found: however, ProVision is unable to identify the object type. This means the
identified object is not supported by auto-discovery at this time.
• Any message highlighted in red - A red highlight in the auto-discovery results warns
you that an object has been deployed previously in ProVision as the wrong class type
(for example, deployed as IDU but auto-discovery detects it as an INUe.) You must
either delete or redeploy the device.
• Example of Eclipse auto-discovery results:

• Example of StarMAX auto-discovery results:
614-330055-001 July 2009 3-45

Troubleshooting Device Deployment

When you deploy a device, you may receive the following error messages:
Exception Corrective Action
IP Address Already Allocated Select OK.

If you attempt to assign an IP address that The Deploying <device name>
has already been allocated to a device the window displays enabling you to
following message displays: re-enter the correct IP address.
Invalid IP Address Select OK and re-enter a valid IP

address.
If you enter an invalid IP address the
following message displays:
Related Topics:
• About Deploying and Managing Devices on page 3-2
• Deploying Devices on page 3-6

Changing a Device’s Container

Introduction
If you have deployed a device under the wrong container and want to move it to a
different container, you can reparent the device in the Tree Viewer.
If you change the device’s container, you must reposition the object in the Map Viewer.
For more information, see Moving Containers and Devices in the Map Viewer on
page 3-48.
Container and device objects are reparented in the Tree Viewer physical
pane.
Reparenting a TNet device within the Tree Viewer is exactly the same as
for other objects. However, reparenting TNet devices to a different TNet
Proxy is a different procedure. See Viewing/Changing TNet Proxy
Configurations on page 3-81.
Procedure
To change the container for a device in the Tree Viewer physical pane:
1. To unlock the tree, select the locked icon, located on the physical pane’s title bar.
2. Select the device to be moved to a different container.

3. Drag and drop the device into the required container.
The device has been reparented and displays under the new container in the Tree
and Map Viewers.
4. To lock the tree, select the unlocked icon.
Related Topics:
614-330055-001 July 2009 3-47

Moving Containers and Devices in the Map Viewer

Introduction
You may want to reposition container objects and/or devices in the Map Viewer. You
can do this, if you have enough user access. For more information see Map Viewer on
page 2-31.
If you move a linked device to another position on the map, the link
moves with the radio.
Moving an object on one map view, for example, the flat view, does not
effect the positioning of the object on the other layer.
Procedure
To reposition objects in the Map Viewer:
1. To unlock the map, select the locked icon.
2. To move an object, in the Map Viewer, select the desired object and drag it to the
new position.
3. To relock the map, select the unlocked icon.
Related Topics:

Renaming a Device
Introduction
You can change device names for devices in ProVision.
Procedure
To rename a device:
1. Right-click the device to be changed. The device’s right-click menu displays.
2. Select Rename on the right-click menu.
The Rename Object window with the selected device’s name displays.
3. Make the required changes to the device’s name.

Related Topics:
614-330055-001 July 2009 3-49

Deleting a Device
Introduction
There are three reasons to delete a device from ProVision:
• A device was accidentally deployed in the wrong region or site.
• The radio has been decommissioned or replaced with a different radio type.
• The radio is no longer being managed by ProVision.
You can delete a device from the Tree Viewer or the Map Viewer. When the device is
deleted the Tree and Map Viewers refresh and the device is no longer displayed.
Deleting a device in ProVision has no effect on the traffic carrying

capability of the device, but event generation is disabled in the device.
You cannot directly delete a DXR 700 radio. You have to select the DXR
SMA option to Discover Terminals. For more information see Manually
Discovering DXR 700 Radios on page 3-56.
WARNING: Be careful when deleting a TNet Proxy, as this also

deletes all the associated child TNet radios in ProVision, and
deletes the Proxy’s database.
Procedure
To delete a device in ProVision:
1. Right-click the device’s icon. The right-click menu displays
2. Select Delete on the right-click menu. A Delete Objects window displays.
3. To delete the selected device, select Yes.
Related Topics:

Managing Devices
This section covers the following device management procedures:

• Unmanaging a Device on page 3-54
• Manually Discovering TRuepoint 6500 Configuration on page 3-55
• Manually Discovering DXR 700 Radios on page 3-56
Managing a Device
Introduction
When you activate Managed status for a device in ProVision, ProVision initiates
presence polling of the device. Then, an informational event is added to the ProVision
event log, noting the radio has been commissioned successfully.
Typically, in ProVision you manage the radio, and then link it to another radio. For a
pre-deployment radio, you create the links first, and then manage the radio.
Important: This process is not applicable for Eclipse Node and DXR 700
radios.
A ProVision managed device that has not yet been installed and
commissioned at the site is shown in ProVision with the connecting icon
.
Procedure
To activate Managed status for a single device:
1. Right-click the device to be managed. The device’s right-click menu displays.
2. Select Manage. ProVision changes the device to a Managed state. A check displays
beside Managed in the right-click menu, showing that the device is Managed.
To set the Managed status of two or more devices:

1. Select the device icons for all the required radios. Then, right-click.
2. If all the devices have the same Managed status, Manage displays in the right-click
menu.
614-330055-001 July 2009 3-51

3. If some devices are set to Managed and some are not, the right-click menu displays
as follows:
4. Set the status to Managed or Unmanaged for the devices. The status that you choose
is applied to all the devices.
Related Topics:
Verifying ProVision is Receiving Device Events

Introduction
When a device is Managed, this enables event traffic between ProVision and the device.
You can verify that ProVision is receiving events from the device by:
• Adjusting Event filtering to display all events received from a device: or
• By causing an alarm to be raised by the radio.
If ProVision is not receiving events from a device, check that the device’s IP address is
correct. The device’s IP address displays in pop-up text when you place the cursor over
the device’s icon in the Tree or Map Viewer. If the IP address is incorrect, you can
change it. See Viewing/Changing Network IP Addresses on page 3-80.
Procedure
To verify that ProVision is receiving events from a device:
1. Right-click the managed device.
2. From the right-click menu, select Event Browser.
The Event Browser displays.

3. Select the View Filters icon.
The Filters window displays.
4. Enable both States, Active and Closed. Enable all the Severity types.
5. Select OK.
If ProVision is receiving events from the radio, these events are displayed in the
Event Browser window.
6. To close the Event Browser window, select the X in the upper right corner.
7. To confirm you do not want to save the changes, select No.
Related Topics:
614-330055-001 July 2009 3-53

Unmanaging a Device
Introduction
When a device is Managed, ProVision polls and monitors the device, and the device
sends events to ProVision. In certain situations you may not want to monitor one or
more devices on the network. For example, a device might be installed in a remote
location where a concert is held on an annual basis. During the concert you would
manage the device in ProVision, and for the remainder of the year you would leave the
device in an un-managed state.
When you un-manage a device in ProVision, the following occurs:
• The device’s event status changes to blue in the Tree Viewer. A blue object balloon
displays in the Map Viewer.
• For DXR SMAs, the connected DXR 700s are also un-managed.
• The device’s event history and performance data are not displayed until the device is
remanaged.
• An unmanaged informational event is added to the ProVision event log.
• ProVision stops presence polling the device.
• Event generation is disabled in the device.
Where a field technician is working on a device that may generate

a large number of faults you must “sleep the device” rather than
unmanaging it. For more information see Sleep Status for a Device on
page 4-20.
Procedure
To un-manage a device:
1. Right-click the device to be un-managed. In the right-click menu, deselect the
Managed checkbox.
The device is changed to an unmanaged state, and is no longer polled by ProVision.
Related Topics:

Manually Discovering TRuepoint 6500 Configuration

Introduction
In ProVision, when you manage a TRuepoint 6500, you have the option of discovering
the radio’s configurations.
When ProVision discovers a TRuepoint 6500, it communicates with the radio and
identifies its plug-ins. The plug-ins are then noted and displayed in ProVision, as
shown below in a sample Tree View of a TRuepoint 6500.
If a TRuepoint 6500 is changed, e.g., one of its plug-ins is removed, a warning Event is
raised for the radio in ProVision, “Device Configuration Changed”. You need to
compare this to related events. If it shows that this is due to a plug-in failure, take steps
to fix this. If the event was raised when a device was configured to add or remove
plug-ins, you need to rediscover the plug-ins, using the procedure below.
Procedure
To manually discover TRuepoint 6500 configurations:
1. In the Tree or Map Viewer, right-click the required TRuepoint 6500 radio. In the
right-click menu, select Discover Configuration.
2. The TRuepoint 6500 is updated to reflect any new connections or any changes that
were discovered. Any changes display in the Tree Viewer.
Related Topics:
614-330055-001 July 2009 3-55

Manually Discovering DXR 700 Radios

Introduction
In ProVision, when you manage a DXR SMA, you have the option of discovering the
connected DXR 700 radios.
You can also manually discover DXR 700 radios in the following situations:
• Where the discover option was not enabled when the DXR SMA was managed in
ProVision, because the radio had not been commissioned.
• Where you are getting unusual responses, you may discover the radios to see if the
radios have been changed, that is, swapped ports.
• To delete a DXR 700 radio from ProVision where a DXR 700 radio has been
physically removed from the network.
Procedure
To manually discover DXR 700 radios:
1. In the Tree or Map Viewer, right-click the required DXR SMA. In the right-click
menu, select Discover Terminals.
2. The user interface is updated to reflect any new DXR 700 radios or any changes that
were discovered.
Related Topics:

Managing SMA and DXR Devices

Introduction
As described in DXR 200 and DXR SMA Device Deployment on page 3-39, DXR 200
is a legacy device. To communicate with ProVision, DXR 200 devices must be
connected to an SMA Proxy. It is the SMA proxy that communicates with ProVision via
ethernet.
To manage an SMA and its DXR 200 devices, you need to ensure that the ProVision
configuration of the DXR radios matches the DXR 200 radios actually configured by an
SMA. The DXR 200 radios must be identified and configured correctly. To do this:
1. Check the status of the DXR 200 radios for an SMA using the Management Viewer
screen.
2. Make any corrections to the configuration of the SMA or DXR 200 radios using the
Management Configuration screen.
DXR 200 radios are set up outside of ProVision. When you create a new
DXR 200 for an SMA, it should be based on the DXR radios that are
physically connected to the SMA. Use the “Discover Terminals” function
to identify these radios.
Procedure
To manage SMA and DXR radios:
1. In the Tree or Map Viewer, right-click the required DXR SMA. In the right-click
menu, select Discover Terminals.
2. Right-click the DXR SMA again and select Management Viewer.
3. The Management Viewer screen displays.
4. The Management Viewer displays data about all the DXR 200 radios contained by
an SMA. This includes the network port, terminal number, status, and ProVision
name. Note the following:
• Radios highlighted in orange need to be deployed or otherwise corrected in
ProVision.
• Radios with a Status of “Not Present” are not physically connected to the SMA.
Radios with a Status of “Deployed” are physically connected to the SMA.
• Radios deployed correctly in ProVision are displayed in white.
614-330055-001 July 2009 3-57

5. If you need to correct the configuration for an existing DXR 200 radio, right-click
its DXR SMA and view the right-click menu. Select Management Configuration.
6. The Management Configuration screen displays.
7. The Management Configuration screen displays all the SMAs. In a tree viewer, it
shows which DXR 200 radios connect to which SMAs.
8. To check the configuration parameters for an SMA or a DXR 200, click on it in the
tree viewer. The configuration values display. For an SMA, you can edit the Name.
For a DXR 200, you can edit the Name, Network Port, and Terminal Number. Click
on Commit Changes to save changes.
9. Select Close to close this screen.
10. If you make any changes, open the Management Viewer again to ensure that any
changes to DXR 200s have been successful.
Related Topics:
• DXR 200 and DXR SMA Device Deployment on page 3-39

RF Linking Procedures
A Radio Frequency (RF) link is added between radios, in ProVision, to show that the
radios are carrying communications traffic. You can only create an RF link between
HSX radios of the same type, for example, Altium MX to Altium MX, protected XP4
248x to protected XP4 248x.
To create an RF link between two radios, the radios must be deployed in ProVision.
By creating an RF link between two radios in ProVision, you are able to see the
complete link, viewing both ends. In the Map Viewer or submap, the highest severity
event from either radio is reflected in the color of the link. For more information see
Event Severity Color Coding on page 2-57.
This section covers the RF linking procedures:
• Creating an RF Link from the Tree Viewer on page 3-60
• Creating an RF Link from the Find Function on page 3-61
• Deleting an RF Link on page 3-65
• Verifying an Eclipse or TRuepoint RF Link on page 3-64
RF links are automatically discovered for Eclipse radios.
614-330055-001 July 2009 3-59

Creating an RF Link from the Tree Viewer
Introduction
From the Tree Viewer, you can select and link two radios. To link two Eclipse radios,
instead of selecting the specific radios, select the link objects for those radios.
To create an RF link from the Find screen, see Creating an RF Link from the
Find Function on page 3-61.
Procedure
To create an RF link between SNMP radios:
1. In the Tree Viewer, locate the two radios to be linked. You may want to check to see
if the radios already have a link to another radio: see Verifying an Eclipse or
TRuepoint RF Link on page 3-64.
2. Select the first radio icon, hold the CTRL key and select the second radio icon.
3. Right-click the second radio icon, and from the right-click menu displayed, select
Create Link.
4. Select OK.
Exceptions
• If you try to create a link using a radio that already has a link, an error message
displays.
• If you are trying to create a link, and the Create Link menu option remains grayed out,
you may not have selected both ends, or the radios selected are not compatible.
• If you try to create a link for two radios that are not compatible, the following error
message displays:
Related Topics:

Creating an RF Link from the Find Function
Introduction
From the Find screen, you can select and link two radios. To link two Eclipse radios,
you must select the link objects for those radios.
To create an RF link from the Tree Viewer, see Creating an RF Link from the
Tree Viewer on page 3-60.
Procedure
1. To open the Find screen, go to the Edit menu and select Search. The Find screen
displays.
2. In the Find screen, locate the two radios to be linked. You may want to check to see
3. Select the icons for the two radios that you want to link.
4. Right-click. From the right-click menu, select Create Link, then select RF Link. A
message will display:
5. Select OK. The radios are now linked.
Exceptions
displays.
• If you try to create a link for two radios that are not compatible, an error message
displays.
Related Topics:
614-330055-001 July 2009 3-61

Creating an Eclipse RF Link
Introduction
When creating an Eclipse RF link you must select compatible Eclipse Nodes. The
Eclipse radio linking configuration options are shown below.
Each end of the link must have the same ODU type, that is ODU 100 to ODU 100 or
ODU 300 to ODU 300.
Figure 3-4. Eclipse Radio Linking Configuration Options
The types of Eclipse radios and the maximum number of links per each radio type are
as follows:
Table 3-5. Eclipse Radios - Number of Links
Type of Eclipse Radio Maximum Number of Links
Eclipse Terminal one link
Eclipse INU three links
Eclipse INUe six links
When creating an RF link between Eclipse Nodes you must select the same type of Link
icons for both sides of the link. The Eclipse Node link icons are as follows:
Table 3-6. Eclipse Radios - Type of Links
Type of Eclipse Link Icon
Link (non-protected)
Protected link
Ring-protected link
Procedure
To create an RF link between two Eclipse radios:
1. In the Tree Viewer, locate the two radios to be linked. You may want to check to see


2. Expand both the Eclipse radios so the required link icons are displayed.
3. Left-click the link icon of the first radio and CTRL left-click the link icon of the
second radio.
4. Right-click, and from the right-click menu displayed, select Create Link. A message
displays, confirming that the link is created:
5. Select OK.
RF links are automatically discovered for Eclipse radios.
Exceptions
displays.
• If you try to create a link for two radios that are not compatible, an error message
displays.
Next Topic:
Verifying an Eclipse or TRuepoint RF Link on page 3-64
Related Topics:
614-330055-001 July 2009 3-63

Verifying an Eclipse or TRuepoint RF Link
Introduction
You can verify the RF link for two Eclipse radios or two TRuepoint radios. This is done
using the Discover RF Link function.
This function is available for TRuepoint 4000, 4040, 5000, and 6400
radios. It is not available for TRuepoint 6500.
TRuepoint 6400 radios can have two RF links. All other radios have one
RF link.
Procedure
To verify an RF link for an Eclipse radio from the Find function:
1. In the Search screen, locate the Eclipse/TRuepoint radio.
2. The radio displays in the Search results frame. Right-click on the radio.
3. From the right-click menu displayed, move the cursor to the Create Link option
and select RF Link.
4. A message will display with the verification results:
5. Select OK.
Related Topics:

Deleting an RF Link
Introduction
There are two reasons why you would delete a link from ProVision; either the wrong
radios were linked, or the link is no longer available due to a change in equipment
installed at the site.
Procedure
To delete a link:
1. In the Tree Viewer, for an Eclipse radio, right-click the Link icon. For all other
radios, right-click the radio icon.
2. In the right-click menu, move the cursor to the Link option and select Delete.
The Delete Link window displays.
3. To confirm deleting the link, select Yes.
Related Topics:
• RF Linking Procedures on page 3-59
614-330055-001 July 2009 3-65

Miscellaneous Device Procedures
This section details several miscellaneous device procedures:

• Viewing Configuration for Devices on page 3-66
• Configuration Profiles for Bulk Configuration on page 3-72
• Eclipse Node Licenses on page 3-121
• Viewing/Changing Network IP Addresses on page 3-80
• Viewing/Changing TNet Proxy Configurations on page 3-81
• Using the TNet Proxy Viewer on page 3-83
Viewing Configuration for Devices

Introduction
Configuration data is entered via a craft tool and stored in the radio. Use the
Configuration Viewer to review the configuration for a device: ProVision retrieves and
displays the device values from the craft tool. You can also save the configuration data
for a device as a text .CSV file.
Procedure
To view a device’s configuration data:
1. Within the Tree or Map Viewer, right-click the radio icon. Select Configuration
Viewer from the right-click menu.
2. The Configuration window displays.
3. Select the required tab to view the device data in which you are interested.
4. The data may have changed since you selected to view it. To refresh the data, select
the Refresh from Radio button.
5. To save the configuration data as a .CSV file, click Save.
6. To close the Configuration window, select Close.

The table below lists the data that displays in the Configuration Viewer for different
radio and device types. Note that the most frequently used tabs are listed first, and
specialized tabs are listed later.
Tab Description
Information tab The information tab lists general information about the device,
such as name, site name, IP address, and type.
Radio For Eclipse radios, the Configuration Viewer window has

Frequency tab separate tabs that list the radio frequency configuration for each
link. It also includes a tab with Inventory details for the radio.
The drawing below shows the Configuration Viewer window for
an Eclipse Node with one link in slot 1 (LINK1) and one link in
slot 4 (LINK4).
For protected XP4 radios the Configuration Viewer window has

two radio frequency tabs: RF 1 and RF 2.
For Altium, DART, TRuepoint, MegaStar, and Velox radios the

Configuration Viewer window has a single link tab.
For DXR radios, there is no RF tab; instead, see the Slot

Configuration tab.
For Constellation radios, Constellation Terminal radios display

one link tab. Constellation Repeater radios display two link tabs.
Non-Farscan Constellation radios display this set of tabs:
Constellation via Farscan Proxy radios display this set of tabs:
614-330055-001 July 2009 3-67

Tab Description
The radio frequency tab lists information about the radio type
(capacity, bandwidth and modulation) and the link settings.
For Eclipse, XP4 and DART radios, if a radio frequency link has
been established, both the local and the remote data displays.
Gateway Data gateway details for a device.

(WiMAX
ASN-GW only)
Hardware tab The Hardware tab lists the version of the supported platform
(Velox only) and IDU serial number and barcode.

Tab Description
Interfaces The device interfaces for a device.

(ADR*,
Memotec,
WiMAX
ASN-GW)
* With
firmware later
than P2.6.
Inventory Tab This tab provides an inventory of all plug-ins associated with a
(Eclipse, device.
TRuepoint 6500,
ADR*, Memotec,
WiMAX
ASN-GW)
* With
firmware later
than P2.6.
IP Routing Tab This tab provides the IP routing settings for a Constellation
(Constellation device.
without FarScan
Proxy only)
MC Alarm Alarm inputs and relay outputs for the DVM’s connections.
Inputs and MC
Relay Outputs
(DVA, CAU)
614-330055-001 July 2009 3-69

Tab Description
Mux Modem Tab Mux modem settings for TRuepoint 4040/5000 or Constellation
(TRuepoint 4040 radios.
and 5000, and
Constellation)
Network DNS and NTP networking for a device.

(WiMAX
ASN-GW Only)
PAI Programmable Alarm Indicators (PAIs) for a DVM.

(DVA Only)
RSC and RPS Data about the Radio Service Channel and Radio Protection
(GP) Switching for the TRuepoint 6500 radio.
(TRuepoint 6500
Only)
Note: For more on the RSPI, RSC/RPS, and Service tab values for
TRuepoint 6500, see the TRuepoint 6500 documentation.

Tab Description
RSPI Radio Section Physical Interface values for the TRuepoint 6500.
(TRuepoint 6500
Only)
Service Service data for the TRuepoint 6500 radio.

(TRuepoint 6500
Only)
Slot Details about each slot for the DXR radio, and the hardware and
Configuration software installed at each slot.
Tab (DXR Only)
Software tab The Software tab lists the version of the software for the
components of the radio.
Related Topics:
614-330055-001 July 2009 3-71

Configuration Profiles for Bulk Configuration

The Configuration Profiles function enables you to apply configuration settings to
multiple radios. Configuring multiple radios at the same time is called bulk
configuration.
Users must have administration or NOC Engineer access to set up Configuration

Profiles and enable bulk configuration.
Related Topics:
• Create and Execute a New Configuration Profile on page 3-72
• Delete a Configuration Profile on page 3-79
Create and Execute a New Configuration Profile

There are two steps to a bulk configuration:
• Create a new Configuration Profile.
• Execute the Configuration Profile to one or more radios.
Procedure
To create a new Configuration Profile:
1. Open the Configuration Profile window in one of three ways:
• From the menu bar, select Configuration > Configuration Profiles.
• Or, right-click the desired container (root , region , site or rack
) and select Configuration > Profiles from the right-click menu.
• Or, right-click the desired radio and select Configuration > Profiles from the
right-click menu.
The Configuration Profiles window opens.
2. From the Profile drop-down menu, select a profile template:

3. The selected configuration template displays.
4. Enter the required configuration values. See Configuration Profile Settings for Bulk
Configuration on page 3-75 for information on the different templates.
5. The Read button is activated if you opened the Configuration Profile window by
right-clicking an individual radio. This feature reads the radio’s configuration and
automatically enters the information to the Configuration Profile window.
Select the Read button to enter the radio’s configuration to the Configuration
Profile window.
6. After you enter the desired settings, you must save the profile as a script before you
execute it. To save the configuration profile template as a script, select the Save or
Save As button. The Save As window displays. Enter the name of the configuration
profile and select the Save button.
7. The newly saved scripts appear in the Profile drop-down menu. Each template
includes a list of the scripts that are assigned to it. The user who created the script
appears in parenthesis next to the script name.
8. Select the Execute button to execute the newly-saved script. The Selected Object
List window opens.
9. The Object List window lists only those radios that support the script’s
614-330055-001 July 2009 3-73

configuration.
Select Open Task Manager to follow the progress in the task manager. Select
Execute to execute the script to the selected radios.
10. The Task Manager tracks the status by displaying the date and time that the bulk
configuration command was issued, with the script name. In this example, the
script name is “Saved Script 1”.
Select the + to display the devices that had the bulk configuration command
applied.
11. Select the Close button to close the Task Manager.

12. Select the Close button to close the Configuration Profile window.
Exceptions
You must save a Configuration Profile and its values as a script before you execute the
profile. Otherwise, the following error message displays:
Related Topics:

Configuration Profile Settings for Bulk Configuration

The table below describes the settings available for each Configuration Profile.
Configuration Profile Settings
Eclipse Ethernet Port Settings for IDU ES Allows you to enter Ethernet port settings for
the selected IDU ES radios. Use the drop-down
menus to select the required settings for the
speed, the duplex, the MDIX and the Priority for
each port.
Eclipse Ethernet Priority Mapping for IDU ES Allows you to enter the Priority Mode settings
for the selected IDU ES radios.
Priority Mode - Select a Priority Mode to receive
the priority values. Choose a value from: Port
Default, 802.1p, 802.1p then Diffserv, or Diffserv
then 802.1p.
Internal Priority -Assigns a priority level to a
device in this set of Priority Mode priorities.
Choose a value from Low, Medium Low, Medium
High, or High.
Eclipse NMS Traps Destination Allows you to enter the NMS trap destination
information for the selected radios.
Enable - Select the checkbox to enable the trap
destination.
Destination - The IP address of the trap
destination.
Port - The UDP port at the trap destination.
Rate - The maximum number of traps that can
be set per minute.
Operation Mode - From the drop-down menu,
select whether the trap destination is powered
by ProVision or a Third Party application.
614-330055-001 July 2009 3-75

Eclipse OSPF Settings Allows you to enter the IP address of a server

to use for OSPF settings, and to enable OSPF
use for the IP’s ports, AUX drives, and slots.
Caution: OSPF system settings are complex. An IP must
be set up in Portal as enabled for OSPF for these
settings to work correctly. This setting should only
be used by experienced administrators with
access to Portal.
Eclipse Time Server Settings Allows you to enter the IP address of a time
server that synchronizes the internal clocks of
the network components.
Eclipse Time Server - Select the checkbox to
activate the Eclipse time server setting.
IP Address - IP address of the Eclipse time
server.
Eclipse Time Zone Settings Allows you to enter a time zone to apply to one
or more selected radios. Use the drop-down
menu to select the required time zone.
Eclipse Ethernet Port Settings DAC ES Allows you to enter Ethernet port settings for
the selected DAC radio. Use the drop-down
menus to select the required values for the
speed, the duplex, the MDIX and the Priority for
each port.

Eclipse Ethernet Port Settings DAC GE Allows you to enter Ethernet port settings for
the selected DAC GE radios. Use the drop-down
menus to select the required values for the
speed duplex, MDIX and the Priority for each
port.
Eclipse Ethernet Priority Mapping for DAC Allows you to enter the Priority Mode settings
GE for the selected DAC GE radios.
Priority Mode - Select a Priority Mode to receive
the priority values. Choose a value from: Port
Default, 802.1p, 802.1p then Diffserv, or Diffserv
then 802.1p.
Internal Priority -Assigns a priority level to a
device in this set of Priority Mode priorities.
Choose a value from Low, Medium Low, Medium
High, or High.
DART NMS Trap Destination Allows you to select up to three trap

destinations for the following components of
the DART radios:
Ethernet
Radio
Serial Port 1
Serial Port 2
Select the check box to activate the trap
destination for the selected component. In the
Destination field, enter the IP address for the
specified trap destination.
614-330055-001 July 2009 3-77


XP4 16/E3 Trib Controls
When you configure the trib controls for each of
the 16 tribs, you choose whether the trib is
Normal (commissioned) or Inverted (not
commissioned.) Note that Normal tribs will
report errors if they have no traffic.
After configuring the controls, click Execute. The
values are applied to the tribs for this device.
TRuepoint Trap Destinations: 5000, 4040, 4000

This allows you to enter the trap destination
information for the selected type of TRuepoint
radios.
destination.
destination.
TRuepoint SNMP Managers: 5000, 4040, 4000

This allows you to enter the trap destination
information for the selected type of TRuepoint
radios.
destination.
Destination - The IP address of the SNMP
manager.
Constellation Trap
Destinations This allows you to enter the trap destination
information for the Constellation radios.
destination.
Note: This data is not active for Constellation for
FarScan devices.
Related Topics:

Delete a Configuration Profile

To delete one configuration profile:
1. From the menu bar, select Configuration > Configuration Profiles. The
Configuration Profiles window opens.
2. From the Profile drop-down menu, select the desired script you wish to delete. The
selected script displays.
3. Select the Delete button. ProVision asks if you really want to delete the selected
script. Select Yes to continue.
4. The selected script is deleted. Select the Close button to close the Configuration
Profiles window.
To delete multiple configuration profiles:

1. From the menu bar, select Configuration > Configuration Profiles. The
Configuration Profiles window opens.
2. From the Profile drop-down menu, select the template of the configuration profile
you wish to delete. (Note that the previously saved scripts are listed under their
respective category.)
3. The Configuration Profiles window for the selected template displays.
4. Select the Delete button. The Delete window opens with a list of all previously saved
scripts for the selected template:
5. Highlight the script to be deleted and select the Delete button.

6. ProVision asks if you really want to delete the selected script. Select Yes to
continue.
7. The selected script is removed from the list. Select the Close button to close the
Delete window.
8. Select the Close button to close the Configuration Profiles window.
Related Topics:
614-330055-001 July 2009 3-79

Viewing/Changing Network IP Addresses

The network configuration gives you a list of the device IP addresses entered via
ProVision. From here you can view and change the ProVision device IP addresses. This
function enables you to view a list of the network devices’ IP address and where
required, change an IP address.
Changing a device’s IP address within ProVision does not change the IP

address stored in the device itself.
Procedure:
To view the IP addresses of the devices on the network:
1. From the menu bar, select Configuration > IP Address.
The IP Address window displays. To display all the devices and associated IP
addresses at once, select Expand All Levels.
2. Double-click the IP addresses to be changed, and type the new IP addresses.

3. To apply the new IP addresses, select Apply.
4. To accept the changes, select OK.
Related Topics:

Viewing/Changing TNet Proxy Configurations

Introduction
The information in this section is only relevant if your network has TNet devices
deployed and commissioned.
The Proxy Configuration Manager displays a subnet view of the network’s TNet
Proxies. From the Configuration Manager, you can identify how many subnets have
been set up for each Proxy, and which devices are grouped under each subnet.
Use this function when setting up the network to ensure the TNet radio details in
ProVision match those stored in the TNet Proxy.
When you select a TNet device its configuration parameters stored in ProVision are
displayed. You can change the device name, and the subnet in tandem with the
necessary cabling changes between the Proxy and its devices.
If you change a subnet without moving the device’s cabling to the

new subnet, when ProVision next polls the Proxy, the device
displays in an errored state.
The TNet device icons are detailed in TNet Devices on page 2-34.
Procedure
To view the TNet Proxy configurations:
1. In the Tree Viewer or Map Viewer, right-click a TNet Proxy icon.
The Proxy right-click menu displays:
614-330055-001 July 2009 3-81

2. Select Proxy Configuration Manager.

The Proxy Configuration Manager window displays.
Activity How to...
To change a Proxy’s name or 1. Select the required Proxy icon.

increase its number of subnets
within ProVision:
2. Make the required changes to the Subnets field. There

is a maximum of 16 subnets per Proxy.
3. To save the changes within ProVision, select Commit
Changes.
To change a Proxy’s IP See Viewing/Changing Network IP Addresses on page 3-80.

address:
To move a TNet device from 1. Expand the Proxy and the subnet to display the TNet
one subnet to another subnet devices. Select the required TNet device.
and/or
change the TNet’s address on
the subnet:
The device’s name, the subnet it is connected on, and

its address on the subnet are displayed.
2. Enter the new subnet number and/or the new address.
3. Select Commit Changes.
To close the Proxy Configuration Manager window, select Close.

Related Topics:
• Using the TNet Proxy Viewer on page 3-83

Using the TNet Proxy Viewer

Introduction
The TNet Proxy Viewer enables you to identify where there are problems with TNet
devices, and if the problems are in ProVision or the TNet Proxy.
In the Proxy Viewer, the Subnet to Radio Status columns contain TNet device data read
from the Proxy. The ProVision name, type and status columns contain the device data
stored in ProVision.
For more information see TRuepoint Device Deployment on page 3-18.
You must have a NOC Engineer or Administration security level to access

the Proxy Viewer.
Procedure
To use the TNet Proxy Viewer:
1. In the Tree Viewer or Map Viewer, right-click the required TNet Proxy icon. Or,
locate and right-click the TNet Proxy icon in the Proxy Configuration Manager
screen.
2. From the right-click menu, select Proxy Viewer.
3. The Proxy Viewer <proxy name> window displays.
4. Check for any discrepancies between the Proxy and ProVision radio data.
5. To close the Proxy Viewer window, select Close.
Related Topics:
614-330055-001 July 2009 3-83

Circuit Management
Circuit information is documented in the following sections:

• About Circuits and Circuit Tracing on page 3-84
• Initiating and Viewing a Circuit Trace on page 3-85
• Circuit Features on page 3-87
• Display a Single Circuit on page 3-90
• Circuit Logical Containers on page 3-91
• Circuit Provisioning: Creating Circuits Between Devices on page 3-93
• Renaming Circuits on page 3-106
• Check and Synchronize Circuit Names on page 3-108
• Delete a Circuit on page 3-109
About Circuits and Circuit Tracing

A circuit is a single tributary path that travels through a sequence of radios. A circuit
bundle is a collection of tributary paths that travel through the same sequence of radios
from the same start point to the same end point.
The Circuit Trace function maps all circuits and circuit bundles through the network
that originate or terminate from a selected Eclipse radio. When a user activates the
Circuit Trace function, and the circuit trace is performed and updated.
Circuit Trace is active and available for the following radio types: Eclipse Terminals
(IDU); or Eclipse Nodes (INU or INUe) that include a DAC plug-in. Circuits are
initiated and terminated on a DAC (INU/INUe), or, for an IDU, within its ethernet/
data module.
For the Circuit Trace to show full, point-to-point circuit endpoints, all intermediate
Eclipse radios in an Eclipse network must be nodes (INU or INUe). Circuit tracing can
show a trace between back-to-back Eclipse Terminals (IDU), provided the IDUs have
the bus interconnection capabilities such as the IDU 20 x V2.
ProVision periodically captures the cross-connect configurations from the radios. If
you make any circuit configuration changes to the radios within a circuit, the circuit
must be re-traced to accurately identify the newly-configured circuit. Circuit tracing:
• Locates incorrect circuit cross-connections within the network
• Views and manages changes to the network circuit configuration (such as adding
circuit capacity during network rollout).
• Supports circuit provisioning during network rollout. For example, you can select a
circuit, use the Circuit Management feature, and make the required circuit capacity
change. Then, you can verify the changes through the circuit trace feature.
• Views the circuits to use the troubleshooting features of ProVision, such as loopback
and PRBS (pseudo random binary sequence) testing.
Next Topic:
Initiating and Viewing a Circuit Trace

Initiating and Viewing a Circuit Trace

To run a Circuit Trace, the selected radio must be either an Eclipse Terminal (IDU) or
an Eclipse Node (INU or INUe) with a DAC plug-in for the trace to be successful.
You can retrace one circuit using the instructions below, or you can retrace all circuits
using the Global Circuit Trace function. Click this icon on the toolbar to run a Global
Circuit Trace:
Procedure
1. Select an Eclipse device in either the Tree Viewer or the Map Viewer. Right-click to
open the right-click menu, and select Circuits - Initiate Trace.
2. A ProVision message box appears. Select Yes to open the Task Manager window.
3. The Task Manager window appears. Open the item using the + to view the Eclipse
Node that is undergoing a circuit trace.
4. The trace is complete when the status reads “Trace Complete.”

5. Select Circuit Root in the Circuits Tab to display the results of the circuit trace in the
Map Viewer.
6. Select the lock icon to re-arrange the radios pictured in the Map Viewer to your
liking. When finished, select the lock icon again to freeze the view.
614-330055-001 July 2009 3-85

The Map Viewer displays the circuits (and their associated radios) that originate or
terminate at the selected radio. Beside the Map Viewer, the Details Tab describes the
link, event status, and circuits for a selected link in the Map Viewer. View and hide the
Details Tab by clicking the Details icon on the right side of the Map Viewer.
The Circuits Tab lists each circuit and its components.
Both the Details and Circuits Tabs display circuit bundle names. A circuit bundle name
includes the names of the two devices that make up the beginning and end of the link.
A circuit name identifies a specific circuit.
You can rename circuits bundles and circuits. Right-click on the circuit or circuit
bundle and select Rename. In the Rename window, enter the new name for the and
click OK.
Event security colors are used with the circuit trace function. The event
code of a circuit is determined by the radio with the most severe event.
Next Topic:
Circuit Features

Circuit Features
After a circuit trace has been performed, the circuit (or circuits) are displayed in the
Map Viewer. The following features make monitoring the network easy and efficient:
• View and Hide Multiple Circuits for a Link
• Circuit Details Tab
• Circuit G.826 Annotation
• Circuit Bundle Text Annotation
View and Hide Multiple Circuits for a Link

Within the Map Viewer, each circuit link has a / switch. Click this to view and hide
multiple circuit bundles for a single link.
When you select one of the circuits from within a selected link, ProVision automatically
highlights the circuit throughout the circuit bundle.
When multiple circuits within a circuit bundle are displayed, place the cursor over one
of the circuits to display the name of the circuit bundle for that circuit. The example
below shows that the last circuit has radio 52 and radio 57 as its terminating radios.
Circuit Details Tab

The Details tab shows information for a selected link. It is a convenient way to view link
details while also viewing the Map View.
614-330055-001 July 2009 3-87

To open the Details tab, click on the Details icon. The Details icon displays on the upper
right side of the Map View. In the sample below, there is an arrow showing which link
is selected. The data for this link is shown in the sample Details tab.
The Details tab displays the following information:

• Link: The name of the link, which indicates the radios connected by this link.
• Severity: The severity of any events for this link.
• Circuits: A list of all the circuits related to the selected link.
Circuit G.826 Annotation

G.826 annotations is another circuit trace feature that displays, in real time,
performance statistics for the selected link. This powerful tool helps you monitor a
single link and helps you respond faster to issues that may arise.
• To enable the G.826 annotations, right-click the or icon and select G.826
Annotation from the drop-down menu.
• To disable the G.826 annotations, right click the or icon and de-select G.826
Annotation from the drop-down menu.
The information in the G.826 annotations are updated approximately every 5 seconds.
The table below shows the performance statistics that are displayed when enabling the
G.826 Annotations feature for a circuit.

Table 3-7. Performance Statistics
Initials Performance Statistic
AS Available Seconds
US Unavailable Seconds
ES Errored Seconds
SES Severely Errored Seconds
EB Errored Blocks
BBE Background Block Errors
Circuit Bundle Text Annotation

You can enable text annotations for the RF paths in a circuit bundle. Use this to label
each circuit with the circuit capacity or the circuit name.
Circuit Capacity
To label the circuit bundle with the circuit capacity, right click the icon and select
Text Annotation > Capacity from the drop-down menu (as shown in the illustration
below).
The capacity is listed as two values. The first value is the capacity for the individual
circuit bundle. The second value (within the parenthesis) is the total available capacity
for the entire link.
Name
To label the circuit bundle with the circuit name, right click the icon and select Text
Annotation > Name from the drop-down menu (as shown in the illustration below).
To remove the text annotation, right click the icon and select Text Annotation > None
from the drop-down menu.
Next Topic:
Display a Single Circuit
614-330055-001 July 2009 3-89

Display a Single Circuit

In the Circuits Tab, select the + next to a circuit bundle to list the circuits associated
with it. Select the name of an individual circuit to display that circuit, and only that
circuit, in the Map Viewer. In the example below, Circuit 21 is selected, and displays in
the Map Viewer.
To view additional information about a circuit, in the Circuits Tab, place the cursor over
the circuit name. A pop-up displays with capacity and link information.
Place the cursor over a link to display additional information about that link.
Next Topic:
Circuit Logical Containers

Circuit Logical Containers

A Logical Container is a user-defined group of circuit bundles or objects (i.e., radios)
that share a common purpose. This grouping allows these objects to be monitored,
managed, and viewed independently of the main network. For example, you may want
to group high-capacity, high-priority circuit bundles together, to differentiate between
high and low impact failures and to respond accordingly.
Both individual radios and entire circuit bundles can be assigned to

one or more logical containers.
The Logical Containers section covers the following topics:

• Logical Containers Tab on page 3-91
• Creating a Logical Container on page 3-92
See also Adding Circuit Bundles to Logical Containers on page 3-100.
Logical Containers Tab

The Logical Containers tab displays all the logical containers that have been created,
and all the circuit bundles assigned to the logical containers.
Figure 3-5. Logical Containers Tab with Circuits Assigned
The circuit bundles can also be displayed in the map view:

• Select the Logical Container Root to display all circuit bundles associated with all
services.
• Select the Logical Container Name to display all circuit bundles associated with that
logical container.
• Select the Circuit Name to display only that circuit bundle. To view details for a circuit
bundle, place the cursor over it. A pop-up displays with the name, type, and capacity
of that circuit bundle. The figure above shows the circuit bundles in a logical
container.
614-330055-001 July 2009 3-91

Creating a Logical Container
Procedure
To create a logical container:
1. In the Logical Containers Tab, right-click on Logical Container Root.
2. In the right-click menu, select Add Logical Container.
3. The Add Logical Container window opens. Enter the user-defined logical container
name and select OK.
The name appears in the Logical Container Tab as a sub-container of Logical

Container Root.
4. Repeat steps 1 - 3 to add additional logical containers.

For additional features, see the section on Logical Containers on page 4-69.
Next Topic:
Circuit Provisioning: Creating Circuits Between Devices

Circuit Provisioning: Creating Circuits Between

Devices
The Circuit Provisioning function allows you to select one or more devices and create
or edit circuits and circuit bundles between the devices. These are then written directly
to the radios. Circuits and circuit bundles can be written to a radio in Portal, but the
ability to do this from ProVision makes ProVision a central circuit manager for radios.
To create a circuit or circuit bundle for a radio in ProVision, you must do the following:
1. Make sure that all links for the network are set up.
2. Discover RF links for the radio (see RF Linking Procedures on page 3-59).
3. Use the Circuit Provisioning function to create the circuit/circuit bundle and write
it to the radio.
4. Commission the circuits.
This section describes how to use Circuit Provisioning and how to commission and
decommission created circuits.
• Using Circuit Provisioning to Create Circuits on page 3-93
• Commissioning and Decommissioning Circuits on page 3-97
Using Circuit Provisioning to Create Circuits
Introduction
The Circuit Provisioning function enables you to create circuits and circuit bundles for
radios. This process defines all possible paths between devices, and allows you to
choose which paths you want to use for circuits.
Note the following:
• To create a circuit, a circuit path must begin and end with a DAC.
• RF links for the involved radios must be discovered before a new circuit can be
created.
• After you create a circuit, you can edit it, increasing or decreasing its capacity and
changing termination ports.
• For an existing circuit bundle, users have two options to increase circuit capacity:
• Users can extend the circuit capacity of an existing bundle, OR
• Users can create a second, replica bundle.
Procedure
To create circuits using circuit provisioning:
1. Check that the radios you want to connect with a circuit have had RF links created.
See RF Linking Procedures on page 3-59 for detailed instructions.
2. In the Tree Viewer or the Circuits tab, select the radio and right-click Circuit
Provisioning.
3. The Circuit Provisioning - Object Selection screen displays. The item in the frame for
614-330055-001 July 2009 3-93

Object A is the radio you selected to open this screen. If you selected two radios, the
second one is in the frame for Object B.
This screen allows users to select two objects to be linked via a circuit.
Select an object in the frame for Object A. The Hide invalid terminations check
box is selected by default. When this is selected, the frame for Object B will only
display options that can link to the selected item for Object A.
After you have selected Object A and Object B, click Next.
4. The Circuit Provisioning - Path Selection screen displays.
This screen shows all possible network paths linking the selected radio end points
for this radio, with the following information:
• Used Capacity = This shows the used/configured capacity of the path for a
circuit bundle. New circuit bundles do not show a capacity value.
• Circuit Bundle = If a network path is already an existing circuit bundle, this
shows the name of the indicated circuit bundle.
• Paths = A graphic of the path of the circuit bundle through the Eclipse network.
The terminating Eclipse radios are indicated by paired DAC + RAC icons.
Intermediate Eclipse nodes are shown as single radio icons. Where there are
more than 5 path hops, a cloud icon is shown, with a number indicating the
number of intermediate Eclipse nodes.

• Pathway Tooltip = Place the cursor over a circuit pathway to view its full
information, displayed as a tooltip.
For an existing circuit bundle, users have two options to increase circuit capacity,
by selecting the option they want:
• Users can extend the circuit capacity of an existing bundle by selecting the
bundle.
• Users can create a second, replica bundle by selecting the Create a new
circuit bundle option that mirrors the existing bundle.
5. Select the network path that you want to have for a circuit, and click Next.
6. ProVision reads the cross-circuit information for nodes in the selected path. This
can take up to 5 minutes. When this is complete, the Circuit Provisioning - Capacity
Selection screen displays the values for the circuit.
• Circuit Bundle = A name prefix for this circuit bundle. This will appear as part
of all circuit names within this bundle.
• Configured Capacity =The capacity for this circuit. If you set the capacity at
too high a value, a warning will display.
7. Enter values for the Circuit Bundle and Configured Capacity. Then, click Apply. The
values are applied to the circuit.
8. Click on the Cross Connect icon at the side of the screen, and select one of the linked
nodes. The node capacity and details display: the name, free capacity, configured
ports, and any other configured links. To change the terminating port for a link,
click the link and select the terminating port from a drop-down menu that shows
all the available links for the port. In this menu, each link status is identified by its
color:
• White - Not used by any other bundle
• Grey - Newly created, not used by any other bundle
614-330055-001 July 2009 3-95

• Brown - Used by another bundle
9. Using the Cross Connect data, review and adjust the configured port connections.
You can review the Cross Connect data for both sides of the link. If you make
changes to the Cross Connect data, you are prompted to save the changes.
10. After the circuit capacity and other values are correct, click Apply, then Write.
11. ProVision writes the changes to the nodes. This can take up to 5 minutes; progress
indicators display during the process. First, ProVision checks with the radios.
Then, it verifies that the circuits are ready for the retrace.A message displays when
the circuit change is written successfully, or if it is not successful.
12. In the Circuit Provisioning screen, click Close. The new circuit displays in the
Circuits tab, in the list of circuits for the radio.
13. After you have completed Circuit Provisioning for a circuit, you can open it, edit the
data port connections and capacity, and write it to the radios again.
Next Topic:
Commissioning and Decommissioning Circuits on page 3-97

Commissioning and Decommissioning Circuits
Introduction
After you create circuits using the Circuit Provisioning function, you must commission
the circuits. Commissioning enables the circuit to carry customer traffic. You can select
all circuits in a circuit bundle to commission.
You can also decommission a circuit. If you are changing or removing customer traffic
from a trib, it needs to be decommissioned. If a trib is commissioned and there is no
customer traffic, the radio will raise a CRITICAL event. Decommissioning avoids this
problem.
From ProVision, you can select and commission one or multiple circuits/circuit
bundles. Selecting a circuit bundle commissions all the circuits in that bundle.
Procedure
1. In the Circuits tab, select the circuits that you want to commission. Or, select a
circuit bundle.
2. Right-click on the circuits/circuit bundles. In the right-click menu, select
Commission. The Commissioning process begins:
3. When the process is complete, a message displays, showing that the circuits were
commissioned successfully.
4. To decommission a circuit, select it and right-click. In the right-click menu, select

Decommission.
5. Again, a message should display, indicating that the circuits were decommissioned
successfully.
Next Topic:
Additional Circuit Functions on page 3-98
614-330055-001 July 2009 3-97

Additional Circuit Functions

These functions are described in the following sections:
• Open Submap on page 3-99
• Event Browser on page 3-99
• Circuit Diagnostics on page 3-99
• Adding Circuit Bundles to Logical Containers on page 3-100
• Configure Circuit Bundles on page 3-102
• Renaming Circuits on page 3-106
• Circuit Problem Icons on page 3-107
• Check and Synchronize Circuit Names on page 3-108
• Delete a Circuit on page 3-109
Right-click a circuit to access the circuit right-click menu, with additional functions for
that circuit. You can access the Circuit right-click menu from either the Logical
Containers Tab or the Circuits Tab.
Circuit Bundles also have a right-click menu. This has functions that apply to the circuit
bundle level. There is overlap between the circuit and circuit bundle functions.

Open Submap
Select Open Submap to open a window showing the elements within the selected circuit
or circuit bundle. Submaps are fully-functional maps with their own menu and tool bar.
For a complete description of submaps and their functions, see Submaps on page 2-38.
Event Browser
To view the events that apply to objects in a circuit or circuit bundle, select Event
Browser. This opens a separate, floating window that displays a scrolling list of events
for the circuit objects.
For a complete description, see Event Browsers on page 4-22.
Circuit Diagnostics
Select Circuit Diagnostics to open the circuit diagnostics window. This feature allows
you to diagnose problems within a circuit and isolate faulty equipment.
For a complete description of this feature, see Circuit Diagnostics Feature on page 5-5.
Major problems with circuits are indicated with the Circuit Problem Icons on
page 3-107.
614-330055-001 July 2009 3-99

Adding Circuit Bundles to Logical Containers

From the right-click menu for a circuit bundle, you can add the circuit bundle to a
Logical Container.
Procedure
To add a circuit bundle to a logical container:
1. From the Circuits Tab, right-click the circuit bundle to be added to a logical
container.
2. From the right-click menu for a circuit bundle, select Configure Logical Containers.
3. The Configure Logical Containers window displays for the selected circuit bundle.
4. Highlight the service in the All Logical Containers list and select the > button. The
circuit bundle is now part of the selected service.
5. A circuit bundle can be included in multiple logical containers. Repeat step 4 to
assign the circuit bundle to another logical container.
6. Select OK to continue.
7. The selected circuit bundle displays within the selected logical container.
Remove a Circuit Bundle from a Logical Container

To remove a circuit bundle from a logical container:
1. From the Circuits Tab, right-click the circuit to be removed from a logical container
2. From the right-click menu, select Configure Logical Containers.

3. The Configure Logical Containers window for the selected circuit displays.
4. Highlight the service in the Configured Logical Containers list and select the <
button. The circuit is removed from the selected logical container.
5. Select OK to continue. The change is saved.
Next Topic:
Configure Circuit Bundles
614-330055-001 July 2009 3-101

Configure Circuit Bundles

From the right-click menu for a circuit, you can assign or remove circuits from a circuit
bundle.
A circuit must be assigned to a circuit bundle. The user can change the
circuit bundle to which a circuit is assigned. A circuit can only be assigned
to one circuit bundle at a time.
Procedure
To add a circuit to a circuit bundle:
1. From the Circuits Tab, right-click the circuit to be added to a circuit bundle.
2. From the right-click menu for a circuit, select Configure Circuit Bundles.
3. The Configure Circuit Bundles window for the selected circuit displays.
4. Highlight the circuit bundle in the All Circuit Bundles list and select the > button.
The circuit is now assigned to the selected circuit bundle.
5. Select OK to continue.
6. The selected circuit displays within the selected circuit bundle.
Remove a Circuit from a Circuit Bundle

To remove a circuit from a circuit bundle:
1. From the Circuits Tab, right-click the circuit to be removed from a service.
2. From the menu displayed select Configure Circuit Bundles.

3. The Configure Circuit Bundles window for the selected circuit displays.
4. Highlight the circuit bundle in the Configured Circuit Bundles list and select the <
button. The circuit is removed from the selected circuit bundle.
5. Select OK. The change is saved.
Next Topic:
Cable Connections for Eclipse IDU-IDU Circuits
614-330055-001 July 2009 3-103

Cable Connections for Eclipse IDU-IDU Circuits
Introduction
For Eclipse radios, circuits normally terminate at DAC cards. From the DAC cards, the
radios are connected to other equipment (base stations, other radios) via cables.
Sometimes, two IDUs may be connected directly using a cable, or an IDU may be
connected to a DAC or data plug-in using a cable. ProVision can recognize these
cable-based connections.
This section describes how to record these connections in ProVision, and how to create
a .CSV report with the cable connection information. This report can then be provided
to technicians, to ensure that the physical cable connection is correct.
Procedure
1. In the Tree viewer, select the two DACs or data plug-ins that have or will have a
cable connection.
2. In the Tree viewer, right-click on one of the DACs. From the right-click menu, select
Create Link > Logical Link.
3. A logical link is created between the DACs or data plug-ins.
4. In the Map Viewer, right-click on the logical link. From the right-click menu, select
Manage Port Connections.
5. The Manage Port Connections screen displays.
6. In this screen, you can either:

• Set up a default Port 1 - Port 1 connection. To do this, click Auto.
• Link specific ports to specific cables. To do this, use the drop-down menus in the
left column to select the ports. The selected port will be connected to the port in
the right column.
Once you have set up the cable/port links, click OK. The links are saved and applied.

7. To save the cable connection data as a .CSV file, click Report. You will be prompted
to assign the report a file name and a folder location.
8. After generating the DAC-DAC connection report, you can distribute this report as
required.
Next Topic:
Retrace a Circuit
Retrace a Circuit
Introduction
Occasionally, changes are required in a network, whether those changes are to a whole
circuit or to an individual radio. Retracing the circuit is necessary to ensure it is
correctly represented within ProVision.
When you run a retrace, the selected circuit is deleted and then retraced. The
terminating plug-ins (such as a DAC) define a circuit. If you retrace one circuit, another
circuit with a common terminating plug-in may also be deleted.
You can retrace one circuit using the instructions below, or you can
retrace all circuits using the Global Circuit Trace function. Click this icon
on the toolbar to run a Global Circuit Trace:
Procedure
To retrace a circuit:
1. Right-click the name of the circuit.
2. Select Retrace on the right-click menu displayed. A message and confirmation
screen displays.
3. If you would like to open the task manager to monitor the circuit trace, select the
check box. Select Yes to continue.
4. ProVision runs the circuit trace.
Next Topic:
Renaming Circuits
614-330055-001 July 2009 3-105

Renaming Circuits
Introduction
This function renames a circuit in ProVision only. The user must then synchronize the
name with the actual radio (see Check and Synchronize Circuit Names on page 3-108 ).
Procedure
To rename a circuit:
1. In the Circuit Tab, right-click the name of the circuit.
2. From the right-click menu, select Rename.
3. The Rename screen displays. Enter the new name for the circuit and click OK.
4. The circuit is renamed in ProVision. To apply the changed name to the radio, you
must run Check and Synchronize Circuit Names on page 3-108.
Next Topic:
Circuit Problem Icons

Circuit Problem Icons

There are two icons that show at a glance if there is a problem with a circuit. The circuit
information icon appears next to a circuit whenever there is a problem with that
particular circuit. It appears in both the Logical Containers Tab and the Circuits Tab.
The invalid circuit icon appears in the Circuits Tab next to any invalid circuits or
circuit bundles. When this appears for a circuit or circuit bundle, the circuit trace failed
to discover both end-points for this circuit.
You can view the details of the invalid circuit by placing the cursor over the invalid
circuit icon. A pop-up window displays, with additional information about the
problem.
For an invalid circuit bundle, the message describes the problem at the circuit bundle
level. Open the circuit bundle to view specific circuits that have errors.
Figure 3-6. Invalid Circuit Details in the Circuit Tab, Circuit Bundle Details
Circuits that become invalid after valid operation remain in their assigned bundle, but
are marked invalid, as shown in the figure above. Circuit bundles that are invalid when
they are first traced are listed under a circuit bundle named Invalid Circuit, as shown
below.The pop-up window includes the details for a selected invalid circuit.
Figure 3-7. Invalid Circuit Bundle, Specific Circuit Details
The pathways saved for an invalid circuit are not available to other
circuits. To reuse these pathways, delete the invalid circuit.
Next Topic:
Check and Synchronize Circuit Names
614-330055-001 July 2009 3-107

Check and Synchronize Circuit Names
Introduction
After renaming circuits, you must check and synchronize circuit names. Synchronizing
names takes any circuit names that have been changed in ProVision and writes them
into each node of the circuits. This ensures that the circuit names in the radio match
the circuit names in ProVision. If there are any problems or inconsistencies, they are
identified during the Synchronize process.
You can synchronize circuit names for an individual circuit, or for all circuits in a circuit
bundle.
See also Renaming Circuits on page 3-106.
Procedure
To synchronize names for a circuit, or for all the circuits in a circuit bundle:
1. Right-click the name of the circuit or circuit bundle.
2. From the right-click menu, select Synchronize Names.
3. ProVision checks that the name for this circuit and any linked circuits are correct.
4. If the names all synchronize, the following message displays:
5. If there is any failure to synchronize, for example, because ProVision cannot

communicate with a node in the circuit, the following message displays:
Next Topic:
Delete a Circuit

Delete a Circuit
Introduction
You can delete one or more circuits from the Circuits Tab. In ProVision, there are two
ways to delete a circuit:
• Deleting it only from within ProVision. This option has no effect on the radios or
communication traffic within the circuit: only the representation of the circuit in
ProVision is deleted.
• Deleting it from both ProVision and the radio network.
Procedure
To delete a circuit:
1. Right-click the name of the circuit.
2. Select Delete on the right-click menu displayed.
The Delete Circuits window displays, with two deletion options:.
3. To delete the selected circuit from both ProVision and the radio network, select
Yes.
4. To delete the selected circuit only from ProVision, select No.
5. To not delete the circuit at all, click Cancel.
6. If you chose step 3 or 4, the Circuits Tab and the Map Viewer are refreshed
immediately and the circuit is no longer displayed.
Next Topic:
Loading/Activating New Eclipse Software and Licenses
614-330055-001 July 2009 3-109

Loading/Activating New Eclipse Software

and Licenses
This section describes how to load and activate new Eclipse software and new Eclipse
node licenses.
• About Loading Eclipse Software Via ProVision on page 3-110
• Eclipse Software Loading Examples on page 3-111
• Stage 1: Eclipse Software Load Procedure on page 3-113
• Stage 2: Eclipse Software Activation Procedure on page 3-118
• Eclipse Node Licenses on page 3-121
• Eclipse and StarMAX Configuration Backup Export on page 3-124
About Loading Eclipse Software Via ProVision
Before loading and activating new Eclipse software, it is

important to review the release notes and the ReadMe file that
accompany the new software version to be aware of any cautions
and advice notes.
Using ProVision, you can remotely upgrade Eclipse software for a number of terminals
simultaneously, using the Loading/Activating New Eclipse Software feature. You select
a number of radios to be loaded, in a single task. Then, ProVision transfers the software
from the software register to the radios. This feature also provides the flexibility to
sequentially run a number of separate software-loading tasks to different radios.
Once the transfer is completed, you can activate the software in the radio in one of two
ways:
• Manual Activation - ProVision lets you activate each radio manually with just a
mouse-click. This method could be useful when, due to network complexities, a
careful, “hands-on” approach to software activation is necessary.
• Scheduled Activation - ProVision also lets you select a date and time to automatically
activate one or more radios. This method could be useful to automatically activate
the new software in large sections of a network (or even in an entire network) at a
time when there is minimal traffic; thus minimizing network disruptions.
An entire network of Eclipse radios can have new software installed. And by being able
to select an activation time to coincide with low circuit usage, you can ensure minimum
disruption to network traffic.

When loading software using this feature, the same version of the
software is loaded onto all parts of an Eclipse radio.
The Eclipse Software Upgrade Process

The Eclipse software upgrade is split into two separate stages: loading and activation.
• Stage 1: Eclipse Software Load Procedure on page 3-113 - The loading stage is slow
and can take up to 30 minutes or longer. Because the loading process does not affect
the network traffic, this slower stage of the software upgrade can be initiated at any
time.
• Stage 2: Eclipse Software Activation Procedure on page 3-118 - The activation stage,
although it occurs almost instantly, may momentarily affect network traffic if, for
example, a soft reset is required. Because of this, the activation stage is under
separate control to allow you to select a time when network traffic is least affected.
The following is an overview of the individual steps that make up the software
download procedure.
1. Bring the new version of Eclipse software into the ProVision Server software
register.
2. Identify the number of download tasks needed in order to software upgrade the
Eclipse network. A software download task refers to the number of Eclipse radios
to be grouped together for a download.
3. Create and initiate a software download task, by selecting the Eclipse software
version and the Eclipse radios to be loaded. Monitor progress using the ProVision
Task Manager.
4. On download completion, activate the software in the Eclipse radios from the
ProVision Task Manager and monitor activation progress.
5. Repeat steps 3 and 4 for other software download tasks. Subsequent tasks begin as
soon as the previous task completes loading. The ProVision Task Manager can be
used to simultaneously activate software across tasks.
Two Eclipse software loading examples are shown
Eclipse Software Loading Examples

This first example divides the network into levels and loads the Eclipse software to each
level as a single task. The first such task would be to load the software to the radios at
the farthest points from the operation center. This group is called “Level 1” in the
example below. The remaining levels can be loaded in subsequent tasks as shown.
614-330055-001 July 2009 3-111

Figure 3-8. Example 1: An Eclipse Radio Network Divided into Levels
The second method is to divide the network into regions and load the Eclipse software
to each region as a single task as shown.
Figure 3-9. Example 2: An Eclipse Radio Network Divided into Regions
Next Topic: Stage 1: Eclipse Software Load Procedure on page 3-113

Stage 1: Eclipse Software Load Procedure

The software load procedure is further divided into two parts:
• Part A: Register the Software onto the ProVision Server on page 3-113
• Part B: Load the Software onto the Eclipse Radios on page 3-115
Part A: Register the Software onto the ProVision Server
Before loading software onto a network of radios, always

complete the load and activation to one remote site and check for
normal operation at that site before downloading software to the
rest of the network.
Ensure that the current software (the version that is about to be

replaced) is listed in the Software Register. In the event of a problem
while loading the new software, the current version can be re-installed if
needed.
Procedure:
To bring the new software onto the ProVision server software register, follow the steps
below.
1. From the menu bar, select Configuration > Software Loading Preferences.
The Software Loading Preferences window displays. It lists all software versions
that were previously registered.
If the required software is already listed on the register, proceed to Part B: Load the
Software onto the Eclipse Radios on page 3-115.
2. Select Register to add a new version of the software pack to the register. A directory
window displays.
614-330055-001 July 2009 3-113

3. Place the CD with the software update (the file type is *.swpack) in the CD ROM
drive. Select the CD ROM drive from the drop-down menu. Select the desired
software pack and select Open.
4. Alternatively, if the software update was downloaded from the Harris Stratex
website (www.harrisstratex.com), select the directory to where the software was
downloaded. Select the desired software pack and select Open.
5. The new software pack now appears on the software register, along with all of the
versions previously registered.
6. Select the Server tab. Two features are displayed:

Server IP Address and Concurrent Loads.
Ensure the Server IP Address is set to the server where the new software packs are
stored.
ProVision writes this IP address to the Eclipse radios. When the software download
is started, the radio uses this IP address as the one it looks for to find the new
software.

7. Select the number of concurrent loads using the Concurrent Loads slide bar.
The Concurrent Loads slide bar controls the number of software transfers that can
be performed at the same time. The number of which (1 - 15) is dependent on the
network’s bandwidth.
The Concurrent Loads slide bar allows you to tell ProVision how many radios it can
simultaneously load software to. If a network has 2000 radios, the ProVision
application can take quite a long time to load the software if it does so one radio at
a time. But if the Concurrent Loads is set to 10 (and if the network has the available
bandwidth) the time to load the software to all 2000 radios would be much faster.
8. Select OK to close the Software Loading Preferences window.
Part B: Load the Software onto the Eclipse Radios

When the software is loaded it resides in both the IDU and the ODU.
• For an Eclipse Node, the software resides in the NCC and in each ODU plug-in.
• For an Eclipse Terminal, the software resides in the IDU and ODU.
Load software from the Software Loading screen. You can open this screen from the
right-click menu in the Tree Viewer for a site or for a device, container or service. You
can also open it from the main menu.
The Software Loading screen identifies the following for each unit in ProVision:
Heading Description
Status If this item is blank for a unit, the unit is live and available to have
new software loaded. Problem icons are:
= fatal condition exists for the item, and software cannot be
loaded. Note that items with this status are grayed out.
= warning icon noting that there are problems with this item,
which may impact on software loading.
Object The name and type of the unit.
Container The IP name of the container.
614-330055-001 July 2009 3-115

Heading Description
Hop Count The distance in IP hops to the target device.
Software The version number of installed software.

Version(s)
The download process may take up to 30 minutes or longer, depending on the

network bandwidth, the number of concurrent loads, the number of radios being
loaded within the task, and the size of the software file being loaded.
Procedure:
Follow steps below to load the software onto the Eclipse radios.
1. From the menu bar, select Configuration > Software Loading. The Software Loading
window displays and it lists each Eclipse radio in the network, the container where
it is located, and its current software version.
2. Select the radios that are to have the software loaded. To more easily select the
radios by the container, select the column heading Object Container to sort the
radios by their location in the network.
• To load a group of radios that are listed sequentially, hold down the shift key
and select the first and last radio in the list.
• To load a group of radios that are not listed sequentially, hold down the ctrl key
and select each radio.
3. Select the Scheduled Activation check box to activate the software at a specific time.
If you do not select Scheduled Activation, the software activates immediately after
you click Load Selected Software.
4. To set the day and time for scheduled activation, highlight an item (for example, the
hour) in the text box and adjust it using the up or down arrows.
5. Select the software pack version to be loaded from the Version drop-down box. (The
version that was loaded in steps 2 and 3 appear in the list.)
6. Select the Load Selected Objects button to begin the download.
7. A ProVision message box appears. Select Yes to close the Software Table window
and open the Task Manager window.
Alternatively, select No to leave the Software Table window open. The Task Manger
window can be opened at anytime by selecting the Task Manager icon .
8. The Task Manager window appears. Select the + to view the objects that are being

updated. A bar chart indicates the progress of the download.
9. The download is complete when the bar chart indicates 100%. At that time, the
Activate buttons appear.
10. If you selected scheduled activation, instead of Activate buttons appearing, a timer
displays which counts down the amount of time before the scheduled activation
occurs.
Next Topic: Stage 2: Eclipse Software Activation Procedure on page 3-118
614-330055-001 July 2009 3-117

Stage 2: Eclipse Software Activation Procedure

The activation procedure is when Eclipse software, installed in, Stage 1: Eclipse
Software Load Procedure on page 3-113, is switched on.
To minimize the possible disruption of the network, it is recommended to begin by
activating the radios at the farthest points from the operations center. One reason is to
avoid the loss of visibility of a remote site in the event there is a software problem
affecting the normal link operations to or from the newly-loaded site. The other reason
is if there is a traffic-affecting problem, then by going first to a remote site, the least
amount of traffic is affected.
The activation process, specifically the reboot (software reset), may or

may not affect traffic. It depends on the software release, the update
destination within a node/terminal, and the hardware versions (plug-ins,
IDUs, ODUs). Always assume that traffic may be affected when
scheduling an activation.
Procedure
To activate the software after it has been loaded onto the radios, follow steps 1 through
6:
1. Select the Activate button to activate the software inside the Eclipse radio. The
Activate button changes to a Running button and an information icon appears.
2. Select the icon to open a pop-up window that tracks the activation process,
which is divided into three steps: activation, reboot, and verify.
Activation (<10 sec.): The Eclipse radio switches IDU (indoor unit) and ODU (out
door unit) switch to the new software. The messages “ODU1 OK” and “NCC OK”
indicate that the new software in both the ODU and the NCC, respectively, is now
activated.
Reboot (90 sec. to 2 min.): The Eclipse radio reboots (resets the software).
• When the message “Wait for reboot OK” appears, it indicates that the reboot is
complete. When the message “Wait for plug-ins OK” appears, it indicates that the
plug-ins (such as the RAC and DAC) are communicating with the NCC.

• It is only during the reboot step (which typically lasts less than 30 seconds) that
traffic can be affected. During the reboot, NMS visibility of the rebooted radio and
any downstream radios are lost.
Verify (2 to 5 min.): ProVision checks the to make sure the software version in the
IDU and ODU is the same as the version in the Software Table (page 3-115). The
message “versions OK” indicates the two versions are the same.
3. The process is complete when each of the activation steps indicates OK.
4. Right-click the task bar to open a pop-up window with additional functions.
• Details - Displays the Task Details window and lists the description, status, start,
and end time for the task. It also keeps a count of the goals within the task that
are errored and completed.
• Abort - Ends the task. This option is only available during the loading and
activation steps. If the task is aborted, both the task and its list of radios remain
in the Task Manger. The status for the task and each radio within the task is
listed as “Aborted.” Note that you cannot abort Activation.
• Delete - Deletes the task from the Task Manager. This option is available after
the task is complete and the task cannot be deleted while it is running. The task
remains in the Task Manager until you delete it or until you log out of the
ProVision Client application.
5. Right-click the individual radio within the task to open a right-click window with
614-330055-001 July 2009 3-119

additional functions.
• Results - Displays the results of the software loading and activation process for
the particular radio and lists the description, status, start, and end time for the
process.
• Error Report - Opens an Error Report window and lists any errors that occurred
during the software load process. This feature is only available if an error
actually occurs. (The message “Check Error Report” also appears next to the
radio’s name.)
6. Select the Close button to close the Task Manager window.
Related Topics:

Eclipse Node Licenses

Introduction
Eclipse Node licenses can be downloaded to individual Eclipse radios, one at a time or
in bulk, to provide RAC capacity greater than the default factory settings. The factory
default Eclipse Node license permits installation of up to six RACs, each with a
maximum capacity of 10xE1, or 16xDS1. Beyond this level, licenses must be purchased,
which provide an up-to capacity on a per RAC basis.
When you browse for new licenses, a copy of each license is stored in the folder:
\ProVisionServer\tomcat\webapps\ROOT\pv\repository\licenses. A copy of each
license is retained in this folder after the license is applied to the radio.
When you upgrade to a higher version of ProVision, the licenses that were
applied to the radios are unaffected. It is recommended to save a backup
copy of the repository folder with the license files, then migrate the folder
to the server once the new version of ProVision has been installed.
Contact one of the regional Harris Stratex Networks sales offices to purchase an
upgraded Eclipse Node license.
Procedure
To install Eclipse Node licenses:
1. When you receive the new Eclipse Node licenses, place them in a temporary folder
on the computer that serves as the ProVision client.
If you are loading 100+ licenses into the folder, this will take some time.
2. From the ProVision menu bar, select Configuration > Eclipse License. The Eclipse
License Table window opens. If you have not previously browsed for or applied any
new Eclipse Node licenses, the window is blank.
3. Select the Browse For New Licenses button. The Location For License File(s)
window opens. From this window, browse to the folder that contains the new
licenses.
614-330055-001 July 2009 3-121

4. Select the Open button. The licenses that were stored in the selected folder are
listed in the Eclipse License Table window. The license files are uploaded to the
ProVision server repository and are stored in the folder:
<pvroot>\ProVisionServer\tomcat\webapps\ROOT\pv\repository\licenses.
Each license file has a serial number that corresponds to a particular radio.
ProVision automatically matches the license to its radio and displays the result in
the Eclipse License Table.
Only the most recent license for a particular object displays in the Eclipse License
Table.
Note that the Application Date and Capabilities columns are blank.
5. Select one or more licenses and select the Apply License to Selected Objects button.
If you are loading a batch of radios, only select 10 - 20 radios at a time.

It takes approximately 5 minutes for ProVision to apply licenses to 10
Eclipse radios on a remote network. A Task Manager displays and shows
the status of the batch as the licenses are applied.
6. The licenses for the selected objects are applied to those objects.
Note that the Application Date and Capabilities columns are now populated.
Table 3-8 details the Eclipse License Table headings.
7. To load licenses against additional radios, repeat steps 4 through 6.

Table 3-8. The Eclipse License Table Headings
Heading Description
Object The name of the Eclipse Node.
Serial The serial number of the Eclipse Node.

Number
Filename The filename of the license.
Creation The data the license was created.

Date
Application The data the license was applied to the Eclipse Node.
Date
Capabilities The capabilities of the Eclipse Node made possible by the

newly-installed license. The notation lists the capability (E1,
DS1, E3, DS3, STM1, OC3, and so on). The numbers separated
by commas show the capacity for the slots.
For example, if the node lists its capability as: “E1, 75, 75, 75,
10, 10, 10” then the newly-applied license allows a capability of
75xE1 for any three RACs and a capability of 10xE1 for the
remaining 3 RACs.
Related Topics:
About Loading Eclipse Software Via ProVision on page 3-110
614-330055-001 July 2009 3-123

Eclipse and StarMAX Configuration Backup Export

Introduction
ProVision automatically saves a configuration backup file every 12 hours for any
Eclipse or StarMAX devices deployed in ProVision.
To do this, ProVision does the following:
• Detects whether configuration has changed by reading the last change time from the
Eclipse/StarMAX devices.
• If change is detected, FTPs the Eclipse/StarMAX configuration file to the backup
location on the ProVision server.
• Returns the last 5 copies of the configuration files onto the server.
• Saves this backup and uses it (for Eclipse, with Portal) to load onto new installations.
This process is run as a background process on a regular basis. You can export the
backup if it is required.
Procedure
To export the configuration backup files for an Eclipse/StarMAX device or node:
1. Select an Eclipse or StarMAX node or device in the Tree Viewer.
2. Right-click the node or device. In the right-click menu, select Configuration, then
select Export Configuration Backup.
3. The Export Configuration Backup screen displays.
4. This screen lists the available backup files for the node or device.
5. Select the most recent backup and click Export.
6. The Select Export Location screen displays. Navigate to the file folder where you

want to save the backup, and click Save.
7. The backup file is saved to this location.

8. The backup file for Eclipse can be used to load the radios using Portal. The backup
file for StarMAX can only be loaded back to the radio using a telnet command.
614-330055-001 July 2009 3-125


Chapter 4. Managing Events
This section introduces the tools for Managing events generated by the network devices
and by the system. This includes:
• Graphic views displaying the impact of events on the network, showing how much or
how little of your business is affected.
• Customizable Event Browsers, with event filtering and browser options that you can
save and reuse.
• Prefiltering events as they are received by ProVision, which reduces the number of
events processed and stored in the ProVision database.
• Scoreboard groups that provide a visual overview of how the network is functioning.
Where Do Events Come From?

Events are the result of the following:
• Traps that reflect a change in a device or an alarm generated in the device, which are
forwarded to ProVision.
• Responses by devices to presence polling from ProVision.
• Generated by ProVision to reflect operator activity, such as a device being deployed.
• Generated by ProVision to reflect a ProVision activity, such as resynchronizing with
a device.
Event data is stored in the ProVision database.
When Would I Manage Events?

Events are Managed when the events generated by devices on the network indicate that
there are problems. As a NOC operator or engineer, you need to quickly determine what
the problems are, where the problems are occurring and the fastest solutions. Filtering
and sorting these events, and reviewing their impact, enables you to effectively deal
with the large number of events being generated by devices on the network.
The topics covered in this section are:

• Event Management Processes on page 4-2
• Event Management Interdependencies on page 4-3
• Event Management Procedures on page 4-5
• Scoreboard Group Scenarios on page 4-78
614-330055-001 July 2009 4-1

Event Management Processes

Once you have a full understanding of the event management process, you can use the
ProVision event management tools to the fullest. This section describes the various
processes involved in managing events:
• Managing Event Processes in ProVision on page 4-2
• Setting Up Scoreboard Groups on page 4-4
• Customizing Event Browsers on page 4-4
Managing Event Processes in ProVision

Managing events involves two stages.
The first stage is to set up the event management tools:
• Services
• Customized Event Browsers
• Event Pre-Filtering
• Security Log
• Scoreboard Groups
The second stage is to actively monitor the Scoreboard groups and Event Browsers.
Monitoring also involves adding, changing and deleting Scoreboards, customized
Event Browsers, and event prefilters in response to events and problems in the
network.
Next Topic:
Suggested Steps for Managing Events

Suggested Steps for Managing Events

Identifying and prioritizing events is essential for managing events and identifying
problems. One problem can cause several events to be sent to ProVision. For example,
a trib cable left unconnected in a DXR 700 radio results in up to 15 events being
generated.
You also need to differentiate between events that require manual intervention and
temporary events that can affect the link such as RSL fade, which can be due to rain and
humidity.
You have several different options to identify and manage events.
Identify events from one of the following:
• Scoreboard Groups: graphs and charts identify the radios that are having events.
• The Tree Viewer: events are shown by the color code for a radio.
• The Map Viewer: again, events are shown by the color code for a radio.
Then, go to the Event Browser to view the details of events.
From the Event Browser, you can do the following for both local and remote radios:
• Filter events
• View event history and performance trends
• Open the Parent Device
For links, you can view the link submap, a link-related Event Browser, and
performance trends.
Next Topic:
Event Management Interdependencies
Event Management Interdependencies

Prerequisites
The following prerequisites enable you to manage events:
• The network radios must be physically installed and commissioned
• The radios must also be deployed and managed in ProVision
Dependencies
The Northbound Interface is dependant on events being managed within ProVision.
Next Topic:
Event Management Procedures on page 4-5
614-330055-001 July 2009 4-3

Setting Up Scoreboard Groups

A simple overview of how to create a Scoreboard group is to:
1. Create the base scoreboard group.
2. Populate the scoreboard group with scoreboards.
3. For each scoreboard, add Scoreboard Details and set up Event Filters.
4. Save the Scoreboard Group.
For detailed instructions, see Scoreboard Group Scenarios on page 4-78.
Next Topic:
Customizing Event Browsers
Customizing Event Browsers

A simple overview of how to steps involved to create a customized Event Browser is:
1. Open the Event Browser.
2. Set up the event browser Filters for date/time, objects, and containment.
3. Set up options for the details and values that will be visible in the Event Browser,
and the way entries will be sorted.
4. Save the Event Browser.
For detailed instructions, see Event Browsers on page 4-22.
Next Topic:
Event Management Procedures

Event Management Procedures

• Network Events on page 4-5
• Event Browsers on page 4-22
• Event Log Pre-Filtering on page 4-36
• Event Notification on page 4-51
• Logical Containers on page 4-69
• Logical Links on page 4-75
• Scoreboard Group Scenarios on page 4-78
Network Events
ProVision continuously monitors and reports on key network incidents, tracking the
ongoing status of devices running on your network.
Events are generated whenever monitored changes occur in the status of individual
network elements, their connections, or the network. Events range from providing
basic status information to notification of critical traffic impairing events.
Using the Event Browser, you can acknowledge events to indicate to other users that
the events are being worked on. When problems are resolved, events are cleared either
automatically by the system or manually, depending on event type. Until an event is
cleared, it continues to affect the state of the device that raised the event.
• Network Event States on page 4-6
• Viewing Network Events on page 4-7
• Viewing an Event’s Properties on page 4-8
• Acknowledging a Network Event on page 4-10
• Unacknowledging a Network Event on page 4-12
• Manually Clearing a Network Event on page 4-14
• Sleep Status for a Device on page 4-20
614-330055-001 July 2009 4-5

Network Event States

It is important to monitor, acknowledge, and, where necessary, escalate active events.
Of particular importance are events that affect communications traffic.
When escalating active events, it is important to know the different states that a
network event may have. These states are detailed in the table below.
Table 4-1. Network Event States
Event State Description
An unacknowledged, original event raised by a device. In the

unacknowledged state, the event is still active. These events are
displayed in the main Event Browser.
An operator has acknowledged an active event.

Note: These events are NOT displayed in the main Event Browser
under the default setting. You can view acknowledged,
clearing, and cleared events in a customized Event Browser.
An operator has unacknowledged a previously acknowledged

active event. These events are displayed in the main Event
Browser.
A clearing event, raised by the device.1
An operator manually cleared the original event.1
ProVision updates the original event to a cleared state.1
Related Topics:

Viewing Network Events

You can view network events from the following locations:
• Event browser
• Tree viewer (in the Physical, Logical Container, and Circuits tabs)
• Map viewer (in both the Physical and Flat maps)
• Object view (for Eclipse devices)
• Service table
• Scoreboards
All unacknowledged active events can be viewed in the main Event Browser.
You can also open a separate Event Browser window by:

• Selecting the New Event Browser icon from the tool bar, or
• Selecting Faults > Event Browser > New Event Browser from the menu bar.
To view events for a specific container, device, or Eclipse device (for example, a DAC or
a link), right-click the selected object then select Event Browser from the drop-down
menu.
For more information, see Event Browsers on page 4-22.
Related Topics:
614-330055-001 July 2009 4-7

Viewing an Event’s Properties
Introduction
You can view an event’s properties to gain information about a specific event. Event
properties allow you to answer the following questions about an event:
• Is the event equipment related, or due to weather or site conditions?
• Can you determine if the event is cleared by the device?
• Should you escalate the event to an engineer?
The figure below shows an example of an Event Properties window.
Figure 4-1. Event Properties Window
From the Information tab you can determine the following about the event:
• Event name, status and category
• Device that generated the event
• Date and time the event occurred
The Probable Cause tab details information about the event such as:
• Fault is intermittent or continuous
• Fault frequency
• Length of time there has been a problem
Select the Probable Cause tab to see the most likely reason for the event.
The Repair Action tab includes any recommended repair actions for the event.
Select the Help button to automatically open the online Help to the page that describes
the selected event. The help page contains a description of the event, a probable cause,
and a detailed list of recommended actions to correct the event.
The event states are described in Network Event States on page 4-6.

For some non-Eclipse devices, the Event Properties window is NOT linked to the help.
Instead, the Event Properties window has a Probable Cause tab, which displays a
description of the event and its probable cause.
Procedure
To view an event’s properties:
1. Within the main Event Browser or a customizable Event Browser, right-click an
event. In the right-click menu, select Event Properties.
2. The Event Properties window displays.
3. To view the probable cause of the event, select the Probable Cause tab.
4. To close the Event Properties window, select Close.
Related Topics:
614-330055-001 July 2009 4-9

Acknowledging a Network Event
Introduction
Acknowledging an event notifies other operators that the event is currently being
handled.
You can acknowledge an event from the following locations:
• The main Event Browser
• A separate Event Browser window
By default, all unacknowledged active events are displayed in the main Event Browser.
Acknowledging an event in the main Event Browser removes it from the browser.
In a customized Event Browser, an acknowledged event is indicated by a check mark,
as shown below.
Figure 4-2. Acknowledged events in a separate Event Browser window
Acknowledging in the Main Event Browser

To acknowledge one or more network events in the main Event Browser:
1. Select the event or events you wish to acknowledge. You can select multiple events
by holding down the ctrl or the shift key and selecting the required events.
2. Right-click the selected event. From the right-click menu, select Acknowledge.
3. ProVision automatically opens an Event Note dialog box. Enter any relevant

information pertaining to the event. Then select the OK button.
4. The selected event (or events) disappears from view after being acknowledged.
See the next section, Acknowledging in a Separate Event Browser, for instructions on
how to view acknowledged events.
Acknowledging in a Separate Event Browser

To acknowledge one or more network events in a separate Event Browser window:
1. Right-click the container or radio that is associated with the event you want to
acknowledge. Or, open a separate Event Browser window for multiple containers or
radios by holding down the ctrl or the shift key and selecting multiple items.
2. From the right-click menu, select Event Browser.
3. If you want to be able to view the acknowledged events, select the View Filters
icon. In the Filters window, select the Acknowledgement, Acknowledge and
Unacknowledge check boxes; then select the OK button. Acknowledged events will
appear with a check box beside them in the Event Browser window.
4. In the separate Event Browser window, select the event or events you wish to
acknowledge. You can select multiple events by holding down the ctrl or the shift
key and selecting the required events.
5. Right-click a selected event and, from the right-click menu, select Acknowledge.
information. Then click OK.
7. The selected event (or events) indicate that they have been acknowledged by the
check and notepad icons next to the event name.
Although the acknowledged event still appears in the separate Event Browser, the event
does not appear in the main Event Browser window.
Related Topics:
614-330055-001 July 2009 4-11

Unacknowledging a Network Event
Introduction
If you need to reassign a previously acknowledged event, the event can be
unacknowledged to make it available to other operators. More than one event can be
unacknowledged at a time.
Acknowledged events can be displayed in a customized Event Browser window and are
indicated with a check mark.
Procedure
To unacknowledge one or more network events:
1. In the Tree or Map Viewer, right-click the container or radio for which you want to
unacknowledge an event.
2. From the right-click menu, select Event Browser. An Event Browser window
displays.
3. In the Event Browser window, select the acknowledged event(s) to be
unacknowledged. The selected event(s) are highlighted.
4. Right-click and from the right-click menu, select Acknowledged.
information pertaining to the event. Then select the OK button.
6. In the Event Browser window, the event changes to unacknowledged and the check
is removed. The event is also displayed in the main Event Browser.
Related Topics:

Managing Event Notification Pop-Ups and Audio Alarms
Introduction
An event notification may include a pop-up screen and an audio alarm. An example of
the pop-up screen is below.
The Event Notification pop-up screen displays details of an event. To open this screen,
click on the Notification item on the lower left of the Event Browser.
Users can also configure events to display the pop-up automatically; see Add or Edit
Event Notification Rules on page 4-53.
The default setting for the pop-up is for it to appear above any other open screens.
The audio alarm is a sound that plays when the pop-up screen opens. If this alarm is on
the Continuous setting, it will play every 5 seconds until an event is acknowledged by a
user. You can stop the alarm sound by Acknowledging events. You can also mute the
audio alarm, temporarily. The alarm will stop playing for a specific event, but it will
play again for any new events that are set up for audio notification.
Procedure
1. To view Event Notification pop-ups, if they are not set up to display automatically,
click on the Notification item on the lower left of the screen.
2. The Event Notification displays.
3. To acknowledge all events, click on the Audio button and select Acknowledge All
from the small pop-up menu. All new Events will be acknowledged, and any audio
alarms will stop.
4. To change how the pop-up screen displays, deselect the Bring to Front check box.
5. To mute the audio alarm, click on the Audio button and select Mute from the small
pop-up menu.
6. The Audio button in the Event Notification screen, and the Audio icon on the Event
Browser, change to show that audio alarms are muted:
• Audio button on Mute=
• Audio icon on Mute=
614-330055-001 July 2009 4-13

Manually Clearing a Network Event
Introduction
Usually, events are raised, and then cleared by the device once the problem is resolved.
For example, a low or high BER or a change in the IDU or ODU temperature may
trigger an alarm. This process is called clear correlation.
Sometimes an event is raised but not cleared, for example, when a radio fails, no
clearing event occurs, and you must clear the event.
Manually clearing an event is not recommended as this results in ProVision not being
synchronized with the radio that generated the event. Even if the event has been
manually cleared, the problem may still remain. Where a radio or link is generating
many events and you know the technician is going to the site you can place the radio in
sleep status. For more information, refer to Sleep Status for a Device on page 4-20.
However, an example of where you might clear an event is when a problem requires a
field technician to visit the radio. The event has been acknowledged but the radio’s
event severity color is still red (indicating a critical event) and so any events from the
radio of the same or less severity would not be immediately obvious, especially from the
Scoreboard view. Clearing the event would return the radio to normal (green) and any
new events changes would be obvious.
Procedure
To manually clear an event from an Event Browser:
1. From any Event Browser window, select the event or events to be cleared.
2. Right-click the selected event or events and from the right-click menu select Clear.
The cleared events are removed from the browser window and the event summary
icons in the bottom right corner are updated.
Related Topics:
• Sleep Status for a Device on page 4-20
• Manually Resynchronize Alarms on page 4-15

Manually Resynchronize Alarms
Introduction
Certain devices do not provide ProVision with efficient alarm resynchronization. For
these devices, you need to use the Manual Alarm Resynchronization function to initiate
their alarm resynchronization.
These devices are:
• MegaStar
• TRuepoint 4000
Manual Alarm Resynchronization is also available for Constellation. Constellation
alarms are automatically resynchronized every six hours. The Manual Alarm
Resynchronization is available as an optional function.
Run the Manual Alarm Resynchronization after any maintenance.
TRuepoint 6400 requires a different procedure to enable its alarm

resynchronization; see Configure TRuepoint 6400 Alarm Resynchronization on
page 4-16.
Procedure
1. In ProVision, from the Tree Viewer or Map, right-click on a Constellation or
MegaStar device.
2. From the right-click menu, select Fault > Manual Alarm Resynchronization.
3. An event displays while the resynchronization is in process.
The manual alarm resynchronization may take some time to be fully

processed.
4. When the manual alarm resynchronization is complete, the event clears. The device
is now fully resynchronized.
Related Topics:
• Configure TRuepoint 6400 Alarm Resynchronization on page 4-16
614-330055-001 July 2009 4-15

Configure TRuepoint 6400 Alarm Resynchronization
Introduction
TRuepoint 6400 devices have two types of alarm resynchronization in ProVision:
• Summary Resynchronization- Always run from ProVision, as a basic support: only
updates the Major and Minor summary alarms for TRuepoint 6400.
• Full Resynchronization - Run when ProVision is enabled to connect directly to the
TRuepoint 6400 radio. ProVision then extracts the list of all active TRuepoint 6400
alarms and resynchronizes the data in ProVision for the radio.
Only one type of alarm synchronization can be in operation for a TRuepoint 6400. To
enable the Full Resynchronization, you need to set up ProVisionwith a minor change to
the Device Security Accounts settings. This is required for each TRuepoint 6400 that
requires resynchronization.
To set this up, you need the user name and password for the radio’s
WebCIT installation. Obtain this, and then follow the procedure below.
Procedure
1. In ProVision, from the Administration menu, select Device Security Accounts.
2. The Device Security Accounts screen displays. In the screen, locate the TRuepoint
6400 radio you want to configure for resynchronization. Right-click on the Device
Login column and select Edit Account Information.
3. The Edit Account Information screen displays. Select the Account Type of Device
Login. The Device Login values display.
4. Type in the WebCIT user name and password.
5. Click OK.

6. The radio now shows that it has been set up with a Device Login. In the Device
Security Accounts screen, click OK.
7. ProVision can now obtain the active alarm list for this TRuepoint 6400 radio from
WebCIT.
Related Topics:
• Manually Resynchronize Alarms on page 4-15
614-330055-001 July 2009 4-17

Customizing Event Names or Severity Levels
Introduction
For most devices, you can customize event names and severity levels through their craft
tool. However, some devices do not provide this function, neither through a craft tool
nor through their MIB interface. For these devices, ProVision provides an Event
Customization function. This enables you to customize the ProVision database name
and/or severity of external alarm inputs and outputs for these devices.
Using Event Customization, you can apply customization settings to a single device,
multiple devices of the same type, or all devices of a specific type.
From ProVision, you can customize event names and severity levels for the following
device types:
Device Customize Event Name? Customize Severity
Level?
Constellation Yes Yes
CAUs Yes Yes
DVAs Yes Yes
Generic Devices Yes Yes
LE3000 Yes No
MegaStar 155 Yes Yes
TRuepoint: 4000, No. Yes

4040, 5000, and Note: Event names must be
6400 customized from
WebCIT.
Procedure
To customize the name or severity level of an Event:
1. For Generic Devices only, ensure that the Event has already been generated. For
Generic Devices, ProVision needs an existing event record to customize. Check the
Event Browser for the Generic Device to see if the event you need is there.
2. Select the device or Container. Right-click on the object.
3. From the right-click menu, select Fault > Event Customization. The Event
Customization screen displays. This screen has a list of all events that can be

customized for the device.
4. If required, select the Object Type from the Object Type drop-down menu.
5. Select an event to customize by checking in the check box. For this event:
• Use the Customize Name field to enter a new name for the event. (Not available
for TRuepoint devices.)
• Use the Customize Severity drop-down menu to select a new severity level for
the event.
6. To apply all Event Customization changes to all objects, click the check box Apply
to all objects of this type.
7. After you have customized all the events you need, click OK.
8. The event customization is applied. These events will now display with your
customized name and severity levels.
Next Topic:
Sleep Status for a Device on page 4-20
614-330055-001 July 2009 4-19

Sleep Status for a Device
Introduction
In ProVision, you can change the status of a device from active to Sleep. When you set
a device to Sleep, the device is still active, but ProVision ignores all events from the
device. The device’s error status is maintained in the ProVision user interface and the
events prior to the device being put to sleep can still be viewed.
Normally, you set a device to Sleep when a field technician is at the site and is
performing maintenance on the device, or when there is heavy rain that is causing
temporary errors.
When a field technician is working on a device that may generate a large number of
faults you must set the device to Sleep rather than unmanage it. For more information,
see Managing SMA and DXR Devices on page 3-57.
ProVision does not wake a device. The device stays asleep until you wake it. Use Search
to find all sleeping devices.
Procedure
To set a single device to Sleep:
1. Right-click the device icon for the required radio.
2. Select Sleep in the right-click menu. A check mark should appear beside Sleep.
The device is set to the Sleep state and displays with the Sleep icon.
To wake a single device:
3. To take a device out of the Sleep state, right-click the device icon for the required
radio.
4. On the right-click menu, select the Sleep checkbox to disable it. The check mark
should disappear.
The Sleep icon is removed from the device.

To set the Sleep status of two or more devices:
1. Select the device icons for all the required radios. Then, right-click.
2. If all the devices have the same sleep status, Sleep displays in the right-click menu.
3. If some devices are set to Sleep and some are not, the right-click menu displays as
follows:
4. Set the status to Sleep or Wake for the devices. The status that you choose is applied
to all the devices.

For Eclipse IDU radios, child devices can be set to a sleep/wake state
independently of their parent device. To enable you to change the sleep/
wake state of the parent device, all the child devices must be in the same
sleep/wake state.
Related Topics:
614-330055-001 July 2009 4-21

Event Browsers
The Event Browser lists all events that occur in a network. The events displayed in the
Event Browser view are continually refreshed as events are received from the devices
on the network.
The main Event Browser is the bottom panel of the ProVision user interface and, by
default, displays all unacknowledged, active events on the entire network.
Figure 4-3. The Main Event Browser
You can also open a separate Event Browser window by:

• Selecting the New Event Browser icon from the tool bar, or
• Selecting Events > Event Browser > New Event Browser from the menu bar.
By default, ProVision displays “active” events that have assigned severities of “critical,”
“major,” “minor” and “warning”. This type of Event Browser, pictured in Figure 4-4,
can be customized to help you better monitor the network. See Customizing Event
Browsers on page 4-4.
Figure 4-4. A Separate Event Browser Window
You can also view the events for a specific container, device, or Eclipse element (for
example, a DAC or a link) by right-clicking the selected object (or objects) then
selecting Event Browser from the drop-down menu.
• Saving an Event Browser View on page 4-24
• Viewing a Saved Event Browser on page 4-25
• Customizing an Event Browser on page 4-26
• Event Browser Filter Values on page 4-27
• Changing Event Browser Options on page 4-29

• Event Browser Option Values on page 4-30

• Deleting an Event Browser on page 4-33
• Saving Event Browser Contents on page 4-34
• Printing Event Browser Contents on page 4-35
For information on viewing and managing network events, see Network Events on
page 4-5.
614-330055-001 July 2009 4-23

Saving an Event Browser View
Introduction
Saving the Event Browser view lets you keep the customized settings for future use,
saving you time an effort. You can also customize the settings of the Event Browser for
your specific situation.
See Customizing an Event Browser on page 4-26 for more information.
Procedure
To save an Event Browser view:
1. Open an Event Browser view:
• To open an Event Browser for the entire network, select the new Event Browser
icon from the tool bar; or select Faults > Event Browser > New Event Browser
from the menu bar.
• To open an Event Browser for selected object(s), highlight the selected object(s),
then right-click the objects and select Event Browser from the drop-down menu.
A separate Event Browser window displays.
2. Select File > Save As... The Save As window displays.
3. In the Name field at the bottom of the window, type a descriptive title for the Event
Browser view, for example, XP4 Critical Events.
This name displays when saved Event Browsers are viewed from the tool bar. Your
name is added to the Event Browser identifying it as yours. However, other
operators can still use it.
4. Select Save. The Event Browser view is saved and the browser window title is
updated to reflect the new name.
Related Topics:

Viewing a Saved Event Browser
Introduction
Saved Event Browsers are accessed from the main user interface Event Browser. These
are Event Browser views that you have customized and saved.
Procedure
To view a saved Event Browser:
1. From the main user interface tool bar, select the Event Browser drop-down arrow
. Select the required saved Event Browser view from the list.
2. You can also select Fault > Event Browser from the menu bar and then select the
required saved Event Browser from the list.
Related Topics:
614-330055-001 July 2009 4-25

Customizing an Event Browser
Introduction
You can change an Event Browser’s name and description. You can also change the
maximum number of events displayed, what fields are displayed, and the display order
by applying a filter.
When you apply a filter to an Event Browser, only those events you wish to view are
displayed. ProVision has default filters to ensure the Event Browser is not filled with
minor events, so you can locate events that have a more serious impact on the network.
Procedure
To apply filters in an Event Browser:
1. Open a separate Event Browser window:
• Open a new Event Browser by selecting the new Event Browser icon from
the tool bar.
• Open a saved Event Browser by selecting the Event Browser drop-down
arrow from the tool bar and then selecting a saved Event Browser from the list.
• Open an Event Browser for selected object(s) by highlighting the selected
object(s), then right-clicking the objects and selecting Event Browser from the
drop-down menu.
An Event Browser window displays.
2. On the tool bar, select the View Filters icon. The Filters window displays.
See the table below for detailed filter value information.

3. Make the required filter changes and select OK.
The Event Browser reflects the filter changes immediately.
4. To save your changes, from the menu bar select File > Save.
5. To close the Event Browser, select the X in the top right corner.

Event Browser Filter Values
Filter Setting Definition
Simple Tab State By default, only active events are

displayed in an Event Browser.
To view cleared events in an Event
Browser view, select the Cleared
checkbox.
You might want to display cleared
events to see how often a particular
event is being raised and cleared.
Acknowledgement
By default, events are displayed
whether they are acknowledged or
unacknowledged.
Severity By default, the events of the following

severity are filtered for:
• Critical
• Major
• Minor
• Warning.
To view Informational and/or Normal
events in an Event Browser view, select
the associated checkbox.
Category By default, all event categories are

displayed.
To enable specific category filtering,
select the Category checkbox. Then
select the categories you are interested
in. All other category types are not
displayed.
Date / Time By default, there is no filtering on date and time.

To activate the date and time filter, select the Date / Time
checkbox.
To enable the filter’s start date and time:
1. Select the Start checkbox.
2. Select the associated drop-down arrow.
3. From the calendar displayed select the required month
and day.
4. Change the time, if required.
To enable the filter’s end date and time, repeat the above
four steps for the filter End date.
614-330055-001 July 2009 4-27

Filter Setting Definition
Objects By default, there is no filtering on object types, and events

for all object types are displayed.
To filter for events generated by specific object types:
• Select the Object Type checkbox.
• Select the checkboxes of the object types required.
Only events generated by the selected object types are
displayed in the Event Browser.
Text By default there are no text filters applied to the event

descriptions.
To apply a filter for an event description:
• Select the Text Filter checkbox.
• Select Add.
• Type the filter text in the Text field.
By default the Include checkbox is checked.
• To exclude events that contain the filter text, select the
Exclude checkbox.
Containment By default, there are no containment filters applied.

This is the most useful and flexible filter setting. You can filter
for all events generated from the general (for example, a
region) to the specific (for example, from an Eclipse radio’s
ODU).
To filter for events generated by a specific object or objects:
• Select the Objects checkbox.
• Expand the tree structure, and select the checkbox of a
specific object or objects.
Related Topics:

Changing Event Browser Options
Introduction
You can set the following Event Browser options:
• The description of the Event Browser view.
• The maximum number of events displayed in this particular browser. By default, the
number is 1000 events.
• The fields displayed in the browser window.
• The order in which the events are displayed. By default, the events are displayed in
descending date and time order.
Selecting the title bar of a column changes how the events in the browser
are sorted.
Procedure
To change Event Browser options:
the tool bar.
drop-down menu. An Event Browser window displays.
2. On the Tool bar, select the Browser Options icon.
The Browser Options window displays.
See the table below for detailed information on each of the fields.
614-330055-001 July 2009 4-29

3. Make the required changes and select OK.

The Event Browser window reflects the browser option changes.
Event Browser Option Values
Tab Option Description

Details Tab (shown above)
Name The name of the Event Browser view.
Description You can enter information about this
Event Browser view (for example, the
filters that were applied, the sort order,
etc.) so that another operator can quickly
determine the settings you have applied.
Highlight Severity When Highlight Severity is enabled, each

row in this Event Browser view is
highlighted in the event’s severity color.
To enable the Highlight Severity option,
select the checkbox.
Max Displayed Events Sets the maximum number of events that

can be displayed in this Event Browser
window.
To change the maximum displayed
events, move the slider.
The maximum number of events that can
be displayed is 15000.
Fields Tab
You can change which fields are displayed in the Event Browser.
To make a field visible in the Event Browser,:
• Double-click the required field in the Hidden column to move it
to the Visible column.
• OR select the required field (or multiple fields) in the Hidden
column then select to move it to the Visible column.
To remove a field from the Event Browser:
• Double-click the required field in the Visible column to move it
to the Hidden column.
• OR select the required field (or multiple fields) in the Visible
column then select to move it to the Hidden column.


Sorting Tab
The events are displayed according to the sorting criteria you
choose.
The three sort criteria enable you to be very specific in your sorting
selection. For example, you could filter on date and time, object,
and event severity.
To change the order in which events are displayed in the Event
Browser:
• Select the Sort Entries By drop-down arrow.
• From the list displayed, select the field on which to sort.
• Select the radio button of the sort order: ascending or
descending.
• Repeat the above two steps if further sort options are required.
Note: If a Field value is Hidden, you will not be able to Sort
entries by that value in the Event Browser. Make sure all
the Field options you require are visible.
Event Sort Options Description
Acknowledged Events are sorted by acknowledged

events.
Active Status Events are sorted by active status.
Category Events are sorted alphabetically by

category description, for example:
communications, equipment, quality of
service.
Cleared Date/ Time Events are sorted by the date and time
when they were Cleared. This value is
Hidden by default.
Event Events are sorted alphabetically by the

event description.
IP Address Events are sorted numerically by the IP

address. For TNet devices, the IP address
field lists its Proxy parent’s IP address,
followed by its subnet number.
Notes Events are sorted by the notes icon.

Notes are only applicable to the Eclipse
devices. A notes icon displays in the notes
column only when a note has been
created by the user.
Object Events are sorted by the device name, in

alphabetical order.
Object Path Events are sorted alphabetically by the

device’s path.
Object Type Events are sorted alphabetically by the

object type, for example: Altium ADR,
Eclipse DAC, Eclipse INU.
614-330055-001 July 2009 4-31

Raised Date/ Time Events are sorted by the date and time
when they were raised.
Severity Events are sorted by the event severity

color-coding.
User Events are sorted by the user associated

with that event. Note that when a field
technician is logged into an Eclipse radio
via Portal, any events they generate are
tagged with their user name.
Related Topics:

Deleting an Event Browser
Introduction
Delete an Event Browser when it is no longer required; for example, the events being
filtered for have been resolved or are no longer occurring.
Procedure
To delete an Event Browser view:
1. From the tool bar, select the Event Browser drop-down arrow .
A list of the saved Event Browsers displays.
2. Highlight the Event Browser to be deleted.
The Event Browser window displays.
3. From the menu bar, select File > Delete... The Delete Event Browser window
displays.
4. Highlight the Event Browser to be deleted. The Delete button is enabled.

5. Select Delete. A warning message displays requesting confirmation of your delete
command.
6. To delete the Event Browser, select Yes.

7. To close the Delete Event Browser window, select Close.
Related Topics:
614-330055-001 July 2009 4-33

Saving Event Browser Contents
Introduction
Saving the contents of an Event Browser to a file gives you an overview of the events at
a particular time. The file is saved as a .txt file. It can be imported into spreadsheet
software to present a graphical view of the historical data.
The saved data reflects your current Event Browser view. You may want to make
changes to the Event Browser, adding additional data, before you save it. See
Customizing Event Browsers on page 4-4.
You might use this file as a comparison to a previously saved file, or view the file later
on when attempting to troubleshoot a set of events.
Procedure
To save the contents of an Event Browser to file:
the tool bar.
drop-down menu.
2. From the menu bar select File > Save to File...

The Save window displays.
3. Browse the directory structure for the folder to save the file.
4. In the File name: field, type in a name for the event log.
5. Select the Files of type drop-down arrow and select the file type.
6. To save the file, select Save.
Related Topics:
• Customizing Event Browsers on page 4-4

Printing Event Browser Contents
Introduction
You can print the contents of an Event Browser for reporting purposes or to
troubleshoot events.
Procedure
To print Event Browser contents:
the tool bar.
drop-down menu.
2. From the menu bar select File > Print...
The Print window displays.
3. Select the printer, set the print range and properties.
4. Select OK to print.
Related Topics:
614-330055-001 July 2009 4-35

Event Log Pre-Filtering

An Event Browser window can become overloaded with hundreds of events, making
sorting through the events a difficult task. This topic describes how to view, create, and
edit pre-filter criteria, which stops matching events from reaching the system. Any
events matching the specified pre-filter criteria are not processed by ProVision. Event
pre-filtering reduces the number of events being fully processed and increases system
performance. Event pre-filters are effective immediately and remain in effect until they
are disabled or deleted.
• Viewing Event Log Pre-Filtering on page 4-39
• Adding An Event Log Pre-Filter at the Root Level on page 4-40
• Adding an Event Pre-filter at an Object Level on page 4-43
• Adding an Event Pre-Filter Via an Event Browser on page 4-44
• Modifying An Event Log Pre-Filter on page 4-45
• Deleting An Event Log Pre-Filter on page 4-47
Why Use Event Pre-filtering?

At the root level (network wide) you can filter out events on a per device basis. This
stops non-essential events entering the system. For example, on Altium radios if ATPC
is enabled an event is generated each time the radio switches between ATPC on and off.
These events do not relate to the performance of the radio nor the communications
traffic. They are not necessary: they are events that can be pre-filtered.
At the radio level, if there is a problem, for example, faulty equipment or an antenna
out of alignment resulting in events being generated and you know a field technician is
going out to the radio to fix the problem, then you can pre-filter for these events for this
radio. However, you must remove the pre-filter once the problem has been fixed.
How Does Event Pre-filtering Work?

A pre-filter applied at a parent level in the hierarchy is automatically applied to child
objects that are included in the criteria. Figure 4-5 on page 4-37 shows an example of
how a pre-filter set at the root level (Southern North Island), for XP4 radios is applied
to all XP4 radios, and shown in this example, the Waikanae XP4 radio. The blank Self
tab displayed for the Waikanae XP4 radio indicates there are no pre-filters applied
directly to the selected object. The Parents tab has the active filters displayed.

Figure 4-5. Example of a Pre-Filter
You can pre-filter events from a specific device or device component. The figure below
shows an example of a pre-filter applied to an Eclipse Node ODU.
Figure 4-6. ODU Pre-filter
614-330055-001 July 2009 4-37

Objects That Can Be Pre-Filtered

Table 4-2. Objects / Events that can be Pre-Filtered
Objects/Events Description
Root Object/ Pre-filters added at the root level, apply to the entire
Network Container network, and any events received that match the
pre-filter criteria are rejected.
You can pre-filter events created by network devices and
certain events created by ProVision. ProVision creates
performance events, for example when 15-minute data
collection is enabled, these events can be pre-filtered
from the system.
These performance events are part of the platform event
group which can only be pre-filtered at the root level.
You can view existing pre-filters and add new pre-filters.
Container Pre-filters added at a container level are only applied to

events from devices that are children of the container.
Any events for these devices that match the pre-filter
criteria are rejected.
You can view existing pre-filters for the container and also
for the parent object.
Radios and Eclipse You can view or add pre-filters for the selected radio or
Radio plug-ins the Eclipse plug-in. You can view pre-filters for the parent
object.
Events You can add this specific event to the pre-filter for the
device it pertains to. You can also view any proposed
pre-filters that were set up at the radio or Eclipse radio
plug-ins level.

Viewing Event Log Pre-Filtering
Introduction
An object that has pre-filtering applied is indicated in the Tree and Map Viewers, by the
icon. You can view what pre-filters have been added directly to an object or to its
parents.
Procedure
To view event log pre-filtering:
1. In the Tree or Map Viewer, right-click the object with the icon.
2. From the right-click menu, select Fault - Event Pre-Filter.
The Event Pre-Filter window displays.
3. To view pre-filters applied to parent objects, select the Parents tab.

4. To close the Event Pre-Filter window, select Cancel.
Related Topics:
614-330055-001 July 2009 4-39

Adding An Event Log Pre-Filter at the Root Level
Introduction
Pre-filters added at the root level apply to the entire network. Any events received that
match the pre-filter criteria are rejected by ProVision. You can pre-filter for events
from network devices and from ProVision, itself.
Pre-filtering at the various object levels is detailed in Viewing Event Log Pre-Filtering
on page 4-39.
There are no default pre-filters in ProVision.The events pre-filter you define can be
enabled immediately or left inactive and then enabled at a later date.
Procedure
To add event pre-filters, at the root level:
1. From the main user interface, tool bar select Faults -Events Pre-Filter. The Event
Pre-Filter window displays.
2. From the Object Type drop-down list, select the type of device to which the
pre-filter is to apply.
3. To display the types of events associated with the selected object, on the Self tab,

select Add. The Add Pre-Filtered Events window displays.
4. Select the check boxes of the event or events required.

5. To accept the events selected, select OK.
The Self tab is updated to display the events selected for the pre-filter.
6. To enable the pre-filter, select the Enable Pre-filter check box.

7. To accept the pre-filter changes, select OK.
Within the Tree and Map Viewers, all radios or Eclipse plug-ins affected by the
pre-filter are displayed with the icon.
To pre-filter Platform events:

1. From the main user interface, tool bar select Events > Events Pre-Filter.
The Event Pre-Filter window displays.
614-330055-001 July 2009 4-41

2. Select the Platform tab.

The Platform tab displays.
3. To enable pre-filtering of Performance events, select the Performance checkbox.

4. Select OK.
Related Topics:

Adding an Event Pre-filter at an Object Level
Introduction
This applies to adding an event pre-filter at the Container, Radio, and Eclipse Plug-in
level.
See Table 4-2, “Objects / Events that can be Pre-Filtered,” on page 38 for a list of object
levels at which you can add a pre-filter.
Procedure
To add an event pre-filter at a object level:
1. In the Tree Viewer or Map Viewer, right-click the container, radio, Eclipse link, or
Eclipse plug-in.
2. From the right-click menu, select Fault -Event Pre-Filter. The Event Pre-Filter
window displays.
For all devices, with the exception of the Eclipse radio and Eclipse Link, the Object
Type is set for the type of radio or plug-in previously selected and cannot be
changed.
3. If you have selected an Eclipse radio, then from the Object Type drop-down list,
select either All Types or the specific component, or plug-in required.
4. To display the type of events associated with the selected object, select Add.
The Add Pre-Filtered Events window displays.
5. To select the event or events required, select the event checkboxes.
614-330055-001 July 2009 4-43

6. To accept the events selected, select OK.

The Self tab is updated to display the events selected for the pre-filter.
7. To enable the pre-filter, select the Enable Pre-filter checkbox.

8. To accept the pre-filter, select OK.
Within the Tree and Map Viewers, all the devices affected by the pre-filter are
displayed with the icon.
Related Topics:
Adding an Event Pre-Filter Via an Event Browser
Introduction
This applies a pre-filter to a specific type of event for a specific device. When you select
this option, the event to be pre-filtered and any other enabled pre-filtered events for
this specific device are displayed, and the event pre-filter is automatically enabled.
Procedure
To add an event from an Event Browser for a specific object, as a pre-filter criteria:
1. In the Event Browser, right-click the required event.

2. From the right-click menu, select the Add to Pre-filter option.

The Add to Pre-Filter <object> window displays, showing the selected event and
any enabled events that are already being pre-filtered for this specific object.
3. To accept pre-filtering for the event, select OK.
Related Topics:
Modifying An Event Log Pre-Filter
Introduction
After you have created an event pre-filter you can add and remove events to and from
the filter.
Disabled event pre-filters are ignored by the system until you enable them, then
ProVision starts pre-filtering any events for the object(s) that meet the pre-filter
criteria.
Procedure
To modify an event pre-filter at a container, radio, Eclipse link, or Eclipse plug-in level:
1. In the Tree Viewer or Map Viewer, right-click the item that has an event log
pre-filter.
2. From the right-click menu, select Fault - Event Pre-Filter. The Event Pre-Filter
614-330055-001 July 2009 4-45

window displays showing the pre-filter events for the selected object.
3. To add more events to the pre-filter select Add. The Add Pre-Filtered Events
window displays.
4. Select the checkboxes of the event or events required, and select OK.
The Self tab displays showing the pre-filter events selected.
5. To remove events from the pre-filter, on the Self tab, select the events no longer
required and select Remove.
6. To enable or disable the event pre-filter, on the Self tab, select the Enable Pre-Filter
checkbox.
7. To save your changes, select OK.
Related Topics:

Deleting An Event Log Pre-Filter
Introduction
You can delete an event log pre-filter when the problem causing the event has been
fixed or no longer exists.
To delete an event log pre-filter, you must select the object to which the pre-filer has
been applied. You cannot delete a parent object’s pre-filters from a child object. For
example, in the figure below, pre-filters set for XP4 radios, at the root level (Southern
North Island) cannot be deleted at the XP4 radio level, for example Waikanae.
Figure 4-7. Deleting Pre-Filters
When an event pre-filter is deleted the icon is no longer displayed beside the
previously pre-filtered object.
614-330055-001 July 2009 4-47

Procedure
To delete an event pre-filter at a container, radio, Eclipse link, or Eclipse plug-in level:
1. In the Tree Viewer or Map Viewer, right-click the container, radio, Eclipse link or
Eclipse plug-in that has an event log pre-filter.
2. From the right-click menu, select Fault - Event Pre-Filter.
The Event Pre-Filter window displays showing the pre-filter events for the selected
object.
3. On the Self tab, select the events no longer required for pre-filtering.
4. Select Remove.
The Enable Pre-filter option is greyed out.
5. To save your changes, select OK.
Related Topics:

Security Log
Introduction
The Security Log provides a record of user activity on ProVision. Whenever a user
makes a change or performs an operation in ProVision, an event for the change is added
to the Security Log. This tracks user change-related events and enables a ProVision
Administrator to identify which user is responsible for any activity on ProVision.
The Security Log records user activity for the following:
• The Physical Root level of ProVision (as shown below in the Tree Viewer)
• The ProVision Manager (as shown below in the Tree Viewer) (
• Regions, Sites, and Containers

• The following devices:
• Altium
• Eclipse
• LE3000
• TRuepoint 4000 and 5000
• Velox
Procedure
To view or change the Security Log for a device:
1. In the Tree Viewer or Map Viewer, right-click the device or object.
2. From the right-click menu, select Fault - Security Log.
The Security Log window displays showing the user change events:
3. The Security Log displays the following event data:
614-330055-001 July 2009 4-49

• Event - Event type.

• Object - Object type.
• User - The user responsible for the event.
• Notes (Text) - Text notes about the event, the client IP/PC user name, and the
affected device.
• Raised Date and Time - Date and time of the event.
4. To change the data displayed in the Security Log, you can:
• Change the Browser options - see Changing Event Browser Options on page 4-29
• Change the Filter values - see Modifying An Event Log Pre-Filter on page 4-45
• Change the Scoreboard options - see About Scoreboard Group Scenarios on
page 4-78

Event Notification
Event notification enables ProVision to notify you when selected events occur within
the network. This feature allows network administrators to stay informed and to
respond quickly to problems, minimizing system downtime.
The user sets up Event Notifications. These send messages when specific events take
place in the ProVision system. The Event Notifications are set up when you create an
Event Notification Rule for each type of event. For example, when ProVision detects a
“radio path down” event, an associated Event Notification Rule could send an email to
the NOC engineer.
ProVision supports the following types of event notification:
• Email = ProVision can send an email to a specified address when Events take place.
Different Event Notifications can be set up to send emails to different addresses.
Using an email notification is also the way to send a text message to a cell phone,
using an email address linked to the cell phone.
• ProVision Client pop-up message = When an event is identified, a text message
displays in a window in the ProVision user interface.
• ProVision Client audio message = When an event is identified, the ProVision
computer makes a distinctive sound.
• Script execution = When an event is identified, ProVision can send a message to the
main server, to trigger an external program to run a script.
The best way to use the event notification feature is to set up Event Notification for
specific events that have a high priority for your network application.
This section provides instructions for setting event notification preferences and adding
event notification rules. It also includes a section that summarizes all the requirements
to set up an email event notification.
• Set the Server Notification Preferences on page 4-52
• Add or Edit Event Notification Rules on page 4-53
• Delete an Event Notification Rule on page 4-56
• Configuring the Notification Rule on page 4-57
• Set Up an Email Event Notification on page 4-60
• Set Up a Pop-Up Message Notification on page 4-63
• Set Up an Audio Alarm Notification on page 4-65
• Set Up Script Execution on Event Notification on page 4-66
614-330055-001 July 2009 4-51

Set the Server Notification Preferences

If you want ProVision to send email notifications, you must set up the Server
Notification Preferences values. In this screen, you note the IP address of your email
server, used when ProVision sends an email message about an event, and a
user-supplied name that appears on the email when ProVision sends the message.
After you have set this up, your system can send email notifications. See Set Up an
Email Event Notification on page 4-60 for more details.
Procedure
To set the event notification preferences for the server:
1. From the Menu Bar, select Administration > Email Server Configuration.
The Server Notifications Preferences window displays.
2. In the Mail (SMTP) Server text box, enter the IP address or name of your email
server.
3. Your mail server set up determines if you need the Use authentication feature:
• If email notifications will be sent within your own company’s mail server, leave
the Use authentication unchecked.
• If email notifications will be sent outside your own company’s mail server, select
the Use authentication checkbox. Also, enter the Username and Password of your
mail server. See your mail server’s administrator for a username and password.
4. In the Email “From” Address text box, enter the text that you would like to appear
in the email messages as the sender. In the example above, the messages have the
name “ProVision” as the sender.
5. Select the Apply button to save the changes while keeping the Server Notification
Preferences window open.
6. You can test the Server preferences by sending an email to the mailbox specified in
the above steps. To do this, click the Test Email button. (Note: the Test Email button
remains inactive until the Apply button is selected.)
7. Select OK to close the Server Notification Preferences window.
8. Select Close to close the Server Notification Preferences window without saving
any changes.
Related Topics:

Add or Edit Event Notification Rules

Adding an event notification rule sets up ProVision to identify specified events. You can
then set up notifications for the events. A notification can be set up to send an email
message to a specified email address. It can also be set up to run a shell script for a
batch file.
You can edit an Event Notification rule. This can change the actions done for an event
notification. You can also update the email to which a notification is sent for an event.
Procedure
To add an event notification rule:
1. From the Menu Bar, select Faults > Event Notifications.
The Event Notification Rules window displays.
2. Select the Add button.
A new rule appears in the window. You need to enter values for this to create a new
Event for notifications.
3. Place the cursor in the Name column and enter a description of the event. The text
entered here is used as the subject line in the email message.
4. In the Action column, select an action from the drop-down menu to occur when the
event takes place.
• Select none if you want no action to occur when the event takes place. This
setting is useful if you want to temporarily “turn off” the notification for an
event.
• Select Edit actions... to create/edit/delete an action.
614-330055-001 July 2009 4-53

5. If Edit actions... is selected, the Event Notification Action window displays.

A new, undefined action appears in the window.
entered here is used as the message for any email messages about this event
8. In the Type column you can select either Email or Run Script.
9. Select Email if you want ProVision to notify you via email when the event occurs. In
the Destination column, enter the email address of the user to be notified when the
event takes place.
10. Select Run Script if you want to run a shell script for a batch file when the event
occurs. In the Destination column, enter the file name for the batch file. For more
details, see Set Up Script Execution on Event Notification on page 4-66.
11. Select OK to save the action.
The Event Notification Actions window is closed. Note that the action that was just
created now appears in the drop-down menu on the Event Notification Rules
window:
To delete an action, highlight the action and then select the Remove
button.

12. Select the Edit Rule button. The Notification Rule window displays.
13. Select OK to save the configuration and close the Notification Rule window.
14. In the Event Notification Rules window, select OK to save the newly-created rule.
15. To edit an Event Notification rule, again open the Event Notification Rules window.
16. Select the rule to be edited. You can type changes to the Name column. In the Action
column, you can select Edit actions... to create/edit/delete an action. Select the Edit
Rule button to edit the notification rule values.
17. Select OK to save the changes and close the Notification Rule window.
18. In the Event Notification Rules window, select OK to save the changes to the
notification rule.
Related Topics:
614-330055-001 July 2009 4-55

Delete an Event Notification Rule

To delete an event notification rule:
1. From the Menu Bar, select Faults > Event Notification.
The Event Notifications window displays.
2. Select the rule to be deleted.

3. Select the Remove button.
The selected rule is removed from the Event Notification Rules window.
Related Topics:

Configuring the Notification Rule

The table below describes how to configure specific values for a new or existing
notification rule. Select a tab to display that tab’s values Select OK to save the settings
for the notification rule.
Notification Rule Tab Description
Notification Tab: Match Count

Enter the number of times the event must occur
before ProVision sends the notification.
For example, if the rule is fan failure and the match
count is set to 5, ProVision must wait until there are
five occurrences of fan failure before it sends the
notification.
Retrigger Delay (seconds)

Enter the length of time, after an event occurs,
ProVision must wait before sending the notification
for a subsequent occurrence of this event. Any
defined events that occur during this time period are
buffered.
• If the event is resolved, then the buffered events
are ignored.
• If the event is not resolved, and the retrigger delay
time has elapsed, then the buffered notification(s)
are sent.
The Match Count and Retrigger Delay features are
useful to prevent ProVision from sending an
unmanageable number of emails or running an
unmanageable number of scripts.
Notify on Clear
When this is selected, ProVision triggers the
notification (sends an email or runs the shell script)
when the event has been cleared.
For example, when a traffic loss condition occurs,
ProVision sends a notification email. And when the
traffic loss condition clears (that is, when the traffic
is restored) ProVision sends a notification email
clarifying that the problem is cleared.
Always Retrigger
When the Always Retrgger checkbox is selected,
ProVision always retriggers the rule when the event
occurs.
For example, when a critical event occurs, ProVision
sends a notification email. When another
occurrence of the same critical event takes place,
ProVision sends another notification email.
614-330055-001 July 2009 4-57

Simple Tab: Acknowledgement

Select the Acknowledgement box to allow
acknowledged and unacknowledged events as
criteria for the notification.
Severity
Select the Severity box to allow the different levels
of severity to be used as criteria for the notification
rule: Critical, Warning, Major, Minor, Information,
or Normal.
Category
Select the Category box to allow these five different
categories to be used as criteria for the notification
rule: Communications, Equipment, Environmental,
Processing Error, or Quality of Service.
These are industry standards to categorize events
that occur in microwave radio networking. When a
Category item is selected, ProVision automatically
assigns these categories to the specified events.
For example, you may want to use the “Quality of
Service” category for notification rules if you
wanted to save data to do a report on quality
control in your network.
Date / Time Tab: Date / Time

The Date/Time feature is not supported as a criteria
for notification rules in the current version of
ProVision.
Objects Tab: Object Type

Select the Object Type box to allow specific types of
radios and plug-ins as criteria for the notification
rule.
Select the box next to the object type(s) that you
wish to include as criteria for the notification rule.

Text Tab: Text Filter

The text filter feature can be useful if you have several
radios in your network that share a name (Name01,
Name02, Name03...). Generally, these radios are
linked or share important characteristics. The text filter
feature allows you to quickly include all these radios in
the notification rule.
To include text as a criteria from the notification rule:
1. Select the Text Filter box to allow text as a criteria
for the notification rule.
2. Select the Add button to create a new text filter.
3. Enter the required text in the Text column.
4. Select Include to include the text as criteria for the
notification rule. Or, select Exclude to remove the
text as criteria.
5. To remove an item from the list, select the item and
select the Remove button
Containment Tab: Objects

Select the Objects box to allow user-defined objects
as criteria for the notification rule.
Select the + next to a container to view objects
within that container.
Select the box next to the object(s) that you wish to
include for the notification rule.
Related Topics
614-330055-001 July 2009 4-59

Set Up an Email Event Notification

This set of instructions describes all the steps required, from start to finish, to set up an
email notification. Some of the information here is also provided in the sections about
how to Set the Server Notification Preferences on page 4-52 and Add or Edit Event
Notification Rules on page 4-53. It is collected here to help users understand how to set
up this type of notification.
First, make sure that ProVision is set up with the Server event notification preferences.
This allows ProVision to communicate with your Server’s web connection, to send
emails. Then, set up the event notification Rules.
Before you begin, you will need the following information:
• Your mail server’s IP address, user name, and password.
• The names and email addresses of people who will be receiving email events.
Some e-mail servers require “secure” authentication. The ProVision

Event Notification does not support secure authentication.
The default event notification email is provision@<yourcompanyname>.com
You may wish to have your IT managers create this email address.
Procedure
1. From the Menu Bar, select Administration > Email Server Configuration.
The Server Notifications Preferences window displays.
2. Have server values been entered in this screen? If they have, go to step 8. If they
have not, go to step 3.
3. In the Mail (SMTP) Server text box, enter the IP address of your email server.
4. Your mail server set up determines if you need to apply the Use authentication
feature:
• If email notifications will be sent within your own company’s mail server, leave
the Use authentication unchecked.
• If your email notifications will be sent outside your own company’s mail server,
select the Use authentication checkbox. Also, enter the Username and Password
of your mail server. See your mail server’s administrator for the proper
username and password.
5. In the Email “From” Address text box, enter the text that you would like to appear

in the email messages as the sender. In the example above, the messages have the
name “ProVision” as the sender.
6. Select the Apply button to save the changes while keeping the Server Notification
Preferences window open.
7. You can test the Server preferences by sending an email to the mailbox specified in
the above steps. To do this, click the Test Email button. (Note: the Test Email button
remains inactive until the Apply button is selected.)
8. Select OK to close the Server Notification Preferences window.
9. From the Menu Bar, select Faults > Event Notifications. The Event Notification
Rules window displays.
10. Select the Add button. A new, undefined rule appears in the window.
that you here is used as the subject line for an email message about this event.
12. In the Action column, select Select Edit actions... from the drop-down menu.
13. The Event Notification Action window displays.
14. Select the Add button. A new Event Notification action appears in the window.You
will set up the email message information here.
614-330055-001 July 2009 4-61

entered here is used as the message within the email message.
16. In the Type column, select Email.

17. In the Destination column, enter the email address where this message will be sent.
18. Select OK to save the action. The Event Notification Actions window is closed. The
email notification action now appears in the drop-down menu on the Event
Notification Rules window:
19. To delete an action, highlight the action and then select the Remove button.
20. Select the Edit Rule button. The Notification Rule window displays. Configure the
rules for this notification.
21. Select OK to save the configuration and close the Notification Rule window.
22. In the Event Notification Rules window, select OK to save the notification rule.
23. ProVision will now send an email message to the specified address if the event
occurs in the notification rule parameters.
Related Topics

Set Up a Pop-Up Message Notification

This set of instructions describes all the steps required, from start to finish, to set up a
pop-up message notification that displays in ProVision. Some of the information here
is also provided in Add or Edit Event Notification Rules on page 4-53. It is collected
here to help users understand how to set up this type of notification.
Notification Dialog Box

If you select “pop-up” for a particular rule, the notification dialog box pops up
whenever there is a match for that rule. You can also open the notification dialog box
from the menu bar by selecting Faults > Notifications Preferences > Notification Dialog.
(If there are no matches for any of the defined rules, the dialog box is blank.)
The Event Notification pop-up window has a dynamic update feature where the
information in the text box is automatically updated when new triggering conditions
occur. Other features of the event notification are listed below:
Feature Description
Text Box Displays the triggering condition as defined by the user, the
device where the event originated, the day and time the event
occurred, the event, and its severity.
Left / Right If more than one dialog box is open, select the left or right arrow
buttons to scroll through the active event notification dialog
boxes.
Event Browser Opens the Event Browser of the device where the event
originated.
Dismiss All Dismisses all active events.
Dismiss Dismisses only the current event. Any active events remain
active.
Close Closes the event notification dialog box, but does not dismiss
the event.

• Events for which you want to view pop-up message notifications.
614-330055-001 July 2009 4-63

The notification preferences for the ProVision client are associated with a
specific user account, so the same preferences are accessible from any
workstation that the user is logged into. If a number of users are logged
into ProVision with the same user name, then the same pop-up
notifications display at each workstation.
Procedure
1. Follow the steps in Add or Edit Event Notification Rules on page 4-53 to create a
new rule for an event.
2. From the Menu Bar, select Faults > Notifications Preferences > Client:
The Client Notifications Preferences window displays.
3. Select the Pop-up check box to instruct ProVision to display the event message for
that event in a pop-up window.
4. Select OK to close the Client Notification Preferences window.
5. Whenever the specified event occurs, ProVision will display the event message in a
pop-up window.
Related Topics

Set Up an Audio Alarm Notification

This set of instructions describes all the steps required, from start to finish, to set up an
audio alarm event notification that is played by ProVision. Some of the information
here is also provided in the sections about how to Set the Server Notification
Preferences on page 4-52 and Add or Edit Event Notification Rules on page 4-53. It is
collected here to help users understand how to set up this type of notification. Before
you begin, you will need the following information:
• Events for which you want to hear sound message notifications.
To successfully use audio alarms, the ProVision computer needs to be

equipped with a sound card and speakers, and the volume needs to be
turned up so that an audio alarm can be heard.
The default audio alarm is a beeping sound. Users can load a .wav sound
file to use as an alarm sound; see the following instructions for more
information.
Procedure
To set up an audio alarm notification:
1. Follow the steps in Add or Edit Event Notification Rules on page 4-53 to create a
new rule for an event.
2. From the Menu Bar, select Faults > Notifications Preferences > Client:
The Client Notifications Preferences window displays.
3. Select the audio notification sound. This sound will play for all audio notifications:
• To choose the default audio notification, select the check box to Use Default.
Provision will play the default audio notification when this is set up for an event.
• To use a .wav file for a different sound, deselect the Use Default check box. The
Audio field will activate. Click the button beside it to select a .wav file. The
614-330055-001 July 2009 4-65

sound played by this .wav file will be the audio notification.
4. When events are set up, they display in this screen. Select the Audible check box to
instruct ProVision to play an audio alarm message for that event.
5. Select OK to close the Client Notification Preferences window.
6. Whenever the specified event occurs, ProVision will play the audio notification.
Related Topics
Set Up Script Execution on Event Notification

An event notification can be set up to run a shell script for a batch file when a specific
event occurs in ProVision.
• Events for which you want to run script executions upon notifications.
• The names and file locations of scripts to be run upon notification.
An event notification can run either an email notification or a batch file.

If you want a notification for an event to run both an email notification
and a batch file, you need to set up two separate event notifications for
that event.
Procedure
To add an event notification rule:
1. From the Menu Bar, select Faults > Event Notifications.


A new, undefined rule appears in the window.
3. Place the cursor in the Name column and enter a description of the triggering
condition. In the Action column, select an action from the drop-down menu to
occur when the event takes place.
• Select Edit actions... to create/edit/delete an action.

4. The Event Notification Action window displays.

A new, undefined action appears in the window.
6. Place the cursor in the Name column and enter a description of the event.
7. In the Type column select Run Script.

8. Run Script runs a shell script for a batch file when the event occurs. In the
Destination column, enter the filename for the batch file. Please note the following:
• The batch file runs on the server.
614-330055-001 July 2009 4-67

• To reference a batch file from another folder, you must include the path along
with the file name. For example: “C:/my documents/ProVisionV/Customers/
Wingate/BatchFiles/filename.bat”. An example in Solaris might be:
\export\home\myuser\filename.sh.
• If you do not specify the folder in the Windows environment, ProVision looks
for the file in the <pv root>/ProVisionVServer/ folder.
• If you do not specify the folder in the Solaris environment, an error message
results.
• Select OK to save the action.
The Event Notification Actions window is closed. Note that the action that was just
created now appears in the drop-down menu on the Event Notification Rules
window:
9. Select the Edit Rule button. The Notification Rule window displays.
10. Configure the notification to meet your requirements, as noted in Configuring the
Notification Rule on page 4-57. Select OK to save the configuration and close the
Notification Rule window.
11. In the Event Notification Rules window, select OK to save the newly-created rule.
12. When this event occurs, the script will run.
Related Topics:

Logical Containers
• Adding a Device to a Logical Container on page 4-70
• Removing a Device from a Logical Container on page 4-72
• Renaming a Logical Container on page 4-73
• Deleting a Logical Container on page 4-74
Network devices that share a common purpose can be grouped together to form a
Logical Container. This grouping allows these devices to be monitored, managed, and
viewed independent of the main network, and at the same time also continue to be
viewed as part of the wider network.
A single network device may participate in more than one logical container. It may be
carrying traffic for more than one customer, event, or emergency service.
In addition to the tree view, logical containers are monitored using the flat map view.
This view displays all logical container devices, which can be linked to represent traffic
connections that exist between the devices.
You can view all the events for a logical container from an Event Browser. You can also
view events for selected devices within the logical container.
A logical container is created when it is applied to at least one device and is
automatically deleted when it is removed from all devices, or you can manually delete
a logical container.
The following are examples of suggested logical containers, and the benefits gained:
• The grouping of high capacity, high priority trunking radios. This enables the user to
quickly and easily differentiate between high and low impact failures and to respond
accordingly.
• The grouping of all radios carrying traffic for specific customers, in order to generate
customized availability reports for each customer.
• The grouping of radios carrying traffic for important events to improve response
times.
• The grouping of radios carrying traffic for emergency services to improve callout
response times.
614-330055-001 July 2009 4-69

Circuit bundles can be included in a logical container. In addition, a

logical container can be included within another logical container.
Region , site and rack containers cannot be included in a logical
container.
Related Topics:
Logical Links on page 4-75
Circuit Logical Containers on page 3-91
Adding a Device to a Logical Container

To add a device to a logical container:
1. Right-click the required device icon.
2. From the menu displayed select Configure Logical Containers.
The Configure Logical Containers window displays.
3. To select a logical container for this device, highlight the service in the All Logical
Containers list and select the > button. The device is now part of the selected logical

container.
4. You can repeat Step 3 to add the radio to another logical container.
5. To accept changes, select OK.
The Logical Container tab displays the new logical container and the selected radio.
Related Topics:
• Adding a Logical Link on page 4-76
614-330055-001 July 2009 4-71

Removing a Device from a Logical Container
Introduction
You would remove a device from a logical container when it is no longer required in the
container, for example when a radio is decommissioned or moved to another site.
Procedure
To remove a device from a logical container:
1. Right-click the device you want to remove from a logical container.
2. From the menu displayed select Configure Logical Containers.
The Configure Logical Containers window displays.
3. Highlight the logical container in the Configured Logical Containers list and select
the < button. The logical container is moved into the All Logical Containers list.
4. Select Apply.
5. To save the changes and close the Configure Logical Containers window, select OK.
Related Topics:

Renaming a Logical Container
Introduction
You can change the name of a logical container.
Procedure
1. Within the Logical Container pane, right-click the logical container to be renamed.
2. From the right-click menu, select Rename.
The Rename Logical Container window displays.
3. Make the required changes to the logical container’s name.
Related Topics:
614-330055-001 July 2009 4-73

Deleting a Logical Container
Introduction
ProVision automatically deletes a logical container when there are no longer any
devices associated with the logical container. You can also manually delete a logical
container.
Deleting a logical container has no effect on the devices that are contained within the
service.
Procedure
To manually delete a logical container:
1. Within the Logical Container pane, right-click the logical container to be deleted.
2. From the right-click menu, select the Delete option.
The following message window displays:
3. Select Yes to confirm deleting the selected logical container.
Related Topics:

Logical Links
• Renaming a Logical Link on page 4-76
• Deleting a Logical Link on page 4-77
A logical link enables you to connect devices within the logical container flat map
viewer. For example, an Altium and an Eclipse Node situated at the same location and
physically connected via cables can be linked in ProVision via a logical link. Logical
links enable you to see the entire network or portions of, across all device types. You
can add, rename and delete logical links.
A logical link is shown in the Map Viewer as a colored dotted line which indicates the
highest severity event of the linked objects.
A device can have multiple logical links.

You can browse a logical link, where events from both ends of the link are displayed in
a separate Event Browser window. The Event Browser features and functionality are
described in Customizing Event Browsers on page 4-4.
A logical link is a ProVision function only, the devices in the network are
in no way affected by a service link.
Related Topic:
Logical Containers on page 4-69
614-330055-001 July 2009 4-75

Adding a Logical Link
Introduction
Logical links are created after you have set up and populated your required logical
containers.
Procedure
To create a logical link between two devices:
1. In the Tree Viewer, locate the two objects to be linked.
2. Select the first object, hold down the CTRL key and select the second object.
3. Right-click the second object. A right-click menu displays.
4. In the right-click menu, move your mouse over the Create Link option and from the
submenu displayed select Logical Link.
A successful link message displays.
5. Select OK to close the message window.
Related Topics:
Renaming a Logical Link
Introduction
Under most circumstances, you can rename a logical link.
If a link has had its name assigned in Portal, you will not be able to rename it in
ProVision. To check this for a link, right-click and read the right-click menu. If the
Rename option does not appear, you cannot rename the container.
Procedure
To rename a logical link:
1. In the Map Viewer right-click the logical link.
2. Select Rename on the right-click menu. The Rename Object window with the
selected link’s name displays.
3. Make the required changes to the logical link’s name.
Related Topics:

Deleting a Logical Link
Introduction
You can delete a logical link. Deleting a logical link does not effect the devices nor the
functionality of the network.
Procedure
To delete a logical link:
1. Within the Map Viewer, right-click the logical link to be deleted.
2. In the right-click menu, select Delete. The Delete Link message window displays.
3. Select Yes to delete the selected logical link.
Related Topics:
614-330055-001 July 2009 4-77

Scoreboard Group Scenarios
This section describes scoreboard group scenarios.

• About Scoreboard Group Scenarios
• Event Management Processes
About Scoreboard Group Scenarios

The Scoreboard is the most convenient way to monitor a group of radios or the entire
network. Typically, every radio in the network is displayed on a Scoreboard
Scoreboard groups provide a summary of the status of a network in a graphical format.
How you set your Scoreboard groups up is flexible and is to be based on your business
requirements.
The Scoreboard group is a container for individual Scoreboards and allows you to:
• Add and remove Scoreboards from the group
• Name and save the Scoreboard group
Once a Scoreboard group is set up it is saved and available to all ProVision users. this
saves having to set up the Scoreboard group each time.
The following examples are business-driven scenarios for using Scoreboard groups.
Golden Cells
Your network includes sites where it is imperative that communications traffic
continues at peak performance. Examples of golden cells are:
• A mobile backhaul network, located close to international sporting events.
• Sites where communications down can mean loss of revenue, for example, share
markets.
• Sites where there is a contractual obligation that includes performance metrics.

Scoreboard groups are a way to monitor these specific sites.
Backbone Sites
These are sites that carry a high proportion of communications traffic and feed off to
less important “leaf sites”. Problems with these backbone sites impacts entire sections
of the network. It is crucial that these sites are kept problem free.
Monitoring Event Categories

You want to monitor the entire network for certain categories of events, such as
communications, and equipment failure.
Monitoring a Specific Site

You have a site experiencing problems. Creating a Scoreboard group dedicated to this
site enables you to monitor events from the radios at that site.

• Viewing a Scoreboard Group on page 4-80
• Creating a Scoreboard Group on page 4-81
• Editing a Scoreboard Group on page 4-83
• Deleting a Scoreboard Group on page 4-83
• Adding a Scoreboard on page 4-84
• Editing a Scoreboard on page 4-87
• Deleting a Scoreboard on page 4-88
• Opening an Event Browser from a Scoreboard on page 4-88
614-330055-001 July 2009 4-79

Viewing a Scoreboard Group
Introduction
There are several ways you can view event activity within ProVision; tree and map
viewers, Event Browsers and Scoreboard groups.
Typically, when using Scoreboards you would have several Scoreboard groups
displayed, giving you an instant, up-to-date, graphical summary of the network events.
Procedure
To view a Scoreboard group:
1. From the tool bar, select the Saved Scoreboard Groups icon .
2. From the drop-down list displayed, select the Scoreboard group required.
The Scoreboard Group window with the latest event summaries displays.
Related Topics:

Creating a Scoreboard Group
Introduction
When a new Scoreboard group is created, by default a Scoreboard showing all active
events displays.
Procedure
To create a Scoreboard group:
1. From the tool bar, select the New Scoreboard Group icon .
The new Scoreboard Group window displays.
2. To save the Scoreboard group, select the Save icon .

The Save As window displays.
3. In the Name field, type a descriptive name for the Scoreboard group.
This name displays when saved Scoreboard groups are viewed from the tool bar.
Your name is added to the Scoreboard group identifying it as yours, however other
operators can still use it.
614-330055-001 July 2009 4-81

4. To save the Scoreboard group, select Save.
The Save As window closes and the Scoreboard Group window displays.
Related Topics:

Editing a Scoreboard Group
Introduction
Editing a Scoreboard group can involve any of the following: adding, modifying, or
deleting Scoreboards within the Scoreboard group.
Procedures
Editing a Scoreboard group involves:
Deleting a Scoreboard Group
Introduction
You can delete a Scoreboard group when you no longer need to monitor the events from
particular sites or radios.
Procedure
2. From the list of Scoreboard groups displayed, select the Scoreboard group to be
deleted. The Scoreboard Group window displays.
3. From the Menu Bar, select File > Delete.
The Delete window, listings all the Scoreboard groups displays.
4. Select the Scoreboard group to be deleted.
5. Select Delete. A deletion confirmation window displays.
6. To confirm deleting the Scoreboard group, select Yes.
7. To close the Delete window, select Close.
Related Topics:
614-330055-001 July 2009 4-83

Adding a Scoreboard
Introduction
A Scoreboard is a visual way to see what events ProVision is receiving. The Scoreboard
shows the ratios of the different event severities.
The Scoreboards contain all the logic for representing the data and provide the
mechanism to modify filters for each Scoreboard. Each Scoreboard has its own filter
that defines the events it uses to calculate its event count.
See Event Browser Filter Values on page 4-27 for information on how to set the filters.
Procedure
To add a Scoreboard:
1. From the tool bar, select the Saved Scoreboard Groups icon.
2. From the list of Scoreboard groups displayed, select the Scoreboard group to which
the Scoreboard is to be added.
The Scoreboard Group window displays.
3. Select the New Scoreboard icon.

4. Select the Settings icon .

The Scoreboard Settings window displays.
5. In the Name field, type a descriptive name.

6. Select the Style drop-down arrow, and select the chart type in which Scoreboard
events displays.
7. To save your changes and close the window, select OK.
8. To set up the Scoreboard filters, select the Filters icon .
The Filters window displays.
614-330055-001 July 2009 4-85

9. Make the required filter changes and select OK.

The Scoreboard filters are applied immediately and the Scoreboard changes to
reflect the filters in place. You can move and adjust the Scoreboards to make the
display meet your requirements.
10. Select X in the top right corner of the Scoreboard group. The Scoreboard modified
dialog window displays, asking if you want to make changes.
11. To save the changes and close the Scoreboard group window, select Yes.
Related Topics:

Editing a Scoreboard
Introduction
You can change the Scoreboard’s name, the chart used to display the events (pie or bar)
and you can modify the event Scoreboard filters.
Procedure
To modify a Scoreboard:
1. From the tool bar, select the Saved Scoreboard Groups icon.
2. From the list of Scoreboard groups displayed, select the Scoreboard group that
contains the Scoreboard to be modified. The Scoreboard Group window displays.
3. On the Scoreboard to be modified.

• To change the filter options, select the Filters icon.
• To change the Scoreboard settings, select the Settings icon.
4. To save your changes, select File > Save.
5. To close the Scoreboard group, select the X in the top right corner.
Related Topics:
614-330055-001 July 2009 4-87

Deleting a Scoreboard
Introduction
Consider carefully before deleting a Scoreboard from a Scoreboard Group. The
Scoreboard, or the Scoreboard settings, may be useful in the future.
Procedure
To delete a Scoreboard:
1. From the tool bar, select the Saved Scoreboard Groups icon. .
2. From the list of Scoreboard groups displayed, select the Scoreboard group from
which the Scoreboard is to be deleted.
3. Select the X in the Scoreboard’s top right corner.
4. Select the X in the top right corner of the Scoreboard group.
The Scoreboard modified dialog window displays.
5. To delete the Scoreboard group, select Yes.
Related Topics:
Opening an Event Browser from a Scoreboard
Introduction
You can open an Event Browser, which displays all Scoreboards events, or an Event
Browser that just displays events of a particular severity.
When you select a Scoreboard segment to view, for example, events of a particular
severity, the filters set for the actual Scoreboard determine the events displayed. The
figure below is an example of a browser window opened from a Scoreboard. The
browser window title reflects the Scoreboard name - All Alarms.
Figure 4-8. Event Browser Opened Via a Scoreboard
Procedure
To open an Event Browser from a Scoreboard:
2. From the drop-down list displayed, select the Scoreboard group required.
3. To view events for an entire Scoreboard, select the Launch Event Browser icon,
located in the left corner of the Scoreboard.
An Event Browser window opens, displaying all the events for the selected
Scoreboard.
4. To view events for a segment of a Scoreboard chart, for example, the critical events,
right-click the segment or bar of the chart.
5. Select the Event Browser option displayed.
The events for the selected segment are displayed in an Event Browser window.
Related Topics:
614-330055-001 July 2009 4-89


Chapter 5. System Diagnostics

and Reports
ProVision provides system diagnostics to enable you to find and locate system
problems. You can precisely locate the network, link, or radio that is having a problem,
and what is the best course of action to resolve the problem. System diagnostics include
viewing an event’s history and probable cause, using diagnostics for XP4 radios,
analyzing performance data and launching the specific radio craft tools.
Your ProVision security access level determines your access to system diagnostics. If
you cannot access system diagnostics, and you think that you should, discuss this with
your system administrator.
ProVision also provides reports for Eclipse radios. These allow you to monitor Eclipse
radio functionality, and to save and review radio data to improve performance or share
information with clients.
• Using System Diagnostics on page 5-2
• About ProVision and Craft Tools on page 5-4
• Diagnostic and Performance Trends Analysis Procedures on page 5-5
• Craft Tools and Diagnostic Controls on page 5-50
• Device and Network Reports on page 5-101
Other Resources
The Harris Stratex Networks Best Practices Guide includes a section on Eclipse
troubleshooting that provides generic information on loopbacks, fade margins, and
other diagnostic tools.
614-330055-001 July 2009 5-1

Chapter 5. System Diagnostics and Reports
Using System Diagnostics
System diagnostics are used when events sent from network radios indicate that there
is a problem with a radio or a link. The system diagnostics gather detailed information
to determine:
• Where the problem is
• What the problem is
• What is causing the problem
For example, the radio forwarding events may not be the radio with the problem; the
radio with the problem may not be working at all. The system diagnostics enable you to
determine if the problem is faulty equipment, or a path related problem such as
rain-fade or ducting.
The following prerequisites are required to utilize the system diagnostics:
• Access to the craft tools
• Security access to the radio
System Diagnostics Overview

System Diagnostics includes the following functions:
• Performance Data for:
• G.826
• G.828 (TRuepoint radios)
• RSL/RSSI
• Ethernet Bandwidth
• Craft Tools, including:
• Configuration of radio networks, frequencies, and tributaries
• Radio fault diagnostics for loop backs, protection switching, and device resets
• TNet Craft Tool and Diagnostics
• XP4 Craft Tool and Diagnostics
• Event Properties
• WiMAX Connectivity and WSN-AGM Controller View
• Diagnostics for:
• Constellation
• CAU
• DVA
• MegaStar

Equipment Malfunctions vs. Path Degradation

An equipment problem is typically not intermittent. If it is not intermittent, the radio’s
Event Browser or the event’s properties show an alarm that has been raised and not
cleared. Check for related equipment alarms at both ends of the link. The problem
could be at the local receiver or the remote transmitter: for example, a failure within
the modulation or demodulation processes or a noisy local oscillator. Use loopback
diagnostics to isolate the problem.
The most common cause of radios raising events is path degradation through rain fade,
diffraction, or multipath. These alarms are raised, and cleared down some time later,
but may occur intermittently over a period of hours.These alarms are typically raised at
the affected end of the link only, though in a path fade situation usually both ends are
similarly affected and hence both ends are alarmed.
10-3 path errors are normally preceded by 10-6 BER alarms.
Next Topic:
About ProVision and Craft Tools
614-330055-001 July 2009 5-3

About ProVision and Craft Tools
Each device has a specific craft tool for configuration, maintenance and diagnostics.
ProVision includes craft tool-like functions for Eclipse, TNet, XP4 radios, and certain
other radios. For more information about craft tools refer to Craft Tools and Diagnostic
Controls on page 5-50.
Where an event in ProVision indicates there is a problem with a radio, why not just
launch the craft tool for that particular radio? As an example, let us compare ProVision
and Portal, the Eclipse craft tool. Both have history and performance screens that
enable you to view traffic error performance measurement. Table 5-1 lists how
ProVision and Portal differ and in which circumstances to use Portal or the craft tool.
Table 5-1. ProVision versus Portal
ProVision Craft Tools (Portal)
ProVision is network focused. Portal is focused on an Eclipse Terminal link or an

Eclipse Node and its links.
You can view the history and performance
trends of one to many radios within the You can view the history and performance trends
network. of one radio.
You can determine if the problem is network You can analysis and diagnose the events from
wide, a group of radios or an isolated radio. one radio.
For example, a weather front with heavy rain
Typically the craft tool’s loopback diagnostics are
is moving across the country. Using the
used to find faulty equipment.
history you can view the performance
affected links and know the problem is The data available is short term only, that is,
temporary and not equipment related limited to what is stored in the radio.
because it is happening to many links.
Single task affecting a single radio.
Long term data is available from the
ProVision database.
ProVision performs bulk tasks such as
collecting inventory data.
Next Topic:
Diagnostic and Performance Trends Analysis Procedures

Diagnostic and Performance Trends Analysis

Procedures
The diagnostic and performance trends analysis procedures are grouped under the
following categories:
• Circuit Diagnostics Feature on page 5-5
• Data Collection on page 5-14
• Ethernet Performance Data Collection on page 5-20
• Performance Features on page 5-33
• Craft Tools and Diagnostic Controls on page 5-50
• TNet Diagnostics on page 5-62
• Diagnostic Controls for Selected Devices on page 5-85
Circuit Diagnostics Feature

The circuit diagnostics feature allows you to diagnose problems within a circuit and
isolate faulty equipment. ProVision displays the radios and links within a circuit
pictorially and lets you easily set up loopback and PRBS (pseudo random bit signal)
tests on different sections of the circuit. The duration of the diagnostic test can be set
for a specific length of time to minimize network disruption.
Only Eclipse radios support the circuit diagnostics feature.

• Circuit Trace for Circuit Diagnostics on page 5-6
• Circuit Diagnostic Window on page 5-7
• Setting Up a Circuit Diagnostic Test on page 5-10
• Circuit Diagnostic Options on page 5-13
Next Topic:
Circuit Trace for Circuit Diagnostics on page 5-6
614-330055-001 July 2009 5-5

Circuit Trace for Circuit Diagnostics

To use the circuit diagnostics feature, the circuits within the network must first be
defined. See the section on Circuit Management on page 3-84 for more information.
The figure below is an example of a circuit trace that has already been performed on a
simple, three-radio circuit.
Figure 5-1. Circuit Trace of a Three-Radio Circuit
To open the circuit diagnostic window, right-click the selected circuit within the
Circuits tab and select Circuit Diagnostics.
Related Topic:
Circuit Diagnostic Window on page 5-7

Circuit Diagnostic Window

This figure illustrates a Circuit Diagnostics window for a three-radio circuit. The
components of the Circuit Diagnostics window are defined below.
See Setting Up a Circuit Diagnostic Test on page 5-10 for an actual example on how to
set up a circuit diagnostic test.
Figure 5-2. Circuit Diagnostic Window
Table 5-2. Circuit Diagnostics Window Details
Circuits Diagnostics Window Description
Main View
Illustrates the individual circuits and shows how
each radio is connected to the next. Place the
cursor over each component to open a pop-up
window with additional information.
614-330055-001 July 2009 5-7

Radio - A radio can be a repeater / node or a

terminal. A repeater / note consists of two or
more links. A terminal (because it is positioned
at the end of a link) has one link and one DAC
unit.
Select the radio name to display the only
available command in the Controls section: the
BUS Loopback. The BUS Loopback provides a
loopback at the INU, INUe, or IDU. The
loopback signal is NOT set along the link.
Place the cursor over the name of the radio to
view additional information.
Link - The connection between the current radio

and the next radio in the circuit. The link can be
one of three types: a standard link, a protected
link, or a Ring Protected link.
Place the cursor over the link to view additional
information including the name of the link. (In
the figure to the left, the name is LINK1 where
the number following indicates its slot location
in the INU/INUe rack.)
No controls are available for the link.
DAC - The terminating unit for a circuit. Place

the cursor over the DAC to view additional
information including the name of the DAC. (In
the figure to the left, the name is DAC3 where
the number following indicates its slot location
in the INU/INUe rack.)
Select the DAC icon to display the available
controls in the Controls section:
(Tributary) Radio Facing Loopback or (Tributary)
Line Facing Loopback - A loopback on a
tributary link within the network.
PRBS Link Test: - Pseudo Random Bit Signal link
test which provides a built-in BER test
capability which allows you to initiate a BER test
on a looped circuit.
Selected Circuit
Select a circuit to undergo diagnostics from the
drop-down menu.

PRBS Test G.821 Data

G.821 is widely used for performance
measurements in E1/DS1 networks. The figure to
the left shows the measured performance for a
circuit undergoing a test. Refer to the table below
for a description of the test parameters.
Table 5-3. Description of the G.821 Data From a Circuit Diagnostics Test
Parameter Description
Elapsed Seconds Seconds that have elapsed since the beginning of the diagnostic test.
Available Seconds Total available time during a fixed measurement interval.
Unavailable Seconds Total unavailable time during a fixed measurement interval.
Bit Error Count Total number of bit errors during a fixed measurement interval.
Bit Error Count Ratio The ratio of bit error counts to the total available time during a fixed
Seconds measurement interval.
Errored Seconds A count of the number of errored seconds since commencement of

the test. An errored second is a one-second period with one or more
errored bits.
Errored Seconds Ratio The ratio of errored seconds to the total available time during a fixed
measurement interval.
Severely Errored Seconds A count of the number of severely errored seconds since the
commencement of the test. A severely errored second is a
one-second period which has a bit error ratio greater than or equal
to 1 x 10-3.
Severely Errored Seconds The ratio of severely errored seconds to total available time during a
Ratio fixed measured interval.
Related Topic:
Setting Up a Circuit Diagnostic Test on page 5-10
614-330055-001 July 2009 5-9

Setting Up a Circuit Diagnostic Test

To set up a circuit diagnostic test:
1. Open up the Circuits tab. Right-click the selected circuit and select Circuit
Diagnostics.
2. The Circuit Diagnostics window displays.
3. Select the DAC unit where the loopback test is planned to originate. The available
controls appear in the Controls panel. Select a device within the circuit to display
the available controls for that device.
4. Select PRBS Link Test to add it to the DAC device.
5. Select the type and location of loopback. In this example, A Bus Loopback is
selected on another radio in the circuit. To perform this operation, select the node
by selecting the name of the radio.
The available control (in this case, the BUS Loopback) displays.

6. Select the BUS Loopback control to add it to the circuit test.
7. Select the Apply button to initiate the circuit diagnostics test.
8. Select Yes to open the Diagnostic Safety Timer window
9. Select OK to accept the default 60-second test.

To set the timer for another setting, select the “On for” radio button and set the
hours, minutes and seconds using the up and down arrows. Then select OK to begin
the test.
10. The results of the test are displayed in the PRBS Test G.821 Data table.
• An “Errors detected” message appears if there are errors.
• The timer in the bottom right corner counts down the time remaining for the
test.
• The information is updated every 10 seconds while the test is running.
614-330055-001 July 2009 5-11

Related Topic:
Circuit Diagnostic Options on page 5-13

Circuit Diagnostic Options

The various options for performing a circuit diagnostic test are listed in the table below
as they appear in ProVision:
Table 5-4. Circuit Diagnostic Test Options
Circuit Diagnostic Options ProVision Set-up
Circuit segment test on a circuit

within a network.
or
or
or
Circuit end-to-end test.
or
Related Topic:
Diagnostic and Performance Trends Analysis Procedures on page 5-5
614-330055-001 July 2009 5-13

Data Collection
This section covers the following details:
• Introduction on page 5-14
• Daily Performance Data Collection on page 5-15
• Enabling 15-minute Performance Data Collection on page 5-17
• Enabling 15-Minute Ethernet Data Collection on page 5-20
• Changing Device Data Collection Status on page 5-18
Introduction
Background G.826 and G.828 error performance data is automatically collected and
stored on a per radio basis. The data is summarized within bins to provide an historical
presentation of performance. This data collection does not affect traffic.
All radios are summarized in daily bins; most radios also have a 15-minute bin option.
Ethernet radios have a 15-minute bin option that collects Ethernet data. 15-minute bins
provide seven days of data; the daily bins provide one month of data.
ProVision automatically tracks device-dependent RSSI and performance data on most
HSX devices:
• Performance monitoring is carried out in accordance with CB-149, G.826
performance specifications, also contingent on device type.
• RSSI data reflects various RSSI, RSL, or AGC values, depending on how the device
measures and reports received signal strength data.
A radio's daily performance registers provide long term performance data collection
information. The monitoring of daily registers is enabled immediately after a radio is
managed, and continue for the life of the radio in the network. ProVision collects the
daily performance register information from all managed radios in the network.
This table describes performance data collection details specific to particular radios.
Table 5-5. Radio Specific Data Collection Details
Device Type Information
Altium MX 2+0 Both A and B side register data (G.826 and RSSI) is
collected.
Protected XP4 Configuring a Protected XP4 variant for data collection,

automatically configures the XP4 radios it manages.
Eclipse INU Can support up to 3 radio paths with a standard chassis,

and up to 6 paths with an expanded chassis configuration.
You can select on which of the available radio links, data
collection is enabled. Also collects TX power (i.e., ATPC
achieved output power).
XP4 radio Tracks both G.821 and G.826 performance data.

Device Type Information
TRuepoint 5000, Performance data (error ratio and error rate values) are
4040, 4000, and 6400 collected from “current value” MIB objects without any
additional processing. The performance value presents the
Megastar
values sampled from the radio at the end of each bin
Constellation period; these sampled values can be viewed as a 15-min
Microstar or daily bin.
TNet
Velox
Sagem-Link
SII SNMP Does not support daily registers, so ProVision artificially

creates daily registers by reading all 96 15-min bins once
Altium Radios
each day, and aggregating them into a single daily bin.
ADR Radios
Problems with a radio may result in a gap in collected performance data. ProVision
provides for data recovery when this happens. If there is a server disconnection, when
the server restarts, it retrieves all missed polls for 30 days from connected devices. In
other circumstances where data is missed, the server retrieves data going back 24 hours
before the data outage.
Next Topic:
Daily Performance Data Collection
Daily Performance Data Collection

When a device is managed in ProVision, daily performance data collection is
automatically enabled, except where the device does not support this, for example,
TNet radios. The daily performance data for the first day is not available until the
following day.
The numbers in the figure refer to the numbered steps below. The example below helps
to illustrate the performance data collection for Eclipse devices. Specifically, it
describes how the Eclipse device bin file that is stored on the device relates to the
ProVision database and NBI files. See the section titled NBI Performance Data
Management in the ProVision Installation and Administration Guide for more
information on NBI files.
ProVision cannot read all daily bins from all of the devices in the network due to
processor loading and NMS channel restrictions. Because of this, the collection of the
data from the bins is staggered over a 24 hour period.
Figure 5-3. Eclipse Device Performance Data Collection and NBI Behavior
614-330055-001 July 2009 5-15

1. Each Eclipse device creates a daily bin file at 12:00 midnight for that day. In this
example, a block of data we will call “Sunday bin” (blue) is created at the end of the
day at 12:00 midnight.
2. For this example, let’s assume a network operator enables daily data collection at
00:00 am on Monday.
A performance bin file with a time stamp for “Sunday midnight” is created in the
database when ProVision reads the data from the first device on Monday.
3. From 00:00 am on Monday, ProVision starts collecting the “Sunday bin” data
collection from all the devices, and the bins are written to the ProVision database,
until all bin devices are read and recorded.
4. ProVision writes the “Sunday bin” data to the NBI files at the same time as it writes
to the ProVision database.
5. At the end of the day a new daily bin is created on each Eclipse device. In this
example, the “Monday bin” (yellow) is created at the end of Monday at 12:00
midnight.
6. On Tuesday, ProVision begins the “Monday bin” data collection from the Eclipse
devices.
A performance bin file with a time stamp for “Monday midnight” is created in the
database when ProVision reads the data from the first device on Tuesday.
7. Again, from 00:00 am on Tuesday, ProVision starts collecting the “Monday bin”
data collection from all the devices. The bins are written to the ProVision database,
until all bin devices are read and recorded.
8. ProVision writes the “Monday bin” data to the NBI files at the same time as it writes
to the ProVision database.
As long as data collection is enabled, ProVision continues to collect the previous day’s
daily bin data.
This procedure applies to the G.826 performance as well as the Ethernet statistics data
collection. However, since Ethernet data collection is based on real-time counts in the
device, ProVision only creates the first Ethernet bin AFTER two samples (24 hours
apart). Therefore, in the above example, the first bin of data is created at the end of the
day on Tuesday.
Any time the ProVision server is re-started, the daily and 15 min
performance data collection is also re-started. Using the above example,
if the ProVision server is stopped at 7:00 pm on Tuesday evening, the
“Monday bin” data collection ceases and all collected data for Monday is
lost. If the ProVision server is subsequently restarted, the “Monday bin”
data collection is resumed. The data cannot be viewed until the end of
the day on Tuesday at 12:00 midnight.
Next Topic:
Enabling 15-minute Performance Data Collection

Enabling 15-minute Performance Data Collection
Introduction
15-minute data collection must be manually enabled or disabled for a device. Radio
15-minute data collection is an intensive operation that can be initiated to further
investigate problems occurring in the network; for example, to use when you suspect a
radio is faulty. When you enable 15-minute data collection on a radio, the icon
displays on the device’s icon in the Tree and Map Viewer. Within 15 minutes, the first
set of data is available for the History and Performance Trends windows.
All devices have Radio 15-Minute Performance Data collection available.

The following devices also have Ethernet 15-Minute Performance Data
collection: Eclipse DAC GE, DAC ES, IDU GE, IDU ES, and IDU SPE
devices. See Enabling 15-Minute Ethernet Data Collection on page 5-20.
Radio 15-minute data collection is intensive on network traffic. It

is recommended that you disable it as soon as it is not required.
For an Eclipse Node or a TRuePoint node, you can enable data collection on the
available radio paths. The Eclipse INU can support up to 3 radio paths, and the Eclipse
INUe up to 6 paths.
Procedure
1. Select the device:
Device Type Required Action
Protected XP4 radio Right-click the container XP4 radio icon.
Eclipse Node • Expand the Eclipse Node to see link icons.

• Right-click the required link icon.
Right-click the radio icon.

Other Harris Stratex devices1
1. For DXR 100 &700 radios, access the 15-minute data via the DXR NET craft tool.
A device-dependant pop-up menu displays, as shown for an Eclipse link.
614-330055-001 July 2009 5-17

2. To enable 15-minute data collection, select the Radio 15-min Performance Data item.
The radio icon is updated with the icon and 15-min data collection is enabled
on the radio.
3. To disable the 15-min Data Collection, de-select the Radio 15-min Data Collection
item.
The icon is removed, and 15-min data collection is disabled for this radio.
Related Topics:
• Changing Device Data Collection Status on page 5-18
• Enabling 15-Minute Ethernet Data Collection on page 5-20
Changing Device Data Collection Status
Introduction
From the Performance Data Collection screen, you can do the following:
• View the performance data collection status, daily and 15-minute, for all the network
devices.
• Change the daily, radio 15-minute, and Ethernet 15-minute performance data
collection status for individual devices.
• Change the daily data collection start time for the entire system.
Procedure
To view/change a device’s performance data collection status:
1. From the main menu, select Performance > Data Collection.
The Performance Data Collection window displays.

2. To display devices for a container, use the +. The links and link details display.
3. To change a device’s performance data collection status, highlight the device, make
the required changes to the check boxes, and select Apply.
4. To change the daily data collection start time, change the value for Collect daily data
at. Select whether the data collection start time is AM or PM. Then, select Apply.
Related Topics:
614-330055-001 July 2009 5-19

Ethernet Performance Data Collection

The Ethernet Data Collection feature is specific to Eclipse IDU GE, IDU ES, or IDU SPE
radios that have DAC ES or DAC GE plug-ins installed. This feature collects
performance data and displays it graphically to allow you to view historical data and
help you analyze and troubleshoot your network from the trends in the data.
Ethernet Data Collection collects and displays performance data for enabled ports and
channels. It does not process or show data for disabled ports and channels.
Next Topic:
Enabling 15-Minute Ethernet Data Collection
Enabling 15-Minute Ethernet Data Collection

The following devices also have Ethernet 15-Minute Performance Data collection:
Eclipse DAC GE, DAC ES, IDU GE, IDU ES, and IDU SPE devices.
To view the Ethernet performance data, you must first enable Ethernet 15-minute
performance data collection on the selected DAC plug-in, then allow some time to
elapse for ProVision to collect some meaningful data.
Procedure
To enable or disable ethernet data collection on a device:
1. Select the device
Device Type Required Action
Eclipse IDU GE, IDU ES, IDU SPE Right-click the radio or plug-in icon.
Device
DAC ES, DAG GE plugins • Expand the Eclipse Node so the plug-in icons
are displayed.
• Right-click the required plug-in icon.
A device-dependant pop-up menu displays, as shown for an Eclipse DAC GE.
2. Ensure that the Radio 15-min Performance Data is active. See Enabling 15-minute
Performance Data Collection on page 5-17.
3. To enable 15-minute Ethernet data collection, select the Ethernet 15-min

Performance Data item.
The radio icon is updated with the icon and Ethernet 15-min data collection is
enabled on the radio.
4. To disable the Ethernet 15-min Data Collection, de-select the Ethernet 15-min
Performance item.
The icon is removed, and Ethernet 15-min data collection is disabled for this
radio.
Use the Search function to quickly display the radios that have 15-minute
radio or ethernet data collection enabled.
Next Topic:
Viewing Ethernet Performance
Viewing Ethernet Performance

To view the Ethernet Performance features for a selected DAC plug-in:
1. Right-click the selected DAC plug in and select Performance > Ethernet from the
drop-down menu.
614-330055-001 July 2009 5-21

2. The Ethernet Performance window for the selected DAC plug-in displays.
Table 5-6. Ethernet Performance Window Details
Item Description
Summary Graphs These graphs show a thumbnail-sized summary of the data

collected for the four ports (A, B, C and D) and the two channels
(1 and 2). The dashed, vertical lines indicate time periods where
no data was collected.
The blue shaded area of the graphs show the Selection Period
and displays at a larger scale on the right side of the window in
the Graphical Tab - Expansion View (see below).
• Click and drag the blue shaded area to move the selection
period to another part of the graph.
• Click and drag the Left and Right Anchors on the blue shaded
area to adjust the duration selection period.
• Click and drag the Slider Bar at the bottom of the graphs to
view the entire length of the graph.
• Click the Left/Right Arrow buttons to expand/contract the
summary graph.
Selection Period The selection period is in the format: DD-Month-YY HH:MM. The
selection period automatically adjusts when you adjust the blue
shaded area of the summary graphs.

Item Description
Summary Parameters Three different summary parameters can be displayed at a

time. These are displayed as red, blue, and green lines on the
graph. You can select which parameters are displayed by
selecting them from the drop down menus. The options are as
follows:
• Mbps In and Out
• Utilization In and Out
• Unicast Packets In and Out
• Broadcast Packets In and Out
• Multicast Packets In and Out
• Octets In and Out
• Discards In
• In Pause Frames
• Errors
• Alignment Errors
• Frame Too Long
• Late Collision Frames
• Excessive Collisions
• Multiple and Single Collision Frames
• Deferred Transmission
• In Bad Octets
• Undersized Frames
• In Fragments
• In and Out Bytes: 64, 127, 255,511, 1023
• In and Out Max Octets
• In Jabbers
• In Filtered
• Out FCS Errored
• Collisions
614-330055-001 July 2009 5-23

Item Description
Graphical Tab This tab displays the graphical data for the selected DAC device.
The four buttons on the right side of the window allow you to
select four different sets of data. Each of these type of graphs
is described below:
Expanded View
This tab displays the expanded view of the graphical data for
the selected port or channel. The area displayed in this view
matches the blue shaded area of the graphs show the Selection
Period (see above).
Select the Expanded View button, then select a Port Button (Port
A, Port B, Port C, Port D) or a Channel Button (Channel 1,
Channel 2) to display the data for that particular port or
channel.

Item Description
Graphical Tab - Packet Types Select the Packet Types button to display the three types of
packets (Unicast, Broadcast, Multicast) in a pie chart and show
their relative numbers as a total number of packets in and
packets out for each individual port and channel.
Note: Ethernet performance data for Eclipse IDU GE radios does not
include any data for Port 3. Port 3 will not show any data in
this view; this is normal.
Graphical Tab - Packet Sizes Select the Packet Sizes button to display the different sizes of
packets (64, 127, 255, 511, 1028 Bytes) in a pie chart and show
their relative numbers as a total number of packets in and
packets out for each individual port and channel.
614-330055-001 July 2009 5-25

Item Description
Graphical Tab - Throughput and Throughput and Errors

Errors
Select the Throughput button to display a line graph of both the
receive and transmit throughput for each individual port and
channel.
Raw Tab Select the Raw tab to display the raw data for the 15-minute and
daily data collection. The individual buttons are described
below.
• Port / Channel Button - (Port A, Port B, Port C, Port D, Channel

1, Channel 2) to display the raw data for that particular port
or channel
• Export Button - Allows you to export the data to a .txt file.

Item Description
Raw Tab Data Raw Data includes data columns for the following values:
• Mbps In and Out
• Utilization In and Out
• Unicast Packets In and Out
• Broadcast Packets In and Out
• Multicast Packets In and Out
• Octets In and Out
• Discards In
• In Pause Frames
• Errors
• Alignment Errors
• Frame Too Long
• Late Collision Frames
• Excessive Collisions
• Multiple and Single Collision Frames
• Deferred Transmission
• In Bad Octets
• Undersized Frames
• In Fragments
• In and Out Bytes: 64, 127, 255,511, 1023
• In and Out Max Octets
• In Jabbers
• In Filtered
• Out FCS Errored
• Collisions
Related Topic:
614-330055-001 July 2009 5-27

Ethernet Bandwidth Utilization

Introduction
Users can view the ethernet bandwidth use for Eclipse regions, devices, or circuits in
ProVision. The Ethernet Bandwidth Utilization screen displays an overview of the
throughput bandwidth usage for the selected part of the network. This allows users to
rapidly identify if the throughput is exceeding the maximum bandwidth available for
the link or links. Normally, users select a Logical Link network or set of circuits to view.
Ethernet Bandwidth Utilization displays performance data for enabled ports and
channels. Data collection processes data for all enabled ports and channels. For
example, if a port was operated for three days and then disabled, the data from the
port’s enabled period would still be displayed, but no additional data would be saved.
If you select a large network to view, it takes time to generate the

Ethernet Bandwidth Utilization display: an hour or more.
Generating this view for a large network also may slow your
ProVision system processing.
Procedure
To view the ethernet bandwidth utilization for a container or a device:
1. Right-click the selected container or device. In the right-click menu, select
Performance > Ethernet Bandwidth from the drop-down menu.
2. ProVision retrieves the ethernet performance data from the server cache. While the
data is downloading, the data status displays in the lower left of the screen.

3. The Ethernet Bandwidth Utilization screen displays with its data for the device.
4. In the Table view, you can:

• Right-click on a circuit, and use the right-click menu to view additional
performance data for the circuit.
• Note the color of the data row for a circuit; these colors match the system’s
performance threshold settings.
5. To change the display from a table to a graph, click on the Show Graph button. A
message displays, showing the status of the graph as it is built.
614-330055-001 July 2009 5-29

6. The Graph view displays:
7. You can adjust the data and time range that display in the table and graph. Use
these Resolution options at the top of the screen:
• 15 Minute - Screen displays 15 minute performance data, for a time range of 15
minutes to 7 days.
• Daily - Screen displays daily performance data, for a time range of 1 week to 12
months.
• Use the Time Scale slider to minimize or maximize the time range of the data
displayed.
• Show Channels - Check this box to display channel details for objects in the
Object column of the table.
• Show Ports - Check this box to display port details for objects in the Object
column of the table
8. You can change the data in the graph display to be either% of utilization or number
of Mbps. Click the Show Mbps or Show% button to change the option.
9. You can sort the values in the data table. Go to the Options menu and select Table
Options. Then, go to the Sorting tab. Use the drop-down menus and Ascending/
Descending buttons to set up your main three sorting criteria.
10. In the Bandwidth Utilization graph, you can adjust the data view. Check the Show

Full Scale box to view the% Utilization range from 0 to 100%. Uncheck this box to
view only the minimum and maximum values in the used range for the %
Utilization.
11. To save the Ethernet Bandwidth Utilization data, go to the File menu and select the
Save option you want:
• Save or Save As to save the data setup for future use in this screen.
• Save to File to save the data as a semicolon-delimited text file.
12. Click Close to close the screen.
The features of the Ethernet Bandwidth Utilization screen are listed below.
Feature Description
Time Scale The Resolution frame contains the functions for selecting the data resolution.
Data Table The Table displays the raw data for the selected data resolution. Change the
table sorting using the Options > Table Options function in the menu. Each data
row displays end-to-end circuit information for a circuit, including its GE/E5
termination. Sort by any column, especially by Ethernet Circuit. Users can also
export and save the data using the File > Save Data function in the menu.
• Ethernet Circuit = The ethernet circuit

• Object = The type and name of the object. May include channel and port
data, if selected.
• Container = The container for the object.
• RX = Percent of throughput bandwidth use for received (incoming) traffic.
• TX = Percent of throughput bandwidth use for sent (outgoing) traffic.
614-330055-001 July 2009 5-31

Feature Description
Data Graph The Graph displays the data points for the selected parameters. The selected
parameters appear as color-coded data points in the chart and in an
automatically-generated legend. You can:
• Click the Show Mbps or Show % button to change the way the data is
displayed in the graph.
• Click on any data point in the graph and hover over it to view a pop-up with
its date, time, and data details.
You can also adjust the layout of the graph by selecting or deselecting Show
Full Scale.
Show/Hide Click this button to Show or Hide the data graph.
Close Click this button to close the screen.
Related Topic
Viewing Ethernet Performance on page 5-21

Performance Features
• Performance History on page 5-33
• Performance Trends on page 5-38
• Performance Thresholds on page 5-42
Performance History
Introduction
The performance history feature allows you to quickly and efficiently determine if there
are performance problems in your network. This feature also correlates collected
performance data with Events occurring within the same period of time.
The performance history feature is supported in any device that collects performance
data including:
• Eclipse Link • DART
• Eclipse IDU • Velox
• EfficientSite Manager • TNet
• XP4 • TRuepoint: 5000, 4000, 4040, 6400,
6500
• Altium/ADR
• MegaStar
• MicroStar
Performance History is created using daily performance data from the

ProVision database. This includes invalid data, as an example of
performance problems. Daily performance data in the database is
required for Performance History output.
TRuepoint 6500 radios have a specific Performance History display. This

is described in detail in this section.
Procedure
To view the Performance History for a selected device:
1. Open the submap for the device.
2. Right-click the link for the device, and select Performance History from the
drop-down menu.
614-330055-001 July 2009 5-33

3. The performance history for the selected device displays.
The features of the standard Performance History window are listed below:
Feature Description
Resolution Select 15-Minute or Daily to display the desired level of detail for the data.
Graph Summary bar The graph summary bar is a represents all the performance data that has
been collected for the selected device. It has features that allow you to
quickly select a range of data and display it in the Graph View or the Report
View.
Place the cursor at any point along the graph summary bar and a pop-up
box appears which indicates the date and time at any point along the
graph summary bar.
Graph View Select the Graph radio button to view the data as a graph.
The Detail Window Showing feature allows you to select a portion of the
performance data to display it in the Graph View. Place the cursor at a
location along the Graph Summary and click once. The white bar indicates
the new range that displays in the Graph View.

Feature Description
G.826 or G.828 Data The Graph View displays the G.826 or G.828 performance data for three
types of data: Errored Seconds, Severely Errored Seconds, and Unavailable
Seconds. These three types of performance data are a good indication if
there is a problem with the device.
Each column on the graph represents one time period; either 15-minute
or daily, depending on the resolution that was selected.
• A red box in the column represents at least one instance of the
performance condition for that time period. For example, at 17:30,
there was at least one instance of an unavailable second for that
15-minute time period.
• A yellow column indicates that there was incomplete amount of data
collected for that time period.
• A gray column indicates that there was no data collected for that time
period.
Receive Signal Level You can also view the RSL (receive signal level) for any time period from
(RSL) the Graph View. Place the cursor at any time period and a pop-up box
appears that lists the minimum, maximum and mean RSL for that time
period.
614-330055-001 July 2009 5-35

Feature Description
Report View .Select Report to view the data as a report.

The Report Data Range feature allows you to select a portion of the
performance data to be represented in the Report View.
Click and drag the cursor along the Graph Summary. and click once. The
black bar indicates the new range that is represented in the Report view.
You can select a range of data from the Graph View to be displayed in the
Report View. Click and drag any number of columns. The data from
resulting columns highlighted in blue displays in the Report View.
The data that displays here is based on data provided by the radio. In
particular, TRuepoint radios show a brief range of values here.
The Report View displays the aggregated data for the selected time
periods.
Event Browser The report view also displays an Event Browser that lists the events
associated with the selected device that have occurred during the selected
Report Data Range. This feature is a very powerful troubleshooting tool that
helps you narrow down the cause of faults in your network.
Save / Print The Save button allows you to save the performance history data to a text
file. The Print button allows you to print a Performance Details Report.
These two features are supported in the Report View.

Feature Description
Remote Select the Remote button to open the Performance History window for the
radio at the other end of the link.
Note: This feature is only supported in the Eclipse link device.
Refresh Collects the latest data from the device and updates the information
displayed in the Performance History window.
Close Closes the Performance History window.
TRuepoint 6500 Performance History Window

The TRuepoint 6500 Performance History window differs from the standard
Performance History window in several ways.
• Performance history is applied to the 6500 MTSU channels. It is presented for each
MSTU line and for each radio channel.
• Data values for Radios provide data for radio channel performance; Radio Errored
Seconds, Radio Severely Errored Seconds, Radio Unavailable Seconds.
• Data values for Line provide data for tributary lines; Line Errored Seconds, Line
Severely Errored Seconds, Line Unavailable Seconds.
• RLM = Receiving Level of Main Receiver.
• RLSD = Receiving Level of SD Receiver.
614-330055-001 July 2009 5-37

EfficientSite Manager Performance History Window

The EfficientSite Manager Performance History window reports on two performance
values: temperature and humidity. These are noted for both enclosure and ambient
readings, as recorded by the EfficientSite Manager.
Related Topic:
Performance Trends on page 5-38
EfficientSite Manager System on page 5-98
Performance Trends
Introduction
The performance trends feature allows you to view trends in the collected performance
data for up to 2 devices by displaying the data in both graphical and tabular form.
Simply view the data for one device, or compare two different devices. You can select
which parameters you would like to display, as well as print and save the data for
processing in other applications, such as MS Excel.

The performance trends feature is supported in any device that collects performance
data, including:
• Altium • MegaStar
• Constellation (only 3DS3, • Radwin WinLink 1000
4DS3, and 155mbit)
• Spectrum II SNMP
• DART
• TNet
• DVM
• TRuepoint: 5000, 4000, 4040, 6400,
• Eclipse 6500
• EfficientSite Manager • Velox
• LE3000 • XP4
• MicroStar
The type of data collected varies for each device. However, it typically includes:
• G.826/G.821 performance statistics
• RF power performance, including RSL and TX power
Procedure
To view the Performance Trends for a selected device:
1. To open the Performance Trends screen:
• For most devices, navigate to the device in the Physical Tree Viewer. Right-click
it and select Performance > Trends.
• For Eclipse devices, navigate to the device, right-click it, and select Open Device.
In the device Submap, right-click on links or plug-ins to select Performance >
Trends.
• For XP devices, navigate to the device, right-click it, and open the Submap. In
the device Submap, right-click on one of the two links to select Performance >
Trends.
614-330055-001 July 2009 5-39

2. The Performance Trends window for the selected device displays.
The features of the Performance Trends window are listed below:

Feature Description
Parameters Pane Select the parameters to be displayed from the list in the
Parameters tab on the left side of the screen.
Select the data type, 15-Min or Daily.
Then, select the Update button to display the selected
parameters in the Graph and Data tabs.
Select the Clear button to clear the selected parameters in the
graph tab.
Chart Options Select the chart options from the list in the Chart Options tab on
the left side of the screen. This tab allows you to select:
• Chart Type - Line, Area, or Bar
• Chart Type Settings - View data as lines, points, or both lines
and points.
• Visible Data - Select the days or time increments of data to
view in the chart.

Feature Description
Chart Tab The Chart tab displays the data points for the selected
parameters. The selected parameters appear as color-coded
data points in the chart and in an automatically-generated
legend. You can also adjust the layout of the graph using the
Chart Options.
Print Chart From the menu bar, select File > Print Chart to print the currently
displayed chart.
Data Tab Select the Data Tab to display the raw data for the selected
parameters. YOu can export the data using the Save Data
feature.
Select the Graph Tab to return to the graph view.
Save Data From the menu bar, select File > Save Data to save the data as a
semicolon-delimited text file.
Related Topic:
Performance Thresholds on page 5-42
614-330055-001 July 2009 5-41

Performance Thresholds
Introduction
When you set up a performance threshold, you are setting up a way to associate an
alarm or group of alarms with unexpected performance results.
For example, the performance criteria “Discards In” measures the number of times the
network has had so much traffic in the buffer that it discards the data at the ethernet
switch. You may want to know when there are too many (10 such discards within a
15-minute period, for example) which would indicate that there is a problem with data
transmission for that device. The performance threshold feature allows you to set up
this situation as a customized event.
The performance thresholds feature is supported in any device that collects
performance data including:
• Eclipse Link • XP4
• Eclipse DAC • Altium/ADR
• Eclipse IDU • DART
• Eclipse INU and INUe • Velox
• TRuepoint: 4000, 4040, 5000, • TNet
6400, 6500
• MicroStar
• MegaStar
You can also set up performance thresholds to a container, where the performance
thresholds apply to all devices within the selected container. This feature is supported
by all containers including:
• Root • Region • Site • Rack
Procedure
To set up performance thresholds for a selected device or container:
1. Right-click the selected device or container and select Performance Thresholds
from the drop-down menu.
2. The Performance Thresholds window for the selected device or container displays.
• If a non-Eclipse radio is selected, the left panel lists only the device name.
• If an Eclipse radio is selected, the left panel lists the Eclipse radio plus all of the
possible Eclipse plug-in devices.
• If an Eclipse plug-in is selected, the left panel lists only the selected plug-in.
• If a container is selected, the left panel lists all devices that support the

performance threshold feature.
3. Select the required device or plug-in. The central panel lists the alarms associated
with the selected device/plug-in.
• Select the 15-Min button to show/hide the alarms for radio 15-minute data
collection.
• Select the Daily button to show/hide the alarms for daily data collection.
4. From the list of alarms in the central panel, select the required alarm.
• Select the “+” (add) button to add a new performance threshold.

• Select the “-” (remove) button to remove an existing performance threshold.
The device selected (in the left panel) is now bold-face -- making it easier to locate
performance threshold events that have be previously created.
5. Enter the information in the right panel as follows:
• Event Description- Enter a name for the newly-created performance threshold.
• Trigger Value - Enter the number of times the alarm must occur before the performance
threshold is triggered.
• Severity - Select a severity level from the drop-down menu.
• Port - This displays only for Eclipse DAC objects. Select a port or channel that is
to be associated with the newly-created performance threshold.
6. You can create multiple thresholds for the selected device or container by repeating
steps 3 - 5 as often as required.
7. Select OK to save the performance threshold(s).
8. The performance threshold icon either appears next to the device/container, or
614-330055-001 July 2009 5-43

in the information pop-up for the device/container.

TRuepoint 6500 Performance Threshold Settings

The TRuepoint 6500 Performance Threshold settings differ from the standard
Performance Threshold settings in several ways.
The most important difference is that the performance threshold settings and readings
for a TRuepoint 6500 are split between the Protection channel and the Working
channels. This is done because, when a TRuepoint 6500 radio is functioning correctly,
the Protection channel is not being used, and its thresholds are zero.
You need to set the Protection values for the Performance Thresholds to zero. Set the
Working channels to your desired performance threshold values.
Related Topic:
614-330055-001 July 2009 5-45

WiMAX WSN ASN-GW Controller and Base Station

Management
Introduction
When ProVision is managing a WiMAX WSN ASN-GW Controller, you can view the
base stations that it controlls from within ProVision. ProVision can automatically
retrieve and display the data and status of all the base stations linked to the controller.
You can also view the Mobility Neighbor for a base station from the ASN-GW
Controller. A Mobility Neighbor is a neighboring base station, used for mobility
handovers of mobile stations and for load balancing.
Procedure
1. In the Tree Viewer, locate the WiMAX WSN ASN-GW Controller.
2. Right-click on the Controller and select Configuration - Configured Base Stations.
3. The Configured Base Stations screen displays. This screen lists all of the base
stations managed by this Controller.
4. Note that you can also Filter and Refresh from this screen.
5. To view the Mobility Neighbor for a specific Base Station, select the Base Station
and click the Get Mobility Neighbors button.
6. The Get Mobility Neighbors screen displays. This screen shows data for the base
station’s Mobility Neighbors.
7. To Save the Base Station or Mobility Neighbor data, click the Save button. You are
prompted to enter a file name. The data is saved as a .CSV file.
8. To close these screens, click Close.
Table 5-7. Configured Base Stations Screen
Column Value
Device Name Name of the Base Station
BS ID Identification of the Base Station.

Column Value
R6 Control IP address of the R6 control.
R6 Data IP address of the R6 data path.
Datapath Type Type of R6 data transmitted over the data path.
ASN-R Control IP address of the ASN-R controller for this base station.
ASN-R Data Path IP address of the ASN-R data path.

Type
Paging Group Notes the specific Group Controller; if none is assigned,

Controller notes this.
Table 5-8. Mobility Neighbors Screen
Column Value
Device Name Name of the Base Station.
Container Container that manages this Base Station in ProVision.
R6 Control IP address of the R6 control.
Neighbor ID Corresponds with the MAC address.
614-330055-001 July 2009 5-47

WiMAX Subscriber Station Connectivity

Introduction
When ProVision is managing a WiMAX base station, you can view its subscriber station
connectivity from within ProVision. ProVision can automatically retrieve and display
the data and status of all the subscriber stations linked to a base station. This is a fast
and convenient way to review subscriber station data; it also provides the most current
data on frequently changing subscriber devices.
Procedure
1. In the Tree Viewer, locate the WiMAX base station.
2. Right-click on the base station and select Configuration - Subscriber Station
Connectivity.
3. The Subscriber Station Connectivity screen displays. This screen lists all of the
subscriber stations that are connected to this base station.
Figure 5-4. Subscriber Station Connectivity
4. From this screen, you can:

• Filter - Click the Filter button to sort subscriber stations based on the available
values.
• Refresh - Click the Refresh button to obtain current data from the subscriber
stations.
5. You can view the details for a subscriber station. Right-click on the subscriber
station and select the Details option. The Subscriber Station Details display:
Figure 5-5. Subscriber Station Details
6. You can view the Customer Premises Equipment (CPE) for a subscriber station.
Right-click on the subscriber station and select the CPE list option. The Subscriber
Station CPE list displays.

Figure 5-6. Subscriber Station CPE List
7. Note that you can also Filter and Refresh from this screen.
8. To close these screens, click Close.
Table 5-9. Subscriber Station Connectivity Screen
Column Value
SS MAC Address Subscriber station MAC address.
SS IP Address Subscriber station IP address.
VLAN ID VLAN port ID.
SS Connectivity Connectivity status.
Admin State Administration status.
Provisioned Provisioning status.
Deregistered Registered or deregistered status.
Table 5-10. Subscriber Station Details
Item Values
CIDs Basic CID - Basic WiMAX channel ID

Primary CID - Primary WiMAX channel ID
Radio SS Config Oper. FEC Code - Current FEC code in the downlink.
Downlink
Admin. FEC Code - Target FEC code in the downlink.
Radio SS Config Oper. FEC Code - Current FEC code in the uplink.
Uplink
Admin. FEC Code - Target FEC code in the uplink.
Uplink Channel CINR and RSSI for the uplink.

Measurement
Table 5-11. Subscriber Station CPE List
Column Value
CPE MAC CPE MAC address.

Address
CPE IP Address CPE specific IP address.
Gateway CPE gateway address.

Address
CPE VLAN ID VLAN identification for the CPE.
CPE VCI VCI identification for the CPE.
614-330055-001 July 2009 5-49

Craft Tools and Diagnostic Controls
A craft tool enables you to connect to a device to manage, troubleshoot and maintain
the device. These craft tools can be launched from within ProVision. This section covers
the following topics:
• List of Craft Tools
• Launching a Craft Tool
• WMT Craft Tool
• TNet Web Craft Tool and Diagnostics
• Diagnostic Controls for Selected Devices
The majority of HSX devices can be accessed via a specific craft tool. Certain devices are
accessed via diagnostic controls. Non-HSX devices can be accessed via a Telnet or
browser session.
The specifics of how to use each craft tool are documented in the related
device manual or online help.
List of Craft Tools

This table lists the Harris Stratex Networks devices, associated craft tools and where to
access help information.

Table 5-12. Harris Stratex Networks Devices and Related Craft Tool
Device Craft Tool Craft Tool Manuals and Related Help Sources
Eclipse Portal Eclipse User Guide (P/N 260-668066-001)
TRuepoint TRuepoint TRuepoint 5000 & 4040 6-38 GHz Operator’s Interface (P/
Web CIT N IMN-90303-E06)
TRuepoint 6400 & 6500 Operator’s Interface (P/N
IMN-907004-E01)
MicroStar MicroStar MicroStar Operator’s Interface

Web CIT
Constellation FarScan FarScan for Windows Instruction Manual (P/N

IMN-006120-E11), also see Diagnostic Controls for
MegaStar
Selected Devices on page 5-85.
All Altium WMT Online help is available from within the craft tool. A brief
description is in WMT Craft Tool on page 5-55.
ADR 2500
ADR 155c
DXR DXR NET DXR NET NMT Installation and Operation Manual
(PN IOM-NMS-2/2.4)
Velox NCT NCT User Guide
TNet TNet Web A brief description is in TNet Web Craft Tool and
Diagnostics on page 5-58.
XP4 XP Web If user accounts have been set up in the XP4 radio, XP Web
opens with view-only access, otherwise it opens with
administration access. Context-sensitive online help is
available in XP Web.
Note: If you are using Windows XP SP2, make the following
adjustment to your web browser:
1. Open your web browser.
2. Select Tools > Internet Options and select the Advanced
tab.
3. Under the Security section, select the Allow active
content to run on files on My Computer option.
DART None: See Diagnostic Controls for Selected Devices on page 5-85.
Diagnostic
DVA
Controls
CAU instead
Memotec CX-U CXTool See LE3000 or Memotec Craft Tool Installation on

page 5-54.
LE3000/
WL1000
614-330055-001 July 2009 5-51

Device Craft Tool Craft Tool Manuals and Related Help Sources
Generic device • Telnet The Launch options displayed for a generic device are
dependant on the information entered into the Browser
• Browser
Port and Telnet Port fields when the device was deployed.
Launching a Craft Tool

Craft tools are software applications used to monitor and maintain devices. ProVision
includes several craft tools. Launching a craft tool from ProVision extends your ability
to troubleshoot, manage, and maintain devices.
From a craft tool you can perform the following:
• Change a radio’s configurations
• Run local and remote loopback tests to help isolate link or radio problems
• Monitor and troubleshoot system status and performance
• Switch protected radio configurations
• Speed up the software upgrade process by downloading the software used to control
radio operation.
A craft tool is launched via a ProVision right-click menu option for the selected device.
Procedure
To launch a craft tool from ProVision:
1. From the Tree Viewer or Map Viewer, right-click the required radio.
2. Select Launch <craft tool>. In this example, Launch DXR NL is selected.

3. Enter the radio security access details, as required.

The craft tool user interface window displays. For example, for an Eclipse node the
Portal Diagnostics - System Summary window displays.
4. Perform the required functions on the selected radio.

5. Close the craft tool window.
Related Topics:
• LE3000 or Memotec Craft Tool Installation on page 5-54
• WMT Craft Tool on page 5-55
• TNet Web Craft Tool and Diagnostics on page 5-58
• XP4 Craft Tool and Diagnostics on page 5-72
• Diagnostic Controls for Selected Devices on page 5-85
614-330055-001 July 2009 5-53

LE3000 or Memotec Craft Tool Installation

Introduction
To be able to launch the Memotec craft tool or the LE3000 craft tool from the device in
ProVision, you must install the craft tools on the ProVision Client and enable it through
ProVision as an accessible application.
Procedure
1. In ProVision, ensure that at least one Memotec/LE3000 device is deployed.
2. Using the media provided by Memotec/LE3000, on the ProVision Client PC,
download and install the craft tool.
3. Open the ProVision Client.
4. Right-click on a Memotec device. From the right-click menu, select Applications >
Edit Applications. The Edit Applications screen displays.
5. Click the Add button. Enter the following data into the row that appears:
• Name = Craft tool name: CXTool for Memotec
• Executable Path = Path to the file folder on the PC where the craft tool is
installed.
• Parameters = %ipaddress
6. Then, click OK.
7. The craft tool is now linked to ProVision. It can be accessed from the Memotec/
LE3000 device right-click menu,

WMT Craft Tool

Introduction
The WMT craft tool can be launched from within ProVision and enables you to connect
to an Altium, Altium MX, Altium 2+0 MX or ADR, ADR155, or ADR2500 radio to
manage, troubleshoot and maintain the device.
Prerequisite
To get the full functionality of WMT, you must make the following change to the Event
Browser for the selected radio.
1. Double-click the selected radio to open the Event Browser.
2. Select the filters icon.
3. In the Filters window, check the Severity checkbox. Then, select the Information
checkbox.
The Information checkbox must be selected in order to display all events in the
WMT craft tool.
Procedure
To launch the WMT craft tool:
1. Right-click the selected radio icon. From the right-click menu, select Launch WMT.
2. A browser window opens that displays the IP address of the radio as a hot link.
Select the hot linked address.
3. A welcome screen displays on the browser window. Select the Apply button. (Leave
the Password text box blank since a password in not required.)
614-330055-001 July 2009 5-55

4. If you have pop-up blocking software activated, you may see a message like this one
on your browser. Select the message, then select Temporarily Allow Pop-ups.
5. The WMT craft tool displays in a pop-up browser window. The color-coded security
level is displayed for each port.
6. The Shelf View is the default screen and displays a graphical representation of the
selected radio.
The color-coded severity level for each port (red = ______, yellow =
_______) displays on the Shelf View.
7. Select one of the slots (A, B, C or D) to display the submenu for that slot. The
example below shows the submenu for the ADR 35M/45M board that is installed
in slot A.
8. Select the fan or the motherboard to display their submenus.
9. Select any port in the Shelf View to display and manage the configuration for the

selected port.
10. Select the Help link to display the on-line help resource. Select the Shelf View link to
return to the current screen.
Related Topics:
614-330055-001 July 2009 5-57

TNet Web Craft Tool and Diagnostics

To manage a TNet device at the craft tool level, you can either:
• Use the TNet craft tool - see Launching the TNet Web Craft Tool
• Use TNet Diagnostics
The TNet Web craft tool can be launched from within ProVision. It enables you to
connect to a TNet device to manage, troubleshoot and maintain the device.
Depending on the device, TNet Web allows you to

• View information on the TNet radio and proxy
• Create user-defined inputs and outputs and assign severity levels
• Activate or de-activate an input or output by manually setting the state (open or
closed)
• Refresh the display to view up-to-the-minute status of the radio
The ProVision administrator and the NOC Engineer both have “read/write” access to
the TNet Web craft tool. The NOC Operator has “read only” access.
If you are using Windows XP SP2, make the following adjustment to your web browser:
2. Select tools > Internet Options and select the Advanced tab.
Under the Security section, select the option Allow active content to run on files on My
Computer.
The available features vary for the different TNet devices and are listed below.

Table 5-13. TNet Web Available Features with each TNet Device
Device Icon Device Available Features
Spectrum I Information, Save, Refresh
W Series and Information, Save, Refresh

and
Protected W Series
Classic II Information, 4 Alarm Inputs, Save, Refresh
and Quantum and Information, 6 Alarm Inputs, Save, Refresh

Protected Quantum
and LC Series and Information, 8 Alarm Inputs, Save, Refresh

Protected LC Series
M Series and Information, 8 Alarm Inputs, Save, Refresh

and
Protected M Series
M Fiber Information, 8 Alarm Inputs, Save, Refresh
and Spectrum II and Information, 8 Alarm Inputs, 4 Alarm Outputs, Save,

Protected Spectrum II Refresh
User-Defined Inputs and Outputs

You can customize the inputs for the TNet radios by assigning names and severity
levels.
When an assigned input (or output) is signaled in the network, the input appears in the
Event Browser as its user-defined name and its user-defined severity. In the example
below, the item with the red icon is at Critical severity; the yellow icon shows Minor
severity; and the white icon is Information only.
614-330055-001 July 2009 5-59

Launching the TNet Web Craft Tool

To launch TNet Web:
1. From the Tree Viewer or Map Viewer right-click the required TNet radio. Select
Launch TNet Web.
2. The TNet Web user interface window displays in the web browser.
The Information tab lists general information on the selected radio and on the TNet
Proxy device.
1. The Alarm Inputs tab and Alarm Outputs tab are only available on certain TNet devices.
If they are available, select the Alarm Inputs tab.
This tab lists the input configuration for the selected TNet radio.
See Table 5-14, “Alarm Input and Alarm Output Settings for TNet Radios,” on
page 62 for information on changing the input configuration.

2. Select the Alarm Outputs tab. (Available on the Spectrum II devices.)
This tab lists the output configuration for the selected TNet radio.
See Table 5-14, “Alarm Input and Alarm Output Settings for TNet Radios,” on
page 62 for information on changing the output configuration.
3. Select the Refresh icon to check the current state of the radio. The Alarm Inputs
and Alarm Output tabs display the updated configurations.
4. Select the Save icon to save the changes to the radio.
TNet Web asks if you want to save the changes. Select OK.
TNet Web displays the following message when the data is successfully written to
the radio.
5. Close the web browser to end the TNet Web session.
614-330055-001 July 2009 5-61

This table lists the Alarm Input settings and the Alarm Output settings for the TNet
radios.
Table 5-14. Alarm Input and Alarm Output Settings for TNet Radios
Item Description
Name User-defined name for the alarm input or output.
State Allows you to physically open (activate) or close (de-activate)

the individual alarm inputs and outputs.
Severity Allows you to assign a severity level to each alarm input and
output:
The severity options for Alarm The severity options for Alarm
Inputs are: Outputs are:
Current Status Displays the current status of the input or output.
Save Saves the input and output configuration to the radio.
Refresh Refreshes the current screen by retrieving the current state of

the inputs and outputs from the radio.
Related Topics:
• TNet Diagnostics on page 5-62
TNet Diagnostics
This section covers the following topics
• TNet Diagnostics - Protection Tab on page 5-64
• TNet Diagnostics - G.821 Performance Tab on page 5-66
• TNet Diagnostics - CB 149 Performance Tab on page 5-68
• TNet Diagnostics - RSSI Tab on page 5-70

Diagnostic tools are used when an event indicates there is a fault with a TNet radio, and
can help to determine if the fault is equipment or path related.
When Diagnostics is selected, ProVision automatically logs into the TNet radio,
retrieves the diagnostic settings from the radio, and displays them in the Diagnostics
window.
The diagnostic tools for the TNet radios are:

• Protection status and settings
• G.821 performance data (Spectrum II radios only)
• CB 149 performance data (all other, non-Spectrum II radios)
• RSSI (receive signal strength indication) data
Access to the Diagnostics menu option is dependant on your ProVision

security access level.
614-330055-001 July 2009 5-63

TNet Diagnostics - Protection Tab

ProVision allows you to set up a protected circuit with two links: A and B. If one link is
lost, the other can be set to automatically take over with no data loss.
The Protection tab in the Diagnostics window allows you to configure a protected link
for a specific TNet radio.
The parameters in the Protection tab are defined below.

Table 5-15. Protection Parameters
Parameter Definition
Protection Status:
TX Lock Identifies the current locking mode of the transmitter function:

• Automatic - Automatic switching is currently in effect for the
transmitter function.
• Locked - Manual switching is currently in effect for the
transmitter function.
TX Online Identifies which transmitter function of the protected pair is

currently online:
• Online A - The Side A transmitter function is currently online.
• Online B - The Side B transmitter function is currently online.
RX Lock Identifies the current locking mode of the receive function:

• Automatic - Automatic switching is currently in effect for the
receive function.
• Locked - Manual switching is currently in effect for the receive
function.

RX Online Identifies which receive function of the protected pair is currently

online:
• Online A - The Side A receive function is currently online.
• Online B - The Side B receive function is currently online.
Protection Settings:
Automatic Select the Automatic checkbox to enable automatic switching. In

automatic mode, built-in protection circuitry automatically
determines which radio transmitter (either A or B) is in service.
(The TX Lock and RX Lock features are inactive if the Automatic
checkbox is selected.)
TX Lock Locks in the transmit signal to either Link A or Link B.

• Lock A - Locks the transmit function to Side A.
• Lock B - Locks the transmit function to Side B.
RX Lock Locks in the receive signal to either Link A or Link B.

• Lock A - Locks the receive function to Side A.
• Lock B - Locks the receive function to Side B.
Related Topics:
614-330055-001 July 2009 5-65

TNet Diagnostics - G.821 Performance Tab

G.821 is a performance standard for microwave radios. The G.821 Performance
window lists the relevant performance parameters.
Some parameters are measured over a measurement interval; the interval ending at the
time stamp displayed in the G.821 Performance tab.
Table 5-16. G.821 Performance Parameters
Available Seconds Total available time during a measurement interval.
Unavailable Seconds Total unavailable time during a measurement

interval.
Errored Seconds A one-second period with one or more errored blocks

or at least one defect.
Severely Errored Seconds A one-second period which contains at least 30%

errored blocks or at least one defect.
Total Test Seconds Total time of the measurement interval.
Degraded Minutes Number of groupings of 60 available seconds,

excluding severely errored seconds that have a BER
worse than 10-6.
Time Stamp Date and time of the most recent update to one or
more performance counters. Date and time
information displays in the following format:
• Month, day and year (for example: Mar-06-2005)
• Time in hh:mm:ss format (for example: 17:38:21)
The various functions in the G.821 Performance tab are defined below.

Table 5-17. Functions in the G.821 Performance Tab
Reset Resets all parameters to zero and sets the time stamp to the
current day and time.
Refresh Collects the most updated values of the parameters from the
radio, displays the updated values in the G.821 Performance tab,
and sets the time stamp to the current date and time.
OK Closes the TNet Diagnostics window.
Cancel Closes the TNet Diagnostics window without saving any changes
made to the performance parameters. Any changes are saved if
the Reset, Refresh, or Apply buttons were selected.
Apply Saves the changes made to the performance parameters without

closing the TNet Diagnostics window.
Related Topics:
614-330055-001 July 2009 5-67

TNet Diagnostics - CB 149 Performance Tab

CB 149 is a performance standard for microwave radios. The CB 149 Performance
window lists the relevant performance parameters.
The parameters are defined below. Some are measured over a measurement interval,
the interval ending at the time stamp displayed in the CB 149 Performance tab.
Table 5-18. CB 149 Performance Parameters
Single Errored Seconds The number of one-second periods with one

errored block or defect.
Multiple Errored Seconds The number of one-second periods with more than
one errored block or defect.
Severely Errored Seconds The number of one-second periods which contain

at least 30% errored blocks or at least one defect.
Frame Errored Seconds The number of one-second periods that an

Out-Of-Frame error is detected.
Data Missing Indicator Contains a flag indicating the validity of

performance counter contents on Side A or Side
B:
• “0” = All performance counters reflect an
accurate count.
• “1” = One or more performance counters have
reached their maximum value. When this
condition occurs, data collection is stopped and
one or more counters are reset to 0. In this
instance, the operator performs a manual reset
operation from the CB-149
Frame Error Count The number of Out-of-Frame errors during a

measurement interval.

Total Parity Errors Contains an internal count used for calculating the
bit error rate on Side A or Side B.
Elapsed Seconds Total number of seconds that have elapsed since

test counters were last reset on Side A or Side B.
• Month, day and year (for example:
Mar-06-2005)
• Time in hh:mm:ss format (for example:
17:38:21)
The various functions in the CB 149 Performance tab are defined below.
Table 5-19. Functions in the CB 149 Performance Tab
radio, displays the updated values in the CB 149 Performance
tab, and sets the time stamp to the current date and time.
Related Topics:
614-330055-001 July 2009 5-69

TNet Diagnostics - RSSI Tab

RSSI is a performance standard for microwave radios. The RSSI Performance window
lists the relevant performance parameters.
Some parameters are measured over a measurement interval, the interval ending at the
time stamp displayed in the RSSI tab.
Table 5-20. RSSI Parameters
RSSI Low (dBm) The minimum signal strength recorded on Side A or

Side B during the measurement interval.
RSSI High (dBm) The maximum signal strength recorded on Side A or

Side B during the measurement interval.
RSSI Current (dBm) The current signal strength level on Side A or Side B.
RSSI Sample Time The total minutes during which RSSI data has been
collected, which encompasses the interval since RSSI
data was last reset.
• Month, day and year (for example: Mar-06-2005)
• Time in hh:mm:ss format (for example: 17:38:21)
The various functions in the RSSI tab are defined below.

Table 5-21. Functions in the RSSI Tab
radio, displays the updated values in the G.821 Performance tab,
and sets the time stamp to the current date and time.
OK Closes the TNet Diagnostics window.
Apply Saves the changes made to the performance parameters without

closing the TNet Diagnostics window.
Related Topics:
614-330055-001 July 2009 5-71

XP4 Craft Tool and Diagnostics

This section covers the following XP4 topics:
• Launching the XP4 Craft Tool on page 5-72
• Launching the XP4 Diagnostics on page 5-72
• Activating and Deactivating an XP4 Tributary Loopback on page 5-73
• Activating and Deactivating an XP4 Local Loopback on page 5-78
• Viewing/Changing XP4 Protection Settings on page 5-81
• Resetting an XP4 Radio Device on page 5-84
For XP4 radios, you can access either the XP4 craft tool or the diagnostic tools. You use
the diagnostic tools when an event or events indicates there is a fault with an XP4 radio,
to determine if the fault is equipment or path related.
Launching the XP4 Craft Tool

If you are using Windows XP SP2, make the following adjustment to your web browser:
2. Select tools > Internet Options and select the Advanced tab.
3. Under the Security section, select the Allow active content to run on files on My
Computer option.
To launch the XP4 craft tool:
1. From the Tree Viewer or Map Viewer right-click the required XP4 radio. Select
Launch XP Web.
2. The XP Web user interface window displays in the web browser. If user accounts
have been set up in the XP4 radio, XP Web opens with view-only access, otherwise
it opens with administration access. Context-sensitive online help is available in XP
Web.
Launching the XP4 Diagnostics
Access to the Diagnostics menu option is based on your ProVision

1. Right-click on an XP4 radio.

2. From the right-click menu, select Diagnostics.
3. ProVision retrieves the diagnostic settings from the radio, and displays them in the

Diagnostics screen.
Loopback tests are run from the local radio using test patterns generated
by externally connected user test equipment. Using a radio tributaries,
loopback tests send test patterns through either the near end IDU or the
entire system, then verify the accuracy of the data being sent or
received. The number of error occurrences, if any, are captured and
handled by the external test source.
Activating and Deactivating an XP4 Tributary Loopback
Introduction
The tributary loopbacks can be applied to the local radio or the remote radio of a link.
Only the tributary loopbacks that are applicable to the selected XP4 radio are displayed
in the Trib loopback tab. Normally, you would run one loopback test at a time. For
example, if a tributary loopback test is running you must first stop the tributary
loopback before activating a digital ODU loopback.
When you run loopback tests on the online unit, traffic is affected.
614-330055-001 July 2009 5-73

Table 5-22. Tributary Loopbacks for XP4 Radios
Loopback Type Loopback Purpose
Local Tributary Loopback To locate faults in equipment and cable connections to the local IDU.
The Local loopback does this by routing each tributary input (data
applicable to:
from customer) directly to the corresponding tributary output (data
2/4/8x radios to customer).
16x E3/DS3 radios Any combination of tributaries can be configured for loopback.
The following diagram shows a local tributary loopback signal path:
Remote Tributary Remote tributary loopback tests enable you to confirm link operation
Loopback with the aid of a connected BER test-set.
applicable to: This loopback is used for locating faults in equipment and cable
connections by connecting the transmit data stream directly to the
2/4/8x radios
receive data stream in the remote IDU. It checks the functionality of
16x E3/DS3 radios the local and remote sides in both directions.
Any combination of tributaries can be configured for loopback.
The following diagram shows a remote tributary loopback signal path:
Remote SU E3/DS3 The Remote SU loopback locates faults in equipment and tributary
Tributary Loopback cable connections by looping a DS3 or E3 tributary input (data from
customer) from the remote side to the local side of the link, checking
applicable to:
the functionality of the local and remote sides in both directions.
16x E3/DS3 radios
The SU loopback is only available for the remote switch unit. There is
no SU loopback for the local switch unit. Customer data coming
through the local switch gets checked by the local IDU ES3/DS3
loopback.
Note: This loopback is only used for protected E3 and DS3 systems
as these connect to a switching unit (SU).
The following diagram shows a remote SU E3/D3 tributary loopback
signal path:

Loopback Type Loopback Purpose
Local MSU E3 Tributary To ensure the MSU is getting a signal from customer equipment. The
Loopback local MSU E3 loopback feeds the output of the multiplexer into the
demultiplexer in the MSU, looping all tributaries between 1 and 16 at
applicable to:
the local side.
16x E3/DS3 radios Note: This tributary loopback is only applicable to protected E3
radios with an MSU.
The following diagram shows a local MSU E3 tributary loopback signal
path:
Local MSU E1 Tributary To ensure the MSU is getting a signal from customer equipment. The
Loopback local MSU E13 loopback feeds the output of the multiplexer into the
demultiplexer in the MSU, looping all tributaries between 1 and 16 at
applicable to:
the local side.
16x E3/DS3 radios Note: This tributary loopback is only applicable to protected E1
radios with an MSU.
The following diagram shows a local MSU E3 tributary loopback signal
path:
Procedure
To activate or deactivate a tributary loopback:
1. From the Tree Viewer or Map Viewer, right-click the XP4 radio icon.
The right-click menu displays.
614-330055-001 July 2009 5-75

2. Select Diagnostics.
A Diagnostics window displays with the settings uploaded directly from the radio.
The Trib Loopbacks controls displayed, varies depending on the type of XP4 radio
and whether or not it is protected.
The example below illustrates the loopback view for an XP4 2/4/8x radio:
The example below illustrates the loopback view for an XP4 16x E3/DS3 radio:
3. Select another tributary loopback control if the Local Loopback is not required.
4. Select the required tributary (or tributaries).
5. To activate the selected tributary loopback on the radio, select Apply. The following

message displays.
6. To continue writing the loopback data to the radio, select Yes. The Diagnostic
window is updated and shows the status as read from the radio.
You can only run loopback on a link at a time. So you need to stop the
currently active loopback before you can start another one.
7. Deselect the tributaries (Trib1, Trib2, and so forth) that have a loopback applied by
selecting the required Trib checkboxes.
Exceptions
If a correct login username and password for this radio has not been set up in ProVision
the following message displays when you attempt to write data to the radio.
If a local loopback is already active and you attempt to activate a trib loopback the
following message displays.
614-330055-001 July 2009 5-77

If ProVision is unable to contact the XP4 radio, the following message displays.
Related Topics:
Activating and Deactivating an XP4 Local Loopback
Introduction
Local loopbacks help to identify which component in the radio is causing the fault. This
table describes the loopbacks available for the local radio and their uses.
In a link, the local radio is the radio nearest to the ProVision server. Conversely, the
remote radio is the far end of the link.
If a loopback is applied to the remote radio then ProVision cannot communicate with
the radio to deactivate the loopback and a service agent must be sent to the remote
radio’s site to manually deactivate the loopback.
Table 5-23. XP4 Local Radio Loopbacks
Local Loopback Loopback Purpose
ODU Analog To determine if the fault lies in the ODU. The loopback checks the signal
processor related analog circuits, and the microprocessor and related digital
circuits in the local ODU. The loopback does this by routing the composite
data stream at the output of the 2-4 level converter directly to the
demodulator output, bypassing the transmit and receive RF modules. The
ODU analog loopback includes the entire baseband path.
The following diagram shows an ODU analog local loopback signal path:

Local Loopback Loopback Purpose
ODU RF Note: This loopback is only available on 23-38 GHz XP4 Plus radios but is standard
for the XP4 Classic radios.
Note: This loopback is not available when the local XP4 has a MSU or a SU.
The transmitter of the remote ODU is muted to prevent interference.

This loopback provides an unambiguous check of all active circuitry in a XP4
terminal. The transmit frequency of the local ODU is changed to transmit to
its own receiver at maximum power.
The following diagram shows an ODU RF local loopback signal path:
IDU Digital To route the outgoing data stream to the incoming data stream, bypassing
the AMI conversion. All tributary inputs are multiplexed and de-multiplexed
and returned to the tributary outputs.
Note: The incoming data stream from the remote terminal is affected.
The following diagram shows an IDU Digital local loopback signal path:
ODU Digital To check the microprocessor and related digital circuitry (including the
IDU-ODU cable and interface) in the ODU. The ODU digital loopback routes
the composite digital data stream prior to the digital-to-analog converter
directly to the multiplexer input, bypassing the RF and analog modules. The
local ODU digital loopback includes the tributaries, transmit and receive
multiplexers, scrambler, and FEC circuitry.
The following diagram shows an ODU digital loopback signal path:
Procedure
To activate a local loopback:
The Diagnostics window displays.
614-330055-001 July 2009 5-79

3. Select the Local Loopbacks tab.

The Local Loopback options are displayed.
4. Select the required local loopback.

5. To activate the selected loopback, select Apply.
The following message displays.
6. To continue writing the loopback data to the radio, select Yes.

7. To deactivate a loopback, select Off. Then, click Apply.
8. To close the Diagnostics window, select OK.
Related Topics:
• Viewing/Changing XP4 Protection Settings on page 5-81

Viewing/Changing XP4 Protection Settings
Introduction
From the Protection Settings tab you can perform the following actions:
• View the protection type set for this link
• Enable/disable the SU front panel rocker switches
When the rocker switches are disabled the protection type and the Transmit (Tx)
mode cannot be changed locally at the radio
• Change the status of the radio transmitter to force it online or offline
To guard against service interruptions, an XP4 radio link can be operated in protected
mode, providing link continuity if a fault occurs in the primary radio. A protected
system is configured by adding an indoor, rack-mounted protection Switching Unit
(SU) and another standby radio terminal. The ODUs may be connected to a waveguide
coupler or splitter, connected to one antenna, or directly connected to their own
antennas.
The protection SU is activated by an alarm condition in the primary link. The following
alarm conditions trigger a switch from the primary to the secondary radio:
• Loss of lock on transmit signal
• Loss of transmit power
• Frame loss (receive),
• BER alarm
• Loss of IDU transmit signal
• DC power loss
• Cable fault
• Loss of tributary input to online IDU (for E3, DS3, and 16E1 systems)
Procedure
To view and/or change the selected XP4 radio’s protection settings:
The Diagnostics window displays.
614-330055-001 July 2009 5-81

3. Select the Protection tab.

The radio’s protection details are displayed on the Protection tab.
The Protection tab fields are defined in Table 5-24.

4. If required, make changes to the protection settings.
5. To apply the changes to the radio, select Apply.
6. To close the Diagnostics window select OK.

Table 5-24. Protection Tab Fields for the XP4 Radio
Protection Tab - Description

Fields
Protection Type A display-only field that indicates:

• The protection type of the local or remote protection switch
The protection types available for the variant XP4 radios are:
2x/4x 8x 16E1,E3,DS3
Hot Standby X X X
Space Diversity]
Frequency Diversity X X X
Dual Link X
• The switching mode of the local or remote Tx rocker switch

The switching mode values displayed are:
• Auto The Tx rocker switch is in the Auto position and the
transmitter is configured to automatically switch when certain
alarm conditions are raised.
• Manual IDU A Tx Lock The Tx rocker switch is in the TX A position
and transmitter A is online.
• Manual IDU B Tx Lock The Tx rocker switch is in the TX B position
and transmitter B is online.
When the SU or MSU is operating in Frequency Diversity mode, both
transmitter A and B are always active. The position of the Tx rocker
switch is not applicable.
Front Panel Lock This field indicates the current state of protection switch front panel
controls. The options are:
• Unlocked The SU or MSU front panel rocker switches are unlocked
and can be changed locally at the SU.
• Locked The SU or MSU front panel rocker switches are locked and
cannot be used locally to change the protection type.
Tx Switch This field indicates the current status of the radio transmitter. The
options are:
• Offline The transmitter function for the selected radio side is offline
now.
• Online The transmitter function for the selected radio side is online
now.
To force a Tx Switch to online the Tx rocker switch must be set to Auto
and the protection type rocker switch must be set to Hot Standby. If
there is a problem when switching Tx, it switches back again.
Related Topic:
• Resetting an XP4 Radio Device on page 5-84
614-330055-001 July 2009 5-83

Resetting an XP4 Radio Device
Introduction
Normally, you would reset individual XP4 radio components if recommended by
Harris Stratex Help Desk personnel. Resetting a IDU or ODU hardware may result in
loss of traffic. The possible reset types include:
• Local IDU and ODU
• Remote IDU and ODU
• Reset NMI
Procedure
To reset an XP4 radio’s device:
1. From the Tree Viewer or Map Viewer, right-click the XP4 radio icon. The right-click
menu displays.
2. Select Diagnostics. The Diagnostics window displays. Select the Resets tab.
3. In this tab, select the drop-down arrow to display the radio’s devices.
4. Select the required radio device and select Reset.
5. Select Yes. to reset the selected radio device.

6. Select OK to close the Diagnostics window.
Related Topics:

Diagnostic Controls for Selected Devices

Some devices do not have a ProVision-compatible craft tool. For these devices, you can
access and set their basic Diagnostic Control values through a screen in ProVision.
Diagnostic tools are used when an event indicates there is a fault with a device, and can
help to determine if the fault is equipment or path related. They are also useful during
device maintenance and commissioning.
When Diagnostics is selected, ProVision automatically logs into the device, retrieves
the diagnostic settings, and displays them in the Diagnostics screen.
These devices and their screens are:
• Constellation Diagnostic Controls
• CAU Diagnostic Controls
• DART Diagnostics Controls
• Diagnostic Controls for Selected Devices
• DVA Diagnostic Controls
• MegaStar Diagnostic Controls
Both TNet and XP4 have both Craft Tools and Diagnostics functions. See
TNet Web Craft Tool and Diagnostics and Diagnostic Controls for Selected Devices.
Constellation Diagnostic Controls

The Constellation diagnostic controls display values and options for tribs, loopbacks,
protection, relays, BER testing, CBER/UBER testing, and RCS alarm clearing. For
complete details on all these diagnostic options, see the Constellation user documents.
Constellation for FarScan has limited Diagnostic Controls. These limits

are noted for each Diagnostic Control option.
Procedure
To access and change Constellation diagnostic controls:
1. Right-click on the selected device. In the right-click menu, select Faults >
Diagnostics. The Diagnostic Controls screen displays.
2. Control status is shown through use of color:
• Green “On” = Control Active
• Green “Off” = Control Inactive
• Gray = Not Available
614-330055-001 July 2009 5-85

3. To reset controls, use drop-down menus where available. See the details for each
tab of this screen below.
4. To apply changes, click Apply.
5. To refresh the data from the device, click Refresh.
6. To exit the screen, click Close.
Tribs Side A and Side B Tabs
Table 5-25. Constellation Tribs Side Tab Values
Item
Tributary Enable or disable loopback controls for DS3, local or remote

Loopbacks circuits. To adjust, select Enabled or Disabled from the
drop-down menu.
Tribs HLM Tab
Table 5-26. Constellation Tribs HLM Tab Values
Item
Loopbacks Enable or disable loopback controls for local or remote HLM

circuits. To adjust, select Enabled or Disabled from the
drop-down menu.

Protection Tab
Table 5-27. Constellation Protection Tab Values
Item
TX Online Status
LEDs Shows whether TX1 or TX2 is in operation for Side A and Side B.
Switch Enables the user to switch TX traffic to the TX that is not in use.
Control This can only be implemented if the TX that is not in use is free
of alarms. To adjust select Set from the drop-down menu.
Note: This is a safer TX switch operation than the TX Lock, which locks
traffic onto an alarmed TX.
Note: Switch data is not displayed for Constellation for FarScan
devices.
Protection Controls
TX / RX Enables protection locking or unlocking of TX, RX, M12, and HLM.

To adjust, select Locked or Unlocked from the drop-down menu.
M12 Locks the selected M12 traffic onto the M12 Standby card.
Standby Note: This lock is over-ruled if the locked M12 becomes absent.
MI2 Release Switches protected M12 traffic from the Standby card back to the
normal card, if the normal card is free of alarms. If this is set to
the status of Release, the M12 Standby value should all be
Unlocked.
HLM Lock Locks the selected High Level Mux (HLM) online, if the HLM is free
of alarms or not.
Note: This lock is over-ruled if the locked HLM becomes absent.
614-330055-001 July 2009 5-87

BER Test Side A and B Tabs
Table 5-28. BER Test A and B Tab Values
Item
Results Results of the BER test for a trib.
Duration Number of days, hours, minutes, and seconds of a BER test for a
trib.
Note: This data is not displayed for Constellation for FarScan devices.
Action Start or Stop the BER test for the trib.
CBER/UBER Test Tab
Table 5-29. BER Test A and B Tab Values
Item
Side A and Side B Results of the CBER/UBER test for Side A and Side B.
Results
Test Duration Number of days, hours, minutes, and seconds of the most
recent CBER/UBER test.
Note: This data is not displayed for Constellation for FarScan
devices.
Start or Stop Start or Stop the CBER/UBER test.

RCS Alarm Clear Tab
Table 5-30. RCS Alarm Tab Values
Item
RCS to TX To clear an RCX to TX Switch alarm, select Clear from the

Switch drop-down menu.
Alarms
RCS to HLM To clear an RCX to TX Switch alarm, select Clear from the
Switch drop-down menu.
Alarms Note: This option is not available for Constellation for FarScan
devices.
Relays Tab
Table 5-31. Constellation Relay Tab Values
Item
External To adjust an external relay, select Reset or Set from the

Relays drop-down menu.
614-330055-001 July 2009 5-89

CAU Diagnostic Controls

The CAU diagnostic controls enable you to view and reset CAU control and alarm relay
status.
Procedure
To access and change CAU diagnostic controls:
2. Select the Control Activation option:

• Global Activation on Apply
• Activate Immediately
4. To reset control relays and alarm relays, use the drop-down menus.
The first object in the alarm relay is a read-only object and cannot be
reset.
5. To apply changes, click Apply. It takes up to 1 minute for the relay changes to be
fully applied; a progress icon displays in the lower left corner of the screen.

Table 5-32. CAU Control and Alarm Values
Item View and Change
Control Shows status of control relay connections. To adjust, select Reset

Relays or Set from the drop-down menu.
Alarm Shows status of alarm relay connections. To adjust, select Reset

Relays or Set from the drop-down menu.
DART Diagnostics Controls

The DART Diagnostic tools available from ProVision are:
• Radio device resetting.
• Local and remote tributary loopback tests used to verify tributary cable connections,
on externally attached equipment.
Loopback tests are run from the local radio using test patterns generated
by externally connected test equipment. The number of error
occurrences, if any, are captured and handled by the external test
equipment.
Procedure
To access and change diagnostic controls, and to reset the DART radio:
2. To adjust a tributary loopback, see Activating and Deactivating DART Tributary
Loopbacks on page 5-92.
3. To reset the radio, select the Resets tab. In this tab, select the drop-down arrow to
display the radio’s devices.
4. Select Reset NMI from the drop-down menu, then select Reset. A message displays:
5. To apply changes, click Apply.

614-330055-001 July 2009 5-91

To exit the screen, click Close.
Access to the Diagnostics menu option is dependant on your ProVision

Activating and Deactivating DART Tributary Loopbacks

The tributary loopbacks can be applied to the local DART radio or the remote radio of
a DART link as shown below.
When you run loopback tests on the online unit, traffic is affected.
Table 5-33. Tributary Loopbacks
Trib Loopback Purpose

Loopback
Local To locate faults in equipment and cable connections to the local

Loopback ODU. The local loopback does this by routing the tributary input
(data from customer) directly to the tributary output (data to
customer).
The following diagram shows a local tributary loopback signal
path:
Remote To locate faults in equipment and cable connections by

loopback connecting the transmit data stream directly to the receive data
stream in the remote ODU. The remote loopback checks the
functionality of the local and remote sides in both directions.
The link operation is confirmed with the aid of a connected BER
test-set.
The following diagram shows a remote tributary loopback signal
path:

Procedure
To activate and deactivate a tributary DART loopback:
1. From the Tree Viewer or Map Viewer, right-click the DART radio icon. The
right-click menu displays.
2. Select Fault >Diagnostics. The Diagnostics window displays.
3. Select the tributary loopback control (Trib 1).
4. To activate the tributary loopback on the radio, select Apply.

The following message displays.
5. To continue writing the loopback data to the radio, select Yes.

The Diagnostic window is updated and shows the status as read from the radio.
You can only execute one loopback on a link at a time. So you need to stop the currently
active loopback before you can start another one.
6. To deactivate a Tributary, un-check the selected checkbox.
614-330055-001 July 2009 5-93

Exceptions
If a correct login username and password for this radio has not been set up in ProVision
the following message displays when you attempt to write data to the radio.
If a local loopback is already active and you attempt to activate a trib loopback the
following message displays.
If ProVision is unable to contact the DART radio, the following message displays.

DVA Diagnostic Controls

The DVA diagnostic controls enable you to view and reset DVA external relay status.
Procedure
To access and change diagnostic controls:
2. Select the Control Activation option:

• Global Activation on Apply
• Activate Immediately
4. To reset relay controls, use the drop-down menus.
Table 5-34. DVA Controls Values
MC1, 2, and To adjust, select Reset or Set from the drop-down menu.
3 Relays
614-330055-001 July 2009 5-95

External Select the external relay option that you want to view from this
Relay drop-down menu. Then, click Refresh. The values for that option
display.
MegaStar Diagnostic Controls

The MegaStar diagnostic controls enable you to view and change loopback controls and
status for specific relays.
Procedure
To access and change diagnostic controls:

3. To reset loopback controls, on the Tributaries tab, use the drop-down menus.
5. To refresh the data from the device, click Refresh. Wait for the data to be updated.
Table 5-35. MegaStar Controls
Item
Tributaries tab

Item
Loopback Controls Enable or disable loopback controls for tribs.
3XDS3 Loopback Notes the status for each trib on each channel.
Status
Wayside Loopback Notes the wayside loopback status of tribs and

Status 3xDS3 connections.
External Relay Select the external relay option that you want to
view from this drop-down menu. Then, click Refresh.
The values for that option display.
614-330055-001 July 2009 5-97

EfficientSite Manager System
Introduction
The Harris Stratex EfficientSite Manager is an intelligent controller based system. It
reduces the energy costs associated with operating telecommunications sites. The
EfficientSite Manager system is supported by ProVision through a rich set of Fault,
Configuration, and Performance management features.
The EfficientSite Manager enables users to:
• View the Energy status and activity, including fuel usage trends, real-time
environmental data, and current energy mode.
• View which field replaceable environment units have important problems and/or
need maintenance.
• Limit operation of generators or air conditioners if fault-finding or testing is
required.
Multiple sites can be deployed through ProVision.
Figure 5-7. EfficientSite Manager
The EfficientSite Manager is a licensed feature. To obtain the separate

license and enable this feature, contact your Harris Stratex
representative.

Procedure
1. Deploy the EfficientSite Manager. For instructions, see EfficientSite Manager
Deployment on page 3-33.
2. Navigate to the EfficientSite Manager in the Tree Viewer or Map View. Right-click
on it and select Open Device.
3. The EfficientSite Manager screen displays, showing the status for the selected site.
Table 5-36. EfficientSite Manager Screen
Item
Installed Systems
Energy Energy management systems are installed.
Access Site access management systems are installed.
Surveillance Video surveillance systems are installed.
Energy Source
Grid Grid supply status, Off or On.
Generator Generator status, Off or On.
Batteries % of battery charge

Current voltage
Charge mode - charging or discharging
Fuel Tank Volume % of fuel tank

Remaining liters in fuel tank
Average consumption per hour
Environment Control
Notes presence and Off or On status of environment

managing devices, such as HVAC and fans.
Environment Conditions
Ambient Temperature and relative humidity readings outside

enclosed site areas.
Enclosure Temperature and relative humidity readings inside

enclosed site areas.
Energy Source Summary
Running time operation for power items for the

overall site, including:
• Grid
• Generator
• Hybrid - Use of energy-saving battery mode
Environmental Controls Summary
614-330055-001 July 2009 5-99

Item
Running time operation for environment items for

the overall site, including:
• Off
• HVAC
Related Topics:
EfficientSite Manager Deployment on page 3-33
Performance History on page 5-33

Device and Network Reports
This section includes procedures for:

• Inventory Reports on page 5-101
• Eclipse Fault Report on page 5-107
• Eclipse Capacity Report on page 5-108
• Network Health Reports on page 5-112
Inventory Reports
This section describes the various options for viewing the inventory for any Eclipse,
TRuepoint, Constellation, or LE3000 radio:
• View the Inventory Reports on page 5-102
• Save an Inventory Report for a Single Device on page 5-104
• Save an Inventory Report for Multiple Devices on page 5-105
• Eclipse Fault Report on page 5-107
For Eclipse radios, you can access the Eclipse Node inventory details via Portal. For
TRuepoint and Constellation radios, the inventory details are available through
WebCIT. However, the Inventory Report in ProVision is the fastest and easiest way to
view the inventory details. The Inventory Report summarizes the components of the
network for a selected radio. It displays as a free-floating window that lists information
about the radio, including:
• General information such as the device name, site name, IP address and device type
• Active license certificate details
• Manufacturing details such as the plug-in type and part number, serial number, and
time in service for each unit or plug-in
The information that displays is the real-time details from the radio. You can manually
save Inventory Reports to the ProVision database and view them at a later time via
ProVision. You can also save the inventory details from either the radio or the database
to a *.txt file.
For more information on the Eclipse Node inventory details, see the
Eclipse User Manual, Portal Installation and Configuration, Eclipse
Configuration > Licensing.
For Constellation for FarScan, the Inventory Report is limited and only
displays the Plug-Ins and Software Version.
614-330055-001 July 2009 5-101

View the Inventory Reports

To view the Inventory Report for a single Eclipse, TRuepoint, Constellation, or LE3000
device:
1. Go to the Tree or Map Viewer. Right-click the selected Eclipse radio icon.
2. On the right-click menu, select Reports > Inventory.
3. The Inventory Report displays.
4. A report for a device is shown below.
5. If the report displays the message “No data in the database,” select the Refresh
From Radio button. The software refreshes and displays the inventory details for
this radio.
6. Select Close to close the Inventory Report.
The data detailed in the Inventory window is listed below.
Table 5-37. Inventory Details
Feature Description
Report Lists the inventory details

The inventory details for the Eclipse INU/INUe include:
• Inventory Report
• General Information
• Active License Certificate Details
• Manufacturing Details
The inventory details for the Eclipse IDU include:

The Eclipse IDUs, except for IDU ES (Connect ES), do not have
“Active License Certificate Details” since the IDU has no capacity
licence.

Feature Description
The inventory details for the TRuepoint 6500 include:

Inventory Report - Lists the day/time stamp when the report was
generated. If a comment was added when the database was
updated, the comment appears under the day/time stamp.
General Information - Lists the device name, site name, device IP

address, and device type.
Active License Certificate Details - Lists the serial number and the
status (active or inactive) for the RAC plug-in user licence.
For more information on the Eclipse radio inventory details

(such as capacity and modulation) see the Eclipse User Manual,
Vol IV. Portal, Licensing.
A default Eclipse Node License allows for installation of up to six
RACs, each with a maximum capacity of 10xE1, or 16xDS1.
Beyond this level, licenses must be purchased, which provide an
up-to capacity on a per RAC basis.
Manufacturing Details - Lists the details for each plug-in installed in

the radio.
• Plug-In = The name of this plug-in.
• Part Number = Plug-in part number
• Plug-in Types = The specific type of this plug-in, for example,
RAC 30, INUv2.
• Software Version = If this is available, this notes the version
number of the software installed on the plug-in.
• Hardware Version = If this is available, this notes the version
number/s of installed hardware.
• Revisions = The revision number of the software for the
plug-in.
• Serial Number = Plug-in serial number
• Time In Service = Total time the plug-in is in service (not
including the time the plug-in is powered down).
Refresh Refreshes the data in the window with the information from the
From radio.
Radio
If you refresh the inventory from the radio it updates the database
and the inventory report is read from the database.
Save Saves an inventory report as a text file.

Report
Close Closes the Inventory window
Next Topic:
Save an Inventory Report for a Single Device
614-330055-001 July 2009 5-103


You can save a device’s inventory details to a file so that you can view or print the details
at a later date. To save the inventory details from the radio:
1. Go to the Tree or Map Viewer. Right-click the selected device icon.
2. On the right-click menu, select Reports >Inventory.
3. The Inventory Report displays.
4. Select Save Report.

5. A directory browser displays. Browse to the required folder, then enter a file name.
6. Select a type of file from the Files of type drop-down menu.
• Text (.txt) - Saves the information as a text file as it appears in the inventory
window. The file name has the format: filename.txt.
• Text (semicolon separated) (.txt) - Saves the information as two separate text files
with the data separated by semicolons. This format allows the data to be viewed
in a spreadsheet application with the data automatically in tabular form. The
two file names have the format:
filename_lic.txt: Lists the radio’s Active License Certificate Details.
filename_mfg.txt: Lists the radio’s Manufacturing Details.
7. Select Save. Select Close to close the Inventory window.
Saved Inventory Reports include additional data; there are columns for
Family and Plug-In Class.
Next Topic:
Save an Inventory Report for Multiple Devices

Save an Inventory Report for Multiple Devices

You can save the inventory details from a group of Eclipse, TRuepoint, Constellation,
or LE3000 devices. For example, you may need to collect the data from a group of
radios that make up a region, a service, or a circuit. This feature can be useful to quickly
collect the data from multiple radios and have it compiled automatically into tabular
form.
To save the inventory details from a group of devices:
1. Within the Tree Viewer, select the desired devices:
• To select a group of radios that are listed sequentially, hold down the shift key
and select the first and last radio in the list.
• To select a group of radios that are not listed sequentially, hold down the ctrl key
and select each radio.
(Selecting multiple radios in this manner is only possible in the Tree Viewer, not in
the Map Viewer.)
2. You can also save the inventory details from a group of radios by selecting the
container.
3. Right-click a selected radios (or the selected container) to display the right-click
menu and select Inventory.
4. The Reports Information window displays.
Enter a Name and a Description for the report. Select the Open Task Manager check
box checked to open the Task Manager window. (You can open it anytime by
selecting the Task Manager icon .)
614-330055-001 July 2009 5-105

5. Select OK.
6. The Task Manager window displays with a Report Generation task listed.
7. The inventory report task generates the report and stores it on the server in the
folder:
<pvroot>\ProVisionServer\reports\
8. This step is finished when the status says “Report Complete” and a Save button
displays. Note that the Inventory Report task also displays the name of the report
defined in step 4.
9. Select the Save button and a directory browser displays. the file name is defaulted
to the name you initially specified. You can also change the file name, if required.
Browse to the required folder, then select Save.
10. The information is saved as two separate text files with the data separated by
semicolons. This format allows the data to be viewed in a spreadsheet application
with the data automatically in tabular form. The two file names have the format:
Saved Inventory Reports include additional data; there are columns for
Family and Plug-In Class.
Next Topic:
Eclipse Fault Report

Eclipse Fault Report

The Eclipse Fault Report is a feature specific to the Eclipse radios and lists a summary
of the activity for a particular radio during a particular time period. The report is in a
free-floating window that lists information about the radio, including:
• General information and link configuration
• License and manufacturing
• Active events and event history
• Performance summary
The Eclipse Fault Report collects event and performance data for a specific time period
for a specific radio. You can also save the fault report as a .txt file and compare the event
and performance data to help you diagnose problems with the radio’s performance.
Procedure
To view a fault report for an Eclipse radio:
1. Right-click the Eclipse icon and select Fault Report from the right-click menu.
2. The Fault Report window displays.
3. Select a start and end date for the report. The default report period is the last seven
days.
4. Select the Change button.
5. Select the Save Report button to save the report as a text file.
6. Select Close to close the Fault Report window.
7. The settings for the date range are not saved. When the fault report window is
re-opened for the same radio, the date range reverts to the default seven-day
period.
614-330055-001 July 2009 5-107

Next Topic:
Eclipse Capacity Report
Eclipse Capacity Report

The Eclipse Capacity Report is a report for Eclipse radios and networks. It can report
on IDU ES and IDU GE radios, providing a summary of the capacity for a particular
radio, noted at a specific date and time. It can also summarize the capacity for an entire
Eclipse network. This report is useful for identifying spare capacity that can be made
available to customers.
The report includes the following information:
• General information and link configuration
• License status
• Specific devices and their maximum, used, and spare capacity
• Performance summary
You can save the Capacity Report as a .CSV file.
Using this report with the Capacity Planning Information option requires
an additional license. Please contact Harris Stratex to acquire this license.
Procedure
To view a capacity report for an Eclipse radio or for a complete Eclipse network:
1. Right-click the Eclipse icon and select Capacity Report from the right-click menu.
2. The Capacity Report window displays for the selected data.
3. Select the Save Report button to save the report as a .csv file.

4. Select Close to close the Capacity Report window.

The data detailed in the Capacity report is listed in the tables below. For more
information on the Eclipse radio inventory details (such as capacity and modulation)
see the Eclipse User Manual, Vol IV. Portal, Licensing.
Table 5-38. Capacity Report Details
Feature Description
Capacity Lists the day/time stamp when the report was generated.
Report
General Lists the device name, site name, device IP address, and device
Information type.
Active Lists the serial number and the status (active or inactive) for the
License RAC plug-in user licence.
Certificate
Details
Capacity Lists the capacity details for each RAC plug-in installed in the
Details radio or network. See the tables below for specific definitions,
for both individual radio and network Capacity Reports.
Refresh from Refreshes the data in the window with the information from the
Radio radio.
Save Report Saves a Capacity Report as a .CSV file. The .CSV report file
includes additional information for each RAC plug-in:
• Radio path identifier, identifying where the RAC is deployed in
ProVision
• Flash card serial numbers
• Plug-in Used Capacity
• Device name and type
• Backplane rate
Close Closes the Capacity Report.
Table 5-39. Capacity Details - Individual Radios
Feature Description
RAC The name of this RAC plug-in
Licensed The amount of capacity licensed for this RAC.

Capacity
Backplane The total capacity that this radio can support.

Equivalent
Hardware The maximum capacity that this hardware can support.
Used The capacity currently used by traffic by this plug-in.
Licensed Spare The amount of capacity licensed for the RAC spare.
Hardware Spare Maximum capacity of the RAC spare.
614-330055-001 July 2009 5-109

Feature Description
Hardware This indicates the capacity for unlicensed hardware. It is

Unlicensed calculated by subtracting the backplane equivalent capacity
from the licensed hardware capacity. If the backplane
equivalent is greater than, or equal to, the licensed hardware
capacity, this result is zero.
Table 5-40. Capacity Details - Network
Feature Description
Path Network path to this radio.
Serial Number Serial number for this radio.
Device Type The radio type, IDU, INU, or INUe.
Backplane Max The total maximum capacity
Licensed The amount of capacity licensed for this radio.

Capacity
Backplane Rate Transmission rate for this radio.
Backplane Backplane equivalent for this radio.

Equivalent
Hardware The maximum capacity that this hardware can support.
Used The capacity currently used by traffic by this plug-in.
Licensed Spare The amount of capacity licensed for the RAC spare.
Hardware Spare Maximum capacity of the RAC spare.
Hardware The difference between licensed capacity and the hardware

Unlicensed capacity. This license may be made available if licensing is
extended.
Next Topic:
View / Save / Delete Server Reports on page 5-111

View / Save / Delete Server Reports

Select the Reports button on the tool bar to display the Server Reports window.
This window lists all previously-saved reports and allows you to easily retrieve them.
Procedure
To view the list of reports and to save or delete selected reports:
1. Select the Reports button to display the Server Reports window.
2. Place the cursor over the name of the report and a small pop-up window appears
that displays the description of the report that was entered when the report was
created.
3. Select the Save button for the selected report. A directory browser displays.
4. The file name is defaulted to the name you initially specified. You can also change
the file name, if required. Browse to the required folder, then select Save.
5. The information is saved as two separate text files with the data separated by
semicolons. This format allows the data to be viewed in a spreadsheet application
with the data automatically in tabular form. The two file names have the format:
6. Select the Delete button to delete a selected report. The security access applies
to the delete function: Administrators can delete any report. Users can delete any
report they create. However, users cannot delete other users’ reports
Related Topic
614-330055-001 July 2009 5-111

Network Health Reports

With ProVision’s Network Health Reports, you can create an RF performance report
about an entire network, or for sub-sections of a network (for example, based on site
context or logical containment context).
This feature provides reporting on the RF performance for a range of Harris Stratex
microwave radios, including:
• Eclipse
• TRuepoint (all variants)
• Altium (all variants)
• Constellation (only 3DS3, 4DS3, and 155mbit)
• DART
• LE3000
• Radwin WinLink 1000
• Spectrum II (all variants)
• XP4 (all variants)
Network Health Reports summarize link performance data in both graphical and
tabular formats. The Overview tab shows a graphic summary of report data. The Detail
tab presents statistics on each individual link. Reports include sorting from worst to
best performing radios, and radios failing to meet a specified link availability target.
Network Health Reports can be saved as spreadsheets (*.XLS) that can be opened in
Microsoft Excel or other compatible applications; or as PDF files.
This section describes how to Run and View Network Health Reports.

The Network Health Report is created using daily performance data from
the ProVision database, excluding invalid data. Daily performance data in
the database is required for Network Health Report output.
614-330055-001 July 2009 5-113

Run and View Network Health Reports

After you have configured a Network Health Report, you can run it and review its data.
The Network Health Report can be run for Eclipse, TRuepoint, and
Constellation (non-FarScan) networks.
Procedure
1. From the menu bar, in the Reports menu, select Network Health Report.
2. Or, in the Tree Viewer, select a site, region, rack, or device for the report by
right-clicking on it and selecting Reports - Network Health.
3. The Network Health Report window displays.
4. Select the values for the report. In the Report Settings frame, select the following:
• Start and End Date: Select a start and end date within this range. The report
will cover data between these two dates.
• Availability threshold = Link availability threshold for this report. Any device
below this threshold is considered to be in error. This is normally set to the
threshold availability in your service level agreement.
5. In the Report Settings frame, click the Generate Report button. The Network Health
report displays.

6. Click on the Details tab to view a statistical breakdown of each individual link.
Devices with below the threshold are highlighted in red. You can check boxes to
Hide Healthy Devices and to Hide Devices with Zero Visibility.
7. To save the report as a PDF, click the Export as PDF button. A Save window
opens, prompting you to save the file with a name at the system location you
choose.
8. To save the report as an Excel.XLS file, click the Export as Excel Spreadsheet
button. A Save window opens, prompting you to save the file with a name at
the system location you choose.
Network Health Report - Overview Tab

This data is included in both the PDF and XLS formats for this report.
Value Description
Report Data Information about this specific network health report.

Start and End- dates for the report coverage beginning
and end.
Availability Threshold- Link availability threshold for the
report.
Availability The % of time that links have been available over the time
they have been deployed. For example, if a link has been
deployed for 365 days, but has been down for
maintenance 1 day, the link has been available 99.72% of
the time.
Visibility The % of time that ProVision is able to obtain data from a

radio. For example, if your ProVision server had been
deployed for seven days, but for one of those days, it had
not been able to communicate with one Eclipse radio, the
visibility for that week would be 85%.
614-330055-001 July 2009 5-115

Value Description
Mean Availability Displays the average availability for all valid performance
data over the reporting period
Mean Visibility Displays the average visibility of the network able to be

viewed by ProVision for this report.
Number of Devices Number of devices in this report.
Devices at/above Number of devices that are operating at or above

threshold threshold.
Devices below Number of devices that are operating below the

threshold availability threshold.
Devices with Zero Number of devices that are not providing any data.
Visibility
Device Availability A pie graph comparing the number of healthy devices with
Chart the number of devices below threshold.
Breakdown by Day A graph showing the % of network availability over the

Chart past 60 days. Mouse over the bar for a specific day to view
its % of availability and visibility.
Network Health Report - Details Tab

There are three levels of detail that can be viewed; Low, Medium, and High. Use the
sliding scale to adjust the level of detail: GRAPHIC
Value Description
Detail Level - Low
Device Device name and network location.
Remote Radio The radio linked to the main device.
Mean Availability % availability of the network.
Mean Visibility The % of the network able to be viewed by ProVision for

this report.
RSL Mean The mean for the Receive Signal Level value.
RSL Max The maximum Receive Signal Level value.
RSL Min The minimum Receive Signal Level value.
Detail Level -
Medium
G.826 Available A count of the number of available G.826 seconds since

Seconds the report Start.
G.826 Unavailable A count of the number of unavailable G.826 seconds since

Seconds the report Start, a good indicator of system problems.
G.826 Errored A count of the number of errored seconds since the report
Seconds Start. An errored second is a one-second period with one
or more errored bits.

Value Description
G.826 Severely A count of the number of severely errored seconds since

Errored Seconds the report Start. A severely errored second is a
one-second period which has a bit error ratio greater than
or equal to 1 x 10-3.
Detail Level - High
Frame Loss The number of seconds that an Out Of Frame error is

Seconds detected.
G.826 Errored A block of data where one or more bits of data are in error.
Blocks
G.826 An errored block not occurring as part of an Severely

Background Block Errored Seconds set.
Errors
Events Data
The Events Data is saved only in the .XLS file of the report. It lists Critical, Major, and
Minor events for relevant devices over the reporting period. The report limits the
maximum number of events to 65,000.
Value Values
• Device
Network Events
• Event
• Time
• Severity
• Acknowledged
614-330055-001 July 2009 5-117

Glossary
About This Glossary
This Glossary defines terms and acronyms used in Harris Stratex Networks manuals
and in radio microwave technology.
Numbers
1+1 protected system
Two transceivers are used at each end of a link to protect against transmission failure.
If a data transmission fails on the operating transceiver, it is transferred to the backup
transceiver. With a 1+1 protected microwave radio link, the protection mechanism
normally allows receiver switching independently of the transmitter, and vice-versa.
1U
Standard Electronic Industries Association size for a single rack unit (44.5 mm / 1.75
in.)
A
AACS
Access and Administration Control System.
ACU
Antenna Coupling Unit.
ADC
Analog-to-digital Converter. A device that converts an analog signal to a digital signal
that represents equivalent information.
Address
The unique number ID assigned to one host or interface in a network.
ADM
Add/Drop Multiplexer. Digital multiplexing equipment that adds/removes individual
signals to/from a collection of multiplexed signals in a network.
AGC
Automatic Gain Control. A process that automatically adjusts gain as a function of a
specified parameter, such as received signal level. AGC is used to help maintain a
constant output level when the input signal level is changing.
AIS
Alarm Indication Signal - The code generated by a regenerator upon loss of input signal
or loss of frame. A signal transmitted in lieu of the normal signal to maintain
transmission continuity and to indicate to the receiving terminal that there is a
transmission fault that is located either at, or upstream from, the transmitting
terminal.
AIS-L
Line Alarm Indication Signal.
ALC
Glossary-1 Harris Stratex Networks

Automatic Level Control. See AGC.
AMI
Alternate Mark Inversion Signal. A pseudoternary signal, representing binary digits.
Successive marks are of alternately positive and negative polarity and the absolute
values of their amplitudes are normally equal. Spaces are of zero amplitude.
Analog signal
A signal that has a continuous nature instead of pulsed or discrete.
ANSI
American National Standards Institute.
ARP
Address Resolution Protocol.
ASCII
American National Standard Code for Information Interchange.
ASIC
Application Specific Integrated Circuit.
ATM
Asynchronous Transfer Mode. A dedicated connection switching technology that
organizes digital data into 53-byte cell units and transmits them over a physical
medium using digital signal technology. Relative to other related cells, each cell is
processed asynchronously and queued before being multiplexed over the transmission
path.
ATPC
Automatic Transmit Power Control. A feature of digital microwave radio
equipment that adjusts the transmitter output power based on path fading
detected at the receiver. This feature reduces interference with neighboring
systems and permits greater link density.
AUX
Auxiliary services module.
Auxiliary Data Channel
A data channel between microwave radio terminals that is outside the customer
payload channel(s). The auxiliary data channel is normally transported in the radio
overhead.
AWG
American Wire Gauge. A wire diameter specification. The smaller the AWG number,
the larger the wire diameter.
Azimuth
The angle in the horizontal ground plane with respect to true North (such as, horizontal
direction); used in reference to antenna alignment.
B
B1
Bit Interleaved Parity-8 (BIP-8). An RSOH byte for error checking the complete STM-1
signal at the end of a regenerator section.
B2
Bit Interleaved Parity-24 (BIP-24). MSOH bytes for error checking an STM-1 signal
(minus the RSOH) at the end of the multiplexer section.
Glossary -2 Harris Stratex Networks

B3ZS
Binary 3 zeros substitution. A “1” is substituted for every 3 zeros.
B8ZS
Binary 8 zeros substitution/Bipolar 8 zero substitution.
BAPT
Bundesamtfur Post Und Telekommunikation (German Telecom Regulatory Agency).
BBP
Baseband Processing.
BCH
Bose-Chaudhuri-Hochquenghem code. A multilevel, cyclic, error-correcting,
variable-length digital code used to correct errors up to approximately 25% of the total
number of digits.
Beamwidth
The beamwidth of an antenna is defined as the angle between the two half-power (-3
dB) points on either side of the main lobe of radiation (half power beamwidth).
BER
Bit Error Ratio or Bit Error Rate - The number of erroneous bits divided by the total
number of bits transmitted, received, or processed over some stipulated period.
BML
Business Management Level in the TMN model
BNC
Type of coaxial connector.
bps
Bits per second.
BSI
British Standards Institute.
Bursty Traffic
Communications data does not flow in a steady stream.
C
CB-149
The Bell Core standard that was used before the ITU standard was adopted.
CCITT
International Telegraph and Telephone Consultive Committee.
CDMA
Code Division Multiple Access.
CE
Conformité Européene. The CE marking indicates that the product has been designed
and manufactured in conformity with the essential requirements of all relevant EU
(European Union) directives, and submitted to the relevant conformity assessment
procedure.
CEMF
Cisco Element Management Framework.
614-330055-001 July 2009 Glossary -3

CEPT
The European Conference of Postal and Telecommunications Administrations.
CEPT-1
ITU-T digital signal level 1 (2.048 Mbps) = E1
CEPT-2
CEPT-3
CEPT-4
ITU-T digital signal level 4 (139.264 Mbps)
CEPT-n
Conference of European Posts and Telecommunications level n.
CLEC
Competitive Local Exchange Carrier Market. A service provider that builds and
operates communication networks in metropolitan areas, thus providing customers
with an alternative to local telephone companies. USA terminology.
CMOS
Complementary Metal Oxide Semiconductor.
CODEC
Abbreviation of coder/decoder. A device that encodes and/or decodes a signal. For
example, telcos use codecs to convert digital signals to analog signals - and vice-versa.
Commissioning
A radio link is commissioned when customer traffic circuits have been connected and
the link is completely ready to provide a data service.
Community String
When configuring an SNMP agent, the community string (which is a name or
combination of characters) is input as part of the configuration information. When a
management system wants to communicate with the device, it authenticates using the
community string. There are normally two community strings accommodated by a
device, one for reading values and one for writing (setting) values. These are normally
set to “Public” or “Private”, but can be set to other values as a form of security.
Component
The component replacement level describes the smallest field-replaceable parts of a
system. For example, for a split-mount radio terminal, the IDU and ODU normally
represent the lowest level of field replaceable items.
CORBA
Common Object Request Broker Architecture.
CRC
Cycle Redundancy Check.
CTB
Cable Termination Block.
CTU
Customer Termination Unit.
D

D/A
Digital to Analog.
DAC
1) For Eclipse: Digital Access Card; 2) Digital to Analog Converter.
DADE
Differential Absolute Delay Equalization. An equalization process used to render a
protected system hitless.
DART
Digital Access Radio Technology. A digital microwave radio system.
dB
The abbreviation for decibel; the standard unit of measure for relative signal power.
DB9
A standardized connector with 9 pins.
dBm
db referenced to one milliwatt = 0 dBm. The standard unit of measure for absolute
power values.
dc
Direct current; Harris Stratex Networks radios operate on dc power.
dc-dc Converter
An electrical device used to convert direct current from one level to another.
DCE
Data Communications Equipment.
DDS
Direct Digital Synthesizer.
DEMUX
De-multiplexer.
DFE
Decision Feedback Equalizer.
DHCP
Dynamic Host Configuration Protocol.
Diagnostic Controls or Functions
Radio system features used for troubleshooting or testing the radio or radio link. Some
examples: RF loopback, PA mute, and tributary loopback.
Diplexer
A RF filter device used to separate the Tx and Rx signals at the transceiver antenna feed
port.
Digital signal (DS)
A signal format where the intelligence is transported as binary code.
Digital signal 1 (DS1)
An ANSI digital signaling rate of 1.544 Mb/s, corresponding to the North American and
Japanese T1 designator.
Direct current (dc)
Harris Stratex Networks radios operate on dc power.
614-330055-001 July 2009 Glossary -5

DLC
Digital Loop Control.
DQPSK
Differential Quadrature Phase Shift Keying.
DS1
Digital signal 1: an ANSI digital signaling rate of 1.544 Mb/s, corresponding to the
North American and Japanese T1 designator.
DS3
Digital signal 3: an ANSI digital signal level 3 (44.736 Mbps), the North American T3
designator.
DSx
ANSI digital signal level x.
DTE
Data Terminal Equipment. Devices acting as data source, data sink, or both. They
typically connect to a network via a DCE.
Dual Link
Two radio links operating in parallel, on different frequencies, and transporting
different data.
DTMF
Dual Tone Multi-frequency.
DTPC
Dynamic Transmit Power Control. A feature enabling the regulation of a target receive
signal level by remotely and proportionally controlling the corresponding transmitter
output power level.
DUART
Dual Universal Asynchronous Receiver-Transmitter.
DVM
Digital Volt Meter.
DXR
Digital Cross-Connect Radio. A legacy Harris Stratex Networks radio family.
E
E1
ITU digital signal level 1 (2.048 Mbps) = CEPT 1.
E3
ITU digital signal level 3 (34.368 Mbps) = CEPT 3.
E/I
Energy to Interference ratio.
E/N
Energy to Noise ratio.
ECC
Error Correction Code.
Eclipse Node

Refers to the Harris Stratex Networks Eclipse INU or INUe with ODU300 and/or ODU
100. Plug-in cards provide multiple link and tributary options. Capacity extends from
4xE1/DS1 to 2xSTM1/OC3. Modulation options extend from QPSK to 256QAM.
Protection options support hot standby, space diversity, frequency diversity, or ring.
Eclipse Terminal
Refers to the Harris Stratex Networks Eclipse IDU with ODU 300 or ODU 100.
Different version are available to transport NxE1/DS1 tribs, STM1/OC3, Fast Ethernet,
or Gigabit Ethernet. Most Terminals are protectable, using two co-located Terminals
with an inter-connecting protection cable.
EEPROM
Electrically Erasable Programmable Read Only Memory
EIA
Electronic Industries Association
EISA
Extended Industry Standard Architecture - A 32-bit bus standard that supports the
features of microchannel architecture. A special card is required for 32-bit operations
that maintain compatibility with the older ISA (Industry Standard Architecture).
Electromagnetic Spectrum
Though the electromagnetic spectrum was, by custom and practice, formerly divided
into 26 alphabetically designated bands, the ITU formally recognizes 12 bands, from 30
Hz to 3000 GHz.
EM
Element Manager.
EMC
Electro-Magnetic Compatibility.
EMI
Electromagnetic interference.
EML
Element Management Level in the TMN model.
EMS
Element Management System.
End-to-end delay
The time it takes a signal to travel from point of transmission, to the point of reception.
EOW
Engineering Orderwire (Voice and/or Data).
ERP
Effective Radiated Power.
ESCAN
Extended SCAN Protocol. A Harris Stratex proprietary protocol that is more efficient
and allows for faster communications than the SCAN protocol, also from Harris
Stratex.
ESD
Electrostatic discharge.
ETSI
614-330055-001 July 2009 Glossary -7

European Telecommunications Standards Institute. Provides international technical
standards for wireless radios. Harris Stratex Networks radios are in compliance with
all relevant ETSI standards.
F
Fade margin
The amount of attenuation a link can suffer before link performance is affected.
Typically measured as the dB difference between the received signal strength and the
receive threshold.
FCAPS
Fault, Configuration, Accounting, Performance and Security functions in the TMN
model.
FCC
Federal Communications Commission. The FCC is an independent United States
government agency, directly responsible to Congress. The FCC was established by the
Communications Act of 1934 and is charged with regulating interstate and
international communications by radio, television, wire, satellite and cable. The FCC's
jurisdiction covers the 50 states, the District of Columbia, and U.S. possessions.
FD
Frequency Diversity. A path protection mode. The main and standby radios are
transmitting simultaneously and are tuned to different frequencies (at least two
channels apart) to avoid interference. When a fault is detected on the active radio, the
traffic is switched to the standby radio.
FEC
Forward Error Correction. A system of error control for data transmission. It
compensates for errors induced in the transmitted stream, by sending along with the
primary data payload, additional information to correct for errors that occur in
transmission.
FFE
Feed Forward Equalizer.
FIFO
First In First Out.
FIR
Finite Impulse Response filter. Designates one of two primary types of digital filters
used in Digital Signal Processing (DSP) applications.
FM
Fault Management.
FPGA
Field Programmable Gate Array.
FSK
Frequency-shift Keying. The modulating signal shifts the output frequency between
predetermined values.
G
G.821

An ITU-T recommendation on error performance parameters and objectives for

primary-rate (64 kbit/s) data circuits. It can be used for higher bit-rates, typically up to
to 2 Mbit/s. G.821 is a bit-based system.
G.826
An ITU-T recommendation on error performance parameters and objectives for
high-speed data circuits; circuits operating at 2 Mbit/s and above. G-826 is a
block-based system.
Ga AsFET
Gallium Arsenide Field Effect Transistor.
Gain
The increase in signal power caused by a device or network (for example, the signal gain
provided by an antenna).
GB
Gigabyte.
GHz
Gigahertz.
Golden Cells
These are sites where it is imperative that communications traffic continues at peak
performance. They are typically sites where any communications down-time can mean
significant loss of revenue, or a significant breach against a service level agreement
(SLA).
GSM
Global Systems for Mobile.
GUI
Graphical User Interface.
H
H.323
A standard approved by the ITU that defines how audiovisual conferencing data is
transmitted across networks. In theory, H.323 should enable users to participate in the
same conference even though they are using different videoconferencing applications.
HDB3
High Density Bipolar Order 3. The default method of encoding transmissions for E1
and E3 radios. Substitutes a 1 for every 3 zeros.
HDLC
High-level Data Link Control. A bit-oriented synchronous data link layer protocol
developed by ISO. HDLC specifies a data encapsulation method on synchronous serial
links using frame characters and checksums.
HHT
Handheld terminal.
Hitless Receive Switching
A protected system configuration whereby if a fault occurs at the receiving end of the
link, the traffic is switched to the standby radio without causing errors.
Hot Standby
614-330055-001 July 2009 Glossary -9

Hot Standby is a protected configuration whereby standby equipment is held ready to
be switched immediately into service if the main equipment fails.
HPA
High Power Amplifier.
HSB
Hot-Standby Protection Mode.
HSC
Hardware/Software Compatibility. Different hardware may require different software
versions.
I
I/O
Input / Output.
ICMP
Internet Control Message protocol. An integral part of the Internet Protocol that
handles error and control messages.
IDC
Indoor Chassis.
IF
Intermediate Frequency. The signal frequency or frequencies intermediate between the
modem electronics and the transmitted/received frequencies.
IIOP
CORBA's Internet Inter-ORB Protocol.
IDU
Indoor Unit. The IDU s the control center of a split-mount radio system. It interfaces
between the customer signals and the ODU.
Intermodulation
Intermodulation can occur in systems where multiple signals are present at the same
point. Where there is a nonlinearity in the system any signal will generate harmonics,
but when two signals are present, harmonics of both are produced. The harmonics of
the two signals can intermix, resulting in further spurious signals that are known as
intermodulation products. The result of an intermodulation signal can have a major
impact on reception if it falls in a receive channel. As the number of signals increases
and/or TX power increases, the probability of an intermodulation signal causing noise
in a receive channel grows.
ITU
International Telecommunications Union. A civil organization established to promote
international standards for telecommunications.
INU
Intelligent Node Unit. INU is the term used to describe the indoor unit of a Harris
Stratex Networks Eclipse Node. The INU is a 1U chassis (the IDC) fitted with
mandatory cards plus option cards. It supports up to three ODUs for three
non-protected links, or one protected/diversity link and one non-protected link.
INUe

Expanded Intelligent Node Unit. The Harris Stratex Networks term used to describe
the 2U indoor unit of an Eclipse Node. The INUe supports up to six ODUs for six
non-protected links, or up to three protected/diversity links.
IP
Internet Protocol. A method or protocol by which data is sent from one device to
another on the Internet.
IRU
Indoor Radio Unit.
ISI
Inter-Symbol Interference.
ISO
International Standards Organization.
ITU-R
International Telecommunication Union - Radio Communication Sector (formerly
CCIR and IFRB).
ITU-T
International Telecommunication Union - Telecommunication Standardization Sector
(formerly CCITT).
K
K1 and K2
In an SDH system, K1 and K2 are MSOH bytes used for
* controlling the multiplexer section protection switching,
* signalling Alarm Indication Signal (AIS), Far End Remote Failure (FERF), and
* signalling Automatic Protection Switching (APS) alarms, when implemented.
L
LAN
Local-area Network. A data network located on a user's premises within a limited
geographical area. Ethernet is the most widely used LAN transport technology.
LBO
Line Build-Out (I/O Cable Distance Compensator).
LED
Light Emitting Diode.
Link
A radio link comprises two terminals, one at each end of the link.
LMCDR
Low-medium capacity data radio.
LMT
Local Maintenance Terminal.
LNA
Low Noise Amplifier.
LO
614-330055-001 July 2009 Glossary -11

Local Oscillator.
LOH
Line Overhead. Contains the media's framing, routing protocol, and network-layer
protocol overhead.
Loopback
A diagnostic function designed to assist testing of system components by routing traffic
back to the direction it came from.
LOS
1) Loss of signal; 2) Line of Sight.
M
MAC address
Media Access Control address. A unique number assigned to every layer 2 Ethernet
device in the world.
Management Information System (MIS)
An organized assembly of resources that collects, processes, and distributes data.
Mbps
Megabits Per Second. Also Mbit/s.
Message Board
Scratch pad text area that allows radio users to leave each other messages.
MGB
Master Ground Bar.
MHSB
Monitored Hot Standby.
MHz
Megahertz = 1 million hertz.
MIB
Management Information Base. A file that describes the information that can be
accessed for each network device. The MIB is required by SNMP.
MMIC
Microwave Monolithic Integrated Circuit.
MIS
Management Information System. An organized assembly of resources that collects,
processes, and distributes data.
MMC
MultiMediaCard. A compact, removable standard for storing and retrieving digital
information in small, low-power devices. MultiMediaCards use flash technology for
reusable recording, and ROM technology for read-only applications.
Modulator/Demodulator
A device used to convert digital signals into analog signals suitable for transmission
over analog communications channels and/or recover digital signals from analog
signals.
MSOH
Multiplexer Section Overhead. Part of an SDH frame.

MSU
Multiplexer Switching Unit.
MTBF
Mean Time Between Failure. The average time (usually expressed in years) over
which a component operates without failure.
MTBO
Mean Time Between Outages. A function of MTBF, MTTR and the probability that the
monitoring circuits detect a failure. The only circuits considered in the MTBO
calculations are the ones that impact traffic.
MTR
Mean Time to Restore.
MTTR
Mean Time to Repair. The average time taken to repair or replace a failed device.
Multiplex
A multiplexer sends/receives two or more signals over the same channel.
Mute
When a transmitter is muted, it is prevented from transmitting.
MUX
Multiplexer. A device that combines two or more information-carrying channels for
transmission over one channel, by using frequency division or time division
techniques.
N
NBI
North Bound Interface.
NE
Network Element.
NEL
Network Elements Level in the TMN model.
NMI
Network Management Interface.
Network Operator
The organization responsible for installing and maintaining a radio network.
NML
Network Management Level in the TMN model.
NMS
Network Management System.
NOC
Network Operations Center.
Node
A network device or device-grouping that is mid-point in a network, as distinct from a
terminal device that is at the end/edge of a network.
Nonprotected
614-330055-001 July 2009 Glossary -13

A 1+0 radio configuration in which there is only one set of radio equipment.
O
O&M
Overhead and Maintenance.
Object Class
The object class identifies the radio type to which the object belongs.
Object Group
A group of network elements created using user-defined selection criteria.
OC-n
Optical Carrier Level n. The optical signal that results from an optical conversion of
a synchronous transport signal n (STS-n). This is the signal that will form the basis
of the interface.
ODU
Outdoor Unit. ODU generally refers to the outdoor transceiver unit that is co-located
with an antenna in a split-mount radio system.
OEM
Original Equipment Manufacturer
ohm
The unit of electrical resistance. A potential difference of one volt across a circuit
resistance of 1 ohm produces a current of one ampere.
OMM
Optical Multimode
OSM
Optical Single Mode
Orderwire
An auxiliary communications channel provided for use by maintenance and service
personnel, typically allowing both voice and/or data transmission between radio
terminals.
Oscillator
An electronic circuit designed to produce an ideally stable alternating voltage or
current.
OSI
Open Systems Interconnection
OSPF
Open Shortest Path First. An OSI layer 3 dynamic routing protocol.
OSS
Operations Support System.
P
PA
Power Amplifier.
PAM

Pulsed Amplitude Modulation.

Path
A radio path refers to the path traversed by the signal between two radios.
PCA
Printed Circuit Assembly.
PCB
Printed Circuit Board.
PCM
Pulse-code Modulation. Modulation in which a signal is sampled, quantized and then
digitized for transmission. PCM is the basic method of encoding an analog voice signal
into digital form using8-bit samples.
PCR
Paperless Chart Recorder. A software based diagnostic tool that stores operational data
from a remote radio and provides view capability to the user.
PCS
Personal Communications Service. A set of capabilities that provides a combination of
terminal mobility, personal mobility, and service profile management.
PDA
Personal Digital Assistant
PDH
Plesiosynchronous Digital Hierarchy. A multiplexing scheme of bit stuffing and byte
interleaving. It multiplexes the lower level 64 kbit/s circuits into a successively higher
order 2 Mbit/s, 34 Mbit/s, 140 Mbit/s and 565 Mbit/s aggregate rates.
Ping
A message used to determine whether an IP address is accessible on a network.
PIU
Plug-In Unit
PLL
Phase-locked Loop. A circuit that controls an oscillator so that it maintains a constant
phase angle relative to a reference signal.
PLT
Party Line Telephone.
PM
Performance Management.
PMA
Protection Multiplex Adaptor.
PN
Part Number.
ppm
Parts per million.
PPP
Point-to-Point Protocol. A TCP/IP routing protocol that allows communications
over serial communications lines without the use of other adapters, such as
614-330055-001 July 2009 Glossary -15

modems.
PROM
Programmable Read Only Memory.
Protection Switch
A unit that controls protection switching in hot-standby, diversity or ring protected
devices.
Proxy
An entity that performs information preparation and exchange on behalf of a device it
is representing.
PSTN
Public switched telephone network.
PSU
Power Supply Unit.
Q
QAM
Quadrature Amplitude Modulation. A method of modulating digital signals using both
amplitude and phase coding.
QoS
Quality of Service.
QPSK
Quadrature Phase Shift Keying. A method of modulating digital signals using four
phase states to code two digital bits per phase shift.
R
RAC
Radio Access Card.
RFI
Radio Frequency Interference.
RAS
Remote Access Server.
RCS
Reverse Channel Switching. A feature set that provides protection against potential
far-end transmitter silent failure.
RDI-L
Remote Defect Indication - Line.
Restricted Area
A location qualified in accordance with IEC Standard 60950-1 as providing an
access that can only be gained by Skilled Persons or users who have been instructed
about the reasons for the restriction applied to the location and about any precautions
to be taken; and access achieved through the use of a Tool, lock and key, or other means
of security, and is controlled by the authority responsible for the location.
RF

Radio Frequency.
RFCOH
Radio Frame Complementary Overhead. Refers to data that is added to a data
transmission unit.
RFU
Radio Frequency Unit.
Rigger
The member of the radio installation team responsible for installing the antenna and
cabling on the transmission tower.
RIM
Radio Interface Module
RIP
Routing Information Protocol. An OSI layer 3 dynamic routing protocol.
RMA
1) Return Material Authorization; 2) Radio Modem Adaptor
RMS
Rack Mounting Space.
Routing Protocol
Routing protocol is a protocol used between routers to exchange routing information.
OSPF and RIP are the two most common dynamic routing protocols.
RPC
Radio Processing Card.
RS
Revertive Switching. A process that sends traffic back to the original working system
after the system returns online.
RSL
Received Signal Level. The signal level at the receiver input (from the antenna). RSL is
usually expressed in dBm.
RSOH
Regenerator Section Overhead. Part of an SDH frame.
RSSI
Received Signal Strength Indicator. The raw indicator of signal level at the receiver
input (from the antenna). Usually expressed as a voltage, RSSI is usually converted to
dBm and presented as an RSL.
RU
Rack Unit, 1 standard EIA rack unit (44.5 mm / 1.75 inch)
Rx
Receive.
S
SAW
Surface Acoustic Wave (filter).
SD
614-330055-001 July 2009 Glossary -17

Space Diversity.
SDH
Synchronous Digital Hierarchy. An international standard for synchronous data
transmission. SDH uses a multiplexing structure that enables direct access to
individual 2 Mbit/s data streams from within the higher order aggregate line signals.
SDLC
Synchronous Data Link Control. A bit-oriented, full-duplex serial protocol that has
spawned numerous similar protocols, including HDLC and LAPB.
SES
Severely Errored Seconds.
SI
System International units.
Simple Network Management Protocol (SNMP)
A networking management protocol used to monitor network-attached devices. SNMP
allows messages (protocol data units) to be sent to various parts of a network. Upon
receiving these messages, SNMP-compatible devices (agents) return data stored in
their Management Information Bases.
Skilled Person
A skilled person in the microwave radio installation and maintenance industry is
considered to have the necessary knowledge and practical experience of electrical and
radio engineering to competently and safely carry out their work. They must have a full
understanding of the various hazards that can arise from working on and around radio
installations and be competent to take responsibility for their safety and the safety of
any other personnel under their immediate supervision.
SLIP
Serial-Line Internet Protocol.
SMA
Services Management Adaptor.
SML
Service Management Level in the TMN model.
SMS
Short Message Service.
SNCP
Subnetwork Connection Protection. Designates path-switched SDH rings that employ
redundant, fiber-optic transmission facilities. Organized in pairs, one fiber transmits
in one direction while the backup fiber transmits in the other. If the primary ring fails,
the backup takes over.
SNR
Signal-to-noise ratio.
SONET
Synchronous Optical Network. An ANSI standard for synchronous data transmission
on optical media that is the equivalent of SDH.
Space Diversity

A protection mode. The main and standby radios are set up in Hot Standby mode, but
are connected to their own antennas. Both antennas, separated by a specific distance,
are receiving the signal transmitted from the online radio at the other end of the link.
If a fault occurs in the receiving end of the link, the traffic is switched to the standby
radio without causing errors (hitless receive switching). As in Hot Standby mode, a
fault detected in the online transmitter causes that transmitter to mute and the standby
transmitter to unmute.
SSC
Software-Software Compatibility.
SSL
Secure Sockets Layer.
Static Routing
Static routing requires manual configuration of the routing table within Layer 3
routers. Data is forwarded within a network via a fixed path defined by the static routes
- it cannot adjust to changing line conditions, unlike dynamic routing.
STDM
Statistical Time Division Multiplexing. Time slots are assigned to signals dynamically
to make better use of bandwidth.
STM-0
ITU digital signal level used in Synchronous Digital Hierarchy (SDH) equivalent to a
51.84 Mbps data rate.
STM-1
ITU digital signal level used in Synchronous Digital Hierarchy (SDH) equivalent to a
155.52 Mbps data rate.
STM-N
Synchronous Transport Module-level N (Nx155.52 Mbps) where N = 1, 4, 16 or 64.
STS-N
Synchronous Transport Signal-level N (Nx51.84 Mbps) where N = 1, 3, 12, 48, or 192.
Subnet
A portion of a network sharing a particular subnet address.
Subnet Mask
A 32-bit combination used to describe which portion of an address refers to the subnet
and which part refers to the host.
SU
Switch Unit.
SWR
Standing Wave Ratio.
T
T-R Spacing
The difference in MHz between transmit and receive frequencies for duplex radios.
T1
614-330055-001 July 2009 Glossary -19

A digital carrier system for DS1 signals. T1 is a term for a digital facility used to transmit
a DS1 formatted digital signal at 1.544 megabits per second. The 'T' is about the carrier
facility and the 'DS' is about the signal format, which includes the muxed relationship
between DS0, DS1, DS2, and DS3.
T3
T3 is a term for a digital facility used to transmit a DS3 formatted digital signal at 44.7
megabits per second.
The 'T' is about the carrier facility and the 'DS' is about the signal format, which
includes the muxed relationship between DS0, DS1, DS2, and DS3.
TAE
Transversal Adaptive Equalization
TCP/IP
Transmission Control Protocol/Internet Protocol. Protocols that define connectivity
across computer platforms interconnected via the Internet. The TCP protocol is
responsible for an error free connection between two computers, while the IP protocol
is responsible for the data packets sent over the network.
TCM
Trellis-Coded Modulation. A bandwidth-efficient scheme that combines
error-correction coding with modulation. The redundancy thus introduced by the
coding does not expand the bandwidth, since the parity bits are absorbed by the
extended signal constellation. Two-dimensional (2D) TCM uses dependency between
in-phase and quadrature symbols, while four-dimensional (4D) TCM introduces
dependency between symbols of two successive intervals.
TCXO
Temperature Controlled Crystal Oscillator.
TELNET
A terminal emulation program for TCP/IP networks such as the Internet. The Telnet
program runs on your computer and connects your PC to a server on the network. You
can then enter commands through the Telnet program and they will be executed as if
you were entering them directly on the server console. This enables you to control the
server and communicate with other servers on the network. To start a Telnet session,
you must log in to a server by entering a valid username and password. Telnet is a
common way to remotely control Web servers.
TFTP
Trivial File Transfer Protocol.
TIM
Tributary Interface Module.
TMN
Telecommunications Management Network.
Tombstone
A database stored in nonvolatile memory.
Trap
A program interrupt, usually caused by some exceptional situation in the user program.
In most cases, the operation system performs some action, then returns control to the
program. Used for event notification with SNMP.
Tree View

A ‘trunk to branches and leaves’ view. It is often applied to a network where the core of
the network is the trunk, and the various end-user connections are the leaves.
Tree Viewer
The Tree Viewer is part of the ProVision User Interface. The entire radio network is
represented as a tree of containers and radios. Each container (for example, a region)
is represented as a parent, with all the devices positioned underneath, as its children.
Regions, sites, racks, and devices are listed in alphabetical order.
Trib
Tributary.
Transistor-Transistor Logic (TTL)
A common semiconductor technology for building discrete digital logic integrated
circuits. It originated from Texas Instruments in 1965.
Tx
Transmit.
U
UDP/IP
Universal Datagram Protocol/Internet Protocol. Used primarily for short, broadcast
messages, such as for SNMP messaging. UDP does not guarantee reliability or ordering
in the way that TCP does. Datagrams may arrive out of order, appear duplicated, or go
missing without notice. Avoiding the overhead of checking whether every packet
actually arrived makes UDP faster and more efficient than TCP, at least for applications
that do not need guaranteed delivery. Time-sensitive applications often use UDP
because dropped packets are preferable to delayed packets.
UTC
Coordinated Universal Time. A time format used when a time zone independent time
and date is required. Identical to Greenwich mean time (GMT) for most purposes.
V
V.24
Serial data communication interface. Also called RS-232.
VCO
Voltage Controller Oscillator. An electronic circuit designed to produce an ideally
stable alternating voltage.
Vdc
Volts, direct current.
VDE
Video Display Emissions.
VF
Voice Frequency signal.
Video graphics array (VGA)
A display standard for IBM PCs.
Viterbi
614-330055-001 July 2009 Glossary -21

Viterbi is a “convolutional code” which is used in data correction circuits. It operates on
serial data, one or a few bits at a time, unlike block codes such as Reed-Solomon, which
operate on relatively large message blocks (typically greater than 100 bytes).
VLSI
Very Large Scale Integration.
Voltage Controlled Oscillator (VCO)
An electronic circuit designed to produce an ideally stable alternating voltage.
VPN
Virtual Private Network.
VSWR
Voltage Standing Wave Ratio.
VT100
A port on the IDU for making a connection to the NMI card.
W
WAN
Wide-area Network. A network that provides telecommunication services to a
geographic area larger than that served by a local area network or a metropolitan area
network.
WAP
Wireless Application Protocol.
WMT
Web-based Maintenance Terminal.
WR-xx
The designation for a specific size of waveguide used to transmit the microwave RF
signal.
X
XPD
Cross-Polar Discrimination.
XPIC
Cross Polarized Interference Cancellation.

Index
Numerics B
15-minute data collection Backups 3-124
enabling and disabling 5-17 menu functions 2-19
for DAC plug-in 5-20 Browser
launching from device 5-51
A to access non-HSX devices 5-50
Bulk Configuration
about i-ii definition 3-72
Acknowledging delete 3-79
network events 4-10 setting up 3-72
Activating settings 3-75
DART tributary loopback 5-92
Eclipse radio software 3-110
C
Eclipse software 3-110
managed status for a device 3-51 CAUs
XP4 tributary loopback 5-73 customize event names 4-18
XP4 tributary loopback, local 5-78 deploying 3-27
Adding diagnostic controls for 5-90
logical link 4-76 CB 149
prefilters 4-40 view TNet performance for 5-68
ADR Changing
deploying 3-13 event browser options 4-29
icon 2-26 password 2-6
view plug-ins for 3-69 TNet device subnet 3-82
Alarms XP4 protection settings 5-81
conditions activating XP4 protection 5- Chassis Views
81 see Equipment Views 2-39
icons and 2-55 Circuit bundles
link to performance criteria 5-42 configure 3-102
manually resynchronize 4-15 configure for logical container 3-100
manually resynchronize for TR 6400 4- definition 3-84
16 remove circuit from 3-102
TNet inputs and outputs 5-62 Circuit Diagnostics 5-5
Altium 2-26 end-to-end tests 5-13
configuration view 3-67 options 5-13
craft tool 5-50 segment tests 5-13
craft tool instructions 5-55 set up test 5-10
data collection 5-14 Circuit Trace
icon 2-26 circuit features 3-87
Network Health Report 5-112 definition 3-84
security log entries 4-49 G.826 annotations 3-88
Altium MX 2+0 2-26 G826 annotations 3-88
icon 2-26 naming 3-89
Aurora required for diagnostics 5-6
deploying 3-13 running 3-85
single circuit 3-90
614-330055-001 July 2009 1

text annotations 3-89 view radio 3-66, 3-72
toggle switch 3-87 viewing a radio’s 3-66
view and hide multiple circuits 3-87 Configuration Alarm Units
viewing 3-86 deploying 3-27
Circuits Configuration Profiles
add to circuit bundles 3-102 bulk configuration 3-72
add to logical containers 3-100 creating 3-72
add to logical containers from right- delete 3-79
click 3-102 executing 3-73
Circuits tab 2-29 menu functions 2-18
commissioning 3-97 overview 3-72
configure circuit bundle 3-102 reading 3-73
configure logical containers 3-100 settings 3-75
decommissioning 3-97 Configuring
definition 3-84 Constellation 3-25
delete 3-109 DXR 200 radios 3-57
diagnostics 3-99, 5-5 DXR SMAs 3-57
diagnostics window 5-7 event notification rules 4-57
event browser for 3-99 protected TNet links 5-64
functions 3-98 Consider 4-88
functions, advanced 3-98 Constellation
invalid 3-107 configuration viewer 3-67
labeling 3-89 configuring 3-25
logical containers and 3-91 deploy new 3-25
performance statistics for 3-88 diagnostic controls for 5-85
pop-up menu functions 3-98 equipment view 2-39
problem indicators 3-107 equipment views 2-39
remove from circuit bundle 3-102 Inventory Report 5-101
remove from logical containers 3-100 Network Health Report 5-112
rename 3-106 resync alarms 4-15
retrace 3-105 contact data
synchronize names 3-108 Harris Stratex Networks i-iii
trace required for diagnostics 5-6 Contact Details
tracing 3-84 for users 2-7
view and hide multiple circuits 3-87 Containers
view elements within a circuit 3-99 adding 3-7
Class Checking 3-16 creating 3-7
invalid deployment if not performed 3- deleting 3-9
18 renaming 3-9
Classic II Craft Tools
icon 2-28 about 5-50
Clear Correlation DXR NET 5-50
definition 4-14 enabled functions 5-52
Clearing launching 5-52
network events manually 4-14 LE3000 5-54
Community String list of available 5-50
definition 3-11 Memotec 5-54
Computer Equipment NCT 5-51
display resolution on monitor 2-2 overview 5-4, 5-50
Configuration Portal 5-50
save as .CSV file 3-66 TNet Web 5-51

TNet Web details 5-58 overview 5-14

WMT 5-50 performance monitoring data 5-14
WMT details 5-55 RSSI data 5-14
XP Web 5-51 Database
Creating backup via menu 2-19
configuration profile 3-72 locking 2-2
logical containers 3-92 purging 2-19
RF links 3-60 searching 2-50
RF links from Find 3-61 Deactivating an XP4 Tributary Loopback 5-
RF links from Tree Viewer 3-60 78
scoreboard 4-84 Deleting
Scoreboard Group 4-81 a device from a service 4-72
scoreboard groups 4-81 a service 4-74
scoreboards 4-84 circuits 3-109
Customer contact details container 3-9
viewing 2-9 devices 3-50
Customer Support event browser 4-33
Harris Stratex Networks 2-9 event notification rule 4-56
Customizing 2-48, 4-26 event prefilter 4-47
event browser 4-26 logical links 4-77
pre-filtering 4-47
D radio frequency links 3-65
Scoreboard Group 4-83
DAC Plug-Ins scoreboards 4-88
enabling data collection 5-20 server reports 5-111
view performance 5-21 Dependencies
DART deploying, devices 3-4
activate tributary loopback 5-92 managing, devices 3-4
configuration profile settings 3-77 managing, events 4-3
configuration view 3-67 Deploying 3-6
deploying 3-13 class checking for Eclipse 3-16
diagnostics 5-91 Constellation 3-25
icon 2-26 containers 3-7
local trib loopback 5-92 definition 3-1
loopbacks 5-91 devices 3-4
remote trib loopback 5-92 DXR 200 3-39
DART NMS Trap Destination 3-77 DXR SMA 3-39
Data Eclipse node 3-15
collection 5-14 EfficientSite Manager 3-33
event data 3-52 generic SNMP device 3-29
into usable information 1-3 Harris Stratex SNMP device 3-11
managing over time 1-3 MegaStar 1+1 3-14, 3-27
Data Collection MegaStar MN 3-14
15-minute collection 5-17 multiplex radios 3-13
about 5-14 network autodiscovery 3-42
change device status for 5-18 prerequisites 3-4
DAC plug-in 5-20 process overviews 3-4
daily 5-15 Protected radios 3-13
ethernet performance data collection 5- single device radios 3-13
20 SMA device 3-39
menu functions 2-18 SNMP devices 3-11
614-330055-001 July 2009 3

StarMAX 3-31 configuration view 3-67
TNet device into proxy manually 3-38 deploying 3-39
TNet devices 3-34 managing 3-57
TNet proxy 3-37 view plug-ins for slots 3-69
TNet troubleshooting 3-36 DXR 700
TRuepoint devices 3-18 configuration view 3-67
WiMAX 3-31 icon 2-26
Devices manually discover 3-56
apply pre-filter for events to 4-44 DXR SMA
change data collection status 5-18 deploying 3-39
configuration view 3-66, 3-72 managing 3-57
deleting 3-50
deleting from service 4-72 E
deploying prerequisites 3-4
Harris Stratex SNMP devices 3-11 Eclipse
managing 3-51 backup configuration of 3-124
object pop-ups 2-58 deploy via autodiscovery 3-42
rename 3-49 network autodiscovery 3-42
reset XP4 5-84 Network Health Report 5-112
services overview 4-69 security log entries 4-49
sleep status 4-20 Eclipse configuration 3-124
states 2-58 Eclipse Ethernet Port Settings DAC ES 3-76
unmanaging 3-54 Eclipse Ethernet Port Settings DAC GE 3-77
Diagnostic Controls Eclipse Ethernet Port Settings for IDU ES 3-
about 5-85 75
CAU 5-90 Eclipse Ethernet Priority Mapping for DAC
Constellation 5-85 GE 3-77
DART 5-91 Eclipse Ethernet Priority Mapping for IDU
DVA 5-95 ES 3-75
MegaStar 5-96 Eclipse License
using 5-85 menu functions 2-17
when applied 5-50 Eclipse NMS Traps Destination 3-75
Diagnostics Eclipse Node
circuits 3-99 deploying 3-15
Disabling license, installing 3-121
15-minute data collection 5-17 menu functions 2-17
Discovering Eclipse OSPF Settings 3-76
DXR 200 radios 3-57 Eclipse Radios
DXR 700 radios 3-56 bulk configuration settings 3-75
RF links 3-64 circuit tracing 3-85
TRuepoint 6500 configurations 3-55 data collection 5-14
Display Resolution 2-2 deploying INU, INUe, or IDU 3-16
DVA deploying protected node 3-16
deploying 3-13 radio frequency links, creating 3-62
diagnostic controls for 5-95 remotely upgrading software 3-110
DVM view plug-ins for 3-69
deploying 3-13 Eclipse Reports
DXR fault report 5-107
craft tools 5-50 inventory report 5-101
icon 2-26 Eclipse Software 3-110
DXR 200 activating 3-118

load onto radios 3-115 viewing 2-48

loading example 1 3-111 Event Log
registering on server 3-113 about 4-36
remote upgrade 3-110 deleting pre-filter 4-47
upgrade process 3-111 filtering overview 4-36
Eclipse Time Server Settings 3-76 modify pre-filter 4-45
Eclipse Time Zone Settings 3-76 object level pre-filter 4-43
Editing objects to be pre-filtered 4-38
performance data status 5-18 pre-filter from Event Browser 4-44
scoreboard 4-87 pre-filtering view 4-39
Scoreboard Group 4-83 root level pre-filter 4-40
EfficientSite Manager Event Notification
Deploying 3-33 adding rule 4-53
deploying 3-33 configuring rule 4-57
using 5-98 delete rule 4-56
Enabling dialog box 4-63
15-minute data collection 5-17 editing rule 4-53
Equipment Malfunctions email notification setup 4-60
identifying 5-2 overview 4-51
Equipment Views pop-up message notification setup 4-63
about 2-39 preferences 4-52
opening 2-39 script execution setup 4-66
Ethernet Event Pre-filter
performance data collection 5-20 definition 2-17
view performance 5-21 Event Properties
Ethernet Bandwidth Utilization 5-28 probable cause tab 4-9
Event Browser viewing 4-8
about 4-22 Event States
acknowledge events from 4-10 acknowledged 4-6
customization filters 4-27 cleared by ProVision 4-6
customizing 4-26 cleared by user 4-6
deleting 4-33 clearing 4-6
description 2-47 unacknowledged 4-6
filtering event logs 4-36 Event Status
hide 2-14 network events 4-6
maximum events 2-47 Event Traffic
navigating 4-22 verifying 3-52
new, opening 2-16 Events
opening 4-22 customize names 4-18
option settings 4-29 manually resynchronize alarms 4-15
option settings, values 4-30 manually resynchronize TR 6400
overview 4-22 alarms 4-16
pop-up menu for events 2-48 prefiltering 4-40
printing 4-35 prefilters
resize 2-14 delete 4-47
save settings in 2-48 modify 4-45
save to file 4-34 severity color coding 2-57
save view 4-24 states 4-6
saving 4-24 verifying receipt of 3-52
security log, opening 2-16 viewing 4-7
view saved 4-25 viewing prefilters 4-39
614-330055-001 July 2009 5

Exceptions Altium MX 2+0 2-26
logging in 2-4 caution 1-4
user session 2-4 circuit information icon 3-107
Exiting circuit invalid icon 3-107
user session 2-5 Classic II 2-28
Container icons 2-25
F DART 2-26
DART protected 2-26
Fault Report display and status 2-55
Eclipse 5-107 DXR 2-26
Filtering DXR 700 2-26
event logs 4-36 DXR 700 protected 2-26
events at input 4-39 DXR protected 2-26
Flat Map 2-33 event severity color codes 2-57
information 2-55
G LC Series 2-28
G.821 M Fiber 2-28
view TNet performance for 5-66 M Series 2-28
G.826 Performance Data note 1-4
identify problems for device 5-35 Quantum 2-28
performance history 5-35 reading data for 2-55
view trends for 5-38 Spectrum I 2-28
Generic Devices Spectrum II 2-28
customize event names 4-18 TNet Proxy 2-28
deploying 3-29 Velox 2-27
interface view 2-46 W Series 2-28
Graphics warning 1-4
map background 2-36 XP4 16/E3/DS3 2-27
XP4 16/E3/DS3 remote 2-27
XP4 16/E3/DS3 remote protected 2-27
H
XP4 2/4/8x 2-28
Hardware XP4 2/4/8x protected 2-28
for radio 3-71 XP416/E3/DS3 protected 2-27
Harris Stratex Networks Increase
contact data i-iii TNet Proxy subnets 3-82
customer support 2-9 Installing
Harris Stratex SNMP Devices Eclipse node license 3-121
deploying 3-11 Interface Views
Help definition 2-46
online 2-11 InterfaceViews
Hierarchical Map opening 2-46
map background graphic 2-36 Inventory Report 5-101
Highlight 4-30 about 5-101
History saving 5-104
of performance 5-33 saving, multi-radio version 5-105
How ProVision works 1-2 viewing 5-102
IP Address
I change for TNet Proxy 3-82
menu functions 2-17
Icons 2-26 searching for 2-51
ADR 2-26 view/change for network 3-80

L XP4 radio 5-73
Labeling
M
circuits 3-89
Launching M Fiber
craft tools 5-52 icon 2-28
LC Series M Series
icon 2-28 icon 2-28
LE3000 Managing
craft tool, installing 5-54 definition 3-1
deploying 3-13 description of 3-51
interface view 2-46 devices 3-51
Inventory Report 5-101 DXR 200 radios 3-57
Network Health Report 5-112 DXR SMAs 3-57
security log entries 4-49 event dependencies 4-3
License event scenarios 4-78
Eclipse Node 3-121 events, overview of 4-1
evaluation 2-8 radios
menu functions 2-17 prerequisites 4-3
permanent 2-8 removing from device 3-54
viewing details 2-8 Managing Events
Link network events 4-5
creating 3-60 prerequisites 4-3
non-protected 3-62 sources of event data 4-1
protected 3-62 suggested process 4-3
ring-protected 3-62 when to 4-1
Loading Manually Clearing Events 4-14
Eclipse software 3-110 Map Viewer
Local Loopback description 2-31
DART 5-92 Flat Map 2-33
Logging In 2-2 hide 2-14
exceptions 2-4 map background graphic 2-36
multiple users 2-2 overview 2-31
Logging Off 2-5 Physical view 2-32
Logging Out 2-5 properties 2-34
Logical Containers repositioning objects 3-48
add circuit bundle 3-100 resize 2-14
add circuit to 3-102 submaps 2-38
creating 3-92 tools 2-34
definition 3-91 visible object types 2-31
functions 3-98 Maps
remove circuit from 3-100 backgrounds, add 2-36
view circuits assigned 3-91 backgrounds, remove 2-36
Logical Links moving objects 3-48
creating 4-76 MegaStar
deleting 4-77 diagnostic controls for 5-96
renaming 4-76 equipment view 2-39
Loopback Test equipment views 2-39
DART 5-91 resync alarms 4-15
run 5-10 MegaStar 1+1
set up 5-10 deploying 3-14, 3-27
614-330055-001 July 2009 7

MegaStar MN pre-filtering icon 4-39
deploying 3-14 repositioning 3-48
Memotec repositioning in map 3-48
craft tool, installing 5-54 Online Help 2-11
deploying 3-13 opening 2-12
view plug-ins for 3-69 terminology 1-4
Menus 2-15 using 2-11
main user interface 2-15
menu items 2-15 P
pop-up menus 2-22
MicroStar Packets
deploying 3-14 displayed in Ethernet performance view
Mobility Neighbors 5-23
view for WiMAX 5-46 Passwords
Modifying changing 2-6
event prefilters 4-45 Path Degradation
scoreboard groups 4-83, 4-87 identifying 5-2
Modulation Performance Analysis
trellis-coded Glossary-20 overview 1-3
Moving 3-48 Performance Data
15-minute collection 5-17
daily 5-15
N
Ethernet 5-20
Naming Standards 3-2 Performance Data collection screen 5-
Navigating 18
Event Browser 2-47 performance history 5-33
menu bar 2-15 performance thresholds 5-42
Network 4-5 performance trends 5-38
IP addresses 3-80 report view for device 5-36
Network Events Performance History
acknowledging 4-10 TRuepoint 6500 specific 5-37
clearing 4-14 Performance Monitoring
overview 4-5 data collection 5-14
status of 4-6 Performance Threshold
unacknowledging 4-12 about 5-42
Network Failure TRuepoint 6500 specific 5-45
identify 5-33 Performance Trends 5-38
Network Health Report Physical Map 2-32
about 5-112 Plug-Ins
device types 5-112 view for Eclipse radios 3-69
values 5-115 Pop-Up Data
viewing 5-114 via Tree Viewer 2-58
NOC Pop-Up Menus
engineer role 1-1 about 2-22
operator role 1-1 circuits 3-98
Notification Dialog Box 4-63 Portal
craft tool 5-50
O craft tool table 5-4
Pre-Deploying 3-4
Objects Prefilters
pre-filtering activated 4-38 adding 4-40

viewing 4-39 configuration profiles 3-72

Prerequisites deployment process 3-4
event management 4-3 icons for 2-25
for deploying devices 3-4 pop-ups for 2-58
managing, radios 4-3 pre-deploying before network rollout 3-
system diagnostics 5-2 4
Printing 4-35 tasks 2-59
event browser data 4-35 5 and 15-min data collection 2-59
Protected Radios performance thresholds 2-59
deploying 3-13 waking 4-22
Protection Settings Region Container
XP4 5-81 icon 2-26
XP4 radio 5-81 Remote Loopback
ProVision 5-4 DART 5-92
client 1-2 Renaming 3-49
how it works 1-2 a service 4-73
optimum use 1-3 circuits 3-106
receiving events 3-52 container 3-9
server 1-2 devices 3-49
skill set prerequisites 1-2 logical link 4-76
user accounts 2-19 TNet Proxy 3-82
version number 2-10 Reports
ProVision Manager Eclipse fault 5-107
icon 2-25 inventory report 5-101
Proxies network health reports 5-112
TNet 3-34 Performance Data 5-36
Purging saving Inventory, multiple radios 5-105
database 2-19 saving Inventory, single radio 5-104
server reports 5-111
Q Repositioning
object 3-48
Quantum Resetting
icon 2-28 XP4 5-84
Retrace
R circuit 3-105
Rack Container Right-click Menus
icon 2-26 see pop-up menus 2-22
Radio Frequency Links Roles
about 3-59 NOC engineer 1-1
create from Find function 3-61 NOC operator 1-1
create from Tree Viewer 3-60 Root Container
creating for Eclipse radios 3-62 icon 2-26
deleting 3-65 RSSI
Discover RF Link function 3-64 view TNet performance for 5-70
Eclipse link types 3-62
Eclipse radios 3-62 S
verifying for Eclipse or TRuepoint 3-64 Sagem-link Radio
Radio Tasks 2-59 deploying 3-13
Radios Saving
configuration data 3-66 event browser contents 4-24, 4-34
614-330055-001 July 2009 9

event browser view 4-24 SNMP radios
inventory report 5-104, 5-105 create RF link, via Tree Viewer 3-60
server reports 5-111 Software
Scenarios for radio 3-71
managing events 4-78 new Eclipse 3-110
Scoreboard Software Loading
adding 4-84 menu functions 2-18
definition 4-84 Software Table
editing 4-87 viewing 2-17
view event browser from 4-88 Spectrum I
Scoreboard Groups icon 2-28
about 4-78 Spectrum II
creating 4-81 icon 2-28
deleting 4-83 Network Health Report 5-112
editing 4-83 StarMAX
functions 4-79 6100, deploying 3-31
modifying 4-83 6400, deploying
scoreboards 4-84 WSC ASN-GW Controller
viewing 2-16, 4-80 deploying 3-31
Scoreboards deploying 3-31
creating 4-84 deploying all types 3-31
deleting 4-88 equipment views 2-39
modifying 4-87 interface views 2-46
Searching Status
all ProVision data 2-50 asleep 2-58
locate function 2-16 connecting 2-58
main function 2-50 errored 2-58
search all ProVision data 2-50 managed 2-58
via Tree Viewer 2-53 of devices 2-58
Security Log 4-49 unmanaged 2-58
about and viewing 4-49 Submaps 2-38
Server Reports 5-111 open 2-38
Service Links 4-75 Subscriber Stations
Services deploying 3-31
deleting a service 4-74 view connectivity 5-48
removing a device 4-72 Synchronize
renaming a service 4-73 circuit names 3-108
service links, overview 4-75 System Diagnostics
Site Container circuit diagnostic window 5-7
icon 2-26 circuit diagnostics, run 5-10
Sleep Status circuits 5-5
overview 4-20 DART diagnostics 5-91
setting for device 4-20 diagnostics 5-1
SmartCore WiChorus ASN-GW overview 5-1
deploying 3-31 prerequisites 5-2
SNMP device procedures 5-5
deploying 3-29 using 5-2
SNMP Devices when to use 5-2
deployment details 3-16 XP4 details 5-72
SNMP devices
deploying 3-11

T using toggle 2-25

Tributary Loopback
Task Manager screen 2-49 activate for XP4 5-73
Tasks activate local for XP4 5-78
radio 2-59 DART 5-92
Technical Support local MSU E3 5-75
version number 2-10 remote SU E3/DS3 5-74
viewing contact information 2-9 Troubleshooting
Telnet TNet deployment 3-36
launching from device 5-51 TRuepoint
to access non-HSX devices 5-50 deploying 3-18
TNet equipment view 2-39
alarm input and output 5-62 equipment views 2-39
CB 149 diagnostic values 5-68 Inventory Report 5-101
configure protected links 5-64 IP address capture 3-17, 3-21, 3-26
craft tool details 5-58 Network Health Report 5-112
craft tool for 5-51 redundant NMS connection support 3-
diagnostic tools 5-62 17, 3-21, 3-26
features for devices 5-59 security log entries 4-49
G.821 diagnostic values 5-66 verify RF links 3-64
Protection diagnostic values 5-64 TRuepoint 4000
RSSI diagnostic values 5-70 resync alarms 4-15
severity levels fori nputs 5-59 TRuepoint 6400
user-defined inputs and outputs for 5- resync alarms 4-16
59 TRuepoint 6500
TNet Devices deploying 3-22
change subnet 3-82 Inventory Report 5-103
deploying 3-34 manually discover 3-55
manually deploying into proxy 3-38 Performance History 5-37
proxies 3-34 Performance Threshold 5-45
troubleshooting 3-36 unique characteristics 3-22
TNet Proxy
change IP address 3-82
U
change name 3-82
configuration 3-81 Unacknowledging
deploying 3-37 network events 4-12
icon 2-28 Unmanaging 3-54
increase subnets 3-82 Upgrading
viewing status 3-83 Eclipse radio software 3-110
TNet Proxy Configuration User Interface 2-13
view/change 3-81 customizing 2-14
TNet Proxy Viewer 3-83 map viewer 2-31
Topology maximize 2-14
exporting 2-16 minimize 2-14
trademarks i-ii User Session
Tree Viewer exceptions 2-4
hide 2-14 exiting 2-5
object pop-ups 2-58 start 2-2
resize 2-14 starting 2-2
searching inside 2-53 Users
user interface 2-24 contact details, saving 2-7
614-330055-001 July 2009 11

multiple user sessions 2-2 deploying 3-31
device types 3-31
V equipment views 2-39
interface views 2-46
Velox network autodiscovery 3-42
configuration view 3-67 subscriber station connectivity viewing
craft tool for 5-51 5-48
deploying 3-13 Subscriber Station CPE list 5-48
icon 2-27 WSN ASN-GW Controller 5-46
security log entries 4-49 WiMAX SmartChorus ASN-GW
Verifying configuration viewer 3-70
event traffic 3-52 WiMAX Subscriber Stations
events, receipt 3-52 connectivity viewing 5-48
RF links, Eclipse 3-64 deploying 3-31
RF links, TRuepoint 3-64 WL1000
Version Number 2-10 deploying 3-13
viewing 2-10 interface view 2-46
Viewing 4-25 Network Health Report 5-112
customer contact details 2-9 workflow diagrams
Ethernet performance 5-21 managing events 4-2
event log pre-filtering 4-39 system diagnostics 5-2
event properties 4-8 WSN ASN-GW
events 4-7 Controller view 5-46
Flat Map 2-33
inventory report 5-102
X
license details 2-8
performance data status 5-18 XP4
Physical Map 2-32 activate loopback 5-73
prefilters 4-39 activate loopback, local 5-78
ProVision license details 2-8 configuration view 3-67
ProVision version number 2-10 craft tool for 5-51
radio configuration 3-66, 3-72 data collection 5-14
saved event browser view 4-25 deploying 3-13
Scoreboard Groups 4-80 diagnostics 5-72
scoreboard groups 4-80 local loopback types 5-79
XP4 protection settings 5-81 Network Health Report 5-112
protection settings 5-81
W XP4 16/E3/DS3
icon 2-27
W Series XP4 2/4/8x and XP4 2/4/8x (protected)
icon 2-28 icon 2-28
Waking XP4 2/4/8x icon 2-28
radios 4-22 XP4 radio
warranty i-ii loopbacks 5-73
When 4-26 protection settings 5-81
WiChorus tributary loopback
deploying 3-31 local MSU E3 5-75
WiMAX remote SU E3/DS3 5-74
ASN-GW Mobility Neighbors viewer 5- XPF
46 reset 5-84
deploy via autodiscovery 3-42

614-330055-001
www.harrisstratex.com

Provision 6.4.3 UserManual

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Provision 6.4.3 UserManual

Uploaded by

Copyright:

Available Formats

ProVision 6.4.

614-330055-001 Rev 024 July 2009

Copyright © 2009 by Harris Stratex Networks, Inc.

ii Harris Stratex Networks

Corporate Headquarters International Headquarters

Harris Stratex Networks Harris Stratex Networks Harris Stratex Networks

TAC.AM@hstx.com TAC.EMEA@hstx.com TAC.ACPAC@hstx.com

614-330055-001 July 2009 iii

iv Harris Stratex Networks

CHAPTER 1, MAKING PROVISION WORK FOR YOU

CHAPTER 2, NAVIGATING PROVISION

614-330055-001 July 2009 1

CHAPTER 3, DEPLOYING AND MANAGING DEVICES

2 Harris Stratex Networks

Viewing/Changing Network IP Addresses.................................................... 3-80

CHAPTER 4, MANAGING EVENTS

614-330055-001 July 2009 3

4 Harris Stratex Networks

CHAPTER 5, SYSTEM DIAGNOSTICS AND REPORTS

614-330055-001 July 2009 5

6 Harris Stratex Networks

Welcome to ProVision. ProVision is a management tool for monitoring the elements in

This documentation is for all ProVision users, including:

This section includes the following topics:

614-330055-001 July 2009 1

Experience working in a ProVision environment is also helpful.

The ProVision Installation and Administration Guide (P/N 614-330053-001) contains

2 Harris Stratex Networks

This manual is organized into the following chapters and appendices:

Deploying and Managing Devices

System Diagnostics and Reports

614-330055-001 July 2009 3

A caution item identifies important information pertaining to

A warning item identifies a serious physical danger or major possible

A note item identifies additional information about a procedure or

4 Harris Stratex Networks

The Goals of ProVision

614-330055-001 July 2009 1-1

How ProVision Works

1-2 Harris Stratex Networks

Getting the Most Value from ProVision

Turning Data Into Information

Managing Data Over Time

Using Performance Analysis

614-330055-001 July 2009 1-3

Performance data can provide information in many ways. If a radio is having

1-4 Harris Stratex Networks

614-330055-001 July 2009 2-1

This section includes the following topics:

Getting Started Procedures

Starting a User Session

Set your display resolution to a minimum of 1024 x 768. This ensures

2-2 Harris Stratex Networks

2. The ProVision Login window displays.

614-330055-001 July 2009 2-3

Select OK and retype your user name and password.

Select OK and retype the server name.

2-4 Harris Stratex Networks

Exiting a User Session

2. To close your ProVision user session, select Yes.

614-330055-001 July 2009 2-5

Changing Your Password

If you type an invalid password in any of the password boxes, an error