ProVision 6.5.2 User Manual PDF

PROVISION
USER GUIDE
6.5.2
614-330055-001
ProVision User Guide Version 6.5.2
ProVision User Guide

614-330055-001 Rev 026 December 2010
This manual incorporates features and functions provided with ProVision 6.5.2.
AviatCopyright 2010 by Aviat 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 Aviat Networks Inc. To request permission, contact techpubs@aviatnet.com.
Warranty
Aviat 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, Aviat Networks reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Aviat 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. Access to the Equipment: Access to the equipment in use must be restricted to service personnel only. 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. Service Personnel Skill: Service personnel must have received adequate technical training on telecommunications and in particular on the equipment this manual refers to.
2. 3.
4.
Trademarks
All trademarks are the property of their respective owners.
ii
Aviat Networks
Contact InformationAviat
Sales and Sales Support:
For sales information, contact one of the Aviat Networks headquarters, or find your regional sales office at Aviathttp://www.aviatnetworks.com/contact . Corporate Headquarters North Carolina, USA Aviat Networks, Inc. Research Triangle Park 637 Davis Drive Morrisville, North Carolina 27560 United States Phone: + 1 919-767-3230 Fax: + 1 919-767-3233 Toll Free for Sales Inquiries: + 1 888-aviatnet-NOW (888-478-9669) Phone: +65 6496 0900 Fax: + 65 6496 0999 Sales Inquiries: +1-321-674-4252 International Headquarters Singapore Aviat Networks (S) Pte. Ltd. 17, Changi Business Park Central 1 Honeywell Building, #04-01 Singapore 486073
Customer Service:
For customer service, contact one of the regional Technical Help Desks listed below. Americas Technical Help Desk Aviat Networks 120 Rose Orchard Way San Jose, CA 95134 U.S.A. EMEA Technical Help Desk Aviat Networks 4 Bell Drive Hamilton International Technology Park Blantyre, Glasgow, Scotland G72 0FB United Kingdom Phone:+44 1698 714 073 Fax: +44 1698 717 204 Asia Pacific Technical Help Desk Aviat Networks Bldg 10, Units A&B Philexcel Industrial Park M. Roxas Hi-way Clark Freeport Zone Philippines 2023 Phone:+63 45 599 5192 Fax: +63 45 599 5196
Phone:+1 210 561 7400 Toll-free in US: +1 800 227 8332 Fax: +1 408 944 1683 TAC.AM@aviatnet.com
TAC.EMEA@aviatnet.com
TAC.APAC@aviatnet.com
Or you can contact your local Aviat Networks office. Contact information is available on our website at: www.aviatnetworks.com/support/customer/.
614-330055-001 February 2010
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 rglage ou modification faits cet quipement hors du cadre dict par ce guide dutilisation ou par toute autre documentation supplmentaire pourraient causer des blessures ou endommager lquipement et peut entraner lannulation de sa garantie.
WARNUNG
Die an diesen Gerten gemachte Einstellungen und/oder nderungen, welche nicht gem dieser Bedienungsanleitung, oder gem anderen zustzlichen Anleitungen, ausgefhrt werden, knnen Verletzungen oder Materialschden zur Folge haben und eventuell die Garantie ungltig machen.
ATENCIN
Llevar a cabo ajustamientos y/o modificaciones a este equipo, sin seguir las instrucciones provistas por este manual u otro documento adicional, podra resultar en lesiones a su persona o daos al equipo, y anular la garanta de este ltimo.
iv
Aviat Networks
Contents
WELCOME
TO
PROVISION 1
What You Need To Know To Use ProVision ..........................................................................................0-2 Additional Documentation ....................................................................................................................0-2 Documentation Organization................................................................................................................0-3 Documentation Conventions and Terminology....................................................................................0-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-4 Changing Your Password ...........................................................................................................2-4 Entering Your Contact Details ...................................................................................................2-5 Viewing Your ProVision License Details ....................................................................................2-6 Viewing Customer Support Contact Details .............................................................................2-7 Viewing ProVisions Version Number ........................................................................................2-7 Using the Online Help................................................................................................................2-8 The ProVision User Interface ...............................................................................................................2-9 Customizing the User Interface....................................................................................................2-10 Menu Bar .......................................................................................................................................2-11 Main Tool Bar ................................................................................................................................2-16 Right-Click Menus ..............................................................................................................................2-17 Tree View Tabs: Physical, Logical, Circuits........................................................................................2-19 Physical Viewer .............................................................................................................................2-20 Logical Tree Viewer.......................................................................................................................2-24 Circuits Tree Viewer ......................................................................................................................2-25 Map Viewer..........................................................................................................................................2-26 Physical Map View .........................................................................................................................2-26 Flat Map View ................................................................................................................................2-27 Map Tools ......................................................................................................................................2-28 Map Backgrounds .........................................................................................................................2-30 Detailed Device Views .........................................................................................................................2-32 Submaps........................................................................................................................................2-32 Equipment Views ...........................................................................................................................2-33 Interface Views ..............................................................................................................................2-39 Event Browser.....................................................................................................................................2-40 The Task Manager Screen ..................................................................................................................2-42 Using Search to Search All ProVision Data .......................................................................................2-43 Searching the Tree Viewers................................................................................................................2-47 614-330055-001 February 2010 1
Icons Information and Usage .............................................................................................................2-48 Viewing Radio Icon Anatomy.........................................................................................................2-49 Event Severity Color Coding .........................................................................................................2-50 Device States.................................................................................................................................2-50 Radio Tasks ...................................................................................................................................2-52 Integrating Windows Applications with ProVision.............................................................................2-53
CHAPTER 3, DEPLOYING AND MANAGING DEVICES

About Deploying and Managing Devices..............................................................................................3-1 The Process for Deploying and Managing Devices .......................................................................3-3 Device Deployment By Type............................................................................................................3-4 Deploying Devices.................................................................................................................................3-5 Adding, Editing, and Deleting Device Containers ..........................................................................3-5 Adding a Container ....................................................................................................................3-6 Renaming a Container...............................................................................................................3-7 Deleting a Container..................................................................................................................3-8 Standard SNMP Device Deployment..............................................................................................3-9 Eclipse Devices and Nodes Deployment......................................................................................3-13 TRuepoint Device Deployment......................................................................................................3-15 TRuepoint 6500 Device Deployment.............................................................................................3-20 Constellation Device Deployment ................................................................................................3-22 CAU (Control Alarm Unit) Deployment ........................................................................................3-24 Generic Device Deployment..........................................................................................................3-25 WiMAX Device Deployment ...........................................................................................................3-28 EfficientSite Deployment ..............................................................................................................3-30 TNet Device Deployment ..............................................................................................................3-31 DXR 200 and DXR SMA Device Deployment.................................................................................3-36 Network Auto-Discovery for Devices ...........................................................................................3-38 Troubleshooting Device Deployment ...........................................................................................3-42 Changing a Devices Container ....................................................................................................3-42 Moving Containers and Devices in the Map Viewer .....................................................................3-43 Renaming a Device .......................................................................................................................3-44 Deleting a Device ..........................................................................................................................3-45 Managing Devices...............................................................................................................................3-46 Managing a Device ........................................................................................................................3-47 Verifying ProVision is Receiving Device Events............................................................................3-48 Unmanaging a Device ...................................................................................................................3-50 Manually Discovering TRuepoint 6500 Configuration..................................................................3-51 Manually Discovering DXR 700 Radios.........................................................................................3-52 Managing SMA and DXR Devices .................................................................................................3-52 RF Linking Procedures .................................................................................................................3-54 Creating an RF Link from the Tree Viewer .............................................................................3-54 Creating an RF Link from the Find Function ..........................................................................3-56 Creating an Eclipse RF Link....................................................................................................3-57 Verifying an Eclipse or TRuepoint RF Link .............................................................................3-58 Deleting an RF Link .................................................................................................................3-59 Miscellaneous Device Procedures .....................................................................................................3-61 Viewing Configuration for Devices................................................................................................3-61 Configuration Profiles for Bulk Configuration.............................................................................3-68 Create and Execute a New Configuration Profile ...................................................................3-68
Aviat Networks
Configuration Profile Settings for Bulk Configuration ...........................................................3-71 Delete a Configuration Profile .................................................................................................3-75 Viewing/Changing Network IP Addresses....................................................................................3-76 Viewing/Changing TNet Proxy Configurations .............................................................................3-77 Using the TNet Proxy Viewer ........................................................................................................3-80 Circuit Management ...........................................................................................................................3-81 About Circuits and Circuit Tracing ...............................................................................................3-81 Collecting Circuit Information ......................................................................................................3-82 Running the Circuit Trace.............................................................................................................3-82 Viewing and Managing Circuits ....................................................................................................3-84 Circuits Tab ..............................................................................................................................3-84 Filter and Select Circuits .........................................................................................................3-86 View a Single Circuit ................................................................................................................3-87 View Intersecting Circuits........................................................................................................3-88 View Ring Circuits ....................................................................................................................3-89 Find and Resolve Conflicting Circuits .....................................................................................3-90 Event Browser for a Circuit .....................................................................................................3-90 Circuit Diagnostics...................................................................................................................3-91 Validate a Circuit ......................................................................................................................3-91 Delete a Circuit ........................................................................................................................3-92 Loading/Activating New Software and Licenses ...............................................................................3-93 About Loading Device Software Via ProVision .............................................................................3-93 Eclipse Software Loading Examples ............................................................................................3-95 Stage 1: Software Load Procedure...............................................................................................3-96 Stage 2: Software Activation Procedure.....................................................................................3-102 StarMAX Software Activation Procedure...............................................................................3-108 Eclipse Node Licenses ................................................................................................................3-110 Eclipse and StarMAX Configuration Backup Export ..................................................................3-113
CHAPTER 4, MANAGING EVENTS

Event Management Processes .......................................................................................................4-2 Managing Event Processes in ProVision...................................................................................4-2 Suggested Steps for Managing Events .....................................................................................4-2 Event Management Interdependencies ....................................................................................4-3 Setting Up Scoreboard Groups ..................................................................................................4-3 Customizing Event Browsers ....................................................................................................4-4 Event Management Procedures ...........................................................................................................4-5 Network Events ...............................................................................................................................4-5 Network Event States ................................................................................................................4-5 Viewing Network Events ............................................................................................................4-6 Viewing an Events Properties ...................................................................................................4-7 Acknowledging a Network Event...............................................................................................4-9 Unacknowledging a Network Event ........................................................................................4-11 Managing Event Notification Pop-Ups and Audio Alarms .....................................................4-12 Manually Clearing a Network Event........................................................................................4-13 Manually Resynchronize Alarms.............................................................................................4-14 Configure TRuepoint 6400 Alarm Resynchronization ............................................................4-15 Customizing Event Names or Severity Levels ........................................................................4-17 Sleep Status for a Device.........................................................................................................4-18 Event Browsers .............................................................................................................................4-20
614-330055-001 February 2010
Saving an Event Browser View ................................................................................................4-22 Viewing a Saved Event Browser ..............................................................................................4-23 Customizing an Event Browser ...............................................................................................4-23 Changing Event Browser Options ...........................................................................................4-26 Deleting an Event Browser......................................................................................................4-30 Saving Event Browser Contents..............................................................................................4-31 Printing Event Browser Contents ...........................................................................................4-32 Event Log Pre-Filtering ................................................................................................................4-33 Viewing Event Log Pre-Filtering .............................................................................................4-35 Adding An Event Log Pre-Filter at the Root Level .................................................................4-36 Adding an Event Pre-filter at an Object Level ........................................................................4-39 Adding an Event Pre-Filter Via an Event Browser..................................................................4-40 Modifying An Event Log Pre-Filter ..........................................................................................4-41 Deleting An Event Log Pre-Filter ............................................................................................4-43 Security Log...................................................................................................................................4-45 Event Notification ..........................................................................................................................4-47 Set the Server Notification Preferences .................................................................................4-47 Add or Edit Event Notification Rules.......................................................................................4-49 Delete an Event Notification Rule ...........................................................................................4-52 Configuring the Notification Rule ...........................................................................................4-53 Set Up an Email Event Notification .........................................................................................4-55 Set Up a Pop-Up Message Notification .................................................................................4-57 Set Up an Audio Alarm Notification ........................................................................................4-60 Set Up Script Execution on Event Notification........................................................................4-62 Logical Containers ........................................................................................................................4-65 Adding a Device to a Logical Container ..................................................................................4-66 Removing a Device from a Logical Container ........................................................................4-67 Renaming a Logical Container................................................................................................4-68 Deleting a Logical Container...................................................................................................4-68 Logical Links .................................................................................................................................4-69 Adding a Logical Link ..............................................................................................................4-70 Renaming a Logical Link.........................................................................................................4-70 Deleting a Logical Link............................................................................................................4-71 Scoreboard Group Scenarios .............................................................................................................4-72 About Scoreboard Group Scenarios.............................................................................................4-72 Viewing a Scoreboard Group ...................................................................................................4-73 Creating a Scoreboard Group..................................................................................................4-74 Editing a Scoreboard Group ....................................................................................................4-75 Deleting a Scoreboard Group ..................................................................................................4-75 Adding a Scoreboard................................................................................................................4-76 Editing a Scoreboard ...............................................................................................................4-79 Deleting a Scoreboard .............................................................................................................4-80 Opening an Event Browser from a Scoreboard ......................................................................4-80
CHAPTER 5, SYSTEM DIAGNOSTICS AND REPORTS

Using System Diagnostics....................................................................................................................5-1 About ProVision and Craft Tools ..........................................................................................................5-3 Diagnostic and Performance Trends Analysis Procedures.................................................................5-4 Circuit Diagnostics Feature ............................................................................................................5-4 Circuit Trace for Circuit Diagnostics .........................................................................................5-5
Aviat Networks
Circuit Diagnostic Window.........................................................................................................5-5 Setting Up a Circuit Diagnostic Test..........................................................................................5-8 Circuit Diagnostic Options .......................................................................................................5-10 Data Collection ..............................................................................................................................5-11 Daily Performance Data Collection .........................................................................................5-13 Enabling 15-minute Performance Data Collection ................................................................5-14 Changing Device Data Collection Status ................................................................................5-16 Ethernet Performance Data Collection........................................................................................5-17 Enabling 15-Minute Ethernet Data Collection........................................................................5-17 Viewing Ethernet Performance ...............................................................................................5-18 Ethernet Bandwidth Utilization ...............................................................................................5-25 Performance Features..................................................................................................................5-30 Performance History................................................................................................................5-30 Performance Trends ................................................................................................................5-36 Performance Thresholds.........................................................................................................5-40 WiMAX WSN ASN-GW Controller and Base Station Management .............................................5-43 WiMAX Subscriber Station Connectivity .......................................................................................5-45 Craft Tools and Diagnostic Controls ..................................................................................................5-47 Launching a Craft Tool..................................................................................................................5-49 LE3000 and LE3200 Craft Tool Installation ..................................................................................5-50 WMT Craft Tool .............................................................................................................................5-51 TNet Web Craft Tool and Diagnostics ..........................................................................................5-54 TNet Diagnostics......................................................................................................................5-58 TNet Diagnostics - Protection Tab ..........................................................................................5-59 TNet Diagnostics - G.821 Performance Tab ...........................................................................5-61 TNet Diagnostics - CB 149 Performance Tab.........................................................................5-63 TNet Diagnostics - RSSI Tab ...................................................................................................5-65 XP4 Craft Tool and Diagnostics ....................................................................................................5-66 Activating and Deactivating an XP4 Tributary Loopback ........................................................5-68 Activating and Deactivating an XP4 Local Loopback..............................................................5-72 Viewing/Changing XP4 Protection Settings ............................................................................5-74 Resetting an XP4 Radio Device................................................................................................5-77 Diagnostic Controls for Selected Devices ....................................................................................5-78 Constellation Diagnostic Controls ..........................................................................................5-78 CAU Diagnostic Controls .........................................................................................................5-83 DART Diagnostics Controls .....................................................................................................5-84 DVA Diagnostic Controls..........................................................................................................5-87 Diagnostic Controls ................................................................................................................5-88 EfficientSite System View ...................................................................................................................5-90 Device and Network Reports..............................................................................................................5-95 Inventory Reports ..........................................................................................................................5-95 View the Inventory Reports......................................................................................................5-96 Save an Inventory Report for a Single Device .........................................................................5-98 Save an Inventory Report for Multiple Devices .....................................................................5-100 Eclipse Fault Report....................................................................................................................5-101 Eclipse Capacity Report ..............................................................................................................5-103 View / Save / Delete Server Reports......................................................................................5-106 Network Health Reports .............................................................................................................5-108 Run and View Network Health Reports ................................................................................5-109
614-330055-001 February 2010
INDEX
Aviat Networks
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 Aviat Networks devices Configuring and managing third party devices Generating supporting reports and graphs This documentation is for all ProVision users, including:
Role NOC Operators Role Description Monitor the radio network for errors and performance. Follow predefined procedures when faults are detected. May have little or no radio expertise. Configure the radio settings and performs software and configuration changes. Radio domain experts. Diagnose and isolate faults in the network down to the unit/ event level. Issue trouble tickets to field engineers where necessary.
NOC Engineers NOC Fault Finders
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 February 2010
-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 Aviat 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 Aviat Networks with the information Aviat 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
-2
Aviat Networks
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 February 2010
-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.
-4
Aviat Networks
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
614-330055-001 February 2010
1-1
Next Topic:
How ProVision Works on page 1-2
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
Aviat 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.
614-330055-001 February 2010
1-3
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. 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.
1-4
Aviat Networks
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-9 Right-Click Menus on page 2-17 Tree View Tabs: Physical, Logical, Circuits on page 2-19 Map Viewer on page 2-26 Detailed Device Views on page 2-32 Event Browser on page 2-40 The Task Manager Screen on page 2-42 Using Search to Search All ProVision Data on page 2-43 Searching the Tree Viewers on page 2-47 Icons Information and Usage on page 2-48 Integrating Windows Applications with ProVision on page 2-53
This section assumes that ProVision has been installed, and the devices are deployed and being managed from ProVision.
614-330055-001 February 2010
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-4 Changing Your Password on page 2-4 Entering Your Contact Details on page 2-5 Viewing Your ProVision License Details on page 2-6 Viewing Customer Support Contact Details on page 2-7 Viewing ProVisions Version Number on page 2-7 Using the Online Help on page 2-8
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: 2-2 Aviat Networks
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.
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-4 Changing Your Password on page 2-4
614-330055-001 February 2010
2-3
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
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
2-4
Aviat Networks
displays for your user name.
2. Select Change Password. The Change Password dialog box displays.
3. In the New Password field, type your new password. 4. Re-type your new password in the Confirm New Password field. Select OK. 5. To accept your password changes on the Change User Details window, select OK. 6. Use your new password the next time you log in to ProVision.
Related Topics: Starting a User Session on page 2-2 Entering Your Contact Details on page 2-5
Entering Your Contact Details

Introduction
ProVision provides a location to store your email and contact details. You can enter new contact details and change existing details, such as an address and phone number.
Procedure
To change your email and contact details:
614-330055-001 February 2010
2-5
1.
Select Administration > Change User Details. The Change User Details window, with your user name, displays.
2. In the Email Address field, enter your email address. 3. Select in the Contact Details frame and type in your details. 4. To accept your changes and close the window, select OK. Related Topic: Changing Your Password on page 2-4
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 on page 2-7 2-6 Aviat Networks
Viewing ProVisions Version Number on page 2-7
Viewing Customer Support Contact Details

Introduction
If you need to contact Aviat Networks AviatCustomer Support, the contact information is available from the ProVision Help menu.
Procedure
To see the contact information for Aviat Networks Customer Support: 1. Select Help > Customer Support. The Customer Support Information window displays. 2. To view the contact details of your regions Aviat Networks Customer Support center, select the appropriate tab. 3. To close the window, select OK.
Related Topics: Viewing Your ProVision License Details on page 2-6 Viewing ProVisions Version Number on page 2-7
Viewing ProVisions 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. 2. To close the window, select OK.
Related Topics: Viewing Your ProVision License Details on page 2-6 Viewing Customer Support Contact Details on page 2-7
614-330055-001 February 2010
2-7
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 Aviat Technical Support Information The online help displays using the default Web browser on the PC. Each topic in the online help has its location listed at the top of the page. This helps you to identify related topic areas. 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: Starting a User Session on page 2-2
2-8
Aviat Networks
The ProVision User Interface on page 2-9
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-1. Main User Interface
The functions of the main user interface are described in the following sections: Customizing the User Interface on page 2-10 Menu Bar on page 2-11 Main Tool Bar on page 2-16 Tree View Tabs: Physical, Logical, Circuits on page 2-19 Map Viewer on page 2-26 Event Browser on page 2-40 Using Search to Search All ProVision Data on page 2-43
614-330055-001 February 2010
2-9
Searching the Tree Viewers on page 2-47
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 Main User Interface To minimize, maximize, or close the interface window To resize the interface window Physical Viewer To resize the Physical Viewer To hide the Physical Viewer To show the Physical Viewer Map Viewer To resize the Map Viewer panel To hide the Map Viewer To show the Map Viewer To add a background Click and drag the vertical split bar. Select the X on the Map toolbar. In the Window menu, select Map. Select Map Properties on the Map toolbar to add a JPG background for the map. You can add different JPG backgrounds for Physical and Flat Map views of the network. Click and drag the vertical split bar. Select the X the Physical Viewer toolbar. In the Window menu, select Physical. Select the required button from the buttons located in the upper right corner. Click and drag any of the outside edges of the interface window. Action
Event Browser To resize the Event Browser To hide the Event Browser To show the Event Browser To change displayed Event values Click and drag the horizontal split bar. Select Hide. In the Window menu, select Events. In the Event Browser toolbar, select Browser Options to edit browser options.
Related Topics: Menu Bar on page 2-11 Main Tool Bar on page 2-16
2-10
Aviat Networks
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-17.
Table 2-2. Menu Bar Items And Pull-Down Options Menu Item Menu Bar Function
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 February 2010
2-11
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-4.
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-43.
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-47.
Fault >
Maintenance Scheduling View the Maintenance Schedule. 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.
2-12
Aviat Networks
Menu Item
Function 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-72.
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-47. 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-47. 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-47. Client Notification Dialogue View the Event Notification dialogue. Configuration > IP Address Enables you to view and change IP information assigned to devices on the network. 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-110. Configuration Profiles Enables you to apply settings to multiple radios. For more information, see Configuration Profiles for Bulk Configuration on page 3-68.
614-330055-001 February 2010
2-13
Menu Item
Function Collection Preferences Enables you to set data collection time and frequency. Software Loading Lists the container and current software version of each Eclipse radio in the network. For more information, see
Loading/Activating New Software and Licenses on page 3-93.
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 Software and Licenses on page 3-93. 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.
2-14
Aviat Networks
Menu Item Performance
Function 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-11. Thresholds Set data collection thresholds for devices in the network. Ethernet Bandwidth View Ethernet Bandwidth use for Eclipse devices.
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-5. 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.
614-330055-001 February 2010
2-15
Menu Item
Function 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-47.
Window>
Click on an item to view or hide that window in the ProVision screen display. Physical Logical Circuits Map Events Reset Layout Renews the default layout.
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 on page 2-16 Tree View Tabs: Physical, Logical, Circuits on page 2-19
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.
2-16
Aviat Networks
Table 2-3. Tool Bar Icons Icon Tool Bar: Name Definition
Search
Enables you to rapidly find specific objects. See The ProVision User Interface on page 2-9.
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 Software and Licenses on page 3-93. Saves and retrieves reports from a single radio or from multiple radios. For more information see View / Save / Delete Server Reports on page 5-106.
Server Reports
Global Circuit Trace Event Browser
Runs a global circuit trace on all circuits in the system. See Running the Circuit Trace on page 3-82. Enables you to open a new Event Browser and select saved Event Browser views. See Event Browser on page 2-40. Enables you to add a new Scoreboard group and view saved Scoreboard groups. See Scoreboard Group Scenarios on page 4-72.
Scoreboard Groups
Related Topics: Tree View Tabs: Physical, Logical, Circuits on page 2-19 Map Viewer on page 2-26
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 the Tree Viewer, the 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. 614-330055-001 February 2010 2-17
To display a right-click menu: 1. Place the cursor over the object or event entry. 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 Tree 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 2. Right-click using the right-click button on the mouse.
Radio Right-Click Menus

