ProVision Plus

User Guide

Version: 2.4.0
260-668271-001
LA Release
 Copyright & Terms of Use

Copyright & Terms of Use

May 2019
This documentation incorporates features and functions provided with ProVision Plus; 2.4.0; LA
Release.

Copyright © 2019 by Aviat Networks, Inc.

All rights reserved.
No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any language or computer language, in any form or by any means, electronic,
magnetic, optical, chemical, manual, or otherwise, without the prior written permission of Aviat
Networks Inc.
To request permission, contact Aviat via [email protected]

Warranty
Aviat Networks makes no representation or warranties with respect to the contents hereof and
specifically disclaims any implied warranties or merchantability or fitness for any particular purpose.
Further, Aviat Networks reserves the right to revise this publication and to make changes from time
to time in the content hereof without obligation of Aviat Networks to notify any person of such
revision or changes.

Safety Recommendations
The following safety recommendations must be considered to avoid injuries to persons and/or
damage to the equipment:
• Installation and Service Personnel: Installation and service must be carried out by
authorized personnel who have the technical training and experience necessary to be aware
of any hazardous operations during installation and service, and of measures to avoid any
danger to themselves, to any other personnel, and to the equipment.
• Access to the Equipment: Access to the equipment in use must be restricted to service
personnel only.
• Safety Norms: Recommended safety norms are detailed in the Health and Safety sections of
the product's Installation guide.
• Service Personnel Skill: Service personnel must have received adequate technical training
on telecommunications and in particular on the equipment and capabilities this addendum
refers to.

Aviat Networks May 2019 iii

Copyright & Terms of Use

Trademarks
All trademarks are the property of their respective owners.

iv May 2019 Aviat Networks

 Aviat Networks Technical Support

Aviat Networks Technical Support

Service and Technical Support:
For customer service and technical support, contact one of the regional Technical Help Desks listed
below.

Americas Technical Help Desk EMEA Technical Help Desk Asia Pacific Technical Help
Desk

Aviat Networks, Inc. Aviat Networks Aviat Networks

San Antonio, TX Blantyre, Glasgow, Scotland Clark Freeport Zone
U.S.A. G72 0FB Philippines 2023
United Kingdom
Phone:+1 210 526 6345 Phone: +1 210 526 6345 Phone: +1 210 526 6345
Toll Free (USA): Fax: Fax: +63 45 599 5196
+1 800 227 8332 +44 16 9871 7204 (English)
Fax:+1 210 526 6315 +33 1 5552 8012 (French)
Email: Email: Email:
[email protected] [email protected] [email protected]

Global Support Hotline: +1 210 526 6345

Call this phone number for support from anywhere in the world. Aviat Networks' Global Support
Hotline is available 24 hours a day, 7 days a week, providing uninterrupted support for all our
customers.
When you call our Global Support Hotline:
• You will be greeted by an automated response that will ask you for your PIN#. Request a
PIN# here: http://aviatnetworks.com/contact-us/technical-assistance/pin-request-form/ .
• As soon as you enter your PIN#, you will be transferred to our Global Technical Helpdesk that
will assist you with your technical issue.
• If you do not have a PIN# your call will be answered by our Support Assurance Desk. Your
call will be supported and prioritized accordingly.
Or you can contact your local Aviat Networks office. Contact information is available on our
website at: http://www.aviatnetworks.com/services/customer-support/technical-assistance/

Aviat Networks May 2019 v

Aviat Networks Technical Support

Sales and Sales Support:

For sales information, contact one of the headquarters, or find your regional sales office at:
HTTP://WWW.AVIATNETWORKS.COM/.

Corporate Headquarters International Headquarters

California, USA Singapore
Aviat Networks, Inc. Aviat Networks(S) Pte. Ltd.
860 N. McCarthy Blvd., Suite 200 51 Changi Business Park Central 2
Milpitas, CA 95035 #04-10 The Signature
U.S.A. Singapore 486066

Phone: + 1 408 941 7100 Phone: + 65 6496 0900

Fax: + 1 408 941 7110 Fax: + 65 6496 0999>
Toll Free for Sales Inquiries: Sales Inquiries:
+ 1 888 478 9669 +1-321-674-4252

vi May 2019 Aviat Networks

 Conventions and Terminology

Conventions and Terminology

This document uses the following conventions and terminology.

Graphic Cues
The following items have graphic cues to identify important supporting information.

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

Caution: A caution item identifies important information pertaining to actions that may
cause damage to equipment, loss of data, or corruption of files.
Warning: A warning item identifies a serious physical danger or major possible problem.

Font Changes
Bold font is used for the names of on-screen elements such as; fields, buttons, and drop-down
selection lists, keywords, commands and for keys on the keyboard.
Courier font in blue text is used to indicate commands that the user needs to type in, with the
command prompt shown as brown text.
AOS# show radio-carrier status Carrier1/1
Any responses or report output from a command is shown as brown text and indented.
radio-carrier status Carrier1/1
oper-status up
Italic font is used to emphasize words and phrases, to introduce new terms, and for the titles of
printed publications.
Button text is highlighted to indicate a click action on the named button.
Menu Navigation through a GUI to a particular screen is highlighted to distinguish from normal text.

Common Terminology
Click or Select: Point the mouse pointer at the item you want to select, then quickly press, and
release the left mouse button.
Right-Click: Point the mouse pointer at the item you want to select, then quickly press and release
the right mouse button.

Aviat Networks May 2019 vii

 Contents

Contents
Copyright & Terms of Use .......................................................................................................... iii
Aviat Networks Technical Support .............................................................................................. v
Conventions and Terminology ................................................................................................... vii
Contents .....................................................................................................................................ix
Chapter 1. Welcome to ProVision Plus................................................................................... 15
Intended Audience ................................................................................................................... 15
What You Need to Know to Use ProVision Plus ....................................................................... 15
Additional Resources................................................................................................................ 15
About ProVision Plus ................................................................................................................ 16
Network Communication ...................................................................................................... 16
Automatic Network Topology Construction .......................................................................... 16
Multi-Layer Topology Visualization ....................................................................................... 16
Rapid Troubleshooting ......................................................................................................... 16
Configuration Validation ....................................................................................................... 17
Network Health Analysis ...................................................................................................... 17
Service Impact Analysis ....................................................................................................... 17
Service Diagnostics ............................................................................................................. 17
Network Troubleshooting With ProVision Plus .......................................................................... 17
Carrier Ethernet Network Layer Modeling ................................................................................. 19
MPLS Network Layer Modeling ................................................................................................ 20
Chapter 2. Getting Started ....................................................................................................... 25
Installing and Running the Product ........................................................................................... 25
System Administration .............................................................................................................. 25
Product License Options .......................................................................................................... 25
Product Modules and Supported Device Types ........................................................................ 26
Chapter 3. Network Deployment ............................................................................................. 27
Communication with Devices.................................................................................................... 28
Manual Deployment using Deploy Object ................................................................................. 28
Container Deployment ......................................................................................................... 29
Device Deployment .............................................................................................................. 30
Access to Deploy Objects .................................................................................................... 31
Automated Deployment via ProVision System .......................................................................... 31
Topology Import Details ....................................................................................................... 31
Handling of Device and Container Name Conflicts ............................................................... 33
Configuring SNMP Notification Initiated Event Collection ......................................................... 33
Making Changes to Deployment ............................................................................................... 33
Rename Device or Container ............................................................................................... 33
Reparent Device or Container .............................................................................................. 34
Delete Device or Container .................................................................................................. 34
Manual Deployment of Physical Links ...................................................................................... 34
Baselining of Network Deployment Changes ............................................................................ 35
Chapter 4. Device Access Control .......................................................................................... 37

Aviat Networks May 2019 ix

Contents

Direct Device Access Control ................................................................................................... 38

Access to Direct Device Access Control View ...................................................................... 38
Direct Device Access Control View Controls ........................................................................ 38
Direct Device Access Control View Attributes ...................................................................... 39
ProVision Network Access Control ........................................................................................... 39
Chapter 5. Multi layer Network Topology Visualization......................................................... 41
Overview of Topology View ...................................................................................................... 42
Complementary Views ......................................................................................................... 42
Baseline vs Live Selector ..................................................................................................... 43
Topology View Alarm Status Indicators ................................................................................ 44
Topology Discovery ............................................................................................................. 44
Topology Map .......................................................................................................................... 45
Map Controls ....................................................................................................................... 47
Map Object Right-Click Menu Navigation ............................................................................. 49
Layers Selector .................................................................................................................... 50
Paired Device Representation ............................................................................................. 53
Services Representation at Each Layer ............................................................................... 54
Service Links Bundling ......................................................................................................... 61
Hidden RT Links (Exceeding Display Max Limit) .................................................................. 62
Navigating Between Interconnected Layers ......................................................................... 62
Map Coordinates ................................................................................................................. 72
Overlay Data and Auto Update ............................................................................................ 76
Detail / Key Indicators .......................................................................................................... 77
Data Panel ............................................................................................................................... 78
Data Panel Tabs .................................................................................................................. 79
Data Panel Controls ............................................................................................................. 81
Data Panel Attributes ........................................................................................................... 81
Tree Context Selector............................................................................................................... 82
Devices Tree........................................................................................................................ 82
Services Tree....................................................................................................................... 82
Tree Context Selector Controls ............................................................................................ 84
Tree Object Right-Click Menu Navigation ............................................................................ 85
Detail View ............................................................................................................................... 86
Detail View Display Areas and Controls ............................................................................... 87
Detail View Attributes ........................................................................................................... 88
Comparison View................................................................................................................. 88
Topology Filtering ..................................................................................................................... 89
Example Topology Filters..................................................................................................... 90
Chapter 6. Configuration Management................................................................................... 95
Network Device Detail .............................................................................................................. 96
Access to Network Device Detail View ................................................................................. 96
Network Device Detail View Controls ................................................................................... 96
Network Inventory .................................................................................................................... 98
Access to Inventory View ..................................................................................................... 99
Inventory View Controls ....................................................................................................... 99
x May 2019 Aviat Networks
 Contents

Direct Device Management .................................................................................................... 100

Access to Direct Device Management View ....................................................................... 100
Direct Device Management View Controls ......................................................................... 101
Direct Device Management View Attributes ....................................................................... 101
Managing Customized Layouts .............................................................................................. 102
Procedure: Create a New Layout ....................................................................................... 102
Device Configuration Backup and Restore ............................................................................. 103
Config Backup and Restore ............................................................................................... 103
Device Config Backup Settings .......................................................................................... 104
Device Licensing .................................................................................................................... 105
Access to Licensing View................................................................................................... 106
Licensing View Controls ..................................................................................................... 106
Licensing Task Dialog ........................................................................................................ 107
Device Software Loading ........................................................................................................ 107
Access to Software Loading View ...................................................................................... 108
Software Loading View Controls ........................................................................................ 108
Load Software Task Dialog ................................................................................................ 110
Software Loading Device Table ......................................................................................... 110
Task Manager ........................................................................................................................ 111
Access to Task Manager View ........................................................................................... 112
Task Manager View Controls ............................................................................................. 112
Task Log Dialog ................................................................................................................. 113
Chapter 7. Managing Network Configuration Changes ....................................................... 115
Monitoring Live Network for Configuration Changes ............................................................... 116
Baseline / Live Selection ........................................................................................................ 116
Live Network Configuration Change Indicators ....................................................................... 117
Reconciliation Report ............................................................................................................. 118
Promoting Live Network Changes to Baseline ........................................................................ 118
Chapter 8. Event Alarm Management ................................................................................... 121
Introduction to Events and Alarms .......................................................................................... 122
Events and Alarms ............................................................................................................. 122
Devices Events and Alarms ............................................................................................... 122
Services Alarms ................................................................................................................. 122
Services Alarms Propagation Behavior .............................................................................. 123
Attributes of Events and Alarms ......................................................................................... 123
Severity Color Coding for Events and Alarms .................................................................... 125
Event Browser ........................................................................................................................ 125
Event Browser Areas and Controls .................................................................................... 125
Acknowledge Event ........................................................................................................... 126
Manually Clear Event ......................................................................................................... 127
Event Browser Filter Configuration..................................................................................... 127
Managing Customized Event Browser Filters ..................................................................... 128
Services Alarms Root Cause Devices Alarms .................................................................... 129
Access to the Event Browser ............................................................................................. 130

Aviat Networks May 2019 xi

Contents

Alarm Status Indicators .......................................................................................................... 131

Device Alarm Status Indictors ............................................................................................ 131
Service Alarm Status Indictors ........................................................................................... 132
Network Alarm Indicators ....................................................................................................... 132
Chapter 9. Performance Management .................................................................................. 135
Data Collection ....................................................................................................................... 136
Resource Performance........................................................................................................... 136
Access to Resource Performance View ............................................................................. 136
Resource Performance View Controls ............................................................................... 137
Overview (Timeline Summary) Tab .................................................................................... 141
Chart Tab........................................................................................................................... 143
Detail Tab .......................................................................................................................... 144
Resource Selection Via Devices Tree ................................................................................ 144
Network Health ....................................................................................................................... 144
Access to Network Health View ......................................................................................... 146
Network Health View Controls ........................................................................................... 147
Overview (Summary) Tab .................................................................................................. 148
Detail Tab .......................................................................................................................... 149
Aggregation of Performance Data .......................................................................................... 150
Chapter 10. Service Diagnostics ......................................................................................... 153
Supported MPLS Diagnostics ................................................................................................. 154
How to Initiate Diagnostics on a Service ................................................................................. 154
Diagnostic Via Service Right Click Menu ........................................................................... 154
LSP Diagnostic Via the Service Selector............................................................................ 155
Diagnostics View (Data Panel Tab) ........................................................................................ 156
Diagnostic Modal View ....................................................................................................... 157
Example Diagnostics ......................................................................................................... 157
Diagnostic History View .......................................................................................................... 161
Chapter 11. System Messages ............................................................................................ 163
Chapter 12. Managing Your Access to the System ............................................................ 165
User Roles ............................................................................................................................. 166
User Profile ............................................................................................................................ 167
User Security Policy ............................................................................................................... 169
User Access Procedures ........................................................................................................ 169
How to set User First Time Login ....................................................................................... 169
How to Reset User Forgot Password ................................................................................. 169
Appendix A: Glossary of Technical Terms .......................................................................... 171

xii May 2019 Aviat Networks

 Contents

Device Attributes .................................................................................................................... 171

L1 Link Attributes.................................................................................................................... 172
TE Link Attributes ................................................................................................................... 172
TE Tunnel Attributes ............................................................................................................... 173
LSP Link Tab Attributes .......................................................................................................... 175
LSP Tab Attributes ................................................................................................................. 175
PW Attributes ......................................................................................................................... 175
L2VPN Tab Attributes ............................................................................................................. 176
RT Link Tab Attributes ............................................................................................................ 177
L3VPN Tab Attributes ............................................................................................................. 177
SyncE Link Tab Attributes ...................................................................................................... 178
PTP Link Tab Attributes.......................................................................................................... 178
Appendix B: Functionality Provided by Product Modules .................................................. 181
Appendix C: Services Alarms Reference ............................................................................. 183
Appendix D: IETF and Cisco Terminology Comparison...................................................... 187

Aviat Networks May 2019 xiii

 Welcome to ProVision Plus

Chapter 1. Welcome to ProVision Plus

Welcome to the ProVision Plus User Guide. This guide provides you with the technical information
required to use ProVision Plus. This includes:
• ProVision Plus key concepts
• Getting started with ProVision Plus
• Network deployment including discovery via ProVision
• Network device access control
• Network topology visualization with graphical map, tree and tabular data views
• Network configuration views including managing discovered network configuration changes
• Network device configuration backup and restore operations
• Network event/alarm management including browser and alarm status indicators functionality
• Network performance management including resource performance and network health
• Service diagnostics functionality
• ProVision Plus system messages
• Managing your access to the system

Intended Audience
The information in this guide is intended for the following roles:

Role Brief Description

Network operator Provides read-only access to all network topology graphical and tabular
data views including the configuration details of devices and services,
together with full access to all event/alarm, configuration and
performance views to support proactive network health analysis and
troubleshooting.
Network engineer In addition to the network operator capabilities, provides the ability to
deploy network devices and physical container hierarchy (Regions,
Sites), set up communications with the network devices, manage
configuration changes discovered in the live network, perform
operations on network devices (e.g. backup the configuration), and
execute network service diagnostics.
A fuller definition of the user roles is provided in section User Roles.

What You Need to Know to Use ProVision Plus

Knowledge of the following is essential to be able to use ProVision Plus effectively and get the most
from using the product:
• Network management concepts, including fault, configuration, performance and security
management, and networking layer-based troubleshooting techniques.
• Basic microwave networking concepts.
• Carrier Ethernet (CE) networking concepts including VLAN services and clock synchronization
(Synchronous Ethernet and IEEE 1588v2 Precision Timing Protocol).
• IP/MPLS networking concepts including L2VPN services and PWs, L3VPN services and VRF
routing, LDP-signaled LSPs and Traffic Engineered LSP tunnels.

Additional Resources
The ProVision Plus Installation and Administration Guide (PN 260-668272-001) describes the
procedures and features associated with installing and administering the product.
Aviat Networks May 2019 15
Welcome to ProVision Plus

The ProVision Installation and Administration Guide (PN 614-330053-001) describes how to
configure ProVision which is used to provide network mediation to SNMP-based devices for
ProVision Plus.
The ProVision Plus Northbound Interface System Integration Guide (PN 260-668273-001)
describes how to integrate with external systems such as operation support system (OSS),
orchestrators, SDN super controllers, and custom SDN applications.

About ProVision Plus

The ProVision Plus platform is engineered to bring an unparalleled degree of visibility and efficiency
to the service management challenge.
Central to ProVision Plus’s philosophy is to present the network in a way that mirrors the human
cognitive model, to allow network engineering and operations staff to efficiently manage at a very
high level of abstraction.
• End-to-end services, such as VLANs, L2VPNs, and TE Tunnels, spanning multiple devices
are treated as first-class entities,
• Models the network as multiple interconnected layers of services,
• Intuitive UI to graphically visualize end-to-end services and relationships between layers,
• Fundamentally architected to enable network programmability, policies and automation, and
• A common infrastructure provides a unified set of essential platform capabilities.
ProVision Plus is a web-based system accessed via modern web browsers such as Google Chrome
and Microsoft Edge. No client application installation is required, minimizing deployment and
support cost.

Network Communication
Communication with the managed network takes place either directly with network devices, or via a
ProVision mediation system. In the current version of ProVision Plus, WTM 4000 devices are
managed directly using NETCONF / YANG communications. All other devices are managed
indirectly via the ProVision Northbound Interface (NBI).

Automatic Network Topology Construction

ProVision Plus dynamically discovers the topology of the network, by combining information from
every device in the network, and intelligently reconstructs an accurate and up-to-date network
topology for every supported layer. For example, IP/MPLS LSP, TE Tunnel, and VPN supported
layers.

Multi-Layer Topology Visualization

Through its unique and intuitive user interface, users can simultaneously visualize multiple layers of
Carrier Ethernet and IP/MPLS network. When a service is selected on the topology view, the
lower-layer services that support it are automatically highlighted. Through this and other
mechanisms users can easily navigate and discover the relationship between the layers.

Rapid Troubleshooting
Device events from one or more devices are analyzed, normalized and automatically correlated as
service alarms for each end-to-end service, such as TE Links, TE Tunnels, PWs and VPNs. The
service alarm state for each service is prominently displayed on the topology view and the data
panels to facilitate troubleshooting.

16 May 2019 Aviat Networks

 Welcome to ProVision Plus

The intuitive multi-layer topological navigation capability in combination with service alarms allow for
rapid visual root cause analysis. When the user selects an alarmed service in the topology view,
the lower-layer services are highlighted. By iteratively selecting on a lower-layer supporting service
with an alarmed state, the user can quickly identify the root cause.

Configuration Validation
Configuration changes to the network devices and IP/MPLS services are automatically detected.
The Baseline design provides a benchmark configuration of all devices and services, including (for
example) L1 links, TE Links, TE Tunnels and VPNs.
Any configuration change deviating from the Baseline design is visually highlighted and the details
identified.

Network Health Analysis

Users can analyze the performance of the network resources, and instantly identify degraded or
poorly performing traffic interfaces or devices. For example, RF interfaces with high unavailability,
Ethernet interfaces experiencing packet loss, or devices experiencing high temperature issues

Service Impact Analysis

Utilizing its knowledge of the complete network, ProVision Plus provides a powerful yet
simple-to-use visual service impact analysis capability. Complex questions such as which VPNs
will be affected where scheduled maintenance needs to be performed on a L1 link are answered
with a few mouse clicks.

Service Diagnostics
On-demand diagnostics provide the ability to quickly identify and troubleshoot L3VPN VRF routing,
TE Tunnel, and LSP services connectivity problems.

Network Troubleshooting With ProVision Plus

Efficient troubleshooting of problems in complex networks requires the ability to apply a number of
structured approaches. Although a single approach may be sufficient in simpler cases, more
complex issues typically require the trouble shooter to apply a variety of approaches to isolate and
resolve the problem.
The following structured approaches are made simple with ProVision Plus:
Table 1: Structured Network Troubleshooting Approaches

Approach Description
The ability to troubleshoot each layer independently, working either up or down to
Layer by layer the next layer, once a layer has been fully verified. This can also involve starting at
an interim layer.
Node by node (on the Fully verify all layers or a number of layers on a node, before moving onto the next
end-to-end path) node on the end-to-end path.
Often the configuration or state of a particular attribute should be identical across
Identify differences multiple devices or services in the network, and identifying differences can quickly
pinpoint the cause.
The ability to identify and analyze configuration changes to each network layer in
Analyze before and after
the live network.

Aviat Networks May 2019 17

Welcome to ProVision Plus

For complex networks such as those delivering Carrier Ethernet or MPLS VPN services, the ability
to discover, model and troubleshoot each network layer independently is fundamental to the above
approaches. The following sections, Carrier Ethernet Network Layer Modeling (on page 19) and
MPLS Network Layer Modeling (on page 20) provide an overview of the modelled layers.
ProVision Plus intelligently constructs an accurate model of the network through a set of
interconnected layers. This facilitates the ability to apply simple and consistent layer-based
management and troubleshooting practices.

18 May 2019 Aviat Networks

 Welcome to ProVision Plus

Carrier Ethernet Network Layer Modeling

The table below describes the interconnected Carrier Ethernet layers included within the IETF
standards-based data model that forms a core component of ProVision Plus.
Table 2: Carrier Ethernet Network Layers Modeled by ProVision Plus

Layer Description
VLAN VLAN services layer. This layer includes both Customer VLAN (C-VLAN) and Service VLAN
(S-VLAN) representation.
Reference: IEEE 802.1Q (Virtual Bridge Local Area Networks).
VLAN Link VLAN Link layer. This layer represents the VLAN topology as a set of VLAN Links, where each
indicates a physical link configured to carry one or more VLANs. This is determined by the
VLAN configuration of the device interfaces.
Reference: IEEE 802.1Q (Virtual Bridge Local Area Networks).
Note: When the VLAN Link layer is filtered to present a VLAN service, all configured
paths are presented, including the alternate paths that need to be resolved through
Spanning Tree or ERPS protocols in order to avoid packet loops in the network.
PTP Link PTP (Precision Timing Protocol) Link layer. This layer represents the PTP topology as a set of
PTP Links, where each indicates a PTP connection between the ports on adjacent devices.
Reference: IEEE 1588v2 (Precision Clock Synchronisation Protocol).
SyncE Link SyncE (Synchronous Ethernet) Link layer. This layer represents the SyncE topology as a set of
SyncE Links, where each indicates a SyncE connection between the ports on adjacent devices.
Reference: ITU G.8262/Y.1362 (Synchronous Ethernet).
Physical The physical topology layer, indicating the devices and their physical interconnecting L1 links
(radio or Ethernet cable connection).

Aviat Networks May 2019 19

Welcome to ProVision Plus

MPLS Network Layer Modeling

The figure and table below describe the interconnected MPLS layers included within the IETF
standards-based data model that forms a core component of ProVision Plus.
Figure 1: MPLS Network Layers Modeled by ProVision Plus

Table 3: MPLS Network Layers Modeled by ProVision Plus

Layer Description
L2VPN L2VPN services layer. This layer includes the Attachment Circuits (ACs) and their mapping to the
underlying PWs that deliver the services between the PE routers.
Reference: IETF RFC 4664 (Framework for L2VPNs).
There are two fundamentally different kinds of Layer 2 VPN service that a service provider could
offer to a customer; Virtual Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS).
• A VPWS is a VPN service that supplies an L2 point-to-point service.
• A VPLS is an L2 service that emulates LAN service across a Wide Area Network (WAN).
PW L2VPN PW (Pseudowire) layer. This presents the PWs, established through Targeted LDP
sessions between the terminating PE routers, over which L2VPN services are delivered.
For VPLS this includes the configured PW mesh, and for VPWS this includes the configured
point-to-point PW.
Reference: IETF RFC 4664 (Framework for L2VPNs).
A "Pseudowire" (PW) is a relation between two PE devices. Whereas an AC is used to carry a
frame from CE to PE, a PW is used to carry a frame between two PE devices.

20 May 2019 Aviat Networks

 Welcome to ProVision Plus

Layer Description
L3VPN L3VPN services layer. This layer includes the VRFs (virtual routing/forwarding instances) and the
configured Attachment Circuits (ACs) of each L3VPN.
Where vpnv4 route sharing is configured between VRFs (i.e. exported from one VRF and imported
into another), the VRFs are considered part of the same L3VPN.
Reference: IETF RFC 4364 (BGP/MPLS IP VPNs).
Consider a set of "sites" that are attached to a common network that we call "the backbone".
Now apply some policy to create a number of subsets of that set, and impose the following rule: two
sites may have IP interconnectivity over that backbone only if at least one of these subsets contains
them both.
These subsets are Virtual Private Networks (VPNs).
Two sites have IP connectivity over the common backbone only if there is some VPN that contains
them both.
RT Link L3VPN VRF RT (Route Target) Link layer. This layer presents the VRF routing topology as a set of
RT links, where each indicates the flow (export to import) of vpnv4 routes (associated with a
configured RT value) between two VRFs. Collectively the RT links for a L3VPN indicate the service
topology.
Reference: IETF RFC 4364 (BGP/MPLS IP VPNs).
A Route Target attribute can be thought of as identifying a set of sites (though it would be more
precise to think of it as identifying a set of VRFs) associating a particular Route Target attribute with
a route allows that route to be placed in the VRFs that are used for routing traffic that is received
from the corresponding sites.
TE Tunnel TE (traffic engineered) LSP Tunnels layer. This layer presents the configuration of the tunnels
together with the state of the associated RSVP-TE signaled tunnel LSPs.
Each tunnel comprises of one or more traffic engineered LSPs in either a 1:1 protected or a
non-protected configuration.
For each tunnel LSP, the ERO (Explicit Route Object) configuration and the RRO (Record Route
Object) end-to-end path state are modelled.
The RRO identifies the routers over which a TE Tunnel LSP has been signaled. This state
information is only available where RRO is enabled on the head-end PE routers.
As the RRO is discovered from the head-end PE router, this enables the model to capture the full
signaled end-to-end path of each tunnel LSP in the case where one or more of the other routers on
the path are either not supported or cannot be communicated with.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for LSP Tunnels).
A set of one or more Tunnel LSPs which carries a traffic trunk, i.e. a set of flows aggregated by their
service class and then placed on an LSP or set of LSPs.
TE Link TE (traffic engineered) Link layer. This layer presents the traffic engineering link layer topology of
the network, i.e. the set of configured TE Links in the MPLS network over which TE Tunnel LSPs
can be signaled. Each TE Tunnel LSP spans one or more TE Links.
Reference: IETF RFC 3630 (TE Extensions to OSPF).
The extensions provide a way of describing the traffic engineering topology (including bandwidth and
administrative constraints) and distributing this information.
For "global traffic engineering", a device can build a traffic engineering database, input a traffic
matrix and an optimization function, crunch on the information, and thus compute optimal or
near-optimal routing for the entire network.

Aviat Networks May 2019 21

Welcome to ProVision Plus

