SHB PRO E10 1 - Ebook PDF

CUSTOMER TRAINING
TECHNICAL TRAINING STUDENT HANDBOOK
ProVision ® 6.10.1
SHB-PRO-E10.1
SHB-PRO-E10.1
Revision History
Issue No. Issue Date ECO Description of Change / Revision
01 01/08/07 E01 First issue for software 6.0
02 01/02/08 E02 Update for software 6.1
09 04/15/12 E09 Update for software 6.8.5
10 02/20/13 E10 Update for software 6.10.1
11 03/25/13 E10.1 Revision of documentation to add WTM6000 RF Link Creation for
software 6.10.1
Part Number SHB-PRO-E10.1

Copyright 2013 Aviat Networks, Inc. All rights reserved
ProVision® 6.10.1 is registered mark of AVIAT
Data subject to change without prior notice
Aviat Networks, Inc. www.aviatnetworks.com

5200 Great America Pkwy TAC US/Canada 800-227-8332
Santa Clara, CA, 95054 EMEA UK +44(0)1698 717 230
United States France +33 (0) 1 77 31 00 33
Tel: 408-567-7000 Asia/Pacific +63 45 599 5192
SHB-PRO-E10.1
AVIAT NETWORKS | FEB. 2013 | Company Proprietary | Copyright © 2013 | ProVision 6.10.1 1
ProVision is the Aviat Networks Element Management System.
As a powerful, standards-based Element Management System (EMS) for access and
microwave transport networks, ProVision offers much more than a standard EMS or
generic SNMP manager.
ProVision provides superior network intelligence for mobile and private network
operators to dramatically improve management efficiencies and drive down operational
costs, in an easy to use and intuitive package that can be run on a desktop computer or
workstation in a network operations center (NOC).
Using Provision, fast network manager responses and simplified network overviews help
detect potential system problems before they result in down time or equipment failure.
With deployments worldwide, ProVision is field-proven, reliable and future-proof.
ProVision is ideal for growing networks, and can be deployed for networks for 60 to over
6,000 networking elements, without adding an additional server. ProVision’s
northbound interface (NBI) options also enable it to be integrated with any third party
Manager of Managers (MoM).
ProVision’s intuitive graphical user interface (GUI) and simplified circuit and network
views enable operators to quickly change network configurations, correct defects and
report on network asset health and performance.
Network operators can speed network rollout and simplify operational management
with ProVision’s user-friendly functions and intelligent network controls. All current and
legacy Aviat access, microwave and networking platforms are supported by ProVision,
including the Eclipse™ Packet Node platform, StarMAX™ base stations, CPEs and ASN
Gateway.
ProVision provides the following features and benefits:
Extensive fault management support including event scoreboards and fault event
notification
In depth performance data management using graphical visualization and reporting
User configurable thresholds and notification profiles (audio alerts, emails, paging, and
SMS)
Comprehensive security, diagnostics and configuration controls
Simple system administration including database and user admin
Single and redundant server options available for UNIX & Windows deployments
Advanced support for TDM and Ethernet circuit management, software downloads,
automated configuration backup, network health and inventory reports
Server processes that track the current state of the network model, manage user access to the
system, monitor network events, and more.
The MySQL database system used for storing and retrieving network element data.
A local client used for establishing a client-to-server session on the server. This deployment is
only recommended for small installations
The ProVision client installation installs client software on the local machine, eliminating 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 client 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.
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 ProVision 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.
Portal must also be installed on the Server. If the Portal software application is installed
only on the server, it can still be accessed from the client. However, the Portal help
application must be installed on all client computers in order to link Portal events with
Portal help.
Client inactivity auto-logout if inactive for a specified period of time
For further reading,
Application views in tabbed frames that can be resized, moved, maximized, and closed.
Saved layouts for each user restored on start-up; default layout can be restored.
New function icons in screens and menus.
New event severity icons match Portal event levels.
Keyboard shortcuts for frequently used functions
Physical Viewer
In the Physical View option, the entire radio network is represented as a tree of
containers and devices. Each container (for example, a region) is represented as a
parent, with all the devices positioned underneath, as its children
Logical Viewer
The Logical tree viewer displays the logical containers created in ProVision, and the
devices and circuits grouped under each logical container. This tree view supports
severity propagation, with the logical container taking on the highest severity of its
Devices. Network devices that share a common purpose can be grouped together to
form a Logical Container. This grouping allows these devices to be monitored, managed,
and viewed independent of the main network, and at the same time also continue to be
viewed as part of the wider network.
The following object types are supported in the Map Viewer;
Region
Site
Rack
Device objects
RF links
Service links.
Right-click an object in the Map Viewer to see the right-click menu, which lists the
options available for that object.
To add a map background, right click on the Map Viewer and scroll to Map Properties
NOTE: A high level container can have additional containers and devices. For example, a
region may consist of several sites and devices.
When deploying the Network you can:
Add/Rename/Delete a Container
Deploy/Rename/Delete a device
Manage and Unmanage a device
Re-parent
Create/Verify/Delete a RF link
Eclipse RF link discovery
Reposition map viewer objects
Define map background
To deploy and manage devices, you must have all of the following information:
A comprehensive network element inventory
List of all the sites, each radio name and its type
Know any radio specific details
Determine IP address assignments
Determine device specific configuration requirements
When a device is installed, successfully commissioned, Deployed and Managed,
ProVision polls the device and receives events, collects data from devices. When a
device is not deployed or managed, ProVision does not recognize nor receives traps
User can define container icons.
Input the various IP address ranges and click on Add,
The IP addresses would be in the Discovery Ranges,
Check the radio button ‘Manage on Deployment’
Click on Start Task
Device data can be edited
Can be deployed to specified Container.
If a Container specified for auto-discovery does not exist, ProVision will create it.
Auto-deployment results: notes and errors
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.
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.
Maximum Sessions - The maximum number of ProVision Client sessions this user can
have open at one time.
Suppress Email Notifications - Check this box if this user should never receive email
notifications about events
In the Tree Viewer or Map Viewer, right click on the root icon or an existing container,
for example the network or region icon and select Deploy Object. Click on Generic after
which you are presented with different categories of devices that can be deployed in
ProVision including Timing Systems
If the system is licensed for Package level management, options will be given to use
custom icons, assign a support package name, and set SNMP options (version,
community strings, etc.)
To deploy a generic device Symbol, the user simply selects the “Symbol” object from the
Generic Family of objects, defines a name for the symbol and selects a custom icon and
subtype for the symbol.
Previously used icons and subtypes can also be used; if no custom icon is selected then
the default icon is used for the object.
Note that the custom icon and type can be modified for an object at any time after
deployment.
This design makes PV able to raise events on a specific NE based on traps received from
the proxy device. It could also support some of the following if supported by the EMS:
Alarm resynchronization
State changes of proxied devices
Automatic deployment of proxied devices (future requirement)
PV server interacts only with the Proxy or EMS via IP or SNMP. Hence the protocol that
proxy uses for contacting NE is completely transparent for PV. As ProVision does not
contact proxied NE directly, the NE state is inherited and managed by proxy.
Reparented or auto-discovered objects will not be positioned correctly in the map view
and thus you can move objects within the current Map. Unlock the Map Viewer for
editing, Drag and drop the object and finally lock the Map Viewer after editing
NOTE: Deleting a device in ProVision has no effect on the traffic carrying capability of
the device, but event generation is disabled in the device.
Links between devices is typically performed after management. It can be perform
before management (Pre-deployment) except DXR 700 and Eclipse Node radios.
If ProVision is not receiving events:
Make sure the IP address is correct
Place the cursor over an object, an information pop-up text box displays
NOTE: RF links are automatically discovered for Eclipse radios
From the Tree Viewer, you can select and link two non-Eclipse or non-TRuepoint radios
Click on the first device, holding Ctrl down, click on the second device, then use
Create Link from the right-click menu to create an RF Link or a Logical Link
From the Tree Viewer, you can select and link two non-Eclipse or non-TRuepoint radios
Click on the first device, holding Ctrl down, click on the second device, then use
Create Link from the right-click menu to create an RF Link or a Logical Link
Network devices that share a common purpose can be grouped together to form a
Logical Container. This grouping allows these devices to be monitored, managed, and
viewed independent of the main network, and at the same time also continue to be
viewed as part of the wider network.
To add a device to a logical container:
1. Right-click the required device icon.
2. From the menu displayed select Configuration, then select Configure Logical
Containers. The Configure Logical Containers window displays.
3.To select a logical container for this device, highlight the service in the All Logical
Containers list and select the > button. The device is now part of the selected logical
container
NOTE: You can select multiple radios/devices and right-click, and you will view a generic
right-click menu. This menu includes only the functions that are shared amongst all the
devices.
Configuration data is entered via a craft tool and stored in the radio.
Use the Configuration Viewer to review the configuration for a device:
ProVision retrieves and displays the device values from the craft tool.
You can also save the configuration data for a device as a text.CSV file.
For Eclipse radios, the Configuration Viewer window has separate tabs that list the radio
frequency configuration for each link. It also includes a tab with Inventory details for the
radio.
The drawing above shows the Configuration Viewer window for an Eclipse Node with
one link in slot 1 (LINK1).
The Configuration Viewer varies depending on the radio.
The Configuration Profiles function enables you to apply configuration settings to
multiple radios.
Users must have administration or NOC Engineer.
Bulk configurations include:
Several common configurations of the Eclipse radios
Trap destinations for most other Aviat radios.
Right-click on a container and then select Configuration  Profiles
The network configuration gives you a list of the device IP addresses entered via
ProVision.
From here you can view and change the ProVision device IP addresses.
This function enables you to view/edit a list of the network devices’ IP.
Radio Types that display equipment views:
ADR 155c
ADR 2500
Constellation
Eclipse
MegaStar M:N and 1+1
TRuepoint 4040 and 5000
TRuepoint 6400
TRuepoint 6500
StarMAX 6100 and 6400
WiMax ASN-GW Home Agent
WTM6000
Interface views are available for the following radio types:

LE3000/3200
WL1000/RW2000
Generic Devices
StarMAX 6100 and 64000
StarMAX Subscriber Stations
WiMAX ASN-GW/Home Agent
Unacknowledged active events are:
Listed in chronological order
the most recent events displayed at the
A maximum of 1000 events can be displayed in the main Event Browser.
Object Event Browser in an independent window
Open an Event Browser by right-clicking an Object and selecting Event Browser
Will display only events pertaining to the object you selected
Customizing Event Browser
You can customize both the main Event Browser and the Event Browser independent
windows.
Dragging the column heading left or right will change the order in which they appear.
You can also create and apply filters to Event Browsers.
Scoreboards are graphic diagrams of events
This topic will be covered in detail in the Events Management lesson.
NOTE:
While ProVision can run multiple tasks simultaneously, it will not run multiple versions
of the same task. For example, only one Inventory Report can be generated at a time.
ProVision’s main search function enables you to find specific data in the ProVision
system. The Search function searches all ProVision data to locate the data you specify,
from an IP address for a specific radio to all radios in a particular state.
Represents additional ProVision
One radio or a set of radios
pre-filtering events
Collecting data
Collecting Performance data
Only active for a radio that is Managed
Comprehensive database management – commands, database backup, PV migration
import after upgrade, Help Desk reports
Full details in PV Installation and Administration Manual, Chapter 9, Database/Server
management
If you are using a Windows 2008 or Windows 7 server, after you select Start >Programs
> Server >C:\ command window select the Run as Administrator option. This opens the
command window at your user level. Change the directory to find the server, then
continue.
Can do the following:
Manual or Scheduled database backups
Database Restore
Database Purge
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 setup for sites, regions, radios, and other important network data. It does not
include Map graphics.
Simple to import and export using functions from File menus
Import/export may take some minutes to process
ProVision is the Aviat Networks Element Management System. ProVision empowers
users to trace, view, group, and manage the circuits for Eclipse networks.
A circuit is a single end-to-end tributary path that traverses the radio network. A circuit
bundle is a collection of circuits that together deliver an end-to-end transport service.
In an Eclipse Super-PDH network, a circuit is an E1 (or DS1), a circuit bundle is a
collection of E1s (or DS1s).
Circuit bundles are identified by ProVision, based on their common network paths.
Users can manually override ProVision’s circuit bundle definitions.
ProVision supports up to 50,000 Eclipse circuits with:

Viewing and Modeling
Auto Discovery
Capacity Management
Diagnostics
Circuit Provisioning
Logical Containers provide a highly flexible means of modeling the radio network. They support
groupings of managed entities (devices, sites, circuits, circuit bundles, etc), so that the user is
able to create multiple models. With logical containers, users group entities by physical, logical,
service, workflow, or other meaningful models. Circuit bundles can also be grouped into
transport service-oriented containers. The adjacent graphic shows Logical Containers with circuit
bundles and radios grouped by main network and by client.
In the Circuits Tab, you can view, sort, analyze, and filter the available circuits. The Circuits Tab
displays immediately behind the main Map Tab in the ProVision user interface. To view details
for a circuit, mouse over it in the map view to see a detailed pop-up. If a circuit's connection
information is out of date, a warning message appears.
Double-click the circuit to expand and view all the aspects of the circuit. Traced end-to-end
circuits can be viewed by selection from the tree viewer. Users can highlight specific circuit
paths to view the links and status for that pathway. Users can also apply the Filter and Search
functions to locate specific circuits. The sample below displays a ring circuit.
The Circuit Trace function maps all circuits and circuit bundles, through the network, and
displays them in the Circuit Tree view. The ProVision user can do this at the network container
or the circuit level, using the Global Trace function.
Circuit tracing benefits an Eclipse network by:
Providing user-friendly visibility of circuits, with their status and configurations.
Supporting circuit provisioning during network rollout. For example, users can make a required
circuit capacity change, then verify the changes using Circuit Trace.
Supporting the functionality of self-healing Super-PDH rings by enabling users to view and
retrace circuits, so that, if a path failure occurs, users can identify alternative circuit routes.
The Circuit Provisioning function enables users to rapidly create or modify end-to-end transport
circuit bundles in a single write operation. This includes the ability to configure the path
(network route), capacity (N x E1 or N x DS1) and circuit naming. The circuit bundle tributary
ports can also be commissioned / decommissioned in a single write operation. Circuit
Provisioning provides the following benefits:
Speed: Users can create or modify end-to-end circuits in minutes, increasing efficiency and
reducing OPEX, whereas node-by-node based configuration often takes hours and is error
prone.
Ensures correctness and consistency: The Circuit Provisioning function verifies correct
configuration and applies consistent naming to all nodes on the circuit path. Incomplete paths
are identified in error reports.
The following steps are involved in creating end-to-end transport circuit bundles:
(1) Object Selection – Select the two radios that will terminate the end-to-end circuit bundle.
(2) Path Selection – ProVision presents the possible network paths, based on the automatically
identified Eclipse network topology. Users then select the network path that best meets their
requirements. If there is an existing circuit bundle for the selected path, the user has the option
to either change the existing bundle, or create a new bundle on the same path.
(3) Capacity Selection – ProVision presents a graphical image of the end-to-end path. Users can
define the circuit capacity, circuit naming, and terminating DAC card ports for both ends of the
path.
(4) Write and Verify – ProVision makes the configuration changes to all the Eclipse nodes on the
path in a single write operation, and then retraces the circuit bundle to verify the changes.
Progress can be traced through the Task Manager function.
Note that circuit provisioning is a licensed feature.
ProVision displays identified problems with Eclipse circuits in several ways: in a circuit
tree viewer, in event browsers and submaps, and in the circuit map. For users, these
problems are displayed via icon indicators, color-coding, and events with detailed
information. These diagnostics enable users to identify and fix problems fast, reducing
OPEX by achieving higher network ability.
End-to-end TDM circuit performance diagnostics are also provided through PRBS testing
with G.821 results generation. Users can perform PRBS tests for specific circuits or
circuit segments. Via the Circuit Diagnostics test screen, users set up generators,
detectors, and loopbacks. ProVision then monitors the circuit and presents the results in
real time.
Running a Circuit Trace
Two methods to trace circuits:
Global Circuit Trace
Individual/Container Circuit Trace
Global Circuit Trace
Scheduled
On-demand
Individual/Container Circuit Trace
Right-click Menu on an Eclipse or container object select Circuit  Initiate Trace
Circuit Table Description
Severity
The severity of any event regarding this link
Status
The status of this link. Status is indicated by color:
Green = OK.
Red = Data incomplete, cannot completely trace this circuit.
Blue = Data inconsistent.
Yellow = Circuit route changed.
Orange = Circuit route removed, circuit has been deleted and recreated.
Glowing Orange = Incorrect Ring configuration.
Circuits are displayed in the Circuits Tab
The following features make monitoring the network easy and efficient:
Circuits Tab
Filter and Select Circuits
View a Single Circuit
View Intersecting Circuits
View Ring Circuits
Find and Resolve Conflicting Circuits
Validate a Circuit
Circuit Diagnostics
Circuits are displayed in the Circuits Tab
The following features make monitoring the network easy and efficient:
Circuits Tab
Filter and Select Circuits
View a Single Circuit
View Intersecting Circuits
View Ring Circuits
Find and Resolve Conflicting Circuits
Validate a Circuit
Circuit Diagnostics
Selected Object
Name of the selected object; its circuits are detailed in this tab.
Note: To view all circuits for the entire network, click the X beside this field.
Include Intersecting Circuits
Check this box to view circuits that pass through the device for this object, in addition to
circuits that start and end at this object.
Groups
Check this box to view these circuits collected into Groups based on termination points.
The Groups are connected by shading.
Filter
Use the Filter function to filter and view specific circuits.
Map Tab
Select a circuit in the table, and a graphic representation displays in the Map Tab.
Conflicts Tab
Shows information for the links of the selected device.
If the Map and Conflicts subtabs are not displaying
Select the circuit and click the Show Details
This opens the Map/Conflicts
To close these subtabs
Click Hide Details.
The Map details include the port numbers for the devices.
Additional information about the circuit
place the cursor over the circuit device
A pop-up displays with capacity and link information.
Menu Item and Function
Show Conflicts
Opens the Conflict subtab and displays any circuit conflicts.
Clear Conflicts
Resolves any identified circuit conflicts.
Validate
Runs an automatic validation of the circuit.
Diagnostics
Opens the Circuit Diagnostics screen.
Event Browser
Opens the circuit-specific Event Browser.
Network Health
Opens a Network Health Report for this specific device.
Connectable (if present)
Right-click on the Connectable table cell to view the Connectable menu. This shows
functions for the object represented in this cell.
Circuits that do not start or terminate at a device, but instead pass through
To include intersecting, check the Include Intersecting Circuits checkbox
A circuit conflict occurs when a circuit pathway needs to be updated.
Circuit conflicts do not occur when a circuit is first traced.
They may be identified in subsequent traces
ProVision includes a Conflicts subtab, which enables you to view and resolve conflicting
circuits.
For Eclipse radios, ProVision offers the optimal solution for managing circuits. It
provides:
Rapid circuit updates to align with network expansions.
Network-wide confirmation of circuit assignments.
Network-wide circuit provisioning and configuration.
Circuit supervision and troubleshooting.
Aviat Eclipse radio technology managed with ProVision provides a unified solution with
optimum flexibility and reduced OPEX costs both today and in the future. Eclipse and
ProVision will continue to be highly compatible.
For future versions of Eclipse, ProVision will provide further advanced circuit support,
including circuit prioritization for Adaptive Modulation and management of Ethernet
Virtual Circuits (EVCs) in next generation Aviat radio products.
ProVision is the Aviat Networks Element Management System. ProVision strengthens
network managers’ ability to quickly manage changes, correct defects, and report on
network health and performance.
One of the most important features of ProVision is Event Management. ProVision
provides superior network event management.
Network event supervision and management is key to containing crises and monitoring
network health
ProVision provides multiple Event Management options, so that users can:
Choose what events are important
View individual details, including recommended fixes
See event impact on overall network health
The Event Browser lists all events that occur in a network. The events displayed in the
Event Browser view are continually refreshed as events are received from the devices on
the network.
The main Event Browser is the bottom panel of the ProVision user interface and, by
default, displays all unacknowledged, active events on the entire network. A separate
event browser can also be opened, to show events for a specific region, container, or
device.
Users can view an event’s properties to gain information about a specific event. Event
properties allow users to answer the following questions about an event:
Is the event equipment related, or due to weather or site conditions?
Can the user determine if the event is cleared by the device?
Should the user escalate the event to an engineer?
At the radio level, if there is a problem, for example, faulty equipment or an antenna out
of alignment resulting in events being generated and you know a field technician is
going out to the radio to fix the problem, then you can pre-filter for these events for this
radio. However, you must remove the pre-filter once the problem has been fixed.
The Scoreboard is the most convenient way to monitor a group of radios or the entire network. Scoreboard groups provide a
summary of the status of a network in a graphical format. Typically, every radio in the network is displayed on a Scoreboard.
How users set Scoreboard groups up is flexible and is to be based on your business requirements.
The Scoreboard group is a container for individual Scoreboards and allows users to add and remove Scoreboards from the group
Name and save the Scoreboard group
Once a Scoreboard group is set up it is saved and available to all ProVision users.
The following examples are business-driven scenarios for using Scoreboard groups.
Golden Cells:
A network includes sites where it is imperative that communications traffic continues at peak performance. Examples of golden
cells are:
A mobile backhaul network, located close to international sporting events. Sites where communications down can mean loss of
revenue, for example, share markets. Sites where there is a contractual obligation that includes performance metrics.
Scoreboard groups are a way to monitor these specific sites.
Backbone Sites:
These are sites that carry a high proportion of communications traffic and feed off to less important “leaf sites”. Problems with
these backbone sites impacts entire sections of the network. It is crucial that these sites are kept problem free.
Monitoring Event Categories:
Users want to monitor the entire network for certain categories of events, such as communications, and equipment failure.
Monitoring a Specific Site:
Users have a site experiencing problems. Creating a Scoreboard group dedicated to this site enables the users to monitor events
from the radios at that site.
At the root level (network wide) you can filter out events on a per device basis. This
stops non-essential events entering the system. For example, on Altium radios if ATPC is
enabled an event is generated each time the radio switches between ATPC on and off.
These events do not relate to the performance of the radio nor the communications
traffic. They are not necessary: they are events that can be pre-filtered.
At the radio level, if there is a problem, for example, faulty equipment or an antenna out
of alignment resulting in events being generated and you know a field technician is
going out to the radio to fix the problem, then you can pre-filter for these events for this
radio. However, you must remove the pre-filter once the problem has been fixed.
How Does Event Pre-filtering Work?