Different radio types have different right-click menu options, based on the available functions for the radio. An example of an individual radio right-click menu is shown below.
2-18
Aviat Networks
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 radios 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.
You can select multiple radios/devices and right-click, and you will view a generic right-click menu. This menu includes only the functions that are shared amongst all the devices.
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.
614-330055-001 February 2010
2-19
Figure 2-2. Physical Viewer Frames
The topics covered in this section include: Physical Viewer on page 2-20 Logical Tree Viewer on page 2-24
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-3. Tree Viewer - Physical Viewer
2-20
Aviat Networks
You can reparent objects within the Physical pane. For more information see DXR 200 and DXR SMA Device Deployment on page 3-36. 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-17.
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 ProVision Manager Notes 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. The Root and ProVision Manager icons are automatically displayed in the Physical Viewer. A region is a grouping of devices and/or sites that is typically geographically based. A site is a location where a device or devices are stored. 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.
Root
Region Site Rack
614-330055-001 February 2010
2-21
The table below lists the Aviat Networks SNMP devices that can be deployed in ProVision.
Table 2-5. AviatAviat SNMP Devices Device Icon ADR 155C: Aviat ADR ADR 2500: SAGEM ADR, an add-on to the Altium. Altium, Altium MX, and Altium MX 2+0 Aurora Constellation Control Alarm Unit
, and
and and
and and
DART and DART (remote management) DVA and DVM, DVM-XT DXR 100 and DXR100 (protected) DXR 700 and DXR 700 (protected): DXR 700 radios are discovered/visible in the ProVision when the connected DXR SMA is deployed. Eclipse INU Node and Eclipse INUe Node (includes IDU 600) 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:
and
2-22
Aviat Networks
Device Icon
Eclipse IDU Terminal: the Eclipse Terminal has a fixed layout; ancillary parts are displayed as plug-ins. Eclipse Optimization Gateway LE3000, LE3200, WL1000, RW2000 and MegaStar 1+1 and M+N 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 WiMAX Juniper Routers: M7i WSG-R, M10iWSG-R
and
XP4 (remote management) 16xE1/E3/DS3 and XP4 16xE1/E3/DS3 (remote management, protected) XP4 16xE1/E3/DS3 and XP4 16xE1/E3/DS3 (protected) XP4 2/4/8x (remote management) and XP4 2/4/8x (remote management, protected) XP4 2/4/8x and XP4 2/4/8x (protected)
and and
and Table 2-6. TNet Device Icons Device Icon Classic II and LC Series and LC Series (protected) M Fiber and M Series and M Series (protected)
614-330055-001 February 2010
2-23
Device Icon and QUANTUM and QUANTUM (protected) SPECTRUM I and SPECTRUM II and SPECTRUM II (protected TNet Proxy and W Series and W Series (protected)
Table 2-7. Generic SNMP Device Icons Device Icon The Generic SNMP device icons represents SNMP enabled, non-Aviat 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-5. Related Topics: Tree View Tabs: Physical, Logical, Circuits on page 2-19 Searching the Tree Viewers on page 2-47 Logical Tree Viewer on page 2-24
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-65.
2-24
Aviat Networks
Figure 2-4. 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-81.
Figure 2-5. Physical Viewer - Circuits Tab
By default, the Circuits tab is not populated at installation. Related Topics: Physical Viewer on page 2-20 Map Viewer on page 2-26 Logical Tree Viewer on page 2-24 614-330055-001 February 2010 2-25
Map Viewer
The Map Viewer provides two different views of the network: Physical Map View on page 2-26 Flat Map View on page 2-27 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-28 Map Backgrounds on page 2-30 Submaps on page 2-32
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:
2-26
Aviat Networks
Figure 2-6. 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-28.
Related Topics: Flat Map View on page 2-27 Submaps on page 2-32
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.
614-330055-001 February 2010
2-27
Figure 2-7. Flat Map View
Related Topics: Map Tools on page 2-28 Submaps on page 2-32
Map Tools
These are the functions in the ProVision Map toolbar.
Map Tool Physical Map Flat Map Navigate Up, Back, or Forwards Zoom to Fit Screen Icon Use Click this to view the Physical Map view. Click this to view the Flat Map view. Use these arrows to navigate to different maps in the network.
The Zoom to Fit Screen tool enables you to zoom in and 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.
2-28
Aviat Networks
Map Tool Enable/ Disable Map Zooming
Icon
Use The map zoom tool enables you to zoom in/out of the Map Viewer. The map zoom tool functions are: 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.
Locked and Unlocked
By default the map padlock is locked. This means that 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-43.
Object Filter
The map object filter tool enables you to search for and select specific map items. The map properties tool enables you to add and change map backgrounds. For more information, see Map Backgrounds on page 2-30.
Properties
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.
614-330055-001 February 2010
2-29
Map Tool Help
Icon
Use The map help, displayed at the top of the screen, 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, click 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-30 Submaps on page 2-32
Map Backgrounds
Introduction
You can add a background image for any object located in the Physical Map or Flat Map 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. You can assign different images to the Physical and Flat Map views. 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)
2-30
Aviat Networks
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 view type to which you want to add a map background, the Physical or Flat map view. on the Map Viewer. The Map Properties window displays.
2. Select the Map Properties icon
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 view type from which you want to remove a map background. 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.
2. Select the Map Properties icon
Related Topics: Physical Map View on page 2-26 Submaps on page 2-32
614-330055-001 February 2010
2-31
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-32. Equipment View - A real-time view of a device, based on the physical configuration of the device. See Equipment Views on page 2-33. Interface View - A view displaying a devices IF interfaces. See Interface Views on page 2-39.
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 Eclipse Optimization Gateway element in either the Physical Viewer or Map Viewer.
Figure 2-8. Eclipse Submap View
2-32
Aviat Networks
Figure 2-9. Eclipse Optimization Gateway 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 devices 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-33. Related Topics: Physical Map View on page 2-26 Detailed Device Views on page 2-32 Equipment Views on page 2-33 Interface Views on page 2-39
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.
614-330055-001 February 2010
2-33
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. 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. 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.
2-34
Aviat Networks
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.
614-330055-001 February 2010
2-35
The radio below is a Constellation repeater, set up for two links.
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:
2-36
Aviat Networks
TRuepoint 6400
TRuepoint 6500
614-330055-001 February 2010
2-37
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
2-38
Aviat Networks
SmartChorus WiMax ASN-GW Base Station
Related Topics:
Detailed Device Views on page 2-32 Equipment Views on page 2-33 Interface Views on page 2-39
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/3200 WL1000/RW2000 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-10. Interface View
614-330055-001 February 2010
2-39
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-32 Submaps on page 2-32 Equipment Views on page 2-33
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.
2-40
Aviat Networks
Figure 2-11. Main Event Browser
# 1 2 3 4 5 6 7
Value Severity Status Acknowledged/Unacknowledged Note Status Bar Notification Dialog Boxes Event Severity Counts
Status Bar
The status bar provides the following information: The user currently logged on. The ProVision server to which you are connected. The number of active notification dialog boxes. For more information see Set the Server Notification Preferences on page 4-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.
614-330055-001 February 2010
2-41
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-33. 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-26. 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-43
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.
2-42
Aviat Networks
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.
Using Search to Search All ProVision Data

Introduction
ProVisions 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 Search > 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
614-330055-001 February 2010
2-43
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.
2-44
Aviat Networks
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 February 2010
2-45
.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: Starting a User Session on page 2-2 Searching the Tree Viewers on page 2-47
Next Topic: Searching the Tree Viewers on page 2-47
2-46
Aviat Networks
Searching the Tree Viewers

Introduction
ProVisions 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 the word North in the item name, there are four ways to enter that I for a wildcard search: North* = An asterisk after the value; finds all items that begin with this value. *North = An asterisk in front of the value; finds all items that end with this value. *North* = An asterisk before and after the value; finds all items that contain this value. N*th = An asterisk within a value; finds all items that begin and end with the noted values.
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.
614-330055-001 February 2010
2-47
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-43 Physical Viewer on page 2-20
Next Topic: Icons Information and Usage on page 2-48
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 objects color reflects the most severe alarm on any of its children. This section covers the following topics: Viewing Radio Icon Anatomy on page 2-49 Event Severity Color Coding on page 2-50 Device States on page 2-50 Radio Tasks on page 2-52
2-48
Aviat Networks
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 Viewers 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 2 3 4 5
This item is Closed in the tree structure; sub-radios and devices are not displaying. If an event is present, the color here indicates the event severity. Mouse over this to view the event type. Radio icon. Task. Radio name.
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 radios name, state, and event information.
Value Map Viewer - Labelled Radio Icon
1 2 3
If an event is present, the color here indicates the event severity. Mouse over this to view the event type. Radio icon. Radio state and task.
614-330055-001 February 2010
2-49
# 4
Value 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-50 Event Severity Colors - Indicates the most severe active event in effect for the device.
Related Topics: Event Severity Color Coding on page 2-50 Device States on page 2-50
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 Critical Major Minor Warning Normal Informational Color Code Red Orange Yellow Cyan Green White
Related Topics: Device States on page 2-50 Radio Tasks on page 2-52
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
2-50
Aviat Networks
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 State Icon Other Indicators
Radio With Pop-up Text
Unmanaged Managed
Event severity is blue. The pop-up text displays State: Unmanaged. 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-47.
Connecting
ProVision is attempting to connect to the device across the network using the devices IP address. There has been no communication from the device since being managed. The pop-up text displays State: Connecting. 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-18.
Asleep
Errored
The managed radio is not responding to polling from ProVision. The pop-up text displays State: Errored.
614-330055-001 February 2010
2-51
Device State + icon
Icon Other Indicators 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: Viewing Radio Icon Anatomy on page 2-49 Radio Tasks on page 2-52
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 Pre-filtered 15-minute data collection Performance Thresholds Icon For more information about pre-filtering events, see Event Log Pre-Filtering on page 4-33. ProVision uses the data from the radio to create performance trends graphs. See Data Collection on page 5-11 for more information. Performance thresholds feature allows you to associate an alarm or group of alarms with unexpected performance results. See Performance Thresholds on page 5-40 for more information. 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.
+ icon
Related Topics: Viewing Radio Icon Anatomy on page 2-49 Device States on page 2-50
2-52
Aviat Networks
Integrating Windows Applications with ProVision

Introduction
You can integrate Windows applications with ProVision, to conveniently launch these applications directly from ProVision. There are two levels of application integration: At the device level, to display in a devices right-click menu. This links the application to that particular device type, and it displays in the right-click menu for all instances of that device type. Use this for applications that are very device-specific, such as a craft tool for a Generic Device. At the main Root level, to display in the main ProVision toolbar. This does not link the application to any device type. Use this option for applications that are based on general data, such as PCR (Paperless Chart Recorder).
For each application to be used, the application files need to be installed on each individual ProVision client. Note the system location where the installation files are saved, for use in the launch configuration procedure.
Procedure
1. On the ProVision Client, install the Generic Device craft tool or tools. 2. Log into ProVision at the NOC engineer or system administrator level, i.e., using the NOC engineer or administrator user name and password. 3. Open the Edit Applications screen, based on the type of application integration you need: To set up the application at the Root level, in the main ProVision toolbar, click on the Applications icon in the upper right of the main screen: . To set up a windows application at the Device level, in the Tree Viewer, locate a device that you want to connect with craft tools. Right-click on its icon. In the right-click menu, Applications > Edit Applications displays. Click on Edit
Applications.
The Edit Applications screen displays. 4. To add a new Application, click Add. A new line appears in the screen. Double-click in the fields to enter the following values: Name - Enter the name of the craft tool application. Executable Path - Navigate to the location of the device craft tool executable file (.exe). Select the .exe file. Parameters - Only use this value if you are linking the application with a specific device type, and only if you need to customize the .exe file with command line parameters. See the Installation and Administration Guide, Generic Devices, for more details.
614-330055-001 February 2010
2-53
5. To enter additional Applications, click Add again. You can save multiple Applications for each device, as shown. 6. When you are done, click OK. 7. The applications are now directly integrated with ProVision. Applications integrated at Root level now display in the upper right of the main screen toolbar. Click on the application icons to open and use the applications. The right-click menu for the device now displays Applications >(Application Names), and you can open the applications from there. 8. If you need to update the application, open Applications > Edit Applications again. This re-opens the Edit Applications screen. Make changes to the application link from this screen.
2-54
Aviat Networks
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 Aviat Networks radio, a DXR SMA or a non-Aviat 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. This section covers the following topics: About Deploying and Managing Devices on page 3-1 Deploying Devices on page 3-5 Managing Devices on page 3-46 Miscellaneous Device Procedures on page 3-61 Circuit Management on page 3-81 Loading/Activating New Software and Licenses on page 3-93
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.
614-330055-001 February 2010
3-1
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 Aviat 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. 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 2. Is this installation an upgrade?
3-2
Aviat Networks
performance trend analysis of G.826 and RSL/RSSI. Next Topic: The Process for Deploying and Managing Devices
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 Aviat 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. 614-330055-001 February 2010 3-3
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 Constellation DXR 200 DXR SMA Eclipse EfficientSite Generic TNet TRuepoint 4000 TRuepoint 4040 TRuepoint 5000 TRuepoint 6400 TRuepoint 6500 WiMAX All Other Devices
CAU (Control Alarm Unit) Deployment on page 3-24 Constellation Device Deployment on page 3-22 DXR 200 and DXR SMA Device Deployment on page 3-36 DXR 200 and DXR SMA Device Deployment on page 3-36 Eclipse Devices and Nodes Deployment on page 3-13 EfficientSite Deployment on page 3-30 Generic Device Deployment on page 3-25 TNet Device Deployment on page 3-31 TRuepoint Device Deployment on page 3-15 TRuepoint Device Deployment on page 3-15 TRuepoint Device Deployment on page 3-15 TRuepoint Device Deployment on page 3-15 TRuepoint 6500 Device Deployment on page 3-20 WiMAX Device Deployment on page 3-28 Standard SNMP Device Deployment on page 3-9
Includes ADR 155c, ADR 2500, Altium, Aurora, DART, DVA, DVM, DVM-XT, DXR 100, LE3000, LE 3200, all MegaStar, Eclipse Optimization Gateway, all MicroStar, SAGEM-LINK, SPECTRUM II SNMP, Velox, Radwin WL1000, RW2000, XP4
Next Topic: Deploying Devices
3-4
Aviat Networks
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-5 Standard SNMP Device Deployment on page 3-9 includes legacy, MicroStar, MegaStar, DVA Eclipse Devices and Nodes Deployment on page 3-13 TRuepoint Device Deployment on page 3-15 TRuepoint 6500 Device Deployment on page 3-20 Constellation Device Deployment on page 3-22 CAU (Control Alarm Unit) Deployment on page 3-24 Generic Device Deployment on page 3-25 WiMAX Device Deployment on page 3-28 TNet Device Deployment on page 3-31 DXR 200 and DXR SMA Device Deployment on page 3-36 Troubleshooting Device Deployment on page 3-42 Changing a Devices Container on page 3-42 Moving Containers and Devices in the Map Viewer on page 3-43 Renaming a Device on page 3-44 Deleting a Device on page 3-45
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-6
614-330055-001 February 2010
3-5
Renaming a Container on page 3-7 Deleting a Container on page 3-8
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. The Deployment window displays.
2. In the right-click menu, select Deploy Object.
Click on Containers. The Containers Family window displays.
3. Select the required Container icon, for example, Site. The Deploying <container>
3-6
Aviat Networks
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 Viewers 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 on page 3-7 Deleting a Container on page 3-8
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.
614-330055-001 February 2010
3-7
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 containers name. 3. To save the changes, select OK.
Related Topics: Adding a Container on page 3-6 Deleting a Container on page 3-8
Deleting a Container
You can delete a container from the Tree Viewer or the Map Viewers 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.
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.
3-8
Aviat Networks
Related Topics: Adding a Container on page 3-6 Renaming a Container on page 3-7
Standard SNMP Device Deployment

Introduction
A Aviat 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-4.
Prerequisites
MicroStar - For each MicroStar device you are deploying in ProVision, you must find that device in WebCIT and set up ProVisions 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 ProVisions 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 devices 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 February 2010
3-9
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. 7. The Deploying <device name> window displays. Enter the values for the new device, as described for specific device types listed in the table below. 8. Select Deploy. The Deploying <device name> results window displays. 9. To close the Deploying <device name> window, select Close.
3-10
Aviat Networks
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 100Eclipse Optimization Gateway. Eclipse Optimization Gateway, LE3000, LE 3200, Radwin WL1000 and RW2000
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 radios 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, DVM (repeater) 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 radios IP address. 3. Enter the B radios IP address. 4. 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. 5. To have ProVision start managing the radio, select the Manage checkbox. Multiplexes: ADR 155C, ADR 2500
1. In the Name field, type a descriptive name for the 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. The Read and Write Community strings must match the strings entered into the radio. 4. To have ProVision start managing this radio, select the Manage checkbox.
614-330055-001 February 2010
3-11
Device Deployment Window
Steps MicroStar I, II, III
1. In the Name field, type a descriptive name for the 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. The Read and Write Community strings must match the strings entered into the radio. 4. To have ProVision start managing this radio, select the Manage checkbox.
MegaStar M:N
1. In the Name field, type a descriptive name for the Megastar device. It is labeled with this name in the User Interface. 2. 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. 3. To have ProVision start managing this radio, select the Manage checkbox.
MegaStar 1+1
1. In the Name field, type a descriptive name for the Megastar 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. The Read and Write Community strings must match the strings entered into the radio. 4. To have ProVision start managing this radio, select the Manage checkbox.
3-12
Aviat Networks
Eclipse Devices and Nodes Deployment

Introduction
Deploying Eclipse devices and nodes is simple, and similar to Standard SNMP Device Deployment on page 3-9. 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, or an Eclipse IDU 600, 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 Devices on page 3-38.
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 February 2010
3-13
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. 2. In the Name field, type a descriptive name for the radio.The radio is labeled with this name in the User Interface. 3. Enter the radios IP address. 4. To have ProVision start managing the radio, select the Manage checkbox. 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
1. Ensure the correct parent displays; the device is placed under the listed parent. 2. In the Name field, type a descriptive name for the radio.The radio is labeled with this name in the User Interface.
Note: In the Name field, note whether the radio is an IDU ES or an IDU GE.
3. Enter the A radios IP address. 4. Enter the B radios IP address. 5. To have ProVision start managing the radio, select the Manage checkbox.
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.
3-14
Aviat Networks
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:
Standard SNMP Device Deployment on page 3-9 Generic Device Deployment on page 3-25 Managing a Device on page 3-47 Verifying ProVision is Receiving Device Events on page 3-48 Network Auto-Discovery for Devices on page 3-38
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-20. Read Standard SNMP Device Deployment on page 3-9and Configuration Profile Settings for Bulk Configuration on page 3-71 for full details.
614-330055-001 February 2010
3-15
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 Aviat 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 ProVisions 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 Servers 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. 6. In the Tree Viewer, right-click an existing container and select Deploy Object. The Deployment window displays. Select the TRuepoint icon. The TRuepoint device options are displayed.
3-16
Aviat Networks
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 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. To have ProVision start managing this radio, select the Manage checkbox. 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 match the strings entered into the radio.
614-330055-001 February 2010
3-17
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 devices data. Select a Type, and enter a Password and a Confirmation for the password. Privacy: This selects the encryption algorithm used for this devices data. Select a Type, enter a Password and a Confirmation for the password.
Note: The Authentication and Privacy types are determined by your organizations network policy. An Authentication of MD5 and a Privacy of AES128 is a common strong security combination. To change or view SNMPv3 credentials on a TRuepoint radio, see the TRuepoint 5000/4040 Operators 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.
Note:
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
3-18
Aviat Networks
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-71. 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-15.
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-71 TRuepoint 6500 Device Deployment on page 3-20 Configure TRuepoint 6400 Alarm Resynchronization on page 4-15 614-330055-001 February 2010 3-19
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-52. There are two types of TRuepoint 6500 devices:
Type Standard Definition Standard TRuepoint 6500 radio. Tree Viewer Display
Double Terminal
This type includes 2 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-9.
Prerequisite
For each TRuepoint device you are deploying in ProVision, you must find that device in WebCIT and set up ProVisions 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.
3-20
Aviat Networks
Procedure
1. Identify the IP addresses for connecting TRuepoint devices to ProVision via a ProVision trap and a ProVision SNMP manager.
2. In the Tree Viewer, right-click an existing container and select Deploy Object. The 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
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 TRuepoint radio is now deployed. TRuepoint 6500 Double Terminal
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. 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. For each of the two terminals, enter the IP addresses. To have ProVision start managing this radio, select the Manage checkbox. 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 614-330055-001 February 2010 3-21
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: Standard SNMP Device Deployment on page 3-9 TRuepoint Device Deployment on page 3-15 Manually Discovering TRuepoint 6500 Configuration on page 3-51
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 Terminals Definition 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. Tree Viewer Display
The procedure below is an overview of the Constellation deployment process. Read Standard SNMP Device Deployment on page 3-9 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
3-22
Aviat Networks
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 ProVisions 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. 2. In the Tree Viewer, right-click an existing container and select Deploy Object. The Deployment window displays. Select the Other Microwave icon. The Constellation 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. 3. Enter the IP address. 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/
614-330055-001 February 2010
3-23
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: Standard SNMP Device Deployment on page 3-9 CAU (Control Alarm Unit) Deployment on page 3-24 Managing a Device on page 3-47 Verifying ProVision is Receiving Device Events on page 3-48
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 Aviat 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.
3-24
Aviat Networks
Prerequisite
For each CAU you are deploying in ProVision, you must find that device in FarScan and set up ProVisions 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. 2. In the Tree Viewer, right-click an existing container and select Deploy Object. The 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 name in the User Interface. 3. Enter the IP address. 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. Related Topics: Configuration Profiles for Bulk Configuration on page 3-68
Generic Device Deployment

Generic devices can be SNMP or IP based, non-Aviat 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
614-330055-001 February 2010
3-25
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.
3-26
Aviat Networks
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 placed under the parent listed. Press the Tab key and type in the devices 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, select the Manage checkbox. 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 match the strings entered into the radio. 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: Managing a Device on page 3-47
614-330055-001 February 2010
3-27
WiMAX Device Deployment