Layer Description
LSP LSP layer. This layer presents:
• LDP-signaled LSPs carrying VPN services, and
• traffic engineered (RSVP-TE signaled) TE Tunnel LSPs irrespective of whether they are
configured to carry VPN services.
Reference: IETF RFC 3031 (Multiprotocol Label Switching Architecture).
The path through one or more LSRs at one level of the hierarchy followed by packets in a particular
Forwarding Equivalence Class (FEC).
Reference: IETF RFC 5036 (LDP Specification).
LDP associates a Forwarding Equivalence Class (FEC) [RFC3031] with each LSP it creates.
The FEC associated with an LSP specifies which packets are "mapped" to that LSP. LSPs are
extended through a network as each LSR "splices" incoming labels for a FEC to the outgoing label
assigned to the next hop for the given FEC.
LSP Link LSP Link layer. This layer presents the point-to-point links between the PE and P routers over
which the LSPs presented in the LSP layer are delivered.
This includes links established through LDP and traffic engineering (RSVP-TE). Each TE Tunnel
LSP or LDP-signaled LSP spans one or more LSP Links.
The links are discovered through reading the label switching “cross connect” information from each
PE and P router in the network, hence all links are discovered irrespective of whether they were
signaled using LDP or RSVP-TE, or statically configured.
Reference: IETF RFC 3031 (Multiprotocol Label Switching Architecture).
The path through one or more LSRs at one level of the hierarchy followed by packets in a particular
Forwarding Equivalence Class (FEC).
Physical The physical topology layer, indicating the devices and their physical interconnecting L1 links (radio
or Ethernet cable connection).

22 May 2019 Aviat Networks

 Welcome to ProVision Plus

The following table describes the more complex connections, where a layer is supported by multiple
underlying layers.
Table 4: MPLS Network Inter Layer Connections

Inter Layer Connection Description

TE Tunnel supported by For a TE Tunnel, the TE Link and LSP layers are presented as supporting layers.
(LSP and TE Link) The TE Link layer presents the configuration attributes of the TE Link (e.g. Default
Metric) and the LSP layer compliments by presenting the state of the traffic carrying
LSPs.
The LSP layer indicates the state of the traffic engineered LSPs within the tunnel,
and the TE Link layer indicates the ERO path configuration together with the RRO
path state (where this has been enabled on the head-end router).

Aviat Networks May 2019 23

 Getting Started

Chapter 2. Getting Started

This section provides information on getting started with ProVision Plus.

Installing and Running the Product

Please refer to the ProVision Plus Installation and Administration Guide for the instructions on
installing and running the product. This guide includes the following information:
• System requirements, including minimum hardware, supported operating systems and
web-browsers.
• ProVision Plus Server application installation procedures.
• Requesting and loading product licenses.
• Configuration of the server and networking.
• Network ports usage for establishing communication with a ProVision network mediation
server, and connecting ProVision Plus client sessions.

System Administration
Please refer to the ProVision Plus Installation and Administration Guide for the instructions on
system administration. This guide includes the following information:
• Role based management including a description of the supported roles.
• User management functionality and the associated procedures for managing users.
• Configuration of user access security policy.
• Database management functionality including the associated procedures for backing up the
system and restoring from backup.
• A description of the available ProVision Plus product license options, including how to request,
load and manage your license.

Product License Options

See section License Management in the ProVision Plus Installation and Administration Guide for a
description of the following licensing topics.
• Available licensed Product Modules
• View the details of the current license
• How to create a license request
• How to install a new license
• Licensing messages reported to the user

Aviat Networks May 2019 25

Getting Started

Product Modules and Supported Device Types

The functionality provided by ProVision Plus for a specific device type is dependent on the licensed
product modules used to manage the device type. The following table indicates the available
product modules together with the device types supported by each.
Table 5: Product Modules and Supported Device Types

Product Module Supported Device Types

EM Fault & Performance WTM 4100, WTM 4200, WTM 4500, WTM 4500T
EM Integration For Provides an EM fault and performance management capability for
ProVision Eclipse and CTR 8540/83xx devices.
Provides a fault management, with very limited configuration
management, capability for all other device types supported by
ProVision.
Carrier Ethernet Fault & WTM 4100, WTM 4200, WTM 4500, WTM 4500T
Performance
Note: This product module is dependent on (i.e. requires) the EM
Fault & Performance product module.
IP/MPLS Fault CTR 8540
Note: For CTR 8540 this product module is dependent on (i.e.
requires) the EM Integration For ProVision product module.
NBI All devices supported by ProVision Plus.
See Functionality Provided by Product Modules (on page 181) for a simple matrix indicating the
functionality provided for each product module.

26 May 2019 Aviat Networks

 Network Deployment

Chapter 3. Network Deployment

This section describes the features available for deploying devices, physical links and the physical
container hierarchy, including the ability to make subsequent changes. In summary the following
capabilities are provided.
• Manual deployment of directly managed devices and their physical links.
• Manual deployment of the physical container hierarchy.
• Automated import and deployment of devices indirectly managed via ProVision and their
physical links.
• Automated import and deployment of the physical container hierarchy from ProVision.
This information is stored in the database, enabling the user to analyze the associated data
irrespective of the communication status with the live network or ProVision mediation server.
This section topics include:
• Communication with Devices (on page 28)
• Manual Deployment using Deploy Object (on page 28)
• Automated Deployment Via Provision System (on page 31)
• Configuring SNMP Notification Initiated Event Collection (on page 33)
• Making Changes to Deployment (on page 33)
• Manual Deployment of Physical Links (on page 34)
• Baselining of Network Deployment Changes (on page 35)

Aviat Networks May 2019 27

Network Deployment

Communication with Devices

ProVision Plus communicates with each network device either directly or indirectly via a ProVision
mediation system. In the current version, devices supporting the NETCONF protocol are managed
directly, and devices supporting SNMP are managed indirectly via the Northbound Interface (NBI) of
a ProVision system.
Devices managed indirectly via a ProVision mediation system are firstly deployed in ProVision, as
the NBI provides a read-only capability. Import and deployment into ProVision Plus then takes
place automatically, once the devices are discovered via the ProVision NBI.
As ProVision Plus provides richer management support (than ProVision) for WTM 4000 devices,
when imported and deployed via ProVision, ProVision Plus automatically starts managing these
devices directly.
NETCONF based event collection from devices can be enhanced to provide for quicker detection of
new events through SNMP notifications. See section Configuring SNMP Notification Initiated
Event Collection (on page 33) for details.

Note: LICENSING: ProVision Plus automatically starts managing imported WTM 4000
devices directly only where the EM Fault & Performance product module (for directly
managed devices) is licensed. Where this product module is not licensed, the WTM 4000
devices are discarded on import, i.e. are nether directly nor indirectly managed in ProVision
Plus.
Note: WTM 4000 devices imported from ProVision automatically become directly managed
in ProVision Plus. Hence they become directly managed by both ProVision and ProVision
Plus. As it is not desirable to have both systems managing the same device, in this situation
it’s recommended that the WTM 4000 devices be deleted in ProVision following successful
import and deployment into ProVision Plus.

Manual Deployment using Deploy Object

Devices can be directly managed in ProVision Plus when deployed using the Deploy Object feature.
This allows the user to manually deploy devices and the physical container hierarchy.
The Deploy Object dialog provides the user with the following capabilities:
• Manually deploy Region and Site objects in the physical container hierarchy.
• Manually deploy device objects into the physical container hierarchy.
• Enter the communication and authentication parameters associated with each device object.
• Manually deploy device and container objects individually or in bulk.
Note: LICENSING: The Deploy Object feature is only available where the EM Fault &
Performance product module (for directly managed devices) is licensed.
Note: USER ROLE: A user must have Engineer role access in order to access the Deploy
Object feature.

28 May 2019 Aviat Networks

 Network Deployment

Container Deployment
The following restrictions are imposed when deploying Region or Site containers.
• Region containers can be deployed into Physical Root or another Region container.
• Site containers can be deployed into a Region or another Site container.
The following figure presents an example Deploy Object view, where a Region container is
deployed into Physical Root.
Figure 2: Example Deploy Region Object

The following figure presents an example Deploy Object view, where multiple Site containers are
deployed into Region ‘California”.
Figure 3: Example Deploy Multiple Site Objects

Deployed Containers are presented in the Devices Tree (section Devices Tree (on page 82)).

Aviat Networks May 2019 29

Network Deployment

Device Deployment
Devices can be deployed into Physical Root, or into a Region or Site container.
The following figure presents an example Deploy Object view, where a single WTM 4200 device
object is deployed into Site ‘Upper Hutt’.
Figure 4: Example Deploy Device Object

The following table provides a description of the parameters to be provided when deploying a
device object.
Table 6: Device Deployment Parameters

Parameter Description
Object Name Name by which the device is represented in ProVision Plus.
Management IP Address IP address used by ProVision Plus to communicate with the device.
NETCONF Authentication Authentication credentials (username, password) used by ProVision
Credentials Plus to communicate with the device using the NETCONF protocol.
Once devices have been deployed, subsequent changes to their deployment parameters can be
made through the following features.
• Object Name and Management IP Address: Direct Device Management view (see section
Direct Device Management (on page 100)).
• NETCONF Authentication Credentials: Direct Device Access Control view (see section Direct
Device Access Control (on page 38)).
Deployed Devices are presented in the Devices Tree (section Devices Tree (on page 82)) and
Topology Map (section Topology Map (on page 45)) and Data Panel (section Data Panel (on page
78)) views.

30 May 2019 Aviat Networks

 Network Deployment

Access to Deploy Objects

The Deploy Object dialog is accessed through the Deploy right-click menu option associated with
the Physical Root or a Container object on the Devices Tree. This allows the user to deploy the
new objects into an existing container.

Automated Deployment via ProVision System

In addition to supporting devices through direct management, devices can also be managed
indirectly via a ProVision system NBI (Northbound Interface). This provides a limited read-only
management capability for all device types supported by ProVision, including Eclipse and CTR
8540/83xx.
Section ProVision Network Access Control in the ProVision Plus Installation and Administration
Guide describes how to configure communications between ProVision Plus and ProVision, using
ProVision’s NBI.
Once connection to a ProVision system is established, the devices and physical container hierarchy
in ProVision are automatically imported and deployed into ProVision Plus. This behavior is
described in detail in section Container Deployment below.

Note: LICENSING: The ability to connect a ProVision system to ProVision Plus requires the
EM Integration For ProVision product module.
Note: USER ROLE: A user must have Engineer role access in order to connect a ProVision
system to ProVision Plus .

Topology Import Details

The network topology deployed in ProVision (including devices, physical links and physical
container hierarchy), is automatically imported and deployed into ProVision Plus. This occurs
when the initial connection between the server applications is established, and as subsequent
changes to the topology occur.
In order to keep both systems aligned and simplify management for the user, the imported devices,
physical links, containers and hierarchy of the imported containers cannot be changed (i.e.
renamed, reparented or deleted) in ProVision Plus. Such changes can only be made in ProVision.
The exception to this behavior is for WTM 4000 devices and the associated physical links imported
and deployed from ProVision, as ProVision Plus automatically starts managing these devices
directly (see section Communication with Devices (on page 28)).

Note: WTM 4000 devices imported from ProVision automatically become directly managed
in ProVision Plus. Hence they become directly managed by both ProVision and ProVision
Plus. As it is not desirable to have both systems managing the same device, in this situation
it’s recommended that the WTM 4000 devices be deleted in ProVision following successful
import and deployment into ProVision Plus.
Note: Devices indirectly managed via ProVision, and containers imported from ProVision,
cannot be manually renamed, re-parented or deleted by the ProVision Plus user. These
changes can only be performed in ProVision, after which the changes are automatically
reflected in ProVision Plus.

Aviat Networks May 2019 31

Network Deployment

The following table identifies the detailed behavior of ProVision Plus where changes are made to
the devices and container hierarchy in ProVision.
Table 7: Topology Import Behavior Associated with ProVision Operations

ProVision Operation Behavior

ProVision NBI connected The container hierarchy and devices are imported and deployed
(configured in ProVision into ProVision Plus. See section Handling of Device and
Networks view) Container Name Conflicts (on page 33) for handling of the
situation where a container or device name already exists in
ProVision Plus .
ProVision NBI deleted (removed Where the user deletes the ProVision NBI connection by
from ProVision Networks view) removing the configuration from the ProVision Networks view,
the container hierarchy and the devices are deleted from
ProVision Plus. See the Delete Device and Delete Container
descriptions below, for details on the associated behavior. This
can only be performed by an engineer user.
Warning: This operation also deletes the associated
historical data for the devices. It’s strongly recommended
that a database backup be performed beforehand.
Add device Device is imported and deployed into the same container as
ProVision. See section Handling of Device and Container
Name Conflicts (on page 33) for handling of the situation where
the device name already exists in ProVision Plus.
Add container Container is imported and deployed into the same parent
container as ProVision. See section Handling of Device and
Container Name Conflicts (on page 33) for handling of the
situation where the container name already exists in ProVision
Plus.
Rename device If indirectly managed via ProVision, the device is renamed. Else
no action is taken. See section Handling of Device and
Container Name Conflicts (on page 33) for handling of the
situation where the new device name already exists in ProVision
Plus.
Rename container Container is renamed. See section Handling of Device and
Container Name Conflicts (on page 33) for handling of the
situation where the new container name already exists in
ProVision Plus.
Reparent device If indirectly managed via ProVision, the device is reparented into
the same container as ProVision. Else no action is taken.
Reparent container Container and any child containers and devices are reparented
into the same parent container as ProVision. This includes any
child containers manually deployed in ProVision Plus, or child
devices that are directly managed in ProVision Plus.
Delete device If indirectly managed via ProVision, the device is deleted. Else
no action is taken.
Delete container Container is deleted.
Note: When deleting a container object in ProVision and
importing the change, any manually deployed child
containers or directly managed devices within the same
container in ProVision Plus are moved to Physical Root.

32 May 2019 Aviat Networks

 Network Deployment

Handling of Device and Container Name Conflicts

When adding or renaming a device or container object in ProVision, there is a possibility that the
new name is already assigned to an existing device or container in ProVision Plus. When this
occurs, ProVision Plus proceeds with the import and deployment, and it’s then left to the user to
identify and resolve the conflicting names. This can be achieved by taking one of the following
actions:
• Rename the newly imported object with the conflicting name in ProVision. When the object is
automatically imported again, the conflict is resolved.
• Rename the directly managed device or manually deployed container object in ProVision
Plus. Once completed, the conflict is resolved.

Configuring SNMP Notification Initiated Event Collection

ProVision Plus collects events from managed devices by periodically polling each device every 5
minutes using the NETCONF protocol.
To provide for quick detection of new events, SNMP notification-based event collection is also
supported by ProVision Plus.
WTM 4000 radios support event change SNMP notifications, whilst providing for management via
the NETCONF protocol. This capability is configured on the Simple Network Management page on
the WTM 4000 GUI. The following table indicates how to configure sending of SNMP notifications
to the ProVision Plus server.
Table 8: WTM 4000 GUI SNMP Notification Parameters

Parameter Description
IP Address IP address of the ProVision Plus server. See section How to Configure
SNMP Port of the ProVision Plus Installation and Administration Guide
for details.
Port UDP port on which ProVision Plus receives SNMP notifications. This
must match the value configured on ProVision Plus. See section How
to Configure SNMP Port of the Installation and Administration Guide for
details.
Type SNMP protocol version. Currently ProVision Plus supports SNMP v2c
only.

Making Changes to Deployment

Directly managed devices, and containers deployed by the ProVision Plus user, can be renamed,
reparented or deleted by using the right-click menus associated with device and container objects.

Note: Devices indirectly managed via ProVision, and containers imported from ProVision,
cannot be manually renamed, reparented or deleted by the ProVision Plus user. These
changes can only be performed in ProVision, after which the changes are automatically
reflected in ProVision Plus.
Note: USER ROLE: A user must have Engineer role access in order to rename, reparent or
delete devices and containers.

Rename Device or Container

Device and container objects can be renamed through the Rename Object dialog. An example is
provided in the figure below.

Aviat Networks May 2019 33

Network Deployment

Figure 5: Example Rename Object Dialog

This is accessed through the Rename right-click menu option associated with device and container
objects in the Devices Tree, Direct Device Management, Topology Map, and Data Panel views.
Device objects can also be renamed directly in the Direct Device Management view, as described in
section Direct Device Management (on page 100).

Reparent Device or Container

Device and container objects can be reparented through the Devices Tree view.
In summary, reparenting is performed by unlocking the Device Tree, drag-and-dropping the device
or container objects to their new places in the container hierarchy, and then relocking the tree.
See section Devices Tree (on page 82) for details on the Devices Tree, and section Tree Context
Selector Controls (on page 84) for details on the reparenting controls.

Delete Device or Container

Device and container objects can be deleted through the Delete Object dialog. An example is
provided in the figure below.
Figure 6: Example Container Delete Object Dialog

Warning: Deleting a device results in all data associated with the device being deleted from
the database. This includes all historical event and performance data. This data cannot be
recovered, other than by restoring an earlier database backup generated prior to device
deletion.
This is accessed through the Delete right-click menu option associated with device and container
objects in the Devices Tree, Direct Device Management, Topology Map, and Data Panel views.

Manual Deployment of Physical Links

Physical links between directly managed devices can be deployed through the Devices Tree view.
In summary, link deployment is performed by selecting the 2 devices in the tree, selecting the
Create Link menu option associated with one of the device objects, and then selecting the interface
endpoints in the Create Link dialog.
An example Create Link dialog is provided in the figure below.

34 May 2019 Aviat Networks

 Network Deployment

Figure 7: Example Create Link Dialog

Note: Physical links between WTM 4000, CTR 8540/83xx and Eclipse devices can be
manually deployed. Physical links between WTM 4000 devices are automatically
discovered.
Note: USER ROLE: A user must have Engineer role access in order to access the Create
Link dialog.

Baselining of Network Deployment Changes

The Model Status Indicators are used to reflect changes to the physical container hierarchy, in the
same way they reflect changes to the devices and services in the live network. Hence the
indicators are updated when any user makes a change in ProVision Plus, or a change is made by a
ProVision user and automatically imported into ProVision Plus.
See section Live Network Configuration Change Indicators (on page 117) for details on the
indicators and section Promoting Live Network Changes to Baseline (on page 118) for details on
promoting the changes to the Baseline design.

Aviat Networks May 2019 35

 Device Access Control

Chapter 4. Device Access Control

This section describes the capabilities provided for establishing and managing communications with
both directly managed devices, and devices indirectly managed via ProVision.
This section topics include:
• Direct Device Access Control (on page 38)
• ProVision Network Access Control

Aviat Networks May 2019 37

Device Access Control

Direct Device Access Control

The Direct Device Access Control view provides the user with the following capabilities:
• Tabular view presenting the access control settings for all directly managed devices.
• Configure the communication authentication credentials for each device.
• Analyze the devices using sort and search controls.
• Quick access to other device management capabilities (through the right-click menu
associated with each device object).
Note: USER ROLE: A user must have Engineer role access in order to configure the Direct
Device Access Control settings.
Figure 8: Example Direct Device Access Control

Access to Direct Device Access Control View

The Direct Device Management view is accessed through the Admin > Direct Device Access
Control menu.

Direct Device Access Control View Controls

The following table identifies the controls available in the Direct Device Access Control view.
Table 9: Direct Device Access Control View Controls

Attribute Icon Description

Preferences Menu Allows the user to select the parameters to be presented in the
Direct Device Access Control view, together with the ability to
export the data. See the table below for details.
Search A text search can be applied to the tabular view, resulting in only
those rows containing a match being displayed.
Column Sort Sort the tabular view by mouse clicking on a column heading.

NETCONF Indicates the NETCONF authentication username, and provides

Authentication the ability to open the NETCONF Authentication Credentials edit
Credentials Edit Button dialog and edit the username and password settings.
Row navigation menu Provides access to the device management capabilities and
views associated with a particular device row, through the mouse
<right-click> menu.
Table 10: Direct Device Access Control Preferences Menu Options

Control Function
Select Enable/disable the ability to compare configuration and state of
selected devices through a specialized variant of the Detail view,
known as the Comparison view. See section Comparison View
(on page 88) for further information.

38 May 2019 Aviat Networks

 Device Access Control

Control Function
Parameter Selection Provides the user with the ability to select the parameters to be
presented in the tabular view for analysis. See section Direct
Device ManagementView Attributes (on page 101) below for
details.
Export to CSV / JSON / PDF Export the access control settings for all directly managed devices
in CSV, JSON or PDF output format.

Direct Device Access Control View Attributes

The following table identifies the parameters presented in the Direct Device Access Control view.
Table 11: Direct Device Access Control Attributes

Control Function
Live (Model Status) Indicator warning when a change is detected in the Live network
that’s not in the Baseline design, i.e. the Baseline design and Live
configuration for the device differ.
For example, symbol indicates that a new device or service has
been detected in the Live network. See section Live Network
Configuration Change Indicators (on page 117) for a definition of
the supported Model Status indicators.
Name Name of the device that has been configured on ProVision Plus.
Type Device type, e.g. WTM 4100, CTR 8540, etc.
NETCONF Authentication Indicates the NETCONF authentication username, and provides the
Credentials ability to open the NETCONF Authentication Credentials dialog to
make changes.

ProVision Network Access Control

The ProVision Network Access Control view provides the user with the ability to configure and
manage communications with a ProVision system through ProVision’s NBI (Northbound Interface).
This capability enables ProVision Plus to indirectly manage the devices being managed by
ProVision. See sections Communication with Devices (on page 28) and Automated
Deployment via ProVision System (on page 31) for further details.
See section ProVision Network Access Control in the Installation and Administration Guide for
details.

Note: USER ROLE: A user must have Engineer role access in order to configure the
ProVision Network Access Control settings.

Aviat Networks May 2019 39

 Multi layer Network Topology Visualization

Chapter 5. Multi layer Network Topology

Visualization
ProVision Plus intelligently constructs an accurate and up-to-date network topology for each
supported networking layer.
For Carrier Ethernet networks this includes VLAN and clock synchronisation layers, down to the
underlying physical wireless topology.
For complex IP/MPLS networks this includes VPN services down through the supporting end-to-end
PWs, LDP-signaled or traffic engineered LSPs, to the underlying physical wireless topology.
LSP end-to-end paths, including the full RRO for TE Tunnel LSPs, are dynamically updated in
near-real time.
The multi-layer network topology visualization capabilities provide a unique and intuitive user
interface, allowing the user to simultaneously visualize the layers, and easily navigate between the
interconnected supporting services at each layer.
This powerful capability readily facilitates service configuration validation, impact analysis, and
layer-based troubleshooting.
This section topics include:
• Overview of Topology View (on page 42)
• Topology Map (on page 45)
• Data Panel (on page 78)
• Tree Context Selector (on page 82)
• Detail View (on page 86)
• Topology Filtering (on page 89)

Aviat Networks May 2019 41

Multi layer Network Topology Visualization

Overview of Topology View

Complementary Views
The network topology is presented through a number of complementary views:
• Graphical map view.
• Tabular view presenting a summary of the devices and end-to-end services.
• Tabular view presenting configuration and state detail for a selected device or end-to-end
service.
To access the topology view, select Topology in the Main Menu (together with a layer that you wish
to view).
The four panes presented when working with network topology views are as follows:
• Tree Context Selector.
• Topology Map.
• Data Panel.
• Detail modal view.
In addition, the Baseline vs Live Selector determines whether the Baseline design or a combined
view with Live network configuration and state is presented in the Topology Map, Data Panel and
Detail panes.
The figure below presents a simple topology view example, indicating L2VPN services together with
the underlying Physical layer (devices and L1 Link connections).
Figure 9: Topology View Panes and Baseline vs Live Selector

Table 12: Topology View Panes and Baseline vs Live Selector

Pane / Selector Function

Tree Context Selector Presents the network topology in a tree format and provides the ability
to filter the information presented in the Topology Map and Data
Panel. See section Tree Context Selector (on page 82) below for
details.

42 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Pane / Selector Function

Topology Map Provides a graph view of the network topology, with the ability to view
multi-layers and overlay with supporting information. See Topology
Map (on page 45) section below for details.
Data Panel Presents a summary of the network topology configuration and state in
a tabular format. See section Data Panel (on page 78) below for
details.
Detail Presents the configuration and state for a single selected device or
service in a tabular format. See section Detail View (on page 86)
below for details.
Access to the Detail modal view is available from the right-click menu
associated with each device and service object presented in the Tree
Context Selector, Topology Map and Data Panel panes.
Baseline vs Live Selector Determines whether the Baseline design or a combined view with Live
network configuration and state is presented in the Topology Map,
Data Panel and Detail panes. See section Baseline vs Live Selector
(on page 43) below for details.

Baseline vs Live Selector

Using the Baseline vs Live Selector, the user can select whether to view “Live + Baseline” or
“Baseline” information in the topology view.
“Live + Baseline” presents a combined view of the Live network configuration and state, together
with discovered configuration differences with the Baseline design. This selection provides the user
with visibility of configuration and state changes to the Live network devices and end-to-end
services.
“Baseline” presents only the Baseline design configuration.

Note: As alarms convey state information, the alarm indicators provided in the Tree Context
Selector, Topology Map and Data panel are only available in the “Live + Baseline” topology
view.
Note: The summary Network Devices and Network Services Alarm Indicators in the Menu /
System Status Bar are always available, irrespective of the Baseline vs Live Selector setting.
See section Baseline / Live Selection (on page 116) for further details on the information
presented by these two options.

Aviat Networks May 2019 43

Multi layer Network Topology Visualization

Topology View Alarm Status Indicators

Alarm Status indicators are provided on the Topology Map, Data Panel and Tree Context Selector
panes for each device and service. Each indicator identifies the highest severity for the currently
active alarms for a specific device or service. An example is provided in the figure below. See
section Alarm Status Indicators (on page 131) for details.
Figure 10: Example Alarm Status Indicators

Tree Context Selector: Data Panel: Topology Map:

Topology Discovery
Discovery of the network topology, together with devices and services configuration and state
information, takes place automatically. This includes initial discovery and subsequent changes to
configuration and state.
For indirectly managed devices, the information is discovered via the ProVision NBI (Northbound
Interface), and also includes the physical deployment tree hierarchy defined in ProVision.
For further details, see section Communication with Devices (on page 28) on communication with
directly and indirectly managed devices, and section Automated Deployment via ProVision
System (on page 31) on automated topology import from ProVision NBI.
The following table provides additional details on the discovery of this information.
Table 13: Topology Discovery Details

Type of update Description

Device When a new device is directly deployed in ProVision Plus, the configuration and state
information is automatically discovered from the device once communication is
established.
When a new device is deployed in the ProVision mediation system, the configuration
and state information is automatically discovered through the ProVision NBI.
Device configuration Configuration changes to the devices in the Live network are detected through the
device configuration change notifications and polling mechanism described in section
Monitoring Live Network for Configuration Changes.
Warning: CTR 8540 devices only generate configuration change syslog
notifications when the changes are saved (persisted) on the device. In the case
where changes are not saved, there will be a delay in discovery until the next
background configuration collection poll occurs. It’s therefore important to save
changes to device configuration as soon as the changes are complete.
Note: WTM 4000 devices do not generate configuration change notifications at
this stage. Therefore changes are automatically detected only through polling
(once per hour).

44 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Type of update Description

Service configuration The services (e.g. L3VPN or L1 Link) and their configuration are derived by ProVision
Plus from the discovered device configuration information.
When ProVision Plus detects changes to a device configuration, or the addition or
deletion of a device, it automatically correlates the changes to the services and updates
the configuration of the services in the data model.
Service supporting Discovery of the supporting layer for each service (e.g. the L1 Link(s) supporting a TE
layer Link), is automatically derived by ProVision Plus from the discovered configuration
and/or state information (dependent on the specific layer), and captured in the data
model.
Note: Where LSPs are signaled using LDP, due to the dynamic behavior the
LSP Links forming the segments of an active LSP can only be established
through tracing the complete LSP end-to-end path.
Note: As CTR currently doesn’t provide a notification when there’s a change to
an LDP-signaled LSP (e.g. creation or deletion) or a change to the LSP
end-to-end path (i.e. the LSP Links that form the path segments), there will be a
delay in discovery (and tracing of the path) until the next 6-hourly background
configuration collection poll occurs. This makes it infeasible for changes to be
automatically quickly reflected in ProVision Plus. The interim workaround is to
manually initiate a configuration discovery of the devices from the ProVision
mediation system. ProVision then pushes the discovered up to date information
to ProVision Plus.
Device Tree Context Changes to the physical topology tree in ProVision, such as re-parenting of a device
Selector (i.e. moving the device to a different container object), are automatically pushed to
ProVision Plus. See section Automated Deployment via ProVision System (on
page 31) for details.

Topology Map
The Topology Map provides the ability to graphically visualize the end-to-end services at each
networking layer, together with the dependency relationships between the layers.
The figure below highlights the main controls available for selecting the network topology to be
visualized on the map, through an example IP/MPLS network. The control types are as follows:
• Map Controls.
• Layers Selector.
• Topology Filter.
Note: LICENSING: IP/MPLS services are only presented in the Topology Map where the
IP/MPLS Fault product module is licensed.
Note: LICENSING: Carrier Ethernet services are only presented in the Topology Map where
the CE Fault & Performance module is licensed.

Aviat Networks May 2019 45

Multi layer Network Topology Visualization

Figure 11: Topology Map Main Controls

Table 14: Topology Map Main Controls