A pre-filter applied at a parent level in the hierarchy is automatically applied to child
objects that are included in the criteria. This figure shows an example of how a pre-filter
set at the root level (Southern North Island), for XP4 radios is applied to all XP4 radios,
and shown in this example, the Waikanae XP4 radio. The blank Self tab displayed for the
Waikanae XP4 radio indicates there are no pre-filters applied directly to the selected
object. The Parents tab has the active filters displayed.
NBI event management enables integration of event management with Network
Management Layer systems.
The main purpose of NBI event management is to convert ProVision events, as displayed
in the Event Browser, into a consistent output format for porting to the Network
Management Layer.
ProVision can output events raised as a result of traps sent from a managed network
device, events raised as a result of polling a managed network device, events raised by
the ProVision platform
For most devices, you can customize event names and severity levels through their craft
tool. For selected devices, ProVision provides an Event Customization function. This
enables you to customize the ProVision database name and/or severity of external
alarm inputs and outputs for these devices. Using Event Customization, you can apply
customization settings to a single device, multiple devices of the same type, or all
devices of a specific type.
This slide shows examples of delivered event notifications via email, ProVision popup,
and mobile text message.
You can remotely upgrade software for the following devices:
All Eclipse Radios
All TRuepoint Radios
Base Stations
WSG ASN Controller (protected and non-protected)
WSG-R Juniper M7i
WSG-R Juniper M10i
A copy of each license is retained in …\ProVisionServer\repository\licenses after the
license is applied to the radio.
NOTE: When you upgrade to a higher version of ProVision, the licenses that were
applied to the radios are unaffected. It is recommended to save a backup copy of the
repository folder with the license files, then migrate the folder to the server once the
new version of ProVision has been installed.
The Export Configuration Backup screen displays. The screen lists the available backup
files for the node or device in which you can perform the following:
• Preview – Displays a preview of the backup
• Restore – Restore a selected backup file
• Export – Export and save the backup file (to export the backup, select the most recent
backup and click Export)
To get reports as related to Inventory, Capacity, Faults, Network Health and Security
Status or to customize reports, right click on the device, go to Reports and then any of
the associated components needed to build the report.
ProVision is to provide a mechanism to give the administrator the ability to display a list
of all current active sessions on the server and terminate selected sessions. Once a
session is terminated, the client will get a popup notifying that the session was
terminated by an administrator.
As a powerful, standards-based Element Management System (EMS) for access and
microwave transport networks, ProVision offers much more than a standard EMS or
generic SNMP manager.
It provides superior network intelligence for mobile and private network operators . As
part of this network intelligence, you can analyze your multi-million dollar network with
ProVision reporting.
ProVision reporting enables you to:
Save reports
Export your network data
Analyze it directly, no further reporting required
Note that some reports require performance data collection to be fully enabled.
This presentation provides a quick overview of ProVision’s reporting options.
This slide displays the Excel exported Network Inventory Report.
Network Health Reports (NHRs) provide a valuable overview of the performance of a microwave radio network. Use them to quickly analyze network performance and provide bench marking for
future reference.
NHRs inform users about the performance of a microwave network via ITU-T G.821 or G.826 statistics. These identify which radios are within a user-defined performance threshold, for example
which links are working below 99.99% availability.
The NHR output can be saved to a CSV format file, for importing into a spreadsheet or to PDF format files suitable for emailing or inclusion with a management report.
What are the benefits of Network Health Reports? Customers can monitor network performance function on a similar level outside of ProVision, but this can be a very labor intensive, time
consuming, and expensive. Using Network Health Reports saves time and money, but most of all, NHRs help customers focus their resources on improving network availability by being pro-active.
The Overview data for the network includes:

Mean Availability – indicates the average availability in percentage terms for all the links in the network report.
Mean Visibility – indicates the average visibility of the network or in other words the amount of performance data ProVision has been able to obtain. With 100% visibility – customers know the
availability data will be accurate. With low visibility, customers will know the availability data could be misleading and therefore they need to analyze the results in more detail.
Number of devices above or below threshold – the number of devices included in the report operating above or below the user-defined availability thresholds.
Devices with Zero Visibility –the number of devices from which ProVision has been unable to collect data from.
The Detail tab presents the data by device or node. Devices below the desired network health threshold are highlighted in red. There are three levels of detail that can be viewed; Low, Medium,
and High. Users can hide healthy devices and devices with zero visibility and if they select a specific device – then right mouse context sensitive menu options are available.
The aim is to provide complete radio coverage for Aviat microwave radios and with the release of ProVision 6.5 – we’re almost there. Network Health reports support:
Eclipse
TRuepoint 4000
TRuepoint 4040
TRuepoint 5000
TRuepoint 6400
TRuepoint 6500
Altium (all variants)
DART
LE3000
Radwin WinLink 1000
Spectrum II (all variants)
XP4 (all variants)
Microstar (all variants)
Velox
Network Health Reports are a licensed ProVision feature. However, the feature is priced to reflect the size of the network and even for large networks.
Add Email Action sends an email to a specified address or addresses when the report is
generated.
Add Directory Action saves the report to a directory on the Server PC.
The default directory is\ProVisionServer\repository\reports.
To change this directory, right-click on the Directory item and select Add Directory. The
Add/Remove Directories screen displays.
Click Add to add a new directory, typing the Name and Location in the fields.
Select a directory and click Remove to remove it from the list of locations
The Inventory Report in ProVision is the fastest and easiest way to view the inventory
details. The Inventory Report summarizes the components of the network for a selected
radio. It displays as a free-floating window that lists information about the radio,
including:
General information such as the device name, site name, IP address and device type
Active license certificate details
Manufacturing details such as the plug-in type and part number, serial number, and time
in service for each unit or plug-in
The Inventory report is available for the following devices:
Eclipse
TRuepoint
Constellation
LE3000 / LE3200
StarMAX base station
The Inventory Report can be saved to a CSV format file, for importing into a spreadsheet
or to PDF format files suitable for emailing or inclusion with a management report.
The Ethernet Bandwidth Utilization screen displays an overview of the throughput bandwidth
usage for the selected part of the network. This allows users to rapidly identify if the throughput
is exceeding the maximum bandwidth available for the link or links. Normally, users select a
Logical Link network or set of circuits to view.
Ethernet Bandwidth Utilization displays performance data for enabled ports and channels. Data
collection processes data for all enabled ports and channels. For example, if a port was operated
for three days and then disabled, the data from the port’s enabled period would still be
displayed, but no additional data would be saved.
If you select a large network to view, it takes time to generate the Ethernet Bandwidth
Utilization display: an hour or more. Generating this view for a large network also may slow your
ProVision system processing.
ProVision users can view the ethernet bandwidth use for:

Eclipse regions and containers
Eclipse devices
Eclipse circuits
StarMAX and associated WiMAX devices, specifically:
StarMAX base stations
WiChorus SmartCore ASN-GW
WSC ASN-GW Controller
Juniper M7i WSG-R
Juniper M10i WSG-R
The Eclipse Security Status Report is a feature specific to the Eclipse devices. This report
collects security data for one or more Eclipse devices. The report is in a free-floating
window that lists security information, including:
Portal Access - whether a device has its Portal access locked from , value is Locked or
Unlocked
Security Enabled - Checks to see if device security is enabled from Portal, value is False
or True
Portal Auto Login Status - If an auto-login is set, this is noted as Credentials Configured
You can save the Security Status Report as a .PDF or.xml file . You can also retain a
specific report configuration as a Custom Report for the selected devices.
From version 6.5.3 of ProVision, the Custom Reports feature enables users to create
customizable reports for devices.
Users can create, save, and edit Custom Reports, and regenerate the reports as
required.
Users can also edit standard ProVision reports and save them as custom reports. This
does not override the existing report.
Available customization options include an enormous range of basic, fault, and
performance data options.
This is a standard feature, available with all versions of ProVision.
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
maintenance 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 HelpDesk to assist you with your problem. The
HelpDesk compares the data in your Help Desk report to the Help Desk report that you
generated at the time of system commissioning.
This report automatically includes:
License details
System configuration
Log of SNMP round trip times for each radio
Log of heartbeat round trip times between the client and the server
Client log files
Server log files
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.
ProVision is used to manage mission critical transmission networks. ProVision’s security
features enable users to protect their equipment, their network integrity, and their
users’ vital personal information.
ProVision strengthens network managers’ ability to quickly manage changes, correct
defects, and report on network health and performance by supporting security for:
Users
Devices
Strong Security
Standby Server/Redundancy
The Security Log provides a record of user activity and device user activity events.
Whenever a user makes a change or performs an operation , an event for the change is
added to the Security Log. This tracks user change-related events and enables a
Administrator to identify which user is responsible for any activity.
The Security Log records user activity for the following:
The Physical Root level of
The Manager
Regions, Sites, and Containers
The following devices:
Altium
Eclipse
LE3000 and LE3200
TRuepoint 4000 and 5000
Velox
Each ProVision user must be assigned a user account. A user account includes a unique login
user name and password, and the user’s security profiles. A user can belong to more than one
security profile.
Administrator level users can manage the requirements for ProVision passwords using the
security_policy template in the ProVision Server program files. In this template, the
administrator can change the values to customize password and user name requirements.
User security levels are:

View - User can view data in ProVision. This does not enable any data editing.
Maintenance - User can view data and set maintenance controls on devices.
Configuration - User can view data and change device / ProVision configuration parameters.
Does not include security, administration, or software loading privileges.
Upgrade - User can view data and perform software upgrades on the network.
Administration - User can view data and perform database administration and ProVision user
account administration tasks. A default administration user will be created by the system when
ProVision is first installed. 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.
SEE PROVISION,INSTALLATION & ADMINISTRATION MANUAL Chapter 7. Access Control