Introduction
ProVision supports the following WiMAX devices:
Type StarMAX 6100 BS StarMAX 6400 BS blade WiChorus SmartCore ASN-GW WSC ASN-GW Controller WiMAX Subscriber Juniper M7i WSG-R Juniper M10i WSG-R Definition StarMAX 6100 WiMAX base station. StarMAX 6400 WiMAX base station blade; each 6400 contains up to 4 blades, and each blade has its own IP address and is managed as a separate device. WiChorus SmartCore ASN-GW and Home Agent device. WSC ASN-GW Controller, linking multiple base stations. WiMAX Subscriber Stations. Only VIP subscriber stations should be deployed as objects. WiMAX Router. WiMAX Router.
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.
ProVision provides extensive management for StarMAX base stations, including: Performance Data Collection and Reporting: see Ethernet Performance Data Collection on page 5-17, Viewing Ethernet Performance on page 5-18, Ethernet Bandwidth Utilization on page 5-25. Inventory Reporting: see Inventory Reports on page 5-95 Backup Restoration: see Eclipse and StarMAX Configuration Backup Export on page 3-113 Administrator-level users can auto-discover and deploy StarMAX base stations: see Network Auto-Discovery for Devices on page 3-38.
For Juniper devices, ProVision captures Juniper Networks Enterprise-Specific SNMP Traps, as defined in the JUNOS Software Network Management Configuration Guide, Chapter 11.
3-28
Aviat Networks
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-45). 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-9for full details.
Procedure
1. Identify the IP addresses for the WiMAX devices. 2. For any Subscriber stations, identify the MAC addresses. 3. In the Tree Viewer, right-click an existing container and select Deploy Object. The 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, Juniper Routers 1. Ensure the correct parent displays; the device is placed under the parent listed. 2. In the Name field, type a name for the device. It is labeled with this name in the User Interface. 3. Enter the IP address. 4. To have ProVision start managing this device, select the Manage checkbox.
614-330055-001 February 2010
3-29
WiMAX Subscriber 1. Ensure the correct parent displays; the device is placed under the parent listed. 2. In the Name field, type a name for the device. It is labeled with this name in the User Interface. 3. Enter the IP address. 4. Enter the MAC address. 5. To have ProVision start managing this device, select the Manage checkbox.
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: Managing a Device on page 3-47 Equipment Views on page 2-33 WiMAX Subscriber Station Connectivity on page 5-45 Network Auto-Discovery for Devices on page 3-38
EfficientSite Deployment
The Aviat EfficientSite is an intelligent controller based system. It reduces the energy costs associated with operating telecommunications sites. EfficientSites are supported by ProVision through a rich set of Fault, Configuration, and Performance management features. EfficientSite devices are deployed in ProVision using the following procedure:
Procedure
1. Identify the IP addresses for the EfficientSites. 2. In the Tree Viewer, right-click an existing container and select Deploy Object. The Deployment window displays. Select the Energy icon. The Energy options are displayed.
3-30
Aviat Networks
3. Select the EfficientSite Manager. Enter the values for it as follows:

Efficient Site Manager
1. Ensure the correct parent displays; the device is placed under the listed parent. 2. In the Name field, type a descriptive name for the device. It is labeled with this name in the User Interface. 3. Enter the devices 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 is deployed within ProVision, the device displays in the Tree Viewer, and can be opened and viewed. 8. For information on the EfficientSite screen, see the EfficientSite System View on page 5-90.
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.
614-330055-001 February 2010
3-31
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-77.
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
3-32
Aviat Networks
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.
2. Select the TNet icon. The TNet devices are displayed.
3. Select the required device icon. 4. The Deploying <device name> window displays. Enter the values for the new device, as described for specific device types listed in the table below. 5. Select Deploy. The Deploying <device name> results window displays. 6. To close the Deploying <device name> window, select Close.
614-330055-001 February 2010
3-33
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 Discrepancy Radio deployed in ProVision but not deployed in the Proxy. Wrong radio type in either ProVision or the Proxy. Solution See Manually Deploying a TNet Device into the Proxy on page 3-35. 1. Delete the radio from ProVision. This also deletes the radio from the Proxy. See
Deleting a Device on page 3-45
2. Deploy and manage the radio in ProVision. The radio is automatically deployed into the Proxy. Radio deployed in the Proxy but not deployed in ProVision, and the radio is not required. 1. Deploy and manage the radio in ProVision. 2. Delete the radio from ProVision. This also deletes the radio from the Proxy.
Table 3-4. Device Deployment Details for TNet Devices Device Deployment Window Steps TNet Proxy
Note: ProVision can manage up to ten TNet Proxies. Each proxy can support up to 16 radio subnets (0 to 15).
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 TNet Proxy. The TNet Proxy is labeled with this name in the User Interface. 3. Press the Tab key and type in the TNet Proxys IP address. 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. Enter the total number of Subnets for this proxy. 6. To have ProVision start managing the TNet Proxy, select the Manage checkbox.
3-34
Aviat Networks
Device Deployment Window
Steps All Other TNet Devices 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 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, select the Manage checkbox. 6. Select Next. The Proxy List displays.
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-80 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. 3-35
614-330055-001 February 2010
2. The TNet device details stored in ProVision, are written into the Proxy database.
Related Topics: Managing a Device on page 3-47 Verifying ProVision is Receiving Device Events on page 3-48 Moving Containers and Devices in the Map Viewer on page 3-43 Renaming a Device on page 3-44
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
3-36
Aviat Networks
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: 1. In the Tree Viewer, right-click an existing container and select Deploy Object. The 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.
Device Deployment Window Steps
Check the Parent field. Ensure the correct parent displays in this field. The device is placed under the parent listed. In the Name field, type a descriptive name for the radio.The radio displays with this name. Press the Tab key and type in the radios IP address. To have the SMA discover its DXR terminals, select Discover DXR Terminals. To have ProVision start managing the radio, select the Manage checkbox. Click Next. Then, on the window that displays, select Deploy. The Deploying SMA results window displays. Select Close.
614-330055-001 February 2010
3-37
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.
Device Deployment Window Steps
Ensure the correct parent displays; the device is placed under the parent listed. In the Name field, type a descriptive name for the radio.The radio is labeled with this name in the User Interface. Press the Tab key and type in the radios 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, select the Manage checkbox. 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: Changing a Devices Container on page 3-42 Standard SNMP Device Deployment on page 3-9 Manually Discovering DXR 700 Radios on page 3-52
Network Auto-Discovery for Devices

Introduction
Network Auto-Discovery is a ProVision task that polls a range of IP addresses for the following device types: Eclipse StarMAX WiMAX base station (BS) devices
3-38
Aviat Networks
Constellation TRuepoint 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 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 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, based on the device password 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
requirements.
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.
614-330055-001 February 2010
3-39
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: 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. You can import the results of the network auto-discovery as a .CSV file by clicking the Import button.
3-40
Aviat Networks
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 February 2010
3-41
Troubleshooting Device Deployment

When you deploy a device, you may receive the following error messages:
Exception IP Address Already Allocated If you attempt to assign an IP address that has already been allocated to a device the following message displays: Corrective Action Select OK. The Deploying <device name> window displays enabling you to re-enter the correct IP address.
Invalid IP Address If you enter an invalid IP address the following message displays:
Select OK and re-enter a valid IP address.
Related Topics:
About Deploying and Managing Devices on page 3-1 Deploying Devices on page 3-5 Managing a Device on page 3-47 Verifying ProVision is Receiving Device Events on page 3-48
Changing a Devices 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 devices 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-43.
3-42
Aviat Networks
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-77.
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 panes 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: Moving Containers and Devices in the Map Viewer on page 3-43 Renaming a Device on page 3-44 Deleting a Device on page 3-45
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-26.
614-330055-001 February 2010
3-43
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: Changing a Devices Container on page 3-42 Renaming a Device on page 3-44 Deleting a Device on page 3-45
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 devices right-click menu displays.
3-44
Aviat Networks
2. Select Rename on the right-click menu. The Rename Object window with the selected devices name displays.
3. Make the required changes to the devices name. 4. To save the changes, select OK.
Related Topics: Changing a Devices Container on page 3-42 Moving Containers and Devices in the Map Viewer on page 3-43 Deleting a Device on page 3-45
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-52.
614-330055-001 February 2010
3-45
WARNING: Be careful when deleting a TNet Proxy, as this also deletes all the associated child TNet radios in ProVision, and deletes the Proxys database.
Procedure
To delete a device in ProVision: 1. Right-click the devices 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: Moving Containers and Devices in the Map Viewer on page 3-43 Renaming a Device on page 3-44
Managing Devices
This section covers the following device management procedures: Managing a Device on page 3-47 Verifying ProVision is Receiving Device Events on page 3-48 Unmanaging a Device on page 3-50 Manually Discovering TRuepoint 6500 Configuration on page 3-51 Manually Discovering DXR 700 Radios on page 3-52 Managing SMA and DXR Devices on page 3-52
3-46
Aviat Networks
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 devices 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. 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 on page 3-48 Unmanaging a Device on page 3-50 614-330055-001 February 2010 3-47
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 devices IP address is correct. The devices IP address displays in pop-up text when you place the cursor over the devices 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-76.
Procedure
To verify that ProVision is receiving events from a device: 1. Right-click the managed device. The Event Browser displays. 2. From the right-click menu, select Event Browser.
3-48
Aviat Networks
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: Managing a Device on page 3-47 Unmanaging a Device on page 3-50
614-330055-001 February 2010
3-49
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 devices 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 devices 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-18.
Procedure
To un-manage a device: 1.
Managed checkbox.
Right-click the device to be un-managed. In the right-click menu, deselect the
The device is changed to an unmanaged state, and is no longer polled by ProVision.
Related Topics: Managing a Device on page 3-47 Verifying ProVision is Receiving Device Events on page 3-48
3-50
Aviat Networks
Manually Discovering TRuepoint 6500 Configuration

Introduction
In ProVision, when you manage a TRuepoint 6500, you have the option of discovering the radios 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: Managing a Device on page 3-47 TRuepoint 6500 Device Deployment on page 3-20
614-330055-001 February 2010
3-51
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 a Device on page 3-47 Managing SMA and DXR Devices on page 3-52
Managing SMA and DXR Devices

Introduction
As described in DXR 200 and DXR SMA Device Deployment on page 3-36, 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.
3-52
Aviat Networks
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. 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.
614-330055-001 February 2010
3-53
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: Managing a Device on page 3-47 DXR 200 and DXR SMA Device Deployment on page 3-36
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 Aviat 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-50. This section covers the RF linking procedures: Creating an RF Link from the Tree Viewer on page 3-54 Creating an RF Link from the Find Function on page 3-56 Deleting an RF Link on page 3-59 Verifying an Eclipse or TRuepoint RF Link on page 3-58 Deleting an RF Link on page 3-59
RF links are automatically discovered for Eclipse radios.
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.
3-54
Aviat Networks
To create an RF link from the Find screen, see Creating an RF Link from the Find Function on page 3-56.
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-58.
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 - RFLink.
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 on page 3-56 Verifying an Eclipse or TRuepoint RF Link on page 3-58 Deleting an RF Link on page 3-59
614-330055-001 February 2010
3-55
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-54.
Procedure
1. To open the Search 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 if the radios already have a link to another radio: see Verifying an Eclipse or TRuepoint RF Link on page 3-58. 3. Select the icons for the two radios that you want to link. 4. Right-click. From the right-click menu, select Create Link - RF Link. A message will display:
5. Select OK. The radios are now linked.
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, an error message displays.
Related Topics: Creating an RF Link from the Tree Viewer on page 3-54 Verifying an Eclipse or TRuepoint RF Link on page 3-58 Deleting an RF Link on page 3-59
3-56
Aviat Networks
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 Eclipse Terminal Eclipse INU Eclipse INUe Maximum Number of Links one link three links 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 Link (non-protected) Protected link Ring-protected link Icon
Procedure
To create an RF link between two Eclipse radios:
614-330055-001 February 2010
3-57
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-58.
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 - RF Link. A message displays, confirming that the link is created:
5. Select OK.
RF links are automatically discovered for Eclipse radios.
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, an error message displays.
Next Topic: Verifying an Eclipse or TRuepoint RF Link on page 3-58
Related Topics: Creating an RF Link from the Tree Viewer on page 3-54 Deleting an RF Link on page 3-59
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.
3-58
Aviat Networks
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 on page 3-59
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.
614-330055-001 February 2010
3-59
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. The Delete Link window displays. 3. To confirm deleting the link, select Yes.
2. In the right-click menu, move the cursor to the Link option and select Delete.
Related Topics: RF Linking Procedures on page 3-54 Verifying an Eclipse or TRuepoint RF Link on page 3-58
3-60
Aviat Networks
Miscellaneous Device Procedures

This section details several miscellaneous device procedures: Viewing Configuration for Devices on page 3-61 Configuration Profiles for Bulk Configuration on page 3-68 Eclipse Node Licenses on page 3-110 Viewing/Changing Network IP Addresses on page 3-76 Viewing/Changing TNet Proxy Configurations on page 3-77 Using the TNet Proxy Viewer on page 3-80
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 devices configuration data: 1.
Viewer from the right-click menu.
Within the Tree or Map Viewer, right-click the device icon. Select Configuration
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. 614-330055-001 February 2010 3-61
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 Information tab Description The information tab lists general information about the device, such as name, site name, IP address, and type. For Eclipse radios, the Configuration Viewer window has 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).
Radio Frequency tab
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 MegaStar, this includes Radio PA status. For DXR radios, there is no RF tab; instead, see the Slot Configuration tab.
3-62
Aviat Networks
Tab
Description For Constellation radios, Constellation Terminal radios display one link tab. Constellation Repeater radios display two link tabs. Each link tab has data for modem settings, protection settings, and link settings. Non-Farscan Constellation radios display one Link tab and the IP Routing tab:
Constellation via Farscan Proxy radios do not display the IP Routing tab. 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.
614-330055-001 February 2010
3-63
Tab Gateway (WiMAX ASN-GW only)
Description Data gateway details for a device.
Hardware tab (Velox only)
The Hardware tab lists the version of the supported platform and IDU serial number and barcode.
Interfaces (ADR*, Eclipse Optimization Gateway, WiMAX ASN-GW) * With firmware later than P2.6. Inventory Tab (Eclipse, TRuepoint 6500, Constellation, ADR*, Eclipse Optimization Gateway, WiMAX ASN-GW, Juniper WSG-R) * With firmware later than P2.6.
The device interfaces for a device.
This tab provides an inventory of all plug-ins associated with a device.
3-64
Aviat Networks
Tab IP Routing Tab (TRuepoint 5000, Constellation without FarScan Proxy only)
Description This tab provides the IP routing settings for a device.
MC Alarm Inputs and MC Relay Outputs (DVA, CAU)
Alarm inputs and relay outputs for the DVMs connections.
Mux Modem Tab (TRuepoint 4040 and 5000, and Constellation)
Mux modem settings for TRuepoint 4040/5000 or Constellation radios.
Network (WiMAX ASN-GW Only)
DNS and NTP networking for a device.
614-330055-001 February 2010
3-65
Tab PAI (DVA Only)
Description Programmable Alarm Indicators (PAIs) for a DVM.
PMP (StarMAX 6100 and 6400 only)
PMP for a StarMAX base station.
RSC and RPS (GP) (TRuepoint 6500 Only)
Data about the Radio Service Channel and Radio Protection Switching for the TRuepoint 6500 radio.
Note:
For more on the RSPI, RSC/RPS, and Service tab values for TRuepoint 6500, see the TRuepoint 6500 documentation.
RSPI (TRuepoint 6500 Only)
Radio Section Physical Interface values for the TRuepoint 6500.
3-66
Aviat Networks
Tab Service (TRuepoint 6500 Only)
Description Service data for the TRuepoint 6500 radio.
Slot Configuration Tab (DXR Only)
Details about each slot for the DXR radio, and the hardware and software installed at each slot.
Software tab
The Software tab lists the version of the software for the components of the radio.
Related Topics: Viewing/Changing Network IP Addresses on page 3-76
614-330055-001 February 2010
3-67
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-68 Configuration Profile Settings for Bulk Configuration on page 3-71 Delete a Configuration Profile on page 3-75
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 ) and select Configuration > Profiles from the right-click menu. or rack
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-68
Aviat Networks
3. The selected configuration template displays.
4. Enter the required configuration values. See Configuration Profile Settings for Bulk Configuration on page 3-71 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 radios configuration and automatically enters the information to the Configuration Profile window. Select the Read button to enter the radios configuration to the Configuration Profile window. The Read button is highlighted in the sample below.
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
614-330055-001 February 2010
3-69
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 scripts 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 on page 3-71 Delete a Configuration Profile on page 3-75
3-70
Aviat Networks
Configuration Profile Settings for Bulk Configuration

The table below describes the settings available for each Configuration Profile.
Configuration Profile Eclipse Ethernet Port Settings for IDU ES Settings 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 February 2010
3-71
Configuration Profile Eclipse OSPF Settings
Settings Allows you to enter the IP address of a server to use for OSPF settings, and to enable OSPF use for the IPs 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.
3-72
Aviat Networks
Configuration Profile Eclipse Ethernet Port Settings DAC GE
Settings 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 GE
Allows you to enter the Priority Mode settings 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 February 2010
3-73
Configuration Profile
Settings 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.
XP4 16/E3 Trib Controls
TRuepoint Trap Destinations: 6400, 5000, 4040, 4000
This allows you to enter the trap destination information for the selected type of TRuepoint radios. Enable - Select the checkbox to enable the trap destination. Destination - The IP address of the trap destination.
TRuepoint SNMP Managers: 5000, 4040, 4000
This allows you to enter the trap destination information for the selected type of TRuepoint radios. Enable - Select the checkbox to enable the trap destination. Destination - The IP address of the SNMP manager.
Note: Executing these changes overwrites any previous settings, and disabling SNMP managers also disables ProVisions SNMP connection to the device.
Constellation Trap Destinations
This allows you to enter the trap destination information for the Constellation radios. Destination - The IP address of the trap destination.
Note: This data is not active for Constellation for FarScan devices.
3-74
Aviat Networks
Configuration Profile
Settings This allows you to enter the trap destination information for the LE3000 or LE3200 radios. Destination - The IP address of the trap destination.
LE3000/LE3200 Trap Destinations
Related Topics: Create and Execute a New Configuration Profile on page 3-68 Delete a Configuration Profile on page 3-75
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:
614-330055-001 February 2010
3-75
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: Create and Execute a New Configuration Profile on page 3-68 Configuration Profile Settings for Bulk Configuration on page 3-71
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 devices 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:
3-76
Aviat Networks
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 Configuration for Devices on page 3-61 Viewing/Changing TNet Proxy Configurations on page 3-77
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 networks 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.
614-330055-001 February 2010
3-77
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 devices 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:
3-78
Aviat Networks
2. Select Proxy Configuration Manager. The Proxy Configuration Manager window displays.
Activity To change a Proxys name or increase its number of subnets within ProVision: How to... 1. Select the required Proxy icon.
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 Proxys IP address: To move a TNet device from one subnet to another subnet and/or change the TNets address on the subnet: See Viewing/Changing Network IP Addresses on page 3-76. 1. Expand the Proxy and the subnet to display the TNet devices. Select the required TNet device.
The devices 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: Viewing Configuration for Devices on page 3-61 Viewing/Changing Network IP Addresses on page 3-76 Using the TNet Proxy Viewer on page 3-80
614-330055-001 February 2010
3-79
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-15.
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: Viewing Configuration for Devices on page 3-61 Viewing/Changing TNet Proxy Configurations on page 3-77
3-80
Aviat Networks
Circuit Management
ProVision provides complete Eclipse circuit management. Eclipse Circuit information is documented in the following sections: About Circuits and Circuit Tracing on page 3-81 Collecting Circuit Information on page 3-82 Running the Circuit Trace on page 3-82 Viewing and Managing Circuits on page 3-84
About Circuits and Circuit Tracing

A circuit is a single tributary path that travels through a sequence of radios. For Eclipse radios, circuits are initiated and terminated on a DAC (INU/INUe), or, for an IDU, within its ethernet/data module. A circuit group is a collection of tributary paths that travel through the same sequence of radios from the same start point to the same end point. There are three steps to loading and managing Circuits: Set up the Circuit Collection Preferences - Collecting Circuit Information on page 3-82 Run the Circuit Trace - Running the Circuit Trace on page 3-82 View and Manage Circuits - Viewing and Managing Circuits on page 3-84 The Circuit Trace function maps all circuits that originate or terminate from a selected Eclipse radio, so that they can be viewed in the ProVision network. When a user activates the Circuit Trace function, the circuit trace is performed and updated. 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). Views the circuits to use the troubleshooting features of ProVision, such as loopback and PRBS (pseudo random binary sequence) testing.
Next Topic: Collecting Circuit Information
614-330055-001 February 2010
3-81
Collecting Circuit Information

ProVision automatically downloads circuit information once a day, at a time that you specify. The circuit data is collected and then analyzed off line, to conserve processing time. You can also run a manual download of circuit information at any time.
Procedure
1. Go to the Configuration menu and click Collection Preferences. 2. The Collection Preferences screen displays.
3. To set the time each day when Circuit information is collected and loaded into ProVision, set the Collect daily data at value. Then, click OK. The Circuit data will be collected and loaded at this time every day. 4. To collect and load circuit information immediately, click Collect Now. The information is immediately downloaded. Once you complete this, you can run a Circuit Trace and view the circuit details. See Running the Circuit Trace on page 3-82. 5. Click OK to close the screen.
Next Topic:
Running the Circuit Trace on page 3-82
Running the Circuit Trace

You can run a Circuit Trace for the following device types: Eclipse Terminal (IDU) Eclipse Node (INU, INUe) with a DAC plug-in Eclipse Containers: this runs the trace for all Eclipse radios in the container
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).
3-82
Aviat Networks
You can retrace one circuit using the instructions below, or you can retrace all circuits using the Global Circuit Trace function. Click this item in the Configuration Menu 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 circuit trace. 4. The trace is complete when the status reads 100% 5. Select the Circuits Tab to view the circuits. The Circuits Tab lists each circuit and its components. Select a Circuit to view it in the Map frame.
Figure 3-5. Circuit Tab View with a Selected Circuit
6. The Circuits are now ready to be viewed, analyzed, and managed.
Next Topic: Viewing and Managing Circuits
614-330055-001 February 2010
3-83
Viewing and Managing Circuits

After a circuit trace has been performed, the circuits are displayed in the Circuits Tab, available to be monitored and managed. The following features make monitoring the network easy and efficient: Circuits Tab Filter and Select Circuits View a Single Circuit on page 3-87 View Intersecting Circuits on page 3-88 View Ring Circuits on page 3-89 Find and Resolve Conflicting Circuits on page 3-90 Validate a Circuit Circuit Diagnostics
Circuits Tab
ProVision can support up to 30,000 circuits in a network. In the Circuits Tab, you can view, sort, analyze, and filter the available circuits. The Circuits Tab displays immediately behind the main Map Tab in the ProVision user interface. Click the Circuits Tab to view this screen. From here, you can access the following functions: Filter and Select Circuits View a Single Circuit on page 3-87 View Intersecting Circuits on page 3-88 View Ring Circuits on page 3-89 Find and Resolve Conflicting Circuits on page 3-90 Validate a Circuit Circuit Diagnostics
3-84
Aviat Networks
Figure 3-6. Circuits Tab:
Table 3-7. Circuit Tab Values
Selected Object
Name of the selected object; its circuits are detailed in this tab.
Note: To view all circuits for the entire network, click the X beside this field.
Include Intersecting Circuits Group
Check this box to view circuits that pass through the circuits for this object, in addition to circuits that start and end at this object. Check this box to view these circuits collected into Groups based on termination points. The Groups are connected by shading. Use the Filter function to filter and view specific circuits. Select a circuit in the table, and a graphic representation displays in the Map Tab. See Find and Resolve Conflicting Circuits on page 3-90 for details. Shows information for the links for the selected device. The severity of any events for this link.
Filter Map Tab Conflicts Tab Circuit Table Severity
614-330055-001 February 2010
3-85
Status
The status of this link. Status is indicated by color: Green = OK. Red = Data incomplete, cannot completely trace this circuit. Blue = Data inconsistent. Yellow = Circuit route changed. Orange = Circuit route removed, circuit has been deleted and recreated. Glowing Orange = Incorrect Ring configuration.
Name Start Connectable End Connectable Capacity Type Priority
The name of the circuit link, which shows the connected devices. Eclipse radio and DAC plug-in/port for the circuit connection beginning. Eclipse radio and DAC plug-in/port for the circuit connection end. Total capacity of the link. Circuit type: E1, E3, STM1, Ethernet, Ring Related to Adaptive Modulation, assigned in Eclipse Portal if applicable.
Next Topic:
Filter and Select Circuits
Filter and Select Circuits