Control Type Function

Map Controls The Map Controls provide the ability to configure the Topology Map. See
section Map Controls (on page 47) for details.
Layers Selector The Layers Selector provides the ability to display one or more networking
layers in the Topology Map and Data Panel. See section Layers Selector
(on page 50) for details.
Layers Filter The Layers Filter (contained in the Topology Map Detail / Key) reflects the
layers currently presented in the Topology Map and Data Panel. See
section Detail / Key Indicators (on page 77) for details.
An example network with VLAN services is presented in the figure below.
Figure 12: Example VLAN Topology Map

An example network with clock synchronisation services is presented in the figure below.

46 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 13: Example SyncE Topology Map

Map Controls
A set of map controls provide the ability to configure the Topology Map networking layers, managed
objects, and graphical format.
Figure 14: Topology Map Controls

Table 15: Topology Map Controls

Control Icon Function

Select an object - Select an object on the map by clicking on a device or end-to-end
service object.
Zoom in and - Use the mouse scroll wheel to zoom in and out on the topology map.
out
Pan - Use the mouse <left-click> and <drag> controls to pan the topology
map.
Layers The Layers button enables the Layer Selector control, providing you
with the ability to select one of more networking layers to be
presented on the Topology Map and Data Panel. See section
Layers Selector (on page 50) for details.
Zoom to fit Click the Zoom to fit button to automatically zoom and center the
map, such that the complete network topology (for the selected
layers) is visible on the map.
Lock/Unlock The Lock/Unlock button toggles the map coordinates lock on and
Coordinates off. See section Map Coordinates (on page 72) for details.
Coordinate The Coordinate Mode drop-down menu provides the ability to
Modes configure the positioning of the node objects on the map. See
section Map Coordinates (on page 72) for details.
Overlay The Overlay drop-down menu provides the ability to overlay the
device and end-to-end service objects on the map with specific
configuration and/or state information. See section Overlay Data
and Auto Update for details.

Aviat Networks May 2019 47

Multi layer Network Topology Visualization

Control Icon Function

Refresh The Refresh button provides the ability to update the topology view
(Map, Data Panel and Context Selector tree) on the client with
discovered changes to the network topology.
The button has two modes of operation, Manual Update and Auto
Update. See section Overlay Data and Auto Update for details on
how to select the required mode.
• Manual Update – In this mode the Refresh button is white, and
turns Orange and rotates to alert the user when topology
changes have been detected. Pressing the rotating button
results in the changes being applied to the topology view.
• Auto Update – In this mode the Refresh button is Green. When
topology changes have been detected, the button rotates and the
changes are automatically applied to the topology view.

48 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Map Object Right-Click Menu Navigation

Additional information and functions associated with each object presented on the topology view
can be accessed via the right-click menu.
Figure 15: Map Object Right-click Menu Options

Table 16: Map Object Right-click Menu

Menu option Description

Detail Opens a Detail window presenting configuration and state details for the
selected device or service object. See section Detail View (on page 86) for
details.
Events Opens an Active Events window presenting the currently active events for the
selected device or service object. See section Event Browser (on page 125)
for details.
Performance Opens the Resource Performance view for a selected device object. See
section Resource Performance (on page 136) for details.
Discover Re-discovers the configuration for a selected directly managed device. For
Configuration indirectly managed devices, this capability is only available through ProVision.
Launch Web Portal Opens the web-based device craft tool on a new browser tab for a selected
device object.
Locate Selects the device or service object as the focus, and automatically zooms and
centers the object on the map.
Delete Presents the user with the Delete Object dialog, allowing the device object to
be deleted. See section Making Changes to Deployment (on page 33) for
details.

Aviat Networks May 2019 49

Multi layer Network Topology Visualization

Menu option Description

Rename Presents the user with the Rename Object dialog, allowing the device name to
be changed. See section Making Changes to Deployment (on page 33) for
details.
Add to Service Adds the selected device to the Service Selector (see section How to Initiate
Selector Diagnostics on a Service (on page 154)), allowing the user to quickly
navigate and execute supported Service Diagnostics.
Note: Service Diagnostics are supported for CTR 8540 only at this
stage.
Filter Adds the selected device or service object to the topology filter and
immediately applies the filter to the topology view (Topology Map and Data
Panel). See section Topology Filtering (on page 89) for details.
Show in Data Panel Highlights the selected device or service object in the Data Panel, and makes it
the selected focus.
Bundle / Unbundle Bundle or Unbundle the selected service link object.
Links By default multiple service link objects of the same type, with the same source
and destination termination points, are presented as a single Bundled Link
object. See section Service Links Bundling (on page 61) for further details.
Note: Where accessing the right-click menu associated with a Bundled Link object (see
section Service Links Bundling (on page 61) for details), the list of service links within the
bundle is presented, from which the above menu options can then be accessed.

Layers Selector
The Layers Selector provides the ability to display one or more networking layers on the Topology
Map and Data Panel. Through this control you can display any combination of the supported
layers.
When a layer is enabled, the end-to-end services for that layer together with the specific devices
supporting that layer are presented. For example, when only enabling the L2VPN layer, the L2VPN
services and the devices that provide an access point to the VPN services are presented. And
when only enabling the TE Tunnel layer, the TE Tunnel services and the devices that terminate the
TE Tunnels are presented.

Note: Unless the Physical layer is enabled, only the devices associated with the enabled
services layers are presented.
Note: LICENSING: IP/MPLS layers are only presented in the Layer Selector where the
IP/MPLS Fault product module is licensed.
Note: LICENSING: Carrier Ethernet (CE) layers are only presented in the Layer Selector
where the CE Fault & Performance product module is licensed.
The example figure below indicates selection of VLAN and Physical layers.

50 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 16: Layers Selector

Table 17: Layers Selector Control

Control Function
Include the layer in the Topology Map and Data Panel.
Exclude the layer from the Topology Map and Data Panel.
The following table provides a description of the layers available for selection. See section MPLS
Network Layer Modeling (on page 20) for further details.
Table 18: Topology Map Layers Available for Selection

Layer Icon Description

L2VPN L2VPN VPLS and VPWS services.
This includes the Attachment Circuits (ACs) and their mapping to the
underlying PWs that deliver the services between the PE routers.
PW PWs established through Targeted LDP sessions between the terminating PE
routers, over which the L2VPN services are delivered.
For VPLS this includes the configured PW mesh, and for VPWS this includes
the configured point-to-point PW.
L3VPN L3VPN services.
This includes the VRFs (virtual routing/forwarding instances) and the
configured Attachment Circuits (ACs) of each L3VPN.
Where vpnv4 route sharing is configured between VRFs (i.e. exported from
one VRF and imported into another), the VRFs are considered part of the
same L3VPN.
RT Link L3VPN VRF RT (Route Target) Link layer.
This presents the VRF routing topology as a set of RT links, where each link
indicates the flow (export to import) of vpnv4 routes (associated with a
configured RT value) between two VRFs.
Collectively the RT links for a L3VPN indicate the service topology.

Aviat Networks May 2019 51

Multi layer Network Topology Visualization

Layer Icon Description

TE Tunnel LSP layer for TE (traffic engineered) LSP Tunnels.
This presents the LSP tunnels and associated RSVP-TE signaled LSPs
between terminating PE routers, over which the PWs and L2VPN services are
delivered.
Enabling this layer provides the ability to visualize the following information:
• TE Tunnel protection configuration and state information, including Primary
Working and Primary Protecting LSP configuration, and active LSP state.
• ERO (Explicit Route Object) configuration for each TE Tunnel LSP.
• RRO (Record Route Object) state for each TE Tunnel LSP, including the
current active path taken. This is only available where RRO has been
enabled on the head-end PE router.
Note: As indicated in section MPLS Network Layer Modeling (on
page 20), the TE Tunnel layer is supported by both the LSP and TE Link
layers described below
TE Link TE (traffic engineered) Link layer.
This presents the traffic engineering link layer topology of the network, i.e. the
set of configured TE Links in the MPLS network over which TE Tunnel LSPs
can be signaled.
Enabling this layer provides the ability to visualize the following information:
• TE Link configuration and state information.
• When filtered through selection of a TE Tunnel, the TE Link hops that form
the end-to-end path of each tunnel LSP.
LSP LSP layer.
This presents:
1. LDP-signaled LSPs carrying VPN services, and
2. traffic engineered (RSVP-TE signaled) TE Tunnel LSPs irrespective of
whether they’re configured to carry VPN services.
Enabling this layer provides the ability to visualize the following information:
• Configuration and state of each LSP, including the source and destination
nodes, and transport label for the first hop.
LSP Link LSP Link layer.
This layer presents the point-to-point links between the PE and P routers over
which the LSPs presented in the LSP layer are delivered.
This includes links established through LDP and traffic engineering
(RSVP-TE). Each TE Tunnel LSP or LDP-signaled LSP spans one or more
LSP Links.
Enabling this layer provides the ability to visualize the following information:
• LSP Link configuration and state information.
• When filtered through selection of an LSP, the LSP Link hops that form the
end-to-end path of the LSP.

52 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Layer Icon Description

VLAN VLAN services.
This includes both C-VLAN and S-VLAN (i.e. QinQ) VLAN services.
Enabling this layer provides the ability to visualize the following information:
• VLAN services (C-VLAN and S-VLAN).
• The access ports associated with each VLAN service. This includes
identifying the devices and ports.
Note: For an S-VLAN service, the supported C-VLANs are presented
as attributes of the S-VLAN. They are not presented as separate VLAN
services.
Note: Where C-VLAN VIDs are reused in a customer bridge network or
S-VLAN VIDs reused in a provider bridge network (e.g. VID 100 re-used
for multiple point-to-point VLANs from access to aggregation nodes),
they are represented as a single VLAN service.
See section VLAN Service Representation (on page 59) for further
information.
VLAN Link VLAN Link layer:
This presents the VLAN topology as a set of VLAN Links.
Enabling this layer provides the ability to visualize the following information:
• Physical links configured to carry one or more VLAN services. This is
determined by the VLAN configuration of the device interfaces.
Note: When the VLAN Link layer is filtered to present a VLAN service,
all configured paths are presented, including the alternate paths that
need to be resolved through Spanning Tree or ERPS protocols in order
to avoid packet loops in the network.
PTP Link PTP Link layer.
This presents the PTP link layer topology of the network.
Enabling this layer provides the ability to visualize the following information:
• PTP configuration on PTP enabled interfaces.
SyncE SyncE Link layer.
Link This presents the SyncE link layer topology of the network.
Enabling this layer provides the ability to visualize the following information:
• SyncE configuration and state (clock quality) information on SyncE
enabled interfaces.
Physical The physical topology layer, indicating the devices and their physical
interconnecting links (radio or wired).

Paired Device Representation

Where multiple devices are required at each end of a radio or Ethernet link to deliver the customer
data, we refer to the devices at each end of the link as being ‘paired’. The following are examples
of paired device configurations requiring two devices at each end of the radio link.
• WTM 4200 2+0 XPIC SD (Space Diversity)
• WTM 4200 2x(2+0 XPIC)
• WTM 4500 1+0 SD (Space Diversity)
For WTM 4000, paired device configurations are represented in the Topology Map by a shaded box
around the device icons. The following figure indicates the notation used for XPIC SD
configuration.

Aviat Networks May 2019 53

Multi layer Network Topology Visualization

Figure 17: Paired Device Configurations

For WTM 4000 SD or L1LA configurations requiring paired devices, a single Radio Link is
presented between Main radio units. No link is presented on the Diversity radio units as they only
provide receiver paths and the RF module data is passed directly to the Main radio unit for
processing.
For WTM 4000 XPIC configurations requiring paired devices, a Radio Link is presented between
the matched radio units at each end of the radio link.

Services Representation at Each Layer

This section describes how end-to-end services at each networking layer are represented on the
Topology Map. In summary, each service is represented by one of more lines (links) between
terminating nodes.
As an example, the figure below presents a Topology Map for the following network design, with all
Layers included:
• Two L2VPN services
o One VPWS service
o One VPLS service with access points on three PE routers
• VPN services are delivered between PE routers via TE Tunnels with 1:1 protected LSPs
• TE Links are configured on all wireless L1 Links
Figure 18: Map Representation of Services at Each Layer (L2VPN and TE Tunnel Example)

As a further example, the figure below presents a Topology Map for a L3VPN service with access
points on three PE routers, and service traffic delivered between the routers via LDP-signaled LSPs

54 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 19: Map Representation of Services at Each Layer (L3VPN with LSP Example)

L3VPN Service Representation

Each L3VPN service is represented by a VPN hexagonal symbol. The PE routers providing the
VPN service to the customer are connected to the VPN symbol with purple links.
Figure 20: L3VPN Service Representation

RT Link Service Representation

Each RT Link is represented by a brown unidirectional link between two terminating PE routers,
indicating the export of vpnv4 routes from a VRF (tagged with a specific Route Target value) and
their import by another VRF.
The following example presents an any-to-any service topology, where 3 sites providing access to a
L3VPN export vpnv4 routes to each other.

Aviat Networks May 2019 55

Multi layer Network Topology Visualization

Figure 21: RT Link Service Representation

L2VPN Service Representation

VPWS Service:
Each VPWS service is represented by a VPN hexagonal symbol. The PE routers providing the
VPN service to the customer (2 in the case of a VPWS point-to-point service) are connected to the
VPN symbol with purple links.
Figure 22: L2VPN VPWS Service Representation

VPLS Service:
Each VPLS service is represented by a VPN hexagonal symbol. The PE routers providing the
VPLS service to the customer are connected to the VPN symbol with purple links.

56 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 23: L2VPN VPLS Service Representation

PW Service Representation
PW:
Each PW is represented by a bidirectional brown link between two terminating PE routers.
Figure 24: PW Service Representation

Aviat Networks May 2019 57

Multi layer Network Topology Visualization

PW mesh (for VPLS service):

The PW mesh for a VPLS service is indicated as a set of PWs, each PW represented by a
bidirectional brown link between two terminating PE routers.
Figure 25: PW Mesh Service Representation

TE Tunnel Service Representation

Each TE Tunnel is represented by a pair of directional pink links between the two terminating PE
routers.
Figure 26: TE Tunnel Service Representation

TE Link Service Representation

Each TE Link is represented by a pair of unidirectional blue links between two terminating PE
and/or P routers. The Name / ID can optionally be overlaid to facilitate distinguishing between the
links.

58 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 27: TE Link Service Representation

LSP Service Representation

Each LSP is represented by a pair of unidirectional pink links between the two terminating PE
routers.
Figure 28: LSP Service Representation

LSP Link Service Representation

Each LSP Link is represented by a pair of unidirectional blue links between two terminating PE
and/or P routers. The Transport Label can optionally be overlaid to facilitate distinguishing
between the links.
Figure 29: LSP Link Service representation

VLAN Service Representation

Each VLAN service (C-VLAN and S-VLAN) is represented by a hexagonal symbol. The devices
providing the VLAN access ports are connected to the VLAN symbol with blue links.
Where C-VLAN VIDs are reused in a customer bridge network or S-VLAN VIDs reused in a provider
bridge network (e.g. VID 100 re-used for multiple point-to-point VLANs from access to aggregation
nodes), they are represented as a single VLAN service.
Aviat Networks May 2019 59
Multi layer Network Topology Visualization

Figure 30: VLAN Service Representation

VLAN Link Service Representation

Each VLAN Link is represented by a single bidirectional blue link between two physically connected
nodes over which one or more VLANs are supported.
Figure 31: VLAN Link Service Representation

PTP Link Service Representation

Each PTP Link is represented by a single bidirectional light green link between the two PTP
enabled interfaces on a L1 Link.
Figure 32: PTP Link Service Representation

SyncE Link Service Representation

Each SyncE Link is represented by a unidirectional green link between the two SyncE enabled
interfaces on a L1 Link.
Priority and Quality indicators can optionally be overlaid to facilitate distinguishing between the links
and monitored quality of signal pass through. The clock source icon can optionally be overlaid on
nodes to distinguish between an external active/inactive clock source and free run mode.
See section Overlay Data and Auto Update for details.

60 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 33: SyncE Link Service Representation

Physical Service Representation

Each L1 Link is represented by a pair of unidirectional black links between two terminating devices.
Figure 34: Physical Service Representation

Service Links Bundling

Where multiple service links of the same type have the same termination points (e.g. multiple LSP
Links originating and terminating on the same PE routers), by default a single Bundled Link object is
presented on the Topology Map overlaid with a count indicating the number of service links within
the bundle.
The figure below presents example Bundled Link objects (each containing two LSP Links), together
with the representation where one of the Bundled Link objects is unbundled (revealing the two LSP
Links with their Transport labels).
Figure 35: Example Bundled and Unbundled Links

The user is able to unbundle and bundle the service links through the right-click menu options
described in the following table.
Table 19: Service Link Object Right-click Menu Bundling

Menu Option Description

Unbundle Links This option is available with Bundled Link objects. Selection results in
the service link objects within the bundle being presented individually.
Bundle Links This option is available with service link objects that have been
temporarily unbundled. Selection results in the service link objects
being presented as a single Bundled Link object again.

Aviat Networks May 2019 61

Multi layer Network Topology Visualization

Hidden RT Links (Exceeding Display Max Limit)

A display limit is imposed on the maximum number of RT Link connections per device object that
can be displayed in the Topology Map view.
Where there are more than 10 RT Links on a device, the RT Links are hidden (not displayed), a
hidden links symbol ( ) is overlaid on top of the device object, and a warning message is
presented.
The hidden links can be unhidden by clicking on the device object. This mechanism allows for
un-hiding the links for one device at a time, hence when clicking the next device object the links
associated with the previous become hidden again.
The following figure presents an example where RT Links are hidden. The warning message is
presented underneath the Detail / Key.
Figure 36: Example Hidden RT Links

Navigating Between Interconnected Layers

This section describes how to navigate between the interconnected end-to-end services at each
layer. In summary, when you select a service on the Topology Map, assuming that the underlying
layer is enabled, the underlying supporting layer service(s) are automatically highlighted by a dotted
line notation.
As an example, the figure below presents an area of a Topology Map where a L2VPN VPLS has
been selected and the underlying PWs supporting the VPN are highlighted by dotted lines.

62 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 37: Example Map Indicating Services at Each Layer

In the case of selecting a TE Tunnel, the supporting TE Links over which the TE Tunnel LSPs are
routed can only be fully identified through the RRO operational state for each LSP.
Navigation from a TE Tunnel to the supporting TE Links is therefore only available where the
Baseline vs Live Selector is set to “Live + Baseline”.
When set to “Baseline”, only the ERO configuration for the TE Tunnel LSPs is indicated. See
below for a detailed example covering both cases (“Live + Baseline” and “Baseline” settings).

Note: Where Topology Filtering is configured, some supporting services for an enabled
layer may not be visible in the Topology Map. See section Topology Filtering (on page 89)
for details.

L3VPN Supporting Layer Navigation

Selecting a L3VPN service highlights the underlying unidirectional RT Links (dotted) providing an
indication of the service routing topology.

Any-to-any:
The following example presents an any-to-any topology, where 3 sites (providing access to the
L3VPN) export vpnv4 routes to all other sites.

Aviat Networks May 2019 63

Multi layer Network Topology Visualization

Figure 38: L3VPN Any to Any Service Navigation

Hub and Spoke:

The following example presents a hub and spoke topology, where spoke sites export vpnv4 routes
to the hub site only, and the hub site exports to the spoke sites.
Figure 39: L3VPN Hub and Spoke Service Navigation

RT Link Supporting Layer Navigation

Selecting an RT Link highlights the underlying TE Tunnel (dotted) or LDP-signaled LSP (dotted).
Where the RT Link is delivered over a TE Tunnel, the TE Tunnel is highlighted as indicated in the
following example.

64 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 40: RT Link Service Navigation

Note: As the RT Link object indicates the flow direction of vpnv4 routes, the TE Tunnel and
tunnel LSP objects are in the opposite direction as they indicate the resultant traffic flow
direction.

L2VPN Supporting Layer Navigation

VPWS Service:
Selecting a VPWS service highlights the underlying PW (dotted).
Figure 41: L2VPN VPWS Service Navigation

Aviat Networks May 2019 65

Multi layer Network Topology Visualization

VPLS Service:
Selecting a VPLS service highlights the underlying PW mesh (dotted).
Figure 42: L2VPN VPLS Service Navigation

PW Supporting Layer Navigation

Selecting a PW highlights the underlying TE Tunnel or LDP-signaled LSP (dotted).
The following example indicates the supporting LDP-signaled LSPs for a selected PW.
Figure 43: PW Service Navigation

66 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

TE Tunnel Supporting Layer Navigation

Selecting a TE Tunnel highlights:
• the underlying LSP(s), and
• the underlying TE Links for each tunnel LSP.
In addition, the following configuration and state attributes are presented for each path.
ERO (Explicit Route Object) path configuration. W indicates Primary Working path routers and P
indicates Primary Protecting path routers. Tick indicates Included in the ERO, and Cross indicates
Excluded from the ERO.
RRO (Record Route Object) path operational state. The green line indicates Primary Working
path, the red line indicates the Primary Protecting path, and an orange line indicates path segments
(TE Links) shared by both Working and Protecting paths. RRO information is only available where:
• it’s been enabled on the head-end router, and
• “Live + Baseline” has been selected. See the following notes for details on these restrictions.
Active and Inactive paths operational state (e.g. for 1:1 protection) (available only where “Live +
Baseline” selected). The solid line indicates the Active path, and the dotted line the Inactive path.

Note: As the RRO for each TE Tunnel LSP is an indication of the operational state, as
opposed to the configuration, an RRO path (TE Links over which an LSP has been
instantiated) is only presented when the Baseline vs Live Selector is set to “Live + Baseline”.
Note: RRO is an optional configuration setting on a PE router. This setting must be
enabled on a TE Tunnel head-end router before is able to discover and present RRO path
information.

Aviat Networks May 2019 67

Multi layer Network Topology Visualization

Example TE Tunnel with TE Link and LSP Layers Enabled

Both the TE Link and LSP layers are enabled in the following example. The solid green lines
indicate the Active Working TE Links (teAB, teBG, teGJ) and LSP (100406) associated with TE
Tunnel 100. And the dotted red lines indicate the Inactive Protecting TE Links and LSP associated
with TE Tunnel 100. Note that the two LSPs are bundled by default, as they have the same source
and destination; however in the example below they have been unbundled.
Figure 44: Example TE Tunnel with TE Link and LSP Link Layers Enabled

Example TE Tunnel with TE Link Layer Enabled

Only the TE Link layer is enabled in the following example.
Figure 45: Example TE Tunnel with TE Link Layer Enabled

68 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Example TE Tunnel Interop with an Unmanaged LSR

Where a CTR router forms the head-end of a TE Tunnel, and the tunnel spans or terminates on
unmanaged (e.g. not supported) MPLS routers, the supporting L1 Links and TE Links between CTR
routers on the Working and Protecting LSP paths are still presented, although the unmanaged
node(s) and the supporting L1 Links and TE Links between either two unmanaged nodes or CTR
and an unmanaged node are not presented.
In the following example, the TE Tunnel inactive Protecting LSP (red dotted line) spans an
unmanaged Cisco router with L1 Link connections to CTR routers 1B-109 (top right) and 1A-112
(bottom right).
Figure 46: Example TE Tunnel Interop with an Unmanaged LSR

Example TE Tunnel and Baseline Only:

Where “Baseline” is selected, as indicated in the following example, only TE Tunnels and TE Links
are presented as LSPs and LSP Links are classified as state information.
Figure 47: Example TE Tunnel and Baseline Only

Example TE Tunnel with Working and Protecting Paths Transiting Same TE Link
Where both Working and Protecting paths transit the same TE Link, an orange line is displayed for
that hop. This is indicated in the following example.
This same notation applies to the LSP Links.

Aviat Networks May 2019 69

Multi layer Network Topology Visualization

Figure 48: Example TE Tunnel with Working and Protecting Paths Transiting Same TE Link

The L1 Links have been excluded from the Layer Selector in order to simplify the representation.

TE Link Supporting Layer Navigation

Selecting a TE Link highlights the underlying L1 Link (dotted).
Figure 49: TE Link Navigation

70 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

LSP Supporting Layer Navigation

Selecting an LSP highlights the set of LSP Links (dotted), i.e. the segments of the LSP that form the
operational end-to-end path.
Figure 50: LSP Service Navigation

LSP Link Supporting Layer Navigation

Selecting an LSP Link highlights the underlying L1 Link (dotted).
Figure 51: LSP Link Service Navigation

VLAN Service Supporting Layer Navigation

Selecting a VLAN service (C-VLAN and S-VLAN) highlights the underlying VLAN Links (dotted)
providing an indication of VLAN topology, i.e. the L1 Links over which the VLAN service is provided.
Figure 52: VLAN Service Navigation

VLAN Link Supporting Layer Navigation

Selecting a VLAN Link highlights the underlying L1 Link (dotted).

Aviat Networks May 2019 71

Multi layer Network Topology Visualization

Figure 53: VLAN Link Navigation

PTP Link Supporting Layer Navigation

Selecting a PTP Link highlights the underlying L1 Link (dotted).
Figure 54: PTP Link Navigation

SyncE Link Supporting Layer Navigation

Selecting a SyncE Link highlights the underlying L1 Link (dotted).
Figure 55: SyncE Link Navigation

Map Coordinates
This section describes the support available for positioning nodes (device and VPN objects) on the
Topology Map. In summary, the following capabilities are provided:
• Use either System Coordinates or Local Coordinates
o See How to Configure System Coordinates
o See How to Configure Local Coordinates
• Manually position nodes on map
• Automatically define the coordinates by applying an Auto Layout algorithm
• Lock/Unlock the ability to change the coordinates
The capabilities are provided through the Coordinate Modes drop-down menu and Lock/Unlock
toggle button as indicated in the figure below and described in the table below.

72 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 56: Map Coordinates Controls

Table 20: Map Coordinates Controls

Control Function
System Coordinates Through the Coordinate Modes drop-down menu, each user can select to use either
and System Coordinates or Local Coordinates to position the nodes on the Topology
Local Coordinates Map.
• System Coordinates provides the ability for all users to adopt common coordinate
positioning. When this mode is selected, any changes to the coordinates
(typically made by a designated Engineer), are automatically reflected in all client
sessions that are using System Coordinates mode.
• Local Coordinates provides the ability for users to adopt their own personal
coordinate positioning.
System Coordinates is the default mode.
USER ROLE: Modification of the System Coordinates requires Engineer user role
access.
Import Local from This Coordinates Mode drop-down menu selection provides the ability to copy the
System Coordinates current common System Coordinates positions into your personal Local Coordinates
positions. This is a recommended initial step to setting up Local Coordinates for the
first time.
This control is only available when Local Coordinates is the selected coordinate
mode.
Export Local to System Provides the ability to copy the current personal Local Coordinates positions into the
Coordinates common System Coordinates positions.
This control is only available when Local Coordinates is the selected coordinate
mode.
Manually position Position node (device or VPN) objects manually on the map by using mouse drag
and drop controls.
This control is only available when the coordinates lock toggle button is set to Unlock.

Aviat Networks May 2019 73

Multi layer Network Topology Visualization

Control Function
Auto Layout Nodes can be positioned automatically by selecting Auto Layout on the Coordinate
Modes drop-down menu. This applies a CoSE (Compound Spring Embedder)
algorithm to determine the optimal coordinate positions for each node in the network.
On selecting the Auto Layout menu option, a confirmation prompt is presented to the
user. On selecting OK, the following prompt is then presented on the Main Menu /
Status Bar:
It’s recommended that Auto Layout only be used as an initial step when positioning
the network nodes for the first time. After applying Auto Layout, you may wish to
further optimize the positions manually.
This control is only available when the coordinates lock toggle button is set to Unlock.
Note: When new nodes are subsequently added to the network (following
Auto Layout), it’s recommended that they be positioned manually, as Auto
Layout will be applied to the previously positioned nodes.
Lock/Unlock The lock toggle button provides the ability to Lock/Unlock the coordinates.
Coordinates This control is applied to the currently selected System Coordinates or Local
Coordinates.
By default the lock toggle button is set to Lock.
Export to PNG Exports the graphical Topology Map view to a PNG file.

How to Configure System Coordinates

The following is the recommended procedure for configuring the System Coordinates for the first
time and then subsequently maintaining throughout the lifetime of the deployed network.

Initial setup of object co-ordinates:

Step Action
1. Unlock the System Coordinates.
2. Optionally apply Auto Layout.
3. Complete positioning of the coordinates manually.
4. Lock the System Coordinates.

Maintain object coordinates as new nodes (devices or VPN services) are added to the network:

Step Action
1. Unlock the System Coordinates.
2. Position the new nodes manually.
3. Lock the System Coordinates
Note: It is recommended that the System Coordinates be maintained by a designated
Engineer.