Management
Administrator-level users can view security access details for all Containers and devices in a
network, using the Device Security Accounts screen.
All Containers and many devices can have their security details edited from this screen.
You can set up device security access accounts on a per region, site, or individual radio basis.
To facilitate Strong Security for devices, ProVision notes the users' security levels when they log
in. This means that administrators can enable a Single Sign On (SSO) mechanism. These SSO
credentials, deployed with other Aviat software, enable the user to log in automatically to
Eclipse Portal, Configuration Backups, and Software Loading at the appropriate level.
Using the Device Security screen, users can set device SNMP values and can set or edit device
SNMP security strings as public or private. This is only required if you have made other security
changes for a radio; these strings are normally set during deployment.
The Security Log provides a record of user activity and device user activity events collected by
ProVision. Whenever a user makes a change or performs an operation in ProVision, an event for
the change is added to the Security Log. This tracks user change-related events and enables a
ProVision Administrator to identify which user is responsible for any activity on ProVision.
•RADIUS should be enabled on both ProVision and the Eclipse
•The credentials of the ProVision user initiating the operation are used to authenticate
with the Eclipse
•Ensure that the correct ProVision and Eclipse user privileges are configured
•Select the radios that are to be updated with the new user account. To update the
entire network selected the ProVision Physical Root from the Physical View. Right-click
and select Configuration > Profiles, then from Configuration Profile dialog and select
the previously saved Eclipse Radio Accounts profile
•Add the new user to the profile. Usernames must be between 4 and 32 characters long
and the password must be 8 to 32 characters long and contain at least one letter and
one number.
•Select the required permissions for the user – the user must belong to at least one
group.
•Save the configuration profile.
•Select Execute to write the changes into each of the selected device. 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.
•The progress of the operation can be monitored using the Task Manager.
Strong Security enables ProVision users to use SNMPv3 privacy/encryption for devices in ProVision. SNMPv1 and
SNMPv2c protocols do not support privacy/encryption which means the SNMP data can easily decoded by using
freely available protocol analyzer software such as Wireshark. SNMPv3 provides “strong security” by preventing this
with privacy/encryption.
In many networks this is not considered a problem because the network management Data Communication Network
(DCN) is isolated from the internet. However, in some networks the DCN is transported over the internet. Therefore,
hackers might be able to access network equipment, change configuration settings, and cause malicious service
interruptions.
As of the 6.5 release of ProVision, TRuepoint 4040 v2 and 5000 devices with V2 controllers support Strong Security. In
the future Eclipse devices will
Strong Security is a licensed feature associated with Aviat equipment. While Strong Security requires a special license
in ProVision, it is provided free of charge to customers who have purchased Strong Security with Aviat equipment.
Strong Security and TRuepoint in Detail
TRuepoint 4040 v2 and 5000 devices with V2 controllers support DES, TDES, AES128, or, for US customers, AES192
and AES256 are also supported. To support SNMPv3 privacy/encryption the ProVision system requires:
A specific Strong Security license.
A Java cryptography extension (JCE unlimited strength jurisdiction policy file/s) from Sun Microsystems.
Contact your Aviat representative to obtain this license and this extension.
To activate Strong Security, SNMPv3 must be configured on TRuepoint devices as well as in ProVision. Strong Security
on TRuepoint devices is configured through WebCIT. Once the TRuepoint device has been configured with strong
security in WebCIT, the equipment can be deployed in ProVision, configuring it with the same options and passwords.
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 credentials enable the user to log in automatically to Eclipse Portal,
Configuration Backups, and Software Loading at the appropriate level.
SSO credentials are encrypted and only saved during the ProVision session; they are deleted when the user logs out.
Also, for Eclipse Portal, SSO is only active for devices with Eclipse 5.3 and later installed: devices with earlier versions
need to be managed as device security accounts.
Administrator level users can lock and unlock Eclipse Portal at the network level. Locking
Eclipse Portal means that only 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.
Administrators can unlock Portal access for specific Eclipse devices, 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.
The Standby Server provides the following capabilities:
1.Warm standby server redundancy with manual failover.
2. Active server database automatically 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, 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.
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, Active Server or Dormant Server is fully active at a given
time, although switching occurs quickly to the peer server when the main server fails.
The Redundancy Controller provides automatic failover ability so that when a problem
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 scenario,
ProVision Clients will have to be manually switched to the New Active Main Server.
The two servers are defined by the following:
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.
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.
Review the installation destination folder. Change this if required, and then click Next.
The Redundancy Controller must link to the ProVision server directory on this Server.
Change the required ProVision directory if incorrect [A valid ProVision server installation
must exist otherwise this step will not proceed]. Then, click Install.
Note: If the root directory Provision path is changed, the installation process will report
an error and will not proceed until the right root directory Provision path is selected
Note: The procedures highlighted must also be carried out on the second server.
To make one of the servers the Active Main Server, you click on unlatch to initialize,
synchronize and have the database running on the Active Main Server
System State
Local Status: Status of the main local server.
Peer Status: Status of the "peer server."
Control
Switch/Unlatch:
Click Switch to change the local server from Active to Dormant or vice versa. If the peer
server is Active you cannot switch the local server to Active.
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
Note: you must have the same version of Provison Redundancy Controller on both Servers
At the Redundancy Controller Configuration Screen,
• Enter the Peer IP address, set the FTP port

• The Server ID value of the Active Main server should be less than the Dormant Latched, this
ensures that the Active Main Server has a higher priority, in this example we have a value of 1
for the Active Main Server and a value of 2 for the Dormant Latched Server (number ranges
from 1 to 65535).
• Set the Dump Timeout – by default, this value is 400. This is the time in seconds for timeout
when backing up the database for server synchronization. For a large database, the default
value can be maintained as a value of 400 or set higher than 400 but for a small database, the
dump timeout can be less than 400
• Set file synchronization hour – this is the time that files are synchronized between the local
and peer server once per day at this hour, it is based on a 24hour clock. Example above 4
indicates 4am while a value of 16 indicates 4pm
• Enter Heartbeat Timeout - If the heartbeat synchronization fails, the timeout is the period of
time in seconds between retries. Default value is 5
• Enter Heartbeat Retries - If the heartbeat synchronization fails, the retry is the number of
times synchronization is attempted again.
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
Security
Password: Change the password for the logged in user.
Confirm Password: Confirm the changed password for the logged in 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 Secret: Confirm the "shared secret" password for the Radius server.
Primary Radius
Enter the following values for the primary Radius server:
•Server IP address
•Authentication Port
Secondary Radius
Enter the following values for the secondary Radius server:
•Check the box to enable this server if required
•Server IP address
•Authentication Port
The first thing to do is to make sure that both servers see each other by changing the
peer IP address and click on Apply
When Both servers see each other, they show as being in Dormant Latched state
1. You have to set one server to be the active controller by removing the latch hold
from the configuration and
2. Switch over the controller to the active side by going to Status > Switch.
3. This will startup
1. Switch over to the other Redundancy controller interface of the other server and
unlatch it from the Dormant latch state
2. This Redundancy controller will resynchronize with the Active Server firstly starts up
the ProVision database and then starts polling the files across
3. Finally it reaches its dormant state
1. To shut down an active server, you must latch the server Configuration>check Server
Latched
2. Switch it to the dormant state Status > Switch
3. The peer server fails over to become the Active Server
The same can be done also on the Active Server and then the full service of the
Redundancy controller can be stopped Start>ProVisionRedundancyController>Stop
Service
To restart the ProVisionRedundancyController,
Start>ProVisionRedundancyController>Start Service
The log file for the redundancy controller can be found in <Install
Directory>\ProVisionRedundancyController\jetty\rc.log
See ProVision IA Manual, Hot Standby Server Redundancy, for details and values
The SSM feature is an extension of the Synchronous Ethernet feature, and provides a
mechanism for monitoring the Quality level (QL) of configured clock sources, and for the
automated switching of the terminal’s clock source to the “best available” source.
The SSM QL values are the usual 4-bit values defined by ITU-T, ANSI and Telcordia. For
example…
QL-PRS: PRS traceable ([ITU-T G.811]).

