Aviat PV User Manual PDF

PROVISION
USER MANUAL
Version 7.1.2
614-330055-001
ProVision Copyright and Terms of Use
December 2015
This documentation incorporates features and functions provided with ProVision, version 7.1.2
Copyright © 2015 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, elec-
tronic, magnetic, optical, chemical, manual or otherwise, without the prior written permission of Aviat Net-
works 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 Net-
works 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 install-
ation and service, and of measures to avoid any danger to themselves, to any other personnel, and to the
equipment.
2. Access to the Equipment: Access to the equipment in use must be restricted to service personnel only.
3. Safety Norms: Recommended safety norms are detailed in the Health and Safety sections of this manual.
Local safety regulations must be used if mandatory. Safety instructions in this document should be used in
addition to the local safety regulations. In the case of conflict between safety instructions stated in this
manual and those indicated in local regulations, mandatory local norms will prevail. Should local reg-
ulations not be mandatory, then the safety norms in Volume 1 will prevail.
4. Service Personnel Skill: Service personnel must have received adequate technical training on tele-
communications and in particular on the equipment this manual refers to.
Trademarks
All trademarks are the property of their respective owners.
614-330055-001 DECEMBER 2015 I

PROVISION USER MANUAL
II AVIAT NETWORKS
Aviat Networks Technical & Sales

Support
Service and Technical Support:
For customer service and technical support, contact one of the regional Technical Help Desks lis-
ted below.
Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help
Desk
Aviat Networks, Inc. Aviat Networks Aviat Networks
San Antonio, TX Blantyre, Glasgow G72 0FB Clark Freeport Zone
U. S. A. United Kingdom Philippines 2023
Phone: +1 210 526 6345 Phone: +1 210 526 6345 Phone: +1 210 526 6345
Toll Free (USA):1-800-227-8332 Fax: +44 16 9871 7204 (English) Fax: +63 45 599 5196
Fax:+1 210-526-6315 Fax: +33 1 5552 8012 (French) Email:
Email: Email: CustomerCare.Asia@aviatnet.com
Cus- Cus-
tomeCare.Americas@aviatnet.com tomerCare.EMEA@aviatnet.com
Global Support Hotline - +1 210 526 6345
Call this phone number for support from anywhere in the world. Aviat Networks' Global Support Hotline is
available 24 hours a day,7 days a week, providing uninterrupted support for all our customers.
When you call our Global Support Hotline:
•You will be greeted by an automated response that will ask you for your PIN#. Request a PIN# here on
the Aviat Networks web site.
•As soon as you enter your PIN#, you will be transferred to our Global Technical Helpdesk that will assist
you with your technical issue.
•If you do not have a PIN# your call will be answered by our Support Assurance Desk. Your call will be sup-
ported and prioritized accordingly.
See our web site at: http://www.aviatnetworks.com/services/customer-support/technical-assist-

ance/
Sales and Sales Support:

For sales information, contact one of the Aviat Networks headquarters, or find your
regional sales office at http://www.aviatnetworks.com/.
614-330055-001 DECEMBER 2015 III

Corporate Headquarters International Headquarters

California, USA Singapore
Aviat Networks, Inc. Aviat Networks (S) Pte. Ltd.
5200 Great American Parkway 17, Changi Business Park Central 1
Santa Clara, California 95054 Honeywell Building, #04-01
U. S. A. Singapore 486073
Phone: + 1 408 567 7000 Phone: +65 6496 0900
Fax: + 1 408 567 7001 Fax: + 656496 0999
Toll Free for Sales Inquiries: Sales Inquiries:
+ 1 888-478-9669 +1-321-674-4252
IV AVIAT NETWORKS
User Manual Table of Contents
ProVision Copyright and Terms of Use i

Aviat Networks Technical & Sales Support iii
User Manual Table of Contents v
CHAPTER 1. WELCOME TO PROVISION 1

The Goals of ProVision 2
How ProVision Works 3
Getting the Most Value from ProVision 4
What You Need To Know To Use ProVision 6
Documentation Organization 7
Documentation Conventions and Terminology 9
Additional Documentation 10
CHAPTER 2. DEVICE SUPPORT IN PROVISION 11

List of Devices Supported in ProVision 12
Eclipse Device Support 16
CTR Device Support 18
CTR 8300 and ProVision 18
WTM 3100 Device Support 23
TRuepoint Device Support 29
Constellation Device Support 31
Generic Device Support 32
Additional Device Support 33
Cisco Device Support 33
DART Device Support 33
DXR Device Support 33
MegaStar Device Support 34
Symmetricom Device Support 34
TNet Device Support 34
XP4 Device Support 34
614-330055-001 DECEMBER 2015 V

CHAPTER 3. NAVIGATING PROVISION 35

Starting a User Session 35
Exiting a User Session 37
Changing Your Password 37
Entering Your Contact Details 38
Viewing Your ProVision License Details 39
Viewing Customer Support Contact Details 40
Viewing ProVision’s Version Number 40
Using the Online Help 41
The ProVision User Interface 44
Customizing the User Interface 44
Menu Bar 45
Main Tool Bar 51
Right-Click Menus 53
View Tabs: Physical, Logical, Circuits, VLAN, EOAM 55
Physical Viewer and Icons 55
Logical Tree Viewer 61
Circuits Viewer Tab 61
Map Viewer 63
Physical Map View 63
Flat Map View 64
Map Tools 64
Map Backgrounds 66
Map Annotations 69
Detailed Device Views 71
Submaps 71
Equipment Views 73
Interface Views 78
Event Browser 80
The Task Manager Screen 82
Using Search to Search All ProVision Data 83
Searching the Tree Viewers 87
Icons Information and Usage 89
Viewing Radio Icon Anatomy 89
About User Defined Icons 91
Alarm Severity Color Coding 91
Device States 92
Radio Tasks 93
Integrating Windows Applications with ProVision 95
Linking Documents to Devices and Maps 97
CHAPTER 4. DEPLOYING AND MANAGING DEVICES 101

About Deploying and Managing Devices 102
The Process for Deploying and Managing Devices 103
Device Deployment By Type 104
VI AVIAT NETWORKS
Deploying Devices 106

Adding, Editing, and Deleting Device Containers 106
Adding a Container 107
User Defined Containers 108
Renaming a Container 111
Deleting a Container 111
Standard SNMP Device Deployment 112
Eclipse Devices and Nodes Deployment 117
DXR 200 and DXR SMA Device Deployment 120
CAU (Control Alarm Unit) Deployment 122
Cisco Deployment 123
Constellation Device Deployment 124
CTR 8300 and 8540 Device Deployment 125
Generic Device Deployment 128
Proxy and Network Element Deployment 131
Symmetricom TP1x00 Deployment 135
Symmetricom TP5000 Deployment 137
TRuepoint Device Deployment 138
TRuepoint 6500 Device Deployment 142
TNet Device Deployment 144
Network Auto-Discovery for Devices 148
Troubleshooting Device Deployment 152
Changing a Device’s Container 152
Moving Containers and Devices in the Map Viewer 153
Renaming a Device 153
Deleting a Device 154
Managing Devices 156
Managing a Device 156
Verifying ProVision is Receiving Device Events 157
Unmanaging a Device 158
Viewing Eclipse RAC Low Latency Links 159
Manually Discovering WTM 6000 Configuration 161
Manually Discovering TRuepoint 6500 Configuration 162
Manually Discovering DXR 700 Radios 162
Managing Proxy Configuration 163
Managing SMA and DXR Devices 165
Linking Procedures 167
Discovering and Verifying Links 167
Creating an RF Link from the Tree Viewer 169
Creating an RF Link from the Find Function 170
Creating an Eclipse RF Link 171
Creating an Ethernet Link 173
Creating a Tributary Link 174
Deleting an RF Link 175
Deleting an Ethernet Link 176
Circuit Management 177
614-330055-001 DECEMBER 2015 VII

About Circuits and Circuit Management 177

Collecting Circuit Information 178
Viewing and Managing Circuits 179
Circuits Tab 179
Filter and Select Circuits 181
View a Single Circuit 182
View Intersecting Circuits 183
View Ring Circuits 183
View Loop Switch Circuits 184
Find and Resolve Conflicting Circuits 185
Event Browser for a Circuit 186
Circuit Provisioning 186
Using Circuit Provisioning 186
Circuit Diagnostics 190
Delete a Circuit 190
Configuring and Synchronizing Devices 192
Clock Synchronization View 192
Viewing Configuration for Devices 194
Configuration Profiles for Bulk Configuration 201
Create and Execute a New Configuration Profile 202
Configuration Profile Reference 206
Delete a Configuration Profile 211
Quality of Service - Classification 212
Quality of Service - Scheduling 214
Viewing/Changing Network IP Addresses 217
Viewing/Changing TNet Proxy Configurations 218
Using the TNet Proxy Viewer 220
Loading/Activating New Software and Licenses 221
About Loading Device Software Via ProVision 221
Eclipse Software Loading Examples 222
Stage 1: Software Load Procedure 224
Part A Register the Software onto the server 224
Part B Load the Software onto the Devices 227
Stage 2: Software Activation Procedure 230
Recommended Activation Process 230
Eclipse Software Activation Procedure 231
TRuepoint Software Activation Procedure 233
Other Software Activation Procedure 236
Eclipse and CTR Node Licenses 237
Device Configuration Backup and Restore 240
CHAPTER 5. CARRIER ETHERNET MANAGEMENT 243

VLAN Management 244
Overview of VLANs 244
Viewing Discovered VLANs 245
VIII AVIAT NETWORKS

Viewing List of Discovered VLANS 246

Viewing VLAN Configuration Details 247
Viewing VLAN Topology 250
Viewing VLANs in the Physical and Flat Maps 252
Identifying and Resolving VLAN Faults 254
Configuring VLANs 257
Provisioning a New VLAN 257
Modifying an Existing VLAN 261
Deleting an Existing VLAN 262
Ethernet OAM Management 263
Overview of Ethernet OAM 264
Viewing Discovered EOAM MAs 265
Viewing List Of Discovered EOAM MAs 266
Viewing EOAM MA Logical Topology 267
Viewing EOAM MA Physical Topology 269
Identifying and Resolving EOAM Configuration Faults 270
Configuring Ethernet OAM 275
Provisioning a New EOAM MA 275
Modifying an EOAM MA 280
Deleting an EOAM MA 280
ERP Ring Management 282
Overview of ERP 282
Viewing Discovered ERP Rings and Ring Configuration 283
Viewing ERP Ring Configuration Details 285
Configuring an ERP Ring 286
Provisioning a New ERP Ring 286
Provisioning an ERP Subring 290
Modifying an ERP Ring 292
Deleting an ERP Ring 292
CHAPTER 6. MANAGING EVENTS 295

Event Management Processes 296
Managing Event Processes in ProVision 296
Suggested Steps for Managing Events 296
Event Management Interdependencies 297
Setting Up Scoreboard Groups 297
Customizing Event Browsers 297
Event Management Procedures 299
Network Events 299
Network Event States 299
Viewing Network Events 300
Viewing an Event’s Properties 301
Acknowledging a Network Event 303
Unacknowledging a Network Event 305
Managing Event Notification Pop-Ups and Audio Alarms 306
614-330055-001 DECEMBER 2015 IX

Manually Clearing a Network Event 307

Manually Resynchronize Alarms 308
Configure TRuepoint 6400 Alarm Resynchronization 308
Customizing Event Names or Severity Levels 310
Sleep Status for a Device 311
Event Browsers 314
Saving an Event Browser View 315
Viewing a Saved Event Browser 316
Customizing an Event Browser 317
Changing Event Browser Options 321
Deleting an Event Browser 323
Saving Event Browser Contents 324
Printing Event Browser Contents 325
Event Log Pre-Filtering 326
Viewing Event Log Pre-Filtering 328
Adding An Event Log Pre-Filter at the Root Level 329
Adding an Event Pre-filter at an Object Level 332
Adding an Event Pre-Filter Via an Event Browser 333
Modifying An Event Log Pre-Filter 334
Deleting An Event Log Pre-Filter 335
Event Analyzer 338
Security Log 340
Event Notification 341
Set the Server Notification Preferences 342
Add or Edit Event Notification Rules 343
Delete an Event Notification Rule 347
Configuring the Notification Rule 348
Set Up an Email Event Notification 351
Set Up a Pop-Up Message Notification 353
Set Up an Audio Alarm Notification 355
Set Up Script Execution on Event Notification 357
Logical Containers 359
Adding a Device to a Logical Container 361
Removing a Device from a Logical Container 362
Renaming a Logical Container 363
Deleting a Logical Container 363
Logical Links 364
Adding a Logical Link 364
Renaming a Logical Link 365
Deleting a Logical Link 365
Scoreboard Group Scenarios 367
About Scoreboard Group Scenarios 367
Viewing a Scoreboard Group 368
Creating a Scoreboard Group 369
Editing a Scoreboard Group 370
Deleting a Scoreboard Group 370
X AVIAT NETWORKS
Adding a Scoreboard 370

Editing a Scoreboard 373
Deleting a Scoreboard 373
Opening an Event Browser from a Scoreboard 374
CHAPTER 7. SYSTEM DIAGNOSTICS AND REPORTS 377

Using System Diagnostics 378
About ProVision and Craft Tools 380
Diagnostic and Performance Trends Analysis Procedures 381
Circuit Diagnostics Feature 381
Circuit Diagnostic Window 381
Setting Up a Circuit Diagnostic Test 384
Circuit Diagnostic Options 386
Data Collection 388
Daily Performance Data Collection 389
Enabling 15-minute Performance Data Collection 390
Changing Device Data Collection Status 392
Ethernet Performance Data Collection 393
Enabling 15-Minute Ethernet Data Collection 393
Viewing Ethernet Performance 394
Ethernet Bandwidth Utilization 399
Performance Features 404
Performance History 404
Performance Trends 409
Performance Thresholds 413
Craft Tools and Diagnostic Controls 417
List of Craft Tools 417
Launching a Craft Tool 419
LE3000 and LE3200 Craft Tool Installation 421
WMT Craft Tool 421
TNet Web Craft Tool and Diagnostics 424
Launching the TNet Web Craft Tool 427
TNet Diagnostics 429
TNet Diagnostics - Protection Tab 430
TNet Diagnostics - G.821 Performance Tab 431
TNet Diagnostics - CB 149 Performance Tab 433
TNet Diagnostics - RSSI Tab 434
XP4 Device Support: Craft Tool and Diagnostics 436
Launching the XP4 Craft Tool 436
Launching the XP4 Diagnostics 437
Activating and Deactivating an XP4 Tributary Loopback 437
Activating and Deactivating an XP4 Local Loopback 441
Viewing/Changing XP4 Protection Settings 443
Resetting an XP4 Radio Device 445
Diagnostic Controls for Selected Devices 446
614-330055-001 DECEMBER 2015 XI

Constellation Diagnostic Controls 447

CAU Diagnostic Controls 451
DART Diagnostics Controls 452
DVA Diagnostic Controls 453
Megastar Diagnostic Controls 455
CHAPTER 8. DEVICE AND NETWORK REPORTS 457

Inventory Reports 458
View and Save the Inventory Report for a Single Device 459
View and Save Inventory Reports for Multiple Devices 462
Eclipse Fault Report 465
Capacity Report 467
View / Save / Delete Server Reports 469
View and Save Capacity Reports for Multiple Devices 471
RF Network Health Reports 474
Run and View RF Network Health Reports 475
Ethernet Network Health Report 480
Clock Synchronization Network Health Report 485
Eclipse Security Status Report 488
Clock Sync Report 490
Link Report 492
Licensing Report 496
Creating Custom Reports 498
Scheduling Reports 507
Reports Available by Device Type 510
Glossary 513
Index dxli
XII AVIAT NETWORKS

Chapter 1. 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:
l Using ProVision to create and maintain network maps
l Monitoring and managing device status, performance, and event reporting
l Configuring Aviat Networks devices
l Configuring and managing third party devices
l Generating supporting reports and graphs
This documentation is for all ProVision users, including:
Role Role Description
NOC Operators Monitor the radio network for errors and performance. Fol-
low predefined procedures when faults are detected. May
have little or no radio expertise.
NOC Engineers Configure the radio settings and performs software and
configuration changes. Radio domain experts.
NOC Fault Finders Diagnose and isolate faults in the network down to the
unit/event level. Issue trouble tickets to field engineers
where necessary.
If you are working with ProVision in a different role, for example, as a ProVision admin-
istrator, refer to the Additional Documentation on page 10.
This section includes the following topics:

l What You Need To Know To Use ProVision on page 6
l The Goals of ProVision on page 2
l How ProVision Works on page 3
l Getting the Most Value from ProVision on page 4
l Additional Documentation on page 10
l Documentation Organization on page 7
l Documentation Conventions and Terminology on page 9
614-330055-001 DECEMBER 2015 1

CHAPTER 1. WELCOME TO PROVISION
The Goals of ProVision

ProVision is the best tool to help your business to manage its radio network in many
ways:
l Achieving maximum system availability.
l Reducing network operating costs.
l 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:
l Information entered when the device was installed and commissioned into
service
l Performance data
l 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:
l Network planning
l Installation
l Commissioning
l Event monitoring
l Device / network performance
l Fault diagnostics
l Device reconfigurations
l Inventory management
Next Topic:
How ProVision Works on page 3
2 AVIAT NETWORKS
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 event-
s/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 com-
puter, or separately.
ProVision can have multiple Clients: up to 15 Clients for each Server.
614-330055-001 DECEMBER 2015 3

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:
l Easy differentiation between real radio problems vs. informational data
l Alarm status for the entire link
l Reducing the amount of data that is not of value by putting the radio in sleep
mode
l 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.
With ProVision's Mobile Client, you can stay posted about network status and faults
while you travel,using Apple iOS or Android devices.
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.
4 AVIAT NETWORKS
Using Performance Analysis

ProVision can collect and save huge amounts of performance data from the radios. This
data is normally over-written in the radios. The data can be used to find patterns before
traffic is affected, and to diagnose problems if a radio fails.
ProVision can keep the daily data for all radios for a predefined time. This data can be
used to spot long term trends in radio performance, identify problem sites or radios.
Radios that are identified as critical or causing problems can also be monitored more
intensely using 15-minute data collection, which can be used to find problems that are
occurring now. This data can also be kept in the ProVision database indefinitely.
Performance data can provide information in many ways. If a radio is having per-
formance 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 per-
formance 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.
614-330055-001 DECEMBER 2015 5

What You Need To Know To Use

ProVision
To use ProVision effectively, we recommend that you have the following knowledge and
skills:
l 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:
l ProVision User Training
l ProVision System Administrator Training
6 AVIAT NETWORKS
Documentation Organization
This manual is organized into the following chapters and appendices:
Device Support in ProVision
This section describes all devices supported by ProVision, and the specific ProVision
functionality that supports the devices. It also includes lists of Generic Device sup-
ported third party devices.
Navigating ProVision on page 35
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 net-
work search facility and navigating context-sensitive pop-up menus and functions.
Deploying and Managing Devices on page 101
This section describes how to deploy, link, and manage radios in ProVision. This
includes circuit management and circuit provisioning.
Carrier Ethernet Management on page 243
This section describes how to view and configure Carrier Ethernet functionality, includ-
ing:
l VLAN
l Ethernet OAM
l ERP
Managing Events on page 295
This section describes event management tools for events generated by the radios and by
the system. This includes:
l Individual event history and probable cause identification.
l Services that enable you to group together network devices that share a
common purpose.
l Customizable Event Browsers with event filtering and browser options that
you can save and reuse.
l Prefiltering events at input which reduces the number of events in the system.
l Scoreboard groups, providing an at-a-glance overview of a network.
System Diagnostics and Reports on page 377
This section describes system diagnostics, including:
l Enabling performance data collection.
l Launching the individual radio craft tools.
l Using Diagnostics.
Device and Network Reports on page 457
614-330055-001 DECEMBER 2015 7

This section describes how to use all ProVision reports, including custom reports and
report scheduling.
8 AVIAT NETWORKS
Documentation Conventions and

Terminology
Graphic Cues
The following icons function as graphical cues used to characterize particular types of
associated supporting information.
CAUTION: A caution item identifies important information pertaining to actions that
may cause damage to equipment, loss of data, or corruption of files.
W AR NING : A warning item identifies a s er ious phys ic al danger or

major pos s ible pr oblem.
NOTE : A note item identifies additional infor mation about a pr oc edur e

or func tion.
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
l Click or Select: Point the mouse pointer at the item you want to select, then
quickly press and release the left mouse button.
l Right-Click : Point the mouse pointer at the item you want to select, then
quickly press and release the right mouse button.
614-330055-001 DECEMBER 2015 9

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:
l Task-oriented assistance in planning for, installing, and configuring ProVision
hardware and software components.
l ProVision database backup and restore procedures
l How to provide Aviat Networks with the information required 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
for Aviat Networks radios.
Further additional documentation includes:
l ProVision Mobile Client Manual
l ProVision Upgrade Guide
l ProVision Solaris Quick Start Guide
l ProVision Windows Quick Start Guide
10 AVIAT NETWORKS
Chapter 2. Device Support in
ProVision
ProVision natively supports all Aviat Networks microwave radio and network support
devices. ProVision also natively supports partner products. Additional third-party
devices are supported through its Generic Device functions.
This section provides a reference list of all the devices that ProVision supports. It also
includes device function summaries for Aviat Networks devices, and for devices that
have special functionality in ProVision.
Content here includes:
l List of Devices Supported in ProVision on page 12
l Eclipse Device Support on page 16
l CTR Device Support on page 18
l WTM 3100 Device Support on page 23
l TRuepoint Device Support on page 29
l Constellation Device Support on page 31
l Generic Device Support on page 32
l Additional Device Support on page 33
614-330055-001 DECEMBER 2015 11

CHAPTER 2. DEVICE SUPPORT IN PROVISION
List of Devices Supported in ProVision

This section lists all the devices supported in ProVision. Each list is in alphabetical
order.
Aviat Networks Microwave Network Devices
l Altium 155, MX
l Aurora
l CAU
l Constellation
l Constellation via Farscan Proxy
l CTR 8300
l CTR 8540
l CTR 8440
l CTR 8611
l DART
l DVA
l DVM 45, xT
l DXR 100
l DXR 200 via SMA Proxy
l DXR 700 / SMA
l Eclipse IDU (all variants), INU, INUe, IDU, IRU600, RAC LL, RAC LL DDR
l LE3000, LE3200
l Megastar 1+, M:N
l Microstar type I, II, III
l SPECTRUM II SNMP
l TNet Proxy devices (all 13 device types)
l TRuepoint 4000, 4040, 5000
l TRuepoint 6400
l TRuepoint 6500
l Velox
l WTM 3100
l WTM 3200
l WTM 3300
l WTM 6000
l XP4 16/E3/T3, 2/4/8X
12 AVIAT NETWORKS
Partner Product Devices

l Accedian EtherNID, Metro NID, MetroNODE
l Cisco range: 3650, ME2400, ME3400E, MWR2941, ME3600, ME3800, ME
3600X, ME 3800X ME 3900, ASR 903, ASR 1000, SNS 3495, Catalyst 2950,
Catalyst 2960
l E-Band E-Link 1000EXR, LR, Q, Eagle
l EMS Proxy and Network Elements
l Memotec CX-U
l Radwin WinLink 1000, Radwin 2000
l Sagem ADR 155C / 2500 eXTRA
l Sagem SAGEM-LINK
l Symmetricom Timers TP 1000+ TP 1100, TP 5000, TP 500
l Tellabs 7300 range: 7345
l Tellabs 8600 range: 8605, 8609, 8611, 8630, 8660
l WiChorus SmartCore
Devices Supported with GDS Packages

l 4RF Aprisa XE Microware Radio
l Adtran MX2800 Mux
l Adtran MX2820 Mux
l Adtran Netvanta 7100 Switch
l Adtran OPTI-6100 Mux
l Adtran TA908e Mux
l Adtran Tracer 6000 Microwave Radio
l Alcatel MDR-8000 Microwave Radio
l Allgon Transcend Microwave Radio
l APC UPS Network Mgmt Card 2
l Argus Cordex CXC
l Asentria SiteBoss S500 Site Managers
l Asentria SL81 Site Manager
l Asentria SL10 Site Manager
l Bats AATS
l Bayly OMNI Flex DACS
l Bayly OMNI Linc Mux
l Bayly OMNI Optix Mux
l Benning MCU Power System
l Benning MCU v2 Power System
l C&D Sageon Power System
l CAC Axxius 800 Mux
l CAC Wide Bank 28 Mux
614-330055-001 DECEMBER 2015 13

l Cisco ASA 5500

l Cisco 1900 ISR Series Router
l Cisco 3750 Metro Switch
l Cisco 3824 Router
l Cisco 3825 Router
l Cisco 7200 Series Router
l Cisco 7350 Switch
l Cisco ASA 5500 Series Firewall
l Cisco ONS 15310-MA Mux
l Delta CSU503 Power System
l DPS NetGuardian G4 - G5 Site Manager
l Eaton SC200 Power System
l Eltek BC2000 Power System
l Eltek Smartpack, Flatpack Power Systems
l Emerson LXP Series Power System
l Emerson Netsure 502 Power System
l ETI ADH NETCOM Dehydrator
l Exalt EX-5i & EX-2.4i Microwave Radios
l Exalt EX-5i-16 & EX-2.4i-16 Microwave Radios
l Fujitsu Flashwave 4100 Mux
l Fujitsu Flashwave 9420 Mux
l GE MDS Intrepid Microwave Radio
l Harris Intraplex
l IPMobileNet IP Network Controller
l Keymile UMUX (via UNEM V8 EMS)
l LaMarche LMHF
l LightPointe Aire X-Stream Microwave Radio
l Lineage Galaxy Pulsar NE843 Power System
l Loop Telecom AM3440-A & C Mux
l Loop Telecom O9100 Mux
l Loop Telecom V4150 Mux
l MDS Intrepid and Intrepid Ultra
l MultiTel iS3, Fusion, Mirador Site Managers
l NEC iPasolink Microwave Radio
l NEC NLite E Microwave Radio
l RFL IMUX 2000 Multiplexers & MDACS
l Siemens HiPath 4000
l Socomec Net Vision Power System
l Sycamore DNX-1u and DNX-11 Mux
l Tejas TJ100 Mux
l Tejas TJ1270 Mux
l Tejas TJ1400 Mux
14 AVIAT NETWORKS
l Tejas TJ1600 Mux

l Telco Systems OTM1000 Mux
l Tellabs 6300 Mux (via ECT EMS)
l Tellabs 8600 Switch
l Terabeam TeraBridge 5x45 and 5x45 11 Ethernet Microwave RadioRadio
l TrangoLINK Giga Microwave Radio
l TrangoLINK GigaPlus Microwave Radio
l TRAK 9100 Timing System
l Zhone IMACS Series Mux
614-330055-001 DECEMBER 2015 15

Eclipse Device Support

What Is Eclipse?
Eclipse is one of the industry’s leading platforms for microwave access, transport and
backhaul applications. Eclipse provides the most comprehensive wireless solution avail-
able for transport of all types of traffic, from low-capacity PDH to high-capacity
SDH/SONET to Carrier Ethernet.
Eclipse features include Super-PDH™ capacity migration, advanced nodal networking
and Liquid Bandwidth assignment of available radio capacity between TDM and Eth-
ernet traffic, all to deliver high-end performance at lower overall cost of ownership.
Eclipse radios are easy to upgrade with the addition of DAC and RAC cards and addi-
tional modules. Because of this, Eclipse networks have a long life. ProVision can man-
age all variants of Eclipse devices, including:
l Eclipse 100
l Eclipse 300 (IDU)
l Eclipse 300 (INU)
l Eclipse 300 (INUe)
l IRU 600
l Eclipse incorporating the following plug-ins: RAC LL DDR, DAC 155o, DAC
155eM, DAC GE3, NCC, NCM, Fan
l Eclipse using DPP port Ethernet
l Eclipse Edge IDUspe
How ProVision Supports Eclipse

ProVision is the best element manager for Eclipse devices. All of ProVision's functions
work for Eclipse. This table lists Eclipse management support functions.
Function Area Information
Deploy and Discover Eclipse Devices and Nodes Deployment on page 117
Network Auto-Discovery for Devices on page 148
Circuits and Links Viewing and Managing Circuits on page 179
About Circuits and Circuit Management on page 177
Circuit Provisioning on page 186
Linking Procedures on page 167
Creating an Eclipse RF Link on page 171
Logical Links on page 364
16 AVIAT NETWORKS

Configure Viewing Configuration for Devices on page 194
Configuration Profiles for Bulk Configuration on page
201
View Devices Submaps on page 71
Viewing Eclipse RAC Low Latency Links
Collect Data Performance Data Collection on page 1
Ethernet Performance Data Collection on page 393
Ethernet Bandwidth Utilization on page 399
Reports RF Network Health Reports on page 474
Capacity Report on page 467
Eclipse Fault Report on page 465
Eclipse Security Status Report on page 488
Clock Sync Report on page 490
Clock Synchronization Network Health Report on page
485
Ethernet Network Health Report on page 480
Link Report on page 492
Manage Device Software Loading/Activating New Software and Licenses on page
221
Eclipse Software Loading Examples on page 222
Eclipse and CTR Node Licenses on page 237
Backup and Restore Device Configuration Backup and Restore on page 240
Configuration Backup and Restoration on page 1
Security and Alarms Eclipse Strong Security on page 1
Event Analyzer on page 338
The ProVision online help includes a complete listing of the
Eclipse Alarms as an appendix.
Carrier Ethernet VLAN Management on page 244
Ethernet OAM Management on page 263
ERP Ring Management on page 282
Clock Synchronization View on page 192
614-330055-001 DECEMBER 2015 17

CTR Device Support

ProVision provides support for the entire suite of CTR devices provided by Aviat Net-
works. Note that all these devices require a specific feature license key.
CTR 8300 and ProVision

The CTR 8300 is a super-compact microwave router that can pack up to 1 Gbps of data
throughput in a single radio channel. It is a smaller version of the CTR 8540 microwave
router.
How ProVision Supports CTR 8300 Devices

Deploy and Discover Standard SNMP Device Deployment on page 112
CTR 8300 and 8540 Device Deployment on page 125
About Loading Device Software Via ProVision on page
221
Creating an RF Link from the Tree Viewer on page 169
Adding a Device to a Logical Container on page 361
Adding a Logical Link on page 364
201
Device Security Accounts
Deploying a Configuration NBI
View Submaps on page 71
Interface Views
Performance History on page 404
Performance Trends on page 409
Performance Thresholds on page 413
18 AVIAT NETWORKS

Reports RF Network Health Reports
Inventory Reports on page 458
Creating Custom Reports on page 498

The Aviat Networks Converged Transport Router (CTR) 8440 is a next generation carrier
class cell site router that combines high performance Carrier Ethernet & IP/MPLS switch-
ing and routing, along with TDM services aggregation, in a compact 1RU platform.

Interface Views
Deploying a Performance Data NBI
Reports Ethernet Network Health Report on page 480
Link Report.htm
614-330055-001 DECEMBER 2015 19


The Aviat Networks Converged Transport Router (CTR) 8540 offers fully converged
microwave indoor unit (IDU) and cell site router (CSR) functions in a new carrier class
platform - built for intelligent microwave and IP/MPLS networking with flexibility to
interwork with both split mount and all outdoor radios.
It is designed to provide complete solutions with lowest cost of ownership by removing
the need to consider which product to use for switching and routing, which for radio,
and their integration for management, training and sparing.
CTR is especially applicable in networks incorporating radio backhaul where this unique
versatility provides the most flexible, scalable, and cost-efficient platform of type. Its fea-
tures include:
l Media convergence and transport over radio, fiber or copper on one compact
l 1U platform
l Site aggregation and expansion through multiple IP, Ethernet, and PDH
interfaces
l Up to eight directly-connected IF or PoE radio links per chassis
l Additional radios can be connected on non-PoE Ethernet interfaces
l Provision for all-indoor operation to 11 GHz or split-mount to 80 GHz
l L1LA support, including for 2+0 L1LA, 2+2 XPIC L1LA, and inter-RAC
protection
l Adaptive or fixed modulation to 1024 QAM
l Co-channel operation with XPIC for double density links in a single frequency
channel
l Comprehensive L2 traffic, service, and protection options; QoS, VLANs, LAG,
l EOAM, QinQ, RSTP, MSTP, ERPS
l PoE+ ports support 65W per interface
l T1/E1 transport via TDM pseudowires
l Chassis based active/standby for protection and expansion
l Plug-in module and software options for service expansion
l CLI, Web GUI, and SNMP management access
l Power efficient design
20 AVIAT NETWORKS

221
201
Interface Views
Clock Synchronization View on page 192
Performance_Trends.htm
Clock Synchronization Network Health Reports

The CTR 8611 is s an integrated microwave router purpose-built for mission-critical
applications where full redundancy and protection are paramount. It has a High Avail-
ability design to interoperate with any transport network, and delivers industry-leading
614-330055-001 DECEMBER 2015 21

L2/L3 routing functionality optimized to improve the performance and manageability of

microwave-based transport networks.

221
201
Interface Views
Performance Trends on page 409
22 AVIAT NETWORKS
WTM 3100 Device Support

What Is WTM 3100?
The Aviat Networks WTM 3100 is an all outdoor packet-microwave radio operating in
licensed frequency bands from 7 to 38 GHz with channel sizes from 7 to 56 MHz. Suit-
able for connecting locations up to ~50km apart, the WTM 3100 will deliver up to 360
Mbit/s of Ethernet capacity on a single port. It is designed to meet Carrier Ethernet
transport requirements and provides operators with an economic solution for basic
microwave networking applications at sites with severe space restrictions.
The WTM 3100 can be deployed in a variety of Ethernet or Carrier Ethernet applications
to connect packet switches, routers or specialized IP enabled platforms such as 4G
mobile RAN. It operates as a transparent Ethernet bridge and can be deployed in chain,
ring, star or mesh topologies.
The WTM 3100 also provides operators with a clear demarcation between the Ethernet
transport (microwave) and the switching layer of the network, enabling rapid fault isol-
ation and optimizing the mean time to repair (MTTR).
How ProVision Supports WTM 3100

ProVision is the best element manager for WTM 3100 devices. This table lists WTM 3100
management support functions.
201
NBI Configuration Management
View Devices Interface Views on page 78
614-330055-001 DECEMBER 2015 23


What Is WTM 3200?
The Aviat WTM 3200 is an advanced all outdoor packet radio featuring an advanced
Carrier Ethernet switch and highly scalable microwave transport platform. Its specialty
is efficient microwave networking for space and power restricted locations.
Equipped with QPSK to 1024 QAM modulation in frequency bands from 6 to 42 GHz,
the WTM 3200 supports throughput rates up 1 Gbit/s.
The WTM 3200’s Carrier Class Ethernet switch supports advanced traffic management,
security and control features. It can be quickly integrated and harmonized with existing
(deployed) Carrier Ethernet networks and devices such as the Aviat Eclipse GE3 switch-
ing platform. The WTM 3200 also provides the added security of AES encryption for
management and payload traffic.
Low power consumption (<35 Watts) and simplified cabling ensures the WTM 3200
maximizes installation, operations and maintenance efficiency at small sites.

ProVision is the best element manager for WTM 3200 devices. This table lists WTM
3200 management support functions.
221
201
24 AVIAT NETWORKS

The Aviat Networks WTM 3300 is an innovative microwave networking platform that
introduced a new class of performance to the 80 GHz market. It delivers link capacities
to urban network sites from 400 Mbps to 1 Gbps in the smallest, lightest and most aes-
thetically integrated package in the market. Applications include mobile backhaul
(macro and small cell), fixed line access and enterprise LAN interconnect.
The Aviat Networks WTM 3300 offers a unique combination of high system gain, adapt-
ive modulation techniques and capacity scalability from 400 Mbit/s to 1 Gbit/s within a
standard 250 MHz channel. Suitable for urban links from 0.5 to 3 km, the WTM 3300 is
the first 80 GHz product to feature an ‘invisible antenna’ design which drives significant
TCO gains for the operator. It also means operators can now access more rooftop, wall
and street level sites compared to traditional parabolic antenna systems that are often
not viable due to technical, environmental or planning restrictions. For locations where
higher gain is required, WTM 3300 can also be equipped with 1 ft or 2 ft parabolic
antenna.

221
201
View Devices Interface Views on page 78
614-330055-001 DECEMBER 2015 25


26 AVIAT NETWORKS

What Is WTM 6000?
The Aviat Networks WTM 6000 is an all-IP trunking radio, capable of supporting up to
4 Gbit/s of aggregate data throughput. The WTM 6000 is a network operator’s first
choice for high trunking capacity for regional and national backbone links in place of
fiber.
It includes advanced packet transport features that have only been available in lower
capacity microwave systems. These include built-in Ethernet switching, link aggreg-
ation, traffic prioritization, Quality of Service controls and Synchronous Ethernet
(SyncE) capabilities. Network operators that need ultra-dependable wireless connections
can use WTM 6000 as a fiber alternative for all-IP network backbone links.
The WTM 6000 is the highest density wireless trunking solution on the market, being
the first system to accommodate up to 16 radio channels in a single sub-rack, and sup-
porting 4 Gbit/s and more of aggregate Ethernet throughput .
With integrated switching and native Ethernet/IP support, the WTM 6000 also
provides optional support for STM-1 traffic, enabling operators to maintain legacy TDM
services without having to use inefficient circuit emulation. The WTM 6000 is also the
first trunking radio in its class to support 256QAM Adaptive Coding and Modulation
(ACM) to enable operators to achieve higher link capacities with smaller antennas.

201
Manually Discovering WTM 6000 Configuration on
page 161
View Devices Equipment Views on page 73
Physical Viewer and Icons on page 55
614-330055-001 DECEMBER 2015 27


28 AVIAT NETWORKS
TRuepoint Device Support

The TRuepoint series are robust, high-capacity digital microwave radios for the North
America wireless transmission market. They deliver broad network flexibility and path
reliability. Supported TRuepoint devices include:
l TRuepoint 4000
l TRuepoint 4040
l TRuepoint 5000
l TRuepoint 6400
l TRuepoint 6500
How ProVision Supports TRuepoint

This table lists TRuepoint management support functions.
Deploy and Discover TRuepoint Device Deployment on page 138
TRuepoint 6500 Device Deployment on page 142
Discovering and Verifying Links on page 167
Configure and Manage Viewing Configuration for Devices on page 194
201
Manually Discovering TRuepoint 6500 Configuration on
page 162
Manually Resynchronize Alarms on page 308
Customizing Event Names or Severity Levels on page
310
Manage Device Software Loading/Activating New Software and Licenses on page
221
614-330055-001 DECEMBER 2015 29

NOTE : For TRuepoint 4040 v2 and 5000 devic es w ith V2 c ontr oller s , an
additional Pr oVis ion func tion enables you to apply SNMPv3 pr i-
vac y/enc r yption. To do this us ing the algor ithm types of TDES, AES128,
or , for US c us tomer s only, AES192 and AES256, your Pr oVis ion s ys tem
r equir es :
* A s pec ific Pr oVis ion featur e lic ens e.
* A Java c r yptogr aphy extens ion (JCE unlimited s tr ength jur is dic tion
polic y file/s ) fr om Sun Mic r os ys tems .
Contac t your Aviat Netw or ks r epr es entative to obtain this lic ens e and
this extens ion.
30 AVIAT NETWORKS
Constellation Device Support

What Is Constellation?
Constellation is a digital microwave radio for the North America wireless transmission
market. It features an all-indoor architecture designed for mid- to high-capacity applic-
ations.
Constellation enables simplified capacity upgrades—from 4xDS1 to 4xDS3 or 1xOC-3—
and easy maintenance without tower-mounted equipment. It offers a rich set of stand-
ard and optional features, including superior transmission characteristics.
How ProVision Supports Constellation

This table lists unique Constellation management support functions.
Deploy and Discover Constellation Device Deployment on page 124
Configure and Manage Viewing Configuration for Devices on page 194
201
Constellation Diagnostic Controls on page 447
Customizing Event Names or Severity Levels on page
310
614-330055-001 DECEMBER 2015 31

Generic Device Support

What Are Generic Devices?
Generic devices can be SNMP or IP based, non-Aviat Networks 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:
l Symbol
l Generic
l Multiplexer
l Router
l Switch
l Microwave Radio
l Site Manager
l Base Station
l Timing System
l Server
l Firewall
l Air Conditioner
How ProVision Supports Generic Devices

Most ProVision generic device support is for Administrator level users and is described
in the ProVision Installation and Administration Manual. Standard-level users can :
l Deploy Generic Devices - Generic Device Deployment on page 128
l View Generic Devices - Interface Views on page 78
l View and Manage Generic Device Events -Event Browser, Event Notification,
About Scoreboard Group Scenarios, NBI Event Management.
NOTE : Aviat Netw or ks pr ovides c ons ulting s er vic es for Gener ic Devic e
integr ation. Pleas e c ontac t your Aviat Netw or ks s ales and s uppor t s taff
for mor e infor mation.
32 AVIAT NETWORKS
Additional Device Support

This section is a reference for other device types that have specific support instructions
in ProVision:
l Cisco
l DART
l DXR
l MegaStar
l Symmetricom
l TNet
l XP4
NOTE : All of thes e ins tr uc tions as s ume that you ar e exper ienc ed w ith
the devic es . Refer to the s our c e doc umentation for the devic es as
r equir ed.
NOTE : Eac h of thes e devic e types mus t be c onfigur ed to s end SNMP

tr aps to the IP addr es s of the Pr oVis ion s er ver .
Cisco Device Support

ProVision installation of Cisco devices requires an extra step, documented here:
l Cisco Deployment on page 123
DART Device Support

ProVision provides specific support for DART devices:
l DART Diagnostics Controls on page 452
l Activating and Deactivating DART Tributary Loopbacks
DXR Device Support

ProVision provides specific support for DXR devices:
l DXR 200 and DXR SMA Device Deployment on page 120
l Manually Discovering DXR 700 Radios on page 162
l Managing SMA and DXR Devices on page 165
614-330055-001 DECEMBER 2015 33

MegaStar Device Support

For MegaStar, ProVision provides:
l Megastar Diagnostic Controls on page 455
Symmetricom Device Support

ProVision installation of Symmetricom devices requires an extra step, documented here:
l Symmetricom TP1x00 Deployment on page 135
l Symmetricom TP5000 Deployment on page 137
TNet Device Support

ProVision provides specific support for TNET devices:
l TNet Device Deployment on page 144
l Using the TNet Proxy Viewer on page 220
l Viewing/Changing TNet Proxy Configurations on page 218
l TNet Web Craft Tool and Diagnostics on page 424
XP4 Device Support

ProVision provides specific support for XP4 devices:
l Activating and Deactivating an XP4 Tributary Loopback on page 437
l Activating and Deactivating an XP4 Local Loopback on page 441
l Viewing/Changing XP4 Protection Settings on page 443
l Resetting an XP4 Radio Device on page 445
34 AVIAT NETWORKS
Chapter 3. Navigating ProVision
This section describes the ProVision user interface and how to start using ProVision,
including:
l The ProVision User Interface on page 44
l Right-Click Menus on page 53
l View Tabs: Physical, Logical, Circuits, VLAN, EOAM on page 55
l Map Viewer on page 63
l Detailed Device Views on page 71
l Event Browser on page 80
l Using Search to Search All ProVision Data on page 83
l Searching the Tree Viewers on page 87
l Icons Information and Usage on page 89
l Integrating Windows Applications with ProVision on page 95
NOTE : This s ec tion as s umes that Pr oVis ion has been ins talled, and the
devic es ar e deployed and being managed fr om Pr oVis ion.
Starting a User Session

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 sys-
tem 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.
NOTE : Set your dis play r es olution to a minimum of 1024 x 768. This
ens ur es that all the c omponents in the Pr oVis ion w indow s ar e vis ible on
your dis play.
614-330055-001 DECEMBER 2015 35

CHAPTER 3. NAVIGATING PROVISION
Procedure
1. From the desktop, double-click the ProVision Client shortcut. (In Windows 8 or
8.1, swipe in from the right edge of the screen, or, using a mouse, point to the upper-
right corner of the screen, move the mouse pointer down to open the function side-
bar, and then tap Search. From here, locate and click on the ProVision Client icon.)
2. The ProVision Login window displays.
3. Type your user name and password in the fields provided. For example:
l User: LeslieSmith
l Password: password
4. Enter the name of your ProVision Server and select Login. The ProVision Loading
window displays.
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,or the sever is not available, the fol-
lowing error message displays.
36 AVIAT NETWORKS
Select OK and retype your user name and password.

CAUTION: After three failed attempts with an incorrect login name or password,
the Login dialog box closes and access to ProVision is denied. At this point you must
contact your Network Administrator.
If the error message displays again, contact your Network Administrator.
Exiting a User Session

ProVision user sessions continue to run until you exit the session or shut down your
workstation.
Procedure
1. Select the X in the upper right corner of the user interface window. A message dis-
plays prompting you to confirm your exit request.
2. To close your ProVision user session, select Yes.
Changing Your Password

Each user requires a user name and password to log into ProVision.The system admin-
istrator 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.
NOTE : If you type an invalid pas s w or d in any of the pas s w or d boxes , an

er r or mes s age dis plays . To c los e the mes s age box and tr y again, s elec t
OK .
614-330055-001 DECEMBER 2015 37

Procedure
1. Select Administration > Change User Details. The Change User Details window
displays for your user name.
2. Select Change Password. The Change Password dialog box displays.
3. In the 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.
Entering Your Contact Details

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
1. Select Administration > Change User Details. The Change User Details window,
with your user name, displays.
38 AVIAT NETWORKS
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.
5. Changing Your Password on page 37
Viewing Your ProVision License Details

The ProVision license details can be viewed at any time. License details display in the
status bar, for example:
There are two types of license, an evaluation license that expires a specified number of
days after installation and a permanent license that has no expiry date.
Procedure
1. Select Help > License Details. The License Detail window displays, for example:
2. To close the window, select OK.
614-330055-001 DECEMBER 2015 39

Viewing Customer Support Contact Details

If you need to contact Aviat Networks Customer Support, the contact information is
available from the ProVision Help menu.
Procedure
1. Select Help > Customer Support. The Customer Support Information window dis-
plays.
2. To view the contact details of your region’s Aviat Networks Customer Support cen-
ter, select the Technical Assistance tab.
Viewing ProVision’s Version Number

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
1. Select Help > About ProVision. The About ProVision window displays, including
the version number.
40 AVIAT NETWORKS
Using the Online Help

The online help module you receive with ProVisionprovides complete documentation of
ProVision, including:
l User Manual
l Installation and Administration Manual
l Alarms
l Technical Support Information
The online help displays using the default Web browser on the PC. The online help user
interface is shown below:
Figure 3-1. ProVision Online Help
614-330055-001 DECEMBER 2015 41

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
NOTE : The Pr oVis ion online help dis plays in your default HTML
br ow s er . The Pr oVis ion help is inc luded w ith the Pr oVis ion s oftw ar e. You
do not need a link to the Inter net to us e the Pr oVis ion help and its fea-
tur es .
1. From the menu bar, select Help > Help Topics. The ProVision online help window
displays.
2. To navigate the online help, use the tabs in the left navigation panel:
l Contents - Enables you to view the information headings organized by subject.
Expand the top-level headings to view the subtopics.
l Index - The index is used to find important terms and display the related
topic.
l Search - Enables you to search for any character string in the help set.
l Glossary - View definitions in the Glossary listing.
l Favorites - Bookmark topics you refer to often in Favorites.
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.
42 AVIAT NETWORKS
614-330055-001 DECEMBER 2015 43

The ProVision User Interface

From the main ProVision interface, you can perform all the required functions to man-
age network responsibilities, quickly and effectively.
Figure 3-2. Main User Interface
The functions of the main user interface are described in the following sections:
l Customizing the User Interface on page 44
l Menu Bar on page 45
l Main Tool Bar on page 51
l Map Viewer on page 63
l Event Browser on page 80
l Using Search to Search All ProVision Data on page 83
Customizing the User Interface

This table lists the ways you can customize the user interface.
Table 3-1. Customizing the Main User Interface
44 AVIAT NETWORKS
Required Result Action

Main User Interface
To minimize, maximize, or Select the required button from the buttons located
close the interface window in the upper right corner.
To resize the interface window Click and drag any of the outside edges of the inter-
face window.
Physical Viewer
To resize the Physical Viewer Click and drag the vertical split bar.
To hide the Physical Viewer Select the X the Physical Viewer toolbar.
To show the Physical Viewer In the Window menu, select Physical.
Map Viewer
To resize the Map Viewer panel Click and drag the vertical split bar.
To hide the Map Viewer Select the X on the Map toolbar.
To show the Map Viewer In the Window menu, select Map.
To add a background Select Map Properties on the Map toolbar to add a
JPG background for the map. You can add different
JPG backgrounds for Physical and Flat Map views
of the network.
Event Browser
To resize the Event Browser Click and drag the horizontal split bar.
To hide the Event Browser Select Hide.
To show the Event Browser In the Window menu, select Events.
To change displayed Event values In the Event Browser toolbar, select Browser
Options to edit browser options.
Menu Bar
The menu bar contains menu items and pull-down options used to access common,
non-device specific functions such as:
l Event Browsers
l Security Management
l Reporting and Data Collection
l Scheduling configuration operations
l Help System
NOTE : The menu bar items dis played on the main us er inter fac e may
var y depending on your us er ac c es s pr ofile.
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.
614-330055-001 DECEMBER 2015 45

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 inform-
ation, see Right-Click Menus on page 53.
Table 3-2. Menu Bar Items And Pull-Down Options
Menu Item 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 ver-
sion of ProVision to ProVision.
For more information see the ProVision Installation and Administration
Guide, Migrating Topology.
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.
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 37
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 83. You can also select the
search icon on the tool bar.
46 AVIAT NETWORKS
Menu Item Function

Fault Device Maintenance
View the sleep status of all devices.
Event Browser > Security Log
View the ProVision Security Log.
Event 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.
You can also use the add Event Browser View icon, and the drop-
down arrow to display saved Event Browser views.
Event Analyzer
Enables you to view and run the Event Analyzer.
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.
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 Scen-
arios on page 367.
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 per-
formance.
For more information on the Event Pre-filters, see Event Notification on
page 341.
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 341.
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
342.
Client Notification Dialogue
View the Event Notification dialogue.
614-330055-001 DECEMBER 2015 47

Menu Item Function

Configuration IP Address
Enables you to view and change IP information assigned to devices on the net-
work.
License Loading
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 and CTR Node Licenses on page 237.
Configuration Profiles
Enables you to apply settings to multiple radios.
For more information, see Configuration Profiles for Bulk Configuration
on page 201.
ProVisioning
Enables you to run Provisioning functions. Select Circuit, VLAN, EOAM, or
ERP.
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 221.
Software Loading Preferences
Enables you to update the software of the Eclipse radios. The functions
include Software Register and Server. For more information, see Load-
ing/Activating New Software and Licenses on page 221.
Network Auto-Discovery
Set up specific devices to be auto-discovered.
Circuit Collection Preferences
Set up circuit collection time preferences.
Global Circuit Trace
Enables you to run a global circuit trace.
Edit User Defined Icons
Enables editing of user defined icons, see About User Defined Icons on
page 91
48 AVIAT NETWORKS
Menu Item Function

Reports Help Desk
Creates a report for you to send to the Help Desk when you need support.
Inventory
Enables you to run an Inventory report for a selected radio.
Capacity
Enables you to run a Capacity report for a selected radio.
Network Health
Enables you to run a Network Health Report. Select from the available NHR
options.
Security Status
Collects security data for one or more Eclipse devices.
Clock Sync
Enables you to view clock synchronization status and values for clock sync sup-
ported devices.
Custom Reports
Enables users to create customizable reports for devices.
Scheduled Reports
Provides ability to schedule reports to run on a regular basis.
Server Reports
Enables you to view generated Server reports.
Link Reports
Enables you to run a Link Report.
Performance Data Collectionn
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 388.
Thresholds
Set data collection thresholds for devices in the network.
Ethernet Bandwidth
View Ethernet Bandwidth use for Eclipse devices.
Clock Sync Performance Metrics
Enables setting and viewing of Clock Quality threshold and Clock Stability
threshold.
614-330055-001 DECEMBER 2015 49

Menu Item Function

Administration User Accounts
This is an administrative function. It enables you to create, delete, and view
all user accounts. For more information see Access Control.
Change User Details
Enables you to change your contact details and password. For more inform-
ation see Entering Your Contact Details on page 38.
Session Manager
Enables an administrator to manage user access to ProVision sessions.
Database Purge
Enables you to set the purge criteria and the time of day that the purge pro-
cess occurs. See 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 Database and Server Management .
Backup Preferences
Enables you to set and save backup preferences. See Set Backup Prefer-
ences.
Server Redundancy
Enable backup server redundancy. See Standby Server Configuration Pre-
requisites.
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 Access Control.
Eclipse Portal Locking
Locks write access to Portal from ProVision. See Locking Eclipse Portal
Write Access from ProVision.
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 ProVi-
sion. See Generic Device Management .
Email Server Configuration
In this screen, you note the IP address of your email server, used when ProVi-
sion sends an email message about an event. See Set the Server Noti-
fication Preferences on page 342.
RADIUS Server Configuration
Allows administrator to enable and configure ProVision RADIUS server
authentication. See Enabling a RADIUS Server.
50 AVIAT NETWORKS
Menu Item Function

Window Click on an item to view or hide that window in the ProVision screen display.
- Physical
- Logical
- Circuits
- VLAN
- EOAM
- Map
- Events
- Reset Layout = Resets the Window layout back to 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 con-
tact details.
About ProVision
Displays the version of ProVision that is installed.
Main Tool Bar

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

Search Enables you to rapidly find specific objects.
See The ProVision User Interface on page 44 .
Task Man- Lists all tasks, completed or otherwise, that have been executed
ager in ProVision. Pop-up windows provided additional information
and functions when executing tasks. See Loading/Activating
New Software and Licenses on page 221.
Server Saves and retrieves reports from a single radio or from multiple
Reports radios.
For more information see View / Save / Delete Server
Reports on page 469 .
614-330055-001 DECEMBER 2015 51

Icon Name Definition

Global Cir- Runs a global circuit trace on all circuits in the system. See See
cuit Trace "Running the Circuit Trace".
Event Enables you to open a new Event Browser and select saved
Browser Event Browser views. See Event Browser on page 80.
Score- Enables you to add a new Scoreboard group and view saved
board Scoreboard groups. See Scoreboard Group Scenarios on page
Groups 367.
Event Ana- Opens the Event Analyzer. See Event Analyzer on page 338.
lyzer
52 AVIAT NETWORKS
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.
To display a right-click menu:
1. Place the cursor over the object or event entry.
2. Right-click using the right-click button on the mouse.
In the ProVision screen, a right-click menu displays. The menu contains the function
options that are available with the selected object or event.
3. Drag the cursor to the desired menu option and left-click to select.
The window or dialog box displays.
Right-click menus are available for all items in the Tree Viewer and Map Viewers, includ-
ing:
l Containers
l Root levels
l NBI options
l Devices
l Device components
l Links
l Logical links
They are also available for all items in the Logical Container, including:
l Logical containers
l Circuits
l Events
Radio Right-Click Menus

Different radio types have different right-click menu options, based on the available func-
tions for the radio. An example of an individual radio right-click menu is shown below.
614-330055-001 DECEMBER 2015 53

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 addi-
tional options:
l Remote([radio] LINKn) - Displays the options for the remote radio that the
selected radio is connected; where “radio” is the name of the remote radio and
“n” is the remote radio’s slot number where the remote link hardware is
installed.
l Link - Displays the options for the link that connects the selected radio and
the remote radio.
NOTE : You c an s elec t multiple r adios /devic es and r ight-c lic k, and you
w ill view a gener ic r ight-c lic k menu. This menu inc ludes only the func -
tions that ar e s har ed amongs t all the devic es .
54 AVIAT NETWORKS
View Tabs: Physical, Logical, Circuits,

VLAN, EOAM
There are several tabs that provide tree views of ProVision devices:
l Physical - Displays the complete “tree view” of the entire network.
l Logical - Displays logical containers.
l Circuits - Displays circuits.
l VLAN - Displays VLANs.
l EOAM - Displays Ethernet OAM.
The topics covered in this section include:

l Physical Viewer and Icons on page 55
l Logical Tree Viewer on page 61
l Circuits Viewer Tab on page 61
l For information about the VLAN and EOAM tabs, see Viewing Discovered
VLANs on page 245 andViewing Discovered EOAM MAs on page 265
Physical Viewer and Icons

In the Physical View option, the entire radio network is represented as a tree of con-
tainers and devices. Each container (for example, a region) is represented as a parent,
with all the devices positioned underneath, as its children.
NOTE : A c ontainer is a c ollec tion of r elated objec ts ar r anged in a hier -

ar c hic al r elations hip. Objec ts c an have par ents and c hildr en.
614-330055-001 DECEMBER 2015 55

Figure 3-3. Tree Viewer - Physical Viewer
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 inform-
ation, see Right-Click Menus on page 53.
Reparent Objects
You can reparent objects within the Tree viewer in the Physical pane.
To do this, left-click on the mouse to select the objects and press the Ctrl key. Keeping
the Ctrl key pressed, move the objects to the new parent container. Do not release the
Ctrl key or the mouse at any point during this process.
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:
l Highlights the selected object in the Physical Viewer and
l Displays the map for the object in the Map Viewer.
Single-clicking an object with the right mouse button:
l Displays a right-click menu listing the options for that object and
l Opens the map for the object in the Map Viewer.
Service and Status Icons

When devices are in service, they display without any additional icons.
When devices are out of service, they display with this icon beside them:
56 AVIAT NETWORKS
An example of the Physical Frame with out of service devices is shown below:
Items with Clock Synchronization display with the Clock Sync icon beside them in the
map:
- Device is clock synced
- Clock source is external
Items with RAC LL and RAC LL DDR enabled display with an R or IF icon beside them
in the Tree Viewer and on their links in the Map:
Items that are Out of Service display with an icon beside them in the Tree Viewer or the
Map:
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 3-4. Containers used in ProVision
Container Icon Notes

ProVision The ProVision Manager generates ProVision related events, for
Manager example trial license expiry messages, and provides access to the
security log, license and customer support details.
Root The Root and ProVision Manager icons are automatically dis-
played in the Physical Viewer.
Region A region is a grouping of devices and/or sites that is typically geo-
graphically based.
614-330055-001 DECEMBER 2015 57

Container Icon Notes

Site A site is a location where a device or devices are stored.
Rack A rack represents a physical storage unit in which a number of

devices can be stored. At a large site, there may be several phys-
ical racks installed.
The table below lists the SNMP devices that can be deployed in ProVision.
Table 3-5. SNMP Devices
Device Icon
Accedian EtherNID, Accedian EtherNODE
ADR 155C: Aviat Networks ADR, ADR 2500: SAGEM ADR,

an add-on to the Altium.
Altium, Altium MX, and Altium MX 2+0
, , and
Aurora
Constellation
Control Alarm Unit
Cisco Devices: 2400, 2941, 3400, ASR 903
CTR 8500, CTR 8440

and
DART and DART (remote management)
and
DVA and DVM, DVM-XT
and
DXR 100 and DXR100 (protected)
and
Symmetricom TP1x00+ TP1100 and TP500
DXR 700 and DXR 700 (protected): DXR 700 radios are
and “discovered”/visible in the ProVision when the connected
DXR SMA is deployed.
58 AVIAT NETWORKS
Device Icon
Eclipse INU Node and Eclipse INUe Node (includes IDU
and 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:
Eclipse IDU Terminal: the Eclipse Terminal has a fixed lay-

out; ancillary parts are displayed as plug-ins.
E-Band E-Link 1000EXR, 1000LR
Memotec CX-U
EMS Proxy and Network Elements
LE3000, LE3200, WinLink 1000, Radwin 2000
MegaStar 1+ and M+N

and
MicroStar I, I (Protected), II, and II
Tellabs 8605, 8609, 8611, 8630, 8668
TRuepoint 6400, TRuepoint 5000, TRuepoint 4040, and

TRuepoint 4000
TRuepoint 6500 and TRuepoint 6500 double terminal

and
Velox
WTM 3100, 3200, and 3300
WTM 6000 and WTM 6000 Repeater
XP4 (remote management) 16xE1/E3/DS3 and XP4

and
16xE1/E3/DS3 (remote management, protected)
XP4 16xE1/E3/DS3 and XP4 16xE1/E3/DS3 (protected)
and
614-330055-001 DECEMBER 2015 59

Device Icon
XP4 2/4/8x (remote management) and XP4 2/4/8x
and (remote management, protected)
XP4 2/4/8x and XP4 2/4/8x (protected)
and
User Defined - based on user provided graphics - see
About User Defined Icons
Table 3-6. TNet Device Icons
Device Icon
Classic II
LC Series and LC Series (protected)

and
M Fiber
M Series and M Series (protected)

and
QUANTUM and QUANTUM (protected)
and
SPECTRUM I
SPECTRUM II and SPECTRUM II (protected)

and
TNet Proxy
W Series and W Series (protected)

and
Table 3-7. Generic SNMP Device Icons
Device Icons
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:
Symbol
Generic
Multiplexer
Router
Switch
Microwave Radio
Site Manager
Base Station
Timing System
Server
Firewall
Air Conditioner
Instructions for adding containers and deploying devices are described in Deploying
Devices on page 106.
60 AVIAT NETWORKS
Related Topics:
l Logical Tree Viewer on page 61
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 sever-
ity 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 359.
Figure 3-4. Physical Viewer - Logical Containers Tab
NOTE : By default, the L ogic al Container s tab is not populated at ins tall-
ation.
Circuits Viewer Tab

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 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 177.
614-330055-001 DECEMBER 2015 61

Figure 3-5. Physical Viewer - Circuits Tab
NOTE : By default, the Cir c uits tab is not populated at ins tallation.
62 AVIAT NETWORKS
Map Viewer
The Map Viewer provides two different views of the network:
l Physical Map View on page 63
l Flat Map View on page 64
The following object types are supported in the Map Viewer;
l Region
l Site
l Rack
l Device objects
l RF links
l 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:
l Map Tools on page 64
l Map Backgrounds on page 66
l Submaps on page 71
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:
614-330055-001 DECEMBER 2015 63

Figure 3-6. Map View
When an Eclipse Node is selected in the Physical Viewer, its chassis and components
are displayed in the Map view.
NOTE : The map help, map pr oper ties , zoom and padloc k func tions ar e
des c r ibed in Map Tools on p age 6 4 .
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 net-
work 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.
Map Tools
These are the functions in the ProVision Map toolbar.
64 AVIAT NETWORKS
Map Tool Icon Use

Physical Map Click this to view the Physical Map view.
Flat Map Click this to view the Flat Map view.
Navigate Up, Back, Use these arrows to navigate to different maps in the
or Forwards network.
Zoom to Fit Screen 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.
Enable/Disable Map The map zoom tool enables you to zoom in/out of the
Zooming 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 By default the map padlock is locked. This means that
Unlocked objects cannot be moved in the Map Viewer.
To move objects around in the Map Viewer, select the
padlock icon. The icon changes to an unlocked padlock.
Select the unlocked padlock, and the icon changes back
to the locked state. The objects in the Map Viewer revert
back to the default, locked state.
For additional information see Moving Containers
and Devices in the Map Viewer on page 153.
Flash for Unac- The Flash tool can be set to flash/blink as a visual indic-
knowledged Events ator that there are unacknowledged Events in this map.
This flashes for events of Minor, Warning, Major, and
Critical severity.
Map Mode Enables you to select the map view mode:
- Off - Displays standard Map View.
- VLAN View - Displays VLAN data.
- Clock Sync OAM View- Displays Clock Sync data.
See Clock Synchronization View.
Map Icon Size The Map Icon tool shrinks or enlarges device icons. This
is useful when you are zooming.
Auto-Arrange The Auto-Arrange tool automatically orders the device
icons in your map view.
614-330055-001 DECEMBER 2015 65

Map Tool Icon Use

Object Filter The map object filter tool enables you to search for and
select specific map items.
Properties The map properties tool enables you to add and change
map backgrounds. For more information, see Map
Backgrounds on page 66 .
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.
Help 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 fol-
lowing pop-up window defines the various links and
icons on the Map Viewer.
Map Backgrounds
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.
66 AVIAT NETWORKS
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:
l jpg
l gif (GIF87 and GIF89a)
NOTE : The map view er w indow s ize is 4096 X 3072 pixels . Us e image
editing s oftw ar e, s uc h as PhotoShop, to s ize the map image to this s ize.
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.
2. Select the Map Properties icon on the Map Viewer. The Map Properties win-
dow displays.
3. Select the checkbox to enable Background Image selection.

4. Select the Map Object Filter 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.
614-330055-001 DECEMBER 2015 67

To remove a map background image:

1. Within the Physical Viewer, select the view type from which you want to remove a
map background.
2. Select the Map Properties icon on the Map Viewer. The Map Properties win-
dow displays.
3. To remove the background image, deselect the Background Image checkbox.
4. To accept the change, select OK.
The Map Viewer displays with a blank background.
Related Topics:
l Physical Map View on page 63
l Submaps on page 71
68 AVIAT NETWORKS
Map Annotations
In the ProVision Map View, you can label specific items in a map. You can also apply a
label to the Container level of the devices, or to the map itself, using the Map Annota-
tions function.
The Map Annotation function is useful for:
l Naming regions or groups
l Providing notes
l Adding corporate identity
Procedure
1. Open a Physical Map in the Map View of ProVision.
2. Right-click on a blank space in the map. In the pop-up menu, select Add
Annotation.
3. The Annotation screen displays.
4. Use this screen to set the annotation text, image, and style.
614-330055-001 DECEMBER 2015 69

5. Click OK.
6. The annotation displays in the Map View. Whenever you open this Map
View, the annotation will display in the upper left corner.
Table 3-8. Annotation Screen Values

Item Value
Text
Text Type the text for the annotation.
Icon Optionally, you can select an icon from your PC. This can
be a custom image or a corporate logo, formatted as a
.jpg, .png, or .bmp file.
Icon Location Relative Whether the icon will be in front of (leading), below,
To Text above, or behind (trailing) the text
Style
Font Type, Font Size, Set the appearance of your font using these items. Note
Font Color, and Back- that for Font Size, you must use the up/down arrows to
ground adjust the size.
Opacity Set the opacity of the text and icon image. You may want
to use large text set at 50% opacity, to give it a trans-
lucent overlay of the map.
Preview What your selected text, icon, and style will look like.
70 AVIAT NETWORKS
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.
NOTE : Devic e view types not r equir ed for your loc ation may not be
inc luded in this doc umentation.
l Submap View - A view displaying managed elements of a device. See

Submaps on page 71.
l Equipment View - A real-time view of a device, based on the physical
configuration of the device. See Equipment Views on page 73.
l Interface View - A view displaying a device’s IF interfaces. See Interface
Views on page 78.
Submaps
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 func-
tional maps with their own menu and tool bar.
A submap can be opened for a container, device, RF link, Eclipse element (for example,
DAC, LINK) or Memotec CX-U element in either the Physical Viewer or Map Viewer.
Submaps display for Eclipse, CTR 8440, and CTR 8540.
Figure 3-7. Eclipse Submap View
614-330055-001 DECEMBER 2015 71

Figure 3-8. CTR Submap View
Use submaps to:

l Have several submaps open at any one time; these can be maximized or
minimized as required.
l Perform specific operations on a submap using its menu and tool bar.
l Increase the Physical Viewer size by minimizing the Map Viewer and
displaying submaps.
Procedure
1. Right-click the container or device (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.
4. If a plug-in is missing, its space includes a question mark icon, as shown below:
NOTE : If the devic e’ s r ight-c lic k menu s ays Open Submap, the view that
dis plays is s imilar to the Flat Map option. Thes e devic es us ually have
mor e detailed Equ ip ment Views on p age 73.
72 AVIAT NETWORKS
In and Out of Service View

When devices are in service, they display without any additional icons.
When devices are out of service, they display with this icon beside them:
An example of the Submap with out of service devices is shown below:
Equipment Views
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 com-
ponents, exactly as they are installed.
Equipment Views are available for the following radio types:
l ADR 155c
l ADR 2500
l Constellation
l MegaStar M:N and 1+1
l TRuepoint 4040 and 5000
l TRuepoint 6400
l TRuepoint 6500
l WTM 6000
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.
614-330055-001 DECEMBER 2015 73

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.
NOTE : ADR equipment view s ar e only available for ADR155c or 2500 if

the ADR fir mw ar e is later than P2. 6.
ADR 2500
The ADR 2500 displays with this equipment view.
74 AVIAT NETWORKS
Constellation
The radio below is a Constellation terminal.
The radio below is a Constellation repeater, set up for two links.
614-330055-001 DECEMBER 2015 75

MegaStar M:N and 1+1

This radio displays at two levels in the equipment view; the shelf and the specific equip-
ment 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:
76 AVIAT NETWORKS
TRuepoint 6400
614-330055-001 DECEMBER 2015 77

TRuepoint 6500
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:
l Accedian
l Cisco devices
l CTR 8440, 8540
l CTR 8611 (cannot enable Ports from the Interface view for CTR 8611)
l Juniper M7i/10i
l Generic Devices
l Symmetricom
l Tellabs 8600 (cannot enable Ports from the Interface view for Tellabs 8600)
l WTM 3300
The color of the interface shows the interface status:
l Green = Connected
l Red = Disconnected
l Gray = Disabled
78 AVIAT NETWORKS
Procedure
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 enable ports for an interface, right-click on an interface and select Port Enable.
6. To view the Event Browser for this item, click the Event Browser button .
614-330055-001 DECEMBER 2015 79

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-fil-
tering. For details see Event Management Procedures on page 299.
By default, unacknowledged active events are listed in chronological order, with the
most recent events displayed at the top of the list. A maximum of 1000 events can be
displayed in the main Event Browser.
Figure 3-9. Main Event Browser
# Value
1 Severity
2 Status
3 Acknowledged/Unacknowledged
4 Note
5 Notification Dialog boxes
6 Event Severity and Counts
Status Bar
The status bar provides the following information:
l The user currently logged on.
l The ProVision server to which you are connected.
l The number of active notification dialog boxes. For more information Set the
Server Notification Preferences on page 342.
l The event severity counts, color-coded representations of the total number of
events of each severity type.
80 AVIAT NETWORKS
NOTE : To view only the events of a par tic ular s ever ity, for example
major events , in a s epar ate Event Br ow s er w indow , s elec t the c olor -
c oded event s ever ity c ount.
Event Browser Menu

The right-click menu has additional functions for the main Event Browser.
l 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 326.
l 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 321.
l Save Settings saves the current Event Browser settings.
l Maximize/Hide allows you to display and hide the Event Browser view.
l Certain events, particularly the WTM 3300 Performance Threshold event,
include pop-up notes with value details
Customizing the Main Event Browser

In the main Event Browser, you can change how the information displays.
1. To move a column, click and drag the column title bar to the required
position.
2. 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, Customizing Event Browsers on page 297.
614-330055-001 DECEMBER 2015 81

The Task Manager Screen

The Task Manager screen shows the status of tasks in progress, including the start and
end time of the task. 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.
You can Filter the Task Manager screen to view tasks for specific devices, hop counts,
containers, or dates/times. Click on the Filter button, then enter the value in the Filter
field.
NOTE : While Pr oVis ion c an r un multiple tas ks s imultaneous ly, it w ill

not r un multiple ver s ions of the s ame tas k. For example, only one Invent-
or y Repor t c an be gener ated at a time.
82 AVIAT NETWORKS
Using Search to Search All ProVision

Data
ProVision’s main search function enables you to find specific data in the ProVision sys-
tem. 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.
NOTE : The s ear c h text field s ear c hes detailed devic e pr oper ties : Clas s
Name, Name, IP Addr es s , State, SNMP Ver s ion, Ec lips e L ic ens e
Ser ial Number , Softw ar e Ver s ion, Devic e Sub-Type (e. g. , RAC 6x),
Devic e IDU Type (e. g. , INUe).
NOTE : To s ear c h for devic e s ubtypes , s uc h as RAC L L , s pec ify the s ub-
type us ing the w ildc ar d as ter ix in the Sear c h field, for example, *RAC
L L . This is c ur r ently r equir ed for this type of s ear c h.
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. For a fast
search, enter a value in the Search: field and click Search Now.
Click on More Criteria to view the full Search screen:
614-330055-001 DECEMBER 2015 83

2. The Search window lists the criteria that you can enter to narrow your search:
l Search - Enter any value or property that you want to search on.
l Physical Container - Enter a Physical Container name.
l IP Address - Enter a full or partial IP address.
l Object Type - Select Object Types from the drop-down menu. Note that you
can search for one object type or multiple object types.
l Object State - Select Object States from the drop-down menu.
l Devices with Pre-Filter Enabled
l Devices with Performance thresholds Enabled
l Devices with Ethernet 15-min or standard data collection every 15 minutes,
Daily
l Devices with Customized events Enabled
l Devices that are Out of Service Enabled
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 des-
cending order.
4. You can right-click an object or a container in the search results screen to view
associated right-click menus. See the Search Result Examples below for a sample of
this.
5. To clear the results, or to enter data for another search, click New Search.
6. To close the Search window, select Close.
Search Result Examples

The figure below shows a search result using text. The asterisks before and after the text
enable wildcard searching, to find all device values that include that text.
84 AVIAT NETWORKS
The figure below shows a search result for a specific IP Address. 10.16.10.199 is the IP
address of an Eclipse INU. The Eclipse radio and its components are displayed as a res-
ult of the search. Note that an item has been right-clicked and displays a menu with
available functions.
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 col-
lection enabled.
614-330055-001 DECEMBER 2015 85

86 AVIAT NETWORKS
Searching the Tree Viewers

ProVision’s Find search function enables you to find specific data in any of the ProVi-
sion 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 Tree Viewer.
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 for a wildcard search:
l North* = An asterisk after the value; finds all items that begin with this value.
l *North = An asterisk in front of the value; finds all items that end with this
value.
l *North* = An asterisk before and after the value; finds all items that contain
this value.
l N*th = An asterisk within a value; finds all items that begin and end with the
noted values.
l To search for device subtypes, such as RAC LL, specify the subtype using the
wildcard asterix in the Search field, for example, *RAC LL. This is currently
required for this type of search.
614-330055-001 DECEMBER 2015 87

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

3. To start the search, either press the Enter key, or click the Up and Down icons in
the Tree Search. The Tree Search function will go up or down the Tree View and high-
light 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.
88 AVIAT NETWORKS
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 ele-
ments. This alerts you to changes in device status.
To identify potential problems, ProVision propagates the alarm state of objects upwards
through each object, and its parent objects change color as well. A parent object’s color
reflects the most severe alarm on any of its children.
This section covers the following topics:
l Viewing Radio Icon Anatomy on page 89
l Alarm Severity Color Coding on page 91
l Device States on page 92
l Radio Tasks on page 93
l See About User Defined Icons on page 91
l Also see Physical Viewer and Icons on page 55 for a list of all device icons
Viewing Radio Icon Anatomy

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

# Value
2 If an event is present, the color here indicates the
event severity. Mouse over this to view the event
type.
3 Radio icon.
4 Task.
5 Radio name.
Map Viewer for Radio Icon Anatomy

The figure below shows an example of an XP4 radio icon displayed in the Map Viewer.
Each radio icon shown in the Map Viewer, or a submap, displays information about the
network element the icon represents. The information includes the radio’s name, state,
and event information.
Figure 3-11. Map Viewer - Labeled Radio Icon
# Value
1 If an event is present, the color here indicates the
event severity. Mouse over this to view the event type.
2 Radio icon.
3 Radio state and task. The current state of the radio.
For more information, see Device States on page 92
4 Radio name. Identifies the specific radio (network ele-
ment) represented by this icon.
5 Mouse over displaying event details.
90 AVIAT NETWORKS
About User Defined Icons

When deploying some device types, such as a Generic Device Symbol, users can enter
customized icons.
User defined icons:

l Can be .jpg, .bmp, or .png graphics
l Can be up to 2.4 MB in size
l Are automatically resized to match icon shape and format
To remove a user-defined icon from a device, right-click the device in the Map view.
Select Remove Customization. The device icon will change to a default.
To manage user-defined icons, go to the Configuration menu and select Edit User
Defined Icons. You can delete or edit selected icons from here.
Alarm 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 3-9. Event Color Codes
Severity Level Color Code

Critical Red
Major Orange
614-330055-001 DECEMBER 2015 91

Severity Level Color Code

Minor Yellow
Warning Cyan
Normal Green
Informational White
Device States
A device state defines the conditions in which a device exists. State representation is
based on Telecom standards that include:
l OSI state dictionary (based on the OSI SMF 10164-2 standard)
l Event state dictionary to display the set of events
A radio can only be in one state, but can have a number of tasks applied to the events it
is generating. When a radio has more than one task, a + sign displays on the state indic-
ator. 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.
Figure 3-12. Radio With Pop-up Text
This table lists the various states for devices, and how these states are indicated in the
user interface.
Table 3-10. Device States
92 AVIAT NETWORKS
Device State Icon Other Indicators

Unmanaged - Event severity is blue. The pop-up text displays State: Unman-
aged.
Managed - Event severity can be any of the colors - green, cyan, yellow,
orange, or red. The pop-up text displays State: Managed.
For more information on managing a device, see Managing a
Device on page 156 .
Connecting ProVision is attempting to connect to the device across the network
using the device’s IP address. There has been no communication
from the device since being managed. The pop-up text displays
State: Connecting.
Asleep The radio is asleep. The pop-up text displays State: Asleep.
For more, see Sleep Status for a Device.
Errored The managed radio is not responding to polling from ProVision.
The pop-up text displays State: Errored.
“+” icon If a “+” icon appears in the bottom left corner of a task icon, this
indicates that more than one radio task and/or device state is asso-
ciated with that radio. The pop-up text displays the additional
tasks/states.
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 dis-
plays with the task icon, for example, pre-filtering.
Table 3-11. Radio Tasks
Radio Task Icon

Pre-filtered For more information about pre-filtering events, see
Event Log Pre-Filtering on page 326 .
15-minute data col- ProVision uses the data from the radio to create per-
lection formance trends graphs. See Data Collection on page
388 for more information.
Performance Performance thresholds feature allows you to associate an
Thresholds alarm or group of alarms with unexpected performance
results. See Performance Thresholds on page 413 for
more information.
“+” icon If a “+” icon appears in the bottom left corner of a task
icon, this indicates that more than one radio task and/or
device state is associated with that radio. The pop-up
text displays the additional tasks/states.
614-330055-001 DECEMBER 2015 93

94 AVIAT NETWORKS
Integrating Windows Applications with

ProVision
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 device’s 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).
NOTE : For eac h applic ation to be us ed, the applic ation files need to be
ins talled on eac h individual Pr oVis ion c lient. Note the s ys tem loc ation
w her e the ins tallation files ar e s aved, for us e in the launc h c onfigur ation
pr oc edur e.
Procedure
1. On the ProVision Client, install the Generic Device craft tool or tools.
614-330055-001 DECEMBER 2015 95

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:
l 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: .
l 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.
l 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:
l Name - Enter the name of the craft tool application.
l Executable Path - Navigate to the location of the device craft tool executable
file (.exe). Select the .exe file.
l 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.
5. To enter additional Applications, click Add again. You can save multiple Applic-
ations for each device, as shown.
6. When you are done, click OK.
7. The applications are now directly integrated with ProVision.
l 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.
l 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.
96 AVIAT NETWORKS
Linking Documents to Devices and Maps

You can link documents to devices and to the main Map display in ProVision, to con-
veniently launch reference documents directly from ProVision. This is done by setting up
an integrated Windows application, then linking a document to run when that applic-
ation is opened.
There are two levels of this:
At the device level, to display in a device’s right-click menu. This links the doc-
ument to that particular device type, and it displays in the right-click menu for all
instances of that device type.
At the main Root level, to display in the main ProVision toolbar. This does
not link the document to any device type, and it is available for all users.
NOTE : For eac h doc ument and applic ation to be us ed, the files need to
be ins talled on eac h individual Pr oVis ion c lient. Note the s ys tem loc ation
w her e the files ar e s aved, for us e in the launc h c onfigur ation pr oc edur e.
614-330055-001 DECEMBER 2015 97

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:
l 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: .
l 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.
l 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:
l Name - Enter the name of the application.
l Executable Path - Navigate to the location of the application executable file
(.exe). Select the .exe file.
l Parameters - Navigate to the location of the document and enter the link to
the document.
5. To enter additional Applications/Documents, click Add again. You can save mul-
tiple documents for each device, as shown.
6. When you are done, click OK.
7. The applications and their linked documents are now directly integrated with
ProVision.
l Linked documents 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.
l The right-click menu for the device now displays Applications >(Application
Names), and you can open the documents from there.
98 AVIAT NETWORKS
8. If you need to update the document, open Applications > Edit Applications
again. This re-opens the Edit Applications screen. Make changes to the document
link from this screen.
614-330055-001 DECEMBER 2015 99

Chapter 4. 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 Networks 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.
l About Deploying and Managing Devices on page 102
l Deploying Devices on page 106
l Managing Devices on page 156
l Configuring and Synchronizing Devices on page 192
l Circuit Management on page 177
l Configuring and Synchronizing Devices on page 192
l Loading/Activating New Software and Licenses on page 221
For Carrier Ethernet functions, including VLAN, Ethernet OAM, and ERP ring, see Car-
rier Ethernet Management on page 243.
614-330055-001 DECEMBER 2015 101

CHAPTER 4. DEPLOYING AND MANAGING DEVICES
About Deploying and Managing Devices

For a radio network, the majority of devices in the network are already physically
installed, commissioned, deployed, and managed in ProVision. When new towers/sites
are installed, the NOC operator/engineer deploys and manages the new devices in ProVi-
sion.
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. Deploy-
ing 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 loc-
ations, radio types, and IP addresses.
To enable you to group devices by location, ProVision includes the following containers:
Region Site Rack
When setting up the network in ProVision you can choose to use any or none of the con-
tainer objects. If the network is already set up and you are deploying new devices, then
follow the existing pattern.
NOTE : A high level c ontainer c an have additional c ontainer s and

devic es . For example, a r egion may c ons is t of s ever al s ites and devic es
Deployment Guidelines
When deploying Aviat Networks devices, you must create your site hierarchy before
deploying any devices. Once you have deployed a device, you can change the site hier-
archy placement of the device at any time.
Naming Standards
You and your company choose the naming standards to apply to your ProVision net-
work. 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:
l 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:
o Eclipse A-1 10.14.135.1
102 AVIAT NETWORKS

o Eclipse B-1 10.14.135.3

o 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 ProVi-
sion management process.
1. Install ProVision.
2. Is this installation an upgrade?
l If Yes, after you install the upgrade, import the saved topology.
l 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 per-
formance trend analysis of G.826 and RSL/RSSI.
Deployment and Management

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, is not polled for status, and the event state color is blue, which signifies an
unmanaged status.
The Process for Deploying and Managing Devices

Prerequisites
To deploy and manage devices, you must have all of the following information:
l A comprehensive network element inventory
l List of all the sites, each device name and its type
l Know any device specific details
l Determine IP address assignments
l 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 devices.
614-330055-001 DECEMBER 2015 103

Deploying Devices
This is the recommended process for deploying Aviat Networks devices in an existing
network.
1. Add a new Container, if required.
2. Deploy the new Radios.
3. If required (for example, for new TRuepoint devices) update their
4. configuration.
5. Manage the new devices.
6. Create links.
7. Verify the new links.
8. Verify that ProVision is receiving events from the devices.
9. Check that the devices, and their links, are all configured correctly.
Pre-Deploying Devices
When you are pre-deploying devices 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
devices.
1. Add a new Container, if required.
2. Deploy the new devices.
3. Create links.
4. Verify the new links.
5. Manage the new devices.
6. Verify that ProVision is receiving events from the devices.
7. Check that the devices, and their links, are all configured correctly.
CAUTION: This process is not applicable to the DXR 700 and Eclipse Node devices.
A DXR 700 is auto-discovered when the DXR SMA to which it is connected is managed
in ProVision, and therefore the device is managed before you can create the link. The
Eclipse Node uses plug-ins, which means its configuration is auto-discovered when
the device is managed in ProVision. Only then can you create a link or links.
Device Deployment By Type

Table 4-1. Device Deployment Instructions by Device Type
104 AVIAT NETWORKS

Device Deployment Details

CAU CAU (Control Alarm Unit) Deployment on page 122
Cisco Cisco Deployment on page 123
Constellation Constellation Device Deployment on page 124
DXR 200 DXR 200 and DXR SMA Device Deployment on page 120
DXR SMA DXR 200 and DXR SMA Device Deployment on page 120
Eclipse Eclipse Devices and Nodes Deployment on page 117
Generic Generic Device Deployment on page 128
Symmetricom Symmetricom TP1x00 Deployment on page 135
TNet TNet Device Deployment on page 144
TRuepoint 4000 TRuepoint Device Deployment on page 138
TRuepoint 6500 TRuepoint 6500 Device Deployment on page 142
All Other Devices Standard SNMP Device Deployment on page 112
Includes ADR 155c, ADR 2500, Altium, Aurora, Cisco, CTR 8500,
DART, DVA, DVM, DVM-XT, DXR 100, E-Link, LE 3000, LE 3200, all
MegaStar, Memotec CX-U, all MicroStar, SAGEM-LINK, SPECTRUM
II SNMP, Symmetricom Timers, Tellabs, Velox, Radwin WinLink
1000, Radwin 2000, XP4
614-330055-001 DECEMBER 2015 105

Deploying Devices
This section covers the following deploying procedures:
l Adding, Editing, and Deleting Device Containers on page 106
l Standard SNMP Device Deployment on page 112
includes legacy, MicroStar, MegaStar, DVA
l Eclipse Devices and Nodes Deployment on page 117
l TRuepoint Device Deployment on page 138
l TRuepoint 6500 Device Deployment on page 142
l Constellation Device Deployment on page 124
l CAU (Control Alarm Unit) Deployment on page 122
l Generic Device Deployment on page 128
l Cisco Deployment
l CTR 8300 and 8540 Device Deployment on page 125
l Symmetricom TP1x00 Deployment
l Symmetricom TP5000 Deployment
l TNet Device Deployment on page 144
l DXR 200 and DXR SMA Device Deployment on page 120
l Troubleshooting Device Deployment on page 152
l Changing a Device’s Container on page 152
l Moving Containers and Devices in the Map Viewer on page 153
l Renaming a Device on page 153
l Deleting a Device on page 154
Adding, Editing, and Deleting Device Containers

A container represents an object that serves as a grouping entity for devices in ProVi-
sion. Other containers are added to a parent container, and devices are deployed from
their container.
This section describes the following Container functions:
l Adding a Container on page 107
l User Defined Containers on page 108
l Renaming a Container on page 111
l Deleting a Container on page 111
106 AVIAT NETWORKS

Adding a Container
The following procedure describes how to add a standard container. There are three
types of container available:
l Region - Use as a container for Sites.
l Site - Use as a container for radios and/or Racks.
l Rack - Use as a container for Radios.
If you need to define your own container type, see User Defined Containers on page 108.
Procedure
1. In the Tree Viewer or the Map Viewer, right-click on a root icon or an existing con-
tainer, for example, the network or a region icon.
2. In the right-click menu, select Deploy Object. The Deployment window displays.
l Click on Containers. The Containers Family window displays.
3. Select the required Container icon, for example, Site. The Deploying <container>
window displays.
614-330055-001 DECEMBER 2015 107

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.
l The Tree Viewer and the Map Viewer’s Hierarchical layer are updated and
display the new containment icon.
l The Deploying <container> results window displays, confirming that the
container has been deployed.
7. Select Close.
NOTE : The c ontainer c an be r eas s igned to another par ent.
User Defined Containers

You can create user-defined containers. This enables you to have container icons and
types defined by your organization.
NOTE : You mus t pr ovide your ow n c ontainer ic ons , in . jpg for mat. The
c ontainer ic ons ar e automatic ally s hr unk to a s mall dis play s ize w hen
they ar e deployed in Pr oVis ion. A s ize of 45 pixels w ide by 35 pixels high
is r ec ommended.
108 AVIAT NETWORKS

Procedure
1. Obtain your Container icon graphics in .jpg format. Save them on the same PC as
your installation.
2. In the Tree Viewer or the Map Viewer, right-click on a root icon or an existing con-
tainer, for example, the network or a region icon.
3. In the right-click menu, select Deploy Object. The Deployment window displays.
l Click on Containers. The Containers Family window displays.
4. Click the User Defined Container icon. The User Defined Container window dis-
plays.
614-330055-001 DECEMBER 2015 109

5. In the Container Type field, enter the Type of container you are defining.
6. To use a previously loaded icon, select it in the Existing User Defined Icons
frame.
7. To load a new icon, enter the icon's Type in the field. Then, click the Select Icon
button. From your PC, choose the .jpg graphic for the container icon. It displays in
the User Defined screen.
8. Click Next.
l The Deploying <container> results window displays, confirming that the
container has been deployed.
l The Tree Viewer and the Map Viewer’s Hierarchical layer are updated and
display the user-defined container icon.
110 AVIAT NETWORKS

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

3. To save the changes, select OK.
Deleting a Container
You can delete a container from the Tree Viewer or the Map Viewer’s Hierarchical layer.
When a container is deleted, the Tree and Map Viewers are refreshed and the container
is no longer displayed.
CAUTION: Before deleting a container, ensure there are no managed radios or
links associated with the container.
NOTE : If you delete a c ontainer that c ontains r adios this has no effec t
on the ac tual r adios or the c ommunic ations tr affic they ar e c ar r ying.
Procedure
1. Right-click the container icon. In the right-click menu, select Delete. The Delete
Objects window displays.
614-330055-001 DECEMBER 2015 111

2. To delete the selected object(s), select Yes.
Standard SNMP Device Deployment

Aviat Networks or third-party SNMP devices have an IP address, can be accessed via IP
networks, and use 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.
NOTE : When a devic e is deployed but not managed in Pr oVis ion, the
devic e does not gener ate alar m tr aps , and is not polled for s tatus . The
event s tate c olor dis plays as blue, w hic h s ignifies an unmanaged s tatus .
This section describes how to deploy standard SNMP devices. To help you deploy spe-
cific device types, see also Device Deployment By Type on page 104.
Prerequisites
l Cisco - For each Cisco device, you must adjust the CLI settings with
ProVision's IP address. See Cisco Deployment on page 123
l CTR 8540 - For each CTR 8540 device, you must set up SNMP and trap
commands, both in the device before ProVision deployment, and within
ProVision. See CTR 8300 and 8540 Device Deployment on page 125.
l MicroStar - For each MicroStar device you are deploying in ProVision, you
must find that device in WebCIT and set up ProVision’s IP address as the
manager of that device. This setting is found in WebCIT via the Provisioning
screen, in Network Setting 2 , as the value SNMP Manager #1. See the
WebCIT Operator manual for further details.
l MegaStar - For each MegaStar device you are deploying in ProVision, you
must find that device in FarScan and set up ProVision’s IP address as the
manager of that device. See the FarScan Operator manual for further details.
l Symmetricom - For each Symmetricom TP5000 device, you must adjust the
CLI settings with ProVision's IP address. See Symmetricom TP5000
Deployment on page 137. For each Symmetricom TP1x00 device, you must
find it in the TimeCraft craft tool and set up ProVision's IP address. See
Symmetricom TP1x00 Deployment on page 135
112 AVIAT NETWORKS

l Community Strings -Many devices require read and write community

strings. The community string (which is a name or combination of characters)
is part of the device’s configuration information. When ProVision wants to
communicate with the device, it authenticates using the community string.
There are typically two community strings linked with a device, one for
reading values and one for writing (setting) values. These are normally set to
“public” or “private”, but can be set to other values as a form of security.
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.
NOTE : If you c annot immediately find the ic on for the devic e type, tr y
Mic r ow ave Radio or Ether net. Then, s elec t the r equir ed devic e ic on.
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.
NOTE : For all new devic es , c hec k to s ee that the Par ent is c or r ec t. T h e
d evice is p l aced u n d er th e p aren t l isted .
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.
Table 4-2. Device Deployment Details for Standard SNMP Devices
614-330055-001 DECEMBER 2015 113

Device Deployment Window Steps

Single Devices: Accedian EtherNID,
Accedian EtherNODE, Aurora, Cisco, CTR 8440,
DVA, DVM, DVM-XT, ADR, Altium, DART, Velox,
XP4, Symmetricom, SPECTRUM II SNMP, DXR
100, ELink, Memotec CX-U, LE3000, LE 3200, Rad-
win WL1000 and RW2000, Tellabs.
In the Name field, type a descriptive name for the radi-
o.The radio is labeled with this name in the User Inter-
face.
Enter the radio’s IP address.
If present, the Read Community and Write Com-
munity 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.
To have ProVision start managing the radio, select the
Manage checkbox.
Protected Radios: DXR 100, XP4, DVM (repeater)
SAGEM-LINK
In the Name field, type a descriptive name for the radio.
The radio is labeled with this name in the User Interface.
Enter the A radio’s IP address.
Enter the B radio’s IP address.
The Read Community and Write Community strings
have the default values. Only change them if the radio set-
ting has been changed.
Manage checkbox.
Multiplexes: ADR 155C, ADR 2500
In the Name field, type a descriptive name for the
MicroStar 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.
To have ProVision start managing this radio, select the
Manage checkbox.
114 AVIAT NETWORKS


MicroStar I, II, III
MicroStar device. It is labeled with this name in the User
Interface.
Manage checkbox.
MegaStar M:N
Megastar 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.
Manage checkbox.
MegaStar 1+1
In the Name field, type a descriptive name for the device.
It is labeled with this name in the User Interface.
Manage checkbox.
614-330055-001 DECEMBER 2015 115


Symmetricom Timing SystemTP1x00+ TP5000
Manage checkbox.
Select the SNMP Version, v2c or V3.
CTR 8540, WTM 3100

Manage checkbox.
Select the checkbox for Perform Class Checking on
Deployment. This checks that the radio class matches
the device deployment window data. If the device deploy-
ment data does not match the actual radio class, an error
message displays:
Click OK. Then, click Back and select the correct

device type.
Select the Set Device out of service check box if
required.
116 AVIAT NETWORKS


WTM 3200, WTM 3300, WTM 6000.
o.The radio is labeled with this name in the User Inter-
face.
Enter the radio’s IP address.
(For WTM 3200, both IPv4 and IPv6 addresses are valid.)
If present, the Read Community and Write Com-
munity strings have the default values. Only change them
if the radio setting has been changed.
Manage checkbox.
Select the checkbox for Perform Class Checking on
Deployment. This checks that the radio class matches
the device deployment window data. If the device deploy-
ment data does not match the actual radio class, an error
message displays:
Click OK. Then, click Back and select the correct

device type.
Select the Set Device out of service check box if
required.
Eclipse Devices and Nodes Deployment

Deploying Eclipse devices and nodes is similar to Standard SNMP Device Deployment
on page 112.
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.
NOTE : To deploy an Ec lips e Edge devic e, deploy it as an IDU; to deploy

an Ec lips e IRU 600, deploy it as an Ec lips e INU.
614-330055-001 DECEMBER 2015 117

NOTE : In addition, Adminis tr ator - level us er s c an auto-dis c over and

deploy Ec lips e devic es w ith Netw or k Auto-Dis c over y. See Net work
Au t o-Discov ery for Dev ices on p age 14 8.
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.
3. Select the Eclipse device that you require. Enter the values for it as follows:
Eclipse Node or Terminal (INU / INUe /
IDU)
Ensure the correct parent displays; the device is

placed under the listed parent.
In the Name field, type a descriptive name for
the radio.The radio is labeled with this name in
the User Interface.
Enter the radio’s IP address. Both IPv4 and
IPv6 addresses are valid.
To have ProVision start managing the radio, select
the Manage checkbox.
Select the checkbox for Perform Class Check-
ing 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 dis-
plays:
Click OK. Then, click Back and select the cor-

rect device type.
118 AVIAT NETWORKS

Protected Eclipse Node

placed under the listed parent.
the radio.The radio is labeled with this name in
the User Interface.
In the Name field, note whether the radio is an
IDU ES or an IDU GE.
Enter the A radio’s IP address.
Enter the B radio’s IP address. Both IPv4 and
IPv6 addresses are valid.
To have ProVision start managing the radio, select
4. When an Eclipse Node is deployed within ProVision, the Eclipse INU icon dis-
plays in the Tree Viewer, and the basic INU chassis displays in the Map Viewer.
5. When an Eclipse Node is managed, ProVision queries the radio to determine its
component layout, and populates the chassis with the results.
Figure 4-1. Eclipse Node that is deployed but not managed
NOTE : When an Ec lips e devic e is fully deployed, Pr oVis ion c aptur es all
of its plug-ins and IP addr es s es . This pr ovides s uppor t for r edundant
NMS c onnec tions .
614-330055-001 DECEMBER 2015 119

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:
l The DXR device communicates with the SMA.
l 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 con-
nected to a network of up to 255 other DXRs.
You can view SMA device configurations via the Configuration Manager and the Man-
agement 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 Col-
lection, 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 Man-
aged, and its DXR 700 terminals are not discovered.
A DXR SMA can have a maximum of four DXR 700s connected.
Figure 4-2. DXR SMA radio deployed in ProVision, but not Managed
Procedure
CAUTION: 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:
120 AVIAT NETWORKS

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

in this field. The device is placed under the parent listed.
o.The radio displays with this name.
Press the Tab key and type in the radio’s IP address.
To have the SMA discover its DXR terminals, select Dis-
cover DXR Terminals.
Manage checkbox.
Click Next. Then, on the window that displays, select
Deploy. The Deploying SMA results window displays.
Select Close.
4. After you have created the SMA, you are ready to set up the DXR 200 devices.
5. In the Tree Viewer, go to the container that includes the SMA. Right-click it and
select Deploy Object.
6. The Deployment window displays. Again, click on the DXR icon. In the DXR Fam-
ily screen, and select DXR 200.
The Deploying DXR 200 window displays.
Ensure the correct parent displays; the device is placed

under the parent listed.
o.The radio is labeled with this name in the User Interface.
Press the Tab key and type in the radio’s Network Port,
which will be one of the values A through D on the SMA.
Enter the Terminal Number of the DXR terminal.
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.
614-330055-001 DECEMBER 2015 121

CAU (Control Alarm Unit) Deployment

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 Networks
standards.
NOTE : The CAU is c onfigur ed and ins talled us ing ins tr uc tions in the CAU
- Contr ol Alar m Unit Ins tr uc tion Manual, P/N IMN-099945- E06, pr ovided
w ith the CAU.
Prerequisite
For each CAU you are deploying in ProVision, you must find that device in FarScan and
set up ProVision’s IP address as the manager of that device. This is required to manage
a CAU from ProVision. See the FarScan Operator manual for further details.
Procedure
1. Identify the IP addresses for connecting the CAUs.
Deployment window displays. Select the Other Microwave icon. The Other
Microwave device options are displayed.
3. Select the CAU device option.
4. The Deploying CAU screen displays. Enter the values for a CAU, as follows:
In the Name field, type a descriptive name for the CAU
device. It is labeled with this name in the User Inter-
face.
Select the Manage checkbox.
5. The CAU and its status can now be viewed from ProVision.
6. To set up the CAU further, Configuration Profiles for Bulk Configuration on page
201
122 AVIAT NETWORKS

Cisco Deployment
Before you deploy a Cisco device in ProVision, you must set up device trap hosting for
the ProVision server using the CLI commands for the device. This enables device com-
munication with ProVision. This is required for all Cisco devices:
l Cisco 2400/3400
l Cisco ASR 903
l Cisco ASR 1000
l Cisco Catalyst 2950/2960
l Cisco ME 3600/3650/3800
l Cisco 3900
l Cisco ME 3600X/Cisco ME 3800X
l Cisco MWR 2941
l Cisco SNS 3495
Follow these instructions for each Cisco device you need to manage with ProVision.
NOTE : For mor e details s ee individual Cis c o doc umentation.
Procedure
1. Obtain the IP address of the ProVision server you will use to manage the
device.
2. Telnet into the Cisco device.
3. Add the ProVision server IP address. Use the following commands to add
and save the IP address of the ProVision server.
enable
config terminal
snmp-server community public ro
snmp-server community private rw
snmp-server queue-length 100
snmp-server enable traps
snmp-server host <ProVision IP address> version 2c public
snmp-server trap link ietf
4. Exit the CLI command window for the device.
5. Log into ProVision and deploy the device.
614-330055-001 DECEMBER 2015 123

Constellation Device Deployment

Introduction
Constellation devices are deployed using the standard Deployment procedure in ProVi-
sion. After they are deployed, a Constellation discovery agent identifies the radios, and
notes their type. There are two types of Constellation radio:
Type Definition Tree Viewer Display
Terminals Terminals have one link. They
can be protected or unprotected.
Protected link =
Unprotected link =
Repeaters Repeaters have two links. They
can have both links protected,
both links unprotected, or they
can have one link protected and
one link unprotected.
The procedure below is an overview of the Constellation deployment process. Read

Standard SNMP Device Deployment on page 112 for full details.
NOTE : Cons tellation for Far Sc an is deployed in Pr oVis ion w ith limited
func tionality. It does not have the follow ing:
* Per for manc e data c ollec tion (r es ulting in no per for manc e thr es holds
or tr ends r ec or ded)
* Netw or k Health Repor t
* Full func tionality for the Inventor y Repor t, Diagnos tic Contr ols , and
Configur ation View er
Per for manc e data c ollec tion for Cons tellation is only s uppor ted for the
follow ing var iants : 3DS3, 4DS3, and 155mbit.
Prerequisite
For each Constellation device you are deploying in ProVision, you must find that device
in FarScan and set up ProVision’s IP address as the manager of that device. This is
required to manage a Constellation device from ProVision. See the FarScan User
manual for further details.
124 AVIAT NETWORKS

Procedure
1. Identify the IP addresses for the Constellation radios.
Deployment window displays. Select the Other Microwave icon. The Constellation
device option is displayed.
Select the Constellation option. The Deploying Constellation screen displays. Enter the
values for a Constellation radio, as follows:
placed under the parent listed.
the Constellation 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.
To have ProVision start managing this radio,
select the Manage checkbox.
3. After you have deployed all the required Constellation devices, the Constellation
discovery agent automatically identifies the devices. Click on the devices in the Tree
Viewer. The devices should display with their links and their protected/unprotected
status.
4. The Constellation devices are now fully deployed and managed from ProVision.
NOTE : When a Cons tellation devic e is fully deployed, Pr oVis ion c ap-
tur es all of its IP addr es s es . This pr ovides s uppor t for r edundant NMS
c onnec tions .
CTR 8300 and 8540 Device Deployment

To deploy a CTR 8300 or CTR 8540 device in ProVision, you must do the following:
l Set up the device prerequisites, as listed below.
l Manually deploy or auto-discover the device in ProVision.
614-330055-001 DECEMBER 2015 125

l Configure the specific device logins and passwords in ProVision.

Follow these instructions for each device you need to manage with ProVision.
For more details see the CTR documentation.
Prerequisites
Before deploying CTR 8540 or cTR 8300 devices in ProVision, you must do the fol-
lowing:
l Use the CLI commands to enable SNMP and to create a ProVision user account
with root access for the device. This enables communication with ProVision.
l Set up the device for syslog forwarding. To do this, either run the command
logging <PV server IP> on the CTR device, or set this up via the CTR
Configuration profile in ProVision. See the Configuration Profile Reference on
page 206.
l Make sure that the system running ProVision (Solaris or any other OS), has no
process using port 514. See Changing Syslog Server Port in the Installation
and Administration Manual.
Procedure
1. Configure the following on each device, using the CLI. See the manual CTR CLI
Reference for details.
a. Enable SNMP and configure the SNMP read/write community strings. Use
the following commands to enable SNMP for the device and note that:
l We recommend using the same values on each CTR 8540 or CTR

8300, simplifying the configuration and maintenance of
passwords on ProVision. This also provides the ability to use
network auto discovery.
l For improved security, we also recommend using a different
value from the commonly used “public” / “private” values.
l The following example indicates the CLI commands required to
enable SNMP and configure read community string value
“public1” and write community string value “private1” on a CTR
device:
aos# configure terminal
aos(config)# snmp-server view all 1 included
aos(config)# snmp-server community public1 version both read all
notify all
aos(config)# snmp-server community private1 version both read
all write all notify all
aos(config)# config save
aos(config)# end
b. Create a provision user account with root access. Use the following
commands to create a ProVision user account with root (privilege level 15)
access. ProVision needs this account to automatically log into the device to
126 AVIAT NETWORKS

perform operations such as event collection, configuration backup and

software download. Passwords must be between 8 and 32 characters long
and contain at least one letter, one number, and alpha-numeric character,
and at least one lower and one upper case character. A new password must
have at least 4 characters different from the old password
l For ease of management access under ProVision we recommend

that a common user name, such as 'provision', and a shared
password for the user name, is used on all CTR devices to be
managed.
l The following example indicates the CLI commands required to
configure a user account called ‘provision’ with the appropriate
level of access:
aos# configure terminal
aos(config)# username provision password <password> privilege 15
aos(config)# config save
aos(config)# end
2. Ensure that all changes are backed up to secure storage. Exit the CLI command
window for the device.
3. Deploy the device in ProVision. Perform the following in ProVision:
a. Where a common “provision” user account password has been

applied, configure the device login in ProVision at the root
network container. See Setting Device Security Account Values.
b. Log into ProVision and deploy the CTR 8540 device, as
described in Standard SNMP Device Deployment on page 112.
Devices can also be found via autodiscovery: see CTR Device
Support on page 18.
c. Where unique “provision” user account passwords have been
applied, configure the device login in ProVision as each device
is deployed. See Setting Device Security Account Values.
d. ProVision can now communicate fully with the CTR 8540
device.
Auto-discovery of RF and Ethernet Links

When upgrading software on CTR 8540 or CTR 8300 from release 2.x to
release 3.0 release, the LLDP protocol is erroneously disabled by the embed-
ded software. This results in ProVision being unable to auto-discover RF
links and Ethernet links.
To solve this problem, the user needs to enable LLDP on the CTR device
through executing the following CLI commands:
c t
set lldp enable
614-330055-001 DECEMBER 2015 127

Auto-discovery of Linked WTM Devices

If a CTR 8540 device is connected to a WTM device via the POE or an Ethr-
net port, ProVision automatically discovers the ink and deploys the WTM
radio as a child object of the parent CTR. The auto-discovered WTMs dis-
play as child devices in the Tree Viewer:
And as links in the details of the Map viewer:
Generic Device Deployment

Generic devices can be SNMP or IP based, non-Aviat Networks 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:
l Generic Devices
l Multiplexer
l Router
l Switch
l Microwave Radio
l Power Supply
l Alarm Unit
l Base Station
128 AVIAT NETWORKS

l Timing System
l Server
l Firewall
l Air Conditioner
l Symbol = Device that has no managed status, can select custom icon
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.
NOTE : If a G ener ic Devic e is an IP devic e, its s uppor t is limited at this

time to being pr es enc e polled.
W AR NING : When you deploy a gener ic devic e, you, or an advanc ed-

level us er , mus t als o s et up the gener ic devic e event c ollec tion. This
func tion r equir es an additional Pr oVis ion module lic ens e. This is doc -
umented in the I nstallation and Administration Guide. If you ar e w or king
w ith an advanc ed- level us er to deploy gener ic devic es , pleas e pr ovide
them w ith all the devic e details : name, type, IP addr es s , and Br ow s er
and Telnet por t s ettings .
Procedure
Device Deployment Windows Steps
Select the Generic Device Type that best
describes the device.
Then, click Next.
614-330055-001 DECEMBER 2015 129

Device Deployment Windows Steps

Enter the values for the device in this
screen:
Ensure the correct parent displays; the
device is placed under the parent listed.
Press the Tab key and type in the device’s
IP address.
The Browser and Telnet Port settings
are the default, only change these if
required.
Some devices have an SSH Port setting.
Select the Communications type for the
device, SNMP or IP.
To have ProVision start managing the
device, select the Manage checkbox.
Click Next.
For the steps below, the Generic Device
module license is required.
For an SNMP Device only, assign the
Read Community and Write Com-
munity 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 Com-
munity strings must match the strings
entered into the radio.
Assign a Support Package name.
Select a Support Package from the Pack-
age drop-down menu, or enter a Support
Package name in the New Package Name
field. If you enter a new Support Package
name, it is available in the Package menu.
If you select an existing Support Package,
it needs to match the device Com-
munication type, SNMP or IP.
Click Deploy. The new device is
deployed.
If you are deploying a Symbol device,
first, you are prompted to enter a Symbol
name.
Then you are asked to select a custom icon.
This is not required. Icons can be .jpg,
.bmp, or .png graphics up to 2.4 MB in
size. ProVision will automatically resize the
icon. Any icons you enter are saved for
later re-use. See About User Defined
Icons on page 91
130 AVIAT NETWORKS

Proxy and Network Element Deployment

You can connect ProVision to another Element Management System (EMS) to make this
visible within ProVision. This type of EMS is called a Proxy.
After you have deployed a Proxy, you can assign Network Elements to the Proxy. This
manages devices that ProVision cannot connect to because the Network Element devices
do not have SNMP.
Prerequisite
For each EMS Proxy you are deploying in ProVision, you must obtain the IP address,
port data (for browser, telnet, and SSH), and Communications type.
Procedure
1. In the Tree Viewer, right-click an existing container or the Root and select Deploy
Object.
1. The Deployment window displays. Select the EMS/Proxy device option.
2. Select whether you want to deploy an EMS or a Proxy.
NOTE : You s hould deploy the EMS fir s t, and then deploy its netw or k ele-
ments as Pr oxies .
3. The Deploying screen displays.

4. Enter the values for the EMS:
614-330055-001 DECEMBER 2015 131


the EMS It is labeled with this name in the User
Interface.
Enter the Browser Port.
Enter the Telnet Port.
Enter the SSH Port.
Select the Communications type from the
drop-down menu.
Only select the Manage checkbox if this EMS is
to be managed.
If required, you can use a custom icon. To activ-

ate this, click the Use Custom Icon check box
and select the icon.
Select the Support Package for the EMS Proxy. If

you have loaded Generic Device Packages pre-
viously, these will display in the Package drop-
down menu as options.
You can also type in the name in the New Pack-
age Name field.
132 AVIAT NETWORKS

Select the SNMP option for the EMS.Options

include v1, v2, and V3.
The Read Community and Write Com-
munity must match the strings entered into the
radio.
5. To deploy a Network Element:
In the Name field, type a descriptive name

for the Network Element. It is labeled with
this name in the User Interface.
Enter the Network Element ID.
Only select the Manage checkbox if this
EMS is to be managed. The Managed state
is inherited from the EMS in the next step.
614-330055-001 DECEMBER 2015 133

If required, you can use a custom icon. To

activate this, click the Use Custom Icon
check box and select the icon. If this is not
required, click Next.
From the Proxy list, select the EMS Proxy

that this will be linked to.
134 AVIAT NETWORKS

Select the Type for the Network Device.

If you have loaded a Type previously, these
will display in the Type drop-down menu as
options.
You can also enter a new Type name in the
Type Name field.
6. The EMS Proxy and its Network Element Devices can now be viewed from ProVi-
sion.
W AR NING : See Managing Proxy C onfigu rat ion on p age 16 3 to r eas -
s ign Netw or k Element Devic es if r equir ed.
Symmetricom TP1x00 Deployment

To fully deploy a Symmetricom TP1x00 (1000, 1100) device in ProVision, you must note
a value from the Symmetricom craft tool for the specific Symmetricom device. You need
to add a new Principal, and use the Principal user name to configure the device SNMP
options when deploying it in ProVision.
Procedure
1. Obtain the IP address of the ProVision server you will use to manage the device.
2. Open the Symmetricon craft tool, TimeCraft.
3. In the left frame, select SNMP Parameters. Then, in the main screen, go to the
SNMP Principals Configuration frame.
614-330055-001 DECEMBER 2015 135

4. Click on the button New Principal and enter the values for a New Principal. Select
the SNMP version from the Type and select the Access. Enter the principal Name as
shown below. Then, click OK.
5. On the SNMP Trap Configuration panel click the Edit button; the Edit Trap Set-
tings screen displays. Select the Principal Name from the drop down list. Assign the
principal name to the IP Address of the ProVision server. Then, click OK.
6. The New Principal appears in the SNMP Principals Configuration and the SNMP
Trap Configuration as shown below (highlighted in red).
136 AVIAT NETWORKS

7. Exit TimeCraft and log into ProVision.

8. Deploy the new Symmetricon device in ProVision using the Standard SNMP
Device Deployment on page 112. In the Deployment screen for SNMP options, add
the user name from step 3 as the Read Community in ProVision. Then, click Deploy.
9. The Symmetricom TP1x00 device is deployed and fully managed by ProVision.
Symmetricom TP5000 Deployment

Before you deploy a Symmetricom TP5000 device, you must set up a read community
string value using the CLI commands for the device. This enables device com-
munication with ProVision.
Follow these instructions for each Symmetricom TP5000 device you need to manage
with ProVision.
614-330055-001 DECEMBER 2015 137

NOTE : For mor e details s ee the Symmetr ic om TP5000 doc ument,

TimePro v ider 5000 IE E E 1588 G rand Mast er C lo ck User’s G uide,
Part Numb er 09 8- 0002 8- 000- rev - d .
Procedure
1. Obtain the IP address of the ProVision server you will use to manage the
device.
2. Telnet into the Symmetricom TP5000 device.
3. Add the ProVision server IP address. Use the following commands to add
and display the IP address of the ProVision server.
set snmp add manager <ip-address>
show snmp manager
4. The SNMP Manager displays.
5. Type the following commands to add the “read community” string (groupv2
in the example shown below; the community name is assigned to the
manager ID with the same index ).
set snmp add v2-community groupv2 secureLv1 read-write
show snmp v-2 community
6. This confirms that you can read and write to the community string. The
Community Name (groupv2) is used as the read community string for
deploying TP5000 in ProVision.
7. Exit the CLI command window for the device.
8. Log into ProVision and deploy the device.
TRuepoint Device Deployment

To deploy a TRuepoint device in ProVision, it must be deployed, then configured using
the Configuration Profiles function. TRuepoint devices must communicate with a ProVi-
sion 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 142.
138 AVIAT NETWORKS

Read Standard SNMP Device Deployment on page 112 and Configuration Profile Refer-
ence on page 206 for full details.
NOTE : For TRuepoint 4040 v2 and 5000 devic es w ith V2 c ontr oller s , an
additional Pr oVis ion func tion enables you to apply SNMPv3 pr i-
vac y/enc r yption. To do this us ing the algor ithm types of TDES, AES128,
or , for US c us tomer s only, AES192 and AES256, your Pr oVis ion s ys tem
r equir es :
* A s pec ific Pr oVis ion featur e lic ens e.
* A Java c r yptogr aphy extens ion (JCE unlimited s tr ength jur is dic tion
polic y file/s ) fr om Sun Mic r os ys tems .
Contac t your Aviat Netw or ks r epr es entative to obtain this lic ens e and
this extens ion.
Prerequisite
To do this, you need access to both ProVision and WebCIT, the TRuepoint craft tool, for
the TRuepoint devices.
For each TRuepoint device you are deploying in ProVision, you must find that device in
WebCIT and set up ProVision’s IP address as the manager of that device. This is
required to manage a TRuepoint device from ProVision. See the Procedure below for spe-
cific instructions.
Procedure
1. Identify and record the IP address of your installation of ProVision. See Determin-
ing the Server’s IP Address in the Installation and Administration Manual for
complete instructions.
2. Identify all the TRuepoint devices you want to deploy in ProVision.
3. Log into WebCIT. For each TRuepoint device noted in step 2:
l Go to the Provisioning screen, in Network Setting 2 .
l Set the value SNMP Manager to the ProVision IP address identified in step 1.
See the WebCIT Operator manual for further details.
l Save the changes.
4. Once steps 2 and 3 are completed for each TRuepoint device, log into ProVision.
5. Identify the IP addresses for connecting TRuepoint devices to ProVision via a
ProVision trap and a ProVision SNMP manager.
Deployment window displays. Select the TRuepoint icon. The TRuepoint device
options are displayed.
7. Select the TRuepoint device that you require. Enter the values for it as follows:
614-330055-001 DECEMBER 2015 139

TRuepoint 4000, 4040, and 6400

for the TRuepoint device. It is labeled with
The Read Community string has the
default value. Only change it if the radio set-
ting has been changed.
The Read and Write Community strings
must match the strings entered into the
radio.
Select Deploy. The Deploying TRuepoint res-
ults window displays.
Click Close. The radio is now deployed.
TRuepoint 4040 v2, 5000, and 5000
2+0
for the TRuepoint device. It is labeled with
Click Next.
Select the SNMP Version. If you select Ver-

sion v2c, the Read and Write Community
options display.
The Read and Write Community strings
must match the strings entered into the
radio.
140 AVIAT NETWORKS

If you select Version v3 for the SNMP ver-

sion, further options display.
If required, check the box to Use Inherited
Security Account from the parent con-
tainer.
Enter a Username. This is associated with
the two passwords below.
Authentication: This selects the algorithm
used for this device’s data. Select a Type,
and enter a Password and a Con-
firmation for the password.
Privacy: This selects the encryption
algorithm used for this device’s data. Select
a Type, enter a Password and a Con-
firmation for the password.
The Authentication and Privacy types are
determined by your organization’s network
policy. An Authentication of MD5 and a Pri-
vacy of AES128 is a common “strong secur-
ity” combination.
To change or view SNMPv3 credentials on a
TRuepoint radio, see the TRuepoint
5000/4040 Operator’s Interface Manual,
IMN-903003-E07. There are two ways to
change these credentials. One is using
WebCIT, logging in as the administrator
user and setting the authentication and pri-
vacy passwords. The other way is using
third-party SNMP tools, such as MGSoft and
NetSNMP.
Click Deploy. The TRuepoint radio is now
deployed.
8. For 4040, 5000, and 6400 radios, there is an extra step. After you have deployed
all the required radios, select them in the Tree Viewer. In the menu bar, go to the
Configuration menu and select Configuration Profile.
9. In the Configuration Profiles screen, select the TRuepoint 6400/5000/4000/4040 Man-
agers option for the TRuepoint radio type. Enable the option and enter the SNMP
manager IP address; this is the ProVision IP address identified in Step 1.
10. Select the TRuepoint 6400/5000/4000/4040Trap Destination option for the TRuepoint
radio type you have deployed. Enable the option and enter the trap destination IP
address; this is the same as the SNMP manager IP address in step 9.
614-330055-001 DECEMBER 2015 141

11. Save and apply the Configuration Profile settings, as documented in Con-
figuration Profile Reference on page 206.
12. The TRuepoint devices are now fully deployed and managed from ProVision.
NOTE : TRuepoint 6400 r equir es an additional pr oc edur e to enable its

alar m r es ync hr onization; s ee C onfigu re TRuep oint 6 4 00 Alarm Resy n-
chronizat ion on p age 308.
NOTE : When a TRuepoint devic e is fully deployed, Pr oVis ion c aptur es all
of its IP addr es s es . This pr ovides s uppor t for r edundant NMS c on-
nec tions , as s how n in this diagr am below :
TRuepoint 6500 Device Deployment

You can deploy and manage TRuepoint 6500 devices in ProVision. In ProVision, TRue-
point 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 doc-
umentation, particularly for Managing SMA and DXR Devices on page 165.
There are two types of TRuepoint 6500 devices:
142 AVIAT NETWORKS

Type Definition Tree Viewer Display

Standard Standard TRuepoint
6500 radio.
Double Ter- This type includes 2

minal supervisory ter-
minal 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 112.
Prerequisite
For each TRuepoint device you are deploying in ProVision, you must find that device in
WebCIT and set up ProVision’s IP address as the manager of that device. This is
required to manage a TRuepoint device from ProVision. This setting is found in WebCIT
via the Provisioning screen, in Network Setting 2 , as the value SNMP Manager #1. See
the WebCIT Operator manual for further details.
Procedure
1. Identify the IP addresses for connecting TRuepoint devices to ProVision via a
ProVision trap and a ProVision SNMP manager.
Deployment window displays. Select the TRuepoint icon. The TRuepoint device
options are displayed.
3. Select the TRuepoint 6500 device that you require, Standard or Double Terminal.
Enter the values for it as follows:
614-330055-001 DECEMBER 2015 143

TRuepoint 6500
TRuepoint device. It is labeled with this name in the
User Interface.
To have ProVision start managing this radio, select
Select Deploy. The Deploying TRuepoint results win-
dow displays.
Click Close. The TRuepoint radio is now deployed.
TRuepoint 6500 Double Terminal

TRuepoint device. It is labeled with this name in the
User Interface.
For each of the two terminals, enter the IP addresses.
To have ProVision start managing this radio, select
Select Deploy. The Deploying TRuepoint results win-
dow displays.
Click Close. The TRuepoint radio is now deployed.
4. After you have deployed the TRuepoint 6500 radio, ProVision immediately dis-
covers 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.
TNet Device Deployment

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
144 AVIAT NETWORKS

performance issues it is recommended that no more than 500 TNet devices are allocated
to a single TNet Proxy. ProVision supports up to 3000 TNet devices.
When an event occurs on a TNet device, an SNMP event is sent by the TNet Proxy to
ProVision.
Within ProVision, TNet devices are typically deployed under the location (region, site or
rack) at which they are physically deployed. This is not necessarily the same location at
which the TNet Proxy is deployed, as shown in the following screen.
You can view Proxy, subnets, and TNet device configurations via the Proxy Con-
figuration Manager. See Viewing/Changing TNet Proxy Configurations on page 218.
NOTE : TNet Web r equir es Java 1. 7.
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 ProVi-
sion 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.
614-330055-001 DECEMBER 2015 145

Figure 4-3. ProVision and a TNet Network
Procedure
CAUTION: 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.

146 AVIAT NETWORKS


Table 4-3. Device Deployment Details for TNet Devices

TNet Proxy
ProVision can manage up to ten TNet Proxies. Each
proxy can support up to 16 radio subnets (0 to 15).
TNet Proxy. The TNet Proxy is labeled with this name
in the User Interface.
Press the Tab key and type in the TNet Proxy’s IP
address.
The Read and Write Community strings must match
the strings entered into the radio.
Enter the total number of Subnets for this proxy.
To have ProVision start managing the TNet Proxy,
All Other TNet Devices
radio. The device is labeled with this name in the User
Interface.
Press the Tab key and type in the subnet number (Sub-
net #). The valid range is 0 - 15.
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.
Press the Tab key and type in the radio address.
To have ProVision start managing the TNet device,
Select Next. The Proxy List displays.
Select a TNet Proxy from the list displayed.
Select Deploy.
The Deploying <device name> results window dis-
plays.
To close the Deploying <device name> window, select
Close.
The table below lists the TNet device deployment/management problems that can occur
between ProVision and the TNet Proxy, and the suggested solutions.
Table 4-4. ProVision and TNet Proxy - Device Deployment Discrepancies
614-330055-001 DECEMBER 2015 147

Deployment Discrepancy Solution

Radio deployed in ProVision but See below, Manually Deploying a TNet Device
not deployed in the Proxy. into the Proxy.
Wrong radio type in either ProVi- Delete the radio from ProVision.
sion or the Proxy. This also deletes the radio from the Proxy. See
Deleting a Device on page 154
Deploy and manage the radio in ProVision.
The radio is automatically deployed into the Proxy.
Radio deployed in the Proxy but Deploy and manage the radio in ProVision.
not deployed in ProVision, and Delete the radio from ProVision.
the radio is not required. This also deletes the radio from the Proxy.
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 writ-
ten 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 220 for more inform-
ation. If the TNet device is not listed in the Proxy database, you can manually deploy
the TNet device into the Proxy.
To manually deploy a TNet device into the Proxy:
1. Right-click the TNet device. In the right-click menu, select Deploy into Proxy.
2. The TNet device details stored in ProVision, are written into the Proxy database.
Network Auto-Discovery for Devices

Network Auto-Discovery is a ProVision task that polls a range of IP addresses for the fol-
lowing device types:
l Eclipse
l CTR 8300, 8440, 8540, 8611
l Constellation
l Cisco ASR 903
l TRuepoint
l WTM 3100, 3200, 3300
l Loaded GDS packages/devices
l Generic Ethernet devices (see note)
148 AVIAT NETWORKS

When you run Network Auto-Discovery, you tell ProVision which IP address ranges to
search. ProVision polls the IP addresses and captures discovered devices in containers in
ProVision. This is a fast way to deploy devices when applying ProVision to an existing
network.
Note that:
l Discovered devices are named with the class name of the device and the
device-specific IP address.
l Users can edit the device data of all discovered devices.
l ProVision only deploys the discovered objects into the specified Container. If a
Container specified for auto-discovery does not exist, ProVision will create it.
l You can review the auto-deployment results and note any errors.
NOTE : G ener ic Ether net devic es that have pr e-r egis ter ed pac kages ar e
only available for autodis c over y if c us tomized w ith a <sysobjectid> in
the pac kage by an adminis tr ator , s ee the Pro Visio n G DS Perf o rmance
Management doc ument. O ther w is e G ener ic devic es ar e auto-dis c over ed
bas ed on ifTable or ifXTable s uppor t. G ener ic Ether net devic es ar e auto-
dis c over ed in this or der : r egis ter ed pac kages , ifXTable s uppor ted (Eth-
er netHC), ifTable s uppor ted (Ether net).
Procedure
1. Log into ProVision.
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:
l Click Add. The Add IP Range fields display. Enter values for:
614-330055-001 DECEMBER 2015 149

o IP Address Range - Enter the start and end of the IP address range. This
accepts both IPv4 and IPv6 addresses.
o Read Community - Enter public or private, based on the device password
requirements.
o Container Name - Enter a unique Container name. All the discovered devices
for this IP address range will be deployed in this container, just below the
PV/Root level in the Physical Tree view.
o If required, check the Manage on Deployment check box. The discovered
devices will be deployed in a Managed state.
o If required, check the Discover Generic Ethernet Devices box. Any discovered
Generic devices that have pre-registered packages or that support ifTable or
ifXTable will be deployed.
l 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.
150 AVIAT NETWORKS

NOTE : Pr oVis ion w ill r un the auto-dis c over y on up to 5 IP addr es s

r anges at one time. All r emaining r anges w ill be queued and r un as
tas ks .
8. When the network Auto-Discovery is complete:

l The new Container is created, and holds any discovered devices.
l 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.
l You can import the results of the network auto-discovery as a .CSV file by
clicking the Import button. The CSV file includes the following data, without a
descriptive header: Start IP Address, End IP Address, Container Name, Read
Community.
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:
l Object at address <####> successfully deployed - An object was found and
deployed.
l Object not detected at address <####>- Nothing at this IP address is
responding to the SNMP request; no object was found or deployed.
l 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.
l 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.
l Example of Eclipse auto-discovery results:
614-330055-001 DECEMBER 2015 151

Troubleshooting Device Deployment

When you deploy a device, you may receive the following error messages:
Exception Corrective Action
IP Address Already Allocated
If you attempt to assign an IP Select OK.
address that has already been alloc- The Deploying <device
ated to a device the following mes- name> window displays
sage displays: enabling you to re-enter
the correct IP address.
Invalid IP Address
If you enter an invalid IP address the Select OK and re-enter a
following message displays: valid IP address.
Verifying ProVision is Receiving Device Events on page 157
Changing a Device’s Container

If you have deployed a device under the wrong container and want to move it to a dif-
ferent container, you can reparent the device in the Tree Viewer.
If you change the device’s container, you must reposition the object in the Map Viewer.
For more information, see Moving Containers and Devices in the Map Viewer on page
153.
NOTE : Container and devic e objec ts ar e r epar ented in the Tr ee View er

phys ic al pane.
152 AVIAT NETWORKS

NOTE : Repar enting a TNet devic e w ithin the Tr ee View er is exac tly the
s ame as for other objec ts . How ever , r epar enting TNet devic es to a dif-
fer ent TNet Pr oxy is a differ ent pr oc edur e. See Viewing/C hanging TNet
Proxy C onfigu rat ions on p age 218.
Procedure
1. To unlock the tree, select the locked icon, located on the physical pane’s title bar.
2. Select the device to be moved to a different container.

3. Drag and drop the device into the required container. The device has been repar-
ented and displays under the new container in the Tree and Map Viewers.
4. To lock the tree, select the unlocked icon.
Moving Containers and Devices in the Map Viewer

You may want to reposition container objects and/or devices in the Map Viewer. You
can do this, if you have enough user access.
NOTE : If you move a linked devic e to another pos ition on the map, the
link moves w ith the r adio.
NOTE : Moving an objec t on one map view , for example, the flat view ,
does not effec t the pos itioning of the objec t on the other layer .
Procedure
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.
Renaming a Device
You can change device names for devices in ProVision.
614-330055-001 DECEMBER 2015 153

Procedure
1. Right-click the device to be changed. The device’s right-click menu displays.
2. Select Rename on the right-click menu. The Rename Object window with the selec-
ted device’s name displays.
3. Make the required changes to the device’s name.

Deleting a Device
There are three reasons to delete a device from ProVision:
l A device was accidentally deployed in the wrong region or site.
l The radio has been decommissioned or replaced with a different radio type.
l 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.
NOTE : Deleting a devic e in Pr oVis ion has no effec t on the tr affic c ar -

r ying c apability of the devic e, but event gener ation is dis abled in the
devic e.
NOTE : You c annot dir ec tly delete a DXR 700 r adio. You have to s elec t
the DXR SMA option to Dis c over Ter minals . For mor e infor mation s ee
Manu ally Discov ering DXR 700 Rad ios on p age 16 2.
CAUTION: WARNING: Be careful when deleting a TNet Proxy, as this also deletes
all the associated child TNet radios in ProVision, and deletes the Proxy’s database.
Procedure
1. Right-click the device’s icon. The right-click menu displays
2. Select Delete on the right-click menu. A Delete Objects window displays.
154 AVIAT NETWORKS

3. To delete the selected device, select Yes.
614-330055-001 DECEMBER 2015 155

Managing Devices
This section covers the following device management procedures:
l Managing a Device on page 156
l Verifying ProVision is Receiving Device Events on page 157
l Unmanaging a Device on page 158
l Manually Discovering WTM 6000 Configuration on page 161
l Viewing Eclipse RAC Low Latency Links on page 159
l Manually Discovering TRuepoint 6500 Configuration on page 162
l Manually Discovering DXR 700 Radios on page 162
l Managing SMA and DXR Devices on page 165
l Managing Proxy Configuration on page 163
l Linking Procedures on page 167
Managing a Device
When you activate Managed status for a device in ProVision, ProVision initiates pres-
ence 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.
NOTE : Importan t: This pr oc es s is not applic able for Ec lips e Node and
DXR 700 r adios .
NOTE : A Pr oVis ion managed devic e that has not yet been ins talled and
c ommis s ioned at the s ite is s how n in Pr oVis ion w ith the c onnec ting ic on
.
Procedure
To activate Managed status for a single device:
1. Right-click the device to be managed. The device’s right-click menu displays.
2. Select Manage. ProVision changes the device to a Managed state. A check displays
beside Managed in the right-click menu, showing that the device is Managed.
To set the Managed status of two or more devices:

1. Select the device icons for all the required radios. Then, right-click.
156 AVIAT NETWORKS

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 dis-
plays as follows:
4. Set the status to Managed or Unmanaged for the devices. The status that you
choose is applied to all the devices.
Verifying ProVision is Receiving Device Events

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:
l Adjusting Event filtering to display all events received from a device: or
l By causing an alarm to be raised by the radio.
If ProVision is not receiving events from a device, check that the device’s IP address is
correct. The device’s IP address displays in pop-up text when you place the cursor over
the device’s icon in the Tree or Map Viewer. If the IP address is incorrect, you can
change it. See Viewing/Changing Network IP Addresses on page 217.
Procedure
1. Right-click the managed device.
2. From the right-click menu, select Event Browser.The Event Browser displays.
614-330055-001 DECEMBER 2015 157

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.
Unmanaging a Device
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 loc-
ation 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:
l The device’s event status changes to blue in the Tree Viewer. A blue object
balloon displays in the Map Viewer.
l For DXR SMAs, the connected DXR 700s are also un-managed.
158 AVIAT NETWORKS

l The device’s event history and performance data are not displayed until the
device is remanaged.
l An unmanaged informational event is added to the ProVision event log.
l ProVision stops presence polling the device.
l Event generation is disabled in the device.
CAUTION: 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 .
Procedure
1. Right-click the device to be un-managed. In the right-click menu, deselect the Man-
aged checkbox.
The device is changed to an unmanaged state, and is no longer polled by ProVision.
Viewing Eclipse RAC Low Latency Links

With ProVision, users can identify Eclipse Low Latency links operating in either IF
repeater or Regenerator mode. These links provide fast, ultra low latency transmission,
with reduced propagation and equipment-related latency.
Eclipse INU and INUe devices that include RAC LL, RAC LL DDR or RAC3X con-
figurations with low latency modem profiles, can be enabled for low latency operation
through the LL software feature license. RAC LL and RAC LL DDR supports IF repeater
and Regenerator functions, whereas RAC 3X only supports the Regenerator function.
NOTE : RAC 3X s uppor ts r egener ation only.
There are two low latency icon indicators, (IF) and (R), which can be viewed to indicate
the low latency mode of a RAC interface:
l (IF) indicates that a LL modem profile is active and IF repeater mode has been
enabled on the RAC interface, resulting in the Eclipse node passing the IF
signal from ODU to ODU.
l (R) indicates that regenerator mode is active, i.e. a LL modem profile is active
however IF repeater mode is disabled.
In the Map view, low latency paths through the network are identified:
Note that where IF repeater mode reverts to Regenerator fallback mode, the RF link
object connecting the RAC interfaces will indicate the associated alarm condition.
614-330055-001 DECEMBER 2015 159

In the Tree view, RACs operating in low latency mode have a low latency indicator
beside the RAC interface object:
In a Submap view, RACs operating in low latency mode have a low latency indicator on
the RAC plugin:
160 AVIAT NETWORKS

Users can search for RAC LL and RAC LL DDR devices using the Search function, enter-
ing Eclipse RAC LL in the text Search field: see Using Search to Search All ProVision
Data on page 83.
In addition, RAC LL devices are included in the Inventory Report, with other licensed
features, noted as LL Capability devices: see View and Save the Inventory Report for a
Single Device on page 459.
NOTE : For mor e infor mation about RAC L L , s ee the topic E clipse Low
Latency Operation in the Av iat Net wo rk s E clipse User Manual .
Manually Discovering WTM 6000 Configuration

In ProVision, when you manage a WTM 6000, you have the option of discovering the
radio’s configurations.
When ProVision discovers a WTM 6000, 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 Map View of a WTM 6000.
If a WTM 6000 is changed in the Craft Tool, e.g., one of its plug-ins is removed, a warn-
ing 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. Then the
updated device configuration will display in the Map View and be used for event man-
agement.
614-330055-001 DECEMBER 2015 161

Procedure
1. In the Tree or Map Viewer, right-click the required WTM 6000 radio. In the right-
click menu, select Discover Configuration.
2. The WTM 6000 is updated to reflect any new connections or any changes that
were discovered. Any changes display in the Tree Viewer.
Manually Discovering TRuepoint 6500

Configuration
In ProVision, when you manage a TRuepoint 6500, you have the option of discovering
the radio’s configurations.
When ProVision discovers a TRuepoint 6500, it communicates with the radio and iden-
tifies 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
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.
Manually Discovering DXR 700 Radios

In ProVision, when you manage a DXR SMA, you have the option of discovering the con-
nected DXR 700 radios.
162 AVIAT NETWORKS

You can also manually discover DXR 700 radios in the following situations:
l Where the discover option was not enabled when the DXR SMA was managed
in ProVision, because the radio had not been commissioned.
l Where you are getting unusual responses, you may discover the radios to see if
the radios have been changed, that is, swapped ports.
l To delete a DXR 700 radio from ProVision where a DXR 700 radio has been
physically removed from the network.
Procedure
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.
Managing Proxy Configuration

For Proxy and Network Element devices, you can change which Network Elements are
assigned to which Proxy.
Procedure
1. In the Tree View or Map View, right click on a Proxy. From the right-click
menu, select Proxy Configuration Manager.
2. The Proxy Configuration Manager displays.
614-330055-001 DECEMBER 2015 163

3. From this screen, you can select a Network Element and reassign its
Network Element ID number.
4. To move a Network Element from one Proxy to another, drag and drop it in
the Tree View. You will be asked to confirm reparenting the Network
Element. Click Yes and the Network Element will be reassigned.
3. Click Close. Your changes are saved.
164 AVIAT NETWORKS

Managing SMA and DXR Devices

As described in DXR 200 and DXR SMA Device Deployment on page 120, 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 con-
figuration 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.
NOTE : DXR 200 r adios ar e s et up outs ide of Pr oVis ion. When you c r eate
a new DXR 200 for an SMA, it s hould be bas ed on the DXR r adios that ar e
phys ic ally c onnec ted to the SMA. Us e the “Dis c over Ter minals ” func tion
to identify thes e r adios .
Procedure
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:
l Radios highlighted in orange need to be deployed or otherwise corrected in
ProVision.
l 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.
l Radios deployed correctly in ProVision are displayed in white.
614-330055-001 DECEMBER 2015 165

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

Linking Procedures
ProVision can discover and create links between certain devices. A Radio Frequency (RF)
link is added between devices in ProVision to show that the devices are carrying com-
munications traffic. An Ethernet link shows that the devices are carrying Ethernet-
enabled traffic. You can only create a link between Aviat Networks devices of the same
type, for example, one Eclipse radio to another Eclipse radio, or one CTR 8540 router to
another CTR 8540 router.
To create an RF or Ethernet link between two devices, the radios must be deployed in
ProVision.
By creating a link between two devices 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 Alarm Severity
Color Coding on page 91.
This section covers the RF and Ethernet linking procedures:
l Discovering and Verifying Links on page 167
l Creating an RF Link from the Tree Viewer on page 169
l Creating an RF Link from the Find Function on page 170
l Creating an Eclipse RF Link on page 171
l Creating an Ethernet Link on page 173
l Creating a Tributary Link on page 174
l Deleting an RF Link on page 175
l Deleting an Ethernet Link on page 176
NOTE : RF links ar e automatic ally dis c over ed for Ec lips e r adios .
Discovering and Verifying Links

You can discover and verify the following link types, which then display in the Map
View:
Link Type Sample from Map View
RF Link Link is a plain line:
614-330055-001 DECEMBER 2015 167

Link Type Sample from Map View

Ethernet Link Link labeled with squares:
Tributary Link Link labeled with diamonds:
Logical Link Links are displayed beside each other:
Optical Link Link labeled with circles:
Multiple Links Link is a thick line: mouse over it to view separate links.
For the following device types:

l Eclipse
l CTR 8540
l TRuepoint
l WTM 3300
This is done using Discover Links.
NOTE : This func tion is available for TRuepoint 4000, 4040, 5000, and
6400 r adios . It is not available for TRuepoint 6500.
TRuepoint 6400 r adios c an have tw o RF links . All other r adios have one
RF link.
Procedure
1. In the Search screen, locate the device.
2. The device displays in the Search results frame. Right-click on the device.
3. From the right-click menu displayed, move the cursor to the Create Link option
and select Discover Links.
168 AVIAT NETWORKS

4. Two messages will display. The first is a progress report: the second is the link dis-
covery results.
5. Select OK.
6. If you need to create additional links, see Linking Procedures on page 167
Creating an RF Link from the Tree Viewer

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.
NOTE : To c r eate an RF link fr om the Find s c r een, s ee C reat ing an RF

Link from t he Find Fu nct ion on p age 170.
Procedure
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 Discovering and Verifying
Links on page 167.
614-330055-001 DECEMBER 2015 169

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
l If you try to create a link using a radio that already has a link, an error
message displays.
l 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.
l To create an RF link for WTM 6000, select both Path Groups, then open the
right-click menu and select C reate Link - RF Link .
l If you try to create a link for two radios that are not compatible, an error
message displays.
Creating an RF Link from the Find Function

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.
NOTE : To c r eate an RF link fr om the Tr ee View er , s ee C reat ing an RF

Link from t he Tree Viewer on p age 16 9 .
Procedure
1. To open the Search screen, go to the Edit menu and select Search. The Find screen
displays.
170 AVIAT NETWORKS

2. In the Find screen, locate the two radios to be linked. You may want to check to
Links on page 167.
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
message displays.
compatible.
message displays.
Creating an Eclipse RF Link

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.
614-330055-001 DECEMBER 2015 171

Figure 4-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 4-5. Eclipse Radios - Number of Links
Type of Eclipse Radio Maximum Number of Links

Eclipse Terminal one link
Eclipse INU three links
Eclipse INUe six links
When creating an RF link between Eclipse Nodes you must select the same type of Link
icons for both sides of the link. The Eclipse Node link icons are as follows:
Table 4-6. Eclipse Radios - Type of Links
Type of Eclipse Link Icon

Link (non-protected)
Protected link
Ring-protected link
Procedure
1. In the Tree Viewer, locate the two radios to be linked. You may want to check to
Links on page 167.
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.
172 AVIAT NETWORKS

5. Select OK.
NOTE : RF links ar e automatic ally dis c over ed for Ec lips e r adios .
Exceptions
message displays.
compatible.
message displays.
Creating an Ethernet Link

From ProVision, you can create Ethernet links for Ethernet-enabled devices.
NOTE : For mor e details about Ether net management s ee VLAN Man-
agement on p age 24 4 , ERP Ring Management on p age 282, and Et h-
ernet OAM Management on p age 26 3.
Procedure
1. In the Tree Viewer, locate the first device to be linked.
2. Right-click, and from the right-click menu displayed, select Create Link -Eth-
ernet Link . The Create Ethernet Link screen displays.
3. For each side of the link,select the device by clicking Change and choosing the spe-
cific device from the drop-down menu.
614-330055-001 DECEMBER 2015 173

4. Then, select the available Port for the device from the Port drop-down menu.
5. Select Create. The link is created.
6. To view the links, see bothViewing EOAM MA Logical Topology on page 267 and
Viewing VLANs in the Physical and Flat Maps on page 252
Ethernet links display in the Map View with a square labeling the link:
7. To delete a link, see Deleting an Ethernet Link on page 176
NOTE : Ether net links ar e automatic ally dis c over ed for Ec lips e r adios .
Exceptions
l Ports that are not available for linking display in red in the drop-down menu.
l If you are trying to create a link, and the Ethernet Link menu option remains
grayed out, the device cannot support an Ethernet link.
l If you try to create a link for two devices that are not compatible, an error
message displays.
Creating a Tributary Link

From ProVision, you can create Tributary links for Eclipse devices that have
3xE3/DSM3M cards.
Procedure
1. In the Tree Viewer, locate the two plug-ins to be linked. Select both plug-ins.
2. Right-click, and from the right-click menu displayed, select Create Link - Trib-
utary Link .
3. ProVision displays the Tributary Link configuration dialog:
4. Select which ports are physically connected together via cable and click OK. ProVi-
sion will create the tributary link.
174 AVIAT NETWORKS

5. To view the links, check the Map View and find the Tributary Links, labeled with a
diamond. Hover over the link to view its details in a pop-up.
Or, right-click on the link to view the menu and see options for managing the link. Click-
ing the Configure Link menu item, displays the same dialog as in Step 4 to change the
port mapping:
6. To delete a link, use the same procedure as in Deleting an Ethernet Link on page
176
Exceptions
l Ports that are not available for linking display in red in the drop-down menu.
l If you are trying to create a link, and the Tributary Link menu option remains
grayed out when you have selected both plug-ins, the plug-in cannot support
a Tributary link.
l If you try to create a link for two devices that are not compatible, or where a
link already exists, an error message displays.
Deleting an RF Link
You can delete an RF link. There are two reasons to delete a link from ProVision; either
the wrong radios were linked, or the link is no longer available due to a change in equip-
ment installed at the site.
614-330055-001 DECEMBER 2015 175

Procedure
1. In the Tree Viewer, for an Eclipse radio, right-click the Link icon. For all other
radios, right-click the radio icon.
2. In the right-click menu, move the cursor to the Link option and select Delete.
The Delete Link window displays.
3. To confirm deleting the link, select Yes.
Deleting an Ethernet Link

You can delete an Ethernet link from the Tree Viewer or the Map View.
Procedure
1. To delete an Ethernet link from the Tree Viewer, right-click the device; at the
bottom of the right-click menu, Ethernet Links display. Select the link and choose
Delete.
2. To delete an Ethernet link from the Map view, select the Ethernet link in the
map. A pop-up menu names the link and provides a Delete option. Choose Delete.
3. The Ethernet link is deleted.
176 AVIAT NETWORKS

Circuit Management
ProVision provides complete Eclipse circuit management. Eclipse Circuit information is
documented in the following sections:
l About Circuits and Circuit Management on page 177
l Collecting Circuit Information on page 178
l Viewing and Managing Circuits on page 179
l Circuit Provisioning on page 186
About Circuits and Circuit Management

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:
l Set up the Circuit Collection Preferences - Collecting Circuit Information on
page 178
l View and Manage Circuits - Viewing and Managing Circuits on page 179
l Provisioning Circuits - Circuit Provisioning on page 186
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:
l Locates incorrect circuit cross-connections within the network
l Views and manages changes to the network circuit configuration (such as
adding circuit capacity during network rollout).
l Views the circuits to use the troubleshooting features of ProVision, such as
loopback and PRBS (pseudo random binary sequence) testing.
ProVision supports circuit tracing amongst the following Eclipse card types:
l DAC GE3
l DAC GE
l DAC ES
l DAC 155eM/155oM
l DAC 16xE1/DS1
l DAC 4xDS1
614-330055-001 DECEMBER 2015 177

l DAC 3xE3/DS3M
l NCM
Circuits can be traced through the DAC 155eM/155oM if NMS traffic is turned on. All
other DAC types will be treated as endpoints of a circuit and cannot be traced through.
Circuit tracing is supported through all RAC card types.
NCM circuits are collected via circuit collection and can be viewed via the Circuits tab:
see View Loop Switch Circuits on page 184
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.
NOTE : Cir c uit infor mation is only c ollec ted fr om nor mal, managed
devic es .
Procedure
1. To set the time for daily collection of circuit information for all circuits, go to the
Configuration menu and click Circuit Collection Preferences.
2. The Circuit Collection screen displays.
3. To set the time each day when Circuit information is collected and loaded into
ProVision, set the Perform daily 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 at the radio/container level,
right-click the device and select Circuits - Circuit Collection. The information is
immediately downloaded.
5. Click OK to close the screen.
178 AVIAT NETWORKS

Viewing and Managing Circuits

The circuits are displayed in the Circuits Tab, available to be monitored and managed.
The following features make monitoring the network easy and efficient:
l Circuits Tab on page 179
l Filter and Select Circuits on page 181
l View a Single Circuit on page 182
l View Intersecting Circuits on page 183
l View Ring Circuits on page 183
l View Loop Switch Circuits on page 184
l Find and Resolve Conflicting Circuits on page 185
l Circuit Diagnostics on page 190
l Circuit Provisioning
l Delete_a_Circuit.htm
Circuits Tab
ProVision can support up to 50,000 circuits in a network. In the Circuits Tab, you can
view, sort, analyze, and filter the available circuits. The Circuits Tab displays imme-
diately behind the main Map Tab in the ProVision user interface. Click the Circuits Tab
to view this screen.
To view details for a circuit, mouse over it in the map view to see a detailed pop-up.
From here, you can access the following functions:
l Filter and Select Circuits on page 181
l View a Single Circuit on page 182
l View Intersecting Circuits on page 183
l View Ring Circuits on page 183
l View Loop Switch Circuits on page 184
l Find and Resolve Conflicting Circuits on page 185
l Circuit Diagnostics on page 190
l Using Circuit Provisioning on page 186
l Commissioning and Decommissioning on page 1
614-330055-001 DECEMBER 2015 179

Figure 4-5. Circuits Tab
Table 4-7. Circuit Tab Values
Value Definition
Selected Object Name of the selected object; its circuits are detailed in this tab.
To view all circuits for the entire network, click the X beside this field.
Bundle Circuits Check this box to bundle circuits. This groups circuits based on shared start
points and circuit paths, to make the circuit information easier to process.
NOTE : Por tal c ir c uit bundles only r elate to

inter nal c r os s -c onnec tions w hile Pr oVis ion
bundles ar e of end-to-end c ir c uits .
Include Intersecting Check this box to view circuits that pass through the circuits for this object, in
Circuits addition to circuits that start and end at this object.
Filter Use the Filter function to filter and view specific circuits. The entered text is com-
pared against the data in a columns of the circuit table.
Export Circuits Use the Export Circuits function to export circuits as a semicolon separated file.
Map Tab Select a circuit in the table, and a graphic representation displays in the Map
Tab.
Conflicts Tab See Find and Resolve Conflicting Circuits on page 185 for details.
Circuit Table Shows information for the links for the selected device.
Severity The severity of any events for this link.
180 AVIAT NETWORKS

Value Definition
Status The status of this link. Status is indicated by color:
Green = OK.
Red = Data incomplete, cannot completely trace this circuit.
Blue = Circuit names inconsistent.
Yellow = Circuit route changed.
Orange = Circuit route removed, circuit has been deleted and recreated.
Glowing Orange = Incorrect Ring configuration.
Name The name of the circuit, which shows the connected devices.
Start Eclipse radio and DAC plug-in/port for the circuit connection beginning.
End Eclipse radio and DAC plug-in/port for the circuit connection end.
Capacity Total capacity of the circuit.
Type Circuit type: E1, E3, STM1, Ethernet, Ring
AM Priority Related to Adaptive Modulation, assigned in Eclipse Portal if applicable.
Filter and Select Circuits

ProVision can manage up to 50,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:
l Name, or part of the name
l Type - E1, E3, etc.
l IP address, or part of the IP address
l Severity level
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.
614-330055-001 DECEMBER 2015 181

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 1
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/Con-
flicts 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 inform-
ation about a circuit, in the Map subtab, place the cursor over the circuit device. A pop-
up displays with link information.
You can right-click on a single circuit. The circuit right-click menu includes:
Item Function
Commission Trib- Runs decommissioning on this circuit. See Commissioning and
utaries Decommissioning on page 1.
Decommission Trib- Runs decommissioning on this circuit. See Commissioning and
utaries Decommissioning on page 1.
Circuit Provisioning Opens the Circuit Provisioning screen. See Using Circuit Pro-
visioning on page 186 .
Show Conflicts Opens the Conflict subtab and displays any circuit conflicts. See
Find and Resolve Conflicting Circuits on page 185.
182 AVIAT NETWORKS

Item Function
Clear Conflicts Resolves any identified circuit conflicts. See Find and Resolve
Conflicting Circuits on page 185.
Diagnostics Opens the Circuit Diagnostics screen. See Circuit Diagnostics
on page 190.
Rename Opens a field enabling you to Rename a circuit.
Delete Deletes the circuit.
Event Browser Opens the circuit-specific Event Browser. See Event Browser for
a Circuit on page 186 .
Network Health Opens a RF Network Health Reports on page 474 for this spe-
Report cific device.
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 inter-
secting circuits in your view of a device’s 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.
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:
614-330055-001 DECEMBER 2015 183

The view clearly identifies Eclipse NCM loop switch card circuits in loop circuit net-
works.
Double-click the circuit to expand and view all the aspects of the loop circuit. This
includes all nodes in the ring including the NCM configuration of east, west, drop and
passthrough circuits.
Hover over the circuit to view any errored devices in the ring.
View Loop Switch Circuits

ProVision clearly identifies Eclipse NCM loop switch card circuits in loop circuit net-
works. When you select and view the Loop Circuit in the Map subtab, it is identified as
a Loop Circuit. Hover over the circuit to view its pathways:
184 AVIAT NETWORKS

Double-click the circuit to expand and view all the aspects of the loop circuit. This
includes all nodes in the ring including the NCM configuration of east, west, drop and
passthrough circuits.
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.
614-330055-001 DECEMBER 2015 185

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 314.
Circuit Provisioning
The Circuit Provisioning function allows you to select one or more Eclipse devices and
create, edit or delete circuits between the devices. These are then written directly to the
radios. Circuits can be written to a radio in Portal, but the ability to do this from ProVi-
sion makes ProVision a central circuit manager for the device network.
W AR NING : Cir c uit pr ovis ioning is only s uppor ted for Ec lips e s oft-
w ar e 5. 1 and later ver s ions . It is not s uppor ted for ear lier ver s ions of
Por tal. This means that only Ec lips e devic es w ith 5. 1 or later embed-
ded s oftw ar e ins talled c an be managed us ing Cir c uit Pr ovis ioning fr om
Pr oVis ion.
To create a circuit a radio in ProVision, you must do the following:

l Make sure that all links for the network are set up.
l Discover RF links for the radio (see Linking Procedures on page 167).
l Use the Circuit Provisioning function to create the circuit or circuits and write
it to the radio.
l Commission the circuits.
This section describes how to use Circuit Provisioning and how to commission and
decommission created circuits.
l Using Circuit Provisioning on page 186
l Commissioning and Decommissioning on page 1
Using Circuit Provisioning

The Circuit Provisioning function enables you to create circuits for radios. This process
defines all possible paths between devices, and allows you to choose which paths you
want to use for circuits.
Note the following:
186 AVIAT NETWORKS

l To create a circuit, a circuit path must begin and end with a DAC.
l RF links for the involved radios must be discovered before a new circuit can be
created.
l After you create a circuit, you can edit it, increasing or decreasing its capacity.
To change the termination points or routing, you must delete and recreate the
circuits.
Procedure
1. Check that the Eclipse radios you want to connect with a circuit have had
RF links created. See RF Linking Procedures.
2. In the Tree Viewer or the Circuits tab, select the radio and right-click Circuit
Provisioning. The Circuit Provisioning screen displays.
NOTE : If ther e ar e too many devic es to dis play in the available paths
w indow , then a c loud is dis played w ith the number of devic es in the path.
3. The upper left corner of the screen shows selected objects. The item in the
frame for Object A is the radio you selected to open this screen. If you
selected two radios, the second one is in the frame for Object B. These fields
allow users to select two objects to be linked via a circuit.
4. If required, select an object in the field for Object B.
614-330055-001 DECEMBER 2015 187

5. After you have selected Object A and Object B, the Available Paths area
displays the link options. The Available Paths area shows all possible
network paths linking the selected radio end points for this radio, with the
following information:
l Free =Shows the available capacity of the path.
l Used = This shows the used/configured capacity of the path for a circuit. New
circuits do not show a capacity value.
l Paths = A graphic of the path of the circuit through the Eclipse network. The
terminating Eclipse radios are indicated by paired DAC + RAC icons.
Intermediate Eclipse nodes are shown as single radio icons. Where there are
more than 5 path hops, a cloud icon is shown, with a number indicating the
number of intermediate Eclipse nodes.
l Pathway Tooltip = Place the cursor over a circuit pathway to view its full
information, displayed as a tooltip.
7. Select the network path that you want to have for a circuit .
8. The Cross Connections Table will be populated with the cross-connection
information for the selected path.
l Cross Connection Table = Shows objects, ports, free capacity, and priority
level of the connection.
l Circuit Name = A name prefix for this circuit bundle. This will appear as
part of all circuit names within this bundle. Note: ProVision circuit bundles
are related to end-to-end circuits.
l Contiguous Circuit = The capacity for this circuit. If you set the capacity at
too high a value, a warning will display.
188 AVIAT NETWORKS

9. Using the Cross Connect data, review and adjust the configured port
connections. You can click on a Port to assign a different port value from a
drop-down menu. Then, assign the Circuit Name and set the Contiguous
Circuit value.
NOTE : O nly fr ee por ts c an be us ed for a new c ir c uit. If you s elec t a por t

that is not a fr ee por t, a w ar ning w ill dis play.
NOTE : For Ec lips e links that have Adaptive Modulation, the Pr ior ity
level indic ates the pr ior ity of the new c ir c uits . Adaptive Modulation pr i-
or ity c annot be c hanged fr om Pr oVis ion.
l If a Loop Switch path has been selected, you can edit the Loop Switch port
connections and directions by clicking the Edit… button:
614-330055-001 DECEMBER 2015 189

o A dialog appears with the cross-connection information for each side of the
loop switch ring:
o As in the previous step, you can click on a port to assign a different port
value from a drop-down menu. To change the east and west directions of
the ring, click the Swap East/West button.
l Click the OK button to confirm the configuration.
10. After the circuit capacity and other values are correct, click Commit
Changes.
11. ProVision writes the changes to the nodes. This can take several minutes;
progress indicators display during the process. First, ProVision checks with
the radios. Then, it verifies that the circuit changes were made successfully.
A message displays when the circuit change is written successfully, or if it is
not successful.
12. In the Circuit Provisioning screen, click Close. The new circuit displays in
the Circuits tab, in the list of circuits for the radio.
13. After you have completed Circuit Provisioning for a circuit, you can open it,
edit the data port connections and capacity, and write it to the radios again.
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 381.
Circuits deleted because they no longer exist in the ratio network are shown via Delete a
Circuit on page 190.
Delete a Circuit
You can delete one or more circuits from the Circuits Tab. Deleting a circuit will delete it
from both the software and the radio network.
190 AVIAT NETWORKS

Procedure
1. In the Circuit Tab, right-click the name of the circuit.
2. Select Delete on the right-click menu displayed.
The Delete Circuits window displays.
3. To delete the selected circuit from both ProVision and the radio network, select
OK.
4. To not delete the circuit at all, click Cancel.
5. If you chose step 3 the Circuits Tab is refreshed and the circuit is no longer dis-
played.
614-330055-001 DECEMBER 2015 191

Configuring and Synchronizing Devices

This section details device configuration and synchronization procedures:
l Clock Synchronization View on page 192
l Viewing Configuration for Devices on page 194
l Configuration Profiles for Bulk Configuration on page 201
l Eclipse and CTR Node Licenses on page 237
l Viewing/Changing Network IP Addresses on page 217
l Viewing/Changing TNet Proxy Configurations on page 218
l Using the TNet Proxy Viewer on page 220
Clock Synchronization View

Synchronous Ethernet allows various nodes in an Ethernet network to synchronize to
the same clock frequency.
NOTE : This func tion r equir es a featur e lic ens e: s ee Abou t Licenses.
In ProVision, you can view the clock synchronization of devices in a network. Clock Sync
Mode, opened in the Map Viewer, provides a visualization of the current network syn-
chronization configuration, allowing an engineer to understand how clock signals are
being distributed across the network, with:
l A color-coded clock icon for each source of timing synchronization. Note that
the sources are normally external to the network.
l Color-coded links between devices receiving their timing from the matching
source.
l Color-coded highlights for devices where clock quality and stability are below
set thresholds.
l Synchronization properties in tool tips
NOTE : You c an view c loc k s ync hr onization per for manc e data us ing the
C lock Sy nchronizat ion Net work Healt h Rep ort on p age 4 85.
192 AVIAT NETWORKS

Procedure
1. Within the Tree Viewer, select a Container or device. The related network displays
in the map Viewer.
NOTE : Note: Us e the Map or L ogic al Container view s o that all nodes
r elating to the s ync hr onized netw or k ar e vis ible.
2. In the Map toolbar, select the Clock Sync icon.

3. The Clock Sync Mode view displays.
4. Review the clock synchronization. The Clock Sync view provides a visualization of
the current network synchronization configuration. The view shows:
l External clock sources as inputs (each external clock source is given a unique
color).
l Distribution of the clock from node to node across radio links, with direction of
clock propagation shown by colored arrows along links.
l Degraded configuration, where a node has fallen back to holdover or free-
running mode.
5. To set the Quality and Stability thresholds for the view, right click on the map
view and select Performance - Clock Sync Performance Metrics. In the screen, set
the quality threshold from the drop-down menu and set the number of switches for
the stability threshold. Click OK and these values are saved and applied to all Clock
Sync Views. Devices that do not meet the quality and stability thresholds will be
highlighted in the view.
614-330055-001 DECEMBER 2015 193

6. Right click on any map icon and select Clock Sync Properties from the menu. A
clock sync properties view is shown for each clocked device in the map item, includ-
ing:
l The clock synchronization device (in the title of the view window)
l Clock sources, listed in priority order.
l The current locked clock source is highlighted (color of the highlight matches
the arrow color on the map).
l The status of the SSM feature, either enabled/disabled. (SSM, Syncronization
Status Messaging, is an extension of the Synchronous Ethernet feature. It
enables monitoring of the Quality Level, QL, of configured clock sources, and
for the automated switching of the device's clock source to the "best available"
source).
Viewing Configuration for Devices

Configuration data is entered via a craft tool and stored in the radio. Use the Con-
figuration Viewer to review the configuration for a device: ProVision retrieves and dis-
plays the device values from the craft tool. You can also save the configuration data for
a device as a text .CSV file.
Procedure
1. Within the Tree or Map Viewer, right-click the device icon. Select Configuration
Viewer from the right-click menu.
2. The Configuration window displays.
194 AVIAT NETWORKS

3. Select the required tab to view the device data in which you are interested.
4. The data may have changed since you selected to view it. To refresh the data,
select the Refresh from Radio button.
5. To save the configuration data as a .CSV file, click Save.
6. To close the Configuration window, select Close.
The table below lists the data that displays in the Configuration Viewer for different
radio and device types. Note that the most frequently used tabs are listed first, and spe-
cialized tabs are listed later.
Tab Description
Information tab The information tab lists general information about the device, such as name,
site name, IP address, and type.
Radio Fre- For Eclipse radios, the Configuration Viewer window has separate tabs that
quency/ Link list the radio frequency configuration for each link.
tabs 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).
NOTE: If DAC GE3s are included for an Eclipse radio, they are listed in
the Software tabs. Note: Remote link information is not supported for
IDU protected devices
For protected XP4 radios the Configuration Viewer window has two radio fre-
quency tabs: RF 1 and RF 2.
614-330055-001 DECEMBER 2015 195

Tab Description
For Altium, DART, TRuepoint, MegaStar, and Velox radios the Con-
figuration 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.
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 Con-
stellation radios display one Link tab and the IP Routing tab:
Constellation via Farscan Proxy radios do not display the IP Routing tab.
196 AVIAT NETWORKS

Tab Description
The radio frequency tab lists information about the radio type (capacity, band-
width 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.
Ethernet (CTR Ethernet port values for a device.

8540)
Hardware tab The Hardware tab lists the version of the supported platform and IDU serial
(Velox only) number and barcode.
614-330055-001 DECEMBER 2015 197

Tab Description
Interfaces The device interfaces for a device.
(ADR*, Memotec
CX-U)
* With firmware
later than P2.6.
IP Routing Tab This tab provides the IP routing settings for a device.
(TRuepoint 5000,
Constellation
without FarScan
Proxy only)
MC Alarm Inputs Alarm inputs and relay outputs for the DVM’s connections.
and MC Relay
Outputs (DVA,
CAU)
198 AVIAT NETWORKS

Tab Description
Mux Modem Tab Mux modem settings for TRuepoint 4040/5000 or Constellation radios.
(TRuepoint 4040
and 5000, and
Constellation)
PAI Programmable Alarm Indicators (PAIs) for a DVM.

(DVA Only)
614-330055-001 DECEMBER 2015 199

Tab Description
POE (CTR 8540 POE plugins and related settings. Includes PSE Settings table which contains
only) power of ethernet port specific information
RSC and RPS Data about the Radio Service Channel and Radio Protection Switching for the
(GP) TRuepoint 6500 radio.
(TRuepoint 6500,
WTM 6000)
NOTE: For more on the RSPI, RSC/RPS, and Service tab values for TRue-
point 6500, see the TRuepoint 6500 documentation.
RSPI Radio Section Physical Interface values for the TRuepoint 6500.
(TRuepoint 6500,
WTM 6000)
200 AVIAT NETWORKS

Tab Description
Service (TRue- Service data for the TRuepoint 6500 radio.
point 6500, WTM
6000)
Slot Con- Details about each slot for the DXR radio, and the hardware and software
figuration Tab installed at each slot.
(DXR Only)
Software tab The Software tab lists the version of the software for the components of the
radio.
Configuration Profiles for Bulk Configuration

This section describes the pre-set profile options for using the Configuration Profiles.
614-330055-001 DECEMBER 2015 201

The Configuration Profiles function enables you to apply configuration settings to mul-
tiple devices, including to their alarms. 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.
Bulk configuration options are available for the following devices:
l Altium
l CTR 8540
l CX/Megastar
l Constellation
l DART
l Eclipse, including options for:
l Ethernet
l IDU ES
l DAC ES
l DAC GE
l DAC GE3
l Portal ACL and SNMP ACL configuration
l Radio account security
l RADIUS
l LE3000/LE3200
l Radwin 2000
l Radwin WL 1000
l TRuepoint
l WTM 3100, 3200, 3300
l WTM 6000
l XP4
To set up bulk configuration, see the following topics:
l Create and Execute a New Configuration Profile on page 202
l Configuration Profile Reference on page 206
l Delete a Configuration Profile on page 211
Create and Execute a New Configuration Profile

From the Configuration Profile screen, you can select and update a
Configuration Profile, apply it to one or more devices, and save it to apply it to addi-
tional devices.
202 AVIAT NETWORKS

Procedure
1. Open the Configuration Profile window:
l From the menu bar, select Configuration > Configuration Profiles.
l Or, right-click a container or a device and select Configuration > Profiles from
the right-click menu.
2. The Configuration Profile window displays the available profile options for the
device in the left frame. In the right frame, it displays the selected profile option for
viewing and editing.
NOTE : Us e the dr op-dow n menu at the upper left to view S uppo rt ed ,

All , or S av ed Configur ation Pr ofiles for this devic e type. You c an als o Fil-
t er for c onfigur ation pr ofiles that c ontain a keyw or d.
3. In the right frame, select the profile option. Click the Read button to view the cur-
rent settings for the device.
NOTE : The R ead button is ac tivated if you opened the Configur ation
Pr ofile w indow by r ight-c lic king an individual r adio. Clic king this button
r eads the r adio’ s c onfigur ation and automatic ally enter s the infor mation
to the Configur ation Pr ofile w indow .
4. In the right frame, enter any changes to the configuration settings. See Con-
figuration Profile Reference on page 206 for information on the different profiles.
Then, click Next.
5. Select the devices where you will execute these new profile settings. The left frame
displays the profile settings. The right frame displays the devices available to receive
this profile setting. Note that you can Filter the devices, or use a check box to select
All Devices or Unmanaged devices. When you have selected the devices, click
Execute. A message will ask you to confirm Executing the profile.
614-330055-001 DECEMBER 2015 203

6. The new profile is executed and applied to the devices. A Task Manager screen dis-
plays the process.
The Task Manager tracks the status by displaying the date and time that the bulk con-
figuration command was issued, with the configuration name. Select the + to display
the devices that had the bulk configuration command applied.
NOTE : If you ar e w r iting c hanges to a TRuepoint devic e, a w ar ning mes -

s age dis plays : E xecut ing t hese changes will o v erwrit e any prev io us
set t ings. Clic k O K to finis h s aving the c hanges .
NOTE : If you ar e w r iting Advanc ed or Ether net c hanges that impac t a

DAC G E, a w ar ning mes s age dis plays : These C o nf igurat io n Pro f ile(s)
may af f ect t raf f ic. Are y o u sure y o u want t o execut e t hem? Clic k OK
to finis h s aving the c hanges .
7. You can save a configuration profile by clicking the Save button in the Con-
figuration Profiles screen. The Save screen displays, prompting you to name
the configuration profile:
204 AVIAT NETWORKS

8. The newly saved profiles appear when you select Saved in the drop-down menu.
Each item includes a list of the scripts that are assigned to it. Select a script and
click Next.
9. Select the Execute button to execute the saved profile. The Selected Object List
window opens.
10. The Object List window lists only those radios that support the profile.
11. Select the Close button to close the Task Manager.
12. Select the Close button to close the Configuration Profile window.
NOTE : Saved c onfigur ations als o appear in the r ight-c lic k menu for the
devic e. See the example below .
614-330055-001 DECEMBER 2015 205

Delete a Configuration Profile on page 211
Configuration Profile Reference

This section includes two tables with bulk configuration setting details:
l Eclipse Configuration Profiles
l Profiles for All Other Devices
Configuration profiles apply configuration settings to multiple devices in a single trans-
action. This includes the ability to predefine the settings for one of more devices and
then later writing to the devices, or copying the settings from one device, optionally edit-
ing, and then writing to the same or other devices.
This section provides a list of the profiles available for each device type. For each profile,
a description of the parameters that can be configured is provided.
NOTE : Alar m Configur ation tabs ar e s imilar for all devic e types . They
lis t the alar ms for the devic e or plug-in, w ith a dr op-dow n menu for
s ever ity levels , inc luding C rit ical, Majo r, Mino r, W arning, o r Inf o rm-
at io nal. You c an r es et the alar m s ever ity levels or us e the Skip option to
s kip them.
Table 4-8. Eclipse Configuration Profiles
Configuration Profile Settings

Eclipse AUX Entry of descriptions and severity levels for additional alarms.
Module:Alarm Input Con- Enter the Alarm Description and select the Severity level.
figuration
Eclipse Alarm Configuration Check the box to reset all alarm values for an Eclipse device or plug-in to
Default Reset the factory defaults.
206 AVIAT NETWORKS


Eclipse DAC GE 3 Plugin: Enables specific DAC GE3/IDU GE3 configurations.
Eclipse Advanced Settings for NOTE: Changing this setting may affect network traffic. For more
DAC GE3 data on these values see the Eclipse Portal documentation.
- Flow Control - Check box to enable.
Eclipse GE 3 Ethernet Mod- - MAC Address Learning - Check this box to enable MAC Address
ule: Eclipse Advanced Settings Learning.
for IDU GE3 - Max Frame Size - Set the maximum frame size.
- Storm Control - Click to enable storm control.
- Broadcast - Check this box to enable broadcast.
- Multicast - Check this box to enable multicast.
- Unknown Unicast - Check this box to enable unknown unicast.
- Storm Traffic Rate % - Specify the % of storm rate (received
broadcast and multicast traffic) enabled from this port. A value of 0
filters all storm traffic: a value of 100 disables storm control.
Eclipse DAC GE Plu- Enables specific DAC GE/IDU GE configurations.
gin/Eclipse GE Ethernet NOTE: Changing this setting may affect network traffic. For more
Module: Eclipse Advanced data on these values see the Eclipse Portal documentation.
Settings for DAC GE/IDU GE - Flow Control - Check box to enable.
- Disable Address Learning - Check this box to disable MAC
Address Learning: this is for devices used in ring/mesh networks.
- Link Status Propagation - Check to enable link status propaga-
tion.
- Storm Traffic Rate % - Specify the % of storm rate (received
broadcast and multicast traffic) enabled from this port. A value of 0
filters all storm traffic: a value of 100 disables storm control.
- Max Frame Size - Set the maximum frame size.
- Restore Timer(s) - Set the restore timers value.
Eclipse GE 3 Ethernet Mod- NOTE: Changing this setting may affect network traffic.
ule: Eclipse Ethernet Port Set- Ethernet port settings for the selected Eclipse device.
tings for IDU GE3
Use the drop-down menus to select the required values for the usage, the
speed, the duplex, and Master/Slave settings.
Eclipse DAC GE3 Plugin:
Eclipse Ethernet Port Settings
for DAC GE3
Eclipse DAC ES Plugin: NOTE: Changing this setting may affect network traffic.
Eclipse Ethernet Priority Map- Ethernet Priority Mode settings for the selected Eclipse devices.
ping for DAC ES - Priority Mode - Select a Priority Mode to receive the priority values.
Choose a value from: Port Default, 802.1p, 802.1p then Diffserv, or
Eclipse DAC GE Plugin: Diffserv then 802.1p, Diffserv.
- Internal Priority -Assigns a priority level to a device in this set of
Eclipse Ethernet Priority Map-
Priority Mode priorities. Choose a value from Low, Medium Low,
ping for DAC GE
Medium High, or High.
Eclipse ES Ethernet Module:

ping for IDU ES
Eclipse GE Ethernet Module:

ping for IDU GE
614-330055-001 DECEMBER 2015 207


Eclipse DAC GE3 Plugin: NOTE: Changing this setting may affect network traffic.
Eclipse Ethernet Priority Map- Ethernet Priority Mode settings for the selected Eclipse devices.
ping for DAC GE3 - Internal Priority - Assigns a Priority level to a device in the set of
Priority Modes: 802.1p, Diffserv, and/or MPLS EXP.Choose a value
Eclipse GE 3 Ethernet Mod- from Q0 (Low) to Q7 (High).
ule: Eclipse Ethernet Priority
Mapping for IDU GE3
Eclipse DAC ES Plugin: NOTE: Changing this setting may affect network traffic.
Eclipse Ethernet Port Settings Ethernet port settings for the selected Eclipse device. Use the drop-down
for DAC ES menus to select the required values for the speed, the duplex,the MDIX,
and Priority settings.
Eclipse DAC GE Plugin:
for DAC GE
Eclipse ES Ethernet Module:

for IDU ES
Eclipse GE Ethernet Module:

Ethernet Priority Mapping for
IDU GE
Eclipse DAC GE3 Plugin: NOTE: Changing this setting may affect network traffic.
Eclipse Link Status Propaga-
tion for DAC GE3 Link status propagation settings for the selected
Eclipse devices, including:
- Local Peer - local port peer.
- Remote Peer - remote port peer.
- Mode - Normal or Degraded.
- Restore and Hold timer values
Eclipse Login Banner Con- Enter text to display before and after a user logs into Eclipse Portal from
figuration a device. This is useful for warnings and administration requirements.
Eclipse NMS Traps Destin- NMS trap destination information for the selected radios.
ation - Enable - Select the checkbox to enable the trap destination.
- Destination - The IP address of the trap destination.
- Destination - IP address of the 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 applic-
ation.
Eclipse OSPF Settings IP address of a server to use for OSPF settings, and to enable OSPF use
for the IP’s ports, AUX drives, and slots.
CAUTION: OSPF system settings are complex. An IP must be set up
in Portal as enabled for OSPF for these settings to work correctly. This
setting should only be used by experienced administrators with access
to Portal.
Eclipse Portal Lockout Set the time in seconds that the Portal Access will not be allowed (i.e.,
Reboot Time users will be locked out of Portal) after a reboot.
208 AVIAT NETWORKS


Eclipse Radio Account Con- Set the user permissions for ProVision users for this specific Eclipse
figuration radio. See Setting Eclipse Device Security Values for more details.
- User Name - Between 4 and 32 characters
- Password - Between 8 and 32 characters
- Confirmation - Retype the Password.
- Enter this information for each user.
- Permissions - Check the boxes for the user's permission levels for
Eclipse radios: Read Only, Engineer, Admin, Crypto. At least one Per-
mission must be selected for a user.
Eclipse RADIUS Con- NOTE: The RADIUS server must be enabled to use this. See
figuration Enabling a RADIUS Server.
Set the RADIUS authentication "shared secret" in bulk for multiple
Eclipse IP addresses.
- Enable - Check to enable for noted radio
- IP address - for Eclipse radio (valid for both IP4 and IP6)
- Port - Authentication port
- Shared Secret - Shared Secret value
- Confirmation - Confirmation value
NOTE: The Eclipse radios will try to authenticate any login request
against each RADIUS server in the order they are listed until one of
the RADIUS servers responds.
Eclipse Security Portal ACL IP addresses in this list are able to connect to Portal. If Enable Portal
Configuration ACL is checked and the IP address is not in this list, the IP addresses are
denied access to Portal.
- Enable Portal ACL- Check to enable Portal ACL for all Eclipse
radios in ProVision.
- IP Address - For Eclipse radio
- Mask - Mask to apply to Eclipse radio range
Eclipse Security SNMP ACL IP addresses in this list are able to send messages/commands to radios. If
Configuration Enable SNMP ACL is checked and the IP address is not in this list, the
SNMP messages are denied.
- Enable SNMP ACL - Check to enable SNMP ACL for all devices in
ProVision.
- IP Address - For SNMP server
- Mask - Mask to apply to SNMP range
Eclipse SNMPv3 User Account Sets up the users able to access Eclipse SNMPv3 devices with:
Configuration - Name
- Account Level - Crypto, Control, Admin, User
- Authentication Password (twice to confirm)
- Privacy Password (twice to confim)
Click Remove to remove one user. Click Remove All to remove all
users.
Eclipse Time Server Settings IP address of a time server that synchronizes the internal clocks of the net-
work 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 Time zone to apply to one or more selected radios. Use the drop-down
menu to select the required time zone.
614-330055-001 DECEMBER 2015 209


Eclipse SNMPv3 User Create or remove SNMPv3 security users, including:
Accounts - Name - User name
- Access Level - Security access level
- Authentication Password
- Privacy Password
Table 4-9. Profiles for All Other Devices

Altium/XP4: XP4 16xE1 Trib When you configure the trib controls for each of the 16 tribs, you choose
Controls whether the trib is Normal (commissioned) or Inverted (not com-
missioned.) Note that Normal tribs will report errors if they have no
traffic.
Constellation Trap Destin- Trap destination information for the Constellation radios.
ations - Destination - The IP address of the trap destination.
NOTE: This data is not active for Constellation for FarScan devices.
DART NMS Trap Destin- Select up to three trap destinations for the following components of the
ation DART radios:
- Ethernet
- Radio
- Serial Port 1
- Serial Port 2
Select the check box to activate the trap destination for the selected com-
ponent. In the Destination field, enter the IP address for the specified
trap destination.
LE3000/LE3200 Trap Destin- Trap destination information for the LE3000 or LE3200 radios.
- Port - Enter the port required for the trap destination.
Radwin 2000 Trap Destin- Trap destination information for the selected Radwin 2000 devices.
WinLink 1000 Trap Destin- Trap destination information for the selected WinLink 1000 devices.
TRuepoint SNMP Man- Trap destination information for the selected type of TRuepoint radios.
- Enable - Select the checkbox to enable the trap destination.
agers: 5000, 4040,
- Destination - The IP address of the SNMP manager.
4000 NOTE: Executing these changes overwrites any previous settings, and
disabling SNMP managers also disables ProVision’s SNMP connection
to the device.
TRuepoint Trap Destin- Trap destination information for the selected type of TRuepoint radios.
ations: 6400, 5000, - Enable - Select the checkbox to enable the trap destination.
4040, 4000
WTM 3100 Time Manager Time zone information for the WTM 3100 devices.
- Enable - Check to enable time management.
- Destination - IP address of the WTM 3100 device.
- Time Zone - Select time zone of device.
WTM 3100 Trap Destinations Trap destination information for the selected WTM 3100 devices.
- Enable - Check this box to enable trap destination management.
210 AVIAT NETWORKS


WTM 3200 SNMP Managers SNMP trap destination information for the WTM 3200 devices.
- Enable SNMP - Check to enable SNMP management.
- IP Address - The IP address of the trap destination.
WTM 3300 NMS Trap Destin- NMS Trap destination information for the selected WTM 3300 devices.
ations - Domain - The specified domain.
WTM 3300 Time Zone Time zone to apply to one or more devices. Use the drop-down menu to
select the required time zone for the radio.
WTM 6000 Trap Destinations Trap destination information for the selected WTM 3100 or WTM 6000
devices.
Destination - The IP address of the trap destination.
Delete a Configuration Profile on page 211

Table 4-10. CTR 8540 / 8300 Configuration Profiles
CTR - Qos - Classification For more information, go to Quality of Service - Classification.
CTR - QoS - Scheduling For more information, go to Quality of Service - Scheduling.
CTR Syslog Forwarding Syslog trap forwarding destination for the selected devices.
- Address Type - Select the checkbox to enable the trap destination.
- Address - The IP address of the destination ProVision server.
- Port - The port number of the destination ProVision server.
- Protocol – The protocol used to send syslog events. This can be
UDP, TCP or TLS.
CTR Time Server IP address of a time server that synchronizes the internal clocks of the net-
work devices.
- Time Server - Select the checkbox to activate the time server set-
ting.
- IP Address - IP address of the time server.
CTR Time Zone Settings Time zone to be applied to the selected devices.
Use the drop-down menu to select the required time zone.
Delete a Configuration Profile

You can delete a saved configuration profile.
Note that you cannot delete one of the default configuration profiles provided by Aviat
Networks. You can only delete configuration profiles that you or your users have created.
Procedure
1. From the menu bar, select Configuration > Configuration Profiles. The Con-
figuration Profiles window opens.
2. From the left side of the screen, select the saved profile to delete.
3. Select the Delete button. ProVision asks if you really want to delete the
selected profile. Select Yes to continue.
614-330055-001 DECEMBER 2015 211

4. The selected profile is deleted. It will not be available in this screen or in the right-
click menus.
5. Select the Close button to close the Configuration Profiles window.
Quality of Service - Classification

This screen displays QoS - Classification. Users can configure priority mapping and clas-
sification for VLANs and interfaces. Supported classification includes priority types for
802.1p, DSCP and IP ToS.
VLANs and interfaces with identical classification configurations are grouped together.
Procedure
1. Go to Qos - Classification.
2. To read the current device's Classification click the Icon-Read. See Create
and Execute a New Configuration Profile for details on reading configuration
profiles.
n The Policy map is also read and will replace the policy map of the
selected CTRs when the configuration is executed.
3. Priority mapping and classification settings display by classification type
(Interface, VLAN). Types that have identical configurations are grouped
together.
4. To add a new Classification, select the type (Interface, VLAN) and click on
the Priority type to Add (Vlan 802.1p, IP Tos, IP DSCP, MPLS EXP).
5. Clicking on the Classification will either collapse or expand it.
6. To remove a classification, expand it and click the Remove button.
7. The values for the classification display. You can change:
n Enabled status of a Priority mapping
n Ingress priority to Internal Priority mapping
n Pre-Color
n Drop Precedence
n Policy Map - Note you will need to read a radio to get all the policies.
8. You can add an Interface or VLAN, depending on the Type of the
classification, by selecting the Applies To button.
n You can only add a VLAN that ProVision knows about but only the
VLANs that the radio knows about will be applied.
n ProVision shows all possible Interfaces that a CTR can have but only
the Interfaces that the radio knows about will be applied.
212 AVIAT NETWORKS

o A port-channel can have any number assigned to it, so port-channels

are shown by their If Index. For example, po (If Index=27).
Figure 4-6. Qos - Classification
Figure 4-7.
Figure 4-8. QoS Policing Values
Field Description
QoS Group Click on a classification to display the values for a QoS group.
Internal Priority Displays the internal priority assigned to ingressing traffic for the inter-
face/ VLAN. Default is 0, lowest priority.
Enable Check the box to enable this priority level. Each priority mapping creates
a rule on the switch. As there are limited rules, it is recommended that
for IP DSCP only the priorities in use should be enabled.
Pre-Color Set the pre-color policing value from the drop-down menu.
- None
- Red
- Yellow
- Green
614-330055-001 DECEMBER 2015 213

Field Description
Policy map/policing Set policing values for policy map ID and policing mode. Options dis-
played are policies configured via E-Portal Quality of Service - Policing.
NOTE: A policy must be configured for traffic to flow. Default con-
figuration contains Policy 1 with no metering.
Quality of Service - Scheduling

This screen displays scheduling action by enabled interface. Users can set QoS Schedul-
ing algorithms and congestion control for each enabled QoS interface. There are eight
queues for each interface.
Procedure
1. Go to Qos - Scheduling.
2. To read the current device's Scheduling click the Icon-Read. See Create
and Execute a New Configuration Profile for details on reading configuration
profiles.
n The Congestion Control map is also read and will replace the
Congestion Control map of the selected CTRs when the configuration is
executed.
3. Any Ports that have a default configuration are shown beside the Default
Ports button.
n The default configuration is Strict Priority and Congestion

Control of None.
n The ports are shown in compressed format. For example, 0/1, 0/2, 0/3,
0/5 will be shown as 0/1-3,5.
4. To change a ports default configuration click the Default Ports button and
untick that port.
5. You can view Internal Priority and Weight values. You can change:
n Scheduler - Select the Scheduler algorithm. Options are listed in the
table below.
n Congestion Control - Select either None or one of the configured queue
templates.
214 AVIAT NETWORKS

Figure 4-9. Qos - Scheduling
614-330055-001 DECEMBER 2015 215

Figure 4-10.
216 AVIAT NETWORKS

Figure 4-11. QoS Policing Values
Field Description
Scheduler Select the QoS Scheduling algorithm:
- Strict Priority
- Round Robin
- Weighted Round Robin
- Weighted Fair Queuing
- Strict Round Robin
- Strict Weighted Round Robin
- Strict Weighted Fair Queuing
- CIR EIR - Committed and excess rate algorithm
- Strict CIR EIR - Strict committed and excess rate algorithm
CAUTION: CIR EIR options are not supported on radio, L1LA or pro-
tection interfaces
Internal Priority Displays the Internal Priority setting for each queue.
Weight Displays the weighting applied to weighted scheduler actions by queue. A
color square displays the apportionment of weighting by weighted queue.
NOTE: Configurable only for scheduling algorithms that use weights. For
Weighted Fair Queuing and Strict Weighted Fair Queuing - the weight
must be larger than the interface's MTU.
Congestion Control Enable congestion control by selecting an option, from the list of con-
figured queue templates. Configure these from E-Portal's Quality of Ser-
vice - Congestion Control.
Viewing/Changing Network IP Addresses

The network configuration gives you a list of the device IP addresses entered via ProVi-
sion. From here you can view and change the ProVision device IP addresses. This func-
tion enables you to view a list of the network devices’ IP address and where required,
change an IP address.
NOTE : Changing a devic e’ s IP addr es s w ithin Pr oVis ion does not c hange
the IP addr es s s tor ed in the devic e its elf.
Procedure:
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.
614-330055-001 DECEMBER 2015 217

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.
Viewing/Changing TNet Proxy Configurations

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

CAUTION: If you change a subnet without moving the device’s cabling to the new sub-
net, when ProVision next polls the Proxy, the device displays in an errored state.
NOTE : The TNet devic e ic ons ar e detailed in TNet Devic es on page 2-34.
Procedure
1. In the Tree Viewer or Map Viewer, right-click a TNet Proxy icon. The Proxy
right-click menu displays:
2. Select Proxy Configuration Manager. The Proxy Configuration Manager window
displays.
Activity How to...
To change a Proxy’s name or Select the required Proxy icon.
increase its number of subnets
within ProVision:
Make the required changes to the Subnets field. There is a max-

imum of 16 subnets per Proxy.
To save the changes within ProVision, select Commit Changes.
To change a Proxy’s IP See Viewing/Changing Network IP Addresses on page 217.
address:
To move a TNet device from Expand the Proxy and the subnet to display the TNet devices.
one subnet to another subnet Select the required TNet device.
and/or
change the TNet’s address on
the subnet:
The device’s name, the subnet it is connected on, and its address
on the subnet are displayed.
Enter the new subnet number and/or the new address.
Select Commit Changes.
To close the Proxy Configuration Manager window, select Close.
614-330055-001 DECEMBER 2015 219

Using the TNet Proxy Viewer

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.
NOTE : You mus t have a Configur ation s ec ur ity pr ofile as a us er to

ac c es s the Pr oxy View er .
Procedure
1. In the Tree Viewer or Map Viewer, right-click the required TNet Proxy icon. Or, loc-
ate 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.
220 AVIAT NETWORKS

Loading/Activating New Software and

Licenses
This section describes how to load and activate new Eclipse, CTR 8540, and TRuepoint
software, and new Eclipse node lice nses.
l About Loading Device Software Via ProVision on page 221
l Eclipse Software Loading Examples on page 222
l Stage 1: Software Load Procedure on page 224
l Stage 2: Software Activation Procedure on page 230
l Eclipse and CTR Node Licenses on page 237
l Device Configuration Backup and Restore on page 240
About Loading Device Software Via ProVision

CAUTION: 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 software for the following devices:
l All Eclipse Radios
l All TRuepoint Radios
l CTR 8540
l WTM 3300
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:
l Manual Activation - ProVision lets you activate each radio manually. This is
available for Eclipse, TRuepoint, CTR, and WTM devices.
l 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.
614-330055-001 DECEMBER 2015 221

An entire network of 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 dis-
ruption to network traffic.
NOTE : When loading s oftw ar e us ing this featur e, the s ame ver s ion of
the s oftw ar e is loaded onto all par ts of a devic e.
W AR NING : Do not initiate s oftw ar e loading dur ing the per iod w hen
daily per for manc e c ollec tion is per for med (default 1 am); this c an r es -
ult in a failed data c ollec tion poll.
The Software Upgrade Process

The software upgrade is split into two separate stages: loading and activation.
l Stage 1: Software Load Procedure on page 224 - 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.
l Stage 2: Software Activation Procedure on page 230 - 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 down-
load 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 soft-
ware 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.
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
222 AVIAT NETWORKS

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 4-12. 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.
614-330055-001 DECEMBER 2015 223

Figure 4-13. Example 2: An Eclipse Radio Network Divided into Regions
Stage 1: Software Load Procedure

The software load procedure is further divided into two parts:
l Part A: Register the Software onto the ProVision Server
l Part B: Load the Software onto the Devices
Part A Register the Software onto the server

Prerequisites
l 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.
l For Eclipse devices with Strong Security enabled, to enable ProVision to load
software updates, you need an active SNMPv3 user account for the devices, set
up with the Crypto access level. An Eclipse SNMPv3 user account can be set
up from the Portal craft tool, or set up from ProVision via the Configuration
224 AVIAT NETWORKS

Profile Settings. See Setting SNMPv3 Security Access on page 1 for more
details.
CAUTION: Before loading software onto a network of devices, always complete the
load and activation to one radio in a test lab, and check for normal operation in the lab
before downloading software to the live network.
Procedure
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.
NOTE : If the r equir ed s oftw ar e is alr eady lis ted on the r egis ter , pr o-
c eed to Part B Load t he Soft ware ont o t he Dev ices on p age 227.
2. Click on the Register menu and select the type of software pack that you want to
load.
3. A directory window displays.

4. You need to select the software that you will load. Either:
l Select the directory that contains the software. Select the desired software pack
and select Open.
614-330055-001 DECEMBER 2015 225

l 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.
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 Servertab. Two features are displayed: Server IP Address and Concurrent
Loads.
Ensure the Server IP Address is set to the IP address of the network interface card
facing the radio network. This is particularly important for servers that use multiple
network interface cards
226 AVIAT NETWORKS

ProVision writes this IP address to the radios of this type. When the software down-
load 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 net-
work’s bandwidth.
The Concurrent Loads slide bar allows you to tell ProVision how many radios it can
simultaneously load software to. If a network has 2000 radios, the ProVision applic-
ation 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 band-
width) the time to load the software to all 2000 radios would be much faster.
8. Select OK to close the Software Loading Preferences window.
Part B Load the Software onto the 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.
614-330055-001 DECEMBER 2015 227

Heading Description
Status 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.
= Incompatible objects.
= warning icon noting that there are problems with this device,
which may impact on software loading.
Object The type and name of the device.
Container The IP name of the container.
Software Ver- The version number of the currently installed software.
sion(s)
The Software Loading screen identifies the following for each unit in ProVision:
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.
NOTE : T h e sof tw are d ow n l oad p rocess m ay take u p to 30 m in u tes or l on g er,

d ep en d in g on th e n etw ork b an d w id th , th e n u m b er of con cu rren t l oad s, th e
n u m b er of d evices b ein g l oad ed w ith in th e task, an d th e siz e of th e sof tw are
f il e b ein g l oad d. Ec lips e s oftw ar e nor mally takes 30 minutes or longer to
load; TRuepoint s oftw ar e may load mor e quic kly.
Procedure:
1. From the menu bar, select Configuration > Software Loading. The Software Load-
ing 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 cur-
rent software version.
3. In the Operation menu, select the software type to load. The devices of that type
display. In the sample below, for the TRuepoint software loading, there are Oper-
ation menu options for standard TRuepoint or RFU upgrade.
4. Select the devices that are to have the software loaded. To organize or filter the
devices, you can:
l Select the column heading Object Container to sort the devices by their
location in the network.
l 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.
228 AVIAT NETWORKS

l To load a group of devices that are not listed sequentially, hold down the ctrl
key and select each device.
l To identify devices that are not compatible with the software type, click filter
Incompatible Objects. An exclamation mark displays beside any incompatible
objects.
5. For Eclipse, CTR8540, CTR8300 and WTM3300 devices, you can Select the Sched-
uled 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.
NOTE : If you do not s elec t Sc heduled Ac tivation, the s oftw ar e ac tivates

immediately after you c lic k Lo ad S elect ed S o f t ware .
6. Select the software pack version to be loaded from the Operation drop-down box.
(The version that was loaded in steps 2 and 3 appear in the list.)
7. Select the Apply Selected Objectsbutton to begin the download.
8. A ProVision message box appears. Select Yesto 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 the
Activatebuttons appear. See Stage 2: Software Activation Procedure on page 230 for
the next steps to take.
NOTE : If you s elec ted s c heduled ac tivation for an Ec lips e devic e,

ins tead of Act iv at e buttons appear ing, a timer dis plays w hic h c ounts
dow n the amount of time befor e the s c heduled ac tivation oc c ur s .
11. If the software load fails, or is incomplete, an alarm icon displays: right-click
on the icon to view information about the software loading problem.
614-330055-001 DECEMBER 2015 229

If the software loading fails for a WTM 3200 device, the following message may display:
To resolve this, reconfigure the WTM 3200 to support https mode: Unmanage it, then
Manage it again and retry the software loading. See Managing a Device on page 156
12. Stage 2: Software Activation Procedure on page 230
Stage 2: Software Activation Procedure

The activation procedure is when software, installed in Stage 1: Software Load Procedure
on page 224 is switched on. There are separate procedures for:
l Eclipse Software Activation Procedure on page 231
l TRuepoint Software Activation Procedure on page 233
l Other Software Activation Procedure on page 236
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/ter-
230 AVIAT NETWORKS

minal, 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 activ-
ating 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 affect-
ing 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.
NOTE : For Ec lips e devic es , w hen the s oftw ar e is loaded it r es ides in

both the IDU and the ODU.
For an Ec lips e Node, the s oftw ar e r es ides in the NCC and in eac h ODU
plug-in.
For an Ec lips e Ter minal, the s oftw ar e r es ides 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.
If the Activation fails, a message displays, with a recommended action forpreparing
the device.
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.
l 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.
l Reboot (90 sec. to 2 min.): The Eclipse device reboots (resets the software).
614-330055-001 DECEMBER 2015 231

l 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.
NOTE : It is only dur ing the r eboot s tep (w hic h typic ally las ts les s than
30 s ec onds ) that tr affic c an be affec ted. Dur ing the r eboot, NMS vis ibility
of the r ebooted devic e and any dow ns tr eam devic es ar e los t.
l 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 (Stage 1:
Software Load Procedure on page 224). The message “versions OK” indicates
the two versions are the same.
3. The process is complete when each of the activation steps indicates OK.
4. Right-click the task bar to open a pop-up window with additional functions. Tool-
tips over the task provide details such as description, status, start, and end time for
the task. It also keeps a count of the goals within the task that are errored and com-
pleted.
l 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.
232 AVIAT NETWORKS

l 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.
l 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.
TRuepoint Software Activation Procedure

To activate the TRuepoint software after it has been loaded onto the devices, follow
steps 1 through 7:
NOTE : Befor e you begin, ens ur e that the TRuepoint devic es have been
s et up w ith the c or r ec t FTP c r edentials ; s ee the Dev i ce Secu ri ty
A ccou n ts s c r een.
NOTE : Standar d TRuepoint s oftw ar e and RFU upgr ades ar e s epar ate
s oftw ar e load pr oc edur es . See Step 4 of St age 1: Soft ware Load Pro-
ced u re on p age 224 for the s oftw ar e loading pr er equis ite for an RFU
upgr ade.
1. Beside the TRuepoint device, a drop-down menu button displays with options:
l Alternate System – The following process is executed:

l Switch the software banks and activate the new Controller
software, through the Alternate Software process (see
below).
l Then load the new interface card firmware and activate,
through the Firmware Upgrade process (see below).
l Alternate Software – Activates the new Controller software through the
following process. Note that this process does not affect traffic:
614-330055-001 DECEMBER 2015 233

l Switch the software banks, with the Alternate now

becoming the Primary bank.
l Reboot of the Controller, resulting in activation of the
new Controller software.
l Firmware Upgrade – Activates the new interface card firmware through the
following process:
l The Controller loads the new interface card firmware into
the cards.
l Activate the new firmware in the cards.
l RFU Upgrade – Activates the new RFU firmware directly.
NOTE : The Fir mw ar e Upgr ade pr oc es s affec ts tr affic .

For TRuepoint 5000 and 4040v2, only the SPU c ar ds (MUXes and
modems ) ar e loaded, but not the RFU(s ).
The RFU(s ) c an be loaded w ith the new fir mw ar e in the ac tive bank
thr ough Web CIT (s ee the final s tep of thes e ins tr uc tions for details ).
For TRuepoint 6400, all c ar ds (L IU, DPU, O PT, RCVR and XMTR) ar e
loaded.
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.
l Activation (<10 sec.): The TRuepoint device switches to the new software.
l 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.
234 AVIAT NETWORKS

NOTE : TRuepoint tr affic is affec ted dur ing both Ac tivation and Reboot
s tages . Dur ing the r eboot, NMS vis ibility of the r ebooted devic e and any
dow ns tr eam devic es ar e los t.
l 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 (Stage 1: Software Load
Procedure on page 224). 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:
l Upgrade Agent Not Accessible - The radio has failed to reboot after the
upgrade. Repeat the Activation from step 1.
l 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 addi-
tional functions.
614-330055-001 DECEMBER 2015 235


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 on page 194.
Other Software Activation Procedure

To activate the software after it has been loaded onto the CTR8540, CTR8300,
WTM3200 and WTM3300 devices, follow steps 1 through 6.
1. Select the Activate button to activate the software inside the device. The Activate
button changes to a Running button and an information icon appears. If the
Activation fails, a message displays, with a recommended action for preparing the
device.
2. Select the icon to open a pop-up window that tracks the activation process.
Usually, once the activation is triggered, the device will be restart with new firm-
ware.
l Reboot: The device reboots (resets the software) which may take few minutes.
l When the message “Wait for reboot OK” appears, it indicates that the reboot is
complete.
NOTE : Dur ing r eboot tr affic c an be affec ted. The NMS vis ibility of the
r ebooted devic e and any dow ns tr eam devic es ar e los t.
3. Right-click the task bar to open a pop-up window with additional functions. Tool-
tips over the task provide 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.
236 AVIAT NETWORKS

4. Right-click the individual device within the task to open a right-click window
with additional functions.
l 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.
Eclipse and CTR Node Licenses

Eclipse and CTR 8540 Node licenses can be downloaded to individual Eclipse radios or
CTR 8540 devices, one at a time or in bulk.
For Eclipse, 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 register new licenses, a copy of each license is stored in the folder: \ProVi-
sionServer\repository\licenses. A copy of each license is retained in this folder after the
license is applied to the radio.
614-330055-001 DECEMBER 2015 237

NOTE : When you upgr ade to a higher ver s ion of Pr oVis ion, the lic ens es
that w er e applied to the r adios ar e unaffec ted. It is r ec ommended to
s ave a bac kup c opy of the r epos itor y folder w ith the lic ens e files , then
migr ate the folder to the s er ver onc e the new ver s ion of Pr oVis ion has
been ins talled.
Contact one of the regional Aviat Networks sales offices to purchase an upgraded Eclipse
or CTR 8540 Node license.
Procedure
To install Node licenses:
1. When you receive the new Node licenses, place them in a temporary folder on the
computer that serves as the ProVision client.
NOTE : If you ar e loading 100+ lic ens es into the folder , this w ill take
s ome time.
2. From the ProVision menu bar, select Configuration > License Loading. The
License Loading window opens. If you have not previously browsed for or applied
any new Node licenses, the window is blank.
3. Select the Register Licenses button. The Location For License File(s) window
opens. From this window, browse to the folder that contains the new licenses. You
can either select one or more individual license files to register, or you can select the
folder to register all licenses in the folder.
4. Select the Open button. The licenses selected 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.
l 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.
l Sort the table by clicking on selected table headings.
l Only the most recent license for a particular object displays in the License
Table.
l A message displays, Found new licenses and uploaded to repository. Click OK
to proceed to the next step.
238 AVIAT NETWORKS

5. Select one or more objects and select the Load License to Selected Objects button.
NOTE : If you ar e loading a batc h of r adios , only s elec t 10 - 20 r adios at

a time. It takes appr oximately 5 minutes for Pr oVis ion to apply lic ens es
to 10 Ec lips e r adios on a r emote netw or k. A Tas k Manager dis plays and
s how s the s tatus of the batc h as the lic ens es ar e applied.
6. The licenses for the selected objects are applied to those objects.
Note that the Date Applied column is now populated. The table below details the
License Table values.
To register additional licenses, repeat steps 3 to 4. To load licenses to objects, repeat

steps 5 to 6.
7. To export the data from the License Information table as a .CSV file, click Export.
You are prompted to select the name and location of the . CSV file. ProVision notifies
you when the Export is complete.
Table 4-11. License Table Headings
614-330055-001 DECEMBER 2015 239

Heading Description
Object The name of the Node.
Container The container of the Node.
Serial Number The serial number of the Node.
Files The names of the License files.
Date Applied The most recent date for this license being applied to the Node.
Related Topics:
About Loading Device Software Via ProVision on page 221
Device Configuration Backup and Restore

ProVision automatically saves a configuration backup file every 12 hours for the fol-
lowing device types deployed in ProVision.
l Eclipse
l CTR 8300, 8540, and 8440 (see note)
l TRuepoint 5000
l WTM 3200 and 3300 (export only, restore is available from the craft tool)
l Symmetricom
l Accedian
NOTE : O ther devic es c an be bac ked up and r es tor ed fr om their

c r aft tools .
To do this, ProVision does the following:

l Detects whether configuration has changed by reading the last change time
from the devices.
l If change is detected, FTPs the configuration file to the backup location on the
ProVision server.
l Returns the last 5 copies of the configuration files onto the server.
l 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.
W AR NING : For TRuepoint 5000 devic es , to enable the Configur ation
Bac kup for eac h devic e, you mus t s et up the devic e s ec ur ity ac c ount in
the c r aft tool, then in Pr oVis ion us ing Dev ice Secu rit y Accou nt s. Onc e
the bac k up is c ollec ted you c an r es tor e the devic es .
240 AVIAT NETWORKS

W AR NING : CTR 8440 devic es c an have their c onfigur ation bac kup
s aved, but not r es tor ed. The c onfigur ation bac kup is done via the TFTP
s er ver w hic h c omes bundled w ith the Pr oVis ion Ser ver ins tallation.
The TFTP s er ver r uns on por t 69. Note that any exter nal TFTP s er ver s
s hould be s topped for the TFTP s er ver on Pr oVis ion to w or k.
Procedure
1. Select a 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:
l Preview - Displays a preview of the backup.
l Restore - Restore a selected backup file.
l 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
want to save the backup, and click Save.
614-330055-001 DECEMBER 2015 241

7. The backup file is saved to this location.

8. The backup file can be used to load the devices again, if required. Select the
backup file and click Restore.
242 AVIAT NETWORKS

Chapter 5. Carrier Ethernet

Management
Using ProVision, you can manage Carrier Ethernet devices. This includes viewing, pro-
visioning, and fault management.
ProVision provides Carrier Ethernet management for the following device types:
l Eclipse family devices with DAC GE3 or IDU GE3 (for VLAN and EOAM,
7.2.32 or later Eclipse firmware: for ERP provisioning, 7.3.32 or later Eclipse
firmware)
l CTR 8540 devices (requires 2.4 or later CTR 8540 firmware)
l VLAN and EOAM for CTR 8300 devices (requires 2.3 or later CTR 8300
firmware)

l VLAN Management on page 244
l Ethernet OAM Management on page 263
l ERP Ring Management on page 282
NOTE : Car r ier Ether net func tions r equir e featur e lic ens es - s ee Abou t
Licenses.
614-330055-001 DECEMBER 2015 243

CHAPTER 5. CARRIER ETHERNET MANAGEMENT
VLAN Management
This section describes how to use ProVision to perform VLAN management:
l Viewing discovered VLANs
l Viewing VLAN configuration details
l Identifying and resolving VLAN faults
l Configuring VLANs
l Creating a VLAN
l Modifying a VLAN
l Validating VLAN configuration
l Deleting a VLAN
ProVision provides VLAN management for the following device types:

l Eclipse family devices with DAC GE3 or IDU GE3 (requires 7.2.32 or later
Eclipse firmware)
This VLAN documentation includes the following sections:

l Overview of VLANs on page 244
l Viewing Discovered VLANs on page 245
l Viewing List of Discovered VLANS on page 246
l Viewing VLAN Configuration Details on page 247
l Viewing VLAN Topology on page 250
l Viewing VLANs in the Physical and Flat Maps on page
252
l Identifying and Resolving VLAN Faults on page 254
l Configuring VLANs on page 257
l Provisioning a New VLAN on page 257
l Modifying an Existing VLAN on page 261
l Deleting an Existing VLAN on page 262
Overview of VLANs
VLANs (Virtual LANs) are used to segregate users and/or services on a LAN (Local Area
Network) from other users/services on the same LAN. VLANs behave as if they were on a
separate LAN, even though they all share the same physical network and network
address.
What are the network benefits of VLANs?
244 AVIAT NETWORKS

l VLANs segment networks to provide improved security, workgroup

management and traffic control.
l VLANs also enable traffic prioritization to support Quality of Service (QoS)
needs. Where Ethernet bandwidth is restricted, traffic tagged as high priority
will transit a switched network ahead of lower priority or untagged traffic. This
is particularly relevant where VLANs are transported over a service-provider
network.
l VLANs can also be stacked to provide a demarcation between customer and
service provider networks. Multiple customer VLANs can be stacked on a
service-provider VLAN, with the service provider able to provide each with a
unique priority to support service level agreements (SLAs).
The VLAN traffic data is identified and separated by Ethernet frame tagging. Ethernet
frames ingressing a VLAN port have a VLAN tag inserted that includes the VLAN ID
and a priority/class setting. Switches within the network use the VLAN ID tag to main-
tain VLAN membership/segregation over common trunk links. VLANs are software-con-
figured; they are not constrained by the physical topology of a network.
For Eclipse, VLAN is enabled with the DAC GE3 card. In Eclipse Portal, VLANs are
established by grouping switch ports under a common VLAN membership identifier
(VLAN ID). Each VLAN uses a different VLAN ID. VLAN configuration sets VLAN tag-
ging and filtering, and selects and customizes cross-connections between user and net-
work ports. VLANs provide a means to manage all traffic within a DAC GE3 switch,
from switch port ingress to egress, and to establish VLANs for use beyond the switch.
NOTE : Pr oVis ion does not pr ovide VL AN pr ovis ioning of NCM por ts .
W AR NING : To enable VL AN view ing and management, Pr oVis ion mus t

be c onfigur ed as the SNMP manager tr ap des tination for the VL AN
Ec lips e devic es . With this c onfigur ation, Pr oVis ion r ec eives faults and
c onfigur ation c hange events fr om the VL ANs w ith minimal delay.
For more about VLANs, VLAN tagging, and VLAN types in Aviat Networks products, see
the Ethernet Operation chapter of the Eclipse Product Description.
Viewing Discovered VLANs

Using ProVision, it is fast and easy to view your network VLANs. ProVision auto-
matically discovers and displays all VLANs in the network in the VLAN Tab, including
the end-to-end topology for each VLAN. The VLAN Table provides a list of the dis-
covered VLANs. From the VLAN Tab, you can also view an end-to-end topology map or
the configuration details of a selected VLAN.
ProVision continually checks for new VLANS and VLAN configuration changes. VLAN
information is persisted in the database to retain VLAN view access during loss of com-
munication with managed devices.
To support VLAN end-to-end discovery, ProVision must identify the underlying Layer 1
network topology. This is enabled by ProVision’s automated discovery, coupled with the
614-330055-001 DECEMBER 2015 245

ability to manually deploy links (RF or Ethernet) where the network devices cannot
provide the management information.
To view VLANs, see these procedures:
l Viewing List of Discovered VLANS on page 246
l Viewing VLAN Configuration Details on page 247
l Viewing VLAN Topology on page 250
l Viewing VLANs in the Physical and Flat Maps on page 252
Viewing List of Discovered VLANS

This section describes how to view the list of discovered VLANs, including filtering for
specific list items.
Procedure
1. To view all VLANs, select the network object in the Tree Viewer. To view the
VLANs associated with a specific object (e.g. a region or a device), select the
specific object in the Tree Viewer.
2. Open the VLAN Tab. The automatically discovered VLANs display in the
VLAN table.
NOTE : Tr ans par ent member devic es of a VL AN ar e inc luded in the VL AN

as par t of the path betw een the main VL AN devic es .
3. By default, the VLAN table is filtered to list only the member ports (for each
VLAN) on the devices within the selected container object in the Tree View.
To extend the VLAN table to include all member ports for each VLAN, select
the Show All Member Ports checkbox.
4. To filter the list of VLANs, you can:
l Sort the VLAN table by clicking on table headers.
l Click on the Filter button to filter for specific text or numbers. You can filter for
VID and severity values: for example, entering "vid=200" will search for results
with a VID value of 200.
l Select an object in the Tree Viewer to view its VLAN items in the VLAN tab.
5. To export the list of VLANs, click the Export button at the bottom of the
VLAN table. You will be prompted to save the VLAN Table data as a .txt file.
VLAN Tab – VLAN Table View

In the VLAN table view, a single row of data displays for each VLAN.
246 AVIAT NETWORKS

NOTE : Dis c over ed VL ANs w ith the s ame VID ar e as s umed to be s ep-
ar ated s egments of the s ame VL AN due to either a c onfigur ation er r or or
a fault c ondition. Ther efor e, they ar e pr es ented as a s ingle entr y in the
VL AN table. Bec aus e a c us tomer may intentionally r eus e VIDs in phys -
ic ally s epar ated par ts of the netw or k, in a futur e r eleas e the option w ill
be pr ovided to s elec t w hether a VL AN in this s tate is ac tually s epar ate
VL ANs .
Table 5-1. VLAN Tab – VLAN Mode Table Definitions

Table Item Definition
Alarm Status Displays the highest active alarm severity for all alarms that are auto-
matically correlated to this VLAN. To see alarm levels, see Alarm Sever-
ity Color Coding on page 91.
VID VID identifier for the VLAN.
Name Name of the VLAN.
Members List of devices included in the VLAN.
Show Option to extend the VLAN Table to include all member ports for each
All member VLAN (i.e., the Members field is no longer filtered by the Tree View con-
Ports tainer selection). This also results in the VLAN Map displaying all
devices in the network with VLAN port membership.
EOAM
This icon indicates that EOAM monitoring is enabled for this
VLAN (i.e., an EOAM MA is configured.)
ERP
= This VLAN contains member ports that form a physical layer
ring.
= This is an ERP control VLAN, with an ERP ring applied.
Viewing VLAN Configuration Details

You can view the configuration details for a specific VLAN using the view Details option.
Procedure
1. Select the VLAN Tab. Select the VLAN in the VLAN table.
2. Click the Details button. The Details display below the table, with a tab of
details for VLAN, and for implemented EOAM and ERP applied to the
VLAN. Note: EOAM and ERP tabs only display if these are implemented. If
614-330055-001 DECEMBER 2015 247

EOAM or ERP are not present on the VLAN, EOAM or ERP tabs will not
display.
3. Click on each tab to view the Details. See the values described below.
4. In the VLAN tab, to view Switches, click the Switches button. To return to
viewing the Edge Ports, click the Edge Ports button.
VLAN Information
This tab presents the details of the selected VLAN.
Edge Ports view:
Switches view:
Details Item Definition

Port Types There are two tables here:
- Edge Ports - Devices on the "edge" of a network that do not con-
nect to other radios
- Network Ports - ports that link radios.
Device Device name. Read only.
Enabled Port state is enabled (checked) or disabled (blank).
248 AVIAT NETWORKS

Port Specified port. Read only.

Device For Network Ports only: the device that supports this VLAN. Second
Enabled and Port values are related to this device.
VLAN Members- All VLANs that include this specified port.
hip
Advanced
Bridge Port For Edge ports. For CTR devices only. Only Customer Bridge is sup-
Mode ported, but at this time Provider Bridge modes will display if they have
been configured via CLI.
Filtering For Edge ports. Enable or disable Filtering for incoming frames.
Trunk For Tagged ports. Enable or disable Trunking. Where available, Trunk
ports are tagged by default. NOTE: Either Filtering or Trunking can be
enabled: they cannot both be enabled.
Forbidden VIDs For all Tagged ports. Trunks are automatically included in any VLAN.
You can block or "forbid" them from being included in a specific VLAN
by entering the VID numbers here.
Priority For untagged Edge Ports.
EOAM Information
This tab presents the details for the EOAM MA associated with the selected VLAN. It
lists all EOAM MA/MEGs configured for the selected VLAN.

MA ID/ME ID Unique MA ID/ME ID defined on the VLAN.
Y1731 Type of service, noted as True (Y.1731) or False (802.1ag)
Level MD/MEG level, representing hierarchical levels of management.
VID VLAN ID for the service being monitored.
MEPs/Devices MEPs and devices with MIPs for this EOAM MA. Note that EOAMs can
have more than 2 MEPs.
Diagnostics
- Links to the EOAM Diagnostics view for this EOAM MA/ME
614-330055-001 DECEMBER 2015 249

ERP Information
This tab presents the details for the ERP rings associated with the selected VLAN. It
presents details for both the main ERP ring and for any ERP subrings.

Name Name of the ERP ring.
Members Devices and ports on the devices used for the ERP. For example,
INUe153 is the device name, and 7/2 indicates the slot and port
(respectively).
RPL Owner
Ring Protection Link Owner – device/port with this icon.
Subring
ERPS Subring - device/port with this icon.
RPL Owner on a
Subring RPL Owner on the Subring (invalid!) - The RPL owner is not
allowed on the subring component of an ERP ring.
Viewing VLAN Topology

With ProVision, you can view the end-to-end topology of a VLAN (Layer 2) correlated
with the physical (Layer 1) network topology. This is displayed as a filtered view of the
Flat Map, using the Flat Map coordinates for positioning each object.
250 AVIAT NETWORKS

Procedure
1. Open the VLAN Tab. Select the VLAN in the VLAN table.
2. Click the Map button. The topology displays in the map. See the map values
described below.
Table 5-2. VLAN Map Attributes

Map Item Definition
Show Option to extend the VLAN Table to include all member ports for each
All Member VLAN (i.e. the Members field is no longer filtered by the Tree View con-
Ports tainer selection). This also results in the VLAN Map displaying all devices
in the network with VLAN port membership.
Alarm Status Displays the alarm levels active for devices. To see alarm levels, see Alarm
Severity Color Coding on page 91.
Port Status
Port status is displayed in the boxes on the link lines.
tool tip
Hover over these for a tool tip that displays:
- Plug-Ins – Device and plug-in Ids for this port.
- Type – Network Port or User Port.
- Status – Enabled or Disabled status for linked ports.
- Alarm Status for the ports.
Edge Ports
Port names highlighted in purple are Edge Ports.
Network
Ports Port names highlighted in orange on links are Network Ports.
614-330055-001 DECEMBER 2015 251

Link or Con- - Black solid line – RF link. Mouse over for RF link details.
nector Status - Square on line– Ethernet link. Mouse over for DAC port link data for
this link branch.
- Looped dash line - Cable connect between two Ethernet plugins (DAC
GE3s).
Filter Displays a field for Filtering the VLAN table based on an alphanumeric
value: only items that include this value will display.
Export Click this to export and save the data as a .txt file.
Create Click this to create a new VLAN.
Viewing VLANs in the Physical and Flat Maps

You can view the configuration details for a specific VLAN in the main Physical Map or
Flat Map view, using the Map Mode – VLAN Mode. This is useful for viewing a selected
VLAN in the context of the larger network.
Procedure
1. Select the Physical or Flat Map. In the map functions, select Map Mode
and choose VLAN Mode.
2. The map display changes to include VLAN items in the upper and lower
right corners. To view the port information on the map, click the arrow
beside VLAN Mode in the map; a drop-down menu displays. You can select
port configurations to view, including:
l Active Ports = Admin enabled ports
l Edge Ports = VLAN terminating ports
252 AVIAT NETWORKS

l Network Ports = Network ports delivering the VLAN

3. To view a specific map, select the VLAN Mode Ports item. Then, select the
VLAN to be displayed from the list of discovered VLANs.
4. For the selected VLAN, the port VLAN map attributes display in the
Physical/Flat map view.
Table 5-3. VLAN Map Attributes for Physical/Flat Map

Map Item Definition
Alarm Status Displays the alarm levels active for this device. See Alarm Severity
Color Coding on page 91.
614-330055-001 DECEMBER 2015 253

Port Status Port status is displayed in the boxes on the link lines. Hover over
these for a tool tip that displays:
- Plug-Ins – Device and plug-in Ids for this port.
- Type – Network Port or Edge Port.
- Status – Enabled or Disabled status for linked ports.
- Alarm Status for the ports.
Edge Ports Port names highlighted in purple are Edge Ports.
Network Ports Port names highlighted in orange on links are Network Ports.
Link Status - Black solid line – RF link. Mouse over for RF link details.
- Square on line – Ethernet link. Mouse over for DAC port link
data for this link branch.
Identifying and Resolving VLAN Faults

This section describes how to use ProVision to identify, verify, isolate and resolve VLAN
faults.
ProVision detects faults in VLANS by automatically performing:
l VLAN configuration validation checks
l Ethernet OAM configuration validation checks
l Ethernet OAM continuity testing
l Correlation of reported events to the VLANs (e.g. a port down alarm is
associated with all VLANs on that specific port).
W AR NING : To r es olve VL AN c onfigur ation faults , you may need to be
able to make c hanges to devic es us ing the devic e c r aft tools , s uc h as
Ec lips e Por tal.
Procedure
1. Open the VLAN Tab. The VLAN Tab displays VLAN connections with faults.
To view these quickly, either:
l Sort the VLAN table by alarm status in descending order.
l View the VLAN map: device alarm status is shown on each device.
254 AVIAT NETWORKS

2. Review the faults for a specific VLAN by right-clicking it in the VLAN Table
and selecting Event Browser. The Event Browser displays all the faults for
the VLAN.
3. You can also view the faults for an EOAM MA by viewing it in the EOAM
tab. Hovering over the errored EOAM MA opens a pop-up with the fault
details.
614-330055-001 DECEMBER 2015 255

4. To isolate this fault and identify its cause, use the VLAN management
features in ProVision:
l Check that there are no physical connection (RF or Ethernet) faults by
inspecting the connections between the nodes using either the VLAN Map or
EOAM Map (where EOAM monitoring has been enabled).
l Where EAOM monitoring has been enabled on the VLAN, use the EOAM
diagnostics identified in section Identifying and Resolving EOAM
Configuration Faults on page 270 to help with diagnosing EOAM MA
continuity faults.
l Inspect the configuration of the VLAN using the VLAN Table, VLAN Details
and VLAN Map identified in this section. See Viewing Discovered VLANs on
page 245.
l Check whether there are packet loss or error problems on the associated ports
or queues that deliver the VLAN using the Ethernet performance feature. See
Ethernet Bandwidth Utilization on page 399.
4. The VLAN Fault Table below lists the most common VLAN faults and
provides resolution actions. For other alarms, see the Alarms Appendix.
Table 5-4. Common VLAN Faults

Alarm Names Cause Resolution Action
Channel X MEP An OAM link or configuration error has - Resolve the link error, or correct the
defect or Port X occurred due to one or more of the fol- configuration. Use ProVision EOAM
MEP defect lowing defects: diagnostics and validation to resolve
- RDI this.
- Remote interface down - Note that the link error, or con-
- No CCM figuration error could be in the local
- Invalid CCM node, the remote node that has the
- Xcon CCM peer MEP defined, or any node in
- Unexpected period - Y1731 mode only between.
- Unexpected MEP - Y1731 mode only
- Mismerge - Y1731 mode only
- Unexpected MEG level - Y1731 mode
only
- Local link failure - Y1731 mode only
- Internal HW failure - Y1731 mode only
- Internal SW failure - Y1731 mode only
- AIS condition - Y1731 mode only
- LCK condition -Y1731 mode only
Ethernet Down The Ethernet port or TC link is down. - Check VLAN connection port cables.
- Check for related alarms on the con-
nected equipment.
- Check the circuit configuration (Cir-
cuits screen).
- Withdraw the DAC GE3 card, pause,
then reinsert. If the alarm persists,
replace the card.
Plug-in initializing The plug-in is still initializing. - Check plug-in presence and con-
nections. Review the device for
alarms.
256 AVIAT NETWORKS

Alarm Names Cause Resolution Action

Port X DPP link The end-end Ethernet link is down due to a - Check local and remote DPP cable
down problem with the DPP cable. connections.
Port X excessive One or more of the VLAN links are down, - If the port/channel is included in a
out of frame drop resulting in traffic congestion on the link aggregation group, check to see if
remaining link(s). it is as a consequence of the failure of
a partner link.
- Check port/channel traffic loading
using the Performance screen.
- Determine if the dropping is an isol-
ated instance or becoming more fre-
quent. If the later, review the
connection design parameters.
Port X SFP missing The SFP is missing from an enabled SFP - Insert the relevant SFP module.
port (P4, P5). The SFP module has not been
installed or has been withdrawn.
Unable to read ProVision cannot read the port information - Check the NMS connectivity to the
port information over SNMP. device, including the MTU (maximum
transmission unit) size.
- Exclude virus scanner from ProVi-
sionServer\mysql\data\tmp directory
Configuring VLANs
This section describes how to configure VLANs. It also describes how to validate that
configuration changes have been applied correctly to VLANs.
See these procedures:
l Provisioning a New VLAN on page 257
l Modifying an Existing VLAN on page 261
l Deleting an Existing VLAN on page 262
Note the following:
l When provisioning a new VLAN, consider whether Ethernet OAM monitoring
of the VLAN service is required. This provides a higher level of service
assurance, resulting in a higher quality VLAN service. See Ethernet OAM
Management on page 263.
Provisioning a New VLAN

In ProVision, users can create and launch new VLAN provisioning from within the ProVi-
sion software. This is available for for Eclipse, CTR 8540, and CTR 8300.
Procedure
1. To open the VLAN Provisioning screen, you have four options:
614-330055-001 DECEMBER 2015 257

l In the VLAN tab, click the Create button.

l In the main menu, open Configuration - Provisioning - VLAN.
l Select devices in the Map view, right-click them, and choose Configuration -
Add to VLAN.
l In the Tree View or Map view, select the items or ports and right-click, and
select Configuration - VLAN Provisioning. Select one or more ports from the
display. Then, click Provision.
2. The VLAN Provisioning screen displays.
258 AVIAT NETWORKS

3. You can review or enable specific VLAN configuration values. These are:
For the overall VLAN:
l VLAN type- Either VID, with VID value, Name, and Transparent, or Trunk .
For Edge Ports and Network Ports:

l Device - Device name. Read only.
l Enabled - Port state is enabled (checked) or disabled (blank).
l Port - Specified port. Read only.
l VLAN Membership - All VLANs that include this specified port.
NOTE : Edge Por ts ar e devic es on the " edge" of a netw or k that do not
c onnec t to other r adios . Netw or k Por ts ar e por ts linking r adios .
5. Click Advanced to set up the following VLAN configuration values for Edge
Ports and Network Ports. First, select whether the ports are Tagged or
Untagged, using the check box to enable Tagged status. Then, set the values:
l Priority - For untagged Edge ports. The priority value (0 - 7) assigned to
untagged frames.
l Bridge Port Mode - For Edge ports. For CTR devices only. Only
Customer Bridge is supported, but at this time Provider Bridge modes will
display if they have been configured via CLI.
l Filtering - For Edge ports. Enable or disable Filtering for incoming frames.
Display only, not supported for this release.
l Trunk - For Tagged ports. Enable or disable Trunking. Where available, Trunk
ports are tagged by default. NOTE: a) Filtering or Trunking can be enabled:
they cannot both be enabled. b) You cannot unset a trunk from here. If you no
longer want a port to be a Trunk, select the trunk VLAN and remove the port
from that VLAN.
614-330055-001 DECEMBER 2015 259

l Forbidden VIDs - Trunks are automatically included in all VLANs. One

example of the use of forbidden VIDs is blocking or "forbidding" them from
being included in a specific VLAN by entering the VID numbers here. Note that
forbidden VIDs are also applicable to non-trunk ports.
6. To review available switches, click the Switches button. VLAN modification,
whether adding a new VLAN or modifying a VLAN or deletion of a VLAN,
applies to only the switches listed here. Users can add additional switches or
remove the displayed ones. A switch is automatically added when any port
for that switch is added.
NOTE : All por ts under a s w itc h ar e vis ible to eac h otehr . Ec lips e is not
c ons ider ed a s w itc h bec aus e por ts on one DAC GE3 ar e not vis ible to
another DAC G E3. For Ec lips e devic es , Sw itc hes ar e DAC GE3 modules .
6. The Switches view displays, with a read-0nly display of the Switches linked
to this VLAN provisioning.
7. You can also add additional ports by dragging and dropping them from the
Tree viewer. Note that a message displays if a selected port cannot be
dropped: see the highlight in this screen sample, where Port 1 is being
dragged and dropped and a message is displaying.
260 AVIAT NETWORKS

W AR NING : If a s etting is inc or r ec t or c aus es a VL AN pr oblem, this

er r or ic on dis plays next to the s etting: You c an only c ommit a
VL AN after r es olving all er r or s .
8. When you have entered all your required settings, click Commit Changes. A
progress window displays and confirms when the provisioning is complete.
For CTR devices, see Saving Carrier Ethernet Configuration for CTR Devices
on page 1.
9. Use ProVision to validate the new VLAN has been correctly provisioned:
l Check that the new VLAN displays in the VLAN table. Click the Details button
to verify the VLAN details. See section Viewing VLAN Configuration Details
on page 247 .
l Click the Map button to verify the VLAN topology. See section Viewing VLAN
Topology on page 250.
l Check that the alarm status field in the VLAN table indicates that no alarms
are active. Where alarms are active, follow the procedure in Viewing VLANs in
the Physical and Flat Maps on page 252 to resolve the fault(s).
10. Use ProVision to configure Ethernet OAM monitoring of the new VLAN
service by applying EOAM Provisioning, see Provisioning a New EOAM MA
on page 275
Modifying an Existing VLAN

The procedure for modifying an existing VLAN is the same as the provisioning pro-
cedure in the section Provisioning a New VLAN on page 257.
614-330055-001 DECEMBER 2015 261

Select the VLAN, right-click it, and select Edit.
NOTE : Pr oVis ion w ill not allow you to make c hanges to a Management
VL AN.
Deleting an Existing VLAN

ProVision can be used to ensure that a VLAN is correctly deleted from the configuration
of all devices.
NOTE : You c annot delete a Management VL AN or a VL AN w ith EOAM or

ERP enabled. Delete the EO AM and ERP befor e you delete the VL AN.
Procedure
1. In ProVision, select the network or container object that contains the VLANs.
Then, open the VLAN tab. In the VLAN table, right-click on the VLAN and
select Delete.
2. Check that the VLAN is no longer displayed in the VLAN table.
NOTE : See the CTR Portal ProVision manual and the CTR 8 5 4 0 CLI Refer-
ence Manual for CTR 8540 ins tr uc tions .
262 AVIAT NETWORKS

Ethernet OAM Management

ProVision provides Ethernet OAM (EOAM) management. This section describes how to
use ProVision’s EOAM functions for:
l Viewing discovered EOAM Maintenance Associations (MAs)
l Viewing MA configuration details
l Configuring EOAM to provide fault monitoring of VLANs (Eclipse only)
l Validating EOAM configuration
ProVision provides EOAM management for the following device types:
Eclipse firmware)
Limitations:
l EOAM Up/In MEP configuration is not supported by CTR 2.3 and 2.4
software.
l EOAM Y.1731 MA in Eclipse 8.0 is not compatible with CTR. An Eclipse fix is
planned for a later 8.0 software release.
The following sections are provided:
l Overview of Ethernet OAM on page 264
l Viewing Discovered EOAM MAs on page 265
l Viewing List Of Discovered EOAM MAs on page 266
l Viewing EOAM MA Logical Topology on page 267
l Viewing EOAM MA Physical Topology on page 269
l Identifying and Resolving EOAM Configuration Faults on page 270
l Configuring Ethernet OAM on page 275
l Provisioning a New EOAM MA on page 275
l Modifying an EOAM MA on page 280
l Deleting an EOAM MA on page 280
See also the section Identifying and Resolving VLAN Faults on page 254 for troubleshoot-
ing VLANs with EOAM.
NOTE : Impo rt ant : To enable EO AM management, Pr oVis ion mus t be

c onfigur ed as the SNMP manager tr ap des tination. With this c on-
figur ation, Pr oVis ion r ec eives faults and c onfigur ation c hange events
fr om the EO AM entities w ith minimal delay.
614-330055-001 DECEMBER 2015 263

Overview of Ethernet OAM

Ethernet OAM (Operation, Administration, and Maintenance) is a set of Ethernet sup-
port functions enabling:
l Detection and resolution of VLAN service faults
l Measurement of VLAN service performance
NOTE : This func tion is enabled fr om Ec lips e ver s ion 7. 2. 32 onw ar ds ,

and CTR 8540 ver s ion 2. 4.
Unlike TDM circuits, Ethernet services are virtual in nature and can be dynamic. Eth-
ernet OAM is needed to ensure Ethernet service quality and availability are predictable
and in line with what was provisioned / subscribed. When data is being transmitted
with Ethernet packet-switched network OAM protocols active, designated OAM PDUs
(frames) are sent alongside user traffic.
Several standards have been developed that support Ethernet OAM at different layers.
Service OAM addresses end-to-end Ethernet connectivity fault management (CFM) and
in future performance monitoring (PM), as defined within IEEE 802.1ag, and ITU-T
Y.1731. Note that:
l 802.1ag and Y.1731 specifications overlap/converge on CFM.
l PM is only defined in Y.1731. (Note: PM is not supported in the current
ProVision product)
l Connectivity & Fault Management (CFM):
l Provides proactive continuity monitoring to identify
problems.
l Provides rapid fault verification and isolation.
l Refers problems to the responsible maintenance entity.
l Performance Monitoring (PM):
l Supports service level agreements (SLA) through
meaningful reporting of:
l Frame loss
l Frame delay
l Frame delay variation
l Provides proactive performance monitoring for maximum
service reliability
For Eclipse, CFM is enabled with the DAC GE3 card. Local and remote maintenance end
points (MEP) must be configured, and, optionally, the maintenance intermediate points
(MIP). In ProVision, the EOAM Provisioning feature configures CFM maintenance asso-
ciations. See Provisioning a New EOAM MA on page 275.
NOTE : EO AM per for manc e monitor ing is not available in this r eleas e of
Pr oVis ion.
264 AVIAT NETWORKS

Ethernet OAM Acronyms

Base acronym definitions for EOAM are:
l EOAM = Ethernet Operations, Administration and Maintenance.
l MA (MEG) = One or more MEs on the same service level, belonging to the
same service VLAN. Sometimes simplified to MA, as in this section.
l MEP = Maintenance Entity End Point, the end points of a ME. The connection
points (ports) that initiate EOAM messages.
l MIP = Maintenance Entity Intermediate Point, a connection point (port)
between two MEPs in a ME that relays and responds to some EOAM
messages. MIPs are not explicitly configured as part of a MA.
ProVision presents both IEEE 802.1ag and ITU-T Y.1731 EOAM terminology. The fol-
lowing table presents the equivalent terms:
IEEE 802.1ag ITU-T Y.1731
No equivalent Maintenance Entity (ME)
Maintenance Association (MA) Maintenance Entity Group (MEG)
MA Identifier (MAID) MEG Identifier (MEG ID)
Maintenance Domain (MD) No equivalent
MD Level MEG Level
MA End Point (MEP) MEG End Point (MEP)
MA Intermediate Point (MIP) MEG Intermediate Point (MIP)
Viewing Discovered EOAM MAs

ProVision makes it simple to visualize your network services and the route / path they
are currently taking across the network. ProVision automatically discovers and displays
all EOAM monitored VLAN services in the network in the EOAM Tab, including auto-
matically and proactively tracing the end-to-end route of dynamic services. The EOAM
Table provides a list of the discovered Maintenance Associations (MA), either 802.1ag
MA or Y.1731 MEG / ME. From the EOAM Tab you can also view logical representation
of the ports in the end-to-end topology of each MA, or view the same MA overlaid on
your physical network flat-map. For each MA you can choose to launch diagnostics to
perform manual link-trace or loop-back tests.
ProVision continually checks for new EOAM MAs and topology changes that affect the
routing of existing MAs, and automatically performs end-to-end link trace tests (in both
directions) to validate connectivity and (in the case of a fault) to isolate faults to a port.
EOAM information is persisted in the database to retain EOAM view access during loss
of communication with managed devices.
To support VLAN end-to-end discovery, ProVision must identify the underlying Layer 1
network topology. This is enabled by ProVision’s automated discovery, coupled with the
ability to manually deploy links (RF or Ethernet) where the network devices cannot
provide the management information.
See these topics:
614-330055-001 DECEMBER 2015 265

l Viewing List Of Discovered EOAM MAs on page 266

l Viewing EOAM MA Logical Topology on page 267
l Viewing EOAM MA Physical Topology on page 269
Viewing List Of Discovered EOAM MAs

It is easy to view and filter EOAM MAs in ProVision. The EOAM tab displays the MA
Table, which is the list of MAs/MEGs that originate/terminate on the devices/objects
selected through the tree view or match the selected filter on the EOAM table.
For a multipoint VLAN service, an associated multipoint MA/MEG is displayed as a set
of entries, one entry for each point-to-point MA/ME.
The set will have common MA/MEG ID name, MD / MEG Level and VID
values. Problem services can be identified quickly through sorting the Alarm status
column.
Procedure
1. In the main ProVision interface, click on the EOAM Tab.
2. The EOAM Tab displays, with the EOAM Services table.
3. To filter the list of EOAMs, you can:

l Sort the table by clicking on table headers.
l Click on the Filter button to filter for specific text or numbers.
l Enter a text filter into the Selected Object field.
Table 5-5. EOAM Services Table
Function or
Definition
Acronym
MA/MEG Attributes
Alarm Status Displays the highest active alarm severity for all alarms that are auto-
matically correlated to this VLAN. To see alarm levels, see Alarm Sever-
ity Color Coding on page 91.
Validation Status Configuration validation status:
- Present, passed validation
- Linktrace continuity failure
- Faulty
266 AVIAT NETWORKS

Type Indicates whether the EOAM service is an 802.1ag MA or Y.1731 MEG.

MA ID/ME ID MA ID or ME ID.
Level MD/MEG level, representing hierarchical levels of management.
VID VLAN ID for the service being monitored.
Start MEP Start MEP for the MA/MEG.
End MEP End MEP for the MA/MEG.
Size Total number of MEPs plus MIPs in the MA/MEG.
Filter Filter the EOAM devices based on a specific value.
Export Export the displayed EOAM data as a .txt file. You can use Filter to
select specific data before you do this.
Map Opens the Map View.
Details Displays or closes the topology inspection view.
Viewing EOAM MA Logical Topology

With ProVision, you can view the end-to-end logical topology of a MA/MEG, including
ports on managed equipment and ports on unmanaged or third-party equipment.
Procedure
2. The EOAM Tab displays, with the EOAM Table.
3. Select an EOAM row in the table. To view its logical topology, click Details.
4. The Details view displays. See the table below for Details view values.
l On mousing over a Details item, a pop-up note indicates the path, type, IP
address, state, and event count.
l On mousing over the port for the item, a pop-up node indicates the port,
MEP, MAC address, path, type, and event count.
614-330055-001 DECEMBER 2015 267

An example of a continuity failure is shown above. See Identifying and Resolving EOAM
Configuration Faults on page 270 for recommended actions to resolve identified prob-
lems.
Third party devices are also displayed in the EOAM Details view. Where a 3rd party
device is not managed in ProVision, a linktrace operation initiated from a managed
device can reveal the MAC address and status of unmanaged devices that have been con-
figured with either a MEP or MIP on the MA/MEG being traced.
Table 5-6. EOAM Details View
Detail Item Definition

Connection topology MEP end points and intermediate MIPs.
in view
Device Name Device name linked to each MEP/MIP, shown in lower left of
each Details item.
Type Device type, shown in all mouseovers.
Path Device location path, shown in all mouseovers.
State Managed or Unmanaged, shown in device mouseovers.
Active Event Count Active event count for each severity level, shown in all
mouseovers.
Port Associated device plug-in for each MEP/MIP, shown on port
mouseover.
MEP Down (out) or Up (inwards), shown on port mouseover.
MAC Address Port MAC address for each MEP/MIP, shown on port mouseover.
NOTE : If the EO AM inc ludes a tr unked link, the link dis plays as s how n:
268 AVIAT NETWORKS

Viewing EOAM MA Physical Topology

With ProVision, you can view the end-to-end topology of a MA/MEG (Layer 2) cor-
related with the Ethernet and RF (Layer 1) network topology. This is displayed as a
filtered view of the Flat Map, using the Flat Map coordinates for positioning each linked
Eclipse device.
Procedure
2. The EOAM Tab displays, with the EOAM Services Table.
3. Select an EOAM row in the table. To view its physical topology, click Map.
4. The EOAM Map view displays for the selected MA/MEG. See the table below
for map attributes.
5. You can right-click on devices to open the full right-click menu, including
access to the craft tool for the device.
Table 5-7. EOAM Map Attributes
614-330055-001 DECEMBER 2015 269

Map Item Definition

Device Icons Mouse over for device status, including assigned EOAM path,
type, state, and alarms. To see alarm levels, see Alarm Severity
Color Coding on page 91
Solid Line – Physical This line is coloured to indicated the highest active severity of the
RF/Ethernet Link RF link related alarm conditions. A tooltip is provided to indicate
the RF link endpoints and status.
Dotted Line – Phys- Physical Ethernet connection (e.g. cable). This line is coloured to
ical Ethernet Con- indicate the highest active severity of the Ethernet port alarm
nection conditions. A tooltip is provided to indicate path details.
Dotted Line – EOAM This can span either a single hop or multiple hops. Black indic-
MA end-to-end Con- ates there is layer 2 connectivity between the devices. Red with
nection Topology an “X” indicates a layer 2 connectivity (continuity) fault. A tooltip
is provided to indicate path details.
Identifying and Resolving EOAM Configuration

Faults
In the Ethernet OAM Diagnostics screen, users can apply Loopback and Link Trace oper-
ations to the selected Maintenance Association (MA).
If the MA has continuity problems, select the device/object adjacent to the point of fail-
ure. Then, use the right-click menu to launch the craft tool to resolve the configuration
problem. See the EOAM Fault Table in this section for probable cause and recommended
actions to resolve identified problems.
Procedure
2. In the EOAM Services table, select the EOAM link to analyze. Right-click on
the link and select Diagnostics.
3. The EOAM Diagnostics screen displays.
270 AVIAT NETWORKS

4. Select whether you are going to analyze the Loopback or the Link Trace. Go
to the Operation item and choose either Loopback or Link Trace.
5. To analyze Loopback :
l Select the Initiator and Target: MEP or MIP.
l For a trunk, you can select the specific MAC address from the Target drop-
down menu:
l Set the Number of Messages. For a MA configured using 802.1, the maximum
message count is 1024. For a MA configured using Y.1731, the maximum
message count is 8192.
l Set the VLAN Priority.
l Click Apply.
6. The Diagnostic is run. The Results tab displays whether the Loopback is a
SUCCESS or a FAILURE, as shown below. Possible problems may include:
l Radio not responding or loopback not supported for this radio
l Device deleted (may display if a device is deleted immediately before
614-330055-001 DECEMBER 2015 271

diagnostics)
l A loopback is currently running for this MEP
7. To analyze Link Trace:

l Select the Initiator and Target MEP or MIP.
l Set the Time to Live (hops) or the maximum number of maintenance points
(EOAM ports) to transverse.
l For a Y.1731-based Maintenance Association there are two additional options
that can be set: Timeout (seconds) and VLAN Priority.
l For a trunk, you can select the specific MAC address from the Target drop-
down menu:
l Click Apply.
8. The Diagnostic is run. The Results tab displays whether the Link Trace is a
SUCCESS or a FAILURE, as shown below. Possible problems may include:
l Another Link Trace is currently running on this DAC
l Acquiring lock (Another linktrace is running, will try again)
272 AVIAT NETWORKS

l Device deleted (may display if a device is deleted immediately before

diagnostics)
l Link Trace has time out. Radio not responding
l Target not found (linktrace runs but Target does not respond)
l EOAM linkTrace disabled (server_configuration.xml has eoam linkTrace
value set to false)
9. Resolve the fault with the recommended resolution actions, listed in the
EOAM Fault table below.
EOAM Fault Table

Alarm or Problem Probable Cause and Recommended Action
Linktrace failure using manual diagnostics Manual linktrace operation results in a failure, due to a
network problem or configuration issue.
Actions:
- Run the linktrace again in the opposite direction to
confirm where the falure is occurring.
Check for invalid configuration changes or physical net-
work issues.
Loopback failure using manual diagnostics Manual loopback operation results in a failure, due to a
network problem or configuration issue.
Actions:
- Run the loopback again in the opposite direction to
confirm where the failure is occurring.
- Check for invalid configuration changes or physical
network issues.
614-330055-001 DECEMBER 2015 273

No Results returned for Automatic linktrace can not be performed, due to MEP
EOAM Link Trace alarm defects on a related port.
Actions:
- Fix the MEP defect (see above).
- May be due to radio timeout, so run again.
MA name (primary VID) does not match the Actions:
primary VLAN ID - Change the MA name(Primary VID) to match the
Primary VLAN ID.
ME of MEP CCI is not enabled Actions:
- Go to Portal for this device and select "CCM
Enabled" on the MEP.
MEP CCI is not enabled Actions:
Enabled" on the MEP.
ME "ME name" CCI is not enabled Actions:
Enabled" on the ME.
MEP directions are different Actions:
- Change all the MEPs in this MA to be either
Down/out or Up/in.
MEP ID of MEP appears more than once for You are not allowed to have MEPs in an MA/ME with
this MA/ME the same ID.
Actions:
- Ensure that all the MEP IDs in this MA/ME are
unique.
MEP VID does not match the MA/ME VID Actions:
- Either make the MEP VID the same as the MA /
ME VID or change the MEP VIDto 0.
Port is not a member of VLAN VID Actions:
- Add the port to the VLAN.
Port X MEP defect alarm A MEP defect has been detected on the specified port,
due to a network problem or configuration issue.
Actions:
- Perform a manual link trace and/or loopback to con-
firm the issue.
- Check for configuration changes.
Red arrows shown in EOAM inspection or dia- Automatic linktrace has failed to trace in one or both
gnostic view directions end-to-end from MEP to MEP.
The red arrow indicates the part of the maintenance
association that has failed to return a linktrace
response, due to a network problem or configuration
issue.
Actions:
- Perform a manual link trace and/or loopback to con-
firm the issue.
- Check for invalid configuration changes or physical
network issues.
VLAN VID does not exist Actions:
- Either create The "VID" VLAN on all devices or
change the VID on the MA/ME to one that exists on
all radios.
274 AVIAT NETWORKS

Configuring Ethernet OAM

This section describes how to configure Ethernet EOAM monitoring of VLANs from
ProVision. It also describes how to validate that configuration changes have been
applied correctly to EOAMs.
These functions are supported for:
Eclipse firmware)
l Provisioning a New EOAM MA on page 275
l Modifying an EOAM MA on page 280
l Deleting an EOAM MA on page 280
NOTE : Pr ovis ioning of EO AM MAs s panning CTR and Ec lips e devic es is

not yet s uppor ted fr om Pr oVis ion due to a limitation in the Ec lips e s oft-
w ar e. This als o impac ts the ability to pr ovis ion ERP r ings s panning CTR
and Ec lips e. The limitation w ill be addr es s ed in later Ec lips e and Pr oVi-
s ion s oftw ar e r eleas es . Inter op r equir es the L egac y Mode tic kbox on the
Ec lips e Por tal O AM s c r een to be untic ked, and the as s oc iated c on-
figur ation objec t is not yet ac c es s ible to Pr oVis ion thr ough the Ec lips e
SNMP management inter fac e.
Provisioning a New EOAM MA

ProVision includes fast Ethernet OAM provisioning for Eclipse, CTR 8540, and CTR
8300. Configuring devices in isolation can lead to errors and poor configurations. The
ProVision EOAM provisioning simplifies this complex task with one screen, accessed
from the VLAN tab. You can use this screen to configure or provision new MAs, or to
edit existing MAs.
To provision an MA/MEG for a multipoint service VLAN, point-to-point MA/ME needs
to be deployed individually using the same VID, MA/MEG ID name and MD / MEG
Level.
EOAM Provisioning Prerequisites

l The VLANs to be monitored through EOAM must already be configured on the
Eclipse DAC GE 3 cards. For more information, see Provisioning a New VLAN
on page 257
614-330055-001 DECEMBER 2015 275

l You will need your configuration information: which devices and which
specific ports will be connected. You will also need configuration details
including type (Y.1731 or 802.1ag), names, directions, etc.
Procedure
1. Select the VLAN tab. VLAN items with EOAM already provisioned show this
icon; .
2. To create a new EOAM, right-click on any VLAN and select EOAM -
Provisioning. Select the device/object.
Or, to edit an existing EOAM, select it from the drop down menu, or go to the EOAM
tab, right-click on the EOAM, and select Edit.
3. The EOAM Provisioning screen displays. Note that it shows the VID from
the VLAN's details in the VLAN tab.
4. If the remote end point MEP is not on a device being managed by ProVision
(e.g., an unsupported third party device type), select Unmanaged Remote
End Point, requiring the user to only enter the remote end MEP number.
5. Select the device/object and interface/port for Object B. This will be the
second half of the provisioned MA. NOTE: When changing a MA (edit) the
Object A and Object B fields cannot be edited. If you need to change the end
points, delete this MA and add a new one.
276 AVIAT NETWORKS

6. You can set up specific MA/ME configuration options. For Y.1731, these are:
l Mode - Y.1731
l MD/MEG Level
l Direction
l ME ID: ICC - The ITU Carrier Code (ICC) is a unique code assigned to a
network operator or service provider by the ITU. It is 1-6 characters,
alphabetic, or leading alphabetic with trailing numeric.
l ME ID: UMC - The Unique MEG ID Code (UMC) is assigned by the network
operator or service provider, and needs to be unique within that organisation’s
domain. It is 6 characters. The user enters up to the first 4 characters.
7. For 802.1, the options are:

l Mode - 802.1
l MD Name - Options include String, Primary VID, Unsigned Integer, RFC 2865
VPN ID
l MD/MEG Level
l Direction
l MA Name - Options include String, Primary VID, Unsigned Integer, RFC 2865
VPN ID
614-330055-001 DECEMBER 2015 277

8. If required, you can set up Advanced configuration options. Click Advanced

to view these. The options include:
l MIPs – Add devices that should be configured to act as Maintenance
Intermediate Points.
l MIP Creation - Select the MIP creation type:
l None = No MIP will be created for the end points at a
higher MD / MEG level.
l Default = MIPs can be created in selected intermediate
nodes, regardless of whether a MEP exists at those nodes
for a lower MD / MEG level. Requires one or more nodes
to be selected for MIPs.
l Explicit = MIPs can be created in selected intermediate
nodes if a MEP exists at those nodes with a lower MD /
MEG level. Requires one or more nodes to be selected for
MIPs.
l CCM Interval – Select an interval from 100ms to 10 minutes.
l CCM Priority - Select number value between 0 and 7, where 7 is the highest
priority (Y.1731 mode only).
278 AVIAT NETWORKS

9. When you have entered all your required settings, click Commit Changes. A
progress window displays and confirms when the provisioning is complete.
10. You can now provision further EOAM maintenance associations for VLAN
items.
11. To validate that the EOAM MA is successfully provisioned:
l Check the alarm status of the devices in the EOAM.
l Run Diagnostics on the EOAM MA/ME. See Identifying and Resolving EOAM
Configuration Faults on page 270.
NOTE : For CTR devic es pr ovis ioned via the Pr oVis ion s oftar e, the pr o-
c es s is c omplete. Note that if EO AM is pr ovis ioned for a CTR devic e via
CL I c ommands , the EOAM notific ation mus t be s et via CL I as w ell: the
c ommand is :
snmp-server enable notifications ethernet cfm all
614-330055-001 DECEMBER 2015 279

Modifying an EOAM MA
The procedure for modifying an existing EOAM is the same as the provisioning pro-
cedure in the section Provisioning a New EOAM MA on page 275.
For an existing MA/MEG, the following settings can be edited. The MA/MEG must be
deleted and recreated in order to change other settings.
l Mode (802.1ag or Y.1731)
l ICC and UMC (Y.1731)
l Addition of new MIPs
l CCM Interval
l CCM Priority (Y.1731)
Deleting an EOAM MA
From ProVision, you can delete an EOAM MA that is in the EOAM Services Table.
W AR NING : You c annot delete EO AMs inc luded in an ERP r ing fr om
Pr oVis ion. Delete the ERP r ing fir s t if this is r equir ed: s ee Delet ing an
ERP Ring on p age 29 2.
W AR NING : You c annot delete individual MEP-to-MEP point-to-point

s egments of an MA/MEG as s oc iated w ith a multipoint s er vic e VL AN.
When s elec ting to delete one of the MA/MEG entr ies in the EOAM
Table, you ar e pr ompted w hether to delete all MA/MEG s egments (i. e.
the c omplete multipoint MA/MEG). O n c onfir mation, all the MA/MEG
s egments ar e deleted in a s ingle tr ans ac tion.
Procedure
2. The EOAM Tab displays, with the EOAM Services Table.
3. Select an EOAM row in the table. To delete it, right-click it and select
Delete.
4. A message displays, asking you to confirm the deletion. If you are certain,
click Yes.
5. The EOAM is deleted from the devices and the network. (For CTR devices,
see Saving Carrier Ethernet Configuration for CTR Devices on page 1.)
6. To confirm that the MA is deleted:
280 AVIAT NETWORKS

l Check the VLAN Details view to ensure that the EOAM no longer displays in
association with a VLAN.
l Check the EOAM Tab to ensure that the EOAM MA/ME no longer displays.
614-330055-001 DECEMBER 2015 281

ERP Ring Management

This section describes how to use ProVision to perform the following ERP operations:
l Viewing discovered network rings (Layer 1 and ERP rings)
l Viewing ring configuration details
l Configuring ERP rings
l Creating an ERP ring
l Modifying an ERP ring
l Deleting an ERP ring
l Validating ERP ring configuration
ProVision provides ERP ring management for the following device types:
l Eclipse family devices with DAC GE3 or IDU GE3 (for ERP provisioning, this
requires 7.3.32 or later Eclipse firmware).
Limitations:
l EOAM Up/In MEP configuration is not supported by CTR 2.3 and 2.4
software, preventing ERP subrings from being configured.
l EOAM 802.1ag based ERP rings are not supported by CTR 2.3 and 2.4
software.
The following sections are provided:
l Overview of ERP on page 282
l Viewing Discovered ERP Rings and Ring Configuration on page 283
l Viewing ERP Ring Configuration Details on page 285
l Configuring an ERP Ring on page 286
l Provisioning a New ERP Ring on page 286
l Provisioning an ERP Subring on page 290
l Modifying an ERP Ring on page 292
l Deleting an ERP Ring on page 292
Overview of ERP
Ethernet Ring Protection (ERP), also known as Ethernet Ring Protection Switching
(ERPS) ITU-T G.8032 / Y.1344, is a form of network protection that enables Carrier-
Grade Ethernet services and performance by providing fast recovery from failure (sub
50ms) and removing loops in layer 2 networks.
282 AVIAT NETWORKS

ProVision provides ERP management for the following device types:

Eclipse firmware)
What is Network Protection?

Network protection uses the topology of the network to provide alternate paths to reach
a final destination. Normally, only one path is used at a time and the other paths are
either blocked or kept in a standby mode. In the event of failure or congestion the net-
work protection protocol re-routes the affected traffic through the next best alternate
path. The most common network topology to provide protection is ring topology but in
the data world mesh topology is also very popular.
ERP
The main purpose of ERP is to provide fast recovery from failure (sub 50ms) and remove
loops in layer-2 networks. ERP eliminates the loops in the network by selecting a Ring
Protection Link (RPL), a Ring Protection Link Owner (RPL), and a protocol that allows
it to indicate and react to failures on the other nodes or links in the ring. With ERP con-
figured, under normal conditions the RPL is blocked. When a link failure is detected the
RPL is unblocked, healing the ring. ERP rings can be revertive or non-revertive.
l G.8032 uses standard Carrier Ethernet technology:
l 802.1 MAC address learning, forwarding and FDB
flushing functions
l 802.1q VLAN tagging
l Y.1731 EOAM MA/MEGs using CCMs to detect failure
l Depending on the CCM interval the topology reconvergence can be achieved in
less than 50 ms
l Other failure detection mechanisms (normally at the physical layer) can be
used to expedite the failure recovery.
l Two versions of the protocol are supported at this time G.8031v1 and
G.8032v2. Both use Ring Automatic Protection Switching PDUs (R-APS) to
communicate among the nodes; SF, NR, RB.
Viewing Discovered ERP Rings and Ring

Configuration
From the VLAN Tab, you can view devices configured into ERP rings, and the details of
the ring configuration.
614-330055-001 DECEMBER 2015 283

NOTE : The topology map view of ERP c onfigur ation is par t of the EOAM
topology map view . See Viewing EOAM MA Phy sical Top ology on p age
26 9 .
Procedure
1. Select the VLAN Tab. The automatically discovered VLANs display in the
VLAN table. VLANs with an active ERP ring display this icon: .
VLANs on a physical ring that can support ERP display this icon: .
You can sort the table for ERPs to display active ERPs and VLANs with ERP
support by clicking on the ERP header.
2. To view the ERP ring for a VLAN, select a VLAN that has the ERP icon.
Then, click Map. The Map view displays the VLAN with the ERP ring.
3. By default, the VLAN table and VLAN Map is filtered to list only the
member ports (for each VLAN) on the devices within the selected container
object in the Tree View. Where Ring nodes are deployed in separate Tree view
containers (e.g. regions), select the Show All Member Ports check box to
see all the ring nodes on the VLAN Map.
4. To filter the list of VLANs for ERP data, you can:
284 AVIAT NETWORKS

l Sort the table by clicking on table headers, especially the ERP column.
l Click on the Filter button to filter for specific text or numbers.
l Enter a text filter into the Selected Object field.
For more information, see Viewing Discovered ERP Rings and Ring Configuration on
page 283 and Viewing VLANs in the Physical and Flat Maps on page 252.
Viewing ERP Ring Configuration Details

You can view ERP member and RPL owner details for an ERP control VLAN.
Procedure
1. To view the ERP details for an ERP control VLAN, in the VLAN tab, select a
VLAN that has the ERP icon.

2. To view the configuration details, click Details. Click the ERP tab. This tab
presents the details for the ERP associated with the selected VLAN,
including the presence of any subrings. The ERP Details tab values are
described in the table below.
Details Tab - ERP Ring

Name Name of the ERP ring.
614-330055-001 DECEMBER 2015 285

Members Devices and ports on the devices used for the ERP. For example,
INUe153 is the device name, and 7/2 indicates the slot and port
(respectively).
RPL Owner
Ring Protection Link Owner – device/port with this icon.
Subring
ERP Subring - The Subring component of this ERP ring, i.e.,
the Up/In EOAM.
RPL Owner on a
Subring RPL Owner on the Subring (invalid!) - The RPL Owner is not
allowed on the Subring component of an ERP ring.
Configuring an ERP Ring

This section describes how to configure ERP rings from ProVision.
l Provisioning a New ERP Ring on page 286
l Provisioning an ERP Subring on page 290
l Modifying an ERP Ring on page 292
l Deleting an ERP Ring on page 292
NOTE : Pr ovis ioning of EO AM MAs s panning CTR and Ec lips e devic es is

not yet s uppor ted fr om Pr oVis ion due to a limitation in the Ec lips e s oft-
w ar e. This als o impac ts the ability to pr ovis ion ERP r ings s panning CTR
and Ec lips e. The limitation w ill be addr es s ed in later Ec lips e and Pr oVi-
s ion s oftw ar e r eleas es . Inter op r equir es the L egac y Mode tic kbox on the
Ec lips e Por tal O AM s c r een to be untic ked, and the as s oc iated c on-
figur ation objec t is not yet ac c es s ible to Pr oVis ion thr ough the Ec lips e
SNMP management inter fac e.
Provisioning a New ERP Ring

ProVision includes fast ERP ring provisioning for Eclipse, CTR 8540, and CTR 8300.
ERP provisioning simplifies a complex process. It provisions ERP rings, including rings
with stacked GE3 links across a protected DAC GE3.
ERP Provisioning Prerequisites

l All of the ports that participate in the ERP ring control plane must have
membership of an ERP control VLAN. Until VLAN provisioning is provided
through ProVision, this VLAN needs to be provisioned using device craft tool
interfaces.
286 AVIAT NETWORKS

l The Eclipse DAC/IDU GE3 supports operation in either 802.1ag or Y.1731
mode, hence does not support both 802.1ag MAs and Y.1731 MEs at the same
time.
Procedure
1. Select the VLAN tab. VLANs where a physical ring (layer 1) has been
detected, that is suitable for ERP provisioning, displays this icon: .

2. To view the physical ring, select the ring and click Show Map.
3. Right-click on the VLAN and select ERP - Provisioning.
4. The ERP Provisioning screen displays. Note that it shows the VID from the
VLAN's details in the VLAN tab.
Y.1731 version:
802.1ag version:
614-330055-001 DECEMBER 2015 287

5. The left side of the screen displays rings that are available for ERP
configuration for this VID. Select the ring to provision.
6. The right side of the screen displays the ring node and provisioning values.
To configure the provisioning, click the Configuration tab and enter the
following:
l Name – User defined name for this ring
l Control VID – VID used for ring control messages (EOAM, R-APS). Where the
ring nodes (Ethernet switches) have been configured for transparent mode
operation, an available VID in the range 1-4094 can be selected.
l Mode - Specify Y.1731 or 802.1ag.
l MD/MEG Level – Level for EOAM MA used in control.
l RPL owner – The node that will block during normal operation, and unblock
during a ring fault.
l Virtual Channel MD Level
l You can set up specific MA/ME configuration options for each Mode. For
Y.1731, these are:
n Mode - Y.1731
n MEG ID: ICC - The ITU Carrier Code (ICC) is a unique code assigned to
a network operator or service provider by the ITU. It is 1-6 characters,
n MEG ID: UMC - The Unique MEG ID Code (UMC) is assigned by the
network operator or service provider, and needs to be unique within
that organisation’s domain. It is 6 characters. The user enters up to the
first 4 characters and ProVision automatically appends 2 characters
(from ‘00’ to ‘99’) that make the UMC for each ME unique.
l For 802.1ag, the options are:
288 AVIAT NETWORKS

n Mode - 802.1ag
n MD Name - Options include String, Primary VID, Unsigned Integer,
RFC 2865 VPN ID.
n MA Name - Options include String, Primary VID, Unsigned Integer,
RFC 2865 VPN ID.
6. If required, click the Advanced tab to enter additional values:
l Operation Mode - Select Revertive (ERP ring returns to a standard

configuration after a problem is managed using the ring) or Non-Revertive
(ERP ring remains in its new post-problem mode.)
l Wait to Restore - Wait time in milliseconds. The valid range is 60 to 720 ms.
l CCM Interval - Select an interval from 100 ms to 10 minutes.
7. Click Commit Changes. A message will display, "This provisioning
operation may affect traffic. Do you want to continue?" Click Yes to
confirm. A progress window displays. This window confirms when the ERP
provisioning is complete.
8. To validate that the ERP is successfully deployed:

l Check the alarm status of the devices in the ERP.
l Run Diagnostics on each EOAM MA/ME for the ERP. See Identifying and
Resolving EOAM Configuration Faults on page 270.
If the ERP deployment has failed, refer to the error message for more information. See
Identifying and Resolving EOAM Configuration Faults on page 270.
614-330055-001 DECEMBER 2015 289

Provisioning an ERP Subring

ERP provisioning can be used to create an ERP subring. A subring is a ring that over-
laps with a portion of another ring.
ProVision includes fast ERP subring provisioning for Eclipse, CTR 8540, and CTR 8300.
ERP Subring Provisioning Prerequisites

l The VLANs that enable the ERP must already be configured on the device.
l An existing ERP ring.
Procedure
1. Select the VLAN tab. VLANs where a physical ring (layer 1) and an ERP ring
have been deployed, and that are suitable for ERP subring provisioning,
display this icon: .

2. To view the physical ring, select the ring and click Show Map.
3. Right-click on the VLAN and select ERP - Provisioning.
4. The ERP Provisioning screen displays. Note that it shows the VID from the
VLAN's details in the VLAN tab.
290 AVIAT NETWORKS

5. The left side of the screen displays rings that are available for ERP subring
configuration for this VLAN. Select the ring to provision with a subring.
6. The right side of the screen displays the ring node and provisioning values.
To configure the provisioning, click the Configuration tab and enter the
following:
l Name – User defined name for this subring
l Control VID – VID used for ring control messages (EOAM, R-APS)
l MD/MEG Level – Level for EOAM MA used in control.
l MEG ID: ICC - The ITU Carrier Code (ICC) is a unique code assigned to a
network operator or service provider by the ITU. It is 1-6 characters,
l MEG ID: UMC - The Unique MEG ID Code (UMC) is assigned by the network
operator or service provider, and needs to be unique within that organisation’s
domain. It is 6 characters. The user enters up to the first 4 characters and
ProVision automatically appends 2 characters (from ‘00’ to ‘99’) that make the
UMC for each ME unique.
l RPL Owner - The node that will block during normal operation, and unblock
during a ring fault.
l Virtual channel MD level - This value is required for a subring that is joining
a main ring. The virtual channel connecting the subring must use a higher MD
level than the other ring links.
7. If required, click the Advanced tab to enter additional values.
l Operation Mode - Select Revertive (ERP ring returns to a standard
configuration after a problem is managed using the ring) or Non-Revertive
(ERP ring remains in its new post-problem mode.)
l Wait to Restore - Wait time in milliseconds.
l CCM Interval - Select an interval from 100ms to 10 minutes.
8. Click Commit Changes. A message will display, "This provisioning
operation may affect traffic. Do you want to continue?" Click Yes to
confirm. A progress window displays. This window confirms when the ERP
provisioning is complete.
9. To validate that the ERP subring is successfully deployed:

l Check the alarm status of the devices in the ERP.
l Run Diagnostics on each EOAM MA/ME for the ERP. See Identifying and
Resolving EOAM Configuration Faults on page 270.
If the ERP deployment has failed, refer to the error message for more information. See
Identifying and Resolving EOAM Configuration Faults on page 270.
614-330055-001 DECEMBER 2015 291

Modifying an ERP Ring

To modify an ERP ring, it is necessary to delete and recreate the ERP. See Provisioning a
New ERP Ring on page 286.
Deleting an ERP Ring

From ProVision, you can delete an ERP ring from a VLAN.
NOTE : You need to delete any c hild or s ubr ings befor e deleting a main
r ing.
Procedure
1. In the main ProVision interface, click on the VLAN Tab.
2. The VLAN Tab displays, with the VLAN Table.
3. Select a VLAN row in the table that has ERP enabled .
4. To delete the ERP configuration, right-click it and select ERP><item>>
Delete.
5. A message displays, asking you to confirm the deletion. This delete

operation may affect traffic. Removing ERP will result in an Ethernet loop
unless part of the physical ring is manually blocked. Type 'confirm' to
continue? If you are certain, type confirm in the field.
6. The ERP is deleted from the devices and the network. (For CTR devices, see
Saving Carrier Ethernet Configuration for CTR Devices on page 1.)
7. To further confirm that the ERP is deleted:
292 AVIAT NETWORKS

l Check the VLAN Details view to ensure that the ERP no longer displays.
l Check the EOAM Tab to ensure that the EOAM MA/MEs for this ERP no
longer display.
614-330055-001 DECEMBER 2015 293

Chapter 6. Managing Events
This section introduces the tools for Managing events generated by the network devices
and by the system. This includes:
l Graphic views displaying the impact of events on the network, showing how
much or how little of your business is affected.
l Customizable Event Browsers, with event filtering and browser options that
you can save and reuse.
l Prefiltering events as they are received by ProVision, which reduces the number
of events processed and stored in the ProVision database.
l 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:
l Traps that reflect a change in a device or an alarm generated in the device,
which are forwarded to ProVision.
l Responses by devices to presence polling from ProVision.
l Generated by ProVision to reflect operator activity, such as a device being
deployed.
l 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:

l Event Management Processes on page 296
l Event Management Interdependencies on page 297
l Event Management Procedures on page 299
l Scoreboard Group Scenarios on page 367
614-330055-001 DECEMBER 2015 295

CHAPTER 6. MANAGING EVENTS
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 pro-
cesses involved in managing events:
l Managing Event Processes in ProVision on page 296
l Setting Up Scoreboard Groups on page 297
l Customizing Event Browsers on page 297
Managing Event Processes in ProVision

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

Identifying and prioritizing events is essential for managing events and identifying prob-
lems. 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 tem-
porary 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.
1. Identify events from one of the following:
l Scoreboard Groups: graphs and charts identify the radios that are having
events.
l The Tree Viewer: events are shown by the color code for a radio.
l The Map Viewer: again, events are shown by the color code for a radio.
Then, go to the Event Browser to view the details of events.
296 AVIAT NETWORKS

2. From the Event Browser, you can do the following for both local and remote
radios:
l Filter events
l View event history and performance trends
l Open the Parent Device
3. For links, you can view the link submap, a link-related Event Browser, and per-
formance trends.
Event Management Interdependencies

Prerequisites
The following prerequisites enable you to manage events:
l The network radios must be physically installed and commissioned
l The radios must also be deployed and managed in ProVision
Dependencies
The Northbound Interface is dependant on events being managed within ProVision.
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 367.
Customizing Event Browsers

A simple overview of how to steps involved to create a customized Event Browser is:
1. Open the Event Browser.
614-330055-001 DECEMBER 2015 297

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 314.
298 AVIAT NETWORKS

Event Management Procedures

l Network Events on page 299
l Event Browsers on page 314
l Event Log Pre-Filtering on page 326
l Event Notification on page 341
l Logical Containers on page 359
l Logical Links on page 364
l Scoreboard Group Scenarios on page 367
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 net-
work 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 auto-
matically 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.
l Network Event States on page 299
l Viewing Network Events on page 300
l Viewing an Event’s Properties on page 301
l Acknowledging a Network Event on page 303
l Unacknowledging a Network Event on page 305
l Manually Clearing a Network Event on page 307
l Sleep Status for a Device on page 311
l Event Browsers on page 314
Network Event States

It is important to monitor, acknowledge, and, where necessary, escalate active events.
Of particular importance are events that affect communications traffic.
614-330055-001 DECEMBER 2015 299

When escalating active events, it is important to know the different states that a net-
work event may have. These states are detailed in the table below.
Table 6-1. Network Event States
Event State Description

An unacknowledged, original event raised by a device. In the unac-
knowledged 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.
Viewing Network Events

You can view network events from the following locations:
l Event browser
l Tree viewer (in the Physical, Logical Container, and Circuits tabs)
l Map viewer (in both the Physical and Flat maps)
l Object view (for Eclipse devices)
l Service table
l Scoreboards
All unacknowledged active events can be viewed in the main Event Browser.
300 AVIAT NETWORKS

You can also open a separate Event Browser window by:
l Selecting the New Event Browser icon from the tool bar, or
l 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 314.
Related Topics:
l Network Event States on page 299
l Viewing an Event’s Properties on page 301
l Acknowledging a Network Event on page 303
Viewing an Event’s Properties

You can view an event’s properties to gain information about a specific event. Event
properties allow you to answer the following questions about an event:
l Is the event equipment related, or due to weather or site conditions?
l Can you determine if the event is cleared by the device?
l Should you escalate the event to an engineer?
The figure below shows an example of an Event Properties window.
Figure 6-1. Event Properties Window
From the Information tab you can determine the following about the event:
l Event name, status and category
l Device that generated the event
l Date and time the event occurred
614-330055-001 DECEMBER 2015 301

The Probable Cause tab details information about the event such as:
l Fault is intermittent or continuous
l Fault frequency
l 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.
NOTE : The event s tates ar e des c r ibed in Net work Ev ent St at es on p age
29 9 .
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
1. Within the main Event Browser or a customizable Event Browser, right-click an
event. In the right-click menu, select Event Properties.
2. The Event Properties window displays.
3. To view the probable cause of the event, select the Probable Cause tab.
4. To close the Event Properties window, select Close.
302 AVIAT NETWORKS

Acknowledging a Network Event

Acknowledging an event notifies other operators that the event is currently being
handled.
You can acknowledge an event from the main Event browser or from a separate Event
Browser window.
By default, all unacknowledged active events are displayed in the main Event Browser.
Acknowledging an event in the main Event Browser removes it from the browser.
In a customized Event Browser, an acknowledged event is indicated by a check mark, as
shown below.
Figure 6-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.
614-330055-001 DECEMBER 2015 303

4. The selected event (or events) disappears from view after being acknowledged.
See the next section, Acknowledging in a Separate Event Browser on page 304, for
instructions on how to view acknowledged events.
Acknowledging in a Separate Event Browser

To acknowledge one or more network events in a separate Event Browser window:
1. Right-click the container or radio that is associated with the event you want to
acknowledge. Or, open a separate Event Browser window for multiple containers or
radios by holding down the ctrl or the shift key and selecting multiple items.
2. From the right-click menu, select Event Browser.
3. If you want to be able to view the acknowledged events, select the View Filters
icon.
4. In the Filters window, select the Acknowledgment, Acknowledge and Unac-
knowledge check boxes; then select the OK button. Acknowledged events will appear
with a check box beside them in the Event Browser window.
5. 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.
6. Right-click a selected event and, from the right-click menu, select Acknowledge.
information. Then click OK.
8. 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.
304 AVIAT NETWORKS

Unacknowledging a Network Event

Introduction
If you need to reassign a previously acknowledged event, the event can be unac-
knowledged to make it available to other operators. More than one event can be unac-
knowledged at a time.
Acknowledged events can be displayed in a customized Event Browser window and are
indicated with a check mark.
Procedure
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 dis-
plays.
3. In the Event Browser window, select the acknowledged event(s) to be unac-
knowledged. The selected event(s) are highlighted.
4. Right-click and from the right-click menu, select Acknowledged.
information pertaining to the event. Then select the OK button.
6. In the Event Browser window, the event changes to unacknowledged and the
check is removed. The event is also displayed in the main Event Browser.
614-330055-001 DECEMBER 2015 305

Managing Event Notification Pop-Ups and Audio

Alarms
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 343.
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 auto-
matically, 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.
306 AVIAT NETWORKS

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

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 clear-
ing 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 manu-
ally 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 311.
However, an example of where you might clear an event is when a problem requires a
field technician to visit the radio. The event has been acknowledged but the radio’s event
severity color is still red (indicating a critical event) and so any events from the radio of
the same or less severity would not be immediately obvious, especially from the Score-
board view. Clearing the event would return the radio to normal (green) and any new
events changes would be obvious.
Procedure
1. From any Event Browser window, select the event or events to be cleared.
2. Right-click the selected event or events and from the right-click menu select Clear.
The cleared events are removed from the browser window and the event summary
icons in the bottom right corner are updated.
614-330055-001 DECEMBER 2015 307

Manually Resynchronize Alarms

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:
l TRuepoint 4000
Manual Alarm Resynchronization is also available for Constellation. Constellation
alarms are automatically resynchronized every six hours. The Manual Alarm Resyn-
chronization is available as an optional function.
Run the Manual Alarm Resynchronization after any maintenance.
NOTE : TRuepoint 6400 r equir es a differ ent pr oc edur e to enable its

alar m r es ync hr onization; s ee C onfigu re TRuep oint 6 4 00 Alarm Resy n-
chronizat ion on p age 308.
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.
3. An event displays while the resynchronization is in process.
NOTE : The manual alar m r es ync hr onization may take s ome time to be
fully pr oc es s ed.
4. When the manual alarm resynchronization is complete, the event clears. The
device is now fully resynchronized.
Configure TRuepoint 6400 Alarm Resynchronization

TRuepoint 6400 devices have two types of alarm resynchronization in ProVision:
l Summary Resynchronization- Always run from ProVision, as a basic support:
only updates the Major and Minor summary alarms for TRuepoint 6400.
l Full Resynchronization - Run when ProVision is enabled to connect directly to
the TRuepoint 6400 radio. ProVision then extracts the list of all active
308 AVIAT NETWORKS

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.
NOTE : To s et this up, you need the us er name and pas s w or d for the
r adio’ s WebCIT ins tallation. O btain this , and then follow the pr oc edur e
below .
Procedure
1. In ProVision, from the Administration menu, select Device Security Accounts.
2. The Device Security Accounts screen displays. In the screen, locate the TRuepoint
6400 radio you want to configure for resynchronization. Right-click on the Device
Login column and select Edit Account Information.
3. The Edit Account Information screen displays. Select the Account Type of Device
Login. The Device Login values display.
4. Type in the WebCIT user name and password.
5. Click OK.
6. The radio now shows that it has been set up with a Device Login. In the Device
Security Accounts screen, click OK.
614-330055-001 DECEMBER 2015 309

7. ProVision can now obtain the active alarm list for this TRuepoint 6400 radio from
WebCIT.
Customizing Event Names or Severity Levels

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 Customize Event Name? Customize Severity Level?
Tool to Use? Tool to Use?
Altium (all variants) Yes, WMT Yes, WMT
Constellation (all Yes, ProVision Yes
variants)
CAUs Yes, ProVision Yes, ProVision
DVAs Yes, ProVision Yes, ProVision
Eclipse: AUX Plugin, Yes, Eclipse Portal Yes, Eclipse Portal
Auxiliary Module
Generic Devices Yes, ProVision Yes, ProVision
LE3000/WL1000 Yes, LE3000 Manager No
LE3200 Yes, LE3200 Manager No
Megastar (all vari- Yes, ProVision Yes, ProVision
ants)
RW2000 Yes, RW2000 Manager No
TNet: Classic II, LC Yes, TNet Web Yes, TNet Web
Series, M Fiber, M
series, QUANTUM,
SPECTRUM II
TRuepoint: 4000, Yes, WebCIT Yes, ProVision
4040, 5000, and
6400
310 AVIAT NETWORKS

Procedure
1. For Generic Devices only, ensure that the Event has already been generated. For
Generic Devices, ProVision needs an existing event record to customize. Check the
Event Browser for the Generic Device to see if the event you need is there.
2. Select the device or Container. Right-click on the object.
3. From the right-click menu, select Fault > Event Customization. The Event Cus-
tomization screen displays. This screen has a list of all events that can be cus-
tomized 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 cus-
tomized name and severity levels.
Sleep Status for a Device

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
614-330055-001 DECEMBER 2015 311

device. The device’s error status is maintained in the ProVision user interface and the
events prior to the device being put to sleep can still be viewed.
Normally, you set a device to Sleep when a field technician is at the site and is per-
forming maintenance on the device, or when there is heavy rain that is causing tem-
porary 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 165.
To find all Sleep settings, use the Device Maintenance screen. Open this from the Fault
menu as Device Maintenance. 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:
312 AVIAT NETWORKS

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.
Continue Monitoring While Asleep - Check this to have ProVision continue mon-
itoring/managing the device while it is asleep.
Then, click the Sleep button.
4. The device is set to the Sleep state and displays with the Sleep icon.
To wake a single device:
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 icon is removed from the device.

To set the Sleep status of two or more devices:
1. Select the device icons for all the required radios. Then, right-click 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.
NOTE : For Ec lips e IDU r adios , c hild devic es c an be s et to a s leep/w ake

s tate independently of their par ent devic e. To enable you to c hange the
s leep/w ake s tate of the par ent devic e, all the c hild devic es mus t be in
the s ame s leep/w ake s tate.
614-330055-001 DECEMBER 2015 313

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 6-3. The Main Event Browser
You can also open a separate Event Browser window by:
l Selecting the New Event Browser icon from the tool bar, or
l Selecting Fault > Event Browser > New Event Browser from the menu bar, or
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 below, can be cus-
tomized to help you better monitor the network. See Customizing Event Browsers on
page 297.
Figure 6-4. A Separate Event Browser Window
Certain events, particularly the WTM 3300 Performance Threshold event, include pop-
up notes with value details.
314 AVIAT NETWORKS

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.
NOTE : If you have a lar ge Pr oVis ion databas e, it takes time to r etr ieve
lar ge amounts o events . A loading ic on dis plays w hile the data is being
r etr ieved.

l Saving an Event Browser View on page 315
l Viewing a Saved Event Browser on page 316
l Customizing an Event Browser on page 317
l Event Browser Filter Values on page 319
l Changing Event Browser Options on page 321
l Event Browser Option Values on page 322
l Deleting an Event Browser on page 323
l Saving Event Browser Contents on page 324
l Printing Event Browser Contents on page 325
For information on viewing and managing network events, see Network Events on page
299.
Saving an Event Browser View

Saving the Event Browser view lets you keep the customized settings for future use, sav-
ing 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 317 for more information.
Procedure
1. Open an Event Browser view:
l 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.
l 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.
614-330055-001 DECEMBER 2015 315

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.
Viewing a Saved Event Browser

Saved Event Browsers are accessed from the main user interface Event Browser. These
are Event Browser views that you have customized and saved.
Procedure
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.
316 AVIAT NETWORKS

Customizing an Event Browser

You can change an Event Browser’s name and description. You can also change the max-
imum 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 dis-
played. 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:
l Open a new Event Browser by selecting the new Event Browser icon
from the tool bar.
l 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.
l 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.
l An Event Browser window displays.
2. On the tool bar, select the View Filters icon. The Filters window displays.
614-330055-001 DECEMBER 2015 317

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.
318 AVIAT NETWORKS

Event Browser Filter Values

Filter Setting Definition
Simple Tab State:
By default, only active events are dis-
played in an Event Browser.
To view cleared events in an Event
Browser view, select the Cleared check-
box.
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 unac-
knowledged.
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 dis-
played.
To enable specific category filtering, select
the Category checkbox. Then select the
categories you are interested in. All other
category types are not displayed.
Date / Time By default, there is no filtering on date
and time.
To activate the date and time filter, select
the Date / Time checkbox.
To enable the filter’s start date and time:
Select the Start checkbox.
Select the associated drop-down arrow.
From the calendar displayed select the
required month and day.
Change the time, if required.
To enable the filter’s end date and time,
repeat the above four steps for the filter
End date.
614-330055-001 DECEMBER 2015 319

Filter Setting Definition

Objects By default, there is no filtering on object
types, and events for all object types are
displayed.
To filter for events generated by specific
object types:
- Select the Object Type checkbox.
- Select the checkboxes of the object
types required.
Only events generated by the selected
object types are displayed in the Event
Browser.
Text By default there are no text filters applied

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

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

Changing Event Browser Options

You can set the following Event Browser options:
l The description of the Event Browser view.
l The maximum number of events displayed in this particular browser. By
default, the number is 1000 events.
l The fields displayed in the browser window.
l The order in which the events are displayed. By default, the events are
displayed in descending date and time order.
NOTE : Selec ting the title bar of a c olumn c hanges how the events in the
br ow s er ar e s or ted.
Procedure
l Open a new Event Browser by selecting the new Event Browser icon from
the tool bar.
l 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.
drop-down menu. An Event Browser window displays.
2. On the Tool bar, select the Browser Options icon. The Browser Options win-
dow 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 DECEMBER 2015 321

Event Browser Option Values

Tab/Option Description
Details Tab
Name 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.
Highlight Severity When Highlight Severity is enabled, each row in this
Event Browser view is highlighted in the event’s severity
color.
To enable the Highlight Severity option, select the check-
box.
Max Displayed Events Sets the maximum number of events that can be dis-
played in this Event Browser window.
To change the maximum displayed events, move the
slider.
The maximum number of events that can be displayed is
15000.
Fields Tab You can change which fields are displayed in the Event
Browser.
To make a field visible in the Event Browser,:
Double-click the required field in the Hidden column to
move it to the Visible column.
OR select the required field (or multiple fields) in the
Hidden column then select to move it to the Vis-
ible 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 Hid-
den column.
322 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.
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
Description
Options
Acknowledged Events are sorted by acknowledged events.
Active Status Events are sorted by active status.
Category Events are sorted alphabetically by category description, for example:
communications, equipment, quality of service.
Cleared Events are sorted by the date and time when they were Cleared. This
Date/Time value is Hidden by default.
Event 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 parent’s IP address, followed by its sub-
net number.
Notes Events are sorted by the notes icon. Notes are only applicable to the
Eclipse devices. A notes icon displays in the notes column only when a
note has been created by the user.
Object Events are sorted by the device name, in alphabetical order.
Object Type Events are sorted alphabetically by the device’s path.
Raised Events are sorted alphabetically by the object type, for example:
Date/Time Altium ADR, Eclipse DAC, Eclipse INU.
Severity Events are sorted by the date and time when they were raised.
User Events are sorted by the event severity color-coding.
Deleting an Event Browser

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.
614-330055-001 DECEMBER 2015 323

Procedure
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 dis-
plays.
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.
Saving Event Browser Contents

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 soft-
ware to present a graphical view of the historical data.
324 AVIAT NETWORKS

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 Cus-
tomizing Event Browsers on page 297.
You might use this file as a comparison to a previously saved file, or view the file later
on when attempting to troubleshoot a set of events.
Procedure
To save the contents of an Event Browser to file:
the tool bar.

drop-down menu.
2. From the menu bar select File > Save to File... The Save window displays.
3. Browse the directory structure for the folder to save the file.
4. In the File name: field, type in a name for the event log.
5. Select the Files of type drop-down arrow and select the file type.
6. To save the file, select Save.
Printing Event Browser Contents

You can print the contents of an Event Browser for reporting purposes or to troubleshoot
events.
Procedure
the tool bar.

614-330055-001 DECEMBER 2015 325


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:
l Saving an Event Browser View on page 315
l Viewing a Saved Event Browser on page 316
l Saving Event Browser Contents on page 324
Event Log Pre-Filtering

An Event Browser window can become overloaded with hundreds of events, making sort-
ing 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-fil-
tering reduces the number of events being fully processed and increases system per-
formance. Event pre-filters are effective immediately and remain in effect until they are
disabled or deleted.
l Viewing Event Log Pre-Filtering on page 328
l Adding An Event Log Pre-Filter at the Root Level on page 329
l Adding an Event Pre-filter at an Object Level on page 332
l Adding an Event Pre-Filter Via an Event Browser on page 333
l Modifying An Event Log Pre-Filter on page 334
l Deleting An Event Log Pre-Filter on page 335
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.
326 AVIAT NETWORKS

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. Example of a Pre-Filter on page 327 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 6-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 6-6. ODU Pre-filter
Objects That Can Be Pre-Filtered

Table 6-2. Objects / Events that can be Pre-Filtered
614-330055-001 DECEMBER 2015 327

Objects/Events Description
Root Object/Network Pre-filters added at the root level, apply to the entire network,
Container and any events received that match the pre-filter criteria are
rejected.
You can pre-filter events created by network devices and certain
events created by ProVision. ProVision creates performance
events, for example when 15-minute data collection is enabled,
these events can be pre-filtered from the system.
These performance events are part of the platform event group
which can only be pre-filtered at the root level.
You can view existing pre-filters and add new pre-filters.
Container Pre-filters added at a container level are only applied to events
from devices that are children of the container. Any events for
these devices that match the pre-filter criteria are rejected.
You can view existing pre-filters for the container and also for
the parent object.
Radios and Eclipse You can view or add pre-filters for the selected radio or the
Radio plug-ins Eclipse plug-in. You can view pre-filters for the parent object.
Events You can add this specific event to the pre-filter for the device it
pertains to. You can also view any proposed pre-filters that were
set up at the radio or Eclipse radio plug-ins level.
Viewing Event Log Pre-Filtering

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
1. In the Tree or Map Viewer, right-click the object with the icon.
328 AVIAT NETWORKS

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.
Adding An Event Log Pre-Filter at the Root Level

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 328.
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
1. From the main user interface, tool bar select Faults -Events Pre-Filter. The Event
Pre-Filter window displays.
614-330055-001 DECEMBER 2015 329

2. From the Object Type drop-down list, select the type of device to which the pre-fil-
ter is to apply.
3. To display the types of events associated with the selected object, on the Self tab,
select Add. The Add Pre-Filtered Events window displays.
4. Select the check boxes of the event or events required.

5. To accept the events selected, select OK. The Self tab is updated to display the
events selected for the pre-filter.
330 AVIAT NETWORKS

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.
614-330055-001 DECEMBER 2015 331

Adding an Event Pre-filter at an Object Level

This applies to adding an event pre-filter at the Container, Radio, and Eclipse Plug-in
level.
See Objects / Events that can be Pre-Filtered on page 327 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.
l For all devices, with the exception of the Eclipse radio and Eclipse Link, the
Object Type is set for the type of radio or plug-in previously selected and
cannot be changed.
3. If you have selected an Eclipse radio, then from the Object Type drop-down list,
select either All Types or the specific component, or plug-in required.
4. To display the type of events associated with the selected object, select Add. The
Add Pre-Filtered Events window displays.
332 AVIAT NETWORKS

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.
NOTE : Ad d ing an Ev ent Pre-Filt er Via an Ev ent Browser on p age 333
Adding an Event Pre-Filter Via an Event Browser

This applies a pre-filter to a specific type of event for a specific device. When you select
this option, the event to be pre-filtered and any other enabled pre-filtered events for this
specific device are displayed, and the event pre-filter is automatically enabled.
Procedure
To add an event from an Event Browser for a specific object, as a pre-filter criteria:
1. In the Event Browser, right-click the required event.
2. From the right-click menu, select the Add to Pre-filter option. The Add to Pre-Fil-
ter <object> window displays, showing the selected event and any enabled events
that are already being pre-filtered for this specific object.
614-330055-001 DECEMBER 2015 333

3. To accept pre-filtering for the event, select OK.
Modifying An Event Log Pre-Filter

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 cri-
teria.
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-fil-
ter.
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 win-
dow displays.
334 AVIAT NETWORKS

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-Fil-
ter checkbox.
7. To save your changes, select OK.
Deleting An Event Log Pre-Filter

You can delete an event log pre-filter when the problem causing the event has been fixed
or no longer exists.
To delete an event log pre-filter, you must select the object to which the pre-filer has
been applied. You cannot delete a parent object’s pre-filters from a child object. For
example, in the figure below, pre-filters set for XP4 radios, at the root level (Southern
North Island) cannot be deleted at the XP4 radio level, for example Waikanae.
614-330055-001 DECEMBER 2015 335

Figure 6-7. Deleting Pre-Filters
When an event pre-filter is deleted the icon is no longer displayed beside the pre-
viously pre-filtered object.
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.
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.
336 AVIAT NETWORKS

4. Select Remove. The Enable Pre-filter option is grayed out.

5. To save your changes, select OK.
614-330055-001 DECEMBER 2015 337

Event Analyzer
The Event Analyzer is a tool to identify events that happen frequently in your network.
At a glance, you can see devices and event types that recur often. You can save the
Event Analyzer data as a .txt file for further reporting analysis.
NOTE : The Event Analyzer analyzes all devic es and events in Pr oVis ion.
Procedure
1. Go to the Faults menu and select Event Analyzer. The Event Analyzer
screen displays. The left side of the screen displays devices or events, sorted
by event frequency. The right side of the screen shows a pie graph of events
by type.
2. To refine your view of the events and devices:

l To refresh the Event Analyzer view with current events, click the Refresh icon.
l In the drop-down menu, select the time period of events:
l Last 24 Hours by Device
l Last 24 Hours by Event
l Last Week by Device
l Last Week by Event
l Last 30 Days by Device
l Last 30 Days by Event
l To combine all plug-ins for one device in the Devices view, check the Bundle
Nodes box.
4. To view the events for a specific device, click on the icons beside the device
in the Devices list. The Event Analyzer Details display for this device:
338 AVIAT NETWORKS

5. You can drill down to review events for a specific time increment. Click the
icon beside the time increment to view an analysis of events. This includes:
l Event type
l Number of occurrences of event
l Graphic layout indicating frequency of events
NOTE : When you dr ill dow n to a devic e or event, us e the For w ar d, Bac k,
and Home ic ons to navigate to the main Event Analyzer s c r een.
4. To save the Event Analyzer data as a .txt file, click the Save icon . The
Save As window displays. Assign a file name and click Save to save the
data.
614-330055-001 DECEMBER 2015 339

Security Log
The Security Log provides a record of user activity and device user activity events col-
lected by ProVision. Whenever a user makes a change or performs an operation in ProVi-
sion, 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 respons-
ible for any activity on ProVision.
The Security Log records user activity for the following:
l The Physical Root level of ProVision
l The ProVision Manager
l Regions, Sites, and Containers
l The following devices:
l Altium
l Eclipse
l LE3000 and LE3200
l Velox
NOTE : The Sec ur ity L og only dis plays in the r ight-c lic k menu for a
devic e if the devic e is c ompatible w ith the Sec ur ity L og, or if the devic e
is an empty c ontainer .
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:
340 AVIAT NETWORKS

3. The Security Log displays the following event data:

l Event - Event type.
l Object - Object type.
l User - The user responsible for the event.
l Notes (Text) - Text notes about the event, the client IP/PC user name, and the
affected device.
l Raised Date and Time - Date and time of the event.
4. To change the data displayed in the Security Log, you can:

l Change the Browser options - see Changing Event Browser Options on page
321
l Change the Filter values - see Modifying An Event Log Pre-Filter on page 334
l Change the Scoreboard options - see About Scoreboard Group Scenarios on
page 367
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:
614-330055-001 DECEMBER 2015 341

l 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.
l ProVision Client pop-up message = When an event is identified, a text
message displays in a window in the ProVision user interface.
l ProVision Client audio message = When an event is identified, the ProVision
computer makes a distinctive sound. Different events can have different
sounds.
l 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 spe-
cific 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.
l Set the Server Notification Preferences on page 342
l Add or Edit Event Notification Rules on page 343
l Delete an Event Notification Rule on page 347
l Configuring the Notification Rule on page 348
l Set Up an Email Event Notification on page 351
l Set Up a Pop-Up Message Notification on page 353
l Set Up an Audio Alarm Notification on page 355
l Set Up Script Execution on Event Notification on page 357
Set the Server Notification Preferences

If you want ProVision to send email notifications, you must set up the Server Noti-
fication Preferences values. In this screen, you note the IP address of your email server,
used when ProVision sends an email message about an event, and a user-supplied name
that appears on the email when ProVision sends the message.
After you have set this up, your system can send email notifications. See Set Up an
Email Event Notification on page 351 for more details.
Procedure
1. From the Menu Bar, select Administration > Email Server Configuration. The
Server Notifications Preferences window displays.
342 AVIAT NETWORKS

2. In the Mail (SMTP) Server text box, enter the IP address or host name of your
email server. If required the default SMTP port can be changed by appending IP
address or host name of your email server with :port where port is SMTP server
port. For example 10.12.13.40:587
3. Your mail server set up determines if you need the Use authentication feature:
l If your company’s mail server requires authenticated email, select the Use
authentication checkbox. Also, enter the Username and Password of your
mail server. See your mail server’s 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.
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.
Add or Edit Event Notification Rules

NOTE : Thes e ins tr uc tions ar e for NO C Engineer s and Adminis tr ator s
only. NO C O per ator s c annot s et up new Event Notific ations .
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:
614-330055-001 DECEMBER 2015 343


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.
3. The Rule Wizard displays. Enter values here to create a new Event for noti-
fications.
344 AVIAT NETWORKS

There are three sets of tabs, accessed on the right side, where you enter the event val-
ues:
l Filters - Values to filter for specific event types for this notification.
l Notification Settings - Notification time criteria.
l Actions - Actions to occur when the event takes place.
4. Set up the Filters as described inConfiguring the Notification Rule on page 348.
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.
l After Event Duration - Event notification will be sent after the event has
lasted for this amount of time.
l 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.
l Reminder After - A reminder about the event will be sent after this amount of
time.
l 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
occurs. An Email event appears in the Actions viewer. Right-click it to:
614-330055-001 DECEMBER 2015 345

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 User’s 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 351.
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 357.
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:
346 AVIAT NETWORKS

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.
NOTE : You c an deac tivate a notific ation to r etain it in Pr oVis ion w ithout
us ing it.
15. To give the new Notification a pop-up or audio notification, right-click in the Cli-
ent Notifications table column. You are prompted to:
l 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 353.
l Subscribe to audio alert - Select this to set up an audio alert. See also Set Up
an Audio Alarm Notification on page 355.
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 win-
dow. 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.
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:
614-330055-001 DECEMBER 2015 347

2. Select the rule to be deleted.

3. Click the Remove button. The selected rule is removed from the Event Noti-
fication Rules window.
Configuring the Notification Rule

The table below describes how to configure specific values for a new or existing noti-
fication rule. Select a tab to display that tab’s values. Select OK to save the settings for
the notification rule.
Notification Rule Tab Description
Simple Tab: Acknowledgement
Select the Acknowledgement
box to allow acknowledged and
unacknowledged events as criteria
for the notification.
Severity
Select the Severity box to allow
the different levels of severity to
be used as criteria for the noti-
fication 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 cat-
egorize 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 qual-
ity control in your network.
348 AVIAT NETWORKS


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.
Objects Tab: Object Type

Select the Object Type box to
allow specific types of radios and
plug-ins as criteria for the noti-
fication rule.
Select the box next to the object
type(s) that you wish to include as
criteria for the notification rule.
614-330055-001 DECEMBER 2015 349


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
To include text as a criteria from
the notification rule:
Select the Text Filter box to
allow text as a criteria for the
notification rule.
Select the Add button to cre-
ate a new text filter.
Enter the required text in the
Text column.
Select Include to include the
text as criteria for the noti-
fication rule. Or, select
Exclude to remove the text
as criteria.
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
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.
350 AVIAT NETWORKS

Delete an Event Notification Rule on page 347
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 342 and Add or Edit Event Noti-
fication Rules on page 343. It is collected here to help users understand how to set up
this type of notification.
First, make sure that ProVision is set up with the Server event notification preferences.
This allows ProVision to communicate with your Server’s web connection, to send
emails. Then, set up the event notification Rules.
Before you begin, you will need the following information:
l Your mail server’s IP address, user name, and password.
l The names and email addresses of people who will be receiving email events.
NOTE : Some e-mail s er ver s r equir e “s ec ur e” authentic ation. If this is

r equir ed, us e the Use S ecure C o nnect io n option.
The default event notific ation email is pro-
vision@<yourcompanyname>.com
You may w is h to have your IT manager s c r eate this email addr es s .
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 5. If
they have not, go to step 3.
3. Enter the server values:
In the In the Mail (SMTP) Server text box, enter the IP address or host
614-330055-001 DECEMBER 2015 351

name of your email server.

If required the default SMTP port can be changed by appending the IP
address or host name of your email server with :port where port is the
SMTP server port. For example, 10.12.13.40:587
Your mail server set up determines if you need to apply the Use authen-
tication feature. If your company’s mail server requires authenticated
email, select the Use authentication checkbox. Also, enter the User-
name and Password of your mail server. See your mail server’s admin-
istrator for the correct username and password.
In the Email “From” Address text box, enter the text that you would
like to appear in the email messages as the sender.
If required, click the Use Secure Connection check box.
4. Select the Apply button to save the changes while keeping the Server Notification
Preferences window open.
5. 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 but-
ton remains inactive until the Apply button is selected.)
6. Select OK to close the Server Notification Preferences window.
7. From the Menu Bar, select Faults > Event Notifications. The Event Notification
Rules window displays.
the Add button.
9. The Rule Wizard displays. Enter values in this window to create a new Event for
notifications: the Filters, the Notification Settings, and the Actions.
NOTE : Ac tions is w her e you w ill enter your email notific ation details .
11. Set up the Notification Settings as described in Add or Edit Event Notification
Rules on page 343.
13. Right-click and select Add Email to have ProVision notify you via email when the
event occurs. To create an email that only includes a subject line, select Add Email
Action (Subject Only). An Email event appears in the Actions viewer. Right-click it
to:
352 AVIAT NETWORKS

l Add email address - Enter an email address. The Edit Actions window
displays:
l Enter the email and click OK. Email notifications will be sent to the entered
email address, and the email is displayed:
l Add User/s - Connect the Notification to a ProVision User, then click OK.
Email notifications will be sent to the User’s email address (see the
Installation and Administration Guide for instructions.)
NOTE : To tes t an email notific ation, open the Edit Ac tions w indow and
c lic k Tes t. An email is s ent: its s our c e addr es s is Pr o-
vis ion@ c ompany. c om.
14. The new Notification is displayed. There are separate icons for an email noti-
fication, a User notification, and an attempt to send an email notification to a user
whose emails have been suppressed:
15. 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 343.
16. The changes are saved automatically. Email notifications will be sent for this
event.
Related Topics:
l Configuring the Notification Rule on page 348
Set Up a Pop-Up Message Notification

You can 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 343.
614-330055-001 DECEMBER 2015 353

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 inform-
ation in the text box is automatically updated when new triggering conditions occur.
Other features of the event notification are listed below:
Feature Description
Text Box Displays the triggering condition as defined by the user, the device
where the event originated, the day and time the event occurred, the
event, and its severity.
Left / Right If more than one dialog box is open, select the left or right arrow but-
tons to scroll through the active event notification dialog boxes.
Event Browser Opens the Event Browser of the device where the event originated.
Dismiss All Dismisses all active events.
Dismiss Dismisses only the current event. Any active events remain active.
Close Closes the event notification dialog box, but does not dismiss the
event.

l Events for which you want to view pop-up message notifications.
NOTE : The notific ation pr efer enc es for the Pr oVis ion c lient ar e as s o-
c iated w ith a s pec ific us er ac c ount, s o the s ame pr efer enc es ar e ac c es s -
ible fr om any w or ks tation that the us er is logged into. If a number of
us er s ar e logged into Pr oVis ion w ith the s ame us er name, then the s ame
pop-up notific ations dis play at eac h w or ks tation.
Procedure
1. Follow the steps in Add or Edit Event Notification Rules on page 343 to create a
new rule for an event.
354 AVIAT NETWORKS

2. The action that was created now appears in the Event Notification tab. Its descrip-
tion is below:
3. To give the new Notification a pop-up notification, right-click in the Client Noti-
fications 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.
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 342 and Add or Edit Event Notification Rules on page 343. 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.
614-330055-001 DECEMBER 2015 355

NOTE : To s uc c es s fully us e audio alar ms , the Pr oVis ion c omputer needs

to be equipped w ith a s ound c ar d and s peaker s , and the volume needs to
be tur ned up s o that an audio alar m c an be hear d.
NOTE : The default audio alar m is a beeping s ound. Us er s c an load a

.wav s ound file to us e as an alar m s ound. Differ ent events c an have dif-
fer ent alar m s ounds . See the follow ing ins tr uc tions for mor e infor m-
ation.
W AR NING : . w av s ound files s hould be betw een 1 and 3 s ec onds long.

If file s ounds ar e longer than that, ther e ar e pr oblems r epeating
s ounds if events r eoc c ur .
Procedure
To set up an audio alarm notification:
1. Follow the steps in Add or Edit Event Notification Rules on page 343 to create a
new rule for an event.
2. The action that was created now appears in the Event Notification tab. Its descrip-
tion is below:
3. To give the new Notification audio notification, right-click in the Client Noti-
fications 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:
356 AVIAT NETWORKS

5. Select whether the audio notification will be a single alert (sounding once) or a con-
tinuous 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:
l To choose the default audio notification, select the check box to Use Default.
The user interface will play the default audio notification when this is set up
for an event.
l 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, the user interface will play the audio noti-
fication.
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.
l Events for which you want to run script executions upon notifications.
l The names and file locations of scripts to be run upon notification.
NOTE : An event notific ation c an r un either an email notific ation or a

batc h file. If you w ant a notific ation for an event to r un both an email noti-
fic ation and a batc h file, you need to s et up tw o s epar ate event noti-
fic ations for that event.
614-330055-001 DECEMBER 2015 357

Table 6-3. Script Parameters

Paremeter Description
%date Date in format yyyy/MM/dd
%time Time in HH:mm:ss
%node Name of node that was event source
%eventDescription Event Description.
%eventState Event status "Active" or "Cleared"
%eventSeverity Severity of event e.g. "Critical"
%ipAddress IP address of event source
%notificationName Notification profile name
%reminder Indicates if reminder has been selected "Reminder" or ""
%nodePath Path of node that was event source
%eventUser User who generated event
Example:
If a notification script filename.bat exists then entering
filename.bat %nodePath %eventDescription %eventSeverity
would mean that replaceable command line parameters %1 would be %nodePath, %2

would be %eventDescription and %3 would be %eventSeverity . These can then be
used in a script.
Procedure
1. From the Menu Bar, select Faults > Event Notifications. The Event Notification
Rules window displays.
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.
NOTE : Ac tions is w her e you w ill enter your s c r ipt details .
5. Set up the Notification Settings as described in Add or Edit Event Notification
Rules on page 343.
358 AVIAT NETWORKS

7. Right-click and select Add Script Action to have ProVision run a shell script for a
batch file when the event occurs.
8. Right-click the Run Script item to Add script.The Edit Actions window displays.
9. Enter the file name for the script batch file, and click OK.
10. The script item displays as an event.
11. 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 Docu-
ments\ProVisionServer\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 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 343.
13. Click Close to save the change.
14. Email notifications will be sent for this event.
15. When this event occurs, the script will run.
Logical Containers
l Adding a Device to a Logical Container on page 361
l Removing a Device from a Logical Container on page 362
l Renaming a Logical Container on page 363
l Deleting a Logical Container on page 363
614-330055-001 DECEMBER 2015 359

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 auto-
matically 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:
l 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.
l The grouping of all radios carrying traffic for specific customers, in order to
generate customized availability reports for each customer.
l The grouping of radios carrying traffic for important events to improve
response times.
l The grouping of radios carrying traffic for emergency services to improve
callout response times.
If the logical container contains any objects that are hidden due to regional access
restrictions, a globe icon will appear next to the logical container. If you mouse over it,
the tooltip will tell you that some objects are hidden due to regional access being
applied. If you delete the logical container it will tell you that the hidden objects will
not be deleted.
360 AVIAT NETWORKS

NOTE : Cir c uit bundles c an be inc luded in a logic al c ontainer . In

addition, a logic al c ontainer c an be inc luded w ithin another logic al
c ontainer . Reg ion , site an d rack con tain ers c anno t b e

in cl u d ed in a l og ical con tain er.
NOTE : L ogic al c ontainer s c an be s et up w ith Performance Threshold s

on p age 4 13.
NOTE : See als o Logical Links on p age 36 4
Adding a Device to a Logical Container

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

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.
Removing a Device from a Logical Container

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
1. Right-click the device you want to remove from a logical container.
2. From the menu displayed select Configuration, then select Logical Containers.
The Configure Logical Containers window displays.
3. Highlight the logical container in the Configured Logical Containers list and
select the < button. The logical container is moved into the All Logical Containers
list.
362 AVIAT NETWORKS

4. Select Apply.
5. To save the changes and close the Configure Logical Containers window, select
OK.
Renaming a Logical Container

You can change the name of a logical container.
Procedure
1. Within the Logical Container pane, right-click the logical container to be renamed.
2. From the right-click menu, select Rename.
The Rename Logical Container window displays.
3. Make the required changes to the logical container’s name.
Deleting a Logical Container

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 ser-
vice.
Procedure
1. Within the Logical Container pane, right-click the logical container to be deleted.
2. From the right-click menu, select the Delete option. The following message win-
dow displays:
3. Select Yes to confirm deleting the selected logical container.
614-330055-001 DECEMBER 2015 363

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

You can browse a logical link, where events from both ends of the link are displayed in a
separate Event Browser window. The Event Browser features and functionality are
described in Customizing Event Browsers on page 297.
NOTE : A logic al link is a Pr oVis ion func tion only, the devic es in the net-
w or k ar e in no w ay affec ted by a s er vic e link.
Adding a Logical Link

Logical links are created after you have set up and populated your required logical con-
tainers.
364 AVIAT NETWORKS

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.
Renaming a Logical Link

Under most circumstances, you can rename a logical link.
If a link has had its name assigned in Portal, you will not be able to rename it in ProVi-
sion. 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 selec-
ted link’s name displays.
3. Make the required changes to the logical link’s name.
Deleting a Logical Link

You can delete a logical link. Deleting a logical link does not effect the devices nor the func-
tionality of the network.
Procedure
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.
614-330055-001 DECEMBER 2015 365

3. Select Yes to delete the selected logical link.
Related Topics:
l Adding a Logical Link on page 364
l Renaming a Logical Link on page 365
366 AVIAT NETWORKS

Scoreboard Group Scenarios

This section describes scoreboard group scenarios.
l About Scoreboard Group Scenarios on page 367
l Event Management Processes on page 296
About Scoreboard Group Scenarios

The Scoreboard is the most convenient way to monitor a group of radios or the entire net-
work. 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:
l Add and remove Scoreboards from the group
l 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:
614-330055-001 DECEMBER 2015 367

l A mobile backhaul network, located close to international sporting events.

l Sites where communications down can mean loss of revenue, for example,
share markets.
l 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 com-
munications, 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.

l Viewing a Scoreboard Group on page 368
l Creating a Scoreboard Group on page 369
l Editing a Scoreboard Group on page 370
l Deleting a Scoreboard Group on page 370
l Adding a Scoreboard on page 370
l Editing a Scoreboard on page 373
l Deleting a Scoreboard on page 373
l Opening an Event Browser from a Scoreboard on page 374
Viewing a Scoreboard Group

There are several ways you can view event activity within ProVision; tree and map view-
ers, 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
1. From the tool bar, select the Saved Scoreboard Groups icon .
2. From the drop-down list displayed, select the Scoreboard group required.
The Scoreboard Group window with the latest event summaries displays.
368 AVIAT NETWORKS

Related Topics:
l Creating a Scoreboard Group on page 369
l Editing a Scoreboard Group on page 370
l Deleting a Scoreboard Group on page 370
Creating a Scoreboard Group

When a new Scoreboard group is created, by default a Scoreboard showing all active
events displays.
Procedure
1. From the tool bar, select the New Scoreboard Group icon . The new Score-
board 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. To save the Scoreboard group, select Save. Enter the name for the Scoreboard
Group and click Save.
5. The Save As window closes and the Scoreboard Group window displays.
614-330055-001 DECEMBER 2015 369

Editing a Scoreboard Group

Editing a Scoreboard group can involve any of the following: adding, modifying, or delet-
ing Scoreboards within the Scoreboard group.
Procedures
Editing a Scoreboard group involves:
l Editing a Scoreboard on page 373
l Deleting a Scoreboard on page 373
Deleting a Scoreboard Group

You can delete a Scoreboard group when you no longer need to monitor the events from
particular sites or radios.
Procedure
2. From the list of Scoreboard groups displayed, select the Scoreboard group to be
deleted. The Scoreboard Group window displays.
3. From the Menu Bar, select File > Delete. The Delete window, listing all the Score-
board 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.
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 mech-
anism to modify filters for each Scoreboard. Each Scoreboard has its own filter that
defines the events it uses to calculate its event count.
370 AVIAT NETWORKS

See Event Browser Filter Values on page 319 for information on how to set the filters.
Procedure
To add a Scoreboard:
1. From the tool bar, select the Saved Scoreboard Groups icon.
2. From the list of Scoreboard groups displayed, select the Scoreboard group to which
the Scoreboard is to be added. The Scoreboard Group window displays.
3. Select the New Scoreboard icon.
4. Select the Settings icon . The Scoreboard Settings window displays.
5. In the Name field, type a descriptive name.

6. Select the Style drop-down arrow, and select the chart type in which Scoreboard
events displays.
614-330055-001 DECEMBER 2015 371

7. To save your changes and close the window, select OK.
8. To set up the Scoreboard filters, select the Filters icon . The Filters window
displays.
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.
372 AVIAT NETWORKS

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

l To change the filter options, select the Filters icon.
l 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.
Deleting a Scoreboard
Consider carefully before deleting a Scoreboard from a Scoreboard Group. The Score-
board, or the Scoreboard settings, may be useful in the future.
Procedure
To delete a Scoreboard:
614-330055-001 DECEMBER 2015 373

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 Scoreboard’s top right corner.
4. Select the X in the top right corner of the Scoreboard group.
The Scoreboard modified dialog window displays.
5. To delete the Scoreboard group, select Yes.
Opening an Event Browser from a Scoreboard

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 sever-
ity, 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 win-
dow title reflects the Scoreboard name - All Alarms.
Figure 6-8. Event Browser Opened Via a Scoreboard
Procedure
374 AVIAT NETWORKS

2. From the drop-down list displayed, select the Scoreboard group required. The
Scoreboard Group window displays.
3. To view events for an entire Scoreboard, select the Launch Event Browser icon, loc-
ated in the left corner of the Scoreboard. An Event Browser window opens, dis-
playing 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.
614-330055-001 DECEMBER 2015 375

Chapter 7. System Diagnostics
and Reports
ProVision provides system diagnostics to enable you to find and locate system prob-
lems. 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 view-
ing an event’s history and probable cause, using diagnostics for XP4 radios, analyzing
performance data and launching the specific radio craft tools.
Your ProVision security access level determines your access to system diagnostics. If you
cannot access system diagnostics, and you think that you should, discuss this with
your system administrator.
ProVision also provides reports for Eclipse radios. These allow you to monitor Eclipse
radio functionality, and to save and review radio data to improve performance or share
information with clients.
l Using System Diagnostics on page 378
l About ProVision and Craft Tools on page 380
l Diagnostic and Performance Trends Analysis Procedures on page 381
l Craft Tools and Diagnostic Controls on page 417
l Device and Network Reports on page 457
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.
614-330055-001 DECEMBER 2015 377

CHAPTER 7. SYSTEM DIAGNOSTICS AND REPORTS
Using System Diagnostics

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

System Diagnostics includes the following functions:
l Performance Data for:
l G.826
l G.828 (TRuepoint radios)
l RSL/RSSI
l Ethernet Bandwidth
l Craft Tools, including:
l Configuration of radio networks, frequencies, and
tributaries
l Radio fault diagnostics for loop backs, protection
switching, and device resets
l TNet Craft Tool and Diagnostics
l XP4 Craft Tool and Diagnostics
l Event Properties
l Diagnostics for:
l Constellation
l CAU
l DVA
Equipment Malfunctions vs. Path Degradation

An equipment problem is typically not intermittent. If it is not intermittent, the radio’s
Event Browser or the event’s properties show an alarm that has been raised and not
378 AVIAT NETWORKS

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 mod-
ulation 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.
614-330055-001 DECEMBER 2015 379

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 417.
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 radio craft tool. Both have history and performance screens that
enable you to view traffic error performance measurement. ProVision versus Portal on
page 380 lists how ProVision and Portal differ and in which circumstances to use Portal
or the craft tool.
Table 7-1. ProVision versus Portal
ProVision Craft Tools (Portal)

ProVision is network focused. Portal is focused on an Eclipse Terminal
You can view the history and performance link or an Eclipse Node and its links.
trends of one to many radios within the You can view the history and performance
network. trends of one radio.
You can determine if the problem is net- You can analysis and diagnose the events from
work wide, a group of radios or an isolated one radio.
radio. For example, a weather front with Typically the craft tool’s loopback diagnostics
heavy rain is moving across the country. are used to find faulty equipment.
Using the history you can view the per- The data available is short term only, that is,
formance affected links and know the prob- limited to what is stored in the radio.
lem is temporary and not equipment
related because it is happening to many Single task affecting a single radio.
links.
Long term data is available from the ProVi-
sion database.
ProVision performs bulk tasks such as col-
lecting inventory data.
380 AVIAT NETWORKS

Diagnostic and Performance Trends

Analysis Procedures
The diagnostic and performance trends analysis procedures are grouped under the fol-
lowing categories:
l Circuit Diagnostics Feature on page 381
l Data Collection on page 388
l Ethernet Performance Data Collection on page 393
l Performance Features on page 404
l Craft Tools and Diagnostic Controls on page 417
l TNet Diagnostics on page 429
l Diagnostic Controls for Selected Devices on page 446
Circuit Diagnostics Feature

The circuit diagnostics feature allows you to diagnose problems within a circuit and isol-
ate 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 dif-
ferent sections of the circuit. The duration of the diagnostic test can be set for a specific
length of time to minimize network disruption.
NOTE : O nly Ec lips e r adios s uppor t the c ir c uit diagnos tic s featur e.

l Circuit Diagnostic Window on page 381
l Setting Up a Circuit Diagnostic Test on page 384
l Circuit Diagnostic Options on page 386
Circuit Diagnostic Window

This figure illustrates a Circuit Diagnostics window for a three-radio circuit. The com-
ponents of the Circuit Diagnostics window are defined below.
614-330055-001 DECEMBER 2015 381

See Setting Up a Circuit Diagnostic Test on page 384 for an actual example on how to
set up a circuit diagnostic test.
Figure 7-1. Circuit Diagnostic Window
Table 7-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 addi-
tional information.
Radio - A radio can be a repeater / node or a ter-

minal. 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 Loop-
back. 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.
382 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 fig-
ure 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 (Trib-
utary) 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 cir-
cuit.
Selected Circuit
Select a circuit to undergo diagnostics from the drop-
down menu.
PRBS Test G.821 Data

G.821 is widely used for performance measurements
in E1/DS1 networks. The figure to the left shows the
measured performance for a circuit undergoing a test.
Refer to the table below for a description of the test
parameters.
Table 7-3. Description of the G.821 Data From a Circuit Diagnostics Test
Parameter Description
Elapsed Seconds Seconds that have elapsed since the beginning of the dia-
gnostic test.
Available Seconds Total available time during a fixed measurement interval.
Unavailable Seconds Total unavailable time during a fixed measurement interval.
Bit Error Count Total number of bit errors during a fixed measurement inter-
val.
Bit Error Count Ratio The ratio of bit error counts to the total available time dur-
Seconds ing a fixed measurement interval.
614-330055-001 DECEMBER 2015 383

Parameter Description
Errored Seconds A count of the number of errored seconds since com-
mencement of the test. An errored second is a one-second
period with one or more errored bits.
Errored Seconds Ratio The ratio of errored seconds to the total available time dur-
ing a fixed measurement interval.
Severely Errored Seconds A count of the number of severely errored seconds since the
commencement of the test. A severely errored second is a
one-second period which has a bit error ratio greater than or
equal to 1 x 10-3.
Severely Errored Seconds The ratio of severely errored seconds to total available time
Ratio during a fixed measured interval.
NOTE : Set t ing Up a C ircu it Diagnost ic Test on p age 384
Setting Up a Circuit Diagnostic Test

To set up a circuit diagnostic test:
1. Open up the Circuits tab. Right-click the selected circuit and select Circuit Dia-
gnostics.
2. The Circuit Diagnostics window displays.
3. Select the DAC unit where the loopback test is planned to originate. The available
controls appear in the Controls panel. Select a device within the circuit to display
the available controls for that device.
4. Select PRBS Link Test to add it to the DAC device.
384 AVIAT NETWORKS

5. Select the type and location of loopback. In this example, A Bus Loopback is selec-
ted on another radio in the circuit. To perform this operation, select the node by
selecting the name of the radio.
The available control (in this case, the BUS Loopback) displays.
6. Select the BUS Loopback control to add it to the circuit test.
7. Select the Apply button to initiate the circuit diagnostics test.
8. Select Yes to open the Diagnostic Safety Timer window:
614-330055-001 DECEMBER 2015 385

9. Select OK to accept the default 60-second test.

l 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.
l An “Errors detected” message appears if there are errors.
l The timer in the bottom right corner counts down the time remaining for the
test.
l The information is updated every 10 seconds while the test is running.
NOTE : C ircu it Diagnost ic Op t ions on p age 386
Circuit Diagnostic Options

The various options for performing a circuit diagnostic test are listed in the table below
as they appear in ProVision:
Table 7-4. Circuit Diagnostic Test Options
386 AVIAT NETWORKS

Circuit Diagnostic Options ProVision Set-up

Circuit segment test on a circuit
within a network.
or
or
or
Circuit end-to-end test.
or
NOTE : Diagnost ic and Performance Trend s Analy sis Proced u res on

p age 381
614-330055-001 DECEMBER 2015 387

Data Collection
This section covers the following details:
l Daily Performance Data Collection on page 389
l Enabling 15-minute Performance Data Collection on page 390
l Enabling 15-Minute Ethernet Data Collection on page 393
l Changing Device Data Collection Status on page 392
Introduction
Background G.826 and G.828 error performance data is automatically collected and
stored on a per radio basis. The data is summarized within bins to provide an historical
presentation of performance. This data collection does not affect traffic.
All radios are summarized in daily bins; most radios also have a 15-minute bin option.
Ethernet radios have a 15-minute bin option that collects Ethernet data. 15-minute bins
provide seven days of data; the daily bins provide one month of data.
ProVision automatically tracks device-dependent RSSI and performance data on most
Aviat Networks devices:
l Performance monitoring is carried out in accordance with CB-149, G.826
performance specifications, also contingent on device type.
l 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 7-5. Radio Specific Data Collection Details
Device Type Information

Altium MX 2+0 Both A and B side register data (G.826 and RSSI) is col-
lected.
Protected XP4 Configuring a Protected XP4 variant for data collection,
automatically configures the XP4 radios it manages.
Eclipse INU Can support up to 3 radio paths with a standard chassis,
and up to 6 paths with an expanded chassis con-
figuration. You can select on which of the available radio
links, data collection is enabled. Also collects TX power
(i.e., ATPC achieved output power).
XP4 radio Tracks both G.821 and G.826 performance data.
388 AVIAT NETWORKS

Device Type Information

TRuepoint 5000, 4040, Performance data (error ratio and error rate values) are
4000, and 6400 collected from “current value” MIB objects without any
Constellation additional processing. The performance value presents
Microstar the values sampled from the radio at the end of each bin
period; these sampled values can be viewed as a 15-min
TNet or daily bin.
Velox
Sagem-Link
SII SNMP Does not support daily registers, so ProVision artificially
Altium Radios creates daily registers by reading all 96 15-min bins once
ADR each day, and aggregating them into a single daily bin.
Communication problems with an Eclipse radio may result in a gap in collected per-
formance data. ProVision provides for daily performance data recovery when this hap-
pens. If a daily performance data poll fails, on the next successful daily poll for that
device the server also attempts to read the data that was missed the day before. For
example, if collection fails on Wednesday, if the server successfully collects on Thursday
it will also attempt to read Wednesday’s data.
Daily Performance Data Collection

When a device is managed in ProVision, daily performance data collection is auto-
matically 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 data-
base 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 pro-
cessor loading and NMS channel restrictions. Because of this, the collection of the data
from the bins is staggered over a 24 hour period.
Figure 7-2. Eclipse Device Performance Data Collection and NBI Behavior
614-330055-001 DECEMBER 2015 389

1. Each Eclipse device creates a daily bin file at 12:00 midnight for that day. In this
example, a block of data we will call “Sunday bin” (blue) is created at the end of the
day at 12:00 midnight.
2. For this example, let’s assume a network operator enables daily data collection at
00:00 am on Monday.
A performance bin file with a time stamp for “Sunday midnight” is created in the
database when ProVision reads the data from the first device on Monday.
3. From 00:00 am on Monday, ProVision starts collecting the “Sunday bin” data col-
lection 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 mid-
night.
6. On Tuesday, ProVision begins the “Monday bin” data collection from the Eclipse
devices. A performance bin file with a time stamp for “Monday midnight” is created
in the database when ProVision reads the data from the first device on Tuesday.
7. Again, from 00:00 am on Tuesday, ProVision starts collecting the “Monday bin”
data collection from all the devices. The bins are written to the ProVision database,
until all bin devices are read and recorded.
8. ProVision writes the “Monday bin” data to the NBI files at the same time as it
writes to the ProVision database.
As long as data collection is enabled, ProVision continues to collect the previous day’s
daily bin data.
This procedure applies to the performance data that is stored in bins on the device.
For many devices performance collection is based on real-time counts read from the
device. In this case ProVision only creates the first performance 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.
NOTE : Any time the Pr oVis ion Ser ver is r e-s tar ted, the daily and 15 min
per for manc e data c ollec tion is als o r e-s tar ted. Us ing the above
example, if the Pr oVis ion Ser ver is s topped at 7:00 pm on Tues day even-
ing, the “Monday bin” data c ollec tion c eas es and all c ollec ted data for
Monday is los t. If the Pr oVis ion Ser ver is s ubs equently r es tar ted, the
“Monday bin” data c ollec tion is r es umed. The data c annot be view ed until
the end of the day on Tues day at 12:00 midnight.
Enabling 15-minute Performance Data Collection

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
390 AVIAT NETWORKS

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 dis-
plays on the device’s icon in the Tree and Map Viewer. Within 15 minutes, the first set
of data is available for the History and Performance Trends windows.
NOTE : All devic es have Radio 15-Minute Per for manc e Data c ollec tion
available. The follow ing devic es als o have Ether net 15-Minute Per -
for manc e Data c ollec tion: Ec lips e DAC G E, DAC ES, IDU GE, IDU ES, and
IDU SPE devic es . See Enabling 15-Minu t e Et hernet Dat a C ollect ion on
p age 39 3.
CAUTION: 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 avail-
able radio paths. The Eclipse INU can support up to 3 radio paths, and the Eclipse
INUe up to 6 paths.
Procedure
1. Select the device:
Device Type Required Action
Protected XP4 radio Right-click the container XP4 radio icon.
Eclipse Node - Expand the Eclipse Node to see link

icons.
- Right-click the required link icon.
Other Aviat Networks Right-click the radio icon.
devices1
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 icon and 15-min data collection is
enabled on the radio.
1For DXR 100 &700 radios, access the 15-minute data via the DXR NET craft tool.
614-330055-001 DECEMBER 2015 391

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.
Changing Device Data Collection Status

From the Performance Data Collection screen, you can do the following:
l View the performance data collection status, daily and 15-minute, for all the
network devices.
l Change the daily, radio 15-minute, and Ethernet 15-minute performance data
collection status for individual devices.
l Change the daily data collection start time for the entire system.
Procedure
To view/change a device’s performance data collection status:
1. From the main menu, select Performance > Data Collection.
The Performance Data Collection window displays.
2. To display devices for a container, use the +. The links and link details display.
392 AVIAT NETWORKS

3. To change a device’s performance data collection status, highlight the device,

make the required changes to the check boxes, and select Apply.
4. To change the daily data collection start time, change the value for Collect daily
data at. Select whether the data collection start time is AM or PM. Then, select
Apply.
Diagnostic and Performance Trends Analysis Procedures on page 381
Ethernet Performance Data Collection

The Ethernet Data Collection feature is available for Eclipse IDU GE, IDU ES, or IDU
SPE radios that have DAC ES or DAC GE plug-ins installed. It is also available for the
following devices:
l CTR 8300, 8440, 8540, 8611
l WTM 3200, 3300, 6000
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.
Enabling 15-Minute Ethernet Data Collection

The following devices also have Ethernet 15-Minute Performance Data collection: Eclipse
DAC GE, DAC ES, IDU GE, IDU ES, and IDU SPE devices.
To view the Ethernet performance data, you must first enable Ethernet 15-minute per-
formance data collection on the selected DAC plug-in, then allow some time to elapse
for ProVision to collect some meaningful data.
Procedure
1. Select the device.
Eclipse IDU GE, IDU ES, IDU SPE Right-click the radio or plug-in icon.
Device
614-330055-001 DECEMBER 2015 393


DAC ES, DAC GE plugins - Expand the Eclipse Node so the plug-in icons
are displayed.
- Right-click the required plug-in icon.
A device-dependant pop-up menu displays, as shown for an Eclipse DAC GE.
2. Ensure that the Radio 15-min Performance Data is active. See Enabling 15-minute
Performance Data Collection on page 390.
3. To enable 15-minute Ethernet data collection, select the Ethernet 15-min Per-
formance Data item. The radio icon is updated with the icon and Ethernet 15-
min data collection is enabled on the radio.
4. To disable the Ethernet 15-min Data Collection, de-select the Ethernet 15-min Per-
formance item. The icon is removed, and Ethernet 15-min data collection is dis-
abled for this radio.
NOTE : Us e the Sear c h func tion to quic kly dis play the r adios that have
15-minute r adio or ether net data c ollec tion enabled.
Viewing Ethernet Performance

To view the Ethernet Performance features for a DAC, DPP plug-in, or WTM 6000:
1. Right-click the selected plug ins or modules, and select Performance > Ethernet
from the drop-down menu. Note: You can select multiple ports from multiple plug-
ins / modules, up to a maximum of 10 ports.
2. The Ethernet Performance window displays.
394 AVIAT NETWORKS

NOTE : For an Ec lips e devic e that inc ludes DAC GE3, extr a per for manc e
data dis plays .
Table 7-6. Ethernet Performance Window Details
Item Description
Summary Graphs These graphs show a thumbnail-sized summary of the data col-
lected 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 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.
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.
614-330055-001 DECEMBER 2015 395

Item Description
Summary Parameters Select the parameters to be displayed from the list in the Para-
meters tab on the left side of the screen. You can search for Avail-
able Parameters by Keyword or by the drop-down menu
options.
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.
Selected items display with a key at the bottom of the graphic dis-
play:
Chart Options Select how you want the chart to display:

Show Points
Log Scale
Graphical Tabs This tab displays the graphical data for the selected DAC device.
The buttons on the right side of the window allow you to select dif-
ferent sets of data:
Expanded View - 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.
396 AVIAT NETWORKS

Item Description
Graphical Tab - Packet Types Select the Packet Types button to display the three types of pack-
ets (Unicast, Broadcast, Multicast) in a pie chart and show their rel-
ative numbers as a total number of packets in and packets out for
each individual port and channel.
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 DECEMBER 2015 397

Item Description
Graphical Tab - Throughput and Select the Throughput button to display a line graph of both the
Errors receive and transmit throughput for each individual port and chan-
nel.
Raw Tab Select the Raw tab to display the raw data for the 15-minute and
daily data collection.
- Port / Channel Button - (Port A, Port B, Port C, Port D,

Channel 1, Channel 2) to display the raw data for that par-
ticular port or channel
- Export Button - Allows you to export the data to a .txt file.
398 AVIAT NETWORKS

Item Description
Raw Tab Data Raw Data includes data columns for the following values:
In and Out 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 Discards
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
Out Bytes: 64, 127, 255,511, 1023
Out Dropped Q7-Q0
Out Dropped Octets Q7-Q0
In Jabbers
In Filtered
Out FCS Errored
Collisions
NOTE : For c ons is tenc y w ith Ec lips e, Pr oVis ion pr es ents the CTR queue
number ing for the Per Q ueue Ether net Per for manc e Par ameter s ( Out
Dro pped , Out Dro pped Oct et s , Out Passed & Out Passed Oct et s ) as
Q 0 to Q 7, w her eas CTR Web Por tal and CL I inter fac e pr es ent as Q 1 to
Q 8.
Ethernet Bandwidth Utilization

ProVision users can view the ethernet bandwidth use for:
l CTR 8300, 8440, 8540, 8611
l Eclipse regions and containers
l Eclipse devices, including DAC and DPP plug-ins
l Eclipse circuits
l WTM 3200, 3300
The Ethernet Bandwidth Utilization screen displays an overview of the throughput band-
width 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.
614-330055-001 DECEMBER 2015 399

Normally, users select a Logical Link network or set of circuits to view. Data trending
can be applied to the data.
Ethernet Bandwidth Utilization displays performance data for enabled ports and chan-
nels. Data collection processes data for all enabled ports and channels. For example, if a
port was operated for three days and then disabled, the data from the port’s enabled
period would still be displayed, but no additional data would be saved.
CAUTION: If you select a large network to view, it takes time to generate the Eth-
ernet 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. Right-click the selected item or device. In the right-click menu, select Per-
formance > Ethernet Bandwidth from the drop-down menu.
2. ProVision retrieves the ethernet performance data from the server cache. While the
data is downloading, the data status displays in the lower left of the screen.
3. The Ethernet Bandwidth Utilization screen displays with its data for the device.
4. In the Table view, you can:

l Right-click on a circuit, and use the right-click menu to view additional
performance data for the circuit.
l Note the color of the data row for a circuit; these colors match the system’s
performance threshold settings.
5. To change the display from a table to a graph, click on the Show Details button. A
message displays, showing the status of the graph as it is built.
400 AVIAT NETWORKS

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:
l 15 Minute - Screen displays 15 minute performance data, for a time range of 15
minutes to 7 days.
l Daily - Screen displays daily performance data, for a time range of 1 week to 12
months.
l Use the Time Scale slider to minimize or maximize the time range of the data
displayed.
l Hide Zero Values - Check this box to hide zero-value results in the table.
8. You can change the data in the graph display to be either% of utilization or num-
ber of Mbps. Click the Show Mbps or Show% button to change the option.
614-330055-001 DECEMBER 2015 401

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 Ascend-
ing/Descending buttons to set up your main three sorting criteria.
10. In the Bandwidth Utilization graph, you can adjust the data view. Check the
Show Full Scale box to view the% Utilization range from 0 to 100%. Uncheck this
box to view only the minimum and maximum values in the used range for the %
Utilization.
11. You can also set up values to view Data Trending. Click on the Trending tab on
the Graph and set up the statistical values to apply. See the Feature table below for
details.
12. To save the Ethernet Bandwidth Utilization data, go to the File menu and select
the Save option you want:
l Save or Save As to save the data setup for future use in this screen.
l Save to File to save the data as a semicolon-delimited text file.
13. Click Close to close the screen.

The features of the Ethernet Bandwidth Utilization screen are listed below.
402 AVIAT NETWORKS

Feature Description
Time Scale The Resolution frame contains the slider 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.
- 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.
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
and Show Points.
614-330055-001 DECEMBER 2015 403

Feature Description
Trending A Trend Line represents a trend, the long-term movement in time series data. Trending
shows whether a particular data set has increased or decreased over the reporting period .
A trend line position and slope is calculated using statistical techniques, such as linear
regression and power regression.
In this tab on the Graph view, you can select the values for the Trending view:
- Linear Regression or Power Regression
- Weeks Forecast
- Data to apply from the drop-down menus: Rx RAW, Tx RAW, Tx Trending, or Rx
Trending. Tx/Rx RAW are the general Tx and Rx values that you see in the Ethernet
Performance window, displayed as % Utilization and Mbps.
Click the Apply button to add Trending to your graph.
Show/Hide Click this button to Show or Hide the data graph.

Close Click this button to close the screen.
Performance Features
l Performance History on page 404
l Performance Trends on page 409
l Performance Thresholds on page 413
Performance History
The performance history feature allows you to quickly and efficiently determine if there
are performance problems in your network. This feature also correlates collected per-
formance data with Events occurring within the same period of time. The performance
history feature is supported in any device that collects performance data .
404 AVIAT NETWORKS

Eclipse Link MicroStar

Eclipse IDU DART
CTR 8300, 8540, 8611 Velox
XP4 TNet
Altium/ADR TRuepoint: 5000, 4000, 4040, 6400, 6500
NOTE : Per for manc e His tor y is c r eated us ing daily per for manc e data
fr om the Pr oVis ion databas e. This inc ludes invalid data, as an example of
per for manc e pr oblems . Daily per for manc e data in the databas e is
r equir ed for Per for manc e His tor y output.
NOTE : TRuepoint 6500 r adios have a s pec ific Per for manc e His tor y dis -
play. This is des c r ibed in detail in this s ec tion.
Procedure
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 The performance history for the selected device displays.
The features of the standard Performance History window are listed below:
Feature Description
Resolution Select 15-Minute or Daily to display the desired level of detail for the data.
614-330055-001 DECEMBER 2015 405

Feature Description
Graph Summary bar The graph summary bar is a represents all the performance data that has been
collected for the selected device. It has features that allow you to quickly select a
range of data and display it in the Graph View or the Report View.
Place the cursor at any point along the graph summary bar and a pop-up box
appears which indicates the date and time at any point along the graph sum-
mary 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 per-
formance 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.
G.826 or G.828 Data The Graph View displays the G.826 or G.828 performance data for three types
of data: Errored Seconds, Severely Errored Seconds, and Unavailable Seconds.
These three types of performance data are a good indication if there is a prob-
lem 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.
406 AVIAT NETWORKS

Feature Description
Receive Signal Level You can also view the RSL (receive signal level) for any time period from the
(RSL) 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.
Report Select Report to view the data as a report.

View The Report Data Range feature allows you to select a portion of the per-
formance 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.
614-330055-001 DECEMBER 2015 407

Feature Description
Event The report view also displays an Event Browser that lists the events associated
Browser with the selected device that have occurred during the selected Report Data
Range. This feature is a very powerful troubleshooting tool that helps you narrow
down the cause of faults in your network.
Save / The Save button allows you to save the performance history data to a text file.
Print 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.
Close Closes the Performance History window.
TRuepoint 6500 Performance History Window

The TRuepoint 6500 Performance History window differs from the standard Per-
formance History window in several ways.
408 AVIAT NETWORKS

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.
l RLM = Receiving Level of Main Receiver.
l RLSD = Receiving Level of SD Receiver.
Related Topics:
l Performance Trends on page 409
Performance Trends
The performance trends feature allows you to view trends in the collected performance
data for a device by displaying the data in both graphical and tabular form. You can
select which parameters you would like to display, as well as print and save the data for
processing in other applications, such as MS Excel.
The performance trends feature is supported in any device that collects performance
data.
614-330055-001 DECEMBER 2015 409

Altium Radwin WinLink

Constellation (only 1000, 2000
3DS3, 4DS3, and SPECTRUM II
155mbit) SNMP
CTR 8300, 8540, 8611 TNet
DART TRuepoint: 5000,
DVM 4000, 4040, 6400,
Eclipse 6500
LE3000, LE3200 Velox
MicroStar XP4
The type of data collected varies for each device. However, it typically includes:
l G.826/G.821 performance statistics
l RF power performance, including RSL and TX power
Procedure
1. To open the Performance Trends screen:
l For most devices, navigate to the device in the Physical Tree Viewer. Right-
click it and select Performance > Trends.
l 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.
l 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.
l For an RF link, go to the Physical Map view. Right-click on the RF link in the
Map to show performance trends for both ends of the RF link.
2. The Performance Trends window for the selected device or link displays.
410 AVIAT NETWORKS

The features of the Performance Trends window are listed below:

Feature Description
Parameters Pane Select the parameters to be displayed from the list in the Parameters
tab on the left side of the screen. You can search for Available Para-
meters by Keyword or by the drop-down menu options.
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.
614-330055-001 DECEMBER 2015 411

Feature Description
Chart Tab The Chart tab displays the data points for the selected parameters.
The selected parameters appear as color-coded data points in the chart
and in an automatically-generated legend. You can also adjust the lay-
out of the graph using the Chart Options.
Print Chart From the menu bar, select File > Print Chart to print the currently
displayed chart.
At the bottom of the screen, select Visible Data to select the days or
time increments of data to view in the chart.
Select the Data Tab to display the raw data for the selected para-
meters. You can export the data using the Save Data feature.
Select the Graph Tab to return to the graph view.

Save Data From the menu bar, select File > Save Data to save the data as a
semicolon-delimited text file.
412 AVIAT NETWORKS

Performance Thresholds
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 .
CTR 8300, 8440, 8540 XP4
Eclipse Link Altium/ADR
Eclipse DAC DART
Eclipse IDU Velox
Eclipse INU and INUe TNet
TRuepoint: 4000, 4040, MicroStar
5000, 6400, 6500
WTM: 3100, 3200, 3300
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:
Logical Con-
Root Region Site Rack
tainers on page
359
Procedure
1. Right-click the selected device or container and select Performance Thresholds
from the drop-down menu.
2. The Performance Thresholds window for the selected device or container displays.
l If a non-Eclipse radio is selected, the left panel lists only the device name.
l If an Eclipse radio is selected, the left panel lists the Eclipse radio plus all of
the possible Eclipse plug-in devices.
l If an Eclipse plug-in is selected, the left panel lists only the selected plug-in.
l If a container is selected, the left panel lists all devices that support the
performance threshold feature.
614-330055-001 DECEMBER 2015 413

3. Select the required device or plug-in. The central panel lists the alarms associated
with the selected device/plug-in.
l Select the 15-Min button to show/hide the alarms for radio 15-minute data
collection.
l 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.
l Select the “+” (add) button to add a new performance threshold.

l Select the “-” (remove) button to remove an existing performance threshold.
l 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:
l Event Description- Enter a name for the newly-created performance threshold.
l Trigger Value - Enter the number of times the alarm must occur before the
performance threshold is triggered.
414 AVIAT NETWORKS

l Severity - Select a severity level from the drop-down menu.

l 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 repeat-
ing 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 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:
l TX Level Threshold Seconds
l TX Level Max (dBm)
l 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 Per-
formance Threshold settings in several ways.
614-330055-001 DECEMBER 2015 415

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 chan-
nels. This is done because, when a TRuepoint 6500 radio is functioning correctly, the
Protection channel is not being used, and its thresholds are zero.
You need to set the Protection values for the Performance Thresholds to zero. Set the
Working channels to your desired performance threshold values.
416 AVIAT NETWORKS

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:
l List of Craft Tools on page 417
l Launching a Craft Tool on page 419
l WMT Craft Tool on page 421
l TNet Web Craft Tool and Diagnostics on page 424
l Diagnostic Controls for Selected Devices on page 446
The majority of Aviat Networksdevices can be accessed via a specific craft tool. Certain
devices are accessed via diagnostic controls. Non-Aviat Networks devices can be
accessed via a Telnet or browser session.
NOTE : The s pec ific s of how to us e eac h c r aft tool ar e doc umented in the
r elated devic e manual or online help.
List of Craft Tools

This table lists the devices, associated craft tools and where to access help information.
Table 7-7. Aviat Networks Devices and Related Craft Tool
Device Craft Tool Craft Tool Documentation and Notes

Eclipse Portal Eclipse User Guide (P/N 260-668066-001)
CTR 8300 and CTR Portal CTR Portal User Manual
CTR 8540
CTR 8611 ProVision INM ProVision INM user documentation suite (multiple manuals)
260-668241-001
TRuepoint TRuepoint Web TRuepoint 5000 & 4040 6-38 GHz Operator’s Interface (P/N
CIT IMN-90303-E06)
TRuepoint 6400 & 6500 Operator’s Interface (P/N IMN-907004-
E01)
WTM 3100 ePortal ePortal User Guide
WTM 3200
WTM 6000
MicroStar MicroStar Web MicroStar Operator’s Interface. Note: Only supported on Win-
CIT dows XP and Windows 2003 platforms
614-330055-001 DECEMBER 2015 417


Constellation FarScan FarScan for Windows Instruction Manual (P/N IMN-006120-E11),
DVM also see Diagnostic Controls for Selected Devices on page
DVA 446.
CAU
MegaStar
All Altium WMT Online help is available from within the craft tool. A brief
ADR 2500 description is in WMT Craft Tool on page 421.
ADR 155c
DXR DXR NET DXR NET NMT Installation and Operation Manual
(PN IOM-NMS-2/2.4). Note: Only supported on Windows XP
and Windows 2003 platforms, the DXR Proxy client does run on
later Windows versions.
Velox NCT NCT User Guide
TNet TNet Web A brief description is in TNet Web Craft Tool and Dia-
gnostics on page 424 .
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 admin-
istration access. Context-sensitive online help is available in XP
Web.
If you are using Windows XP SP2, make the following adjust-
ment to your web browser:
Open your web browser.
Select Tools > Internet Options and select the Advanced tab.
Under the Security section, select the Allow active content to
run on files on My Computer option.
E-Link E-Link Web: E-Link 1000 EXR User Interface Manual_rev_0G
Controlling and E-Link 1000LR User Interface Manual
Monitoring
Your E-Link
DART None: Dia- See Diagnostic Controls for Selected Devices on page 446 .
DVA gnostic Controls
CAU instead
LE3000/3200 Rad- CXTool See LE3000 and LE3200 Craft Tool Installation on page
win WinLink 421.
1000/2000
418 AVIAT NETWORKS


Generic device - Telnet The Launch options displayed for a generic device are dependant
- Browser 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:
l Change a radio’s configurations
l Run local and remote loopback tests to help isolate link or radio problems
l Monitor and troubleshoot system status and performance
l Switch protected radio configurations
l 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
1. From the Tree Viewer or Map Viewer, right-click the required radio.
614-330055-001 DECEMBER 2015 419

2. Select Launch <craft tool>. In this example, Launch DXR NL is selected.

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

5. Close the craft tool window.
420 AVIAT NETWORKS

LE3000 and LE3200 Craft Tool Installation

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.
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:
l Name = Craft tool name: CXTool
l Executable Path = Path to the file folder on the PC where the craft tool is
installed.
l 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

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 man-
age, 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.
614-330055-001 DECEMBER 2015 421

1. Double-click the selected radio to open the Event Browser.
2. Select the filters icon.

3. In the Filters window, check the Severity checkbox. Then, select the Information
checkbox.
The Information checkbox must be selected in order to display all events in the
WMT craft tool.
Procedure
To launch the WMT craft tool:
1. Right-click the selected radio icon. From the right-click menu, select Launch
WMT.
2. A browser window opens that displays the IP address of the radio as a hot link.
Select the hot linked address.
3. A welcome screen displays on the browser window. Select the Apply button.
(Leave the Password text box blank since a password in not required.)
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 secur-
ity level is displayed for each port.
422 AVIAT NETWORKS

6. The Shelf View is the default screen and displays a graphical representation of the
selected radio.
NOTE : The c olor -c oded s ever ity level for eac h por t (r ed = ______, yel-
low = _______) dis plays 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.
614-330055-001 DECEMBER 2015 423

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.
TNet Web Craft Tool and Diagnostics

To manage a TNet device at the craft tool level, you can either:
l Use the TNet craft tool - see Launching the TNet Web Craft Tool on page 427
l Use TNet Diagnostics on page 429
The TNet Web craft tool can be launched from within ProVision. It enables you to con-
nect to a TNet device to manage, troubleshoot and maintain the device.
424 AVIAT NETWORKS

NOTE : TNet Web r equir es Java 1. 7 to oper ate.
Depending on the device, TNet Web allows you to

l View information on the TNet radio and proxy
l Create user-defined inputs and outputs and assign severity levels
l Activate or de-activate an input or output by manually setting the state (open
or closed)
l 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.
Table 7-8. TNet Web Available Features with each TNet Device
Device Icon Device Available Features
SPECTRUM I Information, Save, Refresh
W Series and Protected Information, Save, Refresh

and W Series
Classic II Information, 4 Alarm Inputs, Save, Refresh
614-330055-001 DECEMBER 2015 425

Device Icon Device Available Features

QUANTUM and Pro- Information, 6 Alarm Inputs, Save, Refresh
and tected QUANTUM
LC Series and Protected Information, 8 Alarm Inputs, Save, Refresh

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

and M Series
M Fiber Information, 8 Alarm Inputs, Save, Refresh
SPECTRUM II and Pro- Information, 8 Alarm Inputs, 4 Alarm Outputs, Save, Refresh
and tected 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.
426 AVIAT NETWORKS

Launching the TNet Web Craft Tool

To launch TNet Web:
1. From the Tree Viewer or Map Viewer right-click the required TNet radio. Select
Launch TNet Web.
2. The TNet Web user interface window displays in the web browser.
The Information tab lists general information on the selected radio and on the TNet
Proxy device.
1. The Alarm Inputs tab and Alarm Outputs tab are only available on certain TNet
devices. If they are available, select the Alarm Inputs tab.
This tab lists the input configuration for the selected TNet radio.
See Alarm Input and Alarm Output Settings for TNet Radios on page 428 for inform-
ation on changing the input configuration.
2. Select the Alarm Outputs tab. (Available on the SPECTRUM II devices.)
614-330055-001 DECEMBER 2015 427

This tab lists the output configuration for the selected TNet radio.
See Alarm Input and Alarm Output Settings for TNet Radios on page 428 for inform-
ation 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 7-9. Alarm Input and Alarm Output Settings for TNet Radios
Item Description
Name User-defined name for the alarm input or output.
State Allows you to physically open (activate) or close (de-activate) the indi-
vidual alarm inputs and outputs.
Severity Allows you to assign a severity level to each alarm input and output:
428 AVIAT NETWORKS

Item Description
The severity options for Alarm The severity options for Alarm
Inputs are: Outputs are:
Current Status Displays the current status of the input or output.

Saves the input and output configuration to the radio.
Save
Refreshes the current screen by retrieving the current state of the
Refresh inputs and outputs from the radio.
TNet Diagnostics
l TNet Diagnostics - Protection Tab on page 430
l TNet Diagnostics - G.821 Performance Tab on page 431
l TNet Diagnostics - CB 149 Performance Tab on page 433
l TNet Diagnostics - RSSI Tab on page 434
Diagnostic tools are used when an event indicates there is a fault with a TNet radio, and
can help to determine if the fault is equipment or path related.
When Diagnostics is selected, ProVision automatically logs into the TNet radio, retrieves
the diagnostic settings from the radio, and displays them in the Diagnostics window.
614-330055-001 DECEMBER 2015 429

The diagnostic tools for the TNet radios are:

l Protection status and settings
l G.821 performance data (SPECTRUM II radios only)
l CB 149 performance data (all other, non-SPECTRUM II radios)
l RSSI (receive signal strength indication) data
NOTE : Ac c es s to the Diagnos tic s menu option is dependant on your

Pr oVis ion s ec ur ity ac c es s 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.
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 7-10. 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 trans-
mitter 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.
430 AVIAT NETWORKS

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 func-
tion.
RX Online Identifies which receive function of the protected pair is currently
online:
Online A - The Side A receive function is currently online.
Online B - The Side B receive function is currently online.
Protection Settings:
Automatic Select the Automatic checkbox to enable automatic switching. In auto-
matic 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:
l TNet Diagnostics - RSSI Tab on page 434
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 DECEMBER 2015 431

Some parameters are measured over a measurement interval; the interval ending at the
time stamp displayed in the G.821 Performance tab.
Table 7-11. G.821 Performance Parameters
Available Seconds Total available time during a measurement interval.
Unavailable Seconds Total unavailable time during a measurement interval.
Errored Seconds A one-second period with one or more errored blocks or at
least one defect.
Severely Errored A one-second period which contains at least 30% errored
Seconds blocks or at least one defect.
Total Test Seconds Total time of the measurement interval.
Degraded Minutes Number of groupings of 60 available seconds, excluding
severely errored seconds that have a BER worse than 10-6.
Time Stamp Date and time of the most recent update to one or more per-
formance counters. Date and time information displays in
the following format:
- Month, day and year (for example: Mar-06-2005)
- Time in hh:mm:ss format (for example: 17:38:21)
The various functions in the G.821 Performance tab are defined below.
Table 7-12. Functions in the G.821 Performance Tab
Reset Resets all parameters to zero and sets the time stamp to the current day
and time.
Refresh Collects the most updated values of the parameters from the radio, dis-
plays the updated values in the G.821 Performance tab, and sets the
time stamp to the current date and time.
OK Closes the TNet Diagnostics window.
432 AVIAT NETWORKS

Cancel Closes the TNet Diagnostics window without saving any changes made to
the performance parameters. Any changes are saved if the Reset,
Refresh, or Apply buttons were selected.
Apply Saves the changes made to the performance parameters without closing
the TNet Diagnostics window.
TNet Diagnostics - CB 149 Performance Tab

CB 149 is a performance standard for microwave radios. The CB 149 Performance win-
dow 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 7-13. CB 149 Performance Parameters
Single Errored Seconds The number of one-second periods with one errored
block or defect.
Multiple Errored Seconds The number of one-second periods with more than one
errored block or defect.
Severely Errored Seconds The number of one-second periods which contain at
least 30% errored blocks or at least one defect.
Frame Errored Seconds The number of one-second periods that an Out-Of-
Frame error is detected.
614-330055-001 DECEMBER 2015 433

Data Missing Indicator Contains a flag indicating the validity of performance
counter contents on Side A or Side B:
- “0” = All performance counters reflect an accurate
count.
- “1” = One or more performance counters have
reached their maximum value. When this condition
occurs, data collection is stopped and one or more
counters are reset to 0. In this instance, the operator
performs a manual reset operation from the CB-149
Frame Error Count The number of Out-of-Frame errors during a meas-
urement interval.
Total Parity Errors Contains an internal count used for calculating the bit
error rate on Side A or Side B.
Elapsed Seconds Total number of seconds that have elapsed since test
counters were last reset on Side A or Side B.
Time Stamp Date and time of the most recent update to one or more
performance counters. Date and time information dis-
plays in the following format:
The various functions in the CB 149 Performance tab are defined below.
Table 7-14. Functions in the CB 149 Performance Tab
and time.
plays the updated values in the CB 149 Performance tab, and sets the
Cancel Closes the TNet Diagnostics window without saving any changes made
to the performance parameters. Any changes are saved if the Reset,
TNet Diagnostics - RSSI Tab

RSSI is a performance standard for microwave radios. The RSSI Performance window
lists the relevant performance parameters.
434 AVIAT NETWORKS

Some parameters are measured over a measurement interval, the interval ending at the
time stamp displayed in the RSSI tab.
Table 7-15. RSSI Parameters
RSSI Low (dBm) The minimum signal strength recorded on Side A or Side B
during the measurement interval.
RSSI High (dBm) The maximum signal strength recorded on Side A or Side B
during the measurement interval.
RSSI Current (dBm) The current signal strength level on Side A or Side B.
RSSI Sample Time The total minutes during which RSSI data has been col-
lected, which encompasses the interval since RSSI data was
last reset.
Time Stamp Date and time of the most recent update to one or more per-
formance counters. Date and time information displays in
the following format:
The various functions in the RSSI tab are defined below.

Table 7-16. Functions in the RSSI Tab
and time.
plays the updated values in the G.821 Performance tab, and sets the
OK Closes the TNet Diagnostics window.
614-330055-001 DECEMBER 2015 435

Cancel Closes the TNet Diagnostics window without saving any changes made
to the performance parameters. Any changes are saved if the Reset,
Apply Saves the changes made to the performance parameters without closing
the TNet Diagnostics window.
Related Topics:
l TNet Diagnostics - Protection Tab on page 430
l Diagnostic and Performance Trends Analysis Procedures on page 381
XP4 Device Support: Craft Tool and Diagnostics

This section covers the following XP4 topics:
l Launching the XP4 Craft Tool on page 436
l Launching the XP4 Diagnostics on page 437
l Activating and Deactivating an XP4 Tributary Loopback on page 437
l Activating and Deactivating an XP4 Local Loopback on page 441
l Viewing/Changing XP4 Protection Settings on page 443
l Resetting an XP4 Radio Device on page 445
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.
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
436 AVIAT NETWORKS

opens with administration access. Context-sensitive online help is available in XP

Web.
Launching the XP4 Diagnostics

NOTE : Ac c es s to the Diagnos tic s menu option is bas ed on your Pr oVi-
s ion s ec ur ity ac c es s 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.
NOTE : L oopbac k tes ts ar e r un fr om the loc al r adio us ing tes t patter ns

gener ated by exter nally c onnec ted us er tes t equipment. Us ing a r adio
tr ibutar ies , loopbac k tes ts s end tes t patter ns thr ough either the near
end IDU or the entir e s ys tem, then ver ify the ac c ur ac y of the data being
s ent or r ec eived. The number of er r or oc c ur r enc es , if any, ar e c aptur ed
and handled by the exter nal tes t s our c e.
Activating and Deactivating an XP4 Tributary Loopback

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 loop-
back before activating a digital ODU loopback.
When you run loopback tests on the online unit, traffic is affected.
614-330055-001 DECEMBER 2015 437

Loopback Purpose
Local Tributary Loop- To locate faults in equipment and cable connections to the local IDU. The
back Local loopback does this by routing each tributary input (data from customer)
applicable to: directly to the corresponding tributary output (data to customer).
Any combination of tributaries can be configured for loopback.
2/4/8x radios The following diagram shows a local tributary loopback signal path:
16x E3/DS3 radios
Remote Tributary Loop- Remote tributary loopback tests enable you to confirm link operation with the
back aid of a connected BER test-set.
applicable to: This loopback is used for locating faults in equipment and cable connections
by connecting the transmit data stream directly to the receive data stream in
2/4/8x radios the remote IDU. It checks the functionality of the local and remote sides in
both directions.
16x E3/DS3 radios Any combination of tributaries can be configured for loopback.
The following diagram shows a remote tributary loopback signal path:
Remote SU E3/DS3 Trib- The Remote SU loopback locates faults in equipment and tributary cable con-
utary Loopback nections by looping a DS3 or E3 tributary input (data from customer) from
applicable to: the remote side to the local side of the link, checking the functionality of the
local and remote sides in both directions.
16x E3/DS3 radios The SU loopback is only available for the remote switch unit. There is no SU
loopback for the local switch unit. Customer data coming through the local
switch gets checked by the local IDU ES3/DS3 loopback.
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 To ensure the MSU is getting a signal from customer equipment. The local
Loopback MSU E3 loopback feeds the output of the multiplexer into the demultiplexer
applicable to: in the MSU, looping all tributaries between 1 and 16 at the local side.
This tributary loopback is only applicable to protected E3 radios with an
MSU.
16x E3/DS3 radios
The following diagram shows a local MSU E3 tributary loopback signal path:
438 AVIAT NETWORKS

Loopback Purpose
Local MSU E1 Tributary To ensure the MSU is getting a signal from customer equipment. The local
Loopback MSU E13 loopback feeds the output of the multiplexer into the demultiplexer
applicable to: in the MSU, looping all tributaries between 1 and 16 at the local side.
This tributary loopback is only applicable to protected E1 radios with an
MSU.
16x E3/DS3 radios
The following diagram shows a local MSU E3 tributary loopback signal path:
Procedure
To activate or deactivate a tributary loopback:
1. From the Tree Viewer or Map Viewer, right-click the XP4 radio icon. The right-
click menu displays.
2. Select Diagnostics. A Diagnostics window displays with the settings uploaded dir-
ectly 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:
614-330055-001 DECEMBER 2015 439

3. Select another tributary loopback control if the Local Loopback is not required.
4. Select the required tributary (or tributaries).
5. To activate the selected tributary loopback on the radio, select Apply. The fol-
lowing message displays.
6. To continue writing the loopback data to the radio, select Yes. The Diagnostic win-
dow is updated and shows the status as read from the radio.
NOTE : You c an only r un loopbac k on a link at a time. So you need to s top

the c ur r ently ac tive loopbac k befor e you c an s tar t 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.
440 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 fol-
lowing message displays.
If ProVision is unable to contact the XP4 radio, the following message displays.
NOTE : Act iv at ing and Deact iv at ing an XP4 Local Loop back on p age
441
Activating and Deactivating an XP4 Local Loopback

Local loopbacks help to identify which component in the radio is causing the fault. This
table describes the loopbacks available for the local radio and their uses.
In a link, the local radio is the radio nearest to the ProVision server. Conversely, the
remote radio is the far end of the link.
If a loopback is applied to the remote radio then ProVision cannot communicate with
the radio to deactivate the loopback and a service agent must be sent to the remote
radio’s site to manually deactivate the loopbacks.
614-330055-001 DECEMBER 2015 441

Local Loopback Loopback Purpose

ODU Analog To determine if the fault lies in the ODU. The loopback checks the signal processor
related analog circuits, and the microprocessor and related digital circuits in the
local ODU. The loopback does this by routing the composite data stream at the out-
put 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:
ODU RF 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 ter-
minal. 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.
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 cir-
cuitry.
The following diagram shows an ODU digital loopback signal path:
442 AVIAT NETWORKS

Procedure
To activate a local loopback:
2. Select Diagnostics. The Diagnostics window displays.
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.
NOTE : Viewing/C hanging XP4 Prot ect ion Set t ings on p age 4 4 3
Viewing/Changing XP4 Protection Settings

From the Protection Settings tab you can perform the following actions:
l View the protection type set for this link
614-330055-001 DECEMBER 2015 443

l 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)
l Change the status of the radio transmitter to force it online or offline
To guard against service interruptions, an XP4 radio link can be operated in protected
mode, providing link continuity if a fault occurs in the primary radio. A protected sys-
tem 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 anten-
nas.
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:
l Loss of lock on transmit signal
l Loss of transmit power
l Frame loss (receive),
l BER alarm
l Loss of IDU transmit signal
l DC power loss
l Cable fault
l Loss of tributary input to online IDU (for E3, DS3, and 16E1 systems)
Procedure
2. Select Diagnostics. The Diagnostics window displays.
3. Select the Protection tab. The radio’s protection details are displayed on the Pro-
tection tab.
The Protection tab fields are defined in Protection Tab Fields for the XP4 Radio on
page 445.
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.
444 AVIAT NETWORKS

Table 7-17. Protection Tab Fields for the XP4 Radio
Protection Tab - Fields Description

Protection Type A display-only field that indicates:
- The protection type of the local or remote protection switch
The protection types available for the variant XP4 radios are:
2x/4x 8x 16E1,E3,DS3
Hot Standby Space X X X
Diversity
Frequency Diversity X X X
Dual Link X
The switching mode of the local or remote Tx rocker switch
The switching mode values displayed are:
Auto The Tx rocker switch is in the Auto position and the transmitter is con-
figured 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 trans-
mitter 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 can-
not 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.
Resetting an XP4 Radio Device

Normally, you would reset individual XP4 radio components if recommended by Aviat
Networks Help Desk personnel. Resetting a IDU or ODU hardware may result in loss of
traffic. The possible reset types include:
l Local IDU and ODU
l Remote IDU and ODU
614-330055-001 DECEMBER 2015 445

l Reset NMI
Procedure
2. Select Diagnostics. The Diagnostics window displays. Select the Resets tab.
3. In this tab, select the drop-down arrow to display the radio’s devices.
4. Select the required radio device and select Reset.
5. Select Yes. to reset the selected radio device.

6. Select OK to close the Diagnostics window.
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.
446 AVIAT NETWORKS

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:
l Constellation Diagnostic Controls on page 447
l CAU Diagnostic Controls on page 451
l DART Diagnostics Controls on page 452
l DVA Diagnostic Controls on page 453
l Megastar Diagnostic Controls on page 455
NOTE : Both TNet and XP4 have both Cr aft Tools and Diagnos tic s func -
tions . See C raft Tools and Diagnost ic C ont rols on p age 4 17.
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 com-
plete details on all these diagnostic options, see the Constellation user documents.
NOTE : Cons tellation for Far Sc an has limited Diagnos tic Contr ols . Thes e
limits ar e noted for eac h Diagnos tic Contr ol option.
Procedure
To access and change Constellation diagnostic controls:
1. Right-click on the selected device. In the right-click menu, select Faults > Dia-
gnostics. The Diagnostic Controls screen displays.
2. Control status is shown through use of color:
l Green “On” = Control Active
l Green “Off” = Control Inactive
l 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.
614-330055-001 DECEMBER 2015 447

Tribs Side A and Side B Tabs
Table 7-18. Constellation Tribs Side Tab Values
Item
Tributary Loop- Enable or disable loopback controls for DS3, local or remote circuits. To
backs adjust, select Enabled or Disabled from the drop-down menu.
Tribs HLM Tab
Table 7-19. 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.
448 AVIAT NETWORKS

Protection Tab
Table 7-20. Constellation Protection Tab Values
Item
TX Online Status
LEDs Shows whether TX1 or TX2 is in operation for Side A and Side B.
Switch Con- Enables the user to switch TX traffic to the TX that is not in use. This
trol 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.
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 Enables protection locking or unlocking of TX, RX, M12, and HLM. To
adjust, select Locked or Unlocked from the drop-down menu.
M12 Standby Locks the selected M12 traffic onto the M12 Standby card.
This lock is over-ruled if the locked M12 becomes absent.
MI2 Release Switches protected M12 traffic from the Standby card back to the normal
card, if the normal card is free of alarms. If this is set to the status of
Release, the M12 Standby value should all be Unlocked.
HLM Lock Locks the selected High Level Mux (HLM) online, if the HLM is free of
alarms or not.
This lock is over-ruled if the locked HLM becomes absent.
BER Test Side A and B Tabs
614-330055-001 DECEMBER 2015 449

Table 7-21. BER Test A and B Tab Values
Item
Results Results of the BER test for a trib.
Duration Number of days, hours, minutes, and seconds of a BER test for a trib.
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 7-22. BER Test A and B Tab Values
Item
Side A and Side B Results of the CBER/UBER test for Side A and Side B.
Results
Test Duration Number of days, hours, minutes, and seconds of the most recent
CBER/UBER test.
This data is not displayed for Constellation for FarScan devices.
Start or Stop Start or Stop the CBER/UBER test.
RCS Alarm Clear Tab
Table 7-23. RCS Alarm Tab Values
450 AVIAT NETWORKS

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

The CAU diagnostic controls enable you to view and reset CAU control and alarm relay
status.
Procedure
614-330055-001 DECEMBER 2015 451

2. Select the Control Activation option:

l Global Activation on Apply
l Activate Immediately
4. To reset control relays and alarm relays, use the drop-down menus.
NOTE : The fir s t objec t in the alar m r elay is a r ead-only objec t and c an-
not be r es et.
5. To apply changes, click Apply. It takes up to 1 minute for the relay changes to be
fully applied; a progress icon displays in the lower left corner of the screen.
Table 7-25. CAU Control and Alarm Values
Item View and Change

Control Shows status of control relay connections. To adjust, select Reset or Set
Relays from the drop-down menu.
Alarm Relays 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:
l Radio device resetting.
l Local and remote tributary loopback tests used to verify tributary cable
connections, on externally attached equipment.
NOTE : L oopbac k tes ts ar e r un fr om the loc al r adio us ing tes t patter ns

gener ated by exter nally c onnec ted tes t equipment. The number of er r or
oc c ur r enc es , if any, ar e c aptur ed and handled by the exter nal tes t equip-
ment.
Procedure
To access and change diagnostic controls, and to reset the DART radio:
2. To adjust a tributary loopback, see Activating and Deactivating DART Tributary
Loopbacks on page 1.
452 AVIAT NETWORKS

3. To reset the radio, select the Resets tab. In this tab, select the drop-down arrow to
display the radio’s devices.
4. Select Reset NMI from the drop-down menu, then select Reset. A message dis-
plays:
5. To apply changes, click Apply.

To exit the screen, click Close.
NOTE : Ac c es s to the Diagnos tic s menu option is dependant on your

Pr oVis ion s ec ur ity ac c es s level.
DVA Diagnostic Controls

The DVA diagnostic controls enable you to view and reset DVA external relay status.
Procedure
To access and change diagnostic controls:
614-330055-001 DECEMBER 2015 453

2. Select the Control Activation option:

l Global Activation on Apply
l Activate Immediately
4. To reset relay controls, use the drop-down menus.
Table 7-26. DVA Controls Values
Item View and Change

MC1, 2, and 3 To adjust, select Reset or Set from the drop-down menu.
Relays
External Select the external relay option that you want to view from this drop-
Relay down menu. Then, click Refresh. The values for that option display.
454 AVIAT NETWORKS

Megastar Diagnostic Controls

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

3. To reset loopback controls, on the Tributaries tab, use the drop-down menus.
5. To refresh the data from the device, click Refresh. Wait for the data to be
updated.
Table 7-27. Controls
Item
Tributaries tab
Loopback Controls Enable or disable loopback controls for tribs.
3XDS3 Loopback Status Notes the status for each trib on each channel.
Wayside Loopback Status Notes the wayside loopback status of tribs and 3xDS3 con-
nections.
614-330055-001 DECEMBER 2015 455

Item
External Relay Select the external relay option that you want to view from
this drop-down menu. Then, click Refresh. The values for
that option display.
456 AVIAT NETWORKS

Chapter 8. Device and Network

Reports
This section includes procedures for:
l Inventory Reports on page 458
l Eclipse Fault Report on page 465
l Capacity Report on page 467
l Eclipse Security Status Report on page 488
l RF Network Health Reports on page 474
l Clock Sync Report on page 490
l Link Report on page 492
l Creating Custom Reports on page 498
l Scheduling Reports on page 507
614-330055-001 DECEMBER 2015 457

CHAPTER 8. DEVICE AND NETWORK REPORTS
Inventory Reports
This section describes the various options for viewing the inventory report for any of the
following device types:
l Cisco CSR-903
l CTR 8440, 8540
l E-Band E-Link
l Eclipse
l Constellation
l LE3000 / LE3200
l Radwin WinLink 1000, Radwin 2000
l Tellabs 8600
l Truepoint
l WTM 3100, 3200, 3300, 6000
l XP4
The options are:
l View and Save the Inventory Report for a Single Device on page 459
l View and Save Inventory Reports for Multiple Devices on page 462
l Eclipse Fault Report on page 465
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 net-
work for a selected radio. It displays as a free-floating window that lists information
about the radio, including:
l General information such as the device name, site name, IP address and
device type
l Active license certificate details
l 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.
458 AVIAT NETWORKS

NOTE : For mor e infor mation on the Ec lips e Node inventor y details , s ee
the Ec lips e Us er Manual, Por tal Ins tallation and Configur ation, Ec lips e
Configur ation > L ic ens ing.
For Cons tellation for Far Sc an, the Inventor y Repor t is limited and only
dis plays the Plug-Ins and Softw ar e Ver s ion.
View and Save the Inventory Report for a Single Device

You can view and save the inventory details for a single device:
View an Inventory Report for a Single Device

To view the Inventory Report for supported devices:
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. Select Close to close the Inventory Report. The data detailed in the Inventory win-
dow is listed below.
Table 8-1. Inventory Details
614-330055-001 DECEMBER 2015 459

Feature Description
Report Lists the inventory details. The inventory details for most devices include:
- Inventory Report
- General Information
- General Information
- Manufacturing Details
Some devices also include:
- Active License Certificate Details
- License Nodal Details
- License Feature Details
NOTE: The Eclipse IDUs, except for IDU ES (Connect ES), do not
have license details since the IDU has no capacity licence.
Inventory Report - Lists the day/time stamp when the report was gen-
erated. If a comment was added when the database was updated, the com-
ment appears under the day/time stamp.
Collected On - The date and time when the data for this report was col-
lected.
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 mod-
ulation) see the Eclipse User Manual, Portal, Licensing.
A default Eclipse Node License allows for installation of up to six RACs, each with a max-
imum capacity of 10xE1, or 16xDS1. Beyond this level, licenses must be purchased, which
provide an up-to capacity on a per RAC basis.
License If applicable, lists the RAC plug-in and capacity for any nodal licenses.
Nodal
Details
License If applicable, lists all featured licenses by RAC plug-in, part number, and
Feature whether or not the feature license is present (Yes or No).
Details
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 includ-
ing the time the plug-in is powered down).
Save Report Saves an inventory report as a text file.
Close Closes the Inventory window
460 AVIAT NETWORKS

Save an Inventory Report for a Single Device

You can save a device’s inventory details to a file so that you can view or print the
details at a later date.
Procedure
1. Go to the Tree or Map Viewer. Right-click the selected device icon.
2. On the right-click menu, select Reports >Inventory.
3. The Inventory Report displays.
NOTE : If ther e is no data to gener ate the r epor t, a mes s age w ill dis -
play.
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.
l HTML (.html) - Saves the information as an .html file as it appears in the
inventory window. The file name has the format: filename.html.
l Text (semicolon separated) (.txt) - Saves the information as a text file 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 file
name is:
filename_mfg.txt: Lists the radio’s Manufacturing Details.
6. Select Save. Select Close to close the Inventory window.
NOTE : Saved Inventor y Repor ts inc lude additional data; ther e ar e

c olumns for Family and Plug-In Clas s . See als o View and Sav e Inv ent -
ory Rep ort s for Mu lt ip le Dev ices on p age 4 6 2
614-330055-001 DECEMBER 2015 461

View and Save Inventory Reports for Multiple Devices

You can view and save the inventory details from a group of 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.
Procedure
1. Within the Tree Viewer, select the desired devices:
l 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.
l 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 con-
tainer.
3. Right-click a selected radios (or the selected container) to display the right-click
menu and select Inventory. The Reports Information window displays.
462 AVIAT NETWORKS

4. To set up report fields, select Report Fields from the Options menu. The
Report Fields screen displays. Go through the tree view of options on the
left. To add a field value to the report, select it in the Available Fields frame
and click the right arrow, to add it to the Selected Fields frame. When you
are done adding field values, click OK.
5. To note specific containers, regions, and devices for a report, go to the
Options menu and select Object Filter. The Object Filter window has two
tabs.
l Objects - Select object types to include
l Containment - Select specific containers or devices to
include
6. After you have selected all the values, run the report. Click the Run button.
7. Select the PDF button to save the report as a PDF file. Select the Excel
button to save the report as an Excel file.
8. To save this report, go to the File menu and select Save As. This report
configuration will be saved. To open it again, go to File - Open and select
the report name.
CAUTION: You cannot save a subset of data. You can export a subset of data to a
PDF or spreadsheet by highlighting the subset and saving the content.
9. Select Close to close the report window.
614-330055-001 DECEMBER 2015 463

NOTE : Saved Inventor y Repor ts inc lude additional data; ther e ar e

c olumns for Family and Plug-In Clas s . See als o View and Sav e t he
Inv ent ory Rep ort for a Single Dev ice on p age 4 59 .
464 AVIAT NETWORKS

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:
l General information and link configuration
l License and manufacturing
l Active events and event history
l Performance summary
The Eclipse Fault Report collects event and performance data for a specific time period
for a specific radio. You can also save the fault report as an .html or .txt file and com-
pare the event and performance data to help you diagnose problems with the radio’s per-
formance.
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.
614-330055-001 DECEMBER 2015 465

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 .txt file or an .html 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.
466 AVIAT NETWORKS

Capacity Report
The Capacity Report is a report for Eclipse, WTM 3100, and WTM 3300 devices and net-
works. It can provide a summary of the capacity configuration and utilization for a
single device, noted at a specific date and time, or summarize for multiple devices or the
entire network. This is a valuable feature in support of network capacity planning.
The Capacity report includes the following information:
l General information and link configuration
l License status
l Specific devices and their maximum, used, and spare capacity
l Performance summary
You can save the Capacity Report as an .html file or as a semicolon separated .txt file.
NOTE : Us ing this r epor t w ith the Capac ity Planning Infor mation option
r equir es an additional lic ens e. Pleas e c ontac t Aviat Netw or ks to ac quir e
this lic ens e.
Procedure
1. Right-click the device or container icon; from the right-click menu, select Reports,
then Capacity.
2. The Capacity Report window displays for the selected data.
614-330055-001 DECEMBER 2015 467

NOTE : If ther e is no data to gener ate the r epor t, a mes s age w ill dis -
play.
3. Select the Save Report button to save the report as a .txt file or an .html 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 inform-
ation on the Eclipse radio inventory details (such as capacity and modulation) see the
Eclipse User Manual, Vol IV. Portal, Licensing.
Table 8-2. Capacity Report Details
Feature Description
Capacity Report Lists the day/time stamp when the report was generated.
Generated On The date and time when this report was generated.
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, device type,
and backplane maximum and used.
Active License Cer- Lists the serial number, status (active or inactive), and licensed
tificate Details capacity for each RAC plug-in user license.
468 AVIAT NETWORKS

Feature Description
Capacity Details 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.
License Feature Lists all featured licenses by RAC plug-in, part number, and
Details whether or not the feature license is present (Yes or No).
Save Report Saves a Capacity Report as a semicolon separated file. The .txt
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 8-3. Capacity Details - Individual Radios
Feature Description
RAC The name of this RAC plug-in.
Licensed Capacity The amount of capacity licensed for this RAC.
Link Capacity The total capacity that this radio can support.
Hardware The maximum capacity that this hardware can support.
Used The capacity currently used by traffic by this plug-in.
Licensed Spare The amount of capacity licensed for the RAC spare.
Link Capacity Spare Maximum capacity of the RAC spare.
Link Capacity Unli- This indicates the capacity for unlicensed hardware. It is cal-
censed culated 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.
NOTE : See als o View and Sav e C ap acit y Rep ort s for Mu lt ip le Dev ices.
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
1. Select the Reports button to display the Server Reports window.
614-330055-001 DECEMBER 2015 469

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 cre-
ated.
3. Select the Save button for the selected report. A directory browser displays.
4. The file name is defaulted to the name you initially specified. You can also change
the file name, if required. Browse to the required folder, then select Save.
5. The information is saved as two separate text files with the data separated by
semicolons. This format allows the data to be viewed in a spreadsheet application
with the data automatically in tabular form. The two file names have the format:
l filename_lic.txt: Lists the radio’s Active License Certificate Details.
l filename_mfg.txt: Lists the radio’s 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.
7. See "Save an Inventory Report for a Single Device".
470 AVIAT NETWORKS

View and Save Capacity Reports for Multiple

Devices
You can view and save the capacity details from a group of 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.
Procedure
1. Within the Tree Viewer, select the desired devices:
l 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.
l 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 capacity details from a group of radios by selecting the con-
tainer.
3. Right-click the selected radios (or the selected container) to display the right-click
menu and select Capacity. The Reports Information window displays.
614-330055-001 DECEMBER 2015 471

4. To set up report fields, select Report Fields from the Options menu. The Report
Fields screen displays. Go through the tree view of options on the left. To add a field
value to the report, select it in the Available Fields frame and click the right arrow,
to add it to the Selected Fields frame. When you are done adding field values, click
OK.
5. To note specific containers, regions, and devices for a report, go to the Options
menu and select Object Filter. The Object Filter window has two tabs.
n Objects - Select object types to include
n Containment - Select specific containers or devices to include
7. Select the PDF button to save the report as a PDF file. Select the Excel button to
save the report as an Excel file.
8. To save this report, go to the File menu and select Save As. This report con-
figuration will be saved. To open it again, go to File - Open and select the report
name.
472 AVIAT NETWORKS

614-330055-001 DECEMBER 2015 473

RF Network Health Reports

With ProVision’s RF 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 con-
text or logical containment context).
This feature provides reporting on the RF performance for all Aviat Networks devices
that support G.826 or other performance collection, including:
l Altium (all variants)
l Constellation (only 3DS3, 4DS3, and 155mbit)
l CTR 8540
l DART
l Eclipse circuits
l Eclipse
l LE3000 and LE 3200
l Logical Containers
l Radwin WinLink 1000 and 2000
l SPECTRUM II (all variants)
l SPECTRUM II SNMP
l TRuepoint (all variants)
l WTM 3200 and 3300
l WTM 6000
l XP4 (all variants)
RF Network Health Reports summarize link performance data in both graphical and tab-
ular 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.
There are also specialized RF Network Health Reports for Ethernet devices and net-
works.
See the following:
l Run and View RF Network Health Reports on page 475
l Ethernet Network Health Report on page 480
l Clock Synchronization Network Health Report on page 485
474 AVIAT NETWORKS

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 RF Network Health Reports on page 475.
NOTE : The Netw or k Health Repor t is c r eated us ing daily per for manc e
data fr om the Pr oVis ion databas e, exc luding invalid data. Daily per -
for manc e data in the databas e is r equir ed for Netw or k Health Repor t out-
put.
Run and View RF Network Health Reports

After you have configured an RF Network Health Report, you can run it and review its
data.
NOTE : The RF Netw or k Health Repor t c an be r un for many devic es , s ee

the table Rep ort s Av ailable by Dev ice Ty p e on p age 510.
Procedure
1. From the menu bar, in the Reports menu, select Network Health - RF Network
Health. Or, in the Tree Viewer, select an object for the report by right-clicking on it
and selecting Reports - Network Health - RF Network Health.
2. The RF Network Health Report window displays.
3. Select the values for the report. In the Report Settings frame, select the following:
614-330055-001 DECEMBER 2015 475

l Start and End Date: Select a start and end date within this range. The
report will cover data between these two dates.
l 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.
l Exclude Unmanaged Devices: Click the checkbox to exclude the unmanaged
device ports in the report.
l NOTE : The maximum r epor t r ange mus t be equal to

or les s than the Daily Perf o rmance Dat a databas e
pur ge s etting (Adminis tr ation -> Databas e Pur ge) oth-
er w is e vis ibility w ill be inac c ur ate.
4. In the Report Settings frame, click the Generate Report button. The Network
Health report displays.
Click on the Details tab to view a statistical breakdown of each individual link. Devices
highlighted in red have availability below the threshold. Devices highlighted in orange
do not support, or have not collected, their availability data. You can check boxes to
Hide Healthy Devices and to Hide Devices with Zero Visibility.
476 AVIAT NETWORKS

5. To save the report as a PDF, click the Export as PDF button. A Save win-
dow opens, prompting you to save the file with a name at the system location you
choose.
6. 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.
RF Network Health Report - Overview Tab

This data is included in both the PDF and XLS formats for this report.
Value Description
Report Data Information about this specific network health report.
Start and End- dates for the report coverage beginning and
end.
Availability Threshold- Link availability threshold for the
report.
Availability %(Total G.826 Available Seconds)/(Report Period)
Threshold
Hide Out of Service Check this box to hide Out of Service devices from this report.
Devices At/Above Number of devices operating at or above the Availability
Threshold threshold.
Devices Below Number of devices operating below the Availability threshold.
Threshold
Mean Availability Displays the average availability for all valid performance
data over the reporting period
614-330055-001 DECEMBER 2015 477

Value Description
Mean Visibility Displays the average visibility of the network able to be viewed
by ProVision for this report.
Number of Devices Number of devices in this report.
Devices with Zero Number of devices that are not providing any data.
Visibility
Device Availability A pie graph comparing the number of healthy devices with the
Chart number of devices below threshold.
Breakdown by Day A graph showing the % of network availability over the past 60
Chart days. Mouse over the line for a specific day to view its % of avail-
ability and visibility.
Availability and Visibility Calculations

Availability and visibility are calculated differently for device and summary values.
These calculation definitions are as follows:
Device Calculations
l Availability = (Sample Period in seconds - Total number of Unavailable
Seconds during sample Period)/ Sample Period in seconds
l Visibility = Number of samples / Sample Period in Days.
Summary Calculations
l Availability = Total of the Availability for each device / Total number of
devices (devices that don’t support the G.826 Unavailable Seconds parameters
are not included in this calculation)
l Visibility = Total of the Visibility for each device / Total number of devices
RF Network Health Report - Details Tab

Details displayed for devices are selected from the Report Fields screen. Click on the
Report Values icon to open this screen:
478 AVIAT NETWORKS

Some frequently selected values are defined below:

Value Description
Device Device name and network location.
Remote The radio linked to the main device.
Availability % availability of the network.
Visibility The % of the selected time period when the device was contacted
and performance data collected.
The following additional values appear for Eclipse, TRuepoint 6500, and WTM
6000 devices:
ESR ESR (errored second ratio) is the ratio of ES to total seconds in
available time.
SESR SESR (severely errored second ratio) is the ratio of SES to total
seconds in available time.
BBER Background bloc errors (BBE) ratio to total blocks in available
time.
NOTE : Remote link infor mation is not s uppor ted for Ec lips e IDU pr o-
tec ted devic es .
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 max-
imum number of events to 65,000.
614-330055-001 DECEMBER 2015 479

Value Values
Network Events Device
Event
Time
Severity
Acknowledged
Ethernet Network Health Report

The Ethernet Network Health Report displays an overall view of the health of the Eth-
ernet Network. It will give an overview of Rx and Tx errors and utilization and display
relevant performance parameters.
You can view this report for the network's entire Ethernet network, or for selected
devices in the Ethernet network.
NOTE : The Ether net Netw or k Health Repor t c an be r un for many

devic es , s ee the table Rep ort s Av ailable by Dev ice Ty p e on p age 510.
Procedure
1. From the menu bar, in the Reports menu, select Network Health - Ethernet
Network Health.
2. Or, in the Tree Viewer, select an object for the report by right-clicking on it and
selecting Reports - Network Health - Ethernet Network Health.
3. The Ethernet Network Health Report window displays.
480 AVIAT NETWORKS

l Packet Loss Threshold: % of errored/discarded packets threshold for all the
ports comprising this report. Any port above this threshold is considered to be
in error. This is normally set to the threshold availability in your service level
agreement.
l Utilization Threshold: % bandwidth utilization threshold for all the ports in
this report. Any port above this threshold is considered to be in error.
device links in the report.
5. In the Report Settings frame, click the Generate button. The Ethernet Network
6. Click on the Details tab to view a statistical breakdown of each individual link.
Devices with availability below the threshold are highlighted in orange. You can
check boxes to Hide Healthy Devices.
614-330055-001 DECEMBER 2015 481

choose.
button. A Save window opens, prompting you to save the file with a name at the
system location you choose.
Ethernet Network Health Report - Overview Tab

RX and TX data is summarized individually on the Overview screen.
Value Description
Report Data Information about this specific Ethernet network health report.
Start and End- dates for the report coverage beginning and end.
Packet Loss Threshold- Errored/discarded package threshold
for the report.
Utilization Threshold - Port utilization threshold for the report.
Utilization % bandwidth utilization threshold for this report. Any data per-
centage above this threshold is considered to be in error.
Visibility The number of days for which ProVision is able to obtain one or
more samples from an Ethernet port. For example, if your ProVi-
sion server had been deployed for seven days, but for one of those
days, it had not been able to communicate with one Ethernet port,
the visibility for that week would be 85% for that port.
482 AVIAT NETWORKS

Value Description
Mean Visibility Displays the average port visibility able to be viewed by ProVision
for this report.
Number of Ports Number of ports in this report for which ProVision successfully col-
lected one or more samples.
Ports at/above Number of ports that are operating at or above the packet loss
packet loss threshold threshold.
Ports below packet Number of ports that are operating below the packet loss
loss threshold threshold.
Ports at/above util- Number of ports that are operating at or above utilization.
ization threshold
Ports below util- Number of ports that are operating below the utilization
ization threshold threshold.
Port Healthy Chart A pie graph comparing the number of healthy ports with the num-
ber of ports below threshold.
Breakdown by Day A graph showing the % of port visibility below threshholds over
Chart the report period.
Network Health Report - Details Tab

The available details are sourced from the Ethernet performance parameters available for
each device.
This table lists the shared/standard values, equivalent to the "low" level of detail in the
standard Network Health Report.
Value Description
Device Port name and network location.
Remote The radio port at the end of the radio link.
In/Out Packet Lost % of In/Out packet losses of the port.
Threshold
Visibility The % of the ports able to be viewed by ProVision for this report.
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 max-
imum number of events to 65,000.
Value Values
Network Events Device
Event
Time
Severity
Acknowledged
614-330055-001 DECEMBER 2015 483

484 AVIAT NETWORKS

Clock Synchronization Network Health

Report
You can view clock synchronization data via a Network Health Report.
See also Clock Synchronization View on page 192.
NOTE : The Cloc k Sync hr onization Netw or k Health Repor t c an be r un for

s ever al devic es , s ee the table Rep ort s Av ailable by Dev ice Ty p e on
p age 510. This r epor t r equir es a featur e lic ens e: s ee Abou t Licenses.
Procedure
1. From the menu bar, in the Reports menu, select Network Health - Clock Sync
Network Health. Or, in the Tree Viewer, select an object for the report by right-click-
ing on it and selecting Reports - Network Health - Clock Sync Network Health.
2. The Clock Synchronization Network Health Report window displays.
l Quality Threshold: The minimum acceptable clock Quality Level (QL), as
defined for synchronous Ethernet in ITU-T G.8267 and G.781, for this report.
Any device below this threshold is considered to be in error.
l Stability Threshold: Maximum number of times the clock source can change
its quality level per day and still be within stability limits.
l Not Locked Threshold: Percentage of time spent free running (reliant on the
internal clock and not the clock source) that is within acceptable limits.
devices in the report.
NOTE : The maximum r epor t r ange mus t be equal to or les s than the
Daily Perf o rmance Dat a databas e pur ge s etting (Adminis tr ation -> Data-
bas e Pur ge) other w is e vis ibility w ill be inac c ur ate.
4. In the Report Settings frame, click the Generate Report button. The Network
614-330055-001 DECEMBER 2015 485

choose.
button. A Save window opens, prompting you to save the file with a name at
the system location you choose.
Overview Tab
Value Description
Report Data Information about this specific network health report.
Start and End- dates for the report coverage beginning and
end.
Quality Threshold- Quality Level threshold for the report.
Stability Threshold -Stability threshold for the report.
Not Locked Threshold - Not locked threshold for the report.
Quality The percentage of devices for which the clock Quality Level is
always inside the minimum threshold defined.
Stability The stability of a clock device defined by the number of times it
changed level during a given period (switches per week).
Not Locked The percentage of devices for which the not-locked percentage of
operating time was inside the threshold.
486 AVIAT NETWORKS

Value Description
Visibility The percentage of time during the period where the device was
contacted and performance data was collected.
Breakdown by day The number of device that met or exceeded the desired
threshold (as above) for each day in the sample period.
Details Tab
Value Description
Hide Healthy Hide healthy devices.
Devices
Device Device name.
Visibility Percent of the report period where data was collected.
Min Quality Worst clock quality during period.
Switches The number of times this clock changed level during the given
period (switches per week).
Free Running Percent of time in free running state.
Holdover Percent of time in holdover state.
QL0 - QL15 For each possible clock Quality Level, QL0 (best) through QL15
(worst), the percent of time where the locked clock source was of
that quality.
614-330055-001 DECEMBER 2015 487

Eclipse Security Status Report

The Eclipse Security Status Report is a feature specific to the Eclipse devices. This report
collects security data for one or more Eclipse devices. The report is in a free-floating win-
dow that lists security information, including:
l Portal Access - whether a device has its Portal access locked from ProVision,
value is Locked or Unlocked
l Security Enabled - Checks to see if device security is enabled from Portal,
value is False or True
l Portal Auto Login Status - If an auto-login is set, this is noted as Credentials
Configured
You can save the Security Status Report as a .PDF or.xml file . You can also retain a spe-
cific report configuration as a Custom Report for the selected devices.
Procedure
To view a security status report for one or more Eclipse devices:
1. Right-click the Eclipse icon or icons, or the Eclipse device container. From the
right-click menu, select Reports, then Security Status.
2. The Security Status Report window displays.
3. Select the Run button. The report generates, showing the security status for the
devices.
NOTE : The Sec ur ity Enabled field w ill alw ays s how “Unknow n” for
Ec lips e r adios w ith a ver s ion ear lier than 5. 03. x.
4. To hide rows with no data, click the Hide empty rows check box. To view ports,
click Include Ports.
488 AVIAT NETWORKS

name.
614-330055-001 DECEMBER 2015 489

Clock Sync Report

The Clock Sync Report enables you to view clock synchronization status and values for
clock sync-eligible devices.
You can save the Clock Sync Report as a .PDF or.xml file . You can also retain a specific
report configuration as a Custom Report for the selected devices.
NOTE : The Cloc k Sync Repor t c an be r un for s ever al devic es , s ee the

table Rep ort s Av ailable by Dev ice Ty p e on p age 510.
Procedure
To view a security status report for one or more Eclipse devices:
1. Right-click the Eclipse icon or icons, or the Eclipse device container. From the
right-click menu, select Reports, then Security Status.
2. The Report - Clock Sync window displays.
3. Select the Run button. The report generates, showing the security status for the
devices.
4. To customize the report, select the check boxes to: Hide Empty Rows, Include Plu-
gins, and Include Ports.
490 AVIAT NETWORKS

name.
Clock Sync Report Values

Value Definition
Holdoff Time The time in seconds that this device waits before acting on
signal fail conditions.
Wait to Restore The time that a clock source must be fault free before it is
available as a syncable device again.
Clock Sync Enabled True or False
Clock Sync Mode Master (sending clock), Slave (receiving clock), or Auto
(default)
SSM Option Type Option I or Option II
SSM Enabled True or False
Source Priority Priority level applied to this device for clock selection:
highest priority level is the highest number.
614-330055-001 DECEMBER 2015 491

Link Report
The Link Report provides a seven-day summary for an entire ProVision network, com-
bining device configuration with radio and Ethernet performance data. Each row in the
report represents a single radio link for a single day, with data collected from both sides
of the link.
This report is easy to run from the ProVision user interface, and the report data can be
exported and saved as a .CSV file. However, it is important that the report data pre-
requisites are in place.
NOTE : The L ink Repor t is available for Ec lips e (not for IDU pr otec ted
devic es ) and for CTR 8300 and CTR 8540 devic es . Running the L ink
Repor t r equir es a featur e lic ens e: s ee Abou t _ ProVision_ Licenses. ht m.
Prerequisites
To run the Link Report, daily performance collection must be enabled on every device in
the entire network. Also, Fifteen Minute Ethernet Performance Collection must be
enabled on every Ethernet DAC. Note that fifteen minute radio path data is not
required.
The daily data collection time must be configured to be at midnight to avoid skewing
the collected data in time. This means that database purge and automated backups can-
not be scheduled for midnight as they may delay daily performance collection.
It would be acceptable to set backup and purge to occur at 1am.
Procedure
1. From the Reports menu, select Link Report.
2. The Link Report window displays.
3. Select the Week Ending date range for the report. Then, click the Generate but-
ton. The report generates. Scroll through the report to review all the values.
492 AVIAT NETWORKS

4. To save the report as a CSV file, click Export: CSV. Save the report to your
required location.
Link Report Data

This data can be collected from either side of the link. The Link Report will prefer con-
figuration data from the High side of the link. If this is not available Low side data is
used and the Tx and Rx frequencies will be reversed.
This report only displays data from the current RF configuration.
Value Definition
Date Each row represents one radio link for one day, with the date noted in
this column.
ID High The device site name on the High side of the link.
Reference The reference combines the ID High Link name and the name of the
site. For example:
[D5008_Umtata Telkom Exchange V_04] X3491_Unitra Univ. (V) (-
39.72) - LINK1-D5008_Umtata Telkom Exchange"
When L1LA configured on Link, the L1LA Port reference will be there, in
addition to Links.
L1LA The reference of L1LA Ethernet port (if L1LA configured on the Link).
RX Power Min (dBm) The minimum intra-day RSL detected by the radio. This is read from
the daily performance sample on the device.
RX Power Max (dBm) The maximum intra-day RSL detected by the radio. This is read from
the daily performance sample on the device.
RX Power Mean (dBm) The mean intra-day RSL detected and calculated by the radio. This is
read from the daily performance sample on the device.
Tx (MHz) Frequency of the TX in MHz.
Rx (MHz) Frequency of the RX in MHz.
Bandwidth Bandwidth value in MHz.
614-330055-001 DECEMBER 2015 493

Modulation Maximum configured modulation, or the most frequent modulation on a

different day for AM links.
ATPC Notes if ATPC is enabled, Yes or No.
Capacity Maximum link capacity in Mbps.
TDM Capacity (Mbps) Maximum TDM capacity in Mbps, based on configured TDM circuits
over the link.
Packet Capacity (Mbps) Maximum data packet capacity in Mbps, based on the configured Eth-
ernet circuits over the link. If DPP is applied then the packet capacity is:
Capacity – TDM Capacity.
L1LA Ethernet port reference record will have the aggregated packet
capacity of the L1LA links.
Config Protection type applied to the link or L1LA for the L1LA Ethernet port
reference record.
Reference The reference combines the ID Low Link name and the name of the site.
For example:
[D5008_Umtata Telkom Exchange V_04] X3491_Unitra Univ. (V) (-
39.72) - LINK1-D5008_Umtata Telkom Exchange"
When L1LA configured on Link, the L1LA Port reference will be there, in
addition to Links.
L1LA The reference of L1LA Ethernet port (if L1LA configured on the Link).
Availability % The lowest daily G.826 Available Seconds count for either end of the link
expressed as a percentage of 86,400, the number of seconds in one day.
For example: if the High side of the link has 86,400 available seconds
and the Low side had 43,200 available seconds, the link would show as
50% available.
SES The highest daily G.826 Seriously Errored Seconds count for either end
of the link
BER Mean Average Bit Error Rate for both sides of the link, measured for the day.
Packet Loss % The percentage of dropped packets, as a proportion of the total number
of packets flowing over the link. Packets are counted from all backplane
Ethernet and DPP traffic flowing into both sides of the link.
Where:
Total Packets = Unicast Packets + Multicast Packets + Broadcast Packets
+ Dropped Packets + Errored Packets
Packet loss % = ((High Out Dropped Packets + Low Out Dropped Pack-
ets) / (High Total Packets + Low Total Packets)) x 100
Mbps Mean High/ Low The average throughput measured for the day.
Packet Volume Packet volume total in gigabytes, based on octet count for the day.
Utilization Mean % (Mbps Mean / Capacity) x 100. The mean value is the sum of the fixed
High/Low TDM traffic and Ethernet DAC traffic entering the link.
Mbps Max High/Low The peak throughput measured during the day. This is derived from the
largest fifteen minute sample.
Utilization Max % (Mbps Max / Capacity) x 100.This value is the maximum 15 minute
High/Low period utilization during the day.
Warning: This requires 15 minute performance collection to be enabled
on every DAC GE in the network. If 15 minute Ethernet data collection
is not enabled, the Ethernet utilization will be recorded as zero.
494 AVIAT NETWORKS

Above 80% The number of fifteen minute periods in the day where average util-
ization is at or above 80%. Expressed as a percentage of the 96 fifteen
minute periods in the day.
Sync Synchronization Configured – Yes or No.
Primary Type Type of synchronization technology used for the Primary, i.e. Multicast,
SynchE.
Secondary Type Type of synchronization technologyused for the Secondary, i.e. Multicast,
SynchE.
Primary Port Equipment and port number used as the synchronization source for the
Primary.
Secondary Port Equipment and port number used as the synchronization source for the
Secondary.
Primary Source Plug-In The plug-in which is supplying the clock sync source.
Secondary Source Plug-In The plug-in which is supplying the clock sync source.
Physical Hops The number of physical repeats from the clock sync source.
Logical Hops The number of logical repeats from the clock sync source.
614-330055-001 DECEMBER 2015 495

Licensing Report
The Licensing Report reviews selected devices and presents licensing information for
review and download. You can view all or selected devices, and select specific fields to
include.
Procedure
1. From the Reports menu, select Licensing Report.
2. The Licensing Report window displays.
3. To set up report fields, select Report Fields from the Options menu. The Report
Fields screen displays. Go through the tree view of options on the left. To add a field
value to the report, select it in the Available Fields frame and click the right arrow,
to add it to the Selected Fields frame. When you are done adding field values,
click OK.
4. To note specific containers, regions, and devices for a report, go to the Options
menu and select Object Filter. The Object Filter window has two tabs.
496 AVIAT NETWORKS


l Containment - Select specific containers or devices to include
name.
Licensing Report Value Options

Value Definition
Device Name Name of the device.
Physical Path Device location, related to other devices.
Serial Number License serial device.
Allocated Capacity Total capacity allocated to this license.
Auto Allocation True (active) or False.
Capacity Licensed mBps capacity.
Features Any additional features enabled using this license.
614-330055-001 DECEMBER 2015 497

Creating Custom Reports

The Custom Reports feature enables users to create customized reports for
devices. When they create the reports, they select the devices and report fields to
include, creating a report that matches their exact specifications. Users can create, save,
and edit Custom Reports, and regenerate the reports as required.
Users can also edit standard ProVision reports and save them as custom reports. This
does not override the existing report.
NOTE : Cus tom Repor ts ar e available for all devic es in Pr oVis ion.
Reports with this option include:

l Eclipse Security Status Report on page 488
Procedure
1. In the main ProVision screen, go to the Reports menu and select Custom
Reports. Or, select a device, right-click it, and choose Reports > Custom
from the right-click menu.
2. The Custom Reports screen displays, listing all available device types. Note
that you can use the check boxes to hide empty rows, include plugins, and
include ports in this device listing.
3. To set up report fields, select Report Fields from the Options menu. The
Report Fields screen displays.
4. Go through the tree view of options on the left. To add a field value to the
report, select it in the Available Fields frame and click the right arrow, to
498 AVIAT NETWORKS

add it to the Selected Fields frame. When you are done adding field values,
click OK.
NOTE : For s ome devic e types , ther e may be var iations in the Available
Fields . See the table at the end of thes e ins tr uc tions for thes e var iations .
5. To note specific containers, regions, and devices for a report, go to the

Options menu and select Object Filter. The Object Filter window has two
tabs.
l Containment - Select specific containers or devices to
include
7. You can improve the report display by:
l Sorting data in a column - Click on a column name to
sort its data in alphabetical or numerical order.
l Hiding rows with no data - Click the Hide empty rows
check box.
l Filtering data - Click the Filter button, enter your
filtering value, and click Enter. The report removes all
data that does not include the filtering value. Clicking
the X clears the filter and hides the filter input field.
NOTE : You c annot s ave a s ubs et of data. You c an expor t a s ubs et of data
to a PDF or s pr eads heet by highlighting the s ubs et and s aving the c on-
tent.
8. Select the PDF button to save the report as a PDF file. Up to 10 columns can
be saved in PDF format.
614-330055-001 DECEMBER 2015 499

9. Select the Excel button to save the report as an Excel spreadsheet.

10. To save this report, for these specific devices, go to the File menu and select
Save As. This report configuration will be saved. To open it again, go to
Reports - Custom Reports and select the report name.
11. Select Close to close the Custom Report window.
NOTE : After you have s aved a Cus tom Repor t, the Cus tom Repor t's
name dis plays in the Repor ts - Cus tom Repor ts menu as an option. This
enables you to r un the s aved r epor t dir ec tly.
Custom Report Value Options

NOTE : Many c us tom r epor t values ar e available: this table defines the
mos t popular ones for eac h c ategor y.
NOTE : Some devic es have r enamed values . See the s ec ond table for
this lis t.
Value Definition
General
Device Name Name of the device.
Site Name Name of the device location.
Site Grid Grid that includes the device.
Contact Details Any contact details entered for the device.
Path The unique physical path of this device or container in the tree
structure.
IP Address The unique IP address of this device or container.
FarScan Address FarScan Address, if applicable.
Device Type (ProVision) The specific ProVision device type.
Device Type The device type.
Device Family The device family. Not applicable for plugins.
State The state of the device. Not applicable for containers.
Software Version A list of the software versions for the controller and plugins of a
device.
Slot number If device is a plug-in, the slot number where the device is
installed.
Compact Flash Size Size of any associated compact flash.
Configuration - Time
Time Server Status Whether the time server feature is enabled or disabled on the
device.
Time Servers The list of IP addresses configured for the time server on the
device.
Time Offset The time offset for the device data.
Configuration RF
Capacity Configured link capacity in Mbps.
Licensed Capacity Available licensed capacity in Mbps.
500 AVIAT NETWORKS

Value Definition
Bandwidth (MHz) Configured RF bandwidth of the TX unit in MHz.
TX Modulation Configured TX modulation, e.g. QPSK, 16QAM, etc.
RX Modulation Configured RX modulation for TRuepoint and WTM radio types.
This value is the same as the TX modulation for other radio
types.
Protection Type Configured RF link protection type, e.g. Frequency Diversity,
Space Diversity, etc.
Protection Type GP1 RPS & Type of group protection configured for TRuepoint 6500 or WTM
GP2 RPS 6000 radio.
Protection Status Protection status of the TX unit, e.g. Offline, Online, Unable to
protect.
TX Protection Mode Protection mode of the TX unit, e.g. Enabled, Disabled, unknown,
No response, Error in response, Not equipped.
RX Protection Mode Protection mode of the RX unit, e.g. Enabled, Disabled, unknown,
No response, Error in response, Not equipped.
TX Freq Range (MHz) Frequency range in MHz supported by the TX unit.
TX Freq Band Indicates whether the TX module is TX High or TX Low band.
TX Freq (MHz) Configured frequency in MHz of the TX unit.
RX Freq (MHz) Configured frequency in MHz of the RX unit. Calculated from
the TX frequency and TX-RX frequency spacing.
TX-RX Spacing (MHz) Difference between the Tx frequency and RX frequency in MHz.
RSL (dBm) Current operating Received Signal Level (RSL) in dBm measured
from the RX unit.
ATPC Status Indicates whether Automatic Transmit Power Control (ATPC)
function in the TX module is Active or Inactive.
Max TX Power (dBm) Configured maximum TX power in dBm that the ATPC function
can demand.
Min TX Power (dBm) Configured minimum TX power in dBm that the ATPC function
can demand.
TX Power (dBm) Either 1) the configured TX power or 2) the measured TX power
where ATPC is enabled on the TX module.
TX Static Atten Max (dB) Indicates the TX module maximum static attenuation in dBm for
TRuepoint or Microstar radios.
ATPC Mode Radio 1 ATPC mode of Radio 1, e.g. Enabled, Disabled, No response,
Error in response, Not equipped.
ATPC Mode Radio 2 ATPC mode of Radio 2, e.g. Enabled, Disabled, No response,
Error in response, Not equipped.
ATPC Power Mode Radio 1 ATPC power mode of Radio 1, e.g. Low, High, No response, Error
in response, Not equipped.
ATPC Power Mode Radio 2 ATPC power mode of Radio 2, e.g. Low, High, No response, Error
in response, Not equipped.
Configuration - Clock Sync
Clock Sync Enabled True or False.
SSM Enabled True or False.
SSM Option Type Option I or Option II.
614-330055-001 DECEMBER 2015 501

Value Definition
Holdoff Time The time in seconds that this device waits before acting on signal
fail conditions.
Wait to Restore The time that a clock source must be fault free before it is avail-
able as a syncable device again.
Clock Sync Mode Master (sending clock), Slave (receiving clock), or Auto (default)
Source Priority Priority level applied to this device for clock selection: highest pri-
ority level is the highest number.
SSM SSM value.
Forced QL Include forced QL.
Configuration Inventory
Plug-in Class Class of identified plug-in, e.g. Eclipse RAC, Eclipse DAC.
Plug-in Name Name of identified plug-in.
Plug-in Type Type of identified plug-in, e.g. RAC 6XE, DAC GE3.
Serial Number Device or plug-in serial number.
CLEI The Common Language Equipment Identifier for this device or
plug-in.
Bridge ID If present, the MAC address with additional bridging data.
VLAN Bridging Mode Notes any active VLAN mode that is present.
Part Number Device or plug-in part number.
SW Version Software version installed on device or plug-in.
HW Revision Hardware revision for device or plug-in.
FW Revision Firmware revision for device or plug-in.
Time in Service Time in seconds that the device or plug-in has been in service.
Settings Version Version number of settings for TRuepoint device.
MMC Code Recorded MMC code for TRuepoint device.
Manufacture Date Date of manufacture.
Manufacturer Manufacturer ID.
Asset Tag Asset tag value for E-Band E-Link device.
EOAM Whether EOAM is enabled or disabled.
Y1731 Whether Y1731 is enabled or disabled.
Configuration Port
SFP Type Type of SFP (small form factor), i.e., optical or electrical, with
speed values.
Port Type Type of port, i.e., optical or electrical.
Port Mode Mode of port.
Port Speed Speed of port in Mbps.
Duplex Whether port has duplex enabled.
MDI Whether port is an MDI port.
Max Frame Size Maximum frame size for the port.
Fault
Active Event Count The total active event count on this device/container, not includ-
ing the event counts of children.
Critical Event Count The total active event count with a critical severity on this
device/container, not including the event counts of children.
502 AVIAT NETWORKS

Value Definition
Major Event Count The total active event count with a major severity on this device/-
container, not including the event counts of children.
Minor Event Count The total active event count with a minor severity on this device/-
container, not including the event counts of children.
Warning Event Count The total active event count with a warning severity on this
Normal Event Count The total active event count with a normal severity on this
Informational Event Count The total active event count with an informational severity on
this device/container, not including the event counts of children.
Cleared Event Count The total cleared event count on this device/container, not includ-
ing the event counts of children.
Active Unacknowledged Event The total unacknowledged active event count on this device/-
Count container, not including the event counts of children.
Aggregated Active Event Count The total active event count on this device/container, including
the event counts of children. This should match the event count
in the Event Browser.
Aggregated Critical Event The total active event count with a critical severity on this
Count device/container, including the event counts of children. This
should match the event count in the Event Browser.
Aggregated Major Event Count The total active event count with a major severity on this device/-
container, including the event counts of children. This should
match the event count in the Event Browser.
Aggregated Minor Event Count The total active event count with a minor severity on this device/-
container, including the event counts of children. This should
match the event count in the Event Browser.
Aggregated Warning Event The total active event count with a warning severity on this
Aggregated Normal Event The total active event count with a normal severity on this
Aggregated Informational The total active event count with an informational severity on
Event Count this device/container, including the event counts of children. This
Aggregated Cleared Event The total cleared event count with an informational severity on
Count this device/container, including the event counts of children.
Aggregated Active Unac- The total unacknowledged active event count on this device/-
knowledged Event Count container, including the event counts of children.
Performance
Last 15 min RSL The 15 minute RSL performance value, if one has been collected
in the last 15 minutes of this report being run.
Last Daily RSL The daily RSL performance value, if one has been collected in the
last 24 hours of this report being run.
Last 15 min Transmit Power The 15 minute Transmit power performance value, if one has
been collected in the last 15 minutes of this report being run.
Last Daily Transmit Power The daily Transmit power performance value, if one has been col-
lected in the last 24 hours of this report being run.
614-330055-001 DECEMBER 2015 503

Value Definition
Security
SNMP Read Community String The SNMP Read Community string, if assigned to the device.
SNMP Write Community The SNMP Write Community string, if assigned to the device.
String
Auto Login Status Whether an specific login credential has been configured for a
device.
Eclipse Portal Access If the Portal Locking feature is enabled, displays the locked or
unlocked status of the devices. Only for Eclipse devices.
Portal Security Whether any additonal security features, such as Eclipse security,
are active.
License (INU)
EZF-01 - Link Aggregation Selecting one of these values indicates the presence and part
number of the following licenses:
- EZF-01 - Link Aggregation
- EZF-02 - Adaptive Modulation
- EZF-03 - Secure Management
- EZF-05 - Ethernet over TDM
- EZF-06 - RADIUS
- EZF-09 - Synchronous Ethernet
- EZF-10 - Ethernet OAM
- EZF-1408 -E1/T1 Loop Switch 8x E1/T1
- EZF-14 Ei/T1 Loop Switch 50xE1/63xT1
- EZF-16 - 63xE1/DS1 Node ML-PPP
- EZF-17 - VID Routing
- EZF-18 - 108xE1/135xDS1 Node ML-PPP
- EZF-19 - Enable TDM Ports IDU GE3
- EZF-20 - Advanced QoS IDU GE3
- EZF-41 LL Capability
- EZF-42 - Strong SecurityFIPS 140-2 Compliant
- EZF-43 - IPV6
- EZF-51 - ODU 600 High Power (1)
- EZF-61 - IRU 600v3 High Power (1)
License (IDU)
504 AVIAT NETWORKS

Value Definition
Selecting one of these values indicates the presence and part
number of the following licenses:
- EZF-10002 - Adaptive Modulation
- EZF-10003 - Secure Management
- EZF-10006 - RADIUS
- EZF-10009 - Synchronous Ethernet
- EZF-10010 - Ethernet OAM
- EZF-10019 - TDM Ports
- EZF-10020 - Advanced QOS
- EZF-10400 - Node License 400 Mbps
- EZE-08011 - Node License 2.4 Gbps
Select Configuration Values To The report will display the selected configuration value applied to
Display devices in the report. These values can include:
- Device Name
- Site Name
- Device Type
- Capacity
- Bandwidth (MHz)
- Modulation
- RX Modulation
- Protection Type
- TX Freq Range
- TX Freq Band
- TX Freq (MHz)
- RH Freq (MHz)
- ATPC Status
- Max TX Power (dBm)
- Min TX Power (dBm)
- PA TX Power
- TX Static Atten Max
- TX Protection Mode
- RX Protection Mode
- Protection Status
- ATPC Mode Radio 1
- ATPC Mode Radio 2
- ATPC Power Mode Radio 1
- ATPC Power Mode Radio 2
- Data Rate
- Space Diversity
- GP1 RPS
- GP2 RPS
- FarScan Address
- No. Channels
NOTE : Some devic e types have field name var iations . The defined field
w ill matc h its equivalent in the table above.
Table 8-4. Device Types with Field Name Variations
614-330055-001 DECEMBER 2015 505

Device Available Field Item Names and Variations

Altium RSL = RSSI
Constellation Capacity = Capacity Max
LE3000 Bandwidth = Channel Bandwidth
TX Freq Range = Centre Freq Range
TX Freq
= Current Centre Freq
Megastar M:N Protection Type = Protection System
Microstar I, I, and II TX Freq is TX Freq Current
TX Static Atten Max is Atten
SPECTRUM II RSL (dBm)is Current (mV)
TRuepoint 6400 Capacity = Capacity Max
TX Freq Range = Freq Range
TX Freq = TX Freq Current
TRuepoint 6500 TX Freq = Frequency
506 AVIAT NETWORKS

Scheduling Reports
You can schedule Network Health and Capacity reports to run on a regular basis
in ProVision. This runs and saves the report, with options including:
l Report frequency
l Report type, parameters, and filters
l Report creation notifications
Scheduled reports are accessed from a central screen:
Procedure
1. In the main ProVision screen, go to the Reports menu and select Scheduled
Reports.
2. The Scheduled Reports screen displays, listing the previously created
Scheduled Reports.
3. To add a new Scheduled Report, click the Add button. The Add Scheduled
Report screen displays.
614-330055-001 DECEMBER 2015 507

4. Enter the report requirements from the General tab. The values that display
here are based on the report Type that you select. See the following table for
the screen values for the General tab. These include:
l Ethernet Network Health Report
l Clock Sync Network Health Report
l RF Network Health Report
l Capacity Report
l Link Report
5. Go to the Filter tab. If required, select the Objects check box, and use the
tree view to select the objects to include in this report. This step is optional.
6. Go to the Actions tab. Right-click and select actions from the drop-down
menu to occur when the report is created: Add Email Action and/or Add
Directory Action.
l Add Email Action sends an email to a specified address or addresses when the
report is generated. For more details on adding the email action, see Set Up an
Email Event Notification on page 351
l Add Directory Action saves the report to a directory on the Server PC.
l The default directory is\ProVisionServer\repository\reports.
l To change this directory, right-click on the Directory item
and select Add Directory. The Add/Remove Directories
screen displays.
l Click Add to add a new directory, typing the Name and
Location in the fields.
l Select a directory and click Remove to remove it from the
list of locations.
508 AVIAT NETWORKS

WARNING: You must set up an action in step 6: this is required to save or email the sched-
uled report.
7. Click OK. The report is added to the Scheduled Reports list, and is run at
the specified dates. The scheduled report is run is immediately after the
daily performance data collection is completed. The default time is
midnight, 12:00 AM. For more information, see Data Collection on page
388.
Add Scheduled Report - General Values

Value Details
Details
Name Name that will be applied to this report.
Last X Days Amount of daily data that will be included in this report: for
example, selecting 7 will include the previous 7 days' worth of
data in this report.
Type Select the report type from the drop-down menu. Options
include:
- Ethernet Network Health Report
- Clock Sync Network Health Report
- RF Network Health Report
- Capacity Report
- Link Report
As: Select the report file type from the drop-down menu, Text,
Excel or PDF.
Parameters The parameters that display are based on the selected Report
Type. Select the report parameter values. If a Report Fields
button displays, you can click it to customize the report fields in
this report.
Recurrent Pattern Click the radio button for this report's recurrent pattern:
Daily, Weekly, Monthly, or Yearly. Specific options are
available for each pattern:
- Daily - Every X Days or Every Weekday.
- Weekly - Select day or days of the week by clicking on
check boxes.
- Monthly - Select # day of month or specify day of week
of month.
- Yearly - Select month and day or specify day of week of
selected month.
614-330055-001 DECEMBER 2015 509

Reports Available by Device Type

Eclipse Only Reports
l Eclipse Fault
l Eclipse Security Status
Multi-Device Reports
Clock
RF Ethernet Clock
Inventory Capacity Sync Custom
Devices Network- Network - Sync
Report Report Network - Report
Health Health Report
Health
Accedian YES YES
Altium 155, MX YES YES
Aurora YES
CAU YES
Cisco YES YES
Constellation YES YES YES
CTR 8440 YES YES YES YES
CTR 8540 YES YES YES YES YES YES
DART YES YES
DVA YES
DVM 45, xT YES
DXR 100 YES
DXR 200 YES
DXR 700 / SMA YES
E-Band E-Link YES YES
Eclipse YES YES YES YES YES YES YES
EMS Proxy and YES
Network Ele-
ments
LE3000, LE3200 YES YES YES
Megastar 1+, M:N YES
Memotec CX-U YES
Microstar type I, YES
II, III
Radwin 2000 YES YES YES
Radwin WinLink YES YES YES
1000
510 AVIAT NETWORKS

Clock
RF Ethernet Clock
Inventory Capacity Sync Custom
Devices Network- Network - Sync
Report Report Network - Report
Health Health Report
Health
Sagem ADR 155C YES
/ 2500 eXTRA
Sagem SAGEM- YES
LINK
SPECTRUM II YES YES
SNMP
Symmetricom YES YES
Tellabs 8600 YES YES
TNet Proxy YES
devices
TRuepoint 4000, YES YES YES
4040, 5000
TRuepoint 6400 YES YES YES
TRuepoint 6500 YES YES YES
Velox YES
WTM 3100 YES YES YES YES YES
WTM 3200 YES YES YES YES
WTM 3300 YES YES YES YES YES
WTM 6000 YES YES YES YES
XP4 YES YES YES
614-330055-001 DECEMBER 2015 511

Glossary
1
1+1 protected system
Two transceivers are used at each end of a link to protect against transmission failure. If a
data transmission fails on the operating transceiver, it is transferred to the backup trans-
ceiver. With a 1+1 protected microwave radio link, the protection mechanism normally
allows receiver switching independently of the transmitter, and vice-versa.
1U
Standard Electronic Industries Association size for a single rack unit (44.5 mm / 1.75 in.)
A
AAA (Authentication Authorization Accounting Server)
A network server used for access control. Authentication identifies the user. Authorization
implements policies that determine which resources and services a valid user may access.
Accounting keeps track of time and data resources used for billing and analysis.
AACS
Access and Administration Control System.
ACM (Adaptive Coding and Modulation)

Adaptive modulation refers to the dynamic adjustment of modulation rate. Coding refers to
an ability to adjust individual modulation rates to support more throughput, or more sys-
tem gain. RAC 60 and RAC 6X support ACM with a modulations from QPSK to 256 QAM,
and coding options of maximum throughput or maximum system gain on each modulation
rate. For Eclipse, ACM is enabled on the RAC 60, RAC 6X plug-ins. See Adaptive Mod-
ulation.
ACU
Antenna Coupling Unit.
ADC
Analog-to-digital Converter. A device that converts an analog signal to a digital signal that
represents equivalent information.
614-330055-001 DECEMBER 2015 513

ADM
Add/Drop Multiplexer. Digital multiplexing equipment that adds/removes individual sig-
nals to/from a collection of multiplexed signals in a network.
AGC
Automatic Gain Control. A process that automatically adjusts gain as a function of a spe-
cified parameter, such as received signal level. AGC is used to help maintain a constant out-
put level when the input signal level is changing.
AIS
Alarm Indication Signal - The code generated by a regenerator upon loss of input signal or
loss of frame. A signal transmitted in lieu of the normal signal to maintain transmission
continuity and to indicate to the receiving terminal that there is a transmission fault that is
located either at, or upstream from, the transmitting terminal.
ALC
Automatic Level Control. See also AGC.
AM
Adaptive Modulation.
AM (Adaptive Modulation)
The dynamic adjustment of modulation rate to ensure maximum data bandwidth is
provided most of the time, with a guaranteed bandwidth provided all of the time. This
provides more user capacity over the air during good propagation conditions, where the
modulation level of the radio link “adapts” dynamically to the conditions of the path. On a
typical link, higher capacity will be available for better than 99.5 percent of the time. For
Eclipse, ACM is enabled on the RAC 60, RAC 6X plug-ins; AM only on the RAC 30A.
AMI
Alternate Mark Inversion Signal. A pseudoternary signal, representing binary digits. Suc-
cessive marks are of alternately positive and negative polarity and the absolute values of
their amplitudes are normally equal. Spaces are of zero amplitude.
Analog Signal
A signal that has a continuous nature instead of pulsed or discrete.
ANSI
American National Standards Institute.
ARP
Address Resolution Protocol.
ASCII
American National Standard Code for Information Interchange.
514 AVIAT NETWORKS

ATM
Asynchronous Transfer Mode. A dedicated connection switching technology that organizes
digital data into 53-byte cell units and transmits them over a physical medium using
digital signal technology. Relative to other related cells, each cell is processed asyn-
chronously and queued before being multiplexed over the transmission path.
ATPC
Automatic Transmit Power Control. A feature of digital microwave radio equipment that
adjusts the transmitter output power based on path fading detected at the receiver. This fea-
ture reduces interference with neighboring systems and permits greater link density.
AUX
Auxiliary Services Module.
AWG
American Wire Gauge. A wire diameter specification. The smaller the AWG number, the lar-
ger the wire diameter.
Azimuth
The angle in the horizontal ground plane with respect to true North (such as, horizontal dir-
ection); used in reference to antenna alignment.
B
B1
Bit Interleaved Parity-8 (BIP-8). An RSOH byte for error checking the complete STM-1 sig-
nal at the end of a regenerator section.
B2
Bit Interleaved Parity-24 (BIP-24). MSOH bytes for error checking an STM-1 signal (minus
the RSOH) at the end of the multiplexer section.
B8ZS
Binary 8 zeros substitution/Bipolar 8 zero substitution.
BBP
Baseband Processing.
Beamwidth
The beamwidth of an antenna is defined as the angle between the two half-power (-3 dB)
points on either side of the main lobe of radiation (half power beamwidth).
BER
Bit Error Ratio or Bit Error Rate - The number of erroneous bits divided by the total number
of bits transmitted, received, or processed over some stipulated period.
614-330055-001 DECEMBER 2015 515

BNC
Type of coaxial connector.
bps
Bits per second.
BSI
British Standards Institute.
Bursty Traffic
Communications data does not flow in a steady stream.
C
Carrier Ethernet
Described by the MEF as a ubiquitous, standardized, carrier-class service. It is defined by
attributes for standardized services, reliability, scalability, quality of service, and service
management; attributes that distinguish it from familiar LAN based Ethernet.
CCITT
International Telegraph and Telephone Consultive Committee.
CDMA
Code Division Multiple Access.
CE
Conformité Européene. The CE marking indicates that the product has been designed and
manufactured in conformity with the essential requirements of all relevant EU (European
Union) directives, and submitted to the relevant conformity assessment procedure.
CEMF
Cisco Element Management Framework.
CEPT
The European Conference of Postal and Telecommunications Administrations.
CEPT-1
ITU-T digital signal level 1 (2.048 Mbps) = E1
CEPT-2
CEPT-3
CEPT-4
ITU-T digital signal level 4 (139.264 Mbps)
516 AVIAT NETWORKS

CLEC
Competitive Local Exchange Carrier Market. A service provider that builds and operates
communication networks in metropolitan areas, thus providing customers with an altern-
ative to local telephone companies. USA terminology.
CMOS
Complementary Metal Oxide Semiconductor.
CODEC
Abbreviation of coder/decoder. A device that encodes and/or decodes a signal. For example,
telcos use codecs to convert digital signals to analog signals - and vice-versa.
Commisioning
A radio link is commissioned when customer traffic circuits have been connected and the
link is completely ready to provide a data service.
Community String
When configuring an SNMP agent, the community string (which is a name or combination
of characters) is input as part of the configuration information. When a management sys-
tem wants to communicate with the device, it authenticates using the community string.
There are normally two community strings accommodated by a device, one for reading val-
ues 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.
CORBA
Common Object Request Broker Architecture.
CRC
Cycle Redundancy Check.
CTB
Cable Termination Block.
CTU
Customer Termination Unit.
D
D/A
Digital to Analog.
DAC
1) For Eclipse: Digital Access Card; 2) Digital to Analog Converter.
DADE
Differential Absolute Delay Equalization. An equalization process used to render a protected
system hitless.
614-330055-001 DECEMBER 2015 517

dB
The abbreviation for decibel; the standard unit of measure for relative signal power.
DB9
A standardized connector with 9 pins.
dBm
db referenced to one milliwatt = 0 dBm. The standard unit of measure for absolute power
values.
dc
Direct current; Aviat Networks radios operate on dc power.
dc-dc Converter
An electrical device used to convert direct current from one level to another.
DCE
Data Communications Equipment.
DEMUX
De-Multiplexer.
DFE
Decision Feedback Equalizer.
DHCP
Dynamic Host Configuration Protocol.
Diagnostic Controls or Functions.

Radio system features used for troubleshooting or testing the radio or radio link. Some
examples: RF loopback, PA mute, and tributary loopback.
Digital signal (DS)

A signal format where the intelligence is transported as binary code.
Digital signal 1 (DS1)

An ANSI digital signaling rate of 1.544 Mb/s, corresponding to the North American and
Japanese T1 designator.
Diplexer
A RF filter device used to separate the Tx and Rx signals at the transceiver antenna feed
port.
Direct current (dc)

Aviat Networks radios operate on dc power.
DLC
Digital Loop Control.
518 AVIAT NETWORKS

DPP
Data Packet Plane.
DQPSK
Differential Quadrature Phase Shift Keying.
DS1
Digital signal 1: an ANSI digital signaling rate of 1.544 Mb/s, corresponding to the North
American and Japanese T1 designator.
DS3
Digital signal 3: an ANSI digital signal level 3 (44.736 Mbps), the North American T3 des-
ignator.
DSx
ANSI digital signal level x.
DTE
Data Terminal Equipment. Devices acting as data source, data sink, or both. They typically
connect to a network via a DCE.
DTMF
Dual Tone Multi-Frequency.
DTPC
Dynamic Transmit Power Control. A feature enabling the regulation of a target receive signal
level by remotely and proportionally controlling the corresponding transmitter output power
level.
Dual Link
Two radio links operating in parallel, on different frequencies, and transporting different
data.
DUART
Dual Universal Asynchronous Receiver-Transmitter
DVM
Digital Volt Meter.
DXR
Digital Cross-Connect Radio. A legacy Aviat Networks radio family.
E
E/N
Energy to Noise Ratio.
614-330055-001 DECEMBER 2015 519

E1
ITU digital signal level 1 (2.048 Mbps) = CEPT 1.
E3
ITU digital signal level 3 (34.368 Mbps) = CEPT 3.
ECC
Error Correction Code.
Eclipse Node
Refers to the Aviat Networks Eclipse INU or INUe with ODU300. Plug-in cards provide mul-
tiple link and tributary options. Frequency optins extend from 5 to 38 GHz. Modulation
options extend from QPSK to 256QAM. Protection options support hot standby, space
diversity, frequency diversity, or ring.
Eclipse Packet Node

An industry-leading wireless backhaul solution for current and next generation networks
with unique attributes for transitioning networks from TDM to all-IP. Combines high capa-
city packet transport, intelligent IP networking, and key convergence features, while retain-
ing flexible support for PDH and SDH inter-working.
Eclipse Terminal
Refers to the Aviat Networks Eclipse IDU with ODU 300. Different versions are available to
transport NxE1/DS1 tribs, STM1/OC3, Fast Ethernet, or Gigabit Ethernet. Most Terminals
are protectable, using two co-located Terminals with an inter-connecting protection cable.
EEPROM
Electrically Erasable Programmable Read Only Memory.
EIA
Electronic Industries Association.
EISA
Extended Industry Standard Architecture - A 32-bit bus standard that supports the features
of microchannel architecture. A special card is required for 32-bit operations that maintain
compatibility with the older ISA (Industry Standard Architecture).
Electromagnetic Spectrum
Though the electromagnetic spectrum was, by custom and practice, formerly divided into 26
alphabetically designated bands, the ITU formally recognizes 12 bands, from 30 Hz to 3000
GHz.
EM
Element Manager.
EMC
Electro-Magnetic Compatibility.
520 AVIAT NETWORKS

EMI
Electromagnetic interference.
EML
Element Management Level in the TMN model.
EMS
Element Management System.
End-to-end delay
The time it takes a signal to travel from point of transmission, to the point of reception.
EOW
Engineering Orderwire (Voice and/or Data).
ERP
Effective Radiated Power.
ESD
Electrostatic discharge.
ETSI
European Telecommunications Standards Institute. Provides international technical stand-
ards for wireless radios. Aviat Networks radios are in compliance with all relevant ETSI
standards.
F
Fade Margin
The amount of attenuation a link can suffer before link performance is affected. Typically
measured as the dB difference between the received signal strength and the receive
threshold.
FCAPS
Fault, Configuration, Accounting, Performance and Security functions in the TMN model.
FCC
Federal Communications Commission. The FCC is an independent United States gov-
ernment agency, directly responsible to Congress. The FCC was established by the Com-
munications Act of 1934 and is charged with regulating interstate and international
communications by radio, television, wire, satellite and cable. The FCC's jurisdiction covers
the 50 states, the District of Columbia, and U.S. possessions.
FD
Frequency Diversity. A path protection mode. The main and standby radios are trans-
mitting simultaneously and are tuned to different frequencies (at least two channels apart)
614-330055-001 DECEMBER 2015 521

to avoid interference. When a fault is detected on the active radio, the traffic is switched to
the standby radio.
FDD (Frequency Division Duplexing)

A transmission method utilizing separate channels for transmitting and receiving. See also
TDD.
FEC
Forward Error Correction. A system of error control for data transmission. It compensates
for errors induced in the transmitted stream, by sending along with the primary data pay-
load, additional information to correct for errors that occur in transmission.
FFE
Feed Forward Equalizer.
FIFO
First In First Out.
FPGA
Field Programmable Gate Array.
FSK
Frequency-shift Keying. The modulating signal shifts the output frequency between pre-
determined values.
G
G.821
An ITU-T recommendation on error performance parameters and objectives for primary-rate
(64 kbit/s) data circuits. It can be used for higher bit-rates, typically up to to 2 Mbit/s.
G.821 is a bit-based system.
G.826
An ITU-T recommendation on error performance parameters and objectives for high-speed
data circuits; circuits operating at 2 Mbit/s and above. G-826 is a block-based system.
Ga AsFET
Gallium Arsenide Field Effect Transistor.
Gain
The increase in signal power caused by a device or network (for example, the signal gain
provided by an antenna).
GHz
Gigahertz.
522 AVIAT NETWORKS

Golden Cells
These are sites where it is imperative that communications traffic continues at peak per-
formance. They are typically sites where any communications down-time can mean sig-
nificant loss of revenue, or a significant breach against a service level agreement (SLA).
GSM
Global Systems for Mobile.
GUI
Graphical User Interface.
H
H.323
A standard approved by the ITU that defines how audiovisual conferencing data is trans-
mitted across networks. In theory, H.323 should enable users to participate in the same con-
ference even though they are using different videoconferencing applications.
HDB3
High Density Bipolar Order 3. The default method of encoding transmissions for E1 and E3
radios. Substitutes a 1 for every 3 zeros.
HHT
Handheld terminal.
Hitless Receive Switching

A protected system configuration whereby if a fault occurs at the receiving end of the link,
the traffic is switched to the standby radio without causing errors.
HLDC
High-level Data Link Control. A bit-oriented synchronous data link layer protocol developed
by ISO. HDLC specifies a data encapsulation method on synchronous serial links using
frame characters and checksums.
Hot Standby
Hot Standby is a protected configuration whereby standby equipment is held ready to be
switched immediately into service if the main equipment fails.
HPA
High Power Amplifier.
HSB
Hot-Standby Protection Mode.
HSC
Hardware/Software Compatibility. Different hardware may require different software ver-
sions.
614-330055-001 DECEMBER 2015 523

I
I/O
Input/Output
ICMP
Internet Control Message protocol. An integral part of the Internet Protocol that handles
error and control messages.
IDC
Indoor Chassis.
IDU
Indoor Unit. The IDU s the control center of a split-mount radio system. It interfaces
between the customer signals and the ODU.
IEEE 1588v2
A Precision Timing Protocol (PTP) for phase and frequency synchronization. Dedicated tim-
ing packets are transmited within the data packet stream to maintain a Master-Slave syn-
chronization relationship.
IF
Intermediate Frequency. The signal frequency or frequencies intermediate between the
modem electronics and the transmitted/received frequencies.
IIOP
CORBA's Internet Inter-ORB Protocol.
Intermodulation
Intermodulation can occur in systems where multiple signals are present at the same point.
Where there is a nonlinearity in the system any signal will generate harmonics, but when
two signals are present, harmonics of both are produced. The harmonics of the two signals
can intermix, resulting in further spurious signals that are known as intermodulation
products. The result of an intermodulation signal can have a major impact on reception if it
falls in a receive channel. As the number of signals increases and/or TX power increases, the
probability of an intermodulation signal causing noise in a receive channel grows.
INU
Intelligent Node Unit. INU is the term used to describe the indoor unit of a Aviat Networks
Eclipse Node. The INU is a 1U chassis (the IDC) fitted with mandatory cards plus option
cards. It supports up to three ODUs for three non-protected links, or one protected/diversity
link and one non-protected link.
INUe
Expanded Intelligent Node Unit. The Aviat Networks term used to describe the 2U indoor
unit of an Eclipse Node. The INUe supports up to six ODUs for six non-protected links, or
524 AVIAT NETWORKS

up to three protected/diversity links.
IP
Internet Protocol. A method or protocol by which data is sent from one device to another on
the Internet.
IRU
Indoor Radio Unit.
IRU 600
An all-indoor 1+1 optimized radio transceiver for Eclipse Packet Node. Operation is on the
North American L6 to 11 GHz frequency bands. Comprises two RFUs (Radio Frequency
Unit) and an ACU (Antenna Coupler Unit) in one compact 3RU rack-mounting unit.
IRU 600 Expansion Port

Used to connect two IRU 600 radios, or an IRU 600 and a 3rd party radio, to allow com-
mon access to a waveguide.
ISI
Inter-Symbol Interference.
ISO
International Standards Organization.
ITU
International Telecommunications Union. A civil organization established to promote inter-
national standards for telecommunications.
ITU-R
International Telecommunication Union - Radio Communication Sector (formerly CCIR and
IFRB).
ITU-T
International Telecommunication Union - Telecommunication Standardization Sector
(formerly CCITT).
K
K1 and K2
In an SDH system, K1 and K2 are MSOH bytes used for * controlling the multiplexer section
protection switching, * signalling Alarm Indication Signal (AIS), Far End Remote Failure
(FERF), and * signalling Automatic Protection Switching (APS) alarms, when implemented.
614-330055-001 DECEMBER 2015 525

L
LAN
Local-area Network. A data network typically located on a user's premises or within a lim-
ited geographical area. Ethernet is the most widely used LAN transport technology.
LBO
Line Build-Out (I/O Cable Distance Compensator).
LED
Light Emitting Diode.
Link
A radio link comprises two terminals, one at each end of the link.
LMCDR
Low-medium capacity data radio.
LMT
Local Maintenance Terminal.
LNA
Low Noise Amplifier.
LO
Local Oscillator.
LOH
Line Overhead. Contains the media's framing, routing protocol, and network-layer protocol
overhead.
Loopback
A diagnostic function designed to assist testing of system components by routing traffic
back to the direction it came from.
LOS
1) Loss of signal; 2) Line of Sight.
M
MAC Address
Media Access Control address. A unique number assigned to every layer 2 Ethernet device in
the world.
Mbps
Megabits Per Second. Also Mbit/s.
526 AVIAT NETWORKS

Megahertz
1 million hertz
Message Board
Scratch pad text area that allows radio users to leave each other messages.
MGB
Master Ground Bar.
MHSB
Monitored Hot Standby.
MIB
Management Information Base. A file that describes the information that can be accessed for
each network device. The MIB is required by SNMP.
MIMO (Multiple Input/Multiple Output)

Uses multiple transmitters and receivers (multiple antennas) on wireless devices to improve
performance. The IEEE 802.11n wireless standard uses MIMO to increase maximum speed
to 100 Mbps and beyond, double the 802.11a and 11g wireless standards.
MIS
Management Information System. An organized assembly of resources that collects, pro-
cesses, and distributes data.
MLPPP (Multi-Link Point to Point Protocol)

Based on PPP, a standards-based data-link-layer protocol. MLPPP bonds multiple PPP con-
nections to support one connection with a capacity totalling the individual connections.
Typically used to leverage existing capacity on legacy TDM links whereby multiple PDH cir-
cuits are bonded together to support one high-capacity connection for Ethernet.
MMC
MultiMediaCard. A compact, removable standard for storing and retrieving digital inform-
ation in small, low-power devices. MultiMediaCards use flash technology for reusable record-
ing, and ROM technology for read-only applications.
MMIC
Microwave Monolithic Integrated Circuit.
Modulator/Demodulator
A device used to convert digital signals into analog signals suitable for transmission over
analog communications channels and/or recover digital signals from analog signals.
MSOH
Multiplexer Section Overhead. Part of an SDH frame.
MSU
Multiplexer Switching Unit.
614-330055-001 DECEMBER 2015 527

MTBF
Mean Time Between Failure. The average time (usually expressed in years) over which a
component operates without failure.
MTBO
Mean Time Between Outages. A function of MBTF, MTFF, and the probability that the mon-
itoring circuits detect a failure. The only circuits considered in the MTBO calculations are
the ones that impact traffic.
MTR
Mean Time to Restore.
MTTR
Mean Time to Repair. The average time taken to repair or replace a failed device.
Multiplex
A multiplexer sends/receives two or more signals over the same channel.
Mute
When a transmitter is muted, it is prevented from transmitting.
MUX
Multiplexer. A device that combines two or more information-carrying channels for trans-
mission over one channel.
N
NBI
North Bound Interface.
NCM (Network Convergence Module)

A plug-in module for Eclipse Packet Node for MLPPP operation. See MLPPP.
NE
Network Element.
NEBS (Network Equipment-Building Systems)

A U.S.A. government level of compliance for equipment evaluated for its function in extreme
environments/phenomena, i.e., fire, surge power faults, lightning, earthquakes, airborne con-
taminants, and temperature extremes. Eclipse Packet Node and IRU 600 are NEBS Level 3
certified.
NEL
Network Elements Level in the TMN Model.
Network Operator
The organization responsible for installing and maintaining a radio network.
528 AVIAT NETWORKS

NMI
Network Management Interface.
NML
Network Management Level in the TMN Model.
NMS
Network Management System.
NOC
Network Operations Center.
Node
A network device or device-grouping that is mid-point in a network, as distinct from a ter-
minal device that is at the end/edge of a network.
Nonprotected
A 1+0 radio configuration in which there is only one set of radio equipment.
O
O&M
Overhead and Maintenance.
Object Class
The object class identifies the radio type to which the object belongs.
Object Group
A group of network elements created using user-defined selection criteria.
OC-n
Optical Carrier Level n. The optical signal that results from an optical conversion of a syn-
chronous transport signal n (STS-n).
ODU
Outdoor Unit. ODU generally refers to the outdoor transceiver unit that is co-located with
an antenna in a split-mount radio system.
OEM
Original Equipment Manufacturer.
OFDM (Orthogonal Frequency Division Multiplexing)

Digital transmission using multiple carriers spaced apart at slightly different frequencies.
The multiple subcarriers enable the receiver to more easily detect the signals in envir-
onments with multipath and other interference. Each subcarrier can transmit a lower-speed
signal, all of which are aggregated at the receiving side into the original high-speed signal.
614-330055-001 DECEMBER 2015 529

OFDMA (Orthogonal Frequency Division Multiplexing Air)
A cellular air interface based on OFDM for multiple, simultaneous users. The multiuser cap-
ability is achieved by assigning each user a subset of OFDM subcarriers. Used in com-
munications networks such as WiMAX and LTE, OFDMA is expected to provide air
interfaces that are superior to CDMA and TDMA.
ohm
The unit of electrical resistance. A potential difference of one volt across a circuit resistance
of 1 ohm produces a current of one ampere.
OMM
Optical Multimode.
Orderwire
An auxiliary communications channel provided for use by maintenance and service per-
sonnel, typically allowing both voice and/or data transmission between radio terminals.
Oscillator
An electronic circuit designed to produce an ideally stable alternating voltage or current.
OSI
Open Systems Interconnection.
OSM
Optical Single Mode.
OSPF
Open Shortest Path First. An OSI layer 3 dynamic routing protocol.
OSS
Operations Support System.
P
PA
Power Amplifier.
PAM
Pulsed Amplitude Modulation.
Path
A radio path refers to the path traversed by the signal between two radios.
Payload Encryption
Secures wireless data traffic. Eclipse operation is FIPS-197 compliant and features an AES-
CCM cipher suite with AES counter mode data encryption and CBC-MAC data integrity val-
idation. The integrity of each data frame sent over the link is checked to ensure that received
530 AVIAT NETWORKS

data has been sent by the intended transmitter, and if it detects that received data has been
modified (man-in-the-middle attack), then received data is replaced with AIS.
PCA
Printed Circuit Assembly.
PCB
Printed Circuit Board.
PCM
Pulse-code Modulation. Modulation in which a signal is sampled, quantized and then digit-
ized for transmission. PCM is the basic method of encoding an analog voice signal into
digital form using 8-bit samples.
PCR
Paperless Chart Recorder. A software based diagnostic tool that stores operational data from
a remote radio and provides view capability to the user.
PCS
Personal Communications Service. A set of capabilities that provides a combination of ter-
minal mobility, personal mobility, and service profile management.
PDA
Personal Digital Assistant.
PDH
Plesiosynchronous Digital Hierarchy. A multiplexing scheme of bit stuffing and byte inter-
leaving. It multiplexes the lower level 64 kbit/s circuits into a successively higher order 2
Mbit/s, and 34 Mbit/s aggregate rates.
Ping
A message used to determine whether an IP address is accessible on a network.
PIU
Plug-In Unit.
PLL
Phase-locked Loop. A circuit that controls an oscillator so that it maintains a constant
phase angle relative to a reference signal.
PLT
Party Line Telephone.
PMA
Protection Mutliplex Adaptor.
PN
Part Number.
614-330055-001 DECEMBER 2015 531

ppm
Parts Per Million.
PPP
Point-to-Point Protocol. A TCP/IP routing protocol that allows communications over serial
communications lines without the use of other adapters, such as modems.
PPT
Point-to-Point Protocol. A TCP/IP routing protocol that allows communications over serial
communications lines without the use of other adapters, such as modems.
PROM
Programmable Read Only Memory.
Protection Switch
A unit that controls protection switching in hot-standby, diversity or ring protected devices.
Proxy
An entity that performs information preparation and exchange on behalf of a device it is rep-
resenting.
Pseudowires (PWE-3 – Pseudowire Encapsulation End to End)

An emulation of a TDM service over a packet switched network. Used on modern packet
switched networks to transport legacy TDM circuits.
PSU
Power Supply Unit.
PTSN
Public switched telephone network.
Q
QAM
Quadrature Amplitude Modulation. A method of modulating digital signals using both amp-
litude and phase coding.
QoS
Quality of Service.
QPSK
Quadrature Phase Shift Keying. A method of modulating digital signals using four phase
states to code two digital bits per phase shift.
532 AVIAT NETWORKS

R
RAC
Radio Access Card
RADIUS (Remote Authentication Dial In User Service)

An integrated RADIUS Client capability for Eclipse Packet Node enables authentication,
authorization and accounting of user accounts from a remote RADIUS Server for central
management of Eclipse user accounts. The RADIUS remote server provides centralized man-
agement and authentication of user names, passwords, and access permissions, and ensures
that all users have consistent access privileges throughout the network, using a common set
of user credentials.
RAS
Remote Access Server.
RCS
Reverse Channel Switching. A feature set that provides protection against potential far-end
transmitter silent failure.
RDI-L
Remote Defect Indication - Line.
Restricted Area
A location qualified in accordance with IEC Standard 60950-1 as providing an access that
can only be gained by Skilled Persons or users who have been instructed about the reasons
for the restriction applied to the location and about any precautions to be taken; and access
achieved through the use of a Tool, lock and key, or other means of security, and is con-
trolled by the authority responsible for the location.
RF
Radio Frequency.
RFI
Radio Freqency Interference.
RFU
Radio Frequency Unit.
Rigger
The member of the radio installation team responsible for installing the antenna and cabling
on the transmission tower.
RIM
Radio Interface Module.
614-330055-001 DECEMBER 2015 533

RIP
Routing Information Protocol. An OSI layer 3 dynamic routing protocol.
RMA
1) Return Material Authorization; 2) Radio Modem Adaptor.
RMS
Rock Mounting Space.
Routing Protocol
Routing protocol is a protocol used between routers to exchange routing information. OSPF
and RIP are the two most common dynamic routing protocols.
RS
Revertive Switching. A process that sends traffic back to the original working system after
the system returns online.
RSL
Received Signal Level. The signal level at the receiver input (from the antenna). RSL is usu-
ally expressed in dBm.
RSOH
Regenerator Section Overhead. Part of an SDH frame.
RSSI
Received Signal Strength Indicator. The raw indicator of signal level at the receiver input
(from the antenna). Usually expressed as a voltage, RSSI is usually converted to dBm and
presented as an RSL.
RU
Rack Unit, 1 standard EIA rack unit (44.5 mm / 1.75 inch).
Rx
Receive.
S
SAW
Surface Acoustic Wave (filter).
SD
Space Diversity.
SDH
Synchronous Digital Hierarchy. An international standard for synchronous data trans-
mission. SDH uses a multiplexing structure that enables direct access to individual 2 Mbit/s
data streams from within the higher order aggregate line signals.
534 AVIAT NETWORKS

SDLC
Synchronous Data Link Control. A bit-oriented, full-duplex serial protocol that has spawned
numerous similar protocols, including HLDC and LAPB.
Secure Management
Supports secure management access to Eclipse Packet Node radios over unsecured networks.
It protects the radio from accidental or intentional miss-configuration and provides cent-
ralized access control based on sophisticated permission attributes. An event logger records
all management activity for proper accountability and optimum troubleshooting support.
Security is provided through use of encrypted communication protocols, a requirement for
complex passwords, and protection against mechanized attacks. Communication encryption
is based on a FIPS140-2. SNMPv3 is used to secure the management communication con-
nections.
SES
Severely Errored Seconds.
SI
System International Units.
Simple Network Management Protocol

See SNMP.
Skilled Person
A skilled person in the microwave radio installation and maintenance industry is considered
to have the necessary knowledge and practical experience of electrical and radio engineering
to competently and safely carry out their work. They must have a full understanding of the
various hazards that can arise from working on and around radio installations and be com-
petent to take responsibility for their safety and the safety of any other personnel under
their immediate supervision.
SLIP
Serial-Line Internet Protocol.
SMA
Services Management Adaptor.
SML
Service Management Level in the TMN model.
SMS
Short Message Service.
SNCP
Subnetwork Connection Protection. Designates path-switched SDH rings that employ
redundant, fiber-optic transmission facilities. Organized in pairs, one fiber transmits in one
direction while the backup fiber transmits in the other. If the primary ring fails, the backup
takes over.
614-330055-001 DECEMBER 2015 535

SNMP
Simple Network Management Protocol. A networking management protocol used to monitor
network-attached devices. SNMP allows messages (protocol data units) to be sent to various
parts of a network. Upon receiving these messages, SNMP-compatible devices (agents)
return data stored in their Management Information Bases.
SNR
Signal-to-noise ratio.
SONET
Synchronous Optical Network. An ANSI standard for synchronous data transmission on
optical media that is the equivalent of SDH
Space Diversity
A protection mode. The main and standby radios are set up in Hot Standby mode, but are
connected to their own antennas. Both antennas, separated by a specific distance, are receiv-
ing the signal transmitted from the online radio at the other end of the link. If a fault occurs
in the receiving end of the link, the traffic is switched to the standby radio without causing
errors (hitless receive switching). As in Hot Standby mode, a fault detected in the online
transmitter causes that transmitter to mute and the standby transmitter to unmute.
SSC
Software-Software Compabitility.
SSL
Secure Sockets Layer.
Static Routing
Static routing requires manual configuration of the routing table within Layer 3 routers.
Data is forwarded within a network via a fixed path defined by the static routes - it cannot
adjust to changing line conditions, unlike dynamic routing.
STDM
Statistical Time Division Multiplexing. Time slots are assigned to signals dynamically to
make better use of bandwidth.
STM-0
ITU digital signal level used in Synchronous Digital Hierarchy (SDH) equivalent to a 51.84
Mbps data rate.
STM-1
ITU digital signal level used in Synchronous Digital Hierarchy (SDH) equivalent to a 155.52
Mbps data rate.
STM-N
Synchronous Transport Module-level N (Nx155.52 Mbps) where N = 1, 4, 16 or 64.
536 AVIAT NETWORKS

Strong Security
Refers to the Strong Security options supported on Eclipse Packet Node for payload encryp-
tion, secure management access, and RADIUS Client.
STS-N
Synchronous Transport Signal-level N (Nx51.84 Mbps) where N = 1, 3, 12, 48, or 192.
SU
Switch Unit.
Subnet
A portion of a network sharing a particular subnet address.
Subnet Mask
A 32-bit combination used to describe which portion of an address refers to the subnet and
which part refers to the host.
SWR
Standing Wave Ratio.
Synchronous Ethernet
Enables synchronization to be distributed over the physical layer of the Ethernet network,
through an Ethernet port, in a similar way to the SONET / SDH standards.
T
T1
A digital carrier system for DS1 signals. T1 is a term for a digital facility used to transmit a
DS1 formatted digital signal at 1.544 megabits per second. The 'T' is about the carrier facil-
ity and the 'DS' is about the signal format, which includes the muxed relationship between
DS0, DS1, DS2, and DS3.
T3
T3 is a term for a digital facility used to transmit a DS3 formatted digital signal at 44.7
megabits per second. The 'T' is about the carrier facility and the 'DS' is about the signal
format, which includes the muxed relationship between DS0, DS1, DS2, and DS3.
TAE
Transversal Adaptive Equalization.
TCM
Trellis-Coded Modulation. A bandwidth-efficient scheme that combines error-correction cod-
ing with modulation. The redundancy thus introduced by the coding does not expand the
bandwidth, since the parity bits are absorbed by the extended signal constellation. Two-
dimensional (2D) TCM uses dependency between in-phase and quadrature symbols, while
four-dimensional (4D) TCM introduces dependency between symbols of two successive inter-
vals.
614-330055-001 DECEMBER 2015 537

TCP/IP
Transmission Control Protocol/Internet Protocol. Protocols that define connectivity across
computer platforms interconnected via the Internet. The TCP protocol is responsible for an
error free connection between two computers, while the IP protocol is responsible for the
data packets sent over the network.
TDD (Time Division Duplexing)

A transmission method that uses the same channel for transmitting and receiving but sep-
arates them by time slots. In 1/1 TDD, downlink slots are interleaved equally with the
uplink; a 2/1 TDD gives the downlink twice as many slots as the uplink.
TELNET
A terminal emulation program for TCP/IP networks such as the Internet.
TFTP
Trivial File Transfer Protocol.
TIM
Tributary Interface Module
TMN
Telecommunications Management Network.
T-R Spacing
The difference in MHz between transmit and receive frequencies for duplex radios.
Trap
A program interrupt, usually caused by some exceptional situation in the user program. In
most cases, the operation system performs some action, then returns control to the pro-
gram. Used for event notification with SNMP.
Tree View
A ‘trunk to branches and leaves’ view. It is often applied to a network where the core of the
network is the trunk, and the various end-user connections are the leaves.
Tree Viewer
The Tree Viewer is part of the User Interface. The entire radio network is represented as a
tree of containers and radios. Each container (for example, a region) is represented as a par-
ent, with all the devices positioned underneath, as its children. Regions, sites, racks, and
devices are listed in alphabetical order.
Trib
Tributary.
TVT
Transparent Virtual Tributary.
538 AVIAT NETWORKS

Tx
Transmit.
TXCO
Temperature Controlled Crystal Oscillator
U
UDP/IP
Universal Datagram Protocol/Internet Protocol. Used primarily for short, broadcast mes-
sages, such as for SNMP messaging. UDP does not guarantee reliability or ordering in the
way that TCP does. Datagrams may arrive out of order, appear duplicated, or go missing
without notice. Avoiding the overhead of checking whether every packet actually arrived
makes UDP faster and more efficient than TCP, at least for applications that do not need
guaranteed delivery. Time-sensitive applications often use UDP because dropped packets are
preferable to delayed packets.
UTC
Coordinated Universal Time. A time format used when a time zone independent time and
date is required. Identical to Greenwich mean time (GMT) for most purposes.
V
V.24
Serial data communication interface. Also called RS-232.
VCO
Voltage Controller Oscillator. An electronic circuit designed to produce an ideally stable
alternating voltage.
Vdc
Volts, direct current.
VF
Voice Frequency signal.
VGA
Video Graphics Array. A display standard for IBM PCs.
Viterbi
Viterbi is a “convolutional code” which is used in data correction circuits. It operates on
serial data, one or a few bits at a time, unlike block codes such as Reed-Solomon, which
operate on relatively large message blocks (typically greater than 100 bytes).
VLSI
Very Large Scale Integration.
614-330055-001 DECEMBER 2015 539

VPN
Virtual Private Network.
VSWR
Voltage Standing Wave Ratio.
VT100
A port on the IDU for making a connection to the NMI card.
W
WAN
Wide-area Network. A network that provides telecommunication services to a geographic
area larger than that served by a local area network or a metropolitan area network.
WAP
Wireless Application Protocol.
WiMAX
Worldwide Interoperability for Microwave Access, a telecommunications technology provid-
ing wireless transmission of data, best known for providing portable, fully mobile internet
access, especially last mile wireless broadband without requiring cables or DSL. The tech-
nology is based on the IEEE 802.16 (Broadband Wireless Access) Standard.
WiMAX Base Station

A WiMAX radio receiver/transmitter with a wireless router. It is the hub of a local wireless
network, receiving signals and sending signals to be picked up by nearby subscriber sta-
tions. Base stations can be configured to be the hub between a wired network and the wire-
less network. Aviat Networks’ base station products for WiMAX are the StarMAX 6100 (one
blade) and StarMAX 6400 (up to 4 blades).
WMT
Web-based Maintenance Terminal.
WR-xx
The designation for a specific size of waveguide used to transmit the microwave RF signal.
X
XPD
Cross-Polar Discrimination.
XPIC
Cross-Polarized Interference Cancellation.
540 AVIAT NETWORKS

B
Background Maps 66
Index Backups
Eclipse 240
menu functions 50
Browser 417
launching from device 418
1
to access non-Aviat devices 417
15-minute data collection 390 Bulk Configuration 201
enabling and disabling 390 Classification 212
for DAC 393 definition 202
delete 211
A Scheduling 214
setting up 202
Accedian
settings 206
deploying 114
Activating 106 C
Eclipse radio software 221
Eclipse software 221, 231 Capacity Report
managed status for a device 156 scheduling 507
TRuepoint software 233 Carrier Ethernet
XP4 tributary loopback 437 ERP ring management 282
XP4 tributary loopback, local 441 Ethernet OAM 263
Adding 106 overview 243
devices 106 VLAN management 244
logical link 364 VLAN overview 244
prefilters 329 CAUs 122
ADR customize event names 310
deploying 114 deploying 122
Alarms diagnostic controls for 451
conditions activating XP4 protection 444 CB 149 433
icons and 89 Changing 102
link to performance criteria 413 event browser options 321
manually resynchronize 308 password 37
manually resynchronize for TR 6400 308 TNet device subnet 219
TNet inputs and outputs 429 XP4 protection settings 443
Altium 58 Chassis Views 73
configuration view 196 Circuit Diagnostics 381
craft tool 417 end-to-end tests 386
craft tool instructions 421 options 386
data collection 388 segment tests 386
icon 58 set up test 384
Network Health Report 474 Circuit Trace
security log entries 340 circuit features 179
Altium MX 2+0 58 single circuit 182
icon 58
DXLI AVIAT NETWORKS

Circuits 177 Network Health Report 474

Circuits tab 61 resync alarms 308
delete 190 support of 31
diagnostics 190, 381 Contact Details 38
diagnostics window 381 Containers 107, 109
event browser for 186 adding 107
tracing 177 creating 106
Cisco deleting 111
deploying 114 labeling in map 69
deployment prerequisite 123 renaming 111
supported device list 13 user defined 108
Class Checking 118 CraftTools
invalid deployment if not performed 138 about 417
Clear Correlation 307 DXR NET 417
Clearing 307 enabled functions 419
Clock Synchronization launching 419
Clock Sync Report 490 LE3000 421
Network Health Report 485 list of available 417
saving data of 485 NCT 418
viewing 192 overview 380, 417
Community String 113 Portal 417
Computer Equipment TNet Web 418
display resolution on monitor 35 TNet Web details 424
Configuration 194 WMT 417
save as .CSV file 194 WMT details 421
view radio 194, 201 XP Web 418
Configuration Alarm Units 122 Creating
Configuration Profiles 201 configuration profile 202
bulk configuration 201 RF links 169
creating 202 RF links from Find 170
delete 211 RF links from Tree Viewer 169
executing 205 scoreboard 370
menu functions 48 Scoreboard Group 369
settings 206 scoreboard groups 369
Configuring 348 scoreboards 370
Constellation 124 CTR 8300
DXR 200 radios 165 backup and restore 240
DXR SMAs 165 deploying 125
protected TNet links 430 device support in ProVision 18
Constellation EOAM 263
configuration viewer 196 ethernetbandwidth 399
configuring 124 VLAN management 244
deploy new 124 CTR 8440
diagnostic controls for 447 backup and restore 240
equipment view 73 deploy via autodiscovery 148
Inventory Report 458 ethernet bandwidth 399
DXLII AVIAT NETWORKS

submap view 71 daily 389

supported functions 19 ethernet performance data collection 393
CTR 8540 menu functions 49
backup and restore 240 overview 388
deploy via autodiscovery 148 performance monitoring data 388
deploying 125 RSSI data 388
ERP ring management 282 Database
ethernet bandwidth 399 backup via menu 50
node licenses 237 locking 35
submap view 71 searching 83
supported functions 20 Deactivating an XP4 Tributary Loopback 441
VLAN management 244 Deleting 363
CTR CTR 8611 circuits 190
support in ProVision 21 container 111
CTR devices device from a service 362
device support 18 devices 154
Ethernet performance data 393 event browser 323
VLAN management 244 event notification rule 347
CTR Portal 417 event prefilter 335
Custom Icons logical links 365
Containers 108 pre-filtering 335
Generic Devices 130 radio frequency links 175
Custom Reports 498 Scoreboard Group 370
Customer Support 40 scoreboards 373
Customizing 81 server reports 469
event browser 317 Dependencies 297
deploying, devices 103
D managing, devices 103
DAC Plug-Ins 393 Deploying 112
view ethernet performance 394 class checking for Eclipse 118
DART 58 Constellation 124
configuration profile settings 210 containers 106
configuration view 196 definition 101
device support 33 devices 103
diagnostics 452 DXR 200 120
icon 58 DXR SMA 120
loopbacks 452 Eclipse node 117
DART NMS Trap Destination 210 EMS Proxy 131
Data 157 generic SNMP device 128
into usable information 4 Harris Stratex SNMP device 112
managing over time 4 MegaStar 1+1 115, 122, 132-133
Data Collection MegaStar MN 115
15-minute collection 390 multiplex radios 114
about 388 network autodiscovery 148
change device status for 392 NetworkElements 131
DAC plug-in 393 prerequisites 103
DXLIII AVIAT NETWORKS

process overviews 103 DXR 418

SMA device 120 device support 33
SNMP devices 112 DXR 200 120
TNet device into proxy manually 148 configuration view 196
TNet devices 144 managing 165
TNet proxy 147 DXR 700 162
TNet troubleshooting 147 configuration view 196
TRuepoint devices 138 DXR SMA 120
Device Software managing 165
activating after upload 230
Devices 11 E
apply pre-filter for events to 333 Eclipse
Aviat SNMP Devices 112 backup configuration of 240
change data collection status 392 deploy via autodiscovery 148
configuration view 194, 201 ERP ring management 282
deleting 154 ethernet bandwidth use 399
deleting from service 362 network autodiscovery 148
deploying prerequisites 103 Network Health Report 474
list of supported 12 security log entries 340
managing 156 support of 16
object pop-ups 92 VLAN management 244
rename 153 Eclipse configuration 240
reset XP4 445 SNMPv3 users 209
services overview 360 Eclipse Ethernet Priority Mapping for DAC
sleep status 311
GE 207
states 92
Eclipse License 48
unmanaging 158
Eclipse NMS Traps Destination 208
Diagnostic Controls 446
Eclipse Node 117
CAU 451
license, installing 237
circuits 190
menu functions 48
Constellation 447
Eclipse Optimization Gateway 198
DART 452
Eclipse OSPF Settings 208
DVA 453
Eclipse Radios 117
MegaStar 455
data collection 388
using 446
deploying protected node 119
when applied 417
radio frequency links, creating 171
Disabling 390
remotely upgrading software 221
Discovering 148
Eclipse Reports 457
DXR 200 radios 165
fault report 465
DXR 700 radios 162
inventory report 458
Ethernet links 167
Eclipse Security Status Report 488
RF links 167
Eclipse Software 221
TRuepoint 6500 configurations 162
activating 231
Display Resolution 35
loading example 1 222
DVA 453
remote upgrade 221
upgrade process 222
DXLIV AVIAT NETWORKS

Eclipse Time Server Settings 209 viewing discovered EOAM MAs 265
Eclipse Time Zone Settings 209 Event Browser 314
Editing 373 acknowledge events from 303
performance data status 392 customizing 317
Scoreboard Group 370 deleting 323
ELink description 80
deploying 114 filtering event logs 326
Enabling 390 hide 45
Equipment Malfunctions 378 maximum events 80
Equipment Views navigating 314
about 73 new, opening 47
opening 73 opening 314
ERPs option settings 321
configuring 286 option settings, values 322
ERP ring management 282 overview 314
overview 282 pop-up menu for events 81
provisioning 286 printing 325
viewing ring config 283, 285 resize 45
Ethernet save settings in 81
bandwidth use view 399 save to file 324
change perfornace data collection save view 315
status 392 saving 315
delete Ethernet link 176 security log, opening 47
Ethernet OAM 263 view saved 316
Network Health Report 480 viewing 81
performance data collection 393 Event Log 326
setting priority mapping 207 deleting pre-filter 335
view performance 394 filtering overview 326
Ethernet Bandwidth Utilization 399 modify pre-filter 334
Ethernet Links object level pre-filter 332
about 167 objects to be pre-filtered 327
creating 173 pre-filter from Event Browser 333
delete 176 pre-filtering view 328
discovering 167 root level pre-filter 329
Ethernet NetworkHealth Report Event Notification 341
scheduling 507 adding rule 343
Ethernet OAM 263 configuring rule 348
configuring 275 delete rule 347
create nwe 275 dialog box 354
deleting 280 editing rule 343
list of discovered EOAM MAs 266 email notification setup 351
logical topology 267 pop-up message notification setup 353
overview 264 preferences 342
physical topology 269 script execution setup 357
provisioning 275 Event Pre-filter 47
troubleshooting 270
DXLV AVIAT NETWORKS

Event Properties 301 H

probable cause tab 302
Event States 299 Hardware
acknowledged 300 for radio 201
cleared 300 Help 41
cleared by user 300 Hierarchical Map 66
unacknowledged 300 Highlight 322
Event Status 299 History 404
Event Traffic 157
I
Events 295
customize names 310 Icons 9, 58
manually resynchronize alarms 308 Altium MX 2+0 58
manually resynchronize TR 6400 caution 9
alarms 308 Container icons 57
prefiltering 329 DART 58
prefilters DART protected 58
delete 335 display and status 89
modify 334 DXR 58
severity color coding 91 DXR 700 58
states 299 DXR 700 protected 58
verifying receipt of 157 DXR protected 58
viewing 300 event severity color codes 91
viewing prefilters 328 information 89
Exceptions 36 reading data for 89
user session 36 Velox 59
Exiting 37 warning 9
XP4 16/E3/DS3 59
F XP4 16/E3/DS3 remote 59
Fault Report 465 XP4 16/E3/DS3 remote protected 59
Filtering 326 XP4 2/4/8x 60
events at input 328 XP4 2/4/8x protected 60
Flat Map 64 XP416/E3/DS3 protected 59
In and Out of Service
G via submap 73
In and Out of Service View
G.821 431
via Tree Viewer 56
G.826 Performance Data 404
Increase
identify problems for device 406
TNet Proxy subnets 219
view trends for 409
Installing
Generic Devices
Eclipse node license 237
custom icons for 130
Interface Views 78
customize event names 310
Inventory Report 458
deploying 128
saving 459, 461
interface view 79
saving, multi-radio version 462
support of 32
viewing 459
DXLVI AVIAT NETWORKS

IP Address M
change for TNet Proxy 219
menu functions 48 Manager 57
searching for 85 Managing 156
view/change for network 217 definition 101
devices 156
L DXR 200 radios 165
DXR SMAs 165
Launching 419
event dependencies 297
LE3000 78
event scenarios 367
craft tool, installing 421
events, overview of 295
deploying 114
radios
Inventory Report 458
prerequisites 297
Network Health Report 474
removing from device 158
security log entries 340
Managing Events 295
License 39
network events 299
CTR Node 237
prerequisites 297
Eclipse Node 237
sources of event data 295
evaluation 39
suggested process 296
menu functions 48
Manually Clearing Events 307
viewing details 39
Map Viewer
Licensing
Flat Map 64
licensing report 496
hide 45
Licensing Report 496
map background graphic 66
Link 169
Physical view 63
Link Report 492
properties 64
non-protected 172
repositioning objects 153
protected 172
resize 45
ring-protected 172
submaps 71
Links
tools 64
autodetection of WTM links with CTR 128
visible object types 63
Loading 221
Maps
Logging In 35
annotating 69
exceptions 36
backgrounds, add 68
multiple users 35
backgrounds, remove 68
Logging Off 37
labeling containes 69
Logging Out 37
labeling map items 69
Logical Links 364
moving objects 153
deleting 365
VLAN 252
renaming 365
MegaStar 455
Loopback Test 384
device support 34
DART 452
equipment view 73
run 384
equipment views 73
XP4 radio 437
resync alarms 308
MegaStar 1+1 115
MegaStar MN 112
DXLVII AVIAT NETWORKS

Menus 45 Performance Analysis 5

main user interface 45 Performance Data
menu items 45 15-minute collection 390
pop-up menus 53 daily 389
MicroStar 112 Ethernet 393
Modifying 334 Performance Data collection screen 392
scoreboard groups 370, 373 performance history 404
performance thresholds 413
N performance trends 409
Naming Standards 102 Performance History 404
Navigating 35 Performance Monitoring 388
Event Browser 80 Performance Threshold 413
menu bar 45 TRuepoint 6500 specific 415
Network Performance Trends 409
IP addresses 217 Physical Map 63
Network Elements Pop-Up Data 92
about 131 Pop-Up Menus 53
change proxy assignment 163 Portal 417
deploying 131 craft tool table 380
Network Events 299 Pre-Deploying 103
acknowledging 303 Prefilters 329
clearing 307 Prerequisites
status of 299 event management 297
Network Failure 404 for deploying devices 103
Network Health Report 474 managing, radios 297
Clock Synchronization 485 system diagnostics 378
device types 474 Printing 325
values 477, 482, 486-487 Protected Radios
viewing 475 deploying 114
NOC 1 Protection Settings 443
Notification Dialog Box 354 Proxies 145
about 131
O configuration management 163
deploying 131
Objects 153 Purging
pre-filtering activated 327 database 50
pre-filtering icon 328
repositioning in map 153 R
Online Help 41
terminology 9 Radio Frequency Links 167
using 41 about 167
create from Find function 170
P create from Tree Viewer 169
creating for Eclipse radios 171
Passwords deleting 175
changing 37 Discover RF Link function 167
Path Degradation 378 Eclipse link types 172
DXLVIII AVIAT NETWORKS

Eclipse radios 171 NOC operator 1

verifying for Eclipse or TRuepoint 167 RSSI 434
Radio Tasks 93 view TNet performance for 434
Radios 103
configuration data 194 S
configuration profiles 202 Sagem-link Radio 112
deployment process 103 Saving 462
icons for 57 event browser contents 315, 324
pop-ups for 92 event browser view 315
pre-deploying before network rollout 103 inventory report 459, 461
tasks 93 server reports 469
5 and 15-min data collection 93 Scenarios 367
performance thresholds 93 Scheduling Reports 509
waking 314 Scoreboard Groups 367
Regions creating 369
user defined 108 deleting 370
Renaming 153 editing 370
container 111 functions 368
devices 153 modifying 370
logical link 365 scoreboards 370
service 363 viewing 47, 368
TNet Proxy 219 Scoreboards 370
Reports 457 creating 370
create custom 498 definition 370
Eclipse fault 465 deleting 373
Eclipse Security Status 488 editing 373
Ethernet Network Health Report 480 modifying 373
inventory report 458 view event browser from 374
licensing report 496 Searching
network health reports 474 all data 83
saving Inventory, multiple radios 462 locate function 46
saving Inventory, single radio 459, 461 search all data 84
scheduling 509 via Tree Viewer 87
security status 488 Security
server reports 469 Eclipse Security Status Report 488
Repositioning 153 Security Log 340
object 153 Server Reports 469
Resetting Service Availability View
XP4 445 via Tree Viewer 56
Restoring Service Availabilty View
backup configurations, saved 240 via submap 73
RF NetworkHealth Report Service Links 364
scheduling 507 Services 364
Right-click Menus 53 deleting a service 363
Roles removing a device 362
NOC engineer 1 renaming a service 363
DXLIX AVIAT NETWORKS

Sleep Status 311 Technical Support

setting for device 311 version number 40
sleep value options 311 viewing contact information 40
SNMP Telnet 417
SNMPv3 User Account Configuration 209 launching from device 418
SNMP Devices 112 to access non-Aviat devices 417
deployment details 118 TNet 144
Software 221, 380 alarm input and output 429
client 3 CB 149 diagnostic values 433
for radio 201 change subnet 219
how it works 3 configure protected links 430
optimum use 4 craft tool details 424
receiving events 157 craft tool for 418
server 3 deploying 144
skill set prerequisites 6 Device Support 34
user accounts 50 diagnostic tools 429
version number 40 features for devices 425
Software Table 45 G.821 diagnostic values 431
Spectrum II 474 manually deploying into proxy 148
Status 93 Protection diagnostic values 430
asleep 93 proxies 145
connecting 93 RSSI diagnostic values 434
errored 93 severity levels for inputs 426
managed 93 troubleshooting 147
unmanaged 93 user-defined inputs and outputs for 426
Submaps 71 TNet Proxy 144
Symmetricom change IP address 219
deploying 114 change name 219
device support 34 configuration 218
System Diagnostics 378 deploying 147
circuit diagnostic window 381 increase subnets 219
circuit diagnostics, run 384 view/change 218
circuits 381 viewing status 220
DART diagnostics 452 TNet Proxy Viewer 220
diagnostics 377 Topology
overview 377 exporting 46
prerequisites 378 trademarks i
procedures 381 Tree Viewer
using 378 hide 45
XP4 details 436 object pop-ups 92
resize 45
T searching inside 87
Task Manager screen 82 user interface 55
Tasks 93 using toggle 56
radio 93 Tributary Loopback 437
activate for XP4 437
DL AVIAT NETWORKS
activate local for XP4 441 User Session 35

local MSU E3 438 exceptions 36
remote SU E3/DS3 438 exiting 37
Troubleshooting start 35
EOAM 270 starting 35
TNet deployment 147 Users
VLANs 254 contact details, saving 38
TRuepoint 138 multiple user sessions 35
deploying 138
equipment view 73 V
equipment views 73 Velox
Inventory Report 458 configuration view 196
IP address capture 119, 125, 142 craft tool for 418
Network Health Report 474 icon 59
redundant NMS connection security log entries 340
support 119, 125, 142 Verifying
security log entries 340 event traffic 157
support of 29 events, receipt 157
verify RF links 167 RF links, Eclipse 167
TRuepoint 4000 140 RF links, TRuepoint 167
deploying 138 Version Number 40
resync alarms 308 viewing 40
TRuepoint 4040 30, 139 Viewing
deploying 138 customer contact details 40
TRuepoint 5000 141 Ethernet performance 394
deploying 138 event log pre-filtering 328
TRuepoint 6400 141 event properties 301
deploying 138 events 300
resync alarms 308 Flat Map 64
TRuepoint 6500 142 inventory report 459
deploying 142 license details 39
manually discover 162 performance data status 392
Performance History 408 Physical Map 63
Performance Threshold 415 prefilters 328
unique characteristics 142 radio configuration 194, 201
TRuepoint Software 228 saved event browser view 316
activating 233 scoreboard groups 368
Scoreboard Groups 368
U
version number 40
Unmanaging 158 XP4 protection settings 443
Upgrading VLANs
Eclipse radio software 221 configuring 257
User Interface 44 deleting 262
customizing 44 identify and fix faults 254
maximize 45 overview 244
minimize 45 tab options 246
DLI AVIAT NETWORKS

topology view 250 tributary loopback

view discovered 245 local MSU E3 438
viewing 246 remote SU E3/DS3 438
viewing in maps 252
VLAN management intro 244
W
Waking 311
radios 314
warranty i
Windows Applications 95
integrating 95, 97
WL1000 230
craft tool 421
interface view 79
WTM
links with CTR autodetected 128
WTM 3100
device support 23
WTM 3200
device support 24
WTM 3300
device support 25
event value details 314
WTM 6000
deploying 114
device support 27
manually discover configuration 161
RF link creation 170
X
XP4 436
activate loopback 437
activate loopback, local 441
configuration view 196
craft tool for 418
data collection 388
Device Support 34
diagnostics 436
local loopback types 442
loopbacks 437
protection settings 443
reset 445
DLII AVIAT NETWORKS

614-330055-001
WWW.AVIATNETWORKS.COM

Aviat PV 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

Aviat PV User Manual PDF

Uploaded by

Copyright:

Available Formats

PROVISION

614-330055-001 DECEMBER 2015 I

Aviat Networks Technical & Sales

See our web site at: http://www.aviatnetworks.com/services/customer-support/technical-assist-

Sales and Sales Support:

614-330055-001 DECEMBER 2015 III

Corporate Headquarters International Headquarters

User Manual Table of Contents

ProVision Copyright and Terms of Use i

CHAPTER 1. WELCOME TO PROVISION 1

CHAPTER 2. DEVICE SUPPORT IN PROVISION 11

614-330055-001 DECEMBER 2015 V

CHAPTER 3. NAVIGATING PROVISION 35

CHAPTER 4. DEPLOYING AND MANAGING DEVICES 101

Deploying Devices 106

614-330055-001 DECEMBER 2015 VII

About Circuits and Circuit Management 177

CHAPTER 5. CARRIER ETHERNET MANAGEMENT 243

VIII AVIAT NETWORKS

Viewing List of Discovered VLANS 246

CHAPTER 6. MANAGING EVENTS 295

614-330055-001 DECEMBER 2015 IX

Manually Clearing a Network Event 307

Adding a Scoreboard 370

CHAPTER 7. SYSTEM DIAGNOSTICS AND REPORTS 377

614-330055-001 DECEMBER 2015 XI

Constellation Diagnostic Controls 447

CHAPTER 8. DEVICE AND NETWORK REPORTS 457

XII AVIAT NETWORKS

This section includes the following topics:

614-330055-001 DECEMBER 2015 1

The Goals of ProVision

How ProVision Works

614-330055-001 DECEMBER 2015 3

Getting the Most Value from ProVision

Turning Data Into Information

Managing Data Over Time

Using Performance Analysis

614-330055-001 DECEMBER 2015 5

What You Need To Know To Use

614-330055-001 DECEMBER 2015 7

Documentation Conventions and

W AR NING : A warning item identifies a s er ious phys ic al danger or

NOTE : A note item identifies additional infor mation about a pr oc edur e

614-330055-001 DECEMBER 2015 9

614-330055-001 DECEMBER 2015 11

List of Devices Supported in ProVision

Partner Product Devices

Devices Supported with GDS Packages

614-330055-001 DECEMBER 2015 13

l Cisco ASA 5500

l Tejas TJ1600 Mux

614-330055-001 DECEMBER 2015 15

Eclipse Device Support

How ProVision Supports Eclipse

Function Area Information

614-330055-001 DECEMBER 2015 17

CTR Device Support

CTR 8300 and ProVision

How ProVision Supports CTR 8300 Devices

Function Area Information

CTR 8440 and ProVision

How ProVision Supports CTR 8440 Devices