74 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

How to Configure Local Coordinates

The following is the recommended procedure for configuring the Local Coordinates for the first time
and then subsequently maintaining throughout the lifetime of the deployed network.

Initial setup of object coordinates:

Step Action
1. Unlock the Local Coordinates
2. Either:
• Import Local from System Coordinates (where System Coordinates are configured), or
• Optionally apply Auto Layout.
3. Complete positioning of the coordinates manually.
4. Save the new coordinates positions (click the presented save button).
5. Lock the Local Coordinates.

Maintain object coordinates as new nodes (devices or VPN services) are added to the network:

Step Action
1. Unlock the Local Coordinates.
2. Position the new nodes manually.
3. Save the new coordinates positions (click the presented save button).
4. Lock the Local Coordinates.

Aviat Networks May 2019 75

Multi layer Network Topology Visualization

Overlay Data and Auto Update

This section describes the support available for overlaying configuration and/or state information on
the nodes (device and VPN objects) and links (TE Link, TE Tunnel, PW, etc services) on the
Topology Map. In summary, the following data overlay capabilities are provided:
• Name (of node or link)
• Highest active alarm severity indicator (of node or link)
• Baseline vs Live configuration change indicator (Model Status)
• Configuration and state attribute values
The capabilities are provided through the Overlay Data drop-down menu indicated in the figure
below and described in the table below.
Through this drop-down menu, the user is also provided with the ability to select whether detected
changes to the network topology are automatically applied to the client topology view, or applied
on-demand.

Note: LICENSING: IP/MPLS overlay data is only presented in the dropdown menu options
where the IP/MPLS Fault product module is licensed.
Figure 57: Map Overlay Data and Auto Update Controls

Table 21: Map Overlay Data and Auto Update Controls

Overlay Description
Auto Update Toggles the function of the Refresh button between Manual Update and Auto
Update. See section Map Controls (on page 47) for details.
76 May 2019 Aviat Networks
 Multi layer Network Topology Visualization

Overlay Description
Node Name Display the Name above each node object (device or VPN).
This overlay is enabled by default.
Node Severity Set the color of each node object (device or VPN) to reflect the highest active
alarm severity. See section Severity Color Coding for Events and Alarms
(on page 125) for the alarm severity colors.
Router ID Display the Router ID above each device object.
Link Name Display the Link Name above the link object (e.g. TE Link).
Link Severity Set the color of each link object (L1 Link, TE Link, etc.) to reflect the highest
active alarm severity. See section Severity Color Coding for Events and
Alarms (on page 125) for the alarm severity colors.
Model Status Display the Model Status indicator on top of node and link objects. This
indicates where there is a difference between the Baseline design and Live
network configuration. See section Live Network Configuration Change
Indicators (on page 117) for details.
RT Link: Route Target Display the Route Target (RT) value on top of the RT Link objects.
TE Link: Max Bandwidth Display the TE Link Max Link Bandwidth value on top of the TE Link objects.
TE Link: Default Metric Display the TE Link Default Metric value on top of the TE Link objects.
LSP: First Hop Transport Label Display the LSP transport label for the first hop of the LSP.
LSP Link: Transport Label Display the transport (upper) label on top of the LSP Link objects.
SyncE: Priority & Quality Display the destination configured SyncE priority and current clock quality
state information.
SyncE: Clock Source Display the clock source icon on device node for Free run mode and any
configured external clock source.

Detail / Key Indicators

This section describes the function of the Detail / Key indicators provided in the top left corner of the
Topology Map. In summary, the following information is provided:
• Layers enabled on the topology view, together with the ability to disable the layers
• Selected service object focus
• Key for the supporting layer service (for the selected focus)
The figure below presents an example where the TE Tunnel, TE Link and Physical layers are
presented in the map, and TE Link object “teBD” is the selected focus.
Figure 58: Detail / Key Indicators

Table 22: Detail / Key Indicators

Indicator Description
Layers Indicates the Layers enabled for presentation on the Topology Map and Data
Panel using the Layers Selector.
Focus Indicates the service object (i.e. the specific VPN, PW, RT Link, TE Tunnel, TE
Link, LSP, LSP Link or L1 Link) selected on the Topology Map or Data Panel
using mouse click.

Aviat Networks May 2019 77

Multi layer Network Topology Visualization

Indicator Description
Key for Focus Provides a key for the supporting layer service for the selected Focus. An
supporting example is provided below for each possible supporting layer.
layer services VPN Focus example:

PW Focus example:

TE Tunnel Focus example:

TE Link Focus example:

SyncE Link Focus example:

PTP Link Focus example:

Data Panel
The Data Panel provides a tabular view of the configuration and state information of the devices
and services presented in the Topology Map graphical view.
When enabling networking layers through the Layers Selector (see section Layers Selector), in
addition to the associated devices and services being presented in the Topology Map, a separate
tab for each enabled layer is presented in the Data Panel.
And when filtering on specific devices or services (see section Topology Filtering), the selections
are applied to both the Topology Map and Data Panel views in a complimentary format.

78 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

The figure below presents an example Topology Map and Data Panel. As can be seen, both panes
present the L2VPN, PW and Physical layers enabled through the Layers Selector, and the same set
of devices and services.
• 2 x L2VPNs (1 x VPLS and 1 x VPWS)
• 4 x PWs
• 20 x unidirectional L1 Links
• 8 x Devices
Note: LICENSING: IP/MPLS services are only presented in the Data Panel where the
IP/MPLS Fault product module is licensed.
Figure 59: Example Topology Map and Data Panel

Data Panel Tabs

The following table summarizes the content of each layer tab that can be presented in the Data
Panel. See section Data Panel Attributes (on page 81) for further information on the attributes of
each tab.
Table 23: Data Panel Tabs

Layer Tab Description

L3VPN Each row presents the basic attributes associated with a L3VPN instance.
A unique VPN ID for each L3VPN instance is derived from the configuration of the
VRFs in the network.
RT Link Each row presents the attributes of an RT Link. i.e. the export and import of vpnv4
routes, tagged with a specific Route Target value, between two VRFs.
L2VPN Each row presents the basic attributes associated with a L2VPN VPLS or VPWS
instance.
PW Each row presents the basic attributes associated with a L2VPN PW.
For a VPLS service, each point-to-point PW providing the PW mesh is presented in
a separate row.
TE Tunnel Each row presents the attributes and operational state of a TE Tunnel.
Aviat Networks May 2019 79
Multi layer Network Topology Visualization

Layer Tab Description

TE Link Each row presents the attributes and operational state of a TE Link.
LSP Each row presents the configuration attributes and operational state of a
traffic-carrying LSP, including the source and destination nodes, and transport label
for the first hop.
LSP Link Each row presents the basic attributes associated with an LSP Link, i.e. the LSP
segment between neighboring MPLS routers. Each is uniquely identified by the
transport (upper) label in addition to the Source and Destination routers.
The LSP Links between the adjacent routers are derived by from discovery of the
label bindings (i.e. the label switching cross connect) in each router that have either
been signaled by a label distribution protocol (LDP or RSVP-TE) or statically
configured.
VLAN Each row presents the basic attributes of a VLAN service.
Customer bridge C-VLAN services and provider bridge (QinQ) S-VLAN services are
both uniquely identified by their respective VIDs.
VLAN Link Each row presents the attributes of a VLAN Link. Each VLAN Link is a L1 Link
that’s configured to deliver one or more VLAN services.
PTP Link Each row presents the attribute of PTP Link.
SyncE Link Each row presents the attributes and operational state of SyncE Link.
L1 Link Each row identifies the device and interface that terminates each end of a radio link
or Ethernet cable link.
Device Each row indicates the basic device identifiers, together with the upper layer
services and VPN ACs (Attachment Circuits) that originate or terminate on the
device.
The following information is only presented when the associated upper layer has
been enabled:
• L1 Terminations
• TE Link Terminations
• TE Tunnel IDs
• PW Terminations
• L2VPN ACs
• L3VPN ACs

80 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Data Panel Controls

The controls available for processing the Data Panel are listed in the table below.
Table 24: Data Panel Controls

Control Description
Column Sort Sort the tabular view by mouse clicking on a column heading.
Search A text search can be applied to the tabular view, resulting in only those rows
containing a match being displayed. The search is applied to all tabs in the Data
Panel, i.e. it’s not only applied to the selected/visible tab.
Row Focus When you mouse click on a row in the Data Panel, the associated device or
service object on the map is highlighted and becomes the selected focus.
Row navigation Navigate to Events and Detail views associated with a particular row through the
menu mouse <right-click> menu.
Comparison Enable/disable the ability to compare configuration and state of selected devices
or services through a specialized variant of the Detail view, known as the
Comparison view. See Comparison View for further information.
Export to Export the information on the selected Data Panel tab in CSV, JSON or PDF
CSV/JSON/PDF output format. Where the view has been filtered using the Search control, only
the information in the resultant rows is exported.
Attribute Enable/disable the attributes available for display on the Data Panel tabs. The
list of available attributes is presented in the dropdown menu for the currently
selected (displayed) tab.

Data Panel Attributes

The attributes presented on the tab for each layer in the Data Panel are user configurable.
Changes made to the default selection of attributes are persisted on the user’s client machine. The
changes do not impact other users.
The Glossary of Technical Terms (on page 171) section provides a definition of each
configuration and state attribute that can be included, and clarifies the subset of attributes included
by default.
By default the first two fields on each device and service tab contain Model Status and Alarm Status
indicators, as described in the table below.
Table 25: Data Panel: General Attributes on All Tabs

Attribute Description
Live (Model Indicator warning when a change is detected in the Live network that’s not in
Status) the Baseline design, i.e. the Baseline design and Live configuration for the
device or service differ.
For example, symbol indicates that a new device or service has been
detected in the Live network. See section Live Network Configuration
Change Indicators (on page 117) for a definition of the supported Model
Status indicators.
Alarm Indicator for the highest severity alarm currently active on the device or service.
For example, symbol indicates Major severity. See section Alarm Status
Indicators (on page 131) for details.
Selection of the attributes to be included on each tab is available through the Data Panel Controls
menu described in section Data Panel Controls (on page 81) above.

Aviat Networks May 2019 81

Multi layer Network Topology Visualization

Tree Context Selector

The Tree Context Selector provides the user with the following capabilities:
• Devices tree view representing the physical network hierarchy in terms of containment
hierarchy of Region, Site, Device and device plugin objects.
• Services tree view representing the end-to-end services at each networking layer.
• Apply a device or service object filter to the Topology Map and Data Panel views.
• Apply a device or service object filter to the Performance views.

Devices Tree
The Devices Tree view presents the physical network hierarchy deployed directly in ProVision Plus
and/or indirectly via ProVision. See section Network Deployment (on page 27) for details. The
Devices tree view presents the physical network hierarchy that’s been deployed on the ProVision
network mediation system, and discovered via the NBI. This includes Region, Site, Rack and
Device objects.
Changes made to the physical network hierarchy in the ProVision mediation system are reflected in
ProVision Plus within a few seconds.
The figure below presents an example Devices tree view.
Figure 60: Example Tree Context Selector Devices Tree

Services Tree
The Services tree view presents the end-to-end services, including L2VPN, PW, L3VPN, RT Link,
TE Tunnel, TE Link, LDP LSP, LSP Link and physical L1 Link services.

Note: LICENSING: IP/MPLS services are only presented in the Service Tree where the
IP/MPLS Fault product module is licensed.
Note: LICENSING: Carrier Ethernet (CE) services are only presented in the Service Tree
where the CE Fault & Performance product module is licensed.
The figures below presents an example Services tree view.

82 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 61: Example Tree Context Selector Services Tree with IP/MPLS Services

Figure 62: Example Tree Context Selector Services Tree with CE Services

Aviat Networks May 2019 83

Multi layer Network Topology Visualization

Tree Context Selector Controls

The controls available for processing the Tree Context Selector are listed in the table below.
Table 26: Tree Context Selector Controls

Control Icon Description

Context Physical / Services context selection.

Search Searches for and highlights the next device or service object in the tree
that contains the entered text.
Where the next object is contained within a collapsed tree node, the
node is automatically expanded.
Filter object(s) Objects can be selected /deselected for inclusion in the topology filter by
selection clicking on the object name in the tree.
Selected objects are indicated by a symbol to the left of the object
name.
The filter selection can be viewed / edited by clicking on the filter symbol
( ). See the figure below for an example.
Filter controls = Delete the selected filter.
= Apply the selected filter to either the Topology Map / Data Panel
view, or the Performance view.
= View / edit the selected filter.
Hide / Unhide Hide / Unhide the Tree Context Selector pane.
pane
Lock / Unlock The Lock / Unlock button in the top right corner of the Devices Tree
Tree toggles the tree lock on and off. When unlocked, the tree can be edited
(see section Making Changes to Deployment (on page 33)).
Drag and Drop When the tree is unlocked, Container or directly managed Device objects
can be reparented by drag and drop. See section Making Changes to
Deployment (on page 33) for details.
Device Tooltip Indicates the following information for a device object:
• Object: Device name
• Type: Device type (e.g. WTM 4100)
• IP Address: Management IP address used to communicate with the
device
• State: Management state (Unmanaged, Connecting, Managed or
Errored)
• Severity: Highest active event severity for the device
Container Indicates the following information for a container object
Tooltip • Object: Container name.
• Type: Container type (Region, Site or Rack).
• Children: Number of objects in the container, excluding children of
those objects.
• Severity: Highest active event severity for all devices deployed within
the container, including any child containers.

Figure 63: Example Tree Context Selector Filter View/Edit

84 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Tree Object Right-Click Menu Navigation

Additional information and functions associated with each object presented on the Tree Context
Selector can be accessed via the right-click menu.
Table 27: Tree Object Right-click Menu

Menu option Description

Manage / Unmanage Provides the user with the ability to Manage or Unmanage a single
device, or multiple devices when applied to a container object.
When accessed from a device object, the Manage menu option indicates
the current management state of the device.
When a device is Managed, fault, configuration and performance
information is periodically collected from the device. See section Direct
Device Management (on page 100) for further details on management
configuration and state.
Detail Opens a Detail dialog presenting configuration and state details for the
selected device or service object. See section Detail View (on page 86)
for details.
Events Opens an Active Events window presenting the currently active events for
the selected container, device or service object. See section Event
Browser (on page 125) for details.
Performance Opens the Resource Performance view (see section Resource
Performance (on page 136)) for a selected device, or provides access to
the Performance menu for a container.
Configuration Provides access to the Configuration menu for a container.
Discover Configuration Re-discovers the configuration for a selected directly managed device.
For indirectly managed devices, this capability is only available through
ProVision.
Launch Web Portal Opens the web-based device craft tool interface.
This menu option is available on the Devices object only.
Locate Locates the device or service object on the Topology Map.
Delete Presents the user with the Delete Object dialog, allowing the container or
device object to be deleted. See section Making Changes to
Deployment (on page 33) for details.
Rename Presents the user with the Rename Object dialog, allowing the container
or device name to be changed. See section Making Changes to
Deployment (on page 33) for details.

Aviat Networks May 2019 85

Multi layer Network Topology Visualization

Detail View
The Detail view provides the user with the following capabilities:
• Tabular view presenting the configuration and state detail of a selected device or service.
• Indication of the adjacent dependent (upper) and supporting (lower) layer services.
• Single click navigation to adjacent dependent or supporting layer service.
• Indication of the configuration differences between the Live network and Baseline design.
• Comparison of configuration and state information between multiple selected devices or
services of the same type. See section Comparison View for details.
Access to the Detail modal view is available from the right-click menu associated with each device
and service object in the Tree Context Selector, Topology Map and Data Panel panes.
The following figure presents an example L2VPN where there are no differences between the
discovered Live network configuration and Baseline design.

Note: LICENSING: IP/MPLS services are only accessible in the Detail view where the
IP/MPLS Fault product module is licensed.
Note: LICENSING: Carrier Ethernet (CE) services are only accessible in the Detail view
where the CE Fault & Performance module is licensed.
Figure 64: Example L2VPN Detail View

Figure 65: Example Device Detail View

86 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Detail View Display Areas and Controls

The figure and table below identify the display areas and controls available in the Detail view. A
PW service with differences between the discovered Live network configuration and Baseline
design is presented as an example.
Figure 66: Detail View Display Areas and Controls

Table 28: Detail View Display Areas

Area Description
Title Identifies the selected device or service.
Adjacent layer services Identifies the adjacent layer dependent (upper) and supporting (lower)
layer services.
For example, a specific TE Link may have multiple dependent upper layer
TE Tunnel services, and a single supporting lower layer L1 Link service.
Service detail Indicates the configuration and state detail of the selected device or
service.
Highlighting of attributes indicates the following:
• Blue text indicates that the Live network and Baseline values differ.
• Strike through text indicates that the object or attribute no longer exists
in the Live network.
Live/ Baseline Optionally displays the Live network and Baseline values for selected
Differences pane attributes that differ in value. Multiple attributes can be added.
The pane is displayed when clicking on a blue highlighted attribute.
Table 29: Detail View Controls

Control Icon Description

Navigation to adjacent layer - Clicking on an adjacent dependent or supporting layer
service service navigates to that service, updating the Detail
pane with its associated information.
Locate Locates the device or service object on the Topology
Map and Data Panel.
New window Opens and populates a new browser tab with the
detail view content.
Add attribute to the Live/Baseline - Clicking on a blue highlighted attribute adds it to the
Differences pane Live/Baseline Differences pane.
Remove attribute from the Clicking on the close control removes the attribute
Live/Baseline Differences pane from the Live/Baseline Differences pane.
Hide/Unhide the Live/Baseline Hide/Unhide control for the Live/Baseline Differences
differences pane pane.
Note: State information is only presented in the Detail view where “Live + Baseline” is
chosen in the Baseline/Live Selector. See section Baseline / Live Selection (on page 116)
for details.
Aviat Networks May 2019 87
Multi layer Network Topology Visualization

Detail View Attributes

See section Glossary of Technical Terms (on page 171) for a definition of each configuration and
state attribute presented in the Detail view.

Note: The symbol is used to denote a state (as opposed to configuration) attribute.

Comparison View
The Comparison view is a specialized variant of the Detail view, providing the user with the
following additional capabilities:
• Tabular view presenting the configuration and state of multiple selected devices or services of
the same type.
• Configuration or state attributes that differ in value between the presented devices or services
are highlighted.
• Comparison of Baseline or Live network configuration and state is provided, as determined by
the Baseline vs Live Selector setting.
Access to the Comparison modal view is available from the right-click menu associated with the
Data Panel.

How to Access the Comparison Modal View

Follow the steps below to access the Comparison modal view.

Step Action
1. Enable the Comparison option on the Data Panel drop-down menu.

This toggles the Data Panel right-click menu option from Detail to Comparison.
The checkbox selection column is then presented in the Data Panel table.
2. Multi-select the devices or services to be compared. The following example indicates
selection of two RT Link objects.

3. Select the Comparison option on the Data Panel right-click menu. The Comparison modal
view is then presented.
The figure below provides an example comparing two RT Link objects. In this particular example,
the two RT Links originate on different VRFs on different PE routers, have different Route Target
(RT) values, and terminate on the same VRF.

88 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Figure 67: Comparison View Example

Topology Filtering
Topology filtering provides the ability to view the section of the network topology (in the Topology
Map and Data Panel) that’s associated with one or more specific containers (e.g. regions), devices
or end-to-end services. For a large deployed network containing 100s or 1,000s of devices, this
type of filtering enables the user to quickly select a specific region or area. This capability also
facilitates efficient impact analysis and troubleshooting. For example, on detection of a L2VPN
service failure, filtering on the VPN service identifies the underlying supporting layer services and
devices, one of which is the probable root cause.
A filtered topology view presents the device or service objects included in the filter together with the
following:
• Dependent (higher layer) services in enabled layers.
• Direct or indirect supporting (lower layer) devices and services in enabled layers.
Depending on the method selected for configuring the topology filter, either one or more devices or
one or more services can be selected and applied. This is described further below.
Where multiple objects (devices or services) are included in the filter, the dependent and supporting
layer objects are presented for each. Hence the logic applied by the filter is to display
dependent/supporting layer services/devices for filtered object1 OR object2 etc (as opposed to
object1 AND object2 etc.).
For example, where Device 1 supports only VPN A and Device 2 supports only VPN B, including
Device 1 and Device 2 in the filter, results in both VPN A and VPN B being displayed. Hence when
planning on software upgrading multiple devices in the network, filtering on the devices can be used
to identify the set of VPN services that will be impacted.

Note: When a topology filter is applied, some supporting services on an enabled layer may
not be visible in the Topology Map and Data Panel. For example, when filtering on a device
that supports a TE Tunnel Primary Working LSP and then selecting the TE Tunnel in the
filtered view, the supporting Protecting LSP may not be presented. In this situation, a
warning message is presented to the user. See example procedure in section Example
Topology Filters (on page 90) below.

Aviat Networks May 2019 89

Multi layer Network Topology Visualization

Note: A filtered topology view can also differ between viewing the “Live + Baseline” or the
“Baseline” topology, as operational state information can only be viewed when “Live +
Baseline” is set. For example, the RRO operational state (indicating the supporting TE Links
for the LSPs of a selected TE Tunnel) or LDP LSP operational state (indicating the LSPs
signaled via LDP).
Note: When a topology filter is applied, the rows presented in the Data Panel match the
selected filter, however displayed Termination fields present the full list of terminations
associated with the row device of service object. For example, when applying a TE Link
filter, the Device tab presents the two devices that support the TE Link however the L1
Terminations field lists all the interfaces that terminate L1 Links for that device.
A topology filter can be selected and applied to the topology view via the following methods:
• Tree Context Selector Controls. This method allows for including multiple devices or multiple
services in the topology filter. See section Tree Context Selector Controls (on page 84) for
details on applying a filter via the Tree Context Selector.
• Map object right-click menu. This method provides a quick and simple means of applying a
topology filter comprising a single device or service.

Example Topology Filters

The following examples indicate how to apply topology filtering to assist with service root cause
analysis and service impact analysis.

How to Visualize Topology of L2VPN and Supporting Lower Layer Services

The following steps indicate how to filter on a specific L2VPN service, to identify the supporting
layer PWs, TE Tunnels, TE Links, L1 Links and Devices. This type of filter facilitates root cause
analysis of a faulty L2VPN.

Step Action
1. On the main menu, select Topology > Physical to display the physical network topology.
2. Open the Layer Selector and enable layers L2VPN and PW. The Physical layer is already
enabled.
3. Select and apply the filter via one of the following methods:
Tree Context Selector:
• Select context Services on the Tree Context Selector.
• Click on a VPN service in the Services tree. The selected VPN is added to the context
filter.
• Apply the filter to the Topology view by clicking on the icon in the Tree Context
Selector.
Map object right-click menu:
• Click on the VPN service object on the Topology Map and select menu option Filter on
the right-click menu.
4. The Topology Map and Data Panel are now filtered to only display the VPN service and the
underlying layer services (in this case the PWs and L1 Links) over which the VPN is
delivered. Use the Layer Selector to enable other layers.

How to Visualize Topology of L1 Link and Dependent Higher Layer Services

This example indicates how to filter on a specific L1 Link and identify the higher layer services that
depend upon its availability. This type of filter facilitates service impact analysis (e.g. when
planning maintenance on a wireless L1 Link).

90 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Step Action
1. On the main menu, select Topology > Physical to display the physical network topology.
2. Open the Layer Selector and enable layer L2VPN. The Physical layer is already enabled.
The following example presents the L1 topology for a number of VPWS point-to-point
services.

3. Filter on a L1 Link using one of the two available methods:

Tree Context Selector:
• Select context Services on the Tree Context Selector.
• Click on a L1 Link service in the Services tree. The selected L1 Link is added to the
context filter.
• Apply the filter to the Topology view by clicking on the icon in the Tree Context
Selector.
Map object right-click menu:
• Click on the L1 Link object on the Topology Map and select menu option Filter on the
right-click menu.
For the purposes of this example, L1 Link [193]-[192] is added to the filter:

Aviat Networks May 2019 91

Multi layer Network Topology Visualization

Step Action
4. The topology view is now filtered to only display the L1 Link and the dependent higher layer
L2VPN services.
In this example it can be seen that VPWS 12 and VPWS 10 will be impacted by L1 Link
[193]-[192].

5. On selecting VPWS 10, a warning message beneath the Detail / Key confirms that some
supporting links (end-to-end services) for an enabled layer may not be visible.

6. To better understand why a particular VPN service is impacted (it’s not always intuitively
obvious), simply add the VPN to the topology filter (using the method in step 3).
In this example VPWS 10 is added to the topology filter.

92 May 2019 Aviat Networks

 Multi layer Network Topology Visualization

Step Action
7. In this example, the topology view clarifies that VPWS 10 (between PE routers [176] and
[191]) must transit L1 Link [193]-[192].

8. To better understand how each supporting layer for VPWS 10 is impacted by maintenance
on L1 Link [193]-[192], simply enable each as required using the Layer Selector.

Aviat Networks May 2019 93

 Configuration Management

Chapter 6. Configuration Management

This section describes the support available for analyzing and reporting on the configuration and
associated state information for the managed devices.
This information is stored in the ProVision Plus database, and the configuration analysis and
reporting capabilities are therefore available to the user irrespective of the communication status
with the live network or specific devices.

Note: LICENSING: Configuration management features are only available where the EM
Fault & Performance product module (for directly managed devices) or the EM Integration
For ProVision product module (for devices managed via ProVision EMS) is licensed.
Topics include:
• Network Device Detail (on page 96)
• Network Inventory (on page 98)
• Direct Device Management (on page 100)
• Managing Customized Layouts (on page 102)
• Device Configuration Backup and Restore (on page 103)
• Device Licensing (on page 105)
• Device Software Loading (on page 107)
• Task Manager (on page 111)

Aviat Networks May 2019 95

Configuration Management

Network Device Detail

The Device Detail view provides the user with the following capabilities:
• Tabular view presenting the configuration and state detail for all or a subset of the devices in
the network. This includes the date & time that the information was last updated (i.e.
collected) from each device. A separate row is presented for each physical or logical device
module.
• Analyze the devices using sort and search controls.
• Quick access to other device management capabilities (through the right-click menu
associated with each device object).
The following figure presents an example for two WTM 4100 devices, with the default set of
parameters selected for display.
Figure 68: Example Network Device Detail View

A key is provided at the bottom of the tabular view, indicating the view mode (Live or Baseline), and
the date & time that the view was generated. An example is provided in the following figure.
Figure 69: Example Network Device Detail View Key

Access to Network Device Detail View

The Device Detail view can be accessed as follows:
• Network > Configuration > Device Detail menu
• Configuration > Device Detail right-click menu option associated with a Container object on
the Devices Tree
When accessed from the Network menu, the view is rendered in the fixed right-hand pane, and is
automatically populated with data for all devices in the network.
When accessed from the Devices Tree, the view is rendered in a floating dialog and is
automatically populated with data for the devices within the selected Container.

Network Device Detail View Controls

The figure and table below identify the display areas and controls available in the Device Detail
view.

96 May 2019 Aviat Networks

 Configuration Management

Figure 70: Network Device Detail Controls

Table 30: Network Device Detail Controls

Control Icon Description

Preferences Menu Presents the configuration analysis options for the Device Detail
view, together with the ability to export the data. See the table
below for details.
Generate Button Applies the Preferences Menu parameter selection and View
Mode changes.
The Generate button is highlighted orange when changes have
been entered but not yet applied. Once applied, the orange
highlighting is removed again.
Search A text search can be applied to the tabular view, resulting in only
those rows containing a match being displayed.
Column Sort Sort the tabular view by mouse clicking on a column heading.

Row navigation Provides access to the device management capabilities and

menu views associated with a particular device row, through the mouse
<right-click> menu.
Table 31: Network Device Detail Preferences Menu Options

Control Function
View Mode Provides the user with the following mode selections:
• Live: Presents the latest configuration data collected from the live
network devices, i.e. the Live only data (as opposed to a
combination of Live+Baseline data).
• Baseline: Presents the Baseline only data.
The view defaults to the selection in the Baseline/Live Selector (see
section Baseline Live Selection (on page 116) for details).
Layout Menu Provides the user with the ability to create alternative Device Detail
layouts, which can subsequently be opened without having to
reselect the set of parameters each time. See section Managing
Customized Layouts (on page 102) for details.
General / Inventory / Radio / Provides the user with the ability to select the General, Inventory,
Interface Radio and Interface parameters presented in the tabular view for
analysis. See the Figure below for the available parameters.
Export to CSV / JSON Export the selected parameters for all devices, in CSV or JSON
output format.

Aviat Networks May 2019 97

Configuration Management

Table 32: Network Device Detail Preferences Menu Parameter Selections

General Inventory
Radio parameters: Interface parameters:
parameters: parameters:

Network Inventory
The Inventory view provides the user with a specialized variant of the Device Detail view that
includes the device inventory information for the network. The user is provided with the following
capabilities:
• Tabular view presenting the inventory information for all or a subset of the devices in the
network. This includes the date & time that the information was last updated (i.e. collected)
from each device. A separate row is presented for each physical or logical device module.
• Analyze the inventory using sort and search controls, in order to rapidly identify specific
inventory information. For example to identify all modules of a specific type and hardware
revision.
The following figure presents an example Inventory view.
Figure 71: Example Inventory View

A key is provided at the bottom of the tabular view, indicating the view mode (Live or Baseline), and
the date & time that the view was generated. An example is provided in the following figure.
Figure 72: Example Network Inventory View Key

98 May 2019 Aviat Networks

 Configuration Management

Access to Inventory View

The Inventory view can be accessed as follows:
• Network > Configuration > Inventory menu
• Configuration > Inventory right-click menu option associated with a Container object on the
Devices Tree
When accessed from the Network menu, the view is rendered in the fixed right-hand pane, and is
automatically populated with data for all devices in the network.
When accessed from the Devices Tree, the view is rendered in a floating dialog and is
automatically populated with data for the devices within the selected Container.

Inventory View Controls

The figure and table below identify the controls available in the Inventory view.
Figure 73: Inventory Controls

Table 33: Inventory Controls

Control Icon Description

Preferences Presents the analysis options for the Inventory view, together with the
Menu ability to export the data. See the table below for details.
Generate Button Applies the Preferences Menu parameter selection and View Mode
changes.
The Generate button is highlighted orange when changes have been
entered but not yet applied. Once applied, the orange highlighting is
removed again.
Search A text search can be applied to the tabular view, resulting in only
those rows containing a match being displayed.
Column Sort Sort the tabular view by mouse clicking on a column heading.

Row navigation Provides access to the device management capabilities and views
menu associated with a particular device row, through the mouse
<right-click> menu.
Table 34: Inventory Preferences Menu Options

Control Function
View Mode Provides the user with the following mode selections:
• Live: Presents the latest inventory data collected from the live network
devices, i.e. the Live only data (as opposed to a combination of
Live+Baseline data).
• Baseline: Presents the Baseline only data.
The view defaults to the selection in the Baseline/Live Selector (see
section Baseline Live Selection (on page 116) for details).
Layout Menu Provides the user with the ability to create alternative Inventory layouts,
which can subsequently be opened without having to reselect the set of
parameters each time. See section Managing Customized Layouts (on
page 102) for details.

Aviat Networks May 2019 99

Configuration Management

Control Function
General / Inventory Provides the user with the ability to select the General and Inventory
parameters presented in the tabular view for analysis. See the Figure
below for the available parameters..
Export to CSV / JSON Export the selected parameters for all devices, in CSV or JSON output
format.
Table 35: Inventory Preferences Menu Parameter Selections

General parameters: Inventory parameters:

Direct Device Management

The Direct Device Management view provides the user with the following capabilities:
• Tabular view presenting the ProVision Plus management configuration for all devices in the
network that are directly managed by ProVision Plus, i.e. do not require ProVision EMS for
network mediation.
• Ability to configure the name and management IP address for each device.
• Analyze the devices using sort and search controls.
• Quick access to other device management capabilities (through the right-click menu
associated with each device object).
Note: USER ROLE: A user must have Engineer role access in order to configure the Direct
Device Management settings.
Figure 74: Example Direct Device Management View

Access to Direct Device Management View

The Direct Device Management view is accessed through the Network > Configuration > Direct
Device Management menu.

100 May 2019 Aviat Networks

 Configuration Management

Direct Device Management View Controls

The following table identifies the controls available in the Direct Device Management view.
Table 36: Direct Device Management Controls

Control Icon Description

Preferences Menu Allows the user to select the parameters to be presented in the
Direct Device Management tabular view, together with the ability to
export the data. See the table below for details.
Search A text search can be applied to the tabular view, resulting in only
those rows containing a match being displayed.
Column Sort Sort the tabular view by mouse clicking on a column heading.

Parameter Edit Button Provides the ability to edit the following parameter settings:
• Name: Device name configured on ProVision Plus.
• Management IP Address: The IP address ProVision Plus uses
to communicate with the device. For example, on selecting
the Edit button associated with the Management Name....

…the field becomes editable. The user can then change the
setting and select tick ( ) to complete the edit, or cross ( ) to
cancel.

Row navigation menu Provides access to the device management capabilities and views
associated with a particular device row, through the mouse
<right-click> menu.
Table 37: Direct Device Management Preferences Menu Options

Control Function
Select Enable/disable the ability to compare configuration and state of
selected devices through a specialized variant of the Detail view,
known as the Comparison view. See section Data Panel
Attributes (on page 81) for further information.
Parameter Selection Provides the user with the ability to select the parameters to be
presented in the tabular view for analysis. See section Direct
Device Management (on page 100) below for details.
Export to CSV / JSON / PDF Export the selected parameters for all devices, in CSV, JSON or
PDF output format.

Direct Device Management View Attributes

Table 38: Direct Device Management Attributes

Attribute Description
Live (Model Status) Indicator warning when a change is detected in the Live network that’s
not in the Baseline design, i.e. the Baseline design and Live
configuration for the device differ.
For example, symbol indicates that a new device or service has been
detected in the Live network. See section Live Network Configuration
Change Indicators (on page 117) for a definition of the supported Model
Status indicators.
Name Name of the device that has been configured on ProVision Plus.
Aviat Networks May 2019 101
Configuration Management

Attribute Description
Management State Indicates the current management state of the device.
Where the device is configured as Managed on ProVision Plus, the
Management State is presented as one of the following values:
• Connecting: This transition state is automatically entered when the
device is configured as Managed.
• Managed: This state is automatically entered from either the
Connecting state or Errored state once ProVision Plus successfully
communicates with the device. Fault, configuration and performance
information is periodically collected from the device when in this state.
• Errored: This state is automatically entered from the Managed state
when ProVision Plus is subsequently unable to communicate with the
device.
Where the device is configured as Unmanaged, the ProVision Plus
Management State is presented as Unmanaged. There is no active
communication with the device when in this state.
Management IP Address Management IP address of the device that has been configured on
ProVision Plus. This address is used by ProVision Plus to communicate
with the device.
Type Device type or model (e.g. WTM 4100, WTM 4200, etc.).
Physical Parent The parent container of the device in the Devices Tree.

Managing Customized Layouts

Through the Layout menu, the user is able to create alternative layouts for Device Detail and
Inventory views, each presenting a user-selected set of parameters. This section clarifies the
steps involved in creating and managing user defined layouts.
The following table describes the capabilities provided by the Layout menu.
Table 39: Network Layout Menu

Control Function
Default Layout Resets the view to the default settings, including parameter selection and column
ordering.
Open Presents previously saved customized device layouts as a set of submenu options.
On selection, the saved layout is applied to the Device Detail view.
Save Saves the currently presented parameters selection and column ordering as a
customized Device Detail view on the local client machine.
Delete Deletes the currently viewed customized Device Detail layout. The layout is
removed from the local client machine, and is no longer available for selection.

Procedure: Create a New Layout

The following procedure clarifies the steps involved when creating a new customized layout for the
Device Detail or Inventory view. This capability is available through selecting the required
parameters and column ordering to be presented in the tabular view and saving with a new layout
name.

Step Action
1 Navigate to the view by selecting one of the following:
• Network > Configuration > Device Detail menu
• Network > Configuration > Inventory menu
The default view is presented.

102 May 2019 Aviat Networks

 Configuration Management

Step Action
2 Select the parameters to be presented in the new customized layout, through the General,
Inventory, Radio and Interfaces options in the Preferences pull-down menu ( ).
3 Select the column ordering required through drag and drop of the column headers.
4 Select the Save option in the Layout menu. In the presented dialog, enter a name for the
customized layout and then press the OK button.
5 The name of the new customized layout is now selectable through the Layout > Open
menu.

Device Configuration Backup and Restore

This section describes the capabilities provided for backup of device configurations onto the
ProVision Plus server, together with the ability to subsequently restore a configuration backup to a
device.
Configuration backups are automated, where ProVision Plus periodically checks the managed
devices and automatically backs up a device configuration onto the ProVision Plus server where a
change is detected. Additional backups can also be initiated by the user on demand.
The user can restore a selected backup to a device, either directly from ProVision Plus, or through
exporting the backup to file and restoring onto the device using the device craft tool.

Note: Configuration Backup and Restore is only provided for devices that are directly
managed from ProVision Plus.

Config Backup and Restore

The following figure presents an example Config and Backup Restore dialog for a device, where 4
backups have been collected and stored on the ProVision Plus server.
Figure 75: Example Config Backup and Restore

The device configuration backups are listed in two sections, Automatic Backups and Retained
Backups.

Aviat Networks May 2019 103

Configuration Management

Automatic Backups indicates the last N successful backups automatically read from the device,
where N is the maximum number defined on the Device Config Backup Settings (on page 104)
dialog. Once N backups have been collected for a device, new backups result in the previously
collected backups being automatically purged from the ProVision Plus server.
Retained Backups indicates backups that the user has selected to retain permanently on the
ProVision Plus server. This includes backups initiated by the user on demand, and automatic
backups that the user has subsequently selected to retain.

Note: A configuration backup from WTM 4000 running R2.3 or earlier software is not
supported by a device running R2.4 or later software, and the restored operation is therefore
disallowed.
The controls available with Config Backup and Restore are listed in the table below.
Table 40: Config Backup and Restore Controls

Control Type Function

Backup Now Initiates backup of the device configuration. Backup is performed
irrespective of whether the configuration has changed since the
previous backup.
On completion of downloading the device configuration file, the new
backup is indicated in the Retained Backups section.
Export Downloads the selected configuration backup file from the ProVision
Plus server to the Downloads folder on user’s client machine.
An exported backup can be restored onto the device using the device
craft tool interface.
Restore Restores the selected configuration backup file to the device. The user
is prompted to confirm before the restore takes place.
Retain Allows the user to permanently retain an automated backup on the
ProVision Plus server. This action is only available for automated
backups.
The backup is moved from Automated Backups to Retained Backups,
and is no longer purged when the maximum number of automated
backups is exceeded.
Delete Permanently deletes the selected configuration backup file from the
ProVision Plus server. The user is prompted to confirm before the
deletion takes place.
Description A description can be given to a configuration backup. This is performed
by selecting the Edit button ( ), and entering the required description.
The configuration backup and restore dialog for a device is accessed through the Config Backup
and Restore right-click menu option associated with a device object.

Note: USER ROLE: A user must have Engineer role access in order to access the Config
Backup and Restore feature.

Device Config Backup Settings

The Device Config Backup Settings view provides the user with the ability to enable automated
backup of device configurations. This includes defining how often devices are checked for
configuration change, together with the number of configuration backups to be kept on the
ProVision Plus server for each device.
The following figure presents an example Device Config Backup Settings.

104 May 2019 Aviat Networks

 Configuration Management

Figure 76: Example Device Config Backup Settings

The configurable settings are listed in the table below.

Table 41: Device Config Backup Settings

Field Description
Enable Automatic Provides the ability to Enable/Disable automatic backup of device
Backups configurations. The setting defaults to Enabled.
Automatic Backup Time (in hours) between automatic checking for device configuration
Period changes. The configuration is only backed up on the ProVision Plus
server when a change is detected. The setting defaults to 12 hours.
Maximum Automatic The maximum number of automatic backups kept on the ProVision
Backups Plus server for each device. Once the maximum is reached for a
device, a new backup results in the oldest backup being purged from
the ProVision Plus server. The setting defaults to 5.
Save Applies the changes in settings, and persists the changes to the
ProVision Plus database.
Defaults Resets all Configuration Backup Settings to their default values.
The configuration backup settings view is accessed through the Admin > Device Config Backup
Settings menu.

Note: USER ROLE: A user must have Engineer role access in order to change the
configuration backup settings.

Device Licensing
The Licensing view provides the user with the following capabilities:
• Tabular view presenting all devices that have unlicensed features.
• Ability to register licenses for devices on the ProVision Plus server.
• Ability to activate trial licenses on devices.
• Ability to apply registered licenses to devices.
Note: USER ROLE: A user must have Engineer role access in order to access this view.

Aviat Networks May 2019 105

Configuration Management

Access to Licensing View

The Licensing view is accessed through the Network > Configuration > Licensing menu.
Figure 77: Example Licensing View

Licensing View Controls

The following table identifies the controls available in the Licensing view.
Table 42: Licensing Controls

Control Icon Description

Activate Trial Selecting Activate Trial opens the Licensing Task dialog (see below for
details) with the following header:

The Activate Trial button is only presented after selecting a device (using the
tick box) with "Trial Features" available on the device.
Apply License Opens the Licensing Task dialog (see below for details), allowing the user to
apply licenses to devices.
When this button is clicked, the Licensing Task dialog is displayed (see
below for details).
The Apply License button is only presented after selecting a device (using
the tick box) with "New Features" registered on the Provision Plus server.
Register Allows the user to select device license files for registering on the Provision
License Plus server.
Where the selected license files contain new features not yet licensed on the
managed devices, these features are presented in the New Features column.
Filter table rows Filters the tabular view. The available selections are as follows:
• All – Presents all devices that Provision Plus can manage licensing for.
• New Feature – Presents devices for which there are new features
registered, however the features are not yet applied to the devices.
• Trial – Presents devices that have trial licenses applied, however not yet
activated.
• Unlicensed – Presents devices with features defined as unlicensed.
• No Action – Presents devices for which there are no new license
features and no trial licenses to apply.
By default, the Unlicensed option is selected.
Search A text search can be applied to the tabular view, resulting in only those rows
containing a match being displayed.

106 May 2019 Aviat Networks

 Configuration Management

Control Icon Description

Select Devices are selected through the tick box mechanism in the first column of
the table. This allows the user to select one or more devices.
Selecting a device with "Trial Features" available results in the Activate Trial
button being presented and selecting a device with "New Features" available
results in the Apply License button being presented.
Column Sort Sort the tabular view by mouse clicking on a column heading.

Task This icon is presented when a licensing task is currently running against this
device. The device is not selectable (through the tick box) until the licensing
task completes.
Detail Opens the Device Detail dialog with the Licensing tab open.
Where mode is selected, the differences between
registered licenses and licenses currently on the device are presented in the
Device Detail.
Where mode is selected, only the registered licenses are
presented in the Device Detail.

Licensing Task Dialog

When the Activate Trial or Apply License button is selected, the Licensing Task dialog is presented.
Figure 78: Example Licensing Task Dialog

Table 43: Licensing Task Dialog Controls

Control Icon Description

Description Optionally enter a description to be presented in the Task Manager view

or leave the default description unchanged.
Open in task When selected, the Task Manager view will be opened with this task
Manager selected, when the OK button is selected.
OK When the OK button is selected, the license task is sent to the Task
Manager.
Cancel When Cancel is selected, the dialog is closed with no action taken.

Device Software Loading

The Software loading view provides the user with the following capabilities:
• Tabular view presenting all devices to be software loaded.
• Ability to register software on the ProVision Plus server.
• Ability to load software onto one or more devices.
• Ability to rollback to previous software should a failure occur during software loading.

Aviat Networks May 2019 107

Configuration Management

Software loading a device is broken into two tasks:

1. Software Transfer: Looks after transferring the selected software onto the device.
2. Software Activation: Looks after activation and rollback of the selected software.
Software Transfer is s precursor task to Software Activation, i.e. Software Activation will not run until
Software Transfer has completed.

Access to Software Loading View

The Software Loading view is accessed through the Network > Configuration > Software
Loading menu.

Note: USER ROLE: A user must have Engineer role access in order to access this view.
Figure 79: Example Software Loading View

Software Loading View Controls

The following table identifies the controls available in the Software Loading view.
Table 44: Software Loading Controls

Control Icon Description

Load Software Selecting Load Software opens the Task dialog with the following header.
See section Licensing Task Dialog (on page 107) for details on the Task
dialog.

The Load Software button is only enabled once software loading has
been configured, and one of more devices that support the software
product and version have been selected.

108 May 2019 Aviat Networks

 Configuration Management

Control Icon Description

Register Software Allows the user to select the device software files to be registered on the
ProVision Plus server.
Search A text search can be applied to the tabular view, resulting in only those
rows containing a match being displayed.
Product Allows the user to select the software product to be loaded.
Each software product supports a specific device platform, or a subset of
the device variants of a platform. For example, software product
"wtm4100" version 2.4.0 supports 4100, 4200, 4500 and 4500T variants
of the WTM 4000 platform.
Version Allows the user to select the version of the software product to be loaded.
The list of software versions registered on the ProVision Plus server are
available for selection, with latest versions presented first in the picklist.
Note: Different software versions may support different subsets of
a device platform’s variants. Where a selected version is not
supported by a device, a is presented beside the active version
for that device.
Remove Allows the user to remove the selected registered software version from
the ProVision Plus server.
Show Devices Presents all the devices that support the selected software product and
version.
Alternatively, the user can select specific devices for through the Tree
Context Selector controls. See section Tree Context Selector (on page
82) for details.
Max Concurrent Defines the maximum number of software transfers that can take place
concurrently for the task.
Transfer time Allows the user to define when the software transfer takes place. The
available selections are as follows:
• Manually – Allows the user to start the transfer on-demand.
• Later – Allows the user to define the date and time at which the
transfer takes place.
• Immediately – Start the transfer straight away (when the task is
created in Task Manager)
By default, the Immediately option is selected.
Activate time Allows the user to define when the software activation takes place. The
available selections are as follows:
• Manually – Allows the user to start the activation on-demand.
• Later – Allows the user to define the date and time at which the
activation takes place.
• After Transfer – Start the activation immediately after the transfer is
complete.
By default, Manually option is selected.
Global Rollback Allows the user to define the rollout behaviour to be applied by all
Software Activation tasks.
When Global Rollback is enabled (through the tick box), rollback to the
previous software for all devices in the task takes place where software
activation for any of the devices doesn’t occur within the specified "Within
minutes" time.
When Global Rollback is disabled, no rollout occurs irrespective of a
device failing to activate the software.

Aviat Networks May 2019 109

Configuration Management

Control Icon Description

Within minutes The number of minutes allowed for software activation to take place on all
devices in a task.
This field is only presented when Global Rollback is enabled (through the
tick box).
Apply Now Immediately applies the changes to the Global Rollback settings.
The Apply Now button is only presented when changes have been made
to the settings and have not yet been applied.
Column Sort Sort the tabular view by mouse clicking on a column heading.

Detail Opens the Device Detail dialog with the Software tab presented.
The Detail button is only presented when mode is
selected.
Remove Allows the user to remove the device from the table.

Load Software Task Dialog

When the Load Software button is selected, the Task dialog is presented. See section Licensing
Task Dialog (on page 107) for details.

Software Loading Device Table

The order of the devices in the table represents the order in which Software Transfer and Software
Activation will occur.
Devices can be added to the table by the following methods:
•Selecting the Show Devices button. The presents all devices that support the selected
software product and version and are not currently running this version.
• Selecting specific devices through the Tree Context Selector controls. See section Tree
Context Selector (on page 82) for details. This method provides the ability to select specific
devices. When using this method, any devices previously selected through the Show
Devices button are removed from selection.
The following controls are provided:
• Column sort through mouse clicking the column header.
• Reordering of rows through drag and drop to the desired row position.
Figure 80: Example Software Loading Device Table

The following table describes the fields in the software loading device table.

110 May 2019 Aviat Networks

 Configuration Management

Table 45: Software Loading Device Table Fields

Field Icon Description

Software Indicates when there is currently a software loading task active in the Task Manager
loading task for this device.
indicator When the icon is presented, the Load Software button is disabled.
Device state Indicates the device is currently unmanaged or loss of comms.
indicator
Device The name of the device.

Type The device platform variants supported by the selected software product and version,
e.g. WTM4100, WTM4200, WTM4500 and WTM450T variants are supported by the
"wtm4100" software product.
Active Version Presents the currently active (running) software version in the device.

Version action Presents the action that will occur from a software version perspective.
indicator = The software will be downgraded.
= The software will be upgraded.
= The software is not compatible with the device.
(blank) = The software is active, however has not been Acknowledged. This can occur
where activation has been performed using the device craft tool, without
Acknowledging on activation completion. See the device help documentation for
details.
(blank) = The software is active and acknowledged.
Inactive Version Presents the inactive software version in the device.
Where this is the version you wish to load, this can be performed through Software
Activation without first performing Software Transfer, as the software version is
already on the device.
Detail Opens the Device Detail dialog with the Software tab presented.
The Detail button is only presented when mode is selected.
Remove Allows the user to remove the device from the table.

Task Manager
The Task Manager view provides the user with the following capabilities:
• Tabular view presenting all tasks in the Task Manager.
• Ability to run actions on a task.
• Ability to monitor progress of a task.
• Ability to view details of a task.
Note: USER ROLE: Operator and Engineer users have access to the Task Manager and
can view details about each task, however a user must have Engineer role access in order to
execute actions on a task.
Table 46: Task Manager Progress Indicator

Progress Description

The task has not started.

The task has started and the % completion of the task is known.

Aviat Networks May 2019 111

Configuration Management

Progress Description

The task is attempting to run however devices are not in a ready state or device
comms has been lost.
The device problem needs to be resolved, and then the user can Retry the task.
The identified radio has reported an unexpected state condition. Retry the
operation and if the problem persists, attempt to apply the operation using the
device craft tool.
The task has failed. The user can either Retry or Delete the task.

The task has completed successfully, and the user can Delete the task.

Access to Task Manager View

The Task Manager view is accessed through the Network > Task Manager menu.
Figure 81: Task Manager View

Task Manager View Controls

The following table identifies the controls available in the Task Manager view.
Table 47: Task Manager Controls

Control Icon Description

Delete Provides the user with the ability to delete all successfully completed tasks
Successful where all successor tasks have been successfully completed.
Search A text search can be applied to the tabular view, resulting in only those rows
containing a match being displayed.
Column Sort Sort the tabular view by mouse clicking on a column heading.

112 May 2019 Aviat Networks

 Configuration Management

Control Icon Description

Retry Provides the ability to Retry a running task where the task has failed, loss of
comms with the device has occurred, or the device is not ready.
When the task is retried, the Task Manager reads the state of all the devices
and if none are loss of comms the task will restart.
Abort Provides the ability to Abort a running task where none of the devices are
restarting.
On Abort completion the task is set to failed, and the user can then Retry or
Delete the task.
Start Provides the ability to start the task manually, where the task is set to Manual
and not yet started.
The start button is only presented in this situation.
Delete Provides the ability to Delete the task. This is only supported where the task
is in one of the following states and there are no successor tasks:
• Failed
• Not Started
• Waiting
• Invalid State
• Loss of Comms
• Not Ready
Log Opens the Task Log dialog. See section Task Log Dialog (on page 113)
for details.
When a task is selected, a table of devices is presented with a Detail button for each device. The
Detail button opens the Device Detail dialog with the relevant tab opened.
The following table identifies the controls available in the Task Manager view when a task is
selected that has not been started.
Table 48: Task Manager Detail Control

Control Icon Description

Precursors Provides the ability to select / unselect tasks that need to

complete before this task starts.

Start Allows the user to define when the task starts. The available
selections are as follows:
• Manually – Allows the user to start the task when the Start
button is pressed.
• Later – Allows the user to define the date and time at
which the task automatically starts.
Save Allows the user to apply the changes to the task.
changes
Cancel Allows the user to cancel the current changes to the task.

Task Log Dialog

The following figure presents an example Task Log dialog.

Aviat Networks May 2019 113

Configuration Management

Figure 82: Task Log Dialog

The upper table presents details on the selected task. This includes the details available in the
Task Manager view, together with the following additional fields:
• Concurrent: Indicates the number of subtasks currently running.
• Max Concurrent: Indicates the maximum number of concurrent subtasks supported.
The lower table presents a log of the actions associated with the selected task. The following
types of entry are captured in the log:
• Subtask: This is typically a Netconf Action sent to an individual device.
• Task: A task may have multiple phases. For example, the Transfer Software task has
phases "Load Software", "Load Error" and "Resetting Error". A separate log entry is created
for each phase.
The following table describes the Task Log fields.
Table 49: Task Log Table Fields

Name Description

Action For a subtask entry, this typically indicates a Netconf protocol Action. For a task
entry, this field is blank.
Error Indicates an error occurred during execution of the subtask. The perceived
severity of the error is indicated (critical, major, minor, or warning).
Message This is the message returned from the action sent to the device or the task phase
to be applied to "All" devices.
Date The date and time the task or subtask was executed.

Device Name of the device to which the subtask applied. This field indicates All for a
task entry.
Subtask # Indicates the order of execution of the subtasks. This field is left blank for task
entry.

114 May 2019 Aviat Networks

 Managing Network Configuration Changes

Chapter 7. Managing Network Configuration

Changes
This section describes how ProVision Plus automatically identifies configuration changes made to
devices or end-to-end services in the Live network, and the capabilities available to the user to
manage the detected changes.
The Baseline design provides a benchmark configuration for the complete network, including the
devices and services (for example L1 Links, VLAN or L2VPN services).
Any service with configuration deviating from the Baseline design is visually highlighted, and details
of the configuration change displayed. Through this mechanism, configuration changes can be
quickly audited and validated to prevent human mistakes and unauthorized changes, avoiding
costly issues downstream.
In summary, the following features provide support for this capability:
• Monitoring live network for configuration changes (on page 116)
• Baseline / live configuration (on page 116)
• Live network configuration change indicators (on page 117)
• Reconciliation Report (on page 118)
• Promoting live network changes to baseline (on page 118)

Aviat Networks May 2019 115

Managing Network Configuration Changes

Monitoring Live Network for Configuration Changes

Configuration changes made to the devices in the Live network are detected through the following
mechanisms:
• Processing of device configuration change notifications. This results in quick detection of
changes.
• Regular background polling of device and service objects in the network for configuration
changes. For directly managed WTM 4000 devices, this occurs every hour. For CTR 8540
devices managed via ProVision EMS, this occurs every 6 hours. As there is a considerable
amount of data to read in order to detect changes.
Warning: CTR 8540 devices only generate configuration change syslog notifications when
the changes are saved (persisted) on the device. In the case where changes are not saved,
there will be a delay in discovery until the next background configuration collection poll
occurs. It’s therefore important to save changes to device configuration as soon as the
changes are complete.

Baseline / Live Selection

The topology view (including Topology Map, Data Panel and Tree Context Selector) and Detail view
presents either “Live + Baseline” or “Baseline” information depending on the chosen Baseline/Live
Selector setting.
Selection of “Live + Baseline” provides the ability to identify configuration changes to devices and
end-to-end services in the Live network, whereas “Baseline” provides the ability to view the
Baseline design configuration only.
The table below identifies the available settings and the information presented with each.
Figure 83: Baseline/Live Selector

Table 50: Topology View Baseline/Live Selection

Setting Information presented

Baseline Baseline design, i.e. the configuration data for the network devices and
end-to-end services that represents the expected configuration of the network.
As ProVision Plus currently supports configuration discovery only (i.e. doesn’t
yet support network provisioning), the Baseline design has been established
through the user explicitly accepting (promoting) the discovered Live
configuration (into the Baseline design configuration).
Live + Baseline Combined view of Live configuration (including state information) with the
Baseline design configuration information.
Live represents the configuration and state of the network in its current
operational state. State information includes event/alarm indicators.
This combined view presents the Live information and highlights differences
with the Baseline design through a set of Live network configuration change
Indicators (Model Status). See section Live Network Configuration Change
Indicators (on page 117) below for details.

116 May 2019 Aviat Networks

 Managing Network Configuration Changes

Live Network Configuration Change Indicators

A Live network configuration change indicator (referred to as a Model Status indicator) is displayed
with each device and end-to-end service object in the Topology Map, Data Panel and Tree Context
Selector.
Figure 84: Example Model Status Indicators

Tree Context Selector: Data Panel: Topology Map:

Table 51: Model Status Indicators

Indicator Description
The device or end-to-end-service object is in the Baseline design, however is
Not in Live ( )
not in the Live network.
Probable cause(s):
• Device has been removed from the ProVision mediation system’s
topology.
• End-to-end service has been removed from the configuration of one or
more devices in the network.
Proposed action(s):
• If planned, the change should be explicitly promoted to the Baseline
design. See section Promoting Live Network Changes to Baseline (on
page 118) for details.
• If unplanned (unauthorized or accidental), resolve on ProVision mediation
system or configuration of devices in the network.
The device or end-to-end-service object is in the Live network only, i.e. is not
In Live Only ( )
in the Baseline design.
Probable cause(s):
• New device deployed in ProVision mediation system’s topology.
• New end-to-end service has been configured on one or more devices in
the network.
Proposed action(s):
• Assuming the change is planned, promote to the Baseline design. See
section Promoting Live Network Changes to Baseline (on page 118) for
details.
Configuration Differs The configuration of a device or end-to-end service object in the Live network
differs from the configuration in the Baseline design.
( )
Probable cause(s):
• Configuration attributes of the device or service object have been changed
in the Live network.
Proposed action(s):
• If planned, promote to the Baseline design. See section Promoting Live
Network Changes to Baseline (on page 118) for details.
• If unplanned (unauthorized or accidental), resolve by undoing the
configuration changes on the network devices.

