SHB ProVision E7.6.ebook
SHB ProVision E7.6.ebook
SHB ProVision E7.6.ebook
SHB-PRO-7.6
Revision History
Issue No. Issue Date ECO Description of Change / Revision
01 2/09/13 E6.10.1 Revision and Update
SHB-PRO-7.6
PROVISION
OPERATION AND
ADMINISTRATION
TRAINING V7.6
2 AVIAT NETWORKS
3 AVIAT NETWORKS
AVIAT NETWORKS
SNMP Management
Switches
CTR Routers
Eclipse Power Supplies
X 9000 *
Current Aviat + Obsolete AVIAT/Stratex/Harris/DMC/Other Vendors * Depending on SLV
6 AVIAT NETWORKS
7 AVIAT NETWORKS
ProVision is ideal for growing networks, and can be deployed for networks for just a few
devices 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
many legacy Aviat microwave and networking platforms are supported by ProVision,
including CTR, WTM, and Eclipse™. In addition, Pro Vision also supports many non Aviat
devices, either natively or through package level support.
8 AVIAT NETWORKS
Server/Client
Same machine
LAN
Network Devices
10 AVIAT NETWORKS
The most simple form of Pro Vision deployment is running the server and a single client on the
same machine. The local client is used for establishing a client-to-server session on the server,
eliminating the need to mount files across the network. This deployment is only recommended
for small installations. Users may access the client directly or even with a remote desktop
session.
Server
Machine
LAN
Network Devices
11 AVIAT NETWORKS
Optional ProVision remote LAN client workstations enable multiple concurrent user sessions. The
maximum number of concurrent client user sessions is 15. When running remote clients, server
to client latency must be considered. In a system with multiple clients, slow latency of a single
client can impact the performance of all clients. The recommended latency of any single client is
10 milli seconds with a maximum of 20 milli seconds.
Server
Machine
LAN
WAN
Server
WAN (E1/T1)
WAN Client
Network Devices
12 AVIAT NETWORKS
Another remote client connectivity option is a WAN connection. WAN connections typically
exhibit higher latency and lower bandwidth when compared with LAN connections. 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.
LAN
WAN
Server
WAN (E1/T1)
WAN Client
Network Devices
13 AVIAT NETWORKS
The most simple form of Pro Vision server redundancy is the standby server option. The Standby
server option offers warm standby server redundancy with manual failover. The active database
is typically backed up once per day, so in the event of an active server failure, some data may be
lost. The standby server only requires a second server with the same Pro Vision licensing as the
main server. No additional software is required.
LAN
WAN
Server
WAN (E1/T1)
WAN Client
Network Devices
14 AVIAT NETWORKS
The redundancy Controller option offers enhanced Pro Vision Server redundancy with hot
standby server redundancy and automated failover. The databases are synchronized in near real
time, so there is minimal data loss. The redundancy controller option requires the same Pro
Vision licensing on each server plus the redundancy controller application software and licensing
on each machine.
Maximum 20 This is the maximum latency for any PV Client connection to the
PV Server. Exceeding this value will result in poor performance
16 AVIAT NETWORKS
When planning a network, it is important to know the number of devices your network will
have, to determine the hardware specification. Some devices place more loading on the
server than others. Calculating a server loading value determines the required system
resources for the devices. Calculate the Server Loading Value (SLV) from the equation:
Where the letters A, B, and C are determined by the type of devices in your network and
are listed in Chapter 3 – Installing ProVision - ProVision Installation and Administration
Manual
17 AVIAT NETWORKS
AVIAT NETWORKS
19 AVIAT NETWORKS
Local PC
HTTP
Interface LAN/WAN
Client
Software
Client installation setup Software
can be downloaded after the
installation of the server by opening
http://<serverIP>:8080/ http://<server IP>/pvweb (for
example http://10.20.1.1/pvweb) on
a web browser
20 AVIAT NETWORKS
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.
Username: admin
Password: admin
Or use credentials
provided by the
administrator
21 AVIAT NETWORKS
Click on Download to
run the PV client
installation on your PC
22 AVIAT NETWORKS
Other Commands:
23 AVIAT NETWORKS
Enter user name and password. For example (default login details):
User: admin
Password: admin
Enter the Name or IP Address of your ProVision Server or localhost if Client/Server on same machine
Select Login
24 AVIAT NETWORKS
Global Event
Browser
25 AVIAT NETWORKS
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
27 AVIAT NETWORKS
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.
29 AVIAT NETWORKS
Physical Map View = overview of the network. Displays only the first level of children under the parent
object selected. Click on the Physical Map icon:
Flat Map View = entire network in a single level. Only the network devices and links are displayed, all
network objects. Click on the Flat Map icon:
30 AVIAT NETWORKS
• F1 short cut
• Context
Sensitive
• Searchable
32 AVIAT NETWORKS
1. Download the ProVision Client from the Classroom Pro Vision Server.
2. Install the ProVision Client (if the student has a different version of PV Client already
installed on their machine, The new version will overwrite/update their other version).
3. Once installed, log in using the classroom server's IP Address and the default
username and password.
4. Get familiar with the interface, clicking on various menu options
5. Rearrange/Close the various viewing areas and the reset using the Windows/Reset
Layout pull down menu.
6. Optional- add a background image (Student will have to add an image from their
Client machine, which will be transferred to the classroom Server).
7. Add Map annotation, for example students first name of company name.
8. Open up the help system by clicking F1.
33 AVIAT NETWORKS
AVIAT NETWORKS
35 AVIAT NETWORKS
36 AVIAT NETWORKS
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
39 AVIAT NETWORKS
• Database Backups
✓ Manual
✓ Scheduled
• Database Restore
• Database Purge
• To perform database backup go to
Administration > Database Backup >
Manual Backup or Scheduled
Backup
40 AVIAT NETWORKS
• Administrators can set the location where ProVision will save backup files,
ProVision will save both manual and scheduled backup files to this location.
• From the menu bar, select Administration > Database Backup > Backup
Preference
• Enter the backup location. If it is accessible, a green check displays beside the
location. If it is not accessible, a red X displays, and you must enter a different
location
• When your location is valid, click OK
41 AVIAT NETWORKS
• Administrators can set how long parameters like Daily and 15-minute
Performance, Cleared Events, and Security Events are stored in the database
• From the menu bar, select Administration > Database Purge
42 AVIAT NETWORKS
43 AVIAT NETWORKS
44 AVIAT NETWORKS
1. Each Student should create their own User Account with full
security profile and regional access.
2. Log out and re-log in with the new user account.
3. View the session Manager and verify what other students are
logged in and their latency.
4. Save a Manual Database backup.
5. View manual database Purge settings.
6. Export a topology file.
47 AVIAT NETWORKS
AVIAT NETWORKS
✓ Region
✓ Site
✓ Rack
✓ User Defined
49 AVIAT NETWORKS
NOTE: A high level container can have additional containers and devices. For example, a
region may consist of several sites and devices.
50 AVIAT NETWORKS
51 AVIAT NETWORKS
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
Before deploying CTR 8540 or CTR 8300 devices in ProVision, you must use CLI
commands on the device to enable SNMP and to create a ProVision user account with
root access for the device. This enables communication with ProVision.
A device can be deployed but not managed, if the device is not currently installed or not
reachable through the network. At a later date the device can be chosen to be managed.
Un-Managed devices show a dark blue color in the display. When a device is Un-
Managed, Pro Vision does not waste resources trying to find and manage the device.
5. Deployment Successful !
55 AVIAT NETWORKS
For Eclipse, SNMP v2c Read and Write Community strings should always be “terminal”
and “terminal”
SNMP Management requires SNMP v3 licensing for Pro Vision and Strong Security
licensing on Eclipse.
Un-managed Devices
show Dark Blue
To Manage or Un-manage a Device, Right click on the Device and check or uncheck Manage
58 AVIAT NETWORKS
A device may be chosen to be unmanaged in Pro Vision while waiting for the device to
be installed at the site or waiting for network connectivity.
Once a device is found by Pro Vision, If a loss of communication with the device occurs,
the device will go into an errored state.
•CTR
•Eclipse
•StarMAX WiMAX base
station (BS) devices
•Constellation
•TRuepoint
59 AVIAT NETWORKS
60 AVIAT NETWORKS
AVIAT NETWORKS
• Features
✓ Google maps integration (devices, RF
links, other app users)
✓ Event browsers, scoreboards
✓ Configuration viewer
62 AVIAT NETWORKS
Examples of the
user screens
64 AVIAT NETWORKS
65 AVIAT NETWORKS
66 AVIAT NETWORKS
AVIAT NETWORKS
69 AVIAT NETWORKS
70 AVIAT NETWORKS
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.)
71 AVIAT NETWORKS
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.
*See Appendix B
for details on setup
and deployment
Proxy Supported Architecture
72 AVIAT NETWORKS
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.
73 AVIAT NETWORKS
AVIAT NETWORKS
• Re-parent by
✓ Unlock Tree Viewer for editing
✓ Drag and drop an object between containers
✓ Lock Tree Viewer after editing
75 AVIAT NETWORKS
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
76 AVIAT NETWORKS
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.
77 AVIAT NETWORKS
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.
78 AVIAT NETWORKS
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.
79 AVIAT NETWORKS
• For CTR and Eclipse radios, the Configuration Viewer window has separate tabs that
list the radio frequency configuration for each link.
• It also includes tabs with software version and Inventory details for the radio.
• The drawing above shows the Configuration Viewer windows for an CTR.
• CTR also contains an Ethernet Interface status Tab.
• The Configuration Viewer varies depending on the radio.
80 AVIAT NETWORKS
81 AVIAT NETWORKS
82 AVIAT NETWORKS
83 AVIAT NETWORKS
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.
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.
85 AVIAT NETWORKS
86 AVIAT NETWORKS
87 AVIAT NETWORKS
CTR
Eclipse
ADR 155c
ADR 2500
Constellation
MegaStar M:N and 1+1
TRuepoint 4040 and 5000
TRuepoint 6400
TRuepoint 6500
StarMAX 6100 and 6400
WiMax ASN-GW Home Agent
WTM6000
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.
90 AVIAT NETWORKS
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.
# Value
1 Expand or Collapse sub-components of a device
2 Color here indicates the event severity. Mouse over this to view the
event type
3 Device Icon
4 Task icon, is present when a task is running
5 Device name
91 AVIAT NETWORKS
92 AVIAT NETWORKS
Critical Red
Major Orange
Minor Yellow
Warning Cyan
Normal Green
Informational White
93 AVIAT NETWORKS
94 AVIAT NETWORKS
95 AVIAT NETWORKS
96 AVIAT NETWORKS
AVIAT NETWORKS
Sort function
Display circuit status,
Start /End, capacity,
type, & priority
Filter view,
Export circuits Display circuit path
98 AVIAT NETWORKS
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.
99 AVIAT NETWORKS
Map
Item Definition
Name Name of the circuit link
Start Connectable Eclipse radio and DAC plug-in/port for the circuit connection
beginning
End Connectable Eclipse radio and DAC plug-in/port for the circuit connection
end.
Capacity Total Capacity of the Link
Type Circuit type: E1, E3, STM1, Ethernet, Ring
Priority Related to Adaptive Modulation, assigned in Eclipse Portal if
applicable
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.
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.
AVIAT NETWORKS
111
VLAN : DISCOVERY & VISUALIZATION : VLAN TABLE
Attributes :
1.Automated discovery
2.Lists all discovered VLANs
3.Updates in near real-time
4.VLAN alarm status
5.VLAN config check (future)
6.VID, Name, Member devices
7.VLAN mode (Transparent, Trunking,
Tunneling, Tagging)
8.EOAM monitoring indicator
9.L1 ring (with VLAN) indicator
10.ERP Control VLAN indicator
11.Sort / Filter / Search productivity
12.Export reporting
112
VLAN : DISCOVERY & VISUALIZATION : VLAN TABLE
DEVICE MODE
Attributes :
1.Separate entry for each VLAN
member DAC GE3 card
2.Example: VID 198 has an entry for
each of 8 cards (in 6 devices)
3.User ports and Network ports
indicated for each card
113
VLAN : DISCOVERY & VISUALIZATION : VLAN MAP
Attributes :
1.VLAN configuration & topology
correlated with L1 topology
2.Network ports
3.User (access) ports
4.Port alarm status
5.L1LA, LAG trunk ports
6.Port details through tooltips…
114
VLAN : DISCOVERY & VISUALIZATION : VLAN MAP
Examples :
1.Service 5
2.Service 8
3.Service Multiple
115
VLAN : DISCOVERY & VISUALIZATION : MAP OVERLAY
Attributes :
1.Available Physical & Flat maps
2.User selects VLAN to overlay
3.VLAN and L1 topology correlation
116
ETHERNET LINK MANUAL DEPLOYMENT
Attributes :
1.Ethernet Link (dotted line): Manual
deploy
2.RF Link (full line) : Auto discovery
or Manual deploy
117
VLAN PROVISIONING FOR CTR DEVICES
1.Launch Tool from the
VLAN Tab, the
configuration Pull-down
menu, or directly from
the device or port
2.VLANS can be
created, modified, or
deleted
3.Standard Provisioning
for VID, VLAN name,
tagged/untagged, and
port enable/disable
4.Advanced
Provisioning for VLAN
Filtering and priority
(untagged only)
Eclipse VLAN Provisioning is in the Beta stage, Portal should be used to provision Eclipse
VLANs
AVIAT NETWORKS
• Event Browser filters & sorts events by location, status, severity, description, radio name
/ type, raised / cleared time
• Right-click events to view event history, probable cause & repair actions
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.
• Create thresholds
based on RF or
Ethernet
performance data
• Customize event
names and severity
levels
For most devices, you can customize event names and severity levels through their craft
tool. For selected devices, ProVision provides an Event Customization function. This
enables you to customize the ProVision database name and/or severity of external
alarm inputs and outputs for these devices. Using Event Customization, you can apply
customization settings to a single device, multiple devices of the same type, or all
devices of a specific type.
This slide shows examples of delivered event notifications via email, ProVision popup,
and mobile text message.
AVIAT NETWORKS
142
142 AVIAT NETWORKS
• When the device type is selected, a browser will open to find the software to be
registered.
• Registering the software will transfer a copy of the software to the Pro Vision Server’s
directory
• Multiple software versions can be registered, even for the same device type
• The number of concurrent loads will that should be selected will depend on the
network bandwidth, default is 5
144
144 AVIAT NETWORKS
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)
AVIAT NETWORKS
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.
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:
CTR
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.
153
153 AVIAT NETWORKS
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 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.
• Can be viewed by
clicking on the Reports
tab > Scheduled Reports
• To add a Schedule,
click on the Add
button
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 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.
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.
AVIAT NETWORKS
AVIAT NETWORKS
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
• RADIUS integration
• Single sign-on access to
ProVision and Portal
• Pre-defined user security
profiles
• Account Status controls –
Regional Access
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.
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.
✓ TDES
✓ AES128
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.
AVIAT NETWORKS
#1 #1 #1
Rated Service
microwave turnkey Infonetics rated for partner by our largest
provider in NA/Africa Service & Support customers
5 $130+ 200+
regional technical million dedicated service
support centers FY13 services delivery resources
business
Before we delve into what each of these services do, here is a look at some of
our achievements –
At Aviat we take pride in the level of international and local recognition we have
gained on our service capabilities. We may not be the biggest but we are
consistently rated the best amongst our customers.
Our expertise and experience working not only in some of the most demanding
environments but also extremely demanding industries has allowed us to build a
wealth of knowledge on what is required to be successful. Whether it is Low
Latency networks where time is literally money, or Emergency Response
Networks where performance can mean life or death Aviat has worked with
customers to deliver solutions where 4 and 5 9’s availability is standard. We can
bring that expertise to you as well.
184
AVIATCARE EDUCATE
facts and figures - FY2014
5 ~100 210+
technical training customer locations training sessions
centers served worldwide conducted
AVIAT NETWORKS
185
AVIAT NETWORKS GLOBAL SERVICES
AVIATDESIGN AVIATDEPLOY
CUSTOMER AVIATCARE
ASSURANCE
EXTENDED /
CORRECTIVE / CUSTOMER
ENHANCED
PREVENTATIVE TRAINING
WARRANTY
AVIATCARE
MANAGED NETWORK
SPARES
NETWORK OPTIMIZATION
MANAGEMENT
OPERATIONS SERVICES
AVIAT NETWORKS
186
WAYS TO ACCESS TECHNICAL SUPPORT
1. Self Service using Aviat Knowledge Base
Need documentation?
Manuals
Release Note
News update
Need Software
Latest version?
Previous version?
Just go to the
Download page and
you will get everything
you need
AVIAT NETWORKS
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
The service can be restarted or stopped from the main Start menu item ProVision
Redundancy Controller.
Note: The procedures highlighted must also be carried out on the second server.
To log onto the Redundancy controller, you go to Start Menu > Provision Redundancy
Controller > Launch. By default the username and password is ‘admin’
The Redundancy Controller is now installed and running on both Servers in a Dormant Latched state
and needs to be further configured so that Redundancy across the two Servers is activated.
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
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
Set server to be
the active
controller by
removing the
3
latch hold
The ProVision
database and
tomcat will
startup
2
Switch over the
controller to the
active side
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 3
Unlatch it from Reaches dormant
the Dormant state
latch state
2
Resynchronization
with the Active
Server
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
Both systems are running and a client can be connected to the Active Main Server
1 2 3
1. To switch active servers between machines, simply Switch the active server to the dormant
side by clicking on Status>Switch.
2. This will cause the current dormant to go into a failover state.
3. After some time the dormant server will start initializing itself to become the Active Server.
The original active server will startup to the dormant side
1
To shut down an
active server, you
must latch the server 3
The peer server
fails over to
become the Active
Server
2 Switch it to the
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
AVIAT NETWORKS
218
EOAM : DISCOVERY & VISUALIZATION : SERVICES
TABLES
VLAN attributes :
1.Service 5 (VID 57) example
2.EOAM indicator
MA attributes:
1.Automated discovery
2.Lists all discovered EOAM MAs
3.Updates in near real-time
4.802.1ag and Y.1731 support
5.Automated Link-Trace
6.Automated MA validation
7.MA alarm status
8.MA config validation
9.Size (MEP/MIP hop count)
10.Sort / Filter / Search productivity
11.Export reporting
219
EOAM : DISCOVERY & VISUALIZATION : MAP
Attributes :
1.EOAM MA and L1 (RF, Ethernet) topology
correlation
2.MA connectivity status…
220
EOAM : DISCOVERY & VISUALIZATION : MA DETAILS
Attributes :
1.MA connection topology
2.MEP/MIP and port alarm status indication
(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.
221
EOAM : DIAGNOSTICS (ON-DEMAND)
Attributes :
1.EOAM MA topology
2.Link Trace and Loopback
on-demand diagnostics
3.Initiator, Target MEP, and
Time to Live selection
4.Timeout and VLAN priority
selection for Y.1731 MA
5.Real-time status update with
detailed results
222
EOAM : PROVISIONING : ACCESS
Attributes :
1.Access via right-click VLAN and EOAM table entries or
main Configuration menu
223
EOAM : PROVISIONING : FROM VLAN
Procedure :
1.Select VLAN
2.Right-click EOAM Provisioning Object A (device / interface
/ port)
3.Configure and Commit
1. Object B (device / interface / port)
2. Mode, MD/MEG Level, Direction
3. MA/ME name
4.Advanced (optional)
1. MEP #, MIPs, MIP Creation
2. CCM interval, CCM Priority
Use EOAM Inspection view to validate
224
COMPOSITE VIEWS : VLAN + EOAM EXAMPLE
Attributes
1.Flexible UI framework can be
used to combine panes to
create composite views
required
2.Example: Tree
+ VLAN table
+ VLAN map
+ MA table
+ MA topology diagnostics
225
APPENDIX C –
ETHERNET RING PROTECTION
ERP
AVIAT NETWORKS
1. System automatically discovers all ERP rings and L1 rings (including changes)
in near real-time.
2. System automatically detects faults in ERP rings (EOAM and configuration).
3. Users can view list of all ERP rings and L1 rings and identify which ones have
faults.
4. Users can view ERP ring configuration details including errors in the
configuration.
5. Users can correlate ERP ring configuration, topology, fault information to
diagnose faults.
6. Users can create a new ERP ring from an existing L1 ring and VLAN, and can
edit/delete an existing ERP ring.
227
ERP : DISCOVERY & VISUALIZATION : ERP DETAILS
(VIA VLAN)
VLAN attributes :
1.VID 57 provides ERP Control
VLAN for 7-hop ERP ring
2.ERP Details available through
VLAN table
228
ERP : DISCOVERY & VISUALIZATION : ERP EOAM MAS
VLAN attributes :
1.VID 57 provides ERP Control VLAN
for 7-hop ERP ring
MA attributes:
1.MA for each hop in ERP ring
229
ERP : PROVISIONING : ACCESS
Attributes :
1.VLAN right-click menu + Main
Configuration menu access
2.Select Layer 1 ring with VLAN
to create new ERP ring
3.Edit or delete existing ERP ring
by selecting ERP Control VLAN
230
ERP : PROVISIONING : FROM VLAN
Procedure :
1.Select VLAN
2.Right-click ERP / Provisioning
3.Select L1 ring
4.Configure and Commit
1. ERP ring name, Control VID
2. MD / MEG Level
3. Virtual chl MD Level (for subring)
4. RPL Owner
Use EOAM and VLAN tables to validate
231
APPENDIX D –
CLOCK SYNCHRONIZATION OAM
AVIAT NETWORKS
• Features include...
• Clock Sync Distribution view
• Clock Sync Network Health Report
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…
• Automated discovery
& live network view
✓ Clock sources
✓ Distribution
✓ Priority
(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.
• Clock performance
management
• Quality Level (QL) based on SSM
values (ITU-T, ANSI and Telecordia)
• Stability (switching rate)
• Clock not locked (% time)
Network Report
1.Based on Custom Reports framework;
Sort, Filter, Hide processing efficiency
2.Verification of network clock sync
configuration; quickly identify
misconfiguration
3.Reports (PDF, Excel)
(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.