ProVision can manage up to 30,000 circuits. To locate specific circuits, use the Filter function.
Procedure:
1. Ensure that circuits are loaded into the Circuits tab. 2. If you want to search circuits for one device, select that device in the Tree viewer. The circuits for that device display in the Circuits tab. 3. If you want to search circuits for all devices, open the Circuits tab and click the X beside the Selected Object field. All circuits for the network display in the Circuits tab. 4. At the bottom of the Circuits tab, click the Filter button. 5. The Filter field displays. 6. Enter a value for the circuits. This can include its:
3-86
Aviat Networks
Name Type - E1, E3, etc. IP address 7. Then, press Enter. 8. ProVision filters all available circuits based on this value. For example, if you searched on an IP address, all circuits that include that IP address will be selected. The circuits that match this value display in the Circuits tab.
Next Topic:
View a Single Circuit
View a Single Circuit

In the Circuits Tab, select the table row of an individual circuit to display that circuit, and only that circuit, in the Map subtab of the Circuits. In the example below, Circuit 13 is selected, and displays in the Map subtab:
If the Map and Conflicts subtabs are not displaying, select the circuit and click the Show Details button on the lower right of the Circuits tab. This opens the Map/Conflicts subtabs with the circuit displayed. To close these subtabs, click Hide Details. The Map details include the port numbers for the devices. To view additional information about a circuit, in the Map subtab, place the cursor over the circuit device. A pop-up displays with capacity and link information.
614-330055-001 February 2010
3-87
You can right-click on a single circuit. The circuit right-click menu includes:
Item Show Conflicts Function Opens the Conflict subtab and displays any circuit conflicts. See Find and Resolve Conflicting Circuits.
Clear Conflicts Validate Diagnostics Event Browser Network Health Report if present: Connectable
Find and Resolve Conflicting Circuits. Validate a Circuit.
Resolves any identified circuit conflicts. See Runs an automatic validation of the circuit. See
Opens the Circuit Diagnostics screen. See
Circuit Diagnostics.
Opens the circuit-specific Event Browser. See
Event Browser for a Circuit.

Opens a Network Health Report for this specific device. Right-click on the Connectable table cell to view the Connectable menu. This shows functions for the object represented in this cell.
Next Topic:
View Intersecting Circuits
View Intersecting Circuits

Intersecting circuits for a device are circuits that do not start or terminate at a device, but instead pass through the device on their circuit pathway. You can include intersecting circuits in your view of a devices circuits.
Procedure
1. Select the device in the Tree Viewer. 2. Open the Circuits Tab. The device circuits are displaying. 3. Click the Include Intersecting Circuits check box.
4. Any intersecting circuits are added to the Circuits Tab.

Next Topic:
View Ring Circuits
3-88
Aviat Networks
View Ring Circuits

ProVision clearly identifies circuits for Eclipse ring networks. When you select and view the Circuit in the Map subtab, it is identified as an Eclipse Ring. Hover over the circuit to view its ring pathways:
Double-click the circuit to expand and view all the aspects of the ring circuit.
Next Topic:
Find and Resolve Conflicting Circuits
614-330055-001 February 2010
3-89
Find and Resolve Conflicting Circuits

A circuit conflict occurs when, due to a circuit reconfiguration, a circuit pathway needs to be updated. Circuit conflicts do not occur when a circuit is first traced; they may be identified in subsequent traces. ProVision includes a Conflicts subtab, which enables you to view and resolve conflicting circuits.
Procedure
1. Select the device in the Tree Viewer. 2. Open the Circuits Tab. The device circuits are displaying. 3. To view conflicts for a circuit, right-click the circuit and select Show Conflicts. Or, click the Show Details button, then click the Conflicts subtab. 4. To resolve conflicts for a circuit, right-click the circuit and select Clear Conflicts. If required, use Portal to reconfigure the Eclipse radios.
Next Topic: Event Browser for a Circuit
Event Browser for a Circuit

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-20.
3-90
Aviat Networks
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-4. Circuits deleted because they no longer exist in the ratio network are shown via Delete a Circuit on page 3-92.
Validate a Circuit
Introduction
Occasionally, changes are required in a network, whether those changes are to a whole circuit or to an individual radio. You must validate the circuit to ensure it is correctly represented within ProVision. When you run a circuit validation, the selected circuit is deleted and then retraced. The terminating plug-ins (such as a DAC) define a circuit. If you validate one circuit, another circuit with a common terminating plug-in may also be deleted.
You can validate one circuit using the instructions below, or you can validate all circuits using the Global Circuit Trace function. Click this icon on the toolbar to run a Global Circuit Trace:
Procedure
1. Right-click the name of the circuit. 2. Select Validate on the right-click menu displayed. 3. ProVision runs the circuit trace. The circuit trace progress is shown at the bottom of the Circuit tab.
4. When the circuit trace is complete, a message displays, confirming that the validation is successful and the circuit table is updated.
Next Topic: Delete a Circuit
614-330055-001 February 2010
3-91
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
1. In the Circuit Tab, right-click the name of the circuit. The Delete Circuits window displays, with two deletion options:. 2. Select Delete on the right-click menu displayed.
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 Software and Licenses
3-92
Aviat Networks
Loading/Activating New Software and Licenses

This section describes how to load and activate new Eclipse, StarMAX TRuepoint software, and new Eclipse node licenses. About Loading Device Software Via ProVision on page 3-93 Eclipse Software Loading Examples on page 3-95 Stage 1: Software Load Procedure on page 3-96 Stage 2: Software Activation Procedure on page 3-102 Eclipse Node Licenses on page 3-110 Eclipse and StarMAX Configuration Backup Export on page 3-113
About Loading Device Software Via ProVision

Before loading and activating new 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, StarMAX base station, or TRuepoint software. You can do this for multiple devices simultaneously, using the Loading/Activating New Software feature. You select a number of devices to be loaded, in a single task. Then, ProVision transfers the software from the software register to the devices. This feature also provides the flexibility to sequentially run a number of separate software-loading tasks to different devices and device types. 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. This is available for Eclipse, TRuepoint, and StarMAX. Scheduled Activation - For Eclipse devices only, ProVision also lets you select a date and time to automatically activate one or more radios. This is useful to automatically activate the new software in large sections of a network at a time when there is minimal traffic, minimizing network disruptions. An entire network of Eclipse, StarMAX, or TRuepoint devices 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.
614-330055-001 February 2010
3-93
When loading software using this feature, the same version of the software is loaded onto all parts of a device.
The Software Upgrade Process

The software upgrade is split into two separate stages: loading and activation. Stage 1: Software Load Procedure on page 3-96 - The loading stage is slow, especially for Eclipse devices, 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: Software Activation Procedure on page 3-102 - The activation stage, although it occurs almost instantly, may affect network traffic. 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 device software into the ProVision Server software register.
2. Identify the number of download tasks needed in order to upgrade the network. A software download task refers to the number of devices to be grouped together for a download. 3. Create and initiate a software download task, by selecting the device type, the software version, and the radios to be loaded. Monitor progress using the ProVision Task Manager. 4. On download completion, activate the software in the devices 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 software loading examples are shown, for Eclipse radios.
3-94
Aviat Networks
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.
Figure 3-7. 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-8. Example 2: An Eclipse Radio Network Divided into Regions
Next Topic: Stage 1: Software Load Procedure on page 3-96
614-330055-001 February 2010
3-95
Stage 1: 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-96 Part B: Load the Software onto the Devices on page 3-99
Part A: Register the Software onto the ProVision Server
Before loading software onto a network of devices, 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.
3-96
Aviat Networks
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 Devices on page 3-99. 2. Click on the Register menu and select the type of software pack that you want to load: Eclipse, TRuepoint, or StarMAX Base Station.
3. A directory window displays. 4. You need to select the software that you will load. Either: Select the directory that contains the software. Select the desired software pack and select Open. 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.
614-330055-001 February 2010
3-97
5. The new software pack now appears on the software register.
6. To set the server value for the software type, select the software type, then go to 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 radios of this type. When the software download is started, the radios use 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 networks 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.
3-98
Aviat Networks
Next Topic:
Stage 2: Software Activation Procedure
Part B: Load the Software onto the Devices

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 Status Description If this item is blank for a device, the device is live and available to have new software loaded. Problem icons are: = fatal condition exists for the device, and software cannot be loaded. Note that items with this status are grayed out. = warning icon noting that there are problems with this device, which may impact on software loading. Object Container Hop Count Software Version(s) The type and name of the device. The IP name of the container. The distance in IP hops to the target device. The version number of the currently installed software.
You can select the type of software that you are loading, and you can filter the Software Loading screen to view only devices that match a specified software type.
614-330055-001 February 2010
3-99
The software download process may take up to 30 minutes or longer, depending on the network bandwidth, the number of concurrent loads, the number of devices being loaded within the task, and the size of the software file being loaded. Eclipse software normally takes 30 minutes or longer to load;
TRuepoint software may load more quickly.
Procedure:
Follow steps below to load the software onto the devices.
If you are loading software onto a StarMAX device, you must reset the ProVision FTP port from 555 to 21. Reset this value in the file:
ProVisionServer/tomcat/webApps/Root/pv/Templates/ server_configuration.xml
If you do not reset this value, StarMAX software cannot load. 1. From the menu bar, select Configuration > Software Loading. The Software Loading window displays.
2. In the Type menu, select the device type. The Software Loading screen displays each device of that type in the network, the container where it is located, and its current software version. 3. In the Operation menu, select the software type to load. The devices of that type display. 4. Select the devices that are to have the software loaded. To organize or filter the devices, you can: Select the column heading Object Container to sort the devices by their location in the network. To load a group of devices that are listed sequentially, hold down the shift key and select the first and last device in the list. To load a group of devices that are not listed sequentially, hold down the ctrl key and select each device. To identify devices that are not compatible with the software type, click Filter Incompatible Objects. An exclamation mark displays beside any incompatible
3-100
Aviat Networks
objects.
5. For Eclipse devices, you can Select the Scheduled Activation check box to activate the software at a specific time. 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. If you do not select Scheduled Activation, the software activates immediately after you click Load Selected Software. 6. 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.) 7. Select the Load Selected Objects button to begin the download. 8. 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 . 9. The Task Manager window appears. Select the + to view the objects that are being updated. A bar chart indicates the progress of the download. 10. The download is complete when the bar chart indicates 100%. At that time, for Eclipse and TRuepoint, the Activate buttons appear. See Stage 2: Software Activation Procedure on page 3-102 for the next steps to take.
If you selected scheduled activation for an Eclipse device, instead of Activate buttons appearing, a timer displays which counts down the amount of time before the scheduled activation occurs. 11. If the software load fails, or is incomplete, an alarm icon displays: right-click on
614-330055-001 February 2010
3-101
the icon to view information about the software loading problem.
Next Topic: Stage 2: Software Activation Procedure on page 3-102
Stage 2: Software Activation Procedure

The activation procedure is when software, installed in Stage 1: Software Load Procedure on page 3-96 is switched on. There are separate procedures for: Eclipse Software Activation Procedure TRuepoint Software Activation Procedure StarMAX Software Activation Procedure
Recommended Activation Process

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. Always assume that traffic may be affected when scheduling an activation. To minimize the possible disruption of the network, it is recommended to begin by activating the devices 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. Also, if there is a traffic-affecting problem, then by going first to a remote site, the least amount of traffic is affected.
Eclipse Software Activation Procedure

To activate the Eclipse software after it has been loaded onto the devices, follow steps 1 through 6.
3-102
Aviat Networks
For Eclipse devices, 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. 1. Select the Activate button to activate the software inside the Eclipse device. 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 device 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 device 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 device and any downstream devices 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-99). The message versions OK indicates the two versions are the same.
614-330055-001 February 2010
3-103
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 devices remain in the Task Manger. The status for the task and each device 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 device within the task to open a right-click window with additional functions. Results - Displays the results of the software loading and activation process for the particular device and lists the description, status, start, and end time for the process. 6. Select the Close button to close the Task Manager window.
3-104
Aviat Networks
TRuepoint Software Activation Procedure

To activate the TRuepoint software after it has been loaded onto the devices, follow steps 1 through 7:
Before you begin, ensure that the TRuepoint devices have been set up with the correct FTP credentials; see the Device Security Accounts screen. 1. Beside the TRuepoint device, a drop-down menu button displays with three options:
Alternate System The following process is executed: Switch the software banks and activate the new Controller software, through the Alternate Software process (see below). Then load the new interface card firmware and activate, through the Firmware Upgrade process (see below). Alternate Software Activates the new Controller software through the following process. Note that this process does not affect traffic: Switch the software banks, with the Alternate now becoming the Primary bank. Reboot of the Controller, resulting in activation of the new Controller software. Firmware Upgrade Activates the new interface card firmware through the following process: The Controller loads the new interface card firmware into the cards. Activate the new firmware in the cards.
The Firmware Upgrade process affects traffic. For TRuepoint 5000 and 4040v2, only the SPU cards (MUXes and modems) are loaded, but not the RFU(s). The RFU(s) can be loaded with the new firmware in the active bank through Web CIT (see the final step of these instructions for details). For TRuepoint 6400, all cards (LIU, DPU, OPT, RCVR and XMTR) are loaded.
614-330055-001 February 2010
3-105
2. Select the activation option you require for the TRuepoint device. The button changes to a Running button and an information icon appears.
3. 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 TRuepoint device switches to the new software. Reboot (90 sec. to 2 min.): The TRuepoint device reboots (resets the software). The Wait for reboot OK message indicates that the reboot is complete.
TRuepoint traffic is affected during both Activation and Reboot stages. During the reboot, NMS visibility of the rebooted device and any downstream devices are lost. Verify (2 to 5 min.): ProVision checks to make sure the software version in the device is the same as the version in the Software Table (page 3-99). The message versions OK indicates the two versions are the same. 4. The process is complete when each of the activation steps indicates OK. 5. If a TRuepoint software load has failed, it displays in red. Right-click on the device to view the reason for the software load failure. Possible reasons include: Upgrade Agent Not Accessible - The radio has failed to reboot after the upgrade. Repeat the Activation from step 1.
3-106
Aviat Networks
Failed To Send - Radio is having problems receiving the upgrade: could be a configuration problem with the radio.
6. Right-click the software type-level task bar to open a pop-up window with additional functions.
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 devices remain in the Task Manger. The status for the task and each device 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. 7. To verify that the software version has loaded correctly for the TRuepoint devices, open the Configuration Viewer for each device and check the Inventory tab. This tab should show that the correct firmware version is now loaded to the device. See Viewing Configuration for Devices. 8. Select the Close button to close the Task Manager window.
614-330055-001 February 2010
3-107
Note that RFU software for TRuepoint 5000 and 4040v2 radios cannot be loaded using ProVision. This must be done separately, using WebCIT. In WebCIT, go to Configuration->Inventory-> RFU.
In the RFU screen, click Upgrade to upgrade the RFU software. Once this is done, to view the RFU upgrade in ProVision, refresh the Configuration Viewer for these radios.
Related Topics: Viewing/Changing Network IP Addresses on page 3-76
StarMAX Software Activation Procedure

For StarMAX, the software is activated when it is loaded. However, the loading process has some variations, and you need to verify the software load and wait for the device to reboot automatically. To install StarMAX, follow this procedure. 1. Load software onto the StarMAX device, as described in Part B: Load the Software onto the Devices on page 3-99.
3-108
Aviat Networks
If you are loading software onto a StarMAX device, you must reset the ProVision FTP port from 555 to 21. Reset this value in the file:
ProVisionServer/tomcat/webApps/Root/pv/Templates/ server_configuration.xml
If you do not reset this value, StarMAX software cannot load. 2. In the Task Manager, beside the StarMAX device, the software loading status displays as Command Sent. This shows that the software has been sent to the device.
3. To verify that the StarMAX device has received the software, check in the Task Manager, where the Status should display, titled Upgrading.
4. When the software is done loading, the event status changes to Complete as shown.
5. Click the Activate button. ProVision loads the software onto the StarMAX device and reboots the radio to display the new loaded version of software. Note that this can take some time. The Action status first displays as Running, and then as Complete. When it displays as Complete, the StarMAX software has been loaded successfully.
6. After the software has loaded, the StarMAX device reboots automatically. This
614-330055-001 February 2010
3-109
takes several minutes.
7. After the reboot, check the Inventory Report for the StarMAX device. The report should show that the software version matches the loaded software.
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\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 Aviat 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
3-110
Aviat Networks
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. 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\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. Sort the table by clicking on selected table headings. Only the most recent license for a particular object displays in the Eclipse License Table. 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.
614-330055-001 February 2010
3-111
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. 8. To export the license information as a .CSV file, select the desired licenses and click Export. You are prompted to select the name and location of the . CSV file. ProVision notifies you when the Export is complete.
Table 3-8. The Eclipse License Table Headings Heading Object Container Serial Number Filename Creation Date Application Date Capabilities Description The name of the Eclipse Node. The container of the Eclipse Node. The serial number of the Eclipse Node. The filename of the license. The data the license was created. The data the license was applied to the Eclipse Node. 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.
3-112
Aviat Networks
Related Topics:
About Loading Device Software Via ProVision on page 3-93
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 devices. If change is detected, FTPs the 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. You can do the following with backups from this screen: Preview - Displays a preview of the backup. Restore - Restore a selected backup file. Export - Export and save the backup file. 5. To export the backup, select the most recent backup and click Export. 6. The Select Export Location screen displays. Navigate to the file folder where you
614-330055-001 February 2010
3-113
want to save the backup, and click Save.
7. The backup file is saved to this location. 8. The backup file for Eclipse or StarMAX base stations can be used to load the radios again, if required. Select the backup file and click Restore.
For StarMAX base stations, when you restore the Configuration Backup, ProVision will restart the base stations. In addition, you must reset the login and password for the telnet server in the Device Security Accounts.
3-114
Aviat Networks
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-72
614-330055-001 February 2010
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-3 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.
4-2
Aviat Networks
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
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-72.
Next Topic: Customizing Event Browsers
614-330055-001 February 2010
4-3
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-20.
Next Topic: Event Management Procedures
4-4
Aviat Networks
Event Management Procedures

This section covers the following topics: Network Events on page 4-5 Event Browsers on page 4-20 Event Log Pre-Filtering on page 4-33 Event Notification on page 4-47 Logical Containers on page 4-65 Logical Links on page 4-69 Scoreboard Group Scenarios on page 4-72
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. This section covers the following topics: Network Event States on page 4-5 Viewing Network Events on page 4-6 Viewing an Events Properties on page 4-7 Acknowledging a Network Event on page 4-9 Unacknowledging a Network Event on page 4-11 Manually Clearing a Network Event on page 4-13 Sleep Status for a Device on page 4-18 Event Browsers on page 4-20
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.
614-330055-001 February 2010
4-5
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. An operator manually cleared the original event. ProVision updates the original event to a cleared state.
Related Topics: Viewing Network Events on page 4-6 Viewing an Events Properties on page 4-7 Acknowledging a Network Event on page 4-9
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
4-6
Aviat Networks
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-20.
Related Topics: Network Event States on page 4-5 Viewing an Events Properties on page 4-7 Acknowledging a Network Event on page 4-9
Viewing an Events Properties

Introduction
You can view an events 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.
614-330055-001 February 2010
4-7
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-5. 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 events properties: 1. Within the main Event Browser or a customizable Event Browser, right-click an event. In the right-click menu, select Event Properties.
4-8
Aviat Networks
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: Network Event States on page 4-5 Viewing Network Events on page 4-6 Acknowledging a Network Event on page 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.
614-330055-001 February 2010
4-9
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
4-10
Aviat Networks
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. 6. ProVision automatically opens an Event Note dialog box. Enter any relevant 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: Network Event States on page 4-5 Unacknowledging a Network Event on page 4-11 Manually Clearing a Network Event on page 4-13
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
614-330055-001 February 2010
4-11
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.
5. ProVision automatically opens an Event Note dialog box. Enter any relevant 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: Network Event States on page 4-5 Acknowledging a Network Event on page 4-9 Manually Clearing a Network Event on page 4-13
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-49.
4-12
Aviat Networks
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=
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-18. 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 radios 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. 614-330055-001 February 2010 4-13
Procedure
To manually clear an event from an Event Browser: 1. From any Event Browser window, select the event or events to be cleared. The cleared events are removed from the browser window and the event summary icons in the bottom right corner are updated. Related Topics: Network Event States on page 4-5 Sleep Status for a Device on page 4-18 Manually Resynchronize Alarms on page 4-14 Event Browsers on page 4-20 2. Right-click the selected event or events and from the right-click menu select Clear.
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: 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-15.
Procedure
1. In ProVision, from the Tree Viewer or Map, right-click on a Constellation or device. 2. From the right-click menu, select Fault > Manual Alarm Resynchronization.
4-14
Aviat Networks
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: Network Event States on page 4-5 Manually Clearing a Network Event on page 4-13 Event Browsers on page 4-20 Configure TRuepoint 6400 Alarm Resynchronization on page 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 ProVision with 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 radios WebCIT installation. Obtain this, and then follow the procedure below.
614-330055-001 February 2010
4-15
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: Network Event States on page 4-5 Manually Clearing a Network Event on page 4-13 Manually Resynchronize Alarms on page 4-14
4-16
Aviat Networks
Customizing Event Names or Severity Levels