Aviat Networks May 2019 117

Managing Network Configuration Changes

Reconciliation Report
The Reconciliation Report provides the user with a list of the inconsistencies (or misconfiguration
issues) detected in the Live network.
The following figure presents an example Reconciliation Report with a L2VPN inconsistency.
Figure 85: Example Reconciliation Report

The following table describes the parameters presented with each inconsistency.
Table 52: Reconciliation Report Parameters

Name Description
ID ID generated by ProVision Plus for display purposes only. When combined
with the other fields, this ensures each row is unique.
Rule Identifies the inconsistency rule not adhered to. The supported rules are
listed in the table below.
Summary Summary description of the inconsistency.
Description Fuller description of the inconsistency, indicating the change required in order
to resolve the issue.
Inconsistent Objects Names of the device or service objects exhibiting the inconsistency.
Data Origins Names of the device objects from which the inconsistent data has been
obtained.
The following table presents the set of inconsistencies that are currently detectable.
Table 53: Reconciliation Report Detectable Inconsistencies

Inconsistency Rule Description

Duplicate IP Address Duplicate IP addresses detected in the network. IP addresses should be
unique across the network.
TE Link with non-local A TE Link is misconfigured with an IP address for the local end that doesn’t
IP Address reside on the device.
TE Link remote IP A TE Link is misconfigured. Either the remote IP address does not exist on
Address a managed device, or the remote IP address and remote router ID are not
on the same remote managed device.
L2VPN Service Type The type of L2VPN PW service should be configured as either Ethernet or
Inconsistency TDM at both ends. There is a mismatch, where the PW service type differs
at both ends.
L2VPN Signaling Type The signaling type for a L2VPN PW should be configured as either
Inconsistency ldp-signaled or static at both ends. There is a mismatch, where the type
differs at both ends.
Note: For a Targeted-LDP signaled PW, the type is ldp-signaled.
Access to the Reconciliation Report is available through selection of the Network > Reconciliation
Report menu option.

Promoting Live Network Changes to Baseline

Configuration changes detected to devices and end-to-end services in the Live network are
promoted to the Baseline design through selection of the Network > Create Baseline menu option.

118 May 2019 Aviat Networks

 Managing Network Configuration Changes

Figure 86: Create Baseline

Once the changes have been promoted, the Baseline design is now in sync with the Live network
configuration, and the Live network configuration change indicators (Model Status) should clear.

Aviat Networks May 2019 119

 Event Alarm Management

Chapter 8. Event Alarm Management

ProVision Plus automatically monitors the network devices and end-to-end services for faults, and
intelligently correlates detected faults with its accurate and up-to-date model of the network
topology for each supported layer.
This ability to automatically correlate events and alarms to the correct layer, combined with the
ability to view and navigate the layers through the available network topology views, assists with
rapidly isolating the root cause and verifying the fault resolution, resulting in efficient
troubleshooting.
This section describes the event and alarm management capabilities provided in support of fault
management. Topics include:
• Introduction to events and alarms (on page 122)
• Event browser (on page 125)
• Alarm status indicators (on page 131)
• Network alarm indicators (on page 132)

Aviat Networks May 2019 121

Event Alarm Management

Introduction to Events and Alarms

Events and Alarms
The terms events and alarms are often used interchangeably.
Events are detected from the network devices through either SNMP traps, syslog notifications or
status polling, and provide information associated with fault conditions, status changes,
configuration changes and user actions. For example, “a user has logged into a device” is
considered an event.
Each alarm describes a fault condition and is derived from a sequence of one or more events. For
example, “a wireless link has failed” is considered an alarm.
In ProVision Plus, events and alarms have the same set of attributes, including a severity
value. However whereas an active alarm can have a severity value of Critical, Major, Minor or
Warning, to describe the seriousness of the fault condition, an active event typically has severity
Informational.

Devices Events and Alarms

Events and alarms detected from the network devices are automatically correlated to the entities
that make up the device, i.e. chassis/mainboard, plugins or modules, and interfaces.
The term Devices Alarms is used to describe the alarms detected from the network devices.

Services Alarms
A common set of service-centric alarms (Services Alarms) are implemented for most end-to-end
services in ProVision Plus’s model of the network topology, hence are provided for each IP/MPLS,
Carrier Ethernet, and physical L1 Link service.
The state of the Services Alarms is determined by automatically correlating the Devices Alarms
detected from the network with the services in the network topology model.
The table below indicates the common Services Alarm types. See section Services Alarms
Reference for a more detailed and accurate definition of the Services Alarms supported at each
layer, and description of the correlation of Devices Alarms.
Table 54: Services Alarm Types

Alarm Type Description

Service down Indicates that one or more traffic affecting fault conditions are active for a
specific service.
For example, a “VPN service down” alarm is raised when a configured
L2VPN or L3VPN AC (Attachment Circuit) interface is down.
Service degraded Indicates loss of protection at the reported service layer or at a supporting
service layer.
For example, a “TE Tunnel degraded” alarm is raised when a TE Tunnel
Working or Protecting LSP fails for a TE Tunnel 1:1 protection
configuration. And a “PW degraded” alarm is raised where a supporting
TE Tunnel is degraded.
Service fault This is used to indicate all other fault conditions (other than traffic affecting)
for a specific service.
For example, a “L1 Link service fault” alarm is raised when a configured
network facing Ethernet interface or radio interface is down.

122 May 2019 Aviat Networks

 Event Alarm Management

Alarm Type Description

Service supporting Indicates that a supporting layer is admin disabled (i.e. administratively
layer admin disabled configured as disabled).
For example, a “VPN supporting layer admin disabled” alarm is raised
when a supporting TE Tunnel is admin disabled.
Service admin disabled Indicates that a service is admin disabled.
For example, a “TE Tunnel admin disabled” event is raised when a tunnel
is configured however is administratively disabled. This is raised as a
severity Informational event, to assist with identifying the root cause of
dependent (upper) layer service faults.

Services Alarms Propagation Behavior

Services alarms are propagated to dependent (upper) layer service alarms.
For example, in a traffic engineered network delivering L2VPN services over 1:1 protected TE
Tunnels, a “L1 link down” alarm would result in the following alarms being raised against any
dependent (upper) layer services:
• TE Link down
• TE Working or Protecting LSP down
• TE Tunnel degraded
• PW degraded
• L2VPN service degraded

Attributes of Events and Alarms

All events and alarms presented in ProVision Plus contain the set of attributes identified in the table
below.
Table 55: Event / Alarm Attributes

Attribute Description
Severity Perceived severity value. Based on reference ITU-T X.733.
Supported values and a summary of their meaning are as follows:
• Critical :- A traffic affecting condition is active
• Major :- A potentially traffic affecting condition is active
• Minor :- A non-traffic affecting condition is active
• Warning :- A minor fault condition is active
• Cleared or Normal :- No fault condition is active
• Informational :- Informational only event (not a fault condition)
See section Severity Color Coding for Events and Alarms (on page 125) for
a definition of the colors used to indicate each severity value.
Active (state) Supported event/alarm states are Active (meaning up) or Cleared (meaning
down or inactive).
Events that are considered informational only (e.g. user logged into device)
only have state Active.

Aviat Networks May 2019 123

Event Alarm Management

Attribute Description
Acknowledged Indicates whether the event/alarm has been acknowledged by the user.
For indirectly managed devices the Acknowledged / Unacknowledged setting is
discovered from ProVision.
Indicates whether the event/alarm has been acknowledged by a user in the
ProVision mediation system.
Supported values are as follows:
• Acknowledged
• Unacknowledged
Event (name) A short descriptive name that uniquely identifies the type of event/alarm.
Object Identifies the managed object that the event/alarm is associated with:
• For a device the format is [<device-name>/<plugin>]<interface>.
• For a service the format is <service-name>.
Raised (date/time) Date and time that the event/alarm was detected:
• For a device, this reflects the time that the device detected and generated
the event (i.e. the device generates this timestamp).
• For a service, this reflects the time that detected the fault and raised the
event (i.e. generates this timestamp).
Cleared Date and time that the event/alarm was cleared:
(date/time) • For a device, this reflects the time that the device detected the clearing
condition (i.e. the device generates this timestamp).
• For a service, this reflects the time that ProVision Plus detected the clearing
condition (i.e. generates this timestamp).
Cause Provides a brief description of the probable cause.
Category Categorizes events and alarms into different types. Based on reference ITU-T
X.733.
Supported values are as follows:
• Communication
• Environmental
• Equipment
• Processing Error
• Quality of Service
• Security
• MPLS

124 May 2019 Aviat Networks

 Event Alarm Management

Severity Color Coding for Events and Alarms

The table below identifies the color used to indicate each severity value. This color coding is used
uniformly in the various types of supported event/alarm indicators.
Table 56: Event / Alarm Severity Color Coding

Severity value Color coding

Critical Red
Major Orange
Minor Yellow
Warning Blue
Cleared or Normal Green
Informational White

Event Browser
The Event Browser provides the ability to view events and alarms detected from the network
devices and services in a tabular view.
In summary, the user is provided with the following capabilities:
• Tabular view presenting the history of detected events and alarms associated with devices
and services.
• Analyze the events using sort and search controls.
• Mark events as acknowledged.
• Manually clear events.
• Customize the view, and save for future access.
• For a selected event, locate the device or service in the Topology Map.

Event Browser Areas and Controls

The figure and table below identify the display areas and controls available in the Event Browser
view.
When acknowledging (or unacknowledging) an event, the user can optionally add a short
descriptive note to be associated with the event. The note is captured in the event browser Notes
field for all users to view.
In this particular example the active events for all devices in the network are presented.
Figure 87: Event Browser Areas

Aviat Networks May 2019 125

Event Alarm Management

Table 57: Event Browser Areas

Area Description
Event Browser Identifies the title of the Event Browser view.
Title When viewing a customized browser filter, this reflects the name defined by the user
when the filter configuration was saved. See section Acknowledge Event (on
page 126) below for further details.
Events Table Presents the events history in a tabular format.
The columns included are determined by the Events Browser configuration. See
section Acknowledge Event (on page 126) below for details.
Pagination is enabled when there are more events than fit the display.
Events Summarize the total numbers of active alarms by severity. Separate indicators are
Summary
Indicators provided for Critical, Major and Minor severity. For example,
indicates that 2 x Critical and 8 x Major severity alarms are active.
Table 58: Event Browser Controls

Control Icon Description

Column Sort Sort the tabular view by mouse clicking on a column heading.

Events Search Searches for and displays only those events (table rows) containing
the entered text.
The search is applied to all event attributes, including attributes that
are currently not enabled for display (through the Events Browser
configuration settings).
Browser Filter Toggle control, enabling/disabling access to the browser filter
Configuration configuration settings. See section Acknowledge Event (on page
126) below for details.
Browser Saved Dropdown menu providing access to previously saved browser filter
Filters configurations.
Row navigation Provides access to the management capabilities and views
menu associated with a particular event row, through the mouse
<right-click> menu.

Acknowledge Event
Acknowledging an event notifies other operators that the event is currently being handled.
The Event Browser provides the user with the ability to acknowledge events that are raised against
directly managed devices and service events derived by ProVision Plus. This is available through
the Acknowledge right-click menu option associated with each event. Acknowledged events can
be unacknowledged through the same menu option.
The acknowledged setting is presented in the Event Browser by default, through the Ack column.
Figure 88: Example Event Browser with Acknowledged Events

Note: Acknowledge of events raised against indirectly managed devices (i.e. devices
managed via ProVision) is not supported. This can only be performed in ProVision, resulting
in the acknowledge state being imported and reflected in ProVision Plus.

126 May 2019 Aviat Networks

 Event Alarm Management

Note: USER ROLE: A user must have Operator role access in order to acknowledge /
unacknowledged events.

Manually Clear Event

Active events are typically automatically cleared by the device, when the problem on the device is
resolved. Occasionally however, the device may not clear an active event (e.g. in the case of a
device failure condition), leaving manual clearing by the ProVision Plus user as the only option.
The Event Browser provides the user with the ability to manually clear an active event that is raised
against a directly managed device. This is performed through the Clear right-click menu option
associated with each event. This results in clearing of the current instance of the active event.

Note: Manual clearing of device events raised against indirectly managed devices (i.e.
devices managed via ProVision) is not supported. This can only be performed in ProVision,
resulting in the acknowledged state being imported and reflected in ProVision Plus.
Note: Manual clearing of service events is not supported. As service events are
automatically derived from the state of the dependent device events, they are cleared when
all active dependent device events are cleared.
Note: USER ROLE: A user must have Engineer role access in order to manually clear
events.

Event Browser Filter Configuration

The following Event Browser settings are user configurable for inclusion in a browser filter:
• Event attributes columns.
• Event attributes states or values.
• Date ranges for Raised (transition to active) or Cleared events.
The figure and table below identify the display areas and configurable settings available.
Figure 89: Event Browser Filter Configuration Areas

Aviat Networks May 2019 127

Event Alarm Management

Table 59: Event Browser Filter Configuration Areas

Area Description
Filter Configuration The configurable settings are broken down into the following groups, each
Tabs accessible via a separate filter configuration tab.
• Simple – Filter based on attribute values
• Date – Filter based on date range(s)
• View – Select the columns and max events in the event view
Filter Configuration Presents the user configurable event attributes for a given settings type
Settings (filter configuration tab), and provides the user with the ability to determine
the events to be displayed in the browser based on the attribute values.
For example, only display events with the State attribute value Active and
Severity attribute value Critical.
Table 60: Event Browser Filter Configuration Controls

Control Icon Description

Filter Name Identifies the name of the browser configuration filter.

Apply filter Selecting the Apply button immediately applies the changes
made (on any of the filter configuration tabs) to the viewed
Event Browser.
Note: Selecting the Apply button does not save the
changes.
Save filter Selecting the Save button immediately saves the changes
made (on any of the filter configuration tabs) to the filter
identified by the Filter Name field.
To create a new browser configuration filter, edit the Filter
Name before selecting the Save button.
Note: Select the Save button does not apply the
changes to the viewed Event Browser.

Note: Customized browser filters are saved on the client machine for personal use.

Managing Customized Event Browser Filters

This section clarifies the steps involved in creating and maintaining customized Event Browser
filters.

How to Create a New Customized Event Browser Filter

The following procedure clarifies the steps involved when creating a new Event Browser filter. This
capability is available through editing an existing Event Browser filter and saving with a new Filter
Name.

Step Action
1. Open an Event Browser.
2. Select the Browser Filter Configuration toggle button (), and make the desired
changes/edits to the Filter Configuration Settings on each tab.

128 May 2019 Aviat Networks

 Event Alarm Management

Step Action
3. Check the desired changes by selecting the Apply button, to immediately apply the
changes to the viewed Event Browser.
The Apply button is now highlighted dark blue:

And the changes are now reflected in the viewed Event Browser.
4. Edit the Filter Name to reflect the behavior of the new Event Browser filter.

5. Select the Save button to immediately save the new Event Browser filter.
The Saved button is now highlighted dark blue.

And a system message confirms when the save has successfully completed.

How to Delete a Customized Event Browser Filter

The following procedure clarifies the steps involved when you wish to delete a previously created
Event Browser filter.

Step Action
1. Open an Event Browser.
2. Select the existing customized Event Browser filter to be deleted, from the Browser Saved

Filters dropdown menu control ( ).

The Filter Name field is updated with the name of the selected filter.

3. Select the Save button.

The Delete button is now available for selection.

4. Select the Delete button.

A confirmation prompt is then presented.

5. Select the OK button.

A system message confirms when the delete has successfully completed.

Services Alarms Root Cause Devices Alarms

As described in section Services Alarms, the Services Alarms are derived by automatically
correlating the devices events and alarms detected from the network with the end-to-end services in
ProVision Plus's model of the network topology.
To assist with troubleshooting reported Services Alarms, the Event Browser provides the ability to
instantly identify any root cause Devices Alarms.
Aviat Networks May 2019 129
Event Alarm Management

To illustrate this capability, the figure below presents the example where a traffic affecting fault is
reported for a L3VPN service. In this example the Event Browser indicates service "L3VPN 1" has
a Critical severity "VPN service down" alarm active. By clicking the symbol prefixing the service
alarm name, it can be seen that the fault is due to Ethernet AC (Attachment Circuit) port down on
PE router service access node "10.18.47.2 - CTR 8540".
Figure 90: Example Services Alarm Root Cause

Event Browser: Topology Map:

Access to the Event Browser

The Event Browser can be accessed by a number of different means:
• Network Devices and Network Services Alarm Indicators on the Menu / System Status Bar
• Device and service objects right-click menu
• Network > Events > Event Browser main menu selection
• Network > Events > Show Event Browser Dock main menu selection
The browser configuration filter that’s applied when opening the Event Browser reflects the context
associated with how it was accessed. For example, when opening the Event Browser from a
specific device object on the Topology Map, the filter is set to display only the events and alarms
associated with that specific device.
Table 61: Event Browser Access and Context Filter

Access Icon Context filter applied to Event Browser

Network Devices Alarm Selecting the indicator renders a dropdown menu containing the severity
Indicator values for which there are one or more currently active Devices Alarms.
Selecting one of the presented severity values applies the following filter:
• All devices in the network
• State = Active
• Severity = <selected value>
• Device/Service layer = Device
See section Device Alarm Status Indicators (on page 131) for further
details on the Network Devices Alarm Indicator.
Network Services Alarm Selecting the indicator renders a dropdown menu containing the service
Indicator layers with one or more currently active Service Alarms.
Selecting one of the presented layers applies the following filter:
• All services in the network
• State = Active
• Severity = Critical, Major, Minor, Warning
• Device/Service layer = <selected service layer>
See section Service Alarm Status Indictors (on page 132) for further
details on the Network Services Alarm Indicator.

130 May 2019 Aviat Networks

 Event Alarm Management

Access Icon Context filter applied to Event Browser

Device object right-click - The following filter is applied:
menu • The selected device
• State = Active
• Severity = Critical, Major, Minor, Warning
Devices container object - The following filter is applied:
right-click menu • All devices in the selected container (e.g. in a selected Site)
• State = Active
• Severity = Critical, Major, Minor, Warning
Service object right-click - The following filter is applied:
menu • The selected service
• State = Active
• Severity = Critical, Major, Minor, Warning
Services layer object - The following filter is applied:
right-click menu • All services of the selected layer type (e.g. all TE Tunnel services)
• State = Active
• Severity = Critical, Major, Minor, Warning
Network / Events menu - The following filter is applied:
selection • All devices and services
• State = Active
• Severity = Critical, Major, Minor, Warning
Network > Events > - The following filter is applied:
Show Event Browser • All devices and services
Dock main menu • State = Active
selection
• Severity = Critical, Major, Minor, Warning

Alarm Status Indicators

Alarm status indicators are provided with each device and service object presented in the topology
view Topology Map, Data Panel and Tree Context Selector panes.

Device Alarm Status Indictors

Each Device Alarm Status indicator represents the highest severity of the alarms currently active on
a specific device.
See section Attributes of Events and Alarms (on page 123) for definition of the supported severity
values, and section Severity Color Coding for Events and Alarms (on page 125) for a definition
of the severity color coding.
The figure below presents the different style indicators available on the various panes.
Figure 91: Device Alarm Status Indicators

Context Selector: Devices Tree Data Panel: Topology Map:

Aviat Networks May 2019 131

Event Alarm Management

As displayed in the Context Selector Devices Tree example above, indicators are also provided for
the device interface plugins (physical or logical), in this case ETHERNET interfaces and TRIB
interfaces logical plugins. In addition, aggregated indicators are provided for container objects (e.g.
Sites), each reflecting the highest active severity of the objects (e.g. Devices) in that
container. See section Devices Tree (on page 82) for further details on the Devices Tree.

Service Alarm Status Indictors

Each Service Alarm Status indicator represents the highest severity of the alarms currently active
on a specific service.
See section Attributes of Events and Alarms (on page 123) for definition of the supported severity
values, and section Severity Color Coding for Events and Alarms (on page 125) for a definition
of the severity color coding.
The figure below presents the different style indicators available on the various panes.
Figure 92: Service Alarm Status Indicators

Context Selector: Services Data Panel: Topology Map: VPN: Topology Map: PW,
Tree TE Tunnel, TE Link,
LDP LSP, LSP Link,
L1 Link:

As displayed in the Context Selector Services Tree example above, aggregated indicators are also
provided for the service types, each reflecting the highest active severity of the services of that
type. See section Services Tree (on page 82) for further details on the Services Tree.

Network Alarm Indicators

Summary network alarm indicators are presented in the Menu / System Status Bar, providing an
“always available” live indication of the active alarms in the network irrespective of the currently
selected view and Baseline vs Live Selector setting.
Two indicators are presented;
• a Network Devices Alarm Indicator providing a live summary status of all Devices Alarms for
all devices in the network, and
• a Network Services Alarm Indicator providing a live summary status of all Services Alarms for
all services in the network.
From each of these indicators, the user is able to navigate to a filtered Event Browser presenting
the currently active alarms that determine each indicator’s severity color.
The table below describes the function of each indicator in more detail.

132 May 2019 Aviat Networks

 Event Alarm Management

Table 62: Network Devices and Services Alarm Indicators

Indicator Icon Description

Network Devices Selecting the indicator renders a dropdown menu containing the
Alarm Indicator severity values for which there are one or more currently active
Devices Alarms.
For example, the following indicates 4 Critical and 5 Major
alarms active in total for all devices in the network:

Selecting one of the presented severity values opens an Event

Browser displaying all active Devices Alarms of the selected
severity (e.g. all Major) for all devices in the network.
Network Services Selecting the indicator renders a dropdown menu containing the
Alarm Indicator service layers with one or more currently active Service Alarms.
For example, the following indicates 4 Critical alarms active in
total for all L2VPN layer services.

Selecting one of the presented service layers opens an Event

Browser displaying all active Services Alarms of the selected
layer (e.g. all L2VPN) for all services in the network.

Aviat Networks May 2019 133

 Performance Management

Chapter 9. Performance Management

This section describes the support available for analyzing and reporting on the performance of the
managed devices resources and services. In summary, the following is provided:
• Data Collection (on page 136)
• Resource Performance (on page 136)
• Network Health (on page 144)
• Aggregation of Performance Data (on page 150)
All collected performance data is stored in the ProVision Plus database, and the performance
features process the data available in the database. The performance analysis capabilities are
therefore available to the user irrespective of the communication status with the live network or
specific devices.

Note: LICENSING: Performance management is only available where the EM Fault &
Performance or EM Integration for ProVision product module is licensed.

Aviat Networks May 2019 135

Performance Management

Data Collection
Performance data is automatically collected every 15 minutes from sensors and configured
traffic-carrying interfaces on the managed devices. This includes the following types of
information:
• Transmitter, receiver and modem statistics for radio interfaces
• Packet statistics for Ethernet and radio interfaces (where available), including error, discard,
throughput and utilization statistics
Some devices provide the performance data associated with interfaces and sensors in the form of
15-minute and Daily (24-hour) bins. For example WTM 4000 provides 15-minute and Daily bins for
radio interfaces. And some devices provide the data as a set of online values that continually
change over time. Irrespective of the format provided by the device, ProVision Plus saves all
collected raw performance data in the form of a historical set of 15-minute and Daily bins.

Note: Performance data is not collected from device interfaces that have been configured
as disabled.

Resource Performance
The Resource Performance view provides the ability to perform deep-dive analysis of the
performance data associated with one or more network resources, i.e. radio and Ethernet traffic
interfaces and device sensors for one or more devices.
The user is able to select traffic interfaces and sensors (including the specific performance
parameters) for up to 4 devices, together with the time period over which the analysis is to be
performed. Analysis of the associated data can be performed through the following complimentary
views.
• Overview: Presents a graphical performance summary for the selected resources over time,
including an indication of performance issues for each bin period.
• Chart: Presents a performance line chart for the selected resources.
• Detail: Presents the performance data for the selected resources in a tabular view that can be
sorted and filtered.
Figure 93: Example Resource Performance View

Access to Resource Performance View

The Resource Performance view can be accessed as follows:
136 May 2019 Aviat Networks
 Performance Management

• Network > Performance > Resource Performance menu option

• Right-click menu option associated with a row in a Network Health Detail view
When accessed from the Network menu, the view is rendered in the fixed right-hand pane. The
user then selects the devices or the L1 Links to be analyzed through the Object Selection and Filter
Controls provided with the Devices and Services Tree Context Selector (see section Tree Context
Selector Controls (on page 84) for details).
When accessed from a row in the Network Health Detail view, the view is rendered in a floating
dialog and automatically populated with data for device associated with the selected row.

Resource Performance View Controls

This section describes the controls available to the user to select the resources (devices, traffic
interfaces and sensors) and analyze the associated performance data.
Figure 94: Resource Performance View Controls

Table 63: Resource Performance Analysis Controls

Control Icon Description

Start and End time The Start and End values determine the time period for which available
performance data is to be analyzed.
All performance data in the database can be accessed for analysis through the
Start / End settings.
Note: The performance data purge settings determine how long historical
performance data is retained in the database for analysis. See section
Database Management in the Installation and Administration Guide for
details.
Bin Analysis can be performed on 15-minute or Daily bin data.
15-minute bin data is retained for a maximum of 3 months before purging. As
this data is higher resolution (than Daily) it’s more suitable for short term
analysis.
Daily bin data is retained for up to 12 months, and is therefore suitable for longer
term analysis.

Aviat Networks May 2019 137

Performance Management

Control Icon Description

Aggregation Allows the user to select whether the raw bin data, or aggregated bin data over
the selected Aggregation period, is presented in each column, row or data point
for analysis (in the Overview, Detail and Chart views respectively).
15min Bin Selection:
Where Bin selection is 15-minute, the possible Aggregation selections are None,
1 hour, 2 hours, 6 hours, 12 hours or 1 day.
For example, when selecting Bin 15-minute, Start / End period 2 days and
Aggregation 6 hours, 8 rows for each interface (or sensor) are presented, each
indicating the aggregated values over the 6 hours aggregation period. These
aggregated values are presented on the Detail, Chart and Detail tabs.
15min Bin Selection Auto Aggregation:
Where the Start/End period is longer than 7 days, the available Aggregation
selections are automatically limited and default to the lowest aggregation value
(highest resolution), in order to improve processing speed and reduce the volume
of data displayed.
• Up to 1 week, None
• Up to 4 weeks, 1 hour
• Up to 8 weeks, 2 hours
• Up to 12 weeks, 6 hours
Daily Bin Selection:
Where Bin selection is Daily, the possible Aggregation selections are None, 1
day, 7 days, 14 days or 30 days. See section Aggregation of Performance
Data (on page 150) for details on how each parameter type is aggregated.
Preferences Menu Presents the analysis configuration options for the performance view, together
with the ability to export the performance data. See the table below for details.
Generate Button Applies the latest Start and End time, Aggregation and Preferences Menu
settings to the Overview, Chart and Detail views.
The Generate button is highlighted orange when changes have been entered
however not yet applied. Once applied, the orange highlighting is removed again.
Table 64: Resource Performance Devices and Interfaces Selection

Control Icon Description

Devices Lists the selected devices for which available performance data can be analyzed
in the performance view. Devices can be removed by selecting the cross (X)
presented with the device name.
Interfaces Lists the selected device interfaces for which available performance data can be
analyzed in the performance view. Interfaces can be removed by selecting the
cross (X) presented with the interface name.
Interfaces Provides the user with the ability to select the device interfaces and sensors for
Selection which the available performance data is presented for analysis. The sensors
and traffic-carrying interfaces for each selected device are presented as separate
menu options, with the ability to enable/disable each for analyzing.

138 May 2019 Aviat Networks

 Performance Management

Table 65: Resource Performance Preferences Menu Options

Control Function
Exclude Invalid Data Excludes the raw bin data marked as invalid by the devices. The invalid bins are
greyed out in the Resource Performance Overview timeline, and are not presented in
the Chart and Detail views.
Note: Where Aggregation is also enabled (i.e. set to a value other than None),
invalid bin data is excluded from the aggregated bin calculation. For example,
for Bin selection 15-minute and Aggregation setting 1 hour and 3 of 4 15-minute
bins are invalid, the data for the single valid 15-minute bin would be used.
Note: WTM 4000 radios mark bins as invalid when the radio hasn’t been
operating for the full measurement period of the bin (e.g. a power cycle or reset
has occurred), or the date & time has been adjusted.
Radio / Ethernet / Sensor Provides the user with the ability to select the types of radio (transmitter, receiver and
modem), Ethernet, and Sensor parameters presented in the performance view for
analysis. See the Performance Parameter Selections table below for example
selections.
Export to CSV / JSON Export the performance data for the selected resources in CSV or JSON output
format.
Table 66: Example Performance Parameter Selections for WTM 4000