QL-STU: Synchronized – Traceability unknown.
QL-ST2: Traceable to stratum 2 ([ITU-T G.812], type II).
QL-TNC: Traceable to transit node clock ([ITU-T G.812], type V).
QL-ST3E: Traceable to stratum 3E ([ITU-T G.812], type III).
QL-ST3: Traceable to stratum 3 ([ITU-T G.812], type IV).
QL-SMC: Traceable to SONET clock self timed ([ITU-T G.813] or [ITU-T G.8262],
option II).
QL-ST4: Traceable to stratum 4 freerun (only applicable to 1.5 Mbit/s signals).
QL-DUS: This signal should not be used for synchronization.
(1) Clock quality and stability performance indicators have been introduced to enhance
the ability to rapidly detect and diagnose synchronization problems in the network.
(2) The SSM QL values are the usual 4-bit values defined by ITU-T, ANSI and
Telcordia. For example…
QL-PRS: PRS traceable ([ITU-T G.811]).
QL-STU: Synchronized – Traceability unknown.
QL-ST2: Traceable to stratum 2 ([ITU-T G.812], type II).
QL-TNC: Traceable to transit node clock ([ITU-T G.812], type V).
QL-ST3E: Traceable to stratum 3E ([ITU-T G.812], type III).
QL-ST3: Traceable to stratum 3 ([ITU-T G.812], type IV).
QL-SMC: Traceable to SONET clock self timed ([ITU-T G.813] or [ITU-T G.8262],
option II).
QL-ST4: Traceable to stratum 4 freerun (only applicable to 1.5 Mbit/s signals).
QL-DUS: This signal should not be used for synchronization.
(1) Enables users to quickly verify the network clock distribution configuration. Due to
the complexity of the distributed configuration, the risk of misconfiguration is
significantly reduced.
(2) Based on the custom reports framework, users have flexibility to select devices and
parameters to be included and can quickly filter and sort the results.
(1) Our goal is to simplify provisioning and management through a high level of
automation, that provides for operational efficiency.
(2) Ethernet OAM is fundamental to providing Ethernet service assurance.
(3) Proactive monitoring: Link-Trace is applied automatically by EMS on detection of
configuration change or fault events.
(1) Automated discovery and visualization of Ethernet OAM services.
(2) New Services List, Service Inspection and Diagnostics views.
(3) Browser launched from Services List automatically provides a filtered list of the
events associated with the selected MA/MEG OAM service.
(1) Browser launched from MEP or MIP object automatically provides a filtered list of
the events associated with the DAC interface over which the MA/MEG is delivered.
(1) Although we support a number of 3rd party EOAM-capable devices today (e.g. Cisco
ME 4300), we do not yet associate their events to ports and services on those ports.
Hence, Tellabs 8600 MIP objects are grey above. Event correlation for key 3rd party
devices is planned in a future release.
• The AviatCare Online Customer Support Portal
offers many new features and enhancements to
improve overall online user experience
• New Features and Enhancements:

• Faster display and refresh speeds when entering the web site
• Formatted for the latest smart phones and tablets including iPhone and iPad
• Searchable knowledge base for quick and easy answers
• Expanded library of technical information in the knowledge base
• Intuitive knowledge base search functionality displays recommended
solutions to support requests based upon information entered into the case
• New feedback system allows customers to rate and provide feedback on all
knowledge base articles
• New feedback capability allows customers to rate their support requests
• Front end interface will now capture customer information
• New system automations allows us to respond faster to the customer
reducing the response time for escalation, case updates and resolution

SHB PRO E10 1 - Ebook PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SHB PRO E10 1 - Ebook PDF

Uploaded by

Copyright:

Available Formats

CUSTOMER TRAINING

TECHNICAL TRAINING STUDENT HANDBOOK

Part Number SHB-PRO-E10.1

Aviat Networks, Inc. www.aviatnetworks.com

Interface views are available for the following radio types:

ProVision supports up to 50,000 Eclipse circuits with:

How Does Event Pre-filtering Work?

The Overview data for the network includes:

ProVision users can view the ethernet bandwidth use for:

User security levels are:

SEE PROVISION,INSTALLATION & ADMINISTRATION MANUAL Chapter 7. Access Control

At the Redundancy Controller Configuration Screen,

• Enter the Peer IP address, set the FTP port

The failover window is defined in seconds by (heartbeat timeout * heartbeat retries). If no

QL-PRS: PRS traceable ([ITU-T G.811]).

• New Features and Enhancements:

You might also like