Introduction
For most devices, you can customize event names and severity levels through their craft tool. For selected 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. You can customize event names and severity levels for the following device types, using either ProVision or the indicated craft tool:
Device Altium (all variants) Constellation (all variants) CAUs DVAs Eclipse: AUX Plugin, Auxiliary Module EficientSite Generic Devices LE3000/WL1000 LE3200 Megastar (all variants) RW2000 TNet: Classic II, LC Series, M Fiber, M series, QUANTUM, SPECTRUM II TRuepoint: 4000, 4040, 5000, and 6400 Customize Event Name? Tool to Use? Yes, WMT Yes, ProVision Yes, ProVision Yes, ProVision Yes, Eclipse Portal No Yes, ProVision Yes, LE3000 Manager Yes, LE3200 Manager Yes, ProVision Yes, RW2000 Manager Yes, TNet Web Customize Severity Level? Tool to Use? Yes, WMT Yes Yes, ProVision Yes, ProVision Yes, Eclipse Portal Yes, Web Craft Tool Yes, ProVision No No Yes, ProVision No Yes, TNet Web
Yes, WebCIT
Yes, ProVision
Procedure
To customize the name or severity level of an Event in ProVision: 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.
614-330055-001 February 2010
4-17
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-18
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 devices error status is maintained in the ProVision user interface and the events prior to the device being put to sleep can still be viewed.
4-18
Aviat Networks
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-52. To find all Sleep settings, use the Maintenance Scheduling Table screen. Open this from the Fault menu as Maintenance Scheduling. This displays all the saved Sleep settings for all 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. The Sleep submenu displays.
3. Set the Sleep values for the device: Sleep Now - Sends the device to sleep immediately. Sleep For - Select the number of days/hours/minutes for the sleep period. Sleep Until - Select the date and time when the device will be awoken. Then, click the Sleep button. 4. The device is set to the Sleep state and displays with the Sleep To wake a single device: icon.
614-330055-001 February 2010
4-19
5. To take a device out of the Sleep state, right-click the device icon for the required radio, and select Sleep. 6. On the right-click Sleep menu, select the Wake Now button. The Sleep 1. icon is removed from the device.
To set the Sleep status of two or more devices: Select the device icons for all the required radios. Then, right-click and select Sleep. 2. The Sleep submenu displays as follows:
3. Set the status to Sleep or Wake Now 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: Network Event States on page 4-5 Viewing Network Events on page 4-6
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
4-20
Aviat Networks
You can also open a separate Event Browser window by: Selecting the New Event Browser icon Pressing Ctrl+E. 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
from the tool bar, or
Selecting Fault > Event Browser > New Event Browser from the menu bar, or
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. This section covers the following topics: Saving an Event Browser View on page 4-22 Viewing a Saved Event Browser on page 4-23 Customizing an Event Browser on page 4-23 Event Browser Filter Values on page 4-24 Changing Event Browser Options on page 4-26 Event Browser Option Values on page 4-28 Deleting an Event Browser on page 4-30 Saving Event Browser Contents on page 4-31 Printing Event Browser Contents on page 4-32 For information on viewing and managing network events, see Network Events on page 4-5.
614-330055-001 February 2010
4-21
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-23 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 on page 4-23 Customizing an Event Browser on page 4-23 Event Browser Filter Values on page 4-24
4-22
Aviat Networks
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: Saving an Event Browser View on page 4-22 Customizing an Event Browser on page 4-23 Event Browser Filter Values on page 4-24
Customizing an Event Browser

Introduction
You can change an Event Browsers 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 614-330055-001 February 2010 from 4-23
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 Simple Tab Definition 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.
4-24
Aviat Networks
Filter Setting
Definition 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 filters 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 filters end date and time, repeat the above four steps for the filter End date.
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.
614-330055-001 February 2010
4-25
Filter Setting Text
Definition 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 radios 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: Customizing an Event Browser on page 4-23 Changing Event Browser Options on page 4-26 Event Browser Option Values on page 4-28
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.
4-26
Aviat Networks
Selecting the title bar of a column changes how the events in the browser are sorted.
Procedure
To change Event Browser options: 1. Open a separate Event Browser window: Open a new Event Browser by selecting the new Event Browser icon the tool bar. from
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 Browser Options icon. The Browser Options window displays.
See the table below for detailed information on each of the fields. 3. Make the required changes and select OK. The Event Browser window reflects the browser option changes.
614-330055-001 February 2010
4-27
Event Browser Option Values

Tab Option Name Description Description The name of the Event Browser view. 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. When Highlight Severity is enabled, each row in this Event Browser view is highlighted in the events 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.
Details Tab (shown above)
Highlight Severity
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.
4-28
Aviat Networks
Tab
Option
Description
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 Acknowledged Active Status Category
Description Events are sorted by acknowledged events. Events are sorted by active status. Events are sorted alphabetically by category description, for example: communications, equipment, quality of service. Events are sorted by the date and time when they were Cleared. This value is Hidden by default. Events are sorted alphabetically by the event description. Events are sorted numerically by the IP address. For TNet devices, the IP address field lists its Proxy parents IP address, followed by its subnet number. 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. Events are sorted by the device name, in alphabetical order. Events are sorted alphabetically by the devices path. Events are sorted alphabetically by the object type, for example: Altium ADR, Eclipse DAC, Eclipse INU.
Cleared Date/ Time
Event IP Address
Notes
Object Object Path Object Type
614-330055-001 February 2010
4-29
Tab
Option Raised Date/ Time Severity User
Description Events are sorted by the date and time when they were raised. Events are sorted by the event severity color-coding. 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: Changing Event Browser Options on page 4-26 Deleting an Event Browser on page 4-30 Saving Event Browser Contents on page 4-31
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 .
4-30
Aviat Networks
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: Event Browser Option Values on page 4-28 Saving Event Browser Contents on page 4-31 Printing Event Browser Contents on page 4-32
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.
614-330055-001 February 2010
4-31
Procedure
To save the contents of an Event Browser to file: 1. Open a separate Event Browser window: Open a new Event Browser by selecting the new Event Browser icon the tool bar. from
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. 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: Saving an Event Browser View on page 4-22 Customizing Event Browsers on page 4-4 Deleting an Event Browser on page 4-30 Printing Event Browser Contents on page 4-32
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: 1. Open a separate Event Browser window: Open a new Event Browser by selecting the new Event Browser icon the tool bar. from
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 4-32 Aviat Networks
drop-down menu. An Event Browser window displays. 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: Saving an Event Browser View on page 4-22 Viewing a Saved Event Browser on page 4-23 Saving Event Browser Contents on page 4-31
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. This section covers the following topics: Viewing Event Log Pre-Filtering on page 4-35 Adding An Event Log Pre-Filter at the Root Level on page 4-36 Adding an Event Pre-filter at an Object Level on page 4-39 Adding an Event Pre-Filter Via an Event Browser on page 4-40 Modifying An Event Log Pre-Filter on page 4-41 Deleting An Event Log Pre-Filter on page 4-43
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.
614-330055-001 February 2010
4-33
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-34 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
4-34
Aviat Networks
Objects That Can Be Pre-Filtered

Table 4-2. Objects / Events that can be Pre-Filtered Objects/Events Root Object/Network Container Description Pre-filters added at the root level, apply to the entire 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 Radio plug-ins Events You can view or add pre-filters for the selected radio or the Eclipse plug-in. You can view pre-filters for the parent object. 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.
614-330055-001 February 2010
4-35
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: Adding An Event Log Pre-Filter at the Root Level on page 4-36 Adding an Event Pre-filter at an Object Level on page 4-39 Adding an Event Pre-Filter Via an Event Browser on page 4-40
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-35. 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
4-36
Aviat Networks
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.
614-330055-001 February 2010
4-37
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. 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 on page 4-39 Adding an Event Pre-Filter Via an Event Browser on page 4-40 Modifying An Event Log Pre-Filter on page 4-41
4-38
Aviat Networks
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 35 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.
changed.
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
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.
614-330055-001 February 2010
4-39
5. To select the event or events required, select the event checkboxes. 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 on page 4-40
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.
4-40
Aviat Networks
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: Viewing Event Log Pre-Filtering on page 4-35 Modifying An Event Log Pre-Filter on page 4-41 Deleting An Event Log Pre-Filter on page 4-43
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 February 2010
4-41
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: Viewing Event Log Pre-Filtering on page 4-35 Adding An Event Log Pre-Filter at the Root Level on page 4-36 Deleting An Event Log Pre-Filter on page 4-43
4-42
Aviat Networks
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 objects 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 previously pre-filtered object.
icon is no longer displayed beside the
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.
614-330055-001 February 2010
4-43
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: Viewing Event Log Pre-Filtering on page 4-35 Adding An Event Log Pre-Filter at the Root Level on page 4-36 Modifying An Event Log Pre-Filter on page 4-41
4-44
Aviat Networks
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 and LE3200 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:
614-330055-001 February 2010
4-45
3. The Security Log displays the following event data: 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-26 Change the Filter values - see Modifying An Event Log Pre-Filter on page 4-41 Change the Scoreboard options - see About Scoreboard Group Scenarios on page 4-72
4-46
Aviat Networks
Event Notification
Event notification enables ProVision to notify you when selected events occur within the network. This feature enables 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. Different events can have different sounds. 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. This section covers the following topics: Set the Server Notification Preferences on page 4-47 Add or Edit Event Notification Rules on page 4-49 Delete an Event Notification Rule on page 4-52 Configuring the Notification Rule on page 4-53 Set Up an Email Event Notification on page 4-55 Set Up a Pop-Up Message Notification on page 4-57 Set Up an Audio Alarm Notification on page 4-60 Set Up Script Execution on Event Notification on page 4-62
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.
614-330055-001 February 2010
4-47
After you have set this up, your system can send email notifications. See Set Up an Email Event Notification on page 4-55 for more details.
Procedure
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 host name of your email server. 3. Your mail server set up determines if you need the Use authentication feature: If your companys mail server requires authenticated email, select the Use authentication checkbox. Also, enter the Username and Password of your mail server. See your mail servers administrator for the correct 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 Apply button remains inactive until the Test Email 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 on page 4-49 Configuring the Notification Rule on page 4-53 Set Up an Email Event Notification on page 4-55
4-48
Aviat Networks
Add or Edit Event Notification Rules
These instructions are for NOC Engineers and Administrators only. NOC Operators cannot set up new Event Notifications. Adding an event notification rule sets up ProVision to identify specified events. You can then set up notification actions for the events: sending an email message, running a script for a batch file, sounding an audio alarm, or launching a visual pop-up. You can edit an Event Notification rule to change its actions. This set of instructions is a complete overview of the process. For details or specific event notification types, see: Set Up an Email Event Notification on page 4-55 Set Up a Pop-Up Message Notification on page 4-57 Set Up an Audio Alarm Notification on page 4-60 Set Up Script Execution on Event Notification on page 4-62
Procedure
1. From the Menu Bar, select Faults > Event Notifications. The Event Notifications window displays.
2. To create a new Event Notification, click on the Edit Notifications tab, then select the Add button.
614-330055-001 February 2010
4-49
3. The Rule Wizard displays. Enter values here to create a new Event for notifications.
There are three sets of tabs, accessed on the right side, where you enter the event values: Filters - Values to filter for specific event types for this notification. Notification Settings - Notification time criteria. Actions - Actions to occur when the event takes place. 4. Set up the Filters as described inConfiguring the Notification Rule on page 4-53. 5. Set up the Notification Settings.
6. Enter the time value for each of the following. Time values can be set in seconds, minutes, or hours. After Event Duration - Event notification will be sent after the event has lasted for this amount of time. Guard Time - Guards against excessive notifications. ProVision will notify for the first occurrence of this event for this device, then ignore recurrences for this device within this period of time. Reminder After - A reminder about the event will be sent after this amount of time. Notify on Resolution - Check this box, and a notification will be sent when the event either clears or is otherwise resolved. 7. Set up the Actions:
8. Right-click and select an action from the drop-down menu to occur when the event takes place: Add Email Action or Add Script Action. 9. Select Add Email if you want ProVision to notify you via email when the event
4-50
Aviat Networks
occurs. An Email event appears in the Actions viewer. Right-click it to:
Add email address - Enter an email address. Email notifications will be sent to the entered email address, and the email is displayed: Add User/s - Connect the Notification to a ProVision User. Email notifications will be sent to the Users email address. If a User is deleted from ProVision, they will also be deleted from any Event Notifications.
For more details, see Set Up an Email Event Notification on page 4-55. 10. Select Add Script Action if you want to run a shell script for a batch file when the event occurs. Right-click the Run Script item to Add script, and enter the file name for the script batch file.
For more details, see Set Up Script Execution on Event Notification on page 4-62. 11. Select OK to save the new Notification. 12. The action that was created now appears in the Event Notification tab. Its description is included Click on the up and down arrows to hide and view the description:
13. To assign a name to a new Notification, click in the Rule Name column, and type in the new name. 14. To activate the new Notification, click the Active check box.
614-330055-001 February 2010
4-51
You can deactivate a notification to retain it in ProVision without using it. 15. To give the new Notification a pop-up or audio notification, right-click in the Client Notifications table column. You are prompted to: Subscribe to popup alert - Select this to set up an on-screen pop-up alert. See also Set Up a Pop-Up Message Notification on page 4-57. Subscribe to audio alert - Select this to set up an audio alert. See also Set Up an Audio Alarm Notification on page 4-60. 16. Close the Notification Rule window. The new Notification is now active. 17. To edit an Event Notification rule, again open the Event Notification Rules window. Go to the Event Notification tab, select the rule you want to edit, and click Edit. Make your changes and click OK. 18. To delete a rule, select the rule you want to delete, and click Remove. The rule is deleted. Click Close to save the change.
Related Topics: Delete an Event Notification Rule on page 4-52 Configuring the Notification Rule on page 4-53 Set Up an Email Event Notification on page 4-55 Set Up a Pop-Up Message Notification on page 4-57 Set Up an Audio Alarm Notification on page 4-60 Set Up Script Execution on Event Notification on page 4-62
Delete an Event Notification Rule

To delete an event notification rule: 1. From the Menu Bar, select Faults > Event Notifications. The Event Notifications window displays. Go to the Edit Notifications tab:
2. Select the rule to be deleted.
4-52
Aviat Networks
3. Click the Remove button. The selected rule is removed from the Event Notification Rules window.
Related Topics: Add or Edit Event Notification Rules on page 4-49
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 tabs values. Select OK to save the settings for the notification rule.
Notification Rule Tab Simple Tab: Description 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: Event Raised Date / Time Selects events raised between the Start date/time and End date/time. You can select a Start date, an End date, or both. Selects events cleared between the Start date/time and End date/time. You can select a Start date, an End date, or both.
614-330055-001 February 2010
4-53
Notification Rule Tab Objects Tab:
Description 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 Add or Edit Event Notification Rules on page 4-49
4-54
Aviat Networks
Delete an Event Notification Rule on page 4-52
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-47 and Add or Edit Event Notification Rules on page 4-49. 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 Servers web connection, to send emails. Then, set up the event notification Rules. Before you begin, you will need the following information: Your mail servers 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 or host name of your email server. 4. Your mail server set up determines if you need to apply the Use authentication feature: If your companys mail server requires authenticated email, select the Use authentication checkbox. Also, enter the Username and Password of your mail server. See your mail servers administrator for the correct username and password. 614-330055-001 February 2010 4-55
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. To create a new Event Notification, click on the Edit Notifications tab, then select the Add button. 11. The Rule Wizard displays. Enter values in this window to create a new Event for notifications: the Filters, the Notification Settings, and the Actions.
Actions is where you will enter your email notification details. 12. Set up the Filters as described inConfiguring the Notification Rule on page 4-53. 13. Set up the Notification Settings as described in Add or Edit Event Notification Rules on page 4-49. 14. Set up the Actions:
15. Right-click and select Add Email to have ProVision notify you via email when the event occurs. An Email event appears in the Actions viewer. Right-click it to: Add email address - Enter an email address. The Edit Actions window displays:
Enter the email and click OK. Email notifications will be sent to the entered email address, and the email is displayed: Add User/s - Connect the Notification to a ProVision User, then click OK. Email notifications will be sent to the Users email address (see the Installation and Administration Guide for instructions.)
4-56
Aviat Networks
To test an email notification, open the Edit Actions window and click Test. An email is sent: its source address is Provision@company.com. 16. The new Notification is displayed. There are separate icons for an email notification, a User notification, and an attempt to send an email notification to a user whose emails have been suppressed:.
17. The action that was created now appears in the Event Notification tab. Assign the name, activate it, and set up pop-up or audio notification, as described in Add or Edit Event Notification Rules on page 4-49. 18. The changes are saved automatically. 19. Email notifications will be sent for this event. Related Topics Set Up an Email Event Notification on page 4-55 Set Up a Pop-Up Message Notification on page 4-57 Set Up an Audio Alarm Notification on page 4-60 Set Up Script Execution on Event Notification on page 4-62 Configuring the Notification Rule on page 4-53
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-49. It is collected here to help users understand how to set up this type of notification.
614-330055-001 February 2010
4-57
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 Text Box Description 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. If more than one dialog box is open, select the left or right arrow buttons to scroll through the active event notification dialog boxes. Opens the Event Browser of the device where the event originated. Dismisses all active events. Dismisses only the current event. Any active events remain active. Closes the event notification dialog box, but does not dismiss the event.
Left / Right
Event Browser Dismiss All Dismiss Close
Before you begin, you will need the following information: Events for which you want to view pop-up message notifications.
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.
4-58
Aviat Networks
Procedure
1. Follow the steps in Add or Edit Event Notification Rules on page 4-49 to create a new rule for an event.
2. The action that was created now appears in the Event Notification tab. Its description is below:
3. To give the new Notification a pop-up notification, right-click in the Client Notifications table column. You are prompted to Subscribe to pop-up alert. Select this to set up a pop-up alert. 4. The Pop-up item now displays for the event in the Client Notifications column.
5. Select Close to close the Event Notification window. 6. Whenever the specified event occurs, ProVision will display the event message in a pop-up window. Related Topics Add or Edit Event Notification Rules on page 4-49 Set Up an Audio Alarm Notification on page 4-60
614-330055-001 February 2010
4-59
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-47 and Add or Edit Event Notification Rules on page 4-49. 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. Different events can have different alarm sounds. See the following instructions for more information.
.wav sound files should be between 1 and 3 seconds long. If file sounds are longer than that, there are problems repeating sounds if events reoccur.
Procedure
To set up an audio alarm notification: 1. Follow the steps in Add or Edit Event Notification Rules on page 4-49 to create a new rule for an event.
2. The action that was created now appears in the Event Notification tab. Its
4-60
Aviat Networks
description is below:
3. To give the new Notification an audio notification, right-click in the Client Notifications table column. You are prompted to Subscribe to audio alert. Select this to set up an audio alert. 4. The Event Notification Preferences screen displays:
5. Select whether the audio notification will be a single alert (sounding once) or a continuous alert (with the sound playing repeatedly). 6. Select the Audio Settings. This is where you choose the sound that will play for this audio notification: 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 sound played by this .wav file will be the audio notification. 7. Select OK. The Audio item now displays for the event in the Client Notifications column. Mouse over the column to view the type of audio notification in a pop-up.
8. Select Close to close the Event Notification window. 9. Whenever the specified event occurs, ProVision will play the audio notification. Related Topics Add or Edit Event Notification Rules on page 4-49
614-330055-001 February 2010
4-61
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. You can run a script by itself, or script with a default or customized parameter. Before you begin, you will need the following information: Events for which you want to run script executions upon notifications. The names and file locations of scripts to be run upon notification. Any default or customized parameter requirements.
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
1. From the Menu Bar, select Faults > Event Notifications. The Event Notification Rules window displays.
2. To create a new Event Notification, click on the Edit Notifications tab, then select the Add button. 3. The Rule Wizard displays. Enter values in this window to create a new Event for notifications: the Filters, the Notification Settings, and the Actions.
Actions is where you will enter your script details. 4. Set up the Filters as described inConfiguring the Notification Rule on page 4-53. 5. Set up the Notification Settings as described in Add or Edit Event Notification Rules on page 4-49. 6. Set up the Actions:
7. Right-click and select Add Script Action to have ProVision run a shell script for a batch file when the event occurs.
4-62
Aviat Networks
8. Right-click the Run Script item to Add script.The Edit Actions window displays.
9. To set up the script: Enter the file name for the script batch file. Enter any default parameters for the script. A sample script with default parameters is below. See Default Script Parameters on page 4-64.
Enter any custom parameters for the script. A sample script with default parameters is below. Enter your own value to replace customScriptParameter.
10. Click OK. 11. The script item displays as an event.
Run Script runs a shell script for a batch file when the event occurs.Please note the
following:
The batch file runs on the server. To reference a batch file from another folder, you must include the path along with the file name. For example: C:/my documents/ProVision/ 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>/ProVisionServer/ folder. If you do not specify the folder in the Solaris environment, an error message results. To test a script run, open the Edit Actions window and click Test. An example of the script will be run. 12. The action that was created now appears in the Event Notification tab. Assign the name, activate it, and set up pop-up or audio notification, as described in Add or Edit Event Notification Rules on page 4-49. 13. Click Close to save the change. 614-330055-001 February 2010 4-63
14. Email notifications will be sent for this event. 15. When this event occurs, the script will run.
Table 4-3. Default Script Parameters Parameter %date %time %nodename %eventDescription %eventState %eventSeverity %ipAddress %notificationName %reminder %nodePath %eventUser Value Added to Event Notification Date value, formatted YYYY/MM/DD Time value, formatted HH:MM:SS Short name of device Event description text Event status (i.e., Active or Cleared) Event severity (i.e., Warning, Critical, etc.) Event device IP address Notification rule name Adds the text Reminder if this is a reminder about a notification, otherwise no text appears. Full device path, including device name User name associated with event
Related Topics: Add or Edit Event Notification Rules on page 4-49 Configuring the Notification Rule on page 4-53
4-64
Aviat Networks
Logical Containers
This section covers the following topics: Adding a Device to a Logical Container on page 4-66 Removing a Device from a Logical Container on page 4-67 Renaming a Logical Container on page 4-68 Deleting a Logical Container on page 4-68 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 February 2010
4-65
Circuit bundles logical container

Region , site container.
can be included in a logical container. In addition, a can be included within another logical container.
and rack containers cannot be included in a logical
Related Topics: Logical Links on page 4-69
Adding a Device to a Logical Container

To add a device to a logical container: 1. Right-click the required device icon. The Configure Logical Containers window displays. 2. From the menu displayed select Configuration, then select Logical Containers.
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-66
Aviat Networks
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: Removing a Device from a Logical Container on page 4-67 Renaming a Logical Container on page 4-68 Deleting a Logical Container on page 4-68 Adding a Logical Link on page 4-70
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. The Configure Logical Containers window displays. 2. From the menu displayed select Configuration, then select Logical Containers.
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: Adding a Device to a Logical Container on page 4-66
614-330055-001 February 2010
4-67
Renaming a Logical Container on page 4-68 Deleting a Logical Container on page 4-68
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. The Rename Logical Container window displays. 3. Make the required changes to the logical containers name. 4. To save the changes, select OK. 2. From the right-click menu, select Rename.
Related Topics: Adding a Device to a Logical Container on page 4-66 Removing a Device from a Logical Container on page 4-67 Deleting a Logical Container on page 4-68
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.
4-68
Aviat Networks
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: Adding a Device to a Logical Container on page 4-66 Removing a Device from a Logical Container on page 4-67 Renaming a Logical Container on page 4-68
Logical Links
This section covers the following topics: Adding a Logical Link on page 4-70 Renaming a Logical Link on page 4-70 Deleting a Logical Link on page 4-71 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.
614-330055-001 February 2010
4-69
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-65
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 on page 4-70 Deleting a Logical Link on page 4-71
Renaming a Logical Link