Radio Parameters Ethernet Parameters Sensor Parameters

• Availability • Visibility • Visibility
• Visibility • In Octets • Temperature
• Errored Blocks • In Unicast Packets • Input Voltage
• Errored Seconds • In Multicast Packets • Input Current
• Errored Seconds Ratio • In Broadcast Packets
• Severely Errored Seconds • In Discards
• Severely Errored Seconds • In Errors
Ratio • In Utilization
• Background Block Errors • In Mbps
• Background Block Errors Ratio • In Packets Loss Ratio
• Available Seconds • Out Octets
• Unavailable Seconds • Out Unicast Packets
• RSL Mean • Out Multicast Packets
• RSL Min • Out Broadcast Packets
• RSL Max • Out Discards
• RSL B Mean • Out Errors
• RSL B Min • Out Utilization
• RSL B Max • Out Mbps
• BER Mean • Out Packet Loss Ratio
• BER Min
• BER Ma
• BER B Mean
• BER B Min
• BER B Max
• SNR Mean
• SNR Min
• SNR Max
Aviat Networks May 2019 139
Performance Management

Radio Parameters Ethernet Parameters Sensor Parameters

• SNR B Mean
• SNR B Min
• SNR B Max
• Tx Power Mean
• Tx Power Min
• Tx Power Max
• Tx Power B Mean
• Tx Power B Min
• Tx Power B Max
• XPD Mean
• XPD Min
• XPD Max
• XPD B Mean
• XPD B Min
• XPD B Max
• Frame Loss Seconds
• Frame Loss Seconds B

140 May 2019 Aviat Networks

 Performance Management

Overview (Timeline Summary) Tab

The Overview provides the user with the following capabilities:
• Graphical timeline for selected resources over a selected time period, providing a set of
performance health indicators for the resources for each bin period on the timeline.
• Time correlated view of performance across multiple devices, interfaces and sensors.
• Indication whether data was successfully collected for each bin.
• Indication whether the collected data for each bin is invalid (determined by the radio).
• Indication whether the collected data for each bin in errored or below threshold.
• Ability to view the full set of data for a selected bin.
The figure and table below identify the analysis controls available in the Overview.
Figure 95: Resource Performance Overview Controls

Table 67: Resource Performance Overview Controls

Control Icon Description

Select Bin The full set of performance data for a bin can be viewed by clicking on the
bin in the graphical timeline. The data is then presented directly beneath
the timeline.
Close Bin Details Closes the selected bin details.

Overview Scroll Scrolls the timeline between the selected Start and End times.

Timeline Tooltip Where an errored or below threshold indicator is presented on the

timeline, a tooltip presenting the value is provided.
The table below lists the set of performance parameters presented in the Overview to reflect
resource performance issues. For each parameter, the threshold value associated with the
performance health indicator for each bin is also identified.

Aviat Networks May 2019 141

Performance Management

Table 68: Resource Performance Overview Parameters and Thresholds

Interface / Sensor Performance Parameter and Threshold

Radio Radio interface performance parameters and thresholds:
• Errored Seconds > 0
• Severely Errored Seconds > 0
• Unavailable Seconds > 0
• RSL Mean (dBm). This value is presented by a level indicator. There is
no associated threshold value.
Ethernet Ethernet interface performance parameters and thresholds:
• In Errors > 0
• Out Errors > 0
• In Discards > 0
• Out Discards > 0
Sensor Device sensor performance parameters and thresholds:
• ODU Temperature > 90 degree C
• Input Supply Voltage < 20V
Note: For WTM 4000, the minimum input supply voltage is 20V for
DC and 40V for PoE. The indicator threshold therefore does not
indicate a problem when the device is using PoE supply voltage.
The table below describes the set of performance health indicators that can be presented with each
bin in the Overview timeline.
Table 69: Resource Performance Overview Health Indicators

Indicator Icon Description

Invalid Bin Pink background indicates the device marked the bin as invalid.
o Note: WTM 4000 radios mark bins as invalid when the
r radio hasn’t been operating for the full measurement period
on the bin (e.g. a power cycle or reset has occurred), or the
date & time has been adjusted.

Missing Bin Grey background indicates that data isn’t available for this bin.
For example, where ProVision Plus was unable to communicate
with the device (i.e. no data collected), or the data has been
removed from the database (i.e. collected and subsequently
purged).
See section Database Management of the Installation and
Administration Guide for details on performance data purging.
Errored or Below Red square indicates that the performance parameter for this bin
threshold parameter is below the threshold value identified in the table above.

142 May 2019 Aviat Networks

 Performance Management

Chart Tab
The Chart view provides the user with the following capabilities:
• Performance timeline chart for selected resources over a selected time period.
• Presents time correlated view of performance across multiple device interfaces and sensors.
The figure and table below identify the analysis controls available to in the Chart view.
Figure 96: Resource Performance Chart Controls

Table 70: Resource Performance Chart Controls

Control Icon Description

Select Bin Mouse over presents the data for the selected bin in a pop-up.

Aviat Networks May 2019 143

Performance Management

Detail Tab
The Resource Performance Detail view provides the user with the following capabilities:
• Tabular view presenting the performance data for the selected resources.
• Analyze the data using sort and search controls.
Figure 97: Resource Performance Detail Controls

Table 71: Resource Performance Detail Controls

Control Description
Search A text search can be applied to the tabular view, resulting in only those rows
containing a match being displayed.
Column Sort Sort the tabular view by mouse clicking on a column heading.

Resource Selection Via Devices Tree

When rendered in the fixed right-hand pane, changes to the Devices and Interfaces selection can
be performed through the Object Selection and Filter Controls provided with the Devices Tree
Context Selector (see section Tree Context Selector Controls (on page 84) for details).

Network Health
The Network Health view provides the ability to proactively analyze the performance of all (or a
subset of) the traffic interfaces or device sensors in the network over a selected time period, and
rapidly identify current or historical performance issues. This includes the following types of
problems:
• Traffic interfaces experiencing capacity over (or under) utilization.
• Traffic interfaces experiencing a degradation in performance over time.
• Radio interfaces not meeting expected G.826 availability.
• Radio interfaces with low RSL.
• Ethernet interfaces experiencing packet errors or packet discards.
• Devices experiencing high temperature or low input power.

144 May 2019 Aviat Networks

 Performance Management

• Devices with low visibility (unreliable communications).

The user is able to select the type of resource (Radio interfaces, Ethernet interfaces, or Device
sensors) to be analyzed, together with the time period over which the analysis is to be performed,
and the aggregation bin period applied to the raw daily data. Analysis of the resultant data can be
performed through the following complimentary views.
• Overview: Presents a graphical performance summary.
• Detail: Presents the resultant data in a tabular view that can be sorted and filtered.
Note: The Network Health view provides for analysis of collected daily bin performance
data. Daily, as opposed to 15-minute bin data, is used to provide for higher scalability, as the
analysis is conducted across all device interfaces and sensors in the network.
Figure 98: Example Radio Network Health View

Aviat Networks May 2019 145

Performance Management

Figure 99: Example Ethernet Network Health View

Figure 100: Example Sensor Network Health View

Access to Network Health View

The Network Health view can be accessed as follows:
• Network > Performance > Network Health menu options
• Performance > Network Health right-click menu options associated with a Container object
on the Devices Tree
When accessed from the Network menu, the view is rendered in a floating dialog and is
automatically populated with data for all devices in the network. Radio Network Health covers all
radio interfaces, Ethernet Network Health all Ethernet interfaces, and Sensor Network Health all
sensors.
146 May 2019 Aviat Networks
 Performance Management

When accessed from the Devices Tree, the view is rendered in a floating dialog and is automatically
populated with data for the selected Container or device.
By default the available performance data for the previous 7 days is presented.

Network Health View Controls

This section describes the controls available to the user to analyze the associated performance
data for the selected resources.
Figure 101: Network Health View Controls

Table 72: Network Health View Controls

Control Icon Description

Start and End The Start and End values determine the time period for which available
time performance data is to be analyzed.
All performance data in the database can be accessed for analysis through the
Start / End settings.
Note: The performance data purge settings determine how long historical
performance data is retained in the database for analysis. See section
Database Management of the Installation and Administration Guide for
details on performance data purging.
Aggregation Allows the user to select whether to present a single row or multiple rows for
each interface or sensor in the Detail tabular view. A single row indicates the
aggregated values of the Daily bin data over the Start / End period. Whereas for
multiple rows, each indicates the aggregated values of the Daily bin data over
the selected aggregation duration.
Possible Aggregation selections are All, 7days, 14 days or 30 days.
For example, when selecting a Start / End period 35 days and Aggregation 7
days, this results in 5 rows for each interface (or sensor) being presented, each
indicating the aggregated values over the 7 days Aggregation period. This
provides an indication of how the performance has varied for an interface (or
sensor) over the reporting period.
See section Aggregation of Performance Data (on page 150) for details on
how each parameter type is aggregated.
Preferences Presents the analysis configuration options for the performance view, together
Menu with the ability to export the performance data. See the table below for details.
Generate Button Applies the latest entered Start / End period, Aggregation and Preferences
Menu settings to the Overview and Detail views.
The Generate button is highlighted orange when changes have been entered
however not yet applied. Once applied, the orange highlighting is removed
again.

Aviat Networks May 2019 147

Performance Management

Table 73: Network Health Preferences Menu Options

Control Function
Exclude Invalid Data Excludes the raw bin data marked as invalid by the devices from the analysis
calculations.
Note: Where Aggregation is also enabled (i.e. set to a value other than None),
invalid bin data is excluded from the aggregated bin calculation. For example,
for Aggregation setting 7 days and 3 of 4 daily bins are invalid, the data for the
single valid daily bin would be used.
Note: WTM 4000 radios mark bins as invalid when the radio hasn’t been
operating for the full measurement period of the bin (e.g. a power cycle or reset
has occurred), or the date & time has been adjusted.
Select Parameters Provides the user with the ability to select the types of radio (transmitter, receiver and
modem) and Ethernet parameters presented in the performance view for analysis.
The parameters available for selection are the same for both the Resource
Performance and Network Health views. An example is included in section
Resource Performance View Controls (on page 137).
Export to CSV / JSON Export the performance data for the selected resources in CSV, JSON or PDF output
/ PDF format.

Overview (Summary) Tab

The Overview provides the user with the following capabilities:
• Graphical summary of the performance of either radio or Ethernet interfaces.
• For radio interfaces, an indication of mean interface availability and visibility, including the %
of interfaces above and below a selected network threshold.
• For Ethernet interfaces, an indication of mean interface utilization, packet loss and visibility,
including the % of interfaces above and below a selected network threshold.
• For Device Sensors, an indication of mean ODU temperature and visibility, including the % of
devices above and below a selected network threshold.
The figure and table below identify the analysis threshold controls available in the Overview.
Figure 102: Network Health Overview Threshold Controls

Table 74: Network Health Overview Threshold Controls

Control Icon Description

Availability Threshold Radio interface G.826 availability (%) threshold value.
(%) On selecting the Generate button, the graphical threshold indicators are
updated to present the % of interfaces above and below the selected
value.

148 May 2019 Aviat Networks

 Performance Management

Control Icon Description

Visibility Threshold (%) Radio, Ethernet or Sensor visibility (%) threshold value.
Visibility provides an indication of the % of successful daily data collection
polls over the selected Start/End period. For example, where network
health is being analyzed for all devices in the network over a 30 day
period and ProVision Plus has been unable to collect 1 of 30 daily polls
for each device (e.g. the server lost connectivity with the network),
Visibility will be calculated as 96.667%, i.e. (29 x No. devices) div (30 x
No. devices).
On selecting the Generate button, the graphical threshold indicators are
updated to present the % of interfaces above and below the selected
value.
Utilization Threshold Ethernet interface utilization (%) threshold value.
(%) On selecting the Generate button, the graphical threshold indicators are
updated to present the % of interfaces above and below the selected
value.
Packet Loss Threshold Ethernet interface packet loss (%) threshold value. On selecting the
(%) Generate button, the graphical threshold indicators are updated to present
the % of interfaces above and below the selected value.
ODU Temperature Device ODU temperature (C) threshold value. On selecting the Generate
Threshold (C) button, the graphical threshold indicators are updated to present the % of
interfaces above and below the selected value.
Generate Button Applies the latest entered Start / End period, Aggregation and
Preferences Menu settings and Threshold values to the Overview and
Detail views . The Generate button is highlighted orange when changes
have been entered however not yet applied. Once applied, the orange
highlighting is removed again.

Detail Tab
The Network Health Detail view provides the user with the following capabilities:
• Tabular view presenting the performance data for the selected resources.
• Analyze the data using sort and search controls.
The tabular view presents one or more rows for each Radio or Ethernet interface, or each device
(for the device sensors), depending on the Aggregation parameter setting. See the Aggregation
parameter description in the Network Health View Controls table above for further information.
As an example, the figure below presents 4 rows for each Radio interface, where the Start / End
reporting period is 28 days and the Aggregation setting is 7 days. The parameters in each row are
aggregated values over the collected 7 daily raw samples in the aggregation period.

Aviat Networks May 2019 149

Performance Management

Figure 103: Example Network Health Detail with Multiple Rows Per Interface

Figure 104: Network Health Detail Controls

Table 75: Network Health Detail Controls

Control Description
Search A text search can be applied to the tabular view, resulting in only those rows
containing a match being displayed.
Column Sort Sort the tabular view by mouse clicking on a column heading.

Row navigation menu Provides access to the device management capabilities and views associated with a
particular device row, through the mouse <right-click> menu.

Aggregation of Performance Data

The following table identifies how each different performance parameter data type is aggregated.
Table 76: Aggregation of Performance Data Types

Parameter Type Aggregation Description

Counter Sum of the counter values over the aggregation period.
For example, the aggregated In Errors is calculated as the sum of the In Errors bin
values.
Mean gauge Mean of the gauge values over the aggregation period.
For example, the aggregated RSL Mean is calculated as the mean of the RSL Mean bin
values.
Min gauge Minimum of the gauge values over the aggregation period.
Where the bins contain Mean, Min and Max gauge values, the aggregated Min gauge
value is calculated as the minimum of the Min gauge bin values.
Else, where the bins contain only a Mean gauge value, the aggregated Min gauge value
is calculated as the minimum of the Mean gauge bin values.

150 May 2019 Aviat Networks

 Performance Management

Parameter Type Aggregation Description

Max gauge Maximum of the gauge values over the aggregation period.
Where the bins contain Mean, Min and Max gauge values, the aggregated Max gauge
value is calculated as the maximum of the Max gauge bin values.
Else, where the bins contain only a Mean gauge value, the aggregated Max gauge value
is calculated as the maximum of the Mean gauge bin values.

Aviat Networks May 2019 151

 Service Diagnostics

Chapter 10. Service Diagnostics

This section describes the support available for MPLS service diagnostics. In summary, the
following is provided:
• Initiate on-demand end-to-end connectivity diagnostics on a selected service.
• Select the service on the topology view.
• Maintain a history of the diagnostics performed on each service on the client machine.
• Ability to view execution of the associated CLI commands and results through a CLI console.
• Export of diagnostics test results.
Note: LICENSING: IP/MPLS service diagnostics are only available where the IP/MPLS
Fault product module is licensed.
This section topics include:
• Supported MPLS Diagnostics (on page 154).
• How to Initiate Diagnostics on a Service (on page 154).
• Diagnostics View (Data Panel Tab) (on page 156).
• Diagnostic History View (on page 161).

Aviat Networks May 2019 153

Service Diagnostics

Supported MPLS Diagnostics

The Diagnostics feature provides the ability to execute on-demand MPLS ping and trace
(traceroute) connectivity diagnostics on RT Link (VRF routing), TE Tunnel, and LSP services. The
following table summarizes the set of supported diagnostics.
Table 77: Summary of Supported MPLS Diagnostics

Supported
Service Type Description
Diagnostics
RT Link (VRF routing) Ping + TraceDetermines whether there is L3VPN routing connectivity from a VRF
to a selected network address destination, through executing a VRF
ping or trace diagnostic. This is performed on the VRF at the
terminating end of a selected the RT Link (i.e. the VRF that imports
the RT value tagged routes).
TE Tunnel Ping + Trace Validates connectivity of a selected TE Tunnel, through executing a
TE Tunnel ping or trace diagnostic on a selected TE Tunnel ID.
This is initiated on the head-end PE router for the tunnel.
LSP Ping + Trace Determines whether there is LSP connectivity to a selected network
address destination, through executing an LSP ping or trace
diagnostic. This is initiated on the PE router at the ingress end of
the LSP.
The above ping and trace diagnostics are performed by establishing an SSH session between the
ProVision Plus server and the device on which the diagnostic is initiated, and then executing the
corresponding ping or traceroute CLI commands.

How to Initiate Diagnostics on a Service

There are two methods for initiating diagnostics:
• Service Right Click Menu
• Service Selector

Diagnostic Via Service Right Click Menu

MPLS ping and trace diagnostics can be initiated on:
• RT Link (VRF routing),
• TE Tunnel or
• LSP services,
Initiate through the right-click menu (Diagnostics > Ping and Diagnostics > Trace) associated
with a service presented on the Topology view.
On selecting a diagnostics menu option (ping or trace), the Diagnostics View is automatically
presented on the Data Panel Diagnostics tab, populated with the information associated with the
selected service.
The user is then able to execute the diagnostic through the controls on the Diagnostics View.
The figure below indicates the diagnostics menu options for a TE Tunnel service.

154 May 2019 Aviat Networks

 Service Diagnostics

Figure 105: Example TE Tunnel Diagnostics Menu

LSP Diagnostic Via the Service Selector

As an alternative to initiating an LSP ping or trace diagnostic on a discovered LSP service
presented in the Topology view, the user can simply add two CTR devices to the Service Selector
and initiate the diagnostic irrespective of whether a traffic-carrying LSP has been discovered
between the devices. This provides a valuable troubleshooting capability.
Devices are added to the Service Selector via the Add to Service Selector right-click menu option
associated with a device object in the Topology view.
The figure below provides an example where two CTR devices have been added to the Service
Selector and there are no discovered services between them. LSP Ping and Trace diagnostics can
then be initiated through the right-click menu associated with the Paths displayed in the Service
Selector.
Figure 106: Example Service Selector

Aviat Networks May 2019 155

Service Diagnostics

Diagnostics View (Data Panel Tab)

The Diagnostics tab in the Data Panel provides the ability to execute ping or trace diagnostics on a
selected service.
The figure and table below identify the display areas and controls available in the Diagnostics View.
Diagnostics on a selected TE Tunnel is presented as an example.
Figure 107: Diagnostics View Areas

Table 78: Diagnostics View Areas

Area Description
Service Identifier Unique identifier for the selected RT Link, TE Tunnel or LSP service.
Diagnostic Type Indicates MPLS Ping or MPLS Trace, together with associated settings.
Diagnostic Result The following result information is presented. For a Trace diagnostic test, this is
presented for each node on the path.
• Type: transit or dest (destination) node
• Address / Device: Node IP address
• MTU: Interface Maximum Transmission Unit
• Label(s): Input label(s).
• Time (ms): Round-trip time in milliseconds.
History Selector Lists up to the last 5 diagnostics executed on the selected service, indicating the
service, diagnostic type, execution time and result for each entry.
Table 79: Diagnostics View Controls

Control Icon Description

Diagnostic Type Ability to select MPLS Ping or MPLS Trace diagnostic. This is
pre-populated with the choice made when selecting the service.
Start Start execution of the selected diagnostic on the selected service.
Diagnostics can also be re-run by selecting this button.
Console Option to display the associated CLI commands and results during or
after execution of the diagnostic.
History Selector Ability to select a previous diagnostic that was executed on the selected
service, view the results, and re-run the diagnostic again.

156 May 2019 Aviat Networks

 Service Diagnostics

Control Icon Description

Show All Results Opens the Diagnostic History modal view. See section Diagnostic
History View (on page 161) for details.
Open New Opens the Diagnostic modal view. See section Diagnostic Modal
Window View (on page 157) for details.

Diagnostic Modal View

The Diagnostic View is opened as a modal view when the Topology view is not being presented.
This modal view contains the same information as the Data Panel tab view with the exception there
is no diagnostic history available.
Figure 108: Example Diagnostics Modal View

Example Diagnostics
This section provides some examples ping and trace diagnostics executed on RT Link (VRF
routing), TE Tunnel and LSP services.

How to Perform a RT Link (VRF routing) Ping Diagnostic

Step Action
1. Select an RT Link service and initiate a Ping diagnostic from the right-click menu.

Result: The selected service and diagnostic is populated on the Diagnostics Data Panel Tab.

Aviat Networks May 2019 157

Service Diagnostics

Step Action
2. Select the Destination Address and then press the Start button to execute the diagnostic.
Result: On completion the results are presented as shown below.

Optionally press the Console button to view the associated CLI commands and results.

How to Perform a TE Tunnel Trace Diagnostic

Step Action
1. Select a TE Tunnel service and initiate a Trace diagnostic from the right-click menu.
Result: The selected service and diagnostic is populated on the Diagnostics Data Panel Tab.

158 May 2019 Aviat Networks

 Service Diagnostics

Step Action
2. Press the Start button to execute the diagnostic.
Result: On completion the results are presented as shown below.

Optionally press the Console button to view the associated CLI commands and results.

How to Perform an LSP Trace Diagnostic

Step Action
1. Select an LSP service and initiate a Trace diagnostic from the right-click menu.
Result: The selected service and diagnostic is populated on the Diagnostics Data Panel
Tab.

Aviat Networks May 2019 159

Service Diagnostics

Step Action
2. Press the Start button to execute the diagnostic.
Result: On completion the results are presented as shown below.

Optionally press the Console button to view the associated CLI commands and results.

160 May 2019 Aviat Networks

 Service Diagnostics

Diagnostic History View

The history of service diagnostics executed on the client can be viewed in the Diagnostic History
view, accessed from the Network > Diagnostics > Diagnostic History menu option. The last 5
diagnostics executed on each service is retained in the history.
Figure 109: Example Diagnostic History View

The figure and table below identify the controls available in the Diagnostic History view.
Figure 110: Diagnostic History View Controls

Table 80: Diagnostic History View Controls

Control Icon Description

Search A text search can be applied to the Diagnostic History tabular view, resulting in
only those rows containing a match being displayed.
Open Result Opens the diagnostic in the Diagnostic modal view. See section Diagnostic
Modal View for details.
Delete Result Deletes the results for the diagnostic from the diagnostic history.
Export Results Provides the ability to export the results for the displayed diagnostics in CSV,
JSON or PDF format.

Aviat Networks May 2019 161

 System Messages

Chapter 11. System Messages

The System Message Indicator on the Main Menu / Status Bar provides an indication of the
following types of ProVision Plus system problems:
• Database backup or purge problems
• Discovery of network configuration problems
• Communication failure with a configured ProVision network mediation server
• User failed logins
• ProVision Plus license problems
The figure below presents an example where the System Indicator represents 4 unread messages,
one or more of which are severity Error. By clicking on the indicator, the messages are listed.
The table below describes the supported system messages. The table below describes the
supported system messages, excluding licensing messages. See section License Management in
the Installation and Administration Guide for supported licensing messages.
Figure 111: Example System Messages

Table 81: System Messages

Message Severity Description

Database backup completed Informational The on-demand or scheduled database backup has
successfully successfully completed.
Purge data task completed Informational The on-demand or scheduled purge operation has successfully
successfully completed.
Operational model has Warning Discovered configuration values from the live network for one or
reconciliation issues more services cannot be reconciled.
For example:

Access the Reconciliation Report to identify the attribute(s) that

cannot be reconciled, and resolve the network configuration
issue.
Aviat Networks May 2019 163
System Messages

Message Severity Description

User authentication has Warning The given username has exceeded the maximum login retries
failed or the user has attempted to log in after the account has been
locked. This message is presented to Administrator users only.
Failed to create backup Error The on-demand or scheduled database backup failed to
complete. See section Database Management of the
Installation and Administration Guide for further details on
backups, to help with establishing the cause.
Cannot contact ProVision Error Server is unable to communicate with the configured ProVision
Network network mediation server.
For example:

New Baseline created Warning A new Baseline has been created. Please select the Refresh
button to display the new Baseline design. Save any edits in
progress (e.g. map coordinate repositioning) before selecting
the Refresh button.

164 May 2019 Aviat Networks

 Managing Your Access to the System

Chapter 12. Managing Your Access to the

System
This section describes the functionality and procedures associated with managing your access to
the system.
Topics include:
• User Roles
• User Profile (on page 167)
• User Security Policy (on page 169)
• User Access Procedures (on page 169)

Aviat Networks May 2019 165

Managing Your Access to the System

User Roles
ProVision Plus provides role based access control, i.e. where a user’s access to the system is
determined by the roles the user has been assigned. More accurately the relationship of users and
roles is described as follows:
• A user may be assigned zero or more roles, and
• A role may be assigned to zero or more users.
For example, a user could be assigned both Operator and Engineer roles. Or a number of users
could be assigned the Engineer role.
The equivalent user access restrictions apply to the northbound interface (NBI). See the ProVision
Plus Northbound Interface System Integration Guide for the supported roles, and access provided
for each role, via the NBI.
The table below identifies the supported roles, and describes the access provided with each role.

Table 82: User Roles

User Role Description

All roles All roles include read-only access to the following base capabilities.
• System Messages.
• User Profile.
• License Management view.
Operator The Operator role provides access to the following capabilities, in addition to the
base capabilities.
Read-only access:
• Network Topology views – Map and Data Panel including Baseline / Live views.
• Network Configuration views.
• Detail – Device and Service Detail including Baseline and Live views.
• Reconciliation Report view.
• Event Browser views.
• Network Performance views.
• Device Diagnostics History view.
Read-write access:
• Network Configuration views – Customized layout.
• Event Browser – Customized views.
• Event Browser – Acknowledge events.

166 May 2019 Aviat Networks

 Managing Your Access to the System

User Role Description

Engineer The Engineer role provides access to the following capabilities plus the Operator role
capabilities, in addition to the base capabilities:
Read-write access:
• Topology Map System Coordinates.
• Promote Live network changes to Baseline design.
• Deploy Containers.
• Rename, Reparent, Delete Containers.
• Deploy Directly managed devices.
• Manage / Unmanage directly managed devices.
• Rename, Reparent, Delete Directly managed devices.
• Direct Device Management – Change Name, Management IP.
• Direct Device Access Control – Change authentication credentials.
• Create, Delete physical links.
• ProVision Network Access Control.
• Event Browser – Manually clear events.
• Device Diagnostics execution.
• Device Configuration Backup and Restore.
• Device Software Loading.
• Device Licensing.
• Task Manager.
Administrator The Administrator role provides access to the following capabilities, in addition to the
base capabilities:
Read-write access:
• User Management.
• User Policy Settings.
• Database Management.
• Email Server Management.
• License Management – Create Server Fingerprint, Install License.

User Profile
You are able to view and modify your user profile by clicking on your Display Name presented on
the top left side of the Main Menu / Status Bar. This provides access to the User Profile page.
The figure below presents the User Profile page, together with the Change Password dialog that’s
accessible from this page.

Aviat Networks May 2019 167

Managing Your Access to the System

Figure 112: View / Modify User Profile

The table below describes the settings available for view and modification.
Table 83: User Profile Attributes

Attribute Description
User Account Id A unique identifier automatically allocated to each new user account created
in the system. This cannot be modified.
Email Your email address. This cannot be modified as it’s used to activate and
maintain your user account.
Display Name An alternative and easier to read configurable name (than your email
address). This can be modified.

168 May 2019 Aviat Networks

 Managing Your Access to the System

Attribute Description
Assigned Roles Identifies the roles you’ve been assigned in the system.
A user can be assigned zero, one or multiple roles. The supported roles
are as follows:
• Administrator
• Engineer
• Operator
See section User Roles (on page 166) for details on the access provided by
each supported role.
Password (Current, Enter a new password that adheres to the composition rules defined by an
New) Administrator user.
Note: The first character must always be a letter, including where the
password needs to contain one or more numbers.

User Security Policy

Administrator users are provided with the ability to define the user login security policy applied to all
users of the system. In summary, this includes definition of the following:
• Password composition rules
• Password expiry and notification behavior
• Maximum login retries, after which a user account is locked
• Optional pre and post login banners
See How to Configure User Security Policy for details.

User Access Procedures

This section describes the procedures associated with accessing a user account for the first time,
resetting the password.

How to set User First Time Login

