Installation and 5ProVision Administration Manual 6.11.

PROVISION
INSTALLATION & ADMINISTRATION

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

PROVISION INSTALLATION AND ADMINISTRATION MANUAL
Service and Technical Support:

For sales information, contact one of the Aviat Networks headquarters, or find your regional sales
office at http://www.aviatnetworks.com/.
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: + 65 6496 0999
Toll Free for Sales Inquiries: Sales Inquiries:
+ 1 888-478-9669 +1-321-674-4252
Sales and Sales Support:

For customer service and technical support, contact one of the regional Technical Help Desks listed below.
Americas Technical Help EMEA Technical Help Desk Asia Pacific Technical Help
Desk Desk
Aviat Networks, Inc. Aviat Networks Aviat Networks
5200 Great American Park- 4 Bell Drive Bldg 10, Units A&B
way Hamilton International Tech- Philexcel Industrial Park
Santa Clara, California 95054 nology Park M. Roxas Hi-way
U. S. A. Blantyre, Glasgow, Scotland Clark Freeport Zone
G72 0FB Philippines 2023
United Kingdom
Fax: +1 210 526 6315 Fax: +44 1698 717 204 Fax: +63 45 599 5196
Email: Email: Email:
TAC.AM@aviatnet.com TAC.EMEA@aviatnet.com TAC.APAC@aviatnet.com
Global Support Hotline - +1 210 526 6345
Call this phone number for support from anywhere in the world. Aviat Networks' Global Support Hot-
line is available 24 hours a day,7 days a week, providing uninterrupted support for all our cus-
tomers.
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 supported and prioritized accordingly.
See our web site at: http://www.aviatnetworks.com/services/customer-support/technical-assistance/
II AVIAT NETWORKS
614-330053-001 APRIL 2014 III

Table of Contents
ProVision Copyright and Terms of Use i

Table of Contents v
CHAPTER 1. ADMINISTRATOR INTRODUCTION 1

About ProVision 3
Administrator Documentation Organization 4
Conventions and Terminology 5
CHAPTER 2. SYSTEM DESCRIPTION 7

ProVision Architecture 8
ProVision Deployment Options 9
Single Server/Client Deployment 9
LAN Client Deployment 10
WAN Client Deployment 11
Standby Server Deployment 12
Standby Server Deployment: Sharing or Separate Hardware 13
Standby Server with WAN and Separate Hardware 14
Network Communication, Ports, and Firewalls 16
Device Support 16
Communication Frequencies with Network Devices 16
Network Communication Ports for Firewalls 18
FTP Transfer Firewall Configuration 18
Recommended Port Configuration 19
Network Management Concepts 22
Network Management and SNMP 22
Managers, Agents, and MIBs 22
Manager-Agent Model 23
Manager and Agent Communication 23
Information Exchange and the MIB 24
MIB Organization 24
Internet and Enterprise-Specific MIBS 25
Managing Proprietary Protocol Devices 26
SNMP Traps and Managed Devices 27
CHAPTER 3. INSTALLING PROVISION 29

Installation Prerequisites 31
Platform Requirements 31
614-330053-001 APRIL 2014 V

Virtual Machine Installation Requirements 35

Device Counts: Server Loading Value 36
ProVision Installation DVD Set 38
Eclipse Installation CD 39
Licensing, Database, Node and MTOSI NBI Support 39
Administrator Username and Password 40
Server IP Address 40
RMI Interface for Installation 40
Pre-Installation Tasks 42
Setting Up Computer Equipment and User Rights 42
Disabling Other SNMP Trap Services 42
Exclude Scanning MySQL Temporary Directory 43
Disabling the PC Power Saving Setting 43
Installing Java for a Solaris Server 43
ProVision Commands 44
Installing and Uninstalling ProVision 46
Installing the ProVision Windows Server 46
Install ProVision Server Software - Solaris 50
Installing the ProVision Client 52
Client Software Installation Via DVD 53
Client Software Installation From the Server 54
Uninstall ProVision Server Software 55
Uninstall ProVision Server Software - Solaris 56
Uninstall ProVision Client Software 57
Standby Server Installation and Maintenance 58
Installing and Uninstalling the ProVision Redundancy Controller 60
Uninstalling the Redundancy Controller 64
Windows 8 Navigation and Uninstallation 65
Navigation 65
Uninstalling ProVision on Windows 8 66
CHAPTER 4. UPGRADING PROVISION 67

Introduction to Upgrading 68
Upgrade Process Options 70
Upgrade Checklist 72
Upgrade Prerequisites 72
Backing Up Data from Current Installation 73
Upgrading Primary and Standby Servers 73
Scheduling Upgrade Installation 74
Impact of Upgrade 74
Upgrade Installation of the ProVision Client 76
Database Restore Upgrade 79
Database Migration Upgrade 81
Topology Upgrade 84
Upgrading the Redundancy Controller 85
VI AVIAT NETWORKS
Before You Upgrade 85

Upgrading the Redundancy Controller Only 86
Upgrading the Redundancy Controller and the ProVision Server 88
Stop, Start, Backup, and Restore the Redundancy Controller 91
After Upgrade: Review and Testing 93
Checking Device Compatibility 93
Checking for Invalid Deployed Devices 95
Rollback to Previous Version 97
CHAPTER 5. LICENSING PROVISION 99

About ProVision Licenses 100
Trial Evaluation ProVision License 101
Permanent Server License Application 102
Licensing Procedures 103
Determining the Server’s IP Address 103
Requesting a Permanent License 104
Activating a ProVision Server License 104
CHAPTER 6. SETTING UP PROVISION 107

Prerequisites for Setting Up ProVision 108
Workflow for Setting Up ProVision 109
Changing FTP Server Port 111
Changing Syslog Server Port 112
Configuring for Multiple Network Card Systems 114
Enabling and Disabling Ethernet OAM, VLAN and ERP Ring Functionality 116
Enabling and Disabling Event Driven Clock Synchronization Discovery 117
CHAPTER 7. ACCESS CONTROL 119

Introduction to Access Control 120
Single Sign On and Strong Security 122
ProVision User Security Profiles 124
User Account and Access Control Procedures 128
Creating ProVision User Accounts 128
Changing a ProVision User Account 132
Deleting a ProVision User Account 134
Changing Security Login Policies 135
Managing User Sessions 137
Locking Eclipse Portal Write Access from ProVision 138
Viewing the Security Log 140
Device Security Accounts 141
Editing SNMP Community Strings 142
Setting Eclipse Device Security Values 143
Setting Eclipse Security Accounts 143
Set Up Multiple Eclipse Radio Accounts 145
614-330053-001 APRIL 2014 VII

Update Passwords for Multiple Radio Accounts 146

Set Up NOC Operators with Read Only Portal Access 147
Setting Device Security Account Values 148
Setting SNMPv3 Security Access 149
Device Security Access for Multiple Radios 151
Clearing Device Security Accounts 152
Enabling a RADIUS Server 154
Updating Eclipse RADIUS Authentication Settings 157
Prerequisites 157
Defining the RADIUS Configuration Settings 158
Setting the Radius Configuration on a Single Eclipse Radio 159
CHAPTER 8. MIGRATING TOPOLOGY 161

About Migrating Topology 162
Importing the Topology 163
Exporting the Topology 164
ProVision 2.3/3.0 Topology Migration Tool 166
Migrating StarView Data into ProVision 171
Extracting Constellation Device and Topology Data from StarView 175
CHAPTER 9. DATABASE AND SERVER MANAGEMENT 179

About Managing and Backing Up the ProVision Database 180
Daily, Weekly, and Monthly Backup Processes 181
Changing Database Configuration 182
Database Backup Procedures 184
Set Backup Preferences 185
Manual Backup Procedure 185
Scheduled Backup Procedure 186
Restoring the ProVision Database 187
Checking the Database Integrity 189
Changing Database Purging Criteria 190
Configuration Backup and Restoration 191
Data Backup and Sharing Using Topology Exports 195
Server and Services Management Procedures 196
ProVision Database Commands 196
Monitor Server Disk Space and Memory 197
Stopping the ProVisionServer 199
Starting the ProVision server 200
Resetting the Database 200
Removing ProVision From System Services 201
Installing ProVision as a System Service 202
CHAPTER 10. REDUNDANT SERVER DEPLOYMENTS 203

Managing Standby Servers 205
VIII AVIAT NETWORKS

About Primary and Standby Servers 205

Standby Server Configuration Prerequisites 206
DCN Bandwidth Requirements for a Standby Server 207
Synchronizing Primary Server and Standby Server Databases 208
Configuring Server Type as Primary 209
Configuring Server Type as Standby 210
Primary Server Failure: Activating a Standby Server 211
Primary Server Restoration 211
If The Primary Server Fails: Managing and Restoring After Failover 213
Restoring The Primary Server 214
Hot Standby Server Redundancy 217
About the Redundancy Controller 218
DCN Bandwidth and Latency for the Redundancy Controller 220
Normal Operation of Redundancy Controller 222
Locked Operation of the Redundancy Controller 223
Logging Into the Redundancy Controller 224
Redundancy Controller Status Screen 225
Redundancy Controller Configuration Screen 229
Redundancy Controller Security Screen 231
Troubleshooting the Redundancy Controller 233
Dormant Server Power Loss or Shutdown 233
Active Server Power Loss or Shutdown 234
Network Communication Failure Between Active & Dormant Servers 236
Using Both the Redundancy Controller and the Standby Server 238
CHAPTER 11. GENERIC DEVICE MANAGEMENT 239

Managing Generic Devices and Packages 240
Add a New Package 242
Re-Assigning a Package to a Generic Device 244
Editing Package Information and Events 245
Import and Export Package Data (.XML Files) 245
Loading a Generic Device Service Package 246
Renaming a Package 248
Entering a Description for a Package 249
Setting Trap Mapping to Identify Package Events 250
Trap Mapping Example 254
Managing Imported MIBs 259
Importing Trap Mapping from a MIB File 260
Importing Trap Mapping from a .CSV File 262
Setting Matching Rules for Trap Mapping 263
Match Rules Example: Multiple Trap Types 265
Severity Resync Functions 268
Configuring Generic Device Resynchronization Alarms 268
Creating Custom Events for Packages 270
Resynchronization and Custom Events Example 272
614-330053-001 APRIL 2014 IX

Launching Generic Device Windows Applications from ProVision 276
CHAPTER 12. NORTHBOUND INTERFACE 279

Introduction to the Northbound Interface 280
NBI Event Management 283
Introduction to NBI Event Management 283
Setting Up an Event NBI 285
Deploying an Event NBI 286
Testing an Event NBI Configuration 291
Saving, Printing, and Viewing an Event NBI Configuration Report 294
Editing an Event NBI Configuration 295
Enabling/Disabling an Event NBI 296
Resynchronize an Event NBI 297
Remote Resynchronize 298
Deleting an Event NBI 298
Renaming an Event NBI 299
Configure Services 299
System Integration for NBI Event Management 300
NBI Performance Data Management 304
About NBI Performance Data Management 304
Performance Data Collection 305
Deploying a Performance Data NBI 307
Editing Performance Data NBI Configuration 308
Enabling/Disabling a Performance Data NBI 310
Deleting a Performance Data NBI 311
Renaming a Performance Data NBI 311
Performance Data Files 312
NBI Configuration Management 316
About NBI Configuration Management 316
Deploying a Configuration NBI 317
Editing the Settings for a Configuration NBI 318
Setting the Configuration NBI 319
Enabling/Disabling a Configuration NBI 319
Resynchronizing a Configuration NBI 320
Deleting a Configuration NBI 321
Renaming a Configuration NBI 321
System Integration 322
NBI Topology Management 326
About NBI Topology Management 326
Deploying a Topology NBI 327
Editing the Settings for a Topology NBI 328
Enabling/Disabling a Topology NBI 329
Deleting a Topology NBI 329
X AVIAT NETWORKS
Renaming a Topology NBI 330

Configuring a Topology NBI for Services 330
NBI Topology Files 331
System Integration - NBI Topology Files 331
CHAPTER 13. HELP DESK REPORTS 335

The Help Desk Report 336
Running the Help Desk Report 336
Using Commands to Run Help Desk Reports 337
Saving or Deleting Help Desk Reports 338
CHAPTER 14. PROVISION WEB SERVER 341

Accessing the ProVision Web Server 342
Downloading ProVision Client from the Web Server 344
Help Desk Reports from the Web Server 345
Log Access from the Web Server 346
APPENDIX A. MTOSI NBI AND PROVISION 349

MTOSI NBI Overview 349
MTOSI NBI Use Requirements and Installation 350
Available MTOSI NBI Services 351
Supported Devices 353
Supported Eclipse Plugins and Software Versions 353
Uninstalling the MTOSI NBI 353
Further Documentation 354
Index 355
614-330053-001 APRIL 2014 XI

Chapter 1. Administrator
Introduction
Welcome to the ProVision Installation and Administration Guide. It includes the fol-
lowing topics:
l Administrator Introduction on page 1
l System Description on page 7
l Installing ProVision on page 29
l Upgrading ProVision on page 67
l Licensing ProVision on page 99
l Setting Up ProVision on page 107
l Access Control on page 119
l Migrating Topology on page 161
l Database and Server Management on page 179
l Redundant Server Deployments on page 203
l Generic Device Management on page 239
l Northbound Interface on page 279
l Help Desk Reports on page 335
l ProVision Web Server on page 341
You may need to have administration-level user ID and password to access these
functions. Please check with your supervisor or system administrator if you have any
questions about your user ID level.
Intended Audience
The information in this manual is designed for the following roles:
Role Brief Description

Network Security Man- Provides details on the ProVision user and device secur-
agers ity accounts, including adding, changing, and removing
user accounts and configuring device security accounts.
ProVision Admin- Provides details on maintaining the ProVision Server
istrators itself, including tasks such as database backing up,
restoring and purging, and stopping and starting the
ProVision service.
614-330053-001 4/04/2014 1
CHAPTER 1. ADMINISTRATOR INTRODUCTION
Additional Resources
The ProVision User Guide (PN 614-330055-001) describes the features and uses of
the ProVision network management system. It provides instructions about using
ProVision to create and maintain a graphical representation of your network.
This manual also describes how to start and exit user sessions, how to monitor and
manage device status, performance, and event reporting, how to configure Aviat Net-
works devices, and how to generate supporting reports and graphs.
2 AVIAT NETWORKS
About ProVision
ProVision is a network management tool developed by Aviat Networks. It provides
management solutions to the Aviat Networks SNMP and proprietary protocol
products running on your network.
ProVision builds on our expertise, experience, and user feedback to provide sig-
nificant advances in functionality and ease of use. ProVision delivers an advanced,
flexible, software solution for managing the devices running on your network.
The ProVision network management base can be used with many third party
products and proprietary operational support systems. It is easily extensible through
a variety of standards-based and proprietary management protocols.
614-330053-001 APRIL 2014 3

CHAPTER 1. ADMINISTRATOR INTRODUCTION
Administrator Documentation
Organization
The Installation and Administration Guide is organized into the following sections:
l Administrator Introduction on page 1 - Brief introduction to ProVision and its
features.
l System Description on page 7 - Architecture, platform hardware, software
requirements, deployment options, and an overview of network intelligence
and network management concepts.
l Installing ProVision on page 29 - Installation prerequisites and the procedures
required to install ProVision.
l Upgrading ProVision on page 67 - Procedures for upgrading from ProVision
2.3, or ProVision 3, to the current version of ProVision.
l Licensing ProVision on page 99 - Information on the licensing requirements
and procedures for ProVision.
l Setting Up ProVision - What is needed to get ProVision running and
monitoring the network.
l Access Control on page 119 - User accounts and security groups. Also explains
how to add users and set up device security accounts.
l Migrating Topology on page 161 - How to export the network topology and
how to import the topology .XML file.
l Database and Server Management on page 179 - Database management
functions including: backing up the database, checking the database integrity,
and resetting the database.
l Generic Device Management on page 239 - Managing Packages and entering
Event Trap Mapping for Generic Devices.
l Northbound Interface on page 279 - ProVision’s support of Northbound event
integration with higher-level management solutions.
l Help Desk Reports on page 335 - How to run and save Help Desk reports,
which save important ProVision details.
4 AVIAT NETWORKS
Conventions and Terminology

Graphic Cues
The following items have graphic cues to identify important supporting information.
A note i tem i denti fi es addi ti onal i nformati on about a pro-
cedure or functi on.
CAUTION:A caution item identifies important information pertaining
to actions that may cause damage to equipment, loss of data, or cor-
ruption of files.
WARNING: A war ni ng i tem i denti f i es a ser i ous phy si cal

danger or major possi bl e pr obl em.
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-330053-001 APRIL 2014 5

Chapter 2. System Description
This section describes ProVision’s architecture, deployment options, client/server soft-
ware relationship, and communications with network elements. It contains the fol-
lowing topics:
l ProVision Architecture on page 8
l ProVision Deployment Options on page 9
l Network Communication, Ports, and Firewalls on page 16
l Network Management Concepts on page 22
614-330053-001 4/04/2014 7
CHAPTER 2. SYSTEM DESCRIPTION
ProVision Architecture
ProVision provides a network management solution based on SNMP (Simple Net-
work Management Protocol), a widely accepted standard for performing network
management functions. It does this by layering one or more Element Manager applic-
ations on the foundation system.
ProVision's underlying network management platform is based on an open system
architecture. This enables Aviat Networks users to extend network manageability by
adding their own applications to the platform. The resulting application suite deliv-
ers a seamless software solution that unifies network element management across
the platform. Users can easily move from viewing an alarm on the network, to view-
ing a status screen for the alarmed object, to viewing a performance summary for the
same object.
Figure 2-1. ProVision Architecture Overview
8 AVIAT NETWORKS
ProVision Deployment Options

ProVision can be deployed with one ProVision client and one ProVision server, or
with multiple Clients connecting to one Server. (Up to 15 Clients can be operated
from one Server). The deployment options are based on your front-end user and net-
work requirements.
ProVision can be deployed in the following configurations:
l Single Server/Client Deployment on page 9
l LAN Client Deployment on page 10
l WAN Client Deployment on page 11
l Standby Server Deployment on page 12
Single Server/Client Deployment

The ProVision server installation process includes all of the files required to establish
a client session on the server workstation.
ProVision runs on a Windows workstation called the server. Every ProVision deploy-
ment must have a ProVision server installed.
The server installation includes:
l Server processes that track the current state of the network model, manage
user access to the system, monitor network events, and more.
l The MySQL database system used for storing and retrieving network element
data.
l A local client used for establishing a client-to-server session on the server.
This figure is an overview of the single server/client deployment. This is only recom-
mended for small installations.
Figure 2-2. Single Server/Client Deployment
614-330053-001 APRIL 2014 9

Next Topic:
LAN Client Deployment on page 10.
LAN Client Deployment

The ProVision client installation installs client software on the local machine, elim-
inating the need to mount files across the network. Network traffic occurs only when
the client requires data from the server.
Optional ProVision client workstations enable multiple concurrent user sessions.
A client installation contains only those parts of the ProVision system necessary to
allow users to run a ProVision session. The user session communicates back to the
server when required to retrieve management information. The GUI runs on the cli-
ent machine, freeing system resources on the server machine to process network
information.
A ProVision client is installed locally on the server. Clients can also be installed on
standalone PCs.
This figure shows an overview of the server with clients deployed.
Figure 2-3. Server with LAN Clients Deployed
10 AVIAT NETWORKS
WAN Client Deployment

The ProVision client can also be operated on a remote client machine. For this setup,
the remote client uses a low bandwidth connection with a high latency link. WAN
connections typically exhibit higher latency and lower bandwidth when compared
with LAN connections. As the ProVision client application is optimized for a LAN
connection, a WAN client solution needs to be deployed where a WAN connection is
used to connect remote users to the ProVision server.
To support WAN clients, a WAN client server is set up by connecting it to the ProVi-
sion server via a LAN connection. The ProVision client software is installed on the
WAN client server.
The WAN clients are set up by installing a Windows Terminal Server (WTS) or an
equivalent remote client solution such as Citrix Presentation Server.
More than one WAN client can access the WAN client server, however, since only one
version of the ProVision client is used, all ProVision logging from the multiple WAN
clients are logged onto a single file.
This figure is an overview of the server with both LAN clients and WAN clients
deployed.
614-330053-001 APRIL 2014 11

Figure 2-4. Server with LAN Clients and WAN Clients Deployed
Next Topic:
Standby Server Deployment on page 12
Standby Server Deployment

ProVision provides business-critical supervision of Aviat Networks equipment. A
standby server deployment protects equipment and system operation against emer-
gencies and outages.
A ProVision standby server solution provides the highest level of system protection
by providing two independent ProVision servers providing parallel supervision of
Aviat Networks equipment. Aviat Networks recommends implementing a standby
server deployment if you have strong low-risk requirements, if you have an SLA that
requires uninterrupted 24 -7 access and support, or if you are located in an area
prone to natural disasters, such as earthquakes or hurricanes.
When a standby server is installed, both ProVision servers are independent of each
other, and so are their associated ProVision clients. This would means that ProVi-
sion client #1 could log on to either ProVision server #1 or ProVision server #2, or
indeed both at the same time.
There are multiple standby server options, all described in this section:
l Standby Server with Server and Client Sharing Hardware
l Standby Server with Server and Client on Separate Hardware
l Standby Server with WAN and Separate Hardware
12 AVIAT NETWORKS
For information on installing and managing a standby server deployment, see

Redundant Server Deployments on page 203.
Standby Server Deployment: Sharing or Separate

Hardware
There are two standby server deployment options.
l Standby Server with Server and Client Sharing Hardware: This is
ideal for small networks where only one user is monitoring the network at any
time.
l Standby Server with Server and Client on Separate Hardware: This
is required for systems where more than one user is monitoring the network,
for the support of multiple clients. This option is also required if a server is
located off-site or in a secure computer room with limited access.
The configuration for each of these options is diagrammed below.
See also Server and Services Management Procedures on page 196.
Figure 2-5. Standby Server with Client and Server Sharing Hardware
614-330053-001 APRIL 2014 13

Figure 2-6. Standby Server with Server and Client on Separate Hardware
Standby Server with WAN and Separate Hardware

You can set up a standby server with a WAN and with separate hardware.
14 AVIAT NETWORKS
Figure 2-7. Servers with Standby Client Deployed via WAN Server
614-330053-001 APRIL 2014 15

Network Communication, Ports, and

Firewalls
This section covers the following topics:
l Device Support
l Communication Frequencies with Network Devices on page 16
l Network Communication Ports for Firewalls on page 18
Device Support
A basic Element Manager supporting SNMP devices provides simple presence polling
to an MIB object enabling communication with the devices.
l ProVision provides support for the following Aviat Networks and related
products:
l Eclipse radios: Eclipse Terminal (IDU), Eclipse Node (INU and INUe)
l TRuepoint radios: 5000, 4040, 4000, 6400, 6500
l EION StarMAX WiMAX
l MegaStar radios
l Constellation radios
l LE3000 and LE3200
l Altium: Altium, Altium MX and Altium MX 2+0
l XP4: XP4 248x, XP4 E3
l DXR SMA - DXR700
l ADR
l Velox
l TNET
l E-Link 1000EXR
Communication Frequencies with Network

Devices
This table describes how often ProVision polls the devices on the network, for pres-
ence polling, event polling and trap initiated polling.
16 AVIAT NETWORKS
Some devi ces have di fferent pol l i ng frequenci es for di fferent

areas, such as confi gurati on, l i nk di scovery, and pl ug-i n struc-
tures.
Table 2-1. ProVision - Network Device Communication Frequencies
Device Type Presence Event Traps Event Trap Initiated

Polling Polling Polling
Device Freq. Freq. Freq. Freq.
Accedian 2 min 2 min
ADR 2 min When an event occurs
Altium MX/ 2+0 2 min When an event occurs
Aurora 5 min When an event occurs
CAU 2 min When an even occurs
Cisco Plug-in: 60
mins
Config: 12
hours
Constellation 2 min When an event occurs
DART 5 min When an event occurs
DVA 2 min When an event occurs
DVM45 5 min When an event occurs
DVM-XT 5 min When an event occurs
DXR 100 2 min 2 min
DXR 200 2 min* 2 min
DXR 700/ SMA DXR 2 min 2 min
E-Band E-Link 2 min 2 min
Eclipse Node 2 min 2 min As configured
INU/INUe
Eclipse Terminal 2 min 2 min As configured
(IDU)
Memotec CX-U 2 min When an event occurs
E-Link 1000 EXR, LR 2 min When an event occurs
Generic 2 min When an event occurs
Juniper 2 min When an event occurs
LE3000, LE3200 2 min When an event occurs
MegaStar 2 min When an event occurs
MicroStar I, II, III 2 min When an event occurs
SAGEM 5 min When an event occurs
SPECTRUM 2 SNMP 2 min When an event occurs
SmartCore 2 min When an event occurs
Symmetricom 2 min 2 min
EION StarMAX Base 2 min When an event occurs
Station
614-330053-001 APRIL 2014 17

Device Type Presence Event Traps Event Trap Initiated

Polling Polling Polling
Tellabs Plug-in: 60
mins
Config: 12
hours
TNet Proxy 5 min*
TRuepoint 2 min When an event occurs
Velox 2 min When an event occurs
WL1000, RW2000 2 min When an event occurs
WSG ASN Controller 2 min When an event occurs
WTM 3100 Config: 12
hours
WTM 3200 Config: 12
hours
Links: 60
minutes
WTM 6000 Config: 12 60 minutes
hours
Plug-in: 12
hours
Integrity: 60
mins
XP4 248x / E3 5 min When an event occurs
* Requires a double failure before transition into loss coms, so has an effective pres-
ence poll of 10 minutes.
Next Topic:
Network Communication Ports for Firewalls on page 18
Network Communication Ports for Firewalls

ProVision uses network UDP/IP and TCP/IP communication ports to communicate
with Network Elements (NE), between Client and Server, and other services, where
required. Administrators may need to adjust these ports to communicate around fire-
walls.
This section includes the default port data, to be used as a reference.
FTP Transfer Firewall Configuration

Most modern firewall products are able to intelligently support FTP transfers, avoid-
ing the need to open a large number of TCP ports. If this firewall facility is available,
the ProVision FTP port must be changed to port 21 (see Changing FTP Server Port on
page 111).
18 AVIAT NETWORKS
Also note that the firewall must support Extended Passive Mode FTP (use of the
EPSV command) as defined in RFC 2428.
Recommended Port Configuration

The network communications are grouped by integration between five logical entit-
ies:
1. NE = Network element(s) (e.g. Eclipse INU)
2. Server = ProVision server system(s).
3. Client = ProVision client system(s); including all bundled applications (e.g.
craft tool. browser).
4. NBI = Northbound OSS system(s).
5. IT = IT infrastructure services.
I f any port 5555 needs to be changed, see C hanging FTP Serv er
Port on p age 111.
WARNING: If any por ts ar e changed on a Pr i mar y
Ser v er , y ou must al so change the por ts on the con-
nected Backup Ser v er to match them.
WARNING: Jav a Runti me f or Pr oVi si on chooses many of

the por ts Pr oVi si on wi l l use, based on av ai l abi l i ty . F or
some pr ocesses, and because of v ar i abi l i ty i n por t
sel ecti on, por ts shoul d not be bl ocked or f i r ewal l ed.
C onf i gur abl e por ts ar e noted i n the f ol l owi ng tabl es.
The ProVision client can be run on a remote PC inside a Citrix session (or Remote
Desktop client session). This allows you to implement a firewall between the remote
PC and the ProVision system. Only one port needs to be opened in the firewall. To
do this, the ProVision Client must be installed on a Citrix server (or Terminal ser-
vices server) that is connected to the ProVision server without using a firewall. If you
have further requirements, please contact Aviat Networks for support.
Table 2-2. To Network Elements
Application Protocol Port From Comments

SNMP UDP 161 Server Management requests
Telnet SSH TCP 23 (telnet) Server Management
22 (SSH)
Telnet SSH TCP 23 (telnet) Client Craft tool (CLI)
22 (SSH)
HTTP TCP 80 Server Backup (GET) or Upgrade
443 (HTTPS) (PUT/POST)
HTTP TCP 80 Client Craft tool (web)
443 (HTTPS)
614-330053-001 APRIL 2014 19


Portal TCP 26000 (restore) Client Craft tool (Eclipse Portal)
26003 (normal)
26007 (secure)
Portal UDP 26005 Client Craft tool (Eclipse Portal NE dis-
covery)
Portal Protocol UDP 26000 (restore) Server Management (Eclipse Only)
26003 (normal) Cli-
ent
26007 (secure)
RADIUS UDP 1812 * (auth) IT Authentication and accounting
1813 * (accnt) Ports are configurable
NTP UDP 123 IT Date/time auto-configuration
Table 2-3. To Server

SNMP UDP Any >1023 NE Management responses
SNMP UDP 162 NE Management notifications
SNMP UDP 162 NBI NBI control
FTP (passive) TCP 5555 (control) NE Upgrade
Any >1023 (data) Port is configurable
FTP (passive) TCP 5555 (control) NBI NBI file transfer
FTP (passive) TCP 5555 (control) Client Client file transfer
FTP (passive) TCP 5555 (control) Serve- Redundancy replication
Any >1023 (data) r Port is configurable
HTTP TCP 80 Client Client web requests
8080 8555
HTTP (SOAP) TCP 80 NBI MTOSI NBI operations
443 (HTTPS) Port is configurable
Java RMI TCP 5001 Client Client RMI requests
5558
Java RMI TCP 5001 Serve- Redundancy control
5558 r
RADIUS UDP 1812 * (auth) IT Authentication and accounting
1813 * (accnt) Port is configurable
NTP UDP 123 IT Date/time auto-configuration
SYSLOG UDP 514 NE Management notifications. Port is con-
figurable
TFTP UDP 69 NE Configuration Backup Files for CTR
8440.
Table 2-4. To Client
20 AVIAT NETWORKS

Java RMI TCP 5560 + Server Client RMI callbacks
One port for each simultaneous client
session on a single client system. E.g.
5560-5584 for 25 clients.
FTP (passive) TCP Any >1023 (con- NE Upgrade (via Eclipse Portal)
trol)
Any > 1023 (data)
Portal UDP 26005-26099 NE Craft tool (Eclipse Portal NE discovery)
Port 26007 needs to be opened
between Portal and Eclipse if using
RADIUS
Table 2-5. To NBI

SNMP UDP 162 Server NBI traps
Port is configurable
Proprietary TCP 8081 Server NBI output (ASCII stream-
ing)
Table 2-6. To IT

RADIUS UDP 1812 (auth) Server Authentication and
1813 (accnt) accounting
RADIUS UDP 1812 (auth) NE Authentication and
1813 (accnt) accounting
NTP UDP 123 Server Date/time auto-con-
figuration
NTP UDP 123 NE Date/time auto-con-
figuration
SMTP TCP 25 Server Email notifications
Table 2-7. To Redundancy Controller Server

SNMP UDP 1234 Server Redundancy Con-
troller.
MySQL TCP 3306 Server MySQL Replication
FTP TCP 5555 Server
HTTP TCP 9080 Server
614-330053-001 APRIL 2014 21

Network Management Concepts

This section contains the following topics:
l Network Management and SNMP on page 22
l Managers, Agents, and MIBs on page 22
l Internet and Enterprise Specific MIBs
l Managing Proprietary Protocol Devices on page 26
l SNMP Traps and Managed Devices on page 27
Network Management and SNMP

ProVision communicates directly with Aviat Networks SNMP devices. Aviat Net-
works non-SNMP devices that do not understand SNMP protocol require the services
of proxy software to enable communication with the manager.
All communication between the ProVision application and Aviat Networks devices is
based on SNMP (Simple Network Management Protocol). SNMP is the de facto stand-
ard for systems and device management on TCP/IP (Transmission Control Pro-
tocol/Internet Protocol) networks. Designed to facilitate the exchange of
management information between network devices, SNMP is rapidly replacing pro-
prietary protocols for telecommunications network management.
This section profiles basic SNMP components and operations, describes the role of
the proxy agent when proprietary protocol devices exist on the network, and intro-
duces Aviat Networks enterprise-specific MIB modules. It also takes a closer look at
how traps are handled in both SNMP-managed and proxied environments.
Managers, Agents, and MIBs

l Manager-Agent Model on page 23
l Manager and Agent Communication on page 23
l Information Exchange and the MIB on page 24
l MIB Organization on page 24
The SNMP management protocol is based on the manager-agent model, with an intel-
ligent management system monitoring and controlling multiple device-based agent
22 AVIAT NETWORKS
systems. Manager and agent systems communicate by setting values in a data struc-
ture called a MIB (Management Information Base), which resides on the agent
device. This figure provides a representation of the manager, agent and MIB inter-
actions.
Figure 2-8. Manager, Agent and MIB Interaction
Manager-Agent Model
SNMP treats a network as a collection of cooperative, communicating entities con-
sisting of management systems and agent systems (or managed devices).
A management system, or manager, is the host system running the network man-
agement application and supporting the Simple Network Management Protocol. A
manager can solicit and interpret data about agent systems and network traffic. It
can also trigger status and configuration changes on a managed device. A manager
performs these tasks by making requests to the agent running on the device.
An agent system is the software interface to a managed device, such as a microwave
radio. Like a manager, an agent may actually be one of many processes running on a
workstation. Or it might be implemented in the non-volatile memory of the device
itself. An agent is usually a passive entity. It responds to manager requests, and sup-
plies and changes the values of local variables as needed. An agent can also send
unsolicited messages (called traps) to alert the manager of changes on the managed
device.
Managers and agents communicate, or interact, through SNMP. For devices that use
protocols other than SNMP to communicate on a network, a proxy agent, which
speaks both languages, is used as an intermediary. When proprietary protocol Aviat
Networks devices exist on an SNMP-managed network, the Proxy application,
developed by Aviat Networks, provides translation and other services on behalf of
these devices. Proxy Agents monitor and control private protocol Aviat Networks
devices at a peer level with SNMP-protocol devices.
Manager and Agent Communication

Normally, a manager requests information from an agent. In addition, an agent can
send messages to the manager about the current status of a managed device or about
its own status. This table identifies the SNMP requests used to perform basic SNMP
operations.
614-330053-001 APRIL 2014 23

Table 2-8. SNMP Request Descriptions
SNMP Request Description

Set Write new data to one or more of the objects managed by
an agent.
Get Request the value of one or more of the objects managed
by an agent.
Get Next Request the object identifier(s) and value(s) of the next
object(s) managed by an agent.
Get Bulk Request large amounts of object information in a single
request/response transaction. Get Bulk behaves as if
many iterations of Get Next requests/responses were
issued, except that they are all performed in a single
request/response operation.
Response The data returned by an agent.
Trap Send an unsolicited notification from an agent to a man-
ager indicating that an event or error has occurred on the
agent system.
Information Exchange and the MIB

Within the SNMP framework, all information accessed or modified through the agent
is accessed or modified through the MIB. Each managed object includes one or more
MIBs that define the manageable information for that object.
A MIB is composed of a set of MIB objects. Each MIB object (also called a MIB vari-
able) represents a piece of information (configuration, status, control or other man-
agement-related information) about a managed network element, for example, a
system description or a performance value. The existence of a particular value for a
MIB object is called a MIB object instance. Some MIB objects have only a single
instance for a given managed device, for example, a system description. Other MIB
objects have multiple instances for the device; for example, the status of each inter-
face on the device. By reading information from an agent’s MIB, an SNMP manager
can monitor an agent. By writing or altering information on the MIB, an SNMP man-
ager can control the behavior of the managed device on which the agent resides.
MIB Organization
Internet-standard MIBs reflect a hierarchical organization of MIB objects arranged in
a tree-like structure. Each branch in the tree has a unique name and numeric iden-
tifier. Intermediate branches of the tree serve to group related MIB objects together.
The leaves of the tree represent the MIB objects, or actual device data. Branches, or
24 AVIAT NETWORKS
nodes, are similar to directories in a file system in that they do not contain data in
the normal sense. They contain other directories and files. Leaves are similar to a file
in that they contain data that relates to a particular aspect of a device on the net-
work.
MIB Naming Conventions

MIB objects are identified, or named, by their place in the overall tree structure. A
full object identifier (OID) consists of the identifier of each branch along the path
through the tree hierarchy, from the top of the tree down to the leaf. The OID is con-
ventionally expressed in dot notation format, with a period (.) separating each level
in the path from the top of the MIB hierarchy down to the specific MIB object. Each
branch and leaf have both a numeric name and an ASCII name, with the numeric
name frequently used for ease of reference. This figure shows two different ways of
naming the same MIB object.
Figure 2-9. MIB Object Identifier
MIB Instance IDs

A particular MIB object instance is distinguished from other instances by an
instance ID appended to the end of the MIB OID. For example, if an object has one
and only one instance, then the instance identifier is zero (0). The instance identifier
for a MIB object with more than one instance is 1 or greater.
MIB Object Attributes

Every MIB object also has certain attributes that describe it. In the case of leaf
objects, or MIB variables, these attributes define the type of information (such as
integer, text, or counter), its access (such as read-write or read-only), and its status
(such as mandatory or optional).
Internet and Enterprise-Specific MIBS

MIBs are organized into MIB modules. A MIB module is a file defining all the MIB
objects under a subtree. The foundation module is the standards-based MIB-II
614-330053-001 APRIL 2014 25

module defined by RFC 1213: Management Information Base of Network Man-

agement of TCP/IP Internets: MIB-II.
In addition to the Internet-standard MIB-II objects defined in RFC 1213, many hard-
ware vendors, including Aviat Networks, have developed MIB extensions for their
own products. The MIBs defined by these vendors are referred to as enterprise-spe-
cific MIBs.
Managing Proprietary Protocol Devices

In a proxied environment, Proxy Agents are responsible for translating manager
requests and for notifying the network manager when changes occur on a managed
device.
Private-protocol Aviat Networks devices use the proprietary TNet protocol for net-
work communication. TNet protocol and SNMP differ significantly in terms of data
structure, access method, and protocol packet content. The Proxy Agent mediates
these differences, performing information preparation and exchange functions on
behalf of TNet devices operating in an SNM
More About Protocol Mediation and the Proxy

Using the protocol semantics and polling algorithms, the Proxy Agent converts
SNMP requests from the manager to the proprietary protocols required by TNet
devices. The Proxy Agent constructs, parses, and analyzes each request and resultant
response according to the supported protocol specification, then relays all responses
back to the manager using SNMP.
The Proxy Agent polls managed TNet devices for alarm information and creates a set
of MIB objects for each device. The Proxy Agent also interprets the event data sent to
it by managed TNet devices, reformats this data as SNMP traps (notifications), and
forwards the traps on to the manager. The Proxy Agent does not run on the managed
TNet device itself, but acts as an intermediary between the network manager and the
device as shown below.
26 AVIAT NETWORKS
Figure 2-10. Proxy Agents' Role in Protocol Conversion
SNMP Traps and Managed Devices

Whenever a monitored change occurs in the status of a managed device, an SNMP
trap (also called an event) is generated by the SNMP agent running on the device.
Traps are designed to notify the manager that some monitored condition has
changed in the network enterprise. Traps can range from providing basic status
information to indicating critical system or device problems.
Agent software automatically logs device events to an event table maintained in the
agent MIB. The event table tracks the latest events logged for a managed device1.
Logged events are viewable online via both the Fault window Event Table tab2 and
via the Event Browser window.
l The Event Table tab displays agent-logged events for a selected Aviat Networks
device.
l The Event Browser displays events from many sources, including SNMP traps
generated by agent software, and internal events generated by ProVision. For
more information on the Event Browser refer to the ProVision User Guide,
Managing Events.
Net work Management and SNMP on p age 22
1The maximum number of recent events that are maintained in the event table log
varies by device type.
2An Event Table is not presented for DXR devices.
614-330053-001 APRIL 2014 27

Chapter 3. Installing ProVision
This section describes the installation requirements and the procedures for installing
ProVision.
Thi s secti on focuses on the requi rements and i nstructi ons for
a new, or “cl ean”, i nstal l ati on of ProVi si on. To upgrade an
exi sti ng i nstal l ati on, see Up grad ing ProVision on p age 6 7.
Here is an overview of the steps required to set up and install ProVision:
1. Perform Pre-Installation Tasks. Determine if the software and other equip-
ment were supplied by Aviat Networks.
l No - verify that the equipment and OS software supplied meets the
requirements. Check the amount of ethernet cards in the PCs where server
software will be installed: if they have more than one ethernet card apiece, see
RMI Interface for Installation on page 40.
l Yes - Unpack and check supplied equipment.
2. Set up the ProVision computers.

l Ensure that the installer has Administration rights for the computers
l License Microsoft OS SW
l Edit regional settings
l Change PC power saving setting
l Configure Tracker Box if required
l Locate standby servers if required
l Set up any ProVision Client users with Modify rights on the computer’s
ProVision directory
l For a Solaris installation, ensure that Java is installed.
3. Install ProVision software.
l Install ProVision Server software
l Install Portal software
l Install ProVision Client software
4. Install and configure any standby servers for ProVision.
5. Proceed to the setup of ProVision: licensing, system detail entry, and man-
aging.

l Installation Prerequisites on page 31
l Pre-Installation Tasks on page 42
l Installing and Uninstalling ProVision on page 46
614-330053-001 4/04/2014 29
CHAPTER 3. INSTALLING PROVISION
l Standby Server Installation and Maintenance on page 58

l RMI Interface for Installation on page 40
l Installing and Uninstalling the ProVision Redundancy Controller on page 60
30 AVIAT NETWORKS
Installation Prerequisites
This section includes the following information:
l Platform Requirements on page 31
l Device Counts: Server Loading Value on page 36
l ProVision Installation DVD Set on page 38
l Eclipse Installation CD on page 39
l Licensing, Database, Node and MTOSI NBI Support on page 39
l Administrator Username and Password on page 40Administrator Username
and Password on page 40
l Server IP Address on page 40
l RMI Interface for Installation on page 40
Platform Requirements
This section details the software and hardware specifications required to run ProVi-
sion.
Table 3-1. ProVision Operation System Software Requirements
Operating Sys- ProVision ProVision Redundancy ProVision

tem server Client Controller Mobile Client
Windows XP Yes Yes Yes N/A
Pro
Windows 2003 Yes Yes Yes N/A
Server
Server
Windows Yes Yes Yes N/A
2008R2
Solaris 10 Yes Not sup- Yes N/A
(update 9 or ported
later required
for ProVision
6.11.2
onwards,
requires Java
1.7.0_40 to be
installed)
614-330053-001 APRIL 2014 31

Operating Sys- ProVision ProVision Redundancy ProVision

tem server Client Controller Mobile Client
Apple iOS N/A N/A N/A YES, iOS 7
Android N/A N/A N/A YES, Android 4.0
(Ice
Cream Sandwic-
h) and 4.x (Jelly
Bean)
F or Wi ndows servers runni ng 1,000 nodes or more, a 64 bi t

server software OS i s requi red.
F or an Oracl e MySQL database, ProVi si on requi res versi on
5.1.69.
F or Java, ProVi si on requi res versi on 1.7.0_40.
Virtual Machine Requirements

See the topic Virtual Machine Installation Requirements on page 35 for these
detailed requirements.
Server and LAN Client Specifications

This table lists the Windows server and LAN hardware requirements. The hardware
specification is dependent upon the Node Loading Value. The Node Loading Value is
based on the number and type of radios that make up your network. See the ProVi-
sion Release Notes, and Device Counts: Server Loading Value on page 36 for more
information.
CAUTION:For Solaris installations, ProVision server must be installed
on a dedicated server, used only for ProVision.
Table 3-2. Minimum Server and LAN Hardware Specifications
Node Load- Minimum Windows Minimum Solaris Minimum Client Spe-

ing Value Server Specification Server Specification cification
Up to 100 - 2 GHz processor - - 2 GHz processor
- 4 GB RAM - 4 GB RAM 64-bit OS, 2 GB
- 50 GB HD space to RAM 32-bit OS
install and operate - 10 GB HD space to install
- Ethernet LAN card and operate
- Supports up to 10 - Ethernet LAN card
Mobile Client sessions - 10 Mbps LAN connection
per Client connected to the
Server
- 32-bit color
- Minimum display resolution
1024 x 768
32 AVIAT NETWORKS
Node Load- Minimum Windows Minimum Solaris Minimum Client Spe-

ing Value Server Specification Server Specification cification
Up to 1,000 - 1 x 2-core processor - - 2 GHz processor
- 100 GB HD space to RAM 32-bit OS
install and operate - 10 GB HD space to install
- Ethernet LAN card and operate
- Supports up to 25 - Ethernet LAN card
Mobile Client sessions - 10 Mbps LAN connection
per Client connected to the
Server
- 32-bit color
1024 x 768
Up to 3,000 - 1 x 4-core processor - 4-core SPARC pro- - 1 x 2-core processor
- 8 GB RAM cessor - 4 GB RAM 64-bit OS, 2 GB
- 100 GB HD space to - 8 GB RAM RAM 32-bit OS
install and operate - 300 GB HD space to - 10 GB HD space to install
- Ethernet LAN card install and operate and operate
- 64 bit OS (including swap - Ethernet LAN card
- 64-bit PV server option space) - 10 Mbps LAN connection
- Supports up to 100 - Ethernet LAN card per Client connected to the
Mobile Client sessions - Supports up to 100 Server
Mobile Client sessions - 32-bit color
1024 x 768
Up to 9,000 - 2 x 4-core processors - 8-core SPARC pro- - 1 x 2-core processor
- 16 GB RAM cessor - 4 GB RAM 64-bit OS, 2 GB
- 300 GB HD space to - 16 GB RAM RAM 32-bit OS
install and operate - 300 GB HD space to - 10 GB HD space to install
- Ethernet LAN card install and operate and operate
- 64 bit OS (including swap - Ethernet LAN card
- 64-bit PV Server option space) - 10 Mbps LAN connection
- Supports up to 100 - Ethernet LAN per Client connected to the
Mobile Client sessions - Supports up to 100 Server
Mobile Client sessions - 32-bit color
card - Minimum display resolution
1024 x 768
When addi ti onal features are added to the ProVi si on product,

the RAM requi rements may i ncrease for the node counts spe-
ci fi ed above.
Executi ng a ProVi si on cl i ent sessi on on the server reduces the
stabi l i ty of the server. I t i s recommended that cl i ent sessi ons
are not executed on l arge server depl oyments.
WAN Client Server and WAN Client Specifications

Where access to ProVision client functionality is required over a WAN (Wide Area
Network) connection to the ProVision Server, a ProVision WAN (or thin) Client
614-330053-001 APRIL 2014 33

solution needs to be deployed. Client session counts refer to the number of sim-
ultaneous client sessions to be executed on a single WAN Client Server machine.
Table 3-3. Minimum WAN Client Server and WAN Client Hardware Requirements
Node Load- Minimum Windows WAN Client

ing Value Server Specification
Up to 9,000 • Base RAM requirements for Windows
and Citrix
• Add 1GB per ProVision Client session
Up to 5 clients:
• 2-core processor
Up to 10 clients:
• 4-core processor
Up to 25 clients:
• 2 x 4-core processors
Ei ther Wi ndows 2003 Termi nal Servi ces or Ci tri x Presentati on

Server can be used to provi de a WAN Cl i ent Server sol uti on.
The WAN Cl i ent Server sol uti on must be operated on a stand-
al one machi ne. I t cannot be operated on the same machi ne as
the ProVi si on server.
FarScan Virtual Machine Requirements

In installations where FarScan is required it is recommended that FarScan is
installed on separate hardware the from ProVision server. FarScan can be run in a vir-
tual machine installed on the same hardware as the ProVision server.
The hardware requirements for a server to support a ProVision server and FarScan vir-
tual machine installation should exceed the hardware requirements of the individual
ProVision, virtual machine and FarScan components.
The FarScan hardware requirements are defined in the FarScan for Windows Instruc-
tion Manual. At least two real serial communication ports will also be required for
each FarScan installation.
Aviat has tested operating a ProVision server and four FarScan installations running
in separate VMware environments on the same hardware.
Next Topic:
Device Counts: Server Loading Value on page 36
34 AVIAT NETWORKS
Virtual Machine Installation

Requirements
This paper provides a brief overview of the Virtual Machine installation requirements
for Aviat Networks' ProVision software. For full details about installing ProVision,
see the ProVision Installation and Administration Manual, or ask your Aviat Net-
works sales representative.
Resource Requirements
The ProVision server and client can be installed on a virtual machine, also known as
a virtualized or "cloud" server.
The virtual machine resources created for the ProVision must meet the minimum spe-
cifications as listed below.
Virtual machine resources should be monitored and adjusted if required.
Table 3-4. Virtual Machines Supported
Operating Virtual ProVision

Installation Reference
System Machine Support
Windows VMware http://www.vmware.com/support/pubs Client or server
Solaris 10 Containers/ https://www.sun.com/offers/details/solaris_ Server only
Zones containers.xml
Table 3-5. Minimum Virtual Machine Server and LAN Hardware Specifications
Node Load- Minimum Virtual Win- Minimum Virtual Minimum Virtual Client
ing Value dows Server Solaris Server
Required - Ethernet LAN Card - Ethernet LAN Card - Ethernet LAN Card
For All - DISK I/O: 10-20ms - DISK I/O: 10-20ms - 10 Mbps LAN connection
access time access time per Client connected to the
- NETWORK I/O: 10Mbps - NETWORK I/O: Server
for small networks 10Mbps for small net- - 10 GB HD space
<1000 devices and works <1000 devices - DISK I/O: 10-20ms access
20Mbps for networks and 20Mbps for net- time
>1000 devices. works >1000 devices. - NETWORK I/O: 0.25Mbps or
better
Up to 100 - 2 GHz processor - - 2 GHz processor
- 50 GB HD space RAM 32-bit OS
Up to 1,000 - 1 x 2-core processor - - 2 GHz processor
- 100 GB HD space RAM 32-bit OS
614-330053-001 APRIL 2014 35

Node Load- Minimum Virtual Win- Minimum Virtual Minimum Virtual Client
ing Value dows Server Solaris Server
Up to 3,000 - 1 x 4-core processor - 4 zones - 1 x 2-core processor
- 8 GB RAM - 4 GB RAM - 4 GB RAM 64-bit OS, 2 GB
- 100 GB HD space - 300 GB HD space to RAM 32-bit OS
install and operate
(including swap
space)
Up to 9,000 - 2 x 4-core processors - 8 zones - 1 x 2-core processor
- 16 GB RAM - 4 GB RAM - 4 GB RAM 64-bit OS, 2 GB
- 300 GB HD space - 300 GB HD (including RAM 32-bit OS
swap space)
- Ethernet LAN card
When addi ti onal features are added to the ProVi si on product,

the RAM requi rements may i ncrease for the node counts spe-
ci fi ed above.
Redundancy and Standby Servers with Virtual Machine Installations

Redundant and standby servers for ProVision can be installed on virtual hosts. For
these installations, administrators must ensure that:
l Redundant or standby servers are installed on different virtual machines/hosts
than the primary installation.
l Redundant or standby servers match the mimimum virtual machine
requirements.
l If both redundant and standby servers are used, these must also be installed
on different virtual machines/hosts.
For more information, see Redundant Server Deployments in the ProVision Install-
ation and Administration Manual.
Device Counts: Server Loading Value

When planning a network, it is important to know the number of devices your net-
work will ultimately have. Some devices place more loading on the server than oth-
ers. Calculating a server loading value is a requirement to determine system
resources. Calculate the server loading value from the equation:
Node Loading Value = 3A + 2B + C
Where the letter designation A, B, and C are determined by the type of devices in
your network and are listed in the table below:
Device Letter Designation

Accedian EtherNID, EtherNODE C
Altium C
Aurora C
36 AVIAT NETWORKS

CAU C
Cisco C
Constellation B
Control Alarm Unit C
CTR 8540 A
CTR 8440
DART C
DVA C
DVM C
DXR 200, DXR 100/NMI C
DXR SMA / DXR 700 B
Eclipse IDU B
Eclipse INU, INUe (1), NTU, IRU600 A
E-Band E-Link 1000EXR, 1000LR, 1000Q C
EION StarMAX 6100 B
EION StarMAX 6400 B for each blade (can have
between 1 and 4 blades)
ASN-C A + B (5 for each)
EION StarMAX Base Station PMP/Sector C for each PMP/sector
Generic Devices C
Juniper A+B
LE3000 C
LE3200 C
MegaStar 1+1 SPU B
MegaStar M:N SPU B
MegaStar M:N SPU B
Memotec CX-U C
Microstar (I, II, III) C
Radwin WinLink 1000 C
Radwin 2000 C
Sagem ADR 155C A
Sagem ADR 2500 A
SAGEM-LINK C
- Spectrum II SNMP -C
Symmetricom C
Tellabs 8605 B
Tellabs 8609 A + B (5 for each)
614-330053-001 APRIL 2014 37


TNet C
TRuepoint (4000, 4040, 500) C
TRuepoint 6400 2
TRuepoint 6500 MSTU 1/2 of a C
Velox C
WiChorus ASN-GW C
WiMAX Subscriber Station C
WTM 3100 C
WTM 3200 C
WTM 3300 C
WTM 6000 C
XP4 / XP4 NMI C
For example, for a network with the following devices:

l 100 Eclipse INUs (A)
l 50 Eclipse IDUs (B)
l 200 XP4s (C)
l 10 Altiums (C)
The node loading value is:
= (3 x A) + (2 x B) + (C)
= (3 x 100) + (2 x 50) + (210)
= 610
The Megastar val ue i s per SPU. Where a MegaStar radi o con-
si sts of mul ti pl e SPUs, thi s wi l l produce a hi gher l andi ng
val ue.
ProVision Installation DVD Set

The ProVision installation DVD is one DVD. This installation DVD contains:
l Server and Client Setup applications
l Topology and migration tool files
l Readme file which details important information noted after the Release Notes
were closed off.
l ProVision MIBs
l Redundancy Controller software
l Alarm List for devices
l Time Zone Updater tool
l License Request Form
l Deletion of License form
38 AVIAT NETWORKS
l Java software
l User Documentation:
l Quick Start Guide
l Installation and Administration Guide
l User Guide
l Release Notes
l Tech Notes and White Papers
Eclipse Installation CD
If there are Eclipse radios on the network, you must install the Eclipse craft tool,
Portal, on the ProVision server. Portal enables you to log into the Eclipse radios. The
Portal software is contained on the Eclipse Installation CD 857-000004-001.
See the ProVision release notes for the compatible versions of Portal and ProVision
software.
Licensing, Database, Node and MTOSI NBI Support

Licensing Requirements
ProVision does not run without a valid product license. It requires either a tem-
porary evaluation license or a permanent license.
Using a Trial Evaluation License

A trial evaluation license can be requested from PV-Licensing@aviatnet.com, or by
completing the License_Request_Form.txt in the ProVision release media (see the
Documentation directory). When the evaluation period is complete, to continue to
use the software, you have to obtain and install a permanent license or request
another evaluation license.
A ProVision evaluation license is valid for a specified number of days. When the
expiry date is reached, the license key is no longer valid, all ProVision client sessions
are stopped. The ProVision server, however, remains running. The client sessions can
be started only when a valid license file has been copied into the ProVision server dir-
ectory.
Using a Permanent License

A permanent license has no expiry date and is the standard product licensing
medium. For instructions about requesting a permanent license, refer to Licensing
614-330053-001 APRIL 2014 39

ProVision on page 99.
Database Support
ProVision supports the MySQL database, version 5.1.69 .
Nodes Supported
Where support for a node loading value greater than 6,000 nodes is required, please
contact Aviat Networks for additional information.
MTOSI NBI
The MTOSI NBI must be upgraded separately, and there are steps to take before and
after the ProVision server upgrade. For more information see the Installation and
Upgrade section of MTOSI NBI and ProVision on page 349
Administrator Username and Password

The default ProVision administrator username and password is set as:
l username: admin
l password: admin
The admin password must be changed for security purposes. For more information,
refer to Workflow for Setting Up ProVision on page 109.
Server IP Address
The ProVision server IP address is required when applying for a ProVision license,
and uploading the client.exe from the ProVision server to the client PC. To determine
the Server IP address, refer to Determining the Server’s IP Address on page 103.
The Server I P address suppl i ed must be “stati c”, because the
ProVi si on l i cense i s based on the I P address and the I P
address i s veri fi ed each ti me the server starts up.
RMI Interface for Installation
40 AVIAT NETWORKS
If you are installing the ProVision Server on a PC with more than one Ethernet card,
additional configuration is required to ensure the correct operation of the ProVision
clients.
Thi s process i s not requi red when the server onl y has one Eth-
ernet i nterface.
You must configure the server PC to bind the ProVision Client services onto the net-
work that interfaces with the internal LAN; Client connections are made from this
network. To do this, use the following procedure.
Instructions
1. Ensure that you have administration privileges in the PC's operating
system.
2. Obtain the required network interface IP address for your ProVision Client
interface.
3. Log into the ProVision server PC. Stop the ProVision server (seeProVision
Commands on page 44).
4. Open your Server Configuration file.
l On a Solaris system the file is located at:
ProVisionserver/tomcat/webapps/ROOT/pv/templates/server_
configuration.xml
l On a Windows system the file is located at:
ProVisionServer\tomcat\webapps\ROOT\pv\templates\server_
configuration.xml
5. Using a text editor, edit the server_configuration.xml file. If the ProVision
Client interface is on, for exampl,e network interface 192.168.1.2 then add
this line immediately after the line <server_configuration>:
l <client_interface>192.168.1.2</client_interface>
6. Save the file.
7. Restart the server.
614-330053-001 APRIL 2014 41

Pre-Installation Tasks
Before a new installation of ProVision, the following tasks must be done:
l Setting Up Computer Equipment and User Rights on page 42
l Disabling the PC Power Saving Setting on page 43
l Installing Java for a Solaris Server on page 43
It is also useful to review the ProVision Commands on page 44.
Setting Up Computer Equipment and User Rights

Do the following to set up the computer equipment:
1. Unpack the equipment and verify the computer and accessories received
match the equipment ordered, by checking off the packing slip.
2. If there are any discrepancies between the equipment ordered and the
equipment supplied, or if the equipment is damaged, contact the Aviat
Networks Help Desk.
3. Connect accessories and turn computer on.
Setting Up User Rights on the Computers

To install ProVision Server and ProVision Client, ensure you have administrator
rights for the PC on which you are installing the ProVision software. If you do not
have the correct rights, the software does not install correctly.
Also, all users who will be logging into the Client need to have Modify rights for the
directory \ProVisionClient\ on the PC where the ProVision Client is installed.
To maintain this easily, Aviat Networks recommends creating a Windows user group
that has these rights. Consult the documentation for your version of Windows for
more detailed instructions.
Disabling Other SNMP Trap Services

For ProVision to operate correctly, no other SNMP trap services can be running on
the system. These must be stopped and disabled before starting ProVision.
Otherwise, ProVision will not receive alarm traps from devices.
As an example, Microsoft SNMP Trap Services must be stopped and disabled.
42 AVIAT NETWORKS
Exclude Scanning MySQL Temporary Directory

For some ProVision server installations it may be necessary to configure the antivirus
application to exclude scanning MySQL temporary directory to ensure the correct
operation of the ProVision server.
Exclude the ProVisionServer\mysql\data\tmp directory from being scanned
by any antivirus applications.
Disabling the PC Power Saving Setting

On /windows servers for ProVision, any Power saving setting that switches the server
to Standby needs to be disabled.
This procedure must be performed for all server and client Windows-based com-
puters using ProVision. To disable power saving mode:
1. Select Start > Settings > Control Panel > Power Options. The Power Options
Properties window is displayed.
2. Change the System standby to Never.
3. To save your changes, select OK.
Installing Java for a Solaris Server

To install ProVision on a Solaris 10 server, Java 1.7.0_40 must be installed on the
server. Use the Java installer provided on the ProVision installation DVD and the
instructions below.
To check whi ch j ava versi on i s i nstal l ed run j ava -versi on
from a command l i ne.
Prerequisites
l The ProVision server must have Solaris 10u9 (64-bit version) or later installed
and be a Sun Sparc workstation/server of the correct specification (see the
Customer Release Notes for these details).
l The installation partition must have at least 50 GB free disk space.
l Administration user must be logged in as root.
Procedure
1. Review the Prerequisites and ensure they are all in place.
2. Insert the ProVision Installation DVD into the server machine.
3. Log into the server machine as superuser/root.
614-330053-001 APRIL 2014 43

4. Copy files jre-7u40-solaris-sparc.gz and jre-7u40-solaris-spar-

cv9.gz from the PV install DVD to the directory where you would like to install
Java 1.7. Then run the commands:
gzip –dc jre-7u40-solaris-sparc.gz | tar xf –
gzip –dc jre-7u40-solaris-sparcv9.gz | tar xf –
5. If the new jre1.7.0_40 is not where you want java to reside, you can move it to an
appropriate location.
mv jre1.7.0_40 <your location for java>
6. Remove the old symbolic link.
rm /usr/java
7. Create new symbolic link. Run the command:
ln -s <directory where Java was installed to>/jre1.7.0_40
/usr/java
8. Check that java version "Java 1.7.0_40 " is correct and that 64bit extensions have
been installed. Run the command:
java -d64 -version
9. If the version is correct, this returns:
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)
10. Java is now installed.
ProVision Commands
The tables below define the Windows and Solaris commands accessible via the ProVi-
sion server command window. These commands are useful as you perform the install-
ation, data checks, backups, and data restoration.
F or Wi ndows 7, 2008R2 and 8, run these commands as an
Admi ni strator. To do thi s, open the Commands screen by
ri ght-cl i cki ng the Command Prompt i tem and sel ecti ng Ru n as
Adm in strator .
Table 3-6. ProVision Windows Commands
Windows Command Solaris Command Description

pv service start ./pv_service start Starts the ProVision service
pv service stop ./pv_service stop Stops the ProVision service
pv service ./pv_service_install Installs ProVision as an operating sys-
install tem service
pv service ./pv_service_remove Removes ProVision as an operating sys-
remove tem service
44 AVIAT NETWORKS

not applicable ./pv_service status Shows the ProVision server status
for Windows
pv db restore ./pv_db_restore Restores a database backup, launches
interactive tool
pv db restore ./pv_db_configure Launches window for changing MySQL
database user name, password, and
port
pv db check ./pv_db_check Runs an integrity check on the data-
base (key tables only)
pv db check all ./pv_db_check all Runs an integrity check on the data-
base (all tables)
pv version ./pv_version Shows the ProVision version of the
database
pv db reset ./pv_db_reset Destroys all database contents
pv import <dir- ./pv_db_import <dir- Imports the database
ectory> ectory>
migrate <dir- ./pv_db_migrate <dir- Migrates the database
ectory> ectory>
pv report ./pv_report Generates the ProVision helpdesk
report
pv help not applicable for Shows command line help
Solaris
I f, after enteri ng a command, a wi ndow appears wi th the mes-

sage “Do you want to al l ow the fol l owi ng program to make
changes to thi s computer?” cl i ck Yes .
614-330053-001 APRIL 2014 45

Installing and Uninstalling ProVision

For a new installation of ProVision, do the installation steps in the following order:
ProVision server Computer

l Installing the ProVision Windows Server on page 46
l Install ProVision Server Software - Solaris on page 50
l Installing the ProVision Client on page 52
l See "Installing the Portal Application"
ProVision Client Computer(s)

l Installing the ProVision Client on page 52
l See "Installing the Portal Application"
To uninstall ProVision, see these instructions:
Uninstalling ProVision
l Uninstall ProVision Server Software on page 55
l Uninstall ProVision Server Software - Solaris on page 56
l Uninstall ProVision Client Software on page 57
Installing the ProVision Windows Server

It is simple to install the ProVision Server on a Windows machine from the ProVi-
sion DVD.
See Install ProVision Server Software - Solaris on page 50 to install ProVision server
software on a Solaris machine.
Either obtain a full license or a trial evaluation license. A trial evaluation license can
be requested from PV-Licensing@aviatnet.com, or by completing the License_
Request_Form.txt in the ProVision release media (see the Documentation directory).
When the evaluation period is complete, to continue to use the software, you have to
obtain and install a permanent license or request another evaluation license.
46 AVIAT NETWORKS
Procedure
1. Before you begin, obtain and verify your root database user name, password, and
port number, and obtain a ProVision license.
1. Insert the ProVision Windows Installation DVD.
2. Via Windows Explorer, access the DVD directory.
3. Double-click the server_setup.exe file.
I f you are i nstal l i ng on Wi ndows 2008 SP 2, ri ght cl i ck on the
ser v er _setup.exe fi l e and sel ect Ru n as an Adm in istrator
from the pop-up menu.
4. First, the installer is verified.
5. The License Agreement window displays.
6. Read the license details. To accept the license, select I Agree.

7. Select the installation language.
8. Follow the installation instructions, accept all defaults, and install the server soft-
ware in the default location.
614-330053-001 APRIL 2014 47

9. The server installation and set up is completed. Click Finish .
10. Once the server installation is completed the ProVision server starts auto-
matically and runs in the background.
11. To verify that the ProVision server is running:
Select Start > Programs > ProVision server > C:\ command window.
At the prompt, type pv service start
A message is displayed indicating the server is already running.
If the server is not running, the pv service start command starts the server. If
a window appears with the message “Do you want to allow the following program to
make changes to this computer?” click Yes.
48 AVIAT NETWORKS
Windows 7 and Windows 8 Installation Step

For Windows 7 and Windows 8 installations, you need to manually enable pv com-
mands. To do this:
1. Close ProVision.
2. On the server where ProVision is installed, open Windows Explorer and
navigate to the ProVisionserver directory.
3. In the directory, right-click on wrapper.exe and select Properties.
4. In the Properties screen, click Compatibility and select the Run This
Program As An Administrator check item.
5. Click Apply, then OK.
6. The Properties screen closes.
7. You have now fully enabled pv commands for this installation.
Windows 2008 Server Installation Step

Complete the standard server installation process, then make changes in Windows
2008 as follows:
1. Go to the Control Panel > Administrative Tools > Services dialog.
2. Locate the ProVision service.
3. Right click on the ProVision service and select Properties.

4. On the Log on tab, change the log on account from the default to any user with
administrator privileges, e.g. Administrator.
614-330053-001 APRIL 2014 49

5. Stop the ProVision service, as described above, with the command pv service
start
6. Restart the ProVision service, as described above, with the command pv ser-
vice start
Next Topic:
Installing the ProVision Client on page 52
Install ProVision Server Software - Solaris

It is simple to install the ProVision Server on a Solaris machine from the ProVision
DVD. However, it is vital that all the prerequisites are in place. as listed below.
See Installing the ProVision Windows Server on page 46 to install ProVision server
software on a Windows machine.
See also ProVision Commands on page 44 to view Solaris commands for ProVision.
Prerequisites
l For Solaris installations, ProVision server must be installed on a dedicated
server, used only for ProVision.
l The ProVision server must have Solaris Sparc 10u9 or later installed and be a
Sun workstation/server of the correct specification (see the Customer Release
Notes for these details).
l The installation partition must have at least 50GB free disk space.
l Swap space size should be at least twice the physical memory size.
l For Solaris 10, Java 1.7.0_40 must be installed.To check which java version is
installed run java -version from a command line.
l Either obtain a full license or a trial evaluation license. A trial evaluation
license can be requested from PV-Licensing@aviatnet.com, or by completing
50 AVIAT NETWORKS
the License_Request_Form.txt in the ProVision release media (see the

Documentation directory). When the evaluation period is complete, to
continue to use the software, you have to obtain and install a permanent
license or request another evaluation license.
Procedure
1. Review the Prerequisites and ensure they are all in place.
2. Log into ProVision as superuser/root.
3. Insert the ProVision Installation DVD.
4. From the DVD, copy the file install.jar to the directory where you would like
to install the server.
5. From the Command window, run the following command:
chmod 777 install.jar
6. From the Command window, run the install file:
java -Dfile.encoding=UTF-8 -jar install.jar
7. The ProVision Solaris Installation wizard opens. The License Agreement window
displays.
8. Read the license details. To accept the license, select I Accept the terms of this
license agreement, and click Next.
614-330053-001 APRIL 2014 51

10. Follow the installation instructions, accept all defaults, and install the server soft-
11. Close the wizard when installation has completed.
12. ProVision server will be automatically started when the installation is completed.
CAUTION:If you are using a Windows 2008 or Windows 7 server,
after step 12 or 13 select the Run as Administrator option. See the
Windows 2008 instructions in Installing the ProVision Windows
Server on page 46.
13. You need to do one of the following:

l Add the Sun server hostname and reverse lookup (of ip address to hostname)
to the DNS server OR
l Add the ProVision server hostname and ip address into the host file of every
ProVision client (required for good performance when using a Sun server).
WARNING: If y ou ar e usi ng both Sol ar i s and the Pr oVi -
si on Redundancy C ontr ol l er , Pr oVi si on ser v i ce com-
mands (such as pv ser v i ce stop and ./pv _ser v i ce stop)
M UST NOT be used i f the Pr oVi si on Redundancy C on-
tr ol l er i s i nstal l ed and contr ol l i ng Pr oVi si onser v i ces.
If y ou need to use ser v i ce commands, the Redundancy
C ontr ol l er must be uni nstal l ed and M y sql r epl i cati on
must be tur ned of f .
Installing the ProVision Client

The client software must be installed on the server and on each of the client PCs.
There are two ways the client software can be retrieved/installed onto a ProVision cli-
ent PC.
l Via the ProVision installation DVD from the server or client PC. This is the
method described in Client Software Installation Via DVD on page 53.
l Via browser access the client PC installs the ProVision client software from the
server. This option is used, for example, if the client PC does not have a DVD
drive. For more information, refer to Client Software Installation From the
Server on page 54.
52 AVIAT NETWORKS
Prerequisites
l The ProVision server software is installed on the server computer.
l The client and server computers are on the LAN.
F or a Sol ari s i nstal l ati on, the cl i ent software must al ways be
i nstal l ed on a standal one PC.
Client Software Installation Via DVD

Procedure
1. Insert the ProVision installation DVD in the PC.
2. Select client_setup.exe.
I f you are i nstal l i ng on Wi ndows 2008 SP 2, ri ght cl i ck on the
clien t_ setup.exe fi l e and sel ect Ru n as an Adm in istrator
from the pop-up menu.
3. Select Open . For this first time installation, the License Agreement window dis-
plays.

6. Follow the installation instructions, accept all defaults, and install the client soft-
614-330053-001 APRIL 2014 53

7. When the installation is completed, select Finish.
8. Remove the ProVision installation DVD.

Cl i ent software can be uni nstal l ed. F or more i nformati on
refer to Uninst all ProVision C lient Soft ware on p age 57
Client Software Installation From the Server

You can install a client from the Server if you do not have a DVD drive or do not
have the ProVision DVD. You need to know the server’s IP address to access the
ProVision client software. If you are unsure of the IP address refer to Determining the
Server’s IP Address on page 103.
Prerequisites
The ProVision client software must be installed on the server before running this
installation.
Also, note that 8080 is the default port for the http service.
54 AVIAT NETWORKS
Procedure
To install the ProVision client software from the server computer:
1. On the client computer open a web browser window.
2. In the Address text entry box, type http://<server IP address>:8080
The ProVision online interface displays.
3. Click Download to download the ProVision Client Setup package.

5. When the installation has completed, select Close.
Uninstall ProVision Server Software

Prerequisites
Before you upgrade ProVision to a new version, you must uninstall the ProVision
server software. (See Uninstall ProVision Server Software - Solaris on page 56 to unin-
stall ProVision server software from a Solaris machine.)
You also need to backup the database and export the topology. For more inform-
ation, refer to Migrating Topology on page 161.
Procedure
1. Close all ProVision client sessions.
2. Select Start > Programs > ProVision server > Uninstall ProVision . The Unin-
stall Server Confirmation window is displayed.
3. Select Uninstall.
4. When the process is complete, select Finish.
614-330053-001 APRIL 2014 55

Uninstall ProVision Server Software - Solaris

Prerequisites
You must uninstall the ProVision server software before upgrading ProVision to a
newer version.
You also need to backup the database and export the topology. For more inform-
ation, refer to Migrating Topology on page 161.
WARNING: Thi s method i s f or use wi th Pr oVi si on 6.6
and l ater . If y ou ar e wor ki ng wi th a Pr oVi si on v er si on
that i s 6.5.4 or ear l i er , y ou must use the Sol ar i s uni n-
stal l ati on method i n the documentati on f or that spe-
ci f i c v er si on.
Procedure
To uninstall the ProVision server software from a Solaris machine:
1. Copy any back-ups made from ProVisionserver/mysql/backup directory to a
safe place. These back-ups must be copied back to the same directory if a restore is
required.
2. Copy any provision_license.xml file from the ProVision server dir-
ectory to a safe place.
3. Copy any NBI ascii files (if required) from the ProVisionserver/NBI directory
to a safe place. These files must be copied back to the same directory (if required)
after installing a newer version of ProVision.
4. Login as superuser/root.
5. Launch the uninstaller :
java -jar ProVisionserver/Uninstaller/uninstaller.jar
56 AVIAT NETWORKS
6. The uninstaller runs:
7. Click the checkbox for Force deletion of ... and click Uninstall.
8. Reboot the Sun server: reboot
Uninstall ProVision Client Software

When you are upgrading to a new version of ProVision software or upgrading to a
new computer, you need to uninstall the ProVision client software.
Procedure
1. Ensure there is no ProVision client session running on this machine.
2. Select Start > Programs > ProVision Client > Uninstall ProVision . The ProVi-
sion Client Uninstall window is displayed.
4. When the process is complete, select Finish .
614-330053-001 APRIL 2014 57

Standby Server Installation and

Maintenance
When deploying a ProVision standby server solution, the following items must be
taken into consideration:
l Server location
l Northbound interfaces (NBI)
l Data integrity
l Switch over between ProVision servers
l User security
This section describes the options and requirements for these aspects of installation
and use where standby servers are installed.
See also Installing and Uninstalling the ProVision Redundancy Controller on page
60.
The Standby Server can be used i n tandem wi th the Redund-
ancy Control l er. See Using Bot h t he Red u nd ancy C ont roller and
t he St and by Serv er on p age 238.
Server Location
The server locations are for each installation to decide based on a risk assessment.
Some customers will choose to locate both ProVision servers on the same site. More
often, for improved security, customers will locate the ProVision servers at different
sites.
The main requirements when defining the server location are:
l That the DCN between both ProVision servers and the network elements is
sufficient to support communications.
l That the LAN or WAN network between the ProVision servers and ProVision
clients is sufficient to support communications.
l That there is a connection between the main server and the standby server, to
allow backup files from the main server to be saved on the standby server.
l If you want to use both the Redundancy Controller and the Standby Server,
the Standby Server must be installed on a server that is separate from the two
Redundancy Controller servers.
Northbound Interfaces (NBI)

Where both ProVision servers are using the ProVision NBI to communicate with one
or more OSS systems, the OSS systems should be configured to poll both ProVision
58 AVIAT NETWORKS
servers. This is to detect any failure and to provide the ability to switch between NBI
feeds, either manually or automatically.
Data Integrity
One ProVision server must be set up and maintained as the main server. All data-
base changes should only be done on the main server, including adding, renaming,
deleting or re-parenting of network elements.
The main server and the standby server should have database backups performed on
a regular basis. A database restore to the standby ProVision server should also be
done, using the main ProVision server’s database backup files, again on a regular
basis. See About Managing and Backing Up the ProVision Database on page 180 for
further details and instructions.
With these backups and data restores in place, if the main ProVision server fails or
communications access to the main NOC site goes down, then ProVision client users
will be able to switch over to the standby server and continue operation.
Switch Over Between ProVision Servers

Both ProVision servers are independent of each other, as are the ProVision clients
This means that, where more than one server is available, a ProVision client can log
on to either ProVision server #1 or ProVision server #2, or even into both at the same
time.
Client users choose which server to log into as part of the login process. You should
make sure that your client users are aware of the standby server setup, and that they
have the IP address or hostname of the main server and the backup server, to use as
required.
User Security
ProVision user login details are stored in the ProVision server database. If data integ-
rity is assured by using regular database backups and restores, the same user login
details will apply to both ProVision servers.
614-330053-001 APRIL 2014 59

Installing and Uninstalling the ProVision

Redundancy Controller
The ProVision Redundancy Controller is a separate software module that enables
standby server management of your ProVision network. The ProVision Redundancy
Controller module must be installed after the main ProVision Server is installed.
Before i nstal l i ng the Redundancy Control l er, back up the
ProVi si on server database.
Users must have l ocal admi ni strator ri ghts to i nstal l Redund-
ancy Control l er on Wi ndows and must be a root user on
Sol ari s.
The Redundancy Control l er can be used i n tandem wi th the
Standby Server. See Using Bot h t he Red u nd ancy C ont roller and
t he St and by Serv er on p age 238.
Prerequisites and Warnings

Table 3-7. ProVision Redundancy Controller Software Requirements
Operating System ProVision Redundancy Con-

troller
Windows XP Pro Yes
Windows 2003 Server Yes
Windows 2008 Server Yes
Windows 7 Yes (install in root directory only)
Windows 8 Yes (install in root directory only)
Windows 2008R2 Yes (install in root directory only)
Solaris 10 (requires Java Yes
1.7.0_40 to be installed)
l The Redundancy Controller needs to be installed on two separate ProVision

Servers, known as the Active and Dormant servers. The same version of
ProVision Redundancy Controller needs to be installed on both of these
servers.
l The Active Server and the Dormant Server each must be set up with the same:
l ProVision Versions.
l License Capabilities . This includes Redundancy, NBI,
node code, and other additional licenses. See Licensing
60 AVIAT NETWORKS
l DCN Bandwidth and Latency. See DCN Bandwidth and

Latency for the Redundancy Controller on page 220.
l Ports. See Network Communication Ports for Firewalls on
page 18
WARNING: Both ser v er s must hav e thei r cl ocks sy n-

chr oni zed f or the Redundancy C ontr ol l er mechani sm to
oper ate cor r ectl y .
WARNING: Pr oVi si on ser v i ce commands (such as pv

ser v i ce stop and ./pv _ser v i ce stop) M UST NOT be used
when Pr oVi si onRedundancy C ontr ol l er i s i nstal l ed and
contr ol l i ng Pr oVi si on ser v i ces. If y ou need to use
Pr oVi si on ser v i ce commands, the Redundancy C on-
tr ol l er must be uni nstal l ed and M y sql r epl i cati on must
be tur ned of f . Thi s i s especi al l y i mpor tant f or Sol ar i s
user s.
WARNING: The Redundancy C ontr ol l er i nter f ace i s onl y

compati bl e wi th the web br owser Inter net Expl or er 9
when IE 9 i s bei ng r un i n C ompati bi l i ty M ode. We
r ecommend F i r ef ox as a br owser to use wi th the
Redundancy C ontr ol l er .
Installation of Redundancy Controller on Active and Dormant Windows

Servers
1. Obtain the ProVision Redundancy Controller Installer file from the
installation DVD.
2. Log onto the Server that contains ProVision Server installation. Copy the
redundancy_controller_setup.exe file onto this server.
3. Run redundancy_controller_setup.exe .
4. Select the language. The default is English. Then click OK.
5. Agree to the terms of the License and click I Agree.
6. Review the installation destination directory. Change this if required, and
then click Next.
On Wi ndows 7, Wi ndows 8, and Wi ndows 2008R2 the Redund-
ancy Control l er must be i nstal l ed i nto the root di rectory of
the dri ve, e.g. c:\ I n versi on 6.11.3 of ProVi si on the defaul t
l ocati on for the i nstal l i s c:\P rogram Files ( x8 6 ) - change i t
to i nstal l di rectl y to c:\
7. The Redundancy Controller must link to the ProVision server directory on
this Server. Change the required ProVision directory if incorrect [ Note: A
valid ProVision server installation must exist otherwise this step will not
proceed]. Then, click Install .
614-330053-001 APRIL 2014 61

8. The Redundancy Controller installation runs. At the end, click Finish .

9. The Redundancy Controller is now running as a Service and is configured to
automatically start whenever the Server is powered up. The service can be
restarted or stopped from the main Start menu item ProVision
Redundancy Controller.
10. Repeat the above steps for the other ProVision server machine.
11. The Redundancy Controller is now installed and running on both Servers in
a dormant latched state.
Installation of Redundancy Controller on Active and Dormant Solaris

Servers
1. Obtain the ProVision Redundancy Controller Installer file from the main
installation DVD.
2. Log onto the Server that contains your main ProVision Server installation.
Copy the redundancy_controller_install.jar file onto this server.
3. Run java -Dfile.encoding=UTF-8 -jar redundancy_controller_
install.jar. The installation wizard appears, prompting you with the
installation steps.
4. Accept the terms of the license. Click on the I Accept button and click Next.
5. Review the installation destination directory. Change this if required, and
then click Next.
6. The Redundancy Controller must link to the ProVision server directory on
this Server. Change the required ProVision directory if incorrect. Then click
Next and then click Next again .
A val i d ProVi si on server i nstal l ati on must exi st otherwi se thi s

step wi l l not proceed.
7. The Redundancy Controller installation runs. At the end, click Next and
click Done.
8. The Redundancy Controller is now running as a Service and is configured to
automatically start whenever the Server is powered up. See Stop, Start,
Backup, and Restore the Redundancy Controller on page 91
10. The Redundancy Controller is now installed and running on both Servers in
a dormant latched state.
Setting Up User Names and Passwords

To use the Redundancy Controller, log in with a user name and password. The
default user name and password is ‘admin’. To change the password, log in and go
to Redundancy Controller Security Screen on page 231.
If using a Radius Server to manage user names and passwords, the hierarchy
changes to the following:
1. Primary Radius server user name/password first if available. Login fails if
user/password incorrect.
62 AVIAT NETWORKS
2. Secondary Radius server user name/password second [if configured] if

available. Login fails if user/password incorrect.
3. Local user last [there is only one and it is ‘admin’]. This is only attempted if
no connections can be established with a Radius server.
After Installing the Redundancy Controller

1. The Redundancy Controller is installed and running on both Servers in a
dormant latched state. You must log into each Redundancy Controller and
configure it via its web browser interface. See Logging Into the Redundancy
Controller on page 224.
This step is required to activate the Active server and finalize setting
up the Redundancy Controller.
For a Solaris install, the pv_ service in the <PV SERVERROOT> dir-
ectory is left intact, but you should NOT execute commands manually
if the Redundancy Controller is installed.
2. Configure the Redundancy Controllers Peer IP address correctly. See the

example below and the help topic Redundancy Controller Configuration
Screen on page 229
F or exampl e, Redundancy Control l er Server A I P address i s
10.18.1.22 and Redundancy Control l er Server B I P address i s
10.18.1.28. On Server A set the Peer I P address to be
10.18.1.28 and on Server B set the Peer I P address to be
10.18.1.22. The two servers are now confi gured to com-
muni cate wi th each other.
3. The server that is going to be the Active server needs to be switched from
dormant latched to active by clicking on the Switch button on the Active
server Redundancy Controller Status Screen. See Redundancy Controller
Status Screen on page 225.
4. Login with a ProVision client onto the Active server to check that the
ProVision server is running correctly. Clients can now connect to this server,
but the Redundancy Controller operation is not enabled or complete.
5. Unlatch the Dormant server from dormant latched to dormant by clicking
the Unlatch button on Dormant server Redundancy Controller Status
Screen. See Redundancy Controller Status Screen on page 225.
6. The Dormant server now resynchronizes with the Active server and loads a
copy of the database. The Dormant server then synchronizes the external
files from the Active server.
7. The Redundancy Controller is now fully functional and replicating real time
data for ProVision. See Normal Operation of Redundancy Controller on page
222.
614-330053-001 APRIL 2014 63

Uninstalling the Redundancy Controller

CAUTION:If uninstallation is required, uninstall the Dormant server first. This will prevent the Dor-
mant server becoming Active.
Uninstalling the Redundancy Controller from Windows Servers

1. From the Start > ProVision Redundancy Controller menu, select and run
ProVision Redundancy Controller Uninstaller
2. The Uninstallation wizard displays. Click Uninstall to start.
3. Click Yes on the warning that displays.
4. A message asks you to approve the Manual steps. Click OK.
5. Click Finish to confirm the uninstallation has finished.
Uninstalling the Redundancy Controller on Solaris Servers

1. As root/supervisor, run java -jar
ProVisionRedundancyController/Uninstaller/uninstaller.jar
from the directory above ProVisionRedundancyController directory.
2. The Uninstallation wizard displays. Click on checkbox Force the deletion of
ProVision Redundancy Controller and click Uninstall).
3. When the progress bar displays Finish , click Quit.
After Uninstalling the Redundancy Controller

Once the Redundancy Controller has been uninstalled from both the dormant and
active systems as described above, the ProVision Server is not running.
The ProVision Server needs to be restarted on the active Server so that it is running
as an independent Service.
Login with a ProVision client onto the active server to check that the ProVision
Server is running correctly.
64 AVIAT NETWORKS
Windows 8 Navigation and Uninstallation

I nstal l i ng ProVi si on on Wi ndows 8 uses the standard Wi ndows
i nstal l procedures descri bed here: Inst alling_ ProVision1. ht m.
Navigation
The Windows 8 interface is designed for touch-screens. When ProVision is installed
on a Windows 8 PC, the ProVision function icons display as follows in the Apps
view.
Procedure
1. In Windows 8, to find the ProVision function icons, swipe in from the right edge
of the screen, and then tap Search .
2. If you're using a mouse, point to the upper-right corner of the screen, move the
mouse pointer down, and then click Search .
3. The Search screen displays with the icons for:
614-330053-001 APRIL 2014 65

l Provision Client
l Provision Server command window
l ProVision Redundancy Controller Web Browser
l Provision Redundancy Controller Start
Uninstalling ProVision on Windows 8

To uninstall any ProVision software on a Windows 8 PC, access the Control Panel
>Programs >Uninstall a program. You can also access the Control Panel from the
Search screen.
66 AVIAT NETWORKS
Chapter 4. Upgrading ProVision
This section provides instructions for upgrading to ProVision from an earlier revi-
sion.
l Introduction to Upgrading on page 68
l Upgrade Prerequisites on page 72
l Database Restore Upgrade on page 79
l Database Migration Upgrade on page 81Upgrade Installation of the ProVision
Client on page 76
l Topology Upgrade on page 84
l After Upgrade: Review and Testing on page 93
l Upgrading the Redundancy Controller on page 85
614-330053-001 4/04/2014 67
CHAPTER 4. UPGRADING PROVISION
Introduction to Upgrading
This section provides instructions for upgrading to the latest version of ProVision
from an earlier version of the software.
WARNING: Read thi s enti r e secti on bef or e y ou attempt
an upgr ade pr ocedur e. You must sel ect the cor r ect
upgr ade pr ocess f or y our v er si on, set up the pr e-
r equi si tes, and appl y the upgr ade usi ng the i nstr uc-
ti ons.
What Is An Upgrade?
What is an upgrade? An upgrade replaces your old version of ProVision with the new-
est version. Upgrading lets you benefit from improved new features. When you
upgrade, you can move most of your network database over to the upgrade version of
ProVision.
If you upgrade frequently, easier upgrade processes are available, and you can move
the maximum amount of data into new software versions.
The Right Upgrade Process For Your Version

There are several upgrade options available. See the topic Upgrade Process Options
on page 70 to identify the upgrade requirements for your version.
Once you know your upgrade requirements, refer to the following topics:
l Upgrade Prerequisites on page 72
Upgrade procedures:
l Database Restore Upgrade on page 79
l Database Migration Upgrade on page 81
l Upgrade Installation of the ProVision Client on page 76
l Topology Upgrade on page 84
l Upgrading the Redundancy Controller
After you have upgraded:
l After Upgrade: Review and Testing on page 93
Thi s secti on descri bes how to upgrade for versi on 6.0 and
l ater, up to the current versi on. I f you are upgradi ng from a
versi on earl i er than 6.0, you must upgrade to 6.0 before
upgradi ng further. Pl ease consul t the documentati on for the
earl i er versi ons of ProVi si on for those upgrade processes.
68 AVIAT NETWORKS
CAUTION:The MTOSI NBI must be upgraded separately, and there are

steps to take before and after the ProVision server upgrade. For more
information see the Installation and Upgrade section of MTOSI NBI
and ProVision on page 349
614-330053-001 APRIL 2014 69

Upgrade Process Options

The procedure for upgrading ProVision varies based on your current version of ProVi-
sion.
The database from an older version must be upgraded correctly to preserve as much
data as possible. You must upgrade fully to one version of ProVision before upgrad-
ing to the next one.
The earlier your version of ProVision, the more upgrades you need to perform, and
you may need to use some additional tools. If you have versions earlier than 6.0, the
Topology Upgrade process is recommended, followed by reconfiguring your network
information (This prevents having to do multiple Database Migration Upgrade pro-
cedures).
This table describes the upgrade requirements for different versions of ProVision.
l DB Migration = Database Migration Upgrade
l DB Restore = Database Restore Upgrade
l = This step can be skipped; proceed to the next step.
Table 4-1. Upgrade Process Requirements
Start 6.5.3 6.11.5
Ver- 6.0.1, 6.2.1, throug-
6.1.1 6.3.1 6.4.1 6.4.3 6.5.1 6.5.2 h
sion 6.0.2 6.2.2
below 6.11.4
6.0.1, DB DB DB DB DB
6.0.2 Migra- Migra- Migra- Migra- Restore
tion tion tion tion
6.1.1, DB DB DB DB
6.2.1, Migra- Migra- Migra- Restore
6.2.2 tion tion tion
6.3.1 DB DB DB
Migra- Migra- Restore
tion tion
6.4.1, DB DB
6.4.3 Migra- Restore
tion
6.5.1 DB
throu- Restore
gh
6.11.-
4
70 AVIAT NETWORKS
For example, if you want to upgrade from ProVision 6.1.1 to 6.11.5 you must follow
the requirements in the second row of the table and:
1. First, use the Database Migration Upgrade procedure to upgrade the 6.1.1 data-
base into 6.11.4. (Note that the Database Migration tools are located on the 6.3.1
CD).
2. Use the Database Migration Procedure to upgrade from 6.3.1 to ProVision 6.4.3.
(Note that the Database Migration tools are located on the 6.4.3 CD).
3. Use the Database Migration Procedure to upgrade from 6.4.3 to ProVision 6.5.2.
(Again, the Database Migration tool is on the 6.5.2 DVD).
4. Use the Database Restore Upgrade procedure to upgrade directly from 6.5.2 to
ProVision 6.11.5. (The restore tool is built into the software).
There i s al so the Up grad e Inst allat ion of t he ProVision C lient on
p age 76 , for versi ons after 6.4.
I f you are usi ng the Redundancy Control l er modul e, thi s
i mpacts the upgrade process. See Up grad ing t he Red u nd ancy
C ont roller.
614-330053-001 APRIL 2014 71

Upgrade Checklist
Review and use this list to make sure that you have done everything required before
the upgrade.
l ProVision Installation DVD and Database Migration Tools (CD, DVD, or files
from FTP site)
l Fulfilled all upgrade prerequisites. Upgrade Prerequisites on page 72
l Data from current installation backed up, saved in secure location outside the
ProVision server directory. Backing Up Data from Current Installation on page
73
l If Standby Servers are available, are they ready to be upgraded? Upgrading
Primary and Standby Servers on page 73
l Low-requirement time scheduled for upgrade procedure? Scheduling Upgrade
Installation on page 74
Upgrade Prerequisites
The prerequisites for upgrading the complete ProVision installation are:
l ProVision Installation DVD (6.5 or later) or CD (earlier versions)
l All ProVision Installation DVDs (6.5 or later) or CDs (earlier versions) that are
required for upgrading to intermediate versions.
l Windows PC or Sun Server/Workstation - ProVision server
l Backups of data from current installation:
l System backup
l NBI, maps, Eclipse and TRuepoint backup folders
l Topology
l Any customized template files
l Any customized configuration information
l Any customized MTOSI NBI files (see the Installation and
Upgrade section of MTOSI NBI and ProVision on page
349
A ProVi si on Cl i ent onl y upgrade requi res the ProVi si on I nstal l -

ati on DVD or CD.
F or versi ons before 6.6.0, the database mi grati on tool s are
al ways on the i nstal l ati on DVD or CD. F rom 6.6.0 onward, the
database mi grati on mechani sm i s bui l t i nto ProVi si on.
72 AVIAT NETWORKS
Backing Up Data from Current Installation

Before you begin the upgrade, you need to back up data from the current install-
ation.
1. Establish a safe storage location for the backup files.
A safe l ocati on i s one that i s not wi thi n the ProVi si on server
or ProVi si onCl i ent fol ders.
2. Run a manual backup of the system: see Database Backup Procedures on
page 184.
3. Copy the following folders and files from the ProVision server installation
folder.
l ProVision_license.xml file
l mysql\backup
l NBI
l Maps
4. Check the directory ProVisionServer\conf and subdirectories. Review the
timestamps on all the files in this directory, and record any changes made to
the default settings in the files, for example, the file
conf\ftp\user.properties.
5. Check the directory
ProVisionServer\tomcat\webapps\ROOT\PV\templates.
6. Check the timestamps on all the files in this directory.
7. Record any changes made to the default settings in the files, for example,
the files security_policy.xml and server_configuration.xml
8. Save the backup, folders, and files to the safe location.
I f you have enough di sk space, you can copy the enti re ProVi -
si onServer i nstal l ati on di rectory to a safe storage l ocati on.
CAUTION:Files such as the topology files, database backups, the
license file, NBI files, background maps and all log files MUST be
copied and saved to a directory outside of the <Install Dir-
ectory>\ProVision server computer prior to uninstalling the ProVision
server application. Otherwise these files will be deleted by the unin-
stall process.
6. Export the topology file. Refer to Exporting the Topology on page 164.
Upgrading Primary and Standby Servers

If your ProVision installation includes both Primary and Standby servers, both types
of server must have the same version of ProVision installed.
If you upgrade one server, you must upgrade the other server. Upgrade both your
Primary and Standby servers at the same time.
614-330053-001 APRIL 2014 73

WARNING: Do not r un any backups unti l both the

Pr i mar y and Standby ser v er s hav e the same v er si on of
Pr oVi si on i nstal l ed. If a backup to tr ansf er r ed f r om
Pr i mar y to Standby ser v er when the ser v er v er si ons
do not match, ther e may be database r estor e er r or s,
and the Standby Ser v er may not r estar t.
Instructions
1. Upgrade the Standby server to the latest ProVision version.
2. Set the Standby server temporarily to be Primary.
2. Upgrade the Primary server to the latest ProVision version.
3. Change the Standby server to Standby from Primary.
4. Run a manual backup on the Primary server.The Backup should transfer to the
Standby server, which should restart with the same database as the Primary server.
Troubleshooting
If you have attempted to run a backup when the Primary and Standby server ver-
sions did not match, you can fix the resulting database and version errors:
l Ensure that both the Primary and intended Standby servers have the same
version of ProVision installed.
l Reset the database on the intended Standby server: see ProVision Commands
on page 44.
l Log on to the intended Standby server and set it as the Standby server: see
Standby Server Deployment on page 12.
l Run a backup from the Primary server: see Redundant Server Deployments on
page 203
l The databases should now match on both Primary and Standby servers.
Scheduling Upgrade Installation

It is recommended that you schedule upgrade installation to take place overnight or
at another low-requirement time. After the upgrade is complete, when the server is
restarted, the process of restarting ProVision can take several hours, as databases are
upgraded. It will also create additional loading on the server; the ProVision client
and server operations may take longer than normal to complete.
Impact of Upgrade
Allow for a downtime of 4 hours per server during the upgrade process, in case any
problems occur. A typical upgrade should take 1 hour per server if no problems
74 AVIAT NETWORKS
occur.
Note that no new events or performance data will be collected during the upgrade.
After the upgrade, some devices like Eclipse will perform an event resynchronization
of active events.
614-330053-001 APRIL 2014 75

Upgrade Installation of the ProVision

Client
About Client Upgrade Installations
From version 6.4 onwards, users upgrading ProVision can choose to do an Upgrade
Installation of the ProVision client. The Upgrade Installation option overwrites pre-
vious ProVision Client software while retaining important ProVision client data. This
includes:
l Configuration Settings (including user logins and passwords)
l Client MIBs
l Eclipse JAR files
Follow these instructions to perform an Upgrade Installation.
Procedure
1. Insert the ProVision installation DVD or CD in the CD-ROM drive.
2. Select client_setup.exe.
3. A message displays, warning you that you may have a version of ProVision Client
running on this computer. Ensure that all users are logged out of ProVision, and
that ProVision Client is shut down. Then, click Yes.
4. Select Open . The License Agreement window displays.
76 AVIAT NETWORKS

6. The Choose Your Overwrite Method screen displays. In this screen, select your
install type:
Upgrade Install - Overwrites previous ProVision Client software while retaining
some ProVision Client data
Clean Install - Deletes all previous ProVision Client software and data
7. Then, click Next.

9. When the installation is completed, select Finish.
614-330053-001 APRIL 2014 77

10. Remove the ProVision installation media.
78 AVIAT NETWORKS
Database Restore Upgrade

About Database Restore Upgrades (Applies to 6.6.0 Onwards)
When you upgrade from certain versions of ProVision, a full database migration is
not required. Instead, you can use a Database Restore Upgrade. See Upgrade Process
Options on page 70.
Database Restore Upgrades are used between closely related versions. To do this,
save a backup of the older version of ProVision, and use that backup to restore the
database into the later version of ProVision. Then, restart ProVision. During the
restore process, the database is migrated if required.
Database Restore Upgrade Process:

1. Uninstall the earlier version of ProVision. Note that this will delete the backup
folder:
<Install Directory>\ProVisionServer\MySQL\Backup.
2. Install the new version of ProVision.
3. Copy the saved database, with the backuplisting.xml file, to the newly
installed database backup folder,
<Install Directory>\ProVisionServer\MySQL\Backup.
4. Restore the database into ProVision (Restoring the ProVision Database on page
187).
5. Copy the saved ProVision_license.xml file to the ProVisionserver directory.
6. Copy the saved map files into the ProVisionServer\maps directory.
7. Copy the saved NBI files into the ProVisionServer\NBI directory, if required.
8. Reapply changes made to the default settings in the files security_
policy.xml and server_configuration.xml. These two files are located in the
directory ProVisionServer\tomcat\webapps\ROOT\PV\templates.
WARNING: Do not copy secur i ty _pol i cy .xml and
ser v er _conf i gur ati on.xml f i l es f r om the pr ev i ous v er -
si on of Pr oVi si on as they may not be compati bl e.
Finalize the Upgrade:

1. Restart ProVision. In the command window type pv service start
(or ./pv_service_start for Solaris)
to restart the ProVision server.
614-330053-001 APRIL 2014 79

2. Start a ProVision client session.

3. Setup the newly installed ProVision. See Workflow for Setting Up ProVision on
page 109.
80 AVIAT NETWORKS
Database Migration Upgrade

About Database Migration (ProVision 6.5.2 and earlier)
The database migration process has two steps:
Step 1. Database Export and Conversion

This is a stand-alone command line program that runs in the ProVision server applic-
ation. It exports the current active ProVision database to an intermediate XML
format. The converter then parses and modifies the XML files as necessary to convert
the database formatted for one version to a format compatible with a higher version
of ProVision.
Step 2. Database Import

This is built into ProVision and is launched using a server command.Run the com-
mand from the ProVision directory. The import command performs a database reset
and then allows you to select a database that you previously exported from an earlier
version of ProVision and converted. The command also checks for database version
compatibility.
The process of upgrading from one version of ProVision to a higher version is
described in Upgrade Process Options on page 70.
Notes and Warnings

WARNING: The databases f r om one v er si on of Pr oVi -
si on ar e i ncompati bl e wi th any of the other v er si ons
[the onl y excepti ons ar e noted i n Datab ase R e store
Upgrade on page 79 .] Ther ef or e, the database mi gr ati on
tool M UST be used each ti me a database i s mi gr ated
f r om one v er si on of Pr oVi si on to a hi gher v er si on. See
Upgrade Proce ss Options on page 70
CAUTION:Note that there are two steps in the upgrade process (Migra-
tion steps 3 and 7) that can each take over an hour, due to the large
amount of data processing required. Please schedule time for this
upgrade accordingly.
I f you onl y need to upgrade a ProVi si on Cl i ent, see Up grad e

Inst allat ion of t he ProVision C lient on p age 76 .
614-330053-001 APRIL 2014 81

I f you are upgradi ng to ProVi si on 6.3 or l ater to Wi ndows 7,

Wi ndows 8, or to Wi ndows 2008-R2, the ProVi si on Cl i ent pro-
gram i s i nstal l ed to thi s fi l e l ocati on: <Install Dir-
ectory>\ProVisionClient. Do not change thi s l ocati on as
cl i ent wi l l not work correctl y i f i nstal l ed i n Program F i l es di r-
ectory.
Migrating to a Later Version of ProVision:

CAUTION:Step 3 can take over an hour, depending on the size of the
database. It is completed when the message “Please uninstall ProVi-
sion X.x and install Y.y” is shown.
CAUTION:Step 7 can take over an hour, depending on the size of the

database. It is completed when the message “Database import com-
pleted” is shown.
1. Close all open applications.

2. From the appropriate ProVision installation DVD or CD for the version you are
upgrading to, copy the following database migration tools, into <Install Dir-
ectory>\ProVision server:
l Windows - migration.jar and migrate.bat
l Solaris - migration.tar (Copy into ProVision server directory then run the
command. tar -xvf migration.tar)
See Upgrade Process Options on page 70 to identify the required installation
DVD/CDs.
When you execute the migrate command in step 8, ProVision takes all the database
files located in<Install Directory>\ProVisionServer\mysql and converts
them into database files that are compatible with the higher version of ProVision.
3. In the command window, type:
migrate <directory>.
(or ./pv_db_migrate <directory> for Solaris)
where <directory> is the new location of the migrated database data.
Ensure <directory> is not located in the <Install Directory>\ProVision
server to prevent it from being deleted during the uninstall process.
If you do not specify a directory in this step, ProVision saves the database data to a
directory named \pv_migration. This is located in the user’s home directory.
CAUTION:The location of the migrated database data cannot be the
same location that was used in previous migrations. Otherwise the
migration process will overwrite the old migrated database data. A pos-
sible result of this is that the directory may contain both old data files
and newly-migrated data files, resulting in corrupted migration data.
4. Uninstall the ProVision server and client software. Refer to See "Uninstalling ProVi-
sion".
82 AVIAT NETWORKS
5. Install the released ProVision server and client software. Refer to Installing and
Uninstalling ProVision on page 46.
6. Stop the ProVision server. Copy the license fileprovision_license.xml back
to the directory <Install Directory>\ProVision server.
I f you are upgradi ng a Sol ari s system, make sure that you
have the l atest versi on of Java i nstal l ed (1.6.24 for Sol ari s 10
or l ater). Thi s i s i ncl uded on the ProVi si on i nstal l ati on set.
7. In the command window type pv import <directory>
(or ./pv_db_import <directory> for Solaris)
where <directory> is the location of the database that was converted in step 8.
If no directory is specified, ProVision creates a directory called \pv_migration, loc-
ated in the user’s home directory, and places the converted database files in this
newly created directory.
8. This is completed when the message Database import completed is shown.
9. Copy the saved provision_license.xml file to the ProVisionServer directory.
Finalize the Upgrade

1. Restart ProVision. To do this, in the command window type pv service start
(or ./pv_service start for Solaris)
to restart the ProVision server.
3. Setup the newly installed ProVision. Refer to Workflow for Setting Up ProVision
on page 109.
614-330053-001 APRIL 2014 83

Topology Upgrade
About Topology Upgrades
The topology upgrade is a short, simple upgrade method, from any earlier version to
the latest version, using the Topology Import and Topology Export functions. This is
available for all previous versions of ProVision. Refer to Importing the Topology on
page 163.
Note that this only upgrades the topology: the ProVision topology data does not
include events, performance data, user settings, and other information. Please review
Upgrade Prerequisites on page 72 before deciding if a topology upgrade meets your
requirements.
Topology Upgrade Procedure

1. Export the topology file. Refer to Exporting the Topology on page 164.
2. Backup the ProVision database. Refer to Database Backup Procedures on page
184.
3. Copy the topology file to another directory NOT located within <Install Dir-
ectory>\ProVisionserver.
4. Copy the ProVision license file, provision_license.xml, to another location
NOT within <Install Directory>\ProVisionserver.
5. Close all open applications.
6. Uninstall the ProVision server and client software. Refer to See "Uninstalling ProVi-
sion".
7. Install the released ProVision server and client software. Refer to Installing and
Uninstalling ProVision on page 46.
8. Copy the license file provision_license.xml back to the directory <Install
Directory>\ProVisionserver.
9. In the command window type pv service stop to stop the ProVision server.
(For Solaris, type ./pv_service_stop).
10. In the command window type pv service start to restart the ProVision
server. (For Solaris, type ./pv_service_start).
12. Import the topology file that you exported in step 1. Refer to Importing the Topo-
logy on page 163.
13. Setup the newly installed ProVision. Refer to Workflow for Setting Up ProVision
on page 109.
84 AVIAT NETWORKS
Upgrading the Redundancy Controller

There are several options for upgrading the Redundancy Controller:
l Upgrading the Redundancy Controller Only
l Upgrading the Redundancy Controller and the Server
They are all described in this section.
Before You Upgrade

Before upgradi ng the Redundancy Control l er, back up the
ProVi si on server database.
Scheduling Upgrade Installation

It is recommended that you schedule upgrade installation of active and dormant
servers to take place overnight or at another low-requirement time.
Impact of Upgrade
Allow for a downtime of 4 hours for per server during the upgrade process, in case
any problems occur. A typical upgrade should take 1 hour per server if no problems
occur.
Note that no new events or performance data will be collected during the upgrade.
After the upgrade, some devices like Eclipse will perform an event resynchronization
of active events.
Rollback to Previous Version

If problems occur during upgrade procedure then it may be necessary to rollback the
Server and the Redundancy Controller back to the previously installed version.
Rollback involves installing a previous version of the Server and Redundancy Con-
troller, and repeating the required upgrade procedure.
How To Stop, Start, Backup, and Restore the Redundancy Server

These frequently used steps are described in this help topic: Stop, Start, Backup, and
Restore the Redundancy Controller on page 91
614-330053-001 APRIL 2014 85

Upgrading the Redundancy Controller Only

To upgrade the ProVision Redundancy Controller, you must first upgrade the Dor-
mant server, followed by the Active server.
Prerequisites
l Copy the latest ProVision Redundancy Controller installer to a safe location on
both servers. During the upgrade process the ProVision Redundancy Controller
directory is removed.
WARNING: The Acti v e ser v er wi l l be stopped dur i ng
thi s upgr ade and thi s wi l l mean that al l Pr oVi si on cl i -
ents wi l l be di sconnected unti l the upgr ade of the Act-
i v e ser v er Redundancy C ontr ol l er has been compl eted.
The Acti v e ser v er wi l l not be col l ecti ng per f or mance
data or r ecei v i ng tr aps f r om dev i ces dur i ng the
upgr ade.
WARNING: 15-mi n per f or mance data and ev ents f r om

dev i ces wi l l not be col l ected dur i ng the upgr ade.
Upgrading Dormant Server Redundancy Controller:

On the Dormant Server:
1. Stop the Redundancy Controller on the Dormant server. See Stop, Start, Backup,
and Restore the Redundancy Controller on page 91
2. Backup the configuration file to a safe location. See Stop, Start, Backup, and
3. Uninstall the current ProVision Redundancy Controller. See Installing and Unin-
stalling the ProVision Redundancy Controller on page 60
4. Install the new Redundancy Controller in the same location as the previous install-
ation. See Stop, Start, Backup, and Restore the Redundancy Controller on page 91
6. Restore the configuration file from the safe location.See Stop, Start, Backup, and
The dormant server i s stopped to prevent the acti ve server

resynchroni zi ng wi th an i ncompati bl e dormant server duri ng
the upgrade whi ch woul d corrupt the ProVi si on database.
86 AVIAT NETWORKS
Upgrading Active Server Redundancy Controller and ProVisionServer:

On the Active Server:
7. Stop the Redundancy Controller. See Stop, Start, Backup, and Restore the Redund-
ancy Controller on page 91
9. Uninstall the current Redundancy Controller. See Installing and Uninstalling the
ProVision Redundancy Controller on page 60
10. Install the new ProVision Redundancy Controller in the same location as the pre-
vious installation. See Installing and Uninstalling the ProVision Redundancy Con-
troller on page 60
11. Stop the Redundancy Controller. See Stop, Start, Backup, and Restore the
Redundancy Controller on page 91
12. Restore the configuration file from the safe location. See Stop, Start, Backup, and
The acti ve server i s stopped to prevent the acti ve server
Starting the Active Server:

13. Start the Redundancy Controller on the Active server. See Stop, Start, Backup,
14. Log in to the Redundancy Controller web interface of the Active server and click
switch. Wait until the Active server returns to its normal Active Main Server state.
The Active server restart is now complete.
ProVi si on cl i ents can now be connected agai n to the Acti ve

server.
Starting the Dormant Server:

15. Start the Redundancy Controller on the Dormant server. See Stop, Start, Backup,
16. Log in to the Redundancy Controller web interface of the Dormant server and
wait until the dormant server returns to the Dormant state after resynchronizing
database and external files. The Dormant server restart is now complete.
614-330053-001 APRIL 2014 87

Upgrading the Redundancy Controller and the

ProVision Server
To upgrade the ProVision Redundancy Controller and the ProVision Server in the
same procedure, the Dormant server and the Active server must be upgraded at the
same time to ensure compatibility between database and software versions.
It is recommended that the Dormant server is upgraded before the Active server to
prevent the Dormant server resynchronizing with an incompatible Active server dur-
ing the upgrade process. This would corrupt the ProVision database.
Prerequisites
l Copy the latest ProVision Redundancy Controller installer and ProVision
Server to a safe location on both servers. During the upgrade process the
ProVision Redundancy Controller and ProVision Server directories are
removed.
WARNING: The Acti v e and Dor mant ser v er s and wi l l be
stopped dur i ng thi s upgr ade and thi s wi l l mean that al l
Pr oVi si on cl i ents wi l l be di sconnected unti l the
upgr ade of Acti v e ser v er Redundancy C ontr ol l er and
Pr oVi si on ser v er hav e been compl eted. Acti v e Ser v er
wi l l not be col l ecti ng per f or mance data or r ecei v i ng
tr aps f r om dev i ces dur i ng the upgr ade.
WARNING: 15-mi n per f or mance data and ev ents f r om

dev i ces wi l l not be col l ected dur i ng the upgr ade.
Upgrading Dormant Server Redundancy Controller and ProVision

Server:
On the Dormant Server:
3. Uninstall the current ProVision Redundancy Controller. See Installing and Unin-
stalling the ProVision Redundancy Controller on page 60
4. Upgrade ProVision Server on the Dormant Server, in the same location as the pre-
vious installation. See Upgrading ProVision on page 67.
troller on page 60
88 AVIAT NETWORKS
The dormant server i s stopped to prevent the acti ve server
Upgrading Active Server Redundancy Controller and ProVision server:

On the Active Server:
8. Stop the Redundancy Controller. See Stop, Start, Backup, and Restore the Redund-
10. Uninstall the current Redundancy Controller. See Installing and Uninstalling the
ProVision Redundancy Controller on page 60
11. Upgrade the current ProVision Server in the same location as the previous install-
ation. See Upgrading ProVision on page 67.
troller on page 60.
13. Stop the Redundancy Controller. See Stop, Start, Backup, and Restore the
The acti ve server i s stopped to prevent the acti ve server
Starting the Active Server:

15. Start the Redundancy Controller on the Active server. See Stop, Start, Backup,
16. Log in to the Redundancy Controller web interface of the Active server and click
switch . Wait until the active server returns to its normal Active Main Server state.
The Active server restart is now complete.
After the ProVisionserver has finished starting, the ProVision clients can be con-
nected to the Active server again.
Starting the Dormant Server:

17. Start the Redundancy Controller on the Dormant server. See Stop, Start, Backup,
614-330053-001 APRIL 2014 89

18. Log in to the Redundancy Controller web interface of the Dormant server and
wait until the dormant server returns to the Dormant state after resynchronizing
database and external files. The Dormant server restart is now complete.
90 AVIAT NETWORKS
Stop, Start, Backup, and Restore the

This section details operations that are commonly performed by the Administrator of
the Redundancy Controller on the Redundancy Servers (Main Active Server and Dor-
mant Server). Separate commands are provided for Windows and Solaris.
You must be the Admi ni strator User on Wi ndows or the Super
User on Sol ari s to perform these commands.
Stop Redundancy Controller

Windows
l From the Start menu go to ProVision Redundancy Controller->Stop Server
Solaris
l From the command line enter
/etc/init.d/ProVisionRedundancyController stop
Start Redundancy Controller

Windows
l From the Start menu go to ProVision Redundancy Controller->Start
Server
Solaris
l From the command line enter
/etc/init.d/ProVisionRedundancyController start
Backing up the Redundancy Configuration xml file to safe location

Windows
l Copy the file <ProVisionRedundancy ROOT
folder>\jetty\webapps\rc\WEB_INF\classes\redundancy_
configuration.xml to a safe location outside of <ProVision Redundancy
Root folder>.
Solaris
l From the command line enter cp <ProVision Redundancy ROOT
folder>/jetty/webapps/rc/WEB_INF/classes/redundancy_
configuration.xml to a safe location outside of <ProVision Redundancy
Root folder>.
614-330053-001 APRIL 2014 91

Restoring the Redundancy Configuration xml file from safe location

Windows
l Copy the file redundancy_configuration.xml from the safe location to
<ProVision Redundancy ROOT folder>\jetty\webapps\rc\WEB_
INF\classes, using explorer or copy command in a cmd prompt.
Solaris
l From the command line enter cp <safe location
folder>/redundancy_configuration.xml <ProVision Redundancy
ROOT folder>/jetty/webapps/rc/WEB_INF/classes
92 AVIAT NETWORKS
After Upgrade: Review and Testing

After the upgrade is complete, you need to review and test the upgrade. To do this:
1. Check that the system is working as expected.
2. Check user settings, purge settings, notification settings, events, and performance
data.
3. Check the device compatibility in the newly installed ProVision. Checking Device
Compatibility on page 93.
4. Check for any invalid deployed devices in the newly installed ProVision. See Check-
ing for Invalid Deployed Devices on page 95.
I f the upgrade was a Topol ogy Upgrade, or there were other

changes, see Workflow for Set t ing Up ProVision on p age 109 .
Checking Device Compatibility

The Compatibility Advisor function reviews your radio system configuration and
identifies any problems with incompatible devices or software. It specifically checks
for problems with RAC plug-in compatibility and Eclipse software upgrades.
View the Compatibility Advisor after you install a software upgrade, or after you
receive a Aviat Networks Product Bulletin that identifies changes. When you view
this, a screen displays with the compatibility status. Use the radio buttons in this
screen to display either:
l Devices that have compatibility problems:
614-330053-001 APRIL 2014 93

l Compatibility problems that have been found:
The Compatibility Advisor identifies and recommends fixes for the following com-
patibility problems:
l RAC 30v1 is present: The check process identifies an RAC 30v1, a plug-in that
cannot be used in conjunction with a RAC 30v3.
l RAC 30v2 Software Upgrade Required: The check process has found a RAC
30v2 with software that is not compatible with a RAC 30v3, you must use
03.05.12 software or above
l RAC 30v2 Not in Auto-Compatibility Mode: The check process has found an
RAC 30v2 that has been switched out of automatic compatibility mode.{This
should be reconfigured using Portal for maximum compatibility with RAC
30v1 and v3.
94 AVIAT NETWORKS
l NCC Version 1: The check process has found an INUe with Version 1 installed.
Version 1 NCCs cannot have software loaded by ProVision if they have more
than one ODU.
l Two-step Software Upgrade Required: To upgrade an identified unit to the
latest software versions, you will first have to install a version of software
between 2.6.58 and 2.9.69.
l If a problem is displayed with blue text, it is an informational note. If a
problem displays in purple text, it shows that there is a serious compatibility
problem.
Procedure
1. In ProVision, go to the Tree Viewer. Right-click on the root item. Below the root
item, right-click on the ProVision icon. From the right-click menu, select Com-
patibility Checking.
2. The Compatibility Advisor window displays. Review the results.
3. Save the compatibility issue record by clicking Save. Assign a file name. This
saves the record as a.txt file.
4. Make changes to the system configuration to fix the compatibility problems. Then,
repeat steps 1 through 4.
Checking for Invalid Deployed Devices

If you are upgrading from version 6.0.1 or earlier, ProVision automatically runs class
checking. Class checking identifies any radios that have been deployed with an incor-
rect device class in ProVision. Some radios that are correctly deployed may receive
the “invalid deployment” warning event during the upgrade. The procedure below
shows you how to identify and correct invalid deployments.
Procedure
Follow the steps below to check for invalid deployed devices after a database migra-
tion or import.
1. In ProVision, go to the Event Browser. Review the Event Browser for “invalid
deployment” events. Use the Filter function to find all events titled Invalid Deploy-
ment, as shown below:
2. Clear the Invalid Deployment events.

3. One hour later, review the Event Browser again. If any Invalid Deployment events
recur for Eclipse devices, this indicates a deployment problem. Record the device
614-330053-001 APRIL 2014 95

details. Delete the affected devices, and redeploy the devices with the correct radio
type. See Deploying in the ProVision User Guide for more information.
96 AVIAT NETWORKS
Rollback to Previous Version

If problems occur during upgrade procedure then it may be necessary to rollback
ProVision to the previously installed version.
Rollback involves installing a previous version of ProVision, using these instructions.
Instructions
1. Uninstall the ProVision Client and Server.
2. Install your previous version of ProVision. Use the files saved during your
Upgrade procedure.
3. Copy the saved database, with the backuplisting.xml file, to the newly installed
database backup folder, <Install Directory>\ProVisionServer-
\MySQL\Backup.
4. Restore the database into ProVision: see Restoring the ProVision Database on page
187.
5. Copy the saved provision_license.xml file to the ProVisionserver directory.
8. Reapply changes made to the default settings in the files security_
policy.xml and server_configuration.xml. These two files are located in the
directory ProVisionserver\tomcat\webapps\ROOT\PV\templates.
ProVi si on system data wi l l be restored back to the system
data at the ti me of the ori gi nal upgrade procedure.
WARNING: Do not r estor e a database f r om a l ater v er -
si on of Pr oVi si on i nto an ear l i er v er si on of Pr oVi si on,
because the databases ar e not compati bl e.
614-330053-001 APRIL 2014 97

Chapter 5. Licensing ProVision
l About ProVision Licenses on page 100
l Trial Evaluation ProVision License on page 101
l Permanent Server License Application on page 102
l Licensing Procedures on page 103
614-330053-001 4/04/2014 99
CHAPTER 5. LICENSING PROVISION
About ProVision Licenses

A software license file needs to be applied to the ProVision Server to enable the soft-
ware’s capabilities. The license file mechanism supports two types of licensing; node
(or node count) licenses and feature licenses.
Node Licenses
The ProVision solution packs group node licenses into a number of packages, each
package enabling management of a specific number of devices or specific network
size.
ProVision solution packs include:
l ProVision software
l All node licenses
In general, each node count enables the system to manage a single device (or single
Network Element) with one IP address. For example a single Eclipse radio. The
exception is MegaStar and TRuepoint 6500 trunking radios. For MegaStar each SPU
(providing two STM1 channels) requires a node count of 2. For TR 6500 each MSTU
(providing one STM1 channel) requires a node count of 1.
Synergy Package
The ProVision Synergy package provides a ProVision installation with media war-
ranty and free software upgrades for 1 year. It is purchased as an add-on to the main
solution pack.
When Is A New License Required?

If you have installed ProVision with your license from Aviat Networks, and you
install an upgrade later, you do not need a new license for the upgrade.
A new license is required if you need to enable a new function with licensed cap-
ability. These functions may be added to an upgraded version. Review your product
release notes for your upgrade, and see the Featured Licenses section below.
Feature Licenses
In addition to the standard ProVision license, users can acquire feature licenses to
enable specific functions in ProVision. They can only be acquired in addition to
standard ProVision software/node licenses.
100 AVIAT NETWORKS

License Title Functions Enabled

Eclipse Circuit Pro- Enables full TDM and Ethernet circuit provisioning func-
visioning tionality for Eclipse devices. Without this license, circuit
functionality is limited to the circuit map and tree views,
circuit tracing (including identifying bundles) and end-to-
end circuit diagnostics.
Capacity Planning Enables the Ethernet Bandwidth Utilization functionality.
Enables utilization and planning values for the Eclipse
Capacity Report.
Generic Device Sup- Enables the following for SNMP-based devices: Package-
port level management, event collection, launching windows
applications, and equipment views. Without this license,
Generic Device functionality is limited to deploying gen-
eric devices. This is a per server license.
NBI via MTOSI Enables use of MTOSI NBI.
Network Health Report Enables reporting on the RF performance of the
Eclipse radios in the network.
Northbound Interface This license enables NBI-related Events, Performance,
Topology, Configuration, and Inventory.
Redundancy Controller Enables the Redundancy Controller module for managing
local/peer backup redundancy.
SAGEM-LINK Support for SAGEM-LINK microwave radios.
SNMPv3 Advanced Pri- TDES and AES128, AES192, AES256 SNMPv3 pri-
vacy vacy/encryption.
The server’ s I P address must be suppl i ed when requesti ng a

l i cense.
Trial Evaluation ProVision License

A trial evaluation license can be requested from PV-Licensing@aviatnet.com, or by
completing the License_Request_Form.txt in the ProVision release media (see the
Documentation directory). When the evaluation period is complete, to continue to
use the software, you have to obtain and install a permanent license or request
another evaluation license.
Beginning five days before the evaluation license expiries, each day the ProVision
Manager generates an event warning that the evaluation license is due to expire. The
event can be viewed in the main Event Browser or by right-clicking on the ProVision
V Manager icon and selecting Event Browser from the popup menu displayed.
Figure 5-1. License Expiry Warning Event
A critical event is generated on the day before the trial license expires. If the system
does not find an updated license file when the trial period has expired, all ProVision
614-330053-001 APRIL 2014 101

user sessions are be closed, and you cannot start a new session. The following mes-
sage displays:
Figure 5-2. Evaluation License Expiry Message
I f you are usi ng an eval uati on l i cense from a previ ous versi on
of ProVi si on, the eval uati on l i cense may or may not work wi th
the newl y i nstal l ed versi on of ProVi si on. Contact Techni cal
Support for more i nformati on.
Permanent Server License Application

Installing a permanent or extended evaluation license enables ProVision to operate
normally, beyond the 60-day license trial period. You will also receive support from
Aviat Networks. To apply for a permanent server license, see Requesting a Permanent
License on page 104.
Related Topics:
l Licensing Procedures on page 103
102 AVIAT NETWORKS

Licensing Procedures
l Determining the Server’s IP Address on page 103
l Requesting a Permanent License on page 104
l Activating a ProVision Server License on page 104
Determining the Server’s IP Address

The ProVision server’s IP address is required for the following:
l Requesting a permanent license
l Installing client software from the server
l Logging on to a ProVision client session
Procedure
To determine the server’s IP address in a Windows system:
1. On the server, select Start > Run . The Run window is displayed.
2. Type cmd in the dialog box and select OK. A command window is displayed.
3. At the prompt, type: ipconfig
The computer’s IP details are displayed.
614-330053-001 APRIL 2014 103

4. Write down the IP address.

5. Close the window. To determine the server’s IP address in a Solaris system:
6. On the server, enter the command: Internet host table
The computer’s IP details are displayed: 10.16.15.4 sun4 loghost
7. Write down the IP address.
Requesting a Permanent License

To request a permanent license:
1. On the ProVision CD, find the license.txt file.
2. Fill in the required information.
3. Email this information to licenses@aviatnet.com. A license file is sent to you via
email within three working days.
Activating a ProVision Server License

Use the license file from Aviat Networks, sent as an email attachment.
Procedure
1. Select Start > Programs > ProVision server > C:\ Command Window.
F or Wi ndows 7, 2008R2 and 8, open the Commands screen by
Adm in strator .
2. At the prompt, type pv service stop

3. Press Enter. A message is displayed indicating the ProVision server has stopped.
If a window appears with the message “Do you want to allow the following program
to make changes to this computer?” click Yes.
4. Using Windows Explorer, copy the new license.xml file to the ProVision server
folder.
104 AVIAT NETWORKS

5. To overwrite the old licence file with the permanent license, select Yes.
6. In the ProVision command window, type pv service start
7. Press Enter. A message is displayed indicating the ProVision Server has started.
8. To start the ProVision client, select Start > Programs > ProVision Client >
ProVision Client.
9. To verify the new license is running, login to ProVision and select Help > License
Details.
614-330053-001 APRIL 2014 105

106 AVIAT NETWORKS

Chapter 6. Setting Up ProVision
This section covers the main points to consider when setting up ProVision:
l Prerequisites for Setting Up ProVision on page 108
l Workflow for Setting Up ProVision on page 109
l Changing FTP Server Port on page 111
l Changing Syslog Server Port on page 112
l Configuring for Multiple Network Card Systems on page 114
l Enabling and Disabling Ethernet OAM, VLAN and ERP Ring Functionality on
page 116
l Enabling and Disabling Event Driven Clock Synchronization Discovery on
page 117 (see also: Clock Sync Report and Clock Synchronization Network
Health Report)
After the ProVision server and client PCs have been installed and configured, and the
operating system and ProVision software have been installed and licensed, you need
to set up ProVision. This section details the procedures to get ProVision running,
enabling you and the NOC operators to manage the network.
An overview of the steps for setting up ProVision is as follows:
1. Install ProVision.
2. License ProVision.
3. Set up ProVision. Determine if this installation is an upgrade.
l Yes - Import the Topology file from the previous version.
l No - Set up the Network and enter the network/radio details.
4. Set up user access and user accounts.
5. Set up device security accounts.
6. Set up the Northbound Interface.
7. Set up database purging.
8. Back up the database and export and save the Topology.
9. Deploy devices and manage ProVision as described in the ProVision User Guide.
614-330053-001 4/04/2014 107

CHAPTER 6. SETTING UP PROVISION
Prerequisites for Setting Up ProVision

This table provides details of the information required to set up ProVision.
Table 6-1. Setting Up ProVision Prerequisites
Prerequisite Description
Maps The map files required as backgrounds for the network, on the
ProVision user interface.
ProVision supports the following image formats:
jpg
gif (GIF87 and GIF89a)
You can use a search engine to find websites, which provide
maps for countries, regions, and cities that you can download
and use in ProVision.
Copy the background maps into the ProVision directory:
<pv root>\ProVisionServer\Maps
Network Topology If upgrading from ProVision 3, you can import the network topo-
logy file into ProVision.
For a new network, you must have a plan of the network
regions, sites, racks, radios, and links to be deployed and man-
aged in ProVision. This is required to set up the network in the
ProVision user interface and if required service links between
devices.
Service Topology (optional) A list of the Services (logical groupings of devices) required and
the devices that are to be included in each Service.
List of the IP addresses of the The radio’s IP address is required when deploying the radio.
radios to be deployed in the
network.
List of the ProVision users Required to add new ProVision users.
and their security group.
List of radio usernames and Applicable for XP4 radios. If a user name and password has been
passwords. physically set up in the radio, you need to know what these are
so you can enter the details into ProVision.
Northbound Interface To configure the Northbound Interface, you need the following:
- IP address of “north” computer
- Type of traps required
You also need to know if traps are to be sent and/or information
sent to an ASCII-based file on the ProVision server.
Database purging criteria You need to know how often the events and performance data
are to be deleted from the ProVision database.
108 AVIAT NETWORKS

Workflow for Setting Up ProVision

The workflow steps to set up ProVision to actively monitor and report on the radio
network are detailed in the table below. It is recommended that you proceed through
these steps in the order that they are listed.
Procedures Description Reference

Start an Admin The setting up procedures are per- ProVision User Guide, Starting a
ProVision client formed via the ProVision user interface User Session.
which is opened for a user session.
Change the For security purposes you must change ProVision User Guide, Changing Your
Admin login pass- the admin password. Password.
word
Set up network If upgrading import the network topo- ProVision Installation and Admin-
logy file from ProVision 3. istration Guide, ProVision 2.3/3.0
Topology Migration Tool on page
166
If the network contains TNET devices ProVision User Guide, Deploying a
you need to ensure the TNET proxy and TNet Device.
radio details imported into ProVision
match the details stored in the proxy.
For a new ProVision network, the order in which you set up the network is flexible
and the following is a recommendation only:
Update ports ProVision Installation and Admin-
istration Guide, Setting Up ProVi-
sion on page 107
Add network con- ProVision User Guide, Deploying and
tainers Managing Radios
Import back- ProVision User Guide, Getting Star-
ground maps ted
Deploy, link (RF Optional but implemented by most ProVision User Guide, Deploying and
and Logical users. Managing Devices
links), and man-
age devices
- Add Logical Con- Optional but implemented by most ProVision User Guide, Managing
tainers users. Events
- Create Score-
board Groups
- Set up Pre-
filters
- Create cus-
tomized Event
Browsers
614-330053-001 APRIL 2014 109

Procedures Description Reference

Set up user Required to use ProVision. Functions a ProVision Installation and Admin-
accounts user can perform are determined by istration Guide, User Account and
their security group. Access Control Procedures on page
128
Add ProVision Only required for Dart, Eclipse, and XP4 ProVision Installation and Admin-
Dart, Eclipse, and radios with security enabled, to allow istration Guide, Device Security
XP4 radio secur- access the radio’s diagnostics. Accounts on page 141
ity accounts
Add XP Web Only required for XP4 radios with secur- XP Web applications online help
security accounts ity enabled, to allow access the radio’s
diagnostics Via XP Web.
Set up North- Required when events/traps are to be ProVision Installation and Admin-
bound Interface forwarded as northbound traffic for istration Guide, Northbound Inter-
fault management, or performance face on page 279
date is required for performance data
management.
Set up database This determines how often and what is ProVision Installation and Admin-
purging purged from the database. istration Guide, Changing Database
Purging Criteria on page 190
Backup the data- After completing the ProVision set up, ProVision Installation and Admin-
base backup the database. istration Guide, Database Backup
Procedures on page 184
Export the net- Saves the network objects and hier- ProVision Installation and Admin-
work topology archy to an.xml file. istration Guide, Exporting the Topo-
logy on page 164
Load the updated Only required for networks with Eclipse ProVision User Guide, Load-
software for the radios ing/Activating New Eclipse Software
Eclipse radios
Set up any Gen- Only required for networks with Gen- ProVision Installation and Admin-
eric Devices eric Devices istration Guide, Generic Device Man-
agement on page 239 .
110 AVIAT NETWORKS

Changing FTP Server Port

These instructions describe how to change the FTP Server Port for a ProVision server
installation. The default FTP server port for the ProVision server is port 5555.
On some networks, this port is used by other backup software programs. Because of
this, you can change the ProVision FTP server port, if required.
Warnings
l Aviat Networks recommends that you only change this port value if it is
absolutely necessary.
l If any ports are changed on a Primary Server, you must also change the ports
on the connected Backup Server to match them.
l The ProVision FTP server port number must be unique: it must be different
from the port numbers used by any other FTP server operating on the same
sever.
Change Procedure
1. Stop the ProVision Server using the appropriate command (see ProVision Com-
mands on page 44).
2. Change the value of the FTP server in the server_configuration.xml file of
the ProVision server. This file is located at: ProVi-
sionServer\tomcat\webapps\ROOT\pv\templates
3. Open this file and edit the value of the FTP server port to the new port number
e.g. 5556. Specifically, change the line <port>5555</port> to <port>5556</port>,
as shown below:
<ftp>
<server>
<port>5556</port>
</ftp>
4. Save the file.
5. Restart the ProVision Server.
6. The ProVision FTP server port is now changed to the port that you assigned.
614-330053-001 APRIL 2014 111

Changing Syslog Server Port

These instructions describe how to change the Syslog Server Port for a ProVision
server installation.
The default Syslog server port for the ProVision server is port 514 . On some sys-
tems, especially Solaris, this port maybe used by other processes. Because of this,
you can change the ProVision Syslog server port, if required.
Warnings
l Aviat Networks recommends that you only change this port value if it is
absolutely necessary.
l If any ports are changed on a Primary/Active Server, you must also change the
ports on the connected Standby/Dormant Server to match them. See About the
l The ProVision Syslog server port number must be unique: it must be different
from the port numbers used by any other Syslog server operating on the same
server.
Procedure
1. Stop the ProVision Server using the ./pv_service stop command. See ProVi-
sion Commands on page 44.
2. Change the value of the Syslog server in the server_configuration.xml file of
the ProVision server. This file is located at: ProVi-
sionServer\tomcat\webapps\ROOT\pv\templates
3. Open this file and edit the value of the Syslog server port to the new port number,
such as 5140. Specifically, change the line <trap_syslog_port>514</trap_sys-
log_port> to <trap_syslog_port>5140</trap_syslog_port> as shown
below:
<snmp>
<timeout>10</timeout>
<retry>1< <trap_syslog_port>5140</trap_syslog_port>
<trap_ingress_port>162</trap_ingress_port>/retry>


</snmp>
4. Save the file.
112 AVIAT NETWORKS


6. The ProVision Syslog server port is now changed to the port that you assigned.
614-330053-001 APRIL 2014 113

Configuring for Multiple Network Card

Systems
If you are installing ProVision for use with a system that has multiple network cards
installed, you need to make changes to the SNMP server interface and/or the Client
interface.
Server Interface
When multiple network interface cards are used, the network interface for SNMP
interfacing may need to be defined as a using a specific network interface, normally
the interface facing the radio network.
Procedure for Server Interface Definition

1. Stop the ProVision server using the appropriate command (seeProVision
2. Edit the server_configuration.xml file of the ProVision server. This file is
located at: ProVisionServer\tomcat\webapps\ROOT\pv\templates
3. Open this file and add the value:
<interface>a.b.c.d</interface>
After the lines:

Where a.b.c.d is the IP address of the network interface facing the radio network.
4. Save the file.
5. Edit the server_configuration.xml file of the ProVision server. This file
is located at:
ProVisionServer\tomcat\webapps\ROOT\pv\templates
6. Restart the ProVision server.
Client Interface
When multiple network interface cards are used, the network interface used for Cli-
ent interface may need to be defined as a using a specific network interface, normally
the interface facing the ProVision clients.
114 AVIAT NETWORKS

Procedure for Client Interface Definition

1. Stop the ProVision server using the appropriate command (see ProVision Com-
mands).
2. Edit the server_configuration.xml file of the ProVision server. This file is located
at: ProVisionServer\tomcat\webapps\ROOT\pv\templates
3. Open this file and add the value:
<client_interface>a.b.c.d</client_interface>
After the lines


Where a.b.c.d is the IP address of the network interface facing the ProVision clients.
4. Save the file.
614-330053-001 APRIL 2014 115

Enabling and Disabling Ethernet OAM,

VLAN and ERP Ring Functionality
ProVision Ethernet OAM Management, VLAN Management and ERP Ring Man-
agement functionality is disabled by default. To enable these functions, use this pro-
cedure.
When they are disabled:
l VLAN and EOAM tabs do not display in the ProVision screens.
l EOAM and ERPS menu items do not display in the ProVision menus.
l ProVision does not discover VLAN and EOAM configuration.
l Previously discovered VLAN, EOAM and related port information is deleted
from the database.
l In the Clock Synchronization and Custom Reports, the check box Include ports
is removed.
See the ProVi si on Customer Rel ease Notes for the recom-
mended maxi mum network si ze.
I f there i s a Redundant Server depl oyment for network secur-
i ty, Ethernet OAM, VLAN and ERP Ri ng functi onal i ty must be
enabl ed on both the pri mary and the redundant server. The
server confi gurati on fi l e i s not repl i cated across the acti ve
and dormant servers i n a Redundant Server depl oyment sys-
tem. See Red u nd ant Serv er Dep loy ment s on p age 203.
Procedure
1. Stop the ProVision server using the appropriate command (see ProVision
2. Open the server_configuration.xml file for editing. This file is located
at: ProVisionServer\tomcat\webapps\ROOT\pv\templates.
3. To enable this functionality change <monitor>FALSE</monitor> to
<monitor>TRUE</monitor> in the <eoam> </eoam> section.
4. To disable this functionality change <monitor>TRUE</monitor> to
<monitor>FALSE</monitor> in the <eoam> </eoam> section.
5. Save the file and restart the ProVision server.
6. Ethernet OAM Management, VLAN Management and ERP Ring
Management functionality is now enabled or disabled.
116 AVIAT NETWORKS

Enabling and Disabling Event Driven

Clock Synchronization Discovery
Event Driven Clock Synchronization Discovery is Disabled (false) by default, res-
ulting in tracing taking place every 12 hours through polling only.
When enabled, Clock Synchronization Discovery will be triggered every time clock
source is switched. A large number of clock switching events raised such as "SyncE
clock source changed," will result in continuous tracing of the network distribution,
preventing other ProVision processes from running.
To enable or disable Event Driven Clock Synchronization Discovery use the following
procedure.
Procedure
1. Stop the ProVision server using the appropriate command (see ProVision
2. Open the server_configuration.xml file for editing. This file is located
at:ProVisionServer\tomcat\webapps\ROOT\pv\templates.
3. To enable this functionality change <clock_sync_event_
driven>false</clock_sync_event_driven> to <clock_sync_event_
driven>true</clock_sync_event_driven> in the <eoam> </eoam>
section.
4. To disable this functionality change <clock_sync_event_
driven>true</clock_sync_event_driven> to <clock_sync_event_
driven>false</clock_sync_event_driven> in the <eoam> </eoam>
section.
5. Save the file and restart the ProVision server.
6. Event Driven Clock Synchronization Discovery functionality is now enabled
or disabled.
See al so: C lock Sy nc Rep ort and C lock Sy nchronizat ion Net work
Healt h Rep ort .
614-330053-001 APRIL 2014 117

Chapter 7. Access Control
l Introduction to Access Control on page 120
l ProVision User Security Profiles on page 124
l User Account and Access Control Procedures on page 128
614-330053-001 4/04/2014 119

CHAPTER 7. ACCESS CONTROL
Introduction to Access Control

Access control can be used to:
l Add users
l Change a user’s security group
l Change a user details or password
l Delete users
l Lock users from the application
l Add radio security
ProVision User Access

Security groups control access to ProVision functions. A security group defines the
group of functions to which a user has access.
At least one Administrator user must exist at all times. Part of an administrator’s
role is to create ProVision user accounts and associate each account with at least one
security group. The user account inherits the access control defined by the security
groups to which it belongs. A user account can belong to different security groups,
and these groups control their access to the ProVision functions.
Before a user can start ProVision, they must have a username and password. When
the user logs in, ProVision validates the username and password before starting the
ProVision interface.
A security log records user activities such as logging in, logging out and changing
passwords. Only the administrator has access to the security log.
Device Security Access

The requi rement for radi os to have username and password
access enabl ed i s determi ned by your company‘ s securi ty
pol i cy requi rements.
ProVision enables users to view device security accounts for all devices. Some devices
can have their security edited as follows:
l Eclipse devices can be set with two sets of passwords so that Portal Engineer
users and NOC Operator users have separate access, even within the same
device.
l XP4 and DART devices can be set with passwords.
l Username and password combinations can be set for individuals or groups of
devices, if the groups of radios are of the same type. (For example, a group of
Eclipse radios can all have the same username and password.)
l TRuepoint 4040 and 5000 radios, and Generic Devices, can have their SNMP
security and associated passwords changed.
120 AVIAT NETWORKS

For more details, see Device Security Accounts on page 141.
614-330053-001 APRIL 2014 121

Single Sign On and Strong Security

About Single Sign On for Strong Security
To facilitate Strong Security for devices, ProVision notes the users' security levels
when they log in. This is called a Single Sign On (SSO) mechanism. These SSO cre-
dentials enable the user to log in automatically to Eclipse Portal, Configuration
Backups, and Software Loading at the appropriate level.
The default configuration encryption password that is used during configuration
backup when strong security is enabled is ProVision.
SSO credenti al s are encrypted and onl y saved duri ng the
ProVi si on sessi on; they are del eted when the user l ogs out.
Al so, for Ecl i pse Portal , SSO i s onl y acti ve for devi ces wi th
Ecl i pse 5.3 and l ater i nstal l ed: devi ces wi th earl i er versi ons
need to be managed as devi ce securi ty accounts. See Dev ice
Secu rit y Accou nt s on p age 14 1.
SSO Authentication Matrix

The table below shows the different radio firmware and configurations and which cre-
dentials SSO will use when authenticating for specific operations.
F or al l i tems marked wi th * the Ecl i pse embedded system has
2 defaul t user accounts, NOC Operator and NOC Engi neer;
passwords for these user accounts can be stored i n ProVi si on
and wi l l be used for authenti cati on for non-PV AAA Server
enabl ed devi ces. Al so, al l fai l ed l ogi ns rai se a fai l ure event i n
ProVi si on.
Table 7-1. SSO Credentials for ProVision Authentication with Eclipse
122 AVIAT NETWORKS

Function No Security Firmware Basic Secur- Strong Secur- RADIUS Enabled

Enabled versions ity ity Enabled in ProVision
(All Eclipse <5.3
(No RADIUS) (with or without
firmware
Strong Security)
versions)
Portal Login N/A Locally Locally stored Locally stored Standard ProVision
stored radio credentials if credentials if user credentials. If
security defined.* defined.* fails, Portal login
accounts* If there are If there are screen displays.
none, standard none, standard
ProVision user ProVision user
credentials are credentials are
used. If fails, used. If fails,
Portal login Portal login
screen displays. screen displays.
Software N/A N/A Locally stored Locally stored Standard ProVision
Loading credentials if credentials if user credentials.
defined.* defined.*
If there are If there are
used. used.
Con- N/A N/A Locally stored Locally stored Standard ProVision
figuration credentials if credentials if user credentials.
Restore defined.* defined.*
If there are If there are
used. If fails, a used. If fails, a
message dis- message dis-
plays. plays.
Con- N/A N/A Locally stored Locally stored Use the locally
figuration device cre- device cre- stored “Authentic-
Backup dentials if dentials if ated Background
defined.* defined.* Task Credentials”
encrypted and
store in the ProVi-
sion database.
614-330053-001 APRIL 2014 123

ProVision User Security Profiles

The table below describes the ProVision security profiles and the function access
levels associated with each profile . See Setting Eclipse Device Security Values on
page 143 for instructions on specific device security, and Creating ProVision User
Accounts on page 128 for instructions on assigning security profiles to users.
l RW = Read/write access
l RO = Read-only access
l Full = Function is normally read-only
l ‘--’ = No access
Table 7-2. Security Profiles and Function Access Levels
Function View Maintenance Configuration Upgrade Admin Security

Administer - - RW - - RW
Device Security
Accounts
Administer - - - - RW -
ProVision Secur-
ity Accounts
Administer - - - - - RW
RADIUS Secur-
ity
Application FULL FULL FULL FULL FULL FULL
Launch / Con-
figure
Bandwidth Util- FULL FULL FULL FULL - -
ization
Circuit View FULL FULL FULL FULL - -
Circuit Data Col- - - RW - - -
lection
Circuit Diagnostics - RW RO - - -
Circuit Renaming - - RW - - -
Collection Prefer- - - RW - - -
ences
Commissioning / - - RW - - -
Decommissioning
Delete Circuits - - RW - - -
Provisioning - - RW - - -
Client Sub- RW RW RW RW RW RW
scription
124 AVIAT NETWORKS


Clock Sync Dia- FULL FULL FULL - FULL -
gnostics
Configuration - - RW - - -
Profiles
Configure NBI RO RO RW RO RW -
(All NBI)
Configure FULL FULL FULL FULL - -
Viewer
Craft Tool RO RW RW RW - -
Launch
Database - - RW - RW RW
Backup –
Manual
Database - - - - RW -
Backup – Sched-
uled
Database Pur- - - RO RO RW -
ging
Deploy Device - - RW - - -
Device Con- - - RW - - -
figuration
Backup
Device Con- - - RW - - -
figuration
Restore
Device Dia- RO RW RO - - -
gnostics
Device Main- RO RW RW RW - -
tenance
Eclipse License - - RW RW - -
Loading
Eclipse Portal RO RW RW RW - -
access – Using
local NOC Engin-
eer credentials
Eclipse Portal RO RO RO RO - -
access – Using
local NOC Oper-
ator credentials
Eclipse Portal - - - - RW -
Locking –
Feature
Enabling
Email Con- - - - - RW -
figuration
614-330053-001 APRIL 2014 125


Event Browser / FULL FULL FULL FULL FULL FULL
Scoreboards
Clear Events - RW RW - - -
Acknowledged RW RW RW RW - -
Events
Event Noti- RO RO RW RO RO RO
fication
Event Pre-Filter RO RO RW - - -
ERP Pro- - - RW - - -
visioning
EOAM Dia- RO RW RW - - -
gnostics and Pro-
visioning
Generic Device - - RW - - -
Management –
Package Man-
agement
Help FULL FULL FULL FULL FULL FULL
Logical Con- RO RO RW RO RO RO
tainers
Manage / - - RW - - -
Unmanage
Map view RO RO RW RO RO RO
(Unlock,
/Change Back-
ground)
Network Auto - - RW - - -
Discovery
Notification RW RW RW RW RW RW
Preferences
Object Man- - - RW - - -
agement
(Deploy, Delete,
Rename, Repar-
ent, Link)
Performance RO RW RW RO - -
Collection –
Enable / Disable
Performance his- RW RW RW - - -
tory, trends,
reports
Performance RO RO RW RO - -
Thresholds
Reports FULL FULL FULL FULL FULL FULL
126 AVIAT NETWORKS


Deleting Server - - RW - - -
Reports
Search Object FULL FULL FULL FULL - -
Security Log - - - - - RW
Server Redund- - - - - RW -
ancy
Sleep / Wake RO RW RW RW - -
Software Load- - - - RW - -
ing
Software Load- - - - RW - -
ing Preferences
Software Table RO RO RO RW - -
Task Man- RO RO RW RW
agement
(SW Tasks
Only)
Topology Export FULL FULL FULL FULL - -
Topology Import - - RW - - -
View / Modify RO RO RW RO - -
IP Addresses
View / Modify RW RW RW RW RW RW
Own Security
Details / Pass-
word
VLAN Man- FULL FULL FULL - - -
agement
614-330053-001 APRIL 2014 127

User Account and Access Control

Procedures
l Creating ProVision User Accounts on page 128
l Single Sign On and Strong Security on page 122
l Changing a ProVision User Account on page 132
l Deleting a ProVision User Account on page 134
l Viewing the Security Log on page 140
l Device Security Accounts on page 141
l Clearing Device Security Accounts on page 152
Access Control Prerequisites

For ProVision, the following prerequisites and dependencies must be in place before
you can set up access control.
l ProVision must be installed and running.
l You need to log in with an administrator-level user name and password. Only
administrator-level users can update user accounts and access control.
l You must have user names and passwords for ProVision users. To set up
access control for each user, you must have the following information:
l User Name
l Contact Details
l Default password
l If required, you must have any specific radio security user names and
passwords.
Creating ProVision User Accounts

Each ProVision user must be assigned a user account. A user account includes:
l Unique login user name and password
l Region Access control defines which regions and devices in the network the
user can see and edit. If no values are set, the user has access to ALL regions
and devices in the network.
128 AVIAT NETWORKS

l User security profiles. A user can belong to more than one security profile.
In addition, this is a useful location to store phone numbers and email
address information for a user.
Administrator level users can manage the requirements for ProVision passwords
using the security_policy template in the ProVision Server program files. In this tem-
plate, the administrator can change the values to customize password and user
name requirements.
CAUTION:Only a user with the Administrator profile enabled enabled
can make changes to user accounts.
The fi rst user avai l abl e i mmedi atel y after i nstal l ati on i s the
defaul t admi ni strator; al l other users need to be created.
When the defaul t admi ni strator fi rst l ogs i n, onl y Admi n-
i strati on functi ons are enabl ed for them; further functi ons
need to be added usi ng the fol l owi ng procedure.
Procedure
1. Select Administration > ProVision User Accounts. The ProVision User
Accounts window displays, with the status of each user account.
2. Select Create. The Create User window is displayed. In the General tab, enter
the user details:
614-330053-001 APRIL 2014 129

l User Name - First and last name of the user. This value is case-sensitive.
l Email Address - Email address of the user.
l Session Timeout - If this user is logged in without any activity for this
amount of minutes, they will be logged out automatically. Only
Administrator-level users can set this value.
l Maximum Password Age - Sets the maximum age in days of the password
for this user. When this value is used, user is notified that their password is
nearly expired or expired, and is prompted to reset the password.
l Maximum Sessions - The maximum number of ProVision Client sessions
this user can have open at one time.
l Contact Details - Additional contact details, including phone numbers,
location addresses, and Skype or other communication IDs.
l Suppress Email Notifications - Check this box if this user should never
receive email notifications about events.
3. Select the Security Profiles tab.
4. Select checkboxes to enable ProVision functions for this user. Options are defined
below.
5. Select OK. Then click on the Regional Access tab.
130 AVIAT NETWORKS

6. Select check boxes to enable this user to access specific regions and devices within
the network. Then, click OK.
I f no val ues are set, the user has access to ALL regi ons and
devi ces i n the network.
7. Click the Change Password button. The Change Password window is displayed.
8. Type a password in the New Password field.

9. Re-type the password in the Confirm New Password field. Select OK.
10. To close the ProVision User Accounts window, select Close.
The ori gi nal ' admi n' user can be del eted, but there must
al ways be at l east one user wi th Admi ni strati on functi ons
enabl ed.
Table 7-3. Security Profile Values
Security Pro-
Functions
file
View User can view data in ProVision. This does not enable any data edit-
ing.
Maintenance User can view data and set maintenance controls on devices.
Con- User can view data and change device / ProVision configuration
figuration parameters. Does not include security, administration, or software
loading privileges.
Upgrade User can view data and perform software upgrades on the net-
work.
Admin- User can view data and perform database administration and ProVi-
istration sion user account administration tasks. A default administration
user will be created by the system when ProVision is first installed.
NOTE: At least one Administration user must ALWAYS exist and
be unlocked at all times.
Security The security user is only responsible for configuring and enabling
the information needed to integrate with a RADIUS server and to
view Security logs.
To help users of previous versions of ProVision, below is a table comparing the new
Security Profile values with previous user levels.
Table 7-4. Current and Past ProVision User Security Comparison
614-330053-001 APRIL 2014 131

Past User
Security Profile Comments
Level
View NOC Operator A very limited access level, “read only” access
to devices and the ProVision database ability to
generate reports.
Maintenance Portal Engineer View-only + Ability to set maintenance con-
trols on devices.
Configuration NOC Engineer View-only + Ability to change device / ProVi-
Administrator sion configuration parameters except security
/ administration parameters. Similar to past
NOC Engineer excluding software loading priv-
ileges.
Upgrade NOC Engineer View-only + Ability to perform software
Administrator upgrades on the network. Similar to the soft-
ware loading privileges of the past NOC Engin-
eer user level.
Administration Administrator View-only + Access is limited to database
administration and ProVision user account
administration tasks.
Security Administrator A default user “security” will be created when
the system is first installed. The security user
is only responsible for configuring and enabling
the information needed to integrate with the
RADIUS server.
Changing a ProVision User Account

The following items can be changed in a user account:
l Contact Details - user’s details change.
l Password - user cannot remember password or it is known to other users.
l Lock/Unlock the Account - person on holiday or temporarily away
l Change the Regional Access and/or security profiles - user promoted or
requires greater functionality.
You can also export a list of all users as a .CSV file.
Procedure
Accounts window displays.
132 AVIAT NETWORKS

2. Highlight the user whose details you want to view/change.

3. Select Properties. The User Properties window is displayed.
Data Change Procedure

General details Select the General tab and make the required changes.
Password Select Change Password.
In the Change Password dialog box, type the new password

and then reconfirm by typing it again.
To save the new password and exit the dialog box, select
OK.
Account Status Select the required status, locked or unlocked, from the
Status drop down menu. Only Administrators have access to
locked or unlock user accounts.
Regional Access Select the required regions and/or devices in the regions by
clicking on the check boxes.
You can apply one user's Regional Access settings to other
users via the Apply to Other Users button.
614-330053-001 APRIL 2014 133

Data Change Procedure

Security Profiles Select the Security Profiles tab and make the required
changes.
4. To export the list of all users as a .CSV file, click the Export Users button. Save
the file in the desired network location.
5. To close the User Properties window, select OK.
6. To exit the ProVision User Accounts window, select Close.
Deleting a ProVision User Account

If a user is no longer using ProVision, you can delete the user’s account.
Procedure
Accounts window is displayed.
2. Highlight the user you want to delete.
3. Select Delete. The user is deleted from the system and from the User Accounts
window.
4. To exit, select Close.
134 AVIAT NETWORKS

Changing Security Login Policies

Administrators can access a file that enables them to change ProVision login
policies. This file, security_policy.xml, is in the ProVisionServer directory.
From this file, administrators can edit:
l Minimum password length
l Minimum user name length
l Requiring passwords to have capital letters, alphanumeric characters, or
special characters (such as punctuation)
l The number of log in retries allowed (for example, 3)
l A log in welcome message
l A password policy message
Procedure
1. Before you make changes to the security policy, stop the ProVision Server
using the appropriate command (see ProVision Commands on page 44).
2. The security_policy.xml file is at the file location:
\ProVisionServer\tomcat\webapps\ROOT\pv\templates
2. Navigate to it using the Command line or Windows Explorer. Open the file
using an XML editor or NotePad.
3. Make the changes for the login policies, as described in the table below.
4. Save and close the file.
5. The login policies will be applied for all users of this ProVision installation.
Policy Value in XML file
Password length <password>
<length min='# max='#/>
User name length <username>
<length min='#' max='#'/>
Password text require- <required-characters chars='_#-=' num='YES/NO' caps-
ments s='YES/NO'/>
# of retries allowed <login retries='#'/>
614-330053-001 APRIL 2014 135

Policy Value in XML file

Welcome message Edit this text as required between the <html> tags. An
example is provided below.

Password policy mes- Edit this text as required between the <html> tags. An
sage example is provided below.
<policymessage>
<![CDATA[<html>The password or username does not
meet the security policy for this sys-
tem. Passwords must be # to # characters
long and contain a number, capital letter at least
one character of '_#-='. Usernames must be
# to #characters long and contain no spaces.</htm-
l>></policymessage>
136 AVIAT NETWORKS

Managing User Sessions

ProVision Administrators can manage the logged in sessions of other ProVision
users. Administrators can log out other users. This improves security and enables bet-
ter use of system resources.
It also provides options for managing users when Administrators change regional
access control. Administrators now have the option of logging out users whose
regional access control is affected by region changes; logging users out enables the
regional access changes of the logged out user. See Changing a ProVision User
Account on page 132 for more information.
Procedure
1. In the Administrator menu, select Session Manager.
2. The Session Manager screen displays. It includes:
l User = User names
l IP Address = IP address where user is logged in
l Login Time = Time when user logged in
l Latency = speed of access, the speed is accurate to the nearest millisecond
3. To log out a user, select them and click Terminate.

4. A confirmation message displays:
5. You have two termination options. Click the one that you require:
l Terminate and Lock User = Terminates the user's client session and also locks
them out of ProVision until the administrator restores access.
614-330053-001 APRIL 2014 137

l Terminate = Terminates the user's client session.

6. The user is terminated using the option you have selected.
7. If a user is being logged out by the administrator, this message appears in
their ProVision Client screen:
8. If a user is being logged out by the administrator due to a regional access

change, this message appears in their ProVision Client screen:
Locking Eclipse Portal Write Access from

ProVision
Introduction
From ProVision, Administrator level users can lock and unlock Eclipse Portal at the
network level. Locking Eclipse Portal means that only ProVision users with write
access can unlock access to Portal, giving local Portal users configuration access.
Eclipse Portal Access write locking only locks Portal for Eclipse
devices that have Eclipse software version 5.1 or higher.
Procedure
1. Log into ProVision as an administrator.
2. Select Administration > Eclipse Portal Locking. The Eclipse Portal Locking
screen displays.
138 AVIAT NETWORKS

3. To enable the Portal Lock feature, check the check box. This locks Eclipse
Portal for all Eclipse devices that have software 5.1 or higher. Then, click Re-
Apply.
4. To disable the Portal Lock feature, uncheck the box.
5. To unlock Eclipse Portal for specific Eclipse devices, go to the device in the
Tree Viewer. Right-click on the device. In the right-click menu, go to the
Sleep option. You can click on a check box to enable Portal Write Access. This
enables the write access for this Eclipse device only.
6. To check on the Eclipse Portal locking status for an individual device, mouse
over it and read the mouse-over tooltip. This tooltip includes the name of
the user who locked Portal. To check on the Eclipse Portal locking status for
all devices, go to the Fault menu and select Device Maintenance. This screen
shows the Eclipse Portal Locking status for all devices.
Eclipse Portal Locking status options are:

l Locked - Device has Eclipse Portal Locking active.
l Lock Failed - This device can be locked but the most recent lock attempt
failed. ProVision will automatically try to relock it every 30 minutes.
l Unlocked - Device has Portal write access for users.
l Unlock Failed - This device can be unlocked but the most recent unlock
attempt failed.
l Unsupported -This device has a version of Eclipse software earlier than 5.1
and cannot have its Eclipse Portal access locked.
l N/A - Not Applicable (i.e., non Eclipse devices in maintenance mode).
614-330053-001 APRIL 2014 139

I f the ProVi si on server i s shut down and restarted, i f the

restart takes pl ace wi thi n 1 hour (60 mi nutes) the Portal Lock-
i ng feature stays on and enabl ed. I f the restart takes more
than 60 mi nutes, the Portal Locki ng feature stays on, but al l
radi os go to Unl ocked status.
Engi neers may try to reboot Ecl i pse devi ces to unl ock them
for ProVi si on and Portal . To prevent thi s, set up a rel ated Con-
fi gurati on Profi l e, Ec lips e Por ta l Loc k out R e boot . Set a l ong
reboot l ockout ti me, to ensure that ProVi si on mai ntai ns
access control of Ecl i pse devi ces fol l owi ng a reboot. To
enabl e thi s, go to the C onfigur a tion menu, sel ect C onfigur a tion
Pr ofile s , and i n the C onfigur a tion Pr ofile screen, sel ect Ec lips e
Por ta l Loc k out R e boot .
Viewing the Security Log

The security log enables you to review ProVision user activities that generate normal
and informational ProVision events.
The security log is displayed in an event browser window. You can change and save,
the filter settings and browser options.
Procedure
1. Right-click the ProVision Manager icon .
2. Select Security Log from the popup menu displayed. The Security Log window is
displayed.
140 AVIAT NETWORKS

Device Security Accounts

Administrator-level ProVision users can view security access details for all Con-
tainers and devices in a ProVision network, using the Device Security Accounts
screen.
All Containers and many devices can have their security details edited from this
screen. This table describes which devices, of specific SNMP and device-specific secur-
ity types, can be edited:
Table 7-5. Devices by SNMP Security Type and Editing Level
SNMP Security Type and Devices

Editing Level
v1, edit community string - Aurora
only (SNMP) - Constellation
- DVM, all types
- Memotec CX-U
v2c, edit community string - CTR 8540
only (SNMP) - DVA
- MicroStar I, II, and III
- TRuepoint 6400, 6500, 4040
v2c, edit device login - Eclipse, all types
(user name and pass- - DART
word) - SAGEMs, all types
- XP4
- CTR 8540
614-330053-001 APRIL 2014 141

SNMP Security Type and Devices

Editing Level
v2c or v3, edit SNMP type - Eclipse, all types
- TRuepoint 4040, 5000 and 5000 2+0
v1, v2c, or v3, edit SNMP - Generic Devices
type
You can set up device security access accounts on a network per region, site, or indi-
vidual radio basis.
This section describes how to view and edit security accounts for devices:
l Editing SNMP Community Strings on page 142
l Setting Eclipse Device Security Values on page 143Setting Eclipse Device
Security Values on page 143
l Setting Device Security Account Values on page 148
l Setting SNMPv3 Security Access on page 149
l Device Security Access for Multiple Radios on page 151
l Clearing Device Security Accounts on page 152
Editing SNMP Community Strings

From the Device Security Accounts screen, you can set or edit device SNMP security
strings. This is only required if you have made other security changes for a radio;
these strings are normally set during deployment.
Procedure
To set or edit device SNMP security strings from the Device Security Accounts screen:
1. Obtain the required user names and passwords for the Select Administration >
Device Security Accounts. The Device Security Accounts screen displays.
2. Right-click the required device and select Edit Account Information.
3. The Edit Account Information screen displays:
142 AVIAT NETWORKS

4. Reset the Read Community and Write Community levels to Private or Public.
5. Click OK.
6. The SNMP community strings are reset.
7. To remove the SNMP community string settings, right-click the device and select
Remove SNMP Community.
8. Select OK to close the Device Security Accounts window.
Setting Eclipse Device Security Values

Eclipse radios can be set up to require a user name and password to access the
radio’s diagnostic function. An administrator must set up the access account, with a
user name and password. This can be done in ProVision, from the Device Security
Accounts screen.
For an Eclipse radio, the user name and password set up in ProVision must match
those stored in the radio. After this is done, when a ProVision user selects an Eclipse
diagnostics or configuration viewer, ProVision automatically sends the username
and password to the device. Then, the device verifies the data is valid, and allows
ProVision access to its diagnostic functions. Without a valid password, the radio
ignores write data commands.
Ecl i pse radi os can be set so that “Portal Engi neer” users and
“NOC Operator” users have separate access -- even wi thi n the
same radi o. See the speci fi c i nstructi ons bel ow to Up d at e Pass-
word s for Mu lt ip le Rad io Accou nt s on p age 14 6 .
Setting Eclipse Security Accounts

1. Obtain the required user names and passwords for the Eclipse radios. For default
Eclipse passwords, see Configuring User Name and Password in the Portal doc-
umentation.
2. Select Administration > Device Security Accounts. The Device Security
Accounts screen displays.
3. Right-click the required radio and select Edit Account Information .
614-330053-001 APRIL 2014 143

5. To set the access for users with Engineer level security access, enter and retype the
password in the Engineer Account section.
6. To set the access for users with NOC Operator security access, enter and retype
the password in the Operator Account section.
7. Click OK.
8. A Login icon appears in the Eclipse Login column.
Place the cursor over the icon to view how the security accounts are configured.
9. To remove login information only, right-click the device and select Remove
Eclipse Login . The login data is deleted, and the Login icon is removed.
144 AVIAT NETWORKS

The user name and password entered i n ProVi si on for an i ndi -

vi dual radi o overri des any other user name and password set
at a hi gher l evel i n ProVi si on, for exampl e, a regi on.
Set Up Multiple Eclipse Radio Accounts

The Eclipse Radio Accounts Configuration Profile is the fastest way to add new
users into the radios' security accounts. Using a previously saved configuration pro-
file, the administration user can add the new user and sync all Eclipse radios in the
network (or part of the network) with this account.
With the addition of the Eclipse Radio Accounts Configuration profile, the user can
define a single set of credentials (up to a maximum of 40) that can be written into a
group of network elements or the entire network. This enables the system admin-
istrator to update user credentials consistently across the network in a single action,
ensuring that the credentials are the same for all Eclipse radios in the network.
Thi s feature onl y appl i es to l ocal securi ty accounts that are
stored on the Ecl i pse radi o i tsel f.
Prerequisites:
l The ProVision user performing this operation must have Administration
privileges.
l The ProVision Eclipse Login admin credentials must be defined for each
Eclipse device in the network (seeDevice Security Accounts on page 141 ). This
can be set on a Container if the credentials are to be used for all Eclipse within
the container.
l An admin user must exist in the Eclipse radio. The admin user is a default
user account that always exists in the Eclipse radio.
l Ensure that firewall settings are correct between ProVision and Eclipse.
I f RADI US i s enabl ed i n ProVi si on then the ProVi si on user cre-
denti al s (of the currentl y l ogged i n user) are used to l og i nto
the Ecl i pse NOT the Devi ce Securi ty Account credenti al s. I n
thi s scenari o the ProVi si on user must al l have RADI US cre-
denti al s defi ned to access the radi o (Ecl i pse-Radi o-User_Per-
mi ssi on=Admi ni strati on) a wel l as the correct ProVi si on
credenti al s (ProVi si on-Securi ty-Profi l e=Admi ni strati on + Con-
fi gurati on). See Enabling a RADIUS Serv er on p age 154 for more
detai l s.
Instructions
1. Ensure that the correct ProVision and Eclipse user privileges are configured.
2. Select the radios that are to be updated with the new user account. To update the
entire network select the ProVision Physical Root from the Physical View. Right-click
and select Configuration > Profiles, then go to the Profile drop-down menu and
select the Eclipse Radio Accounts profile. If a previous Eclipse Radio Account pro-
file has been saved, it displays and can be selected:
614-330053-001 APRIL 2014 145

3. Add the new user to the profile, as described in Configuration Profile Settings for
Bulk Configuration. Values are:
l User Name - Between 4 and 32 characters
l Password - Between 8 and 32 characters, including at least one letter and
one number.
l Confirmation - Retype the Password. Enter this information for each user.
l Permissions - Check the boxes for the user's permission levels for Eclipse
radios: Read Only, Engineer, Admin, Crypto. At least one Permission must be
selected for a user.
4. Save the configuration profile.
5. Select Execute to write the changes into each of the selected devices. A dialog will
appear verifying the radios that this profile will be written to. If necessary radios can
be removed from this list. Click Execute again to complete the operation.
6. Optional: to write the changes to other radios or the entire network of Eclipse
radios, select a container or the radios to write this configuration to from the Phys-
ical network view. Then right-click and select Configuration > Profiles. From the
Configuration Profile dialog select the previously saved profile and then press
Execute.
Any changes to the user account defi ni ti ons must be made to
the previ ousl y saved Eclipse Radio Accou n ts P rofile . The
Eclipse Radio Accou n ts P rofile can then be re-appl i ed to the
radi os.
WARNING: If ther e ar e pr obl ems appl y i ng the Pr of i l e
to the r adi os, check the f ol l owi ng: Hav e user cr e-
denti al s been enter ed cor r ectl y f or thi s dev i ce? See
the Edi t Account Inf or mati on scr een descr i bed i n the
Standar d Pr ocedur e ear l i er i n thi s secti on. What secur -
i ty mode i s enabl ed i n the r adi o (None, Basi c, Str ong?)
Is RADIUS authenti cati on bei ng used? Sing le Sig n On
and St rong Securit y on pag e 1 22
Update Passwords for Multiple Radio Accounts

The security policy of many organizations requires periodic changes to user pass-
words. The administrator can update the passwords of an entire Eclipse network if
user permissions are managed via the Eclipse Radio Accounts in the Configuration
Profile.
146 AVIAT NETWORKS

Instructions
1. Ensure that the correct ProVision and Eclipse user privileges are configured.
2. Select the radios that are to be updated with the new user account. To update the
entire network select the ProVision Physical Root from the Physical View. Right-click
and select Configuration > Profiles, then go to the Profile drop-down menu and
select the Eclipse Radio Accounts profile. If a previous Eclipse Radio Account pro-
file has been saved, it displays and can be selected:
3. Add the new user to the profile, as described in Configuration Profile Settings for
Bulk Configuration. Values are:
4. Update the passwords and users as required. The password must be between 8
and 32 characters, including at least one letter and one number. To delete a user,
delete text from the User Name field, or overwrite the text with a new user name.
5. When you are done making changes, click Save. Then, to write the changes to the
radios, click Execute.
6. A dialog will appear verifying the radios that this profile will be written to, if
necessary radios can be removed from this list. Press Execute again to complete the
operation.
7. Optional: to write the changes to other radios or the entire network of Eclipse
radios, select a container or the radios to write this configuration to from the Phys-
ical network view. Then right-click and select Configuration > Profiles. From the
Configuration Profile dialog select the previously saved profile and then press
Execute.
Set Up NOC Operators with Read Only Portal Access

This procedure requires setting up the NOC Operator password in Portal, then link-
ing the ProVision NOC Operator access to the Portal access. In Portal, the Operator
security level is read-only; by setting up ProVision to access Portal for NOC Oper-
ators using the Portal Operator login, the NOC Operator access to Portal is also read-
only.
1. Log into Portal at the Administrator level. Set the Operator password, using the
instructions in the Portal documentation for the topic Configuring User Name and
Password.
2. Log into ProVision. Select Administration > Device Security Accounts. The
Device Security Accounts screen displays.
614-330053-001 APRIL 2014 147

3. Right-click the required radio and select Edit Account Information . The Edit
Account Information screen displays.
4. To set the access for users with NOC Operator security access, enter and retype
the Eclipse Operator user name and password in the Operator Account section.
5. Click OK.
6. The security setting is saved in ProVision. When any NOC Operator opens Portal
from ProVision, Portal will open with read-only access.
Setting Device Security Account Values

To set or edit device security access for CTR 8540, XP4, SAGEM, and DART radios:
1. Obtain the required user names and passwords for the devices.
5. Enter the values for:

l Username
l Password
l Confirmation (re-enter the password here)
6. Click OK.
7. A Login icon appears in the Device Login column.
148 AVIAT NETWORKS

8. To remove login information only, right-click the device and select Remove
Device Login . The login data is deleted, and the Login icon is removed.
The user name and password entered i n ProVi si on for an i ndi -
vi dual radi o overri des any other user name and password set
at a hi gher l evel i n ProVi si on, for exampl e, a regi on.
Setting SNMPv3 Security Access

For Eclipse devices, for TRuepoint 4040 v2 and 5000 devices with SNMPv3 con-
trollers, and for Generic Devices, you can implement strong security. This includes
authentication and privacy algorithms. This can be done when the device is
deployed, or from the Device Security Accounts screen.
For a TRuepoint radio, the authentication and privacy information set up in ProVi-
sion must match those stored in the radio.
After this is done, when a ProVision user selects a diagnostics or configuration
viewer, ProVision automatically sends the username and password to the device.
Then, the device verifies the data is valid, and allows ProVision access to its dia-
gnostic functions. Without a valid password, the radio ignores write data com-
mands.
Prerequisites
For Eclipse devices that have Strong Security, to enable ProVision to change the
SNMPv3 security settings, you need an active SNMPv3 user account for the devices.
An Eclipse SNMPv3 user account can be set up from the Portal craft tool, or set up
from ProVision via the Configuration Profile Settings. To do this from ProVision,
select the Eclipse device and go to Configuration > Configuration Profiles. Then,
select Eclipse SNMPv3 User Account Configuration . Set the SNMPv3 user values,
including account level and authentication password. See Configuration Profile Refer-
ence for more details.
An additional ProVision function enables you to apply SNMPv3 pri-
vacy/encryption . To do this using the algorithm types of TDES, AES128, or, for US
customers only, AES192 and AES256, your ProVision system requires:
* A specific ProVision feature license.
614-330053-001 APRIL 2014 149

* A Java cryptography extension (JCE unlimited strength jurisdiction policy file/s)

from Sun Microsystems.
Contact your Aviat Networks representative to obtain this license and this extension.
Procedure
To set or edit device security access for Eclipse or TRuepoint radios:
1. Obtain the required security details, including user names and passwords, for the
devices.
5. Select the Account type, SNMPv3 .

6. Enter a Username. This is associated with the two passwords below.
l Authentication : This selects the algorithm used for this device’s data. Select
an Algorithm, and enter a Password and a Confirmation for the password.
l Privacy: This selects the encryption algorithm used for this device’s data.
Select an Algorithm, enter a Password and a Confirmation for the
password.
l Each password must be 8 characters long.
The Authenti cati on and Pri vacy types are determi ned by your
organi zati on’ s network pol i cy. An Authenti cati on of MD5 and a
Pri vacy of AES128 i s a common “strong securi ty” com-
bi nati on.
7. Click OK.
150 AVIAT NETWORKS

8. A Login icon appears in the SNMPv3 column, with the user name and security
details.
9. To remove SNMP v3 information only, right-click the device and select Remove
SNMP v3 . The login data is deleted, and the Login icon is removed.
Device Security Access for Multiple Radios

From the Device Security Accounts screen, you can edit device security access for all
the devices in a Container.
Procedure
Accounts window is displayed.
2. Right-click the required container and select Edit Account Information .
3. The Edit Password window is displayed. In the Account Type drop-down menu,
select the security account type. The values in the screen change to the values for the
device security account type.
614-330053-001 APRIL 2014 151

l SNMPv3 - see Setting SNMPv3 Security Access on page 149.

l Device Login - see Setting Device Security Account Values on page 148.
l Eclipse Login - see Setting Eclipse Device Security Values on page 143.
4. The values in the screen change to the values for the device type. Enter the values,
which will be applied to all devices in the container, and click OK.
5. The values display in the main Device Security Accounts screen for all devices
in the container.
6. To remove the values from the container, right-click the device and select the
Remove option.
Clearing Device Security Accounts

You can clear the current device security access details if they do not match the
details stored in the device.
Procedure
2. Right-click the required radio and select Clear All Account Information .
152 AVIAT NETWORKS

3. Data is removed from all columns except the SNMP type, indicating that the
device security has been cleared.
614-330053-001 APRIL 2014 153

Enabling a RADIUS Server

ProVision can authenticate users from a RADIUS server. The RADIUS Server cent-
ralizes user names, logins, and security for users of ProVision, Eclipse, and other
devices.
When the RADIUS Server is used for a network:
l It is installed and maintained separately from ProVision by Administrator-
level users. If you need to install a RADIUS server, for instructions on
installing RADIUS, see the separate Tech Note document FreeRADIUS
Configuration for Aviat Networks.
l Administrators must enable the RADIUS Server connection from ProVision,
using the RADIUS Server Configuration screen.
l RADIUS settings can be configured for all Eclipse radios using the RADIUS
option in Configuration Profile Settings for Bulk Configuration. See Updating
Eclipse RADIUS Authentication Settings on page 157 for details.
Prerequisites
This feature requires additional support with the Eclipse firmware, and it is only
available on Eclipse radios running versions 05.00.xx or greater.
For executing specific operations on the Eclipse Radio when both the ProVision
Server & Eclipse Radio are enabled for Radius Authentication,the logged in Provision
user requires a security profile and permissions for ProVision and for the Eclipse
Radio in the RADIUS server.
See ProVision User Security Profiles on page 124 .These requirements are as follows:
l Eclipse login banner (accessed through the Configuration Profiles in
ProVision)
l Radio Security Accounts (accessed through the Configuration Profiles
in ProVision)
l RADIUS configuration (accessed through the Configuration Profiles in
ProVision)
l SNMPv3 User Account (accessed through the Configuration Profiles in
ProVision)
l For the above four operations, the ProVision user must have: Configuration
and Administrator security profiles in the RADIUS server for ProVision-
Security-Profile, and Security and Administrator security profiles for Eclipse-
Security-Profile.
l Eclipse Software Loading - Requires Upgrade security profile in the
RADIUS server for ProVision-Security-Profile and Engineer security profile in
the RADIUS server for Eclipse-Security-Profile.
154 AVIAT NETWORKS

Procedure
1. Obtain the information for your RADIUS server:
l Server IP Address
l Shared Secret password
l Authentication Port
l Accounting Port
l Client Session Timeout value in Seconds
2. If required, install the RADIUS server.
3. Log into ProVision as an Security-level user. In the Administration menu,
select RADIUS Server Configuration .
4. In the RADIUS Server Configuration screen, enter the information from
Step 1 for the primary RADIUS server. You can enter data for the secondary
server, if required.
4. Click on Background Authentication Credentials. A screen displays:

enter a user name, password, and confirm password.
5. Click OK.
6. In the RADIUS screen, click OK.
7. ProVision is now connected to the RADIUS server. In future, all login
authentications will be done using this configured RADIUS server.
8. To set the RADIUS server settings for a new radio, select the radio that the
RADIUS server profile is to be applied to ,and then select the already saved
RADIUS configuration profile. See Configuration Profile Settings for Bulk
Configuration
614-330053-001 APRIL 2014 155

9. To bulk configure RADIUS server logins for all radios, select the ProVision
Physical Root in the network, right-click and select Configuration >
Profiles, then from Configuration Profile dialog select the Eclipse RADIUS
Configuration profile. Set the values as described in Configuration Profile
Settings for Bulk Configuration.
When you are setti ng up RADI US and popul ati ng the radrepl y
tabl e, you need to i ncl ude attri bute val ues for di fferent Avi at
software access groups. These val ues are:
Access Group Attribute Value

View Only 1
Controls 514
Configuration 1028
Upgrade 2056
Administration 4112
Security 8224
156 AVIAT NETWORKS

Updating Eclipse RADIUS Authentication

Settings
Periodically the system administrator may need to change the settings of the
RADIUS server that the Eclipse devices in the network use for authentication. Typ-
ically all Eclipse devices in the network will point to the same set of RADIUS servers,
thus each Eclipse needs to be updated whenever the RADIUS server address or
shared secret is changed.
The Eclipse RADIUS Configuration Profile allows the administrator to setup and
save the settings of the RADIUS servers (i.e. IP Address, Port and Shared Secret)
within ProVision and then apply these settings to some or all of the Eclipse devices
in the network in a single operation.
See Enabling a RADIUS Serv er on p age 154 for an overvi ew of
the RADI US enabl i ng requi rements.
Prerequisites
RADIUS configuration features are only available to ProVision administration users.
Because this is a security related feature the user must also have administration priv-
ileges on each Eclipse in the network.
The exact security prerequisites depend on whether the ProVision system is con-
figured to use a RADIUS server for authentication.
RADIUS User Authentication Prerequisites

l RADIUS must be enabled on both ProVision and the Eclipse.
l If RADIUS is not enabled in ProVision then the Standard User Authentication
requirements above apply.
l If RADIUS is enabled in ProVision but not in the Eclipse, then a user account
must exist in the Eclipse with same credentials (username and password) as
the ProVision user. This configuration is not recommended.
l Ensure that firewall settings are correct between Eclipse and ProVision.
l The credentials of the ProVision user initiating the operation are used to
authenticate with the Eclipse when reading or writing the configuration
profile, therefore:
l This user must have RADIUS credentials defined for both
the Eclipse and ProVision
l Eclipse – Administration
l ProVision – Administration and Configuration
614-330053-001 APRIL 2014 157

Other Prerequisites
This feature requires additional support with the Eclipse firmware, thus is only avail-
able on radios running versions 05.00.xx or greater.
Defining the RADIUS Configuration Settings

In a typical network using RADIUS authentication there is generally a pair of cent-
ralized RADIUS (primary and secondary) servers that are accessible to the all devices
in the network. The settings for these servers needs to be configured in each device
in the network and as such the user can define a single Eclipse RADIUS Con-
figuration profile for the whole network. This scenario shows how this profile can be
created and then applied to all Eclipse devices.
1. Ensure that the correct ProVision and Eclipse user privileges are con-
figured, based on the Prerequisites.
2. Select the ProVision Physical Root in the network, right-click and select
Configuration > Profiles, then from the Configuration Profile dialog select
the Eclipse RADIUS Configuration Profile.
3. Check the box to enable RADIUS authentication.

4. Enter the IP address, port and shared secret of each of the required
RADIUS servers. 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 respond.
158 AVIAT NETWORKS

5. Save the configuration profile; the profile must be saved before it can be
written back to the radios.
6. Select Execute to write the changes to all supported Eclipse devices in

the network. A dialog will appear verifying the radios that this profile will
be written to, if necessary radios can be removed from this list. Press
Execute again to complete the operation.
7. The progress of the operation can be monitored using the Task Manager.
Setting the Radius Configuration on a Single

Eclipse Radio
When a new Eclipse radio has been added to the network it is possible to re-apply
the RADIUS configuration profile to a single Eclipse. This is easily done by selecting
the Eclipse that the profile is to be applied to and then selecting the already saved
RADIUS configuration profile.
1. Ensure that the correct ProVision and Eclipse user privileges are
configured, based on the Prerequisites.
2. Select the ProVision Physical Root in the network, right-click and
select Configuration > Profiles, then from the Configuration
Profile dialog select the previously saved RADIUS Configuration
profile from the drop down list.
614-330053-001 APRIL 2014 159

3. Select Execute to write the changes to the selected Eclipse device.

Press Execute again on the following dialog to complete the
operation.
4. The progress of the operation can be monitored using the Task
Manager.
160 AVIAT NETWORKS

Chapter 8. Migrating Topology
l About Migrating Topology on page 162
l Importing the Topology on page 163
l Exporting the Topology on page 164
l Migrating StarView Data into ProVision on page 171
614-330053-001 4/04/2014 161

CHAPTER 8. MIGRATING TOPOLOGY
About Migrating Topology

When you are upgrading to a new version of ProVision, or backing up ProVision, it is
useful to create and save a topology file. A topology file contains the details of your
current ProVision setup for sites, regions, radios, and other important network data.
It does not include Map graphics.
I f you are upgradi ng to ProVi si on after usi ng StarVi ew, you
can use the StarVi ew Mi grati on Tool to convert the StarVi ew
data i nto a ProVi si on topol ogy. See Migrat ing St arView Dat a
int o ProVision on p age 171.
Parameters
The network topology is migrated as an.XML file. The .XML file contains:
l Object type (container or device)
l Object name
l Object containment definition
l Device IP addresses (primary)
l SNMP community strings
l Object state (Managed)
l Object performance data collection state (daily enabled/disabled, 15-min
enabled disabled)
l Object coordinates (in Map view)
l Link information
Prerequisites
The topology export file is needed when upgrading from ProVision 2.3 or 3.0 to ProVi-
sion 6.3.
The following parameters must be unique:
l The name of each object in the topology
l Device object IP address (primary)
Dependencies
The northbound interface (NBI) is dependent on the network topology.
162 AVIAT NETWORKS

Importing the Topology

This function imports a previously exported network topology file. The Tree and Map
Viewers are automatically populated with containers and devices.
Any issues encountered during the import are displayed in the Import Results
panel and recorded in the <pvroot>ProVisionClient/system-client.log.
A common problem during an import is when an object that is being imported has
the same name of an object already in the network. The imported object is skipped
and the existing object remains in the network unchanged. The Import Results
screen displays the message:
“Object name is not unique nnnn. Skipping object: nnnn”
Where “nnnn” is the name of the object in question.
Objects that were not imported can be manually deployed and managed.
Topol ogy i mports from ProVi si on 6.9 onwards i ncl ude stand-
ard and l ogi cal l i nks, contai ners, and devi ces. I mports from
earl i er versi ons of ProVi si on do not i ncl ude l ogi cal l i nks and
contai ners.
Procedure
1. Select File > Topology Import. The Topology Import window is displayed.
2. Select the button. The Open window is displayed.

3. Browse to the location of the topology file.
4. Highlight the topology file and select Open . The Open window closes and the
Topology Import window is displayed.
614-330053-001 APRIL 2014 163

5. Select Import.
6. The import is processed. You cannot re-import this file from this screen during
this session; after you complete the import, the Import button is disabled.
7. When the import has completed, select Close.
8. Review the Event Browser for “invalid deployment” events. Use the Filter function
to find all events titled Invalid Deployment, as shown below:
9. Delete the Invalid Deployment events.

10. One hour later, review the Event Browser again. If any Invalid Deployment
events recur for Eclipse devices, this indicates a deployment problem. Record the
device details. Delete the affected devices, and redeploy the devices with the correct
radio type. See Deploying and Managing Devices in the ProVision User Guide for
more information.
Related Topics:
l Exporting the Topology on page 164
Exporting the Topology

This function exports the network topology (objects and hierarchy) to an.XML file.
The network topology can be exported for several reasons, as a backup, for support
diagnostic purposes, for 3rd party northbound integration, and for future migrating
to a later version of ProVision.
Avi at Networks recommends that a topol ogy fi l ename i ncl ude
the date the fi l e was exported.
Topol ogy exports i ncl ude standard and l ogi cal l i nks, con-
tai ners, and devi ces.
F or backi ng up as part of an upgrade, see Dat a Backu p and
Sharing Using Top ology Exp ort s on p age 19 5 and ProVision 2. 3/3. 0
Top ology Migrat ion Tool on p age 16 6 .
164 AVIAT NETWORKS

Procedure
1. Select File > Topology Export. The Topology Export window is displayed.
2. Select the button and browse to the location in which to store the topology
file. The Save window is displayed.
3. Type a descriptive name in the File Name field.
Save the .xml topol ogy fi l e i n a fol der outsi de the ProVi si on
software fol der. I f you do not, the fi l e wi l l be del eted when
ProVi si on i s uni nstal l ed.
4. Select Save. The Save window closes and the Topology Export window is dis-
played.
5. Select Export. The Export Results panel displays the final status of the export,
including any items that could not be exported.
6. Select Close.
614-330053-001 APRIL 2014 165

7. The Export file is now in the folder location where it was saved.
Related Topics:
Importing the Topology on page 163
ProVision 2.3/3.0 Topology Migration Tool

The topology migration tool extracts the network topology information from ProVi-
sion 2.3 or 3.0. Then, it outputs a ProVision compatible topology file, and a log file
which you can view to see any problems that were encountered.
During the topology export a window is displayed, describing the progress of the
export and how long the export is estimated to take. An example of this window is
shown here:
CAUTION:Objects with an illegal character are not exported, an error

message is displayed and the object’s data is listed in the export log.
These objects must be manually deployed in ProVision.
Upgrading from ProVision 2.3 or ProVision 3.0 to ProVision 6.5 requires the fol-
lowing procedures:
166 AVIAT NETWORKS

2.3/3.0 Sun Server

1. Install and run the topology migration tool which exports the network topology to
CemfExport.xml. Refer to ProVision 2.3/3.0 Topology Migration Tool on page 166 for
the procedure.
ProVision Server
1. Install the released ProVision server and client software.
2. If there are Eclipse radios on the network install the Portal software. Refer to See
"Installing the Portal Application".
3. If a permanent ProVision license has been purchased, refer to Activating a ProVi-
sion Server License on page 104.
4. Copy the topology file, CemfExport.xml to the <Install Dir-
ectory>ProVision server directory.
5. Start a ProVision client on the server and import the topology file. For importing
topology file instructions, refer to Migrating Topology on page 161
6. Set up ProVision. Refer to Setting Up ProVision on page 107.
8. Import the topology file CemfExport.xml. See Importing the Topology on page
163.
9. Setup the newly installed ProVision. See Workflow for Setting Up ProVision on
page 109.
10. For an Eclipse network, check the device compatibility in the newly installed
ProVision. See Checking Device Compatibility on page 93.
CAUTION:Scoreboards, customized event browsers, performance data
and NBI configurations are not migrated from ProVision 2.3/3.0 to
ProVision 6.1.
Topology Migration Procedure

To install and run the topology migration tool:
1. Copy the file TopologyExport_x.x.x.tar to the directory where the tool is to
be installed.
2. Extract the file TopologyExport_x.x.x.tar:
tar xvf TopologyExport.tar
3. Change to the newly created directory
cd TopologyExport
4. Run the install script
./install
614-330053-001 APRIL 2014 167

This configures the environment the tool runs in.

If you are running a Solaris 2.6 system, it asks you to install patches. Enter 'y' to
install them. After installing the patches you will be told that it may be necessary to
restart your system; you do not have to do this.
This also configures a Java runtime environment for this tool. Accept the terms and
conditions of the Java environment. At this point, Java is installed and the tool is
ready to run.
5. Run the tool
./export
This creates two files, the export.log, and a file CemfExport.xml that is used to
import your ProVision network topology into ProVision.
View the Export Log File

If there are objects with duplicate names, the first occurrence is exported with the
name unchanged, further occurrences retain the original name but with a number in
brackets added to the end of the name.
The export.log (pictured below) provides a summary of problems encountered during
the export, and the corrective action taken.
Edit the Topology File (CemfExport.xml)

Objects are not exported properly if they have an unrecognized radio type or are not
reachable through the network. The tool includes as much information as possible
about the object. This information is commented out in the topology file. When this
occurs, you are notified by a warning message. Once the export is complete, you can
edit the file to uncomment the affected radios.
For example, when Altium radios are not reachable through the network the type of
Altium cannot be determined and are exported as “Altium Unknown” and
168 AVIAT NETWORKS

commented out. If your network has Altium radios, use the following procedure to
ensure each radio has the correct radio type in the export file:
1. Open CemfExport.xml.
2. Search the export file for occurrences of the Altium radios. The code looks similar
to the following:

3. Change "altiumUnknown" to the correct radio type:
l Altium 1 = "altium"
l AltiumMX = "altiumMX"
l AltiumMX 2+0 = "altiumMX2+0"
4. Remove the comment tags at the beginning, "" of the
radio description. If the radio was an Altium 1, the initial and edited code would
look like:
614-330053-001 APRIL 2014 169

Initial Code Edited Code

 <state>connecting</state>
</object>
5. Save and close the file.
170 AVIAT NETWORKS

Migrating StarView Data into ProVision

StarView users can import the microwave network data that has been managed by
StarView into ProVision. This data is imported in the same format as a ProVision net-
work Topology file.
To do this, you need to install and use the StarView Migration Tool provided by
Aviat Networks.
The StarView Migration tool enables users to:
l Extract data from StarView
l Apply ProVision configuration to the data
l Import the data into ProVision
l Migrates data for the following device types:
o Aurora
o CAU
o Constellation
o DVA
o DVM (T,R) and DVM XT
o MicroStar I, II, or III
o Megastar 1+1, M:N
o TRuepoint 4000, 4040v1, 4040v2, 5000, 5000 2+0, 6400
l Migrates device data and topology data for the following device types:
l Constellation
Prerequisites:
Administrator-level access to the current StarView installation, and to a complete
ProVision installation, ready to operate.
The zip file SVMigrationx.y.zip. In this file name, X and Y are the StarView
migration tool version numbers. The executable files you will need are in this zip file.
The SQL file sv_pv_migration.sql.
Extracting Device Data from StarView

1. Begin with the PC that is running the StarView installation. On this PC, create a
new folder.
2. Copy the file sv_pv_migration.sql onto the StarView PC into the created dir-
ectory.
3. On the StarView PC, open the command prompt.
614-330053-001 APRIL 2014 171

4. Using commands, go to the created directory.

5. Run the following command:
ovdwtopo -export
ovdwquery -file sv_pv_migration.sql -out sv_pv_migration.txt -
sep ;
6. Check the C:\Migration folder. A new file should be created, sv_pv_migra-
tion.txt.
7. Copy sv_pv_migration.txt from the StarView server into the directory where
the StarView migration tool will be installed.
Applying ProVision Configuration to StarView Data

1. Unzip the SVMigrationx.y.zip file into a directory.
2. Run the tool SVMigration.bat. The StarView Migration Tool screen appears:
3. Click the Open button near Input SV File. Find the sv_pv_migration.txt file.
Select it and click Open .
4. With this file selected, click the Convert button. You are prompted to enter the
name of the ProVision topology export file, and the directory where it will be saved.
5. If you have any of the following devices:
l Megastar M:N
l TRuepoint 4040, 5000, 5000 + 2
l MicroStar I, II, or II
l DVM (T,R)
the Device Configuration screen displays:
172 AVIAT NETWORKS

6. In the Device Configuration screen, you can:

l Edit the Name and Configuration values for devices. The values you enter here
will be applied to these devices in the ProVision topology.
l For DVM and MegaStar devices, double-click on them to directly edit their
configuration values. A window pops up to enable this:
l For devices with + signs beside them, which have multiple IP addresses,
mouse over the device for a tooltip with configuration information.
l Sort the data columns by clicking on the column headings.
614-330053-001 APRIL 2014 173

7. Once you are done making changes in the Device Configuration screen, click OK.
8. The StarView data is converted to a ProVision topology file. A log file named
SVmigration.log is also generated, and stored in the ProVisionClient folder.
Any errors i n the conversi on are di spl ayed i n the StarVi ew
Mi grati on screen. These errors are al so saved i n the l og fi l e
sv_migration.log. I f a devi ce i s not converted and i mported
i nto the topol ogy, you wi l l need to enter i t manual l y i nto
ProVi si on.
9. Close the StarView Migration Tool.
Importing the New Topology into ProVision

1. On the ProVision PC, open the ProVision Client. Go to the File menu and select
Topology Import.
2. In the Topology Import screen, select the new .XML file.
3. The StarView data is now imported into ProVision. It displays in the Tree Viewer.
This data is structured in a Container named SV Import -(datetime), sorted
into sub-containers by device family.
4. Move, rename, and reparent devices as required.
174 AVIAT NETWORKS

Importing Multiple Starview Topologies into ProVision

1. On the ProVision PC, open the ProVision Client. Go to the File menu and select
Topology Import.
2. In the Topology Import screen, select the .XML file for the first topology you are
importing.
3. The StarView data is now imported into ProVision. It displays in the Tree Viewer.
This data is structured in a Container named SV Import -(datetime), sorted
into sub-containers by device family.
4. Rename and reparent the devices, placing them in new containers. Make sure that
no devices have duplicate names.
Thi s step i s very i mportant. When you i mport addi ti onal topo-
l ogi es, i f devi ce or contai ner names al ready exi st i n ProVi -
si on, ProVi si on wi l l not i mport those devi ces/contai ners.
Renami ng i mported i tems wi th uni que names avoi ds thi s prob-
l em.
5. Import the second topology file into ProVision.
6. Repeat step 4 for each topology that you import.
Extracting Constellation Device and Topology Data

from StarView
CAUTION:This section is applicable to Constellation devices only.
1. Begin with the PC that is running the StarView installation. On this PC,
create a new folder.
2. Copy the file sv_pv_migration.sql onto the StarView PC into the created
directory.
3. On the StarView PC, open the command prompt.
614-330053-001 APRIL 2014 175

4. Using commands, go to the created directory.

5. Run the following commands:
n ovdwtopo -export
n ovdwquery -file sv_pv_migration.sql -out sv_pv_
migration.txt -sep ;
n ovmapdump –v > ov_pv_migration.txt
6. Check the C:\Migration folder. New files should be created, sv_pv_
migration.txt and ov_pv_migration.txt.
7. Copy sv_pv_migration.txt and ov_pv_migration.txt from the
StarView server into the ProVisionClient directory on the Client PC.
Applying ProVision Configuration to StarView Data

1. Unzip the SVMigrationx.y.zip file into a directory.
2. Run the tool SVMigration.bat. The StarView Migration Tool screen
appears:
3. Click the Open button near Iinput SV File. Find the sv_pv_
migration.txt file. Select it and click Open.
4. Click the Open button near Iinput OV File. Find the ov_pv_
migration.txt file. Select it and click Open.
5. With these file selected, click the Convert button. You are prompted to enter
the name of the ProVision topology export file, and the directory where it
will be saved.
6. The StarView data is converted to a ProVision topology file. A log file named
sv_migration.log is also generated, and stored in the StarView migration
tool is installed.
7. The Topology file can be imported into ProVision and devices can be
reparented and renamed as required.
176 AVIAT NETWORKS

Any errors i n the conversi on are di spl ayed i n the StarVi ew

Mi grati on screen. These errors are al so saved i n the l og fi l e
sv_migration.log.
CAUTION:If a device is not converted and imported into the topology,
you will need to enter it manually into ProVision.
Devi ces wi th dupl i cate names are renamed by appendi ng a

number to dupl i cate. I l l egal characters i n devi ce names are
repl aced by spaces.
614-330053-001 APRIL 2014 177

Chapter 9. Database and Server
Management
This section on Database and Server Management describes the commands and
menu options for managing the ProVision database. It also includes information on
server/services management.
The topics in this section include:
l About Managing and Backing Up the ProVision Database on page 180
l Database Backup Procedures on page 184
l Data Backup and Sharing Using Topology Exports on page 195
l Server and Services Management Procedures on page 196
F or i nformati on on managi ng Standby servers, i ncl udi ng
coordi nati ng backups between a Pri mary server and a
Standby server, see Red u nd ant Serv er Dep loy ment s on p age 203.
614-330053-001 4/04/2014 179

CHAPTER 9. DATABASE AND SERVER MANAGEMENT
About Managing and Backing Up the

ProVision Database
ProVision includes complete functionality for generating backups. Administrator-
level users can also manage the ProVision server and services using database com-
mands.
See the following topics for more information:
l Daily, Weekly, and Monthly Backup Processes on page 181
l Changing Database Configuration on page 182
About Backup Files

Generating and managing backup files is very important for network security and
integrity. ProVision Administrators can schedule automatic backups of the ProVision
network. Administrators can also run backups manually, whenever they are required.
If the database gets corrupted, you can restore the database from a backup. If you
need to identify whether a database is corrupted, you can run the database integrity
check.
The following data is copied to the hard drive when you backup the ProVision data-
base:
l Security data
l User accounts, security groups, device security accounts
l Configuration data
l Deployed network topology, device configuration and status
You also have the option to backup the event and/or the performance data.
When you initiate a database backup, ProVision creates a backup folder, copies the
database into the folder, and updates the backuplisting.xml file. This view
shows the location of the backup folder and an example of the naming standard
used.
The following diagram shows a breakdown of the naming convention used.
180 AVIAT NETWORKS

Backup Frequency
The following backup procedures are recommended:
l Daily - Backup the ProVision database to a CD, DVD, flash drive, or network
drive.
l Weekly- Copy the last database backup to a CD, DVD, or flash drive, which
is then stored off-site. Include the network topology file with this backup.
Aviat Networks also recommends that you run a manual backup before any
upgrade of ProVision, and when any significant changes are made to the
database. This backup should include event and performance data, and including
the network topology.
When to Run Backups

When the system is performing a backup, ProVision automatically locks object
deployment, alarm processing, software installation, and the network topology.
Because of this, you should plan to run backups during a time when there is min-
imal operator activity on ProVision. Administrators often schedule backups to run at
midnight, a good time for avoiding operator activity.
Backup File Size

Database and topology backup files are large files. Servers, CDs, and flash drives for
backup files should have at least 1MB of space available. The size of the database
backup files is influenced by:
l Number and type of devices on the network
l Event pre-filtering
l Frequency of the database purging
l Quality of the network
Daily, Weekly, and Monthly Backup Processes

Aviat Networks recommends that you use the ProVision backup functions to save
your ProVision databases and topology. For best practice and system security, use
the following procedures.
614-330053-001 APRIL 2014 181

Daily Backup Process:

1. Run the database backup from the ProVision User Interface. In the Admin-
istration menu, go to Database Backup and run the Scheduled or Manual
Backup.
2. ProVision then creates a backup folder at ProVisionServer\mysql\backup.
The folder is named for the backup date and time. ProVision copies the database to
this folder and updates the backuplisting.xml file.
3. Then, copy the backup folder and the backuplisting.xml file to a CD, a DVD, a
flash drive, or to a network drive.
Weekly Backup Process:

1. Aviat Networks recommends that you store each daily backuplisting.xml file
on a CD, DVD, or a flash drive. Place the saved backup in a fireproof safe.
2. At the beginning of each work week, move the backup items to your archival stor-
age location.
3. The oldest set of CDs or flash drives can be returned to the engineers for reuse.
Monthly Backup Process:

1. On the fifth working day of the fourth week of each month, you should copy all
the backup files for the entire month onto one read-only CD or flash drive.
2. Label the read-only backup with the month and year that it backs up.
3. Store it permanently off site, at your archival storage location.
Serv er and Serv ices Management Proced u res on p age 19 6
Changing Database Configuration

Administrator level users can change the MySQL database details, updating the user
name, password, and port number. To access this, use the procedure below.
Thi s i s not supported on ProVi si on Redundant Server i nstal l -
ati ons.
Procedure
1. Select Start > Programs > ProVision Server > C:\ Command Window.
2. At the prompt, type pv db configure for Windows or ./pv_db_configure
for Solaris. If a window appears with the message “Do you want to allow the fol-
lowing program to make changes to this computer?” click Yes.
3. The Change Database Details screen displays.
182 AVIAT NETWORKS

4. Enter the updated MySQL database details:

o Username - Between 4 and 16 alphabetic
characters
o Password - Minimum length of 8 characters
o Port number - In a range between 1025 to 65534.
5. To return to the default installation values, click Use Default.
6. To save the entered values, click Set.
7. You are returned to the Command window.
8. Restart the ProVision Service with the command pv service start for
Windows or ./pv_service start for Solaris.
614-330053-001 APRIL 2014 183

Database Backup Procedures

It is important to back up your ProVision system on a regular basis. There are two
types of backup process available, Manual and Scheduled.
l Manual Backup Procedure on page 185
l Scheduled Backup Procedure on page 186
l Restoring the ProVision Database on page 187
l Checking the Database Integrity on page 189
l Changing Database Purging Criteria on page 190
l Configuration Backup and Restoration on page 191
These processes all describe the backup process for a Primary Server installation of
ProVision. If your system uses Standby servers, see also Synchronizing Primary
Server and Standby Server Databases on page 208.
See also About Managing and Backing Up the ProVision Database on page 180.
184 AVIAT NETWORKS

Set Backup Preferences

Administrators can set the location where ProVision will save backup files. ProVision
will save both manual and scheduled backup files to this location.
Procedure
1. Start with the ProVision user interface.
2. From the menu bar, select Administration > Database Backup > Backup
Preferences. The Database Backup Preferences window displays.
3. Enter the backup location. If it is accessible, a green check displays beside the loc-
ation. If it is not accesible, a red X displays, and you must enter a different location.
4. When your location is valid, click OK.
5. The window closes. ProVision will save both manual and scheduled backup files to
this location.
Manual Backup Procedure

Running a manual backup of ProVision takes a backup of the system at the time
that you run the Manual Backup function.
To perform a backup, you must have a ProVi si on cl i ent run-
ni ng to access the database backup opti ons from the user
i nterface.
Procedure
2. From the menu bar, select Administration > Database Backup > Manual
Backup. The Manual Database Backup window displays.
614-330053-001 APRIL 2014 185

3. In the Description field, type a description of the backup. The description you
enter is written in the backuplisting.xml file, located in the ProVi-
sionServer\mysql\backup folder.
4. Use the check boxes to select additional information to include in the backup:
l Include Event Data
l Include Performance Data
l Include Device Config Files
l Include NBI (note: does not include NBI Performance)
5. Select Backup. You will be prompted to view the backup in the Task Manager.
Select OK.
6. The Backup is monitored by the Task Manager, and its success or failure is noted.
Scheduled Backup Procedure

The Scheduled Backup function runs and saves a backup of your ProVision data auto-
matically, based on the schedule values that you enter.
By default, the Scheduled Backup is enabled to run on a weekly basis. The default
Scheduled Backup includes events and performance data, and runs with a start time
of 2 AM. Each weekly backup is purged after 30 days. If you want to change these
Scheduled Backup values, use the procedure below.
Procedure
2. From the menu bar, select Administration > Database Backup > Scheduled
Backup. The Scheduled Database Backup window displays.
186 AVIAT NETWORKS

3. In the Description field, type a description of the backup. The description you
enter is written in the backuplisting.xml file, located in the <Install Dir-
ectory>\ProVisionServer\MySQL\Backup folder.
4. Use the check boxes to select additional information to include in the backup:
l Include Event Data
l Include Performance Data
l Include Device Config Files
l Include NBI (note: does not include NBI Performance)
5. In the Next Update field, select the date (up to two weeks in advance) of the next
update using the up and down arrows.
6. In the Start Time field, select the hour that you want the backup to occur using
the up and down arrows. Then select AM or PM. The update occurs on the hour, for
example 1 AM means the update starts at 1:00:00 AM.
7. In the Frequency field, select the how often, in days, you want the update to
occur. This field can be set between 1 and 30 days.
8. In the Purge backups older than field, select how often, in days, you want to
purge the backup files. This field can be set between 2 and 365 days. A minimum of
a one-hour buffer is recommended between scheduled database backups and sched-
uled database purges.
9. To save the scheduled backup settings, select OK.
Restoring the ProVision Database

Some common reasons for wanting to restore the database are upgrading to a higher
version of ProVision or replacing a corrupted database.
It is important to remember that the restore feature overwrites the existing data in
the database with the stored backup data. Database backups can be stored locally on
614-330053-001 APRIL 2014 187

the Server hard drive, on a network drive, or externally on a CD. For ProVision to
restore a database from a backup, the backup folder and backuplisting.xml file must
be in the following directory:
ProVisionServer\mysql\backup
I f you are restori ng from a backup that has been stored on
CD, you must remove the Read-onl y setti ng from i ts Prop-
erti es. You cannot restore a database from an i ncompati bl e
versi on of ProVi si on, for exampl e, a ProVi si on 3.0 database
i nto ProVi si on 6.5.
Procedure
1. Ensure the backup folder and backuplisting.xml file are in the following directory:
ProVisionServer\mysql\backup
2. Stop all client sessions, by having the operators log off from ProVision.
3. Select Start > Programs > ProVision Server > Command Window.
4. At the prompt, type: pv db restore
For Solaris, type: ./pv_db_restore
The following message is displayed indicating that ProVision needs to be shut down.
Press any key to continue.
ProVision shuts down automatically.

5. The ProVision Restore Database window is displayed, listing the backups.
6. Select the required backup and select Restore.

7. To observe the restore actions, select the Command Window screen. The changes
are shown in this screen.
8. When the restore is complete, the following message window is displayed.
188 AVIAT NETWORKS

If the restore failed, a message informs you that the restore has failed, and asks you
to check restore.log.
Check the file restore.log for details, located in the folder:

ProVisionserver/.
9. Select OK.
10. To close the Restore Database window, select Exit.
11. To restart the ProVision server, type the following in the command window: pv
service start
For Solaris, type: ./pv_service start
12. To start a ProVision client session and verify the restore was successful, select
Start > Programs > ProVision Client.
Checking the Database Integrity

If ProVision is not displaying information correctly, check the database integrity.
This function checks the integrity of the MySQL database table pointers and indexes,
and also repairs these problems if found. It does not check and repair corruption of
ProVision data in the database. Corruption of the ProVision data means you must
restore to a backup of the database before the corruption occurred.
Procedure
The results from the database check are stored in:\ProVi-
sionServer\database\checkrepair.log
To check the database integrity:
2. At the prompt, type: pv db check
For Solaris, type: ./pv_db_check
614-330053-001 APRIL 2014 189

This checks and repairs key database tables.

3. At the prompt, type: pv db check all
For Solaris, type: ./pv_db_check all
This checks and repairs all database tables, but takes longer to run.
The following message is displayed indicating ProVision must be shut down.
4. To close the ProVision Server, press Enter. The Command Window indicates
when the database check has finished.
Check the results in the file checkrepair.log located in the folder: <Install Dir-
ectory>\ProVisionServer\database\.
5. To restart the ProVision Server, type: pv service start
Changing Database Purging Criteria

By default, the ProVision database is purged at regular periods. The data to be
purged from the database has been separated into the following groups:
l Daily performance data
l 15-minute performance data
l Cleared events
l Security events
Procedure
To change the database purge criteria:
1. Start a ProVision user session.
The ProVision user interface is displayed.
190 AVIAT NETWORKS

2. From the menu bar, select Administration > Database Purge.

The Database Purge window is displayed.
3. Make the required changes. Note that:

l A minimum of a one-hour buffer is recommended between scheduled database
backups and scheduled database purges.
4. To run a purge immediately, click the Purge Now button.
5. To accept the changes, select OK.
I f the number of events generated per day, over the purge

peri od, exceeds % of the purge maxi mum (500,000 events),
ProVi si on wi l l rai se an event to noti fy the admi ni strator.
Configuration Backup and Restoration

The Export Configuration Backup function saves and restores configuration for the
following device types:
l Accedian
l CTR 8440 (see note)
l CTR 8540
l Eclipse (see notes)
l Symmetricom
l WSG ASN Controller
l WSG-R Juniper M7i (see notes)
l WSG-R Juniper M10i (see notes)
l WTM 3200 (export only, restore is available from the craft tool)
l WTM 3300 (export only, restore is available from the craft tool)
l EION StarMAX 6400 BS blade
l EION StarMAX 6100 BS
614-330053-001 APRIL 2014 191

The ProVision server stores up to 5 different configuration backups for each device.
For most devices, ProVision checks for device configurations every 12 hours, and
saves any changed Eclipse configurations to the ProVision server. The saved files,
part of ProVision’s backup/restore capability, can be used by Portal to restore
WiMAX devices.
Prerequisites and Notes

l Devices requiring configuration backup/restoration need to have their correct
credentials entered in the device Security Account. See Device Security
Accounts on page 141 in the Administration documentation for more details.
l Eclipse devices can have their configuration backup saved, and then restored
via Portal.
l For Eclipse devices with Strong Security enabled, to enable ProVision to
back up and restore configuration, 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 Profile Settings. See Setting SNMPv3 Security Access on
page 149 for more details.
l Juniper devices are not on the 12-hour device configuration check. Instead,
Juniper automatically sends any configuration changes to ProVision, whenever
these changes are made. ProVision then generates the configuration backup file
when Juniper sends configuration changes. Also, for Juniper, ProVision purges
the configuration backup files every 24 hours, retaining the most recent 5 files
for the Juniper devices.
l CTR 8440 devices can have their configuration backup saved, but not
restored. The configuration backup is done via the TFTP server which comes
bundled with the ProVision Server installation. The TFTP server runs on port
69. Note that any external TFTP servers should be stopped for the TFTP server
on ProVision to work.
Export Configuration Backup Procedure

2. Find the device that you want to back up.
3. From the right-click menu, select Configuration > Export Configuration
Backup. The Export Configuration Backup window displays the available con-
figuration backups for the radio.
192 AVIAT NETWORKS

4. Select the backup that you want to export and click Export.
5. You are prompted to save the export file. Select the directory location and click
Save.
WiMAX Configuration Restore Procedure

2. Find the device for which you want to restore a configuration. Right-click it and
open its craft tool.
3. The craft tool opens with the data for this device.
4. To restore a WiMAX device, go through the following steps:
l Right-click on the WiMAX device that needs its configuration restored and
select Configuration > Configuration Backup.
l Navigate to the configuration file that you require, and click Select.
5. The Confirm Restore message displays:
614-330053-001 APRIL 2014 193

6. Click OK.
7. The saved Configuration is restored to the device.
194 AVIAT NETWORKS

Data Backup and Sharing Using Topology

Exports
As an alternative to database backup, some ProVision users benefit from using ProVi-
sion topology export/import functions to backup and share data. For an overview of
topology export/import, see About Migrating Topology on page 162.
Example
This diagram shows an example of a 3+1 solution. A backup ProVision master sys-
tem provides redundancy for a number of regional ProVision networks. The regional
ProVision administrators send their data to the ProVision master system as topology
files. The topology files are imported into the ProVision master system.
Sample Procedure
1. Each ProVision site administrator should export their topology. For instructions,
see Exporting the Topology on page 164.
2. The exported topology file is emailed to the ProVision master administrator.
3. The ProVision master administrator imports the topology files into the ProVision
master installation. For instructions, see Importing the Topology on page 163.
4. All the devices and configurations from the ProVision sites are coordinated in the
ProVision master system.
Li mi tati ons:
Topol ogy data does not i ncl ude performance data.
614-330053-001 APRIL 2014 195

Server and Services Management

Procedures
Server and services management procedures enable users to start and stop the server,
install and remove ProVision as a system service, and reset the ProVision database.
l Monitor Server Disk Space and Memory on page 197
l ProVision Database Commands on page 196
l Stopping the ProVisionServer on page 199
l Starting the ProVision server on page 200
l Resetting the Database on page 200
l Removing ProVision From System Services on page 201
l Installing ProVision as a System Service on page 202
See also Database Backup Procedures on page 184.
ProVision Database Commands

This table defines the database commands accessible via the ProVision server com-
mand window. These commands are useful as you perform data checks, backups,
and data restoration.
F or Wi ndows 7, 2008R2 and 8, run these commands as an
Admi ni strator. To do thi s, open the Commands screen by
Adm in strator .
Table 9-1. ProVision Database Commands

pv db restore ./pv_db_restore Restores a database backup,
launches interactive tool
pv db check ./pv_db_check Runs an integrity check on the
database (key tables only)
pv db check all ./pv_db_check all Runs an integrity check on the
database (all tables)
pv db reset ./pv_db_reset Destroys all database contents
pv import <dir- ./pv_db_import <dir- Used for database migration.
ectory> ectory>
196 AVIAT NETWORKS

I f a wi ndow appears wi th the message “Do you want to al l ow

the fol l owi ng program to make changes to thi s computer?”
cl i ck Yes .
Monitor Server Disk Space and Memory

From the ProVision Manager object in the Tree Viewer, you can review the ProVision
Server’s available disk space and memory usage. You can also set up a Performance
Threshold to trigger an event when disk space is below a minimum value.
Check Available Space and Memory

1. In the Tree Viewer, right-click on the ProVision Manager object.
2. In the right-click menu, select Performance > Trends. The Performance Trends
screen displays.
3. To view the available disk space, go to the Parameters frame. Select the value
15-Min Disk Space and click Apply. The graph displays the available disk space
for the ProVision Server.
614-330053-001 APRIL 2014 197

4. To view memory usage, select 15-Min Memory Usage and click Apply. The
graph displays the memory usage for the ProVision Server.
Create a Low Disk Space Event

1. In the Tree Viewer, right-click on the ProVision Manager object.
2. In the right-click menu, select Performance > Thresholds. The Performance

Thresholds screen displays.
3. Select the value 15-Min Disk Free Space. The available events display.
4. Edit the following values for available events:
l Event Description - Enter a brief description of a low disk space event. You
can retain an existing event name or alter it.
l Trigger Value - Enter the trigger value in MB. ProVision automatically
converts this to a programming value.
l Severity - Select the Severity level from the drop-down menu.
198 AVIAT NETWORKS

5. After you have edited available events, click OK.

6. If the system disk space goes below the trigger value for an event, you will be aler-
ted via a ProVision Event.
Stopping the ProVisionServer

There are times when you must stop the ProVision server, for instance, when you
want to activate a new license.
Procedure
1. Select Start > Programs > ProVision server > C:\ command window.
Adm in strator .
2. At the prompt, type: pv service stop

For Solaris, type: ./pv_service stop
If a window appears with the message “Do you want to allow the following program
to make changes to this computer?” click Yes.
3. Press Enter. A message displays, indicating the ProVision server has stopped.
614-330053-001 APRIL 2014 199

Starting the ProVision server

When the server computer is turned on, the ProVision server software automatically
starts and runs in the background. However, if you have stopped the ProVision
server, you must manually start the ProVision server.
Procedure
To manually start the ProVision server:
Adm in strator .
2. At the prompt, type: pv service start

3. Press Enter. A message is displayed indicating the ProVision server has started.
Resetting the Database

When you reset the database, you delete all the database contents, from performance
data and event history to the network topology.
Al ways backup the ProVi si on database before resetti ng the
database.
Procedure
1. Select Start > Programs > ProVision Server > C:\ command window.
200 AVIAT NETWORKS

2. At the prompt, type: pv db reset

For Solaris, type: ./pv_db_reset
The following message is displayed, indicating that ProVision needs to be shut
down. If a window appears with the message “Do you want to allow the following
program to make changes to this computer?” click Yes.
3. To close the ProVision server, press Enter to continue. The Command Window dis-
plays the reset actions.
The database is now reset.
Removing ProVision From System Services

Use this command when you want to start the server computer without the ProVi-
sion server starting automatically.
If you have removed ProVision from the system services, you cannot start the ProVi-
sion server or a client user session until you install ProVision as a system service.
Removi ng ProVi si on from the system servi ces does not
remove any of the ProVi si on fi l es.
Procedure
614-330053-001 APRIL 2014 201

2. At the prompt, type: pv service remove

For Solaris, type: ./pv_service remove
3. Press Enter. The command window’s message indicates ProVision has been
removed.
Installing ProVision as a System Service

You would use this command to install ProVision as a system service, if you
removed it. Once you have installed ProVision as system service you also need to
start the ProVision server.
Procedure
2. At the prompt, type: pv service install
For Solaris, type: ./pv_service install
3. Press Enter.
The command window’s message indicates ProVision has been installed.
202 AVIAT NETWORKS

Chapter 10. Redundant Server

Deployments
This section describes the two types of redundant server deployments available in
ProVision.
Standby Server
The Standby Server provides the following capabilities:
1. Warm standby server redundancy with manual failover.
2. Active server database backed up to standby server at regular time interval,
typically once per day.
3. Performance and configuration change data since the last backup is lost
when the active server fails. If backup is daily, hence up to a day’s worth of
data is lost.
4. Both servers are active (although there are restrictions with standby server),
enabling the standby server to be used to support an increased number of
Client sessions.
See the section Managing Standby Servers on page 205 for related topics and instruc-
tions.
The Redundancy Controller provides the following capabilities:
1. Hot standby server redundancy with automated failover.
2. Server databases synchronized in near-real-time through database
replication process, ensuring minimal loss of data when the main server
fails.
3. Only one of the servers is fully active at a given time, although switching
occurs quickly to the peer server when the main server fails.
4. Redundancy Controller application license required.
5. Users can lock and unlock the Redundancy Controller easily. Locking turns
off data replication and automated failover; users can manually restart
ProVision. Unlocking turns on data replication and automated failover, so
that the system is once again operating as a fully redundant ProVision.
See the section Hot Standby Server Redundancy on page 217 for related topics and
instructions.
WARNING: If y ou want to use both the Redundancy C on-
tr ol l er and the Standby Ser v er , the Standby Ser v er
614-330053-001 APRIL 2014 203

CHAPTER 10. REDUNDANT SERVER DEPLOYMENTS
must be i nstal l ed on a ser v er that i s separ ate f r om the

two Redundancy C ontr ol l er ser v er s.
204 AVIAT NETWORKS

Managing Standby Servers

The Standby Server provides the following capabilities:
1. Warm standby server redundancy with manual failover.
2. Active server database backed up to standby server at regular time interval, typ-
ically once per day.
3. Performance and configuration change data since the last backup is lost when the
active server fails. If backup is daily, hence up to a day’s worth of data is lost.
4. Both servers are active (although there are restrictions with standby server),
enabling the standby server to be used to support an increased number of Client ses-
sions.
ProVision includes the following functions to help manage standby servers:

l About Primary and Standby Servers on page 205
l DCN Bandwidth Requirements for a Standby Server on page 207
l Standby Server Configuration Prerequisites on page 206
l Configuring Server Type as Primary on page 209
l Configuring Server Type as Standby on page 210
l Standby Server Deployment on page 12
l Standby Server Deployment: Sharing or Separate Hardware on page 13
l Standby Server with WAN and Separate Hardware on page 14
l Synchronizing Primary Server and Standby Server Databases on page 208
About Primary and Standby Servers

For ProVision, administrators have the option of configuring ProVision to have a
Primary and a Standby server. The two server types are:
l Primary - The ProVision server currently in use by operators. New devices are
deployed, network changes are implemented, and performance data is
collected.
l Standby - A ProVision server held on standby as an operations backup for the
Primary server. Because the Standby server is not in daily use, certain
functions are disabled, as noted below.
Table 10-1. Enabled and Disabled Functions by Server Type
Primary Server Standby Server

NBI Enabled Disabled
614-330053-001 APRIL 2014 205

Primary Server Standby Server

Performance Data Col- Enabled Disabled
lection
Event Collection Enabled Enabled
NBI and performance data are still shown as enabled in the Standby clients, even
though these functions are disabled on the server.
CAUTION:Caution: Do NOT use any Standby clients to deploy devices
or change system or network configuration.
F or exampl es of Pri mary and Standby networks, see St and by

Serv er Dep loy ment on p age 12.
There i s onl y one Pri mary and one Standby server per net-
work. Both the Pri mary and the Standby server must use the
same operati ng system, ei ther Wi ndows or Sol ari s.
WARNING: If Wi ndows oper ati ng sy stems ar e used, i t
i s r ecommended that both the Pr i mar y and Standby
ser v er must use the same v er si on f or Wi ndows, ei ther
32 or 64 bi t. F or r equi r ements, go to S tandb y S e rv e r
C onfiguration Pre re q uisite s on page 206
Standby Server Configuration Prerequisites

Each ProVision Standby server must have the ProVision installation configured with
the following:
l ProVision License: The Standby server must be set up with the same license
capability as the Primary server that it is linked to. This includes NBI, node
count, and other additional licenses. See Licensing ProVision on page 99.
l Matching ProVision Versions: If your ProVision installation includes both
Primary and Standby servers, both types of server must have the same version
of ProVision installed. If Windows operating systems are used, it is
recommended that both the Primary and Standby server must use the same
version for Windows, either 32 or 64 bit. If you upgrade one server, you must
upgrade the other server. Upgrade both your Primary and Standby servers at
the same time. See About Upgrading ProVision on page 1.
l DCN Bandwidth: Set the DCN bandwidth based on the server requirement.
See DCN Bandwidth Requirements for a Standby Server on page 207.
l Ports: Set the ports to match the Primary server's ports. See Changing FTP
Server Port on page 111 and Network Communication Ports for Firewalls on
page 18.
You also need to note the IP address or Host name of the Standby Server. This is
used for: Synchronizing Primary Server and Standby Server Databases on page 208.
Once you have set up the server with the license, DCN bandwidth, and FTP ports,
and noted its IP address or Host name, you are ready to confirm it as the Standby
206 AVIAT NETWORKS

Server. To configure the Primary Server, see Configuring Server Type as Primary on
page 209.
F or i nformati on on i nstal l i ng a Standby Server, see St and by
Serv er Inst allat ion and Maint enance on p age 58.
WARNING: If y ou want to use both the Redundancy C on-
tr ol l er and the Standby Ser v er , the Standby Ser v er
must be i nstal l ed on a ser v er that i s separ ate f r om the
two Redundancy C ontr ol l er ser v er s.
DCN Bandwidth Requirements for a Standby

Server
Specific DCN bandwidths and open ports are required to support database syn-
chronization between the Primary Server and the Standby Server. (See Synchronizing
Primary Server and Standby Server Databases on page 208 for this procedure).
The DCN bandwidth intensive aspect of database synchronization occurs when the
Primary Server database backup file is transferred to the Standby Server. You need to
provide enough DCN bandwidth to minimize the transfer time.
Database backup i s transferred i n a si ngl e compressed fi l e, to
mi ni mi ze the burden on the DCN.
DCN Requirements
Because the required DCN bandwidth is based on the database backup file size and
the time to perform the transfer, we recommend the following bandwidths for dif-
ferent size network deployments.
Deployment with 15 Deployment with

Compressed
min. Ethernet Per- 15 min. Ethernet Max. Trans- Min. DCN
Database File
formance Data col- Performance Data fer Time Bandwidth
Size
lection enabled collection disabled
>1GB 2,000+ devices 2,000+ devices 10+ minutes 15 Mbit/s
500MB - 1GB 1,000+ devices 2,000+ devices 10 minutes 15 Mbit/s
100MB - 500+ devices 1,000+ devices 10 minutes 8 Mbit/s
500MB
<100MB <200 devices 500+ devices 10 minutes 2 Mbit/s
The database backup compressed file (transit.zip) is saved to the directory ProVi-
sionserver/mysql/backup on the Primary Server.
614-330053-001 APRIL 2014 207

Synchronizing Primary Server and Standby

Server Databases
Synchronizing a backup of ProVision sets up a Primary Server to forward database
backups to the Standby Server. Once this is set up, every time the Primary Server
runs a backup, the backup files are forwarded via FTP to the linked Standby Server.
The Standby Server then automatically unpacks and installs the backup file. This
ensures that the Standby Server is ready to be used at any time, with the most
recently backed up database.
To enabl e thi s, see C onfigu ring Serv er Ty p e as Primary on p age
209 .
This section describes what happens when backup files are transferred from the
Primary server to the Standby server. It also notes what happens when the transfer
process fails.
Normal Transfer Process

The normal transfer process is as follows:
1. The Primary Server saves its scheduled backup. The backup file is zipped into a file
named transit.zip and saved to the location ProVi-
sionServer/mysql/backup.
2. The Primary Server starts to send the transit.zip file. An event showing that
the backup transfer is in progress is displayed:
3. The transit.zip file is transferred to the Standby Server.

4. Once the transfer is complete, this event is cleared automatically.
5. The Standby Server automatically unzips the file.
6. When that is complete, the Primary Server sends a resync command to the
Standby Server.
7. The Standby Server is stopped. Active Client sessions on the Standby Server are
closed.
8. The transferred database is restored, and the Standby server restarts. New Client
sessions can be opened on the Standby server.
Failed Transfer Process

If the database backup fails to transfer, an event is raised:
208 AVIAT NETWORKS

This event has to be cleared by the operator.

If the transfer fails, examine the log files for both the Primary and Standby Server to
identify the cause of failure.
CAUTION:The Primary Server must have Scheduled Backup enabled.

The frequency and type of scheduled backup on the Primary Server
determine when the database gets transferred to the Standby Server.
See Scheduled Backup Procedure on page 186 .
CAUTION:If you are synchronizing the Primary Server and the

Standby Server by running a manual backup, allow the manual
backup to run completely. Do not run the manual backup a second
time: the Standby Server needs time to process the first manual
backup and its related restarts.
The mi ni mum DCN bandwi dth must be avai l abl e between

Pri mary and Standby servers. See DC N Band wid t h Requ ire-
ment s for a St and by Serv er on p age 207.
Configuring Server Type as Primary

You need to identify servers as either Primary or Standby. These instructions describe
how to set up the Primary server.
Procedure
1. Start with the ProVision user interface on the Primary server.
2. Set up Scheduled Backup (Scheduled Backup Procedure on page 186 ).
3. From the menu bar, select Administration > Server Redundancy. The Server
Redundancy window is displayed. It should show the System Type as Primary.
4. Check the box Enable Backup to Standby.
614-330053-001 APRIL 2014 209

5. In the Standby field, enter the IP address for the Standby Server.
6. Click OK.
7. The server is now set up as the Primary Server. It will now send all backups to the
Standby Server.
See al so Sy nchronizing Primary Serv er and St and by Serv er Dat a-
bases on p age 208.
Configuring Server Type as Standby

You need to identify servers as either Primary or Standby. These instructions describe
how to set up the Standby server.
Procedure
1. Start with the ProVision user interface on the server that you are configuring.
Redundancy window is displayed. It should show the System Type assigned to the
server.
3. To change the server type, click the System Type button. Select Standby.
4. Click OK.
5. The server is reconfigured as the Standby server. In the lower left corner of the
ProVision Client interface, text appears indicating that this is the Standby server.
When you set a server to be a Standby server, i n the Server

Redundancy wi ndow, the Enabl e Backup to Standby and
Standby Ser v er val ues are grayed out. These are onl y
enabl ed for a Pri mary Server.
210 AVIAT NETWORKS

Primary Server Failure: Activating a Standby

Server
If the Primary server fails, the Standby Server needs to become the temporary
Primary Server. When you do change the server status from Standby to Primary, all
of its disabled functions come on line, and the Standby Server takes over as the tem-
porary Primary Server.
The Standby Server uses data from the most recent backup.
Note that performance data or system changes may be mi ss-
i ng, based on how frequentl y backups are schedul ed.
Procedure
1. Start with the ProVision user interface on the Standby server.
Redundancy window is displayed.It should show the System Type as Standby.
3. Click the System Type button Primary. Uncheck Enable Backup to Standby.
Then, click OK.
4. The Standby server is reconfigured as the temporary Primary server. This process
takes approximately 15 seconds. When this happens, any disabled functions, such as
performance data collection and NBI, are fully enabled.
5. Review the server configuration, and make changes as required.
6. Operate the system in this new configuration until you are ready to restore the
long-term l Primary server. See Primary Server Restoration on page 211.
Next Topic:
Primary Server Restoration on page 211
Primary Server Restoration

Once a problem requiring use of the Standby server is resolved, you need to restore
the Primary server as your center of system operation. You also need to decide when
614-330053-001 APRIL 2014 211

and how to restore the servers to their original roles. There are two options:
l Simple Restoration -If the Primary Server has only been out of use for a few
hours, or switched off, restart the Primary Server and switch the other server
back to Standby mode.
l Database Restoration - If the Primary Server has been offline for a day or
longer, you can update its database from the Standby Server.
This graphic shows the differences between normal operation, operation when the
primary server is down, and the database restoration process.
This set of instructions describes how to do the Database Restore for the Primary
server.
Procedure
1. Clearly identify which server is the long-term Primary server, and which server is
the long-term Standby server. Obtain both of their IP addresses for reference.
2. Start with the ProVision user interface on the server in use as the temporary
Primary server.
3. From the menu bar, select Administration > Redundancy Configuration . The
Redundancy Configuration window is displayed. First, check Enable Backup to
Standby. Then, enter the Standby Server field IP address; this should match the
server that you use for the long-term Primary server.
4. Go to the long-term Primary server. In the Redundancy Configuration window, In
the Redundancy Configuration window, change the System Type to Standby. This
is now a temporary Standby server.
212 AVIAT NETWORKS

5. On the server being used as the temporary Primary server, run a manual backup.
This is saved to both the temporary Primary server and the temporary Standby
server.
6. The temporary Standby server restarts after receiving the backup. When the tem-
porary Standby server has restarted, open one of its ProVision clients.
7. Go to the temporary Primary server. In the Redundancy Configuration window,
change the System Type to Standby.
8. Go to the temporary Standby server. The Redundancy Configuration window
should show the System Type as Standby.
9. Click the System Type button Primary. Check the box to Enable Backup to
Standby, and enter the Standby Server IP address.
10. This server is reconfigured as the Primary server. When this happens, any dis-
abled functions, such as performance data collection and NBI, are fully enabled.
11. In the Redundancy Configuration window, change the Standby Server IP
address back to the long-term Standby server.
If The Primary Server Fails: Managing and

Restoring After Failover
If the ProVision Primary Server fails, users are alerted with alarms. This procedure
describes:
l How to check these alarms
l How to enable the Standby Server as the temporary Primary Server
l How to restore the Primary Server
Checking For "Primary Server Is Unavailable" Alarm

If the Primary Server is unavailable:
l The Standby Server will display an alarm saying that the Primary server is
unavailable in the Event Browser window.
l The Standby Server will also send an Email / SMS with the same alarm:
614-330053-001 APRIL 2014 213

Enabling Standby Server as Temporary Primary Server

When the Primary Server is unavailable, an administrator needs to enable the
Standby Server, as shown:
To do this:
1. Login to the Standby Server.
2. In ProVision, select Administration > Server Redundancy. Change the
System Type from Standby to Primary. Do not check“ Enable Backup to
standby” at this point.
3. The Standby Server is now functioning as the Primary Server. It will start
sending Emails/SMS when alarms are received and/or cleared.
Restoring The Primary Server

Primary server is back in service, and we need to Transfer all the database from the
temporarily Main server to the original Main server.
1. Log back in to the Primary Server, which has been offline. Open ProVision.
Configure it as the Standby Server, in the Administration > Server
214 AVIAT NETWORKS

Redundancy screen, as shown below. Also, note the IP address of this

Server.
2. Log back into the temporary Primary Server/former Standby Server. In the
Administrator > Server Redundancy screen, check the “Enable Backup
to Standby” box, and enter the IP address of the desired Primary Server
from step 1.
3. Go to Administration-> Database Backup -> Manual Backup and run a

Manual Backup. This will backup all the alarms including the newer ones
that came to the system while the Primary Server was offline.
4. When the Manual Backup finishes, it will be transferred to the other server.
614-330053-001 APRIL 2014 215

5. Login again to the Primary Server and verify that the newer alarms are
appearing.
6. Re-configure this as the Primary Server.
7. Re-configure the other server as the Standby Server.
216 AVIAT NETWORKS

Hot Standby Server Redundancy

The ProVision Redundancy Controller is a separate software module that enables
standby server management of your ProVision network.
The Redundancy Controller provides the following capabilities:
1. Hot standby server redundancy with automated failover.
2. Server databases synchronized in near-real-time through database replication pro-
cess, ensuring minimal loss of data when the main server fails.
3. Only one of the servers is fully active at a given time, although switching occurs
quickly to the peer server when the main server fails.
With the Redundancy Controller, setting up your ProVision redundancy and servers
is simple. Log in and enter your server values into the Status, Configuration, and
Security screen. For configuration and setup details, see the following topics:
l About the Redundancy Controller on page 218
l Normal Operation of Redundancy Controller on page 222
l DCN Bandwidth and Latency for the Redundancy Controller on page 220
l Logging Into the Redundancy Controller on page 224
l Redundancy Controller Status Screen on page 225
l Redundancy Controller Configuration Screen on page 229
l Redundancy Controller Security Screen on page 231
l Troubleshooting the Redundancy Controller on page 233
l See also Installing and Uninstalling the ProVision Redundancy Controller on
page 60
The Redundancy Control l er i s a l i censed feature. I f you oper-

ate the Redundancy Control l er wi th an expi red tri al l i cense,
the functi onal i ty i s enabl ed, but i t does not accept ProVi si on
Cl i ent connecti ons. Pl ease contact your sal es representati ve
about the Redundancy Control l er l i cense.
614-330053-001 APRIL 2014 217

About the Redundancy Controller

The Redundancy Controller provides automatic failover ability so that when a prob-
lem occurs with the Active Main Server (or there is a network outage), the Dormant
Server will automatically become the currently Active Main Server. In a failover scen-
ario, ProVision Clients will have to be manually switched to the New Active Main
Server.
The Redundancy Controller consists of two identical server machines. The two serv-
ers can be located at different sites. The two servers are:
l Active Main Server – The ProVision server currently in use by ProVision
Clients. New devices are deployed, network changes are implemented, and
performance data is collected.
l Dormant Server – A server currently replicating data from the Active Main
Server in near real time. This server will automatically become the new Active
Main Server should the existing Active Main Server suffer a power loss or a
network outage.
The Active Main and Dormant Servers host their own web servers on port 9080.
They are configured and monitored using the Redundancy Controller software, via a
web browser interface. When the Redundancy Controller Installer software is first
installed on each of these servers they must be configured to act as the Active Main
Server and Dormant Server. See Installing and Uninstalling the ProVision Redund-
The table below shows the Functions by Server Type.
Active Dormant Server
Main (ProVision Disabled)
Server
(ProVisi-
on
Enabled)
Performance Data Collection Enabled Replicated in real time.
Resynchronized on star-
tup
Event Collection Enabled Replicated in real time.
Resynchronized on star-
tup
NBI, backup, Generic Device Enabled Resynchronized daily on
Packages, software, repository the hour and on startup
licenses, maps
Whenever there is a change to the ProVision on the Active Main Server, that change
is replicated to the Dormant Server in near real time.
The dataset (either the ProVision database or External files) is copied from the Active
Main Server to the Dormant Server. This happens when the Dormant Server is
218 AVIAT NETWORKS

started normally or when there is a failover event. Data external to the database is
synchronized every 24 hours at a configurable time of day.
Note the following:
1. ProVision clients can only connect to the Active Main Server. It is not
possible to connect to a Dormant Server.
2. There is only one Active Main Server and one Dormant Server per network.
Configuration Prerequisites
l The Redundancy Controller needs to be installed on both the Active Main
Server and Dormant Server. Both the Active and the Dormant Server must be
installed on the same operating system, either Windows or Solaris. See
Installing and Uninstalling the ProVision Redundancy Controller on page 60.
l The Active Server and the Dormant Server each must be set up with the same:
l ProVision Versions.
l License Capabilities . This includes Redundancy, NBI,
node code, and other additional licenses. See Licensing
l DCN Bandwidth and Latency. See DCN Bandwidth and
Latency for the Redundancy Controller on page 220.
l Ports. See Network Communication Ports for Firewalls on
page 18
614-330053-001 APRIL 2014 219

DCN Bandwidth and Latency for the

For the Redundancy Controller, database and file synchronization between the Active
and Dormant servers requires specific DCN bandwidths and latency. The systems
require enough DCN bandwidth and latency to optimize the amount of time required
for database and file resynchronization.
DCN Requirements
The required DCN bandwidth and latency is dependent on the size of the ProVi-
siondatabase, and the size of the external database files. Latency is the main factor
in minimizing the transfer times. If the latency time between the Main Active Server
and the Dormant Server is high this significantly increases the transfer times.
The table below details the time required for the Database and external files to fully
resynchronize between the Active and Dormant servers using the specified band-
width and latency criteria. These times were recorded using an uncompressed data-
base of 2.5 GB (2000+ devices) and uncompressed external files of 0.8 GB (40000+
external files).
DCN Band- Latency Database Syn- External File Syn- Effective Bandwidth
width (ms) chronization Time chronization Time (Mbps)
(Mbps) + Catchup Time (mins)
(mins)
10 0 30 10 9
10 10 40 15 7
10 100 200 30 1
20 0 20 7 18
20 10 30 10 9
20 100 200 25 1
Note the following:

l Database Synchronization Time = amount of time required for the
Dormant Server to transfer and load into its database a copy of the Active
Main Servers database.
l External File Synchronization Time = amount of time required for the
Dormant Server to transfer a copy of the Active Main Servers external files.
l Catchup Time= amount of time required for the Dormant Server, once it has
transferred and loaded the Active Servers Database, to catchup and replicate
any database changes that have since occurred on the Active Main Server
during this transfer.
220 AVIAT NETWORKS

l Effective Bandwidth = actual bandwidth calculated to transfer the database

from the Active Server to the Dormant Server under latency.
l The transfer times are also inclusive of local processing times, which include
factors such as compressing and uncompressing files, as well as time required
to transfer across the network.
614-330053-001 APRIL 2014 221

Normal Operation of Redundancy

Controller
Under normal operation, minimal supervision of the Active Main Server and Dor-
mant Server is required. Normal operation is shown in this diagram and defined
below:
l ProVision is running on the Active Main Server collecting performance data.

ProVisionClients connect to the Active Main Server. ProVisionClients cannot
connect to a Dormant Server.
l All database information from the ProVision Active Main Server is replicated to
the Dormant Server in near real time. All external database information such
as NBI is synchronized to the Dormant Server daily at a scheduled time.
l The Redundancy Controller software on both servers monitors for failover
events. The Dormant Server will failover to Active if there is a problem with the
current Active Main Server. In a failover event all existing clients will need to
be manually reconnected to the New Active Main Server.
l The Redundancy Controllers on both the Active Main Server and Dormant
Server record information in their log files. Also, certain events are sent out as
SNMP traps. Details of the SNMP trap destination can be configured on both
servers.
222 AVIAT NETWORKS

Locked Operation of the Redundancy

Controller
Operators typically lock a system to perform maintenance on the active Server that
requires a restart of ProVision. Locking allows this and prevents the dormant server
from failing over to become the active main server whilst locked.
The locked state of the system is shown in this diagram and defined below:
In a locked system the following features are disabled:

l Redundancy - The dormant server will never failover and become the active
server if the Active Server fails. If the Active Server fails in a locked system the
Redundancy Controller attempts to restart it.
l Replication - The dormant server is not replicating any data from the active
server. This includes database updates and or daily files.
l Manual Switching and Unlatching – From the web controller the user is
unable to switch and manually force a failover of the active and dormant
servers. The user is also unable to unlatch a dormant system.
In a locked system the web controller will have the following properties:
l Restart Button – On the active side a restart server button is enabled. This
allows the user to manually restart the active ProVision.
l Unlock Button – On both sides (active and dormant) an unlock button is
enabled. This allows the user to bring the system out of its locked state and
enable the features described above.
614-330053-001 APRIL 2014 223

l Switch and Latch Buttons are disabled – Whilst locked the user is unable
to force an active server switch or unlatch a dormant server.
l Active Server is Locked – The active server will display the status “Active
Main Server Is Locked”
l Dormant Server is Locked – The dormant server will display the status
“Dormant Is Locked”
I n a l ocked System exi sti ng cl i ent sessi ons remai n connected
to the Acti ve ProVi si onand cl i ents can establ i sh new sessi ons
to the acti ve ProVi si on.
CAUTION:In a locked System, if the restart server button is clicked,
existing client sessions will be terminated and only when the active
ProVision restarts can client sessions be re-established.
Logging Into the Redundancy Controller

Logging into the Redundancy Controller via a web browser is simple.
You must be an Admi ni strator user to access the Redundancy
Control l er. I f you requi re access and do not have i t, pl ease
check wi th your ProVi si on admi ni strator.
CAUTION:The web browser interface must have Javascript enabled
for you to use the Redundancy Controller.
WARNING: The Redundancy C ontr ol l er i nter f ace i s not

compati bl e wi th the web br owser Inter net Expl or er 9.
We r ecommend F i r ef ox or Inter net Expl or er 8.
1. In the Start menu, click on the ProVision Redundancy Controller link

from the ProVision Redundancy Controller Menu.
2. Enter your user name and password.
The login screen can also be accessed by entering the URL of the Redundancy Con-
troller IP address or server name, for example: http://pvwenz04:9080/rc
3. The Redundancy Controller displays.
224 AVIAT NETWORKS

Redundancy Controller Status Screen

From the Redundancy Controller Status screen, you can:
l Monitor and change the System State
l Switch the Active Server to become the Dormant Server
l Unlatch a Dormant Latched Server
Table 10-2. Status Screen Values
Item Value
System State
Local Status Status of the local server.
Peer Status Status of the remote peer server
Control
Switch/Unlatch Click Switch to change the local server from Active
to Dormant or vice versa. If the peer server is Act-
ive you cannot switch the local server to Active,
because you cannot manually switch to two Active
servers.
NOTE: When you click the Switch button, a mes-
sage appears, asking you to confirm the change.
Click Yes to confirm.
Click Unlatch to move the local server out of the
Dormant Latched state. This button only becomes
available when the local server is in the Dormant
Latched state.
Locking
614-330053-001 APRIL 2014 225

Item Value
Lock Server Click Lock Server to lock the system. This turns
off the automatic failover and replication functions.
Note that:
- Clients can still connect to an active locked
server.
- While the system is locked, you cannot manually
switch the active server from the browser.
CAUTION:When the system is locked, the
dormant server is not replicating data from the act-
ive server, nor is it monitoring for failover events. If
the active server fails when the system is locked,
the dormant server will not become the active
server, as it would have on a non-locked system.
Instead, the active server will restart and attempt
to become active again.
Restart If the Restart button is visible, click it to restart
the active ProVision Server manually, while it is
locked. This restarts the active ProVision server; all
existing clients will be disconnected and the active
ProVision restarts as Locked. Redundancy, rep-
lication, and automatic failover are still turned off.
The system must be Unlocked to reactivate those
functions.
Unlock Server If the Unlock Server button is visible, click it to
unlock the system. This activates automatic fail-
over and replication so that the system is fully
redundant and replicating.
The Redundancy Control l er provi des a Web Brower I nterface

that can be accessed from both Servers. I f one Server di s-
pl ays “Local Status: Acti ve Mai n Server” and Peer Status “Dor-
mant”, then the other server wi l l di spl ay “Local Status:
Dormant” and Peer Status “Acti ve Mai n Server”.
The table below describes a list of statuses (Local Status and Peer Status) that typ-
ically appear on the status page in the Redundancy Controller Web Interface , fol-
lowed by a second table that lists all available statuses.
Table 10-3. Frequently Seen Status
Local Status Peer Status Description

Acquiring Peer Acquiring Peer Typically the Servers have not been con-
HeartBeat HeartBeat figured within correct Peer IP addresses so
they cannot communicate with each
other.
226 AVIAT NETWORKS

Local Status Peer Status Description

Active Main Active Main This state is not allowed under normal oper-
Server Server ation but can occur when there is a com-
munication loss between Active and
Dormant, causing both servers to become
Active. As soon as the communication is
restored and the servers can communicate
with each other, the Most recent Active
Main Server will automatically go back to
being in Dormant State, and resyn-
chronize with the Active server again.
Active Main Dormant Normal operation – The Active and Dor-
Server mant Servers are in sync and the Active is
replicating to the Dormant. ProVision
Server is running on the Active and ProVi-
sion Clients can connect to this Server.
Dormant Latched Dormant Latched This is typically seen after an installation of
the Redundancy Controller system - Both
Servers will be in Dormant Latched. ProVi-
sion server is not running. The Admin-
istrator needs to perform a switch on the
correct Server to Make it Active. Then, the
Administrator will need to unlatch the
other dormant server so that it goes into
Dormant State so that the Servers are run-
ning in normal operation
Resynchronising Resynchronising The Active Server and Dormant Server are
Dormant Server resynchronising the ProVision Server data-
base from Active to Dormant. This occurs
each time the Dormant Redundancy Con-
troller is started either manually or auto-
matically on an error condition.
Resynchronising Resynchronising The Active Server and Dormant Server are
Files with Dor- Files resynchronizing the external files from Act-
mant Server ive to Dormant. This occurs each time the
Dormant Server is started either manually
or automatically on an error condition. It
also occurs daily as configured in the Web
Browser on the Dormant Server (See File
Synchronisation Hour on the Con-
figuration tab)
Table 10-4. All Available Redundancy Controller Statuses:
Status Description
Acquiring Peer The Redundancy Controller is monitoring its Peer to check
Heartbeat its status
614-330053-001 APRIL 2014 227

Status Description
Active Main Server The Active Redundancy Controller is currently replicating
and providing redundancy. ProVision Server is running and
ProVision Clients can be connected to this Server.
Active Main Server The system is locked. There is no redundancy, automatic fail-
is Locked over, or data replication. See the table above, Status Screen
OR Values, for Unlock and Restart actions.
Dormant is Locked
Active Server Fail- The Active Redundancy Controller has detected a self fail
ing condition and will restart. It will restart in either Dormant
Latched or Dormant (depending on whether it is configured
with Dormant Latched checked).
Dormant The Dormant Redundancy Controller is currently replicating
any changes on the Active Server ProVision system.
Dormant Latched The Redundancy Controller has started but is in a Latched
state. This means there is no replication of data between
itself and its Peer. It also means automatic failover is cur-
rently disabled. When in Dormant Latched State the
Redundancy Controller can be Unlatched into Dormant
State by Unlatching it in the Redundancy Controller Web
Browser Interface .
Failing Over The Dormant Redundancy Controller has lost com-
munication with its Peer. If this loss in communication con-
tinues for longer than the failover window then the
Dormant Redundancy Controller will automatically switch to
the Active Redundancy Controller
Initialization The Redundancy controller is starting up and initialising
Resynchronising The Dormant Redundancy Controller is currently Resyn-
chronising with the Active Redundancy Controller to ensure
the Dormant Server is up to date with the Active Servers
ProVision database.
Resynchronising The Active Redundancy Controller has received a request
Dormant Server from the Dormant Redundancy Controller and is resyn-
chronising the ProVision Server database.
Resynchronising The Dormant Redundancy Controller is currently Resyn-
Files chronising with the Active Redundancy Controller to ensure
the Dormant Server is up to date with the Active Servers
ProVision external files.
Resynchronising The Active Redundancy Controller has received a request
Files With Dormant from the Dormant Redundancy Controller and is resyn-
Server chronising the ProVision Server external files.
Server Not The Redundancy Controller is not licensed on this Server. No
Licensed Replication or Redundancy is enabled in this state. Redund-
ancy is a Licensed Feature of the ProVision server.
Starting Up Active The Redundancy Controller is starting up as the Active
Server.
228 AVIAT NETWORKS

Status Description
Unknown State The Redundancy Controller is unable to communicate with
its Peer and therefore its Peer State is Unknown. Check in
the Redundancy Controller Web Browser Interface that the
Peer IP address is correct.
See also:
Redundancy Controller Configuration Screen

From the Redundancy Controller Status screen, you can:
l Enter the Peer Server IP values to pair the local server with its remote peer
server
l Set up file synchronization frequencies
l Set up failover times and heartbeat timeout
l Set up trap destinations
l Set up the Server to enter the Dormant Latched State when applicable
614-330053-001 APRIL 2014 229

Item Value
System
Peer IP Address IP address of the peer server.
Peer FTP Port FTP port of the peer server.
File Files are synchronized between the local and peer servers once
Synchronization - per day at this hour. Enter a value between 0 and 23.
Hour
Server Latched Check this to configure the server for entering into the "Dor-
mant Latched" state when it is transferring from the Active
state.
Failover
Heartbeat If the heartbeat synchronization fails, the timeout is the period
Timeout of time in seconds between retries. The default value is 5
seconds. This value should be the same on the peer.
230 AVIAT NETWORKS

Item Value
Heartbeat Retries If the heartbeat synchronization fails, the retry is the number
of times synchronization is attempted again. This value must
be the same on the new peer. The default value is 5 retries.
The failover window is defined in seconds by (heartbeat
timeout * heartbeat retries). If no heartbeat is received by the
dormant system during this window the dormant system will
failover and become the active system automatically.
Trap Destinations
Trap IP Address IP address for trap listener.
Trap Port Port ID for trap listener.
See also:
Redundancy Controller Security Screen

From the Redundancy Controller Security screen, you can:
l Change the Administrator password.
l Configure login authentication to use Primary and Secondary Radius Servers,
instead of local authentication.
l Click the Apply button at the bottom of the screen to save these changes.
614-330053-001 APRIL 2014 231

Item Value
Security
Password Change the password for the Administrator user.
Confirm Passwor- Confirm the changed password for the Administrator
d user.
Radius Server
Check Box Link the Redundancy Controller to the Radius Server by
checking this box.
Shared Secret Enter the "shared secret" password for the Radius
server.
Confirm Shared Confirm the "shared secret" password for the Radius
Secret server.
Primary Radius Enter the following values for the primary Radius
server:
l Server IP address
Secondary Enter the following values for the secondary Radius
Radius server:
l Check the box to enable this server if
required
l Server IP address
See also:
232 AVIAT NETWORKS


Troubleshooting the Redundancy Controller

This section describes how to resolve problems that may occur with the Redundancy
Controller.
Dormant Server Power Loss or Shutdown

The Active Server can no longer replicate data to the Dormant Server.
The Redundancy Controller Web Browser Interface on the Active Server will show a
status of:
l Local Status: Active Main Server
l Peer Status: Unknown State
Impact
l Minimal Impact while the Dormant Server is off line
l No Redundancy or Replication available until the Dormant Server is back
online.
l No outage as ProVision is monitoring the Network on the Active Server.
l Client sessions will still be connected to the Active Server
Recovery Actions
When the Dormant Server is back on line it will automatically start resynchronizing
with the Active Server and provide redundancy and replication.
614-330053-001 APRIL 2014 233

Login to the Redundancy Controller Web Browser Interface on the Active Server and
ensure it shows a status of:
l Peer Status: Dormant
The system is now back to normal operation. See Normal Operation of Redundancy
Active Server Power Loss or Shutdown

The Active Server has a power loss or shuts down, losing data transmission to both
the Clients and the Dormant Server.
After the failover window time elapses, the Dormant Server fails over to become the
New temporary Active Server.
The Redundancy Controller Web Browser Interface on the New temporary Active
Server will show a status of:
234 AVIAT NETWORKS

Impact
l Outage of ProVision Server until the Dormant Server becomes the New
temporary Active Server.
l Client Sessions will become disconnected.
l The time of outage is dependent on two factors: 1) the time taken for Dormant
Server to failover (failover window). 2) the time taken for the Dormant Server
to start up as the New temporary Active Server.
The time taken for the Dormant Server to start up as the New temporary Active
Server is dependent on the size of the database and the specification of the Server
machine.
This outage is typically less than 2.5 minutes in which there will be a loss in the col-
lection of Performance data and events.
Recovery Actions
Clients will be disconnected and will need to be reconnected to the New temporary
Active Server, once it has started up.
When the Original Active Server is back on line it will start resynchronizing with the
new temporary Active Server, and becomes the New Dormant Server.
Login to the Redundancy Controller Web Browser Interface on the New Dormant
Server and ensure it shows a status of:
l Local Status: Dormant
l Peer Status: Active Main Server
The system is now back to normal operation but has switched from the original con-
figuration. The initial Active Server is now the New Dormant Server and the initial
Dormant Server is now the New Active Server.
The administrator needs to decide when to switch back to the original configuration.
(This process requires another service outage, as already described).
To do this:
614-330053-001 APRIL 2014 235

Login to the Redundancy Controller Web Browser Interface on the New Active Server
and click the switch button. This will restore the system back to its original state.
Ensure the Browser Interface shows a status of:
l Local Status: Dormant
l Peer Status: Active Main Server
The system is now back to normal operation. See Normal Operation of Redundancy
Network Communication Failure Between Active &

Dormant Servers
Because of a loss in communication there are two Active ProVision Systems trying to
monitor and collect data from the Network.
The Dormant Server fails over to become the New temporary Active Server.
The Redundancy Controller Web Browser Interface on the New temporary Active
Server will show a status of:
The Redundancy Controller Web Browser Interface on the Original Active Server will
show a status of:
Impact
l There should be no loss in the collection of Performance data and Events,
unless connectivity is lost with the Radio network.
l Client Sessions should still be connected unless they lose connection with the
Server.
236 AVIAT NETWORKS

l Any data that was collected by the most New Active Server, but not collected
by the Original Active Server, during this loss in communication, will be lost.
Recovery Actions
When the network communication is restored the New Active Server automatically
goes back into the dormant state whereby it will start Resynchronizing again with
the Original Active Server. Login to the Redundancy Controller Web Browser Inter-
face on the Original Active Server and ensure it shows a status of:
l Peer Status: Dormant
The system returns to normal operation. See Normal Operation of Redundancy Con-
troller on page 222.
614-330053-001 APRIL 2014 237

Using Both the Redundancy Controller

and the Standby Server
If required, networks can be configured to use both the ProVision Redundancy Con-
troller system and the Standby Server system. When both are deployed together, this
provides the most effective data redundancy and recoverability solution.
Requirements:
l Three servers are required: two for the Redundancy Controller system and one
for the Standby Server system.
l The Standby server system must be installed on its own separate server. The
ProVision Redundancy controller system must not be installed on this server.
This diagram shows a sample configuration with the three servers in place:
238 AVIAT NETWORKS

Chapter 11. Generic Device
Management
l Managing Generic Devices and Packages on page 240
l Add a New Package on page 242
l Re-Assigning a Package to a Generic Device on page 244
l Editing Package Information and Events on page 245
l Launching Generic Device Windows Applications from ProVision on page 276
CAUTION:These functions are for administration-level users with
advanced event management system skills. Users must be able to gen-
erate device events, access device MIBs, and possibly communicate
with device manufacturers.
Avi at Networks provi des consul ti ng servi ces for Generi c

Devi ce i ntegrati on. Pl ease contact your Avi at Networks sal es
and support staff for more i nformati on.
614-330053-001 4/04/2014 239

CHAPTER 11. GENERIC DEVICE MANAGEMENT
Managing Generic Devices and Packages

In ProVision, a “generic device” is an object that you deploy and configure. Some
objects, such as Eclipse and TRuepoint radios, have their configurations pre-defined
in ProVision. The Generic Device object allows you to deploy a device that has not
had its configuration pre-defined in ProVision.
There are two levels of Generic Device management. The first is deploying a generic
device, as described in the ProVision User Guide. After a device is deployed, an
administrator-level user needs to set up the events for the Generic Device. This is
done at the second level of Generic Device management, Package-level management.
Package-level management enables event collection and management for SNMP
devices. In ProVision, these SNMP devices are categorized as:
l Multiplexers
l Routers
l Switches
l Microwave Radios
l Power Supplies
l Site Alarm Units
l Base Stations
l Other ancillary equipment that provides an SNMP interface
Generi c Devi ce management at the Package l evel requi res an
addi ti onal l i cense. Pl ease contact Avi at Networks to acqui re
thi s l i cense.
A Package captures and collects configurations for a device type. It contains a
description and important alarm and event information, that are applied to all the
Devices assigned to it. Configuring a Package is a concise way to enter this data for a
range of Generic Devices.
The step-by-step process for assigning events to a Package is as follows:
1. Make sure that all generic devices are correctly assigned to the Package (see Re-
Assigning a Package to a Generic Device on page 244).
2. Using the MIB data for the devices and test devices, generate events against the
devices. OR, import the MIB data directly (see Importing Trap Mapping from a MIB
File on page 260).
3. Use the Trap Mapping function and the event data to generate event records in
ProVision for the devices in the Package (see Setting Trap Mapping to Identify Pack-
age Events on page 250).
4. If necessary, create any Match Rules for grouping events, or acknowledging dif-
ferent types of events (see Setting Matching Rules for Trap Mapping on page 263).
5. If necessary, create any custom events that are required for the Package (see Creat-
ing Custom Events for Packages on page 270).
240 AVIAT NETWORKS

6. Configure the resynchronization alarm events for the Package (see Configuring
Generic Device Resynchronization Alarms on page 268).
Once this process is complete, ProVision can identify and record these events for all
Generic Devices assigned to the Package.
You will also want to enable generic device craft tools for the fully enabled devices.
See Launching Generic Device Windows Applications from ProVision on page 276.
Recommendations
Configuring events for Packages, to apply to Generic Devices, takes time. Here are
some suggestions to help you save time as you enter and manage this data:
l Use the MIB files for devices as a reference and a source of event data.
l Set up major events first, using the Trap Mapping or MIB Import functions.
l You can load some data against a Generic Device from a two-column .CSV file.
This is helpful to create detailed trap mappings from device data, such as a
device alarm list.
Limitations
Events from Generic Devices cannot be Pre-Filtered.
The NBI number for Generic Devices defaults to zero. As a result, no different type
numbers are identified in NBI output.
When the Generic Device Management screen is open, you can only open new
screens from the Generic Device Management screen. If you want to perform addi-
tional system maintenance, or view event browsers, open another ProVision client.
After you have ful l y confi gured a Generi c Devi ce and/or a
Package, al l the event and confi gurati on i nformati on i s saved
when the ProVi si on database i s backed up, or when the user
exports the Package confi gurati on. Users can I mport the Pack-
age confi gurati on i nto another i nstal l ati on of ProVi si on and
benefi t from thi s saved confi gurati on.
GDS packages from Aviat Networks should never be edited. Editing them may inval-
idate your service agreement. For more details, see Loading a Generic Device Service
Package on page 246 .
614-330053-001 APRIL 2014 241

Add a New Package

Introduction
This procedure describes how to add a new Package that you will be able to edit. To
load a GDS Service Package provided by Aviat Networks, see Loading a Generic
Device Service Package on page 246.
Procedure
1. Log into ProVision as an Administrator.
2. In the Administration menu, select Generic Device Management. The Gen-
eric Device Management screen displays.
3. To add a new package, click the Add button.
4. The Add Package screen displays.
5. Select the Object Class for the Package from the drop-down menu. The Package
will be available to any new objects in the selected object class.
6. In the Package Name field, enter the name for the Package. Then, click OK.
7. The Package displays in the Generic Device Management screen. Note that this
screen shows the versions of currently loaded packages. The Object Class, Package
name, and Version are automatically displayed. An icon displays whether the pack-
age is available on an accessible disk, or whether it has been deleted (exclamation
point icon).
242 AVIAT NETWORKS

8. You can now:

l Assign the Package to new Generic Devices of that object class
l Modify the Package by Editing Package Information and Events on page 245,
including:
l Entering a Description for a Package on page 249
l Setting Trap Mapping to Identify Package Events on page 250
l Creating Custom Events for Packages on page 270
l Import and Export Package Data (.XML Files) on page 245
l Importing Trap Mapping from a MIB File on page 260
l Importing Trap Mapping from a .CSV File on page 262
614-330053-001 APRIL 2014 243

Re-Assigning a Package to a Generic

Device
When a user creates a generic device, they are prompted to add or select a Support
Package name. Linking a generic device to a Support Package provides ProVision
with the logic to translate Traps and polled MIB objects into events in the ProVision
events database.
Users can change the Package linked to a Generic Device. They can also add a Pack-
age to a Generic Device that did not receive a Package when it was created.
Procedure
1. In the Tree Viewer or Map View, right-click on the Generic Device that you want to
edit.
You can sel ect mul ti pl e Generi c Devi ces that bel ong to the
same Cl ass.
2. In the right-click menu, select Configuration . Then, select Object Package
Selection . The Object Package Selection screen displays.
3. From the Package drop-down menu, select the Package for the Generic Device.
Then, click OK.
4. The changes are saved for the device.
244 AVIAT NETWORKS

Editing Package Information and Events

For generic devices, you edit device information and events from the Edit Device
Package screen. Information entered here is applied to all devices in a Package.
From this screen, you can do the following to customize a Package for Generic
Devices:
l Import and Export Package Data (.XML Files) on page 245
l Loading a Generic Device Service Package on page 246
l Renaming a Package on page 248
l Entering a Description for a Package on page 249
l Setting Trap Mapping to Identify Package Events on page 250
l Managing Imported MIBs on page 259
l Importing Trap Mapping from a MIB File on page 260
l Importing Trap Mapping from a .CSV File on page 262
l Setting Matching Rules for Trap Mapping on page 263
l Configuring Generic Device Resynchronization Alarms on page 268
See also:
l Trap Mapping Example on page 254
l Match Rules Example: Multiple Trap Types on page 265
l Resynchronization and Custom Events Example on page 272
To dupl i cate an exi sti ng Package for edi ti ng, use the Save As
button i n the mai n Edi t Devi ce Package screen. Packages for
si mi l ar devi ces may have onl y mi nor di fferences.
Import and Export Package Data (.XML Files)

You can import and export Package data from ProVision. The Package data file is an
.XML file.
Using these imports and exports, users can:
l Move Package data between different ProVision installations
l Send Package data to Aviat Networks technical support
Procedure
1. In the Tree Viewer or Map View, select the Generic Device to edit.
614-330053-001 APRIL 2014 245

2. In the Administration menu, select Generic Device Management. Select and

double-click a package. The Edit Device Package screen displays.
3. To import an XML package, click the Import button.
4. A screen displays, prompting you to select a file to import. Select it and click OK.
5. The selected file is imported.

6. To export an XML file for a Package, click the Export button.
7. A screen displays, prompting you to enter a file name and folder location for the
file. Enter this information and click OK.
8. The Package data is exported to the file.
Loading a Generic Device Service Package

Aviat Networks can provide Generic Device Service (GDS) Packages. These are pre-
formatted .XML or .PKG files of data for specific Generic Device types. You can pur-
chase these from Aviat Networks with a features license (contact your sales
246 AVIAT NETWORKS

representative). This procedure describes how to download and install these pack-
ages.
CAUTION:Do not rename or edit a GDS package from Aviat Networks.
Some of these packages are in a file format, .PKG, that cannot be
edited; others are in editable .XML.
Procedure
1. Log into ProVision as an Administrator.
2. In the Administration menu, select Generic Device Management. The Gen-
eric Device Management screen displays.
3. To import a GDS .XML or .PKG package from Aviat Networks, click the Load but-
ton.
4. A screen displays, prompting you to select a file to import. Navigate to the file
folder that has the GDS .XML or .PKG package. Select it and click OK.
5. The selected package is loaded. It displays in the Package Details tab. The Object
Class, Package name, and Version are automatically displayed. An icon displays
whether the package is available on an accessible disk, or whether it has been deleted
(exclamation point icon).
614-330053-001 APRIL 2014 247

Renaming a Package
If you have created a Package, you can rename that Package. The name change is
applied to all devices assigned to the Package.
Package names can be up to 200 characters in length.
CAUTION:Do not rename or edit any GDS package from Aviat Net-
works. Some of these packages are in a file format that cannot be
edited; others are in editable .XML.
Procedure
2. In the Administration menu, select Generic Device Management. The screen
displays.
248 AVIAT NETWORKS

3. Select the Package that you want to rename, and click Rename Package.
4. ProVision asks you to confirm that you want to rename the package. Click Yes.
5. The New Package Name screen displays. Enter the new name for the Package,
then click OK.
6. The Package is renamed.
Entering a Description for a Package

You can enter a detailed Description for a Generic Device package. The description
should include what the Package is for and list the Generic Device types it includes.
Procedure
2. In the Administration menu, select Generic Device Management. The screen
displays.
3. Select the Package that you want to edit, and click Edit Package. The Edit
Device Package screen displays.
4. Go to the Information tab. In the Description field, enter the description.
614-330053-001 APRIL 2014 249

5. Click Save, or go to another tab to make further changes. The Description is

applied to all Devices in this Package.
Setting Trap Mapping to Identify Package Events

An SNMP Trap is an unsolicited message sent by the radio or other device to ProVi-
sion. Each Trap usually contains alarm or event information.
Trap mapping tells ProVision how to extract the Event name, Severity and State
information from each received alarm or event trap.
The user defines trap mapping for each of these 3 parameters by identifying the field
or OID and how to interpret the contents or values. A set of mapping tools, as
described below, enable you to define the mapping.
Prerequisites
To use the Trap Mapping, users have to generate traps. For this, the users supply
their own expertise about the Generic Devices. Work with test installations of the
radios and devices to trigger events for Trap Mapping. Use the device MIB as a ref-
erence.
You may want to review the Trap Mapping Example on page 254.
Devi ce i ntegrati on. Pl ease contact your l ocal Avi at Networks
sal es and support staff for more i nformati on.
Trap Mapping Tools

The Trap Mapping tab contains the following sections:
l Received Traps frame - This displays a list of the most recently received
traps for a selected Generic Device.
l Trap Viewer frame - This shows the detailed values for a selected trap.
250 AVIAT NETWORKS

l Editor frame - The Editor tab contains the trap editing tools and sections
for Event Name, Severity, and State data. Users click and drag data into an
area to identify it and save it for ProVision. If data is placed in an incorrect
section, the section border is red, and the user cannot edit the data. A green
section border shows that the data is matched to the correct section and can
be edited.
An example of the Trap Mapper screen, open to the Mapping Rules tab, is shown
below.
These are the trap mapping tools, and how they are used to edit traps.
Substring: With this tool, a user selects part of the trap. Characters that are not
selected are removed. This only removes characters with absolute positions.
Remove: Users enter text to be removed from a trap. This function searches for and
removes the text. Users can search for specific text or use any regular search expres-
sion, such as .* Common text to remove includes time/date information and spacing
dashes.
614-330053-001 APRIL 2014 251

Replace: Users can find and replace text in a trap. Again, users can apply this to
specific text or use the irregular search, ending with .*
Trim: This function specifically removes padding characters from the beginning and
end of a trap. This is different from the Substring selection or the Remove function,
because it removes characters that have flexible positions. The Trim function only
works for characters at the start and end of a string.
Append: Use this to add additional text and field values to a trap. Common data
to add includes card numbers and port numbers.
Map: Adding the Map function to a trap enables you to assign OID values to a trap.
The values entered here are used by the trap to receive OID input and match it to an
event name, state, or severity.
Trash: To delete an editing tool, click and drag it into the Trash.
Procedure
2. In the Administration menu, select Generic Device Management. The Edit
3. Go to the Trap Mapping frame and click on the Mapping Rules tab.
4. Check to see that events have been generated for devices in this Package. If events
are available, they display in the Received Trap frame. If there are no events in this
frame, click the Refresh Traps button. Any received traps will display.
252 AVIAT NETWORKS

5. Select an event. The fields, OIDs, and values for the event display in the Trap
Viewer tab.
6. The selected trap is now ready to be edited.

7. First, locate and edit the Event.
l In the Selected Trap tab, click on the trap and drag it to the Editor frame. A
Value icon displays, and the Output shows at the bottom of the frame.
l Use the Trap Mapping tools to edit the Output.
Normally, users apply these tools as required:
l Use Subset to select the significant portion of the string.
l Use Remove to delete unwanted text from the string.
l Use Trim to delete padding characters from the string.
l Use Replace and/or Append to edit the string.
l Add a Map icon to conclude the string.
You can appl y the Trap Mappi ng tool s i n any order; however,
a Map i con must al ways concl ude the stri ng.
WARNING: Nev er use punctuati on mar ks i n a Tr ap M ap-
pi ng str i ng. These i ncl ude; : , ? ! and si ngl e quotes ‘.
Usi ng punctuati on mar ks or other contr ol char acter s
may cr eate i nv al i d commands and cor r upt the database
i r r epar abl y .
8. Next, locate and edit the Severity for the event.
614-330053-001 APRIL 2014 253

l In the Selected Trap tab, click on a Value and drag it to the Severity frame. A
Value icon displays.
l The Mapping tool displays. Enter the Severity values from the MIB.
9. Finally, locate and edit the State for the event.
l In the Selected Trap tab, click on a State and drag it to the State frame. A
Value icon displays.
l The Mapping tool displays. Enter the Status values from the MIB.
You can i mport some event stri ng val ues from a .CSV fi l e.
See Imp ort ing Trap Map p ing from a . C SV File on p age 26 2.
10. Repeat steps 5- 9 to configure other events from the Trap Mapping.
11. Click Save. The events are now saved in ProVision. ProVision will now use the
edited trap mapping string to record this event in ProVision records.
A compl eted Trap Mappi ng for an event must have Event
Name, Severi ty, and State val ues. Severi ty and State val ues
must end wi th the Map functi on.
Next Topic:
Trap Mapping Example on page 254
Trap Mapping Example

l This is a step-by-step example of how to set up trap mapping for a device.
l The device in this example is a Loop 9100 Multiplexer.
l The goal is to map events from received traps.
Procedure
1. Set up the Generic Device.
l Follow the instructions for deploying the Generic Device as described in the
ProVision User Guide. Assign a package name to the device.
254 AVIAT NETWORKS

l Obtain a copy of the device MIB. This is used later in this process as a
reference.
2. Generate and Capture Traps for the Generic Device.
l Go to the Loop 9100 telnet interface.
l Configure the ProVision server as a trap destination.
l Use the telnet interface to generate traps using event commands. For the Loop
9100 in this example, this was done by logging in and out, resetting
performance counters, and using the maintenance controls.
3. In ProVision, open the Package for the Generic Device.
l In the Tree Viewer or Map View, select the Generic Device to edit.
l In the Administration menu, select Generic Device Management. The Edit
l Go to the Trap Mapping frame and click on the Mapping Rules tab. The
Received Traps frame should display data, as shown below.
4. Extract the Event Name.

l Select an event name in the Received Traps frame. The event information
displays in the Trap Viewer frame.
For this example, the trap contains a description of the event as a fixed size string:
614-330053-001 APRIL 2014 255

l Note the hyphens in the trap. The hyphens are being used as padding
characters.
l In the Selected Trap tab, click on the trap and drag it to the Editor frame. A
Value icon displays, and the event shows as Output at the bottom of the
frame.
5. Remove the Timestamp from the Trap Name.

l Select the Substring item and drag it to follow the Value icon. The Substring
tool displays for the trap.
l Use the Substring Tool sliders to highlight the example from the start of the
trap to the end of the padding hyphens. This crops the text to match the
selected part of the trap. It is IMPORTANT to retain the hyphens; they may
contain useful information.
l Hover over the Event Trap in the Editor to see the results of editing the
substring for this trap.
6. Remove Padding Hyphens from the Event Name.
256 AVIAT NETWORKS

l The hyphens can now be removed, using the Trim tool.

l Select the Trim item and drag it to follow the Substring item. The Trim tool
displays. In this example, the ‘-” character is being trimmed from the right.
7. Edit the Event Header.

l The final step in editing the trap is to remove the severity text from the
beginning of the string name.
l Select the Remove item and drag it to follow the Trim item. The Remove tool
displays.
l The text ‘.*>’ is entered to be removed. This regular expression represents “any
number of characters ending with >”. Any severity text (CRIT>, INFO>, etc.)
is now removed.
614-330053-001 APRIL 2014 257

The trap is complete.

8. Map the Event Severity.
l Refer to the MIB for this device. This informs us that the event severity value
is in field 6 of the trap, and that the severity values are:
l 1 - Critical
l 2 - Major
l 3 - Minor
l 4 - Informational
l To add this field to the Severity section, add the Value to the Severity frame.
l Then, select the Map tool and drag it to follow the Value in the Severity field.
l The Mapping Tool displays. Map the Severity values for this trap as shown.
9. Map the Event State.

l Again, refer to the MIB for this device. This informs us that the event status
value is in field 7 of the trap, and that the status values are:
l 1 - Active Event
l 2 - Cleared Event
l To add this field to the State section, add the Value to the Status frame.
Then, select the Map tool and drag it to follow the Value in the Status field.
l The Mapping tool displays. Map the State values for this trap as shown.
10. Repeat Steps 3 - 9 for other traps for this device.

11. Click Save.
258 AVIAT NETWORKS

Managing Imported MIBs

You need to manage and scan the MIB files to import them into ProVision (Import-
ing Trap Mapping from a MIB File on page 260). If a MIB file needs to be rescanned,
it is identified.
Procedure
1. Save the MIB file or files to the ProVision Client PC. Save them to the main Client
install folder on the install directory:
ProVisionClient/clientmibs
2. Open ProVision on the ProVision Client PC.
4. In the Administration menu, select Generic Device Management. Click on the
MIB Management tab. The screen displays, listing all loaded MIBs:
5. A MIB with a check beside it is loaded correctly and fully valid.

6. A MIB with a red X beside it is loaded with errors. To review the errors, click on
the MIB. The MIB Errors screen displays, listing the errors for that MIB:
614-330053-001 APRIL 2014 259

7. To fix the errors, close the MIB Errors screen. In the Loaded MIBs list, select the
MIB and click Rescan MIB Folder.
8. ProVision finds and rescans the MIB. The MIB data is refreshed and should dis-
play with a check mark beside it.
9. You are now ready to import the trap mapping from the scanned MIB files.
Importing Trap Mapping from a MIB File

You can import a MIB file into ProVision. You can then review the MIB-sourced trap
details in ProVision.
To do this, first, you have to save the MIB file to the ProVision Client PC. Then, you
scan the MIB against a specific Package (see Managing Imported MIBs on page 259).
In the Edit Device Package screen, note that traps captured from the radio have a yel-
low icon, and that traps from MIBs have a blue icon, as shown below:
In addition, after MIB traps are loaded, the trap OIDs now display as text names,
not as numerical names.
Procedure
4. Go to the lower edge of the Received Traps frame.
260 AVIAT NETWORKS

5. Click on the Add Traps from MIB button.
6. The MIB Object Selector screen displays. Choose the MIB and click the Select but-
ton.
7. In the Received Traps frame of the Mapping Rules tab, the frame is now populated
with traps. The traps sourced from the MIB display with blue icons. In addition,
MIB-sourced trap OID values now display as text values in the Trap Viewer, identi-
fying their purpose.
You can edi t the MI B trap val ues di rectl y from the Trap
Vi ewer frame. To do thi s, tr i pl e cl i ck on a MI B trap (MI B
traps are col ored bl ue).
8. When you click Save, the mapping will be saved with other Package con-
figurations.
614-330053-001 APRIL 2014 261

Importing Trap Mapping from a .CSV File

For some devices the event name is not provided in the SNMP Trap; instead only a
value is provided.
When this is the case, you have to either manually enter the set of event names, or
import the event names can be performed through a .CSV file.
The .CSV file must be formatted with two columns: one for the event name, and one
with the event OID value.
Procedure
4. Create a basic map, as described in Setting Trap Mapping to Identify Package
Events on page 250.
5. Click on the Map tool in the map/string/name to be decided. The Mapping frame
appears at the bottom of the screen.
6. Click on the Load Mapping button. An Explorer screen displays.
7. Find and select the .CSV file and click Open.

8. The maps from the .CSV file display in the Mapping frame. These maps are now
applied to the map from step 4. When you click Save, the mapping will be saved
with other Package configurations.
262 AVIAT NETWORKS

Setting Matching Rules for Trap Mapping

To manage trap mappings, and to support devices with multiple trap types, users
can set up a trap mapping Matching Rule. A Matching Rule is a set of trap mapping
values to select subsets of traps. Matching Rules are defined by Match Criteria.
Matching Rules tells ProVision how to group received alarms or event traps for a
Package, and assign trap mapping rules to them, based on their Match Criteria.
Users can set up matching rules based on trap OIDs and/or fields.
The user defines the Matching Rules by identifying the field or OID and how to inter-
pret the contents or values. A set of mapping tools, as described below, enable you to
define the mapping.
Prerequisites
To use the Matching Rules, traps should be generated first, or imported from MIB
files. For this, the users supply their own expertise about the Generic Devices. Work
with test installations of the radios and devices to trigger events for Trap Mapping.
Use the device MIB as a reference and/or trap source.
It is also useful to review the Matching Rules use example, Match Rules Example:
Multiple Trap Types on page 265.
Devi ce i ntegrati on. Pl ease contact your l ocal Avi at Networks
sal es and support staff for more i nformati on.
Matching Rule Tools

The Matching Rule tab contains the following sections:
l Received Traps frame - This displays a list of the most recently received
traps for a selected Generic Device, and the Rules that they are assigned to.
You can move a Rule set up and down in the list. This is important; the Rules
are analyzed in the order listed, and the first Rule match for a trap is assigned
to the trap.
l Trap Viewer frame - This shows the detailed values for a selected trap.
l Match Criteria frame - The Match Criteria frame contains the Rule editing
tools and sections for trap OIDs and fields.
To create and manage Match Rules, use the buttons below the Received Traps frame:
Button Function
Import traps from an MIB
file.
Add a Match Rule.
614-330053-001 APRIL 2014 263

Button Function
Delete a selected Match
Rule.
Save a Match Rule.
Load a saved Match Rule.
Move Match Rules up and

down in the Received Traps
frame.
An example of the Match Rules tab is shown below.
Procedure
2. Go to the Trap Mapping frame and click on the Match Rules tab.
3. Check to see that events have been generated for devices in this Package. If events
are available, they display in the Received Trap frame. If there are no events in this
frame, click the Refresh Traps button. Any received traps will display.
4. Select an event. The fields, OIDs, and values for the event display in the Trap
Viewer tab. These are helpful when you are assigning values to Match Rules.
5. Set up your Match Rules. For each Match Rule, enter a Rule Name. Then, select
one or more Match Rule value check boxes, and enter a value:
264 AVIAT NETWORKS

l Trap OID - Creates a rule grouping traps that have this specific OID.
l Generic Types - Creates a rule
l Specific Type - Creates a rule
l Num Fields - Creates a rule grouping traps that have a specific number of
fields.
l Field OID - Creates a rule grouping traps that have a specific number of fields
and a specific OID.
l Field Value - Creates a rule grouping traps that have a specific varbind value.
Users can set mul ti pl e val ues for a Match Rul e. The Match
Rul e wi l l appl y to any traps that match al l the val ues.
6. The Match Rule is created and applied to all the traps. The new Match Rule dis-
plays in the Received Traps frame. Traps display in the Received Traps frame
under the Match Rule that applies.
7. If required, adjust the order of the Match Rules. In the Received Traps frame,
use the Up and Down buttons to move the position of Match Rules.
8. Use the + and - buttons below the Received Traps frame to add and delete Match
Rules.
9. Create a final Match Rule. Leave this value as Rule Unknown . This allows users
to view traps that do not match any of the Match Rules.
Step 9 i s requi red whenever you create Match Rul es.
10. Save all the Map Rules you have created.
Users can I mport and Export Match Rul es as wel l as Mappi ng
Rul es. Users can export al l the Trap Mappi ng data, or j ust the
Match Rul es, as speci fi c Modul es.
Match Rules Example: Multiple Trap Types

This is a step-by-step example of how to set up match rules for a device. Devices
with multiple and distinct trap formats require match rule settings to identify the dif-
ferent trap types. In this example, the goal is to map events from MIB data into two
different trap types.
In this example, some traps have the value ifindex in Field 1. Other traps have a
severity value assigned to Field 1. This point of difference will be used to identify the
two different trap types, by creating a separate Match Rule for traps that include the
value ifindex.
Procedure:
1. Set up the Generic Device.
l Follow the instructions for deploying the Generic Device as described in the
ProVision User Guide. Assign a package name to the device.
l Obtain a copy of the device MIB.
614-330053-001 APRIL 2014 265

2. In ProVision, open the Package for the Generic Device.

In the Tree Viewer or Map View, select the Generic Device to edit. In the Admin-
istration menu, select Generic Device Management. The Edit Device Package
screen displays.
3. Go to the Trap Mapping frame. Follow the instructions for importing the device
MIB, as described in Importing Trap Mapping from a MIB File on page 260. When
this is done, the MIB traps display.
4. Click the Match Rules tab. Click the button to Add a Match Rule.
5. The new rule displays in the Received Traps frame. It displays at the bottom of
the trap list as Rule Unknown. Select Rule Unknown.
6. The values for Rule Unknown display in the Match Rules editing area. Enter the
new rule name of Match Interface Traps.
266 AVIAT NETWORKS

7. Then, move this rule name to the top of the list, using the Up button.
8. Edit the Match Interface Traps rule so that it selects traps with the ifindex var-
bind value. To do this, you are identifying a different OID for this rule. Edit the Field
OID value for this rule as follows:
l Review traps in the Trap Viewer until you find one that includes the ifindex
object. Note that you can mouse over an MIB-sourced object to view its
complete values.
l Click on the Field OID check box. This activates Field OID as a value for the
rule.
l Click and drag the ifindex object into the Field OID field. Its OID value
displays.
l Enter the field number that holds the ifindex object. The field number is 1.
In the Field OID field, add a wild card to the end of the OID value. This ensures that
this rule identifies any instance of ifindex.
614-330053-001 APRIL 2014 267

l Click Apply.
9. The new rule is applied. Examples in the Received Traps frame are reorganized
based on this new rule.
10. Create additional Match Rules to identify other trap types, as required.
11. Create a final Match Rule. Leave this value as Rule Unknown . This allows users
to view traps that do not match any of the Match Rules.
Severity Resync Functions

From the Edit Device Package - Security Resync tab, you can set up the fol-
lowing Generic Device customizations:
Summary Events frame -
l Configuring Generic Device Resynchronization Alarms on page 268
l Resynchronization and Custom Events Example on page 272
Custom Events frame -
Configuring Generic Device Resynchronization

Alarms
For some devices, one or more summary alarm objects are provided. They indicate
the current highest active alarm severity of the device.
268 AVIAT NETWORKS

Polling these objects at a regular interval can ensure that ProVision is synchronized
with the highest active severity state of the device. In this situation the Resyn-
chronization Alarm function should be used.
You can specify the object(s) to be polled, and the values that will result in a specific
severity (event raised) or event clearing condition.
When the specified OID value condition is detected, an Alarm Resynchronization
event with the specified severity is generated by ProVision.
Polling is initiated when a device enters the Managed state or enters the Wake (exits
Sleep) state. This function accommodates scenarios where either a single or multiple
OIDs need to be polled. See the Resynchronization and Custom Events Example on
page 272, in the following pages, for further details.
Procedure
2. In the Administration menu, select Generic Device Management. Select and
double-click a package. The Edit Device Package screen displays.
3. Go to the Severity Resync tab. In this tab, go to the Summary Events.
4. To create a new alarm, click Add. A new Summary Event line should display.
614-330053-001 APRIL 2014 269

5. Enter the following values for the resynchronization alarm:

l OID - The OID address of the MIB object being read.
l Severity - The severity value for the event.
l Value - A numerical value for the event. This value must be different for each
OID and Severity pair. If two events for one OID have different Severity values
and the same number value, this number value defaults to the higher severity.
6. All devices assigned to this Package now have a resynchronization event. Click
Save when you are done editing this Package, and the screen closes.
Creating Custom Events for Packages

You can create a custom Event for a Package. When a custom event is detected,
ProVision will refer to the indicated MIB and match the event value to the custom
event. Custom events are a supplement to the Trap Mapping and Alarm Resyn-
chronization functions.
Custom Events are similar to Summary events. Using Custom Events, you can to
configure any number of events for a Package, by specifying event names.
To do this, you specify the Generic Devices to be polled, the custom event name asso-
ciated with the device, and the values that will result in a specific severity (event
raised) or event clearing condition. As with Alarm Resynchronization, the specified
OIDs are polled at 2 minute intervals, with polling initiated following transition to
the Managed state and Wake (exiting Sleep) state.
Each unique event is determined by the Event Name. This provides great flexibility,
enabling you to configure all of the following event types:
l An event whose severity and state is defined by a single OID.
l An event whose severity and state is defined by multiple OIDs.
l An OID whose severity and states represents multiple events.
For example, for a particular event, one OID may indicate the raised condition and
another OID may indicate the clearing condition.
270 AVIAT NETWORKS

See the Resynchronization and Custom Events Example on page 272, in the fol-
lowing pages, for further details.
Procedure
3. Go to the Severity Resync tab. In this tab, go to the Custom Events.
4. To create a new custom event, click Add. A new Custom Event line should dis-
play.
5. Enter the following values for the custom event:

l OID - The MIB object being polled.
l Event Name - Name for the event.
l Severity - The severity value for the event.
l Value - A numerical value for the event. This value must be different for each
OID and Severity pair.
614-330053-001 APRIL 2014 271

6. All devices assigned to this Package now have a custom event alarm. Click Save
when you are done editing this Package, and the screen closes.
Resy nchronizat ion and C u st om Ev ent s Examp le on p age 272
Resynchronization and Custom Events Example

This is a step-by-step example of how to set up resynchronization and custom events
for a generic device.
The goal is to set up the following alarms for the device:
l A resynchronization alarm
l An alarm warning that remote radio connectivity is lost
l A temperature sensor warning alarm
Each alarm is linked with a specific OID, as recorded in the device MIB.
Procedure
2. In the Administration menu, select Generic Device Management. Select the
Package for the Generic Device. The Edit Device Package screen displays.
3. Go to the Severity Resync tab. In this tab, go to the Summary Events frame.
4. To create a new alarm, click Add. A new Summary Event line should display. The
Summary Event line includes the beginning of an OID.
5. Enter the following values for the resynchronization alarm:
l OID: .1.3.6.1.4.1.2347.1.5.6.1.0.1.0 = The OID address of the MIB object being
read. This must include the instance of the OID.
l Severity: Critical.
l Value: 1.
6. The resynchronization alarm requires two more severity levels. Click Add again,
and enter the following values:
272 AVIAT NETWORKS

l Severity: Warning.
l Value: 2.
7. Click Add again, and enter the last set of values:
l Severity: Normal.
l Value: 3.
8. The Resynchronization event is now complete. The Summary Events frame now
includes three events for the same OID:
9. Next, in this screen, go to the Custom Events frame.

10. To create a new custom event, click Add. A new Custom Event line displays.
Again, this includes the beginning of an OID.
11. Enter the following values for the Remote Radio Connectivity Lost event:
l OID: .1.3.6.1.4.1.2347.1.5.6.1.2.1.1
l Event Name: Remote Radio Connectivity Lost
l Severity: Critical.
l Value: 2.
12. Click Add again. A new Summary line displays. Note that this Summary line
includes the same OID as for the event entered in step 9.
614-330053-001 APRIL 2014 273

13. Enter the following values for the Temperature Sensor Warning event:
l OID: 1.3.6.1.4.1.2347.1.5.6.1.2.1.2
l Event Name: Temperature Sensor Warning
l Severity: Warning.
l Value: 3.
14. All devices assigned to the Package now have a resynchronization alarm and two
custom event alarms. When you click Save, all changes are saved for this Package.
274 AVIAT NETWORKS

614-330053-001 APRIL 2014 275

Launching Generic Device Windows

Applications from ProVision
To allow users to launch Generic Device windows applications from a Generic Device
object displayed in ProVision, the system administrator has to preconfigure the
application integration. Administrators can set up multiple applications to be
launched from a type of Generic Device.
F or each appl i cati on to be used, the craft tool s need to be
i nstal l ed on each i ndi vi dual cl i ent. Note the system l ocati on
where the i nstal l ati on fi l es are saved, for use i n the l aunch
confi gurati on procedure.
Procedure
1. In ProVision, set up the Generic Devices and Packages.
2. On the Client, install the Generic Device craft tool or tools.
3. Log into ProVision at the NOC engineer or system administrator level, i.e., using
the NOC engineer or administrator user name and password.
4. In the Tree Viewer, locate a Generic Device that you want to connect with craft
tools. Right-click on its icon. In the right-click menu, Applications > Edit Applic-
ations displays. Click on Edit Applications. The Edit Applications screen displays.
5. To add a new Application for this Generic Device type, 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 Generic Device craft tool
executable file (.exe) for this Generic Device. Select the .exe file.
l Parameters - Customize the .exe file with command line parameters. This
specifies the Generic Device object attributes that are applied to the Windows
executable when it is launched from ProVision.
276 AVIAT NETWORKS

6. To enter additional Applications, click Add again. You can save multiple Applic-
ations for each device, as shown.
7. The right-click menu for the device now displays Applications >(Craft Tool
Names) .
8. The selected craft tool opens for the device.

9. If you need to update the craft tool link, click on Applications > Edit Applic-
ations again. This re-opens the Edit Applications screen. Make changes to the craft
tool link from this screen.
Craft Tool Connection Commands

Craft tool connection commands include:
Command Command Value

ipaddress Device IP Address
name Device name
read_com- Read community
munity string
write_com- Write community
munity string
614-330053-001 APRIL 2014 277

Command Command Value

snmp_version SNMP version 1 or
2c
support_pack- Package name
age
An example of the use of these commands is:

mgibbpe.exe -address %ipaddress -community %read_community -auto-
contact
This command line is enabling the following:
l mgibbpe.exe = Enables this specific .exe file.
l -address %ipaddress = Defines the ip address of the specific ProVision
Client PC.
l -community %read_community = Defines the community string.
l -autocontact = This command is specific to the mgibbpe.exe executable and
the MIB Browser it enables. This command instructs the executable to
automatically contact the device identified by the IP address parameter.
Note: Al ways precede a craft tool connecti on command wi th
the % symbol .
278 AVIAT NETWORKS

Chapter 12. Northbound
Interface
l Introduction to the Northbound Interface on page 280
l NBI Event Management on page 283
l NBI Performance Data Management on page 304
l NBI Configuration Management on page 316
l NBI Topology Management on page 326
614-330053-001 4/04/2014 279

CHAPTER 12. NORTHBOUND INTERFACE
Introduction to the Northbound Interface

What is the Northbound Interface (NBI)? To understand this fully, you need to
understand the concepts of Telecommunications Management Network (TMN)
Logical Layered Architecture (LLA) as illustrated in ProVision in the TMN LLA
Model on page 280. In this Introduction, first we will explain LLA, and then we will
define the NBI for ProVision.
The LLA concept organizes management functions into groupings called “logical lay-
ers” and describes the relationship between layers.
Level 1 is the Networks Elements Level (NEL) and is made up of the functions
(Portal, WMT, DXR NET, LinkView) that are associated with the individual network
elements (Eclipse, SNMP and TNet devices).
Level 2 is the Element Management Level (ELM). ProVision is representative of this
layer as the manager for all Aviat Networks Network devices (elements).
Level 3 is the Network Management Level (NML) and, as its name implies, man-
ages the network that makes up levels 1 and 2.
Level 4 and Level 5 are the Service Management Level (SML) and Business Man-
agement Level (BML), respectively. These are similar to the NML but operate at a
higher level.
Figure 12-1. ProVision in the TMN LLA Model
NBI and ProVision

The Northbound Interface (NBI) supports data exchange between the EML, rep-
resented by ProVision, and the higher-level applications of the NML. ProVision can
be configured to transmit the network information in the specific format (ASCII,
280 AVIAT NETWORKS

SNMP, XML) required for any NML application. The prime function of ProVision is
to provide an integration capability with the higher-order, layer 3 NML.
Different northbound systems have different capabilities and requirements for hand-
ling the events forwarded by ProVision. In ProVision, you can set up filters so that
only the events that match the filter criteria are forwarded to a particular des-
tination.
ProVision supports NBI with higher order management solutions such as:
l TeMIP and HP OpenView for Event Management
l Concorde for Performance Data Management
ProVision is used as the higher order management solution for Topology, Con-
figuration and Inventory Management.
The i nternati onal standard I TU-T Recommendati on M.3010
descri bes the concepts of TMN archi tectures and thei r fun-
damental el ements.
The deployed NBI applications are grouped under the ProVision Manager in the Tree
Viewer, and are displayed as icons in the Map Viewer.
Event severity colors are used with the NBI icons. For example, green indicates the
NBI is enabled with no errors, whereas blue indicates the NBI is disabled. (See
theProVision User Guide for more information.)
The ProVision NBI can forward the following information sets:
l NBI Event Management on page 283
l NBI Performance Data Management on page 304
l NBI Configuration Management on page 316
l NBI Topology Management on page 326
The configuration required to forward this information is typically done during net-
work installation and configuration.
614-330053-001 APRIL 2014 281

F rom Versi on 6.5.3, ProVi si on can al so be used wi th Mul ti -

Technol ogy Operati ons System I nterface (MTOSI ) NBI . To
accessthe ProVi si on MTOSI NBI programmati cal l y , you bui l d
web servi ce cl i ents that use the ProVi si on' s MTOSI NBI API .
Typi cal l y, your web servi ce cl i ent appl i cati on woul d use a
tool ki t that knows how to connect to and i nteract wi th web ser-
vi ces. F or more i nformati on, see the Appendi x: MTOSI NBI
and ProVi si on, whi ch al so refers to a separate documentati on
set.
282 AVIAT NETWORKS

NBI Event Management

The NBI Event Management section covers the following topics:
l Introduction to NBI Event Management on page 283
l Setting Up an Event NBI on page 285
l Deploying an Event NBI on page 286
l Testing an Event NBI Configuration on page 291
l Saving, Printing, and Viewing an Event NBI Configuration Report on page 294
l Editing an Event NBI Configuration on page 295
l Enabling/Disabling an Event NBI on page 296
l Resynchronize an Event NBI on page 297
l Remote Resynchronize on page 298
l Deleting an Event NBI on page 298
l Renaming an Event NBI on page 299
l See "Event Browser"
l Configure Services on page 299
l System Integration for NBI Event Management on page 300
Introduction to NBI Event Management

NBI event management enables integration of event management with Network Man-
agement Layer systems.
The main purpose of NBI event management is to convert ProVision events, as dis-
played in the Event Browser, into a consistent output format for porting to the Net-
work Management Layer.
ProVision can output events raised as a result of:
l Traps sent from a managed network device
l Events raised as a result of polling a managed network device
l Events raised by the ProVision platform
The following steps describe how an event from a managed network device (for
example, an Eclipse radio) is forwarded to the higher-level Network Management Sys-
tem (NMS):
1. The event is passed through the PreFilter application.
2. The event is stored in the ProVision database.
3. The event is passed to the Event Browser and NBI event management.
614-330053-001 APRIL 2014 283

4. NBI event management ensures the event is from a required device and verifies
that the severity and status parameters match the parameters set in the filter file.
l If the event is not from a required device, the process stops.
l If the event is from a required device, it goes to the forwarding function.
l If the parameters do not match, the process stops.
l If the parameters do match, the event is then sent to the NML.
The processes for setting up, deploying, and testing an event NBI are described in
the following sections:
l Deploying an Event NBI on page 286
l Testing an Event NBI Configuration on page 291
The processing to forward an event to an NML is as follows:
1. The event is generated by an event source:
Device Traps
Presence Polling
ProVision platform
2. If the event is not generated by ProVision, it is sent to ProVision.
3. ProVision filters the events and stores them in the database.
4. Based on the event type, events are either:
Sent to the Event Browser for ProVision
Sent to the Events Northbound Interface
5. Events sent to the Events Northbound Interface are analyzed to see if they meet
the event filter criteria. Events that do not meet the criteria are discarded. Events
that do meet the criteria are forwarded to the NML.
This table lists the events associated with NBI Event Management.
Table 12-1. NBI Event Management Events
Event Description
Event-forwarding Corrects any mismatch between the data in the ProVision
resynchronization database and the Network Management Level (NML)
Event-forwarding Initiates an event to be forwarded to the NML
activation
Event NBI remote Similar to event-forwarding resynchronization, corrects
resynchronization any mismatch between the data in the ProVision database
command and the Network Management Level (NML) except that the
command is issued external to ProVision.
The information contained in the forwarded event is comprehensive and is mapped

into the X.733 event model. This table describes the information contained in each
northbound event, based on the format of internal ProVision events.
Table 12-2. NBI Event Information Description
284 AVIAT NETWORKS

Field Description
ProVision server Identifies the ProVision server that has forwarded the
Address event
Trap Number The unique number allocated by ProVision to each for-
warded event
Trap Timestamp The time the event was forwarded from ProVision
Trap Source Path The full physical path of the device where the event
occurred
Trap Device Type For example, an XP4 2/4/8x radio
Trap Source Address IP address of the object (radio or ProVision server) raising
the event
Trap State Active or cleared
Trap Severity Information, normal, warning, minor, major, critical
Event Timestamp The event time recorded in the ProVision database
Event Description A description of the event, for example, Trib 13 uncom-
missioned traffic
Next Topic:
Setting Up an Event NBI on page 285
Setting Up an Event NBI

Prerequisites for Setting Up an Event NBI:
To set up an event NBI, the following items must first be determined:
l The managed network devices to be monitored for the NBI
l The types of events to be forwarded
l The forwarding mechanism to be used
l The output type (SNMP trap, ASCII file or TCP port)
For SNMP trap forwarding, the following two items are required:
l The IP address of the Northbound system
l The UDP port of the Northbound system
For TCP port output, the TCP port, on which the northbound destination system
receives the data, is required.
For ProVision servers with multiple network interface cards, SNMP requests and
traps must be configured to use a specific network interface. Edit the file:
ProVisionServer\tomcat\webapps\ROOT\pv\templates\server_configuration.xml
As an example, if the IP address of the network interface to be used is 10.16.200.1,
after the comments, edit it as follows:

614-330053-001 APRIL 2014 285


Add line: <interface>10.16.200.1</interface>
Then, save the file and restart the ProVision server.
WARNING: You cannot use one networ k i nter f ace f or
SNM P r equests and r adi o tr aps between Pr oVi si on and
the r adi o networ k and use another i nter f ace f or SNM P
ev ent-f or war di ng NBI tr aps.
Overview of Setting Up an Event NBI:

There are several steps involved in setting up an event NBI:
1. Deploy Event Destination:
l Enter the destination name and select forwarding method(s)
l If required, change filter settings
2. Test Event Destination Configuration:
l ProVision generates events that match the filter settings and forwards them to
the destination management system.
3. Save and/or Print the Forwarding Configuration Format report.
Next Step
Deploying an Event NBI on page 286
Deploying an Event NBI

Wh en you add an even t forwardin g dest in at ion , by defau lt , it is
en abled an d st art s forwardin g even t s im m ediat ely. You can st op
even t forwardin g by disablin g t h e even t forwardin g dest in at ion .
Refer t o Enabling/Disabling an Ev ent NBI on p age 29 6 .
When depl oyi ng an event NBI , you have the opti on to choose
to use SNMP V1 Trap MI Bs. ProVi si on users SNMP V2
Trap MI Bs by defaul t. Note that there are speci fi c SNMP MI B
fi l es for each opti on:
l SNMP V1 MIB: STXN-PV-V1-TRAPS.MI2
l SNMP V2 MIB: STXN-PV-V2-TRAPS.MI2
Procedure
1. In the Tree Viewer, right-click the ProVision Manager icon. The right-click
menu is displayed.
2. Select Deploy NBI . The NBI Deployment window is displayed.
286 AVIAT NETWORKS

3. Select the NBI event icon. The Deploying Event Forwarding window is dis-
played.
4. Enter the NBI values, including:

l Destination Name = Higher-level network manager (for example,
HPOpenView) or the name of the computer to which the events are forwarded
(for example, PC435).
l IP address, UDP port, community string
l Select the required event forwarding method. You may select any of the
forwarding methods, two of the three, or all three.
614-330053-001 APRIL 2014 287

Forwarding Actions
Method
SNMP - Select the SNMP checkbox.
- Enter the IP address of the northbound computer.
- If required, change the UDP Port and/or the Community
String settings.
- If required, check the boxes for Use SNMP V1 Trap MIB
and Include Probable Cause.
NOTE: By default, the ProVision NBI uses SNMP V2 traps. If
you need to use SNMP V1 traps instead, check the Use
SNMP V1 Trap MIB check box.
ASCII file Select the Save to ASCII File checkbox.
The ASCII file is located in <Install Dir-
ectory>\PVServer\NBI\Event on the ProVision server. The file-
name matches the destination name you entered in step 3,
for example, HPOpenView.nbf. When the file reaches 10 Mb it
is renamed to <destination>.old and a new.nbf file is started.
The ASCII file can also be sent via FTP.
TCP Port - Select the Output to TCP Port checkbox.
- Enter the TCP Port on which the northbound destination
l system receives the event data.
5. Select Next. The default filter settings are displayed.
6. To edit the filter settings, select Edit. The Filters window is displayed.
Table 12-3. The Filter Settings for an Event NBI
288 AVIAT NETWORKS

Filter Setting Definition

Simple Tab State
By default, only active events are selected to be for-
warded to the destination system.
To forward cleared events, select the Cleared
option.
When a main selection criteria’s (for example, State)
option is selected then filtering is enabled using the
selection criteria.
Acknowledgement
By default, events are forwarded regardless of
whether or not they are acknowledged.
Severity
By default, all events are forwarded.
To exclude any of the event types from being for-
warded, de-select the associated option.
Category
By default, all event categories are forwarded.
To enable specific category filtering, select the Cat-
egory option. Then select the categories required.
All other category types are not forwarded.
Date / Time Tab By default, there is no filtering on date and time. You
can set date/time values for Raised and Cleared
events.
To activate the date and time filter, select the Date
/ Time option.
To enable the filter’s start date and time:
Select the Start option.
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-330053-001 APRIL 2014 289


Objects Tab By default, there is no filtering on object types, and
events for all object types are forwarded.
To filter for events generated by specific object types:
- Select the Object Type option.
- Select the object types required.
Only events generated by the selected object types
and their associated child objects are forwarded.
Text Tab By default there are no text filters applied to the

event descriptions.
You might for example, be interested in “lost
comms” events so you could set up a text filter to
include only lost comms events.
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 selected.
- To exclude events that contain the filter text,
select the Exclude checkbox.
Containment Tab By default there are no containment filters applied.

This is the most useful and flexible filter setting. You
can filter for all events generated from the general
(for example, a region) to the specific (for example,
from an Eclipse radio’s ODU).
To filter for events generated by a specific object/ob-
jects:
- Select the Objects option.
- If required, expand the toggles, and select the
object that is generating the events required, for
example, an Eclipse radio ODU.
290 AVIAT NETWORKS


Notification Criteria Enter the time value for each of the following. Time
values can be set in seconds, minutes, or hours.
After Event Duration - Event notification will be
sent after the event has lasted for this amount of
time.
Guard Time - Guards against excessive noti-
fications. ProVision will notify for the first occurrence
of a matching event for this device, then ignore
recurrences for this device within this period of time.
Reminder After - A reminder about the event will
be sent after this amount of time.
Notify on Resolution - Check this box, and a noti-
fication will be sent when the event either clears or is
otherwise resolved.
7. Make the required filter changes as described in the table above and select OK.
8. The updated filter settings are displayed. Select Next to continue.
9. The Heartbeat Trap setting is displayed. A heartbeat trap is a message that ProVi-
sion sends, at regular intervals, to the northbound application to confirm the con-
nection.
l To forward heartbeat traps, select the check box and select the time interval
(0-60 minutes) for heartbeat trap forwarding. Select Deploy to continue.
l The deployment results are displayed, and the event NBI icon is displayed in
the Tree and Map Viewers.
10. To close the Event Forwarding Configuration window, select Close.
11. After deploying the event NBI, test its configuration to ensure the correct events
are being forwarded. Refer to Testing an Event NBI Configuration on page 291.
Testing an Event NBI Configuration

Once the event NBI configuration is set up, it is important to test it to verify that the
communication channel works and that the configuration was set up correctly. Typ-
ically, you would use this test under one of the following circumstances:
l Migrating from ProVision to ProVision
l New ProVision deployment
l Higher-level manager has changed
When you test an event NBI configuration, ProVision generates events that match
the filter settings and forwards these to the configured destination.
614-330053-001 APRIL 2014 291

Once the test is completed, you can verify that the communication channel is valid
and that the configuration was set up properly.
For example, the Eclipse radio (depending on the mix of plug-ins) could have 400 or
more messages for each of the four alarm events: raise, clear, acknowledge, and unac-
knowledge. So, for example, if you ran a test procedure on a network with 100
identical Eclipse radios without limiting the number of devices to be tested, ProVi-
sion tests all 400 or so messages for each alarm event and for each radio. This
amounts to 160,000 messages and can take over 11 hours.
CAUTION:Aviat Networks recommends limiting the number of devices
of the same type when executing this test function. Otherwise a
lengthy test procedure could result.
The test feature i s onl y avai l abl e for the SNMP i nterface.
Filter Settings Procedure

To limit the number of devices that undergo the test procedure (and thereby limit
the length of the test), use the filter settings as described in the procedure below.
1. From the Tree Viewer, right-click the required NBI event icon.
2. Select Edit from the right-click menu to display the The Event Forwarding Con-
figuration window.
3. Select the Filters tab to display the current filter settings.
4. Select the Edit button to display the Filters window.

5. Make any required changes, then select OK.
6. Select OK to close the Event Forwarding Configuration window.
Test Procedure
The right-click menu is displayed.
2. Select Test. The Event Forwarding Test window is displayed.
292 AVIAT NETWORKS

3. To start the event NBI configuration test, select Start. The Event Forwarding dis-
ruption message is displayed.
4. To proceed with the configuration test, select Yes.

l The verification test may take some time. When the test is finished the Save
button is enabled.
l Select Cancel to end the verification test.
5. A message displays, prompting you to save the Event Forwarding Report.
6. Select Save to save the event forwarding report. The default location and filename
is:
<pvroot>\ProVisionClient\NBI\Event \filename.test
where filename is the event NBI name you selected when you deployed it.
7. To change either the directory name or file name, select the directory select icon
, browse to the required location, and select Save.
8. The event forwarding report can be viewed in a document or spreadsheet applic-
ation.
614-330053-001 APRIL 2014 293

Saving, Printing, and Viewing an Event NBI

Configuration Report
You can view and save the event destination configuration details. This can include
the event forwarding destination, the filters, the event sources, and the events that
can be generated, including the event ID and description.
The report detailing the event destination configuration can be printed or saved as
an ASCII file. The default location for the file is:
<pvroot>\ProVisionClient\NBI\Event
The filename matches the event NBI name you entered when you deployed the event
NBI and the suffix “.rec”. For example the event NBI named OpenView has the file
name OpenView.rec. Use a text editor to view the file.
The detai l s di spl ayed i n the Event F orwardi ng Report wi ndow
and the saved report are di fferent: see the report val ues
tabl e i n thi s topi c.
Procedure
1. From the Tree Viewer, right-click the required NBI event icon. The right-click
menu is displayed.
2. Select Report. The Event Forwarding Configuration Report window is displayed.
3. To save the report, select Save.

4. To save the file in the default directory, select Save.
5. To save the file in another directory, select the button to open the directory
browser. Browse to the desired directory, enter the file name, then select Save. In
the Save Event Forwarding Report window, select Save.
6. To print the report, select Print. Select the required printer in the Print window,
then select OK.
7. The report values in the saved file are listed in the table below.
Table 12-4. NBI Event Information Report Values
294 AVIAT NETWORKS

Field Description
1 - Type of Event Identifies the event type: Acknowledged (3), Cleared (2),
Raised(1)
2 - Server Address
3 - Trap Index The unique number allocated by ProVision to each for-
warded event
4 - Trap Timestamp Date / Time the entry was added to the file
5 - Blank row No data
6 - Trap Source Path The full physical path of the device where the event
occurred
7 - Trap Device Type Class of device, for example, an Eclipse IDU radio
8 - Trap Source IP address of the object (radio or ProVision server) raising
Address the event
9 - Trap Device ID Unique ID of the device generating the event
10 - Event ID Unique ID of the type of event
11 - Event The event time recorded in the ProVision database
Date/Time
12 - Event State Status of event: Active (0), Cleared by User(1), Cleared by
Network / Resync (2), Cleared( 3)
13 - Event Severity Severity of event: Critical (6), Major(5), Minor (4), Warning
(3), Normal(2), Informational(1)
14 - Event Name A description of the event, for example, Trib 13 uncom-
missioned traffic
15 - NBI Integer ID Unique ID of this event
16 - Event Category Category of event: Unknown (0), Communications (1),
Environmental (2), Equipment (3), Processing Error (4),
Quality of Service (5)
17 - User Name The user name associated with this event.
Editing an Event NBI Configuration

To edit an event NBI configuration:
menu is displayed.
2. Select Edit. The Event Forwarding Configuration window is displayed.
614-330053-001 APRIL 2014 295

3. The configuration options are described below. Make any required changes on the
General and Filters tabs and select OK.
4. To close the Event Forwarding Configuration window, select OK.
Table 12-5. Configuration Options When Editing an Event NBI
Filter Setting Filter Options

General Tab Destination Name = Name of this event NBI’s destination (higher-level net-
work manager, name of the computer receiving events).
SNMP = Check this to enable SNMP forwarding.
IP Address = IP address of the northbound computer.
UDP Port = UDP port number.
Community String = Community string name.
Insert Probable Cause = Check to insert a Probable Cause field into the trap
(PVRaiseTrapwithCause is used instead of PVRaiseTrap).
Save to ASCII File =Check to save the Event MIB as an ASCII file.
Output to TCP Port = Check to enable output to the TCP port. Enter the TCP
Port on which the northbound destination system receives the event data.
Filters Tab Current filter settings are displayed. Select Edit to change them.
Advanced Tab The current heartbeat trap settings are displayed. A heartbeat trap is a message
that ProVision sends at regular intervals to the Northbound application to con-
firm the connection. See The Heartbeat Trap setting is displayed. A heartbeat
trap is a message that ProVision sends, at regular intervals, to the north-
bound application to confirm the connection. on page 291 for details.
Enabling/Disabling an Event NBI

By disabling an event NBI you are stopping events being forwarded to a NBI.
However, the configuration settings are still retained and can be enabled at a later
time.
296 AVIAT NETWORKS

The main reason to disable an event NBI is because the destination computer is off-
line or not yet set up.
Procedure
2. Enable or disable on the menu, as required.
Next Step
Resynchronize an Event NBI on page 297
Related Topics:
l Remote Resynchronize on page 298
l Deleting an Event NBI on page 298
l Renaming an Event NBI on page 299
Resynchronize an Event NBI

Occasionally a mismatch may occur between the data in ProVision database and in
the higher-order Network Management Level (NML) due to an interruption of the net-
work connection between the two levels.
For example, the object “pvTrapIndex” keeps track of the number of events. If this
value is 64 when the data is sent to the NML and the next time its value is 80, then
16 traps were missed. In this example, a resynchronization is required. The three-
step resynchronize process is:
1. The Network Management Level (NML) sends a resynchronize request trap to
ProVision.
2. ProVision tells the NML to clear all active events by sending resynchronization
event trap.
3. ProVision re-sends all active events to the NML.
The resynchronize process can also be manually invoked by the user. The steps are
described in the procedure on Procedure on page 298.
614-330053-001 APRIL 2014 297

Procedure
menu is displayed.
2. Select Resynchronize. The event data in ProVision and in the NML is syn-
chronized.
3. The resynchronize event is cleared from the event browser after it is completed. To
view the event, open an event browser by right-clicking the required NBI event icon
from the Tree Viewer.
4. Select Event Browser.
5. Select the filter icon to open the Filters window. The resynchronize events are
displayed in the Event Browser.
Remote Resynchronize
It is also possible to send a resynchronize command to the event NBI from the north-
bound application; as opposed to sending it from within ProVision. For more inform-
ation, see :
l Southbound Trap on page 303.
Deleting an Event NBI

To delete an event NBI:
298 AVIAT NETWORKS

2. Select Delete. The Delete Objects window is displayed.
3. To delete the selected object(s), select Yes.
Renaming an Event NBI

To rename an event NBI event:
menu is displayed.
2. Select Rename. The Rename window with the selected event NBI’s name is dis-
played.
3. Make the required changes to the name.

4. To save the changes, select OK.
Configure Services
For information on adding an event NBI to a service, refer to Services in the ProVi-
sion User Guide.
614-330053-001 APRIL 2014 299

Next Steps
System Integration for NBI Event Management

Event NBI descriptions are required if you are integrating the NBI output with a
higher level NMS.
The MIB file is: <Install Directory>/mibs/STXN-PV-TRAPS.MI2.
The MIB is installed on the ProVision server by default, when the ProVision server
software is installed.
Al l traps are SNMPv2 traps.
Northbound Trap
Within the events MIB there are four northbound event trap types:
l pvRaiseTrap - ProVision Raise Trap
l pvRaiseTrapwithCause - ProVision Raise Trap with Probable Cause included
l pvClearTrap - ProVision Clear Trap
l pvAcknowledgedTrap - ProVision Acknowledged Trap
These northbound event trap types contains the following objects.
pvTrapSourceAddress
l pvTrapIndex
l pvTrapTimeStamp
l pvTrapNotes
l pvEventSourcePhysicalPath
l pvEventSourceDeviceType
l pvEventSourceIPAddress
l pvEventSourceID
l pvEventID
l pvEventTimeStamp
l pvEventState
l pvEventSeverity
l pvEventName
l pvEventIDInteger
l pvEventCategory
l pvEventProbableCause (in pvRaiseTrapwithCause only)
Table 12-6. Event MIB Trap Details
300 AVIAT NETWORKS

Trap Details
OBJECT TYPE SYNTAX DESCRIPTION
pvTrapSourceAddress OCTET STRING This is the IP address and name (where avail-
(SIZE(0..40)) able) of the ProVision server where the trap is
sent from.
pvTrapIndex OCTET STRING This is a unique trap identifier. It represents a
(SIZE(0..20)) signed 64 number and it wraps once it reaches
its maximum. This is used for verifying if there
are missing traps so that a decision for resyn-
chronization can be made.
pvTrapTimeStamp DateAndTime This is the time when the trap is sent by the Man-
ager.
pvTrapNotes DisplayString This is used to provide additional information per-
taining to the traps sent from this source.
Table 12-7. Event MIB Event Details
Event Details
pvEventSourcePhysicalPath DisplayString This is the full physical path (including the
object itself) of the object where the event
occurred.
pvEventSourceDeviceType DisplayString This is the class type of the object where the
event occurred.
pvEventSourceIPAddress IpAddress This is the IP address of the object where the
event occurred.
pvEventSourceID OCTET STRING This is a unique identifier for the event source
(SIZE(0..20)) (e.g, a deployed radio in ProVision). It rep-
resents a signed 64 number. Together with
pvEventID, it forms a unique reference to an
event.
pvEventID OCTET STRING This is a unique identifier for an event and indic-
(SIZE(0..40)) ates the position of each event in the 'event
hierarchy definition' of a particular device type.
Together with pvEventSourceID, it forms a
unique reference to an event.
pvEventTimeStamp DateAndTime This is the event timestamp recorded in the
ProVision database.
pvEventState StateValue This is an integer number indicating the state of
the event. The possible states are:
ACTIVE = 0 (active event);
CLEARED_BY_USER = 1 (clearing event);
CLEARED_BY_NETWORK = 2 (clearing event);
CLEARED = 3
614-330053-001 APRIL 2014 301

Event Details
pvEventSeverity SeverityValue This is the perceived level of severity of the
event. The possible levels are:
UNDEFINED = 0
INFORMATIONAL = 1
NORMAL = 2
WARNING = 3
MINOR = 4
MAJOR = 5
CRITICAL = 6
pvEventName DisplayString This is the textual description of the event that
is logged and has the following format:
Event Name
';' + 1 space
Event Cause Location
';' + 1 space
Event Occurrence Location
Each detail must fill the allocated space where
unused spaces are padded with blank spaces.
An example of this is: Trip 13 uncommissioned
traffic inuaslot1 inuaslot1
pvEventIDInteger INTEGER This is a unique identifier for an event in Integer
format.
It is included for support of TeMIP integration.
It is an alternative to pvEventID. Together with
pvEventSourceID or pvEventSourceIPAddress,
it forms a unique reference to an event.
pvEventCategory INTEGER This is the X.733 classified category of the
event. Possible levels are:
CATEGORY_UNKNOWN = 0 (non X.733)
COMMUNICATIONS = 1
ENVIRONMENTAL = 2
EQUIPMENT = 3
PROCESSING_ERROR = 4
QUALITY_OF_SERVICE = 5
pvEventProbableCause DisplayString This identifies the probable cause of the event.
It is included if this option is set up for the Event
NBI in the Event Forwarding Configuration (see
Editing an Event NBI Configuration on page
295).
Northbound Status
The ProVision northbound status pvNorthBoundStatusTrap contains the following
objects as defined below:
302 AVIAT NETWORKS

Table 12-8. Northbound (NB) Status Details

pvNBStatusSourceIPAddress IpAddress This is the IP address of the ProVision server
pvNBStatusType INTEGER This is the status indication from ProVision.
The possible values are:
EventNBIheartbeat=1
Southbound Trap
ProVision also supports southbound traps. These are commands that the level 3
NML application sends to ProVision. The southbound trap pvSouthBoundCom-
mandTrap contains the following objects as defined below.
Table 12-9. Southbound (SB) Trap Details

pvSBSourceIPAddress IpAddress This is the IP address of the northbound
system that requires the command to be
executed.
pvSBCommand INTEGER This is the command available to the north-
bound system to remotely instruct ProVi-
sion. The possible values are:
EventNBIresync=1
Setting Up an Event NBI on page 285
614-330053-001 APRIL 2014 303

NBI Performance Data Management

This section contains the following topics.
l About NBI Performance Data Management on page 304
l Performance Data Collection on page 305
l Deploying a Performance Data NBI on page 307
l Editing Performance Data NBI Configuration on page 308
l Enabling/Disabling a Performance Data NBI on page 310
l Deleting a Performance Data NBI on page 311
l Renaming a Performance Data NBI on page 311
l Performance Data Files on page 312
About NBI Performance Data Management

The NBI performance data management feature enables the integration collected per-
formance data from managed devices with management systems for the network or
the service layer’s performance.
The integration is achieved through delivering the collected performance data from
the ProVision performance database as a set of ASCII text files that can be accessed
by a northbound system.
Prerequisites
The prerequisites for NBI performance data management include:
l The type of performance data you are interested in (15-minute, daily, or all.)
l The format of the output file (single/multiple files per device/device type).
l The output format of the performance data file (one file for each device or one
file for an entire device type).
l The frequency that the performance data files are to be purged from the server.
Associated Event
The one event that is associated with NBI performance data management is Per-
formance NBI Activation , which initiates the performance data to be forwarded to
the NML
Performance data is collected by the following sources:
304 AVIAT NETWORKS

l Device daily bins

l Device 15-min bins
l Device real-time data
ProVision performance data is gathered by a specific collection application.
The collected performance data is saved to a database in ProVision.
Then, the performance data is analyzed and divided:
l ProVision performance data is displayed in the History Viewer and the Trends
Viewer.
l Northbound Interface performance data is stored in files marked for devices
and device types.
Northbound Interface performance data is accessed via network file sharing and FTP.
Performance Data Collection

This section describes the performance data collection for Eclipse devices. Spe-
cifically, it describes how the Eclipse device bin file that is stored on the device
relates to the ProVision database and NBI files.
This process is illustrated below, where the numbers in the figure refer to the
numbered steps below. In this example, the network is set up for daily data col-
lection and the data is collected for the purposes of the NBI as per device type.
See Editing Performance Data NBI Configuration on page 308 for information on the
data collection options.
It is not feasible for ProVision to read all daily bins from all of the devices in the net-
work due to processor loading and NMS channel restrictions. Therefore the collection
of the data from the bins is staggered over a 24 hour period.
Figure 12-2. Eclipse Device Performance Data Collection and NBI Behavior
1. Each Eclipse device creates a daily bin file at 12:00 midnight for that day. In this
example, a block of data we will call “Sunday bin” (blue) is created at the end of the
day at 12:00 midnight.
614-330053-001 APRIL 2014 305

2. For this example, let’s assume a network operator enables daily data collection at
00:00 am on Monday.
l 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.
l See File Naming Convention on page 312 for more information on the
performance data file name.
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.
l A performance bin file with a time stamp for “Monday midnight” is created in
the database when ProVision reads the data from the first device on Tuesday.
7. Again, from 00:00 am on Tuesday, ProVision starts collecting the “Monday bin”
data collection from all the devices. The bins are written to the ProVision database,
until all bin devices are read and recorded.
8. ProVision writes the “Monday bin” data to the NBI files at the same time as it
writes to the ProVision database.
As long as data collection is enabled, ProVision continues to collect the previous
day’s daily bin data.
This procedure applies to the G.826 performance as well as the Ethernet statistics
data collection. However, since Ethernet data collection is based on real-time counts
in the device, ProVision only creates the first Ethernet bin AFTER two samples (24
hours apart). Therefore, in the above example, the first bin of data is created at the
end of the day on Tuesday.
Other points to keep in mind when collecting NBI performance data:
l If the ProVision server is restarted, than all daily performance data collection
is rescheduled, where the data collection is spread out over the next 24 hours.
l If the radio loses communications, then the radio’s daily performance
collection is also rescheduled.
l If the method of NBI performance data collection is “per device type”, then the
performance file is not complete until the next file is created.
Next Step:
Deploying a Performance Data NBI on page 307
306 AVIAT NETWORKS

Deploying a Performance Data NBI

The ProVision server periodically polls the managed network devices and stores the
events generated in the ProVision database. The NBI performance data is extracted
from the ProVision database.
Before depl oyi ng the performance data NBI , thi nk about the
NBI performance data setti ngs you want to i mpl ement. F or
exampl e, i f 15-mi n. and dai l y data types are enabl ed and the
output fi l e i s set to per Devi ce; for a network of 200 radi os
thi s creates 200 dai l y performance data fi l es and 19200 15-
mi n. performance data fi l es each day. Thi s coul d very qui ckl y
cause probl ems wi th the computer’ s fi l e al l ocati on system
unl ess the fi l es are purged on a regul ar basi s.
Procedure
menu is displayed.
3. Select the performance data NBI icon. The Deploying Performance Data-for-
warding window is displayed. For details of the performance data settings, see Edit-
ing Performance Data NBI Configuration on page 308.
614-330053-001 APRIL 2014 307

4. To save the performance data NBI configuration, select Deploy.

The deployment results are displayed, and the performance data NBI icon is dis-
played in both the Tree and Map Viewers.
5. To close the Deploying Performance Data-forwarding window, select Close.
Editing Performance Data NBI Configuration

To edit a performance data NBI configuration:
1. From the Tree Viewer, right-click the required performance data NBI icon.
2. Select Edit.\ The Performance NBI Configuration window is displayed.
3. When you select your output file format, the purge criteria for the output file
format display. Set the required purge criteria.
4. Make any other required changes and select OK.
Table 12-10. Performance Data NBI Settings
308 AVIAT NETWORKS

Performance Description and Actions

Data NBI Con-
figuration
Name Type a name for the performance data NBI.
Data Type The options are: Ethernet 15-Min, 15 Min, and Daily.
Daily is selected by default. To enable the Ethernet 15-min or 15-min data col-
lection, select the checkbox. All types of performance data collection can be
enabled for NBI forwarding.
Only data from devices currently being performance monitored by ProVision is
exported. Performance data collection is detailed in the ProVision User Guide, Sys-
tem Diagnostics.
Output File To set output file types, select one option from the Format drop-down menu and
one option from the Per drop-down menu:
- Multiple Files and Device = Each performance data file contains a single
record for a single device.
- Multiple Files and Device Type = Each performance data file contains a
single record for all devices of a particular type.
- Single File and Device = Each performance data file contains all records for a
single device.
- Single File and Device Type = A single performance data file is created con-
taining all records for all devices of a particular type.
- Single File and Device Type with RF Grouping = A single performance
data file is created, with data noted by RF grouping.
- Single File and Device Type per Day =A single performance data file is cre-
ated for each device type once a day.
NOTE: Device Type per Day is only available when Single Device is selected as the
Format.
614-330053-001 APRIL 2014 309

Performance Description and Actions

Data NBI Con-
figuration
Purge Criteria By default,the current NBI file is renamed to ".old" and a new NBI is created every
7 days for 15-minute data and every 30 days for Daily data.
Where the option is available for the format type, use the up and down arrows to
set the daily purge criteria from 1 to 52 weeks.
By default the 15-min NBI performance data files older than one day are purged.
Use the up and down arrows to set the 15-min purge criteria from 1 to 60 days.
For the Single File per Device Type per Day, you can enable or disable the
purge by clicking Purge Enabled.
Enable Enable or disable the performance data NBI.
Enabling/Disabling a Performance Data NBI

Disabling a performance data NBI stops the generation of NBI performance data
files. The configuration settings are retained and can be enabled at a later time.
Procedure
1. From the Tree Viewer, right-click the required performance data NBI icon.
2. Enable or disable the performance data NBI, on the menu, as required.
Next Step
Deleting a Performance Data NBI on page 311
Related Topics:
310 AVIAT NETWORKS

l Renaming a Performance Data NBI on page 311

Deleting a Performance Data NBI

To delete a performance data NBI:
1. From the Tree Viewer, right-click the required NBI icon.

Renaming a Performance Data NBI

To rename a performance data NBI:
1. From the Tree Viewer, right-click the required performance NBI icon. The
right-click menu is displayed.
2. Select Rename. The Rename window with the selected performance data NBI’s
name is displayed.

614-330053-001 APRIL 2014 311

Configure Services
For information on adding a performance data NBI to a service, refer to Services in
the ProVision User Guide.
Related Topic:
Performance Data Files

Directory Location
The performance data NBI configuration outputs are stored in text files in
<pv root>\ProVisionServer\NBI\Performance.
The daily and 15-min data are stored in separate subdirectories. For example, a per-
formance data NBI configuration named AviatToNML, that outputs data, stores the
data in the following directories:
<pv root>\ProVisionServer\NBI\Performance\AviatToNML\daily
<pv root>\ProVisionServer\NBI\Performance\AviatoNML\15-minute
File Naming Convention

The file naming convention is based upon the performance data criteria that was
selected when the performance data NBI was set up:
l Data Type =15-min and/or daily
l Output File = per Device Type, per Device, or Device Type per Day
312 AVIAT NETWORKS

Table 12-11. File Naming by File Type
File Name
File Type Sample File Name
Components
15-minute and This example has an Eclipse Link as the device type - Eclipse Link
Per and 24Aug2013 1:45p.m. as the day/time stamp. = device
Device Type PVV_EclipseLink_201308241345_900.txt type
- 2013 = YYYY
- 08 = MM
- 24 = DD
- 13 = HH
- 45 = MM
Daily and Per This example has an Eclipse IDU as the device type - Eclipse IDU
Device Type and 22Aug2013 12:00 midday as the day/time = device
and stamp. type
Device Type PVV_EclipseIDU_201308221200_ - 2013 = YYYY
per Day daily.txt - 08 = MM
- 22= DD
- 12 = HH
- 00 = MM
15-minute and This example has INU08-Link 3 as the device type - INU08-Link3
Per Device and 24Aug2013 1:45 p.m. as the day/time stamp. = device
PVV_INU08-Link3_201308241345_900.txt type
- 2013 = YYYY
- 08 = MM
- 24 = DD
- 13 = HH
- 45 = MM
614-330053-001 APRIL 2014 313

File Name
File Type Sample File Name
Components
Daily and Per his example has INU01-Link 2 as the device type and - INU01-Link2
Device 22Aug2013 12:00 midday as the day/time stamp. = device
PVV_INU01-Link2_201308221200_ type
daily.txt - 2013 = YYYY
- 08 = MM
- 22= DD
- 12 = HH
Accessing Files Via FTP

NBI performance data files can be accessed from the ProVision server through a
shared network drive. They can also be accessed through the FTP server that is
embedded into ProVision. When accessing the performance files using FTP, the north-
bound performance management system needs to log into ProVision’s FTP server
using the following login.
l User: nbi
l Password: nbi
l Port: 5555
l When a performance data NBI is deployed, the data file generation starts after
the next bin is collected from the device.
Performance Data Definitions

The following is a list of commonly collected performance parameters. The data that
is collected varies depending on the parameters supported by the device.
Many of these objects are measured over a fixed measurement interval; 15
minutes or daily (24 hours).
F or a l i st of performance data supported for each devi ce type,
see the fi l e v6.11.4_device_performance_parameters_
list.txt, i n the Documentati on fol der on the ProVi si on
rel ease medi a.
Table 12-12. Performance Data Definitions
Object Description
Device IP Address The IP address of the radio providing the data.
G.826 Available Seconds (AS) Total available time during a fixed measurement interval.
G.826 Unavailable Seconds Total unavailable time during a fixed measurement interval.
(US)
G.826 Errored Seconds (ES) A one-second period with one or more errored blocks or at
least one defect.
G.826 Severely Errored A one-second period which contains at least 30% errored
Seconds (SES) blocks or at least one defect.
314 AVIAT NETWORKS

Object Description
Frame Loss Seconds The number of seconds that an Out Of Frame error is detec-
ted.
G.826 Errored Blocks (EB) A block of data where one or more bits of data are in error.
G.826 Background Block Errors An errored block not occurring as part of an SES.
(BBE)
G.826 Errored Seconds Ratio The ratio of errored seconds (ES) to the total available time
(ESR) during a fixed measurement interval.
G.826 Severely Errored The ratio of severely errored seconds (SES) to total available
Seconds Ratio (SESR) time during a fixed measurement interval.
G.826 Background Block Errors The ratio of background bloc errors (BBE) to total blocks in
Ratio (BBER) the available time during a fixed measurement interval.
RSL Mean Arithmetic average of the Received Signal Level (RSL) during
a fixed measurement interval. The RSL is the signal level at a
receiver input terminal.
RSL Maximum Maximum RSL during a fixed measurement interval.
RSL Minimum Minimum RSL during a fixed measurement interval.
BER Mean Arithmetic average of the Background Error Measurement
during a fixed measurement interval.
BER Maximum Maximum Background Error Measurement during a fixed
measurement interval.
BER Minimum Minimum Background Error Measurement during a fixed
measurement interval.
Remote End Device Name The name of the radio at the remote end of the link.
Remote End Device IP Address The IP address of the radio at the remote end of the link.
Next Step:
NBI Configuration Management on page 316
Related Topic:
l Deleting a Performance Data NBI on page 311
614-330053-001 APRIL 2014 315

NBI Configuration Management

l About NBI Configuration Management on page 316
l Deploying a Configuration NBI on page 317
l Editing the Settings for a Configuration NBI on page 318
l Setting the Configuration NBI on page 319
l Enabling/Disabling a Configuration NBI on page 319
l Resynchronizing a Configuration NBI on page 320
l Deleting a Configuration NBI on page 321
l Renaming a Configuration NBI on page 321
l System Integration on page 322
About NBI Configuration Management

NBI confi gurati on management i s onl y supported for CTR 8440
devi ces, Ecl i pse devi ces, EI ON StarMAX base stati ons, WTM
3100, 3200, and 3300 devi ces, EI ON StarMAX Wi MAX ASN-C,
and Al ti um 1 and 155 devi ces.
NBI configuration management includes all the information relevant to the con-
figuration of a network. The output is in XML format and includes information such
as:
l ProVision server name and IP address
l Device name, type and IP address
l Plug-in name, type, part number, serial number and software version
l Specific plug-in information such as capacity and bandwidth
l Link information
l Cross-connect information
This information is very useful in that it helps you keep track of the inventory that
makes up the network, plan a new network, and improve existing networks.
Associated Events
The events associated with NBI configuration management are:
316 AVIAT NETWORKS

l Configuration NBI activation - Initiates the network configuration data to be

forwarded to the NML.
l Configuration NBI file updated - Updates the network configuration data in
the NML.
Deploying a Configuration NBI

When accessing the NBI configuration files using FTP, the NBI configuration man-
agement system needs to log into ProVision’s FTP server using the following login.
l User: nbi
l Password: nbi
l Port: 5555
The configuration is applied after the next bin is collected from the device.
Procedure
menu is displayed.
3. Select the configuration NBI icon. The Deploying Configuration-for-

warding window is displayed.
614-330053-001 APRIL 2014 317

4. To save the configuration NBI configuration, select Deploy. The deployment res-
ults are displayed, and the configuration NBI icon is displayed in both the Tree and
Map Viewers.
5. To close the Deploying Configuration-forwarding window, select Close.
Editing the Settings for a Configuration NBI

To edit the settings for a configuration NBI:
1. From the Tree Viewer, right-click the required configuration NBI icon.
2. Select Edit.
The Configuration NBI window is displayed.
3. Make the required changes and select OK.
Next Step
Setting the Configuration NBI on page 319
318 AVIAT NETWORKS

Related Topics:
l Resynchronizing a Configuration NBI on page 320
Setting the Configuration NBI

Table 12-13. Configuration NBI Settings
Configuration Description and Actions

Setting
Name Type a name for the configuration NBI.
Configuration Basic Configuration includes information on the NBI destination,
Components device and network inventory.
Circuit Configuration includes information on the radios, links,
and cross-connections.
Enabled By default, the configuration NBI is enabled. Select or de-select the
check box to enable the configuration NBI as required.
Dep loy ing a C onfigu rat ion NBI on p age 317
Enabling/Disabling a Configuration NBI

Disabling the configuration NBI stops the generation of NBI configuration files. The
settings are retained and can be enabled at a later time.
Procedure
2. Enable or disable the configuration NBI, on the menu, as required.
Next Step
Resynchronizing a Configuration NBI on page 320
Related Topics:
l Deleting a Configuration NBI on page 321
614-330053-001 APRIL 2014 319

l Renaming a Configuration NBI on page 321

Resynchronizing a Configuration NBI

The resynchronize feature for configuration NBI obtains an image of the system to be
stored in the database. The database is updated periodically; the information in the
database is from the last update, and not from the radios’ current configuration.
The configuration file is located in following directory where icon_name is the name
of the NBI configuration management icon:
<pv root>\ProVisionServer\NBI\Configuration\icon_name
The line called <creation date> indicates when the configuration file was last
updated. For example, the file with the following notation was created on 12 July
2009 at 4:51 p.m.
<creation_date>Fri Jul 12 16:51:21 NZST 2009</creation_date>
The output file collected the last time the resynchronization feature was performed
on the configuration NBI can be used in the event the network needs to be rebuilt.
The output file can now be sent via FTP.
Procedure
1. From the Tree Viewer, right-click the required configuration NBI icon. The
2. Select Resynchronize. to display the Configuration NBI Resync window.
3. Select Start.
l Select Abort to stop the resynchronization process.
l The resynchronization process is complete when the bar graph reads 100%.
4. Select Close to close the Configuration NBI Resync window.
320 AVIAT NETWORKS

Deleting a Configuration NBI

To delete a configuration NBI:
Renaming a Configuration NBI

To rename a configuration NBI:
1. From the Tree Viewer, right-click the required configuration NBI icon. The
2. Select Rename. The Rename window with the selected configuration NBI’s name
is displayed.

614-330053-001 APRIL 2014 321

Configure Services
For information on adding a configuration NBI to a service, refer to Services in the
ProVision User Guide.
See also:
System Integration
This section describes the NBI configuration management output file. The file is in
XML format and contains the information listed in the following sections.
To create an NBI configuration management file for your specific system, you must
first generate a management file on your network. The files are located in the fol-
lowing directory where icon_name is the name of the NBI configuration man-
agement icon:
<pv root>\ProVisionServer\NBI\Configuration\icon_name
Next, modify that file to include the information listed on this and subsequent
pages.
NBI
The NBI section includes:
l NBI configuration file name
l ProVision server name
l ProVision server IP address
l Date the file was created.
The format is:
<name>Cfg Test</name>
<pvv_server_name>All Real Eclipse</pvv_server_name>
<conserver>10.16.15.15</pvv_server_ip_addr>
<creation_date>Fri Jul 12 16:51:21 NZST 2005</creation_date>
Device
The Device section refers to the Eclipse radio devices and includes:
322 AVIAT NETWORKS

l Device name
l Device IP address
l Device type
l Path the device is deployed in ProVision
The format is:
<device_identifier>
<name>INU 145</name>
<ip_addr>10.16.10.145</ip_addr>
<type>INU</type>
<container>/ProVision</container>
</device_identifier>
Inventory
The Inventory section refers to the plug-in components and includes:
l Component name
l Component type
l Component part number
l Component serial number
l Component software version (where applicable)
The format is as follows:
<component>
<name>NCC</name>
<type>NCC</type>
<part_number>EXN-002</part_number>
<serial_number>LEA05030552</serial_number>
<software>03.00.34</software>
</component>
Components
The Components section contains information specific to a particular plug-in. For
example, a RAC plug-in would need to have information such as capacity and band-
width specified. An example RAC plug-in with ATPC disabled is:
<component>
<local_interface>LINK2</local_interface>
<prot_type>non-protected</prot_type>
<primary>
<plugin>RAC2</plugin>
<capacity>40E1</capacity>
<bandwidth unit="MHz">28</bandwidth>
<modulation>16 QAM</modulation>
<freq_range_tx unit="MHz">14921-15068</freq_range_tx>
614-330053-001 APRIL 2014 323

<freq_band_tx>Tx High</freq_band_tx>
<freq_tx unit="MHz">15010</freq_tx>
<freq_rx unit="MHz">14520</freq_rx>
<freq_tx_rx_spacing unit="MHz">-490</freq_tx_rx_spacing>
<tx_power_settings>
<atpc>
<status>disabled</status>
</atpc>
<tx_power unit="dBm">10.0</tx_power>
</tx_power_settings>
</primary>
</component>
Link
The Link section includes information on the links between the radios. The format is:
<link>
<local_interface>LINK1</local_interface>
<remote_object_name>INU 199</remote_object_name>
<remote_container>/ProVision</remote_container>
<remote_ip_addr>10.16.10.199</remote_ip_addr>
<remote_interface>LINK1</remote_interface>
</link>
Cross-Connect
The Cross-Connect section includes information on the connections that make up a
particular circuit. The format is:
<cross-connect>
<name>Unnamed circuit 1</name>
<local_interface_1>LINK1</local_interface_1>
<local_port_1>1</local_port_1>
<remote_object_name_1>INU 199</remote_object_name_1>
<remote_object_container_1>
/ProVision
</remote_object_container_1>
<remote_ip_addr_1>10.16.10.199</remote_ip_addr_1>
<remote_interface_1>LINK1</remote_interface_1>
<remote_port_1>1</remote_port_1>
<local_interface_2>DAC3</local_interface_2>
<local_port_2>1</local_port_2>
<remote_object_name_2>Unknown</remote_object_name_2>
<remote_object_container_2>
324 AVIAT NETWORKS

Unknown
</remote_object_container_2>
<remote_ip_addr_2>Unknown</remote_ip_addr_2>
<remote_interface_2>Unknown</remote_interface_2>
<remote_port_2>Unknown</remote_port_2>
</cross-connect>
614-330053-001 APRIL 2014 325

NBI Topology Management

l About NBI Topology Management on page 326
l Deploying a Topology NBI on page 327
l Editing the Settings for a Topology NBI on page 328
l Enabling/Disabling a Topology NBI on page 329
l Deleting a Topology NBI on page 329
l Renaming a Topology NBI on page 330
l Configuring a Topology NBI for Services on page 330
l NBI Topology Files on page 331
About NBI Topology Management

The NBI topology management feature is similar to the import and export topology
feature described in Migrating Topology on page 161. It collects information on net-
work topology, including:
l Object type
l Object name
l Object containment definition
l Device IP address
l SNMP community strings
l Object state (managed or unmanaged)
l Object performance data collection state (daily enabled/disabled, 15-minute
enabled/disabled)
l Object coordinates (in the Map Viewer)
However, NBI topology management is more robust in than the import and export
topology feature for the following reasons:
1. It saves the topology as icons on the physical and map viewers.
2. It schedules the topology export for automatic execution.
3. The file in which NBI topology is collected can be sent via FTP.
NBI topology management can be very useful when rolling out a new network. If you
periodically save the network topology, it is easy to restore the network if there are
any problems.
The events associated with NBI Topology management are listed in the table below:
Table 12-14. NBI Topology Management Events
326 AVIAT NETWORKS

Event Description
Topology NBI activation Notes when a topology NBI is deployed.
Topology NBI output file created Notes when a topology NBI output file is cre-
ated or updated.
Deploying a Topology NBI

To deploy a topology NBI:
1. In the Tree Viewer, physical pane right-click the ProVision Manager icon.
3. Select the topology NBI icon. The Deploying Topology window is displayed.
614-330053-001 APRIL 2014 327

4. To save the topology NBI configuration, select Deploy. The deployment results
are displayed, and the topology NBI icon is displayed in both the Tree and Map
Viewers.
5. To close the Deploying Topology window, select Close.
Editing the Settings for a Topology NBI

To edit the settings for a topology NBI:
1. From the Tree Viewer, right-click the required topology NBI icon. The right-
click menu is displayed.
2. Select Edit. The topology NBI window is displayed.
3. Make the required changes and select OK.

Table 12-15. Topology NBI Settings
Topology Setting Description and Actions

Name Type a name for the topology NBI.
Execution Criteria Allows you to set the time of day that the daily output is generated. Use
the up and down arrows to set the hour, then select AM or PM.
Purge Criteria Allows you to set the length of time that files are to be kept. Use the up
and down arrows to set the number of days for the files to be purged.
Enabled By default, the configuration NBI is enabled. Select or de-select the check
box to enable the configuration NBI as required.
Next Step
Enabling/Disabling a Topology NBI on page 329
328 AVIAT NETWORKS

Related Topics:
l Deleting a Topology NBI on page 329
Enabling/Disabling a Topology NBI

Enabling the topology NBI activates the generation of NBOI topology files. Disabling
the topology NBI stops the generation of NBI topology files. The settings are retained
and can be enabled at a later time.
Procedure
1. From the Tree Viewer, right-click the required topology NBI icon.
2. Enable or disable the topology NBI, on the menu, as required.
Next Step
Deleting a Topology NBI on page 329
Related Topics:
Deleting a Topology NBI

To delete a topology NBI:
2. Select Delete.
The Delete Objects window is displayed.
614-330053-001 APRIL 2014 329

Renaming a Topology NBI

To rename a topology NBI:
2. Select Rename. The Rename window with the selected topology NBI’s name is dis-
played.

Configuring a Topology NBI for Services

For information on adding a topology NBI to a service, refer to Services in the ProVi-
sion User Guide.
See also:
330 AVIAT NETWORKS

NBI Topology Files

File Location
The topology NBI configuration outputs can be found in the directory:
<pvroot>\NBI\Topology
Accessing Files Via FTP

NBI topology data files can be accessed from the ProVision server through a shared
network drive. They can also be accessed through the FTP server that is embedded
into ProVision. When accessing the topology files using FTP, the northbound topo-
logy management system needs to log into ProVision’s FTP server using the fol-
lowing login.
l User: nbi
l Password: nbi
l Port: 5555
When a topology NBI is deployed, the data file generation starts after the next bin is
collected from the device.
The topol ogy NBI data fi l e has the same format as the output
that i s generated when usi ng the topol ogy export command.
See Exp ort ing t he Top ology on p age 16 4 i n the I nstal l ati on and
Admi ni strati on Gui de for addi ti onal i nformati on.
System Integration - NBI Topology Files

This section describes the NBI topology output XML file. Each object that makes up
the network is defined by the command:
<object class=’objectname’>
.
.
.
</object>
The following sections give examples of the network objects contained in an NBI
topology output file:
614-330053-001 APRIL 2014 331

Network
The Network section lists the name of the object; in this case, “Lower North Island”:
<object class="network">
<name>Lower North Island</name>
</object>
Radio
Each individual radio in the network has its own section that lists the radio’s name,
physical path, IP address, software version, and other details:
<object class="unity_inu">
<name>INU 198</name>
<physical_path>/Real Radios/INU 198</physical_path>
<read_community>terminal</read_community>
<discover>discover</discover>
<write_community>terminal</write_community>
<is_agent type="boolean">true</is_agent>
<is_chassis type="boolean">true</is_chassis>
<non_container_with_children type="boolean">true>
</non_container_with_children>
<state>connecting</state>
<position type="point">358, 282</position>
</object>
Plug-in
As with the radios, each individual plug-in also has its own section that lists the
plug-in’s name, physical path, IP address, slot number, and other details.
<object class="unity_dac">
<name>DAC3</name>
<physical_path>/Real Radios/INUe/DAC3</physical_path>
<slot>3</slot>
<read_community>slot3</read_community>
<write_community>slot3</write_community>
<position type="point">414, 200</position>
</obj>
332 AVIAT NETWORKS

Link
Each link has its own section that lists the two radios it connects, and the names of
the ODUs that make up the link.
<object class="link">
<name>LINK1 - LINK2</name>
<end_points type="vector">
<obj type="ref">/Site/Kiwi Point/LINK1</obj>
<obj type="ref">/Site/Mount Vic/LINK2</obj>
</end_points>
</object>
614-330053-001 APRIL 2014 333

Chapter 13. Help Desk Reports
The Help Desk Report collects information about the environment and configuration
of ProVision. Run and save this report to provide a record of your system’s con-
figured setup, and to send to Aviat Networks Technical Support when you have a
problem.
l The Help Desk Report on page 336
l Running the Help Desk Report on page 336
l Using Commands to Run Help Desk Reports on page 337
l Saving or Deleting Help Desk Reports on page 338
614-330053-001 4/04/2014 335

CHAPTER 13. HELP DESK REPORTS
The Help Desk Report

The Help Desk Report collects information about the environment and configuration
of ProVision. It captures the configuration and license information of your ProVision
installation whenever you run the report. This report is important for system main-
tenance and support.
The Help Desk Report must be run and saved at the time that your system is fully
commissioned. This captures the environment and configuration of your ProVision
installation.
The purpose of this report is to capture any problems in your system, and to collate
all the information required to enable the Aviat Networks HelpDesk to assist you
with your problem. The Aviat Networks HelpDesk compares the data in your Help
Desk report to the Help Desk report that you generated at the time of system com-
missioning.
This report automatically includes:
l License details
l System configuration
l Log of SNMP round trip times for each radio
l Log of heartbeat round trip times between the client and the server
l Client log files
l Server log files
l Server Status page log files (stored as .zip files, located inside
ProVisionServer/repository/logs/statuspages)
You can generate this report to include your current database. If a database is not
included in a Help Desk report, the topology export file will be included. All the Help
Desk report data is saved in one Zip file, with the name and date. It is saved to the
file location:
ProVisionServer/repository/reports
Running the Help Desk Report

You can run a Help Desk report at any time. Note the following:
l Generating an additional Help Desk Report does not over-write any previous
Help Desk Reports.
l Including the database in a Help Desk Report increases the size of the Help
Desk report zip file. If you need to send multiple Help Desk reports to the
Aviat Networks HelpDesk, we recommend that you include your database with
the first Help Desk Report that you send. Then, later Help Desk Reports can be
336 AVIAT NETWORKS

sent without the database. (If a database is not included in a Help Desk
report, the topology export file will be included.)
Procedure
1. To run the main commissioning report, in the menu bar, go to Reports. Click on
Help Desk.
2. The Report Information screen displays.
3. Check boxes if you want to:

l Include the database backup in the report.
l Open the Task Manager.
l Then, click OK.
4. The Task Manager displays the status of the report generation and shows when
the report is complete.
5. Go to the file location where the Help Desk report has been saved:
ProVisionserver/repository/reports
6. The report file is there, with values for the date and time it was created in its title:
PV_HelpDesk_Report_<Weekday>_<Date>_<ReportID>_<TimeZone>.zip
Send this zip file to your Aviat Networks support contact. Save a copy of this at an
archive location for your users.
Using Commands to Run Help Desk Reports

You can use commands to run the Help Desk Report from a command line. This is
useful if you are having problems with the client or server, and you cannot run the
Help Desk Report in ProVision.
Procedure
To run the ProVision client report from the Commands window;
614-330053-001 APRIL 2014 337

CHAPTER 13. HELP DESK REPORTS
1. From the Start menu, go to Start > All Programs > ProVision Server > Com-
mand Window.
2. Enter the command: pv report
3. The system will ask, “Do you want to include database backup in the report?”
Type Y for yes or N for no.
4. The ProVision Client Help Desk report is generated. The Command window shows
the location where the report is saved.
5. Send the completed Client report .zip to ProVision technical support.
To run the ProVision server report from the Commands window:
1. Log into the server where the ProVision Server is installed and open a command
window, as noted above.
2. Enter the command to run the report, based on whether ProVision is running on a
Windows or a Solaris system:
l Windows = pv report
l Solaris = ./pv_report
3. The ProVision Server Help Desk report is generated. The Command window shows
the system location where the report is saved:
4. Retrieve and send the Server report .zip to ProVision technical support.
Saving or Deleting Help Desk Reports

After you have created a Help Desk report, you can also:
l Save the Help Desk report to an additional network location
l Delete the Help Desk report.
338 AVIAT NETWORKS

Procedure
1. In the menu bar, go to Reports. Click on Server Reports.
2. The Server Report Information screen displays.
3. This screen displays all the Help Desk reports that are saved in the ProVision data-
base.
4. To save a Help Desk report to an additional network location, click the
Save button for that report .

5. The Save As screen displays.
6. Choose the network location where you want to save the report. Edit the file name
of the report. Then, click Save.
7. The report is saved to the specified network location.
8. To delete a Help Desk report from the system, click the Delete icon.
9. The selected Help Desk report is deleted.
614-330053-001 APRIL 2014 339

Chapter 14. ProVision Web
Server
This section describes how and when to use the ProVision Web Server.
Web Server Overview

Why a separate Web Server? The ProVision Web Server is an administrative shortcut,
accessed via a web browser, for several important functions:
l Downloading the ProVision client for installation on client PCs
l Accessing saved Help Deskreports
l Accessing log records generated by the server, including real-time log views
The Web Server enables ProVision administration users to access these functions
from any PC on the same network as the ProVision Server. From the web browser, it
displays as a user-friendly interface.
For instructions, see:

l Accessing the ProVision Web Server on page 342
l Downloading ProVision Client from the Web Server on page 344
l Help Desk Reports from the Web Server on page 345
l Log Access from the Web Server on page 346
614-330053-001 4/04/2014 341

CHAPTER 14. PROVISION WEB SERVER
Accessing the ProVision Web Server

It is easy to access the ProVision Web Server.
You may need to add the URL of the server as a ' Trusted si te'
i n the i nternet setti ngs on your cl i ent PC.
Procedure
1. From a PC that is connected to your network, open a web browser.
2. Enter the URL for the ProVision server's IP address or server name, for
example: http://pvwenz04:8080/pvweb/
3. You are prompted to log in with a user name and password. Your
administrator will provide these. Enter these:
4. The ProVision Web Interface displays.
342 AVIAT NETWORKS

5. You can now use the Web Server functions, including:

l Downloading ProVision Client from the Web Server on page 344
l Server Reports from the Web Server on page 1
l Log Access from the Web Server on page 346
614-330053-001 APRIL 2014 343

Downloading ProVision Client from the

Web Server
Users can access the ProVision Web Server from any PC on the same network as the
ProVision Server. They can download the ProVision Client directly from the ProVi-
sion Web Server. This makes it quick and easy to install the ProVision Client on a
PC.
Procedure
1. Access the ProVision Web Server, as described in Accessing the ProVision
Web Server on page 342.
2. Go to the tab for Downloads.

3. In the Downloads tab, the available versions of the ProVision Client are
listed.
4. To download a version, click the Download button next to the file.
5. The ProVision Client installer is downloaded directly onto the PC.
F or ProVi si on Cl i ent i nstal l ati on detai l s, see Inst alling t he
ProVision C lient on p age 52.
344 AVIAT NETWORKS

Help Desk Reports from the Web Server

For fast viewing of ProVision Help Desk reports, access them from the ProVision Web
Server. This provides a complete list of all generated Help Deskreports. Note that you
cannot generate a report from the Web Server: this must be done from a ProVision
Client.
Procedure
2. Go to the Help Desk Reports tab.
4. Reports of that type that have been generated display. To view the report
details, click the report: the details display in the right tab.
5. To download a help desk report, click on the Download button beside it. A
.cvs version of the server report is downloaded onto your computer.
614-330053-001 APRIL 2014 345

Log Access from the Web Server

For fast viewing of ProVision server logs, access them from the ProVision Web Server.
This provides a complete list of all available logs.
Procedure
2. Go to the tab for Server Logs.
3. This tab displays a list of available log files.

4. To view a log file, click on the log name directly. The panel on the right
displays the log file content.
346 AVIAT NETWORKS

5. To download a log file, click on the Download button beside it. A .txt or .log
version of the log file is downloaded onto your computer.
6. To filter the content in a log file that you are viewing, use the Filter item.
Enter the text you want to filter for in the Filter Results field and click
Filter. The displayed content, or the entire file, is filtered for your desired
value.
614-330053-001 APRIL 2014 347

Appendix A. MTOSI NBI and

ProVision
This Appendix provides a basic overview of how to use ProVision with the Multi-
Technology Operations System Interface (MTOSI) NBI.
CAUTION:This Appendix is an overview/introduction only. For a com-
plete and detailed set of ProVision MTOSI NBI documentation, includ-
ing extensive links to related SOAP, tomcat, and MTOSI
documentation, see the separate ProVision MTOSI NBI API doc-
umentation.
MTOSI NBI Overview

What is MTOSI? MTOSI standard is a unified open interface that can be used among
multiple types of management systems to provide network and service management.
The MTOSI standard covers all communication technologies (from layer 1, e.g.,
SONET/SDH, through higher layer technologies such as VoIP). Based on XML,
MTOSI provides a standard interface between different systems for fulfillment and
assurance functionality.
From Version 6.5.3, ProVision can also be used with the MTOSI NBI.
The ProVision MTOSI NBI API enables developers to update ProVision's topology
and radios/plugins via the MTOSI NBI topology. This document assumes that
ProVision MTOSI NBI users are administration-level users with advanced pro-
gramming skills, already familiar with:
l MTOSI and MTMN standards.
l The functionality available in ProVision. (The ProVision MTOSI API provides a
subset of that functionality.)
l Web Services in general, and XML programming in particular.
To access ProVision's MTOSI NBI API programmatically, you build web service cli-
ents that connect to ProVision's MTOSI NBI API web services. Typically, your web
service client application would use a toolkit that knows how to connect to and inter-
act with web services.Licensing ProVision on page 99
The services are listed below.
The MTOSI NBI runs under axis2 on Tomcat.
The core messaging technology for ProVision's MTOSI NBI API is Simple Object
Access Protocol (SOAP), which is an XML- and HTTP-based protocol with wide sup-
port in the industry. The ProVision's MTOSI NBI API uses document/literal style
SOAP 1.1.
614-330053-001 APRIL 2014 349

APPENDIX A. MTOSI NBI AND PROVISION
The TM Forum’s Multi-Technology Operations System Interface (MTOSI) effort has

the goal of defining a unified open interface to be used between Operations Systems
(OSs), where an OS is any management system that exhibits Element Management
Layer (EML), Network Management (NML) and/or Service Management Layer (SML)
functionality as defined in the ITU-T TMN model.
This interface is based on the released MTOSI v2.0. Documents pertaining to these
standards may be downloaded from the TeleManagement Forum MTOSI home page.
To access ProVision's MTOSI NBI programmatically , you build web service clients
that use the ProVision's MTOSI NBI API. Typically, your web service client applic-
ation would use a toolkit that knows how to connect to and interact with web ser-
vices. (See the SOAP Wiki for more information about SOAP.)
MTOSI NBI Use Requirements and Installation

For use with ProVision, MTOSI NBI has to be installed on a ProVision server PC. It
is available for installation on the ProVision installation DVD.
Before using the MTOSI NBI, you need a feature license to enable this. See Licensing
ProVision on page 99
Administrators who are using MTOSI NBI need to be familiar with web service imple-
mentation and management.
First Time Installation

The ProVision-MTOSI-Setup-v<ProVision Version>-<BUILD>.jar file is
on the ProVision Installation DVD, in the folder MTOSI_NBI. This file requires that
a Java Runtime Environment (JRE) is present on the system. A JRE is included in
the ProVision installation DVD. To verify that the JRE is correctly installed please
execute 'java -version' in a command prompt.
To install the MTOSI NBI for ProVision:
1. Stop the ProVision Server.
2. RunProVision-MTOSI-Setup-v<ProVision Version>-<BUILD>.jar
either by double clicking on the file or by executing
'java -jar FOO.jar'
3. When asked to chose the installation directory, select the existing ProVision
server installation directory. You will be prompted for confirmation, select
YES.
Note that MTOSI uses Tomcat versi on 7.0.42.Al so note that
for Wi ndows 7, Wi ndows 8 and Wi ndows 2008 R2, you cannot
i nstal l MTOSI i n <Drive Letter>:\Program Files.
Re-Installation with ProVision Upgrade
If you have applied a custom configuration to the MTOSI NBI service (e.g. custom
port usage, custom HTTPS certificates), and you are upgrading your ProVision
350 AVIAT NETWORKS

installation, you must backup and restore the custom MTOSI NBI configuration
when upgrading ProVision. To do this:
1. Before beginning any steps of the upgrade, backup the custom configuration
files. To do this, copy all the files in the server tomcat/conf directory
(including the .keystore file and server.xml) to a secure external drive.
2. Upgrade the ProVision server. See Upgrading ProVision on page 67.
3. Install ProVision MTOSI NBI as documented above for the First Time
Installation.
4. Replace the custom configuration files copied in step 1.
Verify MTOSI Web Service Installation

After installing or upgrading the MTOSI service, go through the following steps to
verify that it is working correctly.
1. Open a web browser and navigate to the address
http://localhost:8080/axis2
2. The ProVision MTOSI help displays.
3. Go to the address 'http://localhost:8080/mtosi/' (or replace 'localhost' with
the address of the server if accessing from another computer).
4. If MTOSI is installed correctly then you will get an XML response specifying
"(302) Missing element - envelope, header, header" ... (This exception is
expected and due to the MTOSI request in the previous step not supplying a
valid SOAP message). The same message will be logged to the
'ProVisionServer\tomcat\logs\axis2.log' log file.
5. If you have configured MTOSI to work over a secure SSL connection, retry
steps 4 and 5 above on the secure port using HTTPS protocol,
'https://localhost:8443/mtosi/' Note: Use HTTPS in the URL, this is
required, using only HTTP will fail.
I f you have changed the port confi gurati on from the defaul ts,
8080 for HTTP unsecure / 8443 for HTTPS secure, then you
wi l l need to use the al tered ports i n the procedure above.
Available MTOSI NBI Services

MTOSI R2.0 ManageResourceInventory
• EquipmentInventoryRetrievalHttp
o getAllEquipment to retrieve all slot or plug-in information.
o getEquipment to retrieve slot or plug-in information.
• ManagedElementRetrievalHttp
o getAllManagedElements to retrieve all ME information.
o getManagedElement to retrieve ME information.
614-330053-001 APRIL 2014 351

• ResourceInventoryRetrievalHttp
o getInventory to retrieve a specified portion of all inventory data.
• TerminationPointRetrievalHttp
o getAllPhysicalTerminationPoints to retrieve all physical port information.
o getTerminationPoint to retrieve port information.
MTOSI R2.0 ResourceProvisioning

• CommonResourceProvisioningHttp
o setCommonAttributes to configure plugin wide settings such as Ethernet DAC link
status propagation.
• ConnectionControlHttp
o createAndActivateSubnetworkConnection to create end to end PDH/SDH circuits.
o deactivateAndDeleteSubnetworkConnection to delete end to end PDH/SDH cir-
cuits.
• EquipmentProvisioningHttp
o provisionEquipment to provision plugins in an chassis.
o unprovisionEquipment to unprovision plugins in a chassis.
• FlowDomainControlHttp
o createAndActivateFlowDomainFragment to create VLANs on Ethernet DACs.
o deactivateAndDeleteFlowDomainFragment to delete VLANs on Ethernet DACs.
• TerminationPointControlHttp
o createFloatingTerminationPoint to create layer 1 link aggregation.
o deleteFloatingTerminationPoint to delete layer 1 link aggregation.
o setTerminationPointData to configure various ports settings on support equip-
ment.
MTOSI R2.0 ResourceTroubleManagement

• MaintenanceControlHttp
o getActiveMaintenanceOperations to list active operations.
o performMaintenanceOperation to perform maintenance operations such as loop-
backs or protection locks.
MTOSI R2.0 ResourcePerformanceManagement

• PerformanceManagementRetrievalHttp
o getAllCurrentPerformanceMonitoringData to retrieve performance data.
o getAllPerformanceMonitoringPoints to list available performance data points.
352 AVIAT NETWORKS

Aviat Networks ResourceProvisioning

• PROP-AVIAT-ManagedElementProvisioningHttp
o createManagedElement to create (deploy) a device in the EMS.
o deleteManagedElement to delete a device in the EMS.
Supported Devices
MTOSI currently supports:
l Eclipse INU (5 slots) for version 7.2
l Eclipse INUe (12 slots) for version 7.2
Supported Eclipse Plugins and Software Versions

l Eclipse DAC GE 3 Plug-in all
l Eclipse DAC GE Plug-in all
l Eclipse DAC Plug-in all
l Eclipse RAC Plug-in all
l Eclipse FAN Plug-in all
l Eclipse 2U FAN Plug-in all
l Eclipse NPC Plug-in all
l Eclipse NCC all
Onl y network el ements of the supported types wi l l be con-
si dered for i ncl usi on i n MTOSI resul ts.
Uninstalling the MTOSI NBI

The MTOSI NBI can be safely removed from a ProVision server installation. To do
this:
1. Before beginning any steps of the uninstallation, backup the custom configuration
files. To do this, copy all the files in the server tomcat/conf directory (including
the .keystore file and server.xml) to a secure external drive.
2. Stop the ProVision server.
3. Run <ProVisionServer Install Dir-
ectory>\Uninstaller\uninstaller.jar
WARNING: DO NOT sel ect "F or the del eti on of c:\Pr o-
gr am F i l es\Pr oVi si onSer v er ", as thi s wi l l r emov e the
enti r e Pr oVi si on ser v er !
614-330053-001 APRIL 2014 353

5. Start the ProVision server.
6. ProVision now operates with the MTOSI NBI uninstalled.
Further Documentation
The ProVision MTOSI NBI API documentation is a set of HTML help. It is installed
with the ProVision MTOSI NBI. It includes:
l MTOSI Data Dictionary
l List of Status Codes
l MTOSI Header Values
l Extensive definitions for supported MTOSI operations, supported parameters,
and example request / response / exception SOAP XML documents.
l Proprietary Aviat Networks Services (descriptions and code instructions)
l Common Service Provisioning Behavior
l Common MTOSI Protocol Features
To access it, open the ProVision Web Interface administration page, and click on the
MTOSI API link, highlighted in red below. See ProVision Web Server on page 341 to
access the ProVision Web Interface.
354 AVIAT NETWORKS

preferences 185
scheduled backup procedure 186
scheduling 181
Index set location
using data topology
185
195
C
1 Changing
database purging criteria 190
15-minute performance data 190
Checking 189
purging 190
device incompatibility 93
A invalid deployed devices 95
Class Checking
Access Control 120 Upgrading 95
overview 120 Cleared events 190
prerequisites 128 Client 9, 52
uses of 120 CD software installation 53, 76
Adding software uninstall 57
network containers 109 Clock Synchronization Driven Discovery
Administrator 1 enable or disable 117
definition 120 Commands 44
functions active for 124 cmd 103
user name and password 40 ipconfig 103
ADR Compatibility 167
device support 16 Computer Equipment 42
Agent System 23 administration rights before installing 42
Altium disabling power saver 43
device support 16 Configuration
ensuring radio types correct in Topo- event NBI report 294
logy export file 169 NBI topics 316
Architecture 8 Configuration NBI
overview 8 deleting 321
deploying 317
B disabling 319
Background Maps editing 318
importing 109 enabling 319
Backups 180 renaming 321
Eclipse backup and restore, admin resynchronizing 320
level 191 settings for 319
frequency 181 system integration output file 322
frequently asked questions and CraftTools
enabling for generic devices 276
answers 180
Creating
manual backup procedure 185
user accounts 128
naming standards 180
CTR 8540
overview 180
backup 191
355 AVIAT NETWORKS

Security Account values 148 Editing

configuration NBI 318
D event NBI configuration 295
Daily 190 performance data NBI 308
Database 179 topology NBI settings 328
integrity checking 189 Enabling
management 203 configuration NBI 319
management parameters 196 event NBI 296
migration tool 81 NBI topology 329
practical applications 180 performance data NBI 310
purging criteria 190 ERPs
resetting 200 enabling and disabling 116
restoring 187 Ethernet OAM
support of MySQL database 40 enabling and disabling 116
Database Commands 44 Evaluation License 39
DCN extending 102
for Redundancy Controller 220 Event Browser
DCN Bandwidth 207 events generated by SNMP traps 27
Deleting Event Management 283
configuration NBI 321 NBI overview 283
event NBI 298 Event MIB 300
NBI topology 329 event details 302
performance data NBI 311 location on server 300
Deploying trap details 301
configuration NBI 317 trap types 300
event NBI 286 Event NBI 285
event NBI event management 286 configuration report 294
options for 9 definition 283
performance data NBI 307 deleting 298
topology NBI 327 deploying 286
Device Support 16 disabling 296
Disabling editing configuration 295
configuration NBI 319 enabling 296
event NBI 296 filter settings 291
NBI topology 329 limiting filter settings for 292
performance data NBI 310 printing report 294
DXR SMA renaming 299
device support 16 resynchronizing 297
saving report 294
E setting up, prerequisites 285
testing configuration 291
Eclipse 39 types of events 284
backup and restore configuration, Event Polling 16
admin level 191 Event Table 27
Eclipse Software Expiration Date 39
installation CD 39 Export 164
356 AVIAT NETWORKS

F procedures 46
process overview 29
FTP Access 337 standby server 58
for NBI configuration files 317 Installing 52
for NBI performance data 314 as a system service 202
NBI topology files 331 client from web server 344
client software
G
from Server 54-55
Generic Devices prerequisites 53
configure resynch alarms 268 client software via CD 53, 76
definition 240 Portal software installation CD 39
enabling craft tools for 276 Redundancy Controller 60
limitations 241 server 46
reassigning package 244 server software 47
trap mapping setup 250 Instance IDs 25
Invalid Deployment 95
H checking for invalid devices 95
definition 95
Hardware 31
reviewing topology import for 164
Help Desk Reports 335
IP Address 40
about 336
identifying for server 103
commands 337
static for server 40
running 336
ITU-T 281
saving or deleting 338
Hot Standby Server Redundancy L
overview 217
HPOpenView 280 LAN client 10
Latency
I for Redundancy Controller 220
License
Icons
evaluation 39
caution 5
expiration date 39
note 5
feature licenses for specific function
warning 5
modules 100
Import 163
permanent 39
background maps 109
procedures 103
trap mapping from MIB for generic
Licensing 99
devices 259-260
activating permanent license 104
Installation
by solution packs 99
administration rights required for admin 42
identifying IP address 103
CD set 38
identifying server IP address 103
disabling SNMP trap services 42
permanent license overview 102
Eclipse CD 39
procedures 103
introduction 29
requesting permanent license 104
modify rights required for user 42
LLA 280
platform requirements 31
TMN LLA model 280
prerequisites 31
357 AVIAT NETWORKS

Logging In configuration managment 316

Redundancy Controller 224 definitions 317
Logs event management overview 283
accessing system logs from web performance data collection 305
server 346 performance data management 304
performance data management, over-
M view 304
Manager-agent Model 23 Performance NBI Activation overview 304
Manager icon 101 procedures 303
Managing role 280
database 179, 203 topology details 326
Manual Backup 185 topology management 326
Maps 108 NBI configuration 316
importing 109 associated events 316
MIB 22 Network 22
Enterprise specific 25 device communication 16
event details 302 intelligence 16
importing for generic devices 259-260 management concepts 22
information exchange and SNMP 24 SNMP 22
installation 300 topology 166
instance IDs 25 Network Containers 109
Internet specific 25 Nodes 40
location 300 Northbound Interface 280
naming conventions 24-25 prerequisites 108
object attributes 25
O
object identifier 25
object instance 24 Object attributes 25
organization of 24 Object Identifier 25
trap details 303 Operating system 31
trap types 300 Overwrite 187
pvAcknowledgedTrap 300
pvClearTrap 300 P
pvRaiseTrap 300 Packages 240
MTOSI NBI 349 assigning to device 244
further documentation 354 configuration recommendations 241
overview 349 custom events for 270
requirements 350 description entry 249
MySQL 189 editing configuration 245
matching rules 263
N
renaming 248
Naming Standards trap mapping 250
backup 180 Parameters 196
MIB 25 Passwords 128
NBI 280 administrator default 40
configuration management overview 316 changing 132
358 AVIAT NETWORKS

Eclipse radio security account 143, 149 data saved in database 190
for XP4 radios, for setup 108 pv db 45
multiple radio security account pass- reset 45
words, setting 151 restore 45
XP4 and DART radio security account pv db check 45, 196
passwords, setting 148 pv help 45
PC power saver 43 pv service 44
Performance 190 install 44
Performance Data remove 44
managing for NBI 304 stop 44
Performance data management 304 pvAcknowledgedTrap 300
Performance data NBI 310 pvRaiseTrap 300
accessing files via FTP 314
collection 305
R
deleting 311 Radios
deploying 307 clearing security account settings 152
dsabling 310 Eclipse 39
editing 308 Eclipse security account settings 143, 149
file naming convention 312 IP addresses 108
output files location 312 multiple radio security account settings 151
output location 312 security access 108
parameters and definitions 314 security access accounts 141
renaming 311 XP4 and DART security account settings 148
Permanent license 39 RADIUS Server
Platform Requirements 31 defining authentication settings 158
Portal enabling 154
automatic login, enabled by security set configuration on single Eclipse 159
access 151 updating authentication settings 157
craft tool for Eclipse 39 Redundancy Controller
installation required 39 about and functions 218
Pre-installation Tasks 42 backup 91
Prerequisites Configuration Screen 229
disabling PC power saving setting 43 DCN requirements 220
Northbound Interface 108 functions 217
set up computer 42 installing 60
system setup requirements 108 Latency 220
Presence polling frequency 16 Login 224
Printing operation 222-223
event NBI configuration report 294 overview 203
event NBI report 294 restore 91
ProVision Security Screen 231
evaluation license 39 Status Screen 225
license for use 102 stop and start 91
Purging 181 troubleshooting 233
15-minute performance data 190 upgrading 85
cleared events 190
359 AVIAT NETWORKS

Redundant Servers Portal Engineer, definition 120

and VLAN, ERP,and EOLAM enabling 116 user 124
hot standby server redundancy 217 Security Log
warm standby server redundancy 205 definition 120
Removing overview 140
system service 201 viewing 140
Renaming Server 46
configuration NBI 321 IP Address 103
event NBI 299 server start command 48
NBI topology 330 software installation 47
performance data NBI 311 software uninstall 55
Reports starting 200
auto-FTP for help desk reports 337 starting manually 200
help desk report, saving 338 static IP address 40
help desk reports 336 stopping 199
Resetting 200 upgrade notes for 2.3/3.0 to 5.7 167
database 200 verify server operation 48
Restoring 187 Server IP address 40
database 187 Server Loading Value 36
Resynchronizing 320 calculating 36
configuration NBI 320 Server Reports
event NBI 297 access from Web Server 345
process overview for event NBI 297 Set up 107
remote enabling for event NBI 298 prerequisites 108
Roles 128 process 107
Rollback to previous version 97 user list requirement 108
Single server/client deployment 9
S Single Sign On
Saving credentials 122
event NBI SNMP 22
configuration report 294 agent system, definition 23
event NBI report 294 agents 27
Scheduled Backup 186 communication with 22
Searching Get Bulk request 24
for maps 108 Get Next request 24
Security 12 Get request 24
access control requirements 128 manager-agent model 23
no-access functions 124 MIB data access 24
radio security access, overview 141 request type list 24
read-only functions 124 Set request 24
standby server, installing 58 use 8
write-only functions 124 SNMP Services
Security Groups 120 installation requirements 42
changing for a user 132 Software
NOC engineer, definition 120 commands 44-45, 196
NOC operator, definition 120 pv db reset 45
360 AVIAT NETWORKS

pv db restore 45 standby server deployment 12

pv help 45 WAN client 11
pv service install 44 System Integration 331
pv service remove 44 configuration NBI output file 322
pv service start 44 events MIB 300
pv service stop 44
commands,database 196 T
database integrity 189 Testing 291
database restore 187 event NBI configuration 291
events MIB 300 TMN 280
installation prerequisites 31 definition 280
license expiration 39 TMN LLA model 280
NBI for data exchange 280 TNet
permanent license 39 devices 26
Solaris System 31 Topology 162
identifying IP address for server 104 deleting for NBI 329
uninstalling Server 56 deploying for NBI 327
Standby Servers 58 disabling for NBI 329
about 12 editing NBI settings 328
about and functions 205 editing the Topology file 168
activating 211 enabling for NBI 329
configuring 206 exporting 164
DCN Bandwidth requirements 207 for data backup 195
enabled and disabled functions 205 import troubleshooting 163
managing 203, 205 importing 108, 163
overview 203 migration parameters 162
redundancy options 12 migration prerequisites 162
separate hardware for server and client 14 migration tool for 2.3/3.0 166
sharing versus non-sharing 13 NBI management 326
Starting 200 NBI topology details 326
StarView 171 NBI XML file output 331
StarView Data Import 174 renaming for NBI 330
Static IP Address 40 viewing export log file 168
Stopping 199 Topology NBI
Strong Security system integration 331
SSO mechanism 122 trademarks i
Sun Server 167 Trap Mapping 250
Supported Nodes 40 identifying package events 250
Syslog Server Port 112 importing from CSV 262
System Architecture 8 importing from MIB 259-260
diagrams 8 mapping example 254
System Deployment 9 match rules example 265
LAN client 10 matching rules 263
server with remote clients option 11 setting up 250
server with standalone clients option 10 Traps 23
single server/client option 9 definition 23
361 AVIAT NETWORKS

frequency 17 W
initiated polling frequency 17
SNMP requests 24 WAN client 11
viewing traps created by SNMP 27 warranty i
Troubleshooting Web Server
import of topology 163 accessing 342
Redundancy Controller 233 downloading ProVision Client for install-
ation 344
U log access 346
overview 341
Uninstalling
server reports 345
client software 57
Windows 8
server software 55
navigating 65
Solaris server software 56
uninstalling 65
Upgrading 67
Windows Systems 31
from StarView using the StarView Migra-
platform requirements 31, 60
tion Tool 171
Windows 8 65
Redundancy Controller 85
rollback 97 X
User Accounts 128
editing 132 X.733 event model 284
exporting 132 XP4
User name 40 device support 16
administrator default 40 security access 108
Users 120
creating user accounts 128
list for system setup 108
passwords, creating for 128
radio security account users, for
Eclipse 143, 149
radio security account users, setting for
multiple radios 151
radio security account users, setting for
XP4 and DART 148
security groups 124
setting up access control 120
setting up access control, require-
ments 128
V
Velox
device support 16
VLAN
enabling and disabling 116
362 AVIAT NETWORKS

614-330053-001
WWW.AVIATNETWORKS.COM

Installation and 5ProVision Administration Manual 6.11.

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Installation and 5ProVision Administration Manual 6.11.

Hochgeladen von

Copyright:

Verfügbare Formate

PROVISION

INSTALLATION & ADMINISTRATION

614-330053-001 APRIL 2014 I

Service and Technical Support:

Corporate Headquarters International Headquarters

Sales and Sales Support:

See our web site at: http://www.aviatnetworks.com/services/customer-support/technical-assistance/

614-330053-001 APRIL 2014 III

ProVision Copyright and Terms of Use i

CHAPTER 1. ADMINISTRATOR INTRODUCTION 1

CHAPTER 2. SYSTEM DESCRIPTION 7

CHAPTER 3. INSTALLING PROVISION 29

614-330053-001 APRIL 2014 V

Virtual Machine Installation Requirements 35

CHAPTER 4. UPGRADING PROVISION 67

Before You Upgrade 85

CHAPTER 5. LICENSING PROVISION 99

CHAPTER 6. SETTING UP PROVISION 107

CHAPTER 7. ACCESS CONTROL 119

614-330053-001 APRIL 2014 VII

Update Passwords for Multiple Radio Accounts 146

CHAPTER 8. MIGRATING TOPOLOGY 161

CHAPTER 9. DATABASE AND SERVER MANAGEMENT 179

CHAPTER 10. REDUNDANT SERVER DEPLOYMENTS 203

VIII AVIAT NETWORKS

About Primary and Standby Servers 205

CHAPTER 11. GENERIC DEVICE MANAGEMENT 239

614-330053-001 APRIL 2014 IX

Launching Generic Device Windows Applications from ProVision 276

CHAPTER 12. NORTHBOUND INTERFACE 279

Renaming a Topology NBI 330

CHAPTER 13. HELP DESK REPORTS 335

CHAPTER 14. PROVISION WEB SERVER 341

APPENDIX A. MTOSI NBI AND PROVISION 349

614-330053-001 APRIL 2014 XI

Role Brief Description

614-330053-001 APRIL 2014 3

Conventions and Terminology

WARNING: A war ni ng i tem i denti f i es a ser i ous phy si cal

614-330053-001 APRIL 2014 5

ProVision Deployment Options

Single Server/Client Deployment

614-330053-001 APRIL 2014 9

LAN Client Deployment

WAN Client Deployment

614-330053-001 APRIL 2014 11

Standby Server Deployment

For information on installing and managing a standby server deployment, see

Standby Server Deployment: Sharing or Separate

614-330053-001 APRIL 2014 13

Standby Server with WAN and Separate Hardware

614-330053-001 APRIL 2014 15

Network Communication, Ports, and

Communication Frequencies with Network

Some devi ces have di fferent pol l i ng frequenci es for di fferent

Device Type Presence Event Traps Event Trap Initiated

614-330053-001 APRIL 2014 17

Device Type Presence Event Traps Event Trap Initiated

Network Communication Ports for Firewalls

FTP Transfer Firewall Configuration

Recommended Port Configuration

WARNING: Jav a Runti me f or Pr oVi si on chooses many of

Application Protocol Port From Comments

614-330053-001 APRIL 2014 19