Introduction
Under most circumstances, you can rename a logical link.
4-70
Aviat Networks
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 links name displays. 3. Make the required changes to the logical links name. 4. To save the changes, select OK.
Related Topics: Adding a Logical Link on page 4-70 Deleting a Logical Link on page 4-71
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: Adding a Logical Link on page 4-70 Renaming a Logical Link on page 4-70
614-330055-001 February 2010
4-71
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.
4-72
Aviat Networks
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. This section covers the following topics: Viewing a Scoreboard Group on page 4-73 Creating a Scoreboard Group on page 4-74 Editing a Scoreboard Group on page 4-75 Deleting a Scoreboard Group on page 4-75 Adding a Scoreboard on page 4-76 Editing a Scoreboard on page 4-79 Deleting a Scoreboard on page 4-80 Opening an Event Browser from a Scoreboard on page 4-80
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 .
614-330055-001 February 2010
4-73
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 on page 4-74 Editing a Scoreboard Group on page 4-75 Deleting a Scoreboard Group on page 4-75 Adding a Scoreboard on page 4-76
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.
4-74
Aviat Networks
4. To save the Scoreboard group, select Save.
The Save As window closes and the Scoreboard Group window displays. Related Topics: Adding a Scoreboard on page 4-76 Editing a Scoreboard Group on page 4-75 Deleting a Scoreboard Group on page 4-75
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: Adding a Scoreboard on page 4-76 Editing a Scoreboard on page 4-79 Deleting a Scoreboard on page 4-80
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.
614-330055-001 February 2010
4-75
Procedure
1. From the tool bar, select the Saved Scoreboard Groups icon . 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: Creating a Scoreboard Group on page 4-74 Editing a Scoreboard Group on page 4-75
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-24 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
4-76
Aviat Networks
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.
614-330055-001 February 2010
4-77
8. To set up the Scoreboard filters, select the Filters icon The Filters window displays.
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:
4-78
Aviat Networks
Editing a Scoreboard on page 4-79 Deleting a Scoreboard on page 4-80
Editing a Scoreboard
Introduction
You can change the Scoreboards 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: Adding a Scoreboard on page 4-76 Deleting a Scoreboard on page 4-80
614-330055-001 February 2010
4-79
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. The Scoreboard Group window displays. 3. Select the X in the Scoreboards 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: Adding a Scoreboard on page 4-76 Editing a Scoreboard on page 4-79
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.
4-80
Aviat Networks
Figure 4-8. Event Browser Opened Via a Scoreboard
Procedure
To open an Event Browser from a Scoreboard: 1. From the tool bar, select the Saved Scoreboard Groups icon The Scoreboard Group window displays. 3. To view events for an entire Scoreboard, select the Launch Event Browser icon, located in the left corner of the Scoreboard. . 2. From the drop-down list displayed, select the Scoreboard group required.
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: Viewing Network Events on page 4-6 Acknowledging a Network Event on page 4-9 Unacknowledging a Network Event on page 4-11 Manually Clearing a Network Event on page 4-13
614-330055-001 February 2010
4-81
4-82
Aviat Networks
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 events 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. This section covers the following topics: Using System Diagnostics on page 5-1 About ProVision and Craft Tools on page 5-3 Diagnostic and Performance Trends Analysis Procedures on page 5-4 Craft Tools and Diagnostic Controls on page 5-47 Device and Network Reports on page 5-95
Other Resources The Aviat Networks Best Practices Guide includes a section on Eclipse troubleshooting that provides generic information on loopbacks, fade margins, and other diagnostic tools.
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.
614-330055-001 February 2010
5-1
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
Equipment Malfunctions vs. Path Degradation

An equipment problem is typically not intermittent. If it is not intermittent, the radios Event Browser or the events 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
5-2
Aviat Networks
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-47. 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 ProVision is network focused. You can view the history and performance trends of one to many radios within the network. You can determine if the problem is network wide, a group of radios or an isolated radio. For example, a weather front with heavy rain is moving across the country. Using the history you can view the performance affected links and know the problem is temporary and not equipment related because it is happening to many links. Long term data is available from the ProVision database. ProVision performs bulk tasks such as collecting inventory data. Craft Tools (Portal) 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 radio. You can analysis and diagnose the events from one radio. Typically the craft tools loopback diagnostics are used to find faulty equipment. The data available is short term only, that is, limited to what is stored in the radio. Single task affecting a single radio.
Next Topic: Diagnostic and Performance Trends Analysis Procedures
614-330055-001 February 2010
5-3
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-4 Data Collection on page 5-11 Ethernet Performance Data Collection on page 5-17 Performance Features on page 5-30 Craft Tools and Diagnostic Controls on page 5-47 TNet Diagnostics on page 5-58 Diagnostic Controls for Selected Devices on page 5-78
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. This section covers the following topics: Circuit Trace for Circuit Diagnostics on page 5-5 Circuit Diagnostic Window on page 5-5 Setting Up a Circuit Diagnostic Test on page 5-8 Circuit Diagnostic Options on page 5-10
Next Topic: Circuit Trace for Circuit Diagnostics on page 5-5
5-4
Aviat Networks
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-81 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-5
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-8 for an actual example on how to set up a circuit diagnostic test.
614-330055-001 February 2010
5-5
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.
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.
5-6
Aviat Networks
Circuits Diagnostics Window
Description 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.
614-330055-001 February 2010
5-7
Table 5-3. Description of the G.821 Data From a Circuit Diagnostics Test Parameter
Elapsed Seconds Available Seconds Unavailable Seconds Bit Error Count Bit Error Count Ratio Seconds
Description Seconds that have elapsed since the beginning of the diagnostic test. Total available time during a fixed measurement interval. Total unavailable time during a fixed measurement interval. Total number of bit errors during a fixed measurement interval. The ratio of bit error counts to the total available time during a fixed measurement interval. 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. The ratio of errored seconds to the total available time during a fixed measurement interval. 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. The ratio of severely errored seconds to total available time during a fixed measured interval.
Errored Seconds
Errored Seconds Ratio
Severely Errored Seconds
Severely Errored Seconds Ratio
Related Topic: Setting Up a Circuit Diagnostic Test on page 5-8
Setting Up a Circuit Diagnostic Test

To set up a circuit diagnostic test: 1.
Diagnostics.
Open up the Circuits tab. Right-click the selected circuit and select Circuit
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
5-8
Aviat Networks
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.
614-330055-001 February 2010
5-9
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.
Related Topic: Circuit Diagnostic Options on page 5-10
Circuit Diagnostic Options

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

Circuit segment test on a circuit within a network.
ProVision Set-up
or
or
or
Circuit end-to-end test.
or
Related Topic: Diagnostic and Performance Trends Analysis Procedures on page 5-4
Data Collection
This section covers the following details: Introduction on page 5-11 Daily Performance Data Collection on page 5-13 Enabling 15-minute Performance Data Collection on page 5-14 Enabling 15-Minute Ethernet Data Collection on page 5-17 Changing Device Data Collection Status on page 5-16
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.
614-330055-001 February 2010
5-11
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 Aviat 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
Altium MX 2+0
Information Both A and B side register data (G.826 and RSSI) is collected. Configuring a Protected XP4 variant for data collection, automatically configures the XP4 radios it manages. 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). Tracks both G.821 and G.826 performance data. Performance data (error ratio and error rate values) are collected from current value MIB objects without any additional processing. The performance value presents the values sampled from the radio at the end of each bin period; these sampled values can be viewed as a 15-min or daily bin.
Protected XP4
Eclipse INU
XP4 radio TRuepoint 5000, 4040, 4000, and 6400 Constellation
Microstar StarMAX Base Stations TNet Velox Sagem-Link SII SNMP Altium Radios ADR Radios
Does not support daily registers, so ProVision artificially creates daily registers by reading all 96 15-min bins once each day, and aggregating them into a single daily bin.
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.
5-12
Aviat Networks
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
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, lets 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
614-330055-001 February 2010
5-13
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 days 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 devices icon in the Tree and Map Viewer. Within 15 minutes, the first set of data is available for the History and Performance Trends windows.
5-14
Aviat Networks
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-17.
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:
Required Action Right-click the container XP4 radio icon. Expand the Eclipse Node to see link icons. Right-click the required link icon. Right-click the radio icon. 1. For DXR 100 &700 radios, access the 15-minute data via the DXR NET craft tool.
Other Aviat devices1
Device Type
Protected XP4 radio Eclipse Node
A device-dependant pop-up menu displays, as shown for an Eclipse link.
2. To enable 15-minute data collection, select the Radio 15-min Performance Data item. The radio icon is updated with the on the radio. icon and 15-min data collection is enabled
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-16
614-330055-001 February 2010
5-15
Enabling 15-Minute Ethernet Data Collection on page 5-17
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 devices 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 devices 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. 5. To close the window, select OK.
Related Topics:
5-16
Aviat Networks
Diagnostic and Performance Trends Analysis Procedures on page 5-4
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, and StarMAX base station 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:
614-330055-001 February 2010
5-17
1.
Select the device

Required Action Right-click the radio or plug-in icon. Expand the Eclipse Node so the plug-in icons are displayed. Right-click the required plug-in icon.
StarMAX Base Stations
Device Type
Eclipse IDU GE, IDU ES, IDU SPE Device DAC ES, DAG GE plugins
Right-click the device.
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-14. 3. To enable 15-minute Ethernet data collection, select the Ethernet 15-min Performance Data item. The radio icon is updated with the enabled on the radio. icon and Ethernet 15-min data collection is
4. To disable the Ethernet 15-min Data Collection, de-select the Ethernet 15-min Performance item. The radio. icon is removed, and Ethernet 15-min data collection is disabled for this
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 or StarMAX base station: 1. Right-click the selected DAC plug in or Base Station and select Performance >
5-18
Aviat Networks
Ethernet from the drop-down menu.
2. The Ethernet Performance window displays.
614-330055-001 February 2010
5-19
Table 5-6. Ethernet Performance Window Details Item

Summary Graphs
Description 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.
5-20
Aviat Networks
Item
Summary Parameters
Description 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 February 2010
5-21
Item
Graphical Tab
Description 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.
5-22
Aviat Networks
Item
Graphical Tab - Packet Types
Description 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 February 2010
5-23
Item
Graphical Tab - Throughput and Errors
Description Throughput and 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.
5-24
Aviat Networks
Item
Raw Tab Data
Description 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
Ethernet Bandwidth Utilization

Introduction
ProVision users can view the ethernet bandwidth use for: Eclipse regions and containers Eclipse devices Eclipse circuits StarMAX base stations
614-330055-001 February 2010
5-25
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 ports 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: 1.
> Ethernet Bandwidth from the drop-down menu.
Right-click the selected item or device. In the right-click menu, select Performance
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.
5-26
Aviat Networks
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 systems 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 February 2010
5-27
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
5-28
Aviat Networks
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 Time Scale Description 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 February 2010
5-29
Feature Data Graph
Description 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 Close
Click this button to Show or Hide the data graph. Click this button to close the screen.
Related Topic Viewing Ethernet Performance on page 5-18
Performance Features
This section covers the following topics: Performance History on page 5-30 Performance Trends on page 5-36 Performance Thresholds on page 5-40
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.
5-30
Aviat Networks
The performance history feature is supported in any device that collects performance data including: Eclipse Link Eclipse IDU EfficientSite XP4 Altium/ADR MicroStar DART Velox TNet TRuepoint: 5000, 4000, 4040, 6400, 6500 StarMAX base stations
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, then History from the drop-down menu.
614-330055-001 February 2010
5-31
3. The performance history for the selected device displays.
The features of the standard Performance History window are listed below:
Feature
Resolution Graph Summary bar
Description Select 15-Minute or Daily to display the desired level of detail for the data. 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.
5-32
Aviat Networks
Feature
G.826 or G.828 Data
Description 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 (RSL)
You can also view the RSL (receive signal level) for any time period from 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 February 2010
5-33
Feature
Report View
Description .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. Eclipse Radios with 4x or 6x RAC cards display a value for XPIC (Cross Polarized Interference Cancellation) XPD (Cross Polarization Discrimination). If no 4x or 6x RAC card is available, the phrase No Data displays. 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.
5-34
Aviat Networks
Feature
Save / Print
Description 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.
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. Closes the Performance History window.
Close
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 February 2010 5-35
EfficientSite Performance History Window

The EfficientSite 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.
Related Topic: Performance Trends on page 5-36 EfficientSite System View on page 5-90
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.
5-36
Aviat Networks
The performance trends feature is supported in any device that collects performance data, including: Altium Constellation (only 3DS3, 4DS3, and 155mbit) DART DVM Eclipse EfficientSite LE3000, LE3200 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 Radwin WinLink 1000, 2000 SPECTRUM II SNMP StarMAX base stations TNet TRuepoint: 5000, 4000, 4040, 6400, 6500 Velox XP4
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 February 2010
5-37
2. The Performance Trends window for the selected device displays.
The features of the Performance Trends window are listed below:

Feature
Parameters Pane
Description 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.
5-38
Aviat Networks
Feature
Chart Tab
Description 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. Select the Data Tab to display the raw data for the selected parameters. YOu can export the data using the Save Data feature.
Data Tab
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-40
614-330055-001 February 2010
5-39
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 Eclipse DAC Eclipse IDU Eclipse INU and INUe TRuepoint: 4000, 4040, 5000, 6400, 6500 XP4 Altium/ADR DART Velox TNet MicroStar StarMAX base stations
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. 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
2. The Performance Thresholds window for the selected device or container displays.
5-40
Aviat Networks
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 February 2010
5-41
in the information pop-up for the device/container.
TRuepoint 5000 and 4040 Performance Threshold Settings

The TRuepoint 5000 and 4040 Performance Threshold settings include 15-minute power performance collection options for: TX Level Threshold Seconds TX Level Max (dBm) TX Level Min (dBm) If selected as Performance Threshold settings, these values are shown in the Performance Trends and Performance History data for these radios.
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.
5-42
Aviat Networks
You need to set the Protection values for the Performance Thresholds to zero. Set the Working channels to your desired performance threshold values.
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 controls 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
614-330055-001 February 2010
5-43
stations 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 Device Name BS ID R6 Control R6 Data Datapath Type ASN-R Control ASN-R Data Path Type Paging Group Controller Value Name of the Base Station Identification of the Base Station. IP address of the R6 control. IP address of the R6 data path. Type of R6 data transmitted over the data path. IP address of the ASN-R controller for this base station. IP address of the ASN-R data path. Notes the specific Group Controller; if none is assigned, notes this.
Table 5-8. Mobility Neighbors Screen Column Device Name Container R6 Control Neighbor ID Value Name of the Base Station. Container that manages this Base Station in ProVision. IP address of the R6 control. Corresponds with the MAC address.
5-44
Aviat Networks
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.
614-330055-001 February 2010
5-45
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 SS MAC Address SS IP Address VLAN ID SS Connectivity Admin State Provisioned Deregistered Value Subscriber station MAC address. Subscriber station IP address. VLAN port ID. Connectivity status. Administration status. Provisioning status. Registered or deregistered status.
Table 5-10. Subscriber Station Details Item CIDs Values Basic CID - Basic WiMAX channel ID Primary CID - Primary WiMAX channel ID Radio SS Config Downlink Radio SS Config Uplink Uplink Channel Measurement Oper. FEC Code - Current FEC code in the downlink. Admin. FEC Code - Target FEC code in the downlink. Oper. FEC Code - Current FEC code in the uplink. Admin. FEC Code - Target FEC code in the uplink. CINR and RSSI for the uplink.
Table 5-11. Subscriber Station CPE List Column CPE MAC Address CPE IP Address Gateway Address CPE VLAN ID Value CPE MAC address. CPE specific IP address. CPE gateway address. VLAN identification for the CPE.
5-46
Aviat Networks
Column CPE VCI
Value VCI identification for the CPE.
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 Aviat devices can be accessed via a specific craft tool. Certain devices are accessed via diagnostic controls. Non-Aviat 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 Aviat Networks devices, associated craft tools and where to access help information.
614-330055-001 February 2010
5-47
Table 5-12. AviatAviat Networks Devices and Related Craft Tool Device Eclipse TRuepoint Craft Tool Portal TRuepoint Web CIT Craft Tool Manuals and Related Help Sources Eclipse User Guide (P/N 260-668066-001) TRuepoint 5000 & 4040 6-38 GHz Operators Interface (P/ N IMN-90303-E06) TRuepoint 6400 & 6500 Operators Interface (P/N IMN-907004-E01) MicroStar Constellation MicroStar Web CIT FarScan MicroStar Operators Interface FarScan for Windows Instruction Manual (P/N IMN-006120-E11), also see Diagnostic Controls for
Selected Devices on page 5-78.

All Altium ADR 2500 ADR 155c DXR Velox TNet DXR NET NCT TNet Web WMT
Online help is available from within the craft tool. A brief description is in WMT Craft Tool on page 5-51.
DXR NET NMT Installation and Operation Manual (PN IOM-NMS-2/2.4) NCT User Guide A brief description is in TNet Web Craft Tool and Diagnostics on page 5-54.
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 DVA CAU LE3000/3200 WL1000/2000 None: Diagnostic Controls instead CXTool See Diagnostic Controls for Selected Devices on page 5-78.
See LE3000 and LE3200 Craft Tool Installation on page 5-50.
5-48
Aviat Networks
Device Generic device
Craft Tool Telnet Browser
Craft Tool Manuals and Related Help Sources The Launch options displayed for a generic device are dependant on the information entered into the 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 radios 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.
614-330055-001 February 2010
5-49
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: Diagnostic and Performance Trends Analysis Procedures on page 5-4 LE3000 and LE3200 Craft Tool Installation on page 5-50 WMT Craft Tool on page 5-51 TNet Web Craft Tool and Diagnostics on page 5-54 XP4 Craft Tool and Diagnostics on page 5-66 Diagnostic Controls for Selected Devices on page 5-78
LE3000 and LE3200 Craft Tool Installation

Introduction
To be able to launch the LE3000 /LE3200 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 LE3000/3200 device is deployed. 2. Using the media provided by LE, on the ProVision Client PC, download and install the craft tool.
5-50
Aviat Networks
3. Open the ProVision Client. 4. Right-click on a LE 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 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 LE 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. icon. 2. Select the filters
3. In the Filters window, check the Severity checkbox. Then, select the Information
614-330055-001 February 2010
5-51
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.)
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.
5-52
Aviat Networks
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.
614-330055-001 February 2010
5-53
Related Topics: Diagnostic and Performance Trends Analysis Procedures on page 5-4
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: 1. Open 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.
5-54
Aviat Networks
Table 5-13. TNet Web Available Features with each TNet Device Device Icon Device
SPECTRUM I
Available Features Information, Save, Refresh Information, Save, Refresh
and
W Series and Protected W Series Classic II
Information, 4 Alarm Inputs, Save, Refresh Information, 6 Alarm Inputs, Save, Refresh Information, 8 Alarm Inputs, Save, Refresh Information, 8 Alarm Inputs, Save, Refresh Information, 8 Alarm Inputs, Save, Refresh Information, 8 Alarm Inputs, 4 Alarm Outputs, Save, Refresh
and and and
QUANTUM and Protected QUANTUM LC Series and Protected LC Series M Series and Protected M Series M Fiber
and
SPECTRUM II and Protected SPECTRUM II
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 February 2010
5-55
Launching the TNet Web Craft Tool

To launch TNet Web: 1.
Launch TNet Web.
From the Tree Viewer or Map Viewer right-click the required TNet radio. Select
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. If they are available, select the Alarm Inputs tab.
The Alarm Inputs tab and Alarm Outputs tab are only available on certain TNet devices.
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 57 for information on changing the input configuration.
5-56
Aviat Networks
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 57 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. 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
Name
Description User-defined name for the alarm input or output.
614-330055-001 February 2010
5-57
Item
State
Description 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 Inputs are: The severity options for Alarm Outputs are:
Current Status
Displays the current status of the input or output. Saves the input and output configuration to the radio. Refreshes the current screen by retrieving the current state of the inputs and outputs from the radio.
Save
Refresh
Related Topics: Diagnostic and Performance Trends Analysis Procedures on page 5-4 TNet Diagnostics on page 5-58
TNet Diagnostics
This section covers the following topics TNet Diagnostics - Protection Tab on page 5-59 TNet Diagnostics - G.821 Performance Tab on page 5-61 TNet Diagnostics - CB 149 Performance Tab on page 5-63 TNet Diagnostics - RSSI Tab on page 5-65 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.
5-58
Aviat Networks
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.
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.
614-330055-001 February 2010
5-59
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.
5-60
Aviat Networks
Parameter
Definition
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: TNet Diagnostics - G.821 Performance Tab on page 5-61 TNet Diagnostics - CB 149 Performance Tab on page 5-63 TNet Diagnostics - RSSI Tab on page 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.
614-330055-001 February 2010
5-61
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 Parameter
Available Seconds Unavailable Seconds
Definition Total available time during a measurement interval. Total unavailable time during a measurement interval. A one-second period with one or more errored blocks or at least one defect. A one-second period which contains at least 30% errored blocks or at least one defect. Total time of the measurement interval. Number of groupings of 60 available seconds, excluding severely errored seconds that have a BER worse than 10-6. 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)
Errored Seconds
Total Test Seconds Degraded Minutes
Time Stamp
The various functions in the G.821 Performance tab are defined below.
Table 5-17. Functions in the G.821 Performance Tab Parameter
Reset
Definition Resets all parameters to zero and sets the time stamp to the current day and time. 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. Closes the TNet Diagnostics window. 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. Saves the changes made to the performance parameters without closing the TNet Diagnostics window.
Refresh
OK Cancel
Apply
Related Topics: TNet Diagnostics - Protection Tab on page 5-59 TNet Diagnostics - RSSI Tab on page 5-65
5-62
Aviat Networks
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 Parameter
Single Errored Seconds
Definition The number of one-second periods with one errored block or defect. The number of one-second periods with more than one errored block or defect. The number of one-second periods which contain at least 30% errored blocks or at least one defect. The number of one-second periods that an Out-Of-Frame error is detected. 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
Multiple Errored Seconds
Frame Errored Seconds
Data Missing Indicator
Frame Error Count
The number of Out-of-Frame errors during a measurement interval.
614-330055-001 February 2010
5-63
Parameter
Total Parity Errors
Definition Contains an internal count used for calculating the bit error rate on Side A or Side B. Total number of seconds that have elapsed since test counters were last reset on Side A or Side B. 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)
Elapsed Seconds
Time Stamp
The various functions in the CB 149 Performance tab are defined below.
Table 5-19. Functions in the CB 149 Performance Tab Parameter
Reset
Definition Resets all parameters to zero and sets the time stamp to the current day and time. Collects the most updated values of the parameters from the radio, displays the updated values in the CB 149 Performance tab, and sets the time stamp to the current date and time. 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.
Refresh
Cancel
Related Topics: TNet Diagnostics - Protection Tab on page 5-59 TNet Diagnostics - RSSI Tab on page 5-65
5-64
Aviat Networks
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 Parameter
RSSI Low (dBm)
Definition The minimum signal strength recorded on Side A or Side B during the measurement interval. The maximum signal strength recorded on Side A or Side B during the measurement interval. The current signal strength level on Side A or Side B. The total minutes during which RSSI data has been collected, which encompasses the interval since RSSI data was last reset. 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)
RSSI High (dBm)
RSSI Current (dBm) RSSI Sample Time
Time Stamp
The various functions in the RSSI tab are defined below.

Table 5-21. Functions in the RSSI Tab Parameter
Reset
Definition Resets all parameters to zero and sets the time stamp to the current day and time.
614-330055-001 February 2010
5-65
Parameter
Refresh
Definition 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. Closes the TNet Diagnostics window. 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. Saves the changes made to the performance parameters without closing the TNet Diagnostics window.
OK Cancel
Apply
Related Topics: TNet Diagnostics - Protection Tab on page 5-59 TNet Diagnostics - G.821 Performance Tab on page 5-61 TNet Diagnostics - CB 149 Performance Tab on page 5-63 Diagnostic and Performance Trends Analysis Procedures on page 5-4
XP4 Craft Tool and Diagnostics

This section covers the following XP4 topics: Launching the XP4 Craft Tool on page 5-66 Launching the XP4 Diagnostics on page 5-67 Activating and Deactivating an XP4 Tributary Loopback on page 5-68 Activating and Deactivating an XP4 Local Loopback on page 5-72 Viewing/Changing XP4 Protection Settings on page 5-74 Resetting an XP4 Radio Device on page 5-77 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:
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. To launch the XP4 craft tool: 1. From the Tree Viewer or Map Viewer right-click the required XP4 radio. Select
Launch XP Web.
5-66
Aviat Networks
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 security access level. 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.
614-330055-001 February 2010
5-67
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.
Table 5-22. Tributary Loopbacks for XP4 Radios
Loopback Type Local Tributary Loopback applicable to: 2/4/8x radios 16x E3/DS3 radios
Loopback Purpose To locate faults in equipment and cable connections to the local IDU. The Local loopback does this by routing each tributary input (data from customer) directly to the corresponding tributary output (data to customer). Any combination of tributaries can be configured for loopback. The following diagram shows a local tributary loopback signal path:
Remote Tributary Loopback applicable to: 2/4/8x radios 16x E3/DS3 radios
Remote tributary loopback tests enable you to confirm link operation with the aid of a connected BER test-set. This loopback is used for locating faults in equipment and cable connections by connecting the transmit data stream directly to the receive data stream in the remote IDU. It checks the functionality of 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:
5-68
Aviat Networks
Loopback Type Remote SU E3/DS3 Tributary Loopback applicable to: 16x E3/DS3 radios
Loopback Purpose The Remote SU loopback locates faults in equipment and tributary 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 the functionality of the local and remote sides in both directions. 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:
Local MSU E3 Tributary Loopback applicable to: 16x E3/DS3 radios
To ensure the MSU is getting a signal from customer equipment. The local MSU E3 loopback feeds the output of the multiplexer into the demultiplexer in the MSU, looping all tributaries between 1 and 16 at the local side.
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 Loopback applicable to: 16x E3/DS3 radios
To ensure the MSU is getting a signal from customer equipment. The local MSU E13 loopback feeds the output of the multiplexer into the demultiplexer in the MSU, looping all tributaries between 1 and 16 at the local side.
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:
614-330055-001 February 2010
5-69
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. 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.
5-70
Aviat Networks
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.
8. To accept the changes, select OK.
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.
614-330055-001 February 2010
5-71
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 XP4 radio, the following message displays.
Related Topics: Activating and Deactivating an XP4 Local Loopback on page 5-72 Activating and Deactivating an XP4 Local Loopback on page 5-72
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 radios site to manually deactivate the loopback.
Table 5-23. XP4 Local Radio Loopbacks Local Loopback ODU Analog Loopback Purpose 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:
5-72
Aviat Networks
Local Loopback ODU RF
Loopback Purpose
Note: Note: This loopback is only available on 23-38 GHz XP4 Plus radios but is standard for the XP4 Classic radios. 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: 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.
614-330055-001 February 2010
5-73
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-74
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
5-74
Aviat Networks
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 radios protection settings: 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. 3. Select the Protection tab. The radios 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.
614-330055-001 February 2010
5-75
Table 5-24. Protection Tab Fields for the XP4 Radio Protection Tab Fields Protection Type Description 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 Hot Standby Space Diversity] Frequency Diversity Dual Link X X 8x X X X 16E1,E3,DS3 X 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-77 Activating and Deactivating an XP4 Tributary Loopback on page 5-68
5-76
Aviat Networks
Resetting an XP4 Radio Device

Introduction
Normally, you would reset individual XP4 radio components if recommended by Aviat 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 radios 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 radios 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:
614-330055-001 February 2010
5-77
Activating and Deactivating an XP4 Tributary Loopback on page 5-68
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 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.
Diagnostics. The Diagnostic Controls screen displays.
Right-click on the selected device. In the right-click menu, select Faults >
5-78
Aviat Networks
2. Control status is shown through use of color: Green On = Control Active Green Off = Control Inactive Gray = Not Available 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 Loopbacks Enable or disable loopback controls for DS3, local or remote 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.
614-330055-001 February 2010
5-79
Protection Tab
Table 5-27. Constellation Protection Tab Values Item TX Online Status LEDs Switch Control Shows whether TX1 or TX2 is in operation for Side A and Side B. Enables the user to switch TX traffic to the TX that is not in use. 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: Note: This is a safer TX switch operation than the TX Lock, which locks traffic onto an alarmed TX. Switch data is not displayed for Constellation for FarScan devices.
Protection Controls TX / RX M12 Standby MI2 Release Enables protection locking or unlocking of TX, RX, M12, and HLM. To adjust, select Locked or Unlocked from the drop-down menu. Locks the selected M12 traffic onto the M12 Standby card.
Note: This lock is over-ruled if the locked M12 becomes absent.
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. 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.
HLM Lock
5-80
Aviat Networks
BER Test Side A and B Tabs
Table 5-28. BER Test A and B Tab Values Item Results Duration Results of the BER test for a trib. 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 Test Duration Results of the CBER/UBER test for Side A and Side B. 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.
614-330055-001 February 2010
5-81
RCS Alarm Clear Tab
Table 5-30. RCS Alarm Tab Values Item RCS to TX Switch Alarms RCS to HLM Switch Alarms To clear an RCX to TX Switch alarm, select Clear from the drop-down menu. To clear an RCX to TX Switch alarm, select Clear from the drop-down menu.
Note: This option is not available for Constellation for FarScan devices.
Relays Tab
Table 5-31. Constellation Relay Tab Values Item External Relays To adjust an external relay, select Reset or Set from the drop-down menu.
5-82
Aviat Networks
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: 1.
2. Select the Control Activation option: Global Activation on Apply Activate Immediately 3. Control status is shown through use of color: Green On = Control Active Green Off = Control Inactive Gray = Not Available 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. 6. To refresh the data from the device, click Refresh. 7. To exit the screen, click Close.
614-330055-001 February 2010
5-83
Table 5-32. CAU Control and Alarm Values Item Control Relays Alarm Relays View and Change Shows status of control relay connections. To adjust, select Reset or Set from the drop-down menu. Shows status of alarm relay connections. To adjust, select Reset 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: 1.
2. To adjust a tributary loopback, see Activating and Deactivating DART Tributary Loopbacks on page 5-85. 3. To reset the radio, select the Resets tab. In this tab, select the drop-down arrow to display the radios devices.
4. Select Reset NMI from the drop-down menu, then select Reset. A message displays:
5. To apply changes, click Apply.
5-84
Aviat Networks
6. To refresh the data from the device, click Refresh. To exit the screen, click Close.
Access to the Diagnostics menu option is dependant on your ProVision security access level.
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 Local Loopback Loopback Purpose To locate faults in equipment and cable connections to the local 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 loopback
To locate faults in equipment and cable connections by 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:
614-330055-001 February 2010
5-85
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. 7. To accept the changes, select OK.
5-86
Aviat Networks
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: 1. Right-click on the selected device. In the right-click menu, select Faults >
614-330055-001 February 2010
5-87
2. Select the Control Activation option: Global Activation on Apply Activate Immediately 3. Control status is shown through use of color: Green On = Control Active Green Off = Control Inactive Gray = Not Available 4. To reset relay controls, use the drop-down menus. 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. 6. To refresh the data from the device, click Refresh. 7. To exit the screen, click Close.
Table 5-34. DVA Controls Values Item MC1, 2, and 3 Relays External Relay View and Change To adjust, select Reset or Set from the drop-down menu. Select the external relay option that you want to view from this drop-down menu. Then, click Refresh. The values for that option display.
Diagnostic Controls
The diagnostic controls enable you to view and change loopback controls and status for specific relays. 5-88 Aviat Networks
Procedure
To access and change diagnostic controls: 1.
2. Control status is shown through use of color: Green On = Control Active Green Off = Control Inactive Gray = Not Available 3. To reset loopback controls, on the Tributaries tab, use the drop-down menus. 4. 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. 5. To refresh the data from the device, click Refresh. Wait for the data to be updated. 6. To exit the screen, click Close.
Table 5-35. Controls Item Tributaries tab Loopback Controls 3XDS3 Loopback Status Wayside Loopback Status External Relay Enable or disable loopback controls for tribs. Notes the status for each trib on each channel. Notes the wayside loopback status of tribs and 3xDS3 connections. 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 February 2010
5-89
EfficientSite System View

Introduction
The Aviat EfficientSite is an intelligent controller based system. It reduces the energy costs associated with operating telecommunications sites. The EfficientSite system is supported by ProVision through a rich set of Fault, Configuration, and Performance management features. The EfficientSite functions in ProVision enable users to: View EfficientSite Data - View the Energy status and activity for an EfficientSite, 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. Launch Windows Applications for EfficientSites in ProVision - Associate third party software with the ProVision interface of the EfficientSite. Multiple sites can be deployed through ProVision. When an EfficientSite is deployed in ProVision, it displays in two ways. The EfficientSite, and all its components, are displayed in the Tree Viewer. The components show what devices are included in the installation. The site details and status are displayed in the EfficientSite screen.
Figure 5-7. EfficientSite Details in the Tree Viewer
5-90
Aviat Networks
Figure 5-8. Sample EfficientSite Screen
The EfficientSite management function in ProVision is a licensed feature. To obtain the separate license and enable this feature, contact your Aviat representative.
View EfficientSite Data

1. Deploy the EfficientSite in ProVision. For instructions, see EfficientSite Deployment on page 3-30. 2. Navigate to the EfficientSite in the Tree Viewer or Map View. Right-click on it and select Open Device. 3. The EfficientSite screen displays, showing the status for the selected site. This is automatically updated every 3 minutes. To update this status, click Refresh.
Table 5-36. EfficientSite Screen and Item Status Item Energy The following values are present if related devices are present:
614-330055-001 February 2010
5-91
Item Batteries Fuse Status Current voltage Charge mode - charging or discharging Fuel Tank Lid Probe Fail Average consumption per hour Volume % of fuel tank Remaining liters in fuel tank Generator Grid Generator status, Off or On. AC Mains AC Phase Frequency Delay Surge Fail Total Power Rectifier Fail Use Load Fail Shelter The following values apply to all Shelter views: Humidity Temperature DC Power Total AC HVAC Fan DC Fail Relative humidity reading inside enclosed site areas. Temperature readings inside enclosed site areas. Analog Input reading. Device status noted. Device status noted. Device status noted. Device is On. Device is Off. Device is in its Normal state. Device has an Event or problem. The following values are present if related devices are present:
5-92
Aviat Networks
Item Controls 12VDC Fail AWL Door Modem Fail Panic Smoke DC Voltage Fan DC Current DC Power DC HVAC Voltage value. Fail - status noted mA of current. Watts of power. NO FAIL STATUS?
Windows Applications for EfficientSites in ProVision

Administrator-level users can set up EfficientSite windows applications to launch from an EfficientSite displayed in ProVision. Multiple applications can be installed for each EfficientSite.
For each application to be used, the craft tools need to be installed on each individual client. Note the system location where the installation files are saved, for use in the launch configuration procedure.
Procedure
1. In ProVision, set up the EfficientSites. 2. On the Client, install the EfficientSite craft tool or tools. 3. Log into ProVision at the NOC engineer or system administrator level, i.e., using the NOC engineer or administrator user name and password. 4. In the Tree Viewer, locate a EfficientSite that you want to connect with craft tools. Right-click on its icon. In the right-click menu, Applications > Edit Applications displays. Click on Edit Applications. The Edit Applications screen displays. 5. To add a new Application for this EfficientSite, click Add. A new line appears in the screen. Double-click in the fields to enter the following values: Name - Enter the name of the craft tool application. Executable Path - Navigate to the location of the Generic Device craft tool executable file (.exe) for this Generic Device. Select the .exe file.
614-330055-001 February 2010
5-93
Parameters - Customize the .exe file with command line parameters. This specifies the Generic Device object attributes that are applied to the Windows executable when it is launched from ProVision.
6. To enter additional Applications, click Add again. You can save multiple Applications for each device, as shown. 7. The right-click menu for the EfficientSite now displays Applications >(Craft Tool Names). The craft tools are also displayed as buttons at the top of the EfficientSite screen.
8. To open a craft tool, click on its button.The selected craft tool opens for the device. 9. If you need to update the craft tool link, click on Applications > Edit Applications again. This re-opens the Edit Applications screen. Make changes to the craft tool link from this screen.
Related Topics:
EfficientSite Deployment on page 3-30 Performance History on page 5-30
5-94
Aviat Networks
Device and Network Reports

This section includes procedures for: Inventory Reports on page 5-95 Eclipse Fault Report on page 5-101 Eclipse Capacity Report on page 5-103 Network Health Reports on page 5-108
Inventory Reports
This section describes the various options for viewing the inventory report for any of the following device types: Eclipse TRuepoint Constellation LE3000 / LE3200 StarMAX base station The options are: View the Inventory Reports on page 5-96 Save an Inventory Report for a Single Device on page 5-98 Save an Inventory Report for Multiple Devices on page 5-100 Eclipse Fault Report on page 5-101 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.
614-330055-001 February 2010
5-95
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.
View the Inventory Reports

To view the Inventory Report for a single Eclipse, TRuepoint, Constellation, or LE3000/3200 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.
5-96
Aviat Networks
Table 5-37. Inventory Details Feature Report Description Lists the inventory details The inventory details for the Eclipse INU/INUe include: Inventory Report General Information Active License Certificate Details License Nodal Details License Feature Details Manufacturing Details The inventory details for the Eclipse IDU include: Inventory Report General Information Manufacturing Details The Eclipse IDUs, except for IDU ES (Connect ES), do not have license details since the IDU has no capacity licence. The inventory details for the TRuepoint 6500 include: Inventory Report General Information Manufacturing Details 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. Collected On - The date and time when the data for this report was collected. 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 any RAC plug-in user licence. For more information on the Eclipse radio inventory details (such as capacity and modulation) see the Eclipse User Manual, 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. License Nodal Details License Feature Details If applicable, lists the RAC plug-in and capacity for any nodal licenses. If applicable, lists all featured licenses by RAC plug-in, part number, and whether or not the feature license is present (Yes or No).
614-330055-001 February 2010
5-97
Feature
Description 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 From Radio Save Report Close
Refreshes the data in the window with the information from the radio. If you refresh the inventory from the radio it updates the database and the inventory report is read from the database. Saves an inventory report as a text file. Closes the Inventory window
Next Topic: Save an Inventory Report for a Single Device
Save an Inventory Report for a Single Device

You can save a devices 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.
5-98
Aviat Networks
3. The Inventory Report displays.
If there is no data to generate the report, a message will display. 4. Select Save Report. A directory browser displays. Browse to the required folder, then enter a file name. 5. 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 radios Active License Certificate Details. filename_mfg.txt: Lists the radios Manufacturing Details. 6. 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
614-330055-001 February 2010
5-99
Save an Inventory Report for Multiple Devices

You can save the inventory details from a group of Eclipse, TRuepoint, Constellation, or LE3000/3200 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 .)
5-100
Aviat Networks
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: filename_lic.txt: Lists the radios Active License Certificate Details. filename_mfg.txt: Lists the radios Manufacturing Details.
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
614-330055-001 February 2010
5-101
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 radios performance.
Procedure
To view a fault report for an Eclipse radio: 1. Right-click the Eclipse icon and select Reports, then Fault 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. Next Topic: Eclipse Capacity Report
5-102
Aviat Networks
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 Capacity 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 Aviat to acquire this license.
The Capacity Report is created using daily performance data from the ProVision database, excluding invalid data. Daily performance data in the database is required for Capacity Report output.
Procedure
To view a capacity report for an Eclipse radio or for a complete Eclipse network: 1. Right-click the Eclipse icon and select Reports, then Capacity from the right-click menu.
614-330055-001 February 2010
5-103
2. The Capacity Report window displays for the selected data.
If there is no data to generate the report, a message will display. 3. Select the Save Report button to save the report as a .txt 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 Capacity Report Generated On Collected On General Information Active License Certificate Details Capacity Details License Feature Details Description Lists the day/time stamp when the report was generated. The date and time when this report was generated. The date and time when the data for this report was collected. Lists the device name, site name, device IP address, device type, and backplane maximum Lists the serial number, status (active or inactive), and licensed capacity for each RAC plug-in user licence.
Lists the capacity details for each RAC plug-in installed in the radio or network. See the tables below for specific definitions, for both individual radio and network Capacity Reports. Lists all featured licenses by RAC plug-in, part number, and whether or not the feature license is present (Yes or No).
5-104
Aviat Networks
Feature Refresh from Radio Save Report
Description Refreshes the data in the window with the information from the radio. 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

RAC Licensed Capacity Backplane Equivalent Hardware Used Licensed Spare Hardware Spare Hardware Unlicensed
Description The name of this RAC plug-in The amount of capacity licensed for this RAC. The total capacity that this radio can support. The maximum capacity that this hardware can support. The capacity currently used by traffic by this plug-in. The amount of capacity licensed for the RAC spare. Maximum capacity of the RAC spare. This indicates the capacity for unlicensed hardware. It is 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

Path Serial Number Device Type Backplane Max Licensed Capacity Backplane Rate Backplane Equivalent Hardware
Description Network path to this radio. Serial number for this radio. The radio type, IDU, INU, or INUe. The total maximum capacity The amount of capacity licensed for this radio. Transmission rate for this radio. Backplane equivalent for this radio. The maximum capacity that this hardware can support.
614-330055-001 February 2010
5-105
Feature
Used Licensed Spare Hardware Spare Hardware Unlicensed
Description The capacity currently used by traffic by this plug-in. The amount of capacity licensed for the RAC spare. Maximum capacity of the RAC spare. The difference between licensed capacity and the hardware capacity. This license may be made available if licensing is extended.
Next Topic: View / Save / Delete Server Reports on page 5-106
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-106
Aviat Networks
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: filename_lic.txt: Lists the radios Active License Certificate Details. filename_mfg.txt: Lists the radios Manufacturing Details. 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 Save an Inventory Report for a Single Device
614-330055-001 February 2010
5-107
Network Health Reports

With ProVisions 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 all Aviat devices that support G.826 or other performance collection, including: Eclipse Eclipse circuits TRuepoint (all variants) Altium (all variants) Constellation (only 3DS3, 4DS3, and 155mbit) DART LE3000 and LE 3200 Radwin WinLink 1000 and 2000 SPECTRUM II (all variants) XP4 (all variants) Logical Containers 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.
5-108
Aviat Networks
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.
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 an object for the report by right-clicking on it and selecting Reports - Network Health or 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
614-330055-001 February 2010
5-109
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.
5-110
Aviat Networks
Network Health Report - Overview Tab