When a new user requests the creation of a user account, an admin user creates the account and
triggers the ProVision Plus server to email a user activation link to the user's email addresses.
This procedure covers the steps performed by the new user, from receipt of the activation link
email, through to completing first time login.

Step Action
1. An email containing a user activation link is received from the server.
2. Select the activation link to active the new user account.
3. Follow the instructions and enter a new password.
4. When presented with the login page, enter email address (user name) and password.

How to Reset User Forgot Password

This procedure identifies the steps involved in resetting the login password, in the case where it's
been forgotten.

Step Action
1. Select the Forgot Password? link on the login page.
2. Enter email address when prompted and then select the Request Password Reset link.
Aviat Networks May 2019 169
Managing Your Access to the System

Step Action
3. An email containing a password reset link is received from the server.
4. Select the link.
5. Follow the instructions and enter a new password.
6. When presented with the login page, enter email address and password.

170 May 2019 Aviat Networks

 Glossary of Technical Terms

Appendix A: Glossary of Technical Terms

This section provides a definition of the technical terms used throughout the software. The terms
are grouped into a number of tables, each covering a separate technical area. Where applicable,
references are included with each term.

Device Attributes
Attribute Description
Device Name Name of the device.
Discovered from the ProVision mediation system.
Device Type Device type, e.g. WTM 4100 or CTR 8540
Management IP Address IP address by which the device is managed by ProVision Plus.
For indirectly managed devices, this is the same as the address
used by ProVision.
Management Admin State Device management admin state (unmanaged or managed).
Management Status Device management status (unmanaged, connecting, managed
or errored).
Physical Parent Name of the parent container object, as defined by the network
container hierarchy.
Router ID Router IDs and loopback addresses.
L1 Termination Identifier for device interface/port that terminates a L1 Link.
Notation <plugin_ID>/<port_number> is used. For example,
“Slot2/1” indicates port 1 of the plugin in slot 2.
TE Terminations Identifier for device interface/port that terminates a TE Link.
Notation <plugin_ID>/<port_number> is used. For example,
“Slot2/1” indicates port 1 of the plugin in slot 2.
Interface Name Identifier for a device interface/port.
Notation <plugin_ID>/<port_number> is used. For example,
“Slot2/1” indicates port 1 of the plugin in slot 2.
VPN AC VPN Attachment Circuit (AC) configured on the
device. Indicated by the identifier for a device interface/port.
Notation <plugin_ID>/<port_number> is used. For example,
“Slot0/1” indicates port 1 of the bank of Ethernet ports on the
CTR mainboard.
Interface Phys Address Media Access Control address (MAC address) of a device
interface.
Reference: IETF RFC 1213 (MIB II).
Interface MTU Maximum Transmission Unit (MTU) for a device interface.
Indicates the largest datagram which can be transmitted on the
interface.
Reference: IETF RFC 1213 (MIB II).
Interface Admin Status Administrative state of a device interface.
Indicates the configured/desired state of the interface. Valid
states are up, down and testing.
Reference: IETF RFC 1213 (MIB II).
Interface Oper Status Operational state of a device interface.
Valid values are up, down and testing.
Reference: IETF RFC 1213 (MIB II).
PW Termination Device interface/port that terminates a PW.
Notation <plugin_ID>/<port_number> is used. For example,
“Slot0/1” indicates port 1 of the bank of Ethernet ports on the
CTR mainboard.

Aviat Networks May 2019 171

Contents

Attribute Description
L2VPN AC L2VPN Attachment Circuit (AC) configured on the device.
Indicated by the identifier for a device interface/port.
Notation <plugin_ID>/<port_number> is used. For example,
“Slot0/1” indicates port 1 of the bank of Ethernet ports on the
CTR mainboard.
L3VPN AC L3VPN Attachment Circuit (AC) configured on the device.
Indicated by the device VRF name followed by the identifier for
the device interface/port.
Notation <VRF name>,<plugin_ID>/<port_number> is used.
For example, “VRFA, Slot0/1” indicates port 1 of the bank of
Ethernet ports on the CTR mainboard that’s mapped to VRFA.
L1 Link Attributes
Attribute Description
L1 Link Source Source Device name + Interface of the L1 Link.
Notation <plugin_ID>/<port_number> is used for the
Interface. For example, “Slot2/1” indicates port 1 of the
plugin/card in slot 2.
L1 Link Destination Destination Device name + Interface of the L1 Link.
Notation <plugin_ID>/<port_number> is used for the
Interface. For example, “Slot2/1” indicates port 1 of the
plugin/card in slot 2.
L1 Link Endpoint A/Z Source/destination device name + Interface of the L1 Link.
Notation <plugin_ID>/<port_number> is used for the
Interface. For example, “Slot2/1” indicates port 1 of the
plugin/card in slot 2.
TE Link Attributes
Attribute Description
TE Link Name Name/ID of the TE Link configured on the device.
The name/ID is made unique by combining with the source and
destination device name.
Where a TE Link is configured on device “DUT A” as “teAB”, the
Services Tree presents the name full name (for example) as
“teAB – [DUT A] radio4/1 – [DUT B] radio4/1”.
TE Link Source Source device name + Interface of the TE Link.
Notation <plugin_ID>/<port_number> is used for the
Interface. For example, “Slot2/1” indicates port 1 of the
plugin/card in slot 2.
TE Link Destination Destination device name + Interface of the TE Link.
Notation <plugin_ID>/<port_number> is used for the
Interface. For example, “Slot2/1” indicates port 1 of the
plugin/card in slot 2.
TE Link Protection Type Link protection type (e.g. unprotected, dedicate 1+1, etc.).
Presents the capability that exists for a link, for use in path
computation when setting up LSPs.
Reference: IETF RFC 4204 (Routing Extensions in Support of
GMPLS).
Max Link Bandwidth (kbps) Maximum bandwidth (kbps) that can be used on this TE Link.
Reference: IETF RFC 3630 (TE Extensions to OSPF), and RFC
5305 (IS-IS Extensions for TE).

172 May 2019 Aviat Networks

 Glossary of Technical Terms

Attribute Description
TE Link Default Metric TE Link metric administratively assigned on the router.
For OSPF-TE, referred to as TE Metric. For ISIS-TE, referred to
as TE Default Metric.
Reference: IETF RFC 3630 (TE Extensions to OSPF), and RFC
5305 (IS-IS Extensions for TE).
TE Link Admin Status Admin status (up or down) for the TE Link.
TE Link Oper Status Oper status (up or down) for the TE Link.
TE Link Access Type Link access type (point-to-point or multi-access) for a TE Link.
Reference: IETF RFC 3630 (Traffic Engineering (TE) Extensions
to OSPF).
Max Reservable Link Bandwidth Maximum amount of bandwidth (kbps) that can be reserved over
(kbps) this TE Link.
Reference: IETF RFC 3630 (TE Extensions to OSPF), and RFC
5305 (IS-IS Extensions for TE).
TE Tunnel Attributes
Attribute Description
Tunnel ID Tunnel ID.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Tunnel Source IP Address of the source (ingress) PE router of a TE Tunnel.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Tunnel Destination IP Address of the destination (egress) PE router of a TE Tunnel.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Working / Protecting LSP RRO Identifies the RRO (Record Route Object) operational state of
the Working or Protecting LSP, by identifying the hop-by-hop TE
Links providing the LSP path.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels), RFC 4872 (RSVP-TE Extension in Support of
E2E Recovery).
Working / Protecting LSP ERO Identifies the ERO (Explicit Route Object) for the Primary
Working or Protecting LSP, listing the nodes along the explicit
route.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels), RFC 4872 (RSVP-TE Extension in Support of
E2E Recovery).
Tunnel Active LSP Identifies whether the Working or Protecting LSP is currently
active.
Tunnel Admin Status Admin status (up or down) for a TE Tunnel.
Reference: IETF RFC 1213 (MIB II).
Tunnel Oper Status Oper status (up or down) for a TE Tunnel.
Reference: IETF RFC 1213 (MIB II).
Tunnel Name Name for a TE Tunnel.
Notation <“mplstunnel”><Tunnel ID> is used.
Tunnel Type Always set to tunnel-ptp.
Tunnel Setup Priority Setup priority for a TE Tunnel.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).

Aviat Networks May 2019 173

Contents

Attribute Description
Tunnel Holding Priority Holding priority for a TE Tunnel.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Tunnel Protection Protection (lsp-prot-unprotected or lsp-prot-1-for-n) configuration
for a TE Tunnel.
Note: 1-for-1 protection is indicated as a form of 1-for-n.
Reference: IETF RFC 4872 (RSVP-TE Extension in Support of
E2E Recovery).
Working / Protecting LSP ERO Index for an ERO (Explicit Route Object) subobject.
Index Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Working / Protecting LSP ERO Usage (include or exclude) for an ERO (Explicit Route Object)
Usage subobject.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Working / Protecting LSP ERO IP IP address for an ERO (Explicit Route Object) subobject.
Address Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Working / Protecting LSP ERO Identifies whether an ERO (Explicit Route Object) subobject is
Loose loose or strict (true=loose, false=strict).
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Working / Protecting LSP RRO Index for an RRO (Record Route Object) subobject.
Index Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Working / Protecting LSP RRO IP IP address for an RRO (Record Route Object) subobject.
Address Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Working / Protecting LSP RRO IP IP address prefix length for an RRO (Record Route Object)
Prefix Length subobject.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Tunnel LSP ID ID for a TE Tunnel LSP.
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Tunnel LSP Type Tunnel LSP type (tunnel-p2p or tunnel-p2mp).
Reference: IETF RFC 3209 (RSVP-TE: Extensions to RSVP for
LSP Tunnels).
Tunnel LSP Origin Type Tunnel LSP origin type (ingress or egress).
Reference: IETF RFC 4872 (RSVP-TE Extension in Support of
E2E Recovery).
Tunnel LSP Resource Status Tunnel LSP resource status (primary or secondary).
Reference: IETF RFC 4872 (RSVP-TE Extension in Support of
E2E Recovery).
Tunnel LSP Protection Role Tunnel LSP protection role (working or protecting).
Reference: IETF RFC 4872 (RSVP-TE Extension in Support of
E2E Recovery).

174 May 2019 Aviat Networks

 Glossary of Technical Terms

LSP Link Tab Attributes

Attribute Description
LSP Link Source Source Device name + Interface of the L1 Link.
Notation <plugin_ID>/<port_number> is used for the Interface.
For example, “Slot2/1” indicates port 1 of the plugin/card in slot
2.
LSP Link Destination Destination Device name + Interface of the L1 Link.
Notation <plugin_ID>/<port_number> is used for the Interface.
For example, “Slot2/1” indicates port 1 of the plugin/card in slot
2.
LSP Link Transport Label Transport (upper) label output by the source device over the LSP
Link.
This is sometimes also referred to as the IGP label.
Reference: IETF RFC 3031 (Multiprotocol Label Switching
Architecture).
LSP Tab Attributes
Attribute Description
LSP Source Source Device name.
LSP Destination Destination Device name.
LSP First Hop IP address of the first hop device on the LSP path from the
ingress PE router.
LSP First Label Transport (upper) label output by the ingress PE router, i.e. the
transport label applied to the first hop of the LSP path.
Reference IETF RFC 3031 (Multiprotocol Label Switching
Architecture).
LSP Hops Node Device (node) name for PE or P router.
LSP Hops Operation Label switching operation performed by the identified node (PE
or P router). The supported operations are as follows:
impose-and-forward
pop-and-forward
pop-impose-and-forward
pop-and-lookup.
Reference: IETF RFC 3031 (Multiprotocol Label Switching
Architecture).
LSP Hops Out Label Outgoing transport (upper) label for the LSP on the identified
node (PE or P router).
Reference: IETF RFC 3031 (Multiprotocol Label Switching
Architecture).
LSP Hops Out Interface Outgoing interface for the LSP on the identified node.
LSP Hops Next Hop Next hop device (node) name and IP address.
For the egress PE router, this field is blank.
Where is not managing the next hop device as an MPLS router,
this field only displays the next hop device IP address.
PW Attributes
Attribute Description
PW Name Name of a PW.
Concatenation of PW ID + PW Source + PW Destination.
Notation <PW ID>-<PW Source>-<PW Destination> is used.
For example “21 – [CTR 1]/Slot2/1 - [CTR 2]/Slot1/1”
Aviat Networks May 2019 175
Contents

Attribute Description
PW Source Source PE router name + Interface for the PW.
Notation <plugin_ID>/<port_number> is used for the
Interface. For example, “Slot2/1” indicates port 1 of the
plugin/card in slot 2.
Reference: IETF RFC 4664 (Framework for L2VPNs).
PW Destination Destination PE router name + Interface for the PW.
Notation <plugin_ID>/<port_number> is used for the
Interface. For example, “Slot2/1” indicates port 1 of the
plugin/card in slot 2.
Reference: IETF RFC 4664 (Framework for L2VPNs).
PW Endpoint A/Z Source/destination PE router name + Interface for the PW.
Notation <plugin_ID>/<port_number> is used for the
Interface. For example, “Slot2/1” indicates port 1 of the
plugin/card in slot 2.
PW Admin Status Admin status (up or down) for a PW.
Reference: IETF RFC 1213 (MIB II).
PW Oper Status Oper status (up or down) for a PW.
Reference: IETF RFC 1213 (MIB II).
L2VPN Tab Attributes
Attribute Description
L2VPN Name For a VPLS service the name is discovered from the device.
For a VPWS service notation <“VPWS”><PW
ID><[source_name] - [destination_name]> is used. For
example “VPWS 10 - [CTR1] - [CTR2]”.
L2VPN ACs List of VPN Attachment Circuits.
Notation <device_name>,<plugin_ID>/<port_number> is used
for each AC.
For example, “CTR1, Slot0/1” indicates CTR1 port 1 of the bank
of Ethernet ports on the mainboard.
Reference: IETF RFC 4664 (Framework for L2VPNs).
L2VPN Signaling Type Signaling type used to signal the PW.
Supported types include ldp-signaled and static.
For a Targeted-LDP signaled PW, the type is ldp-signaled.
Reference: IETF RFC 4664 (Framework for L2VPNs).
L2VPN Service Type Type of L2VPN PW service (Ethernet or TDM).
L2VPN AC VLAN ID L2VPN VLAN Attachment Circuit.
Dot1Q trunking VLAN ID.
Reference: IEEE 802.1Q.
L2VPN AC S-VLAN ID L2VPN S-VLAN Attachment Circuit.
Q-in-Q service provider tunneling S-VLAN ID.
Reference: IEEE 802.1Q.
L2VPN AC C-VLAN ID L2VPN C-VLAN Attachment Circuit.
Q-in-Q customer tunneling C-VLAN ID.
Reference: IEEE 802.1Q.

176 May 2019 Aviat Networks

 Glossary of Technical Terms

RT Link Tab Attributes

Attribute Description
RT Link VRF Source Source PE router name and VRF name for an RT Link.
Each RT Link indicates the flow (export to import) of vpnv4
routes (associated with a configured RT value) between two
VRFs.
Collectively the RT links for a L3VPN indicate the service
topology.
Reference: RFC 4364 (BGP/MPLS IP VPNs).
RT Link VRF Destination Destination PE router name and VRF name for an RT Link.
Each RT Link indicates the flow (export to import) of vpnv4
routes (associated with a configured RT value) between two
VRFs.
Collectively the RT links for a L3VPN indicate the service
topology.
Reference: RFC 4364 (BGP/MPLS IP VPNs).
L3VPN VPN ID A positive integer derived by that uniquely identifies a L3VPN.
See the L3VPN Tab Attributes table below for further details.
RT Link Route Target The Route Target value exported by the RT Link source VRF
and imported by the destination VRF.
Reference: RFC 4364 (BGP/MPLS IP VPNs).
L3VPN Tab Attributes
Attribute Description
L3VPN VPN ID A positive integer derived by that uniquely identifies a L3VPN.
All PE router VRFs configured to share vpnv4 routes (through
the VRF Route Target export / import values) are considered as
members of the same L3VPN, i.e. VRFs connected via RT Links
(see definition above).
Each newly discovered L3VPN is allocated the next lowest
available positive integer value.
Note: Where two or more previously discovered L3VPNs
are subsequently reconfigured and discovered as the same
L3VPN (aka VPN join operation) a new VPN ID is allocated.
And where a previously discovered L3VPN is subsequently
reconfigured and discovered as one or more L3VPNs (aka
VPN split operation) each is allocated a new VPN ID.
In a future release we plan to modify this behavior such that
for VPN join the new VPN retains the VPN ID of the
previous VPN with largest PE membership, and for VPN
split the resultant VPN with largest PE membership retains
the original VPN ID.
L3VPN Topology Type A simple indication of the type of routing topology configured for
the L3VPN service, i.e. the topology as determined by VRF
export RT / import RT configuration.
Indicated types are any-to-any, hub-and-spoke, other.
Reference: RFC 4364 (BGP/MPLS IP VPNs).

Aviat Networks May 2019 177

Contents

Attribute Description
L3VPN VRF Name VRF name configured on a PE router.
Note: VRF name is only unique within a PE router.
VRFs on different PE routers that are members of the VPN
can have different VRF names.
Reference: RFC 4364 (BGP/MPLS IP VPNs).
L3VPN VRF Device PE router name.
L3VPN VRF RD Route Discriminator (RD) value configured on a VRF.
Reference: RFC 4364 (BGP/MPLS IP VPNs).
L3VPN VRF Import RTs List of import Route Target (RT) values configured on a VRF.
Reference: RFC 4364 (BGP/MPLS IP VPNs).
L3VPN VRF Export RTs List of export Route Target (RT) values configured on a VRF.
Reference: RFC 4364 (BGP/MPLS IP VPNs).
L3VPN VRF ACs List of Attachment Circuits (ACs) mapped to a VRF.
Each Attachment Circuit is identified by the interface name (e.g.
Slot4/1) and the interface IP address.
Reference: RFC 4364 (BGP/MPLS IP VPNs).
SyncE Link Tab Attributes
Attribute Description
SyncE Link Source Source device name + Interface of the SyncE Link.
Notation <plugin_ID>/<port_number> is used for the Interface.
For example, "Slot2/1" indicates port 1 of the plugin/card in slot
2.
SyncE Link Destination Destination device name + Interface of the SyncE Link.
Notation <plugin_ID>/<port_number> is used for the Interface.
For example, "Slot2/1" indicates port 1 of the plugin/card in slot
2.
Priority SyncE priority set on the interface. The value can be minimum
1 and maximum 1024.
ESMC Ethernet Synchronization Messaging Channel (ESMC) value can
be either receive-only, transmit-only, both or disabled.
Clock Direction Configured clock direction which can set on GigabitEthernet
ports, otherwise it will be same as ESMC value.
Wait to Restore The wait-to-restore timer ensures that a previously failed clock
source has been fault-free for a specified time (0 to 86,400 sec)
before becoming available for selection, while in the meantime
the QL-Failed status is maintained.
Hold Off Time The hold-off timer ensures that short signal-fail conditions are not
acted on (with settings from 50 to 10,000 msec), while in the
meantime the previous QL level is maintained.
Override Quality Tx/Rx Override quality level.
Quality Currently received clock quality level.
PTP Link Tab Attributes
Attribute Description
PTP Endpoint A Endpoint A device name + Interface of the PTP Link.
Notation <plugin_ID>/<port_number> is used for the Interface.
For example, "Slot2/1" indicates port 1 of the plugin/card in slot
2.

178 May 2019 Aviat Networks

 Glossary of Technical Terms

Attribute Description
PTP Endpoint Z Endpoint Z device name + Interface of the PTP Link.
Notation <plugin_ID>/<port_number> is used for the Interface.
For example, "Slot2/1" indicates port 1 of the plugin/card in slot
2.
PTP Enabled Boolean value to represent whether PTP enabled on the
endpoint.

Aviat Networks May 2019 179

 Functionality Provided by Product Modules

Appendix B: Functionality Provided by

Product Modules
The functionality provided by ProVision Plus for a specific device type is dependent on the licensed
product modules used to manage the device type.
See the ProVision Plus Northbound Interface (NBI) System Integration Guide for details on the
supported NBI functionality.
The following table indicates the functionality provided by each Product Module.

ProVision Plus Function EM Fault EM Integ. CE Fault IP/MPLS Limitations

& Perf For PV & Perf Fault
Deployment:
Deploy Object - Device or Yes
container
Rename, Reparent, Delete Yes
Object (manual)
Deploy device or container via Yes
PV
Deploy L1 Link (manual) Yes Yes
Deploy L1 Link via PV Yes Only for devices with
physical links supported
Deploy IP/MPLS services via Yes
PV
Access Control
Direct Device Access Control Yes
ProVision Network Access Yes
Control
Topology
Devices Tree Yes Yes
Services Tree - L1 Link services Yes Yes
Services Tree- Carrier Ethernet Yes
services
Services Tree- IP/MPLS Yes
services
Map – Devices and L1 Links Yes Yes
Map – Carrier Ethernet services Yes
Map – IP/MPLS services Yes
Data Panel – Devices and L1 Yes Yes Limited data for EM
Links Integration For PV
Data Panel – Carrier Ethernet Yes
services
Data Panel – IP/MPLS services Yes
Detail – Device and L1 Link Yes Yes Limited data for EM
Integration For PV
Detail – Carrier Ethernet Yes
services
Detail – IP/MPLS services Yes
Topology Filtering Yes Yes Yes Yes
Configuration Management

Aviat Networks May 2019 181

Functionality Provided by Product Modules

ProVision Plus Function EM Fault EM Integ. CE Fault IP/MPLS Limitations

& Perf For PV & Perf Fault
Network / Device Detail Yes Yes Limited data for EM
Integration For PV
Network Inventory Yes Yes
Network / Direct Device Mgmt Yes
Create Baseline Yes Yes Yes Yes
Reconciliation Report Yes Yes Yes Yes
Device Config Backup and Yes
Restore
Device Software Loading Yes
Device License Loading Yes
Event/Alarm Management
Event Browser – Device and L1 Yes Yes
Link events
Event Browser – Carrier Yes
Ethernet services events
Event Browser – IP/MPLS Yes
services events
Performance Management
Resource Performance Yes Yes For EM Integ. via PV, only
for CTR 8540/83xx and
Eclipse
Network Health Yes Yes For EM Integ. via PV, only
for CTR 8540/83xx and
Eclipse
Service Diagnostics
IP/MPLS service diagnostics Yes

182 May 2019 Aviat Networks

 Services Alarms Reference

Appendix C: Services Alarms Reference

This section provides a definition of each supported Services Alarm, clarifying the following
information for each:
• Type of Devices Alarm(s) that are mapped to the Services Alarm. This can be one or many.
• Networking layer that the Services Alarm is associated with.
• Severity value (e.g. Critical, Major, etc.) associated with the Services Alarm.
See section Services Alarms (on page 122) for further details on Services Alarms.
Table 84: Physical Layer Services

Alarm Layer Severity Description

L1 link down L1 Link Major A network facing device interface (wireless or Ethernet) that
terminates the L1 Link is down.
L1 link degraded L1 Link Minor Loss of protection has occurred for a protected L1 link.

L1 link fault L1 Link Minor A network facing device interface (wireless or Ethernet) that
terminates the L1 Link has a fault or diagnostic mode active.
L1 link admin L1 Link Info The L1 link is admin disabled.
disabled This is raised as a severity Informational event, to assist with
identifying the root cause of dependent (upper) layer service faults.
Table 85: Carrier Ethernet Services

Alarm Layer Severity Description

VLAN service down VLAN Critical An access port is down on one or more devices.
Note: This alarm is supported for customer bridge C-VLANs
and provider bridge (QinQ) S-VLANs.
VLAN service fault VLAN Minor A fault condition exists with the VLAN or supporting layer service.
Note: This alarm is supported for customer bridge C-VLANs
and provider bridge (QinQ) S-VLANs.
VLAN Link down VLAN Major VLAN Link interface is down on one or both devices that terminate
Link the VLAN Link.
VLAN Link fault VLAN Minor A fault condition exists with the VLAN Link or supporting layer
Link service.
PTP Link Down PTP Link Major The PTP Link interface is down on one or both devices that
terminate the PTP Link
PTP Link Fault PTP Link Minor A fault condition exists with the PTP Link or supporting layer service.

PTP Link PTP Link Minor A supporting layer service is admin disabled.
supporting layer
admin disabled
SyncE Link Down SyncE Major The SyncE Link interface is down on one or both devices that
Link terminate the SyncE Link
SyncE Link Fault SyncE Minor A fault condition exists with the SyncE Link or supporting layer
Link service.
SyncE Link SyncE Minor A supporting layer service is admin disabled.
supporting layer Link
admin disabled

Aviat Networks May 2019 183

Services Alarms Reference

Table 86: IP/MPLS Services

Alarm Layer Severity Description

VPN service down L2VPN Critical PW (carrying SAToP traffic) between the PE routers is down, or a
service AC (Attachment Circuit) is down on one or both PE routers.
VPN service down L3VPN Critical AC (Attachment Circuit) is down on one or more PE routers.

VPN service L2VPN, Minor VPN service is degraded due to loss of protection in a supporting
degraded L3VPN layer service.
For example, failure of either the Working or Protecting LSP for a
supporting TE Tunnel 1:1 protection configuration, results in "TE
Tunnel degraded" alarm, which is propagated to a "VPN service
degraded" alarm.
VPN service fault L2VPN Minor One or more of the L2VPN ACs has a fault or a diagnostic mode
enabled.
VPN service L2VPN, Minor A supporting layer service is admin disabled.
supporting layer L3VPN
admin disabled
PW down PW Major PW (carrying Ethernet traffic) between PE routers is down.

PW degraded PW Minor PW is degraded due to loss of protection in a supporting layer

service.
For example, failure of either the Working or Protecting LSP for a
supporting TE Tunnel 1:1 protection configuration, results in "TE
Tunnel degraded" alarm, which is propagated to a PW degraded"
alarm.
PW fault PW Minor A fault condition exists with the PW or a supporting layer service.

PW T-LDP PW Major Targeted LDP session between the PE routers is down.

neighbor down
PW supporting PW Minor A supporting layer service is admin disabled.
layer admin
disabled
RT Link supporting RT Link Minor A supporting layer service is admin disabled.
layer admin
disabled
TE tunnel down TE Major TE Tunnel is down. For 1:1 protection, this alarm indicates that
Tunnel both working and protecting LSPs are down.
TE tunnel TE Minor Working or Protecting LSP has failed in a TE Tunnel 1:1 protection
degraded Tunnel configuration, or loss of protection in a supporting layer service.
TE tunnel fault TE Minor A fault condition exists with the TE Tunnel or a supporting layer
Tunnel service.
TE tunnel working TE Minor TE Tunnel working LSP is down, and the protecting LSP is up
LSP down Tunnel (actively carrying traffic).
TE tunnel TE Minor TE Tunnel protecting LSP is down, and the working LSP is up
protecting LSP Tunnel (actively carrying traffic).
down
TE tunnel TE Minor A supporting layer service is admin disabled.
supporting layer Tunnel
admin disabled
TE tunnel admin TE Info TE Tunnel is admin disabled.
disabled Tunnel This is raised as a severity Informational event, to assist with
identifying the root cause of dependent (upper) layer service faults.
184 May 2019 Aviat Networks
 Services Alarms Reference

Alarm Layer Severity Description

TE link down TE Link Minor The TE link interface is down on one or both routers that terminate
the TE link.
TE link degraded TE Link Minor TE Link is degraded due to loss of protection in a supporting L1 link
service.
For example, protection is lost in a radio link hot standby protection
configuration.
TE link fault TE Link Minor A fault condition exists with the TE Link or a supporting layer
service.
TE link supporting TE Link Minor A supporting layer service is admin disabled.
layer admin
disabled
TE link admin TE Link Info TE Link is admin disabled.
disabled This is raised as a severity Informational event, to assist with
identifying the root cause of dependent (upper) layer service faults.

Aviat Networks May 2019 185

 IETF and Cisco Terminology Comparison

Appendix D: IETF and Cisco Terminology

Comparison
In future the platform is expected to provide support for different vendors' IP/MPLS routers, in
addition to the currently supported Aviat CTR router platform. This ability is catered for under the
hood through implementation of a standardized data model based on IETF Yang data model
standards. For this reason we've chosen to adopt IETF terminology in the user interface.
As Aviat's CTR router adopts Cisco-like terminology, to assist with translating terms between the
two platforms, this section provides a definition of the equivalent Cisco terminology where an
identified difference exists.
Table 87: IETF and Cisco Terminology Comparison

MANAGE / IETF term CTR / Cisco term IETF Reference

Primary / Secondary Path Primary / Secondary Path draft-ietf-teas-yang-te
Cisco IOS MPLS Reference

Aviat Networks May 2019 187

 260-668271-001
LA Release

WWW.AVIATNETWORKS.COM