This data is included in both the PDF and XLS formats for this report.
Value Report Data Description 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. 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%. Displays the average availability for all valid performance data over the reporting period Displays the average visibility of the network able to be viewed by ProVision for this report. Number of devices in this report. Number of devices that are operating at or above threshold. Number of devices that are operating below the availability threshold. Number of devices that are not providing any data. A pie graph comparing the number of healthy devices with the number of devices below threshold. A graph showing the % of network availability over the past 60 days. Mouse over the bar for a specific day to view its % of availability and visibility.
Visibility
Mean Availability Mean Visibility Number of Devices Devices at/above threshold Devices below threshold Devices with Zero Visibility Device Availability Chart Breakdown by Day Chart
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 Detail Level - Low Device Device name and network location. Description
614-330055-001 February 2010
5-111
Value Remote Radio Mean Availability Mean Visibility RSL Mean RSL Max RSL Min Detail Level Medium G.826 Available Seconds G.826 Unavailable Seconds G.826 Errored Seconds G.826 Severely Errored Seconds
Description The radio linked to the main device. % availability of the network. The % of the network able to be viewed by ProVision for this report. The mean for the Receive Signal Level value. The maximum Receive Signal Level value. The minimum Receive Signal Level value.
A count of the number of available G.826 seconds since the report Start. A count of the number of unavailable G.826 seconds since the report Start, a good indicator of system problems. A count of the number of errored seconds since the report Start. An errored second is a one-second period with one or more errored bits. A count of the number of severely errored seconds since 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 Seconds G.826 Errored Blocks G.826 Background Block Errors XPIC XPD The number of seconds that an Out Of Frame error is detected. A block of data where one or more bits of data are in error. An errored block not occurring as part of an Severely Errored Seconds set. XPIC (Cross Polarized Interference Cancellation) XPD (Cross Polarization Discrimination). This is the value before data is input to the RAC. If this value is less than 20 dB, the or more than 50 dB, the related antennas must be realigned.
5-112
Aviat Networks
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 Network Events Values
Device Event Time Severity Acknowledged
614-330055-001 February 2010
5-113
5-114
Aviat Networks
Index
Numerics
15-minute data collection enabling and disabling 5-14 for DAC 5-17 forStarMAX 5-17
B
Backups Eclipse 3-113 menu functions 2-15 StarMAX 3-113 Browser launching from device 5-48 to access non-Aviat devices 5-47 Bulk Configuration definition 3-68 delete 3-75 setting up 3-68 settings 3-71
A
about i-ii Acknowledging network events 4-9 Activating DART tributary loopback 5-85 Eclipse radio software 3-93 Eclipse software 3-93, 3-102 managed status for a device 3-47 StarMAX software 3-108 TRuepoint software 3-105 XP4 tributary loopback 5-68 XP4 tributary loopback, local 5-72 Adding logical link 4-70 prefilters 4-36 ADR deploying 3-11 icon 2-22 view plug-ins for 3-64 Alarms conditions activating XP4 protection 5-75 icons and 2-48 link to performance criteria 5-40 manually resynchronize 4-14 manually resynchronize for TR 6400 4-15 TNet inputs and outputs 5-57 Altium 2-22 configuration view 3-62 craft tool 5-47 craft tool instructions 5-51 data collection 5-12 icon 2-22 Network Health Report 5-108 security log entries 4-45 Altium MX 2+0 2-22 icon 2-22
C
CAUs customize event names 4-17 deploying 3-24 diagnostic controls for 5-83 CB 149 view TNet performance for 5-63 Changing event browser options 4-26 password 2-4 TNet device subnet 3-79 XP4 protection settings 5-74 Chassis Views see Equipment Views 2-34 Circuit Diagnostics 5-4 end-to-end tests 5-10 options 5-10 segment tests 5-10 set up test 5-8 Circuit Trace circuit features 3-84 definition 3-81 required for diagnostics 5-5 running 3-82 single circuit 3-87 Circuits Circuits tab 2-25 definition 3-81 delete 3-92 diagnostics 3-91, 5-4 diagnostics window 5-5 1
614-330055-001 February 2010
event browser for 3-90 retrace 3-91 trace required for diagnostics 5-5 tracing 3-81 Class Checking 3-14 invalid deployment if not performed 3-15 Clear Correlation definition 4-13 Clearing network events manually 4-13 Community String definition 3-9 Computer Equipment display resolution on monitor 2-2 Configuration save as .CSV file 3-61 view radio 3-61, 3-68 viewing a radios 3-61 Configuration Alarm Units deploying 3-24 Configuration Profiles bulk configuration 3-68 creating 3-68 delete 3-75 executing 3-70 menu functions 2-14 overview 3-68 reading 3-69 settings 3-71 Configuring Constellation 3-22 DXR 200 radios 3-52 DXR SMAs 3-52 event notification rules 4-53 protected TNet links 5-59 Consider 4-80 Constellation configuration viewer 3-63 configuring 3-22 deploy new 3-22 diagnostic controls for 5-78 equipment view 2-34 equipment views 2-33 Inventory Report 5-95 Network Health Report 5-108 resync alarms 4-14 Contact Details for users 2-5 Containers adding 3-6 creating 3-5, 3-6
deleting 3-8 renaming 3-7 Craft Tools about 5-47 DXR NET 5-47 enabled functions 5-49 launching 5-49 LE3000 5-50 list of available 5-47 NCT 5-48 overview 5-3, 5-47 Portal 5-47 TNet Web 5-48 TNet Web details 5-54 WMT 5-47 WMT details 5-51 XP Web 5-48 Creating configuration profile 3-68 RF links 3-54 RF links from Find 3-56 RF links from Tree Viewer 3-54 scoreboard 4-76 Scoreboard Group 4-74 scoreboard groups 4-74 scoreboards 4-76 Customer contact details viewing 2-7 Customizing 2-42, 4-23 event browser 4-23
D
DAC Plug-Ins enabling data collection 5-17 view ethernet performance 5-18 DART activate tributary loopback 5-85 configuration profile settings 3-73 configuration view 3-62 diagnostics 5-84 icon 2-22 local trib loopback 5-85 loopbacks 5-84 remote trib loopback 5-85 DART NMS Trap Destination 3-73 Data collection 5-11 event data 3-48 into usable information 1-3 managing over time 1-3
Aviat Networks
Data Collection 15-minute collection 5-14 about 5-11 change device status for 5-16 DAC plug-in 5-17 daily 5-13 ethernet performance data collection 5-17 menu functions 2-15 overview 5-11 performance monitoring data 5-11 RSSI data 5-11 StarMAX base stations 5-17 Database backup via menu 2-15 locking 2-2 purging 2-15 searching 2-43 Deactivating an XP4 Tributary Loopback 5-72 Deleting circuits 3-92 container 3-8 device from a service 4-67 devices 3-45 event browser 4-30 event notification rule 4-52 event prefilter 4-43 logical links 4-71 pre-filtering 4-43 radio frequency links 3-59 Scoreboard Group 4-75 scoreboards 4-80 server reports 5-106 service 4-68 Dependencies deploying, devices 3-3 managing, devices 3-3 managing, events 4-3 Deploying 3-5 class checking for Eclipse 3-14 Constellation 3-22 containers 3-5 definition 3-1 devices 3-3 DXR 200 3-36 DXR SMA 3-36 Eclipse node 3-13 EfficientSite Manager 3-31 generic SNMP device 3-25 MegaStar 1+1 3-12, 3-25 MegaStar MN 3-12 multiplex radios 3-11 614-330055-001 February 2010
network autodiscovery 3-38 prerequisites 3-3 process overviews 3-3 Protected radios 3-11 SMA device 3-36 SNMP devices 3-9 StarMAX 3-29 TNet device into proxy manually 3-35 TNet devices 3-31 TNet proxy 3-34 TNet troubleshooting 3-34 TRuepoint devices 3-15 WiMAX 3-29 Device Software activating after upload 3-102 Devices apply pre-filter for events to 4-40 change data collection status 5-16 configuration view 3-61, 3-68 deleting 3-45 deleting from service 4-67 deploying prerequisites 3-3 managing 3-47 object pop-ups 2-50 rename 3-44 reset XP4 5-77 services overview 4-65 sleep status 4-18 states 2-50 unmanaging 3-50 Diagnostic Controls about 5-78 CAU 5-83 Constellation 5-78 DART 5-84 DVA 5-87 MegaStar 5-88 using 5-78 when applied 5-47 Diagnostics circuits 3-91 Disabling 15-minute data collection 5-14 Discovering DXR 200 radios 3-52 DXR 700 radios 3-52 RF links 3-58 TRuepoint 6500 configurations 3-51 Display Resolution 2-2 DVA diagnostic controls for 5-87 3
DXR craft tools 5-47 icon 2-22 DXR 200 configuration view 3-62 deploying 3-36 managing 3-52 view plug-ins for slots 3-64 DXR 700 configuration view 3-62 icon 2-22 manually discover 3-52 DXR SMA deploying 3-36 managing 3-52
E
Eclipse backup configuration of 3-113 deploy via autodiscovery 3-38 ethernet bandwidth use 5-25 network autodiscovery 3-38 Network Health Report 5-108 security log entries 4-45 Eclipse configuration 3-113 Eclipse Ethernet Port Settings DAC ES 3-72 Eclipse Ethernet Port Settings DAC GE 3-73 Eclipse Ethernet Port Settings for IDU ES 3-71 Eclipse Ethernet Priority Mapping for DAC GE 373 Eclipse Ethernet Priority Mapping for IDU ES 371 Eclipse License menu functions 2-13 Eclipse NMS Traps Destination 3-71 Eclipse Node deploying 3-13 license, installing 3-110 menu functions 2-13 Eclipse Optimization Gateway view plug-ins for 3-64 Eclipse OSPF Settings 3-72 Eclipse Radios bulk configuration settings 3-71 circuit tracing 3-82 data collection 5-12 deploying INU, INUe, or IDU 3-14 deploying protected node 3-14 radio frequency links, creating 3-57 remotely upgrading software 3-93
view plug-ins for 3-64 Eclipse Reports fault report 5-101 inventory report 5-95 Eclipse Software 3-93 activating 3-102 load onto radios 3-99 loading example 1 3-95 registering on server 3-96 remote upgrade 3-93 upgrade process 3-94 Eclipse Time Server Settings 3-72 Eclipse Time Zone Settings 3-72 Editing performance data status 5-16 scoreboard 4-79 Scoreboard Group 4-75 EfficientSite Manager Deploying 3-31 deploying 3-30 using 5-90 Enabling 15-minute data collection 5-14 Equipment Malfunctions identifying 5-1 Equipment Views about 2-33 opening 2-34 Ethernet performance data collection 5-17 view performance 5-18 Ethernet Bandwidth Utilization 5-25 Event Browser about 4-20 acknowledge events from 4-10 customization filters 4-24 customizing 4-23 deleting 4-30 description 2-40 filtering event logs 4-33 hide 2-10 maximum events 2-40 navigating 4-20 new, opening 2-12 opening 4-20 option settings 4-26 option settings, values 4-28 overview 4-20 pop-up menu for events 2-42 printing 4-32 resize 2-10
Aviat Networks
save settings in 2-42 save to file 4-31 save view 4-22 saving 4-22 security log, opening 2-12 view saved 4-23 viewing 2-42 Event Log about 4-33 deleting pre-filter 4-43 filtering overview 4-33 modify pre-filter 4-41 object level pre-filter 4-39 objects to be pre-filtered 4-35 pre-filter from Event Browser 4-40 pre-filtering view 4-35 root level pre-filter 4-36 Event Notification adding rule 4-49 configuring rule 4-53 delete rule 4-52 dialog box 4-58 editing rule 4-49 email notification setup 4-55 overview 4-47 pop-up message notification setup 4-57 preferences 4-47 script execution setup 4-62 Event Pre-filter definition 2-13 Event Properties probable cause tab 4-8 viewing 4-7 Event States acknowledged 4-6 cleared by ProVision 4-6 cleared by user 4-6 clearing 4-6 unacknowledged 4-6 Event Status network events 4-5 Event Traffic verifying 3-48 Events customize names 4-17 manually resynchronize alarms 4-14 manually resynchronize TR 6400 alarms 415 prefiltering 4-36 prefilters delete 4-43 614-330055-001 February 2010
modify 4-41 severity color coding 2-50 states 4-5 verifying receipt of 3-48 viewing 4-6 viewing prefilters 4-35 Exceptions logging in 2-3 user session 2-3 Exiting user session 2-4
F
Fault Report Eclipse 5-101 Filtering event logs 4-33 events at input 4-35 Flat Map 2-27
G
G.821 view TNet performance for 5-61 G.826 Performance Data identify problems for device 5-33 performance history 5-33 view trends for 5-36 Generic Devices customize event names 4-17 deploying 3-25 interface view 2-40 Graphics map background 2-30
H
Hardware for radio 3-67 Help online 2-8 Hierarchical Map map background graphic 2-30 Highlight 4-28 History of performance 5-30 How ProVision works 1-2
I
Icons 2-22
ADR 2-22 Altium MX 2+0 2-22 caution 0-4 Container icons 2-21 DART 2-22 DART protected 2-22 display and status 2-48 DXR 2-22 DXR 700 2-22 DXR 700 protected 2-22 DXR protected 2-22 event severity color codes 2-50 information 2-48 note 0-4 reading data for 2-49 Velox 2-23 warning 0-4 XP4 16/E3/DS3 2-23 XP4 16/E3/DS3 remote 2-23 XP4 16/E3/DS3 remote protected 2-23 XP4 2/4/8x 2-23 XP4 2/4/8x protected 2-23 XP416/E3/DS3 protected 2-23 Increase TNet Proxy subnets 3-79 Installing Eclipse node license 3-110 Interface Views definition 2-40 InterfaceViews opening 2-40 Inventory Report 5-95 about 5-95 saving 5-98 saving, multi-radio version 5-100 viewing 5-96 IP Address change for TNet Proxy 3-79 menu functions 2-13 searching for 2-45 view/change for network 3-76
security log entries 4-45 License Eclipse Node 3-110 evaluation 2-6 menu functions 2-13 permanent 2-6 viewing details 2-6 Link creating 3-54 non-protected 3-57 protected 3-57 ring-protected 3-57 Loading Eclipse software 3-93 Local Loopback DART 5-85 Logging In 2-2 exceptions 2-3 multiple users 2-2 Logging Off 2-4 Logging Out 2-4 Logical Links creating 4-70 deleting 4-71 renaming 4-70 Loopback Test DART 5-84 run 5-8 set up 5-8 XP4 radio 5-67
M
Managing definition 3-1 description of 3-47 devices 3-47 DXR 200 radios 3-52 DXR SMAs 3-52 event dependencies 4-3 event scenarios 4-72 events, overview of 4-1 radios prerequisites 4-3 removing from device 3-50 Managing Events network events 4-5 prerequisites 4-3 sources of event data 4-1 suggested process 4-2 when to 4-1
L
Launching craft tools 5-49 LE3000 craft tool, installing 5-50 interface view 2-40 Inventory Report 5-95 Network Health Report 5-108
Aviat Networks
Manually Clearing Events 4-13 Map Viewer description 2-26 Flat Map 2-27 hide 2-10 map background graphic 2-30 overview 2-26 Physical view 2-26 properties 2-28 repositioning objects 3-43 resize 2-10 submaps 2-32 tools 2-28 visible object types 2-26 Maps backgrounds, add 2-31 backgrounds, remove 2-31 moving objects 3-43 MegaStar diagnostic controls for 5-88 equipment view 2-34 equipment views 2-33 resync alarms 4-14 MegaStar 1+1 deploying 3-12, 3-25 MegaStar MN deploying 3-12 Menus 2-11 main user interface 2-11 menu items 2-11 pop-up menus 2-17 MicroStar deploying 3-12 Mobility Neighbors view for WiMAX 5-43 Modifying event prefilters 4-41 scoreboard groups 4-75, 4-79 Moving 3-43
overview 4-5 status of 4-5 unacknowledging 4-11 Network Failure identify 5-30 Network Health Report about 5-108 device types 5-108 values 5-111 viewing 5-109 NOC engineer role 0-1 operator role 0-1 Notification Dialog Box 4-58
O
Objects pre-filtering activated 4-35 pre-filtering icon 4-35 repositioning 3-43 repositioning in map 3-43 Online Help 2-8 opening 2-8 terminology 0-4 using 2-8
P
Packets displayed in Ethernet performance view 5-21 Passwords changing 2-4 Path Degradation identifying 5-1 Performance Analysis overview 1-3 Performance Data 15-minute collection 5-14 daily 5-13 Ethernet 5-17 Performance Data collection screen 5-16 performance history 5-30 performance thresholds 5-40 performance trends 5-36 report view for device 5-34 Performance History TRuepoint 6500 specific 5-35 Performance Monitoring data collection 5-11 Performance Threshold
N
Naming Standards 3-2 Navigating Event Browser 2-40 menu bar 2-11 Network 4-5 IP addresses 3-76 Network Events acknowledging 4-9 clearing 4-13
614-330055-001 February 2010
about 5-40 TRuepoint 6500 specific 5-42 Performance Trends 5-36 Physical Map 2-26 Plug-Ins view for Eclipse radios 3-64 Pop-Up Data via Tree Viewer 2-50 Pop-Up Menus about 2-17 Portal craft tool 5-47 craft tool table 5-3 Pre-Deploying 3-3 Prefilters adding 4-36 viewing 4-35 Prerequisites event management 4-3 for deploying devices 3-3 managing, radios 4-3 system diagnostics 5-1 Printing 4-32 event browser data 4-32 Protected Radios deploying 3-11 Protection Settings XP4 5-74 XP4 radio 5-74 ProVision 5-3 client 1-2 how it works 1-2 optimum use 1-3 receiving events 3-48 server 1-2 skill set prerequisites 0-2 user accounts 2-15 version number 2-7 ProVision Manager icon 2-21 Proxies TNet 3-32 Purging database 2-15
R
Rack Container icon 2-21 Radio Frequency Links about 3-54
create from Find function 3-56 create from Tree Viewer 3-54 creating for Eclipse radios 3-57 deleting 3-59 Discover RF Link function 3-58 Eclipse link types 3-57 Eclipse radios 3-57 verifying for Eclipse or TRuepoint 3-58 Radio Tasks 2-52 Radios configuration data 3-61 configuration profiles 3-68 deployment process 3-3 icons for 2-21 pop-ups for 2-50 pre-deploying before network rollout 3-3 tasks 2-52 5 and 15-min data collection 2-52 performance thresholds 2-52 waking 4-20 Region Container icon 2-21 Remote Loopback DART 5-85 Renaming 3-44 container 3-7 devices 3-44 logical link 4-70 service 4-68 TNet Proxy 3-79 Reports Eclipse fault 5-101 inventory report 5-95 network health reports 5-108 Performance Data 5-34 saving Inventory, multiple radios 5-100 saving Inventory, single radio 5-98 server reports 5-106 Repositioning object 3-43 Resetting XP4 5-77 Restoring backup configurations, saved 3-113 Retrace circuit 3-91 Right-click Menus see pop-up menus 2-17 Roles NOC engineer 0-1 NOC operator 0-1
Aviat Networks
Root Container icon 2-21 RSSI view TNet performance for 5-65
S
Sagem-link Radio deploying 3-11 Saving event browser contents 4-22, 4-31 event browser view 4-22 inventory report 5-98, 5-100 server reports 5-106 Scenarios managing events 4-72 Scoreboard Groups about 4-72 creating 4-74 deleting 4-75 editing 4-75 functions 4-73 modifying 4-75 scoreboards 4-76 viewing 2-13, 4-73 Scoreboards adding 4-76 creating 4-76 definition 4-76 deleting 4-80 editing 4-79 modifying 4-79 view event browser from 4-80 Searching all ProVision data 2-43 locate function 2-12 main function 2-43 search all ProVision data 2-43 via Tree Viewer 2-47 Security Log 4-45 about and viewing 4-45 Server Reports 5-106 Service Links 4-69 Services deleting a service 4-68 removing a device 4-67 renaming a service 4-68 service links, overview 4-69 Site Container icon 2-21 Sleep Status
overview 4-18 setting for device 4-18 sleep value options 4-18 SmartCore WiChorus ASN-GW deploying 3-28 SNMP Devices deploying 3-9, 3-25 deployment details 3-14 SNMP radios create RF link, via Tree Viewer 3-54 Software for radio 3-67 new Eclipse 3-93 Software Loading menu functions 2-14 Software Table viewing 2-14 Spectrum II Network Health Report 5-108 StarMAX 6100, deploying 3-28 6400, deploying 3-28 backup configuration of 3-113 base station data collection 5-17 base station ethernet bandwidth use 5-25 base station ethernet performance 5-18 base station functions 3-28 base station Inventory Report 5-95 deploying 3-29 deploying all types 3-28 equipment views 2-33 interface views 2-40 StarMaX Software activating 3-108 Status asleep 2-51 connecting 2-51 errored 2-51 managed 2-51 of devices 2-50 unmanaged 2-51 Submaps 2-32 open 2-33 Subscriber Stations deploying 3-29 view connectivity 5-45 System Diagnostics circuit diagnostic window 5-5 circuit diagnostics, run 5-8 circuits 5-4 DART diagnostics 5-84 9
614-330055-001 February 2010
diagnostics 5-1 overview 5-1 prerequisites 5-1 procedures 5-4 using 5-1 when to use 5-1 XP4 details 5-66
T
Task Manager screen 2-42 Tasks radio 2-52 Technical Support version number 2-7 Telnet launching from device 5-48 to access non-Aviat devices 5-47 TNet alarm input and output 5-57 CB 149 diagnostic values 5-63 configure protected links 5-59 craft tool details 5-54 craft tool for 5-48 diagnostic tools 5-58 features for devices 5-55 G.821 diagnostic values 5-61 Protection diagnostic values 5-59 RSSI diagnostic values 5-65 severity levels fori nputs 5-55 user-defined inputs and outputs for 5-55 TNet Devices change subnet 3-79 deploying 3-31 manually deploying into proxy 3-35 proxies 3-32 troubleshooting 3-34 TNet Proxy change IP address 3-79 change name 3-79 configuration 3-77 deploying 3-34 increase subnets 3-79 viewing status 3-80 TNet Proxy Configuration view/change 3-77 TNet Proxy Viewer 3-80 Topology exporting 2-12 trademarks i-ii Tree Viewer
hide 2-10 object pop-ups 2-50 resize 2-10 searching inside 2-47 user interface 2-19 using toggle 2-21 Tributary Loopback activate for XP4 5-68 activate local for XP4 5-72 DART 5-85 local MSU E3 5-69 remote SU E3/DS3 5-69 Troubleshooting TNet deployment 3-34 TRuepoint deploying 3-15 equipment view 2-34 equipment views 2-33 Inventory Report 5-95 IP address capture 3-15, 3-19, 3-24 Network Health Report 5-108 redundant NMS connection support 3-15, 319, 3-24 security log entries 4-45 verify RF links 3-58 TRuepoint 4000 deploying 3-15 resync alarms 4-14 TRuepoint 4040 deploying 3-15 TRuepoint 5000 deploying 3-15 TRuepoint 6400 deploying 3-15 resync alarms 4-15 TRuepoint 6500 deploying 3-20 Inventory Report 5-97 manually discover 3-51 Performance History 5-35 Performance Threshold 5-42 unique characteristics 3-20 TRuepoint Software activating 3-105
U
Unacknowledging network events 4-11 Unmanaging 3-50 Upgrading
10
Aviat Networks
Eclipse radio software 3-93 User Interface 2-9 customizing 2-10 map viewer 2-26 maximize 2-10 minimize 2-10 User Session exceptions 2-3 exiting 2-4 start 2-2 starting 2-2 Users contact details, saving 2-5 multiple user sessions 2-2
W
Waking radios 4-20 warranty i-ii When 4-23 WiChorus deploying 3-28, 3-29 WiMAX ASN-GW Mobility Neighbors viewer 5-43 deploy via autodiscovery 3-38 deploying 3-28, 3-29 device types 3-28 equipment views 2-33 interface views 2-40 network autodiscovery 3-38 subscriber station connectivity viewing 5-45 Subscriber Station CPE list 5-45 WSN ASN-GW Controller 5-43 WiMAX SmartChorus ASN-GW configuration viewer 3-65 WiMAX Subscriber Stations connectivity viewing 5-45 deploying 3-29 Windows Applications integrating with ProVision 2-53 WL1000 interface view 2-40 Network Health Report 5-108 workflow diagrams managing events 4-2 system diagnostics 5-2 WSC ASN-GW Controller deploying 3-28 WSN ASN-GW Controller view 5-43
V
Velox configuration view 3-62 craft tool for 5-48 icon 2-23 security log entries 4-45 Verifying event traffic 3-48 events, receipt 3-48 RF links, Eclipse 3-58 RF links, TRuepoint 3-58 Version Number 2-7 viewing 2-7 Viewing 4-23 customer contact details 2-7 Ethernet performance 5-18 event log pre-filtering 4-35 event properties 4-7 events 4-6 Flat Map 2-27 inventory report 5-96 license details 2-6 performance data status 5-16 Physical Map 2-26 prefilters 4-35 ProVision license details 2-6 ProVision version number 2-7 radio configuration 3-61, 3-68 saved event browser view 4-23 Scoreboard Groups 4-73 scoreboard groups 4-73 XP4 protection settings 5-74
X
activate loopback 5-68 activate loopback, local 5-72 configuration view 3-62 craft tool for 5-48 data collection 5-12 deploying 3-11 diagnostics 5-66 local loopback types 5-73 Network Health Report 5-108 protection settings 5-74 XP4 16/E3/DS3 XP4
614-330055-001 February 2010
11
icon 2-23 XP4 2/4/8x and XP4 2/4/8x (protected) icon 2-23 XP4 2/4/8x icon 2-23 XP4 radio loopbacks 5-67 protection settings 5-74 tributary loopback local MSU E3 5-69 remote SU E3/DS3 5-69 XPF reset 5-77
12
Aviat Networks
614-330055-001
WWW.AVIATNETWORKS.COM

ProVision 6.5.2 User Manual PDF

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.5.2 User Manual PDF

Uploaded by

Copyright:

Available Formats

PROVISION

ProVision User Guide Version 6.5.2

ProVision User Guide

AviatCopyright 2010 by Aviat Networks, Inc.

ProVision User Guide

614-330055-001 February 2010

ProVision User Guide

CHAPTER 1, MAKING PROVISION WORK FOR YOU

CHAPTER 2, NAVIGATING PROVISION

CHAPTER 3, DEPLOYING AND MANAGING DEVICES

ProVision User Guide

CHAPTER 4, MANAGING EVENTS

614-330055-001 February 2010

CHAPTER 5, SYSTEM DIAGNOSTICS AND REPORTS

ProVision User Guide

614-330055-001 February 2010

NOC Engineers NOC Fault Finders

614-330055-001 February 2010

What You Need To Know To Use ProVision

Next Topic Additional Documentation

Next Topic Documentation Organization

ProVision User Guide

Deploying and Managing Devices

Next Topic Documentation Conventions and Terminology

614-330055-001 February 2010

Documentation Conventions and Terminology

A warning item identifies a serious physical danger or major possible problem.

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

Chapter 1. Making ProVision Work For You

The Goals of ProVision

614-330055-001 February 2010

Chapter 1. Making ProVision Work For You

How ProVision Works on page 1-2

How ProVision Works

ProVision User Guide

Getting the Most Value from ProVision

Turning Data Into Information

Managing Data Over Time

Using Performance Analysis

614-330055-001 February 2010

Chapter 1. Making ProVision Work For You

Chapter 2. Navigating ProVision

614-330055-001 February 2010

Chapter 2. Navigating ProVision

Getting Started Procedures

Starting a User Session

ProVision User Guide

From the desktop, double-click the ProVision Client shortcut.

Select OK and retype your user name and password.

614-330055-001 February 2010

Chapter 2. Navigating ProVision

Exiting a User Session

2. To close your ProVision user session, select Yes.

Related Topics: Starting a User Session on page 2-2

Changing Your Password

ProVision User Guide

displays for your user name.

2. Select Change Password. The Change Password dialog box displays.

Entering Your Contact Details

614-330055-001 February 2010

Chapter 2. Navigating ProVision

Viewing Your ProVision License Details

2. To close the window